yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] ADude:
So, can someone clarify (thanks) :

Does the workaround stop the usual automatic screen blanking after a minute or two of non-use ?
[Nook Color Android Development] muness:
Yes, it won't automatically turn off. But only when plugged in.

Sent from my HTC Vision
[Nook Color Android Development] dipole:
odd

1st beta booted up fine, but I wiped and flashed beta 2 now my nook won't boot up if I have an SD card inserted. IF I take out the SD it instantly boots up. Tried reformatting SD, not sure what's going on.
[Nook Color Android Development] bekyndnunwind:
As in, the screen will stay on while its plugged in, or the nook won't go into sleep while its plugged in?
[Nook Color Android Development] GrillMouster:
Did you update the u-boot to B&N's 1.2?
[Nook Color Android Development] henel321:
After installing uboot from 1.2 and also upgrading to beta 2 video works great and large apps on SD are visible again, great job!
[Nook Color Android Development] rhester72:
I'm using verygreen's SD card install for 7.0.3 with the 0424 OC kernel without issues.

It is unclear to me whether verygreen's u-boot.bin is the stock NC 1.1.0 file or modified in some way, but trying to replace it with the stock NC 1.2.0 u-boot, I get the correct "Read Forever" splash but wind up in a recovery-mode boot loop.

Given that it appears the 1.2.0 u-boot is very necessary for happiness with the 2.6.32 betas, is this just an incompatibility with 2.6.29/CM7.0.3, or is it not possible to use the stock 1.2.0 u-boot with the verygreen image? (I sure hope it isn't the latter, because it is exquisitely simple to update builds with it while keeping the eMMC "clean"!)

Rodney
[Nook Color Android Development] ts_mpls:
I didn't see this mentioned but has anyone else noticed that the SD card no longer mounts when connected via USB (on beta2)? I get the MyNOOKcolor (i.e. emmc?) partition but not the sdcard.
[Nook Color Android Development] niphoet:
I want to do a fresh install of the newest release. I used ROM Manager to install ClockworkMod Recovery to the internal eMMC, and when I boot into recovery and do a full wipe, and restart, CM7 is still installed, except it comes up with the "Touch the Android" to set up gapps. How can I completely wipe w/o my ClockworkMod microSD? Thanks.

PS -- FWIW, I updated the uboot to the new 1.2 that was linked a few pages back.
[Nook Color Android Development] paleh0rse:
Is anyone familiar enough with the multi-boot bootloader to update it to the BN 1.2 uboot? I'd hate to give up my alternate-partition stock build, but I really want to switch my primary to the new .32 beta build... hmmm...
[Nook Color Android Development] Animec:
New beta up and running w/out any apparent problems... thanks again for all the hard work you're putting into this :) it's a little silly, but the gingerbread screen-off animation is probably my favourite enhancement so far. Don't judge!

On a more serious note, I noted in the latest nightly I used (68) that the nook was dead quiet even with the screen turned on (referring to the previous issue with the sound from the speaker grille). In this beta, there's a slight electrical hum from the speaker grille when the screen is on. Everything is fine with the screen off however :)

cheers
[Nook Color Android Development] dalingrin:
Both. When connected to USB the Nook's screen will not turn off until you hit the power button. The nook will also not go into deep sleep while connected. Note that the stock 1.2 doesn't sleep on USB either.
[Nook Color Android Development] seth.i.simmons:
Same here, just did a clean (wiped system, data, and cache) install of the new beta from nightly #69, and its awesome so far! No problems at all, all my apps (SD and internal) work great, and you just gotta love the screen off animation :P To me, it seems as fast as my 1.3ghz nightly setup, which is insane since its only running at 925mhz right now! Awesome work dalingrin and all the others who worked on .32, its amazing! Now just to get it to 1.3ghz ")
[Nook Color Android Development] :
Damn it, I rebooted, and now the screen off animation left! Any ideas how to bring it back? It was awesome! Already tried checking/unchecking.

Also, anyone else notice a bright flash before the bootanimation?

EDIT: I'm dumb. In spare parts you must keep window animations to normal for it to show. The other you can change to fast :)
[Nook Color Android Development] yoopyoop:
I second this request. In fact, I already put the BN 1.2 uboot on mine and lost the ability to dual-boot, as I rarely boot into the alternate stock 1.2 anyway.

I'm hoping I can just go into terminal emulator, mount /boot and then copy my uboot.bin.stock (which is really the multi u-boot) back and be able to dual-boot again. But that's a bit of a PITA way to be able to dual-boot.
[Nook Color Android Development] lschroeder:
+1 I have the same problem with the verygreen image for second beta. Asked earlier about it. I was able to get the 2 earlier 2.6.32 ROMs to work with verygreen's image.
[Nook Color Android Development] Calla969:
I also have the speaker hum again. I have the updated uBoot and the latest beta. Speaker was completely silent with the nightlies. There is only noise when the screen is on. Anyone else? When this was fixed in the nightlies, it really seemed to improve the battery life dramatically.

Does anyone else feel like the touch screen is less responsive than it was using the Nightlies and Dalingrin's OC kernel?
[Nook Color Android Development] :
I do. Upping the dpi to 187 (which I always do) seems to have helped.

EDIT: How long does it take to sleep, and can I adjust it?
[Nook Color Android Development] :
Anybody figure out a good way to use the new u-boot.bin AND maintain dual boot? I am loving the .32 Kernel, but I want to be able to have stutter-free video and my Dual-boot with B&N 1.2. . .
[Nook Color Android Development] c0ldburn3r:
I'm amazed at the performance gain with. 32. Can't wait for 1100mhz !

I am the Stig
[Nook Color Android Development] ADude:
So, let me see if I understand this correctly:

* The SOD problem is fixed except when the USB wire is connected to either a PC or the AC charger - so in order to prevent SOD during those two situations, one needs to toggle "Stay Awake" setting. But, even "Stay Awake" is set, pressing the power button will turn off the screen, and that will not affect charging. Is that all correct ?

* And, separate question, does the stock 1.2 no longer turn off the screen when charging ?

Thanks !

( I charge on my nightstand while I sleep, and I need darkness to sleep - personal quirk - so this is an important detail for me. )
[Nook Color Android Development] J-ROCK:
I have tested my BT with the new beta build, and indeed it has improved the range for me. But just by a bit!

Oh yeah can't wait for an OC kernel!
[Nook Color Android Development] :
Hey gang. Few questions:

How long does it take you to hit "deep sleep"?

Would CPUSPY prevent/slow this down?

How's the battery drain?

I'm running beta 2, but I can't figure out why the NC seems to idle at 600 MHz until it hits sleep about 10 minutes later...
[Nook Color Android Development] Teksu:
Sleep while charging has been disabled i believe, however as stated in the post you quoted, you can press the power button once to turn the screen off. i have not run 1.2 stock, but i would assume the screen would automatically time out on the stock build.
[Nook Color Android Development] ADude:
I always up the DPI, so I am curious - why 187 ? why not 186 or 188 ??
[Nook Color Android Development] bitnerd:
Is it necessary to wipe the system and data partitions to get the best performance from the latest uboot image and the beta? I cleared both caches but would rather not lose my data
[Nook Color Android Development] :
I'm using the tablet-tweaked honeycomb theme from the tablet-tweaked thread (in the OP).

I went through quite a few iterations, but I settled in 187 becuase...

1) On some dpis, when the taskbar slider is slid up, there's a little vertical line it it. That eventually drove me nuts :P

