Current drain on the Nook - Nook Touch General

The Nook is pretty good on battery life.
Sometimes, randomly it just drains the battery though.
I've been meaning to look into this for a while.
The start of this is posted in this general hardware thread.
There's a plot below.
It seems to indicate that there is some real problem with the Jorjin WiFi module.
The left side of the plot shows fresh booted with WiFi on.
The right side shows after it has been pinged.
The goal is to make the Nook be drawing only 10 mA all the time.
As far as the "40 mA square waves" go, what are they?
When running at 10 mA they represent a significant current draw.
With the WiFi off they run every 30 seconds for 5 seconds.

Wow, great work Renate! I hope this is a big step towards tracking down the Nook's random battery drains.
I don't have any good guesses about what would be running every 30 seconds, but I think seeing a timestamped power graph with the corresponding logcat output might be interesting.
I can't tell from the pictures, are you running this on a NST or NTSG and which firmware version?
Do you see the 30/5 waves when wifi is on, or only when it's off?
What does the power draw look like when the nook is in sleep mode?
Is there any difference between "sleep" after pushing the power button versus sleep after an idle timeout? I've never noticed a difference and it would be nice to have some evidence to dispel one of this community's long-standing superstitions.

The logcat is boring, just occasional battery updates and not related to the square waves.
Oh, ClockworkMod Recovery runs at a solid 150 mA and no square waves.
Yes, I've tried power button off vs. timeout off many times and both of them go to a baseline of a mA or so.
It could be a random thing though.
To give it a real test I'd have to power it up/down 1000 times.
The power button push is no problem, but if I want to keep with an unmodified swipe I'll have to throw in a robotic finger.
Edit: Actually, if one of the side buttons is "Menu", then you can dismiss the slide dialog with that.
Still, since top does not report any real CPU activity I have to presume that this is a DC load problem.
The Jorjin is already suspicious.
I've checked the eInk power section during the square waves and that is not switching on then.
Note: The 60 second pulses on the chart are the time in the status bar updating.

The 5 second pulses do appear to be a display related activity with a timeout.
I made an app that would draw a few pixels every 10 seconds.
If it hit when there wasn't a square pulse it would start a square that would end exactly 5 seconds later.
If it hit in the middle of a square pulse the square would end at exactly 5 seconds from the start of the square, not the hit.
This is all a bit confusing because I can't detect the eInk power sections firing for all the squares (or even the full 5 seconds of any square).
The power management is complex, with 2 DC converters, 2 charge pumps, 2 LDO regulators.
The big supplies are the +/- 15V @ 120mA!
30V x 120mA / 3.7V = an Ampere or so!

Ok, a few interim observations.
The Nook happily sitting on a reading page doing nothing should draw ~8 mA
When the Nook is cold-booted it draws ~40 mA at rest.
Put it to sleep with the power button, then wake it, it will go to ~8 mA.
The WiFi when it's on, happy and doing nothing draws negligible current.
The WiFi when it's on, just woken up and not even pinged draws an additional 80 mA.
Ping it then and the current goes down to negligible.
Turn it off and the current goes down to negligible.
The USB host mode can be a really power sucker.
With just a OTG cable and no device in host mode it draws an additional 150 mA.
Put it back in peripheral mode and the total Nook drain goes to either 40 mA or 20 mA.
Put the Nook to sleep with the power button and it continues to draw 40 mA or 20 mA.
Code:
Powerdomain (core_pwrdm) didn't enter target state 0
I'm not sure how much this affects anyone else.
I am using S1 as the system console.
When you first boot the Nook, the console is in a normal mode.
It relays dmesg stuff and allows you to type commands.
If you go to sleep and then wake it up it's in a strange mode.
If you hit a console key, it only wakes for 5 seconds.
The next key that you hit will be actually registered.
This is the source of the 5 second square waves.
Type constantly and it's an additional 40 mA.
The thing is, I was seeing this before with nothing connected.
The level shifter has no pullups and was randomly triggering on noise.
A screen update is a major electrical incident that sets it off.
I'll be adding a pullup to my RX in on the console.
Safest way to save the battery (as far as I know right now):
If you reboot, don't use it immediately for long periods, sleep with the power button, then wake.
The safest for WiFi is to wake the Nook with WiFi on, then ping or connect to it.
Then turn it off. (Yes, I know that this is a bit impractical.)
The real wildcard is USB. After using USB host mode, do a power down reset.
Anybody have any insight into why this 5 second wakeup on the console?
From the current drain it must be doing a loop in software or something.

You can show your dmesg and logcat?
You do measurements with SD card?
I am confused by error after sleep
<3> [6439.043121] PM: Failed to prepare device omap3epfb.0 for power transition: error -16
I have a lot these errors. I think that the screen while drawing the screensaver is not the first time screen sleep.
I have deleted the system utility debuggerd. She is all the more load on the CPU.

