yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] fattire:
I'm not sure I understand the scenarios. In the first you were using the custom menu/ u-boot on an SD card w/cm7 (and how did you boot? normally? With the menu? Held down keys?) Trying to load which pair of kernel/ramdisk? And it didn't work... how? What did you try next with this card?

In the second case, where it "worked great"-- you were using another CM7 SD card? Or an HC card? Or a combo card? With which u-boot? the menu/custom one or something else? And how did you boot? Menu? Keys pressed down? And what was the result?

Sorry I'm confused about what you're trying and what the results are. I know two people at least say that it worked with their SD card, so trying to understand the specifics of what you're doing and what results you're seeing.
[Nook Color Android Development] biz18434:
I started with my HC sd card and I could not get it to boot trying every variable.

So, I gave up on my HC sd card and used my CM7 sd card using your u-boot and everything works. I am sorry to waste your time because your u-boot works on my CM7 card. I can boot into recovery using both the menu and the hotkeys and I also can boot into my alt recovery using both the menu and hotkeys. Now if I use my HC sd disk using the same uRecImg, UrecRam uAltIng and UAltRam that worked on my CM7 sd card and select recovery from the menu. I end up with a black screen. If I select recovery using the power button and the n key I get the same result. But, if I select the alt recovery it boots up just fine. Now when I replaced you u-boot.bin on my HC sd card and replaced it with j4mm3r u-boot.bin still on my HC sd card everything works. I can boot into HC if I do not touch any keys on boot. I can hit a key during the countdown and I can boot to recovery or alt recovery on the SD card. Again thank you for all your great work.
[Nook Color Android Development] abs99:
I hadn't seen that in the older setup but also did not extensively test video, so very possibly an issue with flash.

Have you experienced any Wi-Fi cycling or weak signal issues with 85?

Is the problem with slow performance after "wake from sleep" still occurring?

If these problems are resolved, I'll try out nightly 85 and report back, otherwise would prefer to stay on the older build since it has been extremely stable for me.

Thanks.
[Nook Color Android Development] ziggy34:
Next nightly should have the wifi fixed.

Below from the myTouch 4g thread.
[Nook Color Android Development] Mistar Muffin:
Installed N85+Dalingrin's 5/23 kernel last night with a complete wipe of /data, /cache, and /system. I verified deep sleep with CPUspy by letting the NC sit for about 60 seconds and verifying it was in deep sleep for about the last 30 seconds or so of that. With battery @ 40%, I left for about 9 hours and this morning I could not wake it. I had to hold down the power button for about 20 seconds and it booted fine and reports 30% battery. 10% drop after ~9 hours does not sound like it's deep sleeping properly, not to mention the SOD. I checked CPUSpy but it appear those stats are reset on a reboot.
[Nook Color Android Development] paleh0rse:
N85, fattire's latest uboot, gapps 20110307, and 5/23 OC set to Conservative = Just woke after 8 hours of deep sleep without issue -- confirmed in cpuspy -- and battery had only dropped from 48% to 45% overnight!

The odd thing is that it then dropped down to 40% after only 10 minutes of use, and now it's down to 30% after only one hour of light internet use. IOW, it dropped 15% in the last hour using just browser and tapatalk apps! It literally just dropped from 32 to 30% while I was typing this message! Yikes!

Plan to test until battery shutdown...
[Nook Color Android Development] Xhorder:
I'm running (Multi)u-boot in order to dual boot into stock. Am I right that this will overwrite things and I'll loose the dual boot functionality?
[Nook Color Android Development] joenathane:
The new u-boot has dual boot functionality, I'd say backup your old u-boot just in case.
[Nook Color Android Development] Tweakrr:
I am getting the same sleep-death problem with N85 and Dalingrin's 5/23/11 kernel.

It won't wake after it goes to sleep after 60 seconds. Has been pretty consistent, I can hit the power button to turn off the screen, let it sit for 1 minute and the N key does nothing and have to do a force power-off by holding the power button for 20 seconds, and then doing a cold boot to go back into CM7.

This is the first time I've had sleep death problems with my NC, the previous nightlies have been fine. I will try another kernel with N85 and see if it is the kernel or the N85.
[Nook Color Android Development] only one haze:
that's weird...I installed N85 and the 5/23 OC kernel last night and played around for a little while. Pushed power to put it to sleep and then when I got up this morning, I picked it up and it came right on. No issues whatsoever. I did clear cache and davlik before I flashed. No idea if that made any difference tho. But this set up has been super fast (OC'd to 1100) and very responsive for me.
[Nook Color Android Development] boxcar8028:
very interesting, I been having SOD issues ever since after n78. please see my post #3003

