yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] chisleu:
Yep. That is why I am here. I've had no problems with the beta + 5/13 OC kernel.

Yesterday I upgraded to the uboot1.2 modified version (the one with the alternate boot images.)

Then I installed the latest nightly and the latest OC kernel (plus my keyboard remap, although I don't even use a BT keyboard anymore so I don't know why.)

It won't sleep. It stayed at 300 all night and this morning it had gone from ~65 to ~35.

Also When it gets to around 30 it will start turning off. I think this is related to battery life. It's crashing from low voltage. IF this is true then THIS IS VERY BAD. You can't over drain a Lipo. It can do all sorts of bad things. It can short internally and catch on fire (if it's hot). It will lose life cycles at a minimum.

I'm trying to keep it above 50% life for now. I've tried resetting the battery stats w/ the market app as well as the CWM function.

Also, the wifi kept "locking up". It was connected, but no network traffic would go through. Required a reboot to fix because if I turned wifi off and then on, it could no longer see the wifi network. I am using wpa2/psk (aes).

I wiped cache/davlic cache and maybe that will fix it. If not, what to do? Redownload/Reinstall?
[Nook Color Android Development] khaytsus:
I smell FUD. It's not going to explode because the battery is too low. Obviously the thing is turning itself off. What voltage is it getting to, do you even know?
[Nook Color Android Development] chisleu:
I smell noise. It can in fact explode in a plasma ball if it's discharged too quickly, shorted, or overdischarged while too hot or pulling too many amps (which heats it up.)

Educate yourself. I have personally seen many of these fires in the RC community, and there are countless lipo fires on video sites around the world.

I also did not say it was certainly that, just that IF (****IF****) it was, then it was dangerous.

It may be shutting down because of a hardware circuit that is turning off the system because the voltage is too low. Maybe it's shutting down because a pink pony flew in with some pixie dust and did a line. I do not know for sure. That is why I chose to capitalize IF.

Interestingly it allows me to boot back up (but soon crashes again.) Normally when this happens, it wouldn't allow you to boot up. It would stay at the "need more power to boot" screen. This doesn't happen.
[Nook Color Android Development] chisleu:
I don't think it is going to go into deep sleep. I had the screen off for 30 minutes and it didn't get into sleep (nothing running.)

I'm going to leave it home to fully charge today and work with it tonight. Maybe there is some mysterious app running in the background to keep it from sleeping. I don't know. I will try to use the battery calibration app to fix it when it is fully charged this afternoon.

Taking 2-5 week, and 2-10 week courses this summer has me so busy that I've not been able to really do anything with my brand new g73sw-a1 laptop. :(

Had it since Saturday and I've only installed mario wii (dolphin emulator ftw)
[Nook Color Android Development] Arbelzapf:
I thought the main argument against PBD coming from an actually empty battery is that it does not show the "too low to turn on" message on boot? Which would indicate that the battery isn't fully drained and the problem lies elsewhere
[Nook Color Android Development] Ronin3178:
As for PBD, I have not have problems with PBD in a while, since flashing fattires 1.2boot & MLO. I went to N87 for about a day, but went back to 7.1 RC0 and the 5/23 OC kernel due to some problems with Netflix chipmunking, I tried all the tricks before I went back and couldn't fix it. I am getting DpSlp on the 5/23 kernel too.

Here's two screenshots from my last shutdown, 5%.

Currently running 7.1RC0, 5/23 OC (without going to 1.2 stock first either)
[Nook Color Android Development] paleh0rse:
You don't actually need to let cwm freeze up to clear Dalvik. Believe it or not, simply entering the clear dalvik option (where it shows no,no,no,no,yes,no), and then backing out without selecting yes or no, will wipe the dalvik cache -- or, at least it says it's been wiped even though you didn't hit 'yes.'

Doing so allows you to use the reboot menu item instead of requiring the hard-reset...
[Nook Color Android Development] :
Damn pink ponies...always gunkin' up my hardware :D

Hope it's okay, but I think that is sig material right there!
[Nook Color Android Development] semperlux:
not again... "error formatting /data..."

so frustrated... What am I doing wrong that nobody else seems to be running into? I've tried many installs of CM7 (I can't list all the thread's who's instructions I've followed--it's been many!) Is anyone else running into this?

