The Dell Streak is a 800x480 mdpi screen. This places it into the xlarge screen bucket. The Xoom is a typical 10” tablet with a 1280x800 mdpi screen. Converting to mdpi (a 4/3 scaling factor) gives us 426dp x 320dp this matches the minimum size above for the small screen bucket. Here are some more examples of how this works with real screens:Ī QVGA screen is 320x240 ldpi. (Android does not currently support screens smaller than this.) Small screens are at least 426dp x 320dp. Normal screens are at least 470dp x 320dp. Large screens are at least 640dp x 480dp. Xlarge screens are at least 960dp x 720dp. #Android studio emulator change resolution android#Android 2.3 introduced a new bucket size “xlarge”, in preparation for the approximately-10” tablets (such as the Motorola Xoom) that Android 3.0 was designed to support. Devices that fall in the “large” bucket include the Dell Streak and original 7” Samsung Galaxy Tab. Screen-size BucketsĪndroid has included support for three screen-size “buckets” since 1.6, based on these “dp” units: “normal” is currently the most popular device format (originally 320x480, more recently higher-density 480x800) “small” is for smaller screens, and “large” is for “substantially larger” screens. The conversion factor from hdpi to mdpi in this case is 1.5, so for a developer's purposes, the device is 320x533 in dp's. A more recent phone might have physical-pixel dimensions of 480x800 but be a high-density device. In medium-density ("mdpi") screens, which correspond to the original Android phones, physical pixels are identical to dp's the devices’ dimensions are 320x480 in either scale. To remove the size/density calculations from the picture, the Android framework works wherever possible in terms of "dp" units, which are corrected for density. This is why the 320x480 screen on a G1 and 480x800 screen on a Droid are both the same screen size: the 480x800 screen has more pixels, but it is also higher density. These are interrelated: increase the resolution and density together, and size stays about the same. Resolution is the actual number of pixels available in the display, density is how many pixels appear within a constant area of the display, and size is the amount of physical space available for displaying your interface. Understanding Screen Densities and the “dp” Of course, the official write-up on Supporting Multiple Screens is also required reading for people working in this space. We also provide our recommendations for how you can do layout selection in apps targeted at Android 3.2 and higher in a way that should allow you to support the maximum number of device geometries with the minimum amount of effort. If you know all that stuff, you can skip down to “Introducing Numeric Selectors” to read about what’s new. We start by discussing the why and how of Android “dp” arithmetic, and the finer points of the screen-size buckets. This release also offers several new APIs to simplify developers’ work in adjusting to different screen sizes. One important result is better support for a new size of screen what is typically called a “7-inch” tablet. Android 3.2 includes new tools for supporting devices with a wide range of screen sizes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |