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

Root CM7 Nightlies

So I've been having strange sound problems. Apps that normally give a vibrate notification give flat out zero notification if I put the phone's volume on vibrate. I've also have media volume problems, namely the volume is always incredibly low no matter the setting. I have had this problem with multiple kernels and multiple OS builds. Anyone else having problems? My worst offenders seem to be Handcent, the phone and YouTube.
 
Penguissimo said:
Re: #1, how many apps do you have installed to the SD card? If it's more than a handful, do you notice any difference in speed if you move them back to phone storage? I've found that SD card mounting is significantly faster if there are no apps installed to it.
Click to expand...

200+, and I have them all moved to phone storage just because it is faster as you say. The time taken for checking the SD Card is a CM issue that started somewhere around Build 22 or so I think. Before that it didn't take any longer than usual.
 
blkbeltkid17 said:
yes you need the new recovery to flash this build and all the mods have to be redone for this recovery as well
Click to expand...

looks like i am doing a nandroid and flashing this new recovery. It is the weekend, hence my flashing adventures shall begin.

edit: was selecting the menu options through rom manager as i typed, finished typing looked at my phone and said error while dumping boot image and took me back into recovery, wierd but i think i will be manually wiping and clearing cache and flashing now.
 
New Recovery works fine for me. Flashed it then flashed the newest build. Made a backup with no problems. However, when I went to install the .37 kernel, it wouldn't let me get past the splash screen. I let it sit there for about 15 minutes then did a battery pull. Also restored my backup with no problems.
 
Be careful with the new CWM. I've heard it doesn't play nice with any sense ROMs. If all you plan on flashing is AOSP then you should be fine.
 
Pfilly said:
What do you mean? Wouldn't you wipe before installing a different ROM anyways?
Click to expand...

Yes, you would, but from what I've heard, only AOSP ROMs are using the updated scripts necessary to work with CWM 3. I could be wrong, but until all devs start using the updated scripts for their zips I'm not updating to the new CWM.
 
I've been running CM6 on my rooted Incredible, tried CM7 nightly builds 31 and up, but each time the 'android.phone' process keeps force closing continuously. I wiped and installed gapps when installing the nightly builds through ROM Manager. Does anyone know why this might be happening?
 
levitrain said:
I've been running CM6 on my rooted Incredible, tried CM7 nightly builds 31 and up, but each time the 'android.phone' process keeps force closing continuously. I wiped and installed gapps when installing the nightly builds through ROM Manager. Does anyone know why this might be happening?
Click to expand...

Not sure, but I'd suggest not using ROM Manager. There's less room for error when you flash and wipe in recovery manually
 
WormDoes said:
Yes, you would, but from what I've heard, only AOSP ROMs are using the updated scripts necessary to work with CWM 3. I could be wrong, but until all devs start using the updated scripts for their zips I'm not updating to the new CWM.
Click to expand...

Sorry, was getting "CWM" mixed up with "CM."
 
Kennyc11 said:
New Recovery works fine for me. Flashed it then flashed the newest build. Made a backup with no problems. However, when I went to install the .37 kernel, it wouldn't let me get past the splash screen. I let it sit there for about 15 minutes then did a battery pull. Also restored my backup with no problems.
Click to expand...
Me too!! Whew.. no one else on XDA reported this problem. I flashed a different .37 kernel and it worked. Then flashed the new .37 and same thing, white screen. So now I'm on an older slahyer kernel but at least it boots.
 
Just flashed 35. First impressions...

The good:

My sd card checked out very quickly and mounted fast.

Operation is very smooth as with the previous build.

LauncherPro does not forceclose anymore after boot-up.


Not so good:

Gmail does not sync at all. For me, this began with #33 (and that was with a total wipe).

Very long delay waking my phone. It takes longer than 10 seconds for my screen to light up once I press the power key most of the time. Occasionally, it will wake up instantly, but this is unpredictable.

Perhaps the SLOWEST of all the CM builds. I have yet to get a benchmark higher than 1250 in Quadrant, which places me 3rd on the list at best. Don't know if it's the new kernel or what. In real life use, it seems to perform well, as I stated, it is very smooth, just not very fast.

EDIT:

The latest is that my screen won't wake up at all now without rebooting. This is not acceptable to me and I'm flashing back to #30. I'd rather have my sd card take forever to mount than to have a screen that won't wake up...

I would suggest skipping this build altogether. Not good.
 
Thanks for the review, I think I will skip 35. AFA gmail not syncing in 33, I'm running it now and am not having that problem. I did have to go into accounts/sync and when I clicked on google I noticed everything was checked except email. Once I checked that I have had no problems since
 
I'm running 35 on an AMOLED Incredible with no issues. They just added a new kernel into last nights build 2.6.37. Your sd card issues could be hardware related and not so much because of the ROM. My gmail hasn't had any issues. Each phones reacts differently. If you want a good idea of how the builds are head over to XDA and check out the nightly build threads.
 
WormDoes said:
I did have to go into accounts/sync and when I clicked on google I noticed everything was checked except email. Once I checked that I have had no problems since
Click to expand...

Yeah, that's the first thing I did, but it didn't help.

Oh... maybe I did that with 33 and not 35... but the screen issues alone were enough to repel me from this build.
 
masully1984 said:
I'm running 35 on an AMOLED Incredible with no issues. They just added a new kernel into last nights build 2.6.37. Your sd card issues could be hardware related and not so much because of the ROM. My gmail hasn't had any issues. Each phones reacts differently. If you want a good idea of how the builds are head over to XDA and check out the nightly build threads.
Click to expand...

Mine is SLCD, and that might be part of the issue. Those of us with SLCD had to have a new recovery image as part of our Clockwork Mod Recovery console.

35 actually cleared up my sd card issues, which was one thing I liked. The slow prep didn't start happening until somewhere around build 22 or so.
 
humm i just got home from a weakend out boys and 35 is looking promasing and one less step for me flashing the kernel HAHA WOOT DLing now
 
blkbeltkid17 said:
humm i just got home from a weakend out boys and 35 is looking promasing and one less step for me flashing the kernel HAHA WOOT DLing now
Click to expand...

Maybe you'll have better luck with it.

Wednesday will be my last flashing for a while as I'll be in Costa Rica for a week after that... :cool:

I'll keep my fingers crossed for RC1 by Wednesday. :rolleyes:
 
You must log in or register to reply here.
Back
Top Bottom