Database Users

[Q] Battery Issues;BSOD/SOD;EBL?

So, I'm at a loss of what to do here. No matter what settings I seem to use I can't get good/decent battery life.
In fact, I get terrible battery life. With light to moderate usage I have to charge my phone at least two times a day, mostly three. Current widget reads that at standby I'm anywhere between 55mA-70mA and when in use 200mA-500mA. When charging it reaches 400mA-600mA
I see everyone talking about being able to get 5-10mA and I'm amazed at this. I've searched and read most "Battery saver" threads and none of it seems to work.
I was originally using Chucky rom lite and when I noticed the drain was abnormal I switched to the set up that chiasoft uses in his ReadMe for the ROM (stock 2.10ROM/2.08 radio).
Although since switching to the stock WinMo ROM I had repeated BSOD and SOD issues. To the point that it became unusable. I switched over to latest Energy ROM.I installed EBL and on both Stock and this Energy ROM. I am still having BSOD/SOD problems. Could it be the EBL? I plan on upgrading the radio to 2.12 in a few after I test out this EBL theory.
My setup as of this post is this:
WinMo ROM: Energy.BLACKSTONE.21916.Sense2.5.Nov.08 (Switched back to Stock 2.10)
Radio: 2.08.50.08_2 (Switched to 2.12)
Android: MooMoo Froyostone Sense 3.2 w/hastrain kernel
SetCPU:
998max/245min Ondemand on boot
Profiles: Screen off; Priority 100; 384max/245min ondemand
Battery <25% 576max/245min Priority 0 ondemand
Sampling 20000; Up Threshold 40
Advanced Task Killer:
Kill Level Agressive
I really don't want my LI-ON battery to die before I've even had the phone for the year. So if anyone can think of anything to help I'd be ever so grateful.
And of course, thanks to all the people who make all this possible.
(Sorry for the tl;dr post. I wanted to give as much info as possible.)

when you fully charge your batter what is your mV ? use the battery life widget to determine this. If it is not nowhere 4000mV once fully charged, you might need to consider buying a replacement battery.
btw. my mA reading is actually worst than yours. Might have to calibrate the battery again later.

mofoahh said:
when you fully charge your batter what is your mV ? use the battery life widget to determine this. If it is not nowhere 4000mV once fully charged, you might need to consider buying a replacement battery.
btw. my mA reading is actually worst than yours. Might have to calibrate the battery again later.
Click to expand...
Click to collapse
idk what it is fully charged. I'll be sure to check it later though. How do you calibrate the battery?
Also, I realized that I made an oversight on my part. When I switched to the stock WinMo rom I hadn't realized fully that it changed my Radio to 2.08 even though I posted it.
The rom chef recommends 2.10ROM/2.12 Radio, so that's what I switched to to check out that combination.

btw change it to interactive not on demand.
you charge the battery when your phone is off. Till your charge indicator turns green.
Once that is off. you can use root explorer or adb and go to rm/data/system delete the batterystats.bin leave your phone plugged in while you are deleting the batterystats.bin file
i prefer root explorer. but its not free and your device has to be rooted.
let the phone drain the battery till its dead and turn it on again to make sure it is completely dead.
charge the phone like you would usually afterwards.

mofoahh said:
btw change it to interactive not on demand.
you charge the battery when your phone is off. Till your charge indicator turns green.
Once that is off. you can use root explorer or adb and go to rm/data/system delete the batterystats.bin leave your phone plugged in while you are deleting the batterystats.bin file
i prefer root explorer. but its not free and your device has to be rooted.
let the phone drain the battery till its dead and turn it on again to make sure it is completely dead.
charge the phone like you would usually afterwards.
Click to expand...
Click to collapse
I don't have interactive in my options.

what version are you running?

mofoahh said:
what version are you running?
Click to expand...
Click to collapse
2.03 I got it through here.
Just installed 2.04 and there still isn't an interactive.

