Database Info

Pixel colors and power use

Im trying to find a theme that is efficient and uses low power. I read that there are certain pixel colors that use less energy then other colors.
As an example it uses more energy to produce white pixels then it does to produce black pixels.
I have a SGS vibrant and im trying to determine a good theme that uses low energy ... like black froyo but I want to know if there are other colors that are better in color use then all black.
Sent from my SGH-T959V using XDA Premium App

Each pixel is represented by 3 subpixels. Each one is 8bit number. The lower the numbers of each subpixel, the lower power used to display pixel and darker colour (You can check it in gimp or photoshop ). But be aware that darker colours won't give You noticeable power savings. More You can achieve by reducing brightness.
Sent from my GT-I5700 using XDA App

sgtGarcia[PL] said:
Each pixel is represented by 3 subpixels. Each one is 8bit number. The lower the numbers of each subpixel, the lower power used to display pixel and darker colour (You can check it in gimp or photoshop ). But be aware that darker colours won't give You noticeable power savings. More You can achieve by reducing brightness.
Sent from my GT-I5700 using XDA App
Click to expand...
Click to collapse
I know that its not going to be a noticible change in power consumption but anything helps when you use your phone in excess of heavily.
I was also reading an article (I think it was done by google) about subpixels. They were cutting out or shutting off specific ranges. Since each pixel has an RGB subpixel structure they would run a power test that eliminated the B from the RGB so only RG showed. Or if the subpixels value was above a certain amount to "Kill It".
Do.you know if there's any app's that allow you to reproduce this subpixel killing?
Sent from my SGH-T959 using XDA Premium App

ironlood said:
Do.you know if there's any app's that allow you to reproduce this subpixel killing?
Click to expand...
Click to collapse
Seriously, I don't even think if I read something 'bout it.
PS. : I've checked Your phone & it got amoled screen type ( I didn't check earlier ) , that means that using darker scheme/theme will probably give You bit more than slightly improvement with battery life.

sgtGarcia[PL] said:
Seriously, I don't even think if I read something 'bout it.
PS. : I've checked Your phone & it got amoled screen type ( I didn't check earlier ) , that means that using darker scheme/theme will probably give You bit more than slightly improvement with battery life.
Click to expand...
Click to collapse
Thanks
Sent from my SGH-T959 using XDA Premium App

With LCD screens how ever, I don't think you would get any power savings at all. OLED screens use very tiny amounts of power. I'd like to see if you can get any measurable improvement.

The Radio -=[WLAN,BT,Phone]=-
WMLongLife
WMLongLife is an automatic 2G/3G band-switching solution. It will keep your device in 2G when you do not need to use 3G, and will switch to 3G automatically when you do need it. For most users, having your device in 2G uses much less battery, and thus your phone lasts longer on a single charge. 2G also usually generates less radiation than 3G........
Running on my HTC Diamond 2 WM6.1 without any problems at all
Then there is the Theme Generator to get your pixels the color you want 'm in...
don't forget to download that tool to the right <g>

Screen Resolution Change?

I saw some where that people were setting the screen resolution to run at 1920x1080 in order to get better battery. I can't seem to relocate the thread I saw it on. Anyone know how to do this?
Sent from my LG G3

You won't really get better battery life out of a lower resolution since the same amount of pixels are still being pushed. Instead, you'll probably get better performance and less lag since the cpu and gpu wont have to work as hard.
http://forum.xda-developers.com/lg-g3/general/amazing-battery-life-tweaks-t2806078

Finally figured it out. Messes up too much crap to he worth it. I'll stick to stock. Battery life is fine I suppose.
Sent from my LG G3

Is there a way to make resolution size app dependent?

It's reported that the phone come set at the FHD+ (2220x1080) resolution by default in efforts to conserve battery life.
I'm wondering if there is a way to have the phone automatically go to HQHD+ (2960x1440) when I launch my photo viewing app.
I'm a photographer and I would love to display my photos at the highest resolution possible. However I would only need it when showing my photos to others, and not running that phone at that resolution at all time.
So the ideal solution would be for the user to set a default resolution, and then have an app exception.
Or to be able to cycle through the resolution with the Bixby Button, with a overlay of the currently selected resolution that is visible for a second after you've selected the resolution.
Do you guys think there would be something like this available ?

You can most likely achieve this quite easily using Tasker.
It's an app worth buying if you like to tinker and want full automation functionality.
I currently use it for specific apps to enable GPS, set portrait/landscape, set volume, etc and I'm planning on using it to set hqhd in certain apps once my s8+ arrives.
Sent from my Nexus 6 using Tapatalk

You can do this easily with xposed and the skyOnlineHelper app.

cantenna said:
You can do this easily with xposed and the skyOnlineHelper app.
Click to expand...
Click to collapse
No xposed for Nougat (yet) and it'll still probably take quite a while..
Sent from my Nexus 6 using Tapatalk

Eddiemc said:
No xposed for Nougat (yet) and it'll still probably take quite a while..
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
If you live in the Northern hemisphere, we're hoping in time for summer vacation
Sent from my SM-G935W8 using Tapatalk

