• 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

colchiro said:
A new install/upgrade is going to be laggy for a day or so until your caches are built up again.
Click to expand...
A bit more than lag in my case - it would totally freeze on whatever screen it was on and not respond to any input. I'd eventually have to hold the power button to shut it down.

Your mention of caches does bring to mind a question that's been bothering me - is there any way to clear cache/Dalvik (or indeed do anything in recovery except flash a zip) with an SD card installation (verygreen method)? I tried flashing clockworkmod again, but still the only thing that happens when I go into recovery is that it looks for something to flash and then powers down. If there's some way to make it stay in recovery, I haven't found it.
 
There are cache cleaning apps in Market... clear them, then reboot. :D

If it's laggy, I'd suspect the speed, brand, or reliability of the card.
 
colchiro said:
There are cache cleaning apps in Market... clear them, then reboot. :D

If it's laggy, I'd suspect the speed, brand, or reliability of the card.
Click to expand...
I've used those apps on my DInc...don't they only do application caches? I'd be surprised if they took care of Dalvik.

I see the same symptoms on 2 cards (Sandisk unclassified 2GB, Simpletech Class 6 8GB)...they were fine with older nightlies, then things went weird for a while, now (post-136) they're straightening out except under certain conditions (trying to run Simple Text Icons, occasionally when using the Market with a busy hotspot at the local Starbuck's). Doesn't seem like a card problem to me.
 
An updated kernel is up for the next nightly... :D

CyanogenMod nightlies changelog for Encore

Now this: xda-developers - View Single Post - [DEV] CM7 Developers Thread

I know Dalingrin was working on hardware acceleration... :D

Update:

Dalingrin said:
We are in the middle of merging OMAPZoom framework changes primarily for OMAP4 device support(3D, new DSP, etc) but much of it affects the Nook as well. Media playback should improve somewhat for the Nook. Thus far I have new DSP codecs working but the overlay still needs some work.

The kernel commit that was finally merged is just some kernel clean up to eliminate possible causes of instability and SOD. No new features yet.

My 1st priority is to get the OMAPZoom framework changes merged because it affects multiple devices. After that I will focus back on the kernel hopefully figure out SoD and such.

Longer term, TI has been working on an OMAP3 2.6.35 kernel finally and I would like to look into that for the Nook down the road.
Click to expand...
 
Just finishing my second Nook.

Backed up in recovery.
Flashed rom, installed gApps, fixed permissions.
Changed boot logo to Google Gears, changed font to Caviar Dreams, changed lcd density to 187.... think I'm getting a blister. :D

Haven't had a normal boot yet, since everything I've done takes longer, but seems faster.
 
The boot up speed is impressive. And it does seem like screen changes on #150 are a bit snappier than on #140. (I skipped from #140 to #150).
 
If you don't need USB support I'd stay with 150.

150/160 felt a little faster to me, not bad enough to downgrade tho.
 
Looks like nightly 169 is out with quite a few patches. I installed it this morning. Is there an easy way to revert to an older one just in case I have issues? It seems to have booted rather smoothly. I'm looking to overclock just a little and lower the voltage just a tad to get a great experience with it. Kind of wish it was mine instead of my fiance's.
 
I think it's past tense now - he COULD HAVE made a backup.... :)

GriesMonkey (with a name like that, I picture a 70-something Chevy hot-rod in your driveway :) )
If you like the way your NC is working, but have a hankering to try a new/different one, prior to flashing the new ROM make a backup of your old one (an option in ROM Manager). That way if you don't like the new one, you can just restore your backup and the NC will be back exactly like it was when you created the backup.
It's a nice little safety net when messing around with 'stuff'.
 
I had #150 -> #155 -> #160 -> #165... all without issue. #165 seemed a little slower, but that might have been too early after an install or just my imagination.

Wife used hers with #171 on it last night, just before I went to bed. I suspect it was another hour of Mahjong. :D I'll see if she had any issues in a bit.

#171 had a kernel update, which is just an updated screen driver.

Wife says it worked too well. Usually she has trouble with Mahjong crashing and was up waaaay too late. :D
 
Hey C, has your wife mentioned battery life (or lack of) on #171?
I flashed #171 yesterday (without full wipes) on a fully charged (and plugged in) NC. Left it plugged in for a while after that, but did NOT calibrate the battery (doing that this morning).
The charge light was green when I unplugged it around 4pm yesterday, at 7am this morning it was discharged enough that it would not turn on, and I hadn't used it at all. So from fully charged to 'fully' discharged in 15 hours with no use, on my previous #150 that would have been less than 5%. I checked to make sure that wifi is still set to off when the screen is off - it is.
Figure I'll get it fully charged and recalibrate the battery, then see what happens tonight, but was wondering if she (or anyone) had seen similar battery usage.
 
Nope, I wouldn't have a clue what kind of battery life she gets. I work out of town so I'm only around weekends.

On one occasion I think she turned it off, plugged it in the charger (backwards from what I've told her :D and of course plugging it in starts it up again). The next day, thinking it was off, she unplugged and eventually the battery was depleted.

I plug mine in at night so the battery is charged in case a new build comes out. :D OTOH, she won't charge hers unless it's below 50%. That's why I said it was strange to find her's fully charged.

I updated hers to #172, it was laggy and I rebooted to a black screen so restored my #171 backup. #172 had a kernel fix for usb I believe, which I've never tried so don't need.

Your results sound like issues I had with my DroidX a couple times on our vacation, where I rebooted it before bed and it was dead the next day. I since sbf'd back to Froyo, upgraded to a newer gb build, did an advanced restore in recovery of just data and it's been great since. You might be due for a clean install or upgrade an older backup if you can't resolve this. I rarely do batter calibration on my NC since it's the stock battery. My DX has the extended battery tho so I've done that on occasion.

I've used cpuspy to see if I was getting sleep while it's idle.
 
colchiro said:
I had #150 -> #155 -> #160 -> #165... all without issue. #165 seemed a little slower, but that might have been too early after an install or just my imagination.

Wife used hers with #171 on it last night, just before I went to bed. I suspect it was another hour of Mahjong. :D I'll see if she had any issues in a bit.

#171 had a kernel update, which is just an updated screen driver.

Wife says it worked too well. Usually she has trouble with Mahjong crashing and was up waaaay too late. :D
Click to expand...


Just tried 165 and had a lot of freezing issues. This was after a full wipe. I got freezes while overclocking and at the standard 800MHz. I might try 171 though to see if its any better.


Update: having issues getting email to work on with this nightly. Anyone else having this issue? Gmail works, but the other email app doesnt.
 
My NC is being delivered today so I was curious which nightly would be the one to grab right now. I was told 171 was good, but curious if i should go with that or if one of the newer ones are better?

Thanks!
 
You must log in or register to reply here.
Back
Top Bottom