thats odd. because im on 2.0.4 also and I am able to select interactive.
btw i followed this guide for the battery conditioning.
http://forum.xda-developers.com/showthread.php?t=827762&highlight=ultimate+setcpu
and this one for my setcpu settings.
http://forum.xda-developers.com/showpost.php?p=8246854&postcount=4

mofoahh said:
thats odd. because im on 2.0.4 also and I am able to select interactive.
btw i followed this guide for the battery conditioning.
http://forum.xda-developers.com/showthread.php?t=827762&highlight=ultimate+setcpu
and this one for my setcpu settings.
http://forum.xda-developers.com/showpost.php?p=8246854&postcount=4
Click to expand...
Click to collapse
Yeah. No interactive settings. Also, that guide recommends 1190 max, but mine only goes up to 998.
Also, I finally got it to down to 7mA in standby. When I changed the radio to 2.12 and using a 2.10 stock WinMo rom.

no issues here getting 48 hours of light use, or a full 24 of moderate use...

I've yet to "condition" my battery. I'm worried it'll do more harm than good. Especially since I just got it finally to a decent mA draw. Although I'm worried my phone won't charge up to 100%. Always stop at 95.
Is conditioning really necessary/important?

easy answer... whats your full charge voltage? shuld be 4.2
if not , your looseing batt life..

t1h5ta3 said:
easy answer... whats your full charge voltage? shuld be 4.2
if not , your looseing batt life..
Click to expand...
Click to collapse
yes full charge voltage should be around 4.2. Try charging it with the phone OFF till your charge indicator is green. This way you can achieve a full charge.
By the way how the hell are you getting 48 hours on light usage?? excuse my language. What are your setcpu settings, configurations. etc.

mofoahh said:
yes full charge voltage should be around 4.2. Try charging it with the phone OFF till your charge indicator is green. This way you can achieve a full charge.
By the way how the hell are you getting 48 hours on light usage?? excuse my language. What are your setcpu settings, configurations. etc.
Click to expand...
Click to collapse
Yeah, 48 hours seems improbable. I finally got it down to 7-10mA on standby, and I think it charges up to 4.2 but I'll find out for sure tonight.

same
I had the same problem, make sure you use EBL android launcher and set to autoboot at 3 seconds. Make sure you restart your phone anytime youw ant to load android. I assure you this will work.

My HD2, like all others can be flattened in 2-3 hours with windows/android if used hard, the difference seems to be on very light usage/standby win mobile could last 4 days... with everything turned off and basically not used Android would struggle to last 2 days !
Same phone same network/signal levels etc, can only be poor power management within Android, and I think that means voltages for all the processor and comms modules, not just a simple case of turning down speeds.
What do others think ?

Update: Upon switching to WinMo:2.10 and Radio:2.12+ MooMoo's MMS fixed froystone3.2 I was achieving 6-10mA in standby. The phone would last all day with a two-three hour charging period with moderate usage. Low battery use, rare DC's. Perfect. Best build I've used so far.
I'm noticing a new problem however, and I wonder if it's happened to Chiasoft who recommended this build. I'm getting serious touch screen freezes since last night. Anytime before that the set up was working AMAZINGLY.
Now? It's almost unusable sometimes. This morning it was happening in Android so I switched to WinMo and surprisingly enough it happened in there too. So I read touch freezes are Radio problems mostly. Is this true? Should I switch to a new radio? I'm confused as to why it would just randomly start happening though and worried it would mess up my battery troubles I just solved.
Any advice?

Hmm. I noticed that it almost always freezes when I hold down the end home button to turn off the phone or data or to silence it. I can't actually use the touch screen again until I hit the button again to put it to sleep.
I wonder if it's hardware related because it was happening in WinMo that way as well.