http://xdaforums.com/showthread.php?t=960542&page=301
[Nook Color Android Development] seth.i.simmons:
Can anyone tell me what increasing the dalvik cache size does functionally?? Just wondering if it would be worth it to try out a few different sizes and see if I can get any extra performance out of it. Thanks!!

Edit: nevermind, just did a Google search and read up on it for a few minutes. Upped it to 40mb, so far so good!
[Nook Color Android Development] wpnyc2009:
SOD at 31% :(

Ditto. I have same set-up as Tweakrr above (without knowing his/her full specs I mean) and this is the first time I've gotten SOD as well.

Worst part for me: in haste I left my charger at home this morning, so now I'm without NC for the first time on months... :(
[Nook Color Android Development] paleh0rse:
An actual SOD issue should not require a charging cable to reboot. You should be able to hold the power button down for 10 seconds, let go, then hold it down again until it boots up.

Are you sure yours is not a battery-related shutdown? What % was it at prior to what you're calling a "SOD"?

If it was in the 20-30% range, then it could be the battery-based auto-shutdown issue that has been happening frequently with the .32 builds -- this is NOT a "SOD," and does require the charging cable to boot back up...
[Nook Color Android Development] wpnyc2009:
It was at 31% when it shut down. My bad, I guess with all the talk of 'SODs' I'm confused btw a true SOD and a battery related issue. Can you explain briefly, if you have time? Thanks m8!

EDIT: is there any solution to this random shuttting down? Have folks gone back to a specific version that doesn't shut down? Anything will be helpful.
[Nook Color Android Development] fattire:
Hey first off thanks so much for the above-- please don't apologize for "wasting" anyone's time... this is all fun stuff, right? :). There is nothing special I can think of in HC that should work differently than CM7...

So to go through the steps of what you're doing...

"I started with my HC sd card and I could not get it to boot trying every variable."

You mean you had an HC sd card with "my" u-boot on it AND HC's version of uImage AND uRamdisk and you couldn't get it to boot at all?

Then you say you used CM7 and had no problem...

" Now if I use my HC sd disk using the same uRecImg, UrecRam uAltIng and UAltRam that worked on my CM7 sd card and select recovery from the menu. I end up with a black screen."

You typed that you use "uAltIng" for the black screen and UrecRam-- I assume that's a typo, right? It's Img not Ing... and uRecRam not UrecRam...

But in any event you're saying that you switched SD cards, but used the SAME u-boot, the SAME uRecImg and uRecRam and SAME uAltImg and uAltRam that you used on the CM7 one, and got a blank screen? What were you using for uImage and uRamdisk-- same as from cm7? And did you experience a blank screen meaning u-boot didn't load? Or did you experience a blank screen AFTER trying to select one of the boot options? And if so, which options did you try? And did you try it via holding down keys or selecting from a menu? And are you 100% sure you were using the same files from the cm7 boot?

Sorry for all the questions, but I guess it's a complicated little program that has a ton of potential boot scenarios, so the more specific, the better... Again, I don't know of any reason why, if you replaced u-boot, uImage, uRamdisk, uRecRam, uRecImg, uAltRam, and uAltImage from one SD to the other, that it suddenly would blackscreen on you.

UNLESS.... if you are mixing kernels-- like trying to use a .32 kernel (from the most recent CM7 nightlies) on a HC installation, which assumes you're using .29--then you wouldn't be able to load the 2d GFX modules in HC, which means you'd end up with a black screen.

Could that be the issue? If so, it's not a u-boot thing, it's a using-the-wrong-kernel thing. One way to tell is-- first, u-boot would load up and everything, the problem would be after when you started booting. And then you'd get a black screen, but adb would still work. So you could type "adb shell uname -a" and get back the kernel that you're using. If it's 2.6.32.x and you mean for it to run with HC, you'll just need to replace the appropriate kernel with .29.

Hope that makes sense.
[Nook Color Android Development] DizzyDen:
UAltRam is another possibile typo or case issue.
[Nook Color Android Development] t3rabyte:
Which category do you fall into?
[Nook Color Android Development] philburkhardt:
Battery Issue: Nook shuts off somewhere around the 25% mark. Need to plug charging cable in to reboot.

