yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] 360Razir:
+1

..............
[Nook Color Android Development] RoboRay:
One does not need to be a moderator to read and comprehend past statements by moderators.
[Nook Color Android Development] fattire:
Yes, so anyway....

Did anyone try the custom u-boot I posted pre-flamewar? Any problems?
[Nook Color Android Development] khaytsus:
I downloaded but didn't try it yet, as I didn't quite understand a few things, but if you'll clarify I'll put it on tonight. :)

What should I be looking for in improvements vs the 1.2.1 update zip he has in his SD agnostic package? And the out of battery? That's controlled by u-boot? Is that the "Battery too low to start" screen?

And if it goes wrong, no biggie.. That's what I love about the SD installed CM7. Super easy to fiddle with this stuff with no consequences or fixing.. :) But I guess internal isn't that much more difficult, boot a CWM SD and get in and fix stuff.
[Nook Color Android Development] victle:
I tried this with SD installation, I could reboot to recovery but lost ADB connection. Hope that helps.

Update: Never mind, this is not related to the u-boot.bin, re-install the driver get ADB back :)
[Nook Color Android Development] newellj79:
Trying uboot now.
[Nook Color Android Development] geekyradical:
So, I am not running the OC kernel, but I am running just the beta, and I am not getting deep sleep like everyone else. Any ideas as to why?
[Nook Color Android Development] newellj79:
fattire... i just tried your custom uboot. I still had adb connectivity however video stutters noticably more. I'm not sure what kind of changes to look for however, that's just the first things i noticed.
[Nook Color Android Development] fattire:
Im not sure if verygreen put out his uboot changes separately... this should include anything he did tho.

Yes the battery message is generated by u-boot. It checks to make sure you have sufficient battery when you boot, and if you don't it will show one of two screens, either a PLUGIN screen to tell you to plug in, or a CHARGE screen to tell you that your'e plugged in but have to let it charge a little more. I replaced both images with new ones, as well as the regular BOOT screen. Since I was fully charged, I couldn't fully test out the other images.
[Nook Color Android Development] fattire:
I don't think it should affect video at all. Should be stock 1.2 in that regard. The kernel should be identical to whatever .32 you were using before. What I'm mostly wondering is whether the startup splash graphic worked.
[Nook Color Android Development] iDidItAll4theNookie:
Maybe someone could make a page that makes you take a quiz about installation before the download will begin. Don't pass, no download. :p
[Nook Color Android Development] fattire:
That's a funny idea.. You have to answer 3 questions right to get the download location hehe.
[Nook Color Android Development] Divine_Madcat:
What is your name?

What is your quest?

What is the air-speed velocity of an unladen swallow?

:D
[Nook Color Android Development] RoboRay:
What do you mean? African or European?
[Nook Color Android Development] victle:
fattire, my report of ADB losing is false alert. Probably it's my computer, re-install USB driver got it back. As for the startup splash graphic, it showed up when boot but no animation, right?
[Nook Color Android Development] Colchiro:
What's with the Gingerbread reference? :D

I'd like to have a 1.2 u-boot (EMMC) with a custom graphic, anything other than text. Why doesn't that exist?
[Nook Color Android Development] KitF:
My Nook seems to be SOD? Dying? I don't know. But it's off whenever I wake up. And then when I plug it in to charge it and turn it back on, it shows it still has like 50% battery life. This is with the 3.1 beta + 5/13 overclock.

Is this a known issue? I don't see how I can grab logs as it only seems to happen while unplugged for hours at a time.
[Nook Color Android Development] fattire:
That's what it is.

Yup.. Graphic. No animation, as u-boot can't do that.
[Nook Color Android Development] iDidItAll4theNookie:
So far the build has been quite reliable. I charged it last night when it hit 30%, which took 2 days of relatively frequent use. This morning I had the green light and 100% battery. After 8 hours of sleep, it was at 97%. No FCs really to speak of. The only issue that I can find is that the lock screen shows at phone size, so I'm just not using the lockscreen. Top notch work.
[Nook Color Android Development] paleh0rse:
Same exact behavior here... plus one SOD that required a hard reset (no associated kp in logs... No kmesg at all, in fact).
[Nook Color Android Development] bekyndnunwind:
Just woke my nook up from a 20 hour sleep....there was no notification bar. Couldn't get a log because i couldn't hit the menu button to export one, etc.
[Nook Color Android Development] mjb413:
I have had that issue before. A full restart fixed it for me.
[Nook Color Android Development] MedLine:
reporting back. no SOD since Saturday AM. brings my running total = 1 SOD / ~275 standby with 2.6.32 betas past week.