Okay, so now the entire adroid system is acting up mostly related to the touchscreen. Like I use the calculator and it appears that i'm holding a button down. Or I try to make a call and it's not responding. It appears that when I hit end call button repeatedly it allows me to unlock the phone. But when holding down the end call button to get to the Power Off screen nothing in that menu is responsive.
It seems... software related, but I'm not sure. Any info would be helpful. I'm going to reformat my card and reinstall droid and see what happens.
So, called t-mobile. They're sending me a new replacer phone. Oh well. We'll see how that one goes.

pretzdothack said:
Okay, so now the entire adroid system is acting up mostly related to the touchscreen. Like I use the calculator and it appears that i'm holding a button down. Or I try to make a call and it's not responding. It appears that when I hit end call button repeatedly it allows me to unlock the phone. But when holding down the end call button to get to the Power Off screen nothing in that menu is responsive.
It seems... software related, but I'm not sure. Any info would be helpful. I'm going to reformat my card and reinstall droid and see what happens.
So, called t-mobile. They're sending me a new replacer phone. Oh well. We'll see how that one goes.
Click to expand...
Click to collapse
I give you only a very short suggestion
You have just to DELETE SETCPU
and delete ANY TASK KILLER (you can keep it just to close any apps that could hang, but not to "free up ram")
Android is not Windows, you dont need to free up ram, and you dont need to overclock/undervolt to gain some minutes of battlife despite stability.
Talk to any Dev and they will confirm this.
Good Luck

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.

[Q] Flashing ROMs and battery life

Ever since I started trying different ROMs, I've been getting poor battery life. I started with Iced Glacier and just assumed the battery issues were due to the overclocking. Then I tried CM7 Nightly Build 60, which had major issues for me, particularly with battery management. Now I'm running Royal Glacier with Faux's undervolted kernel. I would have thought the undevolting would help, but not so much. Any suggestions for a noob?

You could use an app like SetCPU to underclock your CPU and/or try another ROM. I get great battery life on eViL's Desire HD port. It also has pure Sense (a much nicer UI in my opinion than plain Android and mySense).

TeeJay3800 said:
You could use an app like SetCPU to underclock your CPU and/or try another ROM. I get great battery life on eViL's Desire HD port. It also has pure Sense (a much nicer UI in my opinion than plain Android and mySense).
Click to expand...
Click to collapse
CM7 has built in controller under Performance for that. But if your using Faux's kernel you might want to check the clock frequency as his regular max is 1113mhz. I suggest you download the new CFS2.6.1LV kernel of his and run it. You may want to underclock to min:256mhz/max:768mhz and using smartass gov. When you are done and time you may also properly recalibrate your battery by flashing the battery stats from CWMR (easy) or by removing it manually from terminal (also easy simple rm command).
Now since I flashed new radio when CM7NB60(AOSP2.3.4) came out my data will be useless to you since it can mean its radio related. Only you can compare so if its still problem you may want to flash the new radio also and see if it gives you better battery life along with signal reception.

Also you might try wiping your SD card (backup of course) when you flash a rom, I've noticed that helped me a few days ago when I wiped my sd and reloaded the Sense 2.3.3 leak. Battery life has increase dramatically!

@TmpUsr, could you give me a rundown of properly recalibrating the battery via CWMR? Thanks for everyone's responses.
Sent from my HTC Glacier using XDA App

