Re: [android-developers] Re: Supporting Galaxy Note Issues Due To It Displaying Itself as a LARGE screen layout.
On Sunday, 27 May 2012 04:57:06 UTC+2, Dianne Hackborn wrote: On Sat, May 26, 2012 at 11:36 AM, b0b wrote: In short, f... Samsung and the Galaxy Note for this huge mess. And thanks Google for not thinking about the new Android 3.2 qualifiers, *before*. You're very welcome. I apologize for my ranting tone in previous message. I had spent several hours thinking about the best way to address this issue at the time of writing. Your article on the developers blog on the 3.2 qualifiers has been very helpful to understand the issue. -- 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
Re: [android-developers] Re: Supporting Galaxy Note Issues Due To It Displaying Itself as a LARGE screen layout.
I'm in the middle of addressing the Galaxy Note layouting and found this thread. This device is an anomally with its large/xhdpi nature on Gingerbread, breaking the long standing assumption that large = tablet. Of course Samsung knew they were going to break stuff. According to the latest stats, large/xhdpi doesn't exist: http://developer.android.com/resources/dashboard/screens.html Making correct layouts for all possible size combination is getting more and more difficult and time consuming and is a real nightmare. -- 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
Re: [android-developers] Re: Supporting Galaxy Note Issues Due To It Displaying Itself as a LARGE screen layout.
On Saturday, 26 May 2012 18:23:18 UTC+2, b0b wrote: I'm in the middle of addressing the Galaxy Note layouting and found this thread. Speaking of which...the Galaxy Note is a 800px x 1280px device with generalized dpi = 320 (xhdpi bucket) Which makes the general density factor = 2 (the DisplayMetrics.density value) which makes it a 400dp x 640dp device. How can this be in the large category specified as at least 640dp x 480dp ? -- 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
Re: [android-developers] Re: Supporting Galaxy Note Issues Due To It Displaying Itself as a LARGE screen layout.
Samsung also used interesting screen metrics on the original Galaxy Tab P1000. But back then, 1) the size buckets weren't what they are now 2) there were few apps with tablet specific layouts, so their motivation could possibly be trying to up-scale the entire app. As for me, I design my -large / -xlarge layouts based on the real devices out there, rather than the theoretical limits in the docs, which Samsung is allowed to break. The Galaxy Note is very popluar, and there are still many users with the Galaxy Tab P1000 and its no-name clones. -- K 26.05.2012 21:03, b0b написал: which makes it a 400dp x 640dp device. How can this be in the large category specified as at least 640dp x 480dp ? -- Kostya Vasilyev -- 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
Re: [android-developers] Re: Supporting Galaxy Note Issues Due To It Displaying Itself as a LARGE screen layout.
As for me, I design my -large / -xlarge layouts based on the real devices out there, The Galaxy Note is absolute pain as my -large layouts are made for tablets (ie at least 7 or smallest Width = 600dp). The Note can be handled nicely with the new sw qualifier introduced in Android 3.2 with the tablet/phone distinction at sw600dp. However my large layout must work for 10 and 7 tablets, thus I cannot use xlarge for this (7 tablets are in the large bucket) To manage the Galaxy Note on pre-Android 3.2, I must introduce -large-xdpi resource directories for layout, values, xml categories, which are just copy of the the normal folders (since the Note really should be treated as a normal screen device). In short, f... Samsung and the Galaxy Note for this huge mess. And thanks Google for not thinking about the new Android 3.2 qualifiers, *before*. Really this situation for just essentially one device really makes me want to leave the Note with shitty layouts or marked as incompatible. -- 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
Re: [android-developers] Re: Supporting Galaxy Note Issues Due To It Displaying Itself as a LARGE screen layout.
On Sat, May 26, 2012 at 11:36 AM, b0b pujos.mich...@gmail.com wrote: In short, f... Samsung and the Galaxy Note for this huge mess. And thanks Google for not thinking about the new Android 3.2 qualifiers, *before*. You're very welcome. -- 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
Re: [android-developers] Re: Supporting Galaxy Note Issues Due To It Displaying Itself as a LARGE screen layout.
I just changed to the compatibility-screens qualifiers (or elements depending on which article you read) and filtering looks fine in the developer console. But now my A500 is shown as incompatible. For 10+ screens only I used: compatible-screens !-- high density xlarge size screens -- screen android:screenSize=xlarge android:screenDensity=xhdpi / /compatible-screens Logically that should keep that version to 10 screens and 720p or higher. But that is supported with the A500 so they must have their data wrong on the A500. On 03/15/2012 06:22 PM, Zsolt Vasvari wrote: Why are you surprised this is broken on Google Play. For my app, the Acer Iconia A500 doesn't even show up on the supported device list even though I have no filters/qualifiers/etc at all. On Wednesday, February 8, 2012 7:38:57 AM UTC+8, Doug wrote: On Feb 5, 6:22 am, Daniele Segatodaniele.seg...@gmail.com wrote: On 01/20/2012 02:40 PM, Chris wrote: My app runs on Android 2.1+ , so I can't use the DPI based screen differentiation , are you sure about this? I can tell you that I created an emulator with Android version 2.3.3, told it to be 1280x800, and it picked up my very specific layout that I stored in layout-large-port-xhdpi-1280x800. Was that a fluke? I don't know. But we haven't had any complaints from Note users, whereas if the old layout was used, we would definitely receive some complaints. I think Samsung was aware of the problems with the way that the Note works with some apps, because my company was directly contacted by a representative from Samsung who helped us work out the layout issue with our app on the Note. Doug -- 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
Re: [android-developers] Re: Supporting Galaxy Note Issues Due To It Displaying Itself as a LARGE screen layout.
It would be nice to have a tool that we can confirm how these display qualifiers will show up on Play before we actually upload. Otherwise it could be trial and error. I recently had someone get the Honeycomb version I created for 10 and larger minimum 720p screens who has a 1024x600 7 and of course that version crops the right side and bottom of the screen. He should have gotten the other version that is tabbed and will work fine with smaller screens. The qualifier didn't filter. On Tuesday, February 7, 2012 4:33:37 PM UTC-8, Dianne Hackborn wrote: On Sun, Feb 5, 2012 at 5:42 AM, albnok wrote: 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. You should never, ever see a resource qualifier like that. That is, frankly, insane. Also mixing density with screen size almost certainly means you are doing something on. I can guarantee that you that there will be device configurations in the future that break with such things, because density has *nothing* to do with screen size. The first this is please, please read the documentation and my blog post here: http://android-developers.blogspot.com/2011/07/new-tools-for-managing-screen-sizes.html The blog post includes examples of how to use the new selectors in a compatible way with older devices. Also, yes, the large size bucket is problematic, as the blog post discusses. There isn't anything we can do to help this for older versions of the platform. My suggestion if you need to deal with this is to just fall back on doing it programmatically -- define two layouts that are not qualified by screen size, and when your code runs look at the actual screen size (converted to dp units) and pick the one to use based on that. Or alternatively, just forget about large, code against xlarge and the new -sw qualifier, and make sure your normal layout resizes reasonably when running on a larger screen. -- Dianne Hackborn Android framework engineer 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
Re: [android-developers] Re: Supporting Galaxy Note Issues Due To It Displaying Itself as a LARGE screen layout.
On Sun, Feb 5, 2012 at 5:42 AM, albnok alb...@gmail.com wrote: 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. You should never, ever see a resource qualifier like that. That is, frankly, insane. Also mixing density with screen size almost certainly means you are doing something on. I can guarantee that you that there will be device configurations in the future that break with such things, because density has *nothing* to do with screen size. The first this is please, please read the documentation and my blog post here: http://android-developers.blogspot.com/2011/07/new-tools-for-managing-screen-sizes.html The blog post includes examples of how to use the new selectors in a compatible way with older devices. Also, yes, the large size bucket is problematic, as the blog post discusses. There isn't anything we can do to help this for older versions of the platform. My suggestion if you need to deal with this is to just fall back on doing it programmatically -- define two layouts that are not qualified by screen size, and when your code runs look at the actual screen size (converted to dp units) and pick the one to use based on that. Or alternatively, just forget about large, code against xlarge and the new -sw qualifier, and make sure your normal layout resizes reasonably when running on a larger screen. -- 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
Re: [android-developers] Re: Supporting Galaxy Note Issues Due To It Displaying Itself as a LARGE screen layout.
On Sun, Feb 5, 2012 at 8:42 AM, albnok alb...@gmail.com wrote: 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 The exact qualifiers (-1280x800) were deprecated some time ago. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 4.1 Available! -- 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
