yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Awats:
I only noticed that one time the wi-fi wasn't available for a split second after a 1 hour-ish sleep but it quickly came up. The message popped up and then went away quickly.

I have yet to need to do anything odd to use the Nook. I am on 7.0.3 and overclocked at 1300MHz.
[Nook Color Android Development] Chahk:
No, it was on a desk not connected to anything. Can't remember if it went to sleep on its own our if I turned off the screen manually.
[Nook Color Android Development] colorado_al:
Working pretty well for me on SD card. Only real issue I have had is FC on JuicePlotter which I use to monitor battery life, so no flashy graphics of battery use. Seems to mostly work though. Also fairly quick even at 925.

Thanks for the great work!
[Nook Color Android Development] dookie23:
I read that there is a GC bug in the code that slows down ListViews. read that on Dalingrin's twitter page. Hope someone will look at it soon. The guy who said that also said it had nothing to do with OC'ed or non-OC'ed kernel.
[Nook Color Android Development] dalingrin:
This only affects scrolling through listviews though. Web browsers and such are not affected.
[Nook Color Android Development] Calla969:
After watching YouTube the Nook gets really laggy until a reboot.
[Nook Color Android Development] trsanning:
The new build didn't fix my sdcard issues. Is there something special you gotta do?
[Nook Color Android Development] dalingrin:
Can someone with this issue give me logs(logcat and dmesg)?

I have never seen this happen.

Updated beta build is on OP. This fixes apps on SD card.
[Nook Color Android Development] fattire:
A reminder to anyone who's experiencing a true sleep of death (as in it doesn't wake back up), the next time you reboot, check /proc/last_kmsg and see if at the end there was a kernel panic. If so, might wanna paste it somewhere so everyone here can check it out and laugh at your misfortune. I mean try to fix it.
[Nook Color Android Development] Calla969:
Of course, I download alogcat and now it seems fine after watching YouTube. I'll keep an eye on it and get a logcat if it happenes again. I watched YouTube twice before and my nook became useless both times.
[Nook Color Android Development] lafester:
Hey Dalingrin, since you are here could you update the op so people stop trying to flash your OC kernel with the latest builds of cm7? There seems to be a file extension problem and nobody reads the threads.

Thanks :)

And thanks for all the work with the new kernel!
[Nook Color Android Development] pbcal:
Nice. App on SD works now. Thanks for the great release.:)
[Nook Color Android Development] paleh0rse:
With which build? The separate modified uImage?
[Nook Color Android Development] hockeyfamily737:
Hmmm...... I called that one at 5:30 this morning. Figured someone would try to extract the .32 kernel from the test builds and install it in a stable build too. Haven't seen that one yet. LOL
[Nook Color Android Development] lafester:
No, lol. I said the OC kernel that doesn't play nice with the last few builds. Every day 4 or 5 new posts with people asking why they are bootlooping.
[Nook Color Android Development] lafester:
The build Dal just posted.
[Nook Color Android Development] hockeyfamily737:
My bad...I thought you were talking about people taking the .29 OC kernel and trying to use it with this beta build. I know the other problem as well. Have been extinguishing those fires since around Saturday. Sorry to mire this thread.....back to the topic at hand.
[Nook Color Android Development] vtmike:
http://db.tt/h6y4QrV

It didn't seem as bad after upgrading to beta2 but still slowed down noticeably. Hope this may help.
[Nook Color Android Development] derekr:
The apps are back (without having to do anything) with the new beta, but geez are those Angry Birds pissed at being banished all day! :D
[Nook Color Android Development] vengence_angels:
I flashed the beta 2 ROM and got into bootloop..

and now i cant even boot into CWM..

anyway to fix this problem?

hope i do not have to restore to stock..
[Nook Color Android Development] lafester:
hold power button until nook turns off. then hold n key and power.
[Nook Color Android Development] vengence_angels:
did that..

but still doesnt load in CWM..

tried all kinds of button combinations but still cant boot into CWM..
[Nook Color Android Development] britoso:
after flashing the 1.3GHz 4/24 kernel (with ext4 fix) all my buttons (power,n and voice buttons) do nothing (I have an edited qwerty.kl file) Anyone have a solution?

edit: the problem was root explorer, it gives nobody read permissions on copied files!
[Nook Color Android Development] lafester:
Its kind of touchy but it will go into cwr if you do it right.

Let go of the power button after 5 seconds or so but do not let go of the n key.

