Database Users

[Q] How does rooting affect the battery life

As the title says, does rooting the NST affect the battery life at all?
What about using another e-reader app, say the kindle app, in comparison to the battery usage of the default reader?
And also that crazy NoRefresh app that I saw. What is the affect of the battery life with it enabled?

I can say it running like crazy
The battery went down to 40% for one day uses.
I have many email accounts on the sync though.

GoldenStake said:
As the title says, does rooting the NST affect the battery life at all?
Click to expand...
Click to collapse
I've been running rooted for a few weeks now. I don't think rooting, per se, affects battery life so much as what you do with it.
Out of the box, the NST uses very little power. If you leave wifi off, it will last quite a long time. The minute you start loading up anything that wakes the unit up, or that turns on and uses wifi, battery life drops. Since it normally uses so little power, the drop seems quite dramatic.
Here are some rough and very unscientific numbers based on my usage:
Unit off with wifi off: 2% battery consumption per 6 hours.
Unit off with wifi on: 2% battery consumption per hour.
Unit on and in use with wifi on: 4-6% battery consumption per hour.
I haven't really let it sit long enough to really validate these, but they give you an idea. I'd expect to get a week to 10 days out of it with "typical" usage, and probably much more. Part of the problem of bench-marking this thing is how quickly it charges up, even when I only connect for a few minutes to side-load some books.
I use Tasker to turn wifi off unless a very small group of apps are running, and shut it off when they exit.
If you keep anything from polling, don't use active widgets and turn wifi off when not needed, you should get more out of it than most any other device you own. Watch out for things that hang in the background. I was once downloading some files from the Market and it hung, so I lost a lot of power overnight. If you load up with active wallpapers, widgets and/or apps that poll in the background, expect to see it using the battery quickly.

I charge every 4 days, but that's because I use it without wifi unless I am getting an app or something. But that's just me.

In my experience the battery life got worse after initial rooting. It is noticeable. Rooting itself has nothing to do with it.
The biggest offenders are apps installed in the process. I removed most of apps that either worthless for me or attempt using internet frequently. I don't think I need google on a book reader. The reader does not provide any privacy, even password protection. I removed everything related to google. Apps can be sideloaded if necessary.
Free SuperManager is a very good apps for managing the reader but free version tends to use internet too much.
Now the battery life is back to what it supposed to be. Rooting is only useful for me for gaining control and access to the web browser if there are no alternatives. NT is just a reader and a nice one.

My Nook died afer 3 days of intense exploring (wifi on non-stop).
I've spent approx. 6h/day on it.
But it's a pretty nice result IMO.
I think rooting does't really effect battery life by itself. I've checked battery life log on NookTouchTools (an app) and it says 77% was drained by display, but i cant compare it to non rooted version.

I've seen battery drain vary enormously from not dropping at all to dropping precipitously with normal off (not completely powered down) and WiFi shut off. I think that the only really way to get a handle on this is to put a milliampmeter in the battery circuit and measure in real time the current drain.
I do know that if you have the WiFi on you can still ADB to the Nook even when it is "off". You can even start apps!

Ridiculous ICS Battery Life

On Friday 1 June 2012, which is Friday last week at the time of writing, I gladly updated my phone through Kies after receiving word of the UK update being available from these very forums. Over the past week, I have noticed that my battery life is considerably worse since my upgrade to the new Android version and, when hearing of people hear who manage up to 36 hours of battery life through this phone, I really want to find out what they are doing exactly. At present, I have set the brightness at 1% (the minimum) and only up it to 40% when out in bright light conditions. At home, I also use the Screen Filter app which dims the screen further (I have this set to 50% of my already 1% brightness setting) and claims to improve battery on AMOLED devices. I also have Juice Defend Ultimate running on "Aggressive" mode along with the built-in power saving mode running as well. Yet, looking on CPU Spy, my phone still does not enter deep sleep which is needed to see a real improvement in battery life as far as I am aware. I have tried restarting the phone and also plugging it back into charge before unplugging it with the screen turned on as many have recommended. Any ideas what else I can do?

Uninstall juicedefender. Its not uncommon that it drains a lot more juice than it saves.

There is must be any Application that is hogging your battery.
Install better battery state... Find that application and uninstall that.
I am getting better battery life in ICS as compared to GB...

chintamanijaipuri said:
There is must be any Application that is hogging your battery.
Install better battery state... Find that application and uninstall that.
I am getting better battery life in ICS as compared to GB...
Click to expand...
Click to collapse
I have that app installed, but frankly have no idea how to use it very well. From what I can tell, it is Kik Messenger which is creating a partial wake lock (but I need that to send pictures to my friends), Juice Defender which is supposedly saving battery life and biggest partial wake lock is RILJ or something. But, that is caused from a weak signal and I get that regardless of network at my house. Besides moving, I cannot alter that. As for Juice Defender, I've heard nothing but positive reviews from it. My main aim is to get deep sleep working, but how?

Install Better Battery Stat and check what app is actually causing the problem :
http://forum.xda-developers.com/showthread.php?t=1179809
P_

pakalrtb said:
Install Better Battery Stat and check what app is actually causing the problem :
http://forum.xda-developers.com/showthread.php?t=1179809
P_
Click to expand...
Click to collapse
Read my previous post.

Brad387 said:
On Friday 1 June 2012, which is Friday last week at the time of writing, I gladly updated my phone through Kies after receiving word of the UK update being available from these very forums. Over the past week, I have noticed that my battery life is considerably worse since my upgrade to the new Android version and, when hearing of people hear who manage up to 36 hours of battery life through this phone, I really want to find out what they are doing exactly. At present, I have set the brightness at 1% (the minimum) and only up it to 40% when out in bright light conditions. At home, I also use the Screen Filter app which dims the screen further (I have this set to 50% of my already 1% brightness setting) and claims to improve battery on AMOLED devices. I also have Juice Defend Ultimate running on "Aggressive" mode along with the built-in power saving mode running as well. Yet, looking on CPU Spy, my phone still does not enter deep sleep which is needed to see a real improvement in battery life as far as I am aware. I have tried restarting the phone and also plugging it back into charge before unplugging it with the screen turned on as many have recommended. Any ideas what else I can do?
Click to expand...
Click to collapse
first ,samsung ICS is poorly made ,second you have a high chance of bricking if you wipe your phone with their official kernels so don't do it.
third ,like others said ,juice defender (and any app of this sort) doesn't work anymore (android 2.2 and up) so just uninstall it.
fourth ,not entering deep sleep is mostly due to a rouge app ,and since wiping is not an option for you you need to hunt it down manually ,use better battery status (learn how to use it!!!) and uninstall any apps you don't need.
fifth ,get some knowledge then get rid of crappy touchwiz ROM and install CM9 ,you'll see a huge improvement in terms of performance and battery life.

MR.change said:
first ,samsung ICS is poorly made ,second you have a high chance of bricking if you wipe your phone with their official kernels so don't do it.
third ,like others said ,juice defender (and any app of this sort) doesn't work anymore (android 2.2 and up) so just uninstall it.
fourth ,not entering deep sleep is mostly due to a rouge app ,and since wiping is not an option for you you need to hunt it down manually ,use better battery status (learn how to use it!!!) and uninstall any apps you don't need.
fifth ,get some knowledge then get rid of crappy touchwiz ROM and install CM9 ,you'll see a huge improvement in terms of performance and battery life.
Click to expand...
Click to collapse
Okay, well this is my first proper Android device (minus an old second-hand HTC Desire which had awful storage and I used for around one month). Secondly, I do know that other ROMs offer better performance and battery life but flashing them onto my phone is something I'm not very comfortable with and surely it would also void my warranty. I've only had the phone for four weeks and don't want it wrecked already.

Brad387 said:
Okay, well this is my first proper Android device (minus an old second-hand HTC Desire which had awful storage and I used for around one month). Secondly, I do know that other ROMs offer better performance and battery life but flashing them onto my phone is something I'm not very comfortable with and surely it would also void my warranty. I've only had the phone for four weeks and don't want it wrecked already.
Click to expand...
Click to collapse
I'm fairly new to android as well ,had an S2 (which was so good that I only rooted it ,no custom ROMs) for 5 months before the note and that's it.
but I rooted my note the first day I got it ,and installed a custom ROM less than a week later (was a total noob at the time but I read and learnt quickly) .
then CM9 arrived and I flashed that immediately and haven't regretted it so far.
but I had no warranty to begin with so.....
note that if there is something that can wreck your shinny new note ,then it's amsung official ICS update (read the announcement sticky on ICS and bricking) .

