Don't believe written documentation at this point, there has been some chaos
in this. The current official numbers used by the platform implementation
are:
Normal -- 320dp x 480dp
Large - 480dp x 640dp
XLarge - 720dp x 960dp
Technically in the impl Small is just smaller than normal, but as per
Ok, thanks.
I am testing on the original 7 Galaxy Tab, which is a 600x1024 HDPI
device, which gives 400dpx683dp, so unless I am misunderstanding you,
it should be classificed as a Normal screen device, but it seems to be
pulling resources from the Large folders.
Is there special handling for
When I say, it's a 600x1024 HDPI device, I mean that's what's reported
by DisplayMetrics, even though, in reality, MDPI would be closer.
On Jun 21, 2:58 pm, Zsolt Vasvari zvasv...@gmail.com wrote:
Ok, thanks.
I am testing on the original 7 Galaxy Tab, which is a 600x1024 HDPI
device, which
Yes that is the main thing I am talking about there being some chaos in the
definitions. :/
On Mon, Jun 20, 2011 at 11:58 PM, Zsolt Vasvari zvasv...@gmail.com wrote:
Ok, thanks.
I am testing on the original 7 Galaxy Tab, which is a 600x1024 HDPI
device, which gives 400dpx683dp, so unless I
Yeah, you are right. It has to be this phone being tested by
somebody.
One of the 4 modes are:
•Tablet Mode with one application spread across both screens for a
full 4.7-inch viewing area 800x960
On Jun 20, 1:41 pm, Jitesh dedhiya jitesh.dedh...@gmail.com wrote:
Yeah i think its not
My bet is the Motoroal Ruth/Flipout
http://phandroid.com/motorola-flipout/
On Jun 19, 6:56 pm, Zsolt Vasvari zvasv...@gmail.com wrote:
As part of my app, if I notice a screen size/DPI combo I haven't
tested on, I pop-up a dialog and ask the user to send me an e-mail
about that.
Here's what
The Flipout has a 320x240 screen. Ths is definetely the Kyocera Echo.
My only question when supporting this device is if the screen
consdered Medium or Large? 4.7 seems to be borderline on the screen
size chart.
On Jun 20, 11:40 pm, Dan dan.schm...@gmail.com wrote:
My bet is the Motoroal
To be compatible, a device like this would need to run apps in only one of
the screens. What it means to run in two screens is not well defined.
Fwiw, the division point between normal and large is 480dp x 640dp. So a
800x960 hdpi screen is 533dp x 640dp, just barely classifying as large. On
It may not be compatible, but it certainly can run apps on both
screens. There is a screenshot of it running Angry Birds split
between the 2 screens.
It reports back 800x960 HDPI as its resolution. I guess most apps
would just work.
So Normal/Large depends on the pixel count? From this chart,
Ah sorry, I just re-read what you wrote (dp vs. px)
Makse sense, now.
On Jun 21, 9:27 am, Zsolt Vasvari zvasv...@gmail.com wrote:
It may not be compatible, but it certainly can run apps on both
screens. There is a screenshot of it running Angry Birds split
between the 2 screens.
It reports
I am sorry, how did you get
533dp x 640dp
from
800x960 hdpi screen?
Can you please provide this calculation? Obviously, you divided by
1.5, but where did the 1.5 magic constant come from? I would like to
use this info to determine in my app if I am running on a screen at
least LARGE and do
Got it. It's the density float in DisplayMetrics.
On Jun 21, 9:36 am, Zsolt Vasvari zvasv...@gmail.com wrote:
I am sorry, how did you get
533dp x 640dp
from
800x960 hdpi screen?
Can you please provide this calculation? Obviously, you divided by
1.5, but where did the 1.5 magic
Yeah, 240/160. hdpi == 240, mdpi == 160.
This device should not normally run applications on both screens.
Actually, this is what they did:
https://market.android.com/details?id=com.kyocera.tabletmodeextensionfeature=search_result
So it is a compatible device for purposes of passing the CDD,
Thanks, Dianne. I am actually happy that OEMs are trying to push the
envelop with these devices. Some of these strange form factors may
stick.
So the division point between normal and large is 480dp x 640dp.
Can you please tell me (or point me to a source) what the division
points between
Dianne, I found the following table in attrs_manifest.xml
attr name=screenSize
!-- A small screen configuration, at least 240x320db. --
enum name=small value=200 /
!-- A normal screen configuration, at least 320x480db. --
enum name=normal
15 matches
Mail list logo
