On 11/23/2012 07:52 PM, jtoolsdev wrote:
Probably confusion. It's kind of hard to sort out information from
those documents. In fact I found that emulators and real devices were
picking up different dimens.xml files I was using for setting font
sizes than what the documentation claimed. Fortunately this had also
been discovered by other developers on Stackoverflow and with provided
solutions.
Erm... do yo think that any of those may be useful for my case? have you
got any links?
Thanks in advance,
Samsung seems to be a major culprit in designing devices that are
tricky to create emulators for. They really need to supply emulator
images for the devices that don't fall in line with Android standard
pixel densities. However as I read recently Google is changing the
licensing to prevent this. If you are familiar with the hardware
industry they do this to differentiate their different models which
benefits marketing but not developers or consumers.
On Friday, November 23, 2012 10:37:30 AM UTC-8, RichardC wrote:
What does android.util.DisplayMetrics:
http://developer.android.com/reference/android/util/DisplayMetrics.html
<http://developer.android.com/reference/android/util/DisplayMetrics.html>
give you?
On Friday, November 23, 2012 6:04:50 PM UTC, Fran wrote:
Hi there,
I have an emulator instance that seems to be reporting wrong
resolution,
but I am not sure if it is a problem of the emulator or may be
also a
problem in an actual device with same setup since I have no
one. I use
this code to get the resolution:
getWindowManager().getDefaultDisplay().getWidth()
getWindowManager().getDefaultDisplay().getHeight()
The emulator tries to be like a Samsung Galaxy Tablet with
10'1 inches
screen and 1280x800 resolution, with software buttons. The
problem is
that putting it on landscape mode (pressing ctrl+f12, you
know), and
executing my app, it reports following resolution:
1238x752
I would understand that 752 due these 48 pixels being reserved
for the
software buttons, but the 1238 has no sense at all: software
buttons are
put just in one position depending on device orientation, not
both...
Do you think it is just an emulator bug or may I found this
situation on
actual devices?
Thanks a lot in advance,
--
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
--
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