Renate NST said:
Ok, a few interim observations.
The Nook happily sitting on a reading page doing nothing should draw ~8 mA
When the Nook is cold-booted it draws ~40 mA at rest.
Put it to sleep with the power button, then wake it, it will go to ~8 mA.
Click to expand...
Click to collapse
How does using the rear power button compare with long-holding the front 'n' button, or using Button Savior's virtual power button?

I always sleep with the power button.
I just checked, I removed long push of the "n" button entirely from my policy.jar
I didn't notice anything.
I may try that "sleep 1000 times" experiment.

jeff_kz said:
Is there any difference between "sleep" after pushing the power button versus sleep after an idle timeout? I've never noticed a difference and it would be nice to have some evidence to dispel one of this community's long-standing superstitions.
Click to expand...
Click to collapse
Hello!
I've got a Nook Simple Touch running firmware v1.2.1 and rooted with NookManager, Nook Applications switched off by NookManager and max CPU frequency set to 300mHz. On this and other sites It was stated that Nook SImple Touch enters a bugged sleep mode after pressing the "power' button, consuming much more energy than after an idle timeout. Out of curiosity I took my NST apart and measured current directly through battery lines while setting NST into various states. I've found this thread and it turns out that very much work has already been done, but I'd like to share my measurements anyway - the more information there is the better.
ReLaunch, main screen - 11.5mA
ReLaunch, task manager - 53.5mA
Cool Reader - 12.5mA
Sleep mode:
power button - 0.8mA
screen time-out -0.8mA
default reader app time-out - 0.8mA
Start up - 250mA during ~35 seconds
So, all sleep modes consume the same amount of current.
Also, NST consumes very large amount of current during start up. Combined with rather long start up sequence, it makes one start-up equivalent to ~3 hours of sleep mode! If you're not going to turn it off for more than 3 hours, it's better to use sleep mode instead of turning it off completely.
I hope someone will find it useful!

Sparker_95 said:
Hello!
I've got a Nook Simple Touch running firmware v1.2.1 and rooted with NookManager, Nook Applications switched off by NookManager and max CPU frequency set to 300mHz. On this and other sites It was stated that Nook SImple Touch enters a bugged sleep mode after pressing the "power' button, consuming much more energy than after an idle timeout. Out of curiosity I took my NST apart and measured current directly through battery lines while setting NST into various states. I've found this thread and it turns out that very much work has already been done, but I'd like to share my measurements anyway - the more information there is the better.
ReLaunch, main screen - 11.5mA
ReLaunch, task manager - 53.5mA
Cool Reader - 12.5mA
Sleep mode:
power button - 0.8mA
screen time-out -0.8mA
default reader app time-out - 0.8mA
Start up - 250mA during ~35 seconds
So, all sleep modes consume the same amount of current.
Also, NST consumes very large amount of current during start up. Combined with rather long start up sequence, it makes one start-up equivalent to ~3 hours of sleep mode! If you're not going to turn it off for more than 3 hours, it's better to use sleep mode instead of turning it off completely.
I hope someone will find it useful!
Click to expand...
Click to collapse
Did you test sleep by long pressing the "nook" button? That is usually my method of choice since the power button is in an inconvenient place

smeezekitty said:
Did you test sleep by long pressing the "nook" button? That is usually my method of choice since the power button is in an inconvenient place
Click to expand...
Click to collapse
The problem with long-pressing the "n" button to ensleepify the Nook (at least for me) is that you have to hold it... and hold it... and hold it before it sleeps. Mind you, this observation is on an NSTG with "long press the n button glowlight toggle" enabled, so I don't know the exact number of ms. it is for the regular NST.
But I really prefer using the back button, because you just tap it once, and boom, it's asleep.
By the way, I tested the n button long-press method, and it gives the exact same results as the power button tap method.

thenookieforlife3 said:
The problem with long-pressing the "n" button to ensleepify the Nook (at least for me) is that you have to hold it... and hold it... and hold it before it sleeps. Mind you, this observation is on an NSTG with "long press the n button glowlight toggle" enabled, so I don't know the exact number of ms. it is for the regular NST.
But I really prefer using the back button, because you just tap it once, and boom, it's asleep.
By the way, I tested the n button long-press method, and it gives the exact same results as the power button tap method.
Post thank for the testing?
Click to expand...
Click to collapse
Ok a good enough. The NST without glowlight you don't have to hold it so long

Related

Power Button and Data Retention BiG Problems

