yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] greenmky:
I went from stock 1.2 -> CM7.0.2 stable -> CM nightly 87

BOOT DEVICE: eMMC

MLO: ?

U-BOOT: stock B&N 1.2 (I think? unless nightly 87 messed with it?)

KERNEL: .32

OVERCLOCKED?: to 1.1

GOVERNOR: Conservative

SYSTEM: CM7 Nightly 87 / OC Kernel 5/23

TEST COUNT: 1x

PBD: Died at under 4%. I don't think that counts, frankly - so I would so no problem here. I didn't see any funky percentage jumps either.
[Nook Color Android Development] skwalas:
Fattire, in the 1.2 update zip, there's a separate sub-zip labeled "charger". The updater script for that particular zip has a series of flags (0, 1, and 10) that appear to direct how the update will work based on the battery level when starting the update. Now, I've seen those flags elsewhere in the larger update zip and use in ways that don't appear to relate to installing the update directly. So, I am wondering if there is some call to a procedure that has been missed when isolating the uboot and mlo? Something that requires those flags to properly initiate certain activities when the battery hits milestones like 15%? But don't work properly if the flags or calls or whatever are absent?
[Nook Color Android Development] Gin1212:
I have never received PBD (don't get excited) because I've never let my battery hit under 30% because of all of the reports.

However, last night for the first time ever, I couldn't be bother to get out the adapter for the usb cable, so I just let the computer charge it all night.

Well, I'm a Sub. Teacher and I find on certain days I have a lot of time to read books, so I turn off the wifi and lower the display brightness and get excellent battery. There are days that I spend just reading (8hrs), and I get only as low as 60-80% depending on how heavy I really get to read or if I'm reading something like manga.

Today however, I subbed for a Kindergarten class that did not let me read pretty much at all and by the end of the day I only had like 55% battery with 3 of the 8hrs being heavy reading of a pdf. (The other 5hrs the Nook wasn't even turned on for a second.)

What's my point? I barely touched my nook, and yet had 55% battery by the end of the day with very low display brightness and no wifi. No games were played, and I really only used Adobe Reader and Ezpdf reader.

Hell, I had a Snesoid/Gbaoid day the other day (almost all day because the kids had a field day and I was left with a small group of kids doing independent work) and still only hit 55-60% by the end of that day.

So just my thoughts on "Usb Charging" over the Wall socket charging.

Edit: My settings are N86 OC (5-23) (300/1200 Conservative)

Edit 2: I am now seeing reports of heavy battery usage issues in the CM7 Dev thread, so it may be even possible that it's just using up a ridiculous amount of battery as well... However, that seemed like quite a bit for only 3hrs of real use.
[Nook Color Android Development] skwalas:
Well I'll be damned. It is for sure a calibration issue. Somebody Googled these batteries and read that they could not go below 3050 mv safely. I got pbd repeatedly just a few minutes ago at 20%... and 3000 mv.

Put the charger in and juiced it up a couple percent (showed 3600mv with charger in), unplugged, and let it run down again. Shutoff at 20% and 3000mv. I was able to replicate this multiple times. I already know that my 100% of scale is always right around 4200mv so it seems as if the 0% of scale is out of alignment.

How to recal the 0%?
[Nook Color Android Development] keyodi:
PBD REPORT FORM

TEST CONFIGURATION:

BOOT DEVICE: eMMC

MLO: BN 1.2 built by fattire (MD5: a2c9a23efdbe05a40e0066500c5cfea1)

U-BOOT: BN 1.2 cyan build by fattire (MD5: c3db4062d1e67d50a382245471c1cef8)

KERNEL: uImage 2.6.32.9 from OC 5/23

OVERCLOCKED?: to 1200

GOVERNOR: Conservative

SYSTEM: CM7 Nightly 86

PBD: NO

TEST COUNT: 2x- once with "untimely" u-boot and once with "cyan". Each time nc shut off at ~4%

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)

NOTES: I have dualboot setup on my nook with stock 1.2 installed on parts 9/10. Installation steps: Formatted /system(ext2), /data(ext2) and /cache, Installed stock 1.0.1 then updated to 1.2, setup dualboot partitions, moved 1.2 to dual boot parts, formatted /system(ext4), /data(ext4) and /cache, then restored CM from backup. I often switch between CM7 and 1.2.
[Nook Color Android Development] I Am Marino:
BOOT DEVICE: eMMC

MLO: ?

U-BOOT: Whatever came with N87

KERNEL: 2.6.32.9 OC 5/23

OVERCLOCKED?: 1200

GOVERNOR: Conservative

SYSTEM: CM7 N87

PBD: No

TEST COUNT: 1x

TRIED REVERTING TO OLDER HC/CM7: No

TRIED WIPING CACHE/DATA?: No

DID IT WORK? N/A

PREVIOUSLY INSTALLED:

CM 7.0.3 Stable.

Stock 1.1

EDIT + NOTES: Battery finally died at 4%. I went near or below 3,000mv when it happened.

I had 13% with 3606mv. Voltage started free falling once I hit under 5% battery, I watched it go from around 3400 to 3060 all within the 4% range, right before it died, was trying to screencap when it died on me. I was a little over 12 hours off charger, I took it off at 96%-ish.

It seems 3000 to 3050mv is that cutoff point.
[Nook Color Android Development] Narfx:
Yep, my pbd happened at ~3-3.2V. Seeing as some people are reporting only ~10%-20% at ~3.6V, seems like our batteries were SEVERELY depleted. I hope they were not damaged because of that :/

I'm letting it run down now. Will post my u-boot, MLO et al. when/if it reaches 3.3V.
[Nook Color Android Development] I Am Marino:
I think it would help if people starting finding our their voltages when or near their battery dies. Seems to be a pattern developing.
[Nook Color Android Development] Animec:
This is odd, my 100% is now right around 4000 mV and I know for sure it's been closer to 4200 before :/
[Nook Color Android Development] sinanju:
I have noticed that the meter will read 100% a while before the "n" light on the cable will go green, further pointing to a calibration issue. Perhaps that's your case?
[Nook Color Android Development] Ronin3178:
Here ya go, I got down to 4%, went to plug it in, and it shut down right before I got there. I got a screenshot of the 3041mV I believe. When my Nook comes back on (showing the charge screen right now) I will upload the shots.

Here is the datapoints I got 18-4%

18% 3568

17% 3573, 3566

16% 3563

15% 3538

14% 3562

13% 3557

12% 3565

11% 3505

10% 3508

9% 3501

8% 3499,3490

7% 3482,3475

6% 3390,3382,3356,3336,3321,3302

5% 3279,3256,3232,3198,3158,3123,3101

4% 3101,3041

A majority of this was sitting at battery booster screen watching at full brightness and with screen timeout set to never, so the cpu was pretty much idle.
[Nook Color Android Development] derekr:
It's real scary (and it's not Halloween!) I just finished a battery discharge test where I monitored the voltage and percentage as the battery was used up. The plot as a pdf is below:

