Google has introduced Android 3.2, a small update that includes technical advancements and several bugfixes to the Honeycomb tablet environment. The most significant changes in this release allow better assistance for different sizes and display resolutions. Drastically, this will likely open up the door for Seven-inch Honeycomb tablets. Third-party Android developers are also fine-grained grip over how their apps are accessible on specific screens. You can find new useful resource qualifiers that permit developers to optionally generate separate layouts as well as graphical possessions for random ranges of display densities. There are also new characteristics that developers will use in Android patent files to specify the display resolutions their apps are compatible with.

Third-party Android developers usually only need to create a tablet interface and a phone interface for his or her software-they can count on the stage inherent skill to dynamically change layouts so that you can assistance all of the versions on particular sizes. The fine-grained useful resource qualifiers and new display compatibility features are primarily for giving developers much more flexibility in edge instances where the platform's local layout expansion abilities are insufficient.

One more new feature in Android 3.2 is a "screen compatibility mode" that includes a pixel-scaling device for stretching apps to fill the screen. This function basically works such as the iPad's pixel replication It should hardly ever be required to perform on Android tablets since the platform's inhabitant layout expansion usually offers a improved user understanding. A few of the new changes to match different display resolutions in 3.2-particularly things like the new generic tvdpi display screen density description for televisions-seem similar to preemptive moves to arrange for sustaining third-party Android apps on Google TV.