Other option is to load a recovery sd card. Look for the thread in this forum.
[Nook Color Android Development] britoso:
When your nook is booting and is recognized by adb, issue the 'adb reboot recovery' command.
[Nook Color Android Development] lafester:
so how do you reproduce it?
[Nook Color Android Development] dalingrin:
Please be explicit about the force closes.

Known force closes:

Maps 5.1.0, this happens on other tablets running Gingerbread as well.

Market during purchase, also happens on other tablets on Gingerbread.
[Nook Color Android Development] tominabox1:
Twitter FCs when I try to post something, doesnt do that on my Droid w/ cm7.
[Nook Color Android Development] mustafazr:
Pandora FCs (I think this one is well known)

Live Holdem Poker FCs on startup (used to FC on Nookie Froyo too, Stock Eclair was fine)

Edit: Thanks for all the hard work on CM! Don't mean to sound demanding on the FC issues - just FYI.
[Nook Color Android Development] bdcrim:
I appreciate the response. The market question seems to be in line with a lot of other market questions and comments in this thread. Even though I tend to disagree with the question placement, I do appreciate your help.
[Nook Color Android Development] crashdau:
Has anyone been experiencing random reboots? I have a couple on encore v3 and now v4. There doesn't appear to any rhyme or reason to it. Not show stopping but curous.

Any suggestions on how to dig in further to this?
[Nook Color Android Development] tominabox1:
I've had one since going to the nightlies - attributed it to the 1.1ghz kernel based on experience I've had with OC'd kernels on my phone
[Nook Color Android Development] crashdau:
Interesting point, I'm running 1.1G from Dalingrin when on both v3 and v4.
[Nook Color Android Development] racks11479:
Forgive me if I'm posting in the wrong thread. If so, please move accordingly.

I'm running CM7 nightly v3 on dualboot setup by Rookie1.

I see alot of people are still having issues with their apps force closing on them. And I just wanted to to see if what I did to modify my framework.jar has any aspect as to why some of my apps like Market, Pandora, Live Holdem Poker, Gameloft games & even the XDA app that people said can't survive a login is now running like normal for me without the FC'ing issue.

**Credit goes to the original devs who came up with the patch**

I took the TelephonyManager.patch from http://xdaforums.com/showthread.php?t=955847 and modified some lines to correspond to the framework.jar from the CM7 Rom when patched.

I then backed up my original framework.jar file and replaced it with the new one. And after rebooting. Most (Maps 5.1.0 is still crashing on me), if not all of my apps that were FC'ing before is now running as normal.

I believe the nook didn't have an AndroidID/IMEI# before. But after the patch, I ran "My IMEI" and was able to retrieve one. Could this be the cause for the apps to FC on launch as it is looking for one and doesn't see it?

**Please use my experience as a guide and always do a backup before you try anything new. You are solely responsible for anything that happens to your device**

I've included my patched framework.jar file if anyone wants to take a look at it.

Just my experience. Hope this helps in someway, if not i'll edit accordingly.

Thank you devs for all the hard work you've put in to get this running!
[Nook Color Android Development] ericman77:
which gapps do i install for this?
[Nook Color Android Development] philburkhardt:
Did you replace the file with Root Explorer, or did you push via ADB?
[Nook Color Android Development] racks11479:
I replaced it with root explorer.
[Nook Color Android Development] racks11479:
Get it here http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps

The CM7 version
[Nook Color Android Development] ericman77:
gapps wont install for me.
[Nook Color Android Development] j.a:
Are you installing it from recovery? Gapps zip file has to be installed through recovery.
[Nook Color Android Development] ericman77:
Yeah tried that. Flashed the gapps in cwr sd but dont have any gapps. Tried formating system,data,and cache reinstalled the rom then gapps again still nothing.
[Nook Color Android Development] dalingrin:
Thanks for the post. I'm interested to hear if the AndroidID has some impact on the force closes.

Make sure market is not installed. The new CM7 gapps only visibly install market by default.
[Nook Color Android Development] ericman77:
Nope no market installed. Even checked system/app and its not there. Im trying to install this one cm7 md5: 45e175c25a498c8945c543d92d92e782 is this the correct one?
[Nook Color Android Development] philburkhardt:
This is definitely working!

I was able to start Gun Bros. for the first time since my nook was on Eclair. Before this patch, it would force close as soon as yoiu tried to start it. The XDA app is also working properly.

On a side note, I am jot sure how I did it, but Maps 5.1 definitely works for me. I have been restoring the backup from when I was on froyo, and I haven't had a problem.

