yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] just4747:
On Nightly build 86 and 87 I have been getting constant freezing when turning screen off. Screen will stay off no matter which button I press...this is happening almost every time I use my Nook for more than 5 minutes and I turn off the screen/screen falls asleep. Very very annoying. For 86 I had wiped and flashed, but for 87 I just installed over through ROM Manager.

When this happens, I wait a few minutes and with no luck I just have to hard reboot by holding down power.

Why is this still happening?

Did they remove the permissions options in 87??
[Nook Color Android Development] I Am Marino:
The permission options are still there, I remember seeing them, just don't remember where. Sorry about that.

and as for your problem, it happened to me once, turned screen off, and was frozen, hasn't done it again since though, *knock on wood*
[Nook Color Android Development] just4747:
Also my Wifi Sleep Policy had been set to When Screen Turns Off. I just changed it to Never.

Found the permissions settings under Application Settings in CM Settings, sorry.
[Nook Color Android Development] TheMainCat:
I agree that the the previous OC seemed to sleep just fine. I may switch back to it to confirm.
[Nook Color Android Development] TheMainCat:
Yup. The 05132011 OC will trigger the "deep sleep" (at least it shows up as used in CPUSpy), whereas the 05232011 OC doesn't. Why that is...no idea (not that smart of a fella :D). Just thought to pass on what I noticed
[Nook Color Android Development] paleh0rse:
Nice! Looks good so far... any chance you could make the graphic for "cyanogen" in the cyan color as well? Maybe have different versions for different colors? lol

Seriously though, nice work... thank you!
[Nook Color Android Development] fattire:
Well I'm no artist. That was drakknar's amazing work. You can either ask him to do it, or if you're good with graphics, give it a shot :)
[Nook Color Android Development] :
Flashable zip with fattire's newest uboot. Backups the old one.

...Because I know a million people will ask for it :)
[Nook Color Android Development] I Am Marino:
I'm on the 05232011 OC at 1200 and N87 and according to cpuspy, my NC is able to go into deep sleep, although not constantly.
[Nook Color Android Development] ansleyj44:
05232011 works for me 99% of the time, just occasionally it doesn't. I'm trying to recreate it so i can narrow it down or something.
[Nook Color Android Development] TheMainCat:
The 05232011 doesn't seem to want to do it for me. I went back to after my last post (just to make sure I wasn't seeing things) and had my Nook's screen off for 15min. Checked CPUspy and "deep sleep" was listed as unused. Running N87, 1200Mhz - Concervative (like everyone I think). Not sure what I am missing here.
[Nook Color Android Development] I Am Marino:
Well mine is refusing to go back into deep sleep now.

I just charged battery to 100% and then turned the screen off and on and back off a few times for a few seconds at a time and that's when I got the deep sleep in cpuspy, haven't gotten it since.

EDIT: At 90% battery now, turned screen back off for like 2-3 minutes, it registered about a minute or so of that time as deep sleep, the rest at like 600mHz.

I don't get it.
[Nook Color Android Development] :
Yeah, I have weirdness w/sleep as well. Sometimes rebooting fixes it, sometimes it kills sleep. The only thing I can find that has a direct link to how much it sleeps in weather or not wifi is on when I turn off the NC. 5/13 was great. Now 5/23 semi-borked it?
[Nook Color Android Development] biz18434:
Yes, I believe I am using-the-wrong-kernel. That is my problem with my HC sd card. I figured that out when I was able to boot using my CM7 Card. I will stop playing with my HC sd card and I will start using my CM7 sd card. Thank You for this u-boot.bin on my CM7 sd card it works great.
[Nook Color Android Development] I Am Marino:
Just got another 15 mins straight of deep sleep so it seems overall like it's a deep sleep when it wants to kind of thing.
[Nook Color Android Development] fattire:
This is from last night. I was able to let it go all the way down to 2% before it stopped and gave me the u-boot "plug it in" image (after getting a pop up warning at 15%). I truly don't think the 1.2 u-boot is the cause of this. I used the "untimely" one + the 1.2 MLO I built and posted here previously plus the stock .32 kernel (not OC)... I have now been able to run out the battery at least 2x (out of 2 that I've tried) without any problem.

The Premature Battery Death seems to me to be something else... some bad reporting of the actual battery level... but I really know nothing about power management, so maybe someone else will know more.
[Nook Color Android Development] fattire:
This is the best kind of bug- one where I don't have to fix anything :)

