yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] canteli:
Hello,

i'm having issues with my Nook battery like many (as I understand) after repeated tests over the last couple of days, I can conclude that my Nook doesn't go anything below 24%. When I reach that level, it turns off and will only come back if plugged in. It will power up right away though, rather then have me waiting 15 minutes (which i believe is the norm when the battery REALLY is fully depleted). When it's plugged it will also somewhat jump from ~85% to 100% much quicker than it should, and at the same time, it will discharge faster than it should from 100% to ~85%. One other thing is that I noticed that sometimes it will "recharge" when unplugged by a couple of %age points. I tried to charge to the suppose 100% and recalibrate the battery, but that didn't change anything.

I'm on boot version 1.2 (original), 3.1 beta and OC kernel 300/1200 mhz on smartass. I upgraded to 3.1 beta from nightly 64 I think, wiping only cache and dalvik.

Should I try a fresh install, or rather these new modified boot files that are floating around? The battery life is definitely better than any previous ROM i tried before, but still, knowing I'm only enjoying ~75% of the battery, well, kinda pisses me off :-P

Please advice,

Thanks
[Nook Color Android Development] Rayven01:
Technically you

are

enjoying 100% of the battery life, you're just missing 25% of the battery meter because it's inaccurate.
[Nook Color Android Development] sinanju:
I don't think that's true. Were it so, then after shutdown, when plugging it in, I would think you'd see the "please wait" message until it had sufficient charge to start up. In my case, at least, that did not happen.
[Nook Color Android Development] khaytsus:
That could have been his point, but what he said is still nonsense.
[Nook Color Android Development] :
I feel like the first few lines have to do with the recovery kernel, not the rom one.
[Nook Color Android Development] 12paq:
My Nook generated a last_kmsg file today. Pls see attached.
[Nook Color Android Development] byproxy:
I debated which thread to post this... here or the kernel thread. Hope I made the right choice.

So I was having a ton of freeze ups running 3.1 and the .32 kernel.

I decided to clean install (again) and on a complete guess, skipped the install of beautiful widgets. Amazingly, I think I've had one freeze up since then and have otherwise had perfect performance.

Anyway, just thought I'd share. Maybe BW puts too much strain or something on the cpu with the new kernel or something. Or maybe it's just a freak thing with my particular nook. At any rate, thought I'd share in case others are having the same issues.

I have every other program installed that I had before except for BW, so pretty certain that's what was causing my problems.
[Nook Color Android Development] Arbelzapf:
What governor are you using? I had 2 freezes with smartass, none with ondemand
[Nook Color Android Development] TJNooker:
When you installed 3.1 and the OC kernel, did you restore your apps + data? If so, try clearing the cache and data for BW. Or use Titanium to restore BW but don't restore the data, just the app.
[Nook Color Android Development] smafra:
Hi folks,

I´m trying to connect the nook color on my enterprise network. We´re using a WPA2 Enterprise WiFi network that I managed how to be connected. We use an ISA Server proxy that I need to set up on nc. I know that nc (I use CM7.0.3 and Dal´s OC 1,3Ghz) doesn´t handle that so I decided to use a 3rd party app. I bought ASProxy. This app requires iptables and netfilter... things not present on the kernel.

Since honeycomb 3.1 has proxy setup in native mode, I guess that this shows that the tablets are getting mature to use in the offices.

So, I ask to the developers if those features (iptables and netfilter) could be added to kernel so we can use nc in the enterprise.

Regards,
[Nook Color Android Development] Thirtybird:
I've got a different experience on the battery front from most people here.

I'm running 7.1RC0 Beta 3.1 with the 5/13 OC kernal on verygreens 1.1 SD card install method - this was built from scratch this way and not an update over anything.

Charged to 100% using nook charger, cable light turns green

crank the brightness and the CPU to max, play movies

3.5 hours later, it's still up and going and my battery meter is run all the way down to 5% and no shutdown...

I'm going to repeat this with VG's 1.2.1 SD card install when I have it charged back up.
[Nook Color Android Development] infinityPlusOne:
I too am experiencing this. Many times my NC would completely freeze, and I was forced to push and hold the power button down until it shut off. I noticed it seemed to happen when an app would have to access the internet. So far, I have experienced hard locks like that when going into Google Market, Pulse, GMail. That was with the original beta build. With the most recent build (which I performed a fresh install), I haven't experienced the hard locks, but have noticed that the responsiveness of the OS to have gone way, way down. Definitely hasn't been as snappy as I was used to.

I'll try removing my Beautiful Widgets widget and see if that helps.