Screenshots are all black, so I took a picture. :D
[Nook Color Android Development] racks11479:
Awesome! Good to hear a confirmation. Maybe I'll start a new thread for this as a temporary fix for the force closing issues?
[Nook Color Android Development] dalingrin:
Did you only patch the framework?
[Nook Color Android Development] vengence_angels:
previously i was able to load into the CWM with the n+powerkey..

but now i cant..

at work now so cant load a recovery sd card..

have to wait til tonight before loading the recovery sd card..

sighhh..

was dying to try out the beta2..
[Nook Color Android Development] hockeyfamily737:
I had SOD this morning in the middle of boot after install..... USB to pc/ac power did not wake it. Let sit a couple of hours and it re-started fine. No logcat though :(
[Nook Color Android Development] Jimbo67:
Being my personal fire extinguisher, is Greatly Apreciated! :)
[Nook Color Android Development] saproll:
iptables/netfilter still missing...i'm using ASP proxy and still won't work....
[Nook Color Android Development] britoso:
nvm,its not the SOD, its because of the key mapping issue I'm having...Even the 'n' key does not work.
[Nook Color Android Development] jimvsmij:
So I tried to flash the 7.0.3 and my nook went into permanent orange screen. I then flashed back to 7.0.2 and everything seemed to be back to normal. Today I noticed that the App Market did not load. I checked the settings and under "Accounts and Sync" my gmail account was not listed anymore. It doesn't let me add my gmail account. I think the reason that I cannot get into the Market is because the gmail account is not linked, but I could be wrong.

Can anyone give me some advice to bring it back so I can access Market??

One other think I noticed was the WiFi indicator is all white instead of green. I don't know what that is about either.
[Nook Color Android Development] dalingrin:
How many times did you need to run the YouTube app before it happened? Have you updated to 1.2 in the past? I'm starting to wonder if some of this is from people running different u-boot bootloaders. What does it say on the screen when you first boot the Nook?

Btw. its not related to your problem most likely, but I'd seriously consider removing the "Elixir" app. Its got to be slowing your nook down as active as it is in the background.

So you cannot wake your Nook using the power button or the "N" button?

I can't reproduce a SOD(unless I have USB connected). Perhaps this is also related to the u-boot version.
[Nook Color Android Development] MedLine:
just my 0.02 but this seems like a contradiction in terms. after Settings->Applications->Development->Stay Awake, CPU never idles below 300MHz (or whatever min set at) if USB connected, i.e. Nook never goes into deep sleep. thus, can you really call not waking up from that standby state SOD?

in any event i have no SOD whatsoever to report all day.
[Nook Color Android Development] jdmeer:
Reflash LATEST gapps from the cm wiki.

White means not connected to google server.

Edit: This really belongs on the user thread.

Thought that's where I was when I answered.....

Edit 2: actually now that I think of if it I'm not sure the latest gapps is in the wiki. SEARCH for the one from this month.

Sent from my Cm7 Nook Color.
[Nook Color Android Development] jimvsmij:
After not having luck finding gapps in the forum I googled and found a gapps from this month: gapps-mdpi-20110501-signed.zip

I flashed it and now the WiFi doesn't pick up any signal at all. I tried to reflash the 7.0.2 and it's still the same. How do I get my WiFi to work again?

Sorry if I am in the wrong section...
[Nook Color Android Development] henel321:
I've had two hard lockups on the new build. I was testing if video was still working by running my "spongebob" test (i.e. trying to play an xvid episode for my four year old... :p )

1. Tried playing it using MoboPlayer, app starts, showing playback controls, no sound, no video, app exits (without FC error).

2. Tried playing it using mVideoplayer, app starts, showing playback controls, no sound, no video, app exits (without FC error).

3. Tried playing it using build-in-video player. B-o-o-m - hard lockup - nothing else to do but holding in power and letting it power off.