imagineandfeel said:
It's reported that the phone come set at the FHD+ (2220x1080) resolution by default in efforts to conserve battery life.
I'm wondering if there is a way to have the phone automatically go to HQHD+ (2960x1440) when I launch my photo viewing app.
I'm a photographer and I would love to display my photos at the highest resolution possible. However I would only need it when showing my photos to others, and not running that phone at that resolution at all time.
So the ideal solution would be for the user to set a default resolution, and then have an app exception.
Or to be able to cycle through the resolution with the Bixby Button, with a overlay of the currently selected resolution that is visible for a second after you've selected the resolution.
Do you guys think there would be something like this available ?
Click to expand...
Click to collapse
Personally I do not waste time trying to save battery life when charging it easy and fast I have everything maxed out all the time . If I'm paying £800 for anything I want it to be the best it can be

mattcall said:
Personally I do not waste time trying to save battery life when charging it easy and fast I have everything maxed out all the time . If I'm paying £800 for anything I want it to be the best it can be
Click to expand...
Click to collapse
Good Point, watched a battery stress test on youtube, and this thing gets great battery life. Far more than I would typically use.
But of course that was using the default resolution. However I'm hoping the higher resolution wouldn't kill battery too much more.
I wish there was a test.

Heck, an option to change resolution within the quick settings drop down would be pretty nice as well. Maybe the option exists already.

Eddiemc said:
You can most likely achieve this quite easily using Tasker.
It's an app worth buying if you like to tinker and want full automation functionality.
I currently use it for specific apps to enable GPS, set portrait/landscape, set volume, etc and I'm planning on using it to set hqhd in certain apps once my s8+ arrives.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hey, did you find a way to do that via Tasker? Cause I cant make it happen on my S9+. If you have, contact me with the process.

ONEPLUS 6 screen resolution

Hello Guys is there any way to change One plus 6 screen resolution like to change it from
1080p to 720p ??
to save battery life..:laugh:

@me said:
Hello Guys is there any way to change One plus 6 screen resolution like to change it from
1080p to 720p ??
to save battery life..:laugh:
Click to expand...
Click to collapse
8 hours of screen time already. You want more?

nabbed said:
8 hours of screen time already. You want more?
Click to expand...
Click to collapse
I always get 4:30 or at most 5 hours of screen on time!!
how U get 8 !! even 6 is impossible for me

@me said:
I always get 4:30 or at most 5 hours of screen on time!!
how U get 8 !! even 6 is impossible for me
Click to expand...
Click to collapse
OxygenOS 9.0.2, and latest blu_spark kernel with blu_schedutil governor, i can go around 9h SOT, but in normal daily usage i get around 5h30 with 36h standby, you gotta watch what's running on your phone

Totone56 said:
OxygenOS 9.0.2, and latest blu_spark kernel with blu_schedutil governor, i can go around 9h SOT, but in normal daily usage i get around 5h30 with 36h standby, you gotta watch what's running on your phone
Click to expand...
Click to collapse
Nice :laugh:

@me said:
Nice :laugh:
Click to expand...
Click to collapse
One thing i saw is you start to get good battery life when you don't think about it anymore Just stock, with maybe a custom kernel (blu_spark and Franco are amazing), and you get very good results !
By the way, regarding your OP, on LG G3, is always used it at 1080p instead of 1440p. It was smoother (the S801 had trouble at this time), but battery was exactly the same ! You shouldn't worry about it, Snapdragon 625 devices drive 1080p without problems.

Totone56 said:
One thing i saw is you start to get good battery life when you don't think about it anymore Just stock, with maybe a custom kernel (blu_spark and Franco are amazing), and you get very good results !
By the way, regarding your OP, on LG G3, is always used it at 1080p instead of 1440p. It was smoother (the S801 had trouble at this time), but battery was exactly the same ! You shouldn't worry about it, Snapdragon 625 devices drive 1080p without problems.
Click to expand...
Click to collapse
I agree. When you think about it too much I think you set high expectations and when they are not met, you feel as though your phone has terrible battery life. I used to think 3.5-4 hrs SOT was really bad for a modern phone but that very comfortably gets me through my normal day. So I'm happy with that kind of performance since I charge up once every 18-30 hours.
Sent from my ONEPLUS A6003 using Tapatalk

daniel4653 said:
I agree. Wheb you think about it too much I think you set high expectations and when they are not met, you feel as though your phone has terrible battery life. I used to think 3.5-4 hrs SOT was really bad for a modern phone but that very comfortably gets me through my normal day. So I'm happy with that kid of performance since I charge up once every 18-30 hours
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Exactly. And tweaking too much sometimes have a negative effect.
And when i forget about it, i find that the battery life is almost always better after 3-4 days on "normal use", and by that i mean not using the phone with battery in mind. Ex : Browsing Facebook for 5mn and killing the app vs using it for 10 or 15mn, answering two emails, and locking the phone ... At the end of the day, the second scenario corresponds to an average of 1h more SOT, but battery is only 3/4% less, so in fact, stats are way better ... Killing apps, underclocking, preventing background activity ... All of this gives more battery in very specific situations, but in normal usage, it kills it (taks take longer, apps refresh with 10x more work when you open them, some like Facebook freak out when restricted by things like Greenify ...).
In short : Let the device do it's thing, maybe just cut things you'll never use or don't want (Bloat, services, ect), maybe switch kernels without tweaking too much, then forget about it.

All Browsers destroy my battery

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