yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] skwalas:
Bzzzt... the new 1.2 uboot is NOT a confirmed requirement for the current batch of nightlies. Its just what I happened to have. I'm not changing uboots just to find out if the same conclusions are reached on 1.1. Its certainly possible, but not proven. I only cared about the kernel confusion.

Nemith is polling about uboot use and has stated they will begin bundling an appropriate uboot with future nightlies soon. I suggest going there or PM'ing nemith for more info.

Edit: the .32 kernel has been merged and will be in the next nightly. That should fix at least one problem.
[Nook Color Android Development] aasoror:
CM7 Version: Nightly 75

- Uboot Version: 1.1

- Linux Kernel Version: 0.29

- OC Kernel: Modified ext4 OC 1300 Kernel

- Boot Successfully? Yes. No LWP though :(.
[Nook Color Android Development] ehcan:
You have more battery left than before you went to bed? :eek: I want it, I want it. :D
[Nook Color Android Development] RussianMenace:
CM7 Version: Nightly 78

- Uboot Version: - 1.2

- Linux Kernel Version: - .29

- OC Kernel: - ext4 OC 042411

- Boot Successfully - yes (wipe system/data/cache/dalvik)
[Nook Color Android Development] gbeardmore:
Well, that's what it read when I first turned it on...
[Nook Color Android Development] ehcan:
Anyone having issue with wifi on the nightlies? I am using dual boot with cm7 on the second set of partitions. I have tried all the nightlies between 74-80 and while they boot and run fine, I can't get the wifi to obtain the ip address from the routers at all. I have tried both protected and unprotected routers.

Edited: I found out what the problem is, I was using a dualboot Ramdisk from 7.0.3. This does not work well with wifi in the 7.1 beta or the latest nightlies.
[Nook Color Android Development] Awats:
I noticed the change log for what should become nightly B81 has a lot of changes but one references BT. Maybe it will fix it!

Question: Is there a place where we can log bugs and issues or are we not expected to do that? How is the development team capturing issues? Maybe there is another group doing that?
[Nook Color Android Development] only one haze:
edit...I moved this to the questions forum.
[Nook Color Android Development] :
Oh geez.....Nightly 81 is going to cause quite the stir on here.

http://cm-nightlies.appspot.com/?device=encore

New drivers for everything, new base...yikes.
[Nook Color Android Development] Awats:
It's all about adventure!

I am looking at the Nook source code (not CM7) and some of my old Linux days are coming back to me. More and more is making sense (relative to my experience with Android which is about 3 months ...!)

This a fun! I wish I could push the Thanks button several times for many of the people here.
[Nook Color Android Development] stolenmoment:
I've been doing Unix/FreeBSD/Linux stuff since the 1970s, and Android is an interesting blend of old and new. The hardest thing for me was the terminology shifts; I flashed ROMs when it was write-once and programmed bootloaders with wirecutters.

Hey, you kids! Get off my lawn!
[Nook Color Android Development] wpnyc2009:
Feel pretty around here myself

(38 y.o) Kid - "Sorry, Mr. S. Can we have our ball back?"

Mr. S. - "When I was your age, we had respect ....."

TRS80 anyone?

Cheers m8s! Great weekend to all.
[Nook Color Android Development] Awats:
lol!

Hey, at least we aren't loading the boot-strap via the front panel switches to get the tape loaded to mount the 1MB hard disk. :D

But I regress...
[Nook Color Android Development] boxcar8028:
Can anyone answer this noobe question? With this most anticipated n81 with the new kernel .32 and u-boot merged build coming out anytime now. Do people with stock cm7 builds with no OC kernel and is still running u-boot 1.1 can just flash n81 or do we need to flash new u-boot 1.2 before flashing n81? And I guess, there's no need anymore to flash Kernel .32

I'm currently on: stock cm7 n75 emmc, no oc kernel, u-boot 1.1

There is so much going on right now and with all this fragmentation I just want to get this right. Thanks for the devs hard work, you guys are the best :)
[Nook Color Android Development] gudism:
hi all, having an issue with wifi.

I wish to use CM7 (on phiremod 6.2 previously) due to the better battery performance, but I dont want to get involved with the beta stuff, so, after reading Paul22000's thread http://xdaforums.com/showthread.php?t=1083920 I thought this combination was good for me. (the nightly is 74, prior to the beta)

Pauls instructions.

[start quote]

"And if anyone wants to flash this, the method I used was as follows:

Install ROM Manager from the Market and use it to flash the 3.0.2.8 Recovery

Download to SD card:

