Related
Hi, I recently got a data plan for my vogue and signed in to thr Google account, as well as downloaded a few apps. What I find is that without even touching my phone my battery drains dramatically (about half way in four hours). I had data enabled before, it's just that I never used it. Anybody know why this is?
Data sync is off, and background data is off as well.
Sent from my T-Mobile myTouch 3G using the XDA mobile application powered by Tapatalk
manifest3r said:
Hi, I recently got a data plan for my vogue and signed in to thr Google account, as well as downloaded a few apps. What I find is that without even touching my phone my battery drains dramatically (about half way in four hours). I had data enabled before, it's just that I never used it. Anybody know why this is?
Data sync is off, and background data is off as well.
Sent from my T-Mobile myTouch 3G using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
how old is your battery?
almost 2 years old now, I know that takes a toll too...
Sent from my T-Mobile myTouch 3G using the XDA mobile application powered by Tapatalk
Currently the phone runs at full clock speed all the time.
Back when the kernel had the clock speed and voltage reducing (late feb/early march), I used to get 48-56 hours out of the battery with data on.
Lately, over the past few weekends, I've been only able to get 36 hours. Sucks if I forget to charge my phone overnight.
These numbers are based on when the phone actually shut off due to no more power, not the battery gauge itself (it has been incorrect in the past and may still be).
Try the 2/22 kernel. See if it helps.
You'll lose features, but let me know if it improves anything. I intend to check this out in the future.
You can also open a terminal app in a current kernel and do:
Code:
su
echo 1 > /sys/module/board_htcvogue/parameters/slow_clock_when_lcd_off
echo 1 > /sys/module/pm/parameters/slow_clock_when_idle
Sleep and wake up to make it take effect. This will do the same as the 2/22 kernel.
Perhaps Myn can make this a RogueTools startup option?
NOTE:
1. This was disabled because it didn't work on some phones (caused them to freeze -- worked fine on mine).
2. Don't use this with overclocking! Bad things may result (I haven't checked the code).
jnadke said:
Currently the phone runs at full clock speed all the time.
Back when the kernel had the clock speed and voltage reducing (late feb/early march), I used to get 48-56 hours out of the battery with data on.
Lately, over the past few weekends, I've been only able to get 36 hours. Sucks if I forget to charge my phone overnight.
These numbers are based on when the phone actually shut off due to no more power, not the battery gauge itself (it has been incorrect in the past and may still be).
Try the 2/22 kernel. See if it helps.
You'll lose features, but let me know if it improves anything. I intend to check this out in the future.
You can also open a terminal app in a current kernel and do:
Code:
su
echo 1 > /sys/module/board_htcvogue/parameters/slow_clock_when_lcd_off
echo 1 > /sys/module/pm/parameters/slow_clock_when_idle
Sleep and wake up to make it take effect. This will do the same as the 2/22 kernel.
Perhaps Myn can make this a RogueTools startup option?
NOTE:
1. This was disabled because it didn't work on some phones (caused them to freeze -- worked fine on mine).
2. Don't use this with overclocking! Bad things may result (I haven't checked the code).
Click to expand...
Click to collapse
I'd love to add this to RogueTools but I am not sure if this is something that dzo will address in the kernel.
dzo: Please let me know. I don't want to step on your toes. I have no probs adding this to RogueTools but if you have plans for this I'll stay clear.
myn said:
I'd love to add this to RogueTools but I am not sure if this is something that dzo will address in the kernel.
dzo: Please let me know. I don't want to step on your toes. I have no probs adding this to RogueTools but if you have plans for this I'll stay clear.
Click to expand...
Click to collapse
Actually I have plans for this, however it won't be fixed in the near-term. You could probably add it to RogueTools for now.
I would like to get some form of cpufreq support working on the vogue. I've already talked with dzo in the past about adding cpufreq support, he didn't have much interest in implementing it.
I've never tested scientifically if these values actually make a difference. Technically, as dzo mentions, the clocks are all turned off when the device is idle (i.e. truly sleeping). However, there are cases where the clock-reducing would have an effect when linux is idling, but the processor hasn't slept yet. This would happen if an app is repeatedly waking up the device to sync.
My observations are entirely empirical. I used to get really good battery life across the board until I upgraded my kernel past 2/22 (I used that one up until late March).
I'll use the phone for a while with clock idling turned on and see if my battery life improves.
jnadke said:
Actually I have plans for this, however it won't be fixed in the near-term. You could probably add it to RogueTools for now.
I would like to get some form of cpufreq support working on the vogue. I've already talked with dzo in the past about adding cpufreq support, he didn't have much interest in implementing it.
I've never tested scientifically if these values actually make a difference. Technically, as dzo mentions, the clocks are all turned off when the device is idle (i.e. truly sleeping). However, there are cases where the clock-reducing would have an effect when linux is idling, but the processor hasn't slept yet. This would happen if an app is repeatedly waking up the device to sync.
My observations are entirely empirical. I used to get really good battery life across the board until I upgraded my kernel past 2/22 (I used that one up until late March).
I'll use the phone for a while with clock idling turned on and see if my battery life improves.
Click to expand...
Click to collapse
All the tests I have done suggest that changing the clock when the device is on has no effect on power consumption. We are lucky because the battery reports power consumption. On idle the cpu does a SWFI which stops the CPU clock (and some other clocks too). What would make a difference is implementing power collapse on idle (CPU is completely powered down just like when asleep) and I have thought about doing this. It's quite a bit of work and wince doesn't do this so perhaps it's not reliable. I might do some tests to see how much power it would save.
I've been revamping this thread for new devices for years hoping to share some of the love with newer users. Over the time I've been on android, I've learned a few simple things that can greatly assist in the battery life of our wonderful smartphones.
If you get anything out of the thread, please don't hesitate to rate it and drop me a thanks!
If you read the thread and like the tips, have a new one to suggest, or have a revision, please post it.
On a similar note, moderators, thanks for the sticky!
General Lithium Ion Battery Information - This link includes stuff about charging, including trickle charging aka SBC (Why NOT to use it, or at your own peril)
My tips for good battery life:
Tips for both Rooted and Non-Rooted users
1.Turn off all radios when not in use.
(Bluetooth, wifi, data, 4G/Wimax/LTE, NFC, etc) Use a widget like the default power widgets, Switchpro, or a similar app from the market. *Many rooted ROMs generally allows users to access these radios and other settings from the notification pulldown menu.* The radios of the phone draw power if on even if the user isn't actually utilizing the radio's functions. A radio searching for signal (if you are in a low-signal area) drains more than a radio with good signal, so again, turn 'em off when you aren't using 'em.
To manually turn off radios without a toggle, go to Settings>wireless & networks. This can be accessed from the notification pulldown and hitting the cog icon.
Wifi uses less battery than 3G, so use wifi when you can. Another important setting to note is more dependent on the user. If you live in an area without 4G LTE coverage (check here to see), then go into Settings>Mobile data>Network Mode and check CDMA Only. This will prevent your phone from unnecessarily searching for LTE coverage, which wastes a ton of battery life.
3. I love live wallpapers, and I’ve always been a fan of pixel zombies, but they are really only good for showing off due to their battery drain.
4. Set your screen timeout/brightness to something that fits you.
The screen is the highest drain of battery power on any smartphone. BY setting the timeout, you can prevent your phone from staying on when you don’t manually turn off the screen. Also, manually turn off your screen when you’re done with your phone.
Another huge tip is to turn on automatic brightness (it is enabled by default). This greatly reduces power consumption by constantly changing the brightness of your display, tailoring it to your needs.
Settings>Display, gestures & buttons>Sleep
I use 30 seconds.
4. Task killers used to be all the rage, but no longer.
Here is the ultimate, in depth, graphically assisted, explanation by the famous Fresh ROM's chef, Flipz. Shortly, in light of recent testing, really don’t do anything but force apps that the android OS needed to be open, and thus didn’t close, to re-open. So try not using them, unless for stuff like trying to figure out why your phone isn’t sleeping with system panel. You really won’t notice a performance difference, and the adverse effects you aren’t seeing will stop
+=+ A good alternative is the application SystemPanel Pro. It has a free version, but I highly reccomend purchasing the paid app. It basically monitors everything going on with your phone's usage both in real time an in terms of usage history. If your battery is draiging fast, it tells you what app was doing it, how much it was doing it, and allows you to stop it.
5. I'm sure you have all heard around that your phone isn't "sleeping".
This is referring to the phone's "awake" time, hence the name. When you go to Settings>Power>History. You can compare the lines from awake to screen on versus time on. "Time on battery" refers to the amount of time since the last reboot. The "awake time" is how long the screen has been active. The problem is, a lot of the time, due to the endless possibilities of inconsistencies between apps/ROMs/kernels/phones, the phone will not go to "sleep", drawing power proportionate to the screen being in use when it reality the phone is sitting idle.
If you compare these times and they are the same, or if you note the difference (turn off the screen for a minute, then re-check and they are the same), then your phone is not sleeping.
One solution is to reboot.
I recommend two apps to help monitor:System Panel and Better Battery Stats. These two apps (explained in their FAQ's and descriptions greatly aid in finding those rogues.
Usually, SystemPanel will show an app that has gone "rogue" and is keeping your phone awake.
-This is done by hitting menu>settings>monitoring enabled. Then after some time has passed, ht menu>monitoring>history>change tab to top apps, and see if anything is above, say, 2-4%.
Uninstall applications/reinstalling them slowly, checking after every install to see what is causing it is one tedious but surefire solution.
Lastly,
Follow these steps that I have discovered almost always work.
1. Reboot phone.
2. Instantly upon reboot, as soon as you gain control, open up some type of monitor/taskkiller
3. "kill all" tasks on startup; about 2 times in quick succession should do the trick.
4. Turn off the screen and leave it for about five minutes.
5. Check the up time v. awake time and see if they are the same.
6. If they are, repeat steps 1-5. If they are different, you are good.
6. Apps and Combinations to watch out for!
-Facebook- Tries to sync live feed all the time, HIGHLY recommend unchecking this box, as it creates a massive draw on data
-Skype- This app reportedly (I've seen it myself) likes to sync random data and open up the network for fun. Sign out of app when not in use to fix
-GTalk- This application keeps you constantly connected to all of our google contacts across of your accounts. I have several accounts that I must maintain, and by default the application had me signed in and maintaining a connection with all of them. Open GTalk, then hit each account and sign out to neutralize this puppy. Unless of course you want to stay signed in.
7. Manage your syncing.
This is a big one, and it differs from person to person. Go to Settings>Accounts and Sync, and take a look at what's going on there. Listed app titles means that there is an account syncing data. I, for example, have four email addresses, facebook, dropbox, box, weather, etc. That is bad. You should go through and turn off syncing for nasty apps you might not have known were accessing the internet, or limit the access of apps and services that you do want to allow.
The problem lies in the way this syncing is handled. Each app/service runs on its own schedule, making it particularly likely that your phone could almost always be establishing a data connection and trying to download data for your various apps. See step 2 regarding the app Juice Defender to handle this problem.
8. Vibrate/Haptic Settings
Vibration and haptic feedback eat up a surprising amount of battery. If you have the haptic feedback enabled, then every time you press anything your phone puts out some juice to make itself dance.
Settings>Sound>Vibrate on touch
Some apps have their own haptic feedback settings, and notifications are their own set entirely.
Tips for Rooted users:
1. Try out custom kernels.
By going to the Sprint HTC One Android Development section of the forums, you can see all of the different kernels being developed. These allow for all kinds of modifications like underclocking the CPU and undervolting, both of which save battery. To see how to use them, read the FAQ's in each thread's OPs.
Here is a great guide to custom kernel's by mroneeyedboh.
2. Use Rom Toolbox Pro, SetCPU, or some CPU clocking app in compliance with whatever your custom kernel allows.
This site will explain the basics of SetCPU: http://www.setcpu.com/
-Profiles from SetCPU should usually involve these for battery life optimization:
-Screen off at the minimum clock speed for both, with the max raised on level if sluggishness is apparent
-A temperature greater than “X”
-General power related profiles that lower cpu speed at lower battery levels
(Note that setcpu has fallen off of the radar, but clocking your cpu to levels that suit your needs is still viable, although many argue that the android system's core management should best be left alone. Read up for yourself and make an educated decision)
------------------------------------------------------------------------------------------------------
NOTES:
*Some apps or processes begin to run at startup and keep the phone awake. These apps are not detected by things like spare parts or system panel, unless sometimes represented in the "system" process, in which case its usage will be unusually high.
This shouldn't take more than three repeats, and if it does, you need to factory reset, and slowly add apps back to see what's causing the problem.
___----When it comes to people claiming 20 plus hours of moderate/heavy use out of their current setup or other ridiculous absurdities, consider my position: No matter what you do, the cellphone battery is the cellphone battery. You can tweak it and customize it with kernels, ROMs, and settings, but none of that will turn it into a car battery. The main problem (besides a false sense of pride) that leads to these reports is the misunderstanding of what the usage levels are, so here’s my best summary:
* *Light usage – Phone screen actually on for maybe 0-2 hours. Things like a few texts, some emails, 20 minutes web browsing, etc.
* *Moderate usage – You watched a few youtube videos or similar apps, sustained web browsing, hundreds of texts, some games. Hours range from about 2-5 of screen on
* *Heavy usage – LOTS of video watching and games, pictures or video recording, or some high def gaming/movie watching for at least an hour to an hour and a half in total, with lots of emails and texts, browsing, and other app shenanigans. 5+ hours
*I’m sure everyone doesn't agree with all these numbers, but this is most likely a good average of what powerusers think. All specific hourage may vary due to differences in phones, batteries, ROMs, and kernels… Which also means that most battery comparisons are pointless; it’s only what you can improve on that counts!
I’ll update this whenever I see good stuff, people remind me, or I remember/come across things I do.
Hope it helps everybody!
Hit the "THANKS" button if I help you!
Good thread, we need more informational threads like this.
Biofall said:
* *Heavy usage – LOTS of video watching and games, 3D pics or video, or some high def gaming/movie watching for at least an hour to an hour and a half in total, with lots of emails and texts, browsing, and other app shenanigans. 5+ hours
Click to expand...
Click to collapse
This isn't the Evo 3d forum Bio . Good to see another 3vo user around these parts haha.
Stickied for the time being
demo27vol1 said:
This isn't the Evo 3d forum Bio . Good to see another 3vo user around these parts haha.
Click to expand...
Click to collapse
Haha yep!
Nice catch though, there was a lot there to change.
Hello Biofall,
I was wondering how effective is the Snapdragon BatteryGuru app from qualcomm vs juice defender if you ever tried that app before? I have used juice defender with my EVO 3D but I didn't liked the that the app was turning off Wimax even tough my phone was charging while using it.
Not only are we fighting the screen. We are fighting the quad core processor. It seems to be very aggressive.
Sent from my HTCONE using Xparent Blue Tapatalk 2
Well done.
treIII said:
Not only are we fighting the screen. We are fighting the quad core processor. It seems to be very aggressive.
Sent from my HTCONE using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
It's aggressive when it feels the need to ramp up. When installing several apps, the damn thing actually gets hot to the point where I put it in the freezer. [edit: this is dumb according to the device's thermal protection] I know that the components shouldn't be reaching those temps....
I'm on the lookout for more info on explicit effects of the quad core on battery life and direct ways to combat it.
eXplicit815 said:
Well done.
Click to expand...
Click to collapse
Thanks! I've been scouring for empirical info for years and I owe a lot of thanks to other people.
Turn off Juice defender. In fact, uninstall it. You will see your battery life is actually improved.
Leave the quad core component alone. If the cores aren't being used, they're offline. Offline is essentially 0 power consumption. The only case I can see improving battery by disabling cores would be for games. Otherwise, its probably detrimental.
Felnarion said:
Turn off Juice defender. In fact, uninstall it. You will see your battery life is actually improved.
Leave the quad core component alone. If the cores aren't being used, they're offline. Offline is essentially 0 power consumption. The only case I can see improving battery by disabling cores would be for games. Otherwise, its probably detrimental.
Click to expand...
Click to collapse
Juice defender has a large multitude of components. If some parts use more power for you, then you should post which of them you believe they were, before and after, possibly with battery graph screenshots.
On the last quad-core device that I had used there was a problem where the cores would ramp up unnecessarily for small tasks, so there is certainly a possibility for improvement.
On an unrelated note, there are other things that I want to add to this thread, including screenshots, so if anyone has anything to add, just tell me.
What I don't get is that a lot people seem to believe they know better than HTC's engineers. Doing things like forcing off cores, how do you know that's really saving power? For all you know, the power loss of enabling an extra core for a small task is insignificant to ramping up an already active core to do the same thing.
Sure there are some things you can do to improve power usage (such as avoiding wakelocks) but if you start changing numbers for how internal software power functions work, you should have some damn good reasons why. Even a graph isn't going to be terribly accurate unless you can substantiate the gains across multiple tests. Many of the improvements people mention often have an impact of less than 1% over the course of an entire charge, and that's nearly impossible to even measure. The battery percentage indicator is only an estimation and not only varies between device, but even varies based on the temperature!
Vincent Law said:
What I don't get is that a lot people seem to believe they know better than HTC's engineers. Doing things like forcing off cores, how do you know that's really saving power? For all you know, the power loss of enabling an extra core for a small task is insignificant to ramping up an already active core to do the same thing.
Sure there are some things you can do to improve power usage (such as avoiding wakelocks) but if you start changing numbers for how internal software power functions work, you should have some damn good reasons why. Even a graph isn't going to be terribly accurate unless you can substantiate the gains across multiple tests. Many of the improvements people mention often have an impact of less than 1% over the course of an entire charge, and that's nearly impossible to even measure. The battery percentage indicator is only an estimation and not only varies between device, but even varies based on the temperature!
Click to expand...
Click to collapse
Sure man, sure. There are surely negatives associated with turning off, down, or generally altering core performance. However, taking the decisions that HTC engineers coupled with HTC software designers implemented for mass consumption as the best option for all users is foolish. The reason we have a development community revolves around that concept.
Several of the things I talk about have an impact in terms of hours the device can function without being plugged into an outlet, which has little to nothing to do with battery percent levels.
Sent from my HTC ONE using xda premium
Edited
Biofall said:
Sure man, sure. There are surely negatives associated with turning off, down, or generally altering core performance. However, taking the decisions that HTC engineers coupled with HTC software designers implemented for mass consumption as the best option for all users is foolish. The reason we have a development community revolves around that concept.
Several of the things I talk about have an impact in terms of hours the device can function without being plugged into an outlet, which has little to nothing to do with battery percent levels.
Click to expand...
Click to collapse
Battery percent or how long the device is on is still a hard comparison to make.
You could do the EXACT SAME THING on the phone twice, from full charge to dead, and you'd get a different length of time. Batteries aren't that consistent.
A couple things that bother me:
1. You stick the phone in the freezer because it gets warm. The phone already has thermal protections that keep it from overheating. The CPU can deal with far greater heat than you know (70C isn't even a problem). Anandtech was able to run it through the entire gauntlet of its tests (which are much harder on the device than just installing apps) without it ever triggering thermal protection. Most thermal protections exist solely for the battery's sake, which in itself can deal with 50C while charging, or even higher when not.
2. In almost all cases, it is better to let the CPU drive itself as fast and as hard as possible in order to finish tasks. Let it turn on all the cores and such. Because once it's done, it can go back into deep sleep, where everything is off. This is why almost all phones, not just HTC ones, are designed to do just that.
I agree with Felnarion's sentiment. Juice Defender is probably wasting more power just measuring your battery usage than it is helping you save.
Edited
Originally Posted by Biofall
Sure man, sure. There are surely negatives associated with turning off, down, or generally altering core performance. However, taking the decisions that HTC engineers coupled with HTC software designers implemented for mass consumption as the best option for all users is foolish. The reason we have a development community revolves around that concept.
Several of the things I talk about have an impact in terms of hours the device can function without being plugged into an outlet, which has little to nothing to do with battery percent levels.
Click to expand...
Click to collapse
Battery percent or how long the device is on is still a hard comparison to make.
You could do the EXACT SAME THING on the phone twice, from full charge to dead, and you'd get a different length of time. Batteries aren't that consistent.
A couple things that bother me:
1. You stick the phone in the freezer because it gets warm. The phone already has thermal protections that keep it from overheating. The CPU can deal with far greater heat than you know (70C isn't even a problem). Anandtech was able to run it through the entire gauntlet of its tests (which are much harder on the device than just installing apps) without it ever triggering thermal protection. Most thermal protections exist solely for the battery's sake, which in itself can deal with 50C while charging, or even higher when not.
2. In almost all cases, it is better to let the CPU drive itself as fast and as hard as possible in order to finish tasks. Let it turn on all the cores and such. Because once it's done, it can go back into deep sleep, where everything is off. This is why almost all phones, not just HTC ones, are designed to do just that.
I agree with Felnarion's sentiment. Juice Defender is probably wasting more power just measuring your battery usage than it is helping you save.
Click to expand...
Click to collapse
You could do the same thing and get different results, but in reality strong trends in usage are reflected in battery life.
As for this the CPU discussion, all that I said was that I'd like to look at more in depth studies or core process handling. So it bothers me too.
In regards to JD, it won't be making it into the next revision of the thread, as I have noticed unnecessary draw. Honestly android implemented most of the vital operations into the OS, so it is mostly useless coupled with the other tips and just general awareness.
Finally, the xda app is acting up, sorry for the clutter.
Sent from my HTCONE using xda premium
Thanks for the write up. I went from being a little unimpressed by battery life to blown away. Biggest saver from stock is dropping all the SYNC stuff. Totally unnecessary IMO. If you aren't consuming the news and updates (you know actually in the app), you probably don't need it refreshing. Still baffles me this is the from-the-factory type setup.
Phone used to eat 5-10% of my charge per hour with light use and barely make it through my "day" (~15hr away from charger). Now, after 6hrs. since it's been off the charger, I'm still at 91%.
Kill LTE and go to CDMA only if you don't have it in your area either, or it's still rolling out. Seemed to help too.
EDIT: And I should note my scores are with never letting the Data Connection completely sleep, so I can still get emails as they come in which I find important.
---------- Post added at 01:44 PM ---------- Previous post was at 01:17 PM ----------
Here's another tip: Go into Google Talk and make sure to sign yourself out if you don't use/care for the service.
Lauski said:
Thanks for the write up. I went from being a little unimpressed by battery life to blown away. Biggest saver from stock is dropping all the SYNC stuff. Totally unnecessary IMO. If you aren't consuming the news and updates (you know actually in the app), you probably don't need it refreshing. Still baffles me this is the from-the-factory type setup.
Phone used to eat 5-10% of my charge per hour with light use and barely make it through my "day" (~15hr away from charger). Now, after 6hrs. since it's been off the charger, I'm still at 91%.
Kill LTE and go to CDMA only if you don't have it in your area either, or it's still rolling out. Seemed to help too.
EDIT: And I should note my scores are with never letting the Data Connection completely sleep, so I can still get emails as they come in which I find important.
---------- Post added at 01:44 PM ---------- Previous post was at 01:17 PM ----------
Here's another tip: Go into Google Talk and make sure to sign yourself out if you don't use/care for the service.
Click to expand...
Click to collapse
Solid tips man. Will update the OP. I always forget to change my mobile data to CDMA only. Also, I had three accounts signed into gtalk, which was unnecessary.
Biofall,
Nice thread.. Very very nice.
The battery issue --
When it comes to people claiming 20 plus hours of moderate/heavy use out of their current setup or other ridiculous absurdities
Click to expand...
Click to collapse
While I actually agree with what you say I do feel a bit different. I base mine on previous usage.
My days really fall into one of three areas. When you get old like me you will see your days are all about the same. :crying: My heavy use is going to be someone else light day.
For me I can judge based on different phones, kernels and roms. The 4g days I needed to have a charger at my desk. There was no way I could get through a whole day regardless of how many calls I made.
Now I am judging verse the LTE I had and and very surprised on how well its holding up even on
my
Click to expand...
Click to collapse
heavy days.
Have you had time to try this yet? http://forum.xda-developers.com/showthread.php?t=2230403
Not sure it works, like you said some of these apps just use more than they save. I am going to see what happens over the next few days and see if I can see differences.
Your Facebook and sync statement, man do those hit home! I still have a few phones at work that these guys don't get it.
Gtalk.. beh turns on when you flash a new rom.. People have to remember to go back and shut that sucker off!
Thanks for your post, I am going to show a few people this, maybe it will open their eyes.
Hello everyone, im here to share my future experiences with seeing just how far i can push my battery and share how i did it with everyone.
Backstory:
I'm going hiking in Virginia tomorrow for a week, and would really like to have a camera without carrying extra devices, so..... its time to mod my nexus 5 as low power as possible!
here are some of the "prep steps" that ive done in order to obtain my battery life, i'll update the thread to let everyone know how it worked out!
Rooted
CM stable installed. (up to date as of this post)
Screen Brightness set to low as possibe.
Elemental X Kernel installed (Using TricksterMOD, these are my settings)
Multicore power saving = 2
CPU Freq. Lock= Min( 652800) Max( 652800) Max.screen off(300mhz)
Google Now/voice anything turned off
Home screen has only one page
Airplane Mode
Greenify Installed, Using Xposed Module for advanced/better control
Hibernating almost everything 3rd party, esp things like Facebook,KiK etc.)
BootManager xposed module installed, everything disabled that isn't needed.
Installed gsam for more meaningful data logging.
Unchecked Auto Sync Data in the Data Usage settings
Changed CPU clock min/max 652800
Installed Deep sleep battery saver Xposed module. (on slumber profile) buts phone into deep sleep when screen is off.
If i remember anything else i did on here, i'll post it.
(sorry its taking so long for replies/updates, "new user status" prevents my posts 5 minutes in between.) (hard to believe, been a member since 2011, just lurked alot.)
*May have found lower limit on the CPU, no instability as of yet, however phone is acting a bit erratic, looking into this currently. (booting takes FOREVER. this is a problem.)
*Trickster seems to pick and choose sometimes whether it wants to listen to me, sometimes CPU freq. on sreen off is changing to 652800 on its own. :/ anyone know of a way to get it to respect my settings?
*Changed CPU freq. to min max 652800 based on advice of the community.
Usage scenario:
I'll be using my phone mainly for pictures throughout the trip and possibly listening to some music, anytime its not in use, ill be turning it outright off, however, id really like to see just how far i can take this.
Anyone have any other suggestions for longevity?
gh0stpirate said:
Hello everyone, im here to share my future experiences with seeing just how far i can push my battery and share how i did it with everyone.
Backstory:
I'm going hiking in Virginia tomorrow for a week, and would really like to have a camera without carrying extra devices, so..... its time to mod my nexus 5 as low power as possible!
here are some of the "prep steps" that ive done in order to obtain my battery life, i'll update the thread to let everyone know how it worked out!
Rooted
CM stable installed. (up to date as of this post)
Screen Brightness set to low as possibe.
Elemental X Kernel installed (Using TricksterMOD, these are my settings)
Multicore power saving = 2
CPU Freq. Lock= Min(960000) Max(stock) Max.screen off(157440)
Google Now/voice anything turned off
Home screen has only one page
Airplane Mode
Greenify Installed, Using Xposed Module for advanced/better control
Hibernating almost everything 3rd party, esp things like Facebook,KiK etc.)
BootManager xposed module installed, everything disabled that isn't needed.
If i remember anything else i did on here, i'll post it.
Usage scenario:
I'll be using my phone mainly for pictures throughout the trip and possibly listening to some music, anytime its not in use, ill be turning it outright off, however, id really like to see just how far i can take this.
Anyone have any other suggestions for longevity?
Click to expand...
Click to collapse
Don't forget Google Now and Auto Syncs. (uncheck Auto Sync Data in the Data Usage settings).
Check out this thread here for some more suggestions.
I've been able to push it pretty far even with an active internet connection, though most of the usage comes from reading Reddit or forums with Tapatalk. That was on stock with no root access.
It's possible that it will take less power to just put your phone to sleep when not using than booting it up every time you need it. Depends on how often you boot though.
bblzd said:
Don't forget Google Now and Auto Syncs. (uncheck Auto Sync Data in the Data Usage settings).
Check out this thread here for some more suggestions.
I've been able to push it pretty far even with an active internet connection, though most of the usage comes from reading Reddit or forums with Tapatalk. That was on stock with no root access.
Click to expand...
Click to collapse
Thanks for the tips! heres what i changed:
installed gsam for more meaningful data logging.
unchecked Auto Sync Data in the Data Usage settings
changed CPU clock min/max 300mhz
Zainiak said:
It's possible that it will take less power to just put your phone to sleep when not using than booting it up every time you need it. Depends on how often you boot though.
Click to expand...
Click to collapse
I was thinking that as well, however it would be difficult to find that "mid point" if i had an emergency backup of battery bank to test this theory, i would. However, im going to be stuck in the mountains and would rather have the ability to take the pictures i want rather then pure data log expedition. Great insight/hivemind though.
gh0stpirate said:
I was thinking that as well, however it would be difficult to find that "mid point" if i had an emergency backup of battery bank to test this theory, i would. However, im going to be stuck in the mountains and would rather have the ability to take the pictures i want rather then pure data log expedition. Great insight/hivemind though.
Click to expand...
Click to collapse
Based off my experiments, it takes less than 1% of battery to reboot the phone though I would guess somewhere in the 0.5% range. In airplane mode with all of these functions disabled and in deep sleep, 1% would probably get you 6 hours of idle time or even more. Therefore I would only power it down if you won't be using the phone for at least the next 6 hours. Rough estimations of course, I think either way it would be pretty similar.
If the phone is not powered down you might be inclined to use more than you would otherwise.
bblzd said:
Based off my experiments, it takes less than 1% of battery to reboot the phone though I would guess somewhere in the 0.5% range. In airplane mode with all of these functions disabled and in deep sleep, 1% would probably get you 6 hours of idle time or even more. Therefore I would only power it down if you won't be using the phone for at least the next 6 hours. Rough estimations of course, I think either way it would be pretty similar.
If the phone is not powered down you might be inclined to use more than you would otherwise.
Click to expand...
Click to collapse
Extremely interesting/relevant! do you still have any screenshots or data logs on these restarts anymore?? if thats the case, then yes, id only turn it off while im sleeping then!
gh0stpirate said:
Extremely interesting/relevant! do you still have any screenshots or data logs on these restarts anymore?? if thats the case, then yes, id only turn it off while im sleeping then!
Click to expand...
Click to collapse
Unfortunately I do not, just speculation based off what I've seen when monitoring current draw (using Current Widget) and the battery percentage before and after a reboot.
I do have shots demonstrating low idle drain with Auto Syncs and Locations disabled. On average I'd say my drop is about 1% over 5 hours of deep sleep, but it's always hard to tell because there's no way for me to know exactly when it drops without active logging which would interfere with the phone's deep sleep.
Generally speaking a reboot uses ~1% of your battery. If you're locking your CPU to run at only 300mhz I would just leave it on the entire time. Especially if mobile data is off and so is WiFi. Make sure you go into Settings > WiFi > *Touch the 3-dot menu* > Advanced > Disable "Scanning Always Available". I lose about 1-2% in airplane mode overnight over clocked with high quality sound driver from Viper4Android. Plus the Google now hotword activated everywhere but lock screen.
A while back I did a test with my N5 to purposely nerf its power to see how long of a SoT I could get with it. I did pretty much everything you mentioned in the OP. Locked max CPU frequency to match min. Lowest screen brightness, airplane mode, etc. I was able to get over 12 hours SoT. So if the N5 can get 12 hours with the screen on using the same setup you plan in using with the phone getting nice and warm... I don't think a week standby time is too farfetched as long as it's idle most of the time except for pictures. Depends on how much music you listen to I guess. Only problem is even with music saved on the device itself, running at 300mhz you're going to run into skips and pops. Especially when the screen is off. Music playback will be kinda iffy.
Good luck though and let us know how it goes.
Edit: Actually I was mistaken. I just disabled everything like location, sync, etc. Default kernel parameters except switching to ondemandplus governor. This was on an older release of Uber kernel. 12+ hours SoT with ~30% battery remaining!
Here's my post;
http://forum.xda-developers.com/showthread.php?p=52133394
You'll suffer Lag I would think with CPU at 300mhz max. And likely use more battery than your saving with the phone struggling to process anything.
May have instability issues too. I'd rethink that.
KJ said:
You'll suffer Lag I would think with CPU at 300mhz max. And likely use more battery than your saving with the phone struggling to process anything.
May have instability issues too. I'd rethink that.
Click to expand...
Click to collapse
I agree, but I think that if the phone isn't used at all besides some pictures here and there, it should be fine. If he plans on music playback he's going to have to raise the max frequency, no question. Music playback won't work reliably that low. I don't think lag will be an issue for him considering what's he's trying to accomplish with the phone, but I can't speak to instabilities with 300mhz as max as I've never tried it.
RoyJ said:
I agree, but I think that if the phone isn't used at all besides some pictures here and there, it should be fine. If he plans on music playback he's going to have to raise the max frequency, no question. Music playback won't work reliably that low. I don't think lag will be an issue for him considering what's he's trying to accomplish with the phone, but I can't speak to instabilities with 300mhz as max as I've never tried it.
Click to expand...
Click to collapse
Currently Using Apollo music player, can confirm Zero issues using music playback, confirmed CPU freq. using cpu frequency app. most of these things are using hardware decoders
RoyJ said:
I agree, but I think that if the phone isn't used at all besides some pictures here and there, it should be fine. If he plans on music playback he's going to have to raise the max frequency, no question. Music playback won't work reliably that low. I don't think lag will be an issue for him considering what's he's trying to accomplish with the phone, but I can't speak to instabilities with 300mhz as max as I've never tried it.
Click to expand...
Click to collapse
But if the phone is sleeping soundly as it should.... The max CPU is irrelevant if not being used. The lag and strain to run processes may hurt a lot though.
You let the music play while the screen was off for a few minutes or did you just play it for a few seconds? I have music stutter on screen off with frequencies higher than 300mhz. I get it with 729mhz. If it doesn't happen to you, awesome. Not sure why though. Do you have time to purchase an OTG charger? Might be worth looking into and they aren't that expensive.
http://www.amazon.com/Best-Sellers-...-Phone-Battery-Packs/zgbs/wireless/7073960011
Currently listening with screen off/on full songs. No issues. no time to purchase an OTG charger however :/
Updated main post to reflect newest enhancements.
Trickster seems to pick and choose sometimes whether it wants to listen to me, sometimes CPU freq. on sreen off is changing to 652800 on its own. :/ anyone know of a way to get it to respect my settings?
It can be done
Sent from my Nexus 5 using XDA Free mobile app
I seem to remember a thread somewhere on xda regarding a CPU's "race to finish". Basically a cpu will work as much as it can (or better said "is allowed) to finish each task after which go to a low power state, like a marathon runner accelerates on certain portions and then "coasts" to conserve energy or a a car running on a near empty gas stank. Since you have a couple of days left I would try raising the frequency (600,800 and 1000) and see what happens to the power drained. It would definitely help with usability, as well as enable using photosphere or panorama ( which take quite a few seconds even at full speed to process) if needed. If the power drain would increase by less than 10% I would call that an acceptable trade-off.
While there is nothing wrong with finding the limit of your device, I think that an external battery pack would be a much better solution. There are ones available for less than $20 that could fully charge your device twice,
Flukzr said:
I seem to remember a thread somewhere on xda regarding a CPU's "race to finish". Basically a cpu will work as much as it can (or better said "is allowed) to finish each task after which go to a low power state, like a marathon runner accelerates on certain portions and then "coasts" to conserve energy or a a car running on a near empty gas stank. Since you have a couple of days left I would try raising the frequency (600,800 and 1000) and see what happens to the power drained. It would definitely help with usability, as well as enable using photosphere or panorama ( which take quite a few seconds even at full speed to process) if needed. If the power drain would increase by less than 10% I would call that an acceptable trade-off.
While there is nothing wrong with finding the limit of your device, I think that an external battery pack would be a much better solution. There are ones available for less than $20 that could fully charge your device twice,
Click to expand...
Click to collapse
I remembered a discussion along those lines, ill bump the freq. to 652800 min max, and update the main post. An external pack would be great, but i unfortunately just don't have the cash at the moment. between the trip and i just ordered a triple monitor stand and a new wifi usb to play with nethunter
gh0stpirate said:
Screen Brightness set to low as possibe.
Airplane Mode
Click to expand...
Click to collapse
This is basically all you need, the phone will idle for a week or so in airplane mode.
Hello Everyone! My phone has been wonky and I gotta know why
SO my N6 likes to shut off in the middle of doing something, most notably using google maps and the camera, I did some searching and someone suggested its related to the phone using apps that require location (Google Maps GPS / Google Camera Save Location Option), but there wasn't much input on that thread. Have any of you encountered anything like this yourselves? My phone would whir after opening Maps or after taking a picture from Camera (the whir sounds like its coming from near the top part of the phone btw) and then it would shut off, anyone have any clues as to what's the problem?
Yup same here for a long time. It's not related to location.
It's definitely something with voltage and battery.
I'm compiling my kernel and I've tried many things.
1/ Bcl needs to be on.
2/It's happening only on high cpu load. And so with camera and gps active.
Because those will use more voltage from our poor Motorola battery.
Using os monitor I've see my battery go to 3800mv from 3500 without big problem but clearly below 3600 there's a chance for the phone to shut down as you describe the thing.
Bcl start limiting and hotpluging core when battery reach 3800mv.
The default value is 1.9 ghz
But on stock kernel the phone is limited at 1.7. I think it's mpdecision and/or thermal that doing this. But I'm not sure.
Anyway nexus 6 is not made to handle 4 cores at the same time on low battery. + camera gps Bluetooth etc...
So voltage can drop to 3800mv to 3600 and then go back to 3800 because there's voltage work on kernel and rom side to prevent those things.
For exemple I've see my phone after unlocking it. Coming back to home. Have 3500mv and then after one minute. Come back to 3700.
So maybe WiFi and cpu was using the maximum voltage they could to sync then when job was over. Go back to a normal voltage use.
Not every phone are affected.
Cpu binning level is important i think.
Mine is 7.
0 use the maximum voltage and 15 the minimum.
I've use a pvs 5 phone and problem was the same with my kernel. So I've changed some stuff and it worked.
So for me my battery is bugged. I mean on low mv battery send bad info and doesn't have enough juice.
I've try rma my phone but Google send me a refurbish phone (the pvs5 one) which have screen burning on it. Yes they send me phone with a navbar stuck....
So I've send them back and I'm planning to change the battery myself
In the hope it solve the problem.
Also my turbo charger make a weird noise when phone battery is full. So maybe my charger have always be bugged and broke the battery in some way.
I'm still trying to understand this. But it's what I've test and understand from this. More or less because I've probably forgot something in there
dynamo147 said:
Hello Everyone! My phone has been wonky and I gotta know why
SO my N6 likes to shut off in the middle of doing something, most notably using google maps and the camera, I did some searching and someone suggested its related to the phone using apps that require location (Google Maps GPS / Google Camera Save Location Option), but there wasn't much input on that thread. Have any of you encountered anything like this yourselves? My phone would whir after opening Maps or after taking a picture from Camera (the whir sounds like its coming from near the top part of the phone btw) and then it would shut off, anyone have any clues as to what's the problem?
Click to expand...
Click to collapse
You can try https://drive.google.com/open?id=0BwCC2VJYgCavbHEwMk9CSFR4Snc
this is the version of my kernel i use (it says beta because it's not yet release, don't worry it will not break anything)
Make a backup of /system /data /cache /boot through twrp and flash the zip file
default settings will normaly make your phone not shut off. i've just go into 29% without problem
i can ear a noise from top speaker sometimes but i just stop touching the phone and it go back to normal.
Like i said above i still think a need a new battery
also i've see some users report a same problem on 6p after nougat update maybe we're on something
I generally knows how to flash stuff, use xposed, and whatnot. But I've never really done anything unified to focus on extreme battery saving. I am hoping to be able to switch profiles or something like that so I can keep the phone running on the lowest power possible but still be available for me to wake up to higher power for camera, gps, and messaging uses. The reason for this use case is because I will be hiking half of the Appalachian Trail this summer from Harper Ferry, WVA to Springer Mountain, GA, a total of roughly 1023 miles. Being able to stretch my battery as much as possible without actually enabling airplane mode or turning it off would be extremely helpful. I'm deaf so I cannot just simply borrow anybody else phone to call family. So I must be able to use my current phone for many different functions, including communication.
I do want to be able to use my phone as a primarily social media and messaging device. I have a wordpress blog that I'm trying to get in the habit of updating more often. I also have Instagram, Facebook, and the like. I will be bringing a pocket camera with me but I still want to be able to use my phone to snap pics for easy sharing to Instagram (it will autopost to both Facebook and Wordpress). One of my concern about the camera app is because I know that some ROMs have had issues with the camera's performance after a little while. Being on the trail for about 2 and half month, I won't have any opportunity to fix up my phone. Hence why I want to start testing thing out right now and have about a month or two to go before the actual hike.
GPS is obviously going to be vital. I have a guidebook with me that should covers everything and I almost never ever lose my cardinal direction so I'm not too worried about getting lost. But some GPS access could help just in case I need to figure out exactly how far I've missed a turn or how much I have left to go for the day. Plus it would be nice to have in case of emergency.
I do need bluetooth though. I have a Pebble watch that would be useful for me on the trail, I think. And I will be using a folding bluetooth keyboard on the trail too.
I remember once having Cyanogenmod on an old phone of mine with the ability to extremely underclock. It was incredibly laggy but I was able to create a shortcut to the clocking page so I could switch to a higher speed as I needed it. I'm hoping to be able to do the same with my Verizon's Nexus 6.
Anyway, I'm hoping for any input on which ROM, kernel, etc... would be recommended for setting up the absolute best battery saving and be able to switch the functionality high or low as I needs it. Thanks for any input.
Deafcyclist said:
... to focus on extreme battery saving. ...
Click to expand...
Click to collapse
I know that this doesn't exactly answer the question you asked. And I've only owned my N6 since September, and despite flashing everything under the sun with my older devices, I have yet to leave stock on the 6.
That said, are you considering auxiliary batteries (some will give you about 3-4 full charges and are the size of a deck of cards) and possibly solar arrays to top them off? I would consider hanging one from the top of my pack during the day and taking my rests near clearings for direct sunlight. And if you're really looking to stretch your battery, but don't want to run in flight mode, I would consider leaving the BT devices home and maintaining a 2g connection while hiking, only switching to higher power radios when you need to upload images. Remember, in fringe areas, the higher power radios are going to use exponentially more power than when they have a solid signal. And the 2g radio has better reception in fringe areas, besides. Personally, I would use flight mode while sleeping.
One other thing about the radio: this may sound like snake oil, but it is my understanding that the radio's reception can be stronger when closer to the ground based on how the radio waves travel. (It may have been a placebo, but I'm certain I have seen benefit from this on occasion).
I would also make sure that things like NFC, ambient display, screen rotation, adaptive brightness, sync, notifications and vibration are turned off (Being deaf, I suppose that no vibration may not be possible). I would also uninstall (or disable) any and all apps that are not absolutely necessary for the trip. I would also uninstall the Facebook app, if you are using it. If you prefer an app experience for it, I would recommend the Metal app in it's place. No matter what rom you install, you should go for optimizing the power usage.
As for the camera, I would stay away from the AHDR modes and stick to single frame (huge battery saving there!)
I would set a completely black lock screen and home screen wallpaper, too.
I would also suggest an automation app for managing your power usage. Most allow you to have predefined groups of settings that you can assign home screen shortcuts or a quick settings tile. I recommend Automate by Llama Labs.
Good luck! And I hope you have a fantastic trip!
So far that I know of, is that the CPU and GPU speed and governors affect how much the battery is used (#2 heavy power consumer behind the active-matrix organic LED screen with light background) - the faster they run, the more power they require to do certain tasks. I have since set my Nexus 6 phone's processor at 200 - 300 MHz to 1 GHz across entire quad cores (with AutoSMP hotplug and ondemand governors) and GPU locked to 300 MHz maximum, and that configuration have been saving me a lot of power (and quite noticeable with the new battery I installed last week). The ROM I am using is crDroid (Android 7.1.1 Nougat), if you're wondering.
As for GPS, it depends. It may just sip or hog the power. Vibration? It depends on vibration strength (which can be adjusted with Kernel Adiutor Mod app), the stronger it is, the more current it require. Long story short, experimentation is necessary. I also recommend to use black theme under Substratum, it will also ease current consumption by the screen, which I have been doing also (Swift Black Substratum theme pack is what I'm using, perfect amount of blackness to save a good amount of power, and can be found in Google Play Store).
I second cameraddict's suggestion of a power pack. I have the 3000mah version of this, and it works very well.
https://www.amazon.com/PowerCore-Po...&qid=1490282378&sr=8-4&keywords=anker+battery
There are others with higher capacity, but this one would more than double your N6's capacity, and it's the size of a small cigar.
cameraddict said:
I know that this doesn't exactly answer the question you asked. And I've only owned my N6 since September, and despite flashing everything under the sun with my older devices, I have yet to leave stock on the 6.
That said, are you considering auxiliary batteries (some will give you about 3-4 full charges and are the size of a deck of cards) and possibly solar arrays to top them off? I would consider hanging one from the top of my pack during the day and taking my rests near clearings for direct sunlight. And if you're really looking to stretch your battery, but don't want to run in flight mode, I would consider leaving the BT devices home and maintaining a 2g connection while hiking, only switching to higher power radios when you need to upload images. Remember, in fringe areas, the higher power radios are going to use exponentially more power than when they have a solid signal. And the 2g radio has better reception in fringe areas, besides. Personally, I would use flight mode while sleeping.
One other thing about the radio: this may sound like snake oil, but it is my understanding that the radio's reception can be stronger when closer to the ground based on how the radio waves travel. (It may have been a placebo, but I'm certain I have seen benefit from this on occasion).
I would also make sure that things like NFC, ambient display, screen rotation, adaptive brightness, sync, notifications and vibration are turned off (Being deaf, I suppose that no vibration may not be possible). I would also uninstall (or disable) any and all apps that are not absolutely necessary for the trip. I would also uninstall the Facebook app, if you are using it. If you prefer an app experience for it, I would recommend the Metal app in it's place. No matter what rom you install, you should go for optimizing the power usage.
As for the camera, I would stay away from the AHDR modes and stick to single frame (huge battery saving there!)
I would set a completely black lock screen and home screen wallpaper, too.
I would also suggest an automation app for managing your power usage. Most allow you to have predefined groups of settings that you can assign home screen shortcuts or a quick settings tile. I recommend Automate by Llama Labs.
Good luck! And I hope you have a fantastic trip!
Click to expand...
Click to collapse
Thanks for all of the ideas. I already have a 10,000mah external battery that I will be using..Unfortunately solar panel are not very feasible on the trail, there is a reason why it is sometimes called a green tunnel.
I'll be removing virtually everything unneccesary from the phone. I do use Facebook a lot but I'm planning on using titanium backup to freeze the app (plus other apps) when I'm not using it so it should not be a problem there.
Good idea about limiting to 3g when I'm on the trail. There, I only need minimal data for emergency messaging and basic GPS sharing.
I do have a pebble smartwatch and I'm thinking that maybe using it would offload the battery usage from the phone to my watch allowing me to still have some notification and other details on the watchface.
Dr. Mario said:
So far that I know of, is that the CPU and GPU speed and governors affect how much the battery is used (#2 heavy power consumer behind the active-matrix organic LED screen with light background) - the faster they run, the more power they require to do certain tasks. I have since set my Nexus 6 phone's processor at 200 - 300 MHz to 1 GHz across entire quad cores (with AutoSMP hotplug and ondemand governors) and GPU locked to 300 MHz maximum, and that configuration have been saving me a lot of power (and quite noticeable with the new battery I installed last week). The ROM I am using is crDroid (Android 7.1.1 Nougat), if you're wondering.
As for GPS, it depends. It may just sip or hog the power. Vibration? It depends on vibration strength (which can be adjusted with Kernel Adiutor Mod app), the stronger it is, the more current it require. Long story short, experimentation is necessary. I also recommend to use black theme under Substratum, it will also ease current consumption by the screen, which I have been doing also (Swift Black Substratum theme pack is what I'm using, perfect amount of blackness to save a good amount of power, and can be found in Google Play Store).
Click to expand...
Click to collapse
Yeah, that's why I'm asking about it at this point. I feels that 2 months are long enough for me to experiment with this. I'm hoping to do the trick with governers so I'll be reviewing your comment after work today.
dahawthorne said:
I second cameraddict's suggestion of a power pack. I have the 3000mah version of this, and it works very well.
https://www.amazon.com/PowerCore-Po...&qid=1490282378&sr=8-4&keywords=anker+battery
There are others with higher capacity, but this one would more than double your N6's capacity, and it's the size of a small cigar.
Click to expand...
Click to collapse
Yeah, I have a 10,000 mAh battery, heh.
I'd go back to Marshamallow and not Nougat for battery savings. Also "Pixel Off" app to reduce brightness and turns off 1/2 pixels to save battery. You can also use Black and White mode in Developer Option to save battery. Kernel Audiutor can underclock to 1190 Mhz top and 300 Mhz bottom with "conservative" governor and "powersaving" mode.
HueyT said:
I'd go back to Marshamallow and not Nougat for battery savings.
Click to expand...
Click to collapse
I disagree, because I haven't seen a difference between Marshmallow and Nougat regarding battery saving (even though stock Nougat ROM blows - all the reason to install custom LineageOS derivative ROM instead) - I know because I checked with new battery installed and I am still at 56% battery remaining ever since 5 days after charging to 100%, on the Nougat ROM with aggressive economy CPU settings I tailored on my phone, however, as for 1/2 "Pixel off" and black - white video option to save a bit juice, I agree even though it will make the UI quite ugly.
Dr. Mario said:
I disagree, because I haven't seen a difference between Marshmallow and Nougat regarding battery saving (even though stock Nougat ROM blows - all the reason to install custom LineageOS derivative ROM instead) - I know because I checked with new battery installed and I am still at 56% battery remaining ever since 5 days after charging to 100%, on the Nougat ROM with aggressive economy CPU settings I tailored on my phone, however, as for 1/2 "Pixel off" and black - white video option to save a bit juice, I agree even though it will make the UI quite ugly.
Click to expand...
Click to collapse
https://www.reddit.com/r/GalaxyS7/comments/5ujoyj/nougat_battery_life_latest_btu_vs_marshmallow/
http://www.phonearena.com/news/Bad-...-Edge-after-Android-7.0-Nougat-update_id90859
I had another thought this morning. ( I realize that all my suggestions are minor, but lots of minor adds up.) I would also turn off all animations in Developer options.
I also wanted to agree about the monochrome color option in Developer options. And the dark theme, in general.
As for kernel settings, on other devices I've had, I had quite a bit of success with UV. If memory serves, once I had finished a weeks worth of experimenting, I gained about 10% from UV. And using the ondemand governor, with lots of tweaking, I was able to increase battery life without too big of a hit on usability. I found that powersave always created a very unpleasant experience.
edit:
One more thing, from my experimenting, you can also gain several % by changing how you interact with the device. Your governor will spike the CPU every time you touch the screen. One major difference you can make today is changing that behavior. When reading, scroll from the bottom all the way to the top of the screen and don't touch it again until you need to scroll all the way from the bottom. This isn't as hard or as silly as it sounds. Watch how you use your device, Many people touch the screen a lot
Despite every effort and tweak you can think of, you'll achieve only minimal battery life extension. Your best bet is to use the few tweaks that you feel are acceptable and rely on your 10000mah battery - nothing else will have anything like that effect.
dahawthorne said:
Despite every effort and tweak you can think of, you'll achieve only minimal battery life extension. Your best bet is to use the few tweaks that you feel are acceptable and rely on your 10000mah battery - nothing else will have anything like that effect.
Click to expand...
Click to collapse
Respectfully, I disagree. Each .5%-2% gain adds up. 10 tweaks at an average of .75% gain is 7.5% Add one major tweak that gives an average of 8% and you now have a 15.5% gain. My battery, right now, on official 7.0 (with no tweaks) averages 40 hours on battery with 6-8 hours of SOT. I have many other metrics for this... So 40 hours x 15.5% = total battery life of 46+ hours. Those 6 hours are not minimal effect. Especially when there is no outlet nearby for days.
It is possible with the right mix of OS tweaks, app settings and kernel tweaks to see an average gain in the 30-50% neighborhood.
This, by the way, comes from years of tweaking and experimenting on many devices. Going back to 2003 or so. You can check out my old posts on optimizing my old Galaxy S2, I shared a lot about that device.
No need for "respectfully" I'm sure it's really just a preference. A lot of tweaks may well add up to a respectable extension, but they will never triple it as a 10000mah battery will. I'd rather carry the extra few ounces and be sure that I have a reserve. Not arguing, just stating my preference.
dahawthorne said:
No need for "respectfully" I'm sure it's really just a preference. A lot of tweaks may well add up to a respectable extension, but they will never triple it as a 10000mah battery will. I'd rather carry the extra few ounces and be sure that I have a reserve. Not arguing, just stating my preference.
Click to expand...
Click to collapse
Gotchya. I just mention all the tweaks AND the battery for his use case. As an initial full charge plus three extra charges(with the 10,000mah) without tweaks (conservatively) would net him a total of about 8 days of use. But with 20% savings from tweaks, that goes up to nearly 10 days. Quite a useful increase.
ps... I wrote: "respectfully" 'cause you know how forums can be. Sometimes I think it's best to be proactive and let the person your responding to know that you're not arguing. Cheers!