No strange errors in the logs or kmesg, in this case unfortunately no kernel panic... :(

....but WiFi and sleep works well! :D
[Nook Color Android Development] dalingrin:
My point was to say that I have only experienced SOD with USB and that was before enabling Settings->Applications->Development->Stay Awake

Please report which version of u-boot you have. Either the version from stock 1.1 or 1.2. The 1.2 version says "Reading Forever" or something like that when you boot the Nook. I really think this video issue is u-boot and not a problem with the build. I've torture tested both video and sleep and cannot reproduce any of these problems.
[Nook Color Android Development] hockeyfamily737:
I came straight from the 1.1 firmware (touch the future of reading) to CM7 and have had no problems with video from internal player on this build and I've been on and off with it all day and night.
[Nook Color Android Development] psychoace:
You downloaded the wrong one. It needs to say GB not MDPI. Also the date should be 20110503 for the latest.
[Nook Color Android Development] lschroeder:
If I am going from update-cm-7.1.0-RC0-encore-2.6.32-signed.zip to update-cm-7.1.0-RC0-encore-2.6.32-beta2.zip do I need to get back to full charge before flashing?

If going back to full charge I also need to "You need to disable sleep when connected to usb. Goto Settings->Applications->Development->Stay Awake", when connect to the charger. Correct?

By the way I used [ROM][CM7] Size-agnostic SD Card image and CM7 installer for SD Cards. with updater to install update-cm-7.1.0-RC0-encore-2.6.32-signed.zip and plan to use it again to install beta2 version. Anybody else running these 2.6.32 ROM's from sd cards?
[Nook Color Android Development] fabienk:
http://goo-inside.me/gapps/

use the "CyanogenMod 7	20110307 Universal"
[Nook Color Android Development] henel321:
I'm coming from 1.1 i.e. "Touch the future of reading".. TBH I've never even booted the Nook with anything other than Deepblue HC or CM6/7.. :-)

I will try to reproduce and also see if there is some logging later today when I'm not at work....
[Nook Color Android Development] RoboRay:
I think this is a great way to teach people the importance of reading the directions.

Any way, if the don't read the current posts on it, why are they going to go back and read the OP (again)?
[Nook Color Android Development] Chahk:
SOD again. There was no last_kmsg:

ls: /proc/last_kmsg: No such file or directory

When I hooked it up to USB, it was showing in adb as "offline".

My u-boot is a custom one from this thread.
[Nook Color Android Development] donkey72:
I can confirm that updating the u-boot will fix choppy video playback. I had the same issue on "The Future of Reading" (1.1) u-boot and the beta 2, I would have choppy video and slowed performance after playing a video. Then I flashed this :
[Nook Color Android Development] henel321:
And while I was writing if there was a solution using ADB HTC4AN published just that AND a complimentary zip..... ;) Thanks!
[Nook Color Android Development] Techienana:
Checking to see which method I used to flash this to SD card. I've flashed so many roms with so many different methods now it's hard to remember at my age...

Yes, using Racks' size agnostic SD card.
[Nook Color Android Development] mr_fosi:
Oy vey.

Just a 2 sec look at the forum index and you'd find this.
[Nook Color Android Development] lschroeder:
@mr_fosi By the way I used [ROM][CM7] Size-agnostic SD Card image and CM7 installer for SD Cards. with updater to install update-cm-7.1.0-RC0-encore-2.6.32-signed.zip and plan to use it again to install beta2 version. This is the one that you linked to. For some reason it would not work for beta 2 but used twice in the past for previous 2.6.32 ROMs. Anybody have any suggestions since my plan did not work?

@Techienana Did you use Racks' size agnostic SD card for the current Beta2? Did you do the original 2.6.32 and the update-cm-7.1.0-RC0-encore-2.6.32-signed.zip as well using Rack's method?
[Nook Color Android Development] chisleu:
So the multi-boot is what is causing those video problems? hrms.

I am using the 1.1 u-boot.bin. Anyone know what the changes are in the 1.2 (other than the startup text)?
[Nook Color Android Development] :
Running beta 2. Wiped it all, updated to 1.2 bootloader:

Youtube app now flawless

Moboplayer perfect (same as CM7 nightlies w/OC)

Overall feel, snappy (@ 925 MHz)

All apps work so far

Wifi connects/reacts/seems faster

Boot up time at least 3 times as quick (could be the wipe of everything :P)

Will report more as the day goes on. I have most of my projects done for school, so should be able to play with this more :D

EDIT: OMG just saw the screen off animation. EPIC!
[Nook Color Android Development] Divine_Madcat:
So, what is it about the new uBoot that is doing this? I didn't think that little thing would have such a big effect...
[Nook Color Android Development] :
I'm curious as well. Didn't know anything on that partition and that image could actually affect the user experience.
[Nook Color Android Development] Techienana:
Yes, I installed the original and then just updated it per Racks' instructions. Runs very well.
[Nook Color Android Development] syraz:
I do say this beta2 is pretty slick
[Nook Color Android Development] mr_fosi:
Worth coming off an OCed, working stable nightly for?
[Nook Color Android Development] :
I did, and I don't regret it. Pretty smooth. I'll do some more testing to see how well it emulates OC-like qualities :)
[Nook Color Android Development] mr_fosi:
The "turn off sleep when charging" thing isn't a PITA?
[Nook Color Android Development] nukeruss:
Issue with coming out of sleep