Battery life is amazing though!
[Nook Color Android Development] MedLine:
fwiw just completed clean 100% to 0% battery drain. to recap:

* premature shutdown 23% last night, observed battery stat wonkiness reminiscent of what ace described

* wound up with "new" MLO from nookcolor_1_2_update.zip, among other things, then got clean battery drain 40% to 0%.

* charged to 100% overnight, switched over to fattire u-boot.bin and MLO this morning, booted off of this into 2.6.32-beta3 + OC kernel, 300/1200 smartass

* just now ran battery down to normal shutdown at < 1%, no error

maybe it was MLO after all, "new" BN1.2 MLO certainly didn't hurt.

you're probably right, was just curious about that last_kmsg

hey man we're on same side. nuf said. btw i like your portfolio (your sig), been meaning to ask for a while - are you seriously still shooting with 300D? all the more impressive if so.
[Nook Color Android Development] :
Thanks for the writeup. Is the 1.2 from bn the stock one? How do you mean new?
[Nook Color Android Development] taylor.fowler:
New 1.2 MLO uboot Flashable zip

Packed fattire/VG's modified uboot.bin 1.2 with new MLO into one of the B&N 1.2 uboot flashable zip's from earlier in the thread. Just makes life a little easier.

this is the one with the cyanogenmod splash screen at boot.

Enjoy.
[Nook Color Android Development] Ronin3178:
Is this for SD or eMMC or either?
[Nook Color Android Development] MedLine:
hey man thanks for all your work. think that poll you posted got us moving.

don't want to speak for fattire but by "new" MLO i think he means the one from B&N 1.2 Froyo boot, i.e. the one you can extract straight from the B&N nookcolor_1_2_update.zip download. don't know if there's better way to tell them apart, but B&N 1.2 MLO is 16.5kb file, whereas the "old" B&N 1.0/1.1 MLO is 14.1kb file. this morning i made sure and just used MLO and u-boot.bin from the megaupload link fattire posted, mounted boot partition and pushed them over and rebooted.
[Nook Color Android Development] taylor.fowler:
Derp. Forgot to include the MLO part. this just updates the u-boot.bin gonna fix that.
[Nook Color Android Development] taylor.fowler:
eMMC, but right now it just updates the u-boot.bin, fixing that.
[Nook Color Android Development] taylor.fowler:
Fixed. This one will flash the 1.2 u-boot.bin AND the "new" MLO from fattire's post here
[Nook Color Android Development] paleh0rse:
Does flashing that file require a reinstall or clearing of anything else?
[Nook Color Android Development] taylor.fowler:
I just flashed the zip. All it does is replace the two files in \boot, same as if you were to do it manually.

A clear cache/dalvik probably couldn't hurt but i found it wasn't necessary.
[Nook Color Android Development] Rayven01:
This is because it thinks it has more than 15% battery due to the inaccuracy of the battery meter, I would think. The simple fact that it will not turn on without being plugged in means you are definitely getting 100% of the battery life. More, in fact, than you would if it automatically turned off as normal at 5-10%.
[Nook Color Android Development] Ronin3178:
Installed newer MLO/uboot, currently @ 50%, will post results if I get down to 5% or not without early shutoff using battery refresh app.

Ronin
[Nook Color Android Development] paleh0rse:
Excellent! Thanks for throwing that together. I'll be testing it tonight.
[Nook Color Android Development] paleh0rse:
If calibrated properly (ie. Stock), I thought auto-shutdown was supposed to occur at <1%...?
[Nook Color Android Development] seth.i.simmons:
Just flashed it here, ill also post up if I can get past 18% (my last shutdown). It also seems to have fixed my uSD card not mounting for a while after boot, and sometimes not at all till I would start an app. Could have been clearing the cache/Dalvik, idk, but its good to go now!
[Nook Color Android Development] Ophbalance:
I still await the death of my NC. I've logged 22 miles in Torque, and have had it sitting checking a flash enabled page in Opera since someone suggested the Angry birds game. I'm getting close though, I'm at 19% now. I'm lovin' the battery life on this thing. My poor cell would have died hours ago.
[Nook Color Android Development] Rayven01:
Of the meter, yes, but the meter is usually calibrated with a safety margin since running lithium batteries completely dead is generally a bad idea.
[Nook Color Android Development] chisleu:
no.