Hi All,
I have such a big Power issue with the Magician, or at least Orange's M500 version of it that i'm thinking of taking back the device :'(
It doesn't appear to be a device fault, but a design fault.
In the manual it says that if you press the power button for a short time (less than a second) it turns the PDA on and off. This seems to be correct.
In the manual it says that if you press and hold the power button for two seconds it turns the phone off, but this doesn't work. Instead it turns on and off the back light. If the PDA is on, it turns on and off the back light. If the PDA is off it turns it on with the backlight on.
Last night I turned my PDA into standby mode (As i can't turn the phone off) before going to bed. Around 3am in the morning my PDA woke up saying that the battery power was low. I turned the PDA back into standby mode but it complained later on that night. i.e. had a bad nights sleep last night.
I thought it best to remove the main battery so that it wouldn't continue to wake me up, making sure that the phone and PDA were turned off (no power) and let the data backup battery retain the data until i woke up (5 hours time). However, when i woke up the internal data backup batery was flat. It was fully charged before the i took the main battery out. It is supposed to last 72 hours right!!!!? What a nightmare!
I was wondering if anyone could help me answer these power related questions, as i love the device, but its useless if it won't retain the data when it says it should.
How do you turn the phone off so that nothing is running at all? (i.e. to make sure that the internal battery is only being used to retain my data)
Does activating bluetooth drain the main battery faster even when the PDA is in standby mode? (I think i may have left it switched on last night)
Why would the internal data retention battery drain flat in under 5 hours when the main battery is removed loosing all data? Does it need the main battery in place in order to work? Could the phone and the PDA in standby mode by running off of the internal power?
Thanks in advance to any help you can give. As you can imagine i'm very disappointed as i love the functionality of this device.
Neil
When you took the battery out and left it out, if you had slid the back down (this is the same as a power off) you would of been ok.
The action of sliding the back down and back up is equvalent to a power off. When you press the power button after this, it is like a cold boot. (Not a hard reset)
I hope that made sense.
So to power off the phone and PDA you have to slide off the battery cover and slide it back on again without taking the battery out. Surely there is an easier way to turn off the phone and PDA that to remove the battery cover?
Thats how i do it. I'm sure there is a different [proper] way, but i'm not sure what it is.
Hi
The main battery when flat enough to power off the pda should have 72 hours data retention, its designed that way... so if it goes flat on friday you will still have your data on monday. thats why it was designed that way and apparently it shuts of at 50% capacity.
Bluetooth active will drain more power.
the backup battery is only supposed to last around 20 mins or less, designed so you can take the main battery out without losing data. this is because Ram needs constant voltage to store contents. hence if you leave your main battery out for more time the backup battery has charge you will end up with a hard reset occuring.
The manual needs to be updated i guess. If you want to turn off the phone you can turn on flight mode which disables the GSM radio functions.
Oh and out of interest for the battery type Li ion, its actually better to keep them charged, they dont have cycles like older batteries. they only have a certain lifespan which starts from the date of manufactor and keeping them at low charge degrades them faster.
Enjoy
SpeedN
So up until the 50% point, pressing the power button just puts the PDA in standby and the Phone is still running. Only when the power goes below 50% ish does the PDA power off completely?
So after the phone is fully charged, the M500 battery life meter says there is 6 hours and 31 minutes of battery life in it. You say that the device will turn itself off at 50% battery life remaining, so that means it only has 3h 15m of useable time before it switches off? Can the phone / PDA be used when power gets below 50% or will it just not power up until its recharged?
Thanks for your help BTW very useful information.
Neil
The battery life meter will say eg 6h 31m, the device will turn off in 6h 31m give or take (usage dependant).
when the device is flat there will be still 50% capacity in the battery to allow for the 72 hours data retention. hope thats clearer.
when it is in that state it wont turn on I think...sorry been along time since i been in that state, untill you charge it.
SpeedN
Surely the easiest way to solve this (and yes I was fooled by the manuals answer to press and hold) is to enable flight mode(which turns the phone off) then turn off ? there are a few apps/ shortcuts that will switch to flight mode easily, you then simply press the off button.
Or did I miss something
I think when we push the power off button (or if we select the machine to be powered off after a period of idle time, through setting), the machine will be off except GSM functions. So when you turn on again, it takes a few seconds to make the machine runs.
You can try if you turn off the button, after few minutes (should be more than 180 seconds), then push the Green button to dial, it takes 3-5 seconds to make the dialing pad comes out.
If you do not select the machine to be power off after a period of idle time, you can use other software to "screen off" the machine, so that when you push green button to dial, it comes out very quickly.
If you turn off the GMS, and turn off the PDA, it will not really get into sleep but will be in the state of retention of data. In any case, when you wake up the machine it takes a few seconds.
Therefore, when you are on the run (say on the street) and make calls frequently, do not power off the machine so that you can make calls quickly.
That is only my experience, I have checked other HP and XDA phones, same results. So nothing to do with the speed CPU and size internal ram.
When the machine is ON, I under clock to 208, the dialing pad also comes out very quickly.
flight mode = on , thats all, it turns the gsm function off, so battery would last long.

Strange power consumption issue after suspend

Hi,
With acbPowerMeter I looked at the power consumption of my Magician. Nothing extra has been installed, the SD card is out of the slot.
No today items are active. Just the bare OS and the telephone app,
nothing attached to the phone.
After a soft reset the power consumption is 108 mA (GSM radio on), without backlight even 60 mA.
But now comes the trick. When pressing the power button the device goes to sleep. acbPowerMeter is still running as an application.
When pressing the powerbutton again and lookin at acbPowerMeter it now consumes 200 mA and drops then to 144, but never 108 again. That is 40 mAmps down the drain. WTF!
It has been noticed with other devices that the wave device has a bug that is causing this.
And it sure looks like it.
I have placed the wav1: device in powerstate 4 by setting the value in key:
hklm\System\CurrentControlSet\Control\Power\State\On
"wav1:"=dword:00000004
(like is default for the unattended state)
And then this phenomena does not occur but no sound of course.
Can anyone test it and confirm?
Thanks,
Tweakradje

Problem with the Corvus5 ROM

I was about to post this on Corvus5 dev thread but XDA won't let me
Anyways, I'm experiencing a lag problem when my Advent Vega timesout. This is fresh install of Corvus5 ROM, overclocked to 1.4ghz using SetCPU. After the screen timesout thenr waking the tablet up, everything slows to a crawl. After checking with SetCPU, it seems that I'm stuck at 216mhz.
I have successfully reproduced this bug a few times now, and I have to restart the tablet to make it usable again.
Just an idea but does setcpu have a profile that when you put the device in sleep/idle it clocksdown the cpu to save battery?
No, I don't have any profiles set.
I tried clearing data & cache, reflashing Corvus5, then installing SetCPU only (using corvus' SetCPU Custom config). I can still recreate the bug
Blue led inside POV Mobii
I also can't post in the dev thread and experience a "problem" with Corvus5.
Resuming the device, a blue led inside the device will turn on. The led is near the camera under the black border, it leaks a bit of light onto the display (not noticable when the display is on).
Firing up the camera and backing out of it will turn off the led. Suspending the machine and resuming it will turn it on again.
It's more an aesthetic problem, though it may be an extra drain of power.
I'm having this same problem, but I have not been using setcpu
You might want to try another refresh and trying CPU Master to set the Mhz
As for the Blue light for me it is normally when my using is in nvflash mode. Try a hard power off to see if it goes away e.g. hold power for 5 seconds.
If still not gone then once fully powered off put it into nvflash mode and out again.
To do this press back for 1 sec then still holding back press power for 1 sec, then let go of power, wait another second and let go of back. Hence seq is lig
back 1sec
back + power 1 sec
back 1 sec
Let go of buttons
You should now be in nvflash mode, at this stage press power for 5 seconds to get out of it.

Waking up from sleep - TF reboots

So I got on that newegg deal and got yesterday TF and a dock for $400. Impressed with a build and quality but scratch my head over how the tablet wake ups from sleep mode. What I see is whenever screen goes to sleep due to inactivity (2 min default), and I am trying to wake it up and hit the power button, then TF goes to a full boot sequence instead of just waking up.
I verified battery is full and I tried to update Firmware from 3.1 which it came with to HC 3.2 OTA but it did not help. Interestingly, whenever I manually put it to sleep (using power button quick press) and then turn it back on right away it seem to come right back, so the issue only occurs over either tablet going to sleep on its own or due to longer sleep interval.
I have a bunch of Android devices in family, staring with G1s which were replaced with Vibrants and later Sensations, as well as 7 inch tablets, all rooted, and all devices quickly recover from sleep using power button instant press. Am I having defective tablet or HC has different wake up protocol?
Thanks,
Vadim.
at least yours goes to sleep mine wont, its a pain in the ass, i have the timer set to 15secs and the screen never turns off, i would take the sleeping issue over the non sleeping issue. try hitting your mouse button to wake from sleep. read somewhere that is how to wake it properly with the new firmwares.
I would try mouse wake up if it would be in the dock, but most of the time I use it as a tablet. Any other option except for power button? For instance, Nool Color wakes up also from N button in front, but I could not find any other way on TF.
Thanks.
outside the dock the only thing i can say is power button only way to wake, maybe try a factory reset. go in settings, privacy, and data reset, everything will be like factory just with new firmwares. i would try that.
Have a look here.
I had a similar problem. would always reboot on wake up.
http://forum.xda-developers.com/showthread.php?t=1286549
set disconnection policy for WIFI to "Never" (does not effect battery life much)
In location and security turn off "use wireless networks."
This worked for me.
I have a B80 model, no keyboard

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!

Categories

Resources