Related
I don't know what all your experiences are, but I noticed the past few days that my epic is getting hot on the back.
I also noticed that my battery is draining more so than usual. When I got the update last week my battery life sucked, but now since this overheat thing it's gotten worse. It drops a lot even when in standby.
I do not have gps, wifi, anything else on. I am not rooted. Didn't do any battery tweaks. This is completely stock di18.
This is normal use with 3g. It's getting annoying and I'm hoping someone has an answer. Thanks!
Do you have any email accounts configured in the mail application?
This happened once or twice - I rebooted the phone and all was peachy.
Sounds like you have a rogue process wearin it out.
Yeah my phone overheated yesterday while charging....this phone has a few more steps to go before it really beats my hero...
Sent from my SPH-D700 using XDA App
I partly found out what the problem was, but it seems you guys are ahead of me. I had some process keeping my CPU running at 95-100% nonstop. I still haven't figured out what the process was, as now it is back to the normal 5-15%, but I'll have to keep an eye on it now.
the task manager widget turns red and it shows you what process was causing it...for me it was the xda app...a few times.
I think my problem was not backing out of WordFeud. I didn't notice anything on the task manager though. Hasn't happened since that one time.
this happens to me when i'm plugged in and using gmail. screen flickers and then shuts off. the screen-off battery indicator shows the batt. gauge and a little thermometer sign next to it indicating it's too hot.
wtf?!?! this has to be a defect. anyway, is there any official word on this? any pr from sammy/sprint?
i have read elsewhere about some epics resetting themselves a few times a day which could indicate an issue with heating (at least on a pc). so if you think it might be hardware its possible. otherwise keep doing what your doing, monitor your processes for anything thats eating it up, go to about phone > battery use > cell standby to see your time without signal. the higher this is the more battery use. also, might want to consider a startup manager to prevent the 2 DRM files (search forums) from running as this can affect batt life too
you can also use setcpu even (free on here, search it) to throttle your cpu down when it hits a certain temp.
This is very interesting... My wife and I both have this phone, she has had this happen several times after the last update (I though she was just crazy). Me on the other hand... No problem!
I need to look into this a little deeper.
The only time my epic's battery gets hot is during heavy use or gps. Gps/Nav makes it heat up like a mofo. But other than that... *knocks on wood* Its all good, no problems. As far at battery life, I am rooted and using SetCPU to turn down the processor while the screen is off, helps a ton. Not using anything other than that... was using juicedefender but then I started not getting calls or text...
Sent from my SPH-D700 using XDA App
One thing, I learned, that didn't help my battery was putting my phone in the locker at work. That thing must have killed my TWS and ate my battery alive.
i feel like this thread will start to die but i had a weird somewhat related issue last night. i too have had maybe 3-4 times where i woke up to my charging phone with the red LED and a screen that would not turn on, battery pull, worked fine.
however, THIS morning my phone would freeze like 30 seconds after boot EVERY time. tried a few things to no avail until I wiped, reinstalled my ROM (aosp 0.4.1) and the data from a previous backup (which was the way i got that ROM to first boot successfully according to tips in that thread).
so this worked, but i couldnt figure out why my other steps wouldnt. had to be something in the data partition of my system at the time, since changing that worked. the only thing i could think of is that app watchdog which someone mentioned to track processor usage by apps. anyone else ever experience this?
I have experienced this once when I was playing Robodefense while the phone was charging. My phone tends to get a little warm when it charges, and hot if I run something intensive while its charging. Wondering if this will be an issue when I use this phone for GPS nav while plugged into my car.
Sent from my SPH-D700 using XDA App
"I'm having this problem too...I didn't get any warranty for this either. Any reasons onto why this is happening...I woke up this morning and picked up my burning phone lol the temp was at 50C so I took out the battery and let it sit for 15 mins...it went down to 30C, then after not touching it for another 15..it was at 17C...very odd...what should I do, this crap is going to die within the next hour I'm worried it will fry the hard drive or something. Need help! " - I wrote this on a diff. forum a couple days ago
I dont have anything on, no wifi, gps, or any 4g (lol only if I could find it)...I even got rid of my facebook/twitter/weather updater widgets. The only thing that updates is email, and that's only if I click on it. The battery has been dying a lot faster and I charge my phone next to the window now because its like 20 degrees outside here in Chicago, so that brings down my phones temp lol....and today, my phone's battery life went from 100 to 5 percent in about three hours of barely using it...wtf?!
Also, another problem...sometimes when I lock my phone and unlock it after taking it out my pocket or something, the screen doesn't seem to respond...I keep swiping my finger over it to put in my password and it wont do anything and it only works when I slide up my phone for the horizontal view. This happens like 4 out of every 10 times I open phone.
Very embarrassing especially if your trying to get someones number down, I stopped showing off the phone now ...lol
I’m wondering if my phone or battery is defective. Up until about a month and a half ago, my hardware version 003 Evo used to sleep for 19-20 hours and have 89-91% charge left. I could easily get a full day (for me, 5:00 AM – 9:00 PM) with light to moderate use and still have plenty of charge left. I once got the warning at 15% charge at the end of a 3-hour + phone call and right at about the 20-hour mark. Then things changed.
I now have Azrael 2.1 DC installed with the Azreal Theme, animations, and wallpapers using stock HTC #11 kernel as distributed. The only things synching are Facebook for HTC Sense (synching contacts once a day), Google (normal), News (manual-synch only), Qik (disabled), and weather (every hour). The main Facebook app has everything unchecked and is not running.
I removed the big Favorites (people), Bookmarks, and Friend Stream widgets from the main screens.
The non-default items running has been reduced now to just a few items, but ones that I’ve used all along:
Brightness Toggle Widget, Dr Web Anti-Virus , Documents To Go, and Swype. (Note: Each of these has been through one or more updates since this all began.)
At the current time, if I take my phone off of the charger at 6:00 AM and maybe view/delete a few of the overnight SPAM email, by 8:00 AM (2-hours later) the charge is between 78-82%. If I make no calls or just spend a minute or two on the phone, view/delete 2-5 emails, maybe send a text or two and don’t charge it of course, by the time 5:00 PM rolls around the charge is down to 15-20%. Sometimes it’s less.
I powered on the screen just now and power was at 91%. I viewed two emails, deleting one, in about 30-seconds. Power now at 89%. The phone has been unplugged for 2-hours.
Since I bought SetCPU I installed that temporarily and verified that the CPU isn’t constantly running at 1GHz, but is scaling using On Demand.
Have made backups, tried different kernels, different ROMs (Sense and ASOP) and kernels…it’s all the same, more or less. To add more confusion, my wife’s Evo (completely stock) is now only getting slightly better battery life than mine. Our Evos were pre-ordered and shipped on release day. I’m wondering if either one or both of our phones is screwing up, using far too much power far to quickly, or if it’s the batteries…maybe a bad lot?
I’ve attached a screenshot of the SpareParts battery screen after a full charge. Can someone let me know if the voltage, etc, looks correct? I have several other screen caps showing various info that I can upload later that may help.
If anyone has heard anything that might help to explain this behavior I would greatly appreciate hearing it. Thank you for your time.
New observation. Put SetCPU back on my Evo, and just sat there and watched it for a while. I've observed that the CPU appears to alternate between 245MHz and 998MHz, spending more time at 998MHz than anything else.
I plugged in my Evo, set the screen to not shut off when plugged in, removed SetCPU, installed System Panel, and observed the CPU activity for about 20-minutes.
While the CPU load was very often in the 10-15% range with frequent brief visits to higher demand, the CPU Clock Speed never dropped below 661MHz during that entire 20-minutes and spent a lot of time all over the higher frequencies.
Tried killing everything that I could, even the things that restart; nothing made much difference. Going to wipe eveything, and try some different ROMs and see if I observe the same behavior.
4G may be running in background trying to connect and throwing log errors every 2 secs. Doesnt matter if you turned it off..it keeps going and is a know defect at medium level of support at google site and known for a few months.
Verify using aLogcat or other free log app.
Errors will look similar to
E/Wimax (***): <DC CONNECT> IO error: msg='/1270.1:7771 - Connection Refused'
Click to expand...
Click to collapse
and wont stop unless you reboot the phone after you use 4G.. every time.
Thank you for the reply! Unfortunately, I live in the Greater New Orleans, LA area, one of Sprint's red-headed step-children, where we will probably get 4G right after Tenney, MN gets it.
Last night, after a nand-backup, I wiped everything twice as usual, and install CM 6.1.1, the latest Google Apps, updated everything and built a normal installation. I left the kernel that it came with.
Using the default 'On Demand' CPU governer, once it settles down it does spend more time down at 245MHz, butif it rises at all, it prettymuch goes straight to 998MHz and back again. I set the governer to 'Conservative' and it appears to be working. The CPU does ramp up on occasion but does not necessarily immediately go all the way to 998MHz...in fact it rarely makes it to that speed.
I'll spend a bit of time like this and observe what sort of battery life I get. One odd thing...while sitting on the charger this morning, my Evo spontaniously rebooted itself...we'll see.
Thank you for your time.
nYdGeo said:
I’m wondering if my phone or battery is defective. Up until about a month and a half ago, my hardware version 003 Evo used to sleep for 19-20 hours and have 89-91% charge left. I could easily get a full day (for me, 5:00 AM – 9:00 PM) with light to moderate use and still have plenty of charge left. I once got the warning at 15% charge at the end of a 3-hour + phone call and right at about the 20-hour mark. Then things changed.
I now have Azrael 2.1 DC installed with the Azreal Theme, animations, and wallpapers using stock HTC #11 kernel as distributed. The only things synching are Facebook for HTC Sense (synching contacts once a day), Google (normal), News (manual-synch only), Qik (disabled), and weather (every hour). The main Facebook app has everything unchecked and is not running.
I removed the big Favorites (people), Bookmarks, and Friend Stream widgets from the main screens.
The non-default items running has been reduced now to just a few items, but ones that I’ve used all along:
Brightness Toggle Widget, Dr Web Anti-Virus , Documents To Go, and Swype. (Note: Each of these has been through one or more updates since this all began.)
At the current time, if I take my phone off of the charger at 6:00 AM and maybe view/delete a few of the overnight SPAM email, by 8:00 AM (2-hours later) the charge is between 78-82%. If I make no calls or just spend a minute or two on the phone, view/delete 2-5 emails, maybe send a text or two and don’t charge it of course, by the time 5:00 PM rolls around the charge is down to 15-20%. Sometimes it’s less.
I powered on the screen just now and power was at 91%. I viewed two emails, deleting one, in about 30-seconds. Power now at 89%. The phone has been unplugged for 2-hours.
Click to expand...
Click to collapse
I have been having the exact same problem with my 0003 phone with Nova screen. I used to get fantastic battery live. I would take it off the charger and it would sit at 100% for at least an hour. Nowadays, I take it off the charger and by the time it takes to get to work (10 mins) it will be around 92%. I have tried 3 different batteries, numerous ROMs and kernels with no changes. The only thing I can think of is that a month or 2 ago my daughter knocked my (naked aside from screen protector) phone off of the counter and it fell bottom left corner first onto the tile floor, cracking the screen. I actually went by the Sprint store yesterday and talked about getting the screen replaced. According to him, they don't have parts for the Evo so I am getting a new phone. Hopefully that takes care of my issue. I know that doesn't really help you but just wanted to let you know, I have the same issue
Thank you for your reply! I've been fortunate and have not dropped mine yet. Trying a new 3.70 ROM on my phone and have updated my wife's stock Evo to the same release. Going to observe whether or not this makes any difference.
try doing a full erase and wiping your battery stats (in recovery). see how that works for you.
geekykid said:
try doing a full erase and wiping your battery stats (in recovery). see how that works for you.
Click to expand...
Click to collapse
Thank you for your input. When I created the ROM, I did a multiple complete wipe, and then started flashing. I recently redid everything again with Azrael X v3.0. After a few days, I recharged with the phone off for a few hours after the light was green, and then reset the battery stats. Unfortunately, no change resulted.
I recently flashed the "SBC-net-4.1.9.1-more-havs-v7" kernel, and this has had an effect. When I remove the phone from the charger, usage starts there instead of zooming down to the 88%-92% range. I've disconnected from the charger, and made a short 2-3 minute phone call, and it was still at 100%!
I've charged the phone for a few hours after the light was green, and then again reset the battery stats (though the post for the SBC kernels says that since the battery gets and stays fully charged, no more need to reset the stats).
I am strongly suspecting that the battery is the problem. In order to test this I've ordered a 3500 mah battery. Once I have it installed, I'll fully charge, and then use/charge for several days. I'll observe the battery life during this part, but will then flash to a rooted, but otherwise completely stock ROM, and live with that long enough to observe accurate battery usage.
I'll use the info that I gather during that time to compare with others with the same type of battery. This isn't an exact science of course, but If they get a full day with very heavy usage and I get a full day with little to no usage, I know that my phone is borked, etc.
Thank you for your time, and Happy New Year to everyone!
Well, have had the 3500mAh battery for a while and its not the battery. I am totally baffled. The phone hasn't been dropped, there's not a blemish on it anywhere. Absolutely everything works, there's no 100% wake time...the up time and awake times are different and at least appear to be reasonable.
Both regular and extended batteries have been through the HTC-recommended 'conditioning' procedure, or whatever they call it. I've tried several different Sense ROMs as well as CM6-6.1 (doing double and triple wipes of everything), with various kernels...stock, custom, SBC, non-SBC, HAVs, noHAVs, more aggressive/less aggressive/no undervolting, TM, King's (always wiping cache and dalvik). They don't all run the same, but regardless of what ROM or kernel I have installed, after charging all night I can unplug the phone and leave the house at 6:00 AM, not use the phone at all...100% screen-off time, and by 3-ish in the afternoon the stock battery is at 35-40%. Awake time could be anything from 45-mins to a little over an hour.
Previous to this, and whatever switch got thrown that's causing this, after that same 9-hours of non-use the stock battery would be at least 90%...maybe 85% on a weird day.
With the same 3500mAh battery that others get through 12-hours of extremely heavy use, or with casual use go a few days on, I can use it to maybe answer a couple of texts, quickly view and delete a few emails, manually killing the screen after any activity, and by 5:00 PM, 11-hours later, I'm looking at 40% charge.
The only suggestion that anyone has had (in another forum) was to download the original signed RUU, run it taking the phone completely back to original state, update it OTA, and then re-root (hboot 2.10 with Unrevoked 3.31 or whatever it is, latest RA, etc). The theory is that 'sometimes using the RUU and going completely back to stock is the only thing that fixes some issues'. Has anyone else ever heard of anything like that?
If anyone can shed any light on this in any way, shape or form, you have my sincere thanks in advance.
Thank you for your time.
nYdGeo said:
Well, have had the 3500mAh battery for a while and its not the battery. I am totally baffled. The phone hasn't been dropped, there's not a blemish on it anywhere. Absolutely everything works, there's no 100% wake time...the up time and awake times are different and at least appear to be reasonable.
Both regular and extended batteries have been through the HTC-recommended 'conditioning' procedure, or whatever they call it. I've tried several different Sense ROMs as well as CM6-6.1 (doing double and triple wipes of everything), with various kernels...stock, custom, SBC, non-SBC, HAVs, noHAVs, more aggressive/less aggressive/no undervolting, TM, King's (always wiping cache and dalvik). They don't all run the same, but regardless of what ROM or kernel I have installed, after charging all night I can unplug the phone and leave the house at 6:00 AM, not use the phone at all...100% screen-off time, and by 3-ish in the afternoon the stock battery is at 35-40%. Awake time could be anything from 45-mins to a little over an hour.
Previous to this, and whatever switch got thrown that's causing this, after that same 9-hours of non-use the stock battery would be at least 90%...maybe 85% on a weird day.
With the same 3500mAh battery that others get through 12-hours of extremely heavy use, or with casual use go a few days on, I can use it to maybe answer a couple of texts, quickly view and delete a few emails, manually killing the screen after any activity, and by 5:00 PM, 11-hours later, I'm looking at 40% charge.
The only suggestion that anyone has had (in another forum) was to download the original signed RUU, run it taking the phone completely back to original state, update it OTA, and then re-root (hboot 2.10 with Unrevoked 3.31 or whatever it is, latest RA, etc). The theory is that 'sometimes using the RUU and going completely back to stock is the only thing that fixes some issues'. Has anyone else ever heard of anything like that?
If anyone can shed any light on this in any way, shape or form, you have my sincere thanks in advance.
Thank you for your time.
Click to expand...
Click to collapse
A lot of times its a market app that's the culprit. Make sure you don't have an app installed that keeps your phone awake even when the screen is off. The market tells you what every program has access to including wake issues. After a fresh Rom install / kernel flash........check all apps to make sure none of em do this. Task killers are not the answer......not installing apps with too many permissions helps a ton.
Sent from my PC36100 using XDA App
dagnasty said:
I have been having the exact same problem with my 0003 phone with Nova screen. I used to get fantastic battery live. I would take it off the charger and it would sit at 100% for at least an hour. Nowadays, I take it off the charger and by the time it takes to get to work (10 mins) it will be around 92%. I have tried 3 different batteries, numerous ROMs and kernels with no changes. The only thing I can think of is that a month or 2 ago my daughter knocked my (naked aside from screen protector) phone off of the counter and it fell bottom left corner first onto the tile floor, cracking the screen. I actually went by the Sprint store yesterday and talked about getting the screen replaced. According to him, they don't have parts for the Evo so I am getting a new phone. Hopefully that takes care of my issue. I know that doesn't really help you but just wanted to let you know, I have the same issue
Click to expand...
Click to collapse
I got the same story from the sprint repair center by me as well. When they told me new phone I asked them "do you mean a referb" they said "yes". I'd rather have my screen replaced then get a referb
Thank you for your reply. Yep, I stopped using task killers of any type when froyo was released due to OS functionality making them useless, and if fact a negative.
So far I haven't experienced any extreme wake-time issues, though I knwo they can be a big problem.
I've tested this by completely wiping everything several times, flashing a ROM and not making any changes so its still using the factory HTC #15 kernel which is pretty well known now for good battery life. I've run it like that for a week with multiple restarts, full charges with battery stat wipes, etc.
So far, no luck, no change. Still hoping to figure it out.
Problem Identified but not yet resolved.
It appears that there is some issue with one or more radios in my phone. I don't know enough about the innerds to know if there is more than one, but whatever receives data downstream is screwed up.
Over time I've noticed that my downstream data has gotten slower and slower. Then I started missing calls periodically, and texts sent to me at 10:30 AM were showing up as arriving at 6:30 PM...weird stuff.
After un-rooting, performing a complete factory reset, and a complete data restore (from the ##3282# menu), the phone and texts seem to be more consistant, but running the SpeedTest app to a server here in NOLA produces the following results:
Ping: 20ms - 30ms
Downstream: 0 - 128Kbs (Seriously, I get "0" often, and 128Kbs is the absolute max achieved on occasion)
Upstream: 1.2Mb - 1.46Mb
After re-rooting the phone, I've tested this in the Azrael 4.0 and EViO 1.8 Sense ROMs, and in CM6.12, and the results are identical. Its very strange that it only seems to affect the downstream rate.
I guess its time to RUU, bring it to a Sprint store, pay their $35 and see if they can fix it.
I'm trying to decide whether to root my NST or just leave it as is. I would certainly like to have the extra functionality, but not at a large cost to the battery life. After all, I did buy it as an e-reader first and foremost, so battery life is a very important factor.
I've searched the thread a bit and have seen some people complain a great deal about battery performance after rooting, however perhaps this is down to programs they decide to run, rather than the rooting process itself with the latest touchnooter.
So, could one of you veterans please comment on your experience with battery life after rooting?
Cheers,
R
From my experience, most battery is wasted when refreshing the screen. When you root, most of the time your goal is to use some random android app. This means you are going to be refreshing the screen often, which uses battery.
Someone else tell me if I am wrong, thanks
I don't think that root itself has any impact on battery life, but as you can do more with rooted nook, you consume more. Last week I've used mine almost 100% as a reader and battery is at 50%... and I read much more than 1 hour a day (that's the presumption for "2 months battery life" from B&N )
I've accidentally voted 'significant decrease' whereas in reality I have seen no change. An issue I've run into is that I have 'Keep Screen On' checked in EBookDroid so the page doesn't go away, but then when I'm done reading I forget to hit the power button to sleep it. This has drained the battery on me more than once.
Incidentally, it would be superfly if someone hacked together a script that copied the framebuffer to a file in the screensaver directory so when it went into sleep mode it would keep displaying the page while not wasting batteries.
I might hash that up when I have time.
klausef said:
I've accidentally voted 'significant decrease' whereas in reality I have seen no change. An issue I've run into is that I have 'Keep Screen On' checked in EBookDroid so the page doesn't go away, but then when I'm done reading I forget to hit the power button to sleep it. This has drained the battery on me more than once.
Incidentally, it would be superfly if someone hacked together a script that copied the framebuffer to a file in the screensaver directory so when it went into sleep mode it would keep displaying the page while not wasting batteries.
I might hash that up when I have time.
Click to expand...
Click to collapse
There is system/bin/screenshot
Code:
screenshot /media/001.png
Don’t know how to hook it up to sleep event, hopefully should be very difficult.
Dirty hack – delete all screen saver images, than use screenshot, so it’ll be the only one to pick...
ApokrifX said:
There is system/bin/screenshot
Click to expand...
Click to collapse
Then yours must work better than mine.
They completely screwed up the bitmapping from 565.
Take a shot, it's all blue.
Details here: http://nookdevs.com/Nook_Simple_Touch_screen_capture
Renate NST said:
Then yours must work better than mine.
They completely screwed up the bitmapping from 565.
Take a shot, it's all blue.
Details here: http://nookdevs.com/Nook_Simple_Touch_screen_capture
Click to expand...
Click to collapse
Same thing was happening to mine. More of a cyan/teal, though.
we don't even need it to hook to the sleep event; i was considering just having a service that waits for two minutes of inactivity, clears out the screensaver directory (as mentioned) and then writes a screencap to it.
Renate NST said:
Then yours must work better than mine.
They completely screwed up the bitmapping from 565.
Take a shot, it's all blue.
Details here: http://nookdevs.com/Nook_Simple_Touch_screen_capture
Click to expand...
Click to collapse
I've never tried it, actually...
I've seen something happen randomly, I addressed it in another post:
http://forum.xda-developers.com/showpost.php?p=24232518&postcount=9
On occasion the touch screen sensors do not turn off when the Nook goes to sleep.
Whether this indicates that nothing has gone to sleep or just that the sensor has not gone to sleep is unclear.
Still, you can lose about 4% of a charge per hour overnight.
If you run into this, there is something that you can try:
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db
sqlite> update system set value=0 where name='stay_on_while_plugged_in';
sqlite> .q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
3 is the normal value, telling the Nook to stay on always with USB or charger power.
Unfortunately, once a charger/USB is plugged in it gets its state all confused.
Even with this set to 0 the screen sensors stay active while plugged in.
Or just turn it off
Thanks to all those who replied.
So, basically what you're saying is that if I were to root my NST, but continue to just use the nook software, I will basically get the exact same battery life? And that battery life is only affected by other programs that I may install?
So there is nothing installed standard on the nooter rooting software that causes additional battery drain?
Randy Lahey said:
[...] So, basically what you're saying is that if I were to root my NST, but continue to just use the nook software, I will basically get the exact same battery life?
Click to expand...
Click to collapse
Exact is impossible to say, unless you're doing some sort of structured testing. What I can tell you based on my experience is that, if you're careful with what runs in the background, you can see battery life on a rooted NST on par with what you'd see unrooted.
And that battery life is only affected by other programs that I may install?
Click to expand...
Click to collapse
Only? No, not exactly. Whether you leave wifi on or off will make a big difference in battery life, whether rooted or not. Thus the statement that "battery life is only affected by other programs" is not true. Other programs may affect battery life, but may not be the sole consumer of battery.
In my ad-hoc testing, I saw battery drop roughly 1% per hour with wifi on. With wifi off, that drops to something less than 1% per 6 hours.
So there is nothing installed standard on the nooter rooting software that causes additional battery drain?
Click to expand...
Click to collapse
You're asking questions like a lawyer! I'm not comfortable saying that "there is nothing installed standard on the nooter rooting software", because the Android Market does check in the background for updates, so will consume some battery. Gmail is also installed, and can be set to do background updates.
You also haven't specified a rooting method. Some variants have loaded all sorts of additional software. I can only say that the software loaded by TouchNooter seems to have minimal impact.
Controlling when wifi is enabled has made the biggest impact on battery life in my experience. I'm using Tasker to control when wifi turns on and off, limiting it to a small handful of foreground apps. I disable any background synchronization I can.
The other question nobody can answer for you is how you'll use the device. Screen activity does impact battery life. If you're just reading, there's less of an impact than if you're playing Angry Birds.
SetCPU app
I heard that configuring the CPU may save battery life. I have installed the app SetCPU on my NOOK. Does anybody else have it? How could I configure it to save battery life?
http://urlin.it/2e6b2
genoxygen said:
I heard that configuring the CPU may save battery life. I have installed the app SetCPU on my NOOK. Does anybody else have it? How could I configure it to save battery life?
http://urlin.it/2e6b2
Click to expand...
Click to collapse
There's a bit under the ManualNooter thread about underclocking to improve battery life. I haven't read about it myself, and have only read comments that the improvement is marginal.
bobstro said:
You're asking questions like a lawyer! I'm not comfortable saying that "there is nothing installed standard on the nooter rooting software", because the Android Market does check in the background for updates, so will consume some battery. Gmail is also installed, and can be set to do background updates.
Click to expand...
Click to collapse
Thanks Bobstro, appreciate your response. And anything you say can and will be used against you in a court of law. Nah, I'm not a lawyer....but an accountant...just as bad.
It sounds like the effect will be minimal after rooting the nook unless I install something more intensive.
That being said, can always just restore with the old backed up image if I'm not happy, so the downside seams minimal.
Randy Lahey said:
[...] That being said, can always just restore with the old backed up image if I'm not happy, so the downside seams minimal.
Click to expand...
Click to collapse
With the usual caveat that YMMV, and a warning to back up the device before you start (the NST can't always be completely restored as easily as other B&N devices), I think you're all set!
Just sign this release form...
Last report: mine... well I don't remember when was the last time I've charge it - but it was before Orthodox Easter festivities (i.e. 11 April), and is still at more than 60%, reading at least 2 hours a day!
i had a 4% drain overnight on standby. i don't have that many applications installed (nothing I can think of that would lead to high battery drain at least). i have to look into it but i seem to have "excessive" battery drain after rooting.
leoparis said:
i had a 4% drain overnight on standby. i don't have that many applications installed (nothing I can think of that would lead to high battery drain at least). i have to look into it but i seem to have "excessive" battery drain after rooting.
Click to expand...
Click to collapse
Is wifi on or off? Anything that wakes the device up will cause an increase.
Hello everybody. I need a help with next situation.
I bought my nook like month ago and rooted it with TouchNooter after a couple of days. Everything worked fine for me - coolreader + goldendict, wi-fi, everything. One thing that did not satisfy me was energy drain, so i tried to install another ROM with "minimalistic" package on board. Before i switched i did factory reset and factory restore - my nook has 1.1.0 stock version on board. Unfortunately i discovered that "minimalistic" ROM does not contain android market - so i would not be able to install GoldenDict properly (because programme askes for license check). So i decided to revert back to TouchNooter (with factory reset and restore ofc).
Since then my nook keeps freezing all the time - whatever i do - its just freezes.
If Im trying to read a book with both default reader/coolreader - its freezes after couple of pages. If Im trying to press settings - its freezes again. And it wont boot up without power supply - i need to plug my nook via usb to my PC or to jack.
With energy supply it works fine without any random freezes, reboots etc.
I made a conclusion that its not about ROM (i tried like 30 times factory reset/restore. I tried both versions of n2T Recovery. I tried to use Touch-Formatter.) My device keeps freezing even totally unrooted -i have to plug my device into PC in order to complete registraion process - otherwise it will freeze before my attempt to connect. My nook cant work on its own - it should be plugged in into power source.
So i tried to charge my nook more than it requires - i left it charging for a day with jack. after i unplugged it battery stats shown me 100%. I started to read. Notably that i spend half day reading and using goldendict without any problems, but when my battery drained to 93% my nook started to freezing again.
I just dont understand what is the problem. Why does my nook work fine with cable and cant live without it? One thing i did not do yet is to disassemble my nook and trying to unplug/plug battery - i dont know how it can help but i dont have any options left...
I hope you guys can help me coz i've tried to find same problem and haven't succeeded. Thank you!
Most battery systems require calibration. To do this you need to charge it to full, drain it to low power.. around 10%. 3-4 times is the usual number needed. It sounds like you are having some sort of battery problem and calibration may make the meter read properly. Otherwise it might be time to try for a warranty replacement.
Every time you change roms you need to allow for the calibration period again.
I doubt that the battery calibration is that far out, but you can try:
Code:
am start -n com.android.settings/.BatteryInfo
That will give you all the numbers on your battery.
Voltage goes from a high of 4.200 to about 3.800 as dead.
Renate NST said:
I doubt that the battery calibration is that far out, but you can try:
Code:
am start -n com.android.settings/.BatteryInfo
That will give you all the numbers on your battery.
Voltage goes from a high of 4.200 to about 3.800 as dead.
Click to expand...
Click to collapse
Thank you Renate, but how do i perfrom this and what should i do with all this numbers?
To Nova - i cant charge/recharge my battery several times in order to re-calibrate it - because as i said it simply freezes once been plugged off
That was a command you type in a shell on the Nook, normally over ADB.
You do have ADB working?
It sounds like your battery has simply had an early failure.
I'd try restoring it to stock and returning it under warranty.
This teleir
Renate NST said:
That was a command you type in a shell on the Nook, normally over ADB.
You do have ADB working?
It sounds like your battery has simply had an early failure.
I'd try restoring it to stock and returning it under warranty.
Click to expand...
Click to collapse
I think i'll just return it...but im afraid that other device will have same issue...hope its not that regular
mine too
I'm also experiencing freezes with my NST (rooted 1.1.2). It has 1 1/2 year with light use (approx 30 mins per day).
Whenever the battery reaches 95-80% my nook would start to freeze.
I've tried using "Battery Calibration" app to restart the battery counter but it didn't help.
I know it's a battery related problem but I wouldn't say it's a hardware problem because it doesn't show the "too low to power on" message. Show I unroot my Nook?
Any suggestions?
Did you try looking at your battery info - as Renate shows in post #3
in adb shell :
am start -n com.android.settings/.BatteryInfo
Voltage goes from a high of 4.200 to about 3.800 as dead.
I'm checking with Battery Calibration app. It now shows 96% and 4033mV
I'll recheck it on the next freeze.
ladykayaker said:
Did you try looking at your battery info - as Renate shows in post #3
in adb shell :
am start -n com.android.settings/.BatteryInfo
Voltage goes from a high of 4.200 to about 3.800 as dead.
Click to expand...
Click to collapse
Well, clearly that's wrong as 4.0 volts is not 96%
Can you charge the thing to around 4.200 volts?
Run the battery calibrator reset only when it's at 100% (or so they say).
Does the battery health indicator say good?
Yes, the battery health reads good. I reset the battery calibrator when the actual led light turned to green (my nook was showing 100% a lot before that).
Today the battery was showing 93% and 4014mV.
I maybe onto something. I experienced something weird. I kept reading using the official nook app and checking from time to time the battery app. It was always somewhere 92-93% and 4014-4012mV. Seconds after I highlighted a word the nook froze. I rebooted and immediately I read the battery app. I read 92% 3895mV. I waited a moment and then it went back up to 4010mV.
It seems there something going on on CPU intensive tasks. I wonder if the battery is acting weird or there is some task that misreads the battery status ands freezes the device.
What do you think?
Renate NST said:
Well, clearly that's wrong as 4.0 volts is not 96%
Can you charge the thing to around 4.200 volts?
Run the battery calibrator reset only when it's at 100% (or so they say).
Does the battery health indicator say good?
Click to expand...
Click to collapse
I've found this suggestion in Mobileread forum
http://www.mobileread.com/forums/showpost.php?p=2186779&postcount=103
I opened my nook, disconnected the battery and put all things back. So far it seems the freezes are gone. I'll report any problems!
I've doing this for a couple of months now (once every 2), no freezes anymore.
Perhaps the NST power handling firmware has a bug? Been seeing this issue fixed by that on several forums.
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!