Is it then true that the OS works only in the stepped values of 120, 160 and 240?
Also, any idea if xdpi and ydpi would be fixed anytime soon? Or if some APIs would allow us to query the physical dimensions of the screen? Thanks, Ashutosh On Jan 25, 2:39 pm, Romain Guy <[email protected]> wrote: > This is a known bug. Although screenDPI=240 is the correct value (it's > not the real density of the display, but the density used by the OS > for that screen.) > > > > On Mon, Jan 25, 2010 at 1:37 AM, Ashutosh Sharma <[email protected]> wrote: > > Hi, > > > xdpi and ydpi are currently returning 96 on a Motodola Droid device. > > screenDPI returns a stepped value of 240, which still isn't the > > correct value. This issue was also present much earlier (pre-cupcake) > > -http://groups.google.com/group/android-developers/browse_thread/threa... > > > Is this a known bug? Is this expected to be fixed soon? Given the > > varying pixel densities of devices that are coming up, having a way to > > obtain accurate screen DPI is essential. > > > Thanks, > > Ashutosh > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected] > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en > > -- > Romain Guy > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time > to provide private support. 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