http://dl.dropbox.com/u/22355237/NookBattery.pdf

Look at the rapid drop-off in voltage below 40% to 2860 mV at an indicated 34%. No wonder we are seeing PBD if others have the same problem!

I was watching the voltage drop before my eyes. I actually shut it down at the 2860 mV, and I can't turn it on again (I'm at work) - no charger.

Something is very wrong with the calibration... At an indicated 34% the battery is dead, deceased, gonzo, perished, pushing up daisies......

Edit: n87 - OC523 - data taken with Circle Battery widget.

If you can't see the plot - here's the data:

86	3917

84	3886

79	3839

76	3795

70	3758

67	3751

58	3696

46	3639

40	3604

37	3556

35	3503

34	3271

34	3172

34	2861
[Nook Color Android Development] Ronin3178:
If you look at my post above yours, yeah, def a calibration issue, mine dropped out @ 4% 3041mV

ps, I would switch axis on the graph 0-100% bottom to top, 4000mV to 2400mV left to right
[Nook Color Android Development] derekr:
As you wish :D :

http://dl.dropbox.com/u/22355237/NookBattery2.pdf

however, let's discuss this over a beer sometime - which is the independent variable here? I think the first plot shows the precipitous voltage drop-off in a more graphic fashion... But, as always, your wish is my command :D