Thanks for reporting back!
[Nook Color Android Development] jekagan:
I am seeing this EXACT behavior as well, right down to the same battery percentage. I read through the prior posts but couldn't find the answer. What's the underlying issue?
[Nook Color Android Development] newellj79:
Liking the cyan menu.
[Nook Color Android Development] searius:
I just wake up now and after 8 hours I check cpyspy and 95% of the time the Nook was in Deep Sleep.It remains to 99%.The same % I left before I went to sleep.

I use CM7 n86 and latest OC from Dalingrin.:D
[Nook Color Android Development] boogerboy72:
what were you on before you flashed 86? did you do a full wipe or anything else?
[Nook Color Android Development] seth.i.simmons:
Just let mine sleep with the wifi turned off overnight, and it slept great for 8+ he's with no battery loss. Not are what's up with everyone else, mine seems to sleep fine. I'm on n87 and the 052311 kernel.
[Nook Color Android Development] rhester72:
Too late, obviously, but maybe "Menu|Power toggles selection" would be better, since | is geek for "or"? :)

Rodney
[Nook Color Android Development] sinanju:
Bad news on PBD

I triggered a PBD this morning while capturing logs over WiFi... There was absolutely nothing interesting in the log just as it died. I was in Opera and the last message was common keyboard message.
[Nook Color Android Development] frankusb:
Could the PBD be related to how the Nook is charged? I've noticed that charging via USB results in the percentage increasing faster than it should, time-wise. While charging with the AC adapter seems to take longer to move the same percentage even though it's capable of providing more current.

I haven't checked the mV methodically to back this up as I don't charge via USB often.

Frank
[Nook Color Android Development] just4747:
As I said my Nook has been "sleeping" no matter what I press multiple times since I flashed the last two Nightlies, just downloaded and checked the CPU Spy app, it says Deep Sleep is 37% at 4:33:45, 300MHz is 2%, 600 MHz is 58% of the time, 800 MHz is 0%, and 925 MHz (max I have CPU set to in settings) is 2% of the time.

Does this help with anything?

Sometimes I will turn the screen off for two seconds after doing nothing special on the Nook at all, and it just won't wake up until I come back minutes later and try again. This is so frustrating it's unbelievable. How can this be fixed? Is it the OCS kernel?? I don't even know which one I have right now or if I ever flashed a different one than what CM had.
[Nook Color Android Development] Narfx:
Nope, I always charge using the AC adapter and my battery dies at 20 something percent (~3200mV, IIRC). Started happening when I updated to u-boot 1.2. Updating to 1.2 MLO (as well as all the other mmcblk0p1 files from 1.2) afterwards didn't solve it. Neither did cycling the battery, resetting the stats from recovery, etc.
[Nook Color Android Development] paleh0rse:
Same here -- even after a total wipe and stock 1.2 install. (Although mine makes it to 15-17% before shutting down).
[Nook Color Android Development] :
I love your work fattire, but I think IT IS the 1.2 bootloader. I ran 1.1 all the way down AND it gave me a shutting down warning (all on beta). Then I updated just the bootloader to 1.2, and had a PBD (at 30%). Then I installed full stock 1.2, let the battery drain until shutdown, then reflashed a fresh beta. Now the battery gets down to 3%, but still shutsdown with no warning.

That seemed to be the only thing that changed. But that's just me :)
[Nook Color Android Development] Ronin3178:
I posted this in General, but thought I should put up here too :

Now I did get a warning to connect charger @ 15%, that is your one/only warning. I have seen this on my OG Droid too, a 15% warning, nothing else, eventually the phone just shuts off.

Now the PBD is if you get a hard shutdown PRIOR (generally in the 2x%-3x% range) to the 15% warning, right?
[Nook Color Android Development] paleh0rse:
Right. However, the range is more like 15-35% (mine currently happens at 15-17%).
[Nook Color Android Development] junkrobot:
I've been able to get my battery down to 15% or lower since I started over from 1.2 stock with nightly 85 and the 5/23 OC kernel, but I still have some weird calibration issues such as the green light coming on at 98%, etc. I tried wiping stats at 100% to see if it helped, but it hasn't so far. I'm going to try to run it down to 0% today, but I'm a little nervous it might start PBD-ing on me again since I wiped the stats.
[Nook Color Android Development] joenathane:
A little while back someone said they were able to cure their PBD by running HoneyComb off the SD for a while.

