So i Noticed just as a side note if you change your system from a read only to a writable system it sticks through boot. Idk i rebooted and before i installed i mounted my system as a writable system and when i booted back up it still has me at 1.2MHz

I didn't realize we had two threads going and I posted the below in the other thread. It might help here as well.

Post:

This is the XDA link. I did not see it on Rootzwiki, but probably not looking correctly. In this link is a zip file which appears to work for the D3. The link also contains the link to the person who actually figured this out, along with the code he/she is using. I am assuming the zip file contains this code. I am on a windows machine, and it appears that you need Linux to see the code in the zip file. When unzipped in windows, they show as zero size files, but with a hex editor program I can see something. They are not empty files.

It appears that in order for this to work, you have to set Setcpu to full throttle, min and max. And Setcpu does not report accurately, but the folks are using benchmark programs to "confirm" overclocking. So when using this hack, your phone is going to be forced to run wide open, no native underclocking. And it would be harmless to try to check for functioning, as it does not survive boot. May not be harmless in use for long periods, but that needs to be tested on each phone. And it appears this is a work in progress.

As to surviving the reboot, probably the easiest way would be to use a program like Gscript and just one button push to start after boot. You could set up an autorun program as one poster mentions, but this could be very dangerous unless you have the backups and system setup to restore from recovery.

At issue here is the overclocking and heat and speed, but just as important is voltage. Folks are reporting unstability at higher clock speeds, but this could easily be a voltage issue, and not just the pure speed. It would be my best guess that as moto is using our omap at reduced clock speed, that they have matched the system voltage to work with the reduced clock speed. If this guess is correct, then until the slots and voltages can be addressed together, there is a bit of dark stabbing going on, as undervolted conditions are just as unstable as excessive speed, and undervolting the CPU may be as harmful as the excess speed. At least with excess speed and voltage you usually get high temps, and the system will shut itself down with high temps. At least to date this has been the case.

I only mention this stuff, as it would be easy to say to yourself, hey it is working and I am good to go because my system is not bootlooping or shutting down. With the D1, Prime got us to be able to set our speeds and voltages so we were able to ensure that we were not in undervolting scenarios, and we could balance performance and battery life. So this is some good stuff, but does need to be approached with a bit of understanding, as all things root.

Useful Searches

About DroidForums.net

DroidForums.net was founded in 2009 originally dedicated for the Motorola Droid, the first Verizon Android Phone. We have since expanded our community to cover all Android Phones, Android Tablets, and Android Wearables. We discuss various topics including Android Help, Android Device Reviews, Android Apps, Phone Accessories, Android Games and more. Our ultimate goal is to be the Internet's best and largest Android Forum.