BTW - MATLAB won't let me (simply) reverse the x-axis order...
[Nook Color Android Development] xxiworld:
Given the PBD happens when apparent battery percentage is much higher than the actual battery level, wouldn't we see the reverse?
[Nook Color Android Development] sinanju:
Based on experience and some logs I posted, I posited that some percentage (small or big, I don't know) of SODs were actually the device taking an extremely long time to wake -- more than long enough to think it was dead -- due to trouble with WiFi/WiFi Sleep Policy. Did you see that posting? If so, what did you think?

I thought I had been experiencing SODs until I noticed that their occurrence was almost directly correlated to whether I relied on the sleep policy to shut off WiFi vs shutting it off before turning the screen off. Once I figured that out, I tried turning the device on and, if it failed to wake, simply left it alone. The longest I waited was ~5 minutes, but I'd wager it could take longer. The impatient might give it less time before deciding it was dead. Turning off WiFi explicitly makes the problem -- for me, at least -- go away.
[Nook Color Android Development] dalingrin:
I agree, if there is an issue its likely delayed wake. Unfortunately, I have tried making the WiFi never sleep, sleep when screen is off and explicitly turning off WiFi and none of these produce delayed wakes or SODs for me. If there is an issue I believe its something with the MMC controller(the WiFi is an SDIO device).

My plan is to see what happens after the next nightly with the battery calibration fix. If there are still reports of SODs then we are going to have to get very detailed reports from everybody and go from there.
[Nook Color Android Development] helderp:
I'm having a premature battery death on the stock 1.2 + root. It shuts down at around 17%. I updated from 1.0 to 1.2. I know this post is about CM7, but this is just to let you know. I don't know if anyone else experienced this specific situation.
[Nook Color Android Development] 12paq:
A nice update, thanks. By no means are you even required to do so, so thanks.

Also, the "...very detailed reports from everybody.." is a darn good thing.

Perhaps some sort of basic template or requirements for reporting?

Maybe as simple as list?

Just so those who are not devs can disseminated the correct information, with all the variables reported, so those whom do know more can diagnosis and troubleshoot easier.
[Nook Color Android Development] BitingChaos:
When will there ever be a new nightly? I heard there was hardware issues on the build server, and a "nightly" build hasn't come out in over a week now.
[Nook Color Android Development] :
Really? Like the template this thread started with and people stopped following?
[Nook Color Android Development] 12paq:
Yes.

You read between the lines well.

:)
[Nook Color Android Development] :
Hehe, sorry, sometimes I forget to look at the user and just assume they're someone who shouldn't be on here :)

I'm getting to know the real players on here pretty well....Muhahahaaaa
[Nook Color Android Development] 12paq:
No worries.

I prefer the shadows.. :)
[Nook Color Android Development] pryonix:
Agree completely. I can more or less reproduce SOD (given a few hours) with wifi on/screen off policy, AND having the nook in a wifi area. So far, no SODs with wifi off when screen off. Still experiencing screwy battery level reports though.

Ever since I started following this thread, I've also been randomly checking every now and then what the battery level is as BN stock 1.2 reports it. There really is a discrepancy sometimes as large as 10%.

When charing my Nook under CM7, I wait for my charger light to turn green as it would frequently say 100% but the charger light is still orange. I figured the charger knows the batt percentage better than CM7 does >.<
[Nook Color Android Development] :
So a "fix" was just merged...but after reading about 1.2'ers, I'm curious:

Does the 1.2 not have the battery being read either? Since we grabbed a lot of code from it, I could see that...
[Nook Color Android Development] xc68000:
Will the battery stats fix require a reload of 1.2 or the HC boot fix to generate "good stats" before it will work, or will just flashing the next nightly resolve the issue? Thx
[Nook Color Android Development] RussianMenace:
Nice that there is finally a fix, however, what sucks is that a nightly hasn't been compiled in almost a week.
[Nook Color Android Development] :
It'll just work. Basically writes to a battery file that has not been written to it seems...
[Nook Color Android Development] xc68000:
Well, back on post #150 verygreen stated that if you start with bad data just copying the file won't work, so thats why I was asking the question.

http://xdaforums.com/showpost.php?p=14314569&postcount=150
[Nook Color Android Development] :
Ugh.

Glad you read what I wrote :)

Apparently write now = copy.

Please read the rest of the thread. You may understand it then.
[Nook Color Android Development] BitingChaos:
We may be in luck. The buildbot thing apparently is working now, as several June 4th builds (for other devices) have started showing up. A Nook Color build may show up today or tomorrow.
[Nook Color Android Development] paleh0rse:
ok, here's what I did...

I flashed the new private build Nburnes posted in the CM7 General Discussion thread that is supposed to include all of the latest commits... cleared cache and Dalvik... and was sitting at 30% battery after reboot. I did NOT re-install any OC. Instead, I just booted and set it to 925mhz/ondemand.