I can't format "/data" and that seems to be the issue.
[Nook Color Android Development] paleh0rse:
You "can't," or you don't want to? What version/build are you coming from? On emmc or SD? Is cwm 3.0.28 installed? What error are you running into?
[Nook Color Android Development] mr_fosi:
"error formatting /data..."
[Nook Color Android Development] TJNooker:
Fixed my PBD...maybe

I had PBD issues with the Beta kernel. Before moving to n86, I wiped everything except boot and flashed BN 1.2 + keep CWM. Then I wiped everything again (except boot) and flashed n86 and gapps.

Last night I ran the battery down as low it could go. I got the battery warning at 15% around 3AM before I could no longer keep my eyes open. When I woke up this morning my Nook was dead, so I plugged it in and got the "battery-too-low-to-power-on" warning. When it did power on a few minutes later, the battery level was 10%. So I can't say definitively that the battery ran down to <5%, but it seems likely.
[Nook Color Android Development] paleh0rse:
Do you know if he has already tried a complete install of stock 1.2 with keepcwm? And then going back into cwm to format cache, data, system, dalvik before attempting the cm7 install again?
[Nook Color Android Development] mr_fosi:
I dunno what he has done, I saw the txt of the error in his post title.
[Nook Color Android Development] hockeyfamily737:
Sounds like the symptoms of a newly repartitioned Nook.....error formatting data. There were several threads about it a couple of weeks ago whent the new versions started hitting the shelves.
[Nook Color Android Development] paleh0rse:
Oh... silly tapatalk app doesn't show subject lines :(

Hopefully he comes back to respond...
[Nook Color Android Development] djhotpocket:
I looked through the hundreds of posts in all the relevent topics in the Nook forum and found.nothing concrete regarding my issue, so I apologize in advance if I missed something.

I'm on nightly 86 with Dal's 5/23 OC kernel with the 1.2 uboot file. I can only stay connected to wifi that is unprotected or using WEP. Anything with WPA stays connected for about a minute then drops me even though I still am shown as connected. Ideas or suggestions?
[Nook Color Android Development] chisleu:
If not helpful, I aim to be amusing.
[Nook Color Android Development] 12paq:
Yeah, but where can I get some of that magic pixie dust, man?
[Nook Color Android Development] mr_fosi:
I've done my best to follow this and the dev thread but I'm totally overwhelmed by the flood of info regarding the betas and the newest nightlies.

I'm still running stable 7.0.2 + 4/24 on my NC and I'd like to get in on this "NC actually goes to sleep" business. However, with all the various issues people are posting about their battery drain and wifi with these .32 builds I'm not sure it's worth it.

Can someone who's less overwhelmed by the info post a short summary about which build(s) incorporating .32 are stable enough and seem to suffer from fewer issues and which uboot seems to cause the fewest issues?

Just a short list with some generalities like "this one seems to have solid wifi, but this one cuts out on some people" or something like that?

Or is it really too early to come up with such a general summary...?
[Nook Color Android Development] newellj79:
Nightly 86 has been rock solid for me with the oc kernel. There is no difference for the nc between 86 and 87. It does use the .32 kernel so it does sleep. Also 86+ will automatically install the new preferred uboot for u.
[Nook Color Android Development] Ronin3178:
Here is my experience :

The beta, now called 7.1 RC0 with the 5/23 OC is working great for me. I haven't had any true SOD yet. I have had a few PBD's, but not in like a week or so. I would suggest, that if you didn't already have the the newer uboot installed, flash nightly 86 first, so it gets installed, then the 7.1RC0 and OC kernel.

Like I said, I haven't had any PBD's in a while, my last few discharges, I got down to like 9% and 5%.
[Nook Color Android Development] mr_fosi:
Thank you gents for the replies. :)

So it looks like I should probably step off my 7.0.2 and onto n86 to get the uboot, then perhaps add the 5/23 OC kernel and see how it goes. If all goes well, perhaps I can try the beta (a.k.a. 7.1 RC0). Does this require the full wipe (including /data) that I keep seeing recommended?

