yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] dennisi01:
I just flashed from phiremod 6.2 over to the uboot/rom/.32 kernel/gapps. formatted cache, installed, formatted dalvik cache - all seems well so far. Wifi works fine (so far tethered from my moto droid), deep sleep doesnt seem to shut off the wifi.

I noticed one thing - i was playing Sacred Odyssey, and i exited it by hitting the n button, then shut the screen off with the power button. After turning it back on a few minutes later and checking cpuspy, i noticed it did not go into a deep sleep. I went into system panel, killed the Sacred Odyssey process, shut down the screen, and it is now sleeping deeply again - is this expected behavior?
[Nook Color Android Development] combustiblemonkey:
Took my nook off the charger Friday evening, left it off all weekend. This morning it was stuck in sleep mode, so I powered down completely and brought it back up. 51% battery remaining at the moment.

Edit: This is the only problem I have had with it. And I dont really count it as a problem so much as an oddity.
[Nook Color Android Development] 360Razir:
OK, again, I only had my NC unresponsive once and pushing "n" for ~8 seconds did work for me, so was hoping it was universal. Thanks for the feedback.
[Nook Color Android Development] boogerboy72:
any chance that app says it keeps the phone from sleeping in the "stuff it needs to access" section. (pardon the technical term)
[Nook Color Android Development] joe2262:
My Nook was at 35% when I had to leave the room for about 10 minutes, came back to a black screen and had to hard reboot. When the Nook restarted the battery read 24% so I hook it up to the AC.

Using VG's uSD installer.
[Nook Color Android Development] MACLUIS1:
This is getting boring!!!!!!!!!!!!!!!!!!!!!!!!. No new buids? Need to brick my Nook. Somebody please gime something to flash.
[Nook Color Android Development] dennisi01:
hmm that's a good possibility - i'd have to reinstall it to find out i think though. anybody else know? Shouldn't hitting the power button still put the phone (tablet) to sleep despite that app caveat?
[Nook Color Android Development] Arbelzapf:
Dalingrin has been pretty calm recently. No Twitter updates, no forum posts. I even checked the IRC logs, but he hasn't been there either:(

I can only hope this is a good thing
[Nook Color Android Development] Paul22000:
I believe he is on post-finals break :cool:
[Nook Color Android Development] boogerboy72:
cant say i blame him for that.
[Nook Color Android Development] Arbelzapf:
Well that certainly IS a good thing :o
[Nook Color Android Development] itzankov:
I'm very impressed with this built. I've been using it (with the dal overclock kernel) since the 13th, and still have 67% battery.

As far as I'm concerned this beta worthy for release.

I've had no issues with sleep, except for IMO beta which seems to prevent the device from sleeping. I left it active for over 24h and it drained about 20%.

Many thanks to the developers.
[Nook Color Android Development] dexx0008:
I'm hoping a dev can answer this, sorry if i missed it hidden in some thread.

It is regarding IMEI

We know that some applications require this to run/or to be registered to a user/etc. We also know the nook doesn't have an IMEI. I believe it is set to report NULL for the IMEI. This presents a problem for any applications that rely on it and one doesn't always know this up front.

Is it possible to have the IMEI be generated in CM7 and be included in CM7 which uses the nook colors serial number so that we get a static IMEI that would be unique to each of us?

or... are we to assume we will never be able to use such applications?

I realize there are various hacks out there to patch the framework.jar to accomplish this but I'd rather see something incorporated into CM7.

How does the wifi only galaxy tab report the IMEI, null as well? I thought I read that it was generated off the serial number of the device but the information I read could have been wrong. I don't happen to have the source.
[Nook Color Android Development] GrillMouster:
I've been running the 3.1beta, .32 OC kernel, and 1.2 uboot since they came out and I haven't had any major problems. No wifi dropouts, not SOD.

My install procedure: I just wiped cache of the nightly I was running at the time, flashed uboot, flashed 3.1beta, and OC kernel (in that order). Then I wiped Dalvic, forced power-down by holding power button (always necessary after wiping Dalvic because it locks CWM). Then I started the NC, let it sit for a couple of minutes after the unlock screen appeared. I'm not sure if this next part is necessary for bluetooth, but I did it anway, as it may help fix other problems. I forced powered-down the NC by holding the power button, booted into CWM by pressing power+N until four full seconds after "Read forever" appears. In CWM I fixed permissions, then rebooted system.