but how experts can explain the fact i face:
With every official and custom ROM i install, even CM9, my note keeps eating battery when in use plugged to the charger... it's unbelievable... I can't understand how it happens.
by the way: i always full wipe before installing any custom/official rom.

MR.change said:
I'm fairly new to android as well ,had an S2 (which was so good that I only rooted it ,no custom ROMs) for 5 months before the note and that's it.
but I rooted my note the first day I got it ,and installed a custom ROM less than a week later (was a total noob at the time but I read and learnt quickly) .
then CM9 arrived and I flashed that immediately and haven't regretted it so far.
but I had no warranty to begin with so.....
note that if there is something that can wreck your shinny new note ,then it's amsung official ICS update (read the announcement sticky on ICS and bricking) .
Click to expand...
Click to collapse
Well, is there nothing that I can do to trigger deep sleep or improve battery life on the stock ROM first of all? Secondly, how difficult is rooting and would that void any warranty?

Raphael Alo said:
but how experts can explain the fact i face:
With every official and custom ROM i install, even CM9, my note keeps eating battery when in use plugged to the charger... it's unbelievable... I can't understand how it happens.
by the way: i always full wipe before installing any custom/official rom.
Click to expand...
Click to collapse
it can't happen ,I'd say you either have a faulty battery\charger or there is someting wrong with the phone itself
the note charges while in use and connected to a charger.
Brad387 said:
Well, is there nothing that I can do to trigger deep sleep or improve battery life on the stock ROM first of all? Secondly, how difficult is rooting and would that void any warranty?
Click to expand...
Click to collapse
yes you can ,uninstall the violating apps ,learn to use better battery status ,you'll find that there is an app or two responsible for the wake locks ,thus preventing the phone from entering deep sleep.
or simply install every app and game that seems suspisious or poorly made ,and just keep the essential ones.
as for rooting ,it couldn't be simpler if done carefully and to the letter :
1.flash back to GB using PC ODIN
2.root it
3.backup your EFS folder (important , very important) search for it on the forums.
4. install custom ROMs (stay away from unsafe kernels please ,read the sticky thread about ICS kernels)
3. enjoy
use this guide
http://forum.xda-developers.com/showthread.php?t=1329360
yes there is an easy way to root while on stock ICS as per to this guide ,but I prefer you stay away from official ICS for the sole reason that it's dangerous.
remeber the key is to read and read and read ,in a month you could become a pro
on the other hand if you go the lazy way ,you could just end up with a bricked phone
also once you root ,your warranty is void ,though if you're careful you can return it to stock condition and they won't tell the difference
be careful

MR.change said:
fifth ,get some knowledge then get rid of crappy touchwiz ROM and install CM9 ,you'll see a huge improvement in terms of performance and battery life.
Click to expand...
Click to collapse
That's just wrong. CM9 battery drain with screen on is far, far worse than Stock ROM.

IndDoc said:
That's just wrong. CM9 battery drain with screen on is far, far worse than Stock ROM.
Click to expand...
Click to collapse
no my friend ,I'm afraid you're wrong ,with the 4\6 nightly my phone was running with low usage for 48+ hrs .
the battery life is phenomenal for me .

@Brad387
I have had mine for about 2 weeks. When I turned it on and did the initial setup it had a new software update which was ICS. Since then I have been having issues with deep sleep as well. I turned stuff on and off and it has been totally random what was preventing it from going to deep sleep.
I have done this trick that has been on this forum.
Put you phone to airplane mode.
Power it off completely
Remove battery for 20 seconds or more
put battery back in and power this thing back on
then turn off airplane mode.
This seems to have helped me get into deep sleep. BUT there have been instances of rogue crap going on. Like I was using Google maps with GPS on. When I got home and was done with my traffic mapping I turned off the GPS switch and turned off my phone. I checked an hour later and the battery had died 10% since I got home which was more than when I was driving. I checked Better Battery Stats and it showed that GPS was running that whole time. So I turned on GPS again in the toggle waited a couple seconds then turned it off again and bang it went into deep sleep. It sucks that I have to check crap on it all the time and have become a bit paranoid because the GPS glitch had my phone running pretty hot. Since then everything has been running well and deep sleeping.
There are other things I did do too and the below stuff is up to you if you wish to proceed. I rooted my phone which was very easy...at least for me. http://forum.xda-developers.com/showpost.php?p=20963730&postcount=3 this is what I used with no problem.
From there you can freeze a bunch of stuff you may not use like Social Hub, Accuweather etc etc.You will need Titanium for that though and root access.
I logged out of Latitude too which was on by default for some reason.
If I remember anything else I did I will hit you back here.
Bottom line was finally yesterday I was able to get thru the entire day without needing to plug in so there is light at the end of the tunnel...I hope.
Not sure if this has been mentioned but CPU Spy lets you see if you are getting into deep sleep mode and how much time you are in it along with the other CPU mhz that its running.
Hopefully this can help out a bit because I have been in the same boat and it has been driving me mad. Sorry for all the random thoughts too...I just typed them as I remembered things.