Now that is an interesting point. I was running smartass as well and have been using on demand for almost a week without a problem. I will change back to smartass now and see if I start having crashes.
[Nook Color Android Development] khaytsus:
Sorry, I'm being obtuse here, but so you previously had u-boot 1.2.0 and the old MLO, and switching to u-boot 1.20 and MLO from 1.2.0 you think fixed the battery calibration issue? nemith suggested I try this today too, although last night I got to 7% before I went to bed and charged.

Actually most of those are 40D, some are 300D still.. I'm way, way behind on updating that image gallery. :eek:
[Nook Color Android Development] Ophbalance:
Mine crashed at 18%... bugger. Mayhap I didn't get the MLO in correctly, because u-boot is showing the new boot animation. Oh well, time to recharge and try again later.
[Nook Color Android Development] omega1alpha:
I'll pass on the Beta for now. I tried the 3.1 Beta and it wasn't as smooth as some people mentioned. I also had issues with charging (charger light seems to always stay orange and never gets to green when complete), overall stability, and I get strange lockups when I get under 30% remaining charge. Back on the older kernel with the 1.3 ghz overclock everything runs smooth as butter and the battery life seems much better these days with the current nightlies.
[Nook Color Android Development] MedLine:
it ain't your gear man, its what you do with it. really nice shots.
[Nook Color Android Development] 12paq:
so true.

funny how many CM7 Nook/Photographers are here.

good stuff. :)
[Nook Color Android Development] newellj79:
Just copied the 17k mlo that is going around, to boot, replacing the 15k version that came in the 1.2 uboot. Will see if it makes a difference for me and report.
[Nook Color Android Development] Ronin3178:
So, now currently around 25%, Nook started getting REAL sluggish. Reboot fixed it. Running 300/1200 ONDemand
[Nook Color Android Development] sinanju:
Screen won't turn on... won't call it SOD

Edit:

It may be that the screen is just VERY sluggish to turn on, sometimes. I know the Nook is awake because if I hit the volume keys, it beeps -- so certainly not a SOD. Holding the N button got the screen to come on with the recent apps displayed.

Just tried it again -- yup... just VERY sluggish to turn on.
[Nook Color Android Development] paleh0rse:
the only problem I'm having now is that HBO GO videos no longer play (with modded framework for 3.1). The blue spinning circle just spins forever after the HBO intro plays... :(

Mine is at 29% with fattire's uboot/MLO... Will post if/when it shuts down.