SOD (Sleep of Death): Nook won't wake up after screen being off for a period of time. Requires a hard reboot to turn back on. Cable does not need to be plugged in.
[Nook Color Android Development] :
Thank phil. I wish there was a page that flashed at people who have not been on the NC threads that long to explain things. Would save a lot of typing and pain :)
[Nook Color Android Development] TheMainCat:
Liking the new u-boot. Question is what do I need to get it to boot into recovery? I have clockwork installed in the Nook but nothing on the SD card (far as I know). Pretty sure I am missing something, because holding the power and "n" button just has my device boot normally.
[Nook Color Android Development] paleh0rse:
Actually, I think SOD = Sleep of Death... Meaning it won't "wake up" properly. ;)

I'm going to start calling the battery issue PBD (Premature Battery Death) to try and make it easier to discuss... maybe it will catch on! lol
[Nook Color Android Development] fattire:
From when the boot image/splash appears, you have about 2 seconds to hold Power+"n" to bring up recovery, if you have it installed on the same volume as what you're booting from. Otherwise, hold down only the "n" button for the menu.

If you like, you can hold the special keys down before the splash comes up. Just keep holding until you see the notification that it's booting in the way you selected.
[Nook Color Android Development] philburkhardt:
Haha, I totally meant sleep.:rolleyes:

...fixing now.
[Nook Color Android Development] paleh0rse:
I figured that was the case :P
[Nook Color Android Development] sec6:
Not sure if this helps any with the premature battery death, but noticed when plugging in the nook after putting on the new u-boot that the battery jumped from where it was at (around 80%) to 99% without any additional charging. So if I let it drain from this point, it would make sense that it would shut down at around 20% as the 99% figure is incorrect. I let it charge until the green light came on and it took quite a while as it would from an actual 80% charge. So, I don't think this is really premature battery death. Perhaps it is just incorrect scaling.
[Nook Color Android Development] I Am Marino:
Is the new uboot merged with any of the nightlies yet?

Still rocking the Incredible with the XDA Premium App.
[Nook Color Android Development] joenathane:
Nightly 86 which isn't out yet will have it.

check here for updates

http://cm-nightlies.appspot.com/?device=encore
[Nook Color Android Development] I Am Marino:
So I won't have to flash the 1.2 update by itself, just flash nightly like normal and it's there?
[Nook Color Android Development] khaytsus:
I'm an idiot, but I can't afford a $9000 camera so I guess I'm okay?
[Nook Color Android Development] joenathane:
Once 86 is out all you'll have to do is flash the nightly and it'll take care of the u-boot.
[Nook Color Android Development] paleh0rse:
Just experienced PBD with n85 and all the latest versions of everything... happened at 16%. :(

Recharging now...
[Nook Color Android Development] I Am Marino:
Alright cool so it sounds like 86 is the nightly to have.

Still rocking the Incredible with the XDA Premium App.
[Nook Color Android Development] fattire:
The new nightly wont' have the latest-latest uboot with the menu or the kernel "breathing room". But it will have the new theming. If no one reports problems in a day or so with the newest menu one, nemith will add in the newer menu-enabled u-boot.

So as far as that goes, I believe 86 will basically be a test to make sure his build changes to replace u-boot work.
[Nook Color Android Development] philburkhardt:
Looks like 86 is up!
[Nook Color Android Development] I Am Marino:
Makes sense, I feel a new stable isn't too far away.

Still rocking the Incredible with the XDA Premium App.
[Nook Color Android Development] chemical1der:
Hey folks,

I flashed the new u-boot (which looks awesome!) and while I can boot my nook normally I cannot boot into recovery. When I hold down the power + n buttons it tells me it's booting into recovery but just hangs. Do I need to reflash CWM? Or advance recovery my old boot image and start over again? Any help would be greatly appreciated.

TIA,

chemical1der
[Nook Color Android Development] skwalas:
Eh, we already know it'll work just fine. Y'all don't mess around with these things. 85 with your untimely menu boot and dal's oc and I'm one happy camper.

As an aside, I can't shake the feeling we're near the end of truly Gonzo tweaks for the NC. I might have to stop fiddling around with it and actually start reading with it again!
[Nook Color Android Development] fattire:
Which "new u-boot" is this? The latest from last night or so? Also, are you running it from emmc or sd? Do you have recovery installed on the same volume (sd/emmc) that you're booting from? Umm, oh, and does it work if you try from the menu?

I believe the latest is the "untimely version" :)
[Nook Color Android Development] chemical1der:
fattire,

Sorry for being so vague:

A.) I flashed the "untimely version."

B.) I'm running CM7 from EMMC.

C.) I do have recovery installed on the same volume I'm booting from.

D.) No, it doesn't work if I try to boot into recovery from menu.
[Nook Color Android Development] fattire:
I just experienced the same thing. I think this is may a screwed up /rom/bcb file setting.

Try booting recovery from the menu. From then on it seems to work as expected, both for myself and everyone else who's tried it.

Give it a shot and see if it cleans it up? If so, I'm going to go through it with a fine-toothed comb and see if it's u-boot or bcb or what... the good news is that it seems to work repeatedly once it loads recovery once...

It sucks because having experienced it once, I tried booting from the menu and now it works every time so I dont' know what the cause was :)
[Nook Color Android Development] chemical1der:
Will do. Thanks fattire. I'll report back and let you know if it works.
[Nook Color Android Development] skwalas:
oh dear...

I just drooled on the screen.

nightly 86 (boot worked just fine fattire), added dals 0523 oc, added untimely boot menu (confirmed it went into recovery no problem).

plus: it took only 40 seconds to boot up! Whoa!

plus: video/animation smoothest i've seen yet! Whoa!

plus: it moves mountains and grinds planets to dust! Whoa!

minus: I lost the "install stock 1.2" workaround to the instant shutoff problem (i flashed the nightly at 25%, and it went off at 20%). gol'durn it! i dun wanna have to experience stock 1.2 again. ick.

so close to perfection here......
[Nook Color Android Development] angomy:
Re: skwalas nightly 86

Once these changes go to stable I think I'll take the plunge and install CM7 to EMMC. I find myself using stock less and less --- even for reading, and the Nook is so zippy on these last few nightlies that I can't stand the slowness of unrooted Froyo. Bravo, devs!
[Nook Color Android Development] Tweakrr:
I had some sleep death problems with N85 but with N86 everything's beautiful again! Seems really snappy too. I like the new boot screen. You guys are rocking!
[Nook Color Android Development] paleh0rse:
Fattire, do you guys have any leads at all on the PBD (premature battery death) issue?
[Nook Color Android Development] pseudo_nomen:
WiFi seems solid on N86 - no more looping/fading/disconnecting/locking. Best build yet.
[Nook Color Android Development] fattire:
I don't... I'm at 37% right now so we'll see if I get it.

Update: Look at Settings->Applications->Battery Usage and touch/press on the graphic at the top. You should get a full-screen representation of your battery use. Don't know if there's anything valuable here, but make sure it corresponds to your usage patterns. Who knows, there may be some weird pattern that explains/suggets what the issue is..
[Nook Color Android Development] skwalas:
fattire, as others have stated, i was able to get rid of the PBD (makes me think of PB&J) by flashing the stock 1.2. ran it down all the way (got the 15% warning and shutoff at 3%), then charged up to full 4200 mA (which was 89% on the scale), then used SD to flash 84 (or was it 85?) back on. I reset battery stats while doing that. Once back in CM7, saw 100% as expected, drained all the way down and got a completely different 15% warning (CM7 specific perhaps?) and shut down at 3%. It's been that way ever since, except for when I finally flashed the untimely boot. Now I've got the PBD again.

there must be something unique to 1.2 setup that can sit in the background after flashing n85, but gets wiped. I wonder if bundling a boot with the newer nightlies means the PBD will keep coming back after using the stock 1.2 workaround.

As for the battery usage graph, i've not seen anything untoward in my graphs. I check them often out of habit (from the days of 1%/hour standby drain).
[Nook Color Android Development] paleh0rse:
N86 is rockin' with Dal's 5/23 OC and fattire's "untimely" uboot. The only thing that stands between this and a daily driver may be the infamous PBD. I'm at 65%, so I wont know until tomorrow night... we shall see.

/fingers crossed
[Nook Color Android Development] stinky634:
Thanks for the hard work guys!!!

Fortunately I have not had a lot of the issues that seem to plague folks here (Wifi, the battery thing)

Unfortunately, after the newest nightly, I had some apps disappear (Talk, Twitter, Zillow) and a few apps wont even start (GMail, Pocket Legends) This combined with my status bar occasionally closing, and the occasional SOD, I figured I'd revert to a stable release and see what happens. I have been lucky to have not had to do a full wipe in a long time due to the awesomeness of CM7 and all the work thats been put into it.