Sure why not use my old meth I posted here under this very same section.
Well the borderline idea is the same as you already know you have to completely drain it. Now never use any volt meter those people use to completely discharge it as the negative effect I already explained to you in that post. So best way is to do it by recalibrating so what you do is:
1) Fully charge it.
2) Drain it till you get 1%.
3) Go in recovery and wipe battery, reboot (batterystats.bin created).
4) As you still have battery low now let it charge till 100%.
5) Do the cycle again.
NOTE: This is what I would recommend but as we know the whole issue with CWM restarting while phone is off as you can flash the stock recovery and go back as it takes 3sec. If not follow the above.
1) Heavily use your phone so it drain the battery till its 1%
As you will see the low battery light flashing just so you don't lose your data save it by rebooting.
2) As you still have some battery power left you can now go to Recovery and wipe battery stats.
Or you can manually do it from adb shell by using remove command "rm /data/system/batterystats.bin".
3) Keep it on till its turns itself off.
As you may have guessed it still has power left so keep using the device till its drained completely I would recommend rebooting and going in bootloader as it uses more power due to bight screen as Recovery uses less power on display.
4) Now turn it back on again in bootloader till it turns off again.
It will keep turning itself of as no power left, this is what you want. This is safe way to discharge it without having negative adverse effect.
5) Now let it charge via A/C instead of USB.
Now when the light turns green unplug it and replug it till its green again, keep doing that till you see its green only. Now once you reboot in Android it will rebuild the batterystats.bin and you will be fully recalibrated.
Click to expand...
Click to collapse
Just ignore the part about CWMR post-3.0.0.6 issue was before we were not able to charge it unless we used stock recovery as it would just simply restart.

Thanks. I tried an abbreviated version of that this morning (before reading your post). I charged all night as usual, then first thing this morning turned it off, pulled the battery (hadn't done that since flashing the ROM), then booted into clockwork recovery and wiped battery stats. It's currently almost 9pm and I'm at 52% with light use (though the first half of the day was spent in a poor signal area). If it gives be further trouble, I'll do the whole song and dance above.
Now if I could just figure out why my email and push alerts won't work.
Sent from my HTC Glacier using XDA App

U can also install battery calibration frm market place which does the same as goin in recovery & wipin battery stats....
Mytouch 4g-White
Permrooted s=off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.0

Current problems with CM7

Debating about whether to install CM7, but there have been a few problems with it. I'm having a tough time finding the current state of the following issues:
1. Sleep of Death - Nook goes to sleep and doesn't wake up, forcing a reboot. There seems to be some debate over whether this is solved. One of the threads indicates that it's not a problem if you turn wifi off with the screen. Can anyone confirm?
2. Battery drain - Battery drains at 2%-3% per hour in sleep mode. I believe this is resolved. Can anyone confirm?
3. Premature Battery Death - Battery dies at various points over 0%. There seem to be various utilities for resetting battery stats, etc., but I can't figure out whether or not this is resolved.
4. Screen stays on when plugged in - Forced to hit the screen off button when plugging in the Nook. I've seen recent complaints about this one, so I'm assuming it's not resolved.
I did go through the threads and am confused about whether these issues still exist, so I figured I would try the Q&A section. If someone with CM7 wouldn't mind jumping in, that would be great. Thanks!

1. Maybe, I'm a lucky one but I haven't had problem with SoD regardless wifi on or off. I've been using nb100 and up, and now at 138
2. Using 138, i got 2-3% drop overnight, about 8 or 10 hours. With 120, zero dropped
3. Not experienced yet since I never let it down to sub-5
4. Mine seems act the opposite way: screen off, plug in to charge, screen automatically on, have to press power button to put screen off again.

1. I haven't seen this in recent nightlies.
2. Fixed; NC now deep sleeps when unplugged, even with WiFi on.
3. Fixed as far as I know.
4. Mine acts like yours and votinh's both; these are not mutually exclusive. If you plug in while on, the screen eventually dims instead of going off. If you plug in while off, the device turns on, sometimes just the backlight. I'd call this one minor, especially in relation to the other issues.

511pf said:
Debating about whether to install CM7, but there have been a few problems with it. I'm having a tough time finding the current state of the following issues:
1. Sleep of Death - Nook goes to sleep and doesn't wake up, forcing a reboot. There seems to be some debate over whether this is solved. One of the threads indicates that it's not a problem if you turn wifi off with the screen. Can anyone confirm?
2. Battery drain - Battery drains at 2%-3% per hour in sleep mode. I believe this is resolved. Can anyone confirm?
3. Premature Battery Death - Battery dies at various points over 0%. There seem to be various utilities for resetting battery stats, etc., but I can't figure out whether or not this is resolved.
4. Screen stays on when plugged in - Forced to hit the screen off button when plugging in the Nook. I've seen recent complaints about this one, so I'm assuming it's not resolved.
I did go through the threads and am confused about whether these issues still exist, so I figured I would try the Q&A section. If someone with CM7 wouldn't mind jumping in, that would be great. Thanks!
Click to expand...
Click to collapse
1) I get SOD about once a day regardless of how I have it set up. It does happen less with wifi on sleep only but at work I need to push data, so my wifi is on all the time and...it's an issue, not terrible but annoying none the less.
2) Battery drain, I get about 36 hours if I use it lightly, but I tend to charge it nightly because I can't take a chance of heavy use at work and loosing it.
3) PDB, never had this problem.
4) The screen turns off by just hitting the screen off button. This isn't a big a deal actually, since you gotta plug the thing in, another button isn't a big deal. I have katecca screen lock and off in my bar at the bottom, so it's easy to turn off. I also have the nook power off widget but I haven't used it much.

