yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] iDidItAll4theNookie:
Finally bit the dust at 6%. Just turned off, and when I plugged in, it gave me the "battery too low, please wait" message. It the started up a few minutes later on its own.
[Nook Color Android Development] phamurai:
I'd just like to say that this is the most ridiculously functional "beta" I've ever run on a device. Thank you to the devs for all your hard work.
[Nook Color Android Development] TJNooker:
Battery issue (update)

@fattire

Battery Calibration: I used Nema's Battery Calibration after updating to the Beta/u-boot 1.2/oc kernel. I followed the SOP to the letter.

Settings > Applications > Battery Use: I checked this out last night and everything appeared to be normal. The screen accounted for the vast majority of battery use. A bunch of common applications accounted for the rest.

It Happened Again: I fully recharged my Nook and used it throughout the day today. This evening I started playing a game ~40% battery. After an hour the screen went black without warning. Just like before I cannot revive my Nook with the power button, or any button for that matter. I don't have my charger with me so I can't revive my Nook until I get home.

UPDATE: After reviving it with the charger, the battery level was 27%.
[Nook Color Android Development] 12paq:
agreed!

.
[Nook Color Android Development] altimax98:
Is anyone's Netflix running smooth on this beta? Mine is real choppy :-(
[Nook Color Android Development] :
QUESTION TO THOSE WITH RANDOM SHUTOFFS:

1) If you've "fully charged" after a random shutoff, does the cable glow green?

2) At what point (percentage) did it shut off?
[Nook Color Android Development] GabbleRatchet:
Couple days ago, charged until green. Shut off at 20%. Wasn't sure what was up, let it charge briefly. Only hit about 30%, promptly died again the next time it hit 20. Charged fully (to green light) & reset battery stats in cwr. Today it got to 6% before it died.
[Nook Color Android Development] TJNooker:
Now I'm just a user/tester, so take my opinion with a grain of salt, but I think you're probably right. Just from reading the last four pages of this thread, the move from 1.1 to 1.2 u-boot seems to be the culprit. I just hope that this issue can be resolved without reverting back to stock BN 1.2 and starting over.
[Nook Color Android Development] 12paq:
I get shut downs and sod or sod-alike events at random charge states. The only thing I can reproduce is having the screen off and plugging in the stock charger and the screen goes dark but lighted behind, as others have reported.

3.1 , 1.2, 5/13oc

Still a great build and good progress. runs smooth like butta'
[Nook Color Android Development] :
So everyone is clear, SOD is not the same as random shutdowns. SODs can be powered back on after a hard reset. random shutdowns require actual power.
[Nook Color Android Development] fattire:
Was this with the original mlo or did you try the newest one?
[Nook Color Android Development] angomy:
FWIW, I ran Dungeon Defenders First Wave for the first time since installing beta1 on the same card I had had stable on. It was unplayable (super choppy, menu lag, etc). When I exited out (menu exit, not N etc... etc..) everything was running sluggishly -- Koi live wallpaper was chopping up, distinct lag between pressing any menu options or apps.

Rebooting cleared up the issue. This issue didn't occur when I was running 7.0.3 stable. (Running @ same performance settings, 300/925 ondemand).

Wondering if it's related to the Youtube / flash video issues / system slowdown some people are reporting.
[Nook Color Android Development] racks11479:
Dalingrin,

I'm still running on CM7 v3, but would you mind taking a look as to how I got my market to show apps? Could it be a combination of the framework patch I used and this new apk I found?

Asking because I feel this relates to the development of CM7 regarding the market issues.

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

Thanks,

Racks
[Nook Color Android Development] Chahk:
Running build #5, and my Market can't see protected apps. After trying racks' framework patch, it saw some of them and allowed me to update, but after a reboot it went back to not seeing them again. Both times the list of installed apps was empty.
[Nook Color Android Development] racks11479:
Did you try installing the my marekt APK as well?

**Edit: OK, after 3 reboots, my apps weren't showing again. What I ended up doing to get it to show again was to go into Settings-->Applications-->Manage Applications-->All-->Market-->Uninstall Updates. Once I did that Market was showing my apps again.**
[Nook Color Android Development] bonobomidwest:
There's other posts reporting that AES doesn't work and that people have to use TKIP (which is a pain given the security hole in TKIP), but it is better than nothing.

My N betwork is running on a NetGear WNDR3300, WPA2/AES/PSK

My G network is running on a D-Link WBR2310, WPA2/AES/PSK

The D-link router has a lot of non-standard setup options for G (like "turbo mode") if you read the manual this involves all sorts of non-standard goofery. I just tried setting it to the super duper D-link options, and not only did the NC refuse to connect, but it half an hour later it appears to have shafted the router too :)

So i can at least replicate a part of your misery with my D-link router by enabling all of it's non-vanilla options.

Do you have a friendly neighbor or a spare router or some way of testing whether this is D-link specific - i.e. see if WPA2/AES/PSK works on a different brand of router?
[Nook Color Android Development] diomark:
I have two different dlink routers - a dlink gaming router dgl-4500 and a DIR-825 - AES doesn't work on either:( (but then again, they're both dlink..)

-mark
[Nook Color Android Development] KitF:
I always had terrible luck with D-Link. Their routers were always pieces of crap for me. WPA2/AES works fine on my Linksys.
[Nook Color Android Development] digitalslacker:
so i installed your market APK last night...

just uninstalled the market updates, rebooted, apps are there.

rebooted again, clicked 'my apps', market force closed, went back in, my apps are gone again.

went back in to the settings > applicaitons > market and the uninstall updates option is back...I guess the market auto updates and thats related?

side note, not sure if this troubleshooting is helpful to the devs or not so please let me know if this conversation should be moved into General Discussion. I don't want to clutter this thread up with stuff that isn't useful to the folks working on it.
[Nook Color Android Development] zetaepyon:
I use a D-Link DIR-655, and initially wasn't able to get it to connect, despite the strength of the connection.

I switched the router to 802.11g-only mode instead of mixed-mode, and now it works flawlessly. It's set to WPA2/AES, as well, and CM7 nightly v4 has not had a problem connecting at all. I made this change based on suggestions for the stock B&N rom (I think), but it seems to have been effective.

The network problem that I'm seeing is at work, where we have an open visitor wi-fi network that has a log-in screen. For this network, it just goes between scanning and connecting, without ever even getting an IP. I did not have this problem with a rooted stock ROM, I was able to get to the log-in page just fine, and then use the network normally. So, I don't know what the deal with that is.
[Nook Color Android Development] aludal:
LOL! It would be the first time I witness the little mighty Nookie "shafting" a router :)

Seriously, why not use a DD-WRT-capable router? Fry's has a junk D-Link 615 rebrand for mere $29, it gets DD-WRT just fine, and never had any problem with b/g/n connectivity.

My congrats to your Nookie screwing lousy routers left and right, lol

A story of DD-WRTing of a cheapest router is in my fineoils.blogspot.com blog, everyone is welcome, as there are some of my tips not found in "official" DD-WRT forums.
[Nook Color Android Development] diomark:
For what it's worth - I've had good luck w/ the high-end dlink routers. I don't have connectivity problems from any of my other 20million gadgets in the house:)

-mark
[Nook Color Android Development] bga7x:
so I am in the Middle of porting my theme to the Theme engine, I should wait?? cause I started to convert my images to mdpi. if we are going back to Hdpi you have made me a happy camper!!

bgill55
[Nook Color Android Development] tominabox1:
bgill - I believe HDPI images will work ok. Current HDPI themes work for the most part so I'd say you're all right.
[Nook Color Android Development] Khegobier:
nm, figured it out.
[Nook Color Android Development] bonobomidwest:
Hee hee. Not the NC. I think the router fell over its own fancy protocols...
[Nook Color Android Development] aludal:
Yeah, I was just kidding.
[Nook Color Android Development] j4mm3r:
Yea that set of WIMAX commits broke a lot of stuff here and there... all normal now.

Just pulled the latest commits and the build is good.

Market working.. seems that the device id fix is working!!! Get it all in tomorrows nightly... unless something else breaks... but hell thats what everyone signed up for ;-)
[Nook Color Android Development] tominabox1:
anybody install #7 yet? I am formally disliking the HDPI/LCD density change. The market update was great but now the themes from the engine are more broken than ever and google reader doesnt work right, and now instead of using native MDPI images, its scaling HDPI images so lots of the graphics are blurry. I hope this doesnt stick. Hope I'm not the only one who disagrees with this course of action.
[Nook Color Android Development] Chahk:
It's a work in progress. The scaling does look strange, but I believe it's a short-term work-around for dodgy 2D scrolling.
[Nook Color Android Development] tominabox1:
yeah I shouldn't be freaking out. I'm just nervous it will stay weird and I'll not like it. I need to get a life. sorry folks.
[Nook Color Android Development] burbank:
I am really liking #7. Did a complete wipe and installed #7 fresh. Lots of things fixed. Things that still don't seem to work include video, wireless setting crashes. Status bar is back. Market seems to work great. I installed this, gapps, and the 1.1gHZ overclock. All is well. Nice job, Devs.
[Nook Color Android Development] :
Where can I grab the latest one?
[Nook Color Android Development] TJNooker:
What he^ said. I wasn't aware there was a new mlo. Unless it's in the 1.2 u-boot that was posted 10 billion pages ago, I'm using the old mlo.
[Nook Color Android Development] Deaks2:
1) Yes, the cable always glows green (100% battery) when I unplug it.

