• 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 see #135 hasn't hit yet. I hoped you'd have compiled it and posted a link for us by now. :D
I'm a programmer and haven't even tried to do it. :D
 
;)

I would have, but I can't find all the libraries required to build. I tried to install them manually outside of a package manager in Ubuntu, but failed and now it won't boot... :D

I haven't gotten around to fixing that yet. Thinking about building a dedicated PC so I don't have to keep swapping drives in my laptop. It's messing up the SATA connector on the laptop. :(
 
jump-1.gif
 
I flashed this late last night and have had fairly light use today. But so far everything seems to be fine with reasonable battery use.
However I don't play games on the NC, which I often saw mentioned as the place where folks saw a slowdown in the previous few versions, so my usage isn't particularly taxing. I read books on it (gasp! :) ) and a bit of internet and email. Nothing that will make a CPU cry out for mercy...
 
Builds #132-134 included Dalingrin's kernel which most people complained made their NC laggy. #136 removed the gpu changes which apparently caused the problem.

I can't say #136 is as fast as builds prior to #132, it may be, but it seems fast enough to me.

Also some said that changing the governor with the laggy builds seemed to improve performance.
 
I'm having problems with #136.

First, right off the bat, my NC was locking on boot. I was using a combination of undervolt/overclock settings that was completely stable in #128, but with #136, as soon as Nook Tweaks would make its changes my Nook would lock up solid. I needed to flash back to a previous version, and default the N.C.T. settings so I could re-reflash #136 and actually get into it.

After I made 136 stable, I decided to leave it set on the default clocks, 1.2GHz/300MHz but no voltage or other clock changes. I've encountered many SODs, to the point where I'm scared to put it away for a few hours because I'm not sure it'll wake when I need it. It reboots quickly, though.

Which leads me to my last point; I am not able to acheive any sort of long term stability if the clocks or voltages have been altered with N.C.T. My device is crashing and rebooting often.

Flashed back again to #128 and all is right with the world.
 
Mine's been stable with #136.

The last time I messed with voltages I had instability results similar to yours tho.

SOD? I've only had that once so far. :D
 
Build #136 has been rock solid stable for me, as well. I haven't seen any of the issues AmazingDave describes, but I haven't messed with any of the voltages. I'm running the InteractiveX governor with 600 min and 1350 max speeds.
 
mhotovec said:
600 min, 1350 max? You speed freak. :)
Click to expand...

LMAO! :D

I did have my min set at 275 but, after reading some threads at XDA, others were saying 600 min was better to address some issues I was having at the time (I just wish I could remember which thread and which problems, but I can't since I'm not having them anymore!).
 
I believe the 600 min was to fix the lag caused by the first build to incorporate Dalingrin's kernel. Another fix was to change the governor from InteractiveX to another setting (which escapes me).

Seems to be a lot of memory problems here. :D
 
Happily running on eMMC (which is a SanDisk :) ) since day one. B)

I see 138 has posted, Think I'll give it a shot while my battery is still 100% this morning.
 
I'm going to update my wife's NC with #138 as soon as I finish charging it up. Went to turn it on tonight and found it completely dead! I've told her before, "when you're done with it, plug it in, then tap the shut-off shortcut". Either she doesn't get the order right or just can't remember at all. Can't wait to see what she says when she gets home tonight.
 
I'm having the same trouble with 138. I ended up trying 131 as well and had the same result so I'm going to study the change log and try to track down the issue.

128 performs flawlessly with my undervolt/overclock settings.
 
136 kept freezing on me when flashed over a previous nightly (on a card), but 139 seems to be doing OK at the moment after a fresh install. I did start getting freezing problems after trying to replace my LauncherPro icons with Simple Text Icons ones, but going back to default icons seems to have fixed it. I'm wondering how many of the problems I've had previously were due to Launcher Pro or Simple Text Icons, since that always seems to be the point where I start having trouble. :confused:
 
You must log in or register to reply here.
Back
Top Bottom