Edit: Sorry to have posted this in the Dev thread, meant it for the User thread.
[Nook Color Android Development] TJNooker:
Checking in after n86

I've been running n86 for about 4 hours now and so far so good. I had serious WIFI cycling issues with n85, but n86 has resolved that issue.

I also had PBD (premature battery death) issues with the .32 Beta kernel. I haven't run the battery down low enough to test whether that issue has been resolved in n86. For the record, I did a clean install of n86. I wiped data, cache, & system; flashed BN 1.2 + keep CWM; wiped data, cache, and system again; and then finally flashed n86 and gapps.

EDIT: Oops, I meant to post this in the CM7 Users thread. Please move this, moderator. Now that the beta kernel has been merged with the nightlies, I think most of us should probably be posting in the "Users" thread. Leave this thread to actual development questions & comments.
[Nook Color Android Development] ziggy34:
#86 wifi is working great.

Strange battery, attached screen shot. Has NOT been plugged in for a couple days. After updating to #86, was at 23%, using it to see what battery did. I watched it jump from 22% to 35%.
[Nook Color Android Development] newellj79:
Fattire, is there a reason that the uboot splash with the instrctions was taken out of n86 and left with just the cyanogenmod green logo? I really liked being able to see them. And i was loving your untimely version.
[Nook Color Android Development] khaytsus:
What's in 86 is just the graphics, the one with the text instructions wasn't yet committed.
[Nook Color Android Development] painter_:
The answer you seek was 20 posts before yours.

http://xdaforums.com/showpost.php?p=14114496&postcount=2536
[Nook Color Android Development] paleh0rse:
You can always do what I did and just re-flash the "untimely" version on top of n86... Be sure to post your results (good or bad) to help them make the final decision to include the whole thing in n87 or n88. Consider it a beta. ;)
[Nook Color Android Development] newellj79:
Is untimely the same thing except the splash screen?
[Nook Color Android Development] taylor.fowler:
the "untimely" uboot has the text instructions under the cm logo. it's also here:xdaforums.com/showpost.php?p=14083881&postcount=2488

glad the name stuck :)
[Nook Color Android Development] DizzyDen:
Or you can do what I did... replace the u-boot.bin in the update with fattire's, then install the Nightly.

Works beautifully btw.... and now to do it with N-87

EDIT: Questions for the dev's: Is there a reason that libOMX.TI.JPEG.Encoder.so and libOMX.TI.JPEG.encoder.so are both in the /system/lib folder?

Also: Is there a reason some of the files have ".Decode" and ".Encode" while others have ".decode" and ".encode"... I'm just making sure the naming is correct is all....
[Nook Color Android Development] sinanju:
Sadly, I flashed 86 and still got the PBD @ ~20%
[Nook Color Android Development] only one haze:
I flashed N86 and the OC kernel then fattires "untimely" uboot. When I try to alt boot it says Booting Alt...but just sits there. Alt is for dual boot right? Or am I missing something? Reflashed the nightly and kernel and all is well now, just curious about the alt boot.
[Nook Color Android Development] paleh0rse:
yeah... I left mine running video in a loop overnight and woke up to the dead Nook (as expected). When I plugged it in, it loaded up with 17% battery and quickly shutdown again at 16%. :(

I sure hope they can nail this one down... it's really the only remaining problem I have with the current builds. Everything else is better than it's ever been!
[Nook Color Android Development] :
Regarding PBD (I love that it's sticking so far :P), I really think one needs to run the battery all the way down on 1.2 stock, then recharge a bit and reflash cm7...have you guys done that?

Also, regarding an actual SOD, anyone try this and have it not work?

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

Turning off the screen on animation seems to have helped some people...and it makes sense?
[Nook Color Android Development] sinanju:
PBD: No, I haven't. It's also a rather unreasonable requirement for installation. I could do it and just get it over with, but at this point I'm leaving the device in its current state so I can test any potential fix.

SOD: The SODs I experienced were almost certainly related in some weird way to turning off the screen with WiFi active... I had no screen animation. The version of the issue I had seems to have gone away with #86.
[Nook Color Android Development] sinanju:
Oh... and for what its worth, audio is rock-solid. I've been listening to Bach flute sonatas this morning with nary a skip.