So this morning I was reading about the uboot issues and dual booting. I figured I would try a youtube video and see what all the hub bub is about. It was a little choppy, no big deal for me. I then went back to the XDA forums, read a post and put my nook aside for a couple of hours. When I woke it back up, It was very sluggish and was acting like it was stuck at 300 Mhz. I gave it about 10 minutes and read a post or two in that time. I then exited dolphin and went into settings. I changed the overclock from 925 Mhz to 800 Mhz, this had no effect. I then changed the governor from ondemand to performance and my Nook came back to life.

Maybe this was caused by my dual boot setup, maybe not.
[Nook Color Android Development] HarleyChick:
Tried this - didn't work for me. Youtube is still choppy and the quality sucks.
[Nook Color Android Development] joenathane:
Well you see the uBoot is kinda like the BIOS in a standard PC it setups the nook hardware and hands it off to the OS, you know things like IRQs and the like*

*Disclaimer: I just made that all up :)
[Nook Color Android Development] chisleu:
+1

The performance at 925 is so very very close to .29 at 1300. I had to turn the 4d drawer transparent background off (back to solid black) on it, which only recently became possible on .29 anyways. The video performance is great. The general performance with on demand is great as well. I can't wait for 1300 + interactive. This is a huge step up! :)

It's temporary. If it bothers you, don't use it yet. It is fine though. It just keeps the screen on when you plug it in. Of course, you don't have to keep it plugged in all the time anymore, since it can deep sleep.

I didn't format anything. I did a backup w/ CWM and installed the u-boot.bin.1.2 and then installed the beta2.32 build, then my keyboard modifications. I have great video / youtube app playback.

One question:

I have screen on/off animations enabled but i'm not getting the gingerbread animations. Should I format? What is the deal?

Off topic, but how do I turn off this "Donate to Me" crap? I didn't mean to turn it on to begin with. (EDIT: Nevermind... I typed "Donate to CM7" in the donation address field)
[Nook Color Android Development] mr_fosi:
I like what you say there. :D

Final dumb Q: if you turn on sleep when charging, what happens when you hit the "off" button?

And regarding your animations: this is gingerbread innit? The kernel and ROM both.
[Nook Color Android Development] bekyndnunwind:
If I'm running CM7 nightly 64 and flash this U-boot update.zip, will I still be able to run nightly 64? Will this new U-boot just automatically let me boot back into N64 afterwards like nothing happened? And will I still have CWM afterwards?

I would like to update my u-boot, confirm everything is working on N64, and then flash the 2.6.32 beta build....

Thanks!
[Nook Color Android Development] chisleu:
Spoke too soon. You can turn off the screen while charging... yeah! :)

EDIT: Misread your post. Wow I'm off today.

I believe you can use the 1.2 with n64, certainly. I did both at the same time.
[Nook Color Android Development] derekr:
I installed the u-boot 1.2 and all is well - EXCEPT that I cannot "Reboot into Recovery" from ROM Manager anymore. If I try, I get the Read Forever then the screen goes black and that's the end of that! I can reboot back into android by holding the power button down for about 15 secs (to turn off) and then down for about 10 secs to turn back on.

Suggestions? I can't reflash the beta because I don't have a bootable CWM sd card with me.
[Nook Color Android Development] Divine_Madcat:
Holding the power and n button still work though. Hold down both with the device off, and hold them for about 4-5 seconds after the "Reading" logo pops up, then let go. You can get recovery that way. :)
[Nook Color Android Development] LarcenQ:
So with all this talk of ICS in the news today, about how it'll be open source, I was shocked there wasn't more talk of it here on the forums.

http://developer.android.com/sdk/android-3.1-highlights.html

OR! Maybe it is/has been and I didn't see it. >.>
[Nook Color Android Development] MedLine:
2.6.32 Beta 2 + uBoot 1.2 = still get kp (or at least kernel oops) and lockup after PPTP VPN using native client

i use VPNC without problem but user legolee needs PPTP/L2TP VPN
[Nook Color Android Development] J-ROCK:
Hows the BT range? And do u have to fix permission then reboot to get it going?