[HTC 10 Guides, News, & Discussion] HD2Owner:
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.

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.