Develop Bugs

[Q] Display density and resolution oddity (?)

Using AndroSensor, I get the following output from my HD2:
800x480
160 dpi (custom set)
Logical Density: 1.0
X DPI: 254
Y DPI: 254
Refresh Rate: 60Hz
32-Bit colour
Which looks fine. But the One X gives:
1280x720
320dpi
Logical Density 2.0
X DPI: 345.0566
Y DPI: 342.23157
Refresh Rate: 58Hz
32-Bit colour
Why are the X and Y DPI values different? Should they not be the same for a square pixel ratio?
Also, a minor thing but why a refresh rate of 58Hz and not 60? Is AndroSensor just not reading it right?
The reason I ask about the X/Y DPI thing, is that the screen jumping bug looks like a monitor trying to autofit a non-native resolution signal, and perhaps this is related somehow?
Or are the physical pixels not square?

I have no idea but I'm going to post here so this thread is not forgotten in time cuz if this is related to the screen flickering issue (that isn't really gone with 1.28 OTA) I think it deserves more attention

Dave Trouser said:
But the One X gives:
1280x720
320dpi
Logical Density 2.0
X DPI: 345.0566
Y DPI: 342.23157
Refresh Rate: 58Hz
32-Bit colour
Click to expand...
Click to collapse
None of those DPI values are correct for the screen anyway which is roughly 312dpi.
The odd values are from DisplayMetrics in Android itself. Android tries to be device independant and a lot of the "pixel" values are actually Density Independant Pixels which need to be converted to physical pixels.
I don't think this is significant. My One X has exactly the same values and it doesn't have the screen corruption or tearing at all.

It makes sense then. The refresh rate is meant to be at 60, not 58, or else you get flicker. I remember seeing an identical problem on a monitor recently, where the refresh was slightly off 60 and caused flickering. This could be what's causing it. I will run a test on my other HTC One X that seems bug free to see if it is also running at 58. The one I'm posting from is currently doing 58.

Is there a way to independently set LCD density of S View window?

I prefer a density of 560 over the stock 640 but this results in the S View window being too small. Is there a hack to fix this?
Thanks in advance.

Tried using App Settings module for Xposed Installer but for some weird reason it cuts off the bottom 1/5 the of the screen. Weird. Gets the sizing perfect except for that. Any ideas? Messed with all the settings there and nothing seemed to improve it. I know 640 is stock but for some reason 620 fits best (except for the cutoff screen). Sigh, it's always something.

OK figured it out.
Instead of setting whole system to 560 and using App Settings module to make S View 640 I set entire system to 640 and made only Nova Launcher 560 using App Settings.
Works perfectly.

App Settings -> com.sec.android.sviewcover

[Strange Display Resolution] - Just curious

Hi all,
first things first i dont have a problem its just a question out of curiousity.
I was i the App "Easy DPI Changer" to change the DPI scaling on my OP3 to 480.
That was when i saw the "Display Info" Page was showing a Resolution of 2064x1080, which in it self is a strange meassure.
Everywhere i checked (and how i remembered it) the OP3 & 3T where using a Panel with a Resolution of 1920x1080p.
Now my question, where are the other 144 pixel coming from?
Do i have some naughty pixels that make babys when im sleeping? (that would be the new definition of creepy though)
Or (the more likly one) is it because i dont use the on-screen Buttons and the that space is used?
Thanks in advance and happy weekend
DeMon

Your second assumption is correct. The absence of navigation bar causes the app to assume the physical screen size (or so called resolution) wrongly. Here we see the app trying to add or subtract its available pixels (for example, on yours its 1920x1080, on mine with navigation bar, it's 1790x1080).
The way I (or anyone) can know it's the navigation bar is due to the only number increasing or decreasing is the physical vertical size. So, how do we know precisely what's causing the size to increase apart from assuming it? Maths, that's what.
First, we should know that everything on your screen is displayed in a metrics known as 'dp', density-independent pixels. This metric relies on the dpi, pixel density per inch. Thankfully, this metric can be easily converted to dp, with the formula of:
px = dp * (dpi / 160)
Thanks to the peeps at the Android Developer Support Site for supplying the formula.
So, we have our formula and metrics. Let's insert the numbers.
We know the size of navigation bar is constant, 48dp, whichever or whenever you are, as long as it has a navigation nar, it's 48dp. Of course, some ROMs have a feature to resize this to your willing. But, we aren't going to factor that, we're going to what the standard says.
Then, the DPI is a pretty easy variable to figure out, it's 480.
Punch the numbers and you have:
px = 48 * (480 / 160)
px = 48 * 3
px = 144
Voilà. 144 pixels. Add this to our original vertical resolution, 1920, and we have 2064. Funny thing is that even if you set this to a different DPI, it still works. Let's try the case on mine. I have 48dp navigation bar height with 432 DPI.
px = 48 * (432 / 160)
px = 48 * 2.7
px = 129.6
Add up that 129.6 to 1790 and we'll have, well, 1919.6 but you can round that up to 1920.
I can also consider those pixels making babies, that isn't off the logic.
Cheers!

F4uzan said:
Your second assumption is correct. The absence of navigation bar causes the app to assume the physical screen size (or so called resolution) wrongly. Here we see the app trying to add or subtract its available pixels (for example, on yours its 1920x1080, on mine with navigation bar, it's 1790x1080).
The way I (or anyone) can know it's the navigation bar is due to the only number increasing or decreasing is the physical vertical size. So, how do we know precisely what's causing the size to increase apart from assuming it? Maths, that's what.
First, we should know that everything on your screen is displayed in a metrics known as 'dp', density-independent pixels. This metric relies on the dpi, pixel density per inch. Thankfully, this metric can be easily converted to dp, with the formula of:
px = dp * (dpi / 160)
Thanks to the peeps at the Android Developer Support Site for supplying the formula.
So, we have our formula and metrics. Let's insert the numbers.
We know the size of navigation bar is constant, 48dp, whichever or whenever you are, as long as it has a navigation nar, it's 48dp. Of course, some ROMs have a feature to resize this to your willing. But, we aren't going to factor that, we're going to what the standard says.
Then, the DPI is a pretty easy variable to figure out, it's 480.
Punch the numbers and you have:
px = 48 * (480 / 160)
px = 48 * 3
px = 144
Voilà. 144 pixels. Add this to our original vertical resolution, 1920, and we have 2064. Funny thing is that even if you set this to a different DPI, it still works. Let's try the case on mine. I have 48dp navigation bar height with 432 DPI.
px = 48 * (432 / 160)
px = 48 * 2.7
px = 129.6
Add up that 129.6 to 1790 and we'll have, well, 1919.6 but you can round that up to 1920.
I can also consider those pixels making babies, that isn't off the logic.
Cheers!
Click to expand...
Click to collapse
Wow didnt thought of this kind of extended answer. Thanks for that .
This explains so much
so long
DeMon

New dpi via adb?

Hi
I'm trying to change dpi in adb. Adb finds the device but when I'm typing "adb shell wm density 380" it doesn't work.
Anyone knows why?
Thx in advance

Try going into developer options and enable the security setting to on.

What is the default dpi for mi max 3?

jutley said:
What is the default dpi for mi max 3?
Click to expand...
Click to collapse
Should be 480

Lasse58 said:
Hi
I'm trying to change dpi in adb. Adb finds the device but when I'm typing "adb shell wm density 380" it doesn't work.
Anyone knows why?
Thx in advance
Click to expand...
Click to collapse
I think Xiaomi controlled the dpi using another variable, its called persistent density or something like that.. hence changing the normal density variable wont have any impact
Sent from my ONEPLUS A6000 using Tapatalk

You can change the DPI in MIUI by going to Settings > Additional settings > Accessibilty > Display size

barro32 said:
You can change the DPI in MIUI by going to Settings > Additional settings > Accessibilty > Display size
Click to expand...
Click to collapse
The smallest display dpi is "small"... its still too large for me haha... i think without root, there is no other way
Sent from my ONEPLUS A6000 using Tapatalk

Are USB debugging & USB debugging (Security settings) both enabled?
If I recall correctly, enabling USB debugging (Security settings) is a bit tricky.

https://forum.xda-developers.com/mi-mix-2/how-to/guide-changing-min-width-dpi-miui-9-t3736218
this can be helpful for you. My dpi is now 290. If you go higher google keyboard change tablet mode.

I was able to change it using Activity Launcher using the tutorial below:
http://en.miui.com/thread-1093064-1-1.html

Default dpi is huge even at the smallest setting. I am using 320 and it's perfect, can see a lot of content without being too small
Just make sure Developer options has USB debugging (Security settings) enabled and use adb shell wm density 320
Big difference. Would be a waste to not see more content on such a big screen but also understand some people's eye sight may not be as good so they prefer bigger objects
320 vs Small setting

I used this tool to change dpi:
https://github.com/Saki-EU/XiaomiADBFastbootTools

zed011 said:
Default dpi is huge even at the smallest setting. I am using 320 and it's perfect, can see a lot of content without being too small
Just make sure Developer options has USB debugging (Security settings) enabled and use adb shell wm density 320
Big difference. Would be a waste to not see more content on such a big screen but also understand some people's eye sight may not be as good so they prefer bigger objects
320 vs Small setting
Click to expand...
Click to collapse
tried this. but it doesnt seem to work. none of the layout is changing.

yup changing dpi without root is tricky. u need to enable security usb debugging. u need to use vpn apps.

got usb debugging on.
whats vpn tools?
anyway guys, thanks much. yea i have noticed that there are two options for usb debugging. look passed the other one.
now its working.

I just upgraded from Max 2 to Max 3... LOVE that i can change the DPI without rooting... had no trouble with either phone doing this. With the Max 2 i had it at 360, but with the Max 3 i'm trying 290....i may go up to 320 just because i need my glasses to see things like the battery % lol . No clue why Xiaomi didn't drop it below 400 out of the box but thrilled i can do it easily.

Smoked33 said:
I just upgraded from Max 2 to Max 3... LOVE that i can change the DPI without rooting... had no trouble with either phone doing this. With the Max 2 i had it at 360, but with the Max 3 i'm trying 290....i may go up to 320 just because i need my glasses to see things like the battery % lol . No clue why Xiaomi didn't drop it below 400 out of the box but thrilled i can do it easily.
Click to expand...
Click to collapse
I use Font size 80%, Display size Custom (289), Smallest width 597 dp.
597 or 289dpi is the smallest dpi you can set before tablet mode is enabled in portrait mode.
If you rotate your phone watching a youtube video in full screen tablet mode is already enabled so the notification drawer is opened by swiping down on the left half side of the screen otherwise nothing will happen.
Setting Smallest width value is the easiest way to change dpi in the latest android versions.
Setting it to 596, 598 and 599 won't do anything.
It will either default back down to 595 or jump to 600 because it must represent a whole number in dpi.
It is crazy that pretty much ALL phones comes pre-configured out of the box at factory state with a dpi so large you can barely fit two words across the screen..really...I don't think anyone have this bad eyesight, if so then you need to get new glasses or lenses.
There are high index lenses out there that go to 1.9 and even beyond 2 if you really want to pay a lot if your prescription is crazy high to be able to enjoy a thin and light pair of glasses.
Like what is the purpose of getting a phone this big if you gonna have it display just as little as your old phone with third the screen size..isn't that why you wanted a bigger phone in the first place to get more screen estate, at least that's what I wanted..

SUPERUSER said:
It is crazy that pretty much ALL phones comes pre-configured out of the box at factory state with a dpi so large you can barely fit two words across the screen..really...I don't think anyone have this bad eyesight, if so then you need to get new glasses or lenses.
There are high index lenses out there that go to 1.9 and even beyond 2 if you really want to pay a lot if your prescription is crazy high to be able to enjoy a thin and light pair of glasses.
Like what is the purpose of getting a phone this big if you gonna have it display just as little as your old phone with third the screen size..isn't that why you wanted a bigger phone in the first place to get more screen estate, at least that's what I wanted..
Click to expand...
Click to collapse
I can't agree with you more. Just thankful it's so easy to change
On a side note...and i'm not sure it's related because I didnt' try before changing the dpi(i use the adb method)... my TSN app won't stream any channels. It gives me an error... i'm not sure if that's the DPI setting that caused it? Only app that doesn't work right. I'm going to have to play with that when i'm home from work as it worked on my Max 2 set at 360 no problems and the only main difference i can tell with the 2 phones is the version of Android.
Edit: nevermind it wasn't the DPI setting... i allowed TSN GO to work in full screen mode and that did it.
Love the phone!

Large border around the screen

I have a A505FN with the rom A505FNXXS4BTCA - XEF. I flashed my device with the TWRP patched and the custom splash screen.
It was a success because I'm rooted now, but not whitout problem.
Since I have an important border on my device.
https://zupimages.net/up/20/20/uvwe.jpg
I have for example + 8mm of border on the bottom of the screen..And I can't remove it.
It's an important problem. I restored the rom stock, but the border remained... Could you help me ?
I taped the commande in adb dumpsys display | grep mBaseDisplayInfo
The answer is:
mBaseDisplayInfo=DisplayInfo{"Écran intégré, displayId 0", uniqueId "local:0", app 1080 x 2340, real 1080 x 2340, largest app 1080 x 2340, smallest app 1080 x 2340, mode 1, defaultMode 1, modes [{id=1, width=1080, height=2340, fps=60.000004}], colorMode 0, supportedColorModes [0], hdrCapabilities [email protected], rotation 0, density 420 (403.411 x 404.326) dpi, layerStack 0, appVsyncOff 0, presDeadline 17666666, type BUILT_IN, address {port=0}, state DOZE_SUSPEND, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS, removeMode 0}
Thank you

It seems to be normal for me, may it be you had a dark background image before? 8mm including the navigation bar? You can put your phone under some ligth and see the reel edges of the screen, if you see an extra black border then you have a problem .there is ~3mm buttom border in the A50 .

Looks normal to me