Root Degrading telephone life?

[roym6]

Recently my Ov has been force closing and rebooting on its own randomly or when I am running several apps at once. Has oc'ing the cpu degraded its life to the point of no return? I tried downclocking back to normal but it still does it. Also, I have noticed that it doesn't register touches along the right side anymore, so it is extremely dificult to hit the "p" key. Is that something that can be fixed or is that part dead? Lastly, my battery life is horrible now, i can only get like 4 hours while listening to music or 5ish hours while on WiFi, not even using it just on.

I think that as soon as those new phones come out I'm going to start paying $35 a month :T

 

[Leslie Ann]

It's not likely due to overclock killed your processor but it could be related. Back up your sdcards, then reformat it with your phone. Then put your data back. Cards can corrupt data and when they do, it causes what you are seeing. Backup/restore programs can also damage the app, so you also may have to re-install your rom, and re-download your apps, then put back only the data. Make sure when you backup and restore that you aren't overclocked. Also, you may be overclocked too high or just one of the apps cannot handle the overclock (again overclocked too high) and is causing it.

Re-installing your rom may also fix your screen, but it sounds damaged, that too could be the problem with stability as well.

Music will kill your battery in a few hours, especially if you set the overclock settings wrong.

 

[roym6]

Thanks for the response, but I need some clarification:
-Should I downclock when flashing a new rom or only when restoring?
-Or is it for apps?
-What would recommend while listening to music?

 

[metal571]

What ROM were you runnning? I've had issues like that where I get random reboots then I will set the clock speeds back to normal and I'll STILL get random reboots. What fixes it is reflashing the ROM, that's almost always the fix. Make sure you back up your apps with Titanium.

When flashing a new ROM, the recovery (to my knowledge, however limited that is, correct me if I'm wrong, senior members) uses the stock clock frequencies anyway so you don't have to worry about downclocking before doing that. However, for stability reasons, I would set your clocks back to stock settings before you do Titanium backups. For music, if you can handle it, stock clocks is better, but I just got done reading another thread saying interactiveX 480 min 768 max is actually the best for battery life, potentially better than stock 245 min 600 max ondemand governor. I personally use Google Play Music, and yes it does drain the battery quicker than just idling.

 

[Leslie Ann]

Thanks for the response, but I need some clarification:
-Should I downclock when flashing a new rom or only when restoring?
-Or is it for apps?
-What would recommend while listening to music?

When you are in recovery, your phone should technically be at stock speed, by default.

When using Titanium Backup or whatever in the OS, you should downclock unless you know 100% that your overclock is absolutely 100% perfectly stable, whether restoring or backing up. Data corruption at either side is bad.

Set your minimum at 480 and high at whatever is stable, that is the best combo.

 

[AndyOpie150]

It is always best to make sure the "set at boot" box is unchecked until you have figured out a stable max setting. I forgot one time to check (it was already checked with a new app download) one time and went to playing with the speed to see how high it would go before auto rebooting and just set it for the max. I put my system in a boot loop. Had to pull battery, wipe and format everything necessary and reflash the ROM. I had just spent a couple of hours downloading and putting all my apps just where I wanted them.
I learned the hard way to always double check before messing with the CPU settings.