I tried and it worked for me. I have absolutely no clue how that could work or have any effect, but previously my nook would turn off around the 30% mark or so and now I got the warning @ 15% and ran it down to 7% before just throwing it on the charger....

I know there is no magic to this, there has to be an explanation...
[Nook Color Android Development] junkrobot:
Truly, the whole thing is confounding. I was fine doing a clean install since I hadn't in between using 1.1 and 1.2, but I really am not anxious to have to do that every single time I flash a new nightly in the hopes that maybe the PBD issues will be okay. I'm not bashing anyone's work, obviously, as I think this is all fantastic. I'm more astounded that between all the knowledgeable people here, this little issue still seems to be quite elusive to pin down. I'm sure it'll be resolved one way or another, though.
[Nook Color Android Development] capnblackleg:
I asked Ace this last week I think, but I'm sure I'm not the only one who's been out of the loop and curious.

Is there any real reason to come off beta3?

Tons of posts about issues with nightlies, etc. Beta is running fine for me for the very most part, should I hold out?
[Nook Color Android Development] jekagan:
Can anyone confirm that running HC from SD fixes the PBD? If so, which build?
[Nook Color Android Development] I Am Marino:
For that battery graph, for Phone Signal, my bar is fully yellow and my NC got no sleep last night, it sat at 300mHz all night, what's the yellow mean and I'm guessing that's what kept me out of deep sleep?
[Nook Color Android Development] :
Phone signal means nothing. Don't look at it :P
[Nook Color Android Development] abs99:
This is what I'm worried about and why I think the nightlies should not include U-Boot until we fix the issue. Instead we may need to explain the upgrade process to folks so they don't have the battery death issue. This is one of the reasons I haven't been running the nightlies since I resolved my battery calibration problem . . .

Just a thought, is it possible that the partition that holds the u-boot includes one or more hidden files that are being overwritten when Fat Tire's u-boot (or the one included in the nightlies) is being flashed? I'm thinking there must be a calibration file somewhere we are not accounting for in the process.
[Nook Color Android Development] newellj79:
Fattire, forgot to tell u I love the cyan uboot.
[Nook Color Android Development] searius:
befor I was to the stock 1.2.
[Nook Color Android Development] Wipeout:
I was on the uboot included with n87, which I flashed yesterday. This morning I had what appeared to be SOD, had to hold the power button down to power it down, then power it back on. Happened again today at work. I've flashed the stock "Read Forever" 1.2 uboot and will monitor it.

This is the only thing that I can see wrong right now - the deep sleep and everything else is working fantastically; props to the devs for such a pain-free process!
[Nook Color Android Development] xxiworld:
Wow, glad to know I am not crazy and that it worked for someone else. :D

As a workaround, booting into Honeycomb off SD is a LOT easier than flashing stock 1.2 every time.

Maybe it will also give the devs some idea of what the heck is going on! What, if anything, is the common factor between flashing 1.2 stock, and booting up a Honeycomb SD installation???

Now I just need to find where I put my SD card in case flashing fattire's wonderful updated u-boot has brought it back again! I haven't tested it since it worked the first time.

This one:

[ROM][WIP]Divine Madcat's Honeycomb Hybrid RC1 SD v0.2 Image [5/21]

It doesn't hurt to try it and see if we can get a third data point.
[Nook Color Android Development] paleh0rse:
I can assure you that flashing 1.2 stock, by itself, does not always fix the problem -- I did so several times after total wipes, but mine still suffers from PBD on every nightly since 82.
[Nook Color Android Development] iDidItAll4theNookie:
Man, I went out of town last weekend and lost track of the thread due to a title change. I thought maybe it got too long and imploded. I feel kinda dumb, but at least I can install CM7 properly. :o
[Nook Color Android Development] Arbelzapf:
So you just pop in your HC sd card, play around for an hour and then the issue is fixed? I will try that as flashing 1.2 stock did not work for me as well
[Nook Color Android Development] fattire:
Has anyone who suffers from PBD tried wiping cache/data to see if that restarts/resets anything? It's just so weird-- I had it happen once, starting with beta 3. Then I charged it up and now it's fine at least 2x. I am NOT overclocking.

I think we need to do some kind of statistical analysis to see what the requirements are for this to happen. Here's an example. If you can think of additional "fields" to add, go for it.