I see two 7.1 RC0's though. One is a beta 2 and the other is a beta 3.1. Which one are you using, Ronin?
[Nook Color Android Development] Ronin3178:
I am using 3.1
[Nook Color Android Development] ziggy34:
Nightly #86, love it.
[Nook Color Android Development] derekr:
Would it be worthwhile for a bunch of us to make a plot of battery voltage vs indicated battery %, so that we might determine whether the PBD is a battery calibration error or in fact a hardware/software battery monitoring problem. Let's determine if the system turns off at a prescribed voltage or %.

For example, right now I am measuring 86% at 3917 mv using Circle Battery Widget. I'll keep monitoring and plot a graph.
[Nook Color Android Development] newellj79:
Nightly 86 is newer (has more updates than beta 3.1). Everything from beta 3.1 was merged into n84. So, at this this point once u r on n86 there is nothing to do but keep up with the nightlies. In short, one of the betas would be a step backwards.
[Nook Color Android Development] mr_fosi:
Awesome info, just the kind of stuff that I have missed. :D

I have totally lost the continuity of the release order what with the betas not being listed in the nightly list. I guess I'll go for n86.

Is it best to do the full wipe that ace and others have advocated or did you upp without it?
[Nook Color Android Development] boxcar8028:
well, last night I downloaded cpuspy to check on my cpu and deep sleep. after 7hrs I check my nook to find that it did not sleep once and that my cpu was running at 600mhz all night. my setting are conservative min at 400mhz and max 1200mhz

this would explain why my SOD is fix, it's because my nook is not sleeping.... bitter sweet

cm7 n87 u-boot 1.2 with dalingrin's new kernel 5/23

================

side note: I also downloaded cpuspy to my HTC Airia and found that it is sleeping perfectly with no SOD. my aria is rock solid.

stock cm7 n93
[Nook Color Android Development] newellj79:
A clean wipe is recommended but not mandatory. Use TB and u can b up and running in no time, with peace of mind that u have a clean install. :)
[Nook Color Android Development] chisleu:
Everyone may know this, but it will not sleep with the USB plugged in, wall or computer powered. It will stay at 600mhz while plugged in (to aid in copy speeds over USB.)

I reset my battery stats just now. Not sure if it will help.

I did notice that after a day away from it the wifi hasn't acted up. It didn't go into sleep (charging the battery) but it didn't crash the wifi (yet anyway).

Maybe wiping the caches did something.
[Nook Color Android Development] djhotpocket:
Can anyone please help?
[Nook Color Android Development] seth.i.simmons:
Anybody else here using pure messenger Widgets?? I can't seem to get the Gmail widget to work since updating to n86, anyone have any ideas??
[Nook Color Android Development] boxcar8028:
yeah, I know about the nook not sleeping being plugged in, but that's what's weird about it. the nook was charged at 87% (not plugged in) and 7hrs later its at 63% and my min cpu setting was at 400mhz not 600mhz

so, the nook, thinks its still plugged in? ......odd

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

I see lots of fixes in the change log, maybe something good is coming our way. all else is running well, no wifi issue.... knock on wood :)
[Nook Color Android Development] I Am Marino:
When my NC's screen is off, I'm at 600mHz some days.

Another time, it'll deep sleep. What a confusing issue.
[Nook Color Android Development] TJNooker:
Would you provide a little more detail on the WIFI behavior you're seeing?

After your connection is dropped, does it attempt to reconnect? If so, does it reconnect successfully and then drop you again? Also, are you using a WPA or WPA2 Enterprise connection, i.e., 802.1x EAP or anything like that?
[Nook Color Android Development] chisleu:
Maybe. I STILL spend more time in 600 than in deep sleep even though I AM NOT plugged in. I don't know exactly what is going on.

Willing to test or do anything to help. I'm not stressed for time this weekend (thank... God... ugghhh)
[Nook Color Android Development] Awats:
I just switched to the 0523 OC and I am now seeing the problem. Anyone know if switching back to 0513 is an issue? I didn't have the problem with that OC kernel.
[Nook Color Android Development] boxcar8028:
I know its something in the Kernels. All was well with .29 but now with .32 / .32.9 its all SOD, PBD and lots of deep sleepless nights in seattle :D

not sure what to do....
[Nook Color Android Development] Paul22000:
What the heck is PBD?

