yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Ronin3178:
How often do you reboot between flashing nightly's? I believe fattire's new uboot that is supposed to help with PBD only works during the boot process, so the less you reboot, the more likely you are to still have PBD.
[Nook Color Android Development] I Am Marino:
Mine dies normally at 4%, I've had some times when it dies sooner, but that's my lucky number usually.
[Nook Color Android Development] gudism:
well I dont reboot very often at all, only really when it dies having its PBD (which really isnt a reboot because once you plug it in the screen comes back on...I dont turn it back on)

so should I reboot regularly? twice a day, like nook meds? lol
[Nook Color Android Development] Ronin3178:
I reboot a couple of times per nightly, fixing netflix, installing chainsfire driver, etc. I space it out a little bit. I don't get PBD anymore, altho I dont get a graceful shutdown either... it drops @ like 6% or so, moments after my low voltage alarm goes off @ 3050mV
[Nook Color Android Development] paleh0rse:
Anything less than a graceful shutdown is still considered a PBD.

I'm in the same boat. I have never seen a graceful shutdown on my nook with a .32 build.

Mine still goes dark at ~5% every time... :(
[Nook Color Android Development] gudism:
Ok, I'll try rebooting more often, see if that improves anything.

By the way, what exactly is your low voltage alarm? Free app?
[Nook Color Android Development] Ronin3178:
It's called "battery monitor widget" by 3c, I use the free version, in settings there is a high & low voltage alarm among many other useful things.
[Nook Color Android Development] I Am Marino:
I just use minimalistic text to show a battery voltage widget, when it goes below 3100mv, I know the time is coming.
[Nook Color Android Development] BitingChaos:
Wow. Just had another one of these.

Nightly 106 I think. Dalingrin's 6/18 kernel.

System died at ~40% battery. I thought it was a SoD issue again, but it gives the "charge me" screen when I hold the power button.

I had been getting shutdowns at around 11% before that. I've been rebooting quite a bit just to try and get the battery readings more accurate.

I see now that 7.1 is at RC stage. It's a shame we are still dealing with inaccurate battery readings, "premature battery death", even screen of death issues (WiFi problem?), and other WiFi issues (connection always shows 1 bar strength) so close to a release.
[Nook Color Android Development] gudism:
Thanksfor both replies re battery monitor widget, have it installed now.

Does anyone know what MHz is fully charged? I had a vague recollection of 4500mhz
[Nook Color Android Development] rhester72:
The fully-charged mAh is 4010.

Rodney
[Nook Color Android Development] gudism:
Thanks. Odd on last charge, alarm sounded at 4100 yet it only showed 92%.

Any ideas as to why this would occur? Is it due to the battery being a bit out of whack with the whole PBD issue?
[Nook Color Android Development] rhester72:
I don't think so - my understanding of the need to manually set the max mAh is so that it can calculate current as percentage*max. I have found, though, that the battery application doesn't seem to pick up a change of the max value without being restarted.

Rodney
[Nook Color Android Development] Ronin3178:
The max mV I see is around 4105 or so. As far as mAh setting I used 4000 per specs I found on like enGadget I believe. I only set my min voltage for 3050, the absolute low end is 3000mV, you shouldn't expect to get there.
[Nook Color Android Development] khaytsus:
Except that it's 4200, assuming you mean voltage, not mAh..
[Nook Color Android Development] CalsNC:
Sorry, most of this conversation is over my head. I'm running dual boot sd card CM7 and emmc. Just looking for the best way to extend battery life...and has anybody figured out a way to shut off all phone functions in CM7, Thanks.

If I'm in the wrong thread, cuz I couldn't find anything with a battery saver topic.
[Nook Color Android Development] rhester72:
No, I meant mAh...the # you have to manually input in the Battery Monitor widget. Max voltage is 4200 (+/-...mine's actually 4208 from what I'm reading).

Rodney
[Nook Color Android Development] gudism:
Is the manual input you mention the figure in battery monitor widget under 'battery capacity'?
[Nook Color Android Development] Ronin3178:
Yep, settings/monitoring/battery capacity.
[Nook Color Android Development] wpbear:
Not sure where this new problem goes so here is what happened.

Running CM7 Nightly from 6/23 with OC Kernel 6/18 on EMMC. I have been running nightlies or stable CM7 for at least a month now. Never had a battery problem other than no deep sleep before that was fixed.

Tonight I plugged in to my PC USB port to transfer some files (first time doing this in over a month) NC at first didnt recognize it was plugged to USB then I unplug and replug and the battery meter went from around 70% to 100% immediately.

After a a format and restore of a nandroid it still says 100 and will show discharge but I know it is not 100% since it has not had time to charge. I have reset batt stats also and no change.

Right now I am leaving plugged in to charge overnight since the "n" light on the nook cable is showing orange as in charging even though the batt gauge shows 100%.
[Nook Color Android Development] fattire:
Sounds like your battery is confused and reporting less power than it is capable of holding. Hopefully a few boot cycles will get everything fixed up.

Dunno what the cause is, but if all goes well it will become more accurate over time...
[Nook Color Android Development] wpbear:
I checked Spare Part and Batt stats and last night it was about 4165 and based on before the jump it was about 70%. This morning is at 4190 and the "n" charger is fully green and still shows 100%. I am now going to just use it like normal and see what happens.

Thank you, I hope it works itself out.
[Nook Color Android Development] khaytsus:
Yep, you gotta be specific... Quite a few posts after yours of people confusing the information.

Our battery is 4000mA large, but LiPo max voltage is 4200mV. Close enough for confusion ;) 4000mV is far from fully charged, so people could get confused.
[Nook Color Android Development] gudism:
thanks for that
[Nook Color Android Development] gudism:
I think my battery is getting closer to being right after more and more reboots......a few days ago when it was at 4200mhz it was telling me it was only 92% charged, and was PBD at 14%.