jbeef86 said:
@Brad387
I have had mine for about 2 weeks. When I turned it on and did the initial setup it had a new software update which was ICS. Since then I have been having issues with deep sleep as well. I turned stuff on and off and it has been totally random what was preventing it from going to deep sleep.
I have done this trick that has been on this forum.
Put you phone to airplane mode.
Power it off completely
Remove battery for 20 seconds or more
put battery back in and power this thing back on
then turn off airplane mode.
This seems to have helped me get into deep sleep. BUT there have been instances of rogue crap going on. Like I was using Google maps with GPS on. When I got home and was done with my traffic mapping I turned off the GPS switch and turned off my phone. I checked an hour later and the battery had died 10% since I got home which was more than when I was driving. I checked Better Battery Stats and it showed that GPS was running that whole time. So I turned on GPS again in the toggle waited a couple seconds then turned it off again and bang it went into deep sleep. It sucks that I have to check crap on it all the time and have become a bit paranoid because the GPS glitch had my phone running pretty hot. Since then everything has been running well and deep sleeping.
There are other things I did do too and the below stuff is up to you if you wish to proceed. I rooted my phone which was very easy...at least for me. http://forum.xda-developers.com/showpost.php?p=20963730&postcount=3 this is what I used with no problem.
From there you can freeze a bunch of stuff you may not use like Social Hub, Accuweather etc etc.You will need Titanium for that though and root access.
I logged out of Latitude too which was on by default for some reason.
If I remember anything else I did I will hit you back here.
Bottom line was finally yesterday I was able to get thru the entire day without needing to plug in so there is light at the end of the tunnel...I hope.
Not sure if this has been mentioned but CPU Spy lets you see if you are getting into deep sleep mode and how much time you are in it along with the other CPU mhz that its running.
Hopefully this can help out a bit because I have been in the same boat and it has been driving me mad. Sorry for all the random thoughts too...I just typed them as I remembered things.
Click to expand...
Click to collapse
My phone does not seem to enter Deep Sleep, but runs constantly at 200 MHz instead. At present, after turning on the built-in power saving mode (not noticing any performance differs so can't even tell what it does), running Juice Defender Ultimate on aggressive and screen filter I burn around 2% per hour if I just leave my phone locked. Is that healthy?

Brad387 said:
But, that is caused from a weak signal and I get that regardless of network at my house. Besides moving, I cannot alter that.
Click to expand...
Click to collapse
Actually, there is something you can do about that!
Both Vodafone and Three can supply you with a Femtocell which can greatly improved your signal at home, and uses your home broadband as backhaul.
I know, because I have them!
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2

Battery life of my Note was horrible after upgrade to ICS, and actually already quite bad the last month on GB2.3.6 (all unrooted).
It could get quite warm and often when opening my case the screen was already on.
So I did wipe my phone, reinstalled all apps and battery life has improved immensely.
I see several warnings here about chance to brick your phone when wiping on stock ROM, but not solving the battery drain is of course no option and we don't have a guarantee from Samsung for nothing...
Sent from my GT-N7000 using XDA

foxmeister said:
Actually, there is something you can do about that!
Both Vodafone and Three can supply you with a Femtocell which can greatly improved your signal at home, and uses your home broadband as backhaul.
I know, because I have them!
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Well, thanks for offering that advice but how expensive are these things? Also, I'm the only person on 3 in my house so kind of a waste really...

Brad387 said:
My phone does not seem to enter Deep Sleep, but runs constantly at 200 MHz instead. At present, after turning on the built-in power saving mode (not noticing any performance differs so can't even tell what it does), running Juice Defender Ultimate on aggressive and screen filter I burn around 2% per hour if I just leave my phone locked. Is that healthy?
Click to expand...
Click to collapse
your phone should not be running at 200MHz when you hit the sleep/power button. So if its in your pocket and the screen is off then 200MHz is not healthy. Something is running in the background. Have you tried the airplane mode battery trick yet? What I did when that was happening to me was...turn on the airplane mode, power off the phone, pull out batt for 20 secs, put batt in and power on phone, turn off airplane mode, then go to CPU Stats and clear it, then put phone back to sleep and let it sit for a half hour or less if you cant handle that wait like I couldnt. Go back to CPU Stats and and click refresh and see if it helped and if your phone went into deep sleep.

I may have solved the famous battery problem on Nook & Nook Touch!

Hi,
I've been using Nook for two years and Nook Simple Touch for 5 months or so.
I've rooted both my devices and used them that way (until my original Nook got those screen problems and became unusable)
Starting from first days I realized that the battery life was quite shorter than advertised. In fact it was almost unacceptable, like draining %10-15 a day while standing by (at the regular screensaver)
First I thought this was caused by the rooting and custom firmware. I tried the regular disabling of services, but to no avail. After a while I decided to return to the stock 1.1 firmware (on NST). To my horror I saw that nothing changed. Then I rerooted the hardware, still same.
One day, while I was reading a book I got a call and had to leave the house very fast. Thus I bagged the NST and got out of the house.
After returning home, I left that bag in my living room and did not open it for five days. After five days I picked up the NST, which was %70 charged five days ago, sure that I had to charge it again. To my surprise I saw that the charge was still %62. How could this happen, I began to querry. And remembered that I did not manually activate the screensaver -which was my general behaviour.
After that day I did not manually activate the screensaver even once and the battery drain is never more than 1-2%/day.
I'm not an Android developer, I'm a regular computer guy (using computers for almost 30 years) but I have strong gut feeling that this may be the problem, that manually activating the screensaver is not same as activation after a time out.
I guess many people over here, being -not regular users but optimization obsessed technical people- prefer to activate the screensaver manually. Thus they have the drain problem.
If you are suffering the same problem, please test this and write your feedbacks over here. May be one of the coders can look into this problem in the end.
With kind regards

You may be onto something there.
I certainly believe that the problems are related to not fully going into sleep mode.
I have caught the Nook many times that it was supposed to be sleeping and the touch screen was still running.
I always used the power button when I'm done, I had the screen timeout set on one hour.
I just set my screen timeout to 10 seconds to play with this.
I couldn't get the Nook to act up with the power button shutdown.
To set your screen timeout to a arbitrary value (time in milliseconds):
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db
update system set value=10000 where name='screen_off_timeout';
.q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db

foredog,
Could you clarify a bit, please?
Nook can go into screensaver via
timeout,
front button,
back power button or
"button savior Off" button.
Which button you referring too to manually activate the screensaver?

foredog said:
After that day I did not manually activate the screensaver even once and the battery drain is never more than 1-2%/day.
Click to expand...
Click to collapse
I use my Nook Simple Touch minimally and almost always use the back button to activate the screensaver. I see pretty good battery life upto 20+ days. The only thing I do differently from you is turn off wifi before I activate the screensaver. Maybe wifi is the main cause for the battery drain.
--

cbay said:
I use my Nook Simple Touch minimally and almost always use the back button to activate the screensaver. I see pretty good battery life upto 20+ days. The only thing I do differently from you is turn off wifi before I activate the screensaver. Maybe wifi is the main cause for the battery drain.
Click to expand...
Click to collapse
WiFi is definitely a big one.
Any easy way to "auto turn it off" with screensaver activation?

Don't know about that - I always use the "sleep" button to activate the "screensaver". Right now, I'm up to a month of use, and like 30% batt still. I turn wifi on when I need it, and off again when I don't. Glowlight on for like 20 min/day.
Actually really impressed with NST Glow.

Sorry I did not mention, that my wireless is always off.
@Apokrifx: I'm using the power button at the back to go to sleep mode.
What you all are saying is similar to general behavior. Everyone is not experiencing this drain among Nook users, only some.
In my case, letting NST time out really solved the problem.
What Renate says is really similar to my experience. Time and time I accidentally touched the screen (while it was on the screensaver and it asked for the swipe motion (meaning the touch interface is responding) which should not happen in the sleep mode.
I'll let you know if anything changes.
Thank you for the feedbacks.

I think the original post info is quite accurate. I notice when I don't go back to the home screen, and leave it on the stock reader when I put it down-- battery life is much better.
It appears that, when the stock reader is running, it shuts down most background services. But, that's just a theory.

i guess when u activate ur screensaver that wont drain power from ur battery ..... cuz in screensaver mood the animation on screen stopped like calculator screen ..... just display image and didnt move any pixels on screen ..... so .... ummm .... i guess ur problem may u not charge battery well .... let me tell u .... u must per month empty the battery until nook tells u that ur nook device cant power on .... and that will guarantee to u long life to ur battery also keep ur battery more efficiently and working perfect
hope i helped ..... best regards

Actually, I've had no battery problems in a while.
I've got rid of almost all the B&N stuff though.
USB host mode, with its polling seems to take a bunch of battery though.
It's still manageable.

I got my glowlight nook recently(after I stepped on my old Nook ST, ouch). When you have glowlight on and the Nook goes into sleep mode the glowlight turns off. It happens even if you press the back button. But... I had few instances when the screensaver activated and the glowlight didn't turn off... Can't reproduce this issue too often and with glowlight at least I know when it didn't turn off But other services might have simmilar issue.

I wonder whether this has anything to do with the wi-fi sleep mode you can tweak on normal Android phones... maybe the default sleep disconnects the wifi too, while the sleep button in the back just activates the screensaver.

Renate NST said:
You may be onto something there.
I certainly believe that the problems are related to not fully going into sleep mode.
I have caught the Nook many times that it was supposed to be sleeping and the touch screen was still running.
I always used the power button when I'm done, I had the screen timeout set on one hour.
I just set my screen timeout to 10 seconds to play with this.
I couldn't get the Nook to act up with the power button shutdown.
To set your screen timeout to a arbitrary value (time in milliseconds):
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db
update system set value=10000 where name='screen_off_timeout';
.q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
Hi,
The UK went crazy with the Nook last week and I got one. I also got the problem with the battery. I have tried this:
This is taken from qvc forum. I cannot paste the link, as this my first post. This is what Bogeygirl says: (you will need to google the text below, and find this on qvc)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I love my Nook Simple Touch that I purchased in February of this year. I was so disappointed that after this short time and charging to 100% it would drain to 8% over night..This happened twice. I did NOT have the wi-fi on and the automatic shutoff I had set to 2 minutes so no issue there. No recent updates had been done to cause an issue like this.
I was not worried because it was still under warranty and would be replaced. So I called B&N CS and went through all the steps with them to make sure it was in fact defective.
He asked me to totally shut it down and do a hard reset and re-re-register the unit. I was not hopeful that this would work at all. I know that a hard reset can fix a multitude of sins but I never would have thought it would work to fix this battery draining issue..To my surprise it worked.. Battery charge is holding just like before.. I read a lot and usually charge it once a month.. I am so glad that this worked. Such an easy fix but I will continue to monitor the battery charge just in case.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I have tried it, and it seems to work fine, holding charge OK. Bogeygirl says hard reset, but it is the soft one. Foredog says that you don’t need to click the power button to sleep (just leave Nook to do the job for you), but I do click it to sleep, and I do also tap the screen, just to make sure that it is properly sleeping. It is fine at the moment. I think the whole problem with the battery is a software error with sleeping mode, as you say here. I think you are right.
I don’t have it rooted, as I only want it for reading.
Do you have any other advice for the battery? Or easier? I think everybody is having problems with the battery.:crying:
Thanks

Deep Sleep Battery Saver?
Does Deep Sleep Battery Saver help with the power-button not sleeping properly?
It performs several functions:
1. Supposedly automatically puts the device into sleep mode whenever the screen turns off (if you configure it properly).
2. Functions as a task killer, with a whitelist, to clear out buggy apps.
3. The Whitelist allows you to prevent useful apps from being killed.
I still use the power button to put the NST to sleep. Last night it drained about 7% overnight, although I leave WiFi on and read RSS feeds for an hour before putting it down. Also, DSBS is configured to wake up the device every four hours.

smayonak said:
Does Deep Sleep Battery Saver help with the power-button not sleeping properly?
It performs several functions:
1. Supposedly automatically puts the device into sleep mode whenever the screen turns off (if you configure it properly).
2. Functions as a task killer, with a whitelist, to clear out buggy apps.
3. The Whitelist allows you to prevent useful apps from being killed.
I still use the power button to put the NST to sleep. Last night it drained about 7% overnight, although I leave WiFi on and read RSS feeds for an hour before putting it down. Also, DSBS is configured to wake up the device every four hours.
Click to expand...
Click to collapse
The battery drain is due to some BN apps and Android System apps, mainly. I use the last version of "SystemApp Remover" for disabling apps (eg:AFfileDownloadService.apk,AccountAndSyncSettin gs.apk, BnAuthenticationService.apk, BnCloudRequestSvc.apk, DemoMode.apk, DeviceManager.apk, DeviceRegistrator.apk, Music.apk, NookCommunity.apk, Phone.apk, QuickStartActivity.apk, Shop.apk, Social.apk ,TelephonyProvider.apk, WaveformDownloader.apk).

kuskro said:
The battery drain is due to some BN apps and Android System apps, mainly. I use the last version of "SystemApp Remover" for disabling apps (eg:AFfileDownloadService.apk,AccountAndSyncSettin gs.apk, BnAuthenticationService.apk, BnCloudRequestSvc.apk, DemoMode.apk, DeviceManager.apk, DeviceRegistrator.apk, Music.apk, NookCommunity.apk, Phone.apk, QuickStartActivity.apk, Shop.apk, Social.apk ,TelephonyProvider.apk, WaveformDownloader.apk).
Click to expand...
Click to collapse
I thought it was due to the device not sleeping after the power button was pressed?
I also removed those APKs from the system directory, thanks to many of you guys.

Switching Wifi Off Worked Well
ApokrifX said:
WiFi is definitely a big one.
Any easy way to "auto turn it off" with screensaver activation?
Click to expand...
Click to collapse
I had a Kobo mini & was not happy with the formatting of PDFs, hence I *had* to get a Nook Simple Touch ... the PDF formatting is excellent. However, I soon suffered the battery problem & couldn't get it to charge. I followed the advice on this page and it works so much better now. This is what I did :-
1) Switch off the Wifi. I have no need for it anyway as everything I read is PDFs loaded via SD card.
2) To charge, make sure the device is fully off using the back power button.
3) I charge it using a wall socket, rather than a computer. I have heard that this makes a difference in charging times.
It's early days, regarding how long it stays charged, but I reckon I will be resorting to switching the power off, rather than putting it on standby. I'm just pleased I managed to get it to charge at all and I am back in business.