The only thing odd that has happened is that last night when I plugged the NC to the charger and pressed the N button the screen backlight turned on, but the screen was black. I just tapped the power button and the screen turned off, then tapped it again and the lockscreen came up normally. That was after a full day of running the thing heavily and after three whole days of not being charged and not being rebooted. Once in a while the lock screen is a few seconds delayed coming up when I press the N or power button, but that could be the governor or the "Unlock with Wifi" app I run.
[Nook Color Android Development] joe91584:
My whole issue was I needed to reformat my SD card once I did this everything stop locking up and the system now plays video wonderful.

Colors don't look as sharp but I not *****ing it really overall great.
[Nook Color Android Development] paleh0rse:
Dal has stated that he will not be building an IMEI solution into the official CM7 builds. Your best bet is to use the modded framework.jar files found in the themes and apps forum (look for Swype and/or HBO GO thread and the file that is specific to your current build).
[Nook Color Android Development] vtmike:
Mine does that if I plug the charger in while my nook is asleep. Think its because its set up to not sleep while charging. Easy remedy is to make sure you plug it in while the screen is on.
[Nook Color Android Development] dexx0008:
Thanks for the info, I did not see that Dal had posted that. I did see those links to modded .jars but I think a better solution should be devised.

Since... most people just grab the pre-packaged framework.jar file meaning everyone will have the same IMEI using the static solutions posted. No one (generally speaking) takes the time to recompile things themselves. or they use the random IMEI fix which assigns random imei's everytime you boot which is only good for apps checking for presence of IMEI.

A patch creating one off the nooks serial # if it could be done imho would be a better approach. Even if it was an official patch kept outside of CM7

posted here perhaps (bottom of linked page or in the notes like other devices)

http://wiki.cyanogenmod.com/index.php?title=Latest_Version
[Nook Color Android Development] seth.i.simmons:
Until today this ROM was working absolutely perfectly. My charger broke last Friday, but because of this new Beta build, I was able to run it off and on till Monday, with over 70hrs of sleep in there, and whenever I would wake it up, I saw ZERO battery loss... No SODs yet either, and everything was great until today my status bar FC'd and then didn't come back (which it has before). Then just a few minutes ago, my soft keys disappeared, and then just reappeared as I typed this. Not sure what's up with that... But I'm loving it so far, can't wait to see where this is gonna go!
[Nook Color Android Development] chisleu:
Yeah the softkeys thing has happened to myself and others as well. They are still there, if you know where they are. You can click them, but you can't see them. heh. weird stuff.
[Nook Color Android Development] seth.i.simmons:
Yeah, I had heard of people being able to still tap them, so I tried it, and it worked :P Really weird graphical glitch, but nothing too major. Right now I'm trying to get my battery below 30% to see I'd I get the random shutdowns like other people.
[Nook Color Android Development] iDidItAll4theNookie:
Yeah, when it happened to me, I was glad I had added the control buttons to the power menu. A Nice feature to bail you out until you can reboot. Helps you find out just how broken things are, too. Everything worked, but the notification bar is nice to have visible. ;)
[Nook Color Android Development] deadbot1:
Wont go to poll...battery never been below 40%. Running on emmc.

Left her on all day off the charger(6 am to 9 pm)....97% battery...no issues
[Nook Color Android Development] xantiv:
Anyone else notice the system slowing down after watching videos in youtube or with flash in the browser? I tried downgrading flash player to 10.2 but that didn't help. I'm using CM7 beta 3.1 with the overclock kernel. Everything else is running flawlessly. No SOD. Battery life is great with deep sleep.
[Nook Color Android Development] Matchay:
Hi, in last two days (after I flashed the Beta 3.1) I observed a significant slow down after playing with Nook for a while, but I had no time to investigate deeper. Today I am going to try to confirm if it might be flash-related. Will let you know.

Regards,

Maciej
[Nook Color Android Development] aludal:
I noticed slowing down overall NC operation after watching (Flash) movies in browsers, sure. It's not just 3.1 and/or OC kernel, I used to first reboot, then I discovered I've got caches of browsers stuffed at 5...6 MB when video starts to stutter and/or UI stutters. So now I've been used to clearing these caches.

