What should be the image resolution for Nexus One or Droid?

by javame_android » Mon, 12 Apr 2010 20:27:41 GMT


Sponsored Links
 Hi,

As Android supports multiple devices from different manufacturers
there are different screen resolutions supported.

The table that is available at
 http://developer.android.com/intl/fr/guide/practices/screens_support.html #screen-independence
is not very clear to me.

It shows WVGA and FWVGA in MDPI for Large Screens and HDPI for Normal
screens. So, if the image is kept in drawable-mdpi and its resolution
is 320 * 480 then which image will be taken by Large Screens device of
MDPI.

Moreover, there are two screen resolutions for HDPI i.e. 480 * 800 and
480 * 854. So, with what screen resolution the image should be built.

I want to place the background image which looks distorted in WVGA
emulator since its resolution is 320 * 480.

I have read about nine patchable images but I think they are better
for button images and edittext images so that they can stretch
according to the data in it.

Can someone please guide me in this?


Regards
Sunil

--



Other Threads

1. ADC2 submission: Aurora Device Search (was Aurora 1.0 is available in MarketPlace - more than device search)

Hi community,

I'm happy to announce that  Aurora Device Search has been submitted to ADC2.
It has been published in MarketPlace for a while, and already get many good
feedback from the community (
http://www.cyrket.com/package/com.aurora.android.search). Thanks a lot to
the community!  Here's a short introduction of Aurora Device Search.

Aurora Device search is a full text device search tool on Android. Like
spotli...@mac, Aurora shows search result dynamically as typing. Searched
data scope include:

* Contacts
* Calendar Event
* Application name
* Web history
* Web bookmark
* SMS/MMS
* Audio
* Video
* Image
* SDCard files

What's more, Aurora emphasizes the intelligence of search ranking, and user
accessibility. Highlight features include not limited to:

* Intelligent search ranking based on user behavior. Most frequently used
resources will in the top list. Aurora learns user's habit so that the
longer time you use Aurora, the less letters you may type to find the target
resource.

* Quick share data to your friends. User can share contact card, calendar
event, web link, pictures, and all kinds of data to friends via
sms/mms/gmail.

* Shortcut buttons. It makes user operation much easier. i.e uninstalling an
application, user only needs to type first letters of the application name,
and press "manage" button in the screen. Much easier than going to "Setting"
-> "Manage application" -> .... -> "Uninstall".

* Convenient context menu. Most operations can be done via context menu, so
that Aurora can be your mobile entry.

and more...

Experience Aurora by downloading from MarketPlace!
Any comment, suggestion and bug report are highly appreciated. Please
mailto:3crownt...@gmail.com. Thank you!





--~--~---------~--~----~------------~-------~--~----~

2. Key & Value pair in a spinner

Hey, I was wondering how to put a string array in a spinner (I can,
using the ArrayAdapter) but I also want to set keys for these also.
But it seems that there's no constructors for that (I may be
mistaken).

I have 2 arrays: {"5123", "7434", "7333", "7345" } and {"City 1",
"City 2", "City 3", "City 4" }. Obviously, the spinner UI should show
the name array of the cities, but in the backend (what's returned from
the submission of the form is the value.

Anyone knows how?


// Put the array in the spinner
ArrayAdapter<String> adapter = new ArrayAdapter<String>(this,
android.R.layout.simple_spinner_item, cityNames);
spinCities.setAdapter(adapter);



While, I'm the subject of spinners: is there any resource on the
internet describing every type of spinner layouts? I'm using
simple_spinner_item but I find it too small. Any suggestions?

Thanks.

--~--~---------~--~----~------------~-------~--~----~

3. AlarmClock app API ?

4. submenu

5. Still seriously perplexed about how to build the dev environment

6. MapView Not zooming to center but to top left

7. GPS coordinates within certain radius based on current location