yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] helloelan:
So has the "beta" build of CM been effectively merged with the nightlies? Because I've been using this "beta" build of CM for as long as it has been available, and I'd like to upgrade to the latest nightlies as some of the changes are exciting. I realize I'll still need to install the .32 OC kernel.
[Nook Color Android Development] hockeyfamily737:
U-boot is not part of a rom. U-boot is a pre-rom program which determines where to look for a rom and which kernel to load, and therefore cannot be included in a build of a rom. Upgrading it is as simple as flashing the zip from recovery.
[Nook Color Android Development] :
Well it's not 7.1, so no, they have not.

Also, this.

Not the "DO NOT MERGE" :P
[Nook Color Android Development] Paul22000:
So do you mean that it got merged accidentally? :eek:
[Nook Color Android Development] painter_:
Looking at the commit comments there is a comment
[Nook Color Android Development] Paul22000:
So they decided to merge since it's close to stable?

Who are Erik Hardesty and Brandon Bennett? I'm guessing one is Dalingrin?
[Nook Color Android Development] painter_:
First google search for Erik Hardesty returned this:

Erik Hardesty (dalingrin) is on Twitter. Sign up for Twitter to follow Erik Hardesty (dalingrin) and get their latest updates.

I could not find anything for Brandon Bennett.
[Nook Color Android Development] :
So it's under review. HAS NOT been merged yet.

bennetb01 (Brandon Bennett)
[Nook Color Android Development] helloelan:
So to reiterate, flashing the latest nightly from the current "beta" build would not be a technical regression? Seems like the nightly is much more current than whatever nightly that "beta" was built on.

Basically just wondering if moving to the latest nightly is the "thing to do" at the moment. Cos I wanna do it too.
[Nook Color Android Development] :
Sure, why not. It has more commits on it.
[Nook Color Android Development] helloelan:
Here's my final question for now: When can we expect to see the latest changes (.32 kernel etc) merged into the nightlies? I've just been super confused this past week or so insofar as not even having a clear idea of the roadmap of CyanogenMod-- particularly within the past two nights, as I see code implemented from 7.1 (CM71) but also 7.0.4. being ready to go for some devices. Historically (up until this strange "beta" released for the new .32 kernel) I had assumed the nightly builds were absolute bleeding-edge.

Anyone as confused as me? :confused:
[Nook Color Android Development] :
Only rule of CM: Don't ask for ETAs.

dalingrin, verygreen, and fattire, et al. are busy dudes. It will be done when its done. The reason for the 7.1 vs 7.0.x split is the massive amount of rework that went into 7.1 (new BT driver, display stuff, fuzzy bunny rabbits, etc).

Looks like it will merge soon enough (under review right now).
[Nook Color Android Development] miniaturepeddler:
Interesting, When I simply tried to update from the nightly 75 to the nightly 77, it froze after the 'android_' screen with a simple blinking in the corner. I restored myself to my backup.

Now trying suggestions here, I updated to the 77 nightly and the .32 OC (plus format/clear of the cache) and voila 'It boots' now to my system and I have access to the 1.2 OC via settings.

I do wonder what is wrong with the base kernel that a simple update from 75 to 77 causes the crash.

But I'm just happy that it works.

Oh, for my netflix I had to switch from the Samsung setup to the HTC setup to get Netflix and tv.com apps workiing again.
[Nook Color Android Development] helloelan:
Oh no, I fully understand and respect that rule (and have called people out for being impatient before), I'm just curious because it seems like they fragmented development a bit which seems wholly counterproductive, just to produce nightlies. I could be handed the "beta" or even a more recently nightly as a Final release/gold and be totally content with that. :D

Also, do you have a link handy to see where this supposed merge in the pipeline is mentioned?
[Nook Color Android Development] bekyndnunwind:
As far as I understand, nightlies are 'bleeding edge', by that I mean they contain the latest changes that the devs have commited. Once B&N dropped the .32 kernel, Dalingrin, Verygreen, Fattire and others began creating a separate beta build (based on the latest CM7 stable I believe) to test with the new .32 kernel.

The .32 kernel changes will be merged into CM7 nightlies as soon as the devs are confident that it will not break anyone's Nook. Right now they are trying to find and fix as many bugs as possible before they release the build to the general masses...

So yes, it appears we are seeing some early commits readying CM7 nightlies for the .32 kernel. They must be getting close!! :D
[Nook Color Android Development] helloelan:
Well-said; cleared up a lot of confusion for me. Thanks!
[Nook Color Android Development] ehcan:
Edited: Sorry I mixed up the kernels
[Nook Color Android Development] skwalas:
So try it and report back

