Related
hi,is there anyway u can up the brightness level on these phones its up full at the moment but still could do with being a bit brighter
Afaik you have to wait for custom roms to get that up'd
Regards Dousan...
e: maybe its enough with a custom kernel...
Well the screen is not that great on our phone which is why we get around 2 days battery life with average use even I would like the screen to be brighter but it will greatly reduce battery life
Sent from my R800i using XDA Premium App
Have you tried installing dazzle? This app has some niffty display controls for maxing out the brightness.
Sent from my R800i using XDA App
it all comes down to the fact SE does not allow us to disable auto brightness so even if you "crank" the brightness you still have to live with auto brightness controlling the brightness while settings 1 2 3 on the power control widget appear to turn it up it is still being controlled to an extent..
FrAsErTaG said:
it all comes down to the fact SE does not allow us to disable auto brightness so even if you "crank" the brightness you still have to live with auto brightness controlling the brightness while settings 1 2 3 on the power control widget appear to turn it up it is still being controlled to an extent..
Click to expand...
Click to collapse
Will probably at least take a recompile of the kernel.
An answer to this question is in the Arc section, from SE:
A question on how to disable auto-brightness on Xperia PLAY.
Unfortunately, being able to do this from userspace might be non-functional in the released kernel for Play. The engineering team is aware and it is something they are looking into for future releases, can’t comment if it will be supported though yet.
However, if you’re building your own kernel, you can modify the file arch/arm/mach-msm/board-semc_zeus.c
What you’re looking for is the structure “as3676_platform_data”, where you can change the “als_connected = 1” to “als_connected = 0”.
Click to expand...
Click to collapse
I'm not sure how this would work, but there is a parameter
in /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/ "enable" which by default is set to "1"
Might want to test something like
echo "0" > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/enable
You need to be root to do this
NielDK said:
I'm not sure how this would work, but there is a parameter
in /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/ "enable" which by default is set to "1"
Might want to test something like
echo "0" > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/als/enable
You need to be root to do this
Click to expand...
Click to collapse
this works
waz000000 said:
this works
Click to expand...
Click to collapse
I think it will be set back on reboot, but it may work to add that line to /etc/hw_config.sh
yeah doesnt remain after reboot, will add later and see if it works.
It's not something that bothers me tbh.
waz000000 said:
yeah doesnt remain after reboot, will add later and see if it works.
It's not something that bothers me tbh.
Click to expand...
Click to collapse
Nor me.
The auto brightness is actually pretty awesome in all fairness. I am going to leave mine on even when a fix comes out for it.
News for brightnes controll ?
This guide is meant to help those who have rooted their phones and are now finding it slow, laggy, messy, etc.
I've been seeing a lot of posts repeating common problems that have been fixed by other members of the forums, so I'll compile a list of the most common bugs and fixes for them (the ones that can be fixed) in this guide so people can refer to it instead of swamping dev threads with the same questions over and over again. The quicker we can get through the common problems, the quicker we can get to fixing the ones we don't have solutions to so far.
Disclaimer: After installing the ENG bootloader, you are going to experience less battery life. There are things we can do to improve this, but nothing I have discovered so far will get you back to stock battery life... except re-installing stock ROM. Also standard disclaimer that all of the fixes here are done at your own risk. I am not responsible for any of these fixes breaking your phone.
Bug #1: Phone is laggy after rooting the phone/Battery is down the tank.
Fix: The phone is (partially) lagging because the ENG bootloader automatically sets the CPU governor to "Performance." While this is supposed to lock the CPU frequency at the maximum values, it does cause a lot of heat and possibly throttling. Additionally, the max core clocks are set to 1.593Ghz instead of their actual maximums. Not every CPU Tuner will allow you to set the big cores separately, so look around for one that does if you don't want to use Kernel Toolkit.
First, use Flashfire to flash one of two zips provided by psouza4 on our sister Verizon Galaxy S7 (Edge) threads.
1. Kernel fixes & tweaks V15
2. Kernel fixes, tweaks, & Debloater
You need only flash one of these two zips. One additionally debloats the system, one does not. Choose whichever suits your needs.
What the zips do:
Adds a rotate button to the native gallery app.
Adds a shortcut call button in the call log next to each logged call.
Adjusts several CPU tunables, which fixes phone lag and battery life issues.
Disables "No SIM" popup when no SIM card is present.
Disables roaming data by default.
Disables secure storage support, which fixes Wi-Fi passwords not saving issue.
Disables Verizon provisioning for Wi-Fi tethering/hotspot (will still use your data plan, of course).
Enables ADB to run as root by default.
Enables CPU idling/sleeping, which fixes phone heat issues.
Enables mock GPS locations.
Enables native call recording feature in the dialer.
Enables native Wi-Fi calling feature in the dialer.
Enables RIL power saving features.
Enables scheduled messages in the native messaging app.
Enables the camera during calls.
Enables unlimited contact merging.
Enables using the new 3GPP2 Profile ID (Verizon exclusive).
Fixes various 'searching for service' and other cellular network connectivity issues (SMS/MMS not working, calls not working, etc.)
Knox apps, drivers, and data are removed (fix+debloat version).
Prefers LTE network.
Raises the contact name length limit to 1,280 characters.
Raises the maximum SMS recipient limit from 10 to 90.
Remove nagging 'unauthorized actions' security notification (fix+debloat version).
Removes VoLTE icon.
Removes bloatware and/or apps that can be downloaded from the Play Store and don't need to live in /system (fix+debloat version):
Next, install a CPU Tuner utility like Kernel Toolkit, then change the governor from "Performance" to "Interactive." Also change the max CPU frequency of the little cores to 1.593Ghz and the big cores to 2.150Ghz while you're at it. Leave the cores at their default minimum frequency. This will go a long way to improving the speed of the phone. Also make sure you that have the new settings to apply on boot. Every kernel manager should have this option somewhere.
Note: Although the max frequency in the settings screen will drop to some number, as long as you can see the CPU ramp up to the new settings in the information screen, then everything is fine. You can test the max frequency by turning the screen off and then back on.
Then, install sEFix and set entropy to "Ultra."
Lastly, install L Speed and:
Code:
-Main Tweaks: Turn on
-Battery Improvement
-OOM Killer
-Kernel Tweaks - "Light"
-CPU Tuner: Turn on
-CPU Optimizer
-LNET Optimizer: Turn on
-Google DNS
-Faster Streaming
-Faster Dormancy
-IO Tweaks: Turn on
-IO Boost
-Partition Remount
-RAM Manager
-Balanced
-Seeder
-Moderate
Their individual effects can be read up on here.
Bug #2: Weird "hurricane" icon in the corner.
Fix: This is related to the imsservice.apk which controls the RCS icon and the VoLTE icon being displayed. Someone has a modified version of the Note 5 imsservice.apk with these removed. You can find the apk HERE in the OP's attachment. HOWEVER, you will push this to a different location than the location mentioned in the guide there. You have two choices, you can either push the apk via ADB from you computer or you can copy the file using a root file manager.
ADB Method (Assumes you know what you're doing. Don't copy the code verbatim if you don't know what the command is doing):
Code:
adb remount
adb push imsservice.apk /system/priv-app/imsservice/imsservice.apk
adb reboot
Root File Manager Method:
Transfer the imsservice.apk to your phone. Anywhere where you'll remember the location is fine. Open the file manager with root compatibility and copy the file to /system/priv-app/imsservice/ and overwrite the imsservice.apk already in the folder.
Set permissions of the file to 0644 or rw-r--r-- depending on your file manager. You can set permissions using most file managers.
Restart the phone.
I've included the stock PD8 imsservice.apk as an attachment below if anyone has issues with the modified one from the guide.
Bug #3: Notification warning that system has been modified.
Fix #1: Disable com.samsung.android.securitylogagent & com.tmobile.pr.adapt using your favorite package disabler. This will hide all notifications associated with this app as well as the root check that you might have encountered.
Fix #2: This fix requires Xposed. You can follow the instructions to install Xposed HERE.
Then install the Xposed module NotifyClean, activate the module, and reboot the phone. You will then use this app to block the notification under the package com.samsung.android.securitylogagent by clicking on the package so that it is highlighted red. The notification should disappear!
Note: This app can also be used to hide the icon for WiFi Calling if it's annoying you. You can still use the WiFi calling function while hiding the notification.
Bug #4: I keep losing root.
Fix #1: Secure boot/startup has caused the loss of root. So make sure you DO NOT SETUP the secure boot option when you're first setting up the phone or any time afterwards. This is the same option that forces users to type in/swipe in their password on a screen with a black background. This is not the normal type/swipe your password on your lockscreen after a boot.
Fix #2: Disable Security policy updates. I've also heard that people who leave this option on lose their root after a couple of reboots. You can find this setting under:
Settings > Lock screen and security > Other security settings > Security policy updates > Automatic updates (Turn this setting off).
Fix #3: Disable auto-updates for apps in Google Play Store. It's possible that SuperSU auto-updated, breaking root.
Fix #4: Disable automatic updates for the phone. I don't think these run anyways on modified software, but it can't hurt. You can disable the applications responsible for automatic updates using Titanium Backup, EZ Disabler, or any other package disabler you know of. The packages to disable are:
com.sec.android.soagent
com.wssyncmldm
com.samsung.firmware.nfc
com.samsung.android.firmware.tsp
Bug #5napchat: Unable to log into Snapchat.
Fix #1: This happens if you attempt to login to Snapchat after installing Xposed. Just make sure you login to Snapchat prior to installing Xposed. Done.
Fix #2: If you've already installed Xposed, you can:
-Do a clean install through ODIN, and re-root your phone, install and log into Snapchat, then install Xposed.
-Uninstall Xposed by flashing THIS through Flashfire, uninstalling the Xposed framework app, and clearing the data on your Snapchat app. Then login to Snapchat and re-install Xposed.
Bug #6: WiFi passwords aren't being saved
Fix: Use a root file manager like Solid Explorer and go to /system and open/edit build.prop. Scroll down or use the "find" function to search for ro.securestorage=true and change it from true to false (ro.securestorage=false). Save the file. Done!
If you guys have any more bugs that you run into, please feel free to post them here. Anyone who knows of any additional fixes to these bugs or solutions to any bugs that others post, also feel free to add them in the comments and I will compile them into this guide when I get a chance.
I've included the PD8 imsservice.apk below if you need it
Reserved
Reserved
I downloaded CPU scale and I dont see 1.5hz and 2.1ghz as options to switch too
thegameksk said:
I downloaded CPU scale and I dont see 1.5hz and 2.1ghz as options to switch too
Click to expand...
Click to collapse
Not every CPU Tuner utility will let you set the individual big.LITTLE cores separately. Try using the one recommended or look for another one that does allow it. Kernel Toolkit is the only one that I remember off the top of my head. I'll also make an edit in the post to avoid further confusion.
hey all, does anyone have or has experienced your incoming calls not being recieved? i have called myself and others also and it either rings until voicemail or it just goes straight to voicemail,
any ideas whats causing this?
thanks,
Great post! Unfortunately I'm having problems with smart view after rooting. Every time I try to screen mirror it works but it is extremely laggy making it unusable. This has only been an issue since root and I've tried mirroring to three different devices and it's the same with all of them. I followed the instructions in this thread to see if these tweaks would help but they didn't change my screen mirroring issue at all. Is anyone else out there experiencing this?
little help please.
Followed the guide for bugs 1 & 2 exactly as mentioned. Used the root manager method for bug #2. Now i keep getting this pop-up that the phone is not responding...Any solutions to get rid of this?
thanks
cris_epic said:
hey all, does anyone have or has experienced your incoming calls not being received? i have called myself and others also and it either rings until voicemail or it just goes straight to voicemail,
any ideas whats causing this?
thanks,
Click to expand...
Click to collapse
Just started for me too. Doesn't go straight to voice mail but i don't get calls and cant call out now. Seemed to happen right after i replaced the imsservice.apk and rebooted. The annoying hurricane icon is gone now, just at the expense of making and receiving calls lol.
Did you also happen to overwrite the imsservice.apk?
JKLIMES1 said:
Followed the guide for bugs 1 & 2 exactly as mentioned. Used the root manager method for bug #2. Now i keep getting this pop-up that the phone is not responding...Any solutions to get rid of this?
thanks
Click to expand...
Click to collapse
Looks like I forgot to mention changing permissions on the file after you copy it over. From there, the easiest way to restore it would probably be to adb push the file over since you don't need to reset permissions if you push through adb. This should correct the crashing and allow you to use your phone.
JKLIMES1 said:
Just started for me too. Doesn't go straight to voice mail but i don't get calls and cant call out now. Seemed to happen right after i replaced the imsservice.apk and rebooted. The annoying hurricane icon is gone now, just at the expense of making and receiving calls lol.
Did you also happen to overwrite the imsservice.apk?
Click to expand...
Click to collapse
Yeah I believe I replaced the imsservice.apk when I flashed the fixs and debloater zip thats been going around
Sent from my SM-G935T using XDA-Developers mobile app
Is this what you mean about the cores?
thegameksk said:
Is this what you mean about the cores?
Click to expand...
Click to collapse
Leave the min frequency of the cores at the minimum otherwise your cores will always be at max frequency which is something you definitely don't want.
h.nocturna said:
Looks like I forgot to mention changing permissions on the file after you copy it over. From there, the easiest way to restore it would probably be to adb push the file over since you don't need to reset permissions if you push through adb. This should correct the crashing and allow you to use your phone.
Click to expand...
Click to collapse
AWESOME!! changing the permissions did the job for me. Thanks.
h.nocturna said:
Leave the min frequency of the cores at the minimum otherwise your cores will always be at max frequency which is something you definitely don't want.
Click to expand...
Click to collapse
I switched the minimum to 307 and max 1593 for small cores. For big cores minimum 307 MHz and Maximum is 2150 mhz.
Its not letting me save these numbers. I had min set to 307 and when I left the screen and went back it jumped back up to 1593
cris_epic said:
Yeah I believe I replaced the imsservice.apk when I flashed the fixs and debloater zip thats been going around
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
Trying changing the permissions as mentioned, that worked perfect for me.
thegameksk said:
I switched the minimum to 307 and max 1593 for small cores. For big cores minimum 307 MHz and Maximum is 2150 mhz.
Its not letting me save these numbers. I had min set to 307 and when I left the screen and went back it jumped back up to 1593
Click to expand...
Click to collapse
If you look at the information menu, do you see the cores ramp up to the 2.150 Ghz we set? If it does, then the settings have been saved despite it not reflecting on the settings screen. You can force it to ramp up to max but turning the screen off and then turning it back on.
h.nocturna said:
If you look at the information menu, do you see the cores ramp up to the 2.150 Ghz we set? If it does, then the settings have been saved despite it not reflecting on the settings screen. You can force it to ramp up to max but turning the screen off and then turning it back on.
Click to expand...
Click to collapse
Yes all 2 cpus go to 1593 and 2 go to 2150. This happens for 2 seconds than all 4 go down to 307
thegameksk said:
Yes all 2 cpus go to 1593 and 2 go to 2150. This happens for 2 seconds than all 4 go down to 307
Click to expand...
Click to collapse
This is the expected behavior. This just means that they will clock up to the max when there is a high load, but then drop back down to the lowest frequency to save battery when there is nothing to be done. Everything is working as it should.
Thank you for your help. Does your phone run hot when gaming or charging? My charger also gets very very hot while charging.
thegameksk said:
Thank you for your help. Does your phone run hot when gaming or charging? My charger also gets very very hot while charging.
Click to expand...
Click to collapse
Mines was hot just with normal usage. I used every tip and fix that people suggested but it was still pretty slow and lagged if I had a game running and a couple of more apps running. Battery was OK though.
Hello guys,
As you know we are able to force 90hz for all apps. Not always it's a good idea because of :
- battery reason
- Google maps issues
- games which are not "high end" to avoid high battery usage (games like poker and so on does not need 90hz)
I wanted to ask some developers if they can create an application which can be configured themselve (black list for all apps which should not run in 90hz for example)
Thanks so.much (this would.be a reason to root if it requires root).
Put it on auto and let it manage itself or install gravitybox and you can change refresh rate from the quick-settings tile.
trapcoder666 said:
Put it on auto and let it manage itself or install gravitybox and you can change refresh rate from the quick-settings tile.
Click to expand...
Click to collapse
Really ?
If I root and use gravity box I can change it for every app?
manutoxic said:
Really ?
If I root and use gravity box I can change it for every app?
Click to expand...
Click to collapse
Well, you need to swipe down your quick settings and click the refresh rate tile. So, it's not automated but at least it makes things easier.
trapcoder666 said:
Well, you need to swipe down your quick settings and click the refresh rate tile. So, it's not automated but at least it makes things easier.
Click to expand...
Click to collapse
I Wish there would be an application to configure it app by apl
manutoxic said:
I Wish there would be an application to configure it app by apl
Click to expand...
Click to collapse
No but JOnePlus Tool lets you just turn it on and off with a single button on the fly. Just open the app and it's on the main screen there.
https://play.google.com/store/apps/details?id=net.jroot3d.joneplustools&hl=en_US
https://forum.xda-developers.com/showpost.php?p=79813631&postcount=78
I also use the forced 90hz all apps and the battery drain from this is seriously overblown. People scream about what they know nothing about. People need to educate themselves before making claims. They just say it kills battery without even trying it. I did nothing different, changed nothing and used my phone the same way I normally do and it made a difference of an increase of .7% battery drain with the screen on compared to 90hz on auto. It went from 6.3% drain pet hour to 7.0% per hour of screen on time. And since I've gotten days with 6.1% with it on forced 90hz all apps. So the difference isn't of and significance. Just try it and if you don't like it, switch it back. You'll find it makes no real difference when using it.
So there really should not be a need to blacklist 90hz all apps for just certain apps imo
Im sure someone could setup a tasker profile for this reason.
equlizer said:
Im sure someone could setup a tasker profile for this reason.
Click to expand...
Click to collapse
I did in 2 posts above that was linked, also its in the guides section.
I wish we could have possibility to decide to run some apps in 90hz and another in 60 hz.
For instance I wish KODI could run in 60hz.
netgar said:
I wish we could have possibility to decide to run some apps in 90hz and another in 60 hz.
For instance I wish KODI could run in 60hz.
Click to expand...
Click to collapse
here is my guide
If you need some help setting it up let me know. This will let u choose which apps use 60Hz and others will force 90Hz
Any possibility without buying tasker?
I switch to maps, display switched to 60, I turned off maps and display still remains 60. Didn't switch to 90.
Thats the way that should work? I need to manually switch to 90?
netgar said:
I switch to maps, display switched to 60, I turned off maps and display still remains 60. Didn't switch to 90.
Thats the way that should work? I need to manually switch to 90?
Click to expand...
Click to collapse
Not sure what your setup is exactly but if you're running the forced 90hz for all apps it is a bug that it shows as 60hz in the OOS setting under display. So if the tasker profile you are using switches from 90hz all apps and back to 60hz then your display setting will basically always show 60hz.
You can use this to test what your refresh rate is currently, either 60 or 90hz
https://www.testufo.com/
manutoxic said:
Any possibility without buying tasker?
Click to expand...
Click to collapse
we cannot provide you that info on here... google may be ur friend on how to go about doing that.
Eric214 said:
Not sure what your setup is exactly but if you're running the forced 90hz for all apps it is a bug that it shows as 60hz in the OOS setting under display. So if the tasker profile you are using switches from 90hz all apps and back to 60hz then your display setting will basically always show 60hz.
You can use this to test what your refresh rate is currently, either 60 or 90hz
https://www.testufo.com/
Click to expand...
Click to collapse
I don't use forsed 90hz all apps.
Ones I shut off maps I need to manually switch display back to 90hz.
no issues with maps at 90hz here. Strange as some do.
manutoxic said:
Any possibility without buying tasker?
Click to expand...
Click to collapse
So you want somebody to develop an app for your needs but won't pay for it?
I just found an app called Auto90. You can select which app you want to be auto/60 or 90hz. It's wonderful!
I ran diffchecker on the adb system settings output with force 90hz enabled and disabled, and found the setting that switches when you activate "force 90Hz" in the developer settings: "min_refresh_rate=90.0". If you're rooted you can set that with Tasker based on whatever conditions you want, using the shell command function. The code to activate it is "settings put global min_refresh_rate 90.0", and the code to deactivate is "settings delete global min_refresh_rate" (both need "use root" ticked). I've been testing having it triggered on my phone when I'm connected to my home wifi and ambient light is < 15. The home wifi condition is so I don't run into big battery drains when I'm out late at night, and I'm using ambient light rather than screen brightness because as someone pointed out in a Reddit thread, Smooth Display will still run under 75% screen brightness under certain ambient lighting conditions. So far, battery is definitely taking a hit, but it's not a big deal when I'm home and chargers are in easy reach.
tardis_42 said:
I ran diffchecker on the adb system settings output with force 90hz enabled and disabled, and found the setting that switches when you activate "force 90Hz" in the developer settings: "min_refresh_rate=90.0". If you're rooted you can set that with Tasker based on whatever conditions you want, using the shell command function. The code to activate it is "settings put global min_refresh_rate 90.0", and the code to deactivate is "settings delete global min_refresh_rate" (both need "use root" ticked). I've been testing having it triggered on my phone when I'm connected to my home wifi and ambient light is < 15. The home wifi condition is so I don't run into big battery drains when I'm out late at night, and I'm using ambient light rather than screen brightness because as someone pointed out in a Reddit thread, Smooth Display will still run under 75% screen brightness under certain ambient lighting conditions. So far, battery is definitely taking a hit, but it's not a big deal when I'm home and chargers are in easy reach.
Click to expand...
Click to collapse
This is handy, thank you! Quick question though, how do you run an adb system settings output to see the difference when you switch other settings?
TheBobMiller said:
This is handy, thank you! Quick question though, how do you run an adb system settings output to see the difference when you switch other settings?
Click to expand...
Click to collapse
Assuming you have adb running and connecting to your phone fine already, it's pretty easy. Enter adb shell, then run three commands: "settings list global", "settings list system", and "settings list secure". Open up diffchecker.com and copy the results from the shell into one side. Change whatever setting you're interested in on your phone, then run these commands again and copy the output into the other side of the diffchecker window. It'll show you anywhere the output has changed, and that should be your setting - although there might be a couple other differences flagged, eg I think system uptime is in there somewhere.
tardis_42 said:
Assuming you have adb running and connecting to your phone fine already, it's pretty easy. Enter adb shell, then run three commands: "settings list global", "settings list system", and "settings list secure". Open up diffchecker.com and copy the results from the shell into one side. Change whatever setting you're interested in on your phone, then run these commands again and copy the output into the other side of the diffchecker window. It'll show you anywhere the output has changed, and that should be your setting - although there might be a couple other differences flagged, eg I think system uptime is in there somewhere.
Click to expand...
Click to collapse
Thank you so much! I'm not sure how I never knew this but being an avid Tasker user, I should've known this by now. This is gonna really come in so useful for me! Thank you!
How did you find this script <min_refresh_rate> ? Do you max to lock the maximum fps would be <max_refresh_rate>?
Small change to the command; in Android 11 beta 2.5, you have to use "settings put system min_refresh_rate 90.0". Changing the global flag does nothing to the frame rate anymore but changing the system value can force 90hz, even if you have smooth display turned off.
Trixter313 said:
Small change to the command; in Android 11 beta 2.5, you have to use "settings put system min_refresh_rate 90.0". Changing the global flag does nothing to the frame rate anymore but changing the system value can force 90hz, even if you have smooth display turned off.
Click to expand...
Click to collapse
Thank you!
I have been looking for this since beta 2 came out ?
Has anyone figure method(s) to Force 120Hz display yet ? The dynamic refresh rate in both auto and 120Hz mode is now, the only thing on this phone bothers me so much.
EU rom (under display and brightness) has the option to choose : "Auto Select"; "120Hz" or "60Hz" in Screen Refresh Rate
BlueMeany68 said:
EU rom (under display and brightness) has the option to choose : "Auto Select"; "120Hz" or "60Hz" in Screen Refresh Rate
Click to expand...
Click to collapse
That's true, however, OP points out the fact that even at "120 Hz" setting the phone does some sort of battery saving stuff like optimizing the refresh rate based on applications used, battery level etc.
Which is not a bad thing, don't get me wrong - saving battery when the app (or user) don't benefit from 120 Hz setting is a pretty useful stuff. But then it should not be called "120 Hz" mode but rather "Light Adaptive mode" or something.
Btw Oneplus 8 Pro has even more aggressive approach to this, it literally switches to 60 Hz when you don't touch the screen, back to 120 Hz for two seconds when you touch the screen and then reverts to 60 Hz.
This is the reason why Oneplus 8 Pro is so good in all 120 Hz battery drain tests because, basically... it almost never runs it. This should not be called 120 Hz even though I fully appreciate the battery saving mechanism.
You can check here whether Oppo Find X2 Pro stays at 120 Hz (fps) or switches to 60 Hz right after you touch it like Oneplus: https://www.testufo.com
Killer007TV said:
That's true, however, OP points out the fact that even at "120 Hz" setting the phone does some sort of battery saving stuff like optimizing the refresh rate based on applications used, battery level etc.
Which is not a bad thing, don't get me wrong - saving battery when the app (or user) don't benefit from 120 Hz setting is a pretty useful stuff. But then it should not be called "120 Hz" mode but rather "Light Adaptive mode" or something.
Btw Oneplus 8 Pro has even more aggressive approach to this, it literally switches to 60 Hz when you don't touch the screen, back to 120 Hz for two seconds when you touch the screen and then reverts to 60 Hz.
This is the reason why Oneplus 8 Pro is so good in all 120 Hz battery drain tests because, basically... it almost never runs it. This should not be called 120 Hz even though I fully appreciate the battery saving mechanism.
You can check here whether Oppo Find X2 Pro stays at 120 Hz (fps) or switches to 60 Hz right after you touch it like Oneplus: https://www.testufo.com
Click to expand...
Click to collapse
Thanks for clarifying my point. In addition, OnePlus's high refresh rate displays can be forced to run at the constant value via ADB method but I have no clue for an OPPO's. I don't understand that why OPPO provides both 120Hz and auto refresh rate options but perform exactly the same.
MaKuRoZuMK2 said:
Thanks for clarifying my point. In addition, OnePlus's high refresh rate displays can be forced to run at the constant value via ADB method but I have no clue for an OPPO's. I don't understand that why OPPO provides both 120Hz and auto refresh rate options but perform exactly the same.
Click to expand...
Click to collapse
Sorry if I misunderstood. I've used the website suggested and my x2 pro remains at 118-120hz throughout ?
BlueMeany68 said:
Sorry if I misunderstood. I've used the website suggested and my x2 pro remains at 118-120hz throughout ?
Click to expand...
Click to collapse
Try it on browser like Microsoft Edge or Chrome Dev. Those browsers are limited at 60Hz while I can force run my OnePlus 8's at 90Hz all time via ADB.
MaKuRoZuMK2 said:
Has anyone figure method(s) to Force 120Hz display yet ? The dynamic refresh rate in both auto and 120Hz mode is now, the only thing on this phone bothers me so much.
Click to expand...
Click to collapse
I try something via adb
adb shell settings list secure
And I found this
coloros_screen_refresh_rate=3
3 = 120hz
2=60hz
0=Auto
But I cant put any number because android.permission.WRITE_SECURE_SETTINGS not granted
Maybe, just maybe, if you can put it to another number ( like 1 or 4 ), you can force 120hz on Oppo Find X2/X2Pro
BIBUBO BCJ said:
I try something via adb
adb shell settings list secure
And I found this
coloros_screen_refresh_rate=3
3 = 120hz
2=60hz
0=Auto
But I cant put any number because android.permission.WRITE_SECURE_SETTINGS not granted
Maybe, just maybe, if you can put it to another number ( like 1 or 4 ), you can force 120hz on Oppo Find X2/X2Pro
Click to expand...
Click to collapse
Tried this, was able to put both 1 and 4 and unfortunately, it's not forced at 120Hz. Now it's the dead end haha.
MaKuRoZuMK2 said:
Tried this, was able to put both 1 and 4 and unfortunately, it's not forced at 120Hz. Now it's the dead end haha.
Click to expand...
Click to collapse
ps. 1 is fake 90Hz mode and I have no idea with 4 and beyond.
ps.2 you have to disable permission monitoring in dev options first in order to set those settings.
MaKuRoZuMK2 said:
ps. 1 is fake 90Hz mode and I have no idea with 4 and beyond.
ps.2 you have to disable permission monitoring in dev options first in order to set those settings.
Click to expand...
Click to collapse
Oh I really forgot that option :cyclops:
BTW, There's some command like auto_switch and frozen_time, while Find X2/X2 Pro are using an adaptive 120hz, so any ideas ?
BIBUBO BCJ said:
Oh I really forgot that option :cyclops:
BTW, There's some command like auto_switch and frozen_time, while Find X2/X2 Pro are using an adaptive 120hz, so any ideas ?
Click to expand...
Click to collapse
Will try that as soon as I can
Sad that a 120hz phone only runs 120hz in a few apps, my Moto edge is 90hz in almost every app as I can see, Razer phone was 120hz in every app or you could force an app to run 120hz if it wasn't already, sad
If you want 120Hz in more apps you have to enable O1 Ultra Vision on 120Hz. 1080p only though.
That will make apps like IG smoother and YT in 120Hz.
Jordytjes said:
If you want 120Hz in more apps you have to enable O1 Ultra Vision on 120Hz. 1080p only though.
That will make apps like IG smoother and YT in 120Hz.
Click to expand...
Click to collapse
And I have to sacrifice that 2K resolution on my display
Working around for those options
BIBUBO BCJ said:
Oh I really forgot that option :cyclops:
BTW, There's some command like auto_switch and frozen_time, while Find X2/X2 Pro are using an adaptive 120hz, so any ideas ?
Click to expand...
Click to collapse
Update, I tried to config those two commands with no success
hope to run 120hz every app
Most apps are not optimized for running at 120hz yet, it's down to individual apps, when you set it to auto only the user interface and oppos apps run at 120 but all other apps run at 60, basically some apps do some apps don't , not oppos fault
---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------
Jordytjes said:
If you want 120Hz in more apps you have to enable O1 Ultra Vision on 120Hz. 1080p only though.
That will make apps like IG smoother and YT in 120Hz.
Click to expand...
Click to collapse
The ultra vision only adds frames on to the video that your playing that's all, doesn't smooth out the actual app
kevinireland11 said:
Most apps are not optimized for running at 120hz yet, it's down to individual apps, when you set it to auto only the user interface and oppos apps run at 120 but all other apps run at 60, basically some apps do some apps don't , not oppos fault
---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------
The ultra vision only adds frames on to the video that your playing that's all, doesn't smooth out the actual app
Click to expand...
Click to collapse
That is not true. YT is normally only 60Hz to save battery for example. With O1 it has to be on 120Hz as the actual video is also interpolated to 120Hz. Try it out for your self.
We mean 120hz scrolling/animations within an app, not video playback
For_itembine said:
We mean 120hz scrolling/animations within an app, not video playback
Click to expand...
Click to collapse
+1