assembler31415 said:
I had a Kobo mini & was not happy with the formatting of PDFs, hence I *had* to get a Nook Simple Touch ... the PDF formatting is excellent. However, I soon suffered the battery problem & couldn't get it to charge. I followed the advice on this page and it works so much better now. This is what I did :-
1) Switch off the Wifi. I have no need for it anyway as everything I read is PDFs loaded via SD card.
2) To charge, make sure the device is fully off using the back power button.
3) I charge it using a wall socket, rather than a computer. I have heard that this makes a difference in charging times.
It's early days, regarding how long it stays charged, but I reckon I will be resorting to switching the power off, rather than putting it on standby. I'm just pleased I managed to get it to charge at all and I am back in business.
Click to expand...
Click to collapse
You probably don't want to resort to always powering off your Nook all the way, because the boot-up sequence uses about 3 or 4 times as much battery as regular use, making multiple reboots take up a large amount of battery.

Renate NST said:
To set your screen timeout to a arbitrary value (time in milliseconds):
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db
update system set value=10000 where name='screen_off_timeout';
.q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
Is there a way to change default values?

I have a nook simple touch glowlight, it's about 5 years old. Recently it has been saying battery too low to use. I plug it in and it goes to restart right away. When I look at battery life it my be at 89% (this was today). Is there something I can do to make this stop? It's quite a pain to to this everyday. I read on this a lot about a 1000 pages per week. In the "old" days a charge would last 20-30 days! Please help, I hate to get a new on, I love my nook!

[Q}Lollipop Yotaphone 2 battery life - any fixes?

Hi all,
Having just bought a Yotaphone 2, latest model 801 processor and with Lollipop installed, I was impressed with it... lovely screen, sharp response, great display on the back ....until I realised that battery life on the EPD or indeed doing nothing was (and is) terrible.
This somewhat negates the point of having the EPD. Because whether you use the EPD or not, as others have found, the processor seems to be spending 100% of the time doing something like trying to connect to Google headquarters to report my unethical swearwords as I look at the battery level heading south.
To try and make sure the phone was using the least power, I went through all the running apps and services and terminated as many as I could, turned off things like Yotafit tracking, turned off the service that sends all your contact details to the Kremlin, and so on... then, I turned on the Yotaenergy mode and despite that, we are at less than 24 hours with virtually no phone usage at all. Fully 50% of all the energy according to the battery stats is being used by Android System and Android OS processes when the system is in standby. And the historic battery screenshot shows that the processor is active 100% of the time., even though the phone has not been touched. (sorry, not attached, I'll post at some point, but its not very interesting)
So, does anyone have any clues about how this can be fixed? I have seen screenshots where people have shown that their processors are not active the whole time, and I imagine they have Lollipop? I have heard Lollipop has got some kind of bug which means that data connections are live the whole time, not sure if this is related.
(This might explain the sudden appearance of half price devices on eBay around six months after launch in the UK.)
Many thanks in advance!

YotaDevices has acknowledged the problems on Lollipop battery life, which is the reason they won't be shipping devices coming to USA preinstalled with Lollipop, but with KitKat. Now that I've played around with the EPD and created some widgets/applications for it, I can spot many places where things can go wrong in maintaining battery life and still keep things working.
Personally I've been lucky with the battery life on all versions of Android. When I updated to the last version of Lollipop (firmware 1.44), the phone did show poor battery life for hours after the installation was finished, before calming down to the promised 5 days stand by. Are you on the very last firmware? (Settings - about phone - build number)
As a last resort if your device won't settle down, I guess you could roll back to Kitkat, which had a very good battery life for pretty much everyone. You can install it with Yota's flasher tool: ftp://fw.ydevices.com/YotaPhone2/YotaPhoneFlasher/yotaphone2_flasher.exe
Just carefully select your own region and then the last version of KitKat (4.4.3) they offer. As you are rolling back from one major version to another, I would suggest flashing pretty much everything. You will lose your data.
Yota has said that they are working on bringing Lollipop 5.1 or 5.2 to Yotaphone 2. Let's hope that that works better.

Thanks that was very useful. The question is, will Yota do another build ... or build another device? I'm hoping the Y2 has a bit of life left in it yet and they do launch in the US - it can only help the development community!
I reset back to factory/Lollipop last night as it was eating battery so fast I could not believe it, and I am on the latest build 1.44EU (and was before). Since then.. it doesn't seem to be misbehaving so much, but it does seem to insist that the WIFI is on (when it is switched 'off' in the settings) by 'on' I mean the battery usage recorder... I wil take your advice and 'take it slow' for now, but may flash back to Kitkat if necessary. It is a bit tedious having to reinstall all your apps by hand but this seems to be the only way to ensure it is relatively clean.
The screengrabs below show the phone doing nothing at all in Yotaenergy mode - per first post.

ridgemagnet said:
Thanks that was very useful. The question is, will Yota do another build ... or build another device? I'm hoping the Y2 has a bit of life left in it yet and they do launch in the US - it can only help the development community!
I reset back to factory/Lollipop last night as it was eating battery so fast I could not believe it, and I am on the latest build 1.44EU (and was before). Since then.. it doesn't seem to be misbehaving so much, but it does seem to insist that the WIFI is on (when it is switched 'off' in the settings) by 'on' I mean the battery usage recorder... I wil take your advice and 'take it slow' for now, but may flash back to Kitkat if necessary. It is a bit tedious having to reinstall all your apps by hand but this seems to be the only way to ensure it is relatively clean.
The screengrabs below show the phone doing nothing at all in Yotaenergy mode - per first post.
Click to expand...
Click to collapse
I am quite confident that they will release updated Lollipop sooner or later. They don't have the resources to piss off all their customers just yet.
Your Wifi still does some scans on its own for Google's location service, even if it's not enabled. You can disable this feature in the advanced wifi settings. But that is not the cause of your battery problem. Basically your device is awake all the time, meaning something is holding a wake lock. And by something I mean one of Yota's EPD compoments, which are counted as part of "Android OS" and "Android System" - your biggest battery hogs. It could be one of the EPD widgets that is misbehaving, or it could be some specific combination of them, or just something out of your control.
You could try removing ALL the widgets from the rear screen from Yotahub, then restart the device, and then let it run for an hour with the screen off. Then check the detailed battery log if the device went to sleep or if it was awake. If it went to sleep, you can try adding widgets back one at a time, and then check again if the device sleeps. Basically all the widgets which update periodically hold a wake lock momentarily (time, battery, calendar, weather etc). Of course if the problem lies on Yota's EPD framework, then this wont help at all.

Jeopardy said:
I am quite confident that they will release updated Lollipop sooner or later. They don't have the resources to piss off all their customers just yet.
Your Wifi still does some scans on its own for Google's location service, even if it's not enabled. You can disable this feature in the advanced wifi settings. But that is not the cause of your battery problem. Basically your device is awake all the time, meaning something is holding a wake lock. And by something I mean one of Yota's EPD compoments, which are counted as part of "Android OS" and "Android System" - your biggest battery hogs. It could be one of the EPD widgets that is misbehaving, or it could be some specific combination of them, or just something out of your control.
Click to expand...
Click to collapse
Agreed, I suspect the YotaFit app going bonkers despite my efforts to kill it.... or the Yotagram service, the thing is, looking at the Yota specific apps, you don't really need them, as you can flip the screen with the Yotamirror, and then use any Android app. Sure it would be nice to have notifications on the EPD, but my main focus for this phone is use in bright daylight, and long battery life, not to actually look at the thing 24x7 so I can respond to emails every 30 seconds.
At this point though I'm just trying to determine how bad the underlying hardware is. The GPS on this phone seems to a bit flaky, as does the basic reception of mobile signal. (And I'm not using a metal bumper.) So, I'm happy to flash back to KitKat 4.4.3 to try and give it the best chance..
So, any clues/links about the Yota flash tool? I've put the phone into USB debug mode, installed the flash tool on my windows 7 desktop, and installed ADB/Fastboot as well, but at this point I'm having a bit of an android driver problem, and ADB can't see the phone so that probably explains why the Flashtool says 'waiting for device' when I fire it up. I will go digging to fix that, but I assume that the Flashtool will do all the stuff like putting the phone into bootloader mode, unlock etc...

