yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Ronin3178:
The quick rundown could be from NOT letting it rundown all the time, you've heard of battery memory before right?
[Nook Color Android Development] combustiblemonkey:
the memory effect does not happen to lithium ion batteries.
[Nook Color Android Development] boogerboy72:
well damn, i just cant get away from you sentra guys.

after wiping both caches, reflashing cm, i have had 0 issues. ill get around to flashing the oc kernel sometime.
[Nook Color Android Development] xxiworld:
I seem to be seeing the quick battery drain on 84 too.

Could the PBD actually be the cause of this? I know it is not good to run these batteries down all the way... could doing so have simply damaged our batteries to the point where they drain faster?
[Nook Color Android Development] Ronin3178:
Hope this can help with confusion about PBD (% vs mV)

Ok, from my experiment this morning, on a Nook that doesn't seem to be experiencing PBD anymore, here is a list of the %age,mV from about 18% to 4%. It died right after the last reading @ 4%, 3041mV.

18,3568

17,3573

16,3563

15,3538

14,3562

13,3557

12,3565

11,3505

10,3508

9,3501

8,3499

7,3482

6,3390

6,3302

5,3123

5,3101

4,3101

4,3041

So if you find a widget/app that can show you mV's in realtime, you will know calibration is off if you around 3300 and reading anything other than <10%
[Nook Color Android Development] xKLoWNx:
No Rapid Battery Drain Or Unexpected Shut Off.

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/showpost.php?p=11452450&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-to-restore-the-nook-color-to-stock/

AutoNooter From The Unlockr

http://theunlockr.com/2011/02/05/how-to-root-the-nook-color-autonooter-method/

Nook Color CM7 install instructions

http://xdaforums.com/showpost.php?p=11452450&postcount=19
[Nook Color Android Development] I Am Marino:
While I was at work today, I manually turned my screen off and it went into deep sleep for a full 6 hours never moved from 99% and it deep slept for 5 hours the night before, giving me 11 hours of deep sleep since I last charged it last. Still at 99% now. My battery also dies at 4%=<3000mv each time I've experimented thus far.

Correlation?
[Nook Color Android Development] joenathane:
Guys there is a separate thread for PBD, posting about it here is not only not helping its clogging up this thread. Please use the appropriate thread so your info can help get this problem fixed.

http://xdaforums.com/showthread.php?t=1098178
[Nook Color Android Development] TheMainCat:
I am seeing the same thing. Deep sleep working very well. Just need to get a handle on the "fast" drain. Fully charged it this morning and read a book for about an hour and it dropped 15%.
[Nook Color Android Development] TheMainCat:
Fine. See if I talk about my battery here again...:D
[Nook Color Android Development] I Am Marino:
I know there's a thread, just posting in line with everyone else.

Still rocking the Incredible with the XDA Premium App.
[Nook Color Android Development] khaytsus:
All you have to do is put CWM on an SD card and install CM7, you don't have to do ANYTHING else no matter what's on the eMMC.
[Nook Color Android Development] ivanmmj:
Is the newest source code still in https://github.com/dalingrin/nook_kernel

I don't see any new commits (especially since the new graphics module was added.)
[Nook Color Android Development] screech:
+1

(text added to make the 10character requirement)
[Nook Color Android Development] just4747:
I'm getting all the issues here with Nightly 87. I'm pretty sure my Nook turns off too early in it's low-battery state, like 20% or something and won't turn back on.

But my biggest issue is this random sleep thing. ALL THE TIME I will turn off the screen and try turning it right back on or after a few minutes, and it just won't turn on. I either have to wait till it "recovers" and finally lights back up when pressing a button like nothing ever happened, or I have to hard reboot it with power button hold. Really sucks and it's making the Nook unusable for me. Everything else is fine....

Please tell me something about this?
[Nook Color Android Development] paleh0rse:
Just out of curiosity, has anyone seen or heard from Dalingrin lately?
[Nook Color Android Development] HTCF4N:
...dang it! You mean he has a life??? :rolleyes:
[Nook Color Android Development] boxcar8028:
same here.