Edit: actually don't bother. That doesn't explain why the nightly by itself didn't flash. So that's a red herring.
[Nook Color Android Development] vtmike:
I tried the latest nightly with the 32 oc kernel and was ablest to flash everything okay. For me, CPU spy indicated my nook not entering sleep mode which is the main purpose of using the kernel. Back to beta 3.1 for me.
[Nook Color Android Development] :
The kernel has nothing to do with it.
[Nook Color Android Development] ddgarcia05:
bluetooth working on the latest nightly for anyone? Mines not.
[Nook Color Android Development] vtmike:
Well what ever the cause is thought it is worth noting that, at least for me, sleep does not work while running the nightlies with the 32 oc kernel.
[Nook Color Android Development] miniaturepeddler:
Really frustrating. With the success of updating to 77 with the 32 OC I felt brave on seeing 78 released and tried flashing it. No go. Boot doesn't even make it to the "android" screen.

So I have returned to 77 with OC.
[Nook Color Android Development] skwalas:
Yeah. I just confirmed N78 reverts back to using (or expecting) the .29 kernel. So I'm now on N78 and 0424 oc once again.

Geez, doesn't the phrase "be consistent" mean anything anymore?
[Nook Color Android Development] Dadeeo:
Why in the heck didn't the dev's take that .32 whatver and call it 7.1 and we would have a lot less confusion, I see that "Sorry, I confused the two kernals" quite a lot lately. There are so many posts about nightlies not working I don't know if I can use them or not, guess I'll stick with 75 until this Charlie Fox is cleared up and everyone is on the same page again. Maybe Ice Cream???
[Nook Color Android Development] TJNooker:
Wait...

