It has been recently looked at and i think it's pretty mature already.
The idea is that most of us have had to rely on third party apps, such as lux auto brightness, to be able to control this feature, because the built in was not properly coded or adjusted.
I want to open this thread to ask for the people's experiences: which configuration are they using and if we can really kiss lux goodbye for once.
Not that I am unhappy with this software, but I don't like using external apps when the functionality is integrated (thus saving resources, etc, etc)
Thanks for your impressions and i hope this thread is helpful.
Sent from my GT-I9100 using Tapatalk 2
There's a fair amount of discussion on this in the CM9 thread. Anyway, the HAL now reports lux values from the sensor in values other than powers of 10 so I'm fairly sure it will work. There is still some debate on what the default brightness levels should be in the auto brightness settings but this is all customisable.
Never used lux myself but surely it can't have worked any better than the closed source HAL did because no matter what averaging it does on the data limiting to powers of 10 severely restricts the quality results you can get?
Thanks for the reply.
I know there is some info in the CM9 nightly thread but it kind of gets messed up and buried... That's why I wanted to isolate and study the case here....
Which would be the correct configurations? Or we can just enable it and leave it by default?
Cheers
Sent from my GT-I9100 using Tapatalk 2
Well I've seen NOWE has done a lot of testing with the custom levels as only certain intervals actually result in a noticeable brightness change.
You can search for his posts in the thread: http://forum.xda-developers.com/search.php?searchid=44763856
I'm using default levels at the minute with averaging and a 400 lux reset threshold and 10 second averaging window. Also, I have "Allow light decrease" on and a 50% decrease hysteresis. These are settings I picked up from another user in the thread.
I'm hoping if the custom levels (NOWE or otherwise) are better than the ones currently in the build then they'll get pushed to source and I'll get them that way..
Glad to see this thread opened up as this issue is honestly the only thing keeping me from using cm9 now. The big issue for me is the 10 second window the lux values are being refreshed at. Compared to the default 5 seconds on a Sammy rom it feels like it takes an eternity to register changes in light conditions.
This honestly doesn't seem like it would be that hard to fix, so why is nobody talking about it? Now that the sensors are functioning properly the only thing that needs changed for perfect auto brightness is for the sensor refresh rate to be changed from 10 seconds to 5.
Test it yourself, open the custom auto brightness levels window and watch the sensor values change. Start in a bright area and put your thumb over the sensor. You can count to 10 before any change occurs.
Light sensor levels
I want as many users as possible to test these settings.
If I get positive feedback, I'll go to the developer thread and ask them to make it the default settings.
These settings are very different from the current default settings and will probably cause higher energy consumption.
But for me they are the best settings I ever tried.
Code:
Lower Screen
0 15
24 15
48 40
104 55
186 70
256 80
340 90
437 100
550 110
677 120
821 130
980 140
1157 150
1351 160
1562 170
1792 180
2040 190
2308 200
2594 210
2901 220
3227 230
3574 240
3942 250
6106 255
Some remarks:
The second 15 should be 30, but 30 is mapped to 40 ... Confused?
Look here: https://github.com/CyanogenMod/andr.../blob/ics/drivers/video/samsung/ld9040.c#L309
The values 15, 55 and 80 are redundant. (1...29=GAMMA_30CD, 30...69=GAMMA_40CD, 70...89=GAMMA_70CD)
Entropy512 said that it is difficult to make more steps, but I sill have the slight hope that some day we will have these steps.
(GAMMA_15CD, GAMMA_55CD and GAMMA_80CD or something like that)
So atm the brightness jumps a little bit in the lower range because the steps are too big.
NOWE said:
I want as many users as possible to test these settings.
If I get positive feedback, I'll go to the developer thread and ask them to make it the default settings.
These settings are very different from the current default settings and will probably cause higher energy consumption.
But for me they are the best settings I ever tried.
Code:
Lower Screen
0 15
24 15
48 40
104 55
186 70
256 80
340 90
437 100
550 110
677 120
821 130
980 140
1157 150
1351 160
1562 170
1792 180
2040 190
2308 200
2594 210
2901 220
3227 230
3574 240
3942 250
6106 255
Some remarks:
The second 15 should be 30, but 30 is mapped to 40 ... Confused?
Look here: https://github.com/CyanogenMod/andr.../blob/ics/drivers/video/samsung/ld9040.c#L309
The values 15, 55 and 80 are redundant. (1...29=GAMMA_30CD, 30...69=GAMMA_40CD, 70...89=GAMMA_70CD)
Entropy512 said that it is difficult to make more steps, but I sill have the slight hope that some day we will have these steps.
(GAMMA_15CD, GAMMA_55CD and GAMMA_80CD or something like that)
So atm the brightness jumps a little bit in the lower range because the steps are too big.
Click to expand...
Click to collapse
Ill test. I think having 6000 at 255 is a good idea. Outdoors in the sun you deffo need full brightness, its really horrible to see sometimes!
mertin said:
Test it yourself, open the custom auto brightness levels window and watch the sensor values change. Start in a bright area and put your thumb over the sensor. You can count to 10 before any change occurs.
Click to expand...
Click to collapse
Change the Sample Interval and Window (not sure how these are called in English, I use Dutch) and you can easily see that the sensor is reacting faster than 10 seconds.
Ok, glad I'm not the only one with this issue running around my mind.
So, let's test that values and see if we can report them as ok
Thank you guys.
Sent from my GT-I9100 using Tapatalk 2
CRXed said:
Change the Sample Interval and Window (not sure how these are called in English, I use Dutch) and you can easily see that the sensor is reacting faster than 10 seconds.
Click to expand...
Click to collapse
This is a solution I've seen people throwing around but in fact it only makes the screen adjust even slower.
By adding a filter you are essentially averaging the lux levels being reported and smoothing the gap between jumps. Adding a filter does not effect how often the sensor is reporting data. But by smoothing over the jumps from say, moving from a dark room to outside, it makes the screen brighten gradually rather than going straight to max brightness in one jarring step.
I may have exaggerated slightly by saying 10 seconds. Its more like 7-8. But no fiddling with filter settings is going to change that the light sensor is not reporting data frequently enough. Or am I the only one who feels it is too slow? It drives me nuts and is the sole reason I'm sticking with Sammy roms atm.
mertin said:
This is a solution I've seen people throwing around but in fact it only makes the screen adjust even slower.
By adding a filter you are essentially averaging the lux levels being reported and smoothing the gap between jumps. Adding a filter does not effect how often the sensor is reporting data. But by smoothing over the jumps from say, moving from a dark room to outside, it makes the screen brighten gradually rather than going straight to max brightness in one jarring step.
I may have exaggerated slightly by saying 10 seconds. Its more like 7-8. But no fiddling with filter settings is going to change that the light sensor is not reporting data frequently enough. Or am I the only one who feels it is too slow? It drives me nuts and is the sole reason I'm sticking with Sammy roms atm.
Click to expand...
Click to collapse
Ok I have to agree with you, I am now beginning to understand how this whole light sensor/filtering works.
For example:
W/out filter 20 ------------ 80
With filter: 20 --35 -- 55 -- 80
It is taking the same amount of time to go from 20 to 80, only filtering will make the transition smoother, not faster.
Related
Please add the option of modifying auto-brightness levels, like CM 6.1. I suppose that it would require a kernel modification + an app to do this through gui.
Thanks.
What can CM do? I've been thinking it would be nice to be able to modify the min and max, and maybe the curve.
Thread moved to General.
Noxious Ninja said:
What can CM do? I've been thinking it would be nice to be able to modify the min and max, and maybe the curve.
Click to expand...
Click to collapse
It allows one to arbitrarily edit a table of sensor output vs brightness/button brightness.
It's really nifty.
CM6.1 reports these sensor values:
10, 160, 225, 320, 640, 1280, 2600, 10240
10-160 is in dimly lit indoors, 320-640-1280, in moderately to brightly lit indoors, and the rest is outside.
So I set those to brightness something like 50,60,70,80, 110, 140, 180, 255. A it was perfect to my eye. Not too bright, not too dim.
Didn't ever have to mess with brightness after that.
I'd really like to hear from developers like Netarchy and King, as well as from regular users - if they would like that option.
I would love to see this.
I always feel the auto-sensor tends to be too bright, and never adjusts the screen low enough inside.
rdwing said:
I would love to see this.
I always feel the auto-sensor tends to be too bright, and never adjusts the screen low enough inside.
Click to expand...
Click to collapse
That's exactly what I think. Plus, the brightness is not at maximum in direct sunlight (although that might be a safety feature).
Mine always send to bright, or it won't get bright when I go into a bright area until I sleep and wake it. :|
Sent from my EVO 4Gizzle.
+1 on this. So motivated that I searched for this thread....
Any news?
-----------
The stock auto-brightness is way too bright in completely darkness. This is one of the things I had on my list nearly since the beginning. Nobody else seemed to care.
http://forum.xda-developers.com/showthread.php?t=716547
An article showing how useless auto-brightness is:
http://gizmodo.com/5673444/why-exis...d-brightness-controls-are-effectively-useless
Do people not notice this or do they just not care?
Pretty sure people have given up on this. It's taken me three days of Google searching to find this thread so people probably don't know where to turn.
The lack of adjustments to the auto brightness values is extremely annoying. Even my old Windows mobile 6 phones had this ability.
AdamN said:
Pretty sure people have given up on this. It's taken me three days of Google searching to find this thread so people probably don't know where to turn.
The lack of adjustments to the auto brightness values is extremely annoying. Even my old Windows mobile 6 phones had this ability.
Click to expand...
Click to collapse
There was an application for WM I used to use on my Mogul, cant remember what it was called but it allowed you to calibrate the auto brightness levels. Anyone know what I'm talking about, or if there's an Android version?
This can be done with Tasker in the Market. Its a powerful app and there was a thread a while back about this exact thing. I don't remember what it was called, but I posted in it, so you could browse my posts from a month or so ago.
Hey... This thing makes phone calls too!
I want to change my auto-brightness sensitivity.
Im not talking about manualy changing brightness. I still want my phone to use sensor in order to regulate brightness, but i want every level to be a little bit brighter overall.
That's an coincidence. I was just searching the forum to see if a similar question has been asked... I've noticed varying min / max brightness levels on a variety of builds and I was wondering if there was something I could tweak to change those values (my goal is to get zero to represent something akin to "very dim" (not off), as the builds I've used over the last couple of months have been oh so bright.
Anyone know or point us to a resource that might tell us?
tomj777 said:
That's an coincidence. I was just searching the forum to see if a similar question has been asked... I've noticed varying min / max brightness levels on a variety of builds and I was wondering if there was something I could tweak to change those values (my goal is to get zero to represent something akin to "very dim" (not off), as the builds I've used over the last couple of months have been oh so bright.
Anyone know or point us to a resource that might tell us?
Click to expand...
Click to collapse
We have same problem and i havent seen anyone talking about this. I also noticed its different from build to build. And my latest problem is brightness is too low on recent build im using.
Any help would be appriciated from anyone.
Only thing I can tell you is CM6.1 based builds have those features built in, but I'm not aware of ways to do it for all builds.
JDMS has those features built in as well.
I wonder if it really is auto-brightness or just a kind of work-around. Looking at the ambient light sensor with the app GPS-Status, there are only two values: 10 LUX if darkness is around, and 160 LUX if any light hits the sensor. It seems not really precise...
I've noticed kernels with the 65fps mod have a bug where the colors washout after turning the screen off then on the first time after booting.
Here's how to test it. First go to a dark room and put the screen brightness on a low setting with the power control widget. Second reboot your phone and go to the settings page, don't let the screen go off. Then look at the dark grey background and take a mental picture. Finally turn off then on the screen and look again at the background, it looks washed out and a lighter grey.
Can anyone confirm this? thanks.
Sent from my Nexus S using xda premium
its not a bug. your seeing a difference in the screen frequency. the normal screen frequency is 56Hz, to get 65fps the frequency is changed to 65Hz. those kernels that allow 65fps still boot up at 56Hz then change to 65Hz after the screen is turned off for a few seconds.
simms22 said:
its not a bug. your seeing a difference in the screen frequency. the normal screen frequency is 56Hz, to get 65fps the frequency is changed to 65Hz. those kernels that allow 65fps still boot up at 56Hz then change to 65Hz after the screen is turned off for a few seconds.
Click to expand...
Click to collapse
Oh OK, that makes sense.
To me it's not worth having the 9fps boost at the cost of having the colors washout. I don't think it's even noticeably unless you run quadrant benchmark and see the 65fps at the bottom of the planets test.
Sent from my Nexus S using xda premium
reddv1 said:
Oh OK, that makes sense.
To me it's not worth having the 9fps boost at the cost of having the colors washout. I don't think it's even noticeably unless you run quadrant benchmark and see the 65fps at the bottom of the planets test.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
generally the fps difference isnt noticeable unless its on a high fps game. but its not always better to have the higher fps, sometimes youll even notice "skips" at 65fps, depending on how the game was written. but there are a few(not many at all) games/apps that i have noticed a difference, for the better, with more fps. but the colors dont actually wash out, thats the normal colors before the color drivers kick in. you just dont notice it at the normal fps.
simms22 said:
its not a bug. your seeing a difference in the screen frequency. the normal screen frequency is 56Hz, to get 65fps the frequency is changed to 65Hz. those kernels that allow 65fps still boot up at 56Hz then change to 65Hz after the screen is turned off for a few seconds.
Click to expand...
Click to collapse
The phone actually boots at 50Hz then switches to 56Hz or 65Hz as specified.
The washing out is why I tune the gamma to be punchy.
pay close attention, you will notice it at 56Hz too .
this is more a "not 50Hz bug".
lowering your Hz may allow you to keep vsync longer , but if not, you get hit with 25fps spots in games.
with 65, you will get "33"fps spots.
hope this helps.
morfic said:
The phone actually boots at 50Hz then switches to 56Hz or 65Hz as specified.
The washing out is why I tune the gamma to be punchy.
pay close attention, you will notice it at 56Hz too .
this is more a "not 50Hz bug".
lowering your Hz may allow you to keep vsync longer , but if not, you get hit with 25fps spots in games.
with 65, you will get "33"fps spots.
hope this helps.
Click to expand...
Click to collapse
there you go.. thats why i emailed you, i wasnt a 100% sure my memory was correct. but i knew it wasnt a bug for sure
morfic said:
The phone actually boots at 50Hz then switches to 56Hz or 65Hz as specified.
The washing out is why I tune the gamma to be punchy.
pay close attention, you will notice it at 56Hz too .
this is more a "not 50Hz bug".
lowering your Hz may allow you to keep vsync longer , but if not, you get hit with 25fps spots in games.
with 65, you will get "33"fps spots.
hope this helps.
Click to expand...
Click to collapse
That helps a lot, I can notice there's also is washing out at 56fps.
So how would you go about changing the fps to 50? I know in mach-herring.c setting the freq to 60 gives you 56fps and 72 gives you 65fps.
Sent from my Nexus S using xda premium
Ok, so I have spent the last few days tweaking the auto brightness settings.
My goal was to have the screen at the dimmest level at just about all lighting conditions, and to not have to strain to see things on the screen. In doing so I also altered settings to the sensor filter and scan timing to make it a small bit snapper. I needed to do this because sometimes I unlocked the phone to a screen so dark I could not tell it was on, and it took too long to adjust. Now it is pretty snappy. I took all my samples from many light situations, however there are situations where you may be directly under a light and at a angle where you have glare. I made no compensation for glare, and find no need to as it's very rare for me.
My goals were power savings and usability. I don't care about colors. if I want better color and I'm going to be using in a dark room I'll turn auto off for a bit. But I honestly don't find them that bad and like a dim screen in bed at night..
display Settings/ custom backlight settings.
Window length: 5sec
Reset threshold 400Lux
Sample interval 2sec
Screen dim level 1
edit other levels: -> see pictures
This is good stuff. I've never been able to tolerate auto-brightness, but I may give it another go. Thanks for sharing your tweaks.
jawman27 said:
This is good stuff. I've never been able to tolerate auto-brightness, but I may give it another go. Thanks for sharing your tweaks.
Click to expand...
Click to collapse
No problem. I'm not into coding at all. So when i find something that's on my level to modify i like to give a little back to the community.. Feel free everyone to post tweaks if you find some.. im still going to tweak the high levels, but have not had sunny days to get some good tests
Sent from my SCH-I500 using xda premium
these settings have performed rather well for me the past day or two. including in bright sunlight and dark bedrooms.
Sent from my SCH-I500 using Tapatalk 2
I'm finally been able to use my phone in a dark bedroom with these settings. Its visible enough outdoors too, and when I need some life in the colors I just turn up brightness manually. Thanks for this
sageDieu said:
these settings have performed rather well for me the past day or two. including in bright sunlight and dark bedrooms.
Click to expand...
Click to collapse
I second this. I've been on these settings for a few days now, and I haven't had to touch the manual settings. I think it's safe to say I'm an auto brightness guy now.
I still use manual when I'm indoors like in school where I just leave it all the way down because lighting is consistent, but I leave auto on the rest of the time.
Sent from my SCH-I500 using Tapatalk 2
Been using these setting for the past few days and they are performing great. The brightness seems to almost always be adequate for the lighting conditions. Thanks
neh4pres said:
edit other levels: -> see pictures
Click to expand...
Click to collapse
Neh4pres, at the top of your screen shots it shows:
Sensor (filtered/raw): 6/5
Screen: 4
Buttons: 255
After applying your settings, my phone shows -1/-1, disabled, -1 for those same settings, but I don't see any way to change them. Is there something I'm missing?
That's a great setting for autobrightness. But i think its not good for battery life.. too many levels will cause the system works hard for changing the display. Im currently on 7 levels, it gives me a great battery life. I'll try this and report, maybe my thought was wrong...
Sent from my SGH-I897 using XDA
Anthony2816 said:
Neh4pres, at the top of your screen shots it shows:
Sensor (filtered/raw): 6/5
Screen: 4
Buttons: 255
After applying your settings, my phone shows -1/-1, disabled, -1 for those same settings, but I don't see any way to change them. Is there something I'm missing?
Click to expand...
Click to collapse
Those are not settings, those are a read out of values of the sensor. What you need to adjust is the grey boxes... And your readings of -1 simply means your auto brightness is turned off.
Sent from my SCH-I500 using xda premium
shuyin1102 said:
That's a great setting for autobrightness. But i think its not good for battery life.. too many levels will cause the system works hard for changing the display. Im currently on 7 levels, it gives me a great battery life. I'll try this and report, maybe my thought was wrong...
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
You could have a thousand levels and it would not make a difference.
What would make a miniscule difference is sampling rate.. But you turn that up to high and your going to start feeling very impatient when light around you changes and your screen takes forever to reflect the changes.
And you won't be saving much of anything by doing do.
Example:
Walk indoors from the bright outdoors, your screen takes 10 seconds to turn down from max brightness. You just wasted more battery with your screen in those 10 seconds than you were trying to save by turning sampling time up.
Our screen is our biggest battery killer
Sent from my SCH-I500 using xda premium
I still get about two days of life on the stock battery with these settings. Like neh4pres said, the screen is the real killer. There are also a lot of other tips and tricks out there to get the most out of battery life. In the end, I can't imagine my sampling rate is making any significant difference, and I love watching the screen quickly and smoothly ramp up when I step outside.
I just tried these values....its too dark for me but I like the consistency. I would like to try some slightly brighter values but I am not sure how this works. Can anyone give me some suggestions ?
retareq said:
I just tried these values....its too dark for me but I like the consistency. I would like to try some slightly brighter values but I am not sure how this works. Can anyone give me some suggestions ?
Click to expand...
Click to collapse
At the top of the screen where you start the settings it shows what light level your on at that second. if it's to dark at that moment adjust the corresponding level and hit apply to see the difference.. Or. Sense i have a pretty good ratio setup, just and 1 or 2 to each level for everything below 100
Sent from my SCH-I500 using xda premium
Ok using the values from the OP, currently I am on Screen 11 and its a little too dim for me. What value do I change now? If I unlock screen its on #9 and dim as well..
It's not that bad really just after unlocking there is a heavy blue/purplish tint which goes away in few seconds as the screen brightens but if I could keep it like this only slightly brighter that would work. I don't really know which value I'm supposed to change..
In the meantime I found a nice compromise, I'm using:
Window length: 5sec
Reset threshold 400Lux
Sample interval 2sec
Screen Dim Level @ 20(default)
With the default levels and it seems to be working well so far. I'll know later tonight when I'm listening to beats in the dark.
retareq said:
Ok using the values from the OP, currently I am on Screen 11 and its a little too dim for me. What value do I change now? If I unlock screen its on #9 and dim as well..
It's not that bad really just after unlocking there is a heavy blue/purplish tint which goes away in few seconds as the screen brightens but if I could keep it like this only slightly brighter that would work. I don't really know which value I'm supposed to change..
In the meantime I found a nice compromise, I'm using:
Window length: 5sec
Reset threshold 400Lux
Sample interval 2sec
Screen Dim Level @ 20(default)
With the default levels and it seems to be working well so far. I'll know later tonight when I'm listening to beats in the dark.
Click to expand...
Click to collapse
Screen dim level set to 1. Then it's the values that are different in the pictures, the middle ones. Those are the brightness values. The first 2 numbers on the left are the light levels that would enable that level.
Sent from my SCH-I500 using xda premium
Thanks. I did some google searching and combined your light sensor values with levels I found from another site and also enabled Decrease in the settings. Just tried it outside and inside and it seems to be working. I'm not sure if I should post the levels values here because I'm on a galaxy nexus so I'll just leave it out.
retareq said:
Thanks. I did some google searching and combined your light sensor values with levels I found from another site and also enabled Decrease in the settings. Just tried it outside and inside and it seems to be working. I'm not sure if I should post the levels values here because I'm on a galaxy nexus so I'll just leave it out.
Click to expand...
Click to collapse
I see.. That's probably why yours was to dark. Different screens and all.. Maybe you can make a thread in your forums and help some people out.
Sent from my SCH-I500 using xda premium
Good idea. Thanks again. Some one already started a thread about it so I added it there.
Original post here:
https://forum.xda-developers.com/ga...te-to-96hz-t4073867/post82130937#post82130937
This has the complete guide
https://www.reddit.com/r/samsung/comments/fqk5he/made_the_s20_display_run_at_96hz_so_much_better/
There is an App available now that someone created: https://labs.xda-developers.com/store/app/sszb.s20.refresh
This mod works fine, but why SAMSUNG don´t add this option in the menu?? Cause screen damage??? I don´t know... I revert to 120 hz.
Installed and trying... Works perfect at the moment, will see if cause less battery drain...
I did the adb commands early this morning before work and battery life has taken a small hit, but the extra smoothness is absolutely worth it. I considered installing the app, but I probably won't go back to 60 Hz, and 120 Hz is overkill. I think 96 Hz is the sweet spot
sublimaze said:
I did the adb commands early this morning before work and battery life has taken a small hit, but the extra smoothness is absolutely worth it. I considered installing the app, but I probably won't go back to 60 Hz, and 120 Hz is overkill. I think 96 Hz is the sweet spot
Click to expand...
Click to collapse
Can u send a screenshot? ??
I want a solution that forces everything to run @*120Hz...
everyone just concerned about battery life.
Is there any downside to this app?
juliheavy said:
Can u send a screenshot?
Click to expand...
Click to collapse
I used this adb command:
adb shell settings put system peak_refresh_rate 96.0 && adb shell settings put system min_refresh_rate 96.0
Phone web browser confirms 96-97 HZ on testufo.com
Battery drain is still just over 1%/hour, so 96 Hz hasn't significantly impacted battery, but makes a *huge* improvement in scrolling smoothness and overall experience. Putting my S20+ next to my wife's Z Flip, you can definitely see the difference when scrolling the browser and Twitter. I won't be going back to 60 Hz, so I don't need the app. But I appreciate the work that went into the app, for those who want to use it.
avid_droid said:
96hz works fine for me through the app.
Click to expand...
Click to collapse
If you use the app and want to go back to 60, is there a way to do this?
sublimaze said:
I used this adb command:
adb shell settings put system peak_refresh_rate 96.0 && adb shell settings put system min_refresh_rate 96.0
Phone web browser confirms 96-97 HZ on testufo.com
Battery drain is still just over 1%/hour, so 96 Hz hasn't significantly impacted battery, but makes a *huge* improvement in scrolling smoothness and overall experience. Putting my S20+ next to my wife's Z Flip, you can definitely see the difference when scrolling the browser and Twitter. I won't be going back to 60 Hz, so I don't need the app. But I appreciate the work that went into the app, for those who want to use it.
Click to expand...
Click to collapse
Woah, it's a good result, thanks for sharing!
All the day in 96 hz,around 7 SOT. Not bad
Same today
what about compare 96 with 120hz?
emprize said:
what about compare 96 with 120hz?
Click to expand...
Click to collapse
I use tasker with selective 120hz over all time 96hz. All video streaming apps I use 60hz and rest set to 120hz. I tried all time 96hz but battery is better my way bc if I watch a lot of video, it won't run higher than 60hz so 96 or 120 is a waste. Using tasker profile for selective 120/60hz giving better /same battery as all time 96hz. And 120 is noticeably smoother than 96 at least to me.
The app caused some problem in my S20+ Snapdragon. I installed and set to 96 when I'm normally set to 120, and 6 hours later my phone had dropped 47% percent battery. Nothing else unusual running in background or foreground. No idea why and I haven't seen anyone else report it, so maybe a fluke. Just thought I'd mention it.
emprize said:
what about compare 96 with 120hz?
Click to expand...
Click to collapse
I can see a difference when scrolling text. So I went back to 120Hz for best smoothness. Don't care to much about battery life.
Yesterday and today, all the day 120 hz
juliheavy said:
Yesterday and today, all the day 120 hz
Click to expand...
Click to collapse
Snapdragon 865 at 120Hz