EDIT: Shutdown at 26%... :( Gonna recharge to 100%, recalibrate battery, and try again.
[Nook Color Android Development] TheMainCat:
Does the "new" MLO play nice with the "old 1.2 uboot.bin? I kinda like the "Read Forever" splash screen.
[Nook Color Android Development] newellj79:
No problems here.

Edit: clarification.... NC functioning fine. Still don't know when it will shut down in regards to battery indicator, its rare my NC gets that low on juice.
[Nook Color Android Development] Arbelzapf:
Damn, didn't work for me. Flashed the new uboot and mlo and still had a shutdown at 20 %. I really hoped this would do the trick.
[Nook Color Android Development] Xhorder:
FWIW:

Running (multi)u-boot 0.3, beta3.1, .32 OC Kernel @1.1Ghz Ondemand. I played angry birds until I got the 15% battery warning popup, and then it shut down a couple minutes later.

After plugging it in and rebooting, the battery meter showed 16%
[Nook Color Android Development] xxiworld:
Hmm . . . very disappointing. Thanks to fattire for posting the MLO anyway.
[Nook Color Android Development] fattire:
Damn. It worked for me. Back to the drawing board I guess...
[Nook Color Android Development] xc68000:
Loaded up that MLO that was posted. One problem I am noticing is that nook gets real sluggish after watching a netflix video. I have to reboot to clear it. I don't know if its related, but I dont recall having that issue before.
[Nook Color Android Development] Ronin3178:
I didn't watch a Netflix video before it got sluggish, I think I was playing angry birds. But I am still here, currently @20% :D
[Nook Color Android Development] xc68000:
I'm at 30%. I reproduced several times. While on battery I rebooted, and gave the nook time to settle down and started up netflix. First video plays fine, but as soon as I go exit and go back to the launcher everything becomes sluggish and I have to reboot.

Then I plugged the AC adapter in and everything started working correctly. Was able to reboot, play videos with netflix, exit, come back in and no issues what so ever.

I only left the AC plugged in for about 5 min while I tested and the batter charged to 35%. Then I unplugged and retested (no reboot) and everything was still working fine...went into Netflix several times and played videos..no issues.

Rebooted (still no ac adapter) and retested and everything still works.

Kept testing and as soon as the battery hit 30% again, all of the stuttering came back. I have no idea whats going on at this point :(
[Nook Color Android Development] botossi:
Quick question.... is the profiles from SetCpu (2.13) good to go on this build ?

Thanks!
[Nook Color Android Development] tomtbone:
anyone have a flash version that works well? I can't seem to get 10.3 or 10.2 to work.

also, anytime I hit the batch operation button in Titanium backup, I get a force close right away.
[Nook Color Android Development] botossi:
I would suggest you to use the 10.1 from Stock 1.2... it works pretty well with HW enabled !!! someone already posted it here... or you could check the HBO thread in APPs !
[Nook Color Android Development] tomtbone:
not seeing it there sorry.
[Nook Color Android Development] Ronin3178:
Ok, success for me on the new MLO/uboot. Flashed @ 50% battery, had the sluggishness around 26%, fixed with a reboot. Went to test netflix cause of sluggish behavior around 10%, it did cause it. I was on 300/1200 OnD, performance appeared to fix it. Smartass wouldn't fix it. got the no warning shutdown @ 9%, plugged in and got the "Charge" screen....relative success I would say.

Thanks fattire!

Ronin
[Nook Color Android Development] khaytsus:
I've seen pros take great shots with disposable cameras and idiots take terrible shots with $9000 cameras ;)

SetCPU is still not behaving with CM7 as far as I know... What's wrong with one of the available CPU governors?
[Nook Color Android Development] :
Smartass is a setcpu profile. You don't want setcpu profiles on here yet ;)
[Nook Color Android Development] tomtbone:
Thanks the flash 10.1 from the Netflix post works great. Watching streaming bruins game!
[Nook Color Android Development] newellj79:
Could u please post a link? I looked thru the whole thread and didn't see it.
[Nook Color Android Development] seth.i.simmons:
Same here, my Nook slowed down so bad I had to reboot, but after watching another video, it seems to be fine. One problem I'm having though is that Netflix is terribly choppy, but it was perfect before :( Any ideas on how the new MLO could affect these things??
[Nook Color Android Development] deadbot1:
Gotta say I'm loving life so far...last on charger at 6 am Tuesday...still at 50% after a few(3ish) hours of reading, some Trailer Park Boys on Netflix, and some web surfing...freaking awesome. Flashed the latest uboot/MLO and switched to ondemand...no issues so far...will keep at it till she drops out now....

A side note...no sluggishness after Netflix for me...
[Nook Color Android Development] seth.i.simmons:
It seems my sluggishness is mostly fixed, although I cant seem to get Netflix to play smoothly again. Any suggestions??

Edit: My sluggishness is NOT fixed. Still slows down a lot after watching Netflix, and Netflix is unwatchably stuttery. :( really sucks, since I was killing some Netflix in my free one month trial :P if anybody figures out a way to fix it, let me know! Thanks guys.
[Nook Color Android Development] tomtbone:
Same here on latest mlo. After video(YouTube) , very sluugish, then rebooted and fast again
[Nook Color Android Development] angomy:
I'm having the same issue with Netflix (basically anything that uses Flash -- Hulu, Netflix, Dramafever) and having to reboot my Nook because everything is slow even after exiting (checked running apps, nothing there).

Using 2.6.32 beta1 with standard kernel (not Dal's OC), Flash 10.3 on verygreen's 1.2.1 (with 1.2 u-boot bin) SD install. Wasn't having this issue running stable 7.0.3 though once I upgraded to 10.3 flash my videos were stuttering like crazy, but system would respond as normal after exiting the app.

Still having the same performance issues using 10.2 flash :|
[Nook Color Android Development] seth.i.simmons:
Ill also go ahead and say that I've tried wiping the cache/Dalvik cache, and fixing permissions, but still a no go. Not sure what else to try at this point!

Edit: YouTube also stutters some now, which it has never done for me on any rom or flash version. Seems like this new MLO screwed me over :\
[Nook Color Android Development] sinanju:
It seems that if I explicitly turn off WiFi before I turn off the screen, I don't have a problem turning it back on. If I let it time out, problems getting the screen going happen pretty frequently -- letting it sit for a little while seems to help.
[Nook Color Android Development] joenathane:
I'm having the same issue with the sluggishness after flashing the modded mlo, strange how much effect that little file can have... I'm now trying the stock 1.2 mlo to see if it's any better...

edit: so far i'm not seeing any of the performance issues with the stock 1.2 mlo... netflix is working great...
[Nook Color Android Development] deadbot1:
Eh...spoke to soon. Watched some more TPB then switched to a movie from SD...very stuttery. After leaving that I had a wifi dropout...reboot cured all. Still at 32% after almost 3days off charger...now with almost 2 hours of video in as well...hope these little bugs get sorted...I'm loving it.
[Nook Color Android Development] rhester72:
MLO ain't it. I'm on VG 1.2 with the new u-boot and old MLO and can easly get my battery below 15% (complete with pop-up alarm) on beta 3.1 without ever having recalibrated my battery. I don't know what other effects (if any) that MLO might have, but it doesn't appear to be contributing to the battery issue, unless I somehow have a SuperNook(TM). :)

Rodney
[Nook Color Android Development] TheMainCat:
I am not seeing "sluggish" behavior before or after playing a video (Netflix, YouTube, moboPlayer). I am running 3.1 beta, OC 1200 - ondemand, new MLO, and "old" 1.2 u-boot.bin. Don't know about the "sudden" off issue, since I am still at about 70%.
[Nook Color Android Development] deadbot1:
Well..here's how I stand now...3.1b3, 1.2 uboot and "new" MLO, oc at 1200.......

Video is stuttery, battery life is phenomenal, sudden shut off at 19%....

Edit: no last_ kmesg...

I have only had one of what I would call a true SOD. Everything else has been just screen state queerness or general video stuttering. I say video stuttering because I haven't noticed any other lagginess.
[Nook Color Android Development] fattire:
Those who see stuttering video-- does anything show up in logcat/dmesg during/before/ or after the stuttering episode?

Seems from what I can tell that the stuttering issue is independent of mlo/uboot versions. Similarly, I don't see any consistency in battery shutoffs w/relation to mlo/uboot versions either. Happens to people w/ both (and doesn't happen to people w/ both too).

I think some logs may be the next place to look (?)
[Nook Color Android Development] deadbot1:
Ok...will post logs as I can.

Edit:....getting the sluggishness now....Netflix definitely trigger....

http://db.tt/xT9r83m dropbox link to log....

This one will be better...shows video before and after Netflix...http://db.tt/Si4mShG
[Nook Color Android Development] joenathane:
Getting official http://review.cyanogenmod.com/#change,5085

progress is sweet!
[Nook Color Android Development] greenmky:
Yay

Waiting for a stable or at least a nightly with .32 before I migrate from 7.0.2 stable.
[Nook Color Android Development] fattire:
I'm guessing things will be pretty bumpy with the next few nightlies. I'm not sure which checkin(s) broke the nightly builds of late, but maybe the inclusion of this .32 stuff will bring back some usability. Usability != stability though, so I'd not stray from 7.0.2 or whatever for a little while.

Looking at the "stuttering" log posted above, I see a lot of "D/dalvikvm( 2165): GC_CONCURRENT freed 500K, 49% free 3164K/6151K, external 559K/1071K, paused 3ms+3ms" Do these coincide with the stuttering?

GC = garbage collection. This is something dalingrin was looking at lately, esp. w/regard to the stuttery scrolling of some listviews. I wonder if the bump to 2.3.4 changed garbage collection behavior or something...
[Nook Color Android Development] angomy:
By process of elimination, it really looks like it's something in 2.6.32 beta1 (with or w/o the OC kernel, I'm getting the same results) that's causing my Netflix/flash woes. Used same 1.2.1 verygreen base SD image (1.2 u-boot), but flashed nightly 75 with ext4 OC .29 kernel. Used same flash versions (10.2, then 10.3.today'supdate) with same Netflix app (rev 2 of no device check), and it's running flawlessly. Also tried some videos at www.dramafever.com (flash-based) and again, flawless, no system-wide slowdown or any stutter at all.

Edit: Downreved to 7.0.3 stable / 4/24/11 OC kernel and all flash-based/Netflix issues gone still. When I revved to nightly 80 with .32 OC kernel (would not load for me without .32 kernel on VG's SD install) I had the same stutter/slowdown issues as before with beta1. I love the deep sleep of .32 but can't give up the streaming videos for now.
[Nook Color Android Development] djxcee:
By installing this are we automatically converted to ext4?
[Nook Color Android Development] timoskrempel:
I switched to bn 1.2 uboot, beta 3.1 and oc 051311. I am having wifi problems: the connection stops working after a few minutes even though it thinks it stays connected. Toggling wifi off and on fixes the problem for a few minutes. Ran fix_permissions, deleted some apns and readded them, nothing helps.

A minute ago I got a kernel panic, when I turned off wifi: http://pastebin.com/9yfwR1nC

I hope this helps.

edit: running on emmc.