Thanks String. Although I agree that 169 should not be considered HDPI, if you create an AVD with the same PPI and size, even though it is a generic device, it comes back with the 1.5 factor. So, it is hard to blame Samsung on this one. Next time I create a big app, I will try to use default font sizes and lay it out so that there are as few direct assignments of sizes of objects as possible, as Mark was implying with using wrap_content. Unfortunately, it got too tempting to make the app look as good as possible!
Kim On Nov 17, 12:05 pm, String <sterling.ud...@googlemail.com> wrote: > I'm assuming this is the original Tab? If so, there was some consternation > when it was released because Samsung configured it as HDPI even though its > true pixel density (169 DPI) is well within the MDPI range. It's basically > an outlier in the 7" tablet space, and makes life difficult for virtually > any tablet apps. > > One thing that I have found helpful was to do my Large layouts in inches, > rather than dp/dip. So, instead of 16dp (for example), you'd specify it as > 0.1in. I don't recommend doing this across all your layouts, but for the > "large" category, it seems to work pretty well. And FWIW, I found better > cross device support for "in" (inches) than "mm" (millimeters). > > String -- 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