Latest CM7 Nightly ROM (Still on .29 Kernel)

Google Apps

Modified Overclock Kernel (The standard 0424 one won't work)

Reboot into recovery

Backup ROM

Wipe data/factory reset

Wipe cache

Flash the above three files (kernel optional)

Reboot

Enjoy" [end quote]

Ok so I flashed following Pauls instructions and I am having wifi issues. Wifi connects, signal excellent, but the wifi symbol in the status bar stays grey.

originally, with the stock browser I could surf the net etc. Couldnt access market as I couldnt setup google account due to not being able to connect. And if I tried to access net via the google search widget, wont connect.

I then tried Ace's recommendations in his signature (ie forgetting AP etc), now I can access net via google widget & stock browser, but still nothing when I try to set up google account to get to market. So partial success. I also thought seeing as it was a new rom I would clear the dalvik too. no difference.

have done a fair bit of searching on this site.......no luck.....there is a ton of threads about wifi solutions, but none I've read will help.

I had a similar issue with phiremod 6.1, though then the wifi symbol would be blue but drop out every so often then need to be manually turned off and on. That fixed when went to 6.2

and have flashed to this nightly for the better battery but this is frustrating....I just want my nook back! :)

Is this a common prob with this nightly?

thoughts would be appreciated

thanks :)
[Nook Color Android Development] paleh0rse:
I've used the 20110503 with any/all recent builds, and I haven't had any issues.
[Nook Color Android Development] gudism:
similar problem here, n74. though i can obtain ip and get connected, can use stock browser and google search widget to access net, but cant access market or set up google account.

I came from phiremod 6.2 to this, but am restoring back until this can be fixed.

i actually posted on the next thread page my problem post 2883.

can you let me knoe if you learn anything?
[Nook Color Android Development] MrPib:
It looks like 81 should drop today (5/21), according to this link:

http://wiki.cyanogenmod.com/index.php?title=Barnes_&_Noble_Nook_Color

Specifically:

Starting May 21, 2011 Cyanogen has started bundling a custom secondary bootloader (also know as u-boot) with CyanogenMod 7.1 itself. This was required due to kernel changes that required a specific uboot version.

Along with the new u-boot there are new splash screens that you will see when you boot your nook.
[Nook Color Android Development] paleh0rse:
I really wish they'd leave the stock 1.2 /boot files alone... just my opinion.
[Nook Color Android Development] RoboRay:
That would be my preference as well, as this will create new steps in the process of returning an NC to stock or switching ROMs.

And I actually like the stock "charge me" screens better.
[Nook Color Android Development] EverythingNook:
well its out now its nightly 82, anyone try it?
[Nook Color Android Development] seth.i.simmons:
Downloading now, ill post up when I'm done.
[Nook Color Android Development] EverythingNook:
thanks, time to charge my nook
[Nook Color Android Development] crandy2:
Well, I have the 1.2 uboot, but not the revised mlo.

I flashed 82 right over 77, wiped cache and dalvick, rebooted and 30 seconds after the "Reading Forever ", it came right up. Let it settle for a couple of minutes, and it is working great. I plan to oc later, if needed.
[Nook Color Android Development] lafester:
Took a few reboots but it is running well now.

Looks promising :)
[Nook Color Android Development] sinanju:
Well, Bluetooth is back with 82... that's good.
[Nook Color Android Development] MadMikeSS:
Tried 80 and had some troubles so reverted back to 77. Flashed 82 and everything is working great.
[Nook Color Android Development] sinanju:
Hm... Sadly, audio skipping during MP3 playback still seems to be a problem in #82... pretty frequent, too. Unfortunately, the machine with my dev environment is not in my possession at the moment, so I can't watch the logs in realtime...
[Nook Color Android Development] bekyndnunwind:
Sooooo...is Dalingrin on vacation?????
[Nook Color Android Development] Awats:
I just loaded B82 and yeah, BT is back. And you can turn it on without turning off Wifi and rebooting! The range is still about as much as before (a couple of feet max).

So far so good!

Now to see if they OC 2.6.32 0513 kernel will work!
[Nook Color Android Development] paleh0rse:
Has anyone had any luck with HBO GO in the beta3.1 or n82 builds? (Using the appropriately modded framework.jar, of course)
[Nook Color Android Development] jzibit17:
are you guys running the. 32 OC kernel on the n82?
[Nook Color Android Development] bdcrim:
Working for me, only 10 minutes in however.
[Nook Color Android Development] tech_head:
Old Timers

That would be TRaSh80 and Hammurabi.

Also Timex/Sinclair with ram hanging off the back.

Booting from cassette, writing basic and and Fortran on cards......

The good old days.
[Nook Color Android Development] MadMikeSS:
I've only noticed one odd thing happening since I flashed 82, if I hit the power button to put it in standby, then plug it in to the charger which usually always turns the display back on, I get a blank display. It's coming on, but the display is showing nothing. I have to hit the power button again to put it in standby and then hit the N button to get the display back on normal again.
[Nook Color Android Development] Nburnes:
That comes with the .32 kernel. It is set to stay awake while connected to USB, else SOD would occur.
[Nook Color Android Development] lafester:
n82 + oc is very fast :)

I had a few lock ups so I just wiped everything and started over. so far so good.

once this gets completely stable we will be at a whole new level.

Thanks cm7 team!!
[Nook Color Android Development] Awats:
I am getting a Wifi error message when I try to enable Wifi. The language also came up in Viking or something and had to change it to Late Western Frisian.

B82 + 0513OC + V1.2.1 image.

I will keep playing.

B83 just showed up.
[Nook Color Android Development] boxcar8028:
Just flash n83 and all is running well. Wow, this new build is very smooth. The only odd thing I've found so far is in the status bar. Parts of the bar is transparent with videos, you can see this with youTube, on the web and in the app. It's also this with other video players. All of the functions are working, all of the buttons are working fine, you can hide and unhide just fine. It's just weird looking. Anyone else?

Thanks for all the hard work the devs had put into this. Its most appreciated. :D
[Nook Color Android Development] aasoror:
CM7 Version: Nightly 83

- Uboot Version: 1.1

- Linux Kernel Version: 0.32

- OC Kernel: 0.32 0513OC 1200

- Boot Successfully? Yes.
[Nook Color Android Development] Awats:
B83 with the 0513OC is running fine. Wifi is working again. I am not sure what happened.

BT turns on without disabling Wifi first so that looks like a permanent fix.

Battery level seems to be fine. I let it drop until it shut off and I'm now charging.

One thing I've noticed before in earlier builds back as far as B74, I use Night Mode via Rendering to switch the screen to red for astronomy use. It switches everything to red except the bottom status bar. But when you switch it back to None (normal mode) the screen switches to normal but the status bar goes red! Minor but it happens.

Now to see if the BT range is any better. I was getting a couple of feet before on 74.

**********************************************************

Now to try loading it over B74 where all of my apps and data are!

Edit: Worked! Although I did the build first and then the OC rather than at one time. I am still a bit shy about that after having some issues which could have been all me.
[Nook Color Android Development] aasoror:
IMHO using their own (secondary) bootloader is just brilliant, making the installation more autonomous, and less dependent on whatever your current setup is, is way to go especially with lots of novice users here (just check the many issues couple of pages ago because the bootloader requirement for the nightlies > 75)
[Nook Color Android Development] miniaturepeddler:
CM7 Version: Nightly 83

- Uboot Version: unknown

- Linux Kernel Version: 0.32

- OC Kernel: 0.32 0513OC 1200

- Boot Successfully? Yes.

Wifi: constantly is failing and rebooting, meaning that consistent network access is impossible. Time to head back to Nightly 80
[Nook Color Android Development] Awats:
Wifi is stable on mine and we seem to be running the same exact thing. I wonder what is going on. :confused:

I am not sure about the uBoot though.
[Nook Color Android Development] 12paq:
I am finding nightly 83 stock OCed to 925 is much smoother then 83 with OC beta kernel 5/13 set to 1200max. Both were tested with govener set to Ondemand.

I will probably stay with the stock kernel for a while, its so fast and smooth, at least until a can ascertain the differences with new features, if any. I am wondering if I run the OC Beta kernel 5/13, am I wiping out new improvements built into the stock nightly?

Either way fun stuff, and this new nightly with the new Kernel rocks. Big thanks to the dev team.
[Nook Color Android Development] paleh0rse:
I thought that the 1.2 uboot was supposed to finally be included in n82 and thereafter...? How come some of you are claiming/using 1.1 with n83? Did they decide to leave /boot alone?

Confused...
[Nook Color Android Development] aasoror:
They used a secondary bootloader, so now the installation is bootloader neutral.
[Nook Color Android Development] lyam23:
Flashed. So far it seems not much different than the beta 3.1 Still getting system freezes.

The permissions granularity tool is neat.
[Nook Color Android Development] nemith:
Say what?

I am one of "them" and I don't even know what you are talking about
[Nook Color Android Development] nemith:
Still waiting to be merged. Patience.
[Nook Color Android Development] camalus:
Anyone having issues on newest nightly with Netflix plashing at double speed? I'm sure I've missed something stupid.... but I cat get it to work for the life of me.
[Nook Color Android Development] angomy:
CM7 Version: Nightly 83

- Uboot Version: 1.2 (verygreen 1.2.1 SD image version)

- Linux Kernel Version: 0.32

- OC Kernel: No, running @ 925Mhz with nightly 83 kernel

- Boot Successfully? Yes.

I've had no wifi issues with nightly 83 with or without the OC 5/13/2011 kernel. I did have issues with .32 beta1 and earlier nightlies, so changed my router to be WPA/WPA2 PSK TKIP (not TKIP/AES) and that seemed to clear it (had changed sleep policy but it didn't affect the issue either way). Sleep policy currently set to when screen is off. Haven't had any drops since updating.

Re: Netflix hyperspeed issues - Getting weird fast forward-moving moments and all voices are chipmunked, but it's an improvement from the complete system slowdown (and ~5 fps stuttering performance of all flash-based video) I was having before. Now it's only Netflix that is having weird issues so I'm wondering if the modded (no device check) app I'm using is causing the problem.
[Nook Color Android Development] camalus:
I did the old school build.prop edit and installed the official Netflix app, same superspeed issue.
[Nook Color Android Development] lyam23:
what model and man. did you use? Try vision and HTC.
[Nook Color Android Development] camalus:
Changing it to vision fixed it. Cheers. Had it set to Nexus S.

Works great now.
[Nook Color Android Development] paleh0rse:
Aha! I thought that might be the case. Keep up the great work, and thank you!
[Nook Color Android Development] paleh0rse:
Make sure you're using the HTC Vision mod to build.prop, not Samsung.
[Nook Color Android Development] only one haze:
ok, I just went to N78 last night. I have uboot1.2 and I am using the 4/24 OC.29 kernel. Can I just flash N83 over top? It includes the needed base .32 kernel correct? Then I could flash the OC .32 kernel if I wanted? And would I need to reinstall gapps?
[Nook Color Android Development] xxiworld:
Ah, so the new uboot is coming in a future nightly and is not in 82or 83? Is the new uboot expected to fix the battery level bug or is the cause of this still unknown? THANK YOU for all your work!
[Nook Color Android Development] fattire:
Indeed. The two "bootloaders" are mlo and u-boot.bin --- it goes something like this....

When recovery is chosen to boot, uRecRam is totally different-- it contains, say, clockwork mod. Also u-boot can send instructions to recovery to do stuff, like automatically flash something.

I made that quick so I'm sure stuff isn't exactly right, but maybe it will help. I'll update it as soon as someone points out what I screwed up.
[Nook Color Android Development] aasoror:
Thats the good thing, no one needs to worry about the current boatloader on his/her nook, just flash the ROM regardless and it will work.
[Nook Color Android Development] Awats:
Yes, this change has been very pleasant!
[Nook Color Android Development] hirano:
Dude, what are you saying? That guy nemith is a CM developer and he does not confirm this "uboot merging" at all. Where did you get that from?
[Nook Color Android Development] bekyndnunwind:
Tried N83 and my wifi was turning on and off every minute or so... Anyone else?

Edit: happened with and without 0513 OC...saved the log and will post when I'm back to a PC

Back on beta3.1 w/ OC and all is good.
[Nook Color Android Development] aasoror:
What are you saying I am saying ? :)

I said nothing about uboot merging.

I am speaking about a "secondary" bootloader negating the 1.2 uboot prerequisite that "apparently" existed for nightlies past 75.
[Nook Color Android Development] jtbnet:
THANX for putting this together and presenting it to folks... sometimes we think Everyone understands what we do, and we 'cheap out' on explanations and thus folks Don't get the opportunity to learn... This was Very clear and Informative for folks... I think your time and effort was Well Spent...
[Nook Color Android Development] paleh0rse:
Actually, I believe Nemith confirmed that the inclusion (ie "merge" ) of the custom 1.2 uboot was delayed. IOW, n82 and n83 don't have it. Just as with every previous build, they utilize whatever /boot files you had on your device beforehand...
[Nook Color Android Development] shadowreader:
broken location in google maps with latest nightly build

