Develop Bugs

[Q] Why LCD Density is set to 240

Why does the LCD Density in Galaxy Gran Duos is set to 240?
This can be viewed in \System\build.prop
The real LCD density for the Gran Duos is 187 PPI
In The Stock rom, with android 4.2.2 the LCD Density is set to 240, but this actually causes the objects in screen to look larger and occupies more space than it should.
Well this happens because android system try to compensate the resolution of screen, (Better resolution = More Density)
The android system, makes a scale for application, which leads the applications to resize elements in a scale factor of 1.5x
So every thing you see on ower Galaxy Grand is 1.5x bigger than it should be.

zmp2000 said:
Why does the LCD Density in Galaxy Gran Duos is set to 240?
This can be viewed in \System\build.prop
The real LCD density for the Gran Duos is 187 PPI
In The Stock rom, with android 4.2.2 the LCD Density is set to 240, but this actually causes the objects in screen to look larger and occupies more space than it should.
Well this happens because android system try to compensate the resolution of screen, (Better resolution = More Density)
The android system, makes a scale for application, which leads the applications to resize elements in a scale factor of 1.5x
So every thing you see on ower Galaxy Grand is 1.5x bigger than it should be.
Click to expand...
Click to collapse
PPI and DPI are two different things, not one.
PPI is Pixels Per Inch and DPI is Dots per Inch.
The amount of dots in one pixels differs from phone to phone and manufacture to manufacture, its basically the OEMs choice how they like their phones, so that's why grand has it set to 240 in stock.
Even if you set your DPI to 160, 170 or 180, your PPI stays at 187 at 480x800 resolution

Thanks icey[emoji6][emoji6]