actually, i'm not sure dmesg kernel dump to /proc/last_kmsg enabled with the 2.6.32 beta builds ... just realized the last_kmsg i sent to dalingrin, following my SOD, was from 04/23/2011, probably from CM7 n54, and was still around because i flashed only formatting cache.

YMMV but after SOD on my Nook, i can plug in to USB and get ADB. so basically my SOD follow one of 2 patterns:

(1) on CM7 2.6.29 (nightlies/stables), i can disable the userspace wakelock and induce SOD with every standby. the screen does not come on, all physical buttons are unresponsive, and screen touch unresponsive. plug in USB, however, and system will resume, still nothing on screen but I can get ADB, after which i find what looks like normally functioning system. all logs can be accessed. i can even get button press events running, for example

"adb shell input keyevent 3" will bring the screen back, and "adb shell input keyevent 82" will get LP to offer me the chance to change wallpapers or LP preferences, but i've never found a way in userspace to get functioning screen touch back.

(2) on CM7 2.6.32 (beta3.1), the one SOD i've experienced was subtly different. screen did not come on, but physical buttons remained responsive, and looking back i wish i had blindly jabbed at the screen, e.g. at approximate locations of some dock icons, to see if screen touch was still working. i couldn't get the screen to come on, but in any event i was able to connect USB and ADB for logs.

hth
[Nook Color Android Development] Paul22000:
Yep, that's what happens with bad documentation.

This should be posted somewhere prominently:
[Nook Color Android Development] paleh0rse:
Ummm, can't the boot animation be replaced by simply dropping in a different bootanimation.zip? Why is an entirely new uboot necessary?

Or, am I just missing something and being stupid? lol ;)
[Nook Color Android Development] Ronin3178:
I tried this, and did not have any problems, screen came on normal once I plugged in charger. What is the date you acquired this Nook, is it possible that there different reactions from different Nooks based on build/purchase dates?

I initially checked under my current settings of 600/1200 ondemand, then I switched to the 300/1200 SA$$, let it sit for a few minutes, and still got normal behavior. One additional thing I did notice was that the N started green for a few seconds before going orange and then the screen came on.
[Nook Color Android Development] Ronin3178:
Two things, first you could put a settings icon on one of your pages.

Second - Settings/CM/Tablet Tweaks/buttons - check extend power menu (adds home/back/menu to power menu)
[Nook Color Android Development] newellj79:
It did have the cyanogen loading screen with the "Miami vice" colors.
[Nook Color Android Development] fattire:
There are a few opportunities for logos on startup. When you first turn on the device, after mlo loads, uboot does and shows a splash. You may have seen it as "touch the future of reading", "loading...." or in 1.2 something like "read forever". This is before any kernel loads. If uboot determines you don't have enough battery to load (long story), it will alternatively load a battery/power-related image (and not any kernel) until you have the juice.