took it off charge this morning and it was 4200mhz again (obviously) but was telling me it was 99%.

Will have to wait and see what happens when it get to 15% and below.

thanks for peoples recommendation with battery monitor widget...been most helpful with all this :)
[Nook Color Android Development] buzz killington:
I guess I'll post my experience with pbd here,probably doesn't mean anything but it might help.

I used to get the pbd pretty consistently at around 20%, after the fix fattire put in it got better, the pbd happened at around 9%. It didn't seem to improve after a few charge/discharge cycles so I left it alone.

Last week I restored to stock rooted 1.2, and did a full charge/discharge, and reinstalled the nightly. I just ran it down to 3% running 7.1rc1 and it was still going, so I think mine is pretty much fully fixed.
[Nook Color Android Development] gudism:
still PBD at 15%..... oh well, can't complain with how good our battery life has become!
[Nook Color Android Development] Ronin3178:
Thanks, I thought it would be easiest to have the higher voltage start at the left of the x-axis, but after trying to get it that way on a few free online graphing sites.... no go.
[Nook Color Android Development] :
Just do a loop from 100:-1:1 (or w/e)

Or use fliplr or flipud :)
[Nook Color Android Development] chisleu:
I went back to beta 3.1 from n86 because my wifi kept locking up (requiring reboot), the battery was acting crazy (jumping around even after resetting stats), and I had PBD and couldn't get it to sleep (some android system operation eatting battery at 600mhz most of the time with the screen off.) I had also wiped the caches.

On 3.1 I have no jumpy battery, it sleeps perfectly, the wifi is good.

I am working on running the battery down (~80% now) to see if I get any jumpy battery or PBD.

Also, I have been sig'ed!!! epic.
[Nook Color Android Development] rhester72:
Important - what kernel (before and after)?

Rodney
[Nook Color Android Development] derekr:
Hey Ace,

That's not gonna do it! The problem is in MATLAB's "plot properties" on the x-axis of the plot, which insists that it plots from min to max values left to right, regardless of the data order. Won't let you change that... But we digress, and are OT :D

The big question is what the hell is going on in my Nookie?
[Nook Color Android Development] :
Then this:

plot(x,fliplr(y));set(gca,'xdir','reverse')

But can you fill out the form from the OP? Or maybe you did and I'm too lazy to look back two pages :P Have you ever ran stock 1.2 until drain?
[Nook Color Android Development] paleh0rse:
Ok, I wiped, installed 1.2 keepcwm again, and drained it as far as it would go.

Clarification needed: for those of you who successfully used this method to fix PDB, did you only partially recharge it before wiping again and re-installing CM7, or did you let stock 1.2 recharge to 100% before doing so?
[Nook Color Android Development] :
I did partial, but the battery shut down at ~4% (which is where it still shuts down with beta 3.1 and latest oc kernel and cyan edition bl). If it didn't get around there, maybe charge a bit more and try to drain lower? How far did it get?
[Nook Color Android Development] paleh0rse:
Well, that is actually something I thought was strange. I left it qt ~45% playing a 2-hour movie on youtube when i went to sleep last night. When I woke up, it behaved like a SOD would. It allowed me to do a hard reset using just the buttons (no cable), and it booted all the way up and showed a 12% charge -- there was obviously no "not enough battery to boot" message.

