Android 1.6 supports more screen sizes and resolutions

An important change in Android 1.6 is to support more types of screen sizes. This is good news for both hardware manufacturers and end users, but it is important for developers to leave it alone, this means they have to perform more tests and adjustments before releasing their own programs to adapt to devices with different screen sizes. Of course, we also hope to see more devices supported by Android. If there is a loss, let's stop complaining and see how to deal with it.
So far, the screens of Android devices (such as T-Mobile G1 and Samsung i7500) on the market are hvga (320x480), In 1.6, the device screen size is divided into three types:
1. Small Screen: smaller than G1 and i7500. For example, the latest HTC tattoo
2. Middle screen: it is as big as G1 and i7500
3. Big Screen: as the name suggests, it is bigger than the two above.
Google said that this category is too dominant: "All devices can be divided into one of these three categories ".
At the same time, 1.6 also has the following new features:
1. You can specify the types of screens (large, medium, and small) supported by your software in androidmanifest)
2. Use the newly added API to use image resources and layout in a screen size-independent manner
3. Existing programs in Android 1.6 (programs written using sdks earlier than Android 1.6) can run in a simulated hvga environment.
If the existing program is not upgraded to the SDK of 1.6, market will consider it to be for the screen-in-screen device. By default, it is only displayed on the screen and the screen-in-screen device, of course, the screen device will run these programs in the above-mentioned hvga compatibility mode. Small screens can only use software that explicitly declares support for small screens. The reason is simple: narrowing down a large interface will often lead to poor user experience (on the contrary, it is acceptable to enlarge a small interface, some users may even give your program a poor rating (Google may think about developers more ;)).
Google said the small screen device (HTC tattoo ?) It is expected to invest in the market before Christmas (maybe not Christmas, originally: in time for
Holiday season. Which holiday is it? Hope you can advise), and not all devices will be upgraded to 1.6 at the same time, so even if 1.6 is widely used
A considerable number of devices still run 1.5. That is to say, developers must be confused when selecting the SDK version. Google suggests: If you only want to publish one
If you want the APK to run on both 1.5 and 1.6, use the 1.5 SDK to compile your program and test it on the 1.5 and 1.6 systems. If your
The program wants to seize the HTC tattoo market and use 1.6. If you want your program to run perfectly on three screens, use 1.6 (it seems that only three versions of UI can be written ).

Via: http://android-developers.blogspot.com/2009/10/support-for-additional-screen.html
(Wall now)