------------------------------------------------------------------------------------

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 Nightly 86 (MD5: 9192c60a333c6ae32ab100c9eba16dca)

OVERCLOCKED?: to 925

GOVERNOR: On Demand

SYSTEM: CM7 Nightly 86

PBD: NO

TEST COUNT: 2x- once with "untimely" u-boot. Which should be functionally the same. Both did not have BPD

TRIED REVERTING TO OLDER HC/CM7: NO

TRIED WIPING CACHE/DATA?: NO

DID IT WORK? N/A

NOTES: I did have premature-battery death a week ago with the b3 system, the original 1.0 u-boot & MLO (built from BN source), and an overclocked kernel. Can't remember which one. Here is an image of 3% battery from Tues night (5/24/11).

------------------------------------------------------------------------------------

Rather than have everyone spam this list with such reports, I wonder if there is a way to set up a spreadsheet (google docs) or online form (wiki?) or something (a slapped-together db?). That way we can try to figure what the determining factors may be. Clearly though, some people who have switched out U-Boot have had problems that seem to resolve when switching back, and others who have switched out u-boot have not had any problems at all. Could it be some kind of setting, or something in userspace/system clashing? Or a weird interaction with the oc kernel or something?
[Nook Color Android Development] derekr:
To investigate PBD I suggested on the CM7 Discussion. Thread that we record and plot the battery voltage vs battery %. That way we can compare plots to determine whether the battery calibration is the problem or whether it is the voltage that triggers the shutdown.
[Nook Color Android Development] Ronin3178:
Fattire, maybe someone could create a thread, and have everyone post results. Then incorporate into a db all responses and remove posts as they are included. I tried looking around the market but can't find an app that records both % & batt volts, battery graph just records %age, but if all these Nooks aren't calibrated properly then that's almost useless.
[Nook Color Android Development] Animec:
Re. PBD and the effect of booting HC on the SD card... do you see a similar result booting some SD version of CM7?
[Nook Color Android Development] fattire:
Done. Please let's move the discussion over there.
[Nook Color Android Development] boogerboy72:
ill be flashing from phiremod 6.2 this evening, will report with results this weekend. thanks for all the hard work!
[Nook Color Android Development] derekr:
The data fit to my battery discharge test so far has a straight line fit of

v = 10.01x + 3048

where v is voltage in mV, and x is the indicated battery percentage. This is from six data points between 85 -60%. I'm not sure about the linearity of the discharge curve at lower levels - but it is certainly approximately a straight line over this range.

This indicates that the battery is 100% charged at 4.05 V, and 0% at 3.05V - with the 30% nominal PBD voltage at about 3.35 volts.

From Wklipedia on LiPo batteries: a full charge is 4.2 v, and the load MUST be removed before the voltage hits 3.0 v to prevent damage (reduced lifetime). So, we are in the ball park with these numbers.

