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

Root CM7 Reboot Under Heavy Stress?

L

LittleRedDot

Android Enthusiast
I went back to Cm7 the other day and about 9 times now it has rebooted whenever I run intensive apps (maps, nav, etc).

Any suggestions?
 
LittlrRedDot said:
I went back to Cm7 the other day and about 9 times now it has rebooted whenever I run intensive apps (maps, nav, etc).

Any suggestions?
Click to expand...

yep had that happen to me. about a year ago. it got so bad that i had to flash to a different rom and i was still getting the reboots. so i unrooted it and the same thing happened. finally i took it in and had sprint replace the phone with a refurbished one. they said it was a known hardware issue.
 
JustSomeDude said:
So, a couple questions: what kernel are you on? Did you overclock and/or undervolt? (And of course: full wipe before flashing?)
Click to expand...

Tiamat 4.1.0+sbc

Over clock to 1113600 set on smartassV2

Wiped dalvic and cache and ran superwipe

Anytihing else? Also having to deal with more FC than usual... should I fix permissions?

If it were a hardware prolem I would have seen it before now, right?
 
Try lowering the overclock. My phone starts randomly rebooting if I overclock any more than 1075 (every phone is different).

Also, instead of superwipe next time you flash, just manually wipe everything except sd in amon ra three times. I've been seeing a lot of advice lately from knowledgeable folks like jade over at themikmik that the superwipes are rarely enough...

And yes, fixing permissions is always a good idea on a new Rom flash, especially if you restored from titanium or mybackup root.
 
While I'm waiting for it to reboot, is there any way to speed up the boot process in CM7 like in Mik3.0 (remove boot animation)?

The quickest I've had this thing boot is 4 min 11 sec.
 
4 min boot time is very long, even with wiping dalvik mine has never taken more than 2 min. I would start fresh and do a full wipe and flash vr_superwipe 2x and then flash your rom.
 
Ok I wiped everything manually (except sd) 3 times, and ran superwipe 3 times, reflashed the rom & kernel, fixed permissions and setcpu under 1ghz on smartassV2...

Still having to deal with FCs rampant and reboots under moderate stress. This may be why I left CM7 to begin with as I don't remember any of these issues iin mik3.0...

Any other suggestions before I flash my mik nandroid?
 
ok I decided to uninstall setcpu just to see if it made any difference, and used the baked in performance tweak. Not only do I think it solved my problem but it also bumped up my QS score by almost 300 points.
 
LittlrRedDot said:
ok I decided to uninstall setcpu just to see if it made any difference, and used the baked in performance tweak. Not only do I think it solved my problem but it also bumped up my QS score by almost 300 points.
Click to expand...


JMO Quadrant isn't any good and wouldn't make a decision of that. My scores can jump from 4400 to 3200 and back without changing anything(3vo). A mod here once told me #EarlyMon "friends don't let friends run quadrant". LOL and I stick by it. Your best bet would be to use cfbench or antutu. Also try using system tuner instead of set cpu. It won't interfere with most of the baked in OC settings. Again these are JMO hope it helps.
 
yeah the cm guys say not to run setcpu with their rom, rather just use the built in tweaks. this is probably why
 
mteezey said:
JMO Quadrant isn't any good and wouldn't make a decision of that. My scores can jump from 4400 to 3200 and back without changing anything(3vo). A mod here once told me #EarlyMon "friends don't let friends run quadrant". LOL and I stick by it. Your best bet would be to use cfbench or antutu. Also try using system tuner instead of set cpu. It won't interfere with most of the baked in OC settings. Again these are JMO hope it helps.
Click to expand...

+1

EarlyMon knows his business. ;)

Also I found a post by aamikam on quadrant scores, compliments of nick1313. :D

xda-developers - View Single Post - [ROM]-[MikRoms]-[04/10/2011] - MikFroYo v4.61 -ReEngineered Sense - Odex+Mods+Themes
 
Thanks for all the advice, but even though I got rid of the reboot issue I'm still dealing with FCs and other strange magical...

Not too too happy with CM7 right now...
 
Ok it did it again last night... I opened maps and did a search, as soon as my results came up the phone rebooted. I've wiped thoroughly, reflashed the rom and kernel, and set the overclock below 1ghz.

So do you suggest another wipe and flashing a previous version of the Tiamat + SBC? Or should I just try the baked in kernel (really want the Tiamat though)