I began to run down the battery (Watching Archer, season 2! :))... received the proper warning at 15%... BUT, then experienced yet another hard PBD at 8% -- NOT the "graceful shutdown" at <1% that one should expect from the stock Android shutdown code. :(

I'm not exactly sure how the new "battery fix" is supposed to work, but it certainly didn't work after a simple flash over n87.

While this certainly doesn't prove that n88 will behave the same way, it doesn't bode well for our PBD woes.

I will recharge to 100%, re-calibrate, and test it again. Hopefully n88 becomes available soon so we can all do some proper beta testing...
[Nook Color Android Development] frankusb:
Keep in mind, the update will write the battery stats to a file hourly. The file is only read on boot by U-boot. It may take a few calibration cycles before things become closer to correct.

And FWIW, I'm fairly certain that my 1.1 auto nootered Nook shutdown at 9% or so abruptly so this problem might be a hard one to finally resolve.

Frank
[Nook Color Android Development] pryonix:
hi,

can anyone confirm if the latest nightly fixed pbd/sod?
[Nook Color Android Development] :
As stated earlier, it will take a few cycles for the OS to calibrate the battery.

I've never had SOD. No idea if people actually mean that or PBD. But they're trying all the tricks people say to disable SOD (remove screen on animation, etc).
[Nook Color Android Development] mtutick:
I had PBD a few times around 18% on nightly 86. I upgraded to nightly 91 with OC kernel yesterday and ran it from full charge down to about 30%. Today I upgraded to nightly 93 (did not update to dal's OC kernel) and ran the battery down the rest of the way. I received the warning at 15%, and then at 1/0%, I got the tidy android shutdown. So for me, it looks good.

I've only had SOD once or twice ever, so it's hard for me to comment on that.
[Nook Color Android Development] chisleu:
n91 + OC kernel

System sleeping wonderfully. No PBDs yet.

I ran it down to 50% watching videos for 2+ hours

Charged up to 100%

Light use, off charger all day today - only used 14% life!!! :)

Not going to charge it until it runs out of battery (PBD or graceful, either way)
[Nook Color Android Development] :
Was getting down to around 4% previously. Now running 91 and ran it down to 5% (where it shutoff without warning). Fully charged and will see if it gets any closer this cycle :) I want that nice shutoff! :P
[Nook Color Android Development] clamder:
I'm on nightly 93 with oc. I had pbd at around 30% before. Today, I let it drain til about 9% before it auto shut. I charged it to 20, unplugged it again until about 14, and plugged it in again. At that point, it auto rebooted, but booted in just fine. Just thought that behavior was strange. Pretty happy with 9%!
[Nook Color Android Development] paleh0rse:
My N91 first drain had PBD at 8%. My latest drain on n93 gave me PBD at 6%... so I'm now charged back to 100% and hope to see it get even closer this time. One of these days, I hope I can return to the ever-elusive "graceful shutdown" at <1%... wish me luck! :)
[Nook Color Android Development] bonobomidwest:
Not for me. I installed 91 over 7.0.3. I had The same hybrid problem as before (faster aparrent drain and then something that looked like SOD but which required a power plug to restart).

Also had the same fun as several other people with the new CWM causing bootloops galore
[Nook Color Android Development] khaytsus:
CWM is not executed at all unless you have your u-boot do it. Therefore, CWM being perfect, broken, or missing would not cause boot loops in CM7.
[Nook Color Android Development] ovar:
N93 Dalin's 5/23 Kernel OC 1200.

PBD seems to be fixed with N93. I got the low batter warning at 15%, and then I got a graceful OS shutdown at 0-1%. Charged up to around 95% ( I pull my devices off the charge before they hit 100%, was only able to charge to around 84% before)

Thanks for the fix!
[Nook Color Android Development] BitingChaos:
I'm using nightly 91 and I just got a low battery alarm.

I'm at 12% now and still working fine. No sudden shutdowns at 30-40% like before!

Is the"update stats every hour" the permanent fix? How does B&N stock do it? How do other devices do it?
[Nook Color Android Development] bonobomidwest:
Unless of course you install the vanilla update, ensure stability etc, before booting into CWM to install OC... or after the first time you've had to reflash your backup you play it super safe and wipe data, cache, and system and have to boot into CWM to flash gapps.

Check out the number of folks over in the user thread who had a similar experience yesterday. Also the CWM thread and the OP discuss the issue. Nemith as was super responsive and had a fix posted by the end of the day... another wonderful Dev :)
[Nook Color Android Development] BitingChaos:
Well, my Nook Color shut down at 11%. Still better than before.

Do I need to condition the battery a few times for it to learn the battery levels correctly?