[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

[MOD] Change Default Resolution to 1080P (No root required)

hi
this guide shows how to change the default display resolution on the htc10 (should work on other devices too).
this affects all the apps too of course. the changes are applied in runtime so you can check the effect directly.
some system apps like keyboards might require a soft-reboot (restart systemui) for changes to apply.
the way sony is dealing with 4k displays and the way samsung allows this in settings inspired me to write this guide.
root-access is not needed for this. only enabling usb-debugging in developer settings is needed.
the goal of this guide is to reduce battery consumption by reducing the amount of virtual pixels being diplayed.
warning: i can not be held responsible for any damage this mod might cause to your device or data. on your own risk.
guides how to enable developer options and adb debugging can easily be found on xda.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
requirements:
htc 10 device
a computer with adb folder
connected usb-cable
note:
htc boost app is interfering with this mod.
i recommend to disable all foreground app optimizations in htc boost app.
otherwise, all the apps interface will be too small when reducing screen resolution.
note2:
in android 7 nougat, google added the display-option to reduce display size in addition to fontsize.
this option is also directly interfering with this mod since it represents the wm override density value (see below).
value descriptions:
wm size - physical size: 1440x2560 (that's our native display resolution)
wm size - override size: value is not present in stock rom (android ui is running with physical display resolution)
wm density - physical density: 640 (that's our native virtual display density)
wm density - override density: value is not present until you change display size in settings (640 is used)
when changing display size in settings to "small", override density value is 544.
when changing display size in settings to "big", override density value is 720.
lineage os 14.1 has more options for override display density value: 448/512/576/640/720 (as reference).
the default android density values are: 240(HDPI)/280/320/360(XHDPI)/400/440/480(XXHDPI)/520/560/600/640(XXXHDPI)/680/720)
wm density things change, when changing wm size.
overriding physical density value is reducing the size of all elements on screen,
maybe changes the grid size on homescreen (launcher) and it might add additional options for rows/columns in appdrawer.
some comparisons with other devices values:
htc one m7/m8 (4.7/5inch, 1080p)
wm size - physical size: 1080x1920
wm density - physical density: 480
htc one max (6inch, 1080p)
wm size - physical size: 1080x1920
wm density - physical density: 400
htc u11 (5.5inch, 1440p)
wm size - physical size: 1440x2560
wm density - physical density: 640
nokia 8 (5.3inch, 1440p)
wm size - physical size: 1440x2560
wm density - physical density: 560
google pixel (5inch, 1080p)
wm size - physical size: 1080x1920
wm density - physical density: 420
google pixel XL (5.5inch, 1440p)
wm size - physical size: 1440x2560
wm density - physical density: 560
xperia xz premium (5.5inch, 2160P/4K)
wm size - physical size: 1080x1920
wm density - physical density: 403
note: see how they deal with 2160x3840 display? phone is running only 1080p exept in specific apps.
that's what we want too to save battery.
downside is that we can't use full-res of display anywhere anymore (exept for VR, 1080P should be sufficient though).
first we want to override the physical display size from 1440x2560 to 1080x1920.
the adb command to do so is: "wm size 1080x1920"
second we want to override the display density value from 640 to 480 (i would even recommend 420 or 400).
the adb command to do so is: "wm density 400"
feel free to experiment with this density value and post your results.
when going lower than value of 436, sense launcher changes from 4x4 to 5x5 grid-layout (when 1080p is set as res).
when going lower than value of 370, htc sense keyboard (sense 7) switches to small mode (when 1080p is set as res).
when going lower than value of 289, systemui switches to tablet mode (when 1080p is set as res).
known issues:
-htc bootsplash of the htc10 is made in 1440x2560 so the logo is shifted to the lower right (who cares)
-signal bars are crippled
-navigation bar sometimes shows wrong button-orientation with custom density values
-some apps might show ui scaling problems with custom density values
-htc lockscreen pin entry screen breaks when density value is too low (use aosp lockscreen as alternative)
return both values to default with the following commands:
wm size reset
wm density reset
if you just want to make items smaller but running at native display res (no battery optimization):
wm size - physical size: 1440x2560 (leave this value as it is or revert it with the command above)
wm density: try the override values mentioned above and see how it behaves.
when going lower than value of 581, sense launcher changes from 4x4 to 5x5 grid-layout (when 1440p is set as res).
when going lower than value of 490, htc sense keyboard (sense 7) switches to small mode (when 1440p is set as res).
when going lower than value of 385, systemui switches to tablet mode (when 1440p is set as res).
please report back about problems or battery consumption improvements.
hit the thanks button if you like this guide.

Does density effect power consumption when size is set to 1080x1920?
I set it to 420. Lower or higher,are there any differences?
Edit : What is the perfect match for the 1440x2560 size 544 density in 1080x1920 size?

density should not affect battery consumption. only the virtual display resolution.
the calculated values are:
1440x2560->544(small)/640(default)/720(big)
1080x1920->408(small)/480(default)/540(big)
i will have a closer look at how samsung does it on the s8. there is also a setting for only hd resolution.

HD2Owner said:
density should not affect battery consumption. only the virtual display resolution.
the calculated values are:
1440x2560->544(small)/640(default)/720(big)
1080x1920->408(small)/480(default)/540(big)
i will have a closer look at how samsung does it on the s8. there is also a setting for only hd resolution.
Click to expand...
Click to collapse
What do you mean by "a setting for only HD resolution"?

ordeniz said:
What do you mean by "a setting for only HD resolution"?
Click to expand...
Click to collapse
i just added another image in the first post to explain it.

Thanks a lot for your efforts.

HD2Owner said:
density should not affect battery consumption. only the virtual display resolution.
the calculated values are:
1440x2560->544(small)/640(default)/720(big)
1080x1920->408(small)/480(default)/540(big)
Hello,
i will have a closer look at how samsung does it on the s8. there is also a setting for only hd resolution.
Click to expand...
Click to collapse
Did you try it? and if so did you notice a change in battery life?
Thank you.

nice tutorial
for htc 10 i did
1080x1920 res. and 402 dens fits perfect!
thanks for tutorial OP

Any noticeable effect on battery life?

derdjango said:
Any noticeable effect on battery life?
Click to expand...
Click to collapse
still under observtion . will share here the results soon

almost nothing changed, i will do much more technical experiments

This method is work on HTC U11.
Thank you.

newyesor said:
This method is work on HTC U11.
Thank you.
Click to expand...
Click to collapse
Does this technique improve U11 battery usage?
Thx

I use Viper10 5.11.0 for HTC 10. Current resolution is 720x1280 with DPI 272. It is running ultra smooth and perfect. Only problem is the last apps screen previews does not fit the window. It is like %400 zoomed.

anyone still doing this? Does setting to 1080*1920 with 480ppi improve battery life?

Nooe, it doesn't
Sent from my HTC 10 using XDA-Developers Legacy app

NitroMehmet said:
I use Viper10 5.11.0 for HTC 10. Current resolution is 720x1280 with DPI 272. It is running ultra smooth and perfect. Only problem is the last apps screen previews does not fit the window. It is like %400 zoomed.
Click to expand...
Click to collapse
Is 720p quality acceptable in htc10 screen?

andywkf said:
Is 720p quality acceptable in htc10 screen?
Click to expand...
Click to collapse
Nope. Some apps have some troubles. I revert the settings to original and just using the HTC Boost+ app to run apps in 1080p. I can't see any difference between 1080p and 2K about the battery life.

1440p vs 1080p
Hello guys. First of all, great thanks to HD2Owner, who made this feature(we better say MOD) possible.
Recorded my results firstly with 1440p(native), I have stock ROM, kernel and bootloader. Tried to do almost the same scenario.
2 results from 1440p:
4h 30m
5h 17m
Then i switched resolution to 1080p, Open Apps zooms automatically(looks strange, the same as above in some pictures), boot logo does not show up to all screen and lots of these kind of insignificant bugs.
2 results from 1080p and scenario:
4h 41m
4h 40m
So, I guess you cannot say that there is a difference in battery life for sure. But I noticed that small fonts become a little bit shrunken, if I can use this word, less crisper. When you read or browse websites, you definitely notice it.
Nevertheless, HD2Owner, thank you for this making this experiment and experience possible and I will go back to 1440p.

For gamers this trick is godly ! I use 1280x720 resolution and 280 dpi and it is great for gaming performance! My HTC 10 is now lightning fast ,
I also read that , 720 resolution scales pixel by pixel on the screen because 1280x720 x4 pixels is exactly 2560x1440 ,but 1080p 1440p is 1.777x so it does not scale pixel by pixel.

Display size and DPI

The attached image shows MobileSheetsPro running on my old Galaxy Note 10.1 (left) and on the S4 (right).
The note is 1280x800 and the S4 is 2560x1600.
I would expect the applications to look the same, but this is not the case. On the S4, the dialog is about 25% larger, the icons are larger, etc.
If you are familiar with MobileSheetsPro you can see that I needed to lower the font sizes used by the program (to about 80%) to get the same contents on the display. Other applications show similar differences.
DevCheck (see 2nd attachment) shows resolution 1280x800 and screen density 160dpi (mdpi), 1280dp x 800dp for the Note, and for the S4 resolution 2560x1600 and screen density 360dpi (xhdpi), 1138dp x 711dp. I find the red numbers puzzling.
Is this normal behaviour? Is MobileSheetsPro misbehaving? Is there some setting that can (needs) be adjusted?

'm confused about this as well. Just picked up a a new s4 for super cheap...and games are too zoomed. I used recheck and an online tool and they both show 1280 x 800. Tried changing min width in developer settings to no avail

My tablet is at home, and this isn't the behavior I remember, but i don't use Mobile Sheets, and it could be specific to software. Android does some weird treatments that are supposed to be based on resolution. The xhdpi is a clue to this. In your old tablet it was using the native resolution in determining what resources to use/scale. On the new one, it appears to behave as if it believes the dPI is higher than it really is and the resolution lower. Somebody who understands better how this works in Android will have to give a more complete answer.

General QHD+ / Font size / Display size too large even when set to small

As the title says I've already set the phone to QHD+ (3120x1440), default factory setting was FHD+ (2340x1080)
I've also set both Font Size and Display size to Small
Yet pretty much everything remains still pretty big.
In my old phone (Razer Phone 2) after I make these changes I get a lot of screen real-state space back, but that doesn't seem to be doing much.
To simply put it, I want to be able to read a long text per row, than having the same long text wrap around a few times, regardless if they are the Title of a web page, SMS text, email, whatever.
For example:
When I run Waze (GPS nav) in the 1+9 Pro everything is Large, the GUI (user interface) is taking up too much screen realstate, yet on my old phone (RPP2) after making those same size changes everything reduced in size, opening up the Map to show a lot more streets and area.
Size:
5.72 inches, 90.2 cm2 (~72.0% screen-to-body ratio) RP2
6.7 inches, 108.4 cm2 (~90.3% screen-to-body ratio) 1+9 Pro
Resolution
1440 x 2560 pixels, 16:9 ratio (~513 ppi density) RP2
1440 x 3216 pixels, 20:9 ratio (~525 ppi density) 1+9 Pro
See technically speaking our 1+9 Pro should be able to show lot more stuff on screen, yet I actually get a lot less than from my old RP2.
Trying to figure out if I'm missed any additional Settings I could change from the stock OS, or perhaps we'll need some 3rd party Apps like Screnshift to tweak the ppi or some other hack that we could use.

AllGamer said:
As the title says I've already set the phone to QHD+ (3120x1440), default factory setting was FHD+ (2340x1080)
I've also set both Font Size and Display size to Small
Yet pretty much everything remains still pretty big.
In my old phone (Razer Phone 2) after I make these changes I get a lot of screen real-state space back, but that doesn't seem to be doing much.
To simply put it, I want to be able to read a long text per row, than having the same long text wrap around a few times, regardless if they are the Title of a web page, SMS text, email, whatever.
For example:
When I run Waze (GPS nav) in the 1+9 Pro everything is Large, the GUI (user interface) is taking up too much screen realstate, yet on my old phone (RPP2) after making those same size changes everything reduced in size, opening up the Map to show a lot more streets and area.
Size:
5.72 inches, 90.2 cm2 (~72.0% screen-to-body ratio) RP2
6.7 inches, 108.4 cm2 (~90.3% screen-to-body ratio) 1+9 Pro
Resolution
1440 x 2560 pixels, 16:9 ratio (~513 ppi density) RP2
1440 x 3216 pixels, 20:9 ratio (~525 ppi density) 1+9 Pro
See technically speaking our 1+9 Pro should be able to show lot more stuff on screen, yet I actually get a lot less than from my old RP2.
Trying to figure out if I'm missed any additional Settings I could change from the stock OS, or perhaps we'll need some 3rd party Apps like Screnshift to tweak the ppi or some other hack that we could use.
Click to expand...
Click to collapse
In dev options change the dpi to a larger value, stock is 384, smaller text etc is larger number. I like 411 ...

zoman7663 said:
In dev options change the dpi to a larger value, stock is 384, smaller text etc is larger number. I like 411 ...
Click to expand...
Click to collapse
Are you referring to the setting "Smallest width" ?
it's set to 411 dp by default.
other than that, I can't seem to find an actual setting for "dpi" which is what I was looking for as well.

AllGamer said:
Are you referring to the setting "Smallest width" ?
it's set to 411 dp by default.
other than that, I can't seem to find an actual setting for "dpi" which is what I was looking for as well.
Click to expand...
Click to collapse
Yes, mine was defaulted at 384 but doesn't matter. Raise that value and things on the screen will become smaller.

zoman7663 said:
Yes, mine was defaulted at 384 but doesn't matter. Raise that value and things on the screen will become smaller.
Click to expand...
Click to collapse
That did the trick.
I set it to 525 maximum for this phone, now I got alot of screen space, feels good, less claustrophobic

Damn I thought 450 was small wow lol

i set mine to 601 - which is phablet, and also switches the keyboard layout (enter key isn't on the bottom left, where i find it to be an annoying position). Pretty tiny - but lots of real estate. G