this is something i would have liked to know before hand. is there any way to significantly increase it, say 5h ? i had to add the command line arguments to startup.txt thus disabling the power saving feature (waiting for sd card) otherwise the device would randomly freeze. also the sound volume regularly goes up and down slightly, and the speakerphone doesnt work. it feels like the power is leaking --; i m using FRX07.1 and this is my first successful installation. my previous attempts did not work because i had 6Gb of music being indexed at startup, and it felt like the xdandroid logo would never stop looping. why is it that we have to stare at a logo for minutes when we could see that indexing or loading activity whatever it is, in verbose ?
mr.bryce said:
this is something i would have liked to know before hand. is there any way to significantly increase it, say 5h ? i had to add the command line arguments to startup.txt thus disabling the power saving feature (waiting for sd card) otherwise the device would randomly freeze. also the sound volume regularly goes up and down slightly, and the speakerphone doesnt work. it feels like the power is leaking --; i m using FRX07.1 and this is my first successful installation. my previous attempts did not work because i had 6Gb of music being indexed at startup, and it felt like the xdandroid logo would never stop looping. why is it that we have to stare at a logo for minutes when we could see that indexing or loading activity whatever it is, in verbose ?
Click to expand...
Click to collapse
I don't think any indexing happens during the boot animation - but I could be wrong. However, the type of stuff you'd like to know wouldn't be in any kernel messages, so you wouldn't "see" it anyways.
3 hours on a full charge sounds like either a bad battery, or a phone that wasn't sleeping (at all). If you killed the battery process or have processes running in the background, have GPS on, etc - it will kill your battery, and quickly. If the device isn't sleeping properly, it'll never be able to run for more than a few hours.
ok i ll try making sure the gps is off --; i also installed the overclock widget and downclocked during sleep mode
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!
Hi everybody
My myTouch 4G bots up very fast after switching it off and switching back on.
When I remove the battery,and turn it on,the screen shows "My Touch" for about 5 minutes when booting.
How can I solve this please?
You can't solve it, because it's not a fault.
Start reading instead of asking, please. You'll have tons of additional basic questions that Google can answer.
This is something called "Fast boot" by HTC (don't mix with "fastboot", which is a completely different thing). When you "turn off" the device, it's hibernated (partially or suspended, AFAIK) instead of fully turned off, and getting it back up from hibernation is fast. When the battery is pulled, it shuts down completely, thus requiring full boot. And full boot doesn't take 5 min either.
All,
I've got a stock Nexus 6P, Android 6.0.1, build MHC19Q.
Sometimes the phone will go to sleep and sometimes it won't. In the settings, Display Sleep setting I have 30 seconds as the value, but I've seen my phone stay on for way longer, sometimes until I hit the power button.
I've tried several changes to the time but it doesn't seem to help the times it stays on, it just changes the time for the sleep when it does work.
To explain exactly, when I stop using my phone and I'm on the home screen, if I leave the phone alone for several minutes, it will not sleep, no matter what value I put in the setting. Other times it seems to sleep without a problem.
I've not been able to determine if some app is holding it awake, and I don't see any pattern the would point to any other condition that keeps the phone awake.
I looking for additional ideas to troubleshoot the problem, it just stays on and runs down the battery.
Ideas?
MB
Download and install GSAM. It will tell you specifically which app is keeping the screen on.
If it days Android, System, or Media Playback is the highest, it may be a tweak / custom rom / kernel issue.
Not sure what exactly this does but it's some sort of diagnostics or logging program tmobile uses. I had my phone on airplane mode as I was in a place without service. WiFi on, WiFi calling enabled, Bluetooth enabled, WiFi set to always on when phone is asleep. I did not touch this phone for 4 hours. It was within my sight the whole time and I didn't have a chance to pick it up because I was so busy. I picked the phone up for the first time since setting it down with 100% battery life and realized it was very warm and that the battery was down to 32%. Nothing was showing in the battery optimizer, nothing out of the ordinary, no rogue apps or anything. Android system was at 50% usage and the next one down was com.tmobile.pr.adapt. Reboot did nothing. Lost another 15 percent in the next hour.
Long story short I did a lot of troubleshooting and realized that com.tmobile.pr.adapt was actually the culprit behind Android system showing such high battery usage. I used package disabler pro and disabled this process. Problem is now gone for good.
I highly suggest you consider this if you are having unexplained battery drain or a hot phone with high android system usage. Picture attached.
seh6183 said:
Not sure what exactly this does but it's some sort of diagnostics or logging program tmobile uses. I had my phone on airplane mode as I was in a place without service. WiFi on, WiFi calling enabled, Bluetooth enabled, WiFi set to always on when phone is asleep. I did not touch this phone for 4 hours. It was within my sight the whole time and I didn't have a chance to pick it up because I was so busy. I picked the phone up for the first time since setting it down with 100% battery life and realized it was very warm and that the battery was down to 32%. Nothing was showing in the battery optimizer, nothing out of the ordinary, no rogue apps or anything. Android system was at 50% usage and the next one down was com.tmobile.pr.adapt. Reboot did nothing. Lost another 15 percent in the next hour.
Long story short I did a lot of troubleshooting and realized that com.tmobile.pr.adapt was actually the culprit behind Android system showing such high battery usage. I used package disabler pro and disabled this process. Problem is now gone for good.
I highly suggest you consider this if you are having unexplained battery drain or a hot phone with high android system usage. Picture attached.
Click to expand...
Click to collapse
Disabling NOW, big ups too you kind sir.
I still got a drain and that wasn't in my processes on titanium. Still has android 25% usage.
I'm rooted and this app asked for superuser privileges. It's some kind of security monitoring app that reporys back. I didn't grant privs and froze it with Titanium BU. It's nice to know I'm saving battery, too.
Try doing the same with Samsung+. Another battery hog.
I'm not rooted and I've been disabling bloat all morning trying to get the battery as close to usage stats were before the recall debacle. I'll sacrifice the smoothness to not have to charge this battery draining hog halfway through the day.
com.tmobile.pr.adapt is the process that allows T-Mobile diagnostics (see what apps are on your phone, how you use them, if you're rooted)
I just deny them permission to run diagnostics when the option is presented (when you first set up your phone) and it never runs. You can also go into the T-Mobile app itself, and disable diagnostics. No need to freeze the process itself.
ingenious247 said:
com.tmobile.pr.adapt is the process that allows T-Mobile diagnostics (see what apps are on your phone, how you use them, if you're rooted)
I just deny them permission to run diagnostics when the option is presented (when you first set up your phone) and it never runs. You can also go into the T-Mobile app itself, and disable diagnostics. No need to freeze the process itself.
Click to expand...
Click to collapse
Completely untrue.
I always 100% uncheck the box during setup to disallow tmobile from doing ANYTHING. I have factory reset my phone and reflashed the firmware around 10 times and always be sure to uncheck that. When you do there is a toast message that pops up at the bottom that says "please allow 48 hours to process your request". Process still ran yesterday and destroyed over half my battery.
Ymmv but I've never had an issue.
Sent from my SM-N930T using Tapatalk
ingenious247 said:
Ymmv but I've never had an issue.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
I think it only arises when in airplane mode with WiFi calling enabled. I had Bluetooth on as well and WiFi calling was set to network preferred. It may take those exact circumstances to reproduce it, I don't know. I have had the phone since release and this is the first time I've seen it happen, but if it can happen to me it can happen to others. Also no tmobile app or process should ever be requesting root permissions so the process should be killed regardless.
seh6183 said:
I think it only arises when in airplane mode with WiFi calling enabled. I had Bluetooth on as well and WiFi calling was set to network preferred. It may take those exact circumstances to reproduce it, I don't know. I have had the phone since release and this is the first time I've seen it happen, but if it can happen to me it can happen to others. Also no tmobile app or process should ever be requesting root permissions so the process should be killed regardless.
Click to expand...
Click to collapse
Could be. I disable WiFi calling from the moment I see up my phones, so that scenario would never occur for me. I'll tell you what though, Samsung+, S Health and S Voice always get disabled immediately because they are battery draining monsters IMO.
Sent from my SM-N930T using Tapatalk
It is in fact part of T-Mobiles app that will report back device info. That is usually the first thing that gets frozen on my devices. Love being snooped on by my carrier.