Edit* Ok I wiped and flashed the previous version of this Tiamat+SBC and right off I'm slogging through FCs and then bam, the phone reboots. Gonna Try another wipe and reinstall with baked in kernel, and then it's goodbye CM7 for good this time.
 
LittlrRedDot said:
Ok it did it again last night... I opened maps and did a search, as soon as my results came up the phone rebooted. I've wiped thoroughly, reflashed the rom and kernel, and set the overclock below 1ghz.

So do you suggest another wipe and flashing a previous version of the Tiamat + SBC? Or should I just try the baked in kernel (really want the Tiamat though)

Edit* Ok I wiped and flashed the previous version of this Tiamat+SBC and right off I'm slogging through FCs and then bam, the phone reboots. Gonna Try another wipe and reinstall with baked in kernel, and then it's goodbye CM7 for good this time.
Click to expand...
You know, I loaded this ROM one time, same deal, constant reboots and freezes, and I am a fanatic about wiping...I did load destroyer, it was OK, but I like my sense...just sayin
 
LittlrRedDot said:
Ok it did it again last night... I opened maps and did a search, as soon as my results came up the phone rebooted. I've wiped thoroughly, reflashed the rom and kernel, and set the overclock below 1ghz.

So do you suggest another wipe and flashing a previous version of the Tiamat + SBC? Or should I just try the baked in kernel (really want the Tiamat though)

Edit* Ok I wiped and flashed the previous version of this Tiamat+SBC and right off I'm slogging through FCs and then bam, the phone reboots. Gonna Try another wipe and reinstall with baked in kernel, and then it's goodbye CM7 for good this time.
Click to expand...


I would go with deck 1.3d. It's rock solid and imho the best aosp room out there.

With that said, my first Evo started rebooting every now and again and eventually got worse to the point where I had to replace it. Ocn had the same problem. Your issue might not be the same as what I had but I just thought I'd throw it out there.
 
Back to Mik3.0 after what happened this am... Was sitting in class, with silent mode on, and the phone kept rigging and making noise for text messages. Even after I made sure it was on silent, had to turn it off during class, but it was embarassing.
 
I had cm7 for months on my Evo then all of a sudden I was getting force closes just like the OP had. I ended up breaking that evo and sprint sent me a new Evo 3d. I've since sold the 3D and now back to a newish Evo. I'm running CM7 right now and the 4.1.0 tiamat SBC and still getting force closes in maps and facebook etc. I just uninstalled Setcpu to see if that makes a difference. Is the Deck CM7 any better?

I don't like the sense roms since none can approach the battery life I get with AOSP... but I also dont like FCs haha
 
Here is how to solve all your problems.

1) and this is a 100% must. Get Amon RA 2.3. Link is in my signature. If you're messing around with Clockwork you're asking for trouble. Amon RA 2.3 works every time, 100% of the time. It is a flawless recovery and you should be running it on your Evo if you aren't already.

1a) Make sure you're not using ROM Manager and you do all the below steps while in recovery. ROM Manager has been proven to be buggy. Stay away.

2) Every time you flash a rom, you need to wipe data/factory reset, wipe cache and wipe dalvik cache. One time only. Like I said, with Amon RA, it works the first time. No need to wipe anything multiple times.

3) For good measure, download Calkulin's format all zip file and flash this too
http://db.tt/emsg8Z8P

4) Now you're ready to flash a rom. Did you check the md5 to ensure it's a good download? If not, be sure to do that as well.

5) Now flash your rom, flash your gapps and flash your kernel (if you want...the kernel is optional)

6) Reboot. Restoring anything with Titanium? Only restore user apps (green colored text). Do NOT restore any system data (red colored text).

This should solve all of your problems. And yes, I suggest Deck 1.3d over any build of CM7. It's flawless, everything works. Yes, Deck 1.3d is technically a beta, but ask anyone over in the XDA thread (or me) and we are all pretty much in agreement that it's superior to the "stable" build. Trust me on this one. The link for that is in my sig too, just scroll down to the download links and you should be able to find it in there. If you have any trouble, I can shoot you the direct link.
 
Good job!

now you gotta give us a link to all your aosp setup tips and tweaks. I tried like the dickens to find them the other day and I couldn't.

please? :)
 
You must log in or register to reply here.
Back
Top Bottom