2) The first time at around 30%, today it died at 24%.
[Nook Color Android Development] TJNooker:
1) Yes, it glows green upon full recharge after random shutdown.

2) The first occurrence was 30%; the second was 27%.
[Nook Color Android Development] bekyndnunwind:
Would love to try a different MLO...
[Nook Color Android Development] MedLine:
wow, i got shutdown at 23% too. did following experiment:

* installed 2.6.32-beta3 + 2.6.32 OC kernel to verygreen SD v1.21 ("new" MLO)

* booted back to eMMC 2.6.32-beta3 + 2.6.32 OC kernel (new u-boot.bin, but "old" MLO)

* ran down battery, same shutdown at ~20%.

* plugged in charger, eMMC booted up fine ("old" MLO), battery 19%, powered down.

* inserted verygreen SD ("new" MLO), now won't boot up, get "not enough battery, wait 15 minutes" message

* 15 minutes later eventually boot off SD ("new" MLO), but battery says 11%.

so is "old" MLO problem? i upgraded to BN1.2 uboot like everybody else just replacing u-boot.bin.

btw still haven't had another SOD since the one from last Saturday AM.

EDIT: i'm assuming verygreen SD v1.21 would have "new" MLO

2nd EDIT: hmm ... maybe not, verygreen SD showing MLO 14.1 kb, whereas MLO 16.5 kb from nookcolor_1_2_update.zip. mounted boot partition, copied MLO from nookcolor_1_2_update.zip over, will reboot and try battery run down test again.
[Nook Color Android Development] Hiro666:
Hmm. Currently showing 18% and no SOD. Curious how low she will go. Stay tuned!
[Nook Color Android Development] deadbot1:
Mine runs just fine...except for the first minute is very pixelated....probably a network speed problem rather than anything else.

Hope all the bugs get swished...two days off the power tit...82% with light usage...damn that's sweet.
[Nook Color Android Development] nukeruss:
A little battery data

Two days since last charge with light use and hanging in CM7, Battery read 75%. I rebooted into BN 1.2 and after it settled in, battery was 74%. I then rebooted after 10 minutes into CM7 and battery read 73%. Started with Cm7 7.03, installed BN 1.2 over over it, set up dual boot and copied BN 1.2 TO 2nd boot, installed beta over BN 1.2 on first boot. Did this on 13th and updated to dual uboot v3 when it was released. Overclocking 300/1200 ondemand. Zero issues.
[Nook Color Android Development] Ronin3178:
The fix for the pixelated netflix, skip forward/backward, doesn't matter. It fixes the res problem, everytime.
[Nook Color Android Development] GabbleRatchet:
SOD has nothing to do with battery %. Two different issues.
[Nook Color Android Development] EnTg888:
In case anyone wants to try the new MLO, or accidentally flashed /boot, I made this file when I accidentally flashed /boot. It simply flashes everything in /boot with what was in there from the stock BN 1.2 firmware.

Make sure to flash CM7 over again after flashing this, it also replaces the kernel files

However, I've been using this MLO for a while, and still had a shutdown when the battery was not in the red yet.
[Nook Color Android Development] Hiro666:
Made it as far as 14% and my unit just shut down as has been documented here. Therefore, this symptom is consistent in its occurrence but not consistent at what percentage it happens.
[Nook Color Android Development] Hiro666:
Thanks for setting me straight.
[Nook Color Android Development] MedLine:
yeah, i don't get it. charged to 40% and booted off BN1.2 u-boot.bin + BN1.2 MLO into eMMC 2.6.32-beta3 + OC kernel. this time it ran down to 15% to get "battery low" warning, then kept going to 1% after which it shut down after 2 minutes, which is normal. however, the battery stat numbers "looked" right after round-tripping through verygreen SD installation of same thing, before i ever switched over to the "new" MLO.

