Database Develop

[Q] LCD Density

I've used a few different across my android devices (different meaning other than the stock value) but I still don't quite understand...
Higher Density = Higher or Lower quality?
Lower than Stock density = Lower quality at all?
I'm liking 400 but I'm not sure if it lowers quality or not.

If you can't see any quality degradation, then what's the problem?
Sent from my C6603 using XDA Premium HD app

Well I meant in home/settings apps really, i would hate to later play a higher end game or a movie and see the quality is poor

Movies or games should still be rendering at the resolution of the screen. The DPI doesn't change that. What it could (and most likely will) is adjust the size of UI elements (such as camera controls, video player controls, etc.). Depending on what firmware you're running, the different elements and apps may be able to adjust themselves based on the DPI by utilizing different images within the APKs (mdpi, hdpi, xhdpi, etc.).
Take a look at this link. It might help you out a little.
http://www.androidtablets.net/forum/android-tablet-usage-tips-tricks/9444-lcd-density-explained.html
Also, there are ROMs/MODs that allow for different apps to implement different DPIs on the device. Great examples of this are ParanoidAndroid ROMs and Xposed framework mods. These can give you the ability to adjust dpi by application, that way if there are any incompatibilities at a certain DPI, you can work around the issues.

Screen resolution - stretching?

I actually realized this since the first day of using the tablet... I noticed that the screen actually got stretched when you set your tablet in landscape mode and squished in while in portrait mode.
I suspect that the OS is running at a wrong native resolution... Does anyone have similar observation?

Yep, me too
I noticed the same issue. Circular icons look especially bad. Funny enough, the tablet on the packaging also has a distorted screen. In Youtube, videos have black bars on the top and bottom of the screen. This shouldn't be the case, as 1024x600 is a 16:9 aspect ratio, and videos are typically 16:9.
Code:
adb shell dumpsys display
contains the following output:
Code:
mPhys=PhysicalDisplayInfo{600 x 1024, 59.670002 fps, density 1.0, 177.209 x 171.115 dpi, secure true, appVsyncOffset -5000000, bufferDeadline 22758840}

Yup, installed luna icon pack and looks horrible. Same as letters in Google keyboard.

I was just getting on to post about this very thing. Here is an image comparison I put together showing a screen shot side-by-side with a photo of the screen:
https://drive.google.com/file/d/0B0Z0bpkQXwBFR1djTnJLSGlsTkU/view
According to the images I pulled, the nominal screen resolution is 600x1024, which is also the hardware spec. But the actual image you see is the same aspect ratio as a display with a resolution of 600x1080. This suggests that the display pixels aren't actually square. I tried a couple of resolution changers in the Play Store but they just scale the display without addressing the issue.
I found an old Google Groups post asking about a cheap tablet with non-square pixels, and the answer in 2012 wasn't very encouraging. I wonder if something could be done through an Xposed module?

I lowered the dpi to 150 just to test and same result...

theophile2 said:
I was just getting on to post about this very thing. Here is an image comparison I put together showing a screen shot side-by-side with a photo of the screen:
https://drive.google.com/file/d/0B0Z0bpkQXwBFR1djTnJLSGlsTkU/view
According to the images I pulled, the nominal screen resolution is 600x1024, which is also the hardware spec. But the actual image you see is the same aspect ratio as a display with a resolution of 600x1080. This suggests that the display pixels aren't actually square. I tried a couple of resolution changers in the Play Store but they just scale the display without addressing the issue.
I found an old Google Groups post asking about a cheap tablet with non-square pixels, and the answer in 2012 wasn't very encouraging. I wonder if something could be done through an Xposed module?
Click to expand...
Click to collapse
Also, this line from the display dump above similarly seems to indicate non-square pixels:
Code:
density 1.0, 177.209 x 171.115 dpi
Anyone know how to change horizonal and vertical dpi independently?

Apparently the dpi is 160 normally.
You can set it higher and the icons will look less stretched but the dpi seems correct.

Yeah, this is sadly typical in cheap chinese tablets. What really surprises me is that almost nobody talks about this, and most of the people don't even notice it even after pointing it to them
I've also noticed that this screen has what I think is a slow redraw rate (i. e. painting line by line from the top) which cause funky scroll effects, especially in dark backgrounds in portrait. Grab the tablet with the buttons on top and scroll quickly in the Kindle Store and you'll see it

