Hello everybody, and before all, sory for my english
The main objetive of this thread is to provide a guide to increase performance on high density screen GPU bound devices, for example, the nexus 10.
The last year android devices start shiping with very high definition screens, but without the necesary GPU muscle to make them work good.
Since I was a PC gamer, I know the terrible impact of high definition on the gaming performance, and, on this screen size, this is a useless impact, since the extra resolution are practicaly unperceptible.
The past week I spend a lot of time trying to change my device's resolution (a nexus 7) and with kernel modding, it is posible, but don't are great since I only play 1/3 of the devices usage, and the 1280x800 resolution are great for chat, browsing (or posting on the forum ).
Finally I find a great program that allow me to temporary change the display resolution of my device, and with the free version I was allowed to change resolution to 720x450, and on gaming performance, that was a GREAT performance updrade, even, with the wuality sacrifice (and on a 7 inch display, this wasn't a great lose.
In order to do that, I need to disable soft keys, since they bug A LOT with the resolution change, and to use a custom launcher because the default launcher bug too (go launcher ex is my favourite and the only one I test).
So, I leave a guide on how to prepare your device to use this mod to increase gaming performance, and to provide help to everyone who want it.
First of all, you NEED to be rooted.
Now, start with the device preparing.
Wee need a soft keys replacement, I recomend this one, work great and are really simple to customize.
https://play.google.com/store/apps/details?id=jun.ace.piecontrol
Now, you need to remove the soft keys in order to gain extra screen space and to protect yourself from potential bugs on the user interface.
To do that, you need to edit your build.prop with an editor or manually with a text editor and add this line.
qemu.hw.mainkeys=1
Now, on the next boot your device have the soft keys disabled.
To protect the status bar from being bugged, we need to change the lcd density of our display in order to allow a phone status bar (the phablet one bug on low resolution displays, and on tablets without sofkeys, we need a status bar.
To do that, we need to edit from the build.prop editor the "ro.sf.lcd_density" parameter and set it to something above 214 (nexus 7 have 213 and it enable the phablet interface, and on 214 it enable a full phone interface, but with small icons and more work space, you need to test and find the most usefull dpi for your device)
Now, we need to install the "magic app", and start testing resolutions and trying to find the most confortable for us, I have the paid version and use on the nexus 7 (16:10 or 8:5) 480x768 since it allow GREAT performance improvement and a good image quality for my screen size.
https://play.google.com/store/apps/details?id=com.nomone.resolution_changer
One example of a game that work GREAT with this trick is N.O.V.A. 3, on the tegra 3 plataform it is almost inplayable, and with the trick, on my nexus 7, it looks like this.
So, start testing this, and post your results, configs and devices.
Help us resolving the screen resolution fragmentation on devices!
And mods, please, help the post with a good language correction XD
Edit: Changed the APK link, to a new one, the new app have onscreen buttons to fix the navbar problems, so, pie controls are no longer needed, I leave the link here onlfy for people to know another alternative, thx for NoMone Devs!
i am planning to buy a 7 or 8" android with high resolution and was a bit worried about gaming performance because of the high resolution.. can you post a video of the performance gain plz?
Whoa! I might give this a go when I get home. Good Job.
i am interested for feedbacks in other heavy games like modern combat 4
this!
what android device and other mobile devices lacks.
there's no setting to set the resolution!
people out there always suggest me to change the dpi, but hell no!
"dpi" is not physical resolution, it just changing icon and other ui element to small or big.
this terms confuse many people.
they think DPI is the screen resolution.
and.... i just cannot understand the hype,
many vendors put high res 1080p on 5" device?
what the heck!? is it necessary?
what's next? ultra 4K res on 4" screen?
come on.. it's unnecesary and waste of battery.
gpu works hard to get the job done in that resolution. especially gaming.
thank you for sharing this trick for us.
google should consider to put resolution changer on the next android.
and android vendor should realize put hi-res on small screen is just plain dumb.
-----
Sent from Android device
i will try this thank you. . .:good:
It's hard to take a video without a camera, but to give youman example, on 500x800 asphalt 7 give me 60fps on the shangai track, with my 800x1280 default resolution, I have 20fps aprox with a lot of fluctutations, it's a great app, and with GMD hide buttons, is almost perfect.
Antara33 said:
It's hard to take a video without a camera, but to give youman example, on 500x800 asphalt 7 give me 60fps on the shangai track, with my 800x1280 default resolution, I have 20fps aprox with a lot of fluctutations, it's a great app, and with GMD hide buttons, is almost perfect.
Click to expand...
Click to collapse
ah that indeed seems to be very nice! i have tried it on my htc desire not it does not work nothing changed
yeahman45 said:
ah that indeed seems to be very nice! i have tried it on my htc desire not it does not work nothing changed
Click to expand...
Click to collapse
Yes, on the HTC Desire 480x800 display, you need to set it to something lower that it, for example, 360x600, it increase the gaming performance, this trick work great on high res display like the nexus 7 or nexus 10 displays for example, try to reduce the resoution to something that retain the original aspect ratio and be lower that 480x800, 360x600 or 240x400 make a grat change, but im not sure about image quality on this device...
Antara33 said:
Yes, on the HTC Desire 480x800 display, you need to set it to something lower that it, for example, 360x600, it increase the gaming performance, this trick work great on high res display like the nexus 7 or nexus 10 displays for example, try to reduce the resoution to something that retain the original aspect ratio and be lower that 480x800, 360x600 or 240x400 make a grat change, but im not sure about image quality on this device...
Click to expand...
Click to collapse
ok thx i have tried to set it to 360x640 on the free version.. but nothing happens.. it just say "Display scaler free has been granted root superuser permissions" and nothing happens
Mh, maybe this is a device specific issue, have you posted a review or sended the autor an feedback email about it?
Antara33 said:
Hello everybody, and before all, sory for my english
The main objetive of this thread is to provide a guide to increase performance on high density screen GPU bound devices, for example, the nexus 10.
The last year android devices start shiping with very high definition screens, but without the necesary GPU muscle to make them work good.
Since I was a PC gamer, I know the terrible impact of high definition on the gaming performance, and, on this screen size, this is a useless impact, since the extra resolution are practicaly unperceptible.
The past week I spend a lot of time trying to change my device's resolution (a nexus 7) and with kernel modding, it is posible, but don't are great since I only play 1/3 of the devices usage, and the 1280x800 resolution are great for chat, browsing (or posting on the forum ).
Finally I find a great program that allow me to temporary change the display resolution of my device, and with the free version I was allowed to change resolution to 720x450, and on gaming performance, that was a GREAT performance updrade, even, with the wuality sacrifice (and on a 7 inch display, this wasn't a great lose.
In order to do that, I need to disable soft keys, since they bug A LOT with the resolution change, and to use a custom launcher because the default launcher bug too (go launcher ex is my favourite and the only one I test).
So, I leave a guide on how to prepare your device to use this mod to increase gaming performance, and to provide help to everyone who want it.
First of all, you NEED to be rooted.
Now, start with the device preparing.
Wee need a soft keys replacement, I recomend this one, work great and are really simple to customize.
https://play.google.com/store/apps/details?id=jun.ace.piecontrol
Now, you need to remove the soft keys in order to gain extra screen space and to protect yourself from potential bugs on the user interface.
To do that, you need to edit your build.prop with an editor or manually with a text editor and add this line.
qemu.hw.mainkeys=1
Now, on the next boot your device have the soft keys disabled.
To protect the status bar from being bugged, we need to change the lcd density of our display in order to allow a phone status bar (the phablet one bug on low resolution displays, and on tablets without sofkeys, we need a status bar.
To do that, we need to edit from the build.prop editor the "ro.sf.lcd_density" parameter and set it to something above 214 (nexus 7 have 213 and it enable the phablet interface, and on 214 it enable a full phone interface, but with small icons and more work space, you need to test and find the most usefull dpi for your device)
Now, we need to install the "magic app", and start testing resolutions and trying to find the most confortable for us, I have the paid version and use on the nexus 7 (16:10 or 8:5) 480x768 since it allow GREAT performance improvement and a good image quality for my screen size.
https://play.google.com/store/apps/details?id=com.nexter.miniscalerfree
One example of a game that work GREAT with this trick is N.O.V.A. 3, on the tegra 3 plataform it is almost inplayable, and with the trick, on my nexus 7, it looks like this.
So, start testing this, and post your results, configs and devices.
Help us resolving the screen resolution fragmentation on devices!
And mods, please, help the post with a good language correction XD
Click to expand...
Click to collapse
Hey I bought the app and it works fine i tried most of the resolutions and even a custom one but it seems that no resolution lower than my physical one will go full screen i always get black borders do you get this too?
thanks a8 soc
I tried tweaking my resolution to a higher one yet nothing happens on my Alcatel OneTouch T10. Any fix on this?
Sory for the lazy responce, I have so much time working and other personal things I read on the store that the apk only make the new resolution use the full screen on 4.2+ so if you are on 4.1-, you have it with black borders, sory, but I cant do anything for this :/
is there any way after change resolution for fix buttom touch key(it doesnt work physical touch key)? or any idea where is touch key config file or something like that related in root?
THUNDERASS said:
is there any way after change resolution for fix buttom touch key(it doesnt work physical touch key)? or any idea where is touch key config file or something like that related in root?
Click to expand...
Click to collapse
I don't know, I suppose, android mao this keys as a touchscreen surface or something like that, the most easybway is using gmd hide softkeys and with it, trigger a softkeys quick navbar and play with this, I am using Paranoidandroid right now and with the pie controls I fix all my problems, and on smanager I created 2 scripts to execute the commands to change resolution, one for the 500x800 for gaming and the other to 1280x800, the default resolution of the nexus 7.
Try it and leave me a comment with your experience.
Antara33 said:
I don't know, I suppose, android mao this keys as a touchscreen surface or something like that, the most easybway is using gmd hide softkeys and with it, trigger a softkeys quick navbar and play with this, I am using Paranoidandroid right now and with the pie controls I fix all my problems, and on smanager I created 2 scripts to execute the commands to change resolution, one for the 500x800 for gaming and the other to 1280x800, the default resolution of the nexus 7.
Try it and leave me a comment with your experience.
Click to expand...
Click to collapse
Thanls for your reply.i have mtk quad core 6589T 1.5 ghz device with powervr 544MP1 and 1 gb ram . My screen is 1080p. i think gpu cant handle this resolution sometimes occur wierd lag and some highend games cant playable.After change resolution to 720p and 320 dpi everything perfect games performance increase %80-100 even memory consumption decreasing.(100mb).i am using with pie control but i want to using continiusly 720p i think after change resulotion touch key coordinates change over screen size.if i found that responsible cfg file or something maybe i can handle this.i am still searching..
THUNDERASS said:
Thanls for your reply.i have mtk quad core 6589T 1.5 ghz device with powervr 544MP1 and 1 gb ram . My screen is 1080p. i think gpu cant handle this resolution sometimes occur wierd lag and some highend games cant playable.After change resolution to 720p and 320 dpi everything perfect games performance increase %80-100 even memory consumption decreasing.(100mb).i am using with pie control but i want to using continiusly 720p i think after change resulotion touch key coordinates change over screen size.if i found that responsible cfg file or something maybe i can handle this.i am still searching..
Click to expand...
Click to collapse
For me, the way to go is sticking with default res for everything except gaming, as I say, I have two scripts on 2 widgets on my main screen, one with the commands
su
wm size 500x800
And the other with the commands
su
wm size reset
on jely bean 4.3 this commands set the override resolution of the screen.
on android 4.2.x the wm have to be replaced with am.
The app launch this terminal commands and override our resolution, but since I cant buy the app because of credit card and legal issues on argentina, I made my own scripts with smanager and swidgets . Quick on the fly change, and "letz rack!"
i am using this fantastic program on my thl w8s to scale resolution from 1080p to 720p during games and the speedup is fantastic...i set tasker to autolaunch the app when i click on the game icon, and once finished the game just click on fixes/reset resolution to bring everything back to 1080p . this program is great and the only one i have found...let's hope the developer doesn't abandon it and keeps making it better....and with a better integration in tasker maybe
As the title says, you can use the adb wm size command to change the resolution, higher.
On most phones the resolution shipped is the highest available.
The RM3&3S ship stock 1080p but easily go up much higher.
Personally i recommend 1440x3120
wm size 1440x3120
In an su terminal or adb by pc.
This brings the display up to current phones resolution! (2k)
Enjoy!
As for performance and battery life, there is no noticeable NEGATIVE impact. However, when screen recording or streaming your screen, it can lag if your connection cant support the higher resolution. Native screen recording should be unaffected.
SilentDevGuy said:
As the title says, you can use the adb wm size command to change the resolution, higher.
On most phones the resolution shipped is the highest available.
The RM3&3S ship stock 1080p but easily go up much higher.
Personally i recommend 1440x3120
wm size 1440x3120
In an su terminal or adb by pc.
This brings the display up to current phones resolution! (2k)
Enjoy!
As for performance and battery life, there is no noticeable NEGATIVE impact. However, when screen recording or streaming your screen, it can lag if your connection cant support the higher resolution. Native screen recording should be unaffected.
Click to expand...
Click to collapse
wow nice
anyone has tested this ?
I have downloaded the DevCheck app and under HARDWARE tab > Graphics > Resolution, it is shown as 2340 x 1080. Does it mean that on adb I have to type wm size 3120x1440 instead ?
Thank you
SilentDevGuy said:
As the title says, you can use the adb wm size command to change the resolution, higher.
On most phones the resolution shipped is the highest available.
The RM3&3S ship stock 1080p but easily go up much higher.
Personally i recommend 1440x3120
wm size 1440x3120
In an su terminal or adb by pc.
This brings the display up to current phones resolution! (2k)
Enjoy!
As for performance and battery life, there is no noticeable NEGATIVE impact. However, when screen recording or streaming your screen, it can lag if your connection cant support the higher resolution. Native screen recording should be unaffected.
Click to expand...
Click to collapse
I have tried changing the resolution yes the screen changed to a smaller icon etc but the problem is the below area is not responding to touch for example, the soft button; back, home and app manager does not work when touched.
On mine
lius90 said:
I have tried changing the resolution yes the screen changed to a smaller icon etc but the problem is the below area is not responding to touch for example, the soft button; back, home and app manager does not work when touched.
Click to expand...
Click to collapse
On mine it works without issue at all and I can touch all the way up to 5k no problem, can you tell me your device model and rom?
Not to be rude or offend you but it is 100% user error on your side, the resolutions are accepted, and tested on A11 and A10 multiple devices. Also the icons smaller and all that is just based on DPI, resolution is the resolving power.
lius90 said:
wow nice
anyone has tested this ?
I have downloaded the DevCheck app and under HARDWARE tab > Graphics > Resolution, it is shown as 2340 x 1080. Does it mean that on adb I have to type wm size 3120x1440 instead ?
Thank you
Click to expand...
Click to collapse
No, use 1440x3120 it matters what order the numbers are in.
Thankyou
Thank you. For the display to work properly, you also need to change the pixel density. We enter three commands in adb:
wm size 1440x3120
wm density 640
reboot
Increased clarity even in games! See screenshots...
Source: https://lumpics.ru/how-change-screen-resolution-on-android/#helpgood
Disable nubia red magic 3 animated boot splash screen on phone boot and reboot, save your zip, download my zip and replace via total commander
bootanimation.zip
shutdownanimation.zip
File path:
system/media/theme/bootup
system/media/theme/shutdown
Here is a program Easy DPI Changer root for those who have root rights:
Easy DPI Changer [Root] - Apps on Google Play
Make your screen yours
play.google.com
In the "Density" field, enter the DPI, and in the "Resolution" field, enter the width and length. After changing each parameter, click "Apply" in its block to save the new values. They will apply after a reboot.
I played around with this screen resolution and returned to standard resolution!
Hello,
We're working on Android S in a virtualized environment (Running via QEMU emulator).
How do we change the resolution from the source code ? .
Also, how does
wm size AxB (where A and B are resolution numbers) work in the background from the adb shell ?
Click to expand...
Click to collapse
Which place in the source code do we look for to change the resolution ?
The host is an Ubuntu Setup, and we're using QEMU 6.
Attached screenshot is how we run the Android VM.
You change Android's screen resolution and/or density by editing it's "build.prop" file.
Example:
Code:
adb shell wm size 1080x1920
and then
Code:
adb shell wm density 390
BTW:
Resolution is defined as the following on Google's developer portal:
The total number of physical pixels on a screen. When adding support for multiple screens, applications do not work directly with resolution; applications should be concerned only with screen size and density, as specified by the generalized size and density groups.
And screen density:
The quantity of pixels within a physical area of the screen; usually referred to as dpi (dots per inch). For example, a "low" density screen has fewer pixels within a given physical area, compared to a "normal" or "high" density screen. For simplicity, Android groups all actual screen densities into six generalized densities: low, medium, high, extra-high, extra-extra-high, and extra-extra-extra-high.
xXx yYy said:
"build.prop"
Click to expand...
Click to collapse
what's the build.prop value ?
xXx yYy said:
You change Android's screen resolution and/or density by editing it's "build.prop" file.
Example:
Code:
adb shell wm size 1080x1920
and then
Code:
adb shell wm density 390
BTW:
Resolution is defined as the following on Google's developer portal:
The total number of physical pixels on a screen. When adding support for multiple screens, applications do not work directly with resolution; applications should be concerned only with screen size and density, as specified by the generalized size and density groups.
And screen density:
The quantity of pixels within a physical area of the screen; usually referred to as dpi (dots per inch). For example, a "low" density screen has fewer pixels within a given physical area, compared to a "normal" or "high" density screen. For simplicity, Android groups all actual screen densities into six generalized densities: low, medium, high, extra-high, extra-extra-high, and extra-extra-extra-high.
Click to expand...
Click to collapse
I can change the resolution, while running the image.
with
adb shell > wm size 1920x1080 or something like that.
but, what i want to achieve is, writing a C/C++ code, which can help me change the resolution to whatever i feel like within the minResolution and maxResolution limits of the screen.
something like,
./screen_reso 1920 1080 (passing 1920 1080 as command line arguments or even inside the code)