cm7 n87 uboot1.2
[Nook Color Android Development] mjb413:
Recent tweets (5/27) are mainly about the sound modification app he's writing for the nc.
[Nook Color Android Development] DeadlyDa:
I fully understand that a number of folks have major issues...but I also want to provide a a bit of balance...I'm on 87 eMMC w/OC kernel at 1.2...and it all works flawlessly for me.

No SOD, no "random sleep", all games run great, battery seems to be just fine. Zero issues with wireless & Bluetooth. I can read books for hours and still have plenty of charge left to do other things. While I do watch the occasional movie (just re-screened Sherlock Holmes last night with no problems), I don't use Netflix...so no BuildProp hacks.

Not gloating here (honest!), I just wanted to let others who are considering going to this ROM on eMMC that it does work very well for some of us.
[Nook Color Android Development] mjb413:
+1 no issues here 87 nonoc kernel with netfilx.
[Nook Color Android Development] just4747:
So maybe those of us with issues need to data/system wipe and re-flash the 87 zip? Would a clean install make a difference?
[Nook Color Android Development] angomy:
I did a clean install on EMMC (first install of CM7) and wiped data/caches after installing nightly 87 and OC 5/23 kernel. Got 2 PBDs (khaystus thinks the second was an SOD, but it would not hard boot on no matter what I did until I plugged it in) the last two days.

Restored to stock 1.2 and installed nightly 85 no OC to see if I get another PBD without updated u-boot or OC kernel.
[Nook Color Android Development] greenmky:
Ditto - 87 + 5/23 1.1ghz). The only thing I've had was a Force Close from the status bar a couple of times when launching a full screen app. Once that made me require a reboot. I noticed once in a while that I need to re-enable wi-fi after sleeping.

Battery life is great now that it deep sleeps fine. Everything works great. Battery dies at around 4% which is fine by me.
[Nook Color Android Development] Awats:
B88 looks like it has many changes. Does anyone have an idea when <poof> ... :p
[Nook Color Android Development] malisha1:
Can u please give me your installation steps? I'm running CRW on the internal memory.
[Nook Color Android Development] Awats:
Did you wait to see if it would come on by itself after about 20 seconds?

Mine does.
[Nook Color Android Development] boxcar8028:
I know, drop already. can't wait!

I hope this will fix the SOD, PBD and deep sleep issues.

with fingers crossed :)
[Nook Color Android Development] joenathane:
You can see all that's fixed here http://cm-nightlies.appspot.com/?device=encore
[Nook Color Android Development] boxcar8028:
yeah, thanks, i know about the change log, but i'm not sure on all of the terms and what do they really mean. can you tell if any of the battery issues are fixed.
[Nook Color Android Development] joenathane:
There have been no Nook specific fixes in build 88 so far, so no battery fixes.
[Nook Color Android Development] Awats:
I didn't think it always had to be a Nook specific change for it to affect the Nook. :confused:
[Nook Color Android Development] joenathane:
The PBD and SOD are Nook specific issues, understand?
[Nook Color Android Development] Awats:
Let's keep this civil. What I am suggesting is that a change doesn't have to be marked as encore to impact the nook. And some of the other changes sound interesting if they do.
[Nook Color Android Development] newellj79:
Agreed. There is a rom manager commit for instance, introducing a newer version.
[Nook Color Android Development] joenathane:
I wasn't being uncivil... It's clear you don't understand what I was saying. Every change on the that log effects the Nook because its going into the build, I was posting in response to a direct question, being whether or not the issues with the battery were fixed. Those fixes, when they do come, will be Nook specific and have an Encore label, understand what I'm trying to say?

In any case this whole discussion is starting to get a bit ridiculous and off topic, good day sir!
[Nook Color Android Development] adobomb:
So I updated to this build and all i get is the cyanogen(mod) splash screen followed by a blank screen.. No "Touch The Future of Reading" so I don't even know how to get into recovery, any tips?
[Nook Color Android Development] Awats:
Good day to you too! :)