I watched a video on the Fire for the first time, and while this isn't exactly a scientific test, the video did not seem stretched out or distorted to me. I tested with a second video and it too seemed to display with the correct aspect ratio. If so, then that suggests that the display, controller, and drivers are all capable of rendering an image that is not distorted, and that it may be an issue with the rendering of the Android UI.

Up, i would love having a fix for this.

Mine doesnt seem to show these problems? Is it just a some devices problem or am I missing something?

zach61797 said:
Mine doesnt seem to show these problems? Is it just a some devices problem or am I missing something?
Click to expand...
Click to collapse
Just got one of the $50 Fire tablets delivered and this is one of the first things I noticed. Look at a circular icon when it's in portrait and when it's in landscape and it's really obvious. I noticed it on the Pinterest icon.
If this really is a hardware issue, I don't suppose there's any way to fix it? If not I'll probably return it and get my money back.

amiiboh said:
Just got one of the $50 Fire tablets delivered and this is one of the first things I noticed. Look at a circular icon when it's in portrait and when it's in landscape and it's really obvious. I noticed it on the Pinterest icon.
If this really is a hardware issue, I don't suppose there's any way to fix it? If not I'll probably return it and get my money back.
Click to expand...
Click to collapse
Idk.. I don't really notice it maybe it's just my perspective the seem good to me.

It didn't jump out at me, but yes, the screen is definitely wider than 1024/600. Maybe it is 16:9.
I did notice the weird scrolling. Perhaps it's refreshed in some interlaced fashion?

I've noticed that some people just don't see it. Coincidentally in my case it was the same people that watch 4:3 content stretched in their 16:9 TVs and are happy with it

martinml said:
I've noticed that some people just don't see it. Coincidentally in my case it was the same people that watch 4:3 content stretched in their 16:9 TVs and are happy with it
Click to expand...
Click to collapse
^^^ This!
The incorrect aspect ratio is really distracting. I hope there's a way to fix it now that custom ROMs are available.

Hey guys! Does anyone else have a problem with scrolling. When I scroll down a page it looks like the left side is scrolling slower than the right. So for example, if you scroll down on a page full of horizontal lines or text, all the text slopes to the right until the page stops. I'm not sure if this is normal because the tablets so cheap or if its just mine?

BadPotato said:
Hey guys! Does anyone else have a problem with scrolling. When I scroll down a page it looks like the left side is scrolling slower than the right. So for example, if you scroll down on a page full of horizontal lines or text, all the text slopes to the right until the page stops. I'm not sure if this is normal because the tablets so cheap or if its just mine?
Click to expand...
Click to collapse
It seems "normal" for this tablet, sadly:
martinml said:
I've also noticed that this screen has what I think is a slow redraw rate (i. e. painting line by line from the top) which cause funky scroll effects, especially in dark backgrounds in portrait. Grab the tablet with the buttons on top and scroll quickly in the Kindle Store and you'll see it
Click to expand...
Click to collapse

Can't complaint it's rather solid for it's price imo.

Aghh glad its not just mine then. I'm loving the fire! Though it was going to be rubbish but really surprised!

Change aspect ratio for certain apps?

Some games that I play look like they're been squeezed so I assume it's cause the game doesn't support 4:3 ratio. Is there a way to make certain apps change aspect ratio so it doesn't look like it's been squeezed?

Ruriko said:
Some games that I play look like they're been squeezed so I assume it's cause the game doesn't support 4:3 ratio. Is there a way to make certain apps change aspect ratio so it doesn't look like it's been squeezed?
Click to expand...
Click to collapse
The only way I know requires rooting your tablet and installing xPosed framework. Look for the App Settings module which lets you fine tune almost all aspects of an apps' display, including the DPI, on a per app basis.

Dialer/Call Screen mods/fixes