ridgemagnet said:
Agreed, I suspect the YotaFit app going bonkers despite my efforts to kill it.... or the Yotagram service, the thing is, looking at the Yota specific apps, you don't really need them, as you can flip the screen with the Yotamirror, and then use any Android app. Sure it would be nice to have notifications on the EPD, but my main focus for this phone is use in bright daylight, and long battery life, not to actually look at the thing 24x7 so I can respond to emails every 30 seconds.
At this point though I'm just trying to determine how bad the underlying hardware is. The GPS on this phone seems to a bit flaky, as does the basic reception of mobile signal. (And I'm not using a metal bumper.) So, I'm happy to flash back to KitKat 4.4.3 to try and give it the best chance..
So, any clues/links about the Yota flash tool? I've put the phone into USB debug mode, installed the flash tool on my windows 7 desktop, and installed ADB/Fastboot as well, but at this point I'm having a bit of an android driver problem, and ADB can't see the phone so that probably explains why the Flashtool says 'waiting for device' when I fire it up. I will go digging to fix that, but I assume that the Flashtool will do all the stuff like putting the phone into bootloader mode, unlock etc...
Click to expand...
Click to collapse
The widgets I'm running at the moment without any problems are Time, Mini Calendar, weather, battery, and communications (the small widget which shows phone calls, notifications and sms). And of course my own widget.
The best way to make sure there are no useless services running is to root the device and uninstall them completely, but that's another story.
For the flashtool to detect the device, you need to boot it into download mode manually. The easiest way is to turn off your device and plug the usb in while holding volume down -button. The screen will show "download" or something in very small white text. After that the flashtool should find the device. You probably don't have to flash the user partition (it asks for it separately), i.e. the simulated sdcard section which holds all your photos, documents and music.
Edit. And when you have kitkat installed, the first thing you might want to do is to disable automatic system updates. Otherwise it will nag you about the Lollipop update all the time.

I've been facing similar issues and am considering a downgrade when I have the time. I'm really disappointed in yota and won't be buying their next device.
I have found this thread useful, you may too.
http://forum.xda-developers.com/android/general/guide-extreme-battery-life-t3095884