Has anybody actually recorded the voltage around the PBD? (I'm using the Circle Battery Widget)
[Nook Color Android Development] Ronin3178:
Here is my post from a while (#2455 this thread)

BTW, my last two shutdowns have been @ 9% and 5%.
[Nook Color Android Development] GrillMouster:
Faster Batery Drain While In Use

Since flashing n86 + 5/23 OC (300/1100 conservative) + fattire's untimely u-boot, my battery has been draining faster. Deep sleep doesn't appear to be a problem, as the NC loses no charge or just 1% after several hours of being left alone with the screen off. However, after a few minutes of light web browsing the battery gradually drains several percentage points. I didn't notice this on the 3.1 beta + 5/13 OC + B&N 1.2 u-boot. Anyone else experiencing this?
[Nook Color Android Development] paleh0rse:
Mine is dropping at Mach speeds as well with just light use -- watched it drop 2% while typing a one paragraph post on here the other day! Add to that my legit PBD issues (most recent one at 45%?!), and all I can say is that I'm having some serious battery issues these days... :(

I'm going to wipe and install 1.2 stock (again!), then drain it to 0%, and see if that helps... wish me luck!
[Nook Color Android Development] boogerboy72:
flashed latest nightly last night before bed, when i got up this morning, the nook wouldnt wake. held the power button for 8 seconds and started right up. Anything i can try to get rid of the sod?

edit, just flashed the 5/23 kernel, well see if that changes anything.
[Nook Color Android Development] xKLoWNx:
I been reading back in this forum and there is alot on the PBD. What I am looking for is if anyone else is having the issue with netflix? When i play a movie it is like fast forward and sounds like chipmunks talking. Can someone point me in the direction for the fix.

I flashed the nightly 87

Thanks
[Nook Color Android Development] Arbelzapf:
Did you have any success pairing (and using) your 2-battery keyboard? I'm still out of luck here
[Nook Color Android Development] newellj79:
Edit build.prop. manufacturer to HTC and device to Vision. Works flawlessly with all cm7 builds.
[Nook Color Android Development] xKLoWNx:
I haven't had to edit the build prop before can you give me a little more detail on how to do that. Thanks!!

Edit: i found a helpful forum on this issue i found an easy way to edit the build getting ready to test it to make sure it works thanks!!
[Nook Color Android Development] rhester72:
Just wanted to chime in and say I'm seeing the same (rapid battery drain under normal use) - I thought it was just me!

I did the 1.2 stock drain - it died @ 11%. :/

Rodney
[Nook Color Android Development] Ophbalance:
The rapid drain issue... the 5/23 kernel now only has two modes, conservative and performance. I wonder if that has anything to do with it?
[Nook Color Android Development] rhester72:
There's been at least one report that falling back to CM7 beta 3.1 with the 5/23 kernel stops the rapid battery drain. I haven't tested this yet, but that would seem to exonerate the kernel/schedulers.

Rodney
[Nook Color Android Development] dexx0008:
nighly 86. No dice, it pairs and connects As hid keyboard. Wonder

When this stopped working. Everything else works fine for me on this build.

Wonder if other devices are having bt troubles now.

I'll have to try my old keyboard Monday.

That kinda sucks.
[Nook Color Android Development] khaytsus:
No rapid battery drain here, NC went two days with moderate use, got down to about 12% before I plugged it in at bed time.

If you see a big drop in battery % I suspect it has to do with the calibration issues we're all seeing more than actually dropping capacity.
[Nook Color Android Development] boogerboy72:
flashed n87 over phiremod 6.2, then the fattires newboot, and 5/13 oc kernel, plugged it in and went to sleep, this morning required a hard reboot (holding the power button for 10 secs) to boot up. i have not changed anything other than the kernel and u boot, should i flash the mlo fattire posted?
[Nook Color Android Development] abs99:
Did you wipe the two cache areas after your flash of n87 (especially Dalvik)?
[Nook Color Android Development] boogerboy72:
i have since wiped them and reflashed n86. seems to have no issues now.
[Nook Color Android Development] chisleu:
What's up mang? (<-- PimpSmurf)

That is a "Sleep of Death". It's a known problem. Currently I think the devs are hard at work on the PBD issue so the (very rare for most) SOD's may be back burnered (or maybe not.)

Yes you should be running the MLO as well. I think there is a package floating about with both in one zip.

Wipe 2 cache's and call me in the morning. :)
[Nook Color Android Development] dexx0008:
any chance that the chipmunk voices could be cleared up when using netflix in the new kernel so we don't have to edit the build.prop now that netflix has removed the device check in the latest update to the app? i'm fine editing the build.prop but would be nice not to have to.
[Nook Color Android Development] Ronin3178:
Nope, in my experience. With the 5/23 kernel you still get chipmunks unless you edit to HTC/Vision. Even with the newer no device check version. I don't notice any changes to anything else running, so I leave it all the time. I also edit the build.prop in the zip prior to flashing.
[Nook Color Android Development] Arbelzapf:
Thank you. Well that makes three. Bluetooth definetely seems to have issues
[Nook Color Android Development] GrillMouster:
I was running 3.1 beta + 5/13 OC kernel + B&N 1.2 u-boot and everything was fine. I rarely let the battery run below 60%, as I often charge the NC at work and at home when I'm not actively using it. When I heard about the PBD problems I tried running it down. It died somewhere around 15% and I had to plug it in to get it to turn on again. After that I decided to flash n86 + 5/23 OC kernel + fattire's untimely u-boot. I didn't try running down the battery again to see if the PBD problem was still there, but I found that I was getting rapid battery drain from light usage. I tried flashing 3.1 beta and 5/23 OC kernel, but there was still battery drain. I then flashed the 5/13 OC kernel and battery drain still seemed fast. I just flashed flash n86 + 5/23 OC kernel + fattire's untimely u-boot again, but this time I wiped battery stats in CWM and fixed permissions (I always clear cache & dalvic every time I flash anything). We'll see how it goes.