After recently rooting my J7, I've decided to use one of the resolution changing apps to give my phone a 1080x1920 pixel faked resolution, with a dpi of 280. For the most part, it works. Some built-in apps such as the camera or even the touchwiz launcher (seems some UI elements used hard-coded numbers to define regions, or in case of the camera, the view is almost a quarter of the screen with black around the edge, and the touch input is offset to a different corner.
All else seemed good, until I realized another major flaw - the call screen - it works, however when trying to pull up the keypad when in a call, it only displays a single, gigantic 1 button. no other buttons are available. Button-based menus are of course now impossible to navigate... unless every button to press is 1, 1 and 1. And then 1.
Can't take pictures of it now as the resolution change causes an issue for screenshots - I'll need to get a screenshot app for this, but ultimately, are there apps that replace the call screen? I thought a dialer app would fix this but the one I have only replaces the text/call/contacts apps, not actually calling. I'd prefer there to be an app that can replace it, as it seems most third party apps are almost never hard-coded to a specific resolution, meaning I'd imagine it should work on my modded phone.
If more explanations are needed I can try to provide some screenshots as needed when i'm done. I'm really hoping I don't have to reset the screen. I love how everything works otherwise...

anthonyloprimo said:
After recently rooting my J7, I've decided to use one of the resolution changing apps to give my phone a 1080x1920 pixel faked resolution, with a dpi of 280. For the most part, it works. Some built-in apps such as the camera or even the touchwiz launcher (seems some UI elements used hard-coded numbers to define regions, or in case of the camera, the view is almost a quarter of the screen with black around the edge, and the touch input is offset to a different corner.
All else seemed good, until I realized another major flaw - the call screen - it works, however when trying to pull up the keypad when in a call, it only displays a single, gigantic 1 button. no other buttons are available. Button-based menus are of course now impossible to navigate... unless every button to press is 1, 1 and 1. And then 1.
Can't take pictures of it now as the resolution change causes an issue for screenshots - I'll need to get a screenshot app for this, but ultimately, are there apps that replace the call screen? I thought a dialer app would fix this but the one I have only replaces the text/call/contacts apps, not actually calling. I'd prefer there to be an app that can replace it, as it seems most third party apps are almost never hard-coded to a specific resolution, meaning I'd imagine it should work on my modded phone.
If more explanations are needed I can try to provide some screenshots as needed when i'm done. I'm really hoping I don't have to reset the screen. I love how everything works otherwise...
Click to expand...
Click to collapse
Install Google Phone apk and set it as the default dialer app.
It also replaces the incall screen

Ruturaj Kadam said:
Install Google Phone apk and set it as the default dialer app.
It also replaces the incall screen
Click to expand...
Click to collapse
Awesome. It worked like a charm. Thank you so much!

AA 480p issue

Hey folks,
I am using this module to enable AA on my BMW headunit:
a.aliexpress.com/_U4Jz5
It kinda works nice except for one thing, resolution is not so clear due to dpi settings. Someone else dug into the system and found that in
etc/androidauto/androidauto_config.xml
The resolution is set to 480p instead of 720p and dpi is set to 150 instead of 180.
We have no SSH access but can only upload .bin update files as we dont know the password.
Does anyone know if it would be possible to change 720p to true and up the dpi somehow?
Carplay apparantly is 720p on this unit.
<DisplayWindow><!-- Head Unit side configuration--> <X_Coordinate value="0"/> <Y_Coordinate value="0"/> <DisplayWidth value="1280"/> <DisplayHeight value="480"/> </DisplayWindow> <Display><!-- Phone side configuration--> <DisplayWidth value="232"/><!-- Physical width--> <DisplayHeight value="87"/><!-- Physical height--> <Density value="170"/> <RealDensity value="153"/> <ViewingDistance value="400"/> <Resolution480P value="true"><!-- fps: 30 or 60--> <fps value="30"/> </Resolution480P> <Resolution720P value="false"> <fps value="30"/> </Resolution720P>

Nobody?

Anyone?

