Oneplus 7 Pro
Force 90hz Refresh Rate in almost every App (and Games)
*also uncaps FPS (since Vsync is on by default for Android)
Requirements:
1. A Windows PC (Windows 10 64 Bit is preferred)
2. Oneplus Drivers
3. A USB Type-C Cable
4. Your Oneplus 7 Pro
Steps:
1. Plug in your Oneplus device and select File Transfer mode in your phone's notification selection, then open My Computer and you will see the drive for Oneplus Drivers.
2. Install Oneplus Drivers (you may be prompted to reboot afterwards). You may need to plug and unplug the device to finish driver recognition. Unplug your phone once it is finished.
3. In your phone, go to Settings > About Phone, and tap Build Number multiple times in fast succession until the message "you are now a developer" appears.
4. Go to Settings > System > Developer Options, and turn on USB-debugging.
5. Go to Playstore and download jOnePlus Tools
6. Plug your device in your PC.
7. Anywhere on the empty desktop of your PC, press shift + right click, and select "Open Powershell window here"
8. Wait for Powershell to load
9. Type "adb shell" without the quotes
10. A permission prompt will appear in your Oneplus 7 Pro's screen, allow it.
11. Type "adb shell" once again and press Enter, and you should see your device like this "Oneplus7Pro:/ $"
12. Type or copy-paste the text below without the quotes:
"pm grant net.jroot3d.joneplustools android.permission.WRITE_SECURE_SETTINGS", and press Enter.
13. Once you've entered that, it should repeat what you've typed in the next line.
14. Unplug your device, and open jOnePlus Tools app.
15. Tap Screen Refresh Rate and select Force 90Hz
16. Congratulations, you are done! To confirm, you can go to Settings > Display > Screen Refresh Rate and you should see it as 60Hz from the outside, but when you tap it, you will see that nothing from the 2 choices is selected. It means you are using the 3rd Hidden Setting.
Tip: You may need to reselect Force 90 Hz from the jOnePlus Tools if you have selected 90hz or 60hz from the settings.
Note: This will enable 90hz (and up to 90 fps) for apps and games, unless the app itself has an even stronger FPS-controller then it will tone-down the FPS to the standard set by that game. But for most games without an FPS controller or 30-FPS-locked games without an in-game FPS-controller, it will work 100%.
Credits:
C3C076 (XDA Developer, Dev of GravityBox)
JRoot3D.dev (jOnePlus Tools Developer)
Guide Maker: Ares (Freyelis - XDA Senior Member)
RIP Battery Life?
stanley08 said:
RIP Battery Life?
Click to expand...
Click to collapse
No, try it. The brightness and resolution actually kills more battery than the refresh rate, so set the reso to dynamic, and the brightness to less than 50% always.
Freyelis said:
No, try it. The brightness and resolution actually kills more battery than the refresh rate, so set the reso to dynamic, and the brightness to less than 50% always.
Click to expand...
Click to collapse
Maybe I will
stanley08 said:
Maybe I will
Click to expand...
Click to collapse
Enjoy better gaming man. Try it on Assassin's Creed: Identity too, that game has awesome graphics but was locked at 30 FPS... Not anymore
Freyelis said:
No, try it. The brightness and resolution actually kills more battery than the refresh rate, so set the reso to dynamic, and the brightness to less than 50% always.
Click to expand...
Click to collapse
Anyway to set auto brightness but less than 50% always ??
Or you could simply use Smurf kernel which already has this in the config and stays set through reboots. Or just use the original method from C3C076 which sets it permanently no need for this extra stuff or to have joneplus tools constantly in background for no reason...
9 hrs SOT? @op do you have qhd or fhd?
Stock kernel? Any mods?
if i restart my phone will the settings i made gone?
se7ensde said:
Or you could simply use Smurf kernel which already has this in the config and stays set through reboots. Or just use the original method from C3C076 which sets it permanently no need for this extra stuff or to have joneplus tools constantly in background for no reason...
Click to expand...
Click to collapse
Adb method from C3C076 resets after every reboot, that's why I made this tutorial for those unrooted people who wants to make the setting stick.
bubu23 said:
if i restart my phone will the settings i made gone?
Click to expand...
Click to collapse
No
Xalph92 said:
Anyway to set auto brightness but less than 50% always ??
Click to expand...
Click to collapse
Either set it manually, or use YAAB app as a replacement for auto brightness, which you can set the maximum ang minimum brightness.
virtyx said:
9 hrs SOT? @op do you have qhd or fhd?
Stock kernel? Any mods?
Click to expand...
Click to collapse
Dynamic, stock kernel.
No mods, I just control every background app using built-in background restriction, deepclear, and deep battery optimization.
Just for information, my kernel config has a switch to apply 90Hz, auto or 60 HZ.
Gesendet von meinem xXx_NoLimits_7.1 on GM1913 mit Tapatalk
Freyelis said:
Adb method from C3C076 resets after every reboot, that's why I made this tutorial for those unrooted people who wants to make the setting stick.
Click to expand...
Click to collapse
Did you actually test it? "ADB shell settings global put" command changes user settings that are stored in the filesystem and are thus persisted across reboots until explicitly changed by the user.
Freyelis said:
Dynamic, stock kernel.
No mods, I just control every background app using built-in background restriction, deepclear, and deep battery optimization.
Click to expand...
Click to collapse
Have you restricted system apps too? Did you do this for each app one by one?
Do you have a list of what you've restricted
thanks!
thanks!!!so after doing this im rooted already?because jtools need root right?
Freyelis said:
Adb method from C3C076 resets after every reboot, that's why I made this tutorial for those unrooted people who wants to make the setting stick.
Click to expand...
Click to collapse
Stays through reboots for me... And like I said there are easier simpler and faster ways to achieve this without need of all this extra stuff. Smurf kernel already implemented this in his config so it stays like that too. And C3C076 had made qs tiles for this. I've been using his method for over a week now through several reboots no issues.
C3C076 said:
Did you actually test it? "ADB shell settings global put" command changes user settings that are stored in the filesystem and are thus persisted across reboots until explicitly changed by the user.
Click to expand...
Click to collapse
Sorry, thanks for the clarification sir, great work as always, will revise this one
virtyx said:
Have you restricted system apps too? Did you do this for each app one by one?
Do you have a list of what you've restricted
Click to expand...
Click to collapse
I did not restrict system apps, only the apps that I installed. Apps that I need notifications from such as Telegram, is not included in the restriction. All other apps are, like games, editors, etc..
Related
THE PROBLEM
To save battery while playing video Tegra intelligently decreases the backlight while increasing color brightness and contrast. Because it monitors on a frame by frame basis the changes are often unnoticable. You basically end up with the same displayed image using less backlight.
Unfortunately it seems to get stuck even after you leave the video and the changes are very noticeable as the changes were specific to the video frame you just left and not your homescreen.
This also may be the cause of some ghosting issues and for some it seems to eliminate any ghosting problems for them.
MANUAL FIX
(will reset at each reboot)
In terminal -
(You may need to type "su" and press enter before entering these commands)
To turn it off
echo "0" > /sys/devices/tegradc.0/smartdimmer/enable
To change how aggressive it is (untested)
echo "#" > /sys/devices/tegradc.0/smartdimmer/aggressiveness
Note: battery life while watching videos WILL decrease if you turn it off or decrease the aggresiveness
AUTOMATIC FIX
Trickster Mod
- has the ability to disable PRISM and set it to disable on boot.
N7scripts.rar
- A collection of scripts compiled by hamdir which, in conjunction with Script Manager (available in the market) will allow you to toggle smartdimmer/PRISM on and off at will.
- You can also use script manager to toggle it at boot if you want.
- Also includes a script to disable 3D scaling which may improve 3D gaming performance (untested)
Thanks to hamdir for his pack of scripts and for convincing me to make a new post for these fixes.
I may use this for other sysfs tweaks... mine for now.
Thanks. Easier to save and flash then manually entering in these values each time I crackflash.
If the T3 can increase the color saturation and gamma while decreasing backlight, wonder if we can increase the colors while leaving the backlight alone. All of the N7s I've played with have a dull washed out look with a warm tone for whites.
Sent from my Nexus 7 using xda premium
does flashing the .zip just delete the PRISM file? cuz when I manually enter the command after flashing it via CWM it doesn't allow me to any more.
"
ROM may flash stock recovery on boot? Fix?
No
.
.
.
.
.
Yes - Disable Recovery flash
.
.
.
+++ Go back +++
which reboots if you "go back" what is this?
-------------------------------------------------------------------------
How do you set up the script? I have script manager and the Scrip.rar saved onto my SD card. Thanks in advance!
player911 said:
Thanks. Easier to save and flash then manually entering in these values each time I crackflash.
If the T3 can increase the color saturation and gamma while decreasing backlight, wonder if we can increase the colors while leaving the backlight alone. All of the N7s I've played with have a dull washed out look with a warm tone for whites.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Messing with the kernel I haven't had any luck. You could ask Morfic. He might be able to make something happen.
Also prism increase color BRIGHTNESS for the most part (you said saturation). That's why the homescreen ends up looking washed out and bright and not oversaturated when PRISM fails to shut off.
Sent from my Nexus 7 using xda premium
sharp2G said:
does flashing the .zip just delete the PRISM file? cuz when I manually enter the command after flashing it via CWM it doesn't allow me to any more.
"
ROM may flash stock recovery on boot? Fix?
No
.
.
.
.
.
Yes - Disable Recovery flash
.
.
.
+++ Go back +++
which reboots if you "go back" what is this?
-------------------------------------------------------------------------
How do you set up the script? I have script manager and the Scrip.rar saved onto my SD card. Thanks in advance!
Click to expand...
Click to collapse
There's no prism file. These tweaks are changing a sysfs value. There's no file. The flashable zip adds an init.d file that runs the manual command at every boot.
In your case CWM is complaining about a file that flashes stock recovery on boot and overwrites CWM. These are completely different things. Let CWM "disable recovery flash" and you'll be good to go.
Sent from my Nexus 7 using xda premium
This is awesome. It definitely needs to be implemented in a ton of ROMs
so does flashing this decrease battery life when watching videos? im confused by op..
awesome post, thx!
yes this fix, completely get rid of the grey levels washout issues!!! and greatly improves the quality of the display, it will cost some battery life, but any boost to this average screen is welcome
now about ghosting it did reduce it a lot but sadly it didn't kill it, i still get the very random occasion of faint LCD ghosting
finally we really need to find out a way to fix the stupid low saturation, in particularly the greens are very low
google....these screen issues, lack of tablet UI and launcher rotation issues, makes want to smash it through the wall
Nice find. Hopefully Google/Nvidia/Asus will fix this in an update.
Thank you very much for this! While I don't own a Nexus 7, I *do* own an Asus TF700T and this problem also exists on it. On the TF700, this "mode" is active all of the time, no matter what you are doing and it is *very* noticeable and distracting, especially when watching videos (but it *is* noticeable everywhere else as well).
Disabling this "Feature" makes the problem go away. At the very least, you can enable/disable as needed now.
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Hello from Germany,
my Nexus is unlocked and rooted
Terminal:
su
cd /sys/devices/tegradc.0/smartdimmer
./enable
"Permission denied"
change user rights:
chmod 744 enable
(old settings are 644)
./enable
./enable[1]: 1: not found
so where is my fault?
ever since i disabled this gamma destroying feature and my screen keeps getting better and better
starting to fall in love with it really
Riquelme10 said:
Hello from Germany,
my Nexus is unlocked and rooted
Terminal:
su
cd /sys/devices/tegradc.0/smartdimmer
./enable
"Permission denied"
change user rights:
chmod 744 enable
(old settings are 644)
./enable
./enable[1]: 1: not found
so where is my fault?
Click to expand...
Click to collapse
you didn't even enter the command line properly...
Sent from my Nexus 7
sharp2G said:
you didn't even enter the command line properly...
Sent from my Nexus 7
Click to expand...
Click to collapse
Care to post how it should be done then? Might be a little bit more helpful
Also, does this affect battery life overall? Or just while watching movies?
Riquelme10 said:
Hello from Germany,
my Nexus is unlocked and rooted
Terminal:
su
cd /sys/devices/tegradc.0/smartdimmer
./enable
"Permission denied"
change user rights:
chmod 744 enable
(old settings are 644)
./enable
./enable[1]: 1: not found
so where is my fault?
Click to expand...
Click to collapse
You do not "run" the "enable" file. You need to do this:
echo "0" > /sys/devices/tegradc.0/smartdimmer/enable
or
echo "0" > enable (if you are already in that dir).
That will disable the SMartDimmer "feature". Echoing a "1" will re-enable it. I have not noticed any battery life difference....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
espionage724 said:
Care to post how it should be done then? Might be a little bit more helpful
Also, does this affect battery life overall? Or just while watching movies?
Click to expand...
Click to collapse
yes its an LCD battery saving feature and so disabling it will definitely reduce battery life
choose between battery life or quality display
hamdir said:
yes its an LCD battery saving feature and so disabling it will definitely reduce battery life
choose between battery life or quality display
Click to expand...
Click to collapse
Yes as said in the OP smart dimmer analyzes the video frames and determines whether it can lower the backlight while increasing the color brightness and maintain almost the same image. Lower backlight = better battery life.
Sent from my Nexus 7 using xda premium
After I turned off the dimmer, the screen got a little brighter, so I manually turned down my normal 40% brightness to 30% brightness. So in the end I don't think I'm losing any battery life at all.
Ravynmagi said:
After I turned off the dimmer, the screen got a little brighter, so I manually turned down my normal 40% brightness to 30% brightness. So in the end I don't think I'm losing any battery life at all.
Click to expand...
Click to collapse
I agree - I think any battery life reduction will be *very* minor for most people... I certainly haven't noticed any difference...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
My Oneplus 3T is autoclosing apps that I am using while running, they are running in the background to give me timing and track my GPS, they are just randomly closed.
I have disabled Aggressive Doze and Auto-close high power apps but it is still happening. Is there anything I can do to prevent this?
Preau said:
My Oneplus 3T is autoclosing apps that I am using while running, they are running in the background to give me timing and track my GPS, they are just randomly closed.
I have disabled Aggressive Doze and Auto-close high power apps but it is still happening. Is there anything I can do to prevent this?
Click to expand...
Click to collapse
Yes, activate the lock (top right / multitasking screen) or flash a custom kernel (like: https://forum.xda-developers.com/on...ernel-franco-kernel-r1-28th-november-t3508904) which supports more background apps (limit raised to 60 from stock 32)
Fir3start3r said:
Yes, activate the lock (top right / multitasking screen) or flash a custom kernel (like: https://forum.xda-developers.com/on...ernel-franco-kernel-r1-28th-november-t3508904) which supports more background apps (limit raised to 60 from stock 32)
Click to expand...
Click to collapse
Thanks, I didn't know what the lock button was for. I'll try it next time I go running!
Fir3start3r said:
Yes, activate the lock (top right / multitasking screen)
Click to expand...
Click to collapse
Dumb queston: where is that setting? Can't seem to find it
JRSax said:
Dumb queston: where is that setting? Can't seem to find it
Click to expand...
Click to collapse
Sent from my OnePlus3T using XDA Labs
hello, does the lock solve the issue, could you please confirm ?
There are some hidden settings which might cause this
1. Apps - Setting - Apps auto-launch . Make sure it's turned off
2. Advanced - Recent app management - Make sure Normal clear is selected.
There is option in setting that close the application as soon you clear it from recent apps ....Setting/system UI/advanced
...Make sure it desabled.....Enjoy your device
I can't find any such setting. Which phone are you using now?
3T
---------- Post added at 12:27 PM ---------- Previous post was at 12:24 PM ----------
Naitik527 said:
3T
Click to expand...
Click to collapse
stacyy said:
I can't find any such setting. Which phone are you using now?
Click to expand...
Click to collapse
You have to start system UI tuner then you will be able to see this setting that's why
Preau said:
My Oneplus 3T is autoclosing apps that I am using while running, they are running in the background to give me timing and track my GPS, they are just randomly closed.
I have disabled Aggressive Doze and Auto-close high power apps but it is still happening. Is there anything I can do to prevent this?
Click to expand...
Click to collapse
How about battery optimization setting? apps > gear > special access > battery optimization > apps in Not optimized list?
Yeah, I know. There's Doze, Aggressive Doze, and this Battery Optimization.
I'm having the same issue. Tried Franco Kernel and it didn't help.
Fir3start3r said:
Yes, activate the lock (top right / multitasking screen) or flash a custom kernel (like: https://forum.xda-developers.com/on...ernel-franco-kernel-r1-28th-november-t3508904) which supports more background apps (limit raised to 60 from stock 32)
Click to expand...
Click to collapse
I have tried locking Pokemon Go and it seemed to be working until today when it was killed in the background and I had to reload.
I'm not sure if this is a PoGo issue or a OnePlus issue.
I have now turned off battery optimisations for PoGo to see how that goes.
jamesl1001 said:
I have tried locking Pokemon Go and it seemed to be working until today when it was killed in the background and I had to reload.
I'm not sure if this is a PoGo issue or a OnePlus issue.
I have now turned off battery optimisations for PoGo to see how that goes.
Click to expand...
Click to collapse
So far none of the solutions listed have worked for me. I have same problem with Pokemon Go, Lyft, and Uber. I'm on stock 7.0 not rooted. I tried the Beta 7.1.1 and no difference.
Sent from my ZTE A2017U using XDA-Developers Legacy app
I started my torrent download and i slept as it was downloading in background, but in the morning the download dissappear how to fix this
Same Problem
I'm also having the same problem with PoGo. I can't find this lock button.
I have the same issue with some apps, including PoGo and Firefox and probably Discord (chat application). I bought this device with 6 GB to have not these issues. I'm quite disappointed. The issue occured with Android 6, with what the device was shipped, and with the latest Android 7.1. Maybe it doesn't have 6 GB at all and they did cheat me?
The lock button on the task manager screen does just prevent apps to be swiped away in my opinion.
i have the same issue when playing with pokemon go. very annoying. especially when its connected to my pogo plus. never had an issue with my s7e.
glad i'm not the only one. NPR app closes by itself when I'm listening to it.. I've noticed flipboard closing while i'm using it as well.
Just use a custom kernel, stock one has a limit on 32 max apps open. Other than that the solutions are those given already (Lock icon, disable battery opt for that app, disable doze, etc.)
To save battery, and perhaps have a nice experience could we somehow set screen refresh rate to 90HZ? Does anybody have any info about how to do this..and if it is even possible?
With ADB Fastboot Tool use commands:
adb devices
adb shell
settings put system peak_refresh_rate 90
settings put system min_refresh_rate 90
How can we revert if we don't like?
Simply click at the display settings or also some Adb commands?
Edit: switching in settings to 120 and back to 60 reverts it
Adb shell
settings put system peak_refresh_rate 90
settings put system min_refresh_rate 60
Wouldn't this be better? So some apps only run in 60hz while the others run at 90 instead of 120?
Worked fine
yes it worked. I believe this has to be done every reboot. But let's see if we can get some more juice out of the battery.
qvert said:
Adb shell
settings put system peak_refresh_rate 90
settings put system min_refresh_rate 60
Wouldn't this be better? So some apps only run in 60hz while the others run at 90 instead of 120?
Click to expand...
Click to collapse
Yes this is the right way. For the apps I am not sure but I am sure that lot of them are not yet optimize for more than 60Hz. Like watching YT is still 60Hz , lot of games don't pass 60Hz and I can imagine all the smaller companies apps ...
But with the settings I made I don't need to go below 120Hz. Mine is locked at 120Hz with this commands. And my battery life is more than good. I cannot drain it in one day with heavy usage.
superior888 said:
To save battery, and perhaps have a nice experience could we somehow set screen refresh rate to 90HZ? Does anybody have any info about how to do this..and if it is even possible?
Click to expand...
Click to collapse
Use SetEdit app from PlayStore...
On the 'system table' inside the app, scroll find 'user_refresh_rate' and change the value to 90, and save...
Lock the app on the recent tab, and you good to go... I've tried it... Works flawlessly...
qvert said:
Adb shell
settings put system peak_refresh_rate 90
settings put system min_refresh_rate 60
Wouldn't this be better? So some apps only run in 60hz while the others run at 90 instead of 120?
Click to expand...
Click to collapse
Thx, this works!
qvert said:
Adb shell
settings put system peak_refresh_rate 90
settings put system min_refresh_rate 60
Wouldn't this be better? So some apps only run in 60hz while the others run at 90 instead of 120?
Click to expand...
Click to collapse
This works till I open youtube or GPhone. After it is set to 120 hz again
This works in Normal mode. The moment I change to "battery saver" screen goes back to 60Hz. Any solutions?
ZionMainframe said:
This works in Normal mode. The moment I change to "battery saver" screen goes back to 60Hz. Any solutions?
Click to expand...
Click to collapse
Why put Battery Saver if you don't want save battery ?
Pho3nX said:
Why put Battery Saver if you don't want save battery ?
Click to expand...
Click to collapse
I want to use other features of battery saver (like aggressive killing of background apps) whilst using a 120Hz screen.
ZionMainframe said:
I want to use other features of battery saver (like aggressive killing of background apps) whilst using a 120Hz screen.
Click to expand...
Click to collapse
Ok so you can use SmartHertz for choose Refresh Rate by apps, can stay 120 hz even with Battery Saver mode.
SmartHertz - XDA
SmartHertz - Google Play
Pho3nX said:
Ok so you can use SmartHertz for choose Refresh Rate by apps, can stay 120 hz even with Battery Saver mode.
SmartHertz - XDA
SmartHertz - Google Play
Click to expand...
Click to collapse
Tried this App. Didn't work. Same issue. The moment I turn batter saver on, refresh rate goes to 60
Asnamus said:
With ADB Fastboot Tool use commands:
adb devices
adb shell
settings put system peak_refresh_rate 90
settings put system min_refresh_rate 90
Click to expand...
Click to collapse
can this be converted to a build.prop value ?
Seems like the 90hz setting reverts back to 120 once I switch to power saving or 60hz. Anyway to make it permanent?
Tr
ZionMainframe said:
Tried this App. Didn't work. Same issue. The moment I turn batter saver on, refresh rate goes to 60
Click to expand...
Click to collapse
Try galaxy max hertz app
galaxy max hertz app only work Samsung?
kozmikdeli said:
galaxy max hertz app only work Samsung?
Click to expand...
Click to collapse
No, it works on mi 11 series.
I have downloaded an app called touch sampling rate checker and my Moto Edge 20 only shows a rate of 90-117hz regardless of screen refresh rate setting, however when using the same app on my mi11 it shows a constant 250hz and the mi 11 seems smoother in Twitter and Facebook etc am I missing something here?
Touch sampling rate and refresh rate are two different things. If you want a refresh rate checker, you can find it in developer options.
PhotonIce said:
Touch sampling rate and refresh rate are two different things. If you want a refresh rate checker, you can find it in developer options.
Click to expand...
Click to collapse
Yeah I get that but I thought this phone has a 576hz touch sample rate? Unless the app is inaccurate ?
Not sure about the app, maybe try a different one.
nealyblue said:
Yeah I get that but I thought this phone has a 576hz touch sample rate? Unless the app is inaccurate ?
Click to expand...
Click to collapse
You have to enable game mode for individual apps for max touch sampling rate to be enabled.
dannejanne said:
You have to enable game mode for individual apps for max touch sampling rate to be enabled.
Click to expand...
Click to collapse
Unfortunately I already did that and the maximum I see is 250hz. Where have the 576hz they said gone?
fulltronservice said:
Unfortunately I already did that and the maximum I see is 250hz. Where have the 576hz they said gone?
Click to expand...
Click to collapse
Yeah the highest I've seen is 400hz with game mode
nealyblue said:
Yeah the highest I've seen is 400hz with game mode
Click to expand...
Click to collapse
So that means that the value is dynamic up to 576hz. nothing to worry about then
Android apps dont usually report the correct sampling rate. Connect the phone through USB to a PC and run through ADB run the commands: "Adb shell getevent -r -t -l" and then start swiping on the display. It should report the correct sampling rate.
Username: Required said:
Android apps dont usually report the correct sampling rate. Connect the phone through USB to a PC and run through ADB run the commands: "Adb shell getevent -r -t -l" and then start swiping on the display. It should report the correct sampling rate.
Click to expand...
Click to collapse
That ADB thing really helped. Now I can see the real use of touch sensitivity. From the huge list that came out I could see a maximum of 473hz. So the capability that Motorola offers is installed.
Thanks
fulltronservice said:
That ADB thing really helped. Now I can see the real use of touch sensitivity. From the huge list that came out I could see a maximum of 473hz. So the capability that Motorola offers is installed.
Thanks
Click to expand...
Click to collapse
It varies on how fast you can drag your finger across the screen. I'm sure that if you drag it fast enough you'll hit 576Hz.
Username: Required said:
It varies on how fast you can drag your finger across the screen. I'm sure that if you drag it fast enough you'll hit 576Hz.
Click to expand...
Click to collapse
Yes, I was able to notice that. When I made a simple contact, the response barely reached 100hz, but if I made aggressive contacts, the response was quite high.
fulltronservice said:
Unfortunately I already did that and the maximum I see is 250hz. Where have the 576hz they said gone?
Click to expand...
Click to collapse
I just found out by experimenting Game Turbo:
1. Add your Game App/ Touch Tester App to game mode/turbo
2. Enable Auto Rotation mode (Portrait / Landscape mode)
3. Rotate ur Phone to Landscape even if the app doesnt support it
4. Touch the Screen while in Landscape and see the result Increases to Max Touch Rate
Follow what i said. I want to see the result.
Ty
cjlaysico said:
I just found out by experimenting Game Turbo:
1. Add your Game App/ Touch Tester App to game mode/turbo
2. Enable Auto Rotation mode (Portrait / Landscape mode)
3. Rotate ur Phone to Landscape even if the app doesnt support it
4. Touch the Screen while in Landscape and see the result Increases to Max Touch Rate
Follow what i said. I want to see the result.
Ty
Click to expand...
Click to collapse
Thanks for the tip man I was freaking out with my Xiaomi 11T Pro who supposedly have 480hz sampling rate screen and was just getting 250hz tops within checker apps, until I run them through Gaming Mode as you suggested with Pro mode enabled and YES the sampling rate wen above 500hz tops.
So the range is dynamic? Supposedly to save battery I guess?
Regardless thanks!
[Re-posting this here after I confirmed it work with the Pixel 7 as well]
To be clear, this is not the same as the developer option.
Enter the following ADB commands (you can also modify these values using the app SetEdit in the Play Store, no root required):
adb shell settings put system peak_refresh_rate 24.0
adb shell settings put system min_refresh_rate 24.0
The reason this works is because by assigning it a random and unsupported value, we are [kind of] breaking the refresh rate. As a result of which, the OS won’t be able to adjust this rate, and hence stick with the maximum available rate.
You can also enable the "Force Refresh Rate" in Developer Options. I tried it, but don't really care to keep DO enabled. Also you can enable "Show Refresh Rate" in DO. I did that also, and realized that with keeping it at 60(normal), and keeping "Smooth Display" on, the phone kicks it into 90 the moment you touch the screen. So forcing 90 100% of the time is a waste of battery in my opinion. Only when the phone is not touched for three seconds does it drop back to 60. Otherwise any use of the phone it stays at 90 normally.
bobbyphoenix said:
You can also enable the "Force Refresh Rate" in Developer Options. I tried it, but don't really care to keep DO enabled. Also you can enable "Show Refresh Rate" in DO. I did that also, and realized that with keeping it at 60(normal), and keeping "Smooth Display" on, the phone kicks it into 90 the moment you touch the screen. So forcing 90 100% of the time is a waste of battery in my opinion. Only when the phone is not touched for three seconds does it drop back to 60. Otherwise any use of the phone it stays at 90 normally.
Click to expand...
Click to collapse
Started my day today at 100% 7AM and am at 52% 11PM so I am happy. I can't stand Snapchat being 60.
Update on my observation. It may be a placebo effect, but knowing that it changes makes me see a slight stutter. Forcing 90 at all times "seems" much smoother, so I'm leaving it on also. Cheers!
this trick is irrelevant, you can do it in developer tool....
Vio281 said:
this trick is irrelevant, you can do it in developer tool....
Click to expand...
Click to collapse
The developer option does not force in many cases. In Snapchat when you swipe to the left and the camera is still initialized it stays at 60hz. Once the camera is not initialized it goes to 90hz. I believe it is the same in Instagram.
Jonnyswboy said:
The developer option does not force in many cases. In Snapchat when you swipe to the left and the camera is still initialized it stays at 60hz. Once the camera is not initialized it goes to 90hz. I believe it is the same in Instagram.
Click to expand...
Click to collapse
Jonnyswboy said:
The developer option does not force in many cases. In Snapchat when you swipe to the left and the camera is still initialized it stays at 60hz. Once the camera is not initialized it goes to 90hz. I believe it is the same in Instagram.
Click to expand...
Click to collapse
Has a fix been found for this cause I found this doesn't seem to be an issue at all on iPhone but incredibly frustrating on Android especially Snapchat.
lukeah02 said:
Has a fix been found for this cause I found this doesn't seem to be an issue at all on iPhone but incredibly frustrating on Android especially Snapchat.
Click to expand...
Click to collapse
My fix is in the original post. Has been working great for me.
Been using this for a while, but let's saym hypothetically if I wanted to restore it to default settings, which values do I need to put on the adb commands?
If I do those ADB commands and decide I want to not have them anymore, how would I revert?
To get your default values before doing the change, use:
Code:
adb shell settings get system peak_refresh_rate
and
Code:
adb shell settings get system min_refresh_rate
For me on stock firmware unrooted, peak_refresh_rate = null, and min_refresh_rate = 0.
Thanks for your fix! I was wondering why some apps were low hz.
heisenberg17 said:
Been using this for a while, but let's saym hypothetically if I wanted to restore it to default settings, which values do I need to put on the adb commands?
Click to expand...
Click to collapse
Get default values before doing the change:
adb shell settings get system peak_refresh_rate
adb shell settings get system min_refresh_rate
Default values (stock unrooted):
peak_refresh_rate = null
min_refresh_rate = 0
Thanks for your fix! I was wondering why some apps were low hz.
I've just got a Pixel 7 and thought I'd try this.
Observations, stock not rooted etc
Peak refresh rate = 90
min refresh rate = null
Applied the settings in post 1
and both come back as 24 when 'getting' peak/min rates from adb.
However, turning on show refresh rate in developer options show 90 when using the screen, but drops back to 60 if you leave it for a few seconds.
it only stays at 90 if you turn on Force peak refresh rate in Developer options.
This is only so far when messing about on the home screen, not tested in any apps etc, but it looks like these settings can't be fixed by setting a random number as post 1 implies
As a quick follow up, setting both peak and min to 90 does fix them, but seems a bit pointless as you can turn it on/off within developer settings.
This is not a bash at the OP, but maybe recent update have taken this 'feature' out
Does this survive a reboot?
xduox said:
Get default values before doing the change:
adb shell settings get system peak_refresh_rate
adb shell settings get system min_refresh_rate
Default values (stock unrooted):
peak_refresh_rate = null
min_refresh_rate = 0
Thanks for your fix! I was wondering why some apps were low hz.
Click to expand...
Click to collapse
Though the above might be a possible solution, here is the proper way to revert using ADB:
adb shell settings reset system peak_refresh_rate
To dig further into the possible System settings (amazing topic ^^)
adb shell settings list system
MrPeaski said:
seems a bit pointless as you can turn it on/off within developer settings.
This is not a bash at the OP, but maybe recent update have taken this 'feature' out
Click to expand...
Click to collapse
You can't force peak refresh rate in developer settings. It will still drop at times, like in Snapchat when the camera is accessed, on Google Maps, etc. It still automatically drops to 60hz despite the developer option being enabled.
And after updating to the Android 14 beta this workaround does not work anymore, and I am very frustrated that I am unable to truly force 90hz anymore.