Er... since when could we do that? As far as I know the exact qualifiers only came about in Android 3.2.
layout-large-port-xhdpi-1280x800 I am thinking layout-large-port-xhdpi would make sense, though. I also want to target the Samsung Galaxy Tab 7" specifically, but there isn't a better way besides doing layout-large-hdpi which will sabotage future devices. Meanwhile I would have to say that from an app statistics, these two devices are actually at the top of the installs... and in fact, I doubt there would truly be a layout-large-hdpi device that is anywhere as popular as these two. On Jan 22, 3:31 pm, Doug <[email protected]> wrote: > You're right about the Note being stupid. But I'll tell you exactly > why it's stupid, because I went through this too. There is a thread > in this group if you want to find and follow that. > > The note is "large", which is technically within bounds. Large > screen, according to Google documentation, can be between roughly 4 > and 7 inches. The docs also say "large screens are at least 640dp x > 480dp". This is where the Note is stupid. > > The Note also happens to be "xhdpi", which means that its pixels are > supposed to be about half the size of the mdpi baseline for > calculating dp. So if a large mdpi screen must be at least 640x480, > then xhdpi must be at least 1280x960. As you may know, the note is > actually 1280x800. This means that it's missing an expected 160 > pixels (80dp) on its short edge. If your layouts are (correctly) > assuming this space exists, something may go wrong when it comes time > to draw. > > I got around this by having a Very Special layout for the Note. You > can target pixels sizes in your resource specifiers like this: layout- > large-port-xhdpi-1280x800. Then in your layouts just do what you need > to do without the extra space. I took it on good authority that it's > a Bad Idea to target dimensions size in resource specifiers, but it's > what I had to do to make it work without redesigning a very important > screen in my app. Please don't email me for support! > > Have fun. > > Doug > > On Jan 20, 6:05 am, Chris <[email protected]> wrote: > > > > > > > > > Thanks > > I will just exclude , can't find any other stupid devices like the > > note. > > Kindle sales are in the 100's per day , not doing all that change for > > a few Galaxy Note's. > > > It's a shame Google did not sort this mess out on an earlier release , > > it's becoming a real pain > > > On Jan 20, 1:45 pm, Mark Murphy <[email protected]> wrote: > > > > On Fri, Jan 20, 2012 at 8:40 AM, Chris <[email protected]> wrote: > > > > I am having issues support the Galaxy Note > > > > > My app runs on Android 2.1+ , so I can't use the DPI based screen > > > > differentiation , and the Galaxy note is 2.3.5 I believe. > > > > > My app has a normal display size which works great for small/normal , > > > > I also have a large display layout that has been working great for > > > > 7-10inch tablets like Xoom and Amazon Kindle Fire. > > > > > However this Galaxy Note has thrown a spanner in the mix. > > > > > It is displaying itself as a Large , but my display does not fit on > > > > the screen. > > > > The normal layout looks fine on it. > > > > > Any ideas how I can make that device use the normal display ? > > > > You can't. You need to create a -large set of resources that work well > > > on the Galaxy Note and Kindle Fire. The XOOM can use -xlarge > > > resources, if the revised -large ones do not work well on a 10" > > > screen. > > > > > at the > > > > moment I am tempted to just exclude it from compatible devices - but > > > > if there is an elegant workaround it would be better ! > > > > Bear in mind that your issue is not strictly one tied to the Galaxy > > > Note. I would expect you to encounter similar problems on > > > similarly-sized devices. > > > > -- > > > Mark Murphy (a Commons > > > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > > > Android 4.0 Programming Books:http://commonsware.com/books -- 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