If uboot thinks you have the power, uboot then loads the appropriate kernel (regular or recovery) which can have its own built-in logo/graphic in the console framebuffer. It is usually a penguin (which shows up in verygreen's .32 for example), but you can also change it to whatever.

Then there is a logo graphic you can add to the root of your ramdisk that appears early in the execution of init.encore.rc. I'm on my phone now but I think its called something like initlogo.rle...

And THEN there's the bootanim cycling animation that displays when Android is loading. Its called by the init script as well. In stock android its a bluish "android" with a kind of flash across it. On the nook I think its some kind of rainbowwy nook logo (?) And on cm7 its the circle arrow skateboard guy.

The uboot I built is of the very first type.

Hope this is clear. Please post any corrections :)
[Nook Color Android Development] paleh0rse:
Awesome explanation, thank you!
[Nook Color Android Development] chadamir:
I got my charger to green! No problems after all.
[Nook Color Android Development] Nburnes:
Anyway, flashed your uboot just fine. As far as I can tell everything works great? Except for the whole not knowing what has changed other then the bootsplash thing.
[Nook Color Android Development] fattire:
Other changes are (1) DEBUGging taken out of common/lcd.c, (2) you shouldn't have to hold down power button for as long when booting (verygreen's fix) and (3) this should work w/SDcard as well as emmc (verygreen's fix).

I think aside from the splash that's pretty much it.
[Nook Color Android Development] :
Got a pic of the splash? I wouldn't find saving a few seconds on hard shutdown :P
[Nook Color Android Development] deadbot1:
Mine was a Walmart special roughly 1 month ago
[Nook Color Android Development] Ronin3178:
I got mine from B&N back around the beginning of March.
[Nook Color Android Development] fattire:
(these images are rotated because, well u-boot demands it)

Loading... need to plug in... Need to charge.

u-boot.tar.gz
[Nook Color Android Development] bekyndnunwind:
I was editing a word document with my Nook, and took a 30 second phonecall, so I turned the nook's screen off.

~2 minutes later when I press power button to turn it back on...SOD.

I don't get it, the screen was only off for ~2 minutes - it shouldn't have gone to sleep in that time. So I'm not even sure if its sleep of death...:confused:
[Nook Color Android Development] mkm1126:
I've been doing some testing on this build for the past couple of days and here's what my experience has been.

3.1 beta + 5/13 overclock with 1200/300 smartass :

SOD each time nook went to sleep.

3.1 beta with stock .32 kernel (no OC):

I have not charged since yesterday afternoon and today, nearly 30 hours later, I show 83% battery. I've turned the screen on at least three times (with the most recent just now after not touching it all day) with NO SOD or other lock-ups.

I can only conclude that my issues with SOD are related to the OC kernel somehow, but that's jusst a guess. I just wanted to report my observations in case it helps with development.

No issues with WiFi or any other issues on 3.1 running .32 stock kernel.

I'm very pleased at how it's currently running. I'll leave it at it's current configuration to see if anything shows up, but so far, it's great! Oh, I'm running 925/300 on this and can't really tell a difference from when I was running 1200 in the .29 builds.

I don't think it's relevant, but will mention it in case someone thinks it is, besides removing the OC kernel, I also removed any theme and have not changed the build.prop for netflix. I'll add both of those back on now and see how things go, as I don't think they could possibly be related to the SOD issues I was having, but ya never know.
[Nook Color Android Development] spiicytuna:
I get the same thing. The one time I got SOD I was able to adb into my nook to do an "adb reboot" — That being said I've gotten 1 SOD out of probably 200+ successful deep sleeps which is ALL win in my book.
[Nook Color Android Development] deadbot1:
Fattire ...can you package your uboot for CWM? I'm out on the road with no lappy...and I'm still a partial noob...
[Nook Color Android Development] deadbot1:
Just had my first wifi issue...watching Netflix, when it just dropped. Me and my fat fingers managed to lose the log...saw a lot of dhcp errors...reconnected after I forgot an old connection.
[Nook Color Android Development] fattire:
I'm still testing it. I ran into an issue tonight where I ran out of battery and it's acting weird. No clue if its' related, probably not-- I think I have a corrupted FAT partition somewhere that needs some fsck love, but jic I don't feel like it's ready for non-developer testers who can't put back another if they need to, etc.
[Nook Color Android Development] KitF:
I know this is old but I'm having this issue, after 3-4 hours off the charger 65% of the time it is at 600Mhz. 300min/1200max with smartass with 5/13.

I can't really tell what's eating it though. I've only woken it up to check on the battery.
[Nook Color Android Development] deadbot1:
NP...when you feel its time.
[Nook Color Android Development] :
I was afraid this would happen.

So I read about strange behavior around 30% or so. At 28% running 925 on demand in 3.1, it shut down with no warning. No last kmsg or anything. Will jump to oc and see if same thing happens.

EDIT: So here's what happened.

1) Battery level just changed to 27% a few minutes ago.

2) Nook shuts down with no warning.

3) Plug it back up to see if it was a fluke. It turned itself back on.

4) Batt level ~29%, so I play a video full brightness until it hits 27%. Dies.

5) Boot into CWM, flash .32 kernel, reboot.

6) At about 32%, plays video again down to 27%, dies. (Changed to ondemand, 1100 from ondemand, 925 on stock).

CWM won't let me wipe battery, so Googling as we speak to try and find the file name (if there is one) I can manually reset.