I think some of you are still getting the kernels confused. There is a CM7.1 Beta build (Dalingrin's test build) which is based on the 2.6.32 kernel. Then there is Dalingrin's overclock kernel that was designed and optimized for the CM7.1 Beta build, which some call the ".32 OC kernel" for short.

The latter kernel (the OC kernel) has

nothing

to do with sleep. If you somehow manage to make the .32 OC kernel run on a CM7 2.6.29 build (I don't know why you would even want to), you still will not have deep sleep. Only the Beta build has deep sleep. And the Beta build is still...wait for it...in Beta! It has not been merged into the CM7 nightlies as of this post.
[Nook Color Android Development] furius:
I was checking .zip size of last nightly builds...

until 75 was about 88 MB...

76 and 77 was about 95 MB (like the beta1)

78 is 88 MB

this can confirm the theory... ;)
[Nook Color Android Development] jzibit17:
I'm going to wait for another confirm and update to N78 using also the 4/24 ext4 OC kernel fyi still on 69....
[Nook Color Android Development] khaytsus:
Wow. Just.. Wow.

Exactly what theory? The size differences are from Live Wallpaper.
[Nook Color Android Development] chayesfss:
I'm loving cm7 on my nook
[Nook Color Android Development] oldman_58:
It is larger because it has the Live Wallpapers included.
[Nook Color Android Development] oldman_58:
I am not confused at all:

I loaded #76, #77 neither would boot with uboot 1.2

I downgraded to uboot 1.1 neither would boot

I upgraded to uboot 1.2 loaded #77 and loaded the OC Kernel .32 from Dalgrin and it booted just fine, performance was poor but at lease it booted.

I am now using the "Beta" ROM and have excellent performance.

so in a nut shell starting with Nightly #76

you needed the .32 kernel ( I did not try uboot 1.1 with .2 as that will not work) and uboot 1.2.

either both should have been included in the nightlies or a new install document describing the needed components and procedure to upgrade..

Just my 2 cents...

from jkurl

here is uboot 1.2 http://www.megaupload.com/?d=SFX0W4KM flash via CWM

from whatsinaname

This is really odd. I am on uboot 1.2, nightly #77 and Got Dals kernel from

http://coachz.inetpro.org/~dalingrin...ernels/051311/

Since the nightlies are not perfiect, it was fun for a change to figure out what happened.

dalingrin and the other Devs deserve a huge thanks for all the time they have put into making this happen..
[Nook Color Android Development] GabbleRatchet:
Maybe anyone too confused or unwilling to follow the various iterations of cm should stick with the ones that say "stable" next to them. This is not meant as an insult to anyone. Yes, there have been a lot of kernel/version confusion posts lately, but that is going to continue to happen every time we approach a new milestone. The alternative is for our awesome devs to stop sharing their work with us. Frankly, this whole situation has not been that confusing, and if you are upset because a few nightlies were screwed up, then take a step back & wait for others to flash & report in before flashing with wild abandon.
[Nook Color Android Development] boxcar8028:
Coming from cm7 n75 I was able to successfully flash stock cm7 n77 with no OC Kernel .32 and I'm still using u-boot 1.1 all is running fine but one thing. The home screens will not rotate to landscape. All of my home screens are stuck at portrait. The rotation works fine with other apps in dolphin web pages will rotate. video, games will also rotate fine. I check the setting for something new but all seems to be the same as the past nightlies. So is this something new or a bug? I'm not sure if I like it, its kind of like ipad.

Has this happen to anyone else?
[Nook Color Android Development] :
Did you check the settings for your launcher?
[Nook Color Android Development] TJNooker:
What launcher are you using?
[Nook Color Android Development] boxcar8028:
I'm using the stock cm7 ADW launcher. I haven't try other launchers yet to see if this is a launcher thing or not. I don't think its a ADW setting because I reloaded my saved settings. I'll flash n80 or the latest tonight to see if this will clean it up. thxs
[Nook Color Android Development] Awats:
B80 Success with 2.6.32 OC

I was just able to install build 80 on a 2GB SD card by:

1. Using the new V1.2.1 image with Imagemaker from Verygreen (generic-sdcard-v1.2.1.img)

2. Copying the kernel and system folder from the 2.6.32 OC zip file (update-cm7-dalingrin-2.6.32-sdcard-051311). Unzip it, copy uImage to a new file called kernel, copy kernel and the system folder into build 80 zip file.

3. Add in the gapps 0307 zip file (gapps-gb-20110307-signed).

4. Move the SD card to the Nook.

5. Reboot. Wait about 3-4 seconds after LOADING appears and release the buttons. It should explode the build and gapps files.

I rebooted and it came up with the market set up selection but the screen was flickering and next to impossible to selection one of them. I rebooted and it came up solid and selectable. I set up the market and it working fine. I switched to 1200MHz OC and that is fine so far too. Wifi works.

I tried this same process on the 75-78 builds and it wouldn't work. I am not sure why.

I didn't try installing B80 without the OC kernel and system file/folder.

Now I have to decide if I want to try this on my 16GB that is still running build 74 by overlaying the new B80 with the OC stuff copied in rather than erasing and starting from scratch. I did the Verygreen V1.2.1 update but I haven't tried to drop the new B80 with OC onto the card and seeing if it works. That worked on all of the builds up through 74.

Edit:

1. BT will not turn on. Before it would go on, then off. You had to turn off Wifi, reboot, turn on BT and then Wifi. That doesn't work anymore. BT just sits there trying to turn on. BT seems to stop trying after about an hour.

2. If you turn it off, power consumption is dang low but you have to give it about 10 seconds to fire up the Wifi again. Minor.

3, Scrolling appears to be slightly less smooth than it was before the kernel change. Even B74 appears smoother than B80 with both at 1200MHz. Of course it could be totally unrelated to OC. However, it's still smooth and responsive enough. Minor.
[Nook Color Android Development] oldman_58:
BT may require a hard shutdown, Hold the power key for a count of 10 or so the screen will shut off then restart as usual, once back up turn BT on.
[Nook Color Android Development] Awats:
Yeah, I tried that and several combinations of other things (this on, that off, reboot, on, off, off, on, face north, cuss, etc.)

Still nothing. But it otherwise seems to be working nicely!
[Nook Color Android Development] jzibit17:
Im on clockworkmod 3.0.2.8

Installed nightly 80, install gapps 20110307, installed ext4 OC 4/24 kernel, format cache, wipe dalvik cache, hard reboot

THIS DID NOT BOOT!!!

just fyi for you all... i guess you need to use the .32 kernel but for that you need the 1.2 uboot and i didnt want to read into how to install that so i use the same method and loaded 78 successfully.
[Nook Color Android Development] mr_fosi:
Try fixing permissions (in Cyanogenmod Settings) then hard-offing it. Worked for me when I first flashed CM7.
[Nook Color Android Development] Awats:
From my experience and all of the comments, builds from 75 up require the 2.6.32 kernel. I took the file in my post above, and extracted the kernel (uImage) and system folders and dropped them into the build. That gave it the 2.6.32 kernel and it worked.
[Nook Color Android Development] Paul22000:
Can anyone confirm that they have successfully booted into Nightly 75-80 with 1.1 uboot and .29 kernel?
[Nook Color Android Development] EverythingNook:
guessing n80 needs the .32 kernel too ):
[Nook Color Android Development] jzibit17:
actually 75 and 78 boot with ext4 OC 4/24 (.29)kernel. 76,77, and 80 you need .32 kernel. I don't know if they did on purpose but the ones that don't boot with the old kernel (ext4 OC 4/24) are smaller in size something like 88mb compare to 95mb. and yes I know the size difference signify the live wallpaper but maybe they decided to ID them by releasing them that way.
[Nook Color Android Development] Awats:
Ok, I couldn't get them to go but I am not an expert here. I have 80 running on one card and can switch back to 74 when I need BT for now.
[Nook Color Android Development] LBN1:
Almost. I had 1.1 Uboot, on 7.0.3 Stable. Upgraded to 1.2 Uboot, still on 7.0.3 Stable. Tried to flash Nightly 80, did not work. Then flashed Nightly 78, worked. Nightly 78 has the .29 kernel.
[Nook Color Android Development] Awats:
Man, this is going all over the map. Maybe a little note about the kernel requirement would be nice. I know we can't complain but this is becoming more of a guessing game.

Taking bets on B81! Which kernel? ;)
[Nook Color Android Development] residentorca:
This is a quick "thank you" to those beta testers who ventured down the path with the latest nightlies. My NC was stuck on n.75 (with Dal's 4/24 emmc OC kernel) until the early adopters reported n.78 working with this kernel. I'm also confirming that they play well together. Thanks again to the developers as well!
[Nook Color Android Development] ADude:
Yes, we can complain !

It Sucks !!

I'm pretty sure that there is no note, because whoever is doing it does not have a clue that it is having that effect. It is likely some non-Nook change to CM7 that only works with the recent .32 source - by coincidence.

But in general, good work should get praise, and poor work should get complaints - even if no one is getting "paid".

Without that, there would just be endless morons throwing up crap code - cf the movie "Idiocracy".
[Nook Color Android Development] GabbleRatchet:
And if you think you are on the receiving end of poor work, you're a crazy person.
[Nook Color Android Development] MedLine:
dude, i don't know what to say.

i just feel very sad. i know the CM7 devs will read your post, and i know how it's going to make them feel.

it all just makes me very sad.
[Nook Color Android Development] Awats:
I'll bet they don't blink. They know what they are doing. We are just moaning and they have heard it a million times. At least we aren't asking for da.. <poof>
[Nook Color Android Development] residentorca:
Dear Developers:

No one asked us to be beta testers. There have been a few bumps in the road but it has been worth it for me and my little nook. If the CM7 development stopped right now, I couldn't complain considering how much better it performs compared to just a few months ago.

Signed,

One Happy Customer
[Nook Color Android Development] I Am Marino:
I don't know how anyone could openly complain considering how much work the CM team does.
[Nook Color Android Development] Awats:
Look, he's a Senior Member and out ranks me. I tried to stop him but he wouldn't listen. He had like these time-tunnel spiral eyes man!

Ok, let's not over do it here. Neither of us are being as dramatic as people are making out. :)
[Nook Color Android Development] painter_:
All the title "Senior Member" means is that you have over 100 posts. The value of the posts are irrelevant. (Not pointing out anyone, just clarifying)
[Nook Color Android Development] Awats:
Ok.

Let's get back to testing.
[Nook Color Android Development] aasoror:
ok back to topic.

Now with release 80 out, has anyone got a consistent installation on their nook running off internal memory ?

If so, whats the prerequisites ?

- CWM version.

- uloader.

- Kernel.

Thanks,

p.s. we are all here to help each others, this is a community forum, for the complainers, feel free to submit a "refund" request to whoever charged you for these updates :rolleyes:.
[Nook Color Android Development] Awats:
Look back two pages (284). I am running on SD and noting the functionality. Seems to work well with two little issues.
[Nook Color Android Development] EverythingNook:
is anyone else having trouble with netflix on n80?
[Nook Color Android Development] skwalas:
I did the usual tests. 80 by itself, no joy. 80 with .29(ext4) no joy. 80 with .32 nice cuppa snickerdoodle latte. (So I like flavored coffee. Shoot me)

Question tho. How does one determine the native kernel in a nightly without booting it? Can that be looked up? I'd put money down that all the new nightlies are still bundling .29, but some critical hook or referencing is requiring a .32 kernel be present on boot, which would explain the hang ups on the nightly by itself (I.e. not trying to flash an OC with it).

Edit: oh yeah also still on 1.2 uboot. But... I installed uboot only not the MLO stuff. Any chance that might play a rile?
[Nook Color Android Development] EverythingNook:
going back down to n78 because netflix isnt working for me ):
[Nook Color Android Development] gbeardmore:
Yup! I'm on that exact set up.