Then, after less than 1 minute of use, I experienced the usual PDB shutdown behavior -- in other words, there was no warning, and now it does nothing when I try to use just the buttons to reset.

I have not tried to boot with a cable yet (will do tonight). I just wanted to get clarification before I move forward with any recharging and re-installing of CM7.

Do you think I should do a partial charge to 17%, and then re-drain to test the 15% warning message and actual shutdown %age? I think that's what I'll try first...
[Nook Color Android Development] derekr:
Yep, Ace that works BUT I still think my original plot shows the voltage drop off more dramatically. Can we still be friends?

And just for you:

PBD REPORT FORM

TEST CONFIGURATION:

BOOT DEVICE: eMMC

MLO: as included in n87

U-BOOT: as included in n87

KERNEL: dalingrin OC5/23

OVERCLOCKED?: to 1200

GOVERNOR: Conservative

SYSTEM: CM7 Nightly 87

PBD: Yes

TEST COUNT: 1x- today during battery discharge test. Normally charge before 40%. Didn't actually PBD - I shut it down at battery voltage 2886 mV. Won't restart...

TRIED REVERTING TO OLDER HC/CM7: NO

TRIED WIPING CACHE/DATA?: NO

DID IT WORK? N/A

PREVIOUSLY INSTALLED:

☑ Stock 1.0

☑ Stock 1.1

☐ Stock 1.2

☑ Nookie Froyo (any)

☑ Honeycomb (any)

☑ CM7 2.29 (any)

☑ CM7 2.32 beta 3

☑ CM7 nightlies > 84 (or whenever .32 appeared)
[Nook Color Android Development] Ronin3178:
Hold up, wait a minute.... the only "warning" I have ever received is the 15%, on both my Nook and OG Droid, any shutdown after that is because the battery got too low (as shown in my post at the top of the page). 3041mV is @ the low end of the battery stability, as someone pointed out earlier in the thread.

So I wouldn't advise calling a PBD if it goes below 15%. If you play a game/watch a movie (things that workout the CPU) you are going to have a significant drop in voltage. Since we are talking about milliVolts here, its going to happen fast. My watching the battery from 18% - 4% only took maybe 30mins, and that was with full screen brightness/wifi on/BT on, watching my battery info app.

Now I wouldn't say plug in at 15% everytime, but don't expect it to run down to 1% everytime either. Just the opinion of someone who works with U.P.S. batteries everyday....
[Nook Color Android Development] :
What program are you all running to see all this info? Thanks.
[Nook Color Android Development] Ronin3178:
Battery Booster, search on the market, it only runs phone size on the nook, but theres a notification bar icon too.
[Nook Color Android Development] paleh0rse:
I understand that it was probably not a PBD -- I just used that (mistakenly) to describe the behavior.
[Nook Color Android Development] keyodi:
Has anyone tried copying and replacing the batterystat.bin from someone who's not experiencing the PBD issue?
[Nook Color Android Development] jekagan:
Guys,

For whatever it's worth, I booted my Nook up with a HCv4 SD and let it run ALL the way down. After that I plugged the device in and pressed the power button, at which point I saw the expected "not enough juice, wait 15 minutes" screen. When it finally did power back up, I went into CW and cleared the cache and Dalvik cache, then rebooted from my CM7 eMMC install. When CM7 booted, the power percentage was MUCH lower than I had previously seen with the PBD. I let it charge fully, and now my device is still running at ~12% and hasn't yet died.

Suffice it to say, I think this is a plausible fix. FYI, I'm running Dalingrin's beta 3.1 with the 5/23 OC kernel @ 1200.

Is it possible that flashing a new ROM on battery power alone might cause this? I'm wondering if there is something that the installation caches to somehow map the last known calibrated battery level with the current voltage, and if that stuff might get out of whack when a new ROM is installed with the battery further depleted before it fully boots up. Maybe I am just talking out of my a$$. Any thoughts?
[Nook Color Android Development] :
That's a known "fix", but interesting theory re:battery power alone issue...
[Nook Color Android Development] jekagan:
Just a follow up to the post above.