I just searched via CTRL+F through the past few dozen pages / 600 posts up to post #2500. Not a single post that uses the acronym "PBD" explains what it is. What the heck?
[Nook Color Android Development] Wipeout:
Premature Battery Death - where you're basically out of charge at somewhere between 30 and 15 percent battery (if I'm remembering correctly).
[Nook Color Android Development] painter_:
PBD=Premature Battery Death

The Nook shutting down at 30 -20% battery left on the meter.
[Nook Color Android Development] ansleyj44:
Premature Battery Death
[Nook Color Android Development] seth.i.simmons:
Its "Premature Battery Death". Its when the battery dies without warning when it shouldn't, usually around 30%.
[Nook Color Android Development] pseudo_nomen:
Premature Battery Death

Where the nook shuts off without warning (at ~30-ish - 15-ish % battery) and will only restart when plugged into power - but upon restart displays a battery level that it shouldn't be shutting down at.
[Nook Color Android Development] Paul22000:
Ahhhhhhh , thanks all!
[Nook Color Android Development] djhotpocket:
At first i connect and 45 seconds later it would drop and reconnect over and over. I wiped fully and reinstalled. Now When my wifi drops it doesn't attempt to reconnect. I still see the icon showing I am connected and in wifi settings menu it shows I am connected even though I'm not ( no browser, market, Netflix, etc). My home router uses WEP and that stays up fine. I work for Verizon Wireless so in the office I connect to Thunderbolts, Samsung Charges, LG Revolutions, and Xperia plays...basically any and all android phones with the stock wireless tethering software. They are all set to WPA and behave like this but if I switch them to WEP or turn off encryption completely they stay connected flawlessly. I'm stumped.
[Nook Color Android Development] philburkhardt:
Deleted, post irrelevant. Nothing to see here. :cool:
[Nook Color Android Development] semperlux:
I finally have CM7 but still very confused...

CM7's (update-cm-7.0.3-encore-signed.zip) installed and working like a dream but I don't know how I did it. If someone can help me understand this I'd appreciate it.

My NOOK's software version is 1.2. Earlier, I complained that I couldn't get CM7 flashed and that evolved to not even being able to restore the stock OS either, despite the multi-boot method. At that point, I had absolutely no idea what to do. I had manualnooter 4.5.6 flashed and working perfectly.

I used these instructions to install CM7: (checked md5sums also)

http://xdaforums.com/showpost.php?p=11452450&postcount=19

I first ran into problems here: "10.Under mounts Format /system, /data, cache. Do not format /boot." when my NC returned an error message when trying to format /data, I proceded with the rest of the instructions as I was too far into it to do anything else. As expected, bootloops at the color screen. This had happened before while following another set of instructions that I'd found on YouTube. In frustration and from my experience rooting my phone, I selected, wipe data/factory reset and this time, /data formated without the error message that I saw earlier from the mounts and storage item.