thanks gents, oddly, the advice to let the phone 'calm down' seems to be working. I decided not to revert to KitKat (yet), as every day I use the phone the battery life seems to improve. Yesterday it was down to 40%, today 60% after about a days use. I'm thinking a week of running in will give it time to stabilize. I would love to root the phone but I want to use the Good app, and that doesn't run on rooted phones... (shame but I guess that's the flipside of working for a big corporate for you!)

ridgemagnet said:
thanks gents, oddly, the advice to let the phone 'calm down' seems to be working. I decided not to revert to KitKat (yet), as every day I use the phone the battery life seems to improve. Yesterday it was down to 40%, today 60% after about a days use. I'm thinking a week of running in will give it time to stabilize. I would love to root the phone but I want to use the Good app, and that doesn't run on rooted phones... (shame but I guess that's the flipside of working for a big corporate for you!)
Click to expand...
Click to collapse
Try putting the battery widget on your epd. If it shows 5 days remaining when you are above 85% and you don't use the phone, then the device works as advertised.
That Good app sounds like a real killjoy. There seems to exist some Xposed modules to disable the root check, but they seemed to be rather finicky to setup and very easy to mess up.

I was suffering from terrible battery life after the lollipop upgrade and the EPD battery widget was never showing much above 1d anymore. After much research and tinkering, it has now improved and I am seeing greater than 3d again. I think the culprits were maybe google fit tracking which I have now turned off and I also de-installed and re-installed the google play services updates which is a tip I saw in an android forum. I also over the last two days have received several yota widget updates which may have also helped. At least for now I am seeing a comfortable day's use again!

I experienced poor battery life out of blue again. I went through all the settings, cleared dalvik-cache and cache partition, tried disabling everything, but nothing helped. It only showed <1 day battery life at 100%.
But then I went to mess around in the developer settings, and when I set the animation scales from 1x to 0.25x and enabled "Force GPU rendering", the battery life returned instantly to 5 days.
Just thought I'd add this to the list of things to test out if someone's experiencing poor battery life. The forced GPU rendering might have some unexpected effects on some software rendering based games.

dont know if this will help but just seen some of the new features of android m "marshmallow" one of which is doze and there is a separate app available on play store for this. i have installed and it has helped battery life !!!

I was going through terrible battery life after Lollipop as well. Suffered, tinkered, tried various things. Eventually I just said screw it, backed everything up and factory reset it from recovery. Since then it seems like it's almost back to it's old self. Obviously having root and using some kernel control apps, greenify and some other things helps it but It will happily do at least a couple of days with little-normal usage. Still don't think it's as good as KitKat but it's not too far off. The EPD really does help spread battery out too.

I did the same thing but a 3 weeks on, the battery is as shocking as ever.
Today, on battery since 0730, now @ 1115 51% and 3hrs left!??
No obvious apps causing battery drain, just google services!

Rarelyamson said:
I did the same thing but a 3 weeks on, the battery is as shocking as ever.
Today, on battery since 0730, now @ 1115 51% and 3hrs left!??
No obvious apps causing battery drain, just google services!
Click to expand...
Click to collapse
I have had the phone nearly a week, and these are similar figures I experience. What's the point of the epd if my battery dies by lunch!
Sent from my YD201 using Tapatalk

I think it is something with Android 5.0 that is causing the drain issues. I can go anywhere from half a day to a week with good batteyr life and then it will randomly start draining again. Some background activity seems to hold a permanent wakelock and will not let go of it. I am unable to pinpoint what app is creating the wakelock with better battery stats or wakelock detector since there isn't access to kernel wakelocks in either of the apps for our phone. A restart always fixes things though, so I have a tasker script now that lets me know when idle battery drain exceeds a threshold for too long so I know to do a restart, it's not elegant, but my battery life is exponentially better and gives me enough battery life to make it through the day without a recharge and leave the eink screen on all night as a tv remote.

I got a new phone
sportsfan986 said:
I think it is something with Android 5.0 that is causing the drain issues. I can go anywhere from half a day to a week with good batteyr life and then it will randomly start draining again. Some background activity seems to hold a permanent wakelock and will not let go of it. I am unable to pinpoint what app is creating the wakelock with better battery stats or wakelock detector since there isn't access to kernel wakelocks in either of the apps for our phone. A restart always fixes things though, so I have a tasker script now that lets me know when idle battery drain exceeds a threshold for too long so I know to do a restart, it's not elegant, but my battery life is exponentially better and gives me enough battery life to make it through the day without a recharge and leave the eink screen on all night as a tv remote.
Click to expand...
Click to collapse
In the end, I got a new phone after my Yotaphone decided to brick itself. Its a Zopo Speed 7, Octacore, dual SIM, nice screen, and does 4G very well in my part of the world. It is also around $200 at time of writing. Its a Chinese phone typical of the genre, Zopo seem to be moderately responsive to bugs compared with Yota... This Zopa phone is running 5.1 Android and I can tell you that Lollipop is not the problem...
That's after charging the phone and leaving it overnight, with the battery saver mode on... not too shabby. Of course it won't actually last 28 days, but this phone is nothing special and it is capable of running without all those services running that the Yota has.
The Yota spent its entire time when I had it trying to contact Moscow with that dodgy 'dictionary app'. What (honestly) is the point of the e-ink display if it doesn't save power...

If you are experiencing "always awake" and wifi always on despite your settings saying otherwise it may be worth going into your advanced wifi settings and changing "wifi frequency band" from "auto" to "2.4 GHz only. I remember reading this tip somewhere else for an Android 5.0 phone that was having battery issues similar to this. I made this change about 24 hours ago and have noticed a dramatic difference in battery drain when the screen is off. When I look at my battery stats I am no longer seeing a solid bar for both wifi and awake. Worth trying.
For what it's worth, I have had fairly light use today, some checking of emails and facebook, 40 mins or so of music via bluetooth (with screen off). Total screen on time of 35 mins. The phone has been off charge since 06:30 this morning. It is now 17:00 and is showing battery of 71% with an estimated 2d and 8h left. Better battery stats show deep sleep of 71% whereas previously it had shown awake at 100%. Far better than I had before.

stapo101 said:
If you are experiencing "always awake" and wifi always on despite your settings saying otherwise it may be worth going into your advanced wifi settings and changing "wifi frequency band" from "auto" to "2.4 GHz only. I remember reading this tip somewhere else for an Android 5.0 phone that was having battery issues similar to this. I made this change about 24 hours ago and have noticed a dramatic difference in battery drain when the screen is off. When I look at my battery stats I am no longer seeing a solid bar for both wifi and awake. Worth trying.
For what it's worth, I have had fairly light use today, some checking of emails and facebook, 40 mins or so of music via bluetooth (with screen off). Total screen on time of 35 mins. The phone has been off charge since 06:30 this morning. It is now 17:00 and is showing battery of 71% with an estimated 2d and 8h left. Better battery stats show deep sleep of 71% whereas previously it had shown awake at 100%. Far better than I had before.
Click to expand...
Click to collapse
Have you tried using the setting so Wifi is only on while screen is on? (Unless on charge...)

I think I found the issue, at least with my phone.
I was syncing with exchange, and there is a nasty bug with android 5.0 and exchange sync. The sync is taking forever and doesn´t sync everything. Calendar and contacts missing.
Then I removed the ActiveSync connection on my phone and set up the app Nine to sync instead.
After that I got much better battery. This may help for others as well. The phone is just hammering the exchange server all the time and this takes up a lot of power.

Battery Performance after Nougat update - how is it working for you? (Phone Idle...)

Hello!
I updated to 7.0 last Friday and the phone has been acting very well, overall.
But I am having some problems with the battery life. In actuality, it can last 3 days in standby, but I feel like the "Phone Idle" is eating WAY too much battery regardless.
The drain when in standby, for example, should be closer to 1% for 7-8 hours, but for me it is closer to 7-8%, almost 1 % drain per hour in a supposedly sleeping state.
Right now, my stats are as follows, after 1 day and 10 hours (with 1 day 3 hours left):
Screen 30% (2h 23m SoT, 677mAh)
Phone Idle 20% (1d 10h, 459mAh)
Google Play Services 11% (radio active 1h 24m, 246mAh)
Cell Standby 10% (radio active 4m 45s, 234 mAh)
Android OS 6%
Android System 5%
... the rest is some apps with negligible usage.
So, this tells me that something is very wrong with Phone idle. It has consumed almost as much as the screen.
I read a lot about this issue and a large number of reports claim that doing a factory reset does not fix the problem. I am scared to do a reset, since Debloater no longer works in Android 7, and I will not be able to deactivate crap like all facebook services and What's New. So, it's a bit of a no-exit situation... I don't think rooting and using custom roms is a good idea for me, as I would like to retain warranty of my device until it expires. I plan to root and modify it after that.
Still, are any of you experiencing this issue since the Nougat update? Any ideas on how to solve it?
So far, suggestions include:
- removing SD card
- turning adaptive brightness OFF
- turning location accuracy to battery-saving mode
- turning Wi-Fi awake ON (only when charging), or OFF
- going to App settings and selecting 'reset all app settings'
- wipe cache partition by holding power and volume up keys (while phone is on) until you feel 3 vibrations
I've already done these things today (except sd cards, no way I am giving that up) so it's early to say if they helped.
Feel free to use this thread even if you just want to share your problem-free battery experience on android 7 with your Sony Z5C. I am curious to see how does a "perfectly fine" z5c unit perform in terms of battery, on Android 7. What is the "real" expected real-life performance?
Thanks for reading.

The things you suggest are not gonna change too much.
* Resetting app settings or removing your SD card is not gonna do anything at all.
* The location accuracy can make a little difference (let's say 2% at the end of the day) but the problem with location settings isn't HOW it's gonna look for a location, but HOW MANY TIMES. If you want longer idle, location services should be off (in one or another way) when your phone is sleeping.
In my eyes, with the things you have been doing is not worth the hassle.
** With Nougat, you still have the opportunity to extend your battery life a lot with apps like
Doze Settings Editor
My Android Tools
And you'll have to debloat.
I'm still testing these possibilities. But I just got on Nougat today, and with my initial settings, I broke some functionality I need. (Alarm Clock didn't work in deep sleep and I couldn't install WhatsApp). Maybe I get it working the way I want in the next few days or week, but I guess so.
** Having a kernel that allows you to change governors can also make a huge difference. Governors will give you the opportunity to buy (a lot of) battery life and to reduce heat, but you pay with performance.
** One more thing that can make a huge difference, is performing a clean install. So you need to install Nougat (or whatever ROM you use) on a clean system, and install your apps manually.
"I am curious to see how does a "perfectly fine" z5c unit perform in terms of battery, on Android 7. What is the "real" expected real-life performance?"
-->> With these things done and Doze/MyAndroidTools optimized, your phone shouldn't use more than 2-3% overnight. On an optimized MM (with XPosed/Greenify/Amplify) I had to recharge about 2 times a week. Maybe on Nougat it will be a little bit less because there's no XPosed/Amplify, but it should be possible that your battery life will be about three times as long as you have right now.
** If you want a better understanding about battery life, forget about these stats. You won't learn anything from the stats (like you gave us). Instead you can use an app like Better Battery Stats. Especially in (deep) sleep, knowing as much as possible about wakelocks is quite essential.
By the way, you can't call that a "real" expected thing. Battery life is always a compromise, and balanced with performance. Optimization (in the way I'm speaking about) is that much more than limiting performance/apps/widgets while you use your phone, and turning your phone in a dead object as soon as possible when the screen is off.

--jenana-- said:
...
Click to expand...
Click to collapse
Thank you for this response, it's quite elaborate. But I am fully convinced that the Phone Idle issue is not due to ANY of my settings and should not plague a device, even if it is non-rooted. Most of the suggestions you added would require root, or operations that are beyond what I am willing to risk right now. Even the simple root would likely require me to downgrade to 6 and most likely brick my device due to unreliable nature of many of these guides.
I will definitely be trying out the BBS non-root edition as soon as I get home and manage to activate it properly.
But, overall, a stock non-rooted android 7 should not drain as much battery in idle mode. I know that via rooting you can get as close to 0.2% battery drain per hour. But what about no root?
Ultimately, I will root the device at some point when warranty has expired, or is close to, and I will get it to drain extremely slow with xposed and some tweaking. But we shouldn't be required to do this for normal battery life. It's becoming ridiculous at this point.
BTW. Is doing the "Repair" thing from Sony PC Companion equatable to doing a "clean install"? In other words, can I do this without having to actually re-install a rom completely and without rooting the device?

Bobzee said:
Thank you for this response, it's quite elaborate. But I am fully convinced that the Phone Idle issue is not due to ANY of my settings and should not plague a device, even if it is non-rooted. Most of the suggestions you added would require root, or operations that are beyond what I am willing to risk right now. Even the simple root would likely require me to downgrade to 6 and most likely brick my device due to unreliable nature of many of these guides.
I will definitely be trying out the BBS non-root edition as soon as I get home and manage to activate it properly.
But, overall, a stock non-rooted android 7 should not drain as much battery in idle mode. I know that via rooting you can get as close to 0.2% battery drain per hour. But what about no root?
Ultimately, I will root the device at some point when warranty has expired, or is close to, and I will get it to drain extremely slow with xposed and some tweaking. But we shouldn't be required to do this for normal battery life. It's becoming ridiculous at this point.
BTW. Is doing the "Repair" thing from Sony PC Companion equatable to doing a "clean install"? In other words, can I do this without having to actually re-install a rom completely and without rooting the device?
Click to expand...
Click to collapse
Haha, I'm bad in keeping my stories short.
If you're non-rooted, you won't ever get that experience. Not even close. It depends on the apps you're using, but a few messenger-apps (like facebook/fb messenger/whatsapp) + some google apps like maps/calendar/... or weather apps rely heavily on location settings, and they always want to sync or connect with their mothership. To illustrate my point, at a certain point last year I had done some dirty flashes, I had quite some apps and widgets like this installed, but in the end it drained 30% battery overnight. After clean install + debloater it went down to 10% overnight. After heavily tweaking with Amplify/MyAndroidTools/Greenify and so on, it went down to 1% overnight.
Without root, the only thing major thing you can do is: clean install. Almost everything else (with a large enough impact on battery life) is beyond your control. Apparently the choice of developers is to implement smooth and always-up-to-date apps and widget, always ready to serve you the latest news/messages and so on. I agree with you that smartphones these days aren't lean at all. And there are no secret settings that will give you a much better battery life all of a sudden.
I've never used PC Companion. I've no idea what it does or how it works exactly. I don't think it's powerful enough to solve issues with wakelocks.
Literally:
* If you want control over Android, you need to root. Without root: no control whatsoever;
* Clean install = everything out, fresh start. You can't paint your wall without removing your paintings.

Thanks again for the great response. And PC Companion is Sony's default software that comes with their devices and is used to backup/reset/update, etc.
To clarify, I never expected any secret battery options that will solve all my problems. I was rather hoping that it's a well-known problem with a possible non-root solution.
As to rooting, yeah - I would love to do it, but I am afraid your guide won't work for 7.0, would it? I am already using 32.3.A.0.376-R2D. In any case, rooting so soon after buying it (a few months) is not something I am rushing to do.
Also, to add something else - my old Z1, when it was on KitKat 4.4, used to last me 5 days with low usage EASILY. The thing actually drained about 1% per night without having to root it, with the normal stock features and 3G network on all the time. Something just went wrong down the road for many manufacturers and their relationship with the android OS. The battery life became abysmal for me after android 5 and above it.
And then, at work, I have a Nexus 5x on my desk for testing, which lasts 6 days in standby with a battery which is not dramatically bigger, with no root. But it has no SIM card or 3g/4g on at all, only WiFi.
This brings me to believe that you are absolutely right about location services.
And a last question... if I am to root now, from FW 32.3.A.0.376-R2D, what would you say would be the most reliable method? I saw your guide and really liked it, but it seems to require MM to begin with. Seen many other guides, but in each guide there are responses about frozen/bricked devices, or issies with no working camera/finger scanner/etc... It's a bit worrying.

brokich said:
Thanks again for the great response. And PC Companion is Sony's default software that comes with their devices and is used to backup/reset/update, etc.
To clarify, I never expected any secret battery options that will solve all my problems. I was rather hoping that it's a well-known problem with a possible non-root solution.
As to rooting, yeah - I would love to do it, but I am afraid your guide won't work for 7.0, would it? I am already using 32.3.A.0.376-R2D. In any case, rooting so soon after buying it (a few months) is not something I am rushing to do.
Also, to add something else - my old Z1, when it was on KitKat 4.4, used to last me 5 days with low usage EASILY. The thing actually drained about 1% per night without having to root it, with the normal stock features and 3G network on all the time. Something just went wrong down the road for many manufacturers and their relationship with the android OS. The battery life became abysmal for me after android 5 and above it.
And then, at work, I have a Nexus 5x on my desk for testing, which lasts 6 days in standby with a battery which is not dramatically bigger, with no root. But it has no SIM card or 3g/4g on at all, only WiFi.
This brings me to believe that you are absolutely right about location services.
And a last question... if I am to root now, from FW 32.3.A.0.376-R2D, what would you say would be the most reliable method? I saw your guide and really liked it, but it seems to require MM to begin with. Seen many other guides, but in each guide there are responses about frozen/bricked devices, or issies with no working camera/finger scanner/etc... It's a bit worrying.
Click to expand...
Click to collapse
The guide I wrote is actually outdated. I wrote it in the first weeks after MM was released.
IF you want to root, it's actually not that difficult.
0. Prepare your computer, because you need the right drivers and some tools.
1. If it's the first time you unlock your bootloader, you might want to backup your TA-partition. I leave the details to other people, there are great guides about it in this subforum. As far as I know, to do this, you need to go back to marshmellow. I've never done this, because I unlocked my bootloader before there where any tools or any knowledge available about how to do this. So my original TA partition is gone forever (and I've never missed it).
2. Flash Nougat. This is really simple. You only have to download a (large) file, click a few buttons in flashtool, drink a coffee, and it's done.
3. Make a kernel with Rootkernel. It's basically like following a recipe, and in the end you have a file (the kernel) which you can install with the tools on your computer. In this step, you made root access and TWRP-recovery.
4. Reboot
Personally (and I know not everybody will agree), I wouldn't bother with backup of the TA partition. So *I* would just unlock the bootloader and move on. But your first step should be: make yourself familiar with basic adb commands and with how to make and restore a (full) backup. I really don't know why it causes so much problems for some people. It's true, sometimes you run into unexpected behavior. But then you have 2 options. Go back to last TWRP-backup or get your **** together and start from scratch.
By the way, if I was you (with your priorities), I wouldn't upgrade to Nougat. There are much more tools available to optimize marshmallow. Install some of them, get familiar with them, and in a few days you have a reliable and battery-friendly system.

Hm, these are some fair points.
Thanks for that little root guide - but why would you skip backing up the TA partition? Wouldn't that break some core functionalities? At least that's what I've read (cause I did go through most of the root guides for MM in this section).
I guess people have problems because the guides are sometimes incomplete, or people themselves are not following them properly. I would not expect myself to mess-up instructions, and whenever I have problems with guides, it's usually some kind of disparity between my side and their side. Or the guide is wrong, or something is missing. Many things can go wrong, yeah.
It's not that I am not willing to take risks, it's more that I might end up getting the overheat issue at some point - and at that point I would like to use my warranty. If I mess up anything, the warranty will be lost too soon.
Furthermore, I believe Nougat is far superior to MM, and I am willing to wait unofficial development to continue for at least another year. Perhaps in that time the z5c will have stopped receiving official updates, and we can all settle on some rooted, stable and working version of (probably) 7.1 or smth a bit after it, with working Xposed framework as well. At that point I would like to root and truly make the device shine in terms of battery life.
But for now, I'll have to limit myself with a factory reset at MOST.
I am doing an experiment now, after charging the phone completely. Turned location services off, and google services to "battery saving mode". I've turned wi-fi to off and am just going to be using a constant LTE connection. Auto sync is on.
I'd like to see how the phone handles this configuration without further intervention. So far, after 30 minutes post-charge, it's still sitting at 100%. But I'll have to check the overnight drain to verify any actual improvement. In any case, my 100% charged phone predicts 3 days of standby in the battery settings.
edit: looks good after 1 hour (https://drive.google.com/open?id=0Bwg-0GLG0gP9Wmt1ekZCTFNnS3c)

brokich said:
Hm, these are some fair points.
Thanks for that little root guide - but why would you skip backing up the TA partition? Wouldn't that break some core functionalities? At least that's what I've read (cause I did go through most of the root guides for MM in this section).
Click to expand...
Click to collapse
Mwa, yes and no.
Yes 1: By unlocking bootloader you break your TA partition and loose functionality.
Yes 2: If you ever want to go back to a phone which is unrooted and locked with all functionality, you need that backup.
No 1: There are DRM-fixes. Rootkernel (and the entire 2nd or 3rd step in my other comment) will fix DRM-keys too. And about every modified kernel you'll find over here has that DRM-fix + a few tweaks, so you don't have to worry, you won't miss anything.
I guess there are two kind of people. Some people say "You never know if you ever gonna need it, so you would be stupid not to back it up. After you click that button it will be gone. Forever." They are right. Some people say "Why bother, it's too much work, in the end you'll loose that backup, and actually you won't ever use it. And if it doesn't go smooth, it will give you unnecessary stress". They are right too. I'm in the second group. And I don't want to convince you that what I say is anything better than what others say, I'm just explaining my view...
Also, a lot of tools we use to experiment and tweak the sh#t out of our Z5C are highly experimental and not debugged. I don't care because partially it's a fun way to play around with it and I don't rely on my phone. If it doesn't work tonight, I'll find a way to make it work tomorrow. Again, that's my view...
By the way, I had to send my phone back to sony with a problem (unrelated hardware issue), and my warranty wasn't void.

Ha, that's very interesting. Perhaps they didn't bother to check for root at all, or they did and did not care. Maybe it's really hit and miss...
Overall, I am not extremely worried about it, as the device has actually been acting good so far, with no sign of hardware problems.
Also, I am not really going to gain that much by rooting Android 7, and I have no desire to have to stay on 6. When Xposed is well-developed and reliable on nougat, I'll probably go through the most promising method I can find and do the modifications that are required.
And yeah, I get your point about having fun, and I agree completely. But this device is important to me and I can't really risk it at the moment.
Anyways, the device is at 98% after 3 hours + of idle, which doesn't look too bad. I think perhaps adding the Greenify app might improve it a bit more, making it quite strong as a result, without the need of any root.

On more thing. Actually battery life on Nougat seems to excellent.
I did 4 things (not much work):
1) Edit doze settings more aggressively Doze Settings Editor, with the built-in "GeraldRudi"-preset. It should work on non-root too, but with slightly less aggressive settings.
2) Greenify, of course without the XPosed settings, and without aggressive doze. I think this didn't have any impact on battery performance/deep sleep, because Doze Settings was much more aggressive.
3) Tasker-module to put auto-sync off at night.
4) Kernel Adiutor to set governor to interactive. Obviously at night there was about no load on the CPU at all, but I did it to reduce heat.
All the rest is pretty standard. A lot of Google Apps are installed, messengers (FB messenger, WhatsApp) and social media, I even have a weather widget installed; all working normally.
Overnight it didn't use any power: 0,0% drain per hour; 0% over a 10h period of time. -->> battery stats

