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

Search This thread

HD2Owner

Inactive Recognized Developer
Oct 9, 2009
2,340
2,472
Neuhausen am Rheinfall
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.

attachment.php


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).

attachment.php


please report back about problems or battery consumption improvements.
hit the thanks button if you like this guide.
 

Attachments

  • _screenres_optimizations.png
    _screenres_optimizations.png
    31.9 KB · Views: 5,300
  • _screenres_optimizations_2.png
    _screenres_optimizations_2.png
    42 KB · Views: 5,142
Last edited:

ordeniz

Senior Member
Oct 4, 2012
568
107
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?
 
Last edited:

HD2Owner

Inactive Recognized Developer
Oct 9, 2009
2,340
2,472
Neuhausen am Rheinfall
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.
 

ordeniz

Senior Member
Oct 4, 2012
568
107
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.
What do you mean by "a setting for only HD resolution"?
 

mainem

Member
Jun 6, 2015
5
0
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.

Did you try it? and if so did you notice a change in battery life?
Thank you.
 

NitroMehmet

Member
Mar 30, 2017
6
1
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.
YgPgyE.png
 

asetmumin99

Member
May 7, 2016
43
13
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.
 

Attachments

  • Screenshot_20180119-021116.png
    Screenshot_20180119-021116.png
    105 KB · Views: 391
  • Screenshot_20180120-162358.png
    Screenshot_20180120-162358.png
    105.3 KB · Views: 375
  • Screenshot_20180122-122502.png
    Screenshot_20180122-122502.png
    77.5 KB · Views: 365
  • Screenshot_20180124-012523.png
    Screenshot_20180124-012523.png
    79.5 KB · Views: 353
  • Screenshot_20180122-122450.png
    Screenshot_20180122-122450.png
    141.6 KB · Views: 347
  • Screenshot_20180124-012514.png
    Screenshot_20180124-012514.png
    158.6 KB · Views: 351
  • Like
Reactions: caginun

wapem

Senior Member
Jul 21, 2012
55
11
Hunedoara
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.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    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.

    attachment.php


    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).

    attachment.php


    please report back about problems or battery consumption improvements.
    hit the thanks button if you like this guide.
    3
    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.
    2
    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.
    1
    What do you mean by "a setting for only HD resolution"?

    i just added another image in the first post to explain it.
    1
    almost nothing changed, i will do much more technical experiments
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone