Related
Hello Everyone,
I am new to the forum, but not totally new to rooting and flashing ROMs. I have a MT3G (second android phone to come to the market...yes I'm old school ), rooted and flashed CM7-Gingerbread 2.3.3 and it's working very well.
I also managed to buy a NookColor, immediately rooted it and flashed phiremod nook v5.1. and everything is very good. My Quadrant Score is 1485
However, what I've noticed is that if I compare the battery usage on mytouch 3g vs the nookcolor I see something interesting and I think it might have to do with the overall battery drain I've noticed on the nook....I'm hoping someone here can shed some light.
When I go to my settings > about tablet > battery use, I can see a graph on the top. If I click it, it shows a nice relationship between time (x-axis), battery % (y-axis) and underneath it are 5 variables (Phone Signal, Wi-fi, Awake, Screen on, Charging). These variables are key because you can see what is really draining a battery.
See the two attached images. One is from mytouch 3g and the other is the nook. What you can see is that when my nook is sleep, it drains a lot faster than MT3G and in fact what you see is that the PHONE SIGNAL is constantly on, where when my MT3G is sleep, the PHONE SIGNAL IS NOT....
Is there a way to completely remove this 'phone signal'...I suspect we can get more battery life out of our nook if we can just remove this!!!
Thanks for reading.
easy to do if you have adb.. otherwise use terminal.
rename the following files in /system/app
Mms.apk
TelephonyProvider.apk
Phone.apk (phone will keep forceclosing.
reboot.
If you are not using adb, just force power off using the power button.
When it comes up, you will have much better battery life.
Yeah, I saw that posted somewhere, and I've done that. So does the phone signal still appear on yours after you renamed it?
I wonder if this procedure is enough.....
labrazil said:
Yeah, I saw that posted somewhere, and I've done that. So does the phone signal still appear on yours after you renamed it?
I wonder if this procedure is enough.....
Click to expand...
Click to collapse
Enough to remove Phone from being listed in Spare Parts? Yep. It won't change anything.
CM7 is really bad with the battery. It doesn't sleep properly. The phone or lack of phone has nothing to do with it. It doesn't have a cell radio after all ;-)
Apparently there is a bug and it crashes or something? when it sleeps. I read that the devs just disabled sleep until they can get it fixed. I think that will probably happen after video is all working.
It still easily lasts through the day with a fair bit of use though. I just charge every night instead of every third ;-)
ylixir said:
CM7 is really bad with the battery. It doesn't sleep properly. The phone or lack of phone has nothing to do with it. It doesn't have a cell radio after all ;-)
Apparently there is a bug and it crashes or something? when it sleeps. I read that the devs just disabled sleep until they can get it fixed. I think that will probably happen after video is all working.
It still easily lasts through the day with a fair bit of use though. I just charge every night instead of every third ;-)
Click to expand...
Click to collapse
Okay, so it's safe to assume that the devs are working on this for future ROMs/Kernals? I really like my nook even though I just got the wifi-xoom today.
There's already been a 20+ page thread on this, where comparitive testing found no actual diference in battery life by removing those functions. The result is a purely cosmetic change where the power consumed under "cell standby" is shifted to "phone idle" or something else, I forget exactly. Any perceived improvements in battery life are a placebo effect and/or simply the result of the variables in different day-to-day usage.
Removing them also causes Market problems with certain apps not showing up due to "incompatibility" with devices lacking those functions, which I suspect is why they are not removed in the first place.
The NC's "high" power drain on CM7 is because it's not allowed to actually sleep due too a kernal bug which prevents it from reliably waking up. This will get fixed eventually. Right now, "sleep" simply turns off the screen.
Hi all,
I've been working on getting my XT862 to give me more life on the battery. I've rooted and debloated using psousa's stuff, but I'm still not where I'd like to be. I've noticed a few interesting things:
AOS is showing as the top user in the battery monitor. Currently it's at 32% with my display and WiFi bringing up the rear.
Even though I've run the debloat script as root and confirmed the rename of skype.bourbon and motoprint, these things still start up. How is this possible?
BetterBatteryStats shows that the suspend process is my main battery user. How does one fix that?
Any advice on what to look for?
best route is to install a custom ROM and try different ones out for battery life. I would suggest Maverick ROM also make sure you wipe battery stats after installing a new ROM and fully cycle your battery.
hematose said:
Hi all,
I've been working on getting my XT862 to give me more life on the battery. I've rooted and debloated using psousa's stuff, but I'm still not where I'd like to be. I've noticed a few interesting things:
AOS is showing as the top user in the battery monitor. Currently it's at 32% with my display and WiFi bringing up the rear.
Even though I've run the debloat script as root and confirmed the rename of skype.bourbon and motoprint, these things still start up. How is this possible?
BetterBatteryStats shows that the suspend process is my main battery user. How does one fix that?
Any advice on what to look for?
Click to expand...
Click to collapse
I'm guessing suspend is another way of saying System Idle.. if you wanted to get rid of that, make a nandroid backup of your system (via bootstrap or safestrap) and experiment what system apps/services you can freeze (via Titanium Backup) without getting force closes on the stuff that you use. I have about 30-60 system apps/services frozen depending on the ROM that I run. I have no force close issues, and my system idle uses about 1 percent of the battery per hour.
Additionaly, if you are using the CDMA network, force CDMA mode, likewise from GSM/UMTS, if you are using it, force it, do not use Global, as it will have both radios running and searching for service.
Disable the use of wifi when you aren't using it (there is an option to auto turn it off when the screen turns off, however this may cause worse battery life if you are using data as it will try use your mobile network, requiring more power), if you wish to leave it on, increase the scan time interval (i made mine 10 mins, up from the stock 45 seconds)
Auto brightness (it isn't really that bad...)
And get the app called juice defender. Once you set it up it controls all of your wireless stuff. Like turning wifi and 3g off when you turn your screen off, etc.
Sent from my DROID3 using XDA App
hematose said:
[*]AOS is showing as the top user in the battery monitor. Currently it's at 32% with my display and WiFi bringing up the rear.
Click to expand...
Click to collapse
If you use Wifi often, it is a good idea to check your Wifi Sleep Policy. To do this, navigate to:
Settings > Wireless & Networks > Wifi Settings > Advanced Settings (hit menu to access this) > Wifi Sleep Policy
I have mine set to 'Never'. By default, it was set to turn off the wifi when the screen went off, so any background apps that run and use data default back to the mobile connection. When you turn the phone back on, it turns the Wifi back on from sleep mode. By changing the sleep policy to 'never' you prevent this disconnect/reconnect to Wifi cycle.
This helped my battery life when connected to Wifi. Let me know if it works for you.
Thanks to all
Thank you for your replies everyone. I'll have to get TB and start freezing stuff. What confuses me though is how a service like Verizon Apps or Skype Mobile gets started even though it was renamed ".bak" by psousa's script. Also, I've noticed that when I run the restore bloat software, I don't get back all the apps in my app drawer. I'm not sure why that is.
Is it possible something got screwed up if I ran the debloat script twice? I see that it does a bunch of mv proggie.apk proggie.apk.bak type work. If the first file wasn't found, is it possible that it overwrote the .bak with gibberish?
My WiFi sleep policy is never because I have WiFi all day and I like Google Talk a lot. I'd be happy if I could get WiFi/Display as my top users, just AOS seems like a bug.
I'm on UTMS so it's forced to that all the time.
Maybe the answer is to try the mods. Or maybe SBF to the stock and try again?
It's widely known that the s7 has pretty weak battery life.
In general all qisda dell devices do (the s5/s7/venue).
Many of the bugs exist in the phone/ril and some exist in the logging systems.
In a bug free rom these workarounds should be completely meaningless, but stock roms are not at all bug free.
Recommendation one: Enable airplane mode on wifi s7's
The wifi and 3/4g roms are nearly identical, including the fact that wifi roms still have a full RIL. It apparently is also still enabled even in wifi s7's. Turning airplane mode on while leaving wifi/bluetooth on (as desired) does in fact affect the system.
Ways of checking: with airplane mode off on mine, the s7 has major issues going into sleep mode. Even with the screen off if you check the battery graph it's still active most of the time. Airplane mode more or less fixes this.
Potential gains: 20-30% or so more life, I've only been testing this for half a day or so but it seems to be draining signifigantly slower in sleep.
Recommendation two: (this one is more valid for the s5 then the s7) Connect the s7 to a pc with the android SDK installed and run 'adb logcat'
The qisda devices are known to have far too much logging enabled and included in stock roms. Virtually all the custom roms for the s5/7 have it removed, but there is a known bug with logging.
If you run logcat so the output is directed to it, afterwards it takes care of another one of the bugs. I have not actually tested this specifically on the s7, but it likely is equally valid as the differences from AOSP (ie the customizations qisda does to the roms) are pretty similar in the s5 and s7.
Potential gains: nearly triple battery life after logcat and avoiding a yet different ril bug on the s5. The s5 can go from potentially 10%/hour to 0.3%/hour due to all/no bugs being active. The s7 MAY be a valid target too, but I havnt actually tested this one on the s7.
Roms used to compare:
S7: Stock 506-wifi
S5: Custom 406 based rom
The first one I do, like you said for sleep more than "cell is using battery" nonsense.
The second one I'm confused.... Just run logcat? Or somehow attach logcat to that process, or?
What about disabling those processes? We know there's a ton of Dell processes on the DS 5 and 7 that are generally useless.
The first one I can definitely confirm works (which is stupid as dell shouldnt let this happen)
I'm getting 27h @ 12% drain with airplane mode
while normally it's approx 1%/hour drain otherwise. If it wasnt such a stupid bug airplane mode should do absolutely nothing.
It's visible on the battery graph as the fact the device rarely ever goes into sleep, it's awake 50% of the time that the screen is off. After turning on airplane mode it's able to to go to sleep fully. It's the way the RIL interacts with the kernel or something really stupid.
I've been studying it over the course of a month, my rom hasnt been modified since the 50x launch and I know for a fact that it's not due to apps since none of them are capable of running in the background (my s7 has very few apps at all installed).
I removed all the unneeded engineering mode/logging apps when I installed my rom so they're not even on the device.
If you compare the S7 and S10 side by side in their battery graphs the S10 can sleep properly and the S7 cant, the s10 also gets 4-5x the S7's battery life even though it's less then double it's battery size.
I dont know for a fact the logcat one is valid on the s7, but just run adb logcat for like 10-20 minutes or so (if it were an s5 you could top off your batt while doing it) and suddenly the batt drain goes down by approx 1-3%/hour on it.
Crosspost on S5 forum discusses this one more, it's equally as stupid but I've been able to study it for about 2 months and can consistantly replicate my results.
The fact the s10 trumps both the s5/7 in batt life cant be a coincidence that dell switched ODMs when they made the s10. The s5/7/venue are all made by Qisda and the s10 is made by PEGATRON and the s5/7/venue suffer from the same battery bugs (as they all share the same codebase)
The logcat bug doesnt seem to apply to the s7, I've been watching it's batt stats and it might have been fixed in 5xx.
It might have been valid in 3xx but as I have no interest in testing that I cant confirm or deny
A huge fix is a custom kernel that lets you underclock. I run HoneyStreak R8 and I use SetCPU to do this.
Using custom profiles, I do the following:
On Demand profile
Min: 215mhz
Max: 1000mhz (I use to overclock but not anymore)
Profiles:
Charging: 215mhz (Conservative Profile)
Screen off: 215mhz (Conservative Profile)
Under 50% battery: 700mhz (Conservative Profile)
I have my DS7 last me all day long, and thats with like 2-3 hours of wifi, 1-2 hours of video watching, and an hour or so of gaming and then its at like 40-50% battery life left.
Not really surprised at all, esp after reading the stuff on irc. It's more about undervolting though as even the stock kernel ramps up and down the freq as needed. Though who can say if it does so effectively.
I dont currently use any custom kernels atm though, just a personal preference.
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.
Sorry for the long list of screenshots above, and also for creating a new topic, but didn't want to spam the normal board for battery discussion.
Anyway, I have the N920I model of the Note 5, using it on Telkomsel in Indonesia, and getting average 3+ hours SOT on this device, which I think could stand to be much better, given I got around the same figure on the Moto X 2014, which has significantly worse battery life according to most counts.
Here's my settings:
Screen brightness 60%, auto
Sync on
NFC off
Location high accuracy
Bluetooth on from 8 to 3.30, then off for the rest of the day
Connected to an Asus ZenWatch 2
Wi-Fi on from 4 to night, from plug out in morning to 8
Here's the list of apps I disabled:
And here's how my usage goes:
* Plug in when I wake up, then out at 7-ish.
* Get to school and let My Places switch to "Work" mode, where it changes the Bluetooth, Wi-Fi and power saving settings and turn off data before starting the first class.
* Turn it on between classes to check for new messages.
* Leave at 3-ish, and get home, letting My Places change the settings back to normal. At this point, the phone is usually at 70% with an hour of screen on time to report.
* Use it periodically throughout the rest of the day, switching between WhatsApp, Snapchat, Netflix, Chrome and YouTube.
* Plug in at 8 or 9, then plug out before I go to bed, topping up what's left in the morning.
It's a fairly light usage pattern, which reinforces the point that this phone should get more than just 3 hours. Any specific app you're seeing here that might be putting its toll on battery life, or a specific setting that you can advise enabling or disabling?
Bump
Sent from my SM-N920I using Tapatalk
Just try counting how many threads there are about battery life in this section. A lot! I, being one of the victims of horrendous drains, have tried everything. If you keep the device relatively clean(software) and it still drains then there is only one thing you can do. Wait for the marshmallow. I'm sorry but that's what it means owning a samsung device.
try gsam battery monitor. It may give insight into what is going on....
bonerp said:
try gsam battery monitor. It may give insight into what is going on....
Click to expand...
Click to collapse
Already did! But Android OS is always the top consumer.
thanks!
As Octa_core mentioned, there are quite a few threads about battery life already. They might be of benefit if you haven't already looked through them.
Here are a few things you might try, if you haven't already.
- Turn off location high accuracy, or only turn on location when you need it (if you can)
- Turn off location history
- Turn off Always Allow Scanning in Wifi advanced settings
- Turn off S-Pen settings (alerts, sound, vibration, detection)
- If using Google Fit, disable activity detection in settings (this definitely helped my idle drain)
- Turn off anything you don't need to sync on your Google Account
- Disable enhanced LTE services
- Turn off Motions and Gestures you don't use
- Set touch key light duration to Always Off (under Display)
- Turn off Smart Stay
- Set Screen Mode to Basic
- Use a darker theme
- Try disabling some apps, especially S-Finder (may require Package Disable Pro to disable some apps)
- What does your signal look like in GSam? Some drain may be due to poor signal.
If none of that helps, then uninstall or disable (probably will need Package Disable Pro to disable) all apps you installed, and I also recommend that you disable S-Finder. Turn off all radios (location, NFC, bluetooth, wifi, even data) other than cell. Reboot after those changes. Monitor and see how idle battery drain is. After I did this, my idle drain was around 0.4% per hour. Then you can gradually enable radios/apps, only 2-3 at a time, reboot, and see how it impacts idle drain. Continue until you find app/radio that increase idle drain.