Plus, exiting browsers via settings>Manage Applications helps a lot. I somehow don't see an option to exit (kill) the stock Browser or Opera out of their "regular" controls. (Hopefully mad murdock could tie his "Home" soft button to exit (kill) the app and clear its cache)

There must be some other caches filling with junk and not affected by these manipulations, as watching some online streaming movies can stop after 15...45 minutes for no reason.

In general, I guess we are not that close to the video and/or audio optimal cache sizes and policies to achieve smooth streaming inline video even at 360p. These parameters we have now should be quite good when we get HW overlays working, but as of today it's a different story: stuttering, or A/V desync, or both, plus the whole NC operation is choked.

My youtube and playing "static" video files by Mobo and stock players are not affected, and generally won't slow down the whole NC operation. Their caches don't grow that much anyway.

I also plan to play with number of connections in Opera, to diminish the effect of fluctuating WiFi bandwidth, short interruptions, re-buffering, and the like. My DD-WRT Fry's junk router is perfect as much as a $30 device can be, but its junk non-MIMO WiFi radio leaves a lot to desire, especially in Mixed b/n mode I need for my junk dumbphone, apart from clean "n only" mode.

Never experienced a SOD either. I used the bachviet method with some tweaks detailed in my blog.

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

fineoils.blogspot.com <--some notes on NC and DD-WRT
[Nook Color Android Development] TJNooker:
Others have reported this already, but I figured I'd make my statistic official. I just had my first spontaneous shutdown upon reaching 30% battery. I was browsing apps in AppBrain while disconnected from the charger. When the battery hit 30% the screen went black. I assume it shutdown because I could not revive it with a hard reboot. I held down the power button for 15 seconds several times to no avail. Once I plugged it into the charger it booted right up; no button pressing required.

I thought this was odd because a few days ago I played Angry Birds Rio until the 15% battery warning came up. This, so far, is the only abnormal behavior I've experienced with this kernel.
[Nook Color Android Development] fattire:
This battery thing is indeed curious... I'm wondering if somehow a "false bottom" is being set below the actual end-of-charge level so that Android doesn't realize it's running out of battery when it actually is flat out. If that's the case, maybe some sort of recalibration would be necessary (or might happen automatically on next charge?) so that the reported battery consumption == actual charge left.

I do also remember seeing reports of battery levels in b3 seeming to drop hard abruptly. I had this happen once, where battery level dropped from like 83% to ~50% after being put to sleep for like 5 minutes. So maybe something weird is going on with calibration and level estimation.

This is all idle speculation., but has anyone who has had the battery drop out at 15-30% done a full charge after that and then let it drop back down to that range? if so did it go down to 0 normally, or did it exhibit the strange dropouts a second time?

TJNooker, let us know once it's charged back up whether you experience this again at 30% (or at all for that matter).

Also, you can see your reported battery level over time in Settings->Applications-> Battery Use (at the top). Anyone see anything weird there?
[Nook Color Android Development] Narfx:
Mine went from ~60 to ~30 while sleeping (two or three hours). It happened during a SOD, though, so I'm not sure if it's related.
[Nook Color Android Development] Zorkman:
this is not specifically 2.6.32 related,

because I'm on 2.6.29 (OC 1.3) and CM7 Nightly #70

It happened to me also already two times

last time I'm not sure what the percentage was when it shut itself down, but after rebooting (only possible by charging the nook) it said it was at 20%

as far as I know this never happened to me with the OLD OC kernel

since the new nightlies I had to use this kernel:

http://xdaforums.com/showpost.php?p=13499750&postcount=2382

Or is there already an "official" 1.3 OC kernel from dal?

(last time I flashed it from his site and from the app "kernel manager" my Nook refused to boot and I had to reflash either the stock CM7 one or the one posted in the link above)

it might also have to do with me updating to u-boot 1.2?

didn't happen with u-boot 1.1
[Nook Color Android Development] Hiro666:
I have now experienced 3 SODs over a period of about a week. I am on u-boot 1.2, beta 3.1 - OC kernel not installed but set at 925. Otherwise, no issues to report.

Edit: Forgot to mention that my battery was somewhere between 25 and 30 percent when the SODs occurred.
[Nook Color Android Development] iDidItAll4theNookie:
I guess we will see for me today. I've not charged for over 2 days, and I'm at 41%. I've used it quite a bit, too. Everything from browsing, email, games, app downloads, and videos, so it seems like I should be lower on my battery %.
[Nook Color Android Development] :
I recharged mine the night I posted it shutdown, and I'm trying to watch netflix on performance until it gets down to 27% today...should be around noon :P

