-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Droid X/2 Overclock App - Easy & Noob friendly ;)
- Thread starter jrummy16
- Start date
-
- Tags
- motorola droid x
MrDonBonJovi
Member
If my phone soft boots, it doesn't show the M logo, just my boot animation, is it related to overclocking or is it something else?
The problem isn't that the program has been removed, it is the "market issues" that some DroidXs have. I couldn't find it in the market or use any of the links provided until I changed to another ROM which fixed the market problems.
So I suspect that when you SBF the phone, it removed the market fix that was on the phone before you did that. You should be able to get the market fix back by modifying your .prop file again, or by moving to a ROM that has the .prop file edits already done.
sezaro21
Member
How do I modify my prop. file as I never did anything before. Is there an APK for the market place that I could use?
nope. I sbf-ed my phone from 2.1 to ota 2.2 and it is fine. Got this app no problem this morning.
pinhead875
Member
It's in my market. I have ApeX rom and Revolution theme.
Try looking at this post. You need to open the build.prop file (it is located under the /system folder) and edit it per the thread above. It is easiest to do this with Root Explorer IMHO, but there are other ways as well.
Also, it seems that the build.prop edits have been loaded onto the ROM Manager app, so if you have that installed, you can make the edits by loading the build.prop edit ROM instead of doing it manually.
If none of those options work, then you might have to load a new ROM like Apex. Although I did not try any of the new build.prop edits, I was unable to see the app either until I loaded a new ROM.
Good luck. I'm sure we can find a solution for you.
PS - Here is another thread that gives a lot of the different build.prop edits, but unfortunately it doesn't actually explain the steps to actually modify the file. I guess it was written for a more advanced user that already knew how to modify the file.
Also, it seems that the build.prop edits have been loaded onto the ROM Manager app, so if you have that installed, you can make the edits by loading the build.prop edit ROM instead of doing it manually.
If none of those options work, then you might have to load a new ROM like Apex. Although I did not try any of the new build.prop edits, I was unable to see the app either until I loaded a new ROM.
Good luck. I'm sure we can find a solution for you.
PS - Here is another thread that gives a lot of the different build.prop edits, but unfortunately it doesn't actually explain the steps to actually modify the file. I guess it was written for a more advanced user that already knew how to modify the file.
Piercing Heavens
Well-Known Member
At Ultra Low Voltage I'm getting a stable 1.35Ghz and 700Mhz. Only question is that since I have set CPU and already have it underclocking based on battery and screen off will using the ULV make a difference?
Also which program should I use to control the clock settings?
Also which program should I use to control the clock settings?
iamfiretruck
Member
What happens if your phone is "set on boot" and wont boot up? is it time to sbf?
I'm assuming you didn't have a nandroid? Jeez people.
something to look out for...my phone is stable @ 1.2ULV, but my quadrant scores are very erratic, ranging from 1400's to upper 1600's. However, at 1.1ULV, i'm in the mid 1500s very consistently.
This application does not "overclock" your phone, it passes frequency and voltage parameters to a kernel module(which actually changes the settings at the hardware level) which is the intellectual property of Milestone Overclock by Tiago Sousa, and is distributed under a GPL license.
Milestone Overclock is available freely from the Android Marketplace, and is the real reason anyone is overclocking right now. Support Tiago, and donate to him. Hopefully he'll be able to get a Droid 2 World Edition or something, and be able to support DX/D2 more closely.
Milestone Overclock is available freely from the Android Marketplace, and is the real reason anyone is overclocking right now. Support Tiago, and donate to him. Hopefully he'll be able to get a Droid 2 World Edition or something, and be able to support DX/D2 more closely.
This app is making my head spin. I could not get anything stable above 1.1GHz, tried more voltage and got nothing but a turtle. Lowered the voltage and I was able to overclock to 1.3GHz before a turtle. This goes against everything I was taught about overclocking. Overclocking = more volts, underclocking = less volts. Long story short, I'm overclocked to 1.2GHz using the Ultra Low Voltage and I'm completely stable.
for those who can't find the app in the market, read this post:
http://androidforums.com/droid-x-all-things-root/154976-2-2-market-issues-use-mod.html
it solved the problem for me.
http://androidforums.com/droid-x-all-things-root/154976-2-2-market-issues-use-mod.html
it solved the problem for me.
SlvrScoobie
Android Enthusiast
Omg just ran quandrant 2x and got 17xx! I get 14xx usually on stock.
1.35ghz on low voltage! Stable, And no turtling! My phone kicks ass!
1.35ghz on low voltage! Stable, And no turtling! My phone kicks ass!
Airmaxx23
Android Expert
Keep in mind though that the ultra low voltage isn't actually low at all. It's low when compared to the other settings but it's still higher than stock.
mxsjw
Android Expert
Ah, thank you...I did not know this.
What about when you clock it under 1ghz, or the voltages below stock then?
I guess, what is stock when comparing to this apps default choices?
Two things are NEEDED for this app.
1: The ability to import current settings into the custom profile builder.
2: The ability to read the current voltage settings, not just the clockspeed.
Honestly, taking care of #1 will effectively fix #2 at least in a roundabout way.
I was able to run 1.45Ghz ULV through a bunch of benchmarks and 1hr of Angry Birds/Reckless Racing with no problem, not even alot of heat. Then an hour after not using the phone it just rebooted while idle which makes very little sense. I've been running 1.25Ghz ULV for 2 days without a reboot, but would like to play with the 1.45Ghz ULV settings and "tweak" those values a little. Unfortunately the ULV voltage settings aren't documented anywhere, so there's no way for me to build a custom profile with the ULV 1.45 settings.
Please add the "import" functionality to the custom profiles, or at least add a way to read the current voltage settings.
2.2 OTA release day X (from walmart).
1: The ability to import current settings into the custom profile builder.
2: The ability to read the current voltage settings, not just the clockspeed.
Honestly, taking care of #1 will effectively fix #2 at least in a roundabout way.
I was able to run 1.45Ghz ULV through a bunch of benchmarks and 1hr of Angry Birds/Reckless Racing with no problem, not even alot of heat. Then an hour after not using the phone it just rebooted while idle which makes very little sense. I've been running 1.25Ghz ULV for 2 days without a reboot, but would like to play with the 1.45Ghz ULV settings and "tweak" those values a little. Unfortunately the ULV voltage settings aren't documented anywhere, so there's no way for me to build a custom profile with the ULV 1.45 settings.
Please add the "import" functionality to the custom profiles, or at least add a way to read the current voltage settings.
2.2 OTA release day X (from walmart).
Airmaxx23
Android Expert
If you want to check the current clock speed and voltage type the following command line in terminal emulator:
cat /proc/overclock/mpu_opps
There is a space after cat.
This is one of the scripts that I have setup in gscript, one press and I'm done, no retyping the line if I need to check it again later.
The ULV settings for 1.2GHz are:
1200000 65
1000000 58
850000 57
400000 36
These are all higher than stock settings except for the one 58.
The stock voltage values are:
62
58
48
33
Thanks, I've looked into the manual overclocking thread, but haven't spent any time to see if the settings were actually stored anywhere. I thought it was just sent to the module but not stored anywhere. Still, being able to quickly build a profile would be sweet.
Makes much more sense now. I had a WTFBBQ moment yesterday.