• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Prepare for the storm: CM7 RC2 now up for selected devices

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Samsung have never released the source code for their drivers. Those are proprietary and not subject to open source agreement. All the work on CM is happening on i9000. They had their source since last year. Still the work is slow since Samsung driver codes are not available and probably never will be. Samsung proprietary drivers are why there is still no true 100% working AOSP rom for any galaxy s.

Sanding released their source code for the epic. Just gota see if devs can make anything useful out of it.
 
Well I loaded it up and it's nice, the problem is that a number of the apps that I use on a regular basis (RSS Demon, YouTube, and a few others) keep force closing. If an OS can't run the apps that I want then it won't work for me. Looks like I'll be going back to my backed up ROM and waiting for a more stable build to be released.
 
Well I loaded it up and it's nice, the problem is that a number of the apps that I use on a regular basis keep force closing.
Are you sure you followed the instructions and cleared everything? There are several caches that you have to clear. If you dont, you might get what you're getting.

I've had very few issues on my Incredible. It works very very well.
 
Last edited:
Are you sure you followed the instructions and cleared everything? There are several caches that you have to clear. If you dont, you might get what you're getting.

I've had very few issues on my Incredible. It works very very well.

Yep, I actually performed the wipes that were stated needed to be done twice.
 
Well I loaded it up and it's nice, the problem is that a number of the apps that I use on a regular basis (RSS Demon, YouTube, and a few others) keep force closing. If an OS can't run the apps that I want then it won't work for me. Looks like I'll be going back to my backed up ROM and waiting for a more stable build to be released.

This may be Gingerbread related rather than CM related. I had similar issues with CM6 with many apps.
 
I put this on my evo last week and battery life dropped from the 6.1.2 with savage kernel 1.3.4.

So.. I found that SavagedZen 0.0.7 was available so I installed the SavagedZen-0.0.7-CFS-HAVS kernel and voila, battery life is back to 6.1.2 levels or perhaps a bit better even. The GPS works now with the EVO as well.
 
Just installed CM7, the nightly build #11. So far so good. Anyone using CM7 as their regular OS on their phone? Just wondering how stable it is. This is my first custom ROM, too.
 
i'm using it daily on my nexus, still on nightly 7. with the dewonkificator app running, everything is fine for me.
 
Just installed CM7, the nightly build #11. So far so good. Anyone using CM7 as their regular OS on their phone? Just wondering how stable it is. This is my first custom ROM, too.

Was building my own from source until CM started releasing nightlies. So, been using since about early January on a G2 (on CM7 nightly 12 right now). It's super stable. GPS works, no force closes, etc. etc.
 
I'm still running the RC1 build on an Incredible and it's by far the best rom I've used on the Incredible. Battery life (1500mah) is now comparable to, if not better than my DroidX. I don't know how they pulled that off.

Other than email issues that are probably unrelated to the rom or gingerbread, it works perfectly with the same or less FC's (maybe 1 every 2-3 days).
 
This may be a noob question but how often do you guys update the nightlies?

I skipped the RC1 and went to nightly #11. I see nightly #12 is out but my phone is working fine (as far as I can tell with less than a day of testing). The only weird thing I'm seeing right now is the "Battery Use" view. Doesn't seem to be updated and "resetting" after I charge the phone so that I can see how long my phone lasted since being plugged in last.
 
i usually update every few days when i have an hour free...in case something gets messed up i can revert to a backup right away. but upgrading nightlies is painless, just flash right over your current one.
 
This may be a noob question but how often do you guys update the nightlies?

I skipped the RC1 and went to nightly #11. I see nightly #12 is out but my phone is working fine (as far as I can tell with less than a day of testing). The only weird thing I'm seeing right now is the "Battery Use" view. Doesn't seem to be updated and "resetting" after I charge the phone so that I can see how long my phone lasted since being plugged in last.

Download from teamdouche website, place on root of SD, boot into recovery, wipe cache/dalvik, flash .zip. That's it really. No need for a full wipe.
 
Download from teamdouche website, place on root of SD, boot into recovery, wipe cache/dalvik, flash .zip. That's it really. No need for a full wipe.

Thanks, I didn't realize it was that easy. I"m still on #11 as I don't see much change in #12 (plus some people on XDA have complained about lag).

So far so good, though. I get a few forcecloses here and there but nothing that makes it unbearable.
 
Thanks, I didn't realize it was that easy. I"m still on #11 as I don't see much change in #12 (plus some people on XDA have complained about lag).

So far so good, though. I get a few forcecloses here and there but nothing that makes it unbearable.

No problem. 🙂

Fix permissions from recovery, and the forcecloses should go away for good.

FYI, running 12 myself...no lag. But I flash the nightlies as they release. Want to at least try to help TD catch bugs.
 
This may be a noob question but how often do you guys update the nightlies?

I skipped the RC1 and went to nightly #11. I see nightly #12 is out but my phone is working fine (as far as I can tell with less than a day of testing). The only weird thing I'm seeing right now is the "Battery Use" view. Doesn't seem to be updated and "resetting" after I charge the phone so that I can see how long my phone lasted since being plugged in last.

The RC1 version only launched for some their handsets. Some, like the Droid, are still on nightlies. They build numbers changed because of a change to the build bots they're using.
 
I put this on my evo last week and battery life dropped from the 6.1.2 with savage kernel 1.3.4.

So.. I found that SavagedZen 0.0.7 was available so I installed the SavagedZen-0.0.7-CFS-HAVS kernel and voila, battery life is back to 6.1.2 levels or perhaps a bit better even. The GPS works now with the EVO as well.

Does 4g work on the EVO?
 
Would love to see this for the Nook. I'm a little overwhelmed with all the new info and am terrified of destroying it. Looking for totally noob proof instructions on doing this... I bought one yesterday and have it rooted.
 
Would love to see this for the Nook. I'm a little overwhelmed with all the new info and am terrified of destroying it. Looking for totally noob proof instructions on doing this... I bought one yesterday and have it rooted.

From everything that I've been reading it looks like it's just about impossible to brick the nook color. Plus you can just get an extended warranty from squaretrade and if you somehow manage to brick it just go throw it off the top of a building and then claim your warranty.
 
Back
Top