ROM & Overclocking ? Question
Right now I am curious as too if anyone has done any testing over the last 2 days of what the best ROM is for Overclocking? OTA , FLYX , RUBIX , ZAPX , APEX ? I want to get the best battery life and still maintain a great ROM to go along with it.
Currently I am on APEX RC2 and it is OK I am overclocked to 1.3 GHZ
If anyone has done any further testing Please Post Here.
When I get a chance I will do some myself but working all the time.
4000 / 30
7000 / 35
9000 / 45
1300 / 65
Also 1 more question regarding Corporate Sync on APEX RC2 ... Is there a problem with APEX RC2 Syncing too servers with this ROM because on OTA I had no problem Syncing. Is that because of blurless that is preventing me from Syncing Thanks
Edit: Additional Question
Question 3? Is it confirmed that the 1.38 GHZ overclock off ROM Manager works with every CPU ? 2nd Question. Does this install install-recovery.sh incase it does not work ? ... From What I know everyone that overclocks is on a X to X bases depending.
Last edited by lithiasales.js; 10-20-2010 at 11:30 PM.
10-20-2010 10:45 PM
Droid X Forums
I have had Flyx and now RUBIX and I have had it over clocked at 1.38 and 1.15GHZ and to be honest with you I still get awesome battery life with the 1.15 over clocked. I have found the higher you go and the higher the voltage the more battery life you will use. I also have Incognito as my theme. Works great. I hear all RUBIX roms have great battery life.
Im currently running rubixfocus1.0 and am OCed at 1.38ghz. Battery life was excellent before OCing and doing well afterwards. I tried rubixblurry and focused before and the battery life was superb. Rubixblurry was my fav of the two. But so far all three roms are extremely stable. Hope this helps.
The 1.38 GHz from ROM manager will not be stable on every Droid X; it's not on mines. I am only able to get a stable 1.1 GHz so far unfortunately. The install-recovery.sh is only to be used only if you have a stable OC that's been stressed so the settings will stay even after reboot.
In practical terms... your oc stability is going to have a lot to do with how you use your phone. For instance, i oc'd to 1.38ghz, which was really stable for my standard phone usage like texting and sending emails, web browsing, etc... However, using that same setscale to play ff7 on psx4droid for a few hours while bored at work caused my phone to overheat and go in to cooldown mode (temporary brick).
I ended up at 1.18ghz. I can play ff7 for hours without crashing at that speed and its pretty damn smooth. Another issue is battery life: the higher you clock, the more power your chip will need. 1.18 at 64 doesnt drain my battery noticably more than stock, but 1.38 sucked it dry in no time.