On Tue, Sep 8, 2009 at 10:44 AM, Al Sutton<[email protected]> wrote: > > Most of the WVGA Android devices I've seen announced are 5" media > tablets. > > This has *everything* to do with my monitor because it's what the > emulator is being displayed on.
Not really. The emulator, by default, displays the framebuffer and that's it. So only the resolution matters. It doesn't give you any idea of the screen size being displayed. As Romain mentioned, using -scale <your monitor dpi>dpi will scale the emulator to roughly emulate the actual screen size. Using '-scale 96dpi' on a w...@160dpi and w...@240dpi will result in different scaling. > I'm not saying that the dpi of my > monitor should be the same as the dpi of the emulator, what I am > saying is if I open an QVGA, HVGA, or WVGA sized window in the native > OS the dpi stays the same, therefore if I request a QVGA, HVGA, or > WVGA sized screen for the emulator and it opens a QVGA, HVGA, or WVGA > sized window I wouldn't expect the emulator to start changing the dpi > *as well* without either asking or warning me. Actually your are warned (kinda). When you create an AVD based on android 1.6, at the end it'll tell you it created it with the following hardware config: hw.lcd.density=240 We should probably make it more obvious, but then we'd probably need make the whole hardware config more obvious. For example, hat tablet you keep referring to has no navigation buttons (d-pad/trackball) and yet the emulator will emulate one. Xav -- Xavier Ducrohet Android Developer Tools Engineer Google Inc. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