I just upgraded to the current nightly CM7 build with uboot 1.2 and the dalingrin 5/13 OC kernel. things seem to be working great and it feels very quick. However, the wifi based location function in google maps is broken now. not sure if it is the kernel or the rom. anyone else? Thanks.
[Nook Color Android Development] fattire:
This is right. The check-in is right here and will be accepted whenever kmobs gets back from whatever he's doing.

If you want to see/try the new u-boot now (with nifty new graphics from drakkar), you can always just grab the binary and install it yourself.

Also, a clarification on my little flowchart-- verygreen points out that when u-boot checks "/rom/bcb" for whether to load recovery or not, it may be technically incorrect to refer to the 2nd partition as "/rom". It's called that in the partition list at nookdevs, which is why I called it that, but it's never mounted as "rom" or anything in cm7. So really just think of it as the 2nd partition. Call it "/rom" or call it "/bob"... it's the 2nd partition.

Edit: I just updated the image. Also fixed another thing-- "yes" and "no" switched on the plugged-in check. Anyway. No one probably cares but wanted to get it right anyway.
[Nook Color Android Development] shadowreader:
Nevermind. I reinstalled the google apps package and all is good again.
[Nook Color Android Development] Awats:
I do. It adds a lot of clarity for those what want to understand even the basic stuff. Thanks to you!
[Nook Color Android Development] only one haze:
Went ahead and flashed N83 over N78 (after doing a backup) and everything went well. Booted up just fine, maybe slower than normal, but booted none the less. Checked it out for a few minutes and then flashed the OC kernel. Runs great so far.
[Nook Color Android Development] aasoror:
Now I am messed up, if no secondary uboot was used (despite whats mentioned on the wiki), why is n83 working fine on my nook with 1.1 uboot yet n76 and later never did (while worked fine for those with 1.2 uboot) ?!
[Nook Color Android Development] eespiritu:
One word: AMEN.
[Nook Color Android Development] boxcar8028:
n83 been getting lots of SOD

flashing back to 78
[Nook Color Android Development] 911jason:
Exact same issue here. Scouring the forums looking for solution... unless, of course, some kind soul here would like to enlighten me.
[Nook Color Android Development] Nburnes:
I don't have that problem at all :(
[Nook Color Android Development] TJNooker:
Similar behavior has occurred on past nightlies. Here are two things you can try:

1. Turn off WIFI on your Nook and reboot. After your Nook has rebooted, turn it back on.

2. If #1 didn't work, go into WIFI management & settings and look for "remembered" networks. Long press each remembered network and choose "forget network." Once you've done that for every remembered network, repeat #1. Then go back into your WIFI settings and try to connect to your preferred network. You will have to re-enter whatever network information was "forgotten."
[Nook Color Android Development] fattire:
A shorter way to do #2 is:

adb shell rm /data/misc/wifi/wpa_supplicant.conf

(and reboot)
[Nook Color Android Development] 911jason:
Thanks guys, trying those steps now. =)
[Nook Color Android Development] 911jason:
Neither worked. Wifi connects successfully to my network and I'm able to begin pulling data from the internet, but the connection drops within a minute or two and then immediately reconnects itself. Repeat, ad infinitum.
[Nook Color Android Development] Ophbalance:
Did you install an overclock kernel over the 7x nightlies? It appears that the kernel included with them did not work. However, installing the 5/13 overclock .32 kernel would allow them to boot up. It never had anything to do with u-boot. In fact, the only thing I've seen about replacing u-boot is to help with glitching (video) and not actual system bootup.
[Nook Color Android Development] Canadoc:
Also getting lots of sod on 83 stock kernel came from manual nooterso I think I am on uboot 1.2
[Nook Color Android Development] aasoror:
Yup, but that never worked past n75.
[Nook Color Android Development] Ophbalance:
You tried the .32 kernel source? Because that was required for some of the nightlies in the 7x range, and is now required for all those going forwards it looks like.
[Nook Color Android Development] lanzagas:
No WIFI issues on n83 running from SD using verygreen 1.2.1 concoction.

The only issue so far netflix chipmuncks with version that doesn't check device.
[Nook Color Android Development] Narfx:
Running 82 with stock .32 kernel (no OC). No problems so far.
[Nook Color Android Development] bekyndnunwind:
Still havnt been able to fix this yet either. :-(
[Nook Color Android Development] danvee:
Same here with all nightlies using .32 kernel-whether O/C or not. Tried all other posted netflix fixes as well.

No joy...but still hacking away at it.

Otherwise, everything else runs very well.:)
[Nook Color Android Development] newellj79:
Use the Netflix app from the market. Change manufacturer to HTC and device to Vision in the build.prop. Works flawlessly in all cm7 builds.