Related
Especially with root now becoming available, I started giving this more thought:
If someone wanted to do that, would running a lower resolution be an option, to perhaps extend your battery life?
The screen is QHD, 1440x2560. To minimize scaling issues with a fixed-pixel-location screen like an LCD, you could go down to HD, 720x1280. Now the graphics hardware is dealing with 1/4 as many pixels. It won't look as good, granted, but lets say the user accepts that trade-off.
Is this even possible? If so, do you think it could help battery life?
I don't have experience with this on phones. But on a computer, you can certainly lower your display resolution, even if using an LCD. It will look fuzzy at a non-native resolution, but perhaps that's less of an issue here, with the pixels being so small by comparison. And if you were gaming on the PC, lowering the resolution would allow higher framerates, assuming you were limited by your graphics card, not your CPU. I've admittedly never thought about it from a power-use perspective, but it seems reasonable that, if keeping the framerate the same, running a lower resolution would require less power for the PC.
My Galaxy S3 was 720x1280, admittedly on a smaller 4.8" screen, but I thought it looked fine. If using a lower screen resolution could, say, add 20% to my G4's SOT, I would be interested in that.
I believe this is what changing the DPI is for. This can be done via apps, or changing the value in the build.prop I think. Pushing less pixels on to the screen will definitely increase battery life. There's a threshold though, and depending on which G4 variant you have (whether it's branded by a carrier, etc.) you may want to research on what a safe number might be. I think some AT&T G4 user reported bootloops after changing the DPI to <530 or something. It looks like the camera doesn't get affected by the DPI change too, which is a definite good sign.
I'm waiting to see how the battery life holds up right now with root mode now being enabled in Greenify. If I can't squeeze more than 5 hours SoT while at a certain brightness and using BT, I'll consider changing the DPI.
This is not going to improve battery life in the slightest. You might be running a lower resolution but all the pixels are stilled turned on. The lower tax on the GPU is negligible.
kyle1867 said:
This is not going to improve battery life in the slightest. You might be running a lower resolution but all the pixels are stilled turned on. The lower tax on the GPU is negligible.
Click to expand...
Click to collapse
Agreed. This was done on the G3 and batter life was not changed, only game performance improved as you are pushing graphics at 1080p instead of 1440p.
AhsanU said:
I believe this is what changing the DPI is for. This can be done via apps, or changing the value in the build.prop I think. Pushing less pixels on to the screen will definitely increase battery life. There's a threshold though, and depending on which G4 variant you have (whether it's branded by a carrier, etc.) you may want to research on what a safe number might be. I think some AT&T G4 user reported bootloops after changing the DPI to <530 or something. It looks like the camera doesn't get affected by the DPI change too, which is a definite good sign.
I'm waiting to see how the battery life holds up right now with root mode now being enabled in Greenify. If I can't squeeze more than 5 hours SoT while at a certain brightness and using BT, I'll consider changing the DPI.
Click to expand...
Click to collapse
I believe that that's wrong, specially if you set it to numbers lower than stock.
I found a way to change the resolution
https://forum.xda-developers.com/galaxy-s5/general/tool-change-phone-resolution-dpi-root-t3582863
Follow this thread, it's so simple and works perfectly!! on LG G4 818p
Hi guys,
How Asus Zenfone Max Pro M1 6GB variant compares with Mi Max 3?
I feel Mi Max 3 will be on positive side for
1. bigger battery (5500 mAh vs 5000 mAh)
2. quick charge 3
3. IR blaster
Whereas Asus Zenfone Max Pro M1 6GB variant will be on positive side for
1. Near stock android (vs MIUI)
I use Nexus 6. I do a lot reading on it. Many times I read in split screen mode in two apps (say two instances of Microsoft Word, one through ES Parallel Space). Nexus 6 has broader screen (16:9 ratio). It was launched in 2014, but still have higher resolution and pixel density than both Max 3 and Zenfone!!! This makes it best to read in split screen mode in two apps. So I feel bigger screen of Mi Max 3 will be suitable for this purpose.
Also its stock android is great. Split screen functionality of Stock Naugat is better than that of MIUI.
I also feel MIUI provides better control over backgound apps and hence battery. I live with my four year old Nexus 6 in always on battery saver mode. This helps to extend battery life to at least 1 day. If I dont use battery saver mode, it will barely last for 15 hours. Also my Nexus 6 lags quite a lot now. Opening some 40 page word docs takes at least 5 sec. Will all this be gone with both Max 3 or Zenfone?
Also Nexus 6 had great camera with OIS. Mi Max 3 have AI camera while Asus Zenfone have 16MP phone. Dont know which one will have better camera at least better than Nexus 6?
So was guessing what will be best choice for me.
Hi there. I think you are comparing apples with oranges. MM3 is 6.9, Max Pro M1 is 5.99. It is a perfect hardware match for redmi note 5 - so there you should compare. Regards!
Neznam123 said:
Hi there. I think you are comparing apples with oranges. MM3 is 6.9, Max Pro M1 is 5.99. It is a perfect hardware match for redmi note 5 - so there you should compare. Regards!
Click to expand...
Click to collapse
yeah I know there is 0.9" difference.
But I am not trying to compare them with each other, but with my usage scenario. Thats why I explained how I usually use it.
Usage scenario 1: Two Microsoft Word documents in split screen mode each 40+ page.
Usage scenario 2: Satisfying camera (at least better than Nexus 6)
I believe broader screen like Nexus 6 serves better when it comes to my usage scenario 1. Zenfone seems a bit narrower. In fact, in todays market, most 6" phone is narrower than 6" Nexus 6 due to their 18:9 ratio (Nexus 6 is 16:9). Also two instances of Word should work smoothly in split screen. My 4 year old Nexus 6 lags considerably at this. I dont know what is culprit: old processor (but its 2.6GHz quad core)? slower / smaller RAM? or battery?
On paper, M1 is good but users report M1 has some problem included multitouch problem, not so good on battery/matterial quality
Ho boy.. I have Nexus 6 too. Was my daily driver until I ditched it for good with my Max 2. The worst thing about Nexus 6 was the camera, it's barely useable. Also fingerprint, the battery and SoC efficiency, I would trade AMOLED 1440p and front firing speakers for those any time of the day. Once you are in 10+ hours SOT territory you don't ever want to go back.
Also MIUI is not that bad at all, it's not as intrusive and forceful as Huawei EMUI. It looks clean and still have material design language.
I just upgraded from 8.1 to 9.0 on my XL 2 over the weekend. I am stock rooted.
Is it just me or is the overall display brightness much less on Pie than it was on Oreo? In the same daytime environment, I feel like Pie needs to be around 70% brightness whereas on Oreo, I feel like the display was set on about 35%. I rarely had Oreo brightness above 50%. Now with Pie, I feel like I can barely see the screen when it's under 50%.
On Oreo, my display was set to Saturated and of course, white theme since that's all we had.
On Pie, I used the same settings and it looks much dimmer. I adjusted display to Boosted and have toogled back and forth between light and dark themes and I don't notice any difference with how much dimmer the overall display feels.
The display can still get just as bright. They've just changed the way the values are displayed from the slider is all.
angus242 said:
I just upgraded from 8.1 to 9.0 on my XL 2 over the weekend. I am stock rooted.
Is it just me or is the overall display brightness much less on Pie than it was on Oreo? In the same daytime environment, I feel like Pie needs to be around 70% brightness whereas on Oreo, I feel like the display was set on about 35%. I rarely had Oreo brightness above 50%. Now with Pie, I feel like I can barely see the screen when it's under 50%.
On Oreo, my display was set to Saturated and of course, white theme since that's all we had.
On Pie, I used the same settings and it looks much dimmer. I adjusted display to Boosted and have toogled back and forth between light and dark themes and I don't notice any difference with how much dimmer the overall display feels.
Click to expand...
Click to collapse
Google changed the algorithm on the brightness slider. Therefore, 70% is the new 30% So, no, it's not you. Another brilliant improvement for the sake of supposed progress! ?
Badger50 said:
Google changed the algorithm on the brightness slider. Therefore, 70% is the new 30% So, no, it's not you. Another brilliant improvement for the sake of supposed progress! ?
Click to expand...
Click to collapse
Lol, not sure what they're Smoken at Google headquarters...
galaxys said:
Lol, not sure what they're Smoken at Google headquarters...
Click to expand...
Click to collapse
Probably hanging out with this guy! ???
I agree with everyone else. 100% on 9 is still as bright as 100% was on 8.1 but 50% on 9 is NOT what 50% was on 8.1, no doubt about it. On 8x I usually kept my brightness around 65%... now on 9, to get something similar I am around 70-75%... If the same energy is being used to illuminate the display at the different values, batt life should remain about the same... But WHY?
Why change what 50% was on 8 to be different on 9? Isn't HALF the available illumination HALF the available illumination regardless of the OS version? What is the effect, or end game Google was looking for with this?
The max brightness is the same. The difference is the slider is no using a logarithmic algorithm instead of the old linear algorithm.
Here is the explanation of why it was done:
The first noteworthy feature is a changed brightness slider behavior: It now changes the brightness logarithmically instead of linearly. Before this preview when it was linear, about 90% of the brightness was controlled by the lower 20% of the left of the slider. The old 50% brightness was almost identical to 100% max brightness, and the old 5% brightness was significantly brighter than 0% brightness. Now, the change in perceptual brightness is more uniform as you increase or decrease the slider.
Exactly. 50% before was definitely not 50% nits output for the screen which, with a rated max 403 by anandtech, would be only 201.5 nits. And that was before the November update that lowered the max by 50 nits.
jimv1983 said:
The max brightness is the same. The difference is the slider is no using a logarithmic algorithm instead of the old linear algorithm.
Here is the explanation of why it was done:
The first noteworthy feature is a changed brightness slider behavior: It now changes the brightness logarithmically instead of linearly. Before this preview when it was linear, about 90% of the brightness was controlled by the lower 20% of the left of the slider. The old 50% brightness was almost identical to 100% max brightness, and the old 5% brightness was significantly brighter than 0% brightness. Now, the change in perceptual brightness is more uniform as you increase or decrease the slider.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
EeZeEpEe said:
Exactly. 50% before was definitely not 50% nits output for the screen which, with a rated max 403 by anandtech, would be only 201.5 nits. And that was before the November update that lowered the max by 50 nits.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Doesn't really bother me. My normal brightness is now just like 60% instead of around 20%. Not sure why some freaked out about it.
galaxys said:
Lol, not sure what they're Smoken at Google headquarters...
Click to expand...
Click to collapse
The same shìt as the retards who designed the P3XL.
I've configured my screen brightness to maximum and disabled "Adaptive Brightness" and "Comfort Tone".. Despite this, the device "decides" from time to time to reduce brightness.. How can I resolve this? I want brightness to be on maximum all the time no matter what..
I'm guessing that is does this because it's bad for the device to have full brightness on all the time.
First of all, why would you want to be on max brightness ? It will hurt your eyes in the dark, drain your battery and it may cause burn-in in long term.
Anyway, to answer your question, it reduces its brightness probably because of heating. An higher brightness means a higher temperature. To solve that, it may be possible to do that via magisk but i've never heard of something like this. Or you could try some custom roms that don't include that type of software cooling system.
Klbgr said:
First of all, why would you want to be on max brightness ? It will hurt your eyes in the dark, drain your battery and it may cause burn-in in long term.
Anyway, to answer your question, it reduces its brightness probably because of heating. An higher brightness means a higher temperature. To solve that, it may be possible to do that via magisk but i've never heard of something like this. Or you could try some custom roms that don't include that type of software cooling system.
Click to expand...
Click to collapse
Thanks! When the brightness gets low it hurts my eyes.. On my smasung galaxy s21 ultra, it never reduces brightness.. Why? simply because that's what I choose. It seems that oneplus would not let me choose to work with high brightness all the time.
dilgit said:
Thanks! When the brightness gets low it hurts my eyes.. On my smasung galaxy s21 ultra, it never reduces brightness.. Why? simply because that's what I choose. It seems that oneplus would not let me choose to work with high brightness all the time.
Click to expand...
Click to collapse
Oh i see. Isn't this related to DC dimming ? If so some custom roms may support that.
dilgit said:
Thanks! When the brightness gets low it hurts my eyes.. On my smasung galaxy s21 ultra, it never reduces brightness.. Why? simply because that's what I choose. It seems that oneplus would not let me choose to work with high brightness all the time.
Click to expand...
Click to collapse
Low brightness doesn't harm your eyes. It may cause muscle strain because you can't focus properly; harmless.
Full brightness can demage your retina over time especially viewing it in a dark environment.
Full brightness will greatly decrease the display lifespan of a AMOLED.
The blue pixels die first.
Use manual brightness control and try to limit it to no more than needed, 50% or less is best.
Do not use in direct sunlight for more then a few seconds.
blackhawk said:
Low brightness doesn't harm your eyes. It may cause muscle strain because you can't focus properly; harmless.
Full brightness can demage your retina over time especially viewing it in a dark environment.
Full brightness will greatly decrease the display lifespan of a AMOLED.
The blue pixels die first.
Use manual brightness control and try to limit it to no more than needed, 50% or less is best.
Do not use in direct sunlight for more then a few seconds.
Click to expand...
Click to collapse
This is very annoying.. The fact that the device won't let me use full brightness all the time
dilgit said:
This is very annoying.. The fact that the device won't let me use full brightness all the time
Click to expand...
Click to collapse
It's a bug, i've same problem, it lowers brightness by itsself! Me too have all disabled, annoying bug.
brunochka said:
It's a bug, i've same problem, it lowers brightness by itsself! Me too have all disabled, annoying bug.
Click to expand...
Click to collapse
Except it's not a bug. It's a feature. More likely multiple features designed to improve the health and longevity of the device. That said, I'm all for individual choice. If a user really wants to risk damage to their device as well as their own vision, they should be free to do so. It does make sense, however, that such an option wouldn't be in plain sight in the Settings app.
Have you tried any 3rd party apps that support High Brightness Mode/HBM? Most will probably require root since HBM is a hardware-level setting (brighter than just moving the slider to max). I don't know if there's a way to do it more permanently with adb or not.
Klbgr said:
First of all, why would you want to be on max brightness ? It will hurt your eyes in the dark, drain your battery and it may cause burn-in in long term.
Anyway, to answer your question, it reduces its brightness probably because of heating. An higher brightness means a higher temperature. To solve that, it may be possible to do that via magisk but i've never heard of something like this. Or you could try some custom roms that don't include that type of software cooling system.
Click to expand...
Click to collapse
Custom roms are always dimmer than OxygenOS, have you never noticed this?
On OxygenOS I can have my brightness at 50% and see the phone fine, on custom roms I need to have it around 75-80% to get the same brightness
djsubterrain said:
Custom roms are always dimmer than OxygenOS, have you never noticed this?
On OxygenOS I can have my brightness at 50% and see the phone fine, on custom roms I need to have it around 75-80% to get the same brightness
Click to expand...
Click to collapse
Don't know, I haven't tried custom roms yet on my 9 Pro. But I remember it was like you said on my 5T.
Hello, is the phone still having problems with the green screen in low brightness? As is the case with the s20 series?
adek89 said:
Hello, is the phone still having problems with the green screen in low brightness? As is the case with the s20 series?
Click to expand...
Click to collapse
I did not encounter a problem like that (snap version).
KlemenC said:
I did not encounter a problem like that (snap version).
Click to expand...
Click to collapse
and what does the issue of overheating look like? instagram, browser, yt?
adek89 said:
and what does the issue of overheating look like? instagram, browser, yt?
Click to expand...
Click to collapse
no overheating problems...
It is true that i have debloated it, and have most apps on deep sleep (except mail and few other), so i limit background activity.
I also use "galaxy max hz" mod so i can force low refresh rate and batery saving on screen off.
Thank you very much. I'm thinking about s20fe and 21fe. However, when I watch yt and see what are the temperatures or the results on the battery, it rejects me a bit
I understand. I moved to s21 FE from upper mid range galaxy a8 (2018). I i would say that battery efficiency on s21 fe is a bit lacking. I am not a power user so with the old phone i needed to charge oproximately every 5 days. With this one optimised as best i could i reach 3 days, maybe 4. I know that it has bigger screen and faster refresh rate and those things impact battery life a lot, but i would say that snap 888 has an inefficient standby or the low power cores are still too power hungry for my taste...
Don't get me wrong i love the phone, and am happy that i switched. The main reason for me was getting an upper range camera sistem at a low as possible price, and i bought the phone through a samsung trade in program. Also in europe it is realy hard to get any galaxy phone with a snapdragon procesor...
Hope this helps you in deciding.