After the HC recalibration I mentioned above, the Nook finally just died at 2% showing voltage around 3000mv. MUCH better than the 31% it died at before.
[Nook Color Android Development] sinanju:
While the approach effective, the point is to determine a resolution that doesn't require a ROM hokey pokey and get it into an update.
[Nook Color Android Development] xxiworld:
For the record, just running HC for 15-20 minutes fixed my PBD. I didn't run the battery down in HC at all. I just noticed that my battery level in HC was 20 lower than it had been seconds earlier Cm7. When HC on SD was proving too laggy and some applications were not working, I switched my SD back again, and noticed the battery level was at the new, 20% lower level in CM7 as well."
[Nook Color Android Development] I Am Marino:
So it would seem that instead of using your battery meter to show when your NC is gonna die, look at mv, if it hits 3100 or below, get ready?
[Nook Color Android Development] xxiworld:
True. But it is such a bizarre fix, perhaps the very fact that it seems to work could help diagnose the issue??? It seems utterly implausible that simply popping in an SD build could fix the emmc build...but we now have a number of data points suggesting that it does.

FWIW, at the time I had PBD I was running beta 3.1 with the 5.13 OC and b&n uboot. I had previously had installed stock 1.0 and CM7 7.0.2 stable. I never flashed stock 1.2.
[Nook Color Android Development] sinanju:
Right. But as ace7196 pointed out, that's a well-known work-around at this point.
[Nook Color Android Development] boxcar8028:
Any idea if this HCv4 SD work around can help people with SOD or the no deep sleep issues?
[Nook Color Android Development] Ronin3178:
Possible way to avoid PBD

Found an app "Battery Monitor Widget" by 3c06, it looks REALLY promising. Has widget that can have voltage in mV, estimated time remaining, graphing of voltage/aH/mW etc. You can also set high/low alarms for voltage and a LOT more. Just put it in, so I will let you all know how it works, but like I said, it looks really promising.
[Nook Color Android Development] jekagan:
Completely understood. Having the additional circumstantial evidence may help establish a pattern and/or point toward the root cause if it proves too difficult to ascertain anything via a debugger.
[Nook Color Android Development] xKLoWNx:
No PBD and No Early Shut Down.

I Flashed the nightly 87 and am not having an issues its running smooth. I also did the netflix fix and it also runs smooth.

I want to share what I did before I flashed this rom maybe it will help with the prob or may not, so I will just give it a shot.

