icon in Droid is badly scaled

by yidongsoft » Thu, 14 Jan 2010 17:26:02 GMT

Sponsored Links
 In my G2, the icon is ok. But in Droid, the icon look bad. The
skeleton is good, but the icon is scaled and the icon looks cheap. I
try to set the icon big in resolution, but the button enlarged and the
balance of layout is break. Can any one help me to fix it? Thanks!

icon is not the icon for application present on desktop, but normal
ones present on image button.


icon in Droid is badly scaled

by Lance Nanek » Thu, 14 Jan 2010 23:17:06 GMT

 You can use the hdpi qualifier on a resource directory to provide a
higher resolution version for the Droid that it won't try to scale. If
your image is currently in "res/drawable", for example, you can put a
high resolution version of it in "res/drawable-hdpi-v4". The normal
drawable folder is considered medium display density, so Droid will
scale things up from that by default.

To avoid bad looking scaling you should also make sure your app isn't
in compatibility mode re supporting multiple screen resolutions by
setting your uses-sdk and supports-screen manifest elements to avoid
that. See the documentation for details:

> Thanks!

Sponsored Links

icon in Droid is badly scaled

by yidongsoft » Fri, 15 Jan 2010 08:58:49 GMT

 Thank you! I will give a summary later.

> > Thanks!

Other Threads

1. How the sensor daemon(akmd2) communicate the application?

Hi all.
I am digging into the structure of sensor, especially compass sensor.
when I was following the flow from compass.java to kernel driver of
compass, I was stuck at the communication between sensors HAL and
Following is the flow of compass sensor from application.
onSensorChanged Listener in compass.java -> thread sensors_data_poll
run in SensorManager.java -> sensors_data_poll() in
android_hardware_SensorManager.cpp JNI -> sensors_data_poll() in
Then I was stuck at the loop of sensors_data_poll(). It seems that the
socket is the key to communicate between the poll loop and the akmd2
but I can't find the code how to make the socket, open, write( from
the akmd2 daemon to the sensors_data_poll()), read.
any helps would be appreciated.
thanks in advance.

unsubscribe: android-porting+unsubscr...@googlegroups.com

2. Why does booting time reduce from 2 min to 1 min after just adding a printk(..) invoking?

Well, as Greg said, the first thing you should do is use initcall_debug.
See http://elinux.org/Initcall_Debug

Also, try turning on timestamps for printks with "time" on the kernel
command line. See http://elinux.org/Printk_Times

Is it the kernel that's taking 2 minutes, or the whole system?

Note that on Android, the very first boot of a newly installed system
will take a very long time, due to building a dalvik cache of pre-processed

Just inserting a single printk in the initcall loop shouldn't have
any effect on bootup time.

If you're still seeing funny stuff after turning on some more
timing debugging info, please send you kernel message log output.
 -- Tim

Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Network Entertainment

unsubscribe: android-kernel+unsubscr...@googlegroups.com

3. Android Drivers being dropped from Kernel 2.6.34

4. Dalvick VM trigger

5. help on singleinstance launchmode behavior

6. How to save an object in onSaveInstanceState?

7. /dev/log/radio, /dev/log/events