Do you have a copy of the BIN? My guess is unpacking and repacking the BIN will be the hardest part of this. You probably won't be able to do this without source scripts. You are in the right place regarding the XML file inside. All android head units, regardless of what they are, have to tell our phones what resolution to serve up. If the head unit says to run 1024x600 then that is what you are getting.
An alternative would be to ask the manufacture to release an update set to the proper settings.
---------- Post added at 09:12 PM ---------- Previous post was at 09:09 PM ----------
Here you go The Andream unit you have should likely work with one of these firmwares. Do a lot of reading there before you proceed. I cannot be responsible for you flashing the wrong software to your unit.
I have a similar unit to yours and was able to get mine running at the proper resolution.

@heresy_fnord, when you say the proper resolution, what resolution are you referring to? I have the Andream (version: NBT-02B) unit myself, and flashed the latest .BIN with the AA Widescreen fix, but I feel the scale is slightly off. Text and elements are too small compared to the screen size (I have 8.8", 1280x480).

ckarv said:
@heresy_fnord, when you say the proper resolution, what resolution are you referring to? I have the Andream cool:unit myself, and flashed the latest .BIN with the AA Widescreen fix, but I feel the scale is slightly off. Text and elements are too small compared to the screen size (I have 8.8", 1280x480).
Click to expand...
Click to collapse
OK, my guess is the physical screen size is the issue. If you are certain the 8.8" screen also runs 1280x480 then the settings for DPI are probably not appropriate. Here is what I see for a 10.25" screen:
<Display>
<DisplayWidth value="244"/> 244mm is 9.6" width
<DisplayHeight value="92"/> 92mm is 3.62" height
<WidthMargin value="0"/>
<HeightMargin value="0"/>
<Density value="220"/>
<RealDensity value="133"/> This calculator indicates a real density of just a hair over 133PPI
So for example, your real density should be set to 155PPI based on that logic. I don't know what your update file was set to. I don't know what your display width and height should be set to since I don't know how the 8.8" screen measures length and width. Finally, I think they are setting the Density of the widescreen fixed update to 210 and you might try 220 which is as big as it can be set before it cuts back over to the non-widescreen view, and see if that works.

heresy_fnord said:
OK, my guess is the physical screen size is the issue. If you are certain the 8.8" screen also runs 1280x480 then the settings for DPI are probably not appropriate. Here is what I see for a 10.25" screen:
<Display>
<DisplayWidth value="244"/> 244mm is 9.6" width
<DisplayHeight value="92"/> 92mm is 3.62" height
<WidthMargin value="0"/>
<HeightMargin value="0"/>
<Density value="220"/>
<RealDensity value="133"/> This calculator indicates a real density of just a hair over 133PPI
So for example, your real density should be set to 155PPI based on that logic. I don't know what your update file was set to. I don't know what your display width and height should be set to since I don't know how the 8.8" screen measures length and width. Finally, I think they are setting the Density of the widescreen fixed update to 210 and you might try 220 which is as big as it can be set before it cuts back over to the non-widescreen view, and see if that works.
Click to expand...
Click to collapse
I've put some effort into looking into this now, basically reading 100 odd pages in the "Andream MMI Box - Wireless CarPlay & Android Auto" thread (starting on pg. 135), over at the Bimmerpost forum.
Findings:
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
* Attached a picture of my screen with 200 dpi.
You are using a "Density" value of 220, do you have an example of what that looks like in practice?
Thanks

ckarv said:
I've put some effort into looking into this now, basically reading 100 odd pages in the "Andream MMI Box - Wireless CarPlay & Android Auto" thread (starting on pg. 135), over at the Bimmerpost forum.
Findings:
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
* Attached a picture of my screen with 200 dpi.
You are using a "Density" value of 220, do you have an example of what that looks like in practice?
Thanks
Click to expand...
Click to collapse
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
This is accurate.
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
I don't know, perhaps this is true.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
Your scale of text is set by the DPI essentially. Its a combination of resolution and DPI. Basic example, if I was to set my DPI to 200, the text on my screen would be smaller.
* Attached a picture of my screen with 200 dpi.
This is a 10.25" screen with 220DPI
In your case, the one update file was made for a 10.25" screen. The thing is, there will be a DPI difference between the two even if the resolution is the same. I suspect you need check with that community to see if there is an update that maintains widescreen mode but uses the different DPI.
EDIT: To be fair, I think your screen looks "normal" but then, it looks like your clock and such are the same scale as mine. Maybe AA is just smaller text in general?