Now back to fixin' stuff.
[Nook Color Android Development] :
Did you try doing the exact same thing as you have always been doing?
[Nook Color Android Development] newellj79:
Golly... that's all u r suppose to get, it has a custom uboot now. Hold the n button on boot like always, or boot into it from the rom.
[Nook Color Android Development] greenmky:
I followed eyeballer's guide all the way.

http://xdaforums.com/showthread.php?t=1030227

I went from Stock BN 1.2 -> CM7.0.2 stable + OC kernel for a few weeks -> nightly 87 with 5/23 OC kernel.

Of note, I did NOT wipe the dalvik cache...I wiped only the standard cache since that's what eyeballer's guide said to do (it said only to wipe cache).
[Nook Color Android Development] LongbowFoSho:
I'm experiencing the lack of deep sleep on 87 w/ the 5/23 OC kernel. Is the random deep sleep issue limited to 87 or has it been ongoing for awhile now?

Would reverting to 86 or earlier be a good idea for those of us who legitimately need the deep sleep?
[Nook Color Android Development] bekyndnunwind:
There is no difference between N86 and N87 (there was one commit in between, but it was not Nook specific.

I am using Beta 3.1 still w/ the 5/23 OC kernel and my Nook goes into deep sleep.
[Nook Color Android Development] Rick_V:
I am on #87 with the 5-23 kernel. I unplugged my Nook at around 5:30 this morning hadn't touched it until just now 9:30. It is at 99%. The trick is in settings: goto Wireless and Networks/Wi-Fi settings then click on the menu icon select advanced then Wi_Fi sleep policy and select When screen turns off. Not sure if reboot is necessary but it can't hurt.
[Nook Color Android Development] adobomb:
unfortunately all it boots to is a blank screen, so i'm not able to get into recovery via the rom.. holding the n button also doesn't do anything
[Nook Color Android Development] paleh0rse:
Boot to a SD with CWM, and start formatting and reflashing accordingly...
[Nook Color Android Development] martian21:
Sounds like you flashed an incompatible kernel. Your options are to boot Clockworkmod from an SD card as stated or you can try to use the n+power trick but it can be difficult.

I've had pretty good luck accessing Clockworkmod by doing the following:

Hold down the "n" button then press and hold the power button and continue holding both - the Nook will power on [continue holding both buttons] then after about 10 seconds it will power off.

KEEP HOLDING THE "n" button but release the power button once it powers off then press and hold the power button again [all while still holding the "n" button]

Once the screen flashes, indicating the Nook is powering back on, [5-6 seconds] release the power button but KEEP HOLDING THE "n" until you enter recovery!

I don't believe the first step is technically necessary however it seems to make the next steps work much more reliably. Make sure that on the second power up you release the power button before the nook powers off again. Typically it powers on after 5-6 seconds and then will power off again after ~10 seconds so you only have about a 4 second window to release the power button to get it right.

Hope this helps.

Martian21
[Nook Color Android Development] DizzyDen:
Asked a while back in http://xdaforums.com/showpost.php?p=14126927&postcount=2562 but never got any information....

EDIT: Questions for the dev's: Is there a reason that libOMX.TI.JPEG.Encoder.so and libOMX.TI.JPEG.encoder.so are both in the system/lib folder?

Also: Is there a reason some of the files have ".Decode" and ".Encode" while others have ".decode" and ".encode"... I'm just making sure the naming is correct is all....
[Nook Color Android Development] AntsInMyPants:
Betas?

I have been running CM7.10 RC0 2.6.32-beta3.1 (1.2 uBoot & dalgrin 05-13-11 kernel) for a while now and everything works great.

Where can I find further work on this?

I thought there was a separate thread that had the links and instructions for the beta but cannot find anything.

Thanks!
[Nook Color Android Development] vtmike:
The most recent changes are in the nightlies. I believe the beta was merged over beginning with 84.
[Nook Color Android Development] LongbowFoSho:
Just wanted to quote myself to say that I've solved the problem, albeit in a somewhat unorthodox way.

Background: I have two Nooks (one is mine, the other a friend's), both running N87 and the 5/23 kernel. Mine deep sleeps with no issues, his doesn't.

I'd been reading the PBD thread about using HC from the SD to correct it and thought "what the hell?" The only difference between my Nook and his was mine has had every major ROM run on it at one time or another, including HC for a very short time.

So, I put HC on the SD card, booted it up and let it run for 15-20 minutes. I didn't install anything or do anything other than just mess with it every few minutes. I didn't even connect it to WiFi.

I then took out the SD card and rebooted back into CM7 N87 on the emmc and VOILA.....deep sleep within a minute of the screen shutting off.

I'm going to fully charge the battery and let it sit to see if the battery is indeed being preserved in deep sleep as it should be. Will update with results here in a few hours.

Cliffs: Running HC from an SD card could also possibly fix deep sleep issues as well as PBD.

Hope this helps someone else.
[Nook Color Android Development] paleh0rse:
The problem with that "fix" is that there is some evidence to suggest that its only temporary. A few that have used it have said that PDB eventually returns -- and that PDB may even get worse over time as a direct result of the amount of time your NC spends in deep sleep (not proven yet).

Whatever your results are, please remember to share them in the PBD thread! Good luck!
[Nook Color Android Development] chesh420:
I was just having an issue with deep sleep myself. It had been working fine, but then I played with some settings and it didn't work. Finally realized it was location services being turned on. As soon as it was turned off, deep sleep worked fine again.
[Nook Color Android Development] pbcal:
No updated for one week

For one week there is no new release uploaded to to the Cyanogen Mirror:

http://download.cyanogenmod.com/

Not even for any other device.

Last file is a week old. Is the server moved to any new location?
[Nook Color Android Development] AntsInMyPants:
Chris Soyars tweeted yesterday that the drives on the server are acting up so he wants to wait a few days to see if they crap out. No new builds until then.
[Nook Color Android Development] kz121:
Just curious, I'm running the beta rom off emmc myself (CM7.10 RC0 2.6.32-beta3.1 (1.2 uBoot & dalgrin 05-13-11 kernel)) and for whatever reason I can not find where or how to enable usb debugging or enable standard USB Mass Storage Support. Is/has anyone else experienced this too? If so, can someone suggest a remedy? Should I move up to the most recent nightly? Which kernel is being used in the current nightly? Is it the dalgrin OC kernel?

My nook is running soooo stable since my accidental CWM install and flash to EMMC - now i'm nervous to try another build! just can't get it to mount emmc or sd on my mac (osx)...

Thought?

(feel free to direct PM me - I really need an answer as this NC is a daily driver these days)

Thanks!

kz121
[Nook Color Android Development] boxcar8028:
USB mounting is working in cm7 n87 but for me I'm having battery issues, SOD and no deep sleep. the dev's are working on this and will have it fixed real soon.

debugging settings are here: Settings / Application / Development

but, this may help. just remember to eject before unplugging.
[Nook Color Android Development] Nburnes:
Which is why you should set up a box and build your own. Doesn't take longer then 10 minutes for a build on my machine.
[Nook Color Android Development] dalingrin:
None of the dev team can reproduce SODs or sleep issues. :(

The battery calibration is a real issue though and is being worked on.

You shouldn't need an app to mount eMMC or the SD card on the later CM7 nightlies.
[Nook Color Android Development] Awats:
Maybe the calibration fix will help narrow the SOD.
[Nook Color Android Development] boxcar8028:
yeah, not sure why but my nook has not deep sleep for days now. I haven't had any SOD anymore for my nook no longer deep sleep. I have try the boot into HC SD trick but this will only work for about 1-2 days and then its back to no DS. I have try turning wifi off with no luck. I have try a full wipe and re-flash with and with out OC kernel but it always turns out the same, no deep sleep. Im hoping the new battery calibration will help.

stock cm7 1.2 u-boot n87
[Nook Color Android Development] ansleyj44:
The only time I experience no deep sleep, is if i turn off the screen after charging it to full, remove the USB, play for couple minutes and then turn the screen off. It won't enter deep sleep 1/8 th of the time i do this, but I can solve it by double checking that has entered deep sleep after a minute. If it hasn't, then the next time I turn off my screen ( usually a couple minutes after that) it sorts itself out and enters deep sleep.

Given my current experience, is almost as if my nook isn't reading that the charger had been removed or something. Just my 2 cents.

Running nightly 86 OC kernel and 1.2 uboot
[Nook Color Android Development] mr_fosi:
I'm interested in learning more about this. Perhaps you have a link handy that will point me in a good direction?
[Nook Color Android Development] eusor:
I also had problem with it not going into deep sleep. In my case, I think it's somehow related to wifi...

Just before turning off the screen, I closed the wifi and it started sleeping instantly... I'll try to look into it when I get some extra time. Maybe start from a fresh version and start installing packages one by one.
[Nook Color Android Development] chisleu:
Clearing the caches fixed this problem for me repeatedly. Maybe it will work for you.

Same thing here. I also had the wifi lock up (white signal) and I couldn't get it to come up without a reboot. This went away with the sleeping issue after I wiped davlik.

The battery issue seems to be causing SOD's. I went back to beta 3.1 and everything seemed well and good. The battery issue eventually came back. Today it wouldn't come on until I put it on a charger. I think it's the battery issue hard shuting the system down because the OS thinks the battery is super low. I guess this is being worked on but may be a SOD-like problem that many users call SOD although it is not SOD.
[Nook Color Android Development] fattire:
New U-Boot for y'all...

Okay here's a new u-boot... call it "Cyan Plus One" Edition.

Changes:

New Configuration Feature - Always Use Alternate Boot - this makes it more practical to put an overclocked kernel setup in uAltImg/uAltRam and make it the default boot option. The "u-boot.altboot" file works just like the "u-boot.device" file does. Put a "1" in /rom/u-boot.altboot in emmc p2 (/rom) and, unless manually overridden, you'll always load w/ the alternate boot option. (If for whatever reason a(n) uAltImg is not available on your boot device, it should automatically fallback to uImage/uRamdisk.)

Similar to u-boot.altboot, the "u-boot.device" file has been moved from /boot (p1 on either boot device) to /rom (p2 on *eMMC* only). If you were using j4mm3r's version or any version up to now, move the file to /rom.

Updated menu text to reflect new configurations

Improvement to button detection. Earlier versions did it 3 times. Last version got it down to two. This version got it down to 1.

There was a lot of discussion internally about the best place to put configuration files such as "u-boot.device", which formerly was in the /boot directory of the boot device (whether it was SD or EMMC), and has now been moved to /rom (always p2 on EMMC). /rom seems to be the place for boot settings. No matter where you boot from, it will always look in the same place for your settings. It also means someone can throw a front end on it in a "Tweaks" app and make these preferences a UI option.

So here's how it might work with a .32 nightly...

Take dalingrin's latest .32 OC kernel. Put it in /boot and call it uAltImg. Then copy uRamdisk to uRecImg. Now you can either boot to Alternate via the menu to have the OC kernel once, or do something like:

echo "1" > /rom/u-boot.altboot

to make the OC the default, and then use the boot menu for those occasions when you want to go back to the original kernel.

The same setting should work w/SD cards-- booting will check the setting on the EMMC and make the choice for the selected boot device (by default it will be SD if your'e booting from SD unless overridden by the menu or the u-boot.device file in emmc:/rom)

Again, this is going from my compiler straight to this post, so as with all of these u-boots, if you are going to try it, do so at your own risk. It is very possi-probable that this won't work. Please read caveats in my previous posts about the importance of backing up, having boot SDs, etc. Do not try unless you know what you are doing. I have not done any testing with SD yet, since I was testing the other stuff, so I'd be interested as to whether it works or not.

u-boot.bin (cyan plus one)
[Nook Color Android Development] :
And now for a flashable one :D
[Nook Color Android Development] lafester:
thanks guys :)
[Nook Color Android Development] fattire:
Thought: While you're at it, you could have it add an OC kernel (uAltImg) and the same uRamdisk (as uAltRam) so people can play with it :) Not that I advise such behavior, of course.
[Nook Color Android Development] Nburnes:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Encore
[Nook Color Android Development] fattire:
10 minutes? It takes 2+ hours for me from make clobber on my macbook pro... But I have a new thinkpad on the way mwa-haha!