That's great. Thanks a lot for the responses. Really helpful.

I have only had it CM7 on my nook for one day, so im not sure about the battery issue. But i know i put it down around 10pm last night with less then half a battery and i got home from work around 3pm and it had about 25% batt left.
Besides that sometimes when i plug it in it stays lit up. but thats a "meh who cares" to me at least.

Running 7.1.0 RC1 with Dal's OC, On Demand, with lowered Voltage on the steps
1) I've only had one SOD ever (knock on wood), it seems to be mostly cleared up
2) Battery drain has not been a problem for me. On .29 it was more only 1%/hr for battery drain.
3) I haven't experienced early battery death at all
4) It isn't a big deal, especially if you charge with the provided outlet adapter for quick charge. Don't see this preventing you from installing CM7.
If these stats are correct from ASI (I'm hoping they are, they sound right), I'm at 76% after 3 days, 19 hours uptime, and 7 hours of it without sleep.
I say go for it. Even if it is off SD (mines on emmc) it is still a much better experience than stock/rooted. I doubt anything will make me change from CM7, unless ICS becomes a viable option in the future.

Just a follow up on this. I installed CM7 and have not had a Sleep of Death, have normal battery drain comparable to stock rooted, and have not had premature battery death. The screen does come on when I plug the Nook in, but like everyone mentioned, I just turn it off and it's no big deal.
So far, my wifi actually reconnects more reliably than on stock rooted 1.1. I'm overclocked to 1200 Mhz, with no voltage or other adjustments.

Following up again - I get a SOD or a reboot about every five times I turn off the screen in CM7. I tried to use Tasker to turn wifi off with the screen, which has solved the problem for some people but this made no difference at all. I was running a nightly from late July and updated to another from late August (173?) but the problem hasn't gone away. I may try Stock 1.2 rooted.

511pf said:
Following up again - I get a SOD or a reboot about every five times I turn off the screen in CM7. I tried to use Tasker to turn wifi off with the screen, which has solved the problem for some people but this made no difference at all. I was running a nightly from late July and updated to another from late August (173?) but the problem hasn't gone away. I may try Stock 1.2 rooted.
Click to expand...
Click to collapse
I had no SODs from almost a week with n165; I upgraded to n171, got an SOD first time I put it down for a while, so I reflashed n165 and I'm sticking with it until I hear of something I need.
WiFi always on.
As always, YMMV.
Sent from my NookColor using XDA Premium App

Just a little update:
Since using nb169, I got a few SoD, did update again to nb173, still got hit occasionally.
I never have this kind of issue before but lately.
The changes I made
a. Played around with ADW Launcher setting (especially Desktop Animation)
b. Recently installed Simi Clock and updated some apps (such Nook app)
c. Recently having 8GB uSD card plugged in.
For some reason, I don't think a. and b. causing problem but c.

can you run cm7 with the 1.2 or 1.3 updates from b&n? im on a autonooter 1.1 and have been wanting to move up to something better especially if i can have flash finally.

miss_october said:
can you run cm7 with the 1.2 or 1.3 updates from b&n? im on a autonooter 1.1 and have been wanting to move up to something better especially if i can have flash finally.
Click to expand...
Click to collapse
CM7 is custom Gingerbread-based ROM, it has nothing to do with stock ROM and there is absolutely no relationship between the two (except they are both Android OS)

votinh said:
CM7 is custom Gingerbread-based ROM, it has nothing to do with stock ROM and there is absolutely no relationship between the two (except they are both Android OS)
Click to expand...
Click to collapse
thanks for the response

One last (I think) follow up. I installed stock rooted 1.2 thinking it CM7 causing me problems over the last month. Turns out I had the same problem on CM7.
I read my Nook before I go to sleep, so it's often dark in the room. I turn the brightness WAY down. The problem ended up being the Adjbrightness "Lock brightness so other applications can't change" setting. It has something to do with screen dimming when turning off the screen. This setting being on was causing frequent reboots both on CM7 and stock rooted 1.2. I ended up going to ScreenFilter instead, and the problem has completely gone away at least so far.

511pf said:
Debating about whether to install CM7, but there have been a few problems with it. I'm having a tough time finding the current state of the following issues:
1. Sleep of Death - Nook goes to sleep and doesn't wake up, forcing a reboot. There seems to be some debate over whether this is solved. One of the threads indicates that it's not a problem if you turn wifi off with the screen. Can anyone confirm?
2. Battery drain - Battery drains at 2%-3% per hour in sleep mode. I believe this is resolved. Can anyone confirm?
3. Premature Battery Death - Battery dies at various points over 0%. There seem to be various utilities for resetting battery stats, etc., but I can't figure out whether or not this is resolved.
4. Screen stays on when plugged in - Forced to hit the screen off button when plugging in the Nook. I've seen recent complaints about this one, so I'm assuming it's not resolved.
I did go through the threads and am confused about whether these issues still exist, so I figured I would try the Q&A section. If someone with CM7 wouldn't mind jumping in, that would be great. Thanks!
Click to expand...
Click to collapse
I try to stay up to date with the latest nightlies.
1) This is not completely solved. It's rare now (I think it was issues with WiFi), but it has still happened to me recently.
2) Battery drain was fixed with kernels that support Deep Sleep correctly. Not any 7.0.x builds, only 7.1.x+ (RC1) and nightlies have fixed kernel. So this shouldn't be an issue (unless you have a rogue app that is keeping the CPU active, which would prevent Deep Sleep. The "CPU Spy" app will let you see if this is working correctly).
3) This is better, but still a problem. My Nook Color will just switch off at 4% battery now. It use to switch off when I was a lot higher. It's not supposed to do that. It's supposed to gracefully shutdown when low. I have several iOS and Apple devices, so I'm use to things shutting down correctly when low. My Nook Color always just randomly powers off.
4) This isn't a big deal. The screen comes on when charging, but you can turn it off if you want. It stays dim, and the Nook Color charges fine. Dalingrin (the kernel developer guy) said leaving the screen on was a fix to some nasty crash.
#3 is the biggest issue to me, as I've been in the middle of something when my Nook Color randomly powered off. Clearing battery stats, rebooting, etc - none of that makes it perfect.
#1 use to be the biggest problem, but it's very rare for me now.
#2 has been fixed, and #4 doesn't bother me.

stolenmoment said:
I had no SODs from almost a week with n165; I upgraded to n171, got an SOD first time I put it down for a while, so I reflashed n165 ...
Click to expand...
Click to collapse
I misspoke; n165 SOD's on me too, so I conclude that I dl'd 165 and didn't flash it; I reflashed n161 and have been stable since.
I keep WiFi on for email and podcast updates.
I've always got an 8G uSD card in.
Sent from my NookColor using XDA Premium App

Nook's endless freezes

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.