- Sent from my Nook Color.
[Nook Color Android Development] tiffanydawnn:
I got the warning at 15% and powering off notice/shutdown at 1%. I wiped battery stats right after my first charge to 100% after flashing. I'm on 94 with the 0523 OC kernel. Also no deep sleep issues and no SOD. Previously, I would shut down at 20-30%. Thanks for fixing this!
[Nook Color Android Development] :
Forgive my ignorance but should that max**** file have an updated date? In root explorer it does not seem to be written to (I see the script being called in the init file, but the modified date isn't being changed in R.E.).

Getting 5% consistently (second full drain from 100%).
[Nook Color Android Development] yozh:
I`m not sure if I have the same issue, but it kind of sounds like it. Let me explain. I had my nook color since May 24th, first thing I did was update to 1.2 and flash to CM7 and right away flash to CM7 nightly 87, with 5/23 OC kernel. Things were great, battery was perfect it would last me 2 days with out recharge and a lot of use. I would take it of the charger before going to sleep with 100% wake up and it would still be at 100% or 99%. It was great. This Saturday night after playing around with it, I went to sleep with approximately 40%-50% and in the morning it was dead. I charged it to 100% flashed 93 nightly on it, left it over night with approximately 70%-80% charged, woke up with 44%. Yesterday I charged it to 97% used it a bit, it went to approximately 75-80%, this morning wake up to 57% battery.

Almost seems that if it gets left idle for a while it looses 30% of the battery some how. Do you guys think its the same issue as the PBD ? Or do is it something else ? What can I try to fix it ? Maybe my battery is going bad ?

Thanks in advance.,

EDIT: Also the battery use shows Android OS as 41% use (This morning anyway) I saw yesterday the same. After removing from the charger it doesnt show such high usage by the OS. I guess I have to try not a nightly ROM to see if it works better, unless some one has a better suggestion. I just dont understand why it was working so great before....
[Nook Color Android Development] chrisjs81:
Really now? That sounds nothing like PBD--where the nook shuts off hard when the battery still reads as having a good charge.

Sounds like your nook isn't sleeping for whatever reason.
[Nook Color Android Development] yozh:
This is what I was thinking, but I was reffered to this thread when posted. I guess I have to dig deeper any clues?
[Nook Color Android Development] khaytsus:
Spare Parts is one place to look to see if anything is holding a wakelock or other things using significant CPU.

If you're using Beautiful Widgets you might remove the Widgets for a while and see what happens. If not, maybe try other widgets.
[Nook Color Android Development] paleh0rse:
Update: my last drain on n94 (no OC kernel) got me down to 5%, so I'm getting there I guess... baby steps...
[Nook Color Android Development] skwalas:
Ditto here. Finally hit 3% last night on 94. What was weird was the last few % seemed to really drag out, almost as if the %-age was trying to match up with the voltage...
[Nook Color Android Development] yozh:
Thanks for the tip, no Beautiful Widgets here.... I`ll start working with Spare parts. I just updated to the last nightly. Hopefully it`ll fix. If not I guess, full format for /system /data is due. I will go back to my other thread to work on this. Thanks
[Nook Color Android Development] seth.i.simmons:
FINALLY!!! Got a graceful shutdown for the first time at less than 1% today. This is on N95 with the 052311 kernel and VG's USB Host kernel... I had been switching back and forth all day between the two to try out USB host, and it died on dal's kernel at 0%, with the "shutting down" message. So, thanks for the fix fattire!
[Nook Color Android Development] yozh:
What was your fix ?
[Nook Color Android Development] seth.i.simmons:
The fix incorporated by fattire into the latest nightlies I suppose. Didn't do anything special, besides switching back and forth between dal's and VGs kernels. Working great now!
[Nook Color Android Development] TJNooker:
My first drain on n95 got me down to 5% as well, but 5% has been my limit since n87. We'll see what happens next drain.

EDIT: On my second drain it shutdown at 5% again. :\
[Nook Color Android Development] gudism:
PBD dead?

so has PBD been fixed in nightlys?

because I am still having them, and have so on n95,101,108 & now 112......all at the 14% mark.

Is there a fix I can do that I havent read?
[Nook Color Android Development] liqn7:
Have you tried calibrating your battery?
[Nook Color Android Development] I Am Marino:
I don't believe there's any fix, more or like most people having the issue have already said something or just living with it for now.
[Nook Color Android Development] gudism:
No I haven't. Care to refresh my memory about how to do that? Read about it sometime ago but can't recall.

I do wipe my battery stats after flashing to a new nightly though and flash fully charged.
[Nook Color Android Development] gudism:
Ah ok. I mean it isn't much of a drama.....you just know that in reality you are only charging to about 85% capacity (if PBD occurs at 15%)