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

Root [ROM] CTMod 3.80 (04/01/13)

Capn069 said:
My phone was doing that also after charging or sitting inactive for a period of time. I bumped my low clock speed to 300 and it quit doing it. It may not be what is happening on your phone but I would try that because its an easy fix.

If that doesn't fix it up I would probably reflash the rom/kernel and see if that fixes it.
Click to expand...

Thanks.
But I've never gone under 300. I'm actually at 500 right now to see if that helps at all (which it hasn't). I assume that's a high enough minimum that I don't need to try anything higher...
 
itony said:
Thanks.
But I've never gone under 300. I'm actually at 500 right now to see if that helps at all (which it hasn't). I assume that's a high enough minimum that I don't need to try anything higher...
Click to expand...

It could be the graphics overclock causing it but I don't know. If it is that there's really nothing you can do other then try a different version of hyper or a different kernel.
 
itony said:
Thanks.
But I've never gone under 300. I'm actually at 500 right now to see if that helps at all (which it hasn't). I assume that's a high enough minimum that I don't need to try anything higher...
Click to expand...

I would just start all the way over with stock and then do a fresh flash of CTMod. If that doesn't fix it, Bloods right.
 
How do I get roaming only working? Use to work through hidden menu but since this rom is based on the update the hidden menu option for RO is gone. Any other way to get this to work?
 
Sprint, I didn't think the carrier matters when this rom is only for boost and sprint and they use the same network.
 
itony said:
Thanks.
But I've never gone under 300. I'm actually at 500 right now to see if that helps at all (which it hasn't). I assume that's a high enough minimum that I don't need to try anything higher...
Click to expand...

My wife's Marquee had the same problem. CT3.68 Hyper 2.0. I tried a few settings. Even 500-900Mhz. It still got really hot and randomly froze.

Also froze with MBv2/Hyper1.5.

Could be we got some bad hardware. I set it back to a rooted ZV4 ROM all stock and it's been running fine. SLOOOW, but no freezes for over two weeks.

It's a shame cuz the CT and MB were significantly better than stock. She's a casual user but she noticed the speed difference.
 
hjc73734 said:
My wife's Marquee had the same problem. CT3.68 Hyper 2.0. I tried a few settings. Even 500-900Mhz. It still got really hot and randomly froze.

Also froze with MBv2/Hyper1.5.

Could be we got some bad hardware. I set it back to a rooted ZV4 ROM all stock and it's been running fine. SLOOOW, but no freezes for over two weeks.

It's a shame cuz the CT and MB were significantly better than stock. She's a casual user but she noticed the speed difference.
Click to expand...

yeah.sucks for us I guess we're just S.O.L. but no thanks to zv4 haha been to busy to try a clean flash but a little reboot every night and I've been good to go so far.
 
If your having problems you should try switching to supersu.

Ive been having a ton of force closes I mean TONS. I updated to 3.68 and updated superuser latest failure at the same time, so i wasnt sure what was the problem. Tried all the usual cache wipes several times.

I charge my phone at night. This morning I woke up to a phone that was about 140* when i turned the screen on a popup box said WARNING battery overheated disconnect power supply. cleared that and got the failsafe shutdown popup. :mad: pretty pissed. cpu skipped my max clock speed and stuck on 1400 all night. All my setcpu temperature and screen off profiles were ignored.

First thing I did was battery pull cuz it went totally unresponsive. then It got some freezer time to cool things down. Installed superSU right away and havnt had a single force close since. So Im pretty sure that somehow this was superusers doing. I dont trust it one bit any more.
 
jsmz said:
If your having problems you should try switching to supersu.

Ive been having a ton of force closes I mean TONS. I updated to 3.68 and updated superuser latest failure at the same time, so i wasnt sure what was the problem. Tried all the usual cache wipes several times.

I charge my phone at night. This morning I woke up to a phone that was about 140* when i turned the screen on a popup box said WARNING battery overheated disconnect power supply. cleared that and got the failsafe shutdown popup. :mad: pretty pissed. cpu skipped my max clock speed and stuck on 1400 all night. All my setcpu temperature and screen off profiles were ignored.

First thing I did was battery pull cuz it went totally unresponsive. then It got some freezer time to cool things down. Installed superSU right away and havnt had a single force close since. So Im pretty sure that somehow this was superusers doing. I dont trust it one bit any more.
Click to expand...

Keep us updated on how that's working out for you.

I can't say for sure, but my Marquee with CT3.68 and MBv2 seems to be overshooting it's cpu settings too. Even setting the max at 900Mhz, it got really uncomfortably hot.

Now with ZV4 and stock 1Ghz, the temps never gets even close to what it felt like before at 900Mhz.
 
You must log in or register to reply here.
Back
Top Bottom