anyway you look at it this is great news. suggests that maybe a sizable percentage of presumed SOD were just premature shutdown from a battery stat bug, whatever is causing it.

my personal SOD running total is still just 1 SOD against probably 350 standby. once i quit going out of my way to go into standby that probably averages out to 1 SOD / month. if this holds up that's an EPIC win.
[Nook Color Android Development] sinanju:
MP3 playback drops-out frequently...

I upgraded just before my trip home from China. Video was lovely. Battery life in sleep was lovely.

MP3s drop-out frequently. I was on a plane, so wifi activity was not an issue. I tried three of the governors -- smartass, ondemand, conservative -- there was no discernible difference. I haven't has the chance to hook it to my laptop, so I have no logs yet. I'll try to post them tomorrow.
[Nook Color Android Development] sinanju:
Got the shut-off at 29% after reading this thread and running down the Nook. Interesting that there wasn't the "too run down to boot, try again in 15 minutes" message after plugging it in and hitting the power button. It certainly seems the meter is correct, initially, and something else is afoot.
[Nook Color Android Development] TJNooker:
Here goes...

I'm giving this a try.

I downloaded your file, Beta 3.1, Gapps, & the OC kernel. I cleared cache, flashed the files in that order, and then cleared dalvik cache. I'll let you know what happens when the battery approaches 30%.
[Nook Color Android Development] boogerboy72:
running phiremod 6.2 got the sod @ 30% last night. plugged in, did a hard rest and everything is as normal.

i ran the latest beta/uboot for about a day, ran into issues and restored phiremod,
[Nook Color Android Development] fattire:
I'm currently at 16% with the new mlo, playing pandora at top volume w/screen on to try to run it out, and so far no shut down. It's in the red zone tho.

Update: Just got the "Please connect charger" 15% warning. Good! Plugging and unplugging re-gives me the warning. Gonna charge it back up now :)

Here is the "new" MLO (x-loader) I used. It's new in the sense that it is built by me from BN's latest source drop that came with stock 1.2 without any changes, and I assume it's similar if not identical to the one in the 1.2 distribution. If you're a developer/tester who's had problems with the spontaneous battery-related shutdown w/.32 and a new u-boot and you came directly from CM7 or another OS other than stock 1.2 (thus using the previous mlo), this may help. Then again, it may not. Seriously. It may do nothing, or worse. I guess that's what I'd like to find out.

No guarantees of success by any means, but it did seem to work for me, at least on this one go. With the long time to charge and then use up the battery, it's not something I can easily test quickly.

If you choose to try it, you accept that it's entirely at your own risk. Read the GPLv2 for disclaimers. Be sure to back up your old MLO and have a bootable SD card ready just in case something goes wrong.

If you don't know what to do with mlo-- I won't go into too much detail but you'll find it in /boot along with uImage, u-boot.bin, etc.

Incidentally, nemith and others have talked about packaging u-boot and mlo into nightlies, since (at least) a newer u-boot will apparently be needed for .32. A question is which features should be added to u-boot. Nemith started a thread on this, so check it out.

"new" mlo.tar.gz built from 1.2 source drop (with no changes)

"new" u-boot.tar.gz (built from 1.2 source drop with splash and changes from myself and verygreen)
[Nook Color Android Development] breebauer:
1) yes, not sure when though.

2) both times it was at 23% when I plugged it back in.

Side notes:

- After the 1st time, I charged it to 100% and cleared batt stats in cwr.

- Both times after it's shut off like this, I let it charge for a while, but after I unplug it, it says it's still charging- even though the % is decreasing. Weird.

I'm not sure if rebooting would fix it, going to try that now...

Yup- hard reboot fixed it.
[Nook Color Android Development] chisleu:
I had this issue. I did a complete format/reinstall and haven't had it happen since. I went from CM7 nightly to beta 3.1 & "Read Forever" boot from 1.2 at the same time.

Since format it's been working great (formatted Saturday night, almost a week ago and no problems.)

I would like to upgrade to your u-boot anyway and install this mlo for testing, but I can't find install instructions anywhere. I checked that other thread too. :)
[Nook Color Android Development] Ophbalance:
Looking at the CWM script someone had set up for the stock 1.2 u-boot, if you mount "/" as RW you could then:

mkdir -p /boot
mount /dev/block/mmcblk0p1 /boot

If you then have mlo/u-boot.bin on your SD card or dropbox or ADB, you could then rename the current ones, and add the new ones and reboot. To clarify, both mlo and u-boot.bin reside in /boot.

I've not yet tried this, but will be doing so shortly. It actually looks really straight forward to modify a CWM script to do this as well.

EDIT: Please, please be aware that without a script to restore /boot (and there's a few floating around here, I know that there's at least one for the 1.0 stock and also the 1.2 stock) that change these files incorrectly will make for a Bad Day (TM).
[Nook Color Android Development] Ophbalance:
Cool, so I got the new boot animation and the system booted back up. I presume everything is all good and such. I'm at 98% charge though, and since I've plowed through all my current reading I don't think I'll see a number below 30% for at least another day.
[Nook Color Android Development] Ronin3178:
Play some angry birds, that will keep you going and use the battery fairly quickly. :D
[Nook Color Android Development] Arbelzapf:
I'd say emulators, namely FPse or n64oid.

Another good benchmark is an app called Fleya. On my device, it really shows the difference in performance between ondemand and smartass. With ondemand, it plays pretty fluently, on smartass, it's more jerky.
[Nook Color Android Development] martian21:
Made the jump to the Beta 3.1 last night and it seems to have fixed my wifi issues however I keep getting Force Closes on the XDA app!?! I committed a cardinal sin in that I restored app+data in Titanium so I have nobody to blame but myself.

Is anyone else having Force Close issues in the XDA app on Beta 3.1? Just curious before I format and reflash (and not do things I no I shouldn't in Titanium...)

Thanks,

Martian21

ps. I've cleared app data for the XDA app and uninstalled, cleared Cache and Dalvik and fixed permissions in Clockwork and re-installed the app from the market - still no go.
[Nook Color Android Development] Ophbalance:
Well, I lost 8% to Torgue driving my kids to preschool. Although angry birds is fun, I just don't have that much free time on my hands at present ;). However, I'll probably load up Opera and just let it sit n' spin on my site monitors. That ought to drain it fairly quickly.
[Nook Color Android Development] ansleyj44:
I could be wrong but I believe this is something that's been an issue with cm7 for quite some time now, not just with the beta release. I think the only workaround ( at least what I use) is to just use the tapatalk app.
[Nook Color Android Development] sinanju:
It has never worked for me... FCs whenever I try to read a thread after authenticating. I try after every flash. I don't think anyone looks at the crash reports.
[Nook Color Android Development] niphoet:
I have been using it without a problem in beta3.1. I have the paid version, not sure if that makes any difference.
[Nook Color Android Development] khaytsus:
Nonsense :( This premature battery shutdown thing has nothing to do with SOD. If you can power it off and back on without ever plugging in, obvious the battery was not dead.

This premature battery issue is a calibration problem from something, hopefully fattire has gotten to the bottom of it with mis-matched files or such, we'll see. I'll try his new files tonight when I get home, however...

I got down to 7% last night and plugged in for bed. I just replaced u-boot.bin with fattire's version, didn't replace any other files in /boot, and I'm on 2.6.32 beta 3.1 on eMMC now.

Only semi-strange thing I've seen was charging went from 95% to 100% in one jump at the end of the charge cycle. I guess I'll see how low it goes this cycle.
[Nook Color Android Development] joenathane:
I think his point is that people have been labeling just about every problem they have with 3.1 Beta as the SOD, and that the actual number of real SOD's are far less than perceived.

Personally, I haven't experienced the SOD but I have had the battery issue...
[Nook Color Android Development] :
What joenathane said.
[Nook Color Android Development] RoboRay:
I do get amused when people tell somebody they're wrong and then agree with everything they said. :p
[Nook Color Android Development] MedLine:
hey take it easy, buddy. i'm with you all the way. nice post, though, gotta keep those 2.6.32 beta bashers at bay.

my one SOD was from last Saturday which i described here and had dutifully sent all recoverable logs. none since.

speaking of logs did anybody look at ace's last_kmsg from couple days ago, still curious as to why kernel identified as 2.6.29 (first line), looked for all the world like it came from one of the 042311 OC kernel build.

.... anyway, charged to 100% this morning, charger light green, running "new" MLO, draining battery looping chisleu's 480p 2000K Miss A video with Act 1 at 100% brightness as we speak, will report back in few hours.
[Nook Color Android Development] 12paq:
lol

. . .