I was running Nookie Comb and I wanted to switch to CM7 Nightly 87. So what I did was Did the back to stock through The Unlockr website followed all the steps on the stock load and put my wireless in and registered, then immediately shut the nook off, (so it would not get the OTA update.) Then I did the autonooter on The Unlockr page (I did the Autonooter for 1.0.1 thats what the back to stock brings it back to is 1.0.1) I followed the steps for Autonooter, then downloaded Rom manager and flashed CWM and once that was done I booted right away into recovery. ( I was trying to work fast so it wouldn't happen to get the OTA update) Once I was in recovery, I put my sdcard in that i already had setup with these instructions. http://xdaforums.com/show...0&postcount=19 I followed the instructions flashed what it said to and that was it. I didn't add another Kernel or anything else. I flashed just what it said. ("11. Flash from .zip the uBoot.zip, cm7 zip and the google apps zip".)

I am running the CPUspy and lastnight when I went to bed I reset the counter and hit the power button for screen off, when I woke up and checked the CPUspy it was in deep sleep for 12 hours and the battery never moved from the % it was at when I put it to sleep.

I really hope this helps in some way. If you have any further questions with The Unlockr steps or the netflix steps I did Let me know.

Links:

Back to Stock The Unlockr

http://theunlockr.com/2011/02/14/how...olor-to-stock/

AutoNooter From The Unlockr

http://theunlockr.com/2011/02/05/how...nooter-method/

Nook Color CM7 install instructions

http://xdaforums.com/show...0&postcount=19

Edit: Even just turning down the screen brightness 2% to 5% really helps in conserving battery life. And you cant even tell you turned it down really.
[Nook Color Android Development] xKLoWNx:
I used this app with my phone the pro version. It seems to run battery down pretty fast when you are using widget graphs, but it is very awesome app on keeping an eye on what your battery is doing. Good Luck!
[Nook Color Android Development] seth.i.simmons:
TEST CONFIGURATION:

BOOT DEVICE: eMMC

MLO: MLO installed by CM7 >N86

U-BOOT: U-Boot installed by CM7 >N86

KERNEL: Dalingrin's 052311 OC Kernel

OVERCLOCKED?: to 1200Mhz

GOVERNOR: Conservative

SYSTEM: CM7 Nightly 87

PBD: Yes

TEST COUNT: 3x- once with Beta 3.1 (Died at 18%), once with N86 (Died at less than 15%, ~10%), and once with N87 (Died at 18% again)

TRIED REVERTING TO OLDER HC/CM7: Yes, when I got the PBD with Beta 3.1

TRIED WIPING CACHE/DATA?: Yes, wiped everything.

DID IT WORK? Somewhat, got down to less than 15%

PREVIOUSLY INSTALLED:

☐ Stock 1.0

☐ Stock 1.1

☑ Stock 1.2

☐ Nookie Froyo (any)

☑ Honeycomb (any)

☑ CM7 2.29 (any)

☑ CM7 2.32 beta 3

☑ CM7 nightlies > 84 (or whenever .32 appeared)

NOTES: Got a PBD at 18% on Beta 3.1 (with Dal's 051311 kernel), so I wiped completely except /boot, and reinstalled BN 1.2 (keep CWM version) but had to use a bootable CWM sd card, when for some reason I couldnt get into recovery. I then wiped completely again, and installed N86, with Dalingrin's 052311 kernel. That's when I got down below 15%. I then installed N87, and ran it down again today, while using Battery Monitor Widget to keep track of mV and %. In the log kept by BMW, it died at 18% and 3015mV. Here are some pics of the battery info after I started it up again.

http://dl.dropbox.com/u/30528238/snap20110527_212142.jpg

http://dl.dropbox.com/u/30528238/snap20110527_212223.jpg
[Nook Color Android Development] jtbnet:
THAT was my suspicion too based on published specs...

HAS anyone else tried just deleting /data/system/batterystats.bin and rebooting and let it re-learn this info... I did as thought I remembered similar on other devices and it seems my nook works just fine with notify at %15 and off is low single digits... but one try when not sure I ever had a problem does not constitute a fix!
[Nook Color Android Development] fattire:
Results thusfar....

Could someone check my work?

I filled out the appropriate box for people if someone wasn't sure, but I was (ie, they said "whatever MLO comes with cm7 > 86... that would be a built one from the BN 1.2 source...)

Not a huge number of submissions, but I do notice some things...

There does not seem to be any correlation w/built mlo or u-boot.

There doesn't seem to be a dependency on governor or even system..

Everyone who experienced PBD was using some kind of OC.

However, not everyone who used some kind of OC experienced PBD

All PBD but one involved the 5/23 OC

My PBD went away when I installed nightly 86, which replaced my OC kernel with cm7's non-OC'd one.

There aren't enough data points here to really conclude anything for sure, but I'm seeing some sort of rough trends, especially correlating with the o/c kernel.

mutant13 is the most interesting to me-- because he had PBD on stock BN 1.2 everything-- with the only wildcard being that he replaced the kernel with an o/c kernel. That's pretty damning. The thing is- he says he used the 5/13 kernel, not the 5/23. mutant13, can you confirm that it was the 5/13 OC and not the 5/23 OC?

5/13's OC had a LOT of checkins on 5/22 and 5/23 and I wonder if any of them messed with the battery reporting?

Anyway, this is just a working theory and could be entirely wrong and blown away by more evidence (or people pointing out that I screwed something up)-- but if you're having the problem still, or even if your'e not, please continue to fill out the form as it's helpful!

One final note-- some people reported running the regular cm7 kernel faster than it should be able to be run... but I erred on the side of the kernel version and not the max speed reported...

Also-- for those who said you "fixed" the problem by running HC or something else for a while, then reflashing cm7, did you ALSO re-flash the o/c kernel? And then did it still fix it w/the o/c kernel?

Enquiring minds want to know.

Incidentally, I initially patched BFS into the OC kernel and was pushing dalingrin to go for it... but now I'm starting to think some people are right that maybe it's not such a good idea.

Anyway, could those who were having the issue try charging up to full with the non-OC kernel and see if it still occurs? That would go a long way to establishing if there's a correlation.

Update: Noticed that some people claim to be running at speeds like 1200 which aren't supported by the nightly cm7s... Weird.
[Nook Color Android Development] joenathane:
Great reporting and work so far...

I have been able to run my nook down past 7% before throwing it on the charger twice now with no PBD after running HC off SD for an hour or two and having changed nothing before or after with my CM7 install.... strange, I know.

I have been running nightly 85 with the 5/23 OC @ 1200mhz
[Nook Color Android Development] fattire:
When you use HC, it's switching to 2.6.29... so it is-- if my theory is right-- another way of saying "I stopped using .32 (OC?) for a while..." Maybe it was resetting the battery level somehow?

Maybe it's some kind of a drift in the level reporting? something miscalculating so it reports as higher than it really is, with the discrepancy growing over time? Maybe switching to a .29 or non-oc kernel will return it back to normal only to have it drift again..

more talking out of my ass tho...