Related
I have the brightness turned almost all the way down then I turn it on auto. Is this the correct way to set it? It seems very bright even set so low.
brianfields33 said:
I have the brightness turned almost all the way down then I turn it on auto. Is this the correct way to set it? It seems very bright even set so low.
Click to expand...
Click to collapse
It definitely is too bright, i agree. I'm just putting together a nice setup for the Lux app, and hope that Google will make it a little less aggressive and therefor more battery-friendly
I noticed this as well. I just turned it down and left it (no auto).
Luxferro said:
I noticed this as well. I just turned it down and left it (no auto).
Click to expand...
Click to collapse
I thought about doing this, but then it will be hard to see in bright sunlight.
brittonberkan said:
It definitely is too bright, i agree. I'm just putting together a nice setup for the Lux app, and hope that Google will make it a little less aggressive and therefor more battery-friendly
Click to expand...
Click to collapse
I've never used Lux. Could you share the profile if possible when it's complete?
brianfields33 said:
I've never used Lux. Could you share the profile if possible when it's complete?
Click to expand...
Click to collapse
Sure thing, check back a little later please man, what were the folks at google thinking when they made these settings...
Gesendet von meinem Nexus 5 mit Tapatalk
Agree the screen is way too bright out of the box. Interested in your lux config as well
Sent from my Nexus 5 using Tapatalk
garrisj said:
Agree the screen is way too bright out of the box. Interested in your lux config as well
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'll have it done in a few hours. The dark values are fine but i need to wait for daylight
Gesendet von meinem Nexus 7 mit Tapatalk 4
brittonberkan said:
Sure thing, check back a little later please man, what were the folks at google thinking when they made these settings...
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
They were outside in California during the summer in the day and in an overly bright and cheerful Google headquarters during the night. They forget not everywhere has retina burning light levels
I've noticed that iOS, Touchwiz and a few other vendor Android skins implement a sliding-scale auto-brightness: You can enable auto, but also slide the overall average brightness up and down. This is a simple solution for varying comfort levels: Brightness fiends can tune the auto higher and those with sensitive eyes can tune it lower. I am surprised stock Android has yet to implement this.
I found auto brightness to be a bit erratic. I'm sticking with manual brightness.
Sent from my Nexus 5 using xda app-developers app
Here are my lux settings. At very bright areas you might have to add a few steps but it works well for me in darker, dimmer areas
https://docs.google.com/file/d/0B7IQuH022o2GSTAyWGtWTnhmaEU/edit?usp=docslist_api
I'm using dynamic mode
Edit: Sorry it apparently wasn't publicly available, but it is now
Have any of you had your brightness fluctuate from higher to lower? I don't remember the n4 doing that only. I thought android only went from low to high.
I actually want the opposite. I set my brightness all the way high in manual but I hate that automatic dimming. Can I get that fix? All I want is to work like my HTC One where I set the brightness all the way high and never saw the screen dim itself automatically. Please help
jbecerril said:
I actually want the opposite. I set my brightness all the way high in manual but I hate that automatic dimming. Can I get that fix? All I want is to work like my HTC One where I set the brightness all the way high and never saw the screen dim itself automatically. Please help
Click to expand...
Click to collapse
So yours is dimming itself as well correct? Pheww.. I'm not crazy
digitalsmoke said:
So yours is dimming itself as well correct? Pheww.. I'm not crazy
Click to expand...
Click to collapse
Yeah, and i hate that. I am not battery crazy like some other users, all i want is a bright screen regardless what time of the day it is. 100% brightness all the time. Can Auto brightness be turned off? Otherwise, and I hate to say it, but will going back to the One until this gets fixed.
auto brightness is terrible
the screen become yellow and green look while the brightness is low
only 100% can present the true white color
compare with htc one, i think one is better performance
anyone get the yellow tint problem?
brittonberkan said:
It definitely is too bright, i agree. I'm just putting together a nice setup for the Lux app, and hope that Google will make it a little less aggressive and therefor more battery-friendly
Click to expand...
Click to collapse
+1 for Lux. I had the battery-guzzling HTC Amaze ("you'll be AMAZED how fast your phone dies!" ). Lux would almost double my battery life when I programmed it with ultra-conservative (but still usable) settings.
If Google will update the auto brightness calibration everyone will start seeing much better battery life.
Sent from my Nexus 4 using Tapatalk
riprowan said:
+1 for Lux. I had the battery-guzzling HTC Amaze ("you'll be AMAZED how fast your phone dies!" ). Lux would almost double my battery life when I programmed it with ultra-conservative (but still usable) settings.
If Google will update the auto brightness calibration everyone will start seeing much better battery life.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Which Lux app do i need from the Play Store? There are many of them...
CitizenX said:
Which Lux app do i need from the Play Store? There are many of them...
Click to expand...
Click to collapse
I use this one:
https://play.google.com/store/apps/details?id=com.vito.lux
The trick is in setting up the profiles by hand, the automatic profile settings can be wonky.
Take some light measurements in dimmes light and establish the lowest level you can accept the screen. On an N5 this is probably all the way min. (At first you may find that it's pretty dim but Realize that you'll get used to this and later wonder why you liked the screen so bright.)
Then go into bright light and find the min level that you can accept. This might be all the way bright (on my Amaze, all the way bright was unnecessarily bright EVEN IN SUNLIGHT).
Then take a reading in a normal room and find the min acceptable brightness. This may still be all the way min.
You may want to sample a point or two in other light levels, usually 3-5 samples is enough if you suss out the power curve correctly.
Everyone loves iPhone battery life... ever notice how conservative an iPhone's auto brightness setting is? I'll go out on a limb and guess that, if the N5 is as aggressively bright in auto mode as everyone says (don't have mine yet), there's the possibility of getting an entire extra hour of SOT just by switching instead to very conservative auto-brightness settings.
Also if the min brightness is still pretty darn bright, there's a really good chance an update can knock that brightness down and stretch the battery even further.
I want to start a bounty (if there is even any interest for this?) to disable the screen brightness throttling.
Now of course I understand people say "oh it will damage your phone" but you know what, so will overclocking your processor and graphics etc.
My problem is that whilst not even doing intensive tasks, my screens maximum brightness lowers, apparently due to temperature throttles. It is really frustrating because sometimes the phone does not even feel hot, and I'm not even using the phone intensively.
Even if there is no interest in this, I'd happily pay someone to increase the temperature throttle for brightness reduction.
Many Thanks
danieljamie said:
I want to start a bounty (if there is even any interest for this?) to disable the screen brightness throttling.
Now of course I understand people say "oh it will damage your phone" but you know what, so will overclocking your processor and graphics etc.
My problem is that whilst not even doing intensive tasks, my screens maximum brightness lowers, apparently due to temperature throttles. It is really frustrating because sometimes the phone does not even feel hot, and I'm not even using the phone intensively.
Even if there is no interest in this, I'd happily pay someone to increase the temperature throttle for brightness reduction.
Many Thanks
Click to expand...
Click to collapse
Maybe you have it set for automatic. I have have my auto setting turned off and set to full brightness. It has never changed or become dimmer and I play a rather demanding game for an hour or more at a time.
Solarenemy68 said:
Maybe you have it set for automatic. I have have my auto setting turned off and set to full brightness. It has never changed or become dimmer and I play a rather demanding game for an hour or more at a time.
Click to expand...
Click to collapse
I definitely have auto brightness off. It's a known fact it thermal throttles the brightness. Perhaps you live in Antarctica?
Sent from my SM-N9005 using xda app-developers app
Mine never changes either and I live in illinois.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
drakeymcmb said:
Mine never changes either and I live in illinois.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
It happens on the Snapdragon model 9005 when auto brightness is off, brightness is set to max and under heavy load. Even worse if you are charging the device at the same time.
There are other threads confirming brightness throttle.
Hell, I even got a message in brightness settings to say it.
Sent from my SM-N9005 using xda app-developers app
yes, brightness (and CPU) throttling on ALL N9005 devices is fact, although some perform better (later throttling) and some not, which maybe has something to do with CPU-binning (search for that, the higher the number the lesser the voltage, less voltage means less leaking current > lower temp under load) i'm sure this is kernel related, so theoretically it should be no problem to disable it with a custom kernel!
due to "display problems" i switched through 6 devices, 2 of them were noticeable better in regards of throttling... as always with consumer devices: it's a bit "luck of the draw" which device you get...
I have to agree with the others, I have never seen that message in normal use. The only time I ever experienced that message was when my phone was in a car holder on the windscreen and it was 34 Celsius outside on holiday. For example, I could play a game in my home (in the UK where it is currently much cooler) on full brightness and never have any noticeable problem with brightness throttling.
Sent from my SM-N9005 using xda app-developers app
The throttle will only activate if you have the screen brightness at 100%, a quick workaround would be to set the screen brightness to 99%.
npras42 said:
I have to agree with the others, I have never seen that message in normal use. The only time I ever experienced that message was when my phone was in a car holder on the windscreen and it was 34 Celsius outside on holiday. For example, I could play a game in my home (in the UK where it is currently much cooler) on full brightness and never have any noticeable problem with brightness throttling.
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
I am in the UK...
Riyyi said:
The throttle will only activate if you have the screen brightness at 100%, a quick workaround would be to set the screen brightness to 99%.
Click to expand...
Click to collapse
Nope. Even at low brightnesses I get the throttle flicker.
Sent from my SM-N9005 using xda app-developers app
In which case it sounds like there is something wrong with your phone. Maybe hardware fault?
Sent from my Nexus 10 using xda app-developers app
npras42 said:
In which case it sounds like there is something wrong with your phone. Maybe hardware fault?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Please, plug in your phone, play a game for an hour at full brightness and tell me what happens.
Not ten mins. An hour gaming. The message is there in brightness settings. This is not a fault, Samsung created this!
Sent from my SM-N9005 using xda app-developers app
danieljamie said:
I definitely have auto brightness off. It's a known fact it thermal throttles the brightness. Perhaps you live in Antarctica?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Well I guess the issue her is that mine is not a 9005, but a 900A.
So that might have some bearing as I run mine at 100% brightness all the time and at nigh as I am going to bed i play Valkyrie Crusade on the charger and have never seen any flicker or dimming in video brightness.
I just this weekend played NFS: Most Wanted for more than three hours straight with at least 2 hours on the charger and all at full brightness and never saw this. I am sure because I usually use auto brightness but don't like it shifting brightness whilst playing a game and changed it back as soon as I was done. The thermostat in my flat is usually set at 23.
Also like I said, its not like I have never seen the message, just in vastly more strenuous situations than you are describing which again makes me think you have a hardware fault making this problem occur more frequently.
Let's see if someone else can replicate your problem in similar circumstances to see if it is a more widespread issue.
Sent from my Nexus 10 using xda app-developers app
npras42 said:
I just this weekend played NFS: Most Wanted for more than three hours straight with at least 2 hours on the charger and all at full brightness and never saw this. I am sure because I usually use auto brightness but don't like it shifting brightness whilst playing a game and changed it back as soon as I was done. The thermostat in my flat is usually set at 23.
Also like I said, its not like I have never seen the message, just in vastly more strenuous situations than you are describing which again makes me think you have a hardware fault making this problem occur more frequently.
Let's see if someone else can replicate your problem in similar circumstances to see if it is a more widespread issue.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I was using a LG optimus G pro before this one, in my opinion the bright is poor in this phone vs for example S4 or LG. So , will be very interesting get a solution meaby by kernel or similar to get more bright. I offert another 10$ if anyone can developed any thing in this direction.. thanks in advance
danieljamie said:
I want to start a bounty (if there is even any interest for this?) to disable the screen brightness throttling.
Now of course I understand people say "oh it will damage your phone" but you know what, so will overclocking your processor and graphics etc.
My problem is that whilst not even doing intensive tasks, my screens maximum brightness lowers, apparently due to temperature throttles. It is really frustrating because sometimes the phone does not even feel hot, and I'm not even using the phone intensively.
Even if there is no interest in this, I'd happily pay someone to increase the temperature throttle for brightness reduction.
Many Thanks
Click to expand...
Click to collapse
Buy the n900 (exynos).. it doesen't have that issue
I've read many threads about this issue and I guess that it persists only on SM-N9005 Snapdragon devices. I live in Greece and in summer when temperatures are really high, the thermal throttling issue becomes really annoying especially when gaming, because thermal throttling affects screen brightness, CPU clocks and GPU clocks too! For those who don't believe this, here's a screenshot of my N9005 when overheated.
maybe this...?
I'm in the US, with a rooted N3, 900t. stock kernal and ROM, and have also experienced the brightness flicker/throttle.
I've noticed it under varying circumstances, but yes, most frequently when plugged in and surfing web.
I have Xposed framework installed, with a CPU temp display module. Based on what I've noiticed, the dim happens around 146-150 degrees farenheit. Most games, however, will not allow the dim to occur.
There is also another Xposed module I have been using with mixed results called DVS disabler. It will randomly keep the screen from dimming at temps as high as 167 degrees farenheit! (at that temp, i can feel the heat coming off the screen at almost an inch away)
Side-thought::: I have a 'tempered glass' screen protector on that may/may not be affecting the whole temperature thing. not certain.
I get this issue too... Sometimes not even doing anything that intensive... Hopefully it's a simple kernel tweak.
Sent from my SM-G900F using XDA mobile app
My phone has been doing this as well since day.
Try with this
https://play.google.com/store/apps/details?id=mobi.pruss.superdim
Here is a little tutorial I have put together for the upcoming Motorola Moto X Style (Pure Edition). The new Moto X comes with a Q-HD display. Though a higher resolution might be nice it does use more battery as well. With this simple guide you can force the GPU to render the OS and everything in it, in 1080p instead of Q-HD. The display will still be Q-HD but everything on the phone, including the full Android OS, will be displayed in 1080p. This will increase S.O.T and battery life noticeably.
Prerequisites:
1) A rooted device running stock/stock based ROM.
Step 1:
Install the Terminal Emulator app from the Play Store. Download from HERE
Click to expand...
Click to collapse
Step 2:
Open the app and type the following:
Code:
su
Grant terminal Emulator super su access.
Click to expand...
Click to collapse
Step 3:
Next type the following:
Code:
wm size 1080x1920
Click to expand...
Click to collapse
Step 4:
After that, type:
Code:
wm density 420
Click to expand...
Click to collapse
Step 5:
Finally to re-render all the un-changed drawables and pre-loaded system components type:
Code:
stop && start
Your phone will now reboot.
Click to expand...
Click to collapse
That's it! Now you can get some extra juice out of your new Moto X.
To Revert to Stock Settings:
Step 1:
Code:
wm size reset
Click to expand...
Click to collapse
Step 2:
Code:
wm density reset
Click to expand...
Click to collapse
Step 3:
Code:
stop && start
Click to expand...
Click to collapse
Are there even any QHD videos or games available? What would make use of the QHD screen?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
buggerritt said:
Are there even any QHD videos or games available? What would make use of the QHD screen?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
My point exactly...If you go the the Google developer stats website you can see on 4.7% of apps on Google Play take advantage of QHD. Also almost 89% of youtube videos are max 1080p. Knowing this I put together this guide. So at least Q-HD won't drain my battery.
Interesting to see if it makes a diference. So, could this be made also to work on a 1080P display and lower it to 720p you know to save even more battery???
Shawn5162 said:
My point exactly...If you go the the Google developer stats website you can see on 4.7% of apps on Google Play take advantage of QHD. Also almost 89% of youtube videos are max 1080p. Knowing this I put together this guide. So at least Q-HD won't drain my battery.
Click to expand...
Click to collapse
Pretty nice.. I'm going to bookmark this.. It's it easy to change back?
Sent from my SPH-L900 using XDA Free mobile app
joshhud said:
Pretty nice.. I'm going to bookmark this.. It's it easy to change back?
Sent from my SPH-L900 using XDA Free mobile app
Click to expand...
Click to collapse
Yes...I will add a guide on how to revert...Acutlly reverting requires less steps that lowering the resolution.
Sent from my SM-G900I using Tapatalk
cerobles1 said:
Interesting to see if it makes a diference. So, could this be made also to work on a 1080P display and lower it to 720p you know to save even more battery???
Click to expand...
Click to collapse
You could...What device do u have. I could PM u the steps to lower its res.
Sent from my SM-G900I using Tapatalk
If this phone comes out as scheduled or somewhere near that and I buy one, I'm going to avoid any tweaks or hacks for a while but I appreciate your info. Thanks for posting it.
This might just end up being a big battery saver.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
This could be awesome or a complete fail. I know with other phones I have tried this on some stock apps like camera completely stop working and a lot of the FYI isn't working. However I didn't do this exactly so it may have been the wrong ethod. I'm excited to hear results. ☺
Can't you just paste this into the terminal in one take?
Code:
su
wm size 1080x1920
wm density 420
stop && start
Shawn5162 said:
You could...What device do u have. I could PM u the steps to lower its res.
Sent from my SM-G900I using Tapatalk
Click to expand...
Click to collapse
Currently I have the Galaxy S5 (SM-G900A) AT&T variant, but I'm running an International ROM. I would definitely like to try it and be a ginnie pig. But more than likely I would do it at the end of this week since I have a 4-day weekend coming up, giving me plenty of time in case things go bananas and have to revert back to stock. But please do let me know what the steps are for my current phone.
Would this really make a huge impact on the battery life?
I'm curious to know, does the screen actually not turn on each pixel with these options? From what I understand, with LCD screens it's either all or nothing.
If I'm correct about the all or nothing this trick would lower the batter consumption by a bit, but not much. The only thing it would do is lower the tax on the CPU.
From my understanding it will have to render less pixels therefore less power consumption as the GPU will not have to work as hard
If LCD's on cell phones work the same as on computer screens, then this will not have any affect but to change how things look on the screen. The same number of pixels will still be activated. Only some will do double duty. If you can, go ahead and lower the resolution on your computer screen and things will look larger but all the pixels are still being used. I cannot imagine this will have much, if any effect on battery life. Maybe I'm wrong??
jaseman said:
If LCD's on cell phones work the same as on computer screens, then this will not have any affect but to change how things look on the screen. The same number of pixels will still be activated. Only some will do double duty. If you can, go ahead and lower the resolution on your computer screen and things will look larger but all the pixels are still being used. I cannot imagine this will have much, if any effect on battery life. Maybe I'm wrong??
Click to expand...
Click to collapse
This is exactly what I was expecting. There's no way it would have much effect if any.
Sent from my Nexus 7 using Tapatalk
Ganondroid said:
This is exactly what I was expecting. There's no way it would have much effect if any.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
People did this on the LG G3 and their battery life had a massive jump in SOT. Not sure how it works but it is worth trying for sure. Of anything it will make the phone faster because it isn't pushing so many pixels. Only time will tell use the phone normal for a week to let the battery set in and get a good idea. Then drop it and compare. If it is the same you have yoru answer, if it does what the G3 did and almost doubles the SOT then we will have a party.
joshuadjohnson22 said:
People did this on the LG G3 and their battery life had a massive jump in SOT. Not sure how it works but it is worth trying for sure. Of anything it will make the phone faster because it isn't pushing so many pixels. Only time will tell use the phone normal for a week to let the battery set in and get a good idea. Then drop it and compare. If it is the same you have yoru answer, if it does what the G3 did and almost doubles the SOT then we will have a party.
Click to expand...
Click to collapse
The G3 never saw massive battery life jumps. All lowering the resolution did was boost the performance. There was a slight increase in battery life due to lower strain on the CPU/GPU, but that was it. The only way this style of mod would help battery life would be on an OLED screen and it would have to actually turn off some pixels instead of duplicating them.
If you want better battery life from the screen resolution you would have to turn your device into a frankenphone by taking a lower resolution screen from something else, which is essentially impossible at this time.
Ganondroid said:
The G3 never saw massive battery life jumps. All lowering the resolution did was boost the performance. There was a slight increase in battery life due to lower strain on the CPU/GPU, but that was it. The only way this style of mod would help battery life would be on an OLED screen and it would have to actually turn off some pixels instead of duplicating them.
If you want better battery life from the screen resolution you would have to turn your device into a frankenphone by taking a lower resolution screen from something else, which is essentially impossible at this time.
Click to expand...
Click to collapse
even so, not pushing that many pixels on the CPU/GPU may make a pretty noticeable difference. For those who do not mind a fuzzier screen it could be a good solution. I still think it would be worth testing but we will have to come across that bridge when the phones are here. Who knows, maybe it wont be bad to begin with
Would not like 1080p stretched out over a Qhd screen. Too fuzzy for my liking. Always stick to native resolution on amoled/lcd.
I've been running smooth display (90 hz) since I got my pixel 4 xl. Just switched it off yesterday and can't notice any difference. Now I'm wondering why all the initial negative reviews about it switching back and forth initially when you can't even really tell?
in_dmand said:
I've been running smooth display (90 hz) since I got my pixel 4 xl. Just switched it off yesterday and can't notice any difference. Now I'm wondering why all the initial negative reviews about it switching back and forth initially when you can't even really tell?
Click to expand...
Click to collapse
Are u seriously?
Every phone that I take, now fells so choppy and uncomfortable. Same if I just switch off smooth display.
in_dmand said:
I've been running smooth display (90 hz) since I got my pixel 4 xl. Just switched it off yesterday and can't notice any difference. Now I'm wondering why all the initial negative reviews about it switching back and forth initially when you can't even really tell?
Click to expand...
Click to collapse
I'm with you. Turned it off since a while now cause of the colour shift. A barely notice a huge difference. Phone feels smooth anyway.
lapapunk said:
Are u seriously?
Every phone that I take, now fells so choppy and uncomfortable. Same if I just switch off smooth display.
Click to expand...
Click to collapse
Yeah I agree, 60hz is just choppy now. I can't go back to a 60hz phone
Maybe you're not sensitive to frame rate difference. To me it's much smoother! I've been spoiled lol. 60 FPS looks so choppy now ?
That's interesting, mine feels as smooth as it's ever been, not choppy at all on 60 hz. Oh well... Sorta disappointed that I didn't notice a difference lol
Within settings or your app drawer, just scroll up and down on 60hz and then do it on 90hz. You should instantly notice the difference in the refresh rate. [emoji848]
Sent from my Pixel 4 XL using Tapatalk
Curiousn00b said:
Within settings or your app drawer, just scroll up and down on 60hz and then do it on 90hz. You should instantly notice the difference in the refresh rate. [emoji848]
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Yes this is definitely an easy way to show the difference. Website scrolling is also another area I notice it most. It's as noticable as watching a sports highlight in 60 FPS in YouTube vs not.
Sent from my Pixel 4 XL using Tapatalk
Scrolling anything; address book, website, mail list, etc. There is more to it than the refresh though and it isn't easy to separate everything out and see it on it's own. My daughter and son and law picked up a Tmo bogo on Note 10s over the holidays and we were comparing smoothness between mine and theirs and the Pix is no question smoother when sitting side by side and doing the same thing. We thought it was the refresh so I put it to 60 where presumably the better specced Note would show it's stuff but it didn't happen there either, the Pix is still smoother. As an aside I haven't been on a Samsung device since they screwed my over on my international Note 8 with the bootloader shenanigans and man, those whites are really, really, REALLY, blue. Loved the brightness though, gotta troll through Magisk and see about getting some boost action going on.
How do you set to stay on 90hz after update... Don't see developers settings no more
Another reason people might not notice the difference is between 90hz and 60hz is because of the apps they use. Not all apps are drawn at 90fps which in turns causes the display to render at 60hz as well. Google maps for example only does 60fps and thus you won't notice the benefit of the 90hz display. But UI element (such as scrolling through settings or app drawer) definitely highlights the 90hz refresh rate and should instantly be noticeable.
Calmplex4g said:
How do you set to stay on 90hz after update... Don't see developers settings no more
Click to expand...
Click to collapse
When developer options is enabled just use the search function up top. Type in 90hz and you should be able the find the setting to force 90hz.
Calmplex4g said:
How do you set to stay on 90hz after update... Don't see developers settings no more
Click to expand...
Click to collapse
Keep tapping build number and it will appear under system settings
I'm in the middle on this argument. I can clearly see the difference between 60 and 90 when scrolling. That being said I don't care about being able to read something while I'm scrolling... Lol
I have not really tested the difference in battery life with or without the smooth enabled but I'm not losing any sleep over no having it enabled. I guess if I had it forced for a while I'd prolly miss it more if I switched it off then.
Calmplex4g said:
How do you set to stay on 90hz after update... Don't see developers settings no more
Click to expand...
Click to collapse
Still there after my January update. If not, well that's interesting. Turn on smooth display then :good:
I was on the OnePlus 7 Pro before the 4 XL so I've been using 90Hz for a while now. I mention that because I feel the difference is more and more noticeable as time goes on. The longer you use 90, the more significant the difference is from 60.
That's been my experience at least. I have 90 force enabled as well. However, I use Tasker to disable 90 once my phone hits 40%.
EeZeEpEe said:
Yes this is definitely an easy way to show the difference. Website scrolling is also another area I notice it most. It's as noticable as watching a sports highlight in 60 FPS in YouTube vs not.
Click to expand...
Click to collapse
Also when using gestures (eg, slide to switch app)
in_dmand said:
That's interesting, mine feels as smooth as it's ever been, not choppy at all on 60 hz. Oh well... Sorta disappointed that I didn't notice a difference lol
Click to expand...
Click to collapse
Don't be lol. It's a blessing! :angel:
It's definitely noticeable in any app that supports the refresh rate and system UI. I can't go back to 60hz and same with my monitor at home it's 144hz and the difference between 60 is a day and night difference. Once you go high refresh rate you don't go back! As for battery life impact it's probably there but I don't care. With my usage and using cell data I can make it over a day without having to charge. Adaptive battery and optimizations really go a long way.
Calmplex4g said:
How do you set to stay on 90hz after update... Don't see developers settings no more
Click to expand...
Click to collapse
Same way as before - tap on Build Number 7 times to enable Developer Mode. The Force 90Hz option is still there for me on the January update
If i Switch to 90hz force do you notice more battery consumption?
I am currently on stock Android 12. I flashed the unlocked stock image (non-verizon) a few weeks back. With Android 11, Android 12, LineageOS, etc. every browser I have tried including Chrome, Brave, Via, etc. all drain the battery way faster than browsers did on my previous Moto G5 plus. i would say when I am surfing the net on my browser (usually just reading forums, no video), the battery drains about 1% every 5 minutes or less. I have tried 2.4Ghz wifi, LTE, etc. and data connection type doesn't seem to impact anything.
Is this normal for this phone? anything to do to reduce browser battery drain?
If you go into battery usage graph, is the browser the only app listed as using up the battery (and not the screen brightness, or another app that may be contributing to the heavy usage)
JohnC said:
If you go into battery usage graph, is the browser the only app listed as using up the battery (and not the screen brightness, or another app that may be contributing to the heavy usage)
Click to expand...
Click to collapse
correct. if I am using other apps the battery drain isn't near as severe. I keep the display setting "extra dim" enabled all the time and I keep it down as low as I can tolerate. I use a pitch black wallpaper use dark mode in browsers so they have mostly black background with white text.
Phone idle is the only other thing that seems to use a sizeable amount of battery according to the battery usage data in settings.
Sounds about right. Came from a Moto G7 Play (15 months back) and saw similar drain rates. All three devices have similar battery specs which plays into the units being used to assess drain. Is what it is.
FWIW - Opera
DB126 said:
Sounds about right. Came from a Moto G7 Play (15 months back) and saw similar drain rates. All three devices have similar battery specs which plays into the units being used to assess drain. Is what it is.
FWIW - Opera
Click to expand...
Click to collapse
Not gonna lie, it makes me want to go back to Motorola when this Pixel bites the dust.
badtlc said:
Not gonna lie, it makes me want to go back to Motorola when this Pixel bites the dust.
Click to expand...
Click to collapse
Many Moto's bring a nice package with unique tricks. Gotta do your homework on what features are most important when the time comes.
DB126 said:
Many Moto's bring a nice package with unique tricks. Gotta do your homework on what features are most important when the time comes.
Click to expand...
Click to collapse
I definitely did that. I only got the 4a because it was the perfect size and had a headphone jack. I assumed with a newer hardware set and similar sized battery compared to my old phone batter life "should" be better. Nope.
Na, it's more complicated. 4a sports more sensors, brighter/denser display, faster processors, etc. System and personal apps clearly play a role in longevity (behind screen brightness); you'd need to do a detail study to understand what's drawing when and why.
I use to fuss over such matters but find the device lasts a full day for my use case which is all that really matters. Charges up quick from a modest size battery pack when camping/traveling. Just like past Motos.
Not sure who I'll partner with in the next dance. Love Pixel cameras (especially in challenging conditions) and routine updates. Miss some of Moto's innovations, like active display and actions. Needs to be close to AOSP; no Samsung UX butchery. In the end form factor will likely be the deciding factor once non-contenders are ruled out.
badtlc said:
I assumed with a newer hardware set and similar sized battery compared to my old phone batter life "should" be better.
Click to expand...
Click to collapse
I don't know what CPU you came from, but if the Moto only had "small" cores then of course it used less battery. "Big" cores use more power. They go faster too, but if you have a constant load, then they'll eat battery faster.
I don't know if there's a non-root way to disable the big cores, but I suspect you can do it with root (but don't know for sure).
Otherwise, you gotta get your browser to stop running JavaScript. If you're watching video you need to make sure the browser is offloading all the decoding to the hardware codecs rather than doing it on the CPU.
And if the screen is on, it might help to try and get it "more black" (eg. Use night mode) or turn down the brightness. The screen is often the primary user of power when a device is being used.
a1291762 said:
I don't know what CPU you came from, but if the Moto only had "small" cores then of course it used less battery. "Big" cores use more power. They go faster too, but if you have a constant load, then they'll eat battery faster.
I don't know if there's a non-root way to disable the big cores, but I suspect you can do it with root (but don't know for sure).
Otherwise, you gotta get your browser to stop running JavaScript. If you're watching video you need to make sure the browser is offloading all the decoding to the hardware codecs rather than doing it on the CPU.
And if the screen is on, it might help to try and get it "more black" (eg. Use night mode) or turn down the brightness. The screen is often the primary user of power when a device is being used.
Click to expand...
Click to collapse
Thanks for the suggestions. My power complaints are just limited to the browser so I dont think it is just the larger CPUs. I think my standby consumption issues are related to Stock Android as I am now running GrapheneOS and my standby power consumption now matches my old Moto G5 Plus.
As for browser usage consumption, I have tried everything but disabling Javascript. I will try that and see if it breaks anything I use regularly. Thanks for the idea.
tangent back to general power consumption, I typically disable just about everything behind the scenes as I can. I keep the theme on pitch black. I use the extra dim setting to keep screen brightness as low as I can tolerate. I use night mode in browser to keep as much black background as possible. I disable all tap-to-wake or sensor based features. When I was trying to run Android 12, I disabled all the smart services and removed all the google apps I could. I removed all permissions I could. I restricted all apps I could. I disabled adaptive settings, etc. There is a bunch of stuff running in the background on Android 12 and I just could not
Welcome to the future. Older phones had better battery life
Locklear308 said:
Welcome to the future. Older phones had better battery life
Click to expand...
Click to collapse
I dont think it is all the phone. GrapheneOS has 40% better standby battery usage than stock android 12. On graphene, it matches my old Moto G5 Plus. It is either lazy programmers with inefficient coding these days or it is google having the stock OS do waaaay too much by default with no way to disable it.
I'm trying to figure that out now.
badtlc said:
I dont think it is all the phone. GrapheneOS has 40% better standby battery usage than stock android 12. On graphene, it matches my old Moto G5 Plus. It is either lazy programmers with inefficient coding these days or it is google having the stock OS do waaaay too much by default with no way to disable it.
I'm trying to figure that out now.
Click to expand...
Click to collapse
I totally agree on the lazy thing. So many devs now days are so lazy. I develope QuickBase databases and constantly run into extremely poorly setup realms/apps. Just basic stuff. Lol