I read for days trying to figure out what to do. I really only wanted the improved standby battery life by eliminating the speaker buzz. Couldn't really find a definitive answer. So yesterday I took the plunge and went with Nightly 75 and used OC 042411. Still on 1.1 uboot and it came up just fine.

I've been running at 1,300 Ondemand since that with absolutely no issues. Left it on overnight to see how the battery would fare. Went to bed with it at 82%, got up 7 hours later and it showed 83%. Pretty happy with this setup till the next Stable is released.
[Nook Color Android Development] EverythingNook:
wait the .29 kernel!? are you using the ext4 kernel, if so i need it please.
[Nook Color Android Development] aasoror:
Thanks, I saw your post, I meant to ask about an internal memory setup.

Do you need a specific CWM version to flash with 1.2 uboot ?

Thats as far as you will go, I have the same setup, anything higher than 75 was a no go for me.

Here you are.
[Nook Color Android Development] EverythingNook:
im on n80 with the .32 kernel and whenever i open up the netflix app it freezes if tried to uninstall it and reinstall it, anyone else have this problem?
[Nook Color Android Development] gbeardmore:
Yes, from what I've figured out, 75 is where I stop. Oh, this is an Internal install, not from an SD. I'm just really happy to have decent battery performance!

One more thing, I wiped Data, Cache and Dalvik before I flashed anything. FWIW.
[Nook Color Android Development] Paul22000:
Yes! This would be the most helpful thing if we all posted in the same format about whatever version we were able to successfully boot into.

Here's what I'm on:

CM7 Version: Nightly 74

- Uboot Version: 1.1

- Linux Kernel Version: 0.29

- OC Kernel: Modified ext4 OC 1300 Kernel

- Boot Successfully? Yes, seems stable. Been using since Sunday morning.

Now can anyone fill in some of these? (Fill in what you have used in order to successfully boot with -- or I suppose what you used and didn't work would be helpful too.)

CM7 Version: Nightly 75

- Uboot Version:

- Linux Kernel Version:

- OC Kernel:

- Boot Successfully?

CM7 Version: Nightly 78

- Uboot Version:

- Linux Kernel Version:

- OC Kernel:

- Boot Successfully?

CM7 Version: Nightly 80

- Uboot Version:

- Linux Kernel Version:

- OC Kernel:

- Boot Successfully?
[Nook Color Android Development] skwalas:
You're a little obsessive about this but just to oblige:

CM7 Version: Nightly 75, 78

- Uboot Version: 1.2

- Linux Kernel Version: .29

- OC Kernel: 042411(ext4)

- Boot Successfully? Of course

CM7 Version: Nightly 76, 77, 80

- Uboot Version: 1.2

- Linux Kernel Version: .32

- OC Kernel: 051311

- Boot Successfully? ONLY if the .32 is also flashed at same time

Doing some text hunt on the unzipped nightlies, I can confirm ALL nightlies are still bundled with the .29 kernel. Since 76, 77, and 80 hang up when flashed by themselves and when flashed with the OC'ed .29 kernel, but will boot fine with the OC'ed .32 kernel, leads me to believe that something in the boot procedure has been changed to go looking for a .32 kernel but the kernel itself is still .29.
[Nook Color Android Development] Paul22000:
Obsessive? Not really. Just trying to find out what's going on. See the previous dozen pages or so to see just how much confusion there is... ;)

Your post was great though. Anyone can clearly see two things straight away:

A) Everyone wanting to run CM7 absolutely needs to upgrade the uboot (note that this information is listed officially absolutely NOWHERE). Unless someone can post that they are using these nightlies on uboot 1.1 (?) then this is something that should be in the OP.

B) The kernel is still 0.29.

Thanks for the great post. :cool:
[Nook Color Android Development] jzibit17:
A sticky should be made with that info!!!! that way it would keep the confusion to a minimum a plus would be to merge it with this thread

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

This way we know what works with what and what problems/benefits... Now how do we get it sticky?

ps CM7 Version: Nightly 75, 78

- Uboot Version: 1.2

- Linux Kernel Version: .29

- OC Kernel: 042411(ext4)

- Boot Successfully? Of cours

it also boots with Uboot 1.1