That's insane!!!! Big ups
I will absolutely try the Doze editor.
Sadly, no tasker with no root, but I might as well turn off auto-sync manually at night.
The kernel editor, I'm guessing, is also off-limits for me with no root.
What I did was to just turn off location and use greenify. My current idle draw is 0.66%.
But your is perfect. That's exactly what I want to achieve. Close to 0% draw when idle. That's how it should be.
Do you think it will be possible to achieve similar results with just the doze settings from step 1? (+turning auto sync off at night)

Bobzee said:
That's insane!!!! Big ups
I will absolutely try the Doze editor.
Sadly, no tasker with no root, but I might as well turn off auto-sync manually at night.
The kernel editor, I'm guessing, is also off-limits for me with no root.
What I did was to just turn off location and use greenify. My current idle draw is 0.66%.
But your is perfect. That's exactly what I want to achieve. Close to 0% draw when idle. That's how it should be.
Do you think it will be possible to achieve similar results with just the doze settings from step 1? (+turning auto sync off at night)
Click to expand...
Click to collapse
Your idle time doesn't look bad at all. Without something like that Better Battery Stats it's hard to guess if some apps use CPU/power/... or cause unnecessary wakelocks, but if you use 6-7% over 10h idle time, it's not that bad.
As far as I know, changing governor without root is a no-go. Not possible, only the system has the right permissions. By the way, this should affect idle time that much, it mostly affects your phone while you use it.
Doze Editor should make a difference, because it speeds up the time after you turn off your device to put it in deep sleep. Out-of-the-box, that takes a long time (I don't know how long, but it's suggested to be about 30 minutes). Standard settings in Doze Editor, which you can use with adb and without root, bring that back to 3 minutes. It's fully explained in that Doze Settings-thread.