2) On some dpis (sometimes the same as 1, sometimes not) if there is a place where a slider would popup (like adjusting the volume, etc) with this theme a little jagged bit of slider would be offset.

So 187 does not show either of those...it's just the OCD in me. I found above 180 is good for hitting buttons as well :)
[Nook Color Android Development] ADude:
Suggestion - the Beta2 download link should be removed from the OP and moved to the FAQ post only (261) that is linked in the OP.

So, users should at least have to move their eyes down the FAQ before downloading...
[Nook Color Android Development] ADude:
That's a good question and I'd like to hear a reply from a dev.

Given the partition names, one would think that clearing system would be a good idea that would not affect any of one's settings, which in theory would be in "data", but I am not sure if that is the actual practice.

FYI - uboot.bin is in the boot partition.

BTW, reading earlier posts shows that people had good results by merely clearing cache, dalvik-cache, and the cache of any picture apps (Gallery,QuickPic, etc.)
[Nook Color Android Development] HTCF4N:
I PM'ed Rookie1 about it since he's the man that gave us the u-boot option. I could probably compile a new u-boot.bin but just don't have the time right now to get into this.
[Nook Color Android Development] seth.i.simmons:
Hmm, I've just noticed that this build seems to idle a lot more at 600mhz than the previous kernel. Is there a specific reason for this?? Seems like it would kill battery life compared to idling at 300mhz. Also, for some reason I'm getting a little speaker buzz again, where as it was completely gone on nightly 67 and up for me. Any way to fix that??
[Nook Color Android Development] MedLine:
with wifi off, within 10 seconds. with wifi on, meanders around first 10 minutes with cpu spending about 1/3 of time in deep sleep, after which seems to go into deep sleep for good. this is based on a few empirical observations.

no. app developed by storm717. go here to give some props, or go back to Market and give 5 stars. app itself no active monitoring, only reads time_in_state. you can get same info by running:

cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

my personal observation 0.1-0.2% / hour. think about it though, that's iPad-like 20+ day standby time.
[Nook Color Android Development] indagroove:
Can't you just place the nook screen side down?
[Nook Color Android Development] J-ROCK:
For some reason I just took my nook of the charger, and the battery icon shows like its still charging!
[Nook Color Android Development] iDidItAll4theNookie:
Actually, it doesn't appear to do so, at least not on rooted 1.2 (I wouldn't think that rooting would change that setting). I plugged it in yesterday, and the battery charging screen popped up, then the lockscreen stayed on. I watched it for a few minutes and it never turned off. I had to hit the power button. I can check again if it will be helpful.
[Nook Color Android Development] RoboRay:
Or just press the power button when you put it down. :rolleyes:
[Nook Color Android Development] hockeyfamily737:
I think there's a misconception here....The sleep settings are not referring to the "screen timeout", but to the cpu. You can still turn your screen off and charging your Nook will have no impact on your personal sleep habbits :)
[Nook Color Android Development] 12paq:
lol, my old Vibrant on Eclair would light up bright and make a sound, in the middle of the night when fully charged. Maybe becouse devs program best in the dead of night?
[Nook Color Android Development] ADude:
Except that the "Stay Awake" setting that dalingrin says to enable says:
[Nook Color Android Development] chisleu:
Except that it will indeed allow the screen to turn off, it just won't sleep while plugged in.
[Nook Color Android Development] RoboRay:
So. Press. The. Power. Button.
[Nook Color Android Development] chisleu:
Good call!
[Nook Color Android Development] derekr:
Am I the only one with a non-dual boot who can't use ROM Manager to reboot into recovery after installing u-boot 1.2? It was working fine with the old u-boot. I have been trying for hours to get to CWM by holding the "n" key with power button, it just won't work.

I just tried using a bootable CWM sd card to reflash beta 2, but still have the same problem.
[Nook Color Android Development] chisleu:
Have you tried reflashing CWM?

NOTE: If you don't see the Screen off Animation, go into spare parts and turn the animation speed down to normal. With fast it doesn't show.

Why is there a Screen On Animation setting and no screen on animation? lol
[Nook Color Android Development] :
Yeah, my idle time at 600 MHz is 3/4 of my time the NC is on. Weird...

Speaker buzz is still there as well (when screen is on only).
[Nook Color Android Development] HTCF4N:
Yes, try reflashing CWR using rom manager. It's actually kind of tricky to get into CWR with this u-boot for some reason. Hold down power + n until the text disappears and let go, if it restarts before the text disappears, do it again. This time the text will stay on longer, keep holding it until it disappears and let go of the keys and then you should get into CWR assuming your uRecImg and uRecRam with CWR is still good.
[Nook Color Android Development] paleh0rse:
Just switched mine to 187, and I'm liking it so far -- especially the size of the keyboard in portrait. Nice find!
[Nook Color Android Development] derekr:
@chisleu & HTCf4N

Thanx a bundle I didn't realize that you could reflash CWM thru ROM Manager. I upgraded to 3.0.2.8 and all is well with the world again.
[Nook Color Android Development] chisleu:
I set 187 but when I pull down the task bar, the center is off center. haha.

Plus I dislike everything being bigger.
[Nook Color Android Development] :
Yeah, I noticed that too. If you use the stock themes it's a little goofy, but with the HC looking one, all is well :)

EDIT: Wrong URL. This is meant for us: http://xdaforums.com/showthread.php?t=1041588
[Nook Color Android Development] seth.i.simmons:
Love the theme for the most part, but the status bar is way too unusably small :P When I bump the Lcddensity up to 187 everything but the status bar is way too big :\ love everything else, just wish I could adjust the status bar size!
[Nook Color Android Development] keyodi:
I compiled the u-boot based on the 1.2 b&n source and merged rookie1's dual boot changes. So far it seems to work, but I haven't done that much testing. Is anyone interested in testing it with the .32 kernel?
[Nook Color Android Development] paleh0rse:
Got a link? I'll give it a shot!
[Nook Color Android Development] yoopyoop:
Sign me up. I'll give it a crack.
[Nook Color Android Development] ts_mpls:
Anyone?

+10char
[Nook Color Android Development] :
So, as the poster somewhere above me mentioned, wifi tends to make the nook take its time sleeping. Here's a pic from when wifi was on:

Which brings me to point 2: Why am I hanging out at 600 MHz for pretty much the whole time. Can some other people grab cpuspy and tell me if they see similar things. I did a full wipe, and have very little on there right now, and nothing that would run in the background a lot.
[Nook Color Android Development] mkm1126:
What app do you recommend to use to set your dpi?
[Nook Color Android Development] keyodi:
ok, here it is. The only thing i forgot to add was the multi boot image at startup.

Just flash with CWM.

Edit: Updated the boot.bin to include the multi boot image and give credit to rookie1 during install.

Edit2: Removed attachment. Updated multi boot can be found at: http://xdaforums.com/showthread.php?t=959461
[Nook Color Android Development] capnblackleg:
Haven't had a single issue so far using beta2 and the 2.1 uboot. Thanks to all the devs for finally giving our batteries some life.
[Nook Color Android Development] :
root explorer. Open it, navigate to /system/ open build.prop, and change the value about display=161 to 187, back out to save it, and restart.
[Nook Color Android Development] chisleu:
more importantly, how did you get the HC icons for the back buttons and such? :)

Mine shows 2:00 of deep sleep and not a lot of 600. Are you plugged into USB making it not sleep?
[Nook Color Android Development] :
Haha, wouldn't you like to know ;)

Under the tablet tweaks thread, in murdock's OP (although he does't link to the right one for the NC):

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

I changed dpi to 187 for two reasons. I hate the split on the taskbar (seemingly fixed for a dpi of 161, but not others). Also, there is a bit of an offset line on sliders (like volume), which was fixed at 187. I'm not sure how you role chisleu, but those little gui things grind my gears. Anywho, yeah, it looks awesome and works well w/CM7.

No worries, I can read threads just fine ;) I was not plugged in, and have set the box to stay awake w/usb. However, coming back home and running on my network seems to have helped/resolved the issue. OSU is a bit weird w/their network...I'll test again tomorrow. Maybe the encryption has something to do with it?
[Nook Color Android Development] :
Sorry, use this one:

http://xdaforums.com/showthread.php?t=1041588
[Nook Color Android Development] yoopyoop:
On first inspection, it appears to be working perfectly. Thank you.
[Nook Color Android Development] dalingrin:
My guess that some of that time was with USB connected. The CPU will not idle below 600mhz with USB. This is a workaround made by B&N or TI to improve data transfer speeds over USB.
[Nook Color Android Development] :
I knew that about data transfer, but I was connected to the A/C adapter for some of the time, and didn't know it applied to that as well. Looking at the NC now shows much better sleep (5 mins at 600, hour in deep sleep). Thanks for clarifying.
[Nook Color Android Development] bekyndnunwind:
I just installed 2.6.32 beta 2 (w/ 1.2 uboot). <---Love it

As others have said, this build is snappy as hell! Even at 800mhz it isn't bad (but certainly can't wait for potential 1.1 and 1.3 OCs, it appears they will blow .29 kernel out of the water). Great work, devs.

I did have one issue after first boot: I waited for things to settle down, then set the Nook down for an hour or so to test the new sleep capabilities. When I came back to check CPUSpy, it wouldn't wake up. I tried hitting the power button, and the 'n' button, but it wouldn't respond (SOD??). Had to hold the power button (for ~8 seconds) to turn it off, then I turned it back on and it booted right up. It hasn't happened again...
[Nook Color Android Development] paleh0rse:
I set it manually by editing the /system/build.prop file and rebooting...
[Nook Color Android Development] :
So something like that happened to me. After charging the screen wouldn't turn on. I had to unplug, then only the power button would show the screen (after holding it for about 3 seconds).
[Nook Color Android Development] celyst:
Charged my NC overnight to ensure it was on full battery, wiped system, data and cache, installed beta 2, wiped battery stats and dalvik cache, and rebooted. Pretty responsive, set CPU to 925 and ondemand. Ran Quadrant and got around 1600+, which seems like a decent score. Gonna leave it on now to see how the battery fares after a few hours on sleep mode.
[Nook Color Android Development] rhester72:
OK - verygreen's u-boot is definitely *NOT* 1.1.0 stock. I applied beta 2 to my VG SD card install, which worked fine with the VG u-boot. As soon as I 'upgrade' the SD u-boot.bin to either the 1.2.0 stock or the recent (multi)U-boot, I get a "Loading..." screen followed by what appears to be a recovery-mode (i.e. blue sideways text) boot-loop.

Is it possible there's also something different/required about the RamDisk image or similar? VG's agnostic SD card image is too valuable (VERY easy SD-only operation and upgrades!) to give up, but trying to run the 32 kernel with the 1.1.0 u-boot also isn't a great idea.

Help?

Rodney
[Nook Color Android Development] paleh0rse:
Works perfectly, thank you!

Got 7.1.0 beta2 running on primary partitions, and stock 1.2 on the alternate -- both with perfect video playback... righteous! :)
[Nook Color Android Development] Skilover:
I hope this doesn't sound dumb , but can I flash beta build of CM7 with 2.6.32 Beta 2 on top of a relatively current nightly build (say Encore 69 or an earlier one)? Is the version of CM7 included with the package relatively similar? My clockwork recovery is the one I used to install CM7 in the first place, I assume it is relatively current and would assume to not have to create a new image--it's worked fine on the CM7 Encore beta's to date. Once I install this, should I not flash any new Encore CM7 betas, other than those specifically released for 2.6.32?
[Nook Color Android Development] Skilover:
I didn't realize that either! How did you do it, and where did you get 3.0.2.8 ?Thanks.
[Nook Color Android Development] bekyndnunwind:
I updated to the latest version of CWM via Rom Manager (took all of 5 seconds), then I went into recovery and flashed this: uboot-1.2-update.zip

I restarted my nook to make sure that the new boot was working... Went back into recovery and flashed 2.6.32 Beta 2.

Worked for me..
[Nook Color Android Development] Chahk:
Another SOD just now, and again no last_kmsg. I updated my u-boot to stock 1.2 to rule out any incompatibilities there. NC was off the charger throughout the evening.
[Nook Color Android Development] ehcan:
This works very well for my Nook running BN 1.2 on primary and CM7 7.0.3 on the dualboot partition. Thanks!!!!
[Nook Color Android Development] screech:
+1

when can we get beta3 or final?

Sent from npad.
[Nook Color Android Development] mkm1126:
Thanks! That's easy!
[Nook Color Android Development] hockeyfamily737:
Dalingrin just anounced in another thread that he'd be discontinuing support for the .29 kernel. So I'd say we'll be running this full time moving forward.
[Nook Color Android Development] xxiworld:
I flashed beta2 and the updated u-boot posted upthread. Video works nicely through Vitalplayer and the Youtube app, but Flash video seems very poor - lots of audio lag, jerky motion, and dropped frames.

I'm running Flash 10.2 from the Market, not the B&N version of flash. I've got Max CPU set to 925 and the Conservative governor on.

I didn't have this problem running 7.0.2 with the 3-31 OC kernel at 1100 mhz - Flash videos actually worked fairly well.

Are others seeing the same thing? And is this actually a bug or just an inevitable result of the lack of OC in this version of the kernel?
[Nook Color Android Development] dalingrin:
A new release candidate build will be going up momentarily. This build fixes the sleep issue when connected to USB. Doesn't mean it will sleep while connected to USB but it will not lock up anymore. So, no need to set Settings->Applications->Debugging->Stay Awake.
[Nook Color Android Development] paleh0rse:
Three problems Im having with beta2 so far:

1) Pandora app FC's during sign-in. [EDIT: ran FixPermissions from RomManager, and it seems to have fixed this problem]

2) Can't purchase (paid) apps using Market app -- Causes vendor.apk FC. Free and previously purchased apps download, install, and update without issues. (Tried both 3/07 and 5/03 GAPPS).

3) HBO GO app still FC's during sign-in. Any chance we can get the IMEI issue fixed/addressed in the actual build?

Can anyone confirm these?
[Nook Color Android Development] mjb413:
pandora fine here. dal's beta v2. i am using v1.5.6 of pandora.

downloaded a previously paid for app without issues. 3/07 gapps. haven't paid for a new app to test.
[Nook Color Android Development] paleh0rse:
I managed to fix Pandora. As for Market apps, I should clarify that previously paid for apps AND free apps work fine. But, when I go to purchase ADW Ex, it keeps causing an FC when I click on the button with the price on it.