I tried to restore to NC's OS using the multiple interrupted starts and was not working. Then I read that you can also restart using the START and NOOK (home) button--that worked! (but I'm not sure how) Everything was restoring and I was expecting the unrooted NOOK's home screen but instead the little blue android letters with the blinking cursor. I thought, "ok, that was my best shot--now I'm really screwed :( ...".

Then BANG! the spinning CM7 logo that I'm used to seeing on my HTC Evo. I thought, "WTF? Ok, what just happened?". So ther you have it, like I said, it's working and it's absolutely beautiful--the market is HUGE! everything is exactly what I'm used to seeing in CM7 on my phone--and it's really fast! :D But I don't know how I did it?

I'd like to know what happened because I'm afraid to try any nightlies or kernels... I'm afraid to reboot it actually. Anyone?
[Nook Color Android Development] chisleu:
I let her sit for about an hour and lost about 2% battery. It is staying in 600mhz quite a lot. It is eating battery life while powered off.

I checked and it's "android system" at 90% of the usage. Definitely something up.
[Nook Color Android Development] MadMikeSS:
Just noticed since folks were talking about clock speed and other random effects. Don't know when it changed, but it had to be within the last couple nightlies, but I don't see ONDEMAND as an option in the CPU Governor settings anymore. I only have Conservative and Performance now, and since it chose conservative it's been mostly running at 600 which I have set as my low end. Any reasons for removing OnDemand?
[Nook Color Android Development] Ronin3178:
Dal said that he noticed ondemand and smartass weren't playing well with. 32 so he removed them from the 5/23 OC, and I guess maybe the regular kernel too.
[Nook Color Android Development] MadMikeSS:
Ah, that explains it then. Thanks.
[Nook Color Android Development] redvinestudios:
Looking for a lil help...

I've had a rooted Nook Color for almost 2-3 months. Since February at the least.

Never had an issue updating to a newer nightly version of Cyanogen until last night.

I went through the normal process of putting a verified copy of the update on my memory card, rebooted into Clockwork recovery and did the ol' flash and gapps update.

Rebooted, shut down the device, removed the SD card properly and powered up.

I saw the new green Cyanogen logo and then nothing. A backlit black screen, nothing more. I let it sit for about 30 mins, and nothing.

I proceeded to reboot and it would not start at all. I could only get into my SD card, which has Clockwork Recovery on it. I got a .zip file to put everything back to Stock and it worked. Except it of course hung at the grey N, because I'm running EXT 4 for Cyanogen 7.

So... I updated to Nightly 68, and that's as high as it'll go. I cannot update to the 70's range or 80's nightlies.

What did I do wrong (if anything) and what might be wrong with my Nook? Any help or recommendations will be deeply appreciated.

As I sit currently, I'm on nightly 68... but I would love to run a newer build, especially if it runs better.

-Tim
[Nook Color Android Development] TJNooker:
Ok, I've got a few things you can try:

1. Turn off your WIFI and reboot your Nook. Once it's booted back up, turn WIFI on and try to connect.

2. If that didn't work, go to WIFI settings where you can see all available networks. Long press each "remembered" network and select "Forget Network." Once you've done that for all remembered networks, repeat #1.

If none of that works, then this is beyond my level of expertise.
[Nook Color Android Development] chisleu:
I downgraded to the older .32 OC kernel to test (5/13 or something. I forget)

Now the NC won't even turn the screen off even if you hit the power button. lol.

fun times.
[Nook Color Android Development] Awats:
I'll know here in a bit, I am going to try and back down to 0513 OC on SD.
[Nook Color Android Development] chisleu:
I went back to beta 3.1 and installed the latest kernel. Performance is great!

It sleeps and battery drain with the screen is gone.
[Nook Color Android Development] miniaturepeddler:
What I have noticed with the .32 kernal Nightlies (80+ through 87) is that they have a hard time remaining connected to my WPA secured network at home (Belcon - wireless), but seem to be rock solid with my WEP networks at work (a noname generic brand - cheap) and a secondary network (WEP also - Trendnet) that I've now set up at home.

So does this mean that somewhere in the new kernals there is a problem with WPA security connections? (looks that way from the limited experience of one - myself).

Hope this helps anyone trying to track down the wifi issue of c7.

Robyn
[Nook Color Android Development] only one haze:
Can someone tell me/point me to how to create the uAltImage and uAltRamdisk? I am running a dualboot with CM7 on the main partition and stock1.2 on the secondary partition. Since the new boot menu has been implemented I cannot get into the stock partition. I believe that creating the uAltImage and Ramdisk will get me to that partition. Am I off in that thinking? The AltBoot is for a second partition correct?
[Nook Color Android Development] MadMikeSS:
I'm running n86, but this hasn't changed since I've been running the nightlies, I have a netgear WNR3500 router, have it setup to use WPA, have always had a solid connection with the nook and CM7. I also connect to an unsecured network at work and have a solid connection here as well.
[Nook Color Android Development] 911jason:
When I had wifi problems on vacation last week, it was with a Belkin router. The two other reports I've seen here regarding the wifi continuously connecting and then immediately disconnecting have also been on Belkin routers. With no modifications to my Nook, the wifi was rock solid when I got home and connected to my D-Link router with the same WPA2 settings. Belkin seems to be the problem.
[Nook Color Android Development] sinanju:
Has anyone else noticed...

Ghost typing seems to be gone.

Previously, when connected to the stock charger, folks found the device to be nearly unusable -- attempts to touch the screen would result in presses from random locations on the screen. I had the problem, very consistently, myself. I just realized today that, as of the upgraded kernel, that seems no longer seems to be the case.

It makes me wonder if there's a charging bug fix that gets rid of ghost typing that might also be related to PBD. I have nothing to base that on but a hunch.