Thanks for the info
I tried Greenify since last night and it seemed to actually slow my device down. I could literally sense lag in the OS and nothing else could explain it. There was also a delay with every hit of the power button before the screen comes on. This, to me, was more bad than good, so I uninstalled this app. Perhaps it truly is a bit useless, or even detrimental to performance without root.
These Doze settings is what I will be trying out tonight, but I fear it might be a similar story to Greenify and not help me much without having root, or even potentially slow the device down?
Furthermore, I uninstalled all Google Play services updates and re-installed it. It used to take ~450mb of space, now it's back to ~150mb.
Hopefully, this will improve the Google services battery drain, because right now it is on the top of the list:
79% battery left, 2d 16h remaining:
25% google play services
15% phone idle
15% screen
12% cell standby
So, play services is still hogging too much battery, even with location off.
I re-installed it, so I have yet to see if this has any positive effect.

Z4 tablet problem too
I'm getting high battery drain on idle on my Z4 tablet, haven't attempted any fix yet.

My experience is a very big battery drain even if a clean install. I used MyAndroidTools to stop all unnecessary Google Play Services , with Kernel Audiutor I selected interactive governor CPU, with Doze I used GeraldRudi presetting. Switching off LTE, wifi, bluetooth and data , in less than 3 hours I loose 30% of battery, can not arrive to evening with a charge. I am back on 6.0.1 and I am able to recharge my Z5C every two days !

alpadolmeri said:
My experience is a very big battery drain even if a clean install. I used MyAndroidTools to stop all unnecessary Google Play Services , with Kernel Audiutor I selected interactive governor CPU, with Doze I used GeraldRudi presetting. Switching off LTE, wifi, bluetooth and data , in less than 3 hours I loose 30% of battery, can not arrive to evening with a charge. I am back on 6.0.1 and I am able to recharge my Z5C every two days !
Click to expand...
Click to collapse
That definitely sounds like you have one of those problematic units, with overheating and extreme battery drain, or perhaps it was due to a bug in the 7.0 ROM you used.
I am still able to get 2 days of my phone with 7.0 and no root, but that to me seems very unsatisfactory. Such a battery should easily last you a week with a single charge with LTE on, if you keep it idle most of the time. In my case, that's up to 3 days. If you see jenana's battery stats, it is possible to achieve almost 0.0% drain per hour at the cost of some performance. In those conditions, with ULTRA stamina on, your phone should last about a full month in idle mode with active network signal reception during that full period of time (but not LTE and other extras).
6.0.1 should be even better due to the Xposed framework, but I don't think that more than a month is a realistic with any OS and the current batteries.
Surely, 2 days is ridiculous. I don't use my phone much some days and the drain seems to be flat. It should be ALMOST 0% per hour. I assure you, even auto-syncing should be fully usable at all times without any kind of insane battery drain.

roycol said:
I'm getting high battery drain on idle on my Z4 tablet, haven't attempted any fix yet.
Click to expand...
Click to collapse
Seems I am in the same boat as you I really was enjoying Nougat, but I cannot live with half a day of charge. Last thing to try unrooted nougat and phh's superuser. Maybe this can resolve the massive drain. It is sad, really. I will report back with my findings...
I would appreciate any hint on to overcome this issue.
Cheers everyone!

Poor for me. I can get a day's worth out with about 3 to 4 hrs SOT but usually now my battery is less than 10% when I put it on charge. Marshmallow I was easily getting 4hrs SOT and down around 20 to 30% battery left. I love nougat but battery life is really poor. I have a mate who had x compact and 2 hrs SOT only uses about 25% battery. I just don't get it, so must be Sony with a poor ROM and not tested correctly or nougat not designed for this phone.
Sent from my E5823 using Tapatalk

Hey, I can not understand it when people say the battery runs better than never before. I updated to 32.3.A.0.378, Sony has put the CPU on the best performance "performance". So with me runs the Z5C on the settings max. 10 hours. In the plaintext, I need root to convert this as it did at Marshmallow "interactive".

For everybody that experiences battery drain and heat problems: try rooting the phone with phh superuser instead of superSu. I couldn't get through a single day with superSu. Now, the phone is cool and endurance of battery is back to normal.
Sent from my E5823 using XDA Free mobile app