- Aug 20, 2010
- 2,197
- 218
- 0
My phones' been burning the oil faster than usual since I've updated to Apex 1.3.1, in fact it could of been since 1.3. reading through the other threads here I'm seeing that I'm not the only one.
Now because Fab has integrated Jrummys Overclock app into the Apex1.3.1 update I'm assuming this would be only effecting those w/ the Jrummys Droid Overclock app installed in their phones prior to the update.
Prior to update I had set my phone to reboot at Low Voltage 1ghz setting and that was ok...until the update.
I've come across a command (surfing the web) that will reveal your actual frequency's. I thought id fly with this and see what was under the hood. As I suspected the app was making NO CHANGES TO MY PHONE AT ALL.
This could be an isolated issue w/ my phone but if you'd like to check what you got running try these commands in Terminal.
su
cat /proc/overclock/mpu_opps
I uninstalled my overclock app to go EXCLUSIVELY w/ Fabs overclocking script in Terminal. I'm hoping this might help with the oil (battery) lasting a little longer than 14 hours.
$su
# overclock
Now because Fab has integrated Jrummys Overclock app into the Apex1.3.1 update I'm assuming this would be only effecting those w/ the Jrummys Droid Overclock app installed in their phones prior to the update.
Prior to update I had set my phone to reboot at Low Voltage 1ghz setting and that was ok...until the update.
I've come across a command (surfing the web) that will reveal your actual frequency's. I thought id fly with this and see what was under the hood. As I suspected the app was making NO CHANGES TO MY PHONE AT ALL.
This could be an isolated issue w/ my phone but if you'd like to check what you got running try these commands in Terminal.
su
cat /proc/overclock/mpu_opps
I uninstalled my overclock app to go EXCLUSIVELY w/ Fabs overclocking script in Terminal. I'm hoping this might help with the oil (battery) lasting a little longer than 14 hours.
$su
# overclock
Last edited: