yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] breebauer:
I posted in the kernel thread but just in case this helps anyone:

I tried all of the 7.0x and nightly builds and each of the. 29 kernels, and was one of the few unlucky people who couldn't OC past 1100 without it totally locking up.

On Beta 3.1 with the OC kernel, (upgraded to 1.2 uboot, and wiped data, & caches) and now I can set it to 1200.

I haven't had any issues; hasn't locked up, market works, wifi works.

And CPUspy says that I've spent time at 1200.

I'm happy.

Thanks again Dalingrin!

(Seroiusly- I still can't believe you did any of this during finals. You could've just handed your professors my nook and told them to have a nice day... :-)
[Nook Color Android Development] breebauer:
Forgot to say that video is great too.
[Nook Color Android Development] newellj79:
Try downloading gmail from the market. Under settings, accounts, your gmail account, check it to sync.
[Nook Color Android Development] boogerboy72:
this is the correct order? Is there a thread on how to update to the new u-boot? i cant find one to save my life.
[Nook Color Android Development] Ronin3178:
Link in this post http://xdaforums.com/showpost.php?p=11452450&postcount=19 to get new uboot.
[Nook Color Android Development] bucketheadmn:
Upgraded to 3.1 beta yesterday and deep sleep is great - did not lose any battery over night! Simply amazing!!

One thing that I noticed and not sure if it is the ROM or Market. While running 7.0.2 I was able to install directly from market.android.com as my NC would be listed as a device. However, after updating NC no longer shows up in market online. No big deal, but did not see it mentioned previously in thread.

Dal thanks for all the hard work with this! Still can not believe how much use we get out of our NC.
[Nook Color Android Development] ianPhillips1:
8)

Dal, I am at a loss for words, this time you have indeed blown my mind,thx for your dedication.
[Nook Color Android Development] bitnerd:
yeah, I lost the bar once at one point and had it randomly return later. The strange thing was that the buttons still worked even if you couldn't see them

This was in reference to derekr's post above
[Nook Color Android Development] stevemp:
Originally Posted by boogerboy72 View Post

this is the correct order? Is there a thread on how to update to the new u-boot? i cant find one to save my life.

Worked for me, I was on CM7.0.3 and it's been good so far. Only problem has been with the browser crashing on crackle.com

Link to CM7.1 http://coachz.inetpro.org/~dalingrin/nook/CM7/update-cm-7.1.0-RC0-encore-2.6.32-beta3.1.zip

Link to uboot http://www.mediafire.com/?zyg5yrc6ucqcie7

Link to oc kernel http://coachz.inetpro.org/~dalingrin/nook/kernels/051311/update-cm7-dalingrin-2.6.32-emmc-051311.zip
[Nook Color Android Development] botossi:
location...

thanks dal and the whole team foe the excelent work, beta 3 is awesome! just one thing i noticed is that the location service doesnt work in programs like weather, go weather etc but work in maps... is that normal? i came from stock 1.2 with MN full wiped...
[Nook Color Android Development] MedLine:
finally had SOD :(.

1.2 uBoot + 2.6.32 beta3.1 + 2.6.32 OC Kernel (which in turn flashed over beta2 ... beta1 ... n64 ... all fomatting only cache/dalvik cache each time)

300/1200 smartass

last night misc reading on Nook, hit power button to go standby, unplugged. this morning woke up and screen would not come on with either "N" or pb. it had definitely powered up, because i can hear hissing from speaker. i connected to USB and could adb in. pressing "N" produces this message:

I/power ( 1073): *** set_screen_state 1
D/WifiService( 1073): ACTION_SCREEN_ON

pressing pb then produces this:

I/power ( 1073): *** set_screen_state 0
D/WifiService( 1073): ACTION_SCREEN_OFF

repeatedly pressing "N" and pb alternately produces this:

I/power ( 1073): *** set_screen_state 1
D/WifiService( 1073): ACTION_SCREEN_ON
I/power ( 1073): *** set_screen_state 0
D/WifiService( 1073): ACTION_SCREEN_OFF
D/WifiService( 1073): setting ACTION_DEVICE_IDLE timer for 900000ms
D/KeyguardViewMediator( 1073): wakeWhenReadyLocked(3)
I/power ( 1073): *** set_screen_state 1
D/WifiService( 1073): ACTION_SCREEN_ON
I/power ( 1073): *** set_screen_state 0
D/WifiService( 1073): ACTION_SCREEN_OFF

went on trying various button presses of different duration. screen just never comes on.

will hard reboot and keep rolling with 2.6.32 beta3 + OC kernel. i'm really liking that smartass governor. with interactive/ondemand governor, screen transitions sometimes feel harsh, like a bit of turbo lag that kicks in at the wrong time. with smartass governor and 300/1200 OC things feel assured, controlled, like you're rolling along always with serious torque behind you.

PM'ed logcat, dmesg, and last_kmsg to dalingrin.

EDIT: wanna add that this the one, and only one, SOD i've had since the current round of 2.6.32 beta started early this week.

2nd EDIT: also no general wonkiness or app-specific errors so far.
[Nook Color Android Development] iDidItAll4theNookie:
Just using the.size agnostic approach that is one of the dev threads. Just burned the image, dropped the beta to the FAT partition and booted. I started over with a fresh flash of the card, as I'm not sure if using recovery mode with an old version of CN installed will work.
[Nook Color Android Development] henel321:
I can confirm this one. Happened to me with both stock 300-925 ondemand and with oc and 300-1200 smartass... No hissing though! :)
[Nook Color Android Development] Animec:
Silly question perhaps but do you guys turn your wifi off for the night? what's your wifi sleep policy set to?
[Nook Color Android Development] Ronin3178:
I left my wifi on all night, and maybe had it sleeping about a max of 6-7hrs, but no SOD. The wifi disconnects by itself after a bit, and reconnects upon wake no problem for me. I think I only lost about 1% battery in that 6-7hrs of sleep.
[Nook Color Android Development] khaytsus:
I had SOD once yesterday evening, wouldn't wake up. And then after rebooting about 30m later I had a hard lock, left it for 5-10 minutes before I gave up and hard rebooted with power button for 30s.
[Nook Color Android Development] newellj79:
Just happened to me.
[Nook Color Android Development] byproxy:
i'm having some random freeze-ups that require a force reboot to fix.

i'm running latest .32 cm7 and kernel w/ 300/1200 smartass. tried dropping to 300/1100 and still am getting freeze-ups.

not sure if it's the oc kernel or the .32 software. just thought i'd post for tracking purposes or whatever.

thanks!
[Nook Color Android Development] junkrobot:
So, I installed all the most recent updates including the OC kernel, but I've noticed something odd about the status bar:

There's a weird little seam of what looks like a pixel in width right in the middle, so it looks like the bar is tearing, if that makes any sense.

This is minor, I realize, but is there any way to fix this?

Dal, this is awesome. I can't believe my nook is even faster now.
[Nook Color Android Development] chisleu:
Yes. Since the 3.1 I have had several times that I had to long hold the power button to get it to shutdown. This morning while using google maps navigation the screen went black and I can't get it to turn on. When I get home I will try putting it on usb/charge. I hope I don't have to pull the battery.

I long press it for like 10 seconds and then hold it to boot and nothing. :(

Edit: yeah it just booted.... again this wasn't SOD although I have had crashes while sleeping. This was a straight up crash.

Edit: yeah it just crashed again while booting. When I can get it to boot I will go back to adw ex from adb shell and if it crashes again I will drop back to 1100 from 1200 to help eliminate problems.
[Nook Color Android Development] MedLine:
wanna clarify something for people who might not be aware.

with each 2.6.29 CM7 nightly, ever since the first one, there is a userspace wakelock designated "1" written to /sys/power/wake_lock in init at bootup. this can be canceled in userspace with the following command:

echo "1" > /sys/power/wake_unlock

when i did that in CM7 n64 i get sod EACH AND EVERY time i enter standby on my Nook.

this wakelock was finally removed in the current 2.6.32 betas, which is why we get deep sleep.

at the current rate, if it holds up, i get 1 sod in ~200 standby. even if it never gets fixed beyond that, by some act of Android miracle, i'm sticking with 2.6.32. i really hated not getting deep sleep in standby, and CM7 is just too much better than stock B&N 1.2. just my 0.02.
[Nook Color Android Development] junkrobot:
Damn, I take it back. I just had a whole slew of force closes on Gmail and Titanium Backup. I'm going to restore to my last stable point and try to start over from the beginning. Either that or I might just wait until it's out of beta. It was worth a shot, though. Awesome stuff.
[Nook Color Android Development] deadbot1:
Had an issue last night.

With stock charger plugged in....pressed power button to turn screen off. Screen went blank...backlight stayed on. Hit power button a second time...backlight went off. Hit buttons third time...screen woke up. Hit a forth time...screen went to sleep properly. Problem has not resurfaced since. Have not power cycled to see if it does.

Edit: disregard this I guess..been trying everything I can...can't seem to get it to happen again.

Second edit: found a way to trigger this...had my nook on the stock cable/charger when the cord wiggled loose. After the power became disconnected, the screen was off...backlight was on. Hitting the home button had no effect...power button made backlight go off...second press everything goes back to normal. This is repeatable on my end.
[Nook Color Android Development] Ronin3178:
For all the bugs I am seeing come up, I am having none of them. I modified the build.prop (HTC, vision) so I could use Netflix, it runs awesome!! Haven't charged the thing in over 24hrs, still around 15% No FC's, watching NFlix last night for an hour only used 4% battery. AngB's runs great, robo dfense awesome.

Ronin
[Nook Color Android Development] Moxie3000:
Last night I went back and did a fresh re-flash of 3.1 (following the instructions to the letter) with OC kernel and everything is beautiful now...have been hopelessly addicted to digging dirt since.

Thanks!
[Nook Color Android Development] thechrisventura:
Will the new U-boot prevent me from accessing my second partition? I have my Nook set up with multi-boot and use the second partition (Stock) very often and can't really afford to give it up. I know someone raised this question earlier, but I was out of the loop for a few days (had exams, usually follow this very diligently) and cannot find the answer for the life of me. Thank you all!
[Nook Color Android Development] chisleu:
Now that is awesome. I might sign up for netflix. Hah
[Nook Color Android Development] junkrobot:
I'm pretty sad about it. I was using the thing on and off for like a half an hour and barely saw any battery drain. It's remarkable stuff. I'm just unsure if I did something wrong to cause all the issues I had or if I ought to wait it out more.
[Nook Color Android Development] Ronin3178:
I was running Nightly 70 before going to this. I installed new uboot, then wiped system, cache, installed beta, kernel, wiped davlik, installed 0307 gapps. Has been running great. If thats any help...
[Nook Color Android Development] junkrobot:
I'll give this a shot again later today. Thanks for the tips! I tried to update from Phiremod 6.2, which may have been the problem for all I know. I'm getting less squeamish about flashing new stuff now that I have the hang of just booting into recovery and going back to a daily that worked for me.
[Nook Color Android Development] Ronin3178:
I hear you about the getting less squeamish, I was there not too long ago, but the Nook has gotten me over that. if you are feeling real adventurous, check out this thread to get netflix up and running on your NC.

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

basically, since I haven't paid for root explorer, I edited the build.prop in the beta .zip and then flashed. for the .32 kernels use the HTC, Vision settings. Samsung gives you chipmunk audio/video

Good Luck
[Nook Color Android Development] keyodi:
Yes, but you can download the updated multi-boot here: http://xdaforums.com/showthread.php?t=959461, look for "My modified u-boot.bin based on B&N 1.2 source"
[Nook Color Android Development] fearthepenguin:
Just upgraded to the 5.13 beta. Wow!
[Nook Color Android Development] bachviet:
I just installed this over phiremod 6.2. These are the steps.

1. Update ROM Manager and recovery to latest versions (4.2.0.2 and 3.0.2.8 respectively).

2. From ROM Manager, boot into recovery.

3. Format cache and Dalvik-cache.

4. Flash the B&N 1.2 uBoot.

5. Flash ROM.

6. Flash the 2.6.32 kernel (5/13).

7. Flash gapps-gb-20110307-signed.zip.

8. Reboot then wait 5 minutes after boot.

Everything should just work.
[Nook Color Android Development] lafester:
I've had a few SODs if thats what they were. Screen won't turn on after being asleep for awhile. If you max out the volume you can hear it make a little beep so I know the power is on, just no screen.

power off, then power back on to fix.

everything else works great. fast and smooth. much fewer hangups when scrolling.

great work dal!
[Nook Color Android Development] furius:
I did exactly the same steps over CM7.0.2 and all went well, I still have all my apps and settings

No data/system wipe is required.

awesome!

thanks dalingrin
[Nook Color Android Development] chadamir:
Anyone notice that their battery reading is off? I just had mine die while my fiance was using it, plugged it in and it read 30% and 3700mv.
[Nook Color Android Development] Colchiro:
Delete your battery stats in recovery and recharge it.
[Nook Color Android Development] chisleu:
I got it home and it said "battery too low to power on."

I'm not sure if it drained while it was crashed (it was charged last night) or if my battery stats were off. I'm going to fully charge it and try booting.
[Nook Color Android Development] paleh0rse:
Same here. I swapped in a modded framework.jar to get HBO GO up and running, and I changed the build.prop for Netflix... so far, I'm sailing with no FC's, SODs, or any other errors. Running at 300/1200 ondemand.

Good times! :)
[Nook Color Android Development] Ronin3178:
Battery booster is registering my nook as 100% right now, but the stock nook charger is still orange. Reading abt 4170mV. Gonna go till the charger cable reads green, then go into CWR and reset battery stats.
[Nook Color Android Development] chadamir:
Same, I'm at 100 percent now with an orange cable and I'm under 4100.
[Nook Color Android Development] junkrobot:
Thanks! I'll try this right now. I hope Titanium doesn't keep force closing on me.
[Nook Color Android Development] newellj79:
Is anybody still losing wifi connection where the icon still shows signal but u cannot transfer any data? I can reconnect real fast by toggleing it with a widget but it is still a pain. Granted, it is not near as bad as it was for me using the nightlies. Still loving this build!!!! Beta 3.1 and oc kernel.
[Nook Color Android Development] chadamir:
Well, I got it to 4195mv and it wasn't buding. Light was still orange except when I'd restart it'd turn green periodically for a second. Not sure how the light works so it's hard to tell but I was afraid of overcharging or something weird happening.

Edit: after restarting now I'm being told its at 4100 so I give up on getting a correct reading, I'm not chancing it.
[Nook Color Android Development] newellj79:
Weird, action buttons on the status bar just disappeared but they still work even though u can't see them. I have heard of this happening to other people too.
[Nook Color Android Development] 12paq:
Nope mine are gone. The combination of upgrading my router software dd-wrt (the most significant change I believe), no aes and the new Kernel drivers on the new oc kernels, I'm hoping to never see the problem again. So far so good.

I did just experiance a dead Nook, possibly SOD for the first time. I was fully charged and picked the Nook up and it was just off and would not wake. It was unresponsive to even holding the power button down at first. Within a few minutes I was able to get it to power back on. Got my pulse rate up that's for sure, I was thinking of hocky guy and his dead Nook. (hope he's ok)

Still no complaints here, only praise, this little reader is amazing now. Thanks!
[Nook Color Android Development] Ronin3178:
Mine topped out around 4200mV, reboot into CWR and reset batt stats x2. We will see how it goes over the next day or so.
[Nook Color Android Development] newellj79:
I did not do a complete wipe, I flashed over nightly 70. I'm thinking tomorrow I might use titanium and do a complete wipe and fresh install.
[Nook Color Android Development] junkrobot:
I got all my apps working just fine!

My only gripe is the middle of the status bar still has a weird little tear in it as if its dimensions are incorrect. I'm trying to search for a solution since I know it's probably out there, I'm just not sure how to search for it. The terminology eludes me!
[Nook Color Android Development] khaytsus:
I've had 3 times the last 14 or so hours since installing 2.6.32 beta 3.1 where it wouldn't wake up, SOD I presume. And one hard lock where the screen froze and I had to 30s power button to turn it off.

I'm using the stock kernel, not the OC one, I believe I was at 800mhz at least one time, but 925mhz the other two times... I'm NOT yet using the u-boot.bin as verygreen hadn't updated it yet, but his thread reflects he's got an updated version so I'm going to try it next time if it's still possible there's something related to SOD or lockup's and the u-boot.bin.

Both times I had just put the NC down after being finished with it and picked it up later and it wouldn't turn on after multiple N or Power button presses.. I was patient each time, no joy, had to reboot.

I've gone back to the original 2.6.32 test build which doesn't have any of those issues, although I do see more phantom CPU usage.. Oh well. :) Was the original 2.6.32 test build verygreen's .32 and the ones since the B&N kernel? I wonder what's different..

Look forward to more builds to test Dal :)
[Nook Color Android Development] Calla969:
Does anyone else have trouble with the power button? When I shut the screen off using the power button, the screen turns off then back on immediately. I usually have do this 3 or 4 times before the screen will stay off. Also, when I hold the power button to access the shutdown menu, the screen powers off before I can select an option. Again, I have to mess with this several times before I can select an option.

Sent from my NookColor
[Nook Color Android Development] Ophbalance:
So far, I've had a solid 9 (almost straight) hours of reading in today, and it's not behaved badly on me yet on Beta 3.1. It did, however, seem a bit warm towards the end of about 7 hours or so near the "n", but it could be I've noticed this before.
[Nook Color Android Development] lyam23:
You want to search for changing your dpi.
[Nook Color Android Development] :
I like 187 :)
[Nook Color Android Development] junkrobot:
Thanks again, everyone! Everything is working great now! Y'all are the best.

I used the LCDDensity app, but it doesn't seem as if it sticks after restart. Such silly little problems! Ha.
[Nook Color Android Development] 12paq:
Ah, but as you know, those silly little problems are so fun to work on!
[Nook Color Android Development] lyam23:
You can manually edit it somewhere. maybe the build.prop? It sticks then.
[Nook Color Android Development] jmak10:
Why 187 instead of 185 or 190? I see a lot of strange numbers for this setting and was wondering why.

Thanks,

jmak
[Nook Color Android Development] junkrobot:
Mere moments later I edited the build.prop and now all is well. This is a lot of fun!
[Nook Color Android Development] :
I'm using the honeycomb theme (see my sig). 187 is large enough I don't have to worry about pressing stuff, but small enough it doesn't consume the whole screen. Also, it fixes the vertical line thingy as well as a HC theme specific thing that comes up with sliders being a bit off.

Also, using any sort of root file browser (root explorer, for example), you can navigate to /system/ then find the build.prop file, scroll about have way down, and where it mentions density=161, you can change it to the value you want.
[Nook Color Android Development] jmak10:
I just changed mine to 192, but when searching I found all kinds of specific values like 181, 187, 192, 204 and was just curious if there was some reason for it besides how the screen looks. Why not use 180, 185, 190, and 205? I couldn't see the difference between 190 and 192 but used 192 because other people were using it.
[Nook Color Android Development] hockeyfamily737:
That dead Nook's still sitting in my dresser. Bought another one yesterday. I'm back in business.

sent from my Ginger-Hero CDMA
[Nook Color Android Development] Ronin3178:
What happened to your Nook? My impression was that u can't brick a nook b/c it will always boot from sd
[Nook Color Android Development] geekyradical:
Anyone else having problems with market crashing? It comes up as a white screen then closes.
[Nook Color Android Development] hockeyfamily737:
I was testing Beta 2 and put my book to sleep while charging to see what would happen (against advisement from the OP)....Couldn't wake it, power it down, or ADB connect. To this day it is totally unresponsive. It'll die someday and restart im sure, but I wasn't about to wait any longer.

sent from my Ginger-Hero CDMA
[Nook Color Android Development] iDidItAll4theNookie:
I went all-in this morning and installed to the emmc. Been very happy so far. All apps install, gReader works, and I left it in sleep for 6 hours and battery didnt even drop a %. I don't know if I could ever own a regular tablet, as this whole experience has been as fun as actually using the device. Is it wrong that I have never read a book on my NC? I may start a pole about that one... :D
[Nook Color Android Development] Iucas:
+1 here. I had flashed the Beta 3.1 yesterday. I wipe everything except the data. Everything is perfect after the flash. But I still get my battery drain down from 46 to 36 last night. It seems the deep sleep does not work for my nc.
[Nook Color Android Development] geekyradical:
Solved the issue, if anyone else is having it, by reflashing the gapps using the ROM manager.
[Nook Color Android Development] aludal:
I somehow lost my uboot.bin.bak, so can someone show me the link to an original (.29) flashable uboot .zip.

If there's no such thing, then please what exactly I need to edit in the .32 uboot's script to revert to what it was at .29.

I'm going back to .29: sure, it's nice and snappy UI, but I've lost half of my streaming video, Crackle, e.g.

Thank you in advance
[Nook Color Android Development] :
1st sod I think. Running smartass, latest everything. Touched it once today. Just opened opera. No kernel panic. Was sleeping, then I wouldn't wake up until hard reset.
[Nook Color Android Development] davidukfl:
came from 1.2 rooted and installed this. It's running perfect, no issues at all
[Nook Color Android Development] screech:
Freezes on Beta2 and Beta3.1

Also not using the OC kernel, and what I have seen a couple of times now on Beta2 and Beta3.1 is that when sleeping, it just hangs.

I need to do the N button + power button trick to reset the Nook to get it back.

Does anyone know where syslog happens to live on the filesystem ?
[Nook Color Android Development] olm3ca:
Same issue with sleep causing it to hang. Latest OC kernel and beta 3, left it overnight w/out charger at 90% charge and this morning it was non-responsive. After plugging it in to the charger it booted and was at 50% charge, strange.
[Nook Color Android Development] joe91584:
Great Kernel and rom it's smoking... Only issue is if I use the Ondemand governor the Nook locks up after 20-30 mins of hard use.

Has anyone else had this issue?