.
kevinireland11 said:
The refresh rate must need some work done to it because when you enable force 120, the screen doesn't stutter when scrolling anymore.
Although might hit battery life a little moreView attachment 5468011
Click to expand...
Click to collapse
This isn't a revelation bro. People already know this. LTPO is still a very new technology and hasn't been perfected yet.
kevinireland11 said:
The refresh rate must need some work done to it because when you enable force 120, the screen doesn't stutter when scrolling anymore.
Although might hit battery life a little moreView attachment 5468011
Click to expand...
Click to collapse
Ah yes the oldest trick in the book
Screen refresh rate is controlled by several variables, 3 which I found are:
Code:
# getprop ro.surface_flinger.use_content_detection_for_refresh_rate
<true by default; you will need Magisk's resetprop to override it>
# settings get system min_refresh_rate
<0 by default; you can set e.g. to '60'>
# settings get system peak_refresh_rate
<60 or 120 depending on toggle 'Smooth display' in Settings>
When you use 'Force peak refresh rate' in developer options then:
Code:
# settings list system | grep refresh
min_refresh_rate=120.00001
Weird number by the way. Anyway that forces the driver into 120Hz continuously.
Burt Squirtz said:
This isn't a revelation bro. People already know this. LTPO is still a very new technology and hasn't been perfected yet.
Click to expand...
Click to collapse
There's a catch though,
It's for the people that didn't know, if "we all" new then I wouldn't have posted it
On my Pixel 6 Pro it always displays '60' if you turn on 'Show refresh rate', regardless if any of the other use/force smooth display/refresh rate options is set to true...
Is this the same for you?
HerrT said:
On my Pixel 6 Pro it always displays '60' if you turn on 'Show refresh rate', regardless if any of the other use/force smooth display/refresh rate options is set to true...
Is this the same for you?
Click to expand...
Click to collapse
Mine is 60, except when things are changing on the screen, then its 120.
96carboard said:
Mine is 60, except when things are changing on the screen, then its 120.
Click to expand...
Click to collapse
After a reboot mine is behaving the same (and as originally expected) now.
Thanks for the reply!
Related
Hey there,
Daki from www.androidkosmos.de published a short article that the resolution can be changed to 4k by default (so Kudos to you man). As it's in German and not exactly step-by-step, I felt like posting a short how-to.
Step 1: Turn on Developer Options.
- Settings -> About -> Click 5x on Build-Number
Step 2: Allow USB debugging
- Settings -> Developer Options -> USB Debugging [X]
Step 3: Open ADB, (always without the " ofc!)
- Type "adb devices", click on "allow request" on your phone
Step 4: Change Resolution and DPI
- Type "adb shell"
- Type "wm size 2160×3840"
- Type "wm density 807 (after a little tinkering, I found 721 to be the best DPI. Yea, really, 721)"
There is no information so far as to how battery life is affected!
Back to default:
Repeat steps 1-3
Step 4: Change Resolution and DPI (back to default)
- Type "adb shell"
- Type "wm size 1080×1920"
- Type "wm density 403"
Best
IlluX
Further to this, if you're a weirdo like me and want everything reset rather than a set value due to your own personal OCD, you can use "wm size reset && wm density reset" :good::fingers-crossed::silly:
Illux said:
Hey there,
Daki from www.androidkosmos.de published a short article that the resolution can be changed to 4k by default (so Kudos to you man). As it's in German and not exactly step-by-step, I felt like posting a short how-to.
Step 1: Turn on Developer Options.
- Settings -> About -> Click 5x on Build-Number
Step 2: Allow USB debugging
- Settings -> Developer Options -> USB Debugging [X]
Step 3: Open ADB, (always without the " ofc!)
- Type "adb devices", click on "allow request" on your phone
Step 4: Change Resolution and DPI
- Type "adb shell"
- Type "wm size 2160×3840"
- Type "wm density 807 (after a little tinkering, I found 721 to be the best DPI. Yea, really, 721)"
There is no information so far as to how battery life is affected!
Back to default:
Repeat steps 1-3
Step 4: Change Resolution and DPI (back to default)
- Type "adb shell"
- Type "wm size 1080×1920"
- Type "wm density 403"
Best
IlluX
Click to expand...
Click to collapse
Thanks, when I set the 4k res, I get the error message "bad resolution"... why?
Awesome!
will this work on Z5 Premium?
sev7en said:
Thanks, when I set the 4k res, I get the error message "bad resolution"... why?
Click to expand...
Click to collapse
No idea, typo maybe? Tested it back and forth, not a single issue to report.
sev7en said:
Thanks, when I set the 4k res, I get the error message "bad resolution"... why?
Click to expand...
Click to collapse
ytheekshana said:
will this work on Z5 Premium?
Click to expand...
Click to collapse
I don't have a Z5P so I can't guarantee but I'm quite confident it does.
Haha look at that. Nice and thanks for share
I also published on talk.sonymobile.com forum.
Illux said:
No idea, typo maybe? Tested it back and forth, not a single issue to report.
Click to expand...
Click to collapse
Morning! Yes, it was... I used * instead of "x", I need new glasses eheh
How's the battery for you guys? When I do this to my Z5P, the battery doesn't even last a few hours
jms.flynn said:
Further to this, if you're a weirdo like me and want everything reset rather than a set value due to your own personal OCD, you can use "wm size reset && wm density reset" :good::fingers-crossed::silly:
Click to expand...
Click to collapse
Thanks. I checked my default density before changing it with the command "wm density" which exported 420, not 403 like OP said .
Phat-T said:
How's the battery for you guys? When I do this to my Z5P, the battery doesn't even last a few hours
Click to expand...
Click to collapse
The draining is very poor, not an impact so remarkable. The issue is about the themes, e.g. in the Agree Bird I have now when I asnwer to a call, the dialer disappear and it becomes a nightmare eheh
the phone app is not working correctly after change to 4k. phone app force close if you try to make a call and dialer disappear
got the aame result did not see any different on battery anyway, i think it is just mock, the desity shown in cpu z is same. but resolution is making at 4k in cpu z. need to change back due to phone app force closing though
gpx said:
the phone app is not working correctly after change to 4k. phone app force close if you try to make a call and dialer disappear
Click to expand...
Click to collapse
I heard somewhere that the phone app will work properly if you use 1440x2560 resolution, not sure about DPI though. I think it was Z5 Premium thread.
aren't the ui supposed to be 4k unlike the z5 p? or did they changed it?
tommy96814 said:
aren't the ui supposed to be 4k unlike the z5 p? or did they changed it?
Click to expand...
Click to collapse
They said during CES or something similar that you would be able to change the resolution in settings, so you could run 4K all the time if you wanted to. But that isn't the case on the phone right now.
Either the people from Sony that made the claim had their information wrong or Sony changed their mind afterwards. Either way, it sucks that you can't control your resolution in the settings.
MiniDemonic said:
They said during CES or something similar that you would be able to change the resolution in settings, so you could run 4K all the time if you wanted to. But that isn't the case on the phone right now.
Either the people from Sony that made the claim had their information wrong or Sony changed their mind afterwards. Either way, it sucks that you can't control your resolution in the settings.
Click to expand...
Click to collapse
yes i do not know they give us independently, like s8 did. easily for them to control like that actually.
tanipat said:
yes i do not know they give us independently, like s8 did. easily for them to control like that actually.
Click to expand...
Click to collapse
Hopefully it comes in a future update, maybe there were some issues with certain apps in 4K. I wouldn't count on it happening but it's not completely off the table.
Has someone used this for a while and can tell us about eventually battery effects of this? Does the phone app force closes etc?
So we know the 120hz is only enabled for FHD+ and limited to 60hz on QHD, but there's been some talk from leaks leading up to today saying it may still be possible to get 120hz in QHD using a developer mode option, can anyone confirm this is still possible?
arvz said:
So we know the 120hz is only enabled for FHD+ and limited to 60hz on QHD, but there's been some talk from leaks leading up to today saying it may still be possible to get 120hz in QHD using a developer mode option, can anyone confirm this is still possible?
Click to expand...
Click to collapse
I'd like to know this as well. Hopefully you get an answer from someone who has knowledge within the phone. I pray if there isn't an option that XDA finds a way to do it through ADB like the force 90hz option on OnePlus 7 Pro.
hopefully that exists
I really hope we can Atleast do 90Hz on 1140p.,
arvz said:
So we know the 120hz is only enabled for FHD+ and limited to 60hz on QHD, but there's been some talk from leaks leading up to today saying it may still be possible to get 120hz in QHD using a developer mode option, can anyone confirm this is still possible?
Click to expand...
Click to collapse
Can you try this tasker profile.
Import this little profile here to tasker. You need to give tasker the permissions it asks for within adb please report back
https://taskernet.com/shares/?user=...WrgmW2Mlw=&id=Profile:Selective+120hz+Per+App
Kevtrejo37 said:
Can you try this tasker profile.
Import this little profile here to tasker. You need to give tasker the permissions it asks for within adb please report back
https://taskernet.com/shares/?user=...WrgmW2Mlw=&id=Profile:Selective+120hz+Per+App
Click to expand...
Click to collapse
Anyone tested ? Does this work ?
Thread title is a bit misleading
Hi guys,
Simply question, IT is possible to change refresh rate or software overclock display to more Hz?
Or any APPS on this?
Unlock 90hz or 120hz anything else?
Thanks for answer
:good:
Kasp3rsky said:
Hi guys,
Simply question, IT is possible to change refresh rate or software overclock display to more Hz?
Or any APPS on this?
Unlock 90hz or 120hz anything else?
Thanks for answer
:good:
Click to expand...
Click to collapse
nope , that app used for s20 not work for n10+ , i think n10+ locked to 60hz
Sent from my SM-N975F using Tapatalk
Kasp3rsky said:
Hi guys,
Simply question, IT is possible to change refresh rate or software overclock display to more Hz?
Or any APPS on this?
Unlock 90hz or 120hz anything else?
Thanks for answer
:good:
Click to expand...
Click to collapse
No, if it was the relevant option(s) would be visible and available to us on the phone.
Currently people are using activity launchers to run a menu option for the S20 that is hidden on the Note 10+. While it can be toggled it appears to not work at all on the Note 10+ due to hardware limitations.
scottusa2008 said:
No, if it was the relevant option(s) would be visible and available to us on the phone.
Currently people are using activity launchers to run a menu option for the S20 that is hidden on the Note 10+. While it can be toggled it appears to not work at all on the Note 10+ due to hardware limitations.
Click to expand...
Click to collapse
Do you have a link?
Reaper1337 said:
Do you have a link?
Click to expand...
Click to collapse
Hi,
https://forum.xda-developers.com/galaxy-note-10/how-to/toys-oneui-2-1-update-t4077297
Tried the activity launcher and I assure 100% note 10+ locked to 60hz...
I installed the app and applied the setting as well. Not so much as a placebo effect. Checked at testufo and can confirm only 60hz. Is there anything useful anyone has discovered in this app?
The Problem will be the drivers for the display
To achieve more than 60hz you would have to create a custom resolution and refresh rate
Effectively overclocking the display
Anyone ever checked what resolution and refresh rate the Note 10+ can actually use, by running the shell command “dumpsys display,” in adb?
According to this article the setting option was a mistake.
https://piunikaweb.com/2020/04/07/s...-120hz-refresh-rate-but-dont-get-too-excited/
by the fact the display was launched as purely 60hz it is probably a hardware limitation.
LCD/LED/other panels are manufactured to work at a maximum speed, it will be hardware controlled through the display chips, so unless you can swap out the controller chip and the panel is actually capable of altering the individual points at that speed you are likely never getting past 60hz. so unless the hardware was designed for 120hz and Samsung chose to just massively underclock the screen (but why would they do that when it would have been a good brag?) there is likely no way past 60hz as since the change from CRT the only way to overclock a screen is if the screen is shipped underclocked by the manufacturer.
so the reason it doesn't show up in the standard settings without extra steps should tell you this option being there is a mistake of them not removing the setting deep enough in the software.
If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
rickysidhu_ said:
If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
Click to expand...
Click to collapse
That's something I've been wondering how to do! kudos
rickysidhu_ said:
If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
Click to expand...
Click to collapse
Will this work for the older Pixel devices as well (such as my Pixel 4)? : o
Help The Peace said:
Will this work for the older Pixel devices as well (such as my Pixel 4)? : o
Click to expand...
Click to collapse
No reason why not looking at the command, give it a try
danw_oz said:
No reason why not looking at the command, give it a try
Click to expand...
Click to collapse
Sounds good. But will it also drain battery from then on? Or will it continually "charge" to keep it at 80%? And is your command an ADB command?
You can use this in Tasker with a "run shell" task when the device boots since this reverts to 100 if you ever reboot the device.
Does this command require root?
Other than prolonging the battery condition/longevity, is there another reason to set a charge limit?
Last question: The command stays in effect until reboot?
Thanks.
snovvman said:
Does this command require root?
Other than prolonging the battery condition/longevity, is there another reason to set a charge limit?
Last question: The command stays in effect until reboot?
Thanks.
Click to expand...
Click to collapse
I believe it does require a root, yes
I don't know any other benefit for limiting charge other than preserving the battery's long-term, overall health. Not allowing your battery to go too low or too high will help keep its maximum charge for a longer time
And yes, the setting will revert back to the default 100 after a reboot. I use Tasker to run the command on each boot, gotta love automation!
does limiting the charge affect the battery optimization algorithms?
thanks for this. if only every phone was this easy
rickysidhu_ said:
If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
Click to expand...
Click to collapse
Thank you!
For what it's worth, this works with the Battery Charge Limit [ROOT] app (XDA thread). Go into the app's settings, enable Configurable CTRL File Data, click Configure Control Data, click I Understand, paste "/sys/devices/platform/google,charger/charge_stop_level" (without quotes) in the Set Path to Desired File, and since this app expects you to set values for Enabled and Disabled, I set both to 75, since that's what I want my battery to charge up to.
If I start using an automation app like Tasker, then I can set it a different way, but I kinda like this app method anyway.
Edit:
Now I am using the Advanced Charging Controller (ACC) Magisk Module and the AccA app which is a front-end/GUI for configuring the module.
Forgive my ignorance I have not paid much attention to the forums over the last couple of years.
Is there a benefit to limiting the charge percent? is 90 the default recommendation?
dms76 said:
Forgive my ignorance I have not paid much attention to the forums over the last couple of years. Picked up a job where I can't slack and read ll day long.. LOL
Is there a benefit to limiting the charge percent? is 90 the default recommendation?
Click to expand...
Click to collapse
The point is to limit battery degradation. Tesla does it with their cars. Personally, I'd rather just have an alert to notify me and I use AccuBattery Pro for that. I rarely charge overnight but if I actually do, I let adaptive charging handle handle the slow charging.
nycdiplomat said:
You can use this in Tasker with a "run shell" task when the device boots since this reverts to 100 if you ever reboot the device.
Click to expand...
Click to collapse
i did that but it won't do anything. it still charges above my set value, so i was wondering.
what i did in tasker:
created a profile > event > system event > device boot
created a task > run shell > "echo 65 > /sys/devices/platform/google,charger/charge_stop_level"
i rebooted to make sure tasker was running (had battery optimization disabled on tasker), and tasker seems to run but it won't work. the "65" value was just set while i was testing it and since my phon was below 50% charge i did not want to wait that long so i started with 55, then 60 and so on. as i write this i'm waiting for it to hit 65% and hopefully stop charging. all i can think of is that i probably used the wron profile in tasker?
regards
roirraW edor ehT said:
Thank you!
For what it's worth, this works with the Battery Charge Limit [ROOT] app (XDA thread). Go into the app's settings, enable Configurable CTRL File Data, click Configure Control Data, click I Understand, paste "/sys/devices/platform/google,charger/charge_stop_level" (without quotes) in the Set Path to Desired File, and since this app expects you to set values for Enabled and Disabled, I set both to 75, since that's what I want my battery to charge up to.
If I start using an automation app like Tasker, then I can set it a different way, but I kinda like this app method anyway.
Click to expand...
Click to collapse
No problem!
Yeah for sure, that’s the beauty of android, there are several ways of going about things.
I use Tasker because that way it’s just one less app that I have on my phone. I like to have as many things inside of Tasker as possible to keep things organized and consolidated.
Although I’m currently back on iOS after being on Android for six years! I didn’t like the 6 Pro enough to keep it and I’m not going to get into details because there’s already a lot of hate threads for it - and I don’t want to add to that.
Let’s just say that I’ve been enjoying iOS more than I thought I would, especially considering I’ve been on android for so many years. So we’ll see what Google cooks up for the 7 series.
Anyways, back to topic, definitely going to miss Tasker for how much that can be done with it! The Shortcuts app on iOS is the closest thing to Tasker and it’s nowhere near as robust lol
rickysidhu_ said:
If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
Click to expand...
Click to collapse
does this work without root? i tried this using tasker but it did not work. how did u test it?
boxemall said:
does this work without root? i tried this using tasker but it did not work. how did u test it?
Click to expand...
Click to collapse
Yes, As far as root required.
boxemall said:
does this work without root? i tried this using tasker but it did not work. how did u test it?
Click to expand...
Click to collapse
You need root.
I just got one of these: https://chargie.org/
Seems to work well so far.
cmh714 said:
I just got one of these: https://chargie.org/
Seems to work well so far.
Click to expand...
Click to collapse
I have looked at them before but they seem very expensive for what they are, it is easier just to set a silent alarm for a few hours after you intend to get up.
Good day. Please can someone give advice - i got CN X80pro V2185A 12\256.
When i set screen refreshrate to smart switch i get only 60 and 120 real refresh rate via counter.
if i touch screen 120hz, after 3-4 sec it drops to 60 and never less.
i make full restore, update last firwware, but no changes.
MrDiegoSPB said:
Good day. Please can someone give advice - i got CN X80pro V2185A 12\256.
When i set screen refreshrate to smart switch i get only 60 and 120 real refresh rate via counter.
if i touch screen 120hz, after 3-4 sec it drops to 60 and never less.
i make full restore, update last firwware, but no changes.
Click to expand...
Click to collapse
You're in dark mode I bet. It doesn't work in dark mode it seems. Annoying
nope, not in dark
MrDiegoSPB said:
nope, not in dark
Click to expand...
Click to collapse
OH I see! That looks messed up. Funtouch os? I think that'll probably be fixed with an update cause you seem to be on all the correct options.
You're using auto brightness?
lawtq said:
OH I see! That looks messed up. Funtouch os? I think that'll probably be fixed with an update cause you seem to be on all the correct options.
You're using auto brightness?
Click to expand...
Click to collapse
yes auto brightness
Wish I could help, but I have the China dimensity 9000 version with no issues
asked vivo CN customer service, this is their refresh rate strategy for dark mode, so it wont be fixed, probably they have their reason behind for it
so its looks like
1) 1-120 wont work in dark mode theme
2) 1-120 wont work in low brightness
3) 10-120 work in 30%+ level
4) 1-120 work in 70% levels
If I set my refresh rate to 120hz should it stay there wherever I am or whatever I am doing woth my phone? Coz even in homescreen or using chrome it still goes down to 10.