EDIT: Damn, 1100 on performance and netflix on full brightness really kill the battery.

Woohoo! Made it to 23%! This is after a full charge overnight (with the N logo never turning green, but battery reporting 100%).
[Nook Color Android Development] seth.i.simmons:
Just ran mine down to 18% before it shut itself down. Better than alot of people's, but still weird that it didnt warn me or anything... But the battery life in this kernel is awesome, I can get around 6hrs of Netflix in on a single charge. Gotta love that! I noticed that Netflix stays at 600mhz when watching a video, which certainly helps.
[Nook Color Android Development] Arbelzapf:
Calibrating didn't help. Yesterday I had a shutdown at around 26%. Afterwards, I charged to 100% and wiped battery stats. Today it shut down at 24%

FPse really helps testing this issue :D
[Nook Color Android Development] xc68000:
I had a spontaneous shutdown just now. My battery was around 86%. After reboot it was 84%. Using the beta plus 1.2 uboot plus overclock kernal (but only set to 800 on demand)
[Nook Color Android Development] skwalas:
and.... bing!

instant shutdown again last night, 22%, no buttons worked. it automatically ebooted when plugging into the BN charger.

I'm still on nightly 75, with the new 1.2 uboot. I have never flashed the beta. Given that the uboot is the common point between the beta users and myself, it's almost certain there's some change in the new uboot causing this.

Just a couple weeks ago i was all the way down to 9%. I was still on the 1.1 uboot at the time, and on a post-battery-standby-fix nightly as well.
[Nook Color Android Development] stevemp:
Four days of continuous running before shutting down at 14% Light use, but still impressive! 1.2 uboot, oc kernel ondemand governor @ 300 min 1100 max.
[Nook Color Android Development] deadbot1:
Had more screen wierdness this morn. Alarm went off, couldn't get screen to come on to kill it. Backlight was on, but no screen or touch sensor. Had to hard shutdown to kill it. Battery still at 87% after reading for two hours last night...last on charger at 6 am yesterday.
[Nook Color Android Development] chisleu:
When that happened to me it killed he battery very fast as if it were running ballsout the whole time.
[Nook Color Android Development] xdajunkman:
For everyone with the auto-shutdown at around 30% battery, I can confirm that the procedure from this post fixed it for me:

I am not running the beta test build (forgive me if I am clogging up the thread, but I thought this might be pertinent). I am running 7.0.3 stable, but updated to the 1.2 uboot. I have noticed my Nook shutting down ~30% battery since the update to the new uboot. I did a full backup, reflashed to B&N stock 1.2 and ran the battery down. It shut off at 28%, and when I plugged it in and let it charge for a few minutes it started up and had the battery at 14%. I did a full restore (including the boot partition) of my CM7 backup, and the battery was at 15%. Fully charged the device and ran it down again - did not shut off until it reached less than 10%.

Perhaps the problem lies somewhere in the process of updating to the 1.2 uboot, as it seems only those with the new uboot have this problem. As I did a full restore of my previous CM7/1.2 uboot setup and things seem to be working now it can't be a problem with the uboot itself...perhaps just the method we are using to update it.
[Nook Color Android Development] Narfx:
BTW, mine also died at 19%.
[Nook Color Android Development] bekyndnunwind:
Running beta 3.1 and still seeing Gmail notifications endlessly looping.

I will get an email while I'm at work, and it will play the Gmail notification for 8 hours while I'm at work. I walk in the door at home and hear it playing, and it stops once I view the notification...

Is anyone seeing this on the nightlies, or is this just an issue in the beta builds?
[Nook Color Android Development] Arbelzapf:
Can you go back to b3.1 after doing this or will that bring back the ~25% death?
[Nook Color Android Development] furius:
I'm coming from CM7 nightly thread where it seems there are people using the .32 dalingrin kernel over the #77 nightly build...

how can be possible?
[Nook Color Android Development] niphoet:
My SODs have also all happened around 20-30% battery level. I'm running 1.2 uBoot, beta3.1, OC kernel. I just reflashed beta3.1 without the OC kernel to see if it makes any difference.

On Friday when I charged the NC from ~70% to full, it only took about an hour or 2. This morning when I plugged it into the same cable connected to the same computer, it has taken about 5 hours to go from 23% to 29%. Anyone else experience this kind of charging behavior?
[Nook Color Android Development] ovar:
I also experienced the Nook shutting down around 25% battery life. Long press N or power button had no effect. I plugged the Nook in and it powered up.

I have wiped battery stats and will report if there is any change the second time through.
[Nook Color Android Development] newellj79:
I had this problem. I changed the notification sound andt he problem stopped.
[Nook Color Android Development] capnblackleg:
I had it happen once when I dropped really low. I just rebooted and it started charging as fast as always.
[Nook Color Android Development] fattire:
Hmm. Since people coming directly from 1.2 don't seem to have this battery issue, I took a look at MLO. (MLO is the first thing that loads, even before u-boot, and it goes in /boot right along with u-boot.bin, and uImage, etc. ) There are differences between mlo (x-loader) from 1.1 to 1.2... including this, possibly relating to the battery issue...

> .word 300, 12, 0, 4 /* ARM@150MHz Low-power conf. used when battery is DEAD */
> .word 20, 0, 0, 2 /* Low power config used when battery is DEAD */

verygreen thinks this may just be for uboot's battery check and not the Android stuff, but just in case I built the new MLO and am trying it to see if it makes a difference. I assume that the new MLO is already built and included in the official 1.2 update as well, but maybe someone else can confirm that.
[Nook Color Android Development] :
Well I wiped EVERYTHING (boot, system, data, cache, emmc (due for a clean start)).

Burned a SD CWM bootable disk (been a while...)

Installing pure stock (including recovery).

Then will go back to beta and burn through the battery...

OR should I burn through it on stock?
[Nook Color Android Development] iDidItAll4theNookie:
2 days, 13 hours later, I finally got the low battery warning at 15%. Nook keeps on truckin' without issue. I am coming from rooted 1.2 (925), so I should be running B&N's uboot. Not sure if I want to charge it now or run it till it's dead. At 13% as I post this. Just fantastic. :)
[Nook Color Android Development] :
From BN it should have have an issue. The issue is with going from 1.1 to 1.2 (it seems).

Interestingly enough, before I wiped the hell out of my nook, the battery was reporting at 94%. Now running full stock 1.2 and it reads 76%, which is about the different that the NC shut off at running beta 3.1...
[Nook Color Android Development] EverythingNook:
to update uboot is it just a simple flash in CWM or anything special?
[Nook Color Android Development] :
Check 1st line of sig. flashable uboot there.
[Nook Color Android Development] EverythingNook:
thanks man

edit: worked fine! but no android text?
[Nook Color Android Development] :
Finally! Am I right or what? :P Although I could do without that bright flash, but that's in stock 1.2 as well...
[Nook Color Android Development] EverythingNook:
ya thanks man! are you missing the android text on boot or is that just me?
[Nook Color Android Development] :
AH HA!

TL;DR: Sorry, didn't solve the problem in an easy way. Took the long way home...

Story:

So got pissed at this thing, and with it being Week 8 and all, I'm right between needing to do stuff, so I wanted to get this to work.

In short, I formatted everything with cwm sd bootable card. Boot included.

I installed the original 1.2 update complete with its stock recovery.

Data/factory reset ('cause I can). Booted up, bypassed Oobe.

Check battery, 78% or so (different from CM7.1beta of 9x%, and I was charging the whole time...)

Put back in bootable sd, flashed beta 3.1, may gapps, 5/13 OC kernel.

Boot up, a little more than 78% (from charging)

Shut it down at 87%. Wanted it to charge faster and see that green glow ~90% (as I have before all this)

At roughly 90% (I assume, it's off after all), green! Note I did not see green ever before in beta 3.1. So this is me assuming that because the NC knows where the "top" of the charge range is, it will know the (proper) bottom. Well drain it and see.

Based off me knowing not a lot, I would think just flashing the 1.2 bootloader alone is messing things up...But just my 2¢.

Just a thought, maybe backup, flash stock 1.2 (after wiping everything), flash latest everything, then do advanced restore and just select data? May work, but may break some stuff to.

EDIT: So booted it up, meter read 86%. Plugged into USB to copy some stuff over, now reads 99%. But still green...So we'll see. Maybe it's just correctly adjusting :P