Steps :
1. Download any terminal emulator .
(you'll need root permissions)
2. on command prompt type following commands :
# su
# wm density 320
# wm size 720x1280
( After each command press enter )
Note : you can change software density ( display size / smallest width ) from settings . Set it according to your preference . ( Second command set default . )
For hd use density 320 size 720x1280 .
For full-hd use density 443 size 1080x1920 .
For quad-hd use density 548 size 1440x2560 .
how does this work, where will the excess pixels go if our screen is 1080p?
and what are the benefits?
AgentNemo said:
how does this work, where will the excess pixels go if our screen is 1080p?
and what are the benefits?
Click to expand...
Click to collapse
It cant change your display lcd ppi as it is hardware default , but it changes the display resolution like we do for dpi in settings .
Only a tweak . But this will show your display resolution changed in system diagnosis. ( DPI )
Screens
Do you notice any difference from FullHD to Quad-HD? Does the image quality look better?
CaiqueRSoares said:
Do you notice any difference from FullHD to Quad-HD? Does the image quality look better?
Click to expand...
Click to collapse
It is difficult to observe , but yes , slightly . But at d same time , load on cpu increased a bit , smoothness of ROM affected .
Switching to HD smoothened ROM a bit but at d cost of image quality .
Anyone must try
8k resolution ??
7840×4320
thanks ! I've been trying for ages to use 720p resolution on this phone to improve battery life and no app on play store was working fine. Even if picture is not as crispy, it is okay enough for every day use.
There is an easier way to do the same modification.
Download Easy DPI Changer, through Play Store.
Related
Has anyone been able to get any density changer apps working on their Nitro HD? I've tried all of the following, and none seem to work. It's possible there is a problem with my su access, so if anyone HAS gotten any of these to work, please let me know. That at least tells me I definitely have an su problem...
DPI Changer
LCD Resolution
LCDDensity
Root Tools
Never mind; my build.prop file was set to read only.
Excuse my ignorance, but what exactly are they for? Does the density changes only the size of text or everything including graphic become bigger/smaller?
[email protected] said:
Excuse my ignorance, but what exactly are they for? Does the density changes only the size of text or everything including graphic become bigger/smaller?
Click to expand...
Click to collapse
wondering the same thing as well.
aquariuz23 said:
wondering the same thing as well.
Click to expand...
Click to collapse
For the most part, yes. Decreasing the LCD Density is like increasing your desktop's resolution. Icons and text become smaller, though apps that are written to scale to any resolution will usually appear the same.
Hmmm...I do see some issues with current density, for instance the avatars in Talk don't stretch to fit the square.
So witch tool would you suggest?
I tried DPI Changer the other and couldn't get it to work, thanks for the heads-up about the build.prop!
The Nitro also already has the "Screen Optimization" util (Settings > Display > Screen Optimization) that resizes checked apps to the Nitro's display. It helped with a few games, but some games just won't work (like Asphalt 5)...But now with the Density changer, maybe I'll give it another try.
[email protected] said:
Hmmm...I do see some issues with current density, for instance the avatars in Talk don't stretch to fit the square.
So witch tool would you suggest?
Click to expand...
Click to collapse
Actually, I'm not sure any of the tools above would work; part of the problem I am sure is that the build.prop file was not only read only, but there wasn't an entry for the LCD Density - so if the apps work by simply retrieving and editing the property, they aren't going to work. I just edited the file directly with a text editor, saved, and restarted the phone. Some of the apps would then at least report the new value, but still didn't seem to successfully update it. I quit looking because I got the density I wanted (about 270, down from the native 320).
As for compatibility with other apps, if they don't quite look correct it is because they aren't written well, and a different density changing app isn't going to do you any good. Again, it's like changing the resolution on your computer - it doesn't matter how you change your resolution - once it's set it is what it is, and apps that don't accommodate it just aren't going to look good.
Namuna said:
I tried DPI Changer the other and couldn't get it to work, thanks for the heads-up about the build.prop!
The Nitro also already has the "Screen Optimization" util (Settings > Display > Screen Optimization) that resizes checked apps to the Nitro's display. It helped with a few games, but some games just won't work (like Asphalt 5)...But now with the Density changer, maybe I'll give it another try.
Click to expand...
Click to collapse
The Screen Optimization utility only seems to address apps that are written to a specific resolution - not pixel density. In this sense, the LCD Density is actually more like changing your computer's DPI - I didn't use that analogy first because more people are more familiar with changing a desktop's resolution. The fact is that LCD screens have a set resolution, and you cannot increase or decrease that resolution through software. The Nitro's extremely high resolution (1280x720) just isn't common enough in phones (most software would see it as a tablet) to be accounted for in all apps - particularly older ones. So, the screen optimization app that is built-in will automatically stretch apps to take up the entire 1280x720 pixels, even if the app only renders (for instance) 800x480 pixels .
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.
Hi guys,
I changed the resolution of my phone to 1920x1080 to test if it has any impact on performance or maybe even battery life.
I went to terminal and did the following:
su
wm size 1080x1920 && wm density 480
Now the resolution is set to 1920x1080, but the hardware keys (home back and the other one) stopped working.
When I change the resolution back to 1440x2560 the hardware keys start working again.
Anyone know how to make the hardware keys work again on 1080x1920?
Already tried in buildprop qemu.hw.mainkeys 1 but that didn't work.
Firstly we have to change the DPI of the screen. To do this go to the build.prop in /system and edit the line: ro.sf.lcd_density=480 to 320. (I like to use 315dpi).
Save the edited build.prop.
Now with APP ScreenSettings let's change the resolution to 720p.
Link to download APP: ScreenSettings
When opening the app, allow ROOT access and select "use a custom screen size" and type "4.5" OK.
Now under "Aspect Ratio" select 16: 9, and drag the resolution selection bar to 1280x720. Make sure that "Auto DPI selection" is selected. And press APPLY.
The system will do a quick reboot, and will start with large letters and objects. Then restart again, but a full reboot now, so that the build.prop DPI will take effect. :good:
Actually it could be still much more simple.
Download any terminal emulator apk, i use "Material Terminal" (you'll need root permissions).
- Type the following commands:
# su
# wm density 320
# wm size 720x1280
That's all.
moonlightdrive said:
Actually it could be still much more simple.
Download any terminal emulator apk, i use "Material Terminal" (you'll need root permissions).
- Type the following commands:
# su
# wm density 320
# wm size 720x1280
That's all.
Click to expand...
Click to collapse
Does this have to be done every time the system reboots? Or is it permanent?
Sent from my [device_name] using XDA-Developers Legacy app
Joel Oliveira said:
Does this have to be done every time the system reboots? Or is it permanent?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
It's totally permanent and you can swap to your desired screen resolution anytime by typing those commands again.
moonlightdrive said:
It's totally permanent and you can swap to your desired screen resolution anytime by typing those commands again.
Click to expand...
Click to collapse
ah OK, thank you! I knew only this method.
Sent from my [device_name] using XDA-Developers Legacy app
The G4 Plus screen is not 4.5", the method in the first post is for a G4.
G4 Plus screen is 5.5" diagonal, 1920x1080, 401 ppi. So the ppi for 720 should be something like 267...
SoNic67 said:
The G4 Plus screen is not 4.5", the method in the first post is for a G4.
G4 Plus screen is 5.5" diagonal, 1920x1080, 401 ppi. So the ppi for 720 should be something like 267...
Click to expand...
Click to collapse
Um, both the G4 and G4 Plus have 5.5" screens.
SoNic67 said:
The G4 Plus screen is not 4.5", the method in the first post is for a G4.
G4 Plus screen is 5.5" diagonal, 1920x1080, 401 ppi. So the ppi for 720 should be something like 267...
Click to expand...
Click to collapse
yes, I know it's 5.5, but I put 4.5 only to show the 720p resolution with the dpi326. But I believe it works when you type 5.5 too. I have a Moto G4 XT1625 (5.5 1080p).
Sent from my [device_name] using XDA-Developers Legacy app
This will improve performance of device? Can you explain how?
u_knw_who said:
This will improve performance of device? Can you explain how?
Click to expand...
Click to collapse
Probably because a lower resolution will result in more frames per second.
I'll suggest you to get 144Hz Screen to see those extra frames
Link redirects
Joel Oliveira said:
Firstly we have to change the DPI of the screen. To do this go to the build.prop in /system and edit the line: ro.sf.lcd_density=480 to 320. (I like to use 315dpi).
Save the edited build.prop.
Now with APP ScreenSettings let's change the resolution to 720p.
Link to download APP: ScreenSettings
When opening the app, allow ROOT access and select "use a custom screen size" and type "4.5" OK.
Now under "Aspect Ratio" select 16: 9, and drag the resolution selection bar to 1280x720. Make sure that "Auto DPI selection" is selected. And press APPLY.
The system will do a quick reboot, and will start with large letters and objects. Then restart again, but a full reboot now, so that the build.prop DPI will take effect. :good:
Click to expand...
Click to collapse
When I click download.......
The Link you provided takes me to a cloud page where it tells me my ip is over my limit.
I have never been to that page before.
It wants me to purchase a cloud page.
Am I missing something ?
---------- Post added at 12:48 PM ---------- Previous post was at 12:18 PM ----------
moonlightdrive said:
Actually it could be still much more simple.
Download any terminal emulator apk, i use "Material Terminal" (you'll need root permissions).
- Type the following commands:
# su
# wm density 320
# wm size 720x1280
That's all.
Click to expand...
Click to collapse
Thank You This works for me. :good:
Question: Boot Animation is now off screen is there a way to fix this or do I need a different Boot Animation ?
Thank you
The camera shows error, doesnt start
moonlightdrive said:
Actually it could be still much more simple.
Download any terminal emulator apk, i use "Material Terminal" (you'll need root permissions).
- Type the following commands:
# su
# wm density 320
# wm size 720x1280
That's all.
Click to expand...
Click to collapse
What are the commands for us to revert back to the original? Is it 480 and 1080x1920??
how to revert it back to original? i got my entire buttons messed up bruhhhh
begalaspal said:
how to revert it back to original? i got my entire buttons messed up bruhhhh
Click to expand...
Click to collapse
wm size reset
wm density reset
moonlightdrive said:
Actually it could be still much more simple.
Download any terminal emulator apk, i use "Material Terminal" (you'll need root permissions).
- Type the following commands:
# su
# wm density 320
# wm size 720x1280
That's all.
Click to expand...
Click to collapse
Thanks so much for this!
I put LineageOS on my Note 9 and the resolution was maxed at 2K+ which I don't want, regardless if it uses much more battery or not most content I watch is in 1080p or lower so 2K+ is simply not needed for me.
Joel Oliveira said:
Firstly we have to change the DPI of the screen. To do this go to the build.prop in /system and edit the line: ro.sf.lcd_density=480 to 320. (I like to use 315dpi).
Save the edited build.prop.
Now with APP ScreenSettings let's change the resolution to 720p.
Link to download APP: ScreenSettings
When opening the app, allow ROOT access and select "use a custom screen size" and type "4.5" OK.
Now under "Aspect Ratio" select 16: 9, and drag the resolution selection bar to 1280x720. Make sure that "Auto DPI selection" is selected. And press APPLY.
The system will do a quick reboot, and will start with large letters and objects. Then restart again, but a full reboot now, so that the build.prop DPI will take effect. :good:
Click to expand...
Click to collapse
pls help, i have installed sceensettings app
after reboot, the screen is oversized and i can't change it back becouse the pin lock numbers is out of screen.. how can i restore this back?
Is there any way to change the resolution of the screen from Full HD to just HD to decrease battery drain?
Please test :
from PC with adb.exe
adb shell wm size 720х1520
and next command
adb shell wm density 320
To revert :
adb shell wm size 1080х2280
adb shell wm density 480
Problem
It has a problem. When change resolution battery percentage and other icons appear behind notch and how i fix it.
Also it has screenshot problem
Sandro2101 said:
It has a problem. When change resolution battery percentage and other icons appear behind notch and how i fix it.
Also it has screenshot problem
Click to expand...
Click to collapse
Try with resolution 840x1600 and density 320, you will have a less tall screen (it hides notch)
Medo22 said:
Is there any way to change the resolution of the screen from Full HD to just HD to decrease battery drain?
Click to expand...
Click to collapse
I've tried 787x1661...it's fully functional and don't give any problem with notification bar
Hi all,
Is there a real autonomy benefit using lower screen resolution ?
I understand that it's easier/faster/less energizing to render less pixels, but I guess there should be an extra work to adapt high resolution screens to lower display.
So, can someone confirm (and maybe quantify...) the gain in batterie life using lower resolution ?
Thanks in advance :good: