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
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
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
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
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
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
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
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
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
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
10 matches
Mail list logo
