Don't believe written documentation at this point, there has been some chaos in this. The current official numbers used by the platform implementation are:
Normal -- 320dp x 480dp Large - 480dp x 640dp XLarge - 720dp x 960dp Technically in the impl Small is just smaller than normal, but as per the CDD the smallest this can be is 320dp x 426dp. * *I really need to write a blog post about this, especially on conjunction with some other stuff coming up. :} On Mon, Jun 20, 2011 at 9:57 PM, Zsolt Vasvari <zvasv...@gmail.com> wrote: > Dianne, I found the following table in attrs_manifest.xml > > <attr name="screenSize"> > <!-- A small screen configuration, at least 240x320db. --> > <enum name="small" value="200" /> > <!-- A normal screen configuration, at least 320x480db. -- > > > <enum name="normal" value="300" /> > <!-- A large screen configuration, at least 400x530db. --> > <enum name="large" value="400" /> > <!-- An extra large screen configuration, at least > 600x800db. --> > <enum name="xlarge" value="500" /> > </attr> > > Are those correct? I couldn't find the code where it would do the > checking -- I guess it's in native code. > > On Jun 21, 10:17 am, Zsolt Vasvari <zvasv...@gmail.com> wrote: > > Thanks, Dianne. I am actually happy that OEMs are trying to "push the > > envelop" with these devices. Some of these strange form factors may > > stick. > > > > So the division point between normal and large is 480dp x 640dp. > > > > Can you please tell me (or point me to a source) what the division > > points between small/normal and large/xlarge are? > > > > On Jun 21, 9:51 am, Dianne Hackborn <hack...@android.com> wrote: > > > > > > > > > Yeah, 240/160. hdpi == 240, mdpi == 160. > > > > > This device should not normally run applications on both screens. > > > > > Actually, this is what they did: > https://market.android.com/details?id=com.kyocera.tabletmodeextension... > > > > > So it is a compatible device for purposes of passing the CDD, but you > can > > > download an app of theirs that makes it incompatible. > > > > > Writing the CDD sometimes feels like trying to do a deal with the > devil. :p > > > > > On Mon, Jun 20, 2011 at 6:41 PM, Zsolt Vasvari <zvasv...@gmail.com> > wrote: > > > > Got it. It's the density float in DisplayMetrics. > > > > > > On Jun 21, 9:36 am, Zsolt Vasvari <zvasv...@gmail.com> wrote: > > > > > I am sorry, how did you get > > > > > > > 533dp x 640dp > > > > > > > from > > > > > > > 800x960 hdpi screen? > > > > > > > Can you please provide this calculation? Obviously, you divided by > > > > > 1.5, but where did the 1.5 magic constant come from? I would like > to > > > > > use this info to determine in my app if I am running on a screen at > > > > > least LARGE and do some stuff differently. > > > > > > > On Jun 21, 9:19 am, Dianne Hackborn <hack...@android.com> wrote: > > > > > > > > To be compatible, a device like this would need to run apps in > only one > > > > of > > > > > > the screens. What it means to run in two screens is not well > defined. > > > > > > > > Fwiw, the division point between normal and large is 480dp x > 640dp. So > > > > a > > > > > > 800x960 hdpi screen is 533dp x 640dp, just barely classifying as > large. > > > > On > > > > > > the other hand the aspect ratio of that screen is only 1.2, which > is > > > > not > > > > > > compatible according to the CDD. It is also not compatible to > change > > > > the > > > > > > screen configuration, so there are two reasons it must run > applications > > > > on > > > > > > one screen for compatibility. > > > > > > > > On Mon, Jun 20, 2011 at 5:24 PM, Zsolt Vasvari < > zvasv...@gmail.com> > > > > wrote: > > > > > > > The Flipout has a 320x240 screen. Ths is definetely the > Kyocera > > > > Echo. > > > > > > > > > My only question when supporting this device is if the screen > > > > > > > consdered Medium or Large? 4.7" seems to be borderline on the > screen > > > > > > > size chart. > > > > > > > > > On Jun 20, 11:40 pm, Dan <dan.schm...@gmail.com> wrote: > > > > > > > > My bet is the Motoroal Ruth/Flipout > > > > > > > > > >http://phandroid.com/motorola-flipout/ > > > > > > > > > > On Jun 19, 6:56 pm, Zsolt Vasvari <zvasv...@gmail.com> > wrote: > > > > > > > > > > > As part of my app, if I notice a screen size/DPI combo I > haven't > > > > > > > > > tested on, I pop-up a dialog and ask the user to send me an > > > > e-mail > > > > > > > > > about that. > > > > > > > > > > > Here's what I got yesterday: > > > > > > > > > > > Display width: 800 > > > > > > > > > Display height: 960 > > > > > > > > > Display DPI: 240 > > > > > > > > > > > Anybody has a clue as to what kind of device has a 800x960 > > > > squarish > > > > > > > > > screen. The HDPI indiciates that it's a phone. I asked > the > > > > user, but > > > > > > > > > he hasn't come back to me -- my guess it's something > unreleased.- > > > > Hide > > > > > > > quoted text - > > > > > > > > > > - Show quoted text - > > > > > > > > > -- > > > > > > > You received this message because you are subscribed to the > Google > > > > > > > Groups "Android Developers" group. > > > > > > > To post to this group, send email to > > > > android-developers@googlegroups.com > > > > > > > To unsubscribe from this group, send email to > > > > > > > android-developers+unsubscr...@googlegroups.com > > > > > > > For more options, visit this group at > > > > > > >http://groups.google.com/group/android-developers?hl=en > > > > > > > > -- > > > > > > Dianne Hackborn > > > > > > Android framework engineer > > > > > > hack...@android.com > > > > > > > > Note: please don't send private questions to me, as I don't have > time > > > > to > > > > > > provide private support, and so won't reply to such e-mails. All > such > > > > > > questions should be posted on public forums, where I and others > can see > > > > and > > > > > > answer them.- Hide quoted text - > > > > > > > > - Show quoted text -- Hide quoted text - > > > > > > > - Show quoted text - > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "Android Developers" group. > > > > To post to this group, send email to > android-developers@googlegroups.com > > > > To unsubscribe from this group, send email to > > > > android-developers+unsubscr...@googlegroups.com > > > > For more options, visit this group at > > > >http://groups.google.com/group/android-developers?hl=en > > > > > -- > > > Dianne Hackborn > > > Android framework engineer > > > hack...@android.com > > > > > Note: please don't send private questions to me, as I don't have time > to > > > provide private support, and so won't reply to such e-mails. All such > > > questions should be posted on public forums, where I and others can see > and > > > answer them.- Hide quoted text - > > > > > - Show quoted text -- Hide quoted text - > > > > - Show quoted text - > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