EDIT2: Can manually wipe the file here:

data/system/batterystatsbin

Giving it one more go (at 30% right now) running smartass.

WOW. Got a last_kmsg.

From looking at it (and I barely know 1% of what I'm looking at), doesn't look like much. Hope it helps.

At 27% now....and off.
[Nook Color Android Development] hockeyfamily737:
Hmmm.....I'm at 31% now. Been off charge for more then 48 hours (screen & wifi 5+ hours use), but this new Nook has been rock solid SO FAR!!! Guess we'll see what happens through the night here.
[Nook Color Android Development] xxiworld:
Yeah I had the same thing happen, though it was at 22%

I was running beta3.1 OC Smartass 300/1200. I had just cleared battery history with Battery Calibration when I was at 100%, and was letting it run down, but I didn't expect it to give out with no warning, nor that early.

I plugged in and charged up to 100 again. I'm now at 84. If it happens again, what kind of log should I try to find/post? kmsg?
[Nook Color Android Development] :
Not sure, but from what I read the file in the /proc/ folder called last_kmsg can be useful (if it's not zero size). What I know it, it's all the info the kernel sees, so I assume that means recovery and everything else. Not sure if I caught anything worthwhile in there, but maybe...?
[Nook Color Android Development] fattire:
basically, you can see exciting initialization and other message from the kernel by typing "dmesg" at the shell. dmesg (display message) is a running kernel log (whenever a programmer used the printk command). If this log gets too long, it'll remove items from the top as it adds to the bottom.

If you get a kernel panic and the computer restarts abruptly, some kernels will leave their log buffer in /proc/last_kmsg (last kernel message) on the next reboot. It's a good way to try to figure out the last thing that happened when the system went down. That file isn't always left behind though, and the kernel needs to be configured to do it.

(BTW- figured out my issue-- it was a corrupt partition 2 (/rom). Fixed it and everything seems to be working now.)
[Nook Color Android Development] skwalas:
So here's something I can contribute to the batt issue: I had the same thing happen to me last night at 22% but...

I was on nightly 74.

The batt issue you are seeing is not exclusive to .32 build apparently.

Recharged overnight but it had maxed out at 75% and 4200mV after 8 hour charge on BN charger. So I wiped battle stats to reset to 100% and noting that drain is a lot slower today (now on n75)

Anyway, the instant shutoff at 20-30% isn't just with the beta. Just sayin'.

Edit: I did flash the new uboot a couple days ago ("read forever"). Maybe that's the common link?
[Nook Color Android Development] MedLine:
confusing, why is first line of last_kmsg "Linux version 2.6.29-omap1 (erik@myhost) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-188) ) #10 PREEMPT Sat Apr 23 19:26:06 CDT 2011," as if came from n54 or one of 042311 OC kernels?

same thing happened to me.
[Nook Color Android Development] fattymcdirty:
perhaps this issue comes with uboot 1.2? had one SOD a night before.. i'm on beta 2 with smartass 1200mhz.. another thing: sometimes, when i switch on the screen, battery is at e.g. 72% - then i'm using the device for like 2minutes and the battery switches to e.g. 56% immediately - wtf?!
[Nook Color Android Development] fattymcdirty:
that's what i'm assuming, too...
[Nook Color Android Development] KitF:
Okay, my "SOD" isn't exactly what it seems. When I go to bed at night and leave my nook on idle for a few hours, I thought the screen not coming on meant that it died around 60% battery.

Not true. The nook is still on. I can hear the unlock noises and the touch screen is still responsive. The screen just never turns on. Has anyone else had this?
[Nook Color Android Development] hockeyfamily737:
3 & 1/2 hours later....haven't been using the Nook at all and still showing 31% battery. I have a funny feeling I'll get home from work, fire this thing up and the battery level will drop out and shut down. Guess we'll see in a couple more hours.
[Nook Color Android Development] 360Razir:
Yes, I was in a dark room at the time and I could see a faint glow from my screen, so I knew it wasn't off completely. Just could not wake screen by simply pressing "n" like normal. Power button was unresponsive as well.

Holding down "n" for ~8 seconds brought my screen back to life. That has only happened to me once, so I have not been able to test whether or not that works all the time, so if someone can test if holding down "n" works when it looks like their NC is in a coma, then that may save some hard shutdowns in the future.
[Nook Color Android Development] legolee:
for those who are having battery problem like shutting down without warning at 3x or 2x % battery, i have a solution for you.

I had this problem when I was running phiremod 6.2. I use battery calibration app on the market, but did not work. use the wipe battery stat option in clockworkmod, still did not work (i did charge it to 100% and wipe the battery stat, then full discharge, full charge, then it still shut down at 3X%).

So my last shot was to flash the official 1.2 ROM back to emmc, and then used it until it shut down at 2x/3x %. Then plug in charger, it said battery too low. Waited 15 mins, then nook could be turned on and I now see 7-8% on battery meters. GOOD! I charged it non-stop to 100%, then restore back to phiremod 6.2 and everything is fine now :)

And my battery is still working properly with beta 3.1 + oc kernel (but i switched back tp phiremod 6.2 at this moment since I always have the system freezes system).

I hope my above info can help you guys
[Nook Color Android Development] iDidItAll4theNookie:
I was wondering if what version you were upgrading from had anything to do with some of these issues. I came from rooted 1.2, and so far so good. Someone else suggested that the uboot patch could be the cause, and I was wondering that, too. The only other thing I can think of is that there may be an app that is not playing nice and is messing with deep sleep and maybe even CPU cycles. I know it's not exactly the same, but I've had rouge apps kill my iPhone overnight a few times.
[Nook Color Android Development] legolee:
I think u are referring to the random freezes issue? My nook is only 2-3 weeks old. I upgraded it from stock 1.1 to 1.2 on first day. then use the SD method to install CM7 to emmc. also tried ROM like phiremod 6.1/6.2 and 1.2 rom flashable via CWM.

Are you saying that there are different version of uboot 1.2 (read forever)?
[Nook Color Android Development] Zorkman:
I don't think there are different version of uboot 1.2

if you're not on stock you can get it here:

http://xdaforums.com/showpost.php?p=13682477&postcount=1403
[Nook Color Android Development] legolee:
i always wipe all and cache when switching ROM.
[Nook Color Android Development] Homer_S_xda:
Small bug in beta 3.1, I think, it looks like installing an apk manually (copying to apps) does not get the icon on the show all apps screen. I'm fairly certain it does in the stable/nightly versions.

The specific APK I was using was the NookColor UMS from this board. Also, if anyone knows how to get that app back to full screen would be great. Yes, compatibility mode is on in spare parts.

Homer
[Nook Color Android Development] :
Does fine for me.

Copy it, change permissions.

If it doesn't show on reboot, just install it from the folder.
[Nook Color Android Development] khaytsus:
It just occurred to me that maybe there's a good reason some people are seeing two distinct different "SOD". One being that the NC appears to be alive, adb responds, buttons make beeps, etc, but the screen is off. The other being the NC is completely dead and nothing responds until you power off for 8+ seconds, then power back on.

Can anyone who has seen either one report what install they're running from? eMMC or SD?

it occurred to me that maybe the SD card is going into deep sleep, and since I'm seeing the "completely dead" variety and I'm booted into CM7 from SD card, perhaps that's why?
[Nook Color Android Development] junkrobot:
I've been running rock solid on 3.1 Beta with OC 300/1200 OnDemand. I haven't given it extensive time with deep sleep, but I've powered off the screen to go do some errands and returned to it with no issues.

I'm going to try to let my battery run down to around the 30% mark to see if I also experience any weirdness. Disconcerting.
[Nook Color Android Development] :
Made a poll over here.

If you could tell me how you went to Beta and if you're on eMMC or SD, that'd be a big help.

NOTE: I want your battery to have at least been depleted to 20% to vote.

http://xdaforums.com/showthread.php?t=1083354
[Nook Color Android Development] Ronin3178:
Tried to post a response there, got some data null or something, couldn't post from my D1
[Nook Color Android Development] Homer_S_xda:
Thanks. I guess I should have been more clear. I was recalling (could be wrong though) that the reboot was not required.

It did show up on reboot and switching off compatibility mode got the app to full screen.

Homer
[Nook Color Android Development] KitF:
This isn't working for me.
[Nook Color Android Development] joe2262:
I toggled comparability mode and rebooted and it's fullscreen. I also have an app drawer icon?