Closed GoogleCodeExporter closed 9 years ago
Please give more details. What device are you using? Can you supply a
screenshot?
Original comment by pmerl...@googlemail.com
on 29 Sep 2010 at 8:37
O.K. Attached photo of the wvga device (Spice M1700 with 800x480 screen)
running SIPDroid.
Original comment by spicemi...@gmail.com
on 30 Sep 2010 at 12:49
Attachments:
Do you get this with other apps, too? I am asking because the Nexus One has the
same screen resolution and works fine with Sipdroid.
Original comment by pmerl...@googlemail.com
on 30 Sep 2010 at 9:48
No, I only have this device to test.
Cheers, Kelvin.
Original comment by spicemi...@gmail.com
on 30 Sep 2010 at 3:34
ok. I tested with a acer liquid which has a 800x480 resolution and it has no
problem.
The Droid Pad (M1700) however, has a 7 inch screen n has the problem as
reported.
Cheers, Kelvin.
Original comment by ss1...@gmail.com
on 2 Oct 2010 at 4:16
Issue 715 has been merged into this issue.
Original comment by pmerl...@googlemail.com
on 6 Nov 2010 at 7:41
What the issue is this occurs when the LCD density is messed with. Stock
density is 240, however, if you change the density to something smaller than
that, the screen gets "smaller". One reason for doing this is if you have a
custom launcher (launcher pro or adw launcher) you can change the number of
columns and rows. So, if you decrease the lcd density, you can have more icons
on the home screen without them sitting on top of each other. Some apps are
able to handle the screen density changes (like angry birds or the browsers or
what have you), but it some apps arent (sipdroid). It's almost like the
resolution is variable in some apps (like it reads the info from the system vs.
in other apps the dev sets the resolution, giving us the black box around the
app.
Original comment by AMiller...@gmail.com
on 20 Jan 2011 at 3:38
just a follow up, I have the Droid X... If I change the LCD density back to
stock (240), everything is fine. If I change the LCD density back to what I
have it at (190), sipdroid probably takes up on half of the screen's total real
estate.
Original comment by AMiller...@gmail.com
on 20 Jan 2011 at 3:40
Original comment by pmerl...@googlemail.com
on 31 Jan 2011 at 4:55
Original comment by pmerl...@googlemail.com
on 15 Feb 2011 at 9:45
Original issue reported on code.google.com by
spicemi...@gmail.com
on 29 Sep 2010 at 7:09