bigdaddydad / android-xbmcremote

Automatically exported from code.google.com/p/android-xbmcremote
0 stars 0 forks source link

Scaling issues with custom DPI settings #450

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Non-default DPI settings.

What is the expected output? What do you see instead?
Expected: full screen remote control function
Instead: Slightly scaled down remote control function in full-screen.

What version of XBMC Remote are you using?
v0.8.4-beta1, revision 703

Which Android device are you using (and which ROM, if custom)?
HTC HD2 with HD2ONE 0.3.4 (a Cyonagen Mod port for the HD2) 
[http://hd2one.com/downloads/]

Which XBMC revision are you running and on which platform?
10.0 (Dharma) Windows XP Professional x86

Original issue reported on code.google.com by z.ahd...@gmail.com on 21 Dec 2010 at 12:05

GoogleCodeExporter commented 8 years ago
I don't understand. The HTC HD2 is a Windows Mobile device that won't run this 
app. If you're talking about another phone, please specify which resolution it 
has. Tablet resolution problems are being adressed.

Original comment by phree...@gmail.com on 16 Jan 2011 at 3:36

GoogleCodeExporter commented 8 years ago
Ah, I'm sorry if I wasn't entirely clear about this bug.
It's true that the HD2 is a WM device, I'm just running Android on it, is all.

The problem can be reproduced with any custom 2.2.1 ROM that uses a non 
standard DPI setting (example: the various Cyanogen builds out there. 

As far I know the device's resolution isn't relevant, only the DPI setting. The 
default DPI in Android is 240. When using a lower value like 180(this is done 
in order to have more screen real-estate), the remote scales down accordingly, 
leaving about 25% of the screen blank/black.

This problem can be accurately reproduces using a HTC Desire with a custom ROM 
*with* custom DPI settings.

Again, sorry for the confusion.

Original comment by z.ahd...@gmail.com on 16 Jan 2011 at 6:28

GoogleCodeExporter commented 8 years ago
Alright then, so your use case is a HVGA 320x240 display with density set at 
180? I'll look into that, but my guess is due to the changes I'm gonna 
introduce for tablets this problem is going to be solved too.

Original comment by phree...@gmail.com on 17 Jan 2011 at 7:51

GoogleCodeExporter commented 8 years ago
Remote control spans correctly now. However detail changes depending on the 
device's density setting. See two screenshots with density set to 160 and 240 
respectively. 160 is clearly blurred while using the same image resources.

Original comment by phree...@gmail.com on 18 Jan 2011 at 3:00

Attachments:

GoogleCodeExporter commented 8 years ago
Fixed in r717.

Original comment by phree...@gmail.com on 18 Jan 2011 at 3:01