• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM7 Nightly builds/custom kernels

I seem to have missed a beat here.
Deep sleep? To me deep sleep sounds good, where of course sleep of death I know to be bad. Colchiro, you said on the 6/30 kernel that you hadn't had a deep sleep in 8 hours, that sounds bad to me, but then you said you weren't sure which kernel you'd put on wife's NC. I'm so confused...
'xplain please. :)

Edit: I installed 7.1RC and the 6/30 kernel, and now I understand about it not going in to deep sleep. The screen dims, but it never actually shuts off. Guess I'll try a different kernel to see if that helps.
 
Deep sleep is determined by installing cpu spy. My screen powered off fine, but my cpu was at 300-600 the whole time, the same thing that it would do with the .29 kernel roms, so no big deal.

I flashed the 0618 kernel on my wife's NC after seeing the max OC was still 925.

You should reflash your rom before flashing a new kernel. :D
 
Just read that unchecking background data under "accounts and sync" might help with deep sleep. Trying it now.


EDIT: didn't help. Still runs about 65% deep sleep when it does sleep and the rest 300 & 600, mostly 300. Also, Market REQUIRES background data to be enabled so turned it back on.
 
I dropped back to nightly 101 which is what I'd been using and had a good backup of. I couldn't find a way to make the screen shut diwn like it should on 7.1. I tried reflashing 7.1rc after wiping both caches and data, but still had the same problem. I made a backup of 7.1rc so I can easily go back to it if I get the urge to mess with it some more.
 
I never wipe data for an update, only cache, dalvik cache and system.

Of course you could wipe both caches at any time. I'm not a fan of reinstall all data, even if it's backed up with TIBU.

It's rare for anyone to format cache with the nightlies and look how often that gets installed. :D
 
The first time I installed it I just flashed over the top of 101 without wiping data, but did wipe cache. I just did the data wipe the second time to see if that would solve the sleep priblem, it didn't.
 
Mine wasn't sleeping again. I blame it on the 0630 kernel. Daringrin did mention that it was an iffy version.
 
This just in....
Dalingrin said:
I will no longer be releasing this kernel separately from CM7. It will be merged into CM7 as the default kernel. I will keep this thread alive for Stock 1.2 users.

By default CM7 will use a 32 bit framebuffer as it always has. If you prefer 16 bit for performance, like what is in this OC kernel, then you will be able to switch it via Nook Color Tweaks.

Once this update is merged it will contain a few other changes. The biggest change other than the kernel is the GPU drivers and libraries. These have been updated to a much newer and supposedly faster release. The wifi driver has also been updated.

In a separate commit I will also be moving us back to lcd density 160. I've stuck with 161 for a long time now due to a bug in the Android Market. Fortunately, the new Market has fixed the issue and we can now move back to a 160. This will allow more apps to better scale to our display.

... also this:

TheAmazingDave said:
Dal, no joke, you're my hero man. Incredible work, simply incredible.

I wish I would have kept with programming. Thank you so much for your hard work and dedication.
:D

No sign of it in the changelog yet tho.
 
Yes, only the camera and phone updates where there before (bottom two lines).

Use Dalingrin's OC kernel, new GPU modules and lib
New kernel, new gpu modules and libs, new wifi module,
includes kernels with both 16 bit and 32 bit framebuffers.
Default to 32 bit framebuffer but can be swapped either manually
or with Nook Color Tweaks.
New GPU drivers have RGBX8888 support
You can bet that will be downloaded a lot. I think I'll give it a day or two to get rated. :D
 
I tried to set up my Linux install to build CM from source. It didn't work out so well, or else I would have compiled this already... :D
 
Yes, only the camera and phone updates where there before (bottom two lines).

You can bet that will be downloaded a lot. I think I'll give it a day or two to get rated. :D

Early reports seem to indicate that you won't be getting this version...(nor will I)
 
I thought Dalingrin was going to remove the gpu kernel changes to see if that helped (but I see nothing "encore" in the changelog for tomorrow).
 
Thought I'd report in about my experience with nightly 132 - it was a bad build for me, too. NC started overheating and freezing up, at the same kernel speed I'd been using for weeks, then it wouldn't recognize my SD card. I tried lowering clock speeds and changing the governor, to no avail. So I restored back to 128, which had been running stellar for me, but was still having all those problems and I figured 132 might have corrupted something.

I was on the verge this morning of wiping everything and starting over clean, but then I figured I'd just try fixing permissions and voila! - everything is back to beautiful speed and snappiness on #128. I won't be trying another build with the built-in kernel until those GPU changes have been confirmed (which they're not for #133 today).

Also, I'm running the new 3.0.26 Market, inverted. You can get it here: Market 3.0.26 optimized - Droid Forum - Verizon Droid & the Motorola Droid Forum

Google+ inverted can be found here: http://www.droidforums.net/forum/team-inversion-conversion/157364-google-inverted.html

Both confirmed working on my Nook Color. A note about the inverted Market, though -- they're still working on getting it to pick up a white text color on some of the screens, so unless you're running a theme that changes the text color to white or something light (light blue in my case), the app names can be challenging to read.
 
Back
Top Bottom