Database Info

OverClocking Motorola Droid [root]

Warning Note: Overclocking may result in damage to your phone components, loss of life expectancy, or even frying them. Overclocking is done at your own risk and we take no responsibility for any damage you inflict upon your phone.
***This guide assumes you have rooted your Droid ***
Step 1: Download evilboot8.img here. (this is to overclock to 800mhz, on the web you can find files for 900mhz, 1.1 ghz and up to 1.3 ghz (tho not stable)
Step 2: Make sure you have/do all the following..
* Make sure you have sprecovery
* Make sure you have flash_image on your system, in /system/xbin/ or /system/bin
* Make sure you perform a nandroid backup first
* Make sure to enable USB debugging on phone
Step 3: Copy the respected evilboot file to the root of your SDCard (evilboot8.img)
Step 4: Now, reboot in sprecovery
Step 5: Select mount options
* mount /system
* mount /sdcard
Step 6: From your PC run the following…
* adb shell /system/xbin/flash_image boot /sdcard/evilboot8.img OR
* adb shell /system/bin/flash_image boot /sdcard/evilboot8.img
* (Where ever your flash image is on your phone xbin folder or bin folder)
Step 7: Now, unmount both system and sdcard using the following command
* unmount/system
* unmount/sdcard
Step 8: Now, reboot your device.
Click to expand...
Click to collapse
(this is not my work, just a mash up of guides from the net)

Is this for the milestone to?

Isn't this far more complicated than necessary?
As long as you have root, the free version of Rom Manager allows you to download any of bekit's or P3Droids kernels, low/normal/high voltages up to 1.2 or 1.3 ghz I believe. That coupled with setCPU (for on-demand scaling) eliminates any need to use the SDK really, doesn't it?

yes setcpu is much essier but i just thought i post here as a resource

Overclocking made easy
Just use this app (also available on the market).
This will allow you to set a predefined speed or custom speed/vsel (voltage selection).
Then use SetCPU and use option Autodetect speed. If you don't choose this option, you won't be able to set it to it's maximum speed.
I'm using SHOLS_U2_02.31.0 (2.1-update1) from this website and working perfect after applying root offcourse.
I do not know if this app is working for other versions then SHOLS_U2_02.31.0

Sort of related:
Is there a guide to the "best" configurations for stability and battery life using SetCPU or Overclock Widget on the Motorola Droid -- I've been trying to overclock my girlfriend's phone to save her battery life but neither SetCPU nor Overclock Widget work properly. SetCPU doesn't seem to run profiles correctly and is constantly spamming the highest clockspeed chosen, eating battery life like you wouldn't believe and Overclock Widget isn't properly recognizing clock speeds, displaying the wrong value...
So I was hoping that somewhere there was a guide to configuring these options once the phone was rooted and running a ROM which used a kernel that supported overclocking.

corrosivefrost said:
Sort of related:
Is there a guide to the "best" configurations for stability and battery life using SetCPU or Overclock Widget on the Motorola Droid -- I've been trying to overclock my girlfriend's phone to save her battery life but neither SetCPU nor Overclock Widget work properly. SetCPU doesn't seem to run profiles correctly and is constantly spamming the highest clockspeed chosen, eating battery life like you wouldn't believe and Overclock Widget isn't properly recognizing clock speeds, displaying the wrong value...
So I was hoping that somewhere there was a guide to configuring these options once the phone was rooted and running a ROM which used a kernel that supported overclocking.
Click to expand...
Click to collapse
What you want to do is UNDERclock her phone
but best for battery life would be to turn off widgets that update automatically or update less frequently so once every 30 min or 15 also display time out i find around 7 seconds is aways good and brightness of display down that will all help

I literally JUST picked up a Droid from a friend (used to have an Eris)
Rooted, flashed Cyan 6 and I'm up and running with Clockwork and ROM manager.
However, absolutely none of the OC kernels are working for me :/ Infinite splash screen!! doesn't even make it to the animation.
Any suggestions?
So far I have tried 1000, 1100 and 1200 mhz low voltage kernels and also 1100 and 1200 standard voltage.

First the kernel you use you must make sure it is compatible with your rom, I had many issues with kernel being compatible with bugless beast v0.4 but was able to find on from p3droid. I would recommended searching for a kernel specific to the rom. It should also say in the roms download forum which ones are compatible. There are roms still downloadable for previous version roms like 2.1 and etc. Just becareful, I had just switched to sapphire 0.8.4 which is from a new source build and I can tell you works great, I just followed spacific instructions on rom forum for overclocking, it mentions roms have scripts that make certain kernels work with them only if they were created for it or compatible. I should mention I also tried cm6 and I've found sapphire more stable and customizable as well as user friendly.
Sent from my Droid using XDA App

I didn't know where to post this, but I figured this was an appropriate thread because it dealt with overclocking.
http://www.greenecomputing.com/apps/linpack/linpack-top-10/
I was unable to get to the device specific listing, but it's clear that the Droid is ridiculous being on the list (once as the Milestone). I was wondering what it was these guys did to get so high? I understand flashing a stupid fast ROM, but are these phones similar to "dyno queens" in relation to cars? Just good for numbers but unstable for day-to-day use?
If so, what are the numbers for more "stable" ROMs in terms of MFLOPs?

Apparently the issues I was having were related to the recovery image not being properly flashed, therefore not flashing other zips correctly... after re-flashing the recovery a few times, I was able to boot up with Chevy's 1200mhz Low Voltage kernel and it runs perfectly on CM6.

Collin_ph Battery Tweak RC1 for Cyanogen / Darch Froyo roms (possibly others)

UPDATE 8/24! Please go to the site and download the latest version RC1b which corrects 2 small bugs people have reported. It now sets the proper permissions on batt-diag so it runs, and it changes the way the program tries to SU so that you can choose to not have the program attempt to run SU if your rom has trouble running su from terminal;
---Original Below---
I decided to create a new forum for the latest battery tweak as so much has changed since the initial versions.
To get things started, I'll just say that collin_ph battery tweak is a collection of scripts designed to make the hero (for now) last longer on battery, run faster, and run better. The tweak includes CPU management, Battery Management, Disk Performance Boost, Scheduler Boost, LED Fix, Audio Quality boost and other features to improve the usability of your Hero.
Instructions: Go to http://www.primoweb.com/froyo to download the latest version and get the documentation.
Boot into recovery and flash the zip file.
After reboot, you may run batt-cfg from shell or terminal (Note, that the scripts will all request root access, so there's no longer a need to su before running them).
to run batt-cfg
go to terminal in the phone or use adb shell from your PC
once there, type
batt-cfg
It will pull up a menu of choices. For further info, see http://www.primoweb.com/froyo
You can load a 691 mhz default (most Cyanogen kernels now only support up to 691 mhz anyway), or, if you have an uncapped kernel, you can choose a 768 mhz setting. Note: Both settings actually run at 691 when on battery and only run higher when plugged in.
The basics of how the battery is extended is that this tweak causes your phone to scale down (to lower frequencies) faster and to scale up slower. In stock configuration, the cpu scales up when only under 70% load -- while part of this tweak causes it not to scale until it's at 95% load, avoiding unnecessary scaling and battery drain. A second (and arguably more important) feature, is that as the battery drains, it lowers the maxumum CPU frequency. So when you have 1% battery left, you may be running at 468mhz instead of 691. Another plus is that the phone runs in a "higher performance" mode while charging via AC, and another mode to make sure the phone is actually charging when connected bia USB, in addition to the settings mentioned above when the phone is on battery.The best part is that almost every parameter in the system is adjustable through terminal or adb shell using a program called batt-cfg -- just run it and you'll be presented with a menu of options.
I'm constantly updating the documentation, so please check back often as I'll update this thread until there's a final 3.0 version. We're already working on a 4.0 which will be available on the market. We'll post more info there as it happens at www.tweaktool.com
COMPATIBILITY NOTES:
This tweak only works with clockable kernels. A lot of ROMS have reclockable or overclockable kernels which should work. I recommend Froyo roms, but I have heard of the tweak running with 2.1 releases. The main incompatibility seems to be with the service startup-- on some roms, the service doesn't automatically start up.
to verify if your rom is compatible and that the tweak is working, reboot.
Then go to terminal or adb shell and type:
pidof batt.sh
if it returns a number, then the service is running. If not, you'll have to start it manually every time the phone reboots by going to terminal or adb shell and typing
batt-cfg
then choose the option to save and exit. This will manually start or restart the service. Note: if your rom does not start the service automatically, you'll have to do the above batt-cfg procedure after EVERY boot or battery tweak will not run.
If you're a ROM developer, you'll can probably make your ROM compatible by adjusting your rom (ramdisk) to call (import) /system/etc/init.local.rc from init.rc -- assuming your ROM has an overclockable kernel like fresh, darch, or others.
ROMS based on unclockable kernels like Damage Control, won't work without a kernel upgrade and may still not start the service automatically upon reboot.
Thanks to Decad3nce for testing and improving several parts of the battery tweak.

So to flash this tweak and have it working on the latest Froyo nightly, do we need to flash overclockfix.zip ??
I had to flash this fix almost with ever nightly, coz the frequency list would not show up when i need to customize tweak settings.

I was reading the documentation and saw the CFS tweaks are disabled by default. Will this correct the GPS issue that was on beta 10?
Froyo Hero to the rescue

Thank you for all your work on this, got 12 hrs on 50% today with beta 10 and Decad3nse #8, 768 pre-set, most time I've ever gotten outa my Hero. Flashed your RC1 (with Darch's RC1) about 45mn ago and used custom settings to jack-up the max to 768 across the board, min.s and intervals stock. Thank you for explaining the 768 pre-set is really 691! Gonna sit on what I've got for a day and then try w/ Darch's "fix" kernel. Hope I can keep the max on batt @ 768 'cause it seems to make my Hero more responsive/less laggy.

I was not able to use the batt-diag in adb shell. I'll report back tomorrow how the tests go.

What is the procedure for installing this if you're currently running Beta 10? Do you have to wipe, reflash, etc or can you just flash the update and reconfigure in adb?

it made my hero laggy!!!

ToxicToastKatz said:
What is the procedure for installing this if you're currently running Beta 10? Do you have to wipe, reflash, etc or can you just flash the update and reconfigure in adb?
Click to expand...
Click to collapse
Follow the uninstall steps form the documentation
How do I uninstall it?
adb shell
batt-rm.sh
Follow the prompts and the tweak will be uninstalled.
Click to expand...
Click to collapse
Then flash the new version, this is how I have been doing it.

Excellent tweak! Used it through Beta and now enjoying the RC. Well done!

wow.. the way things are going i don't think i am going to jump into a evo... i am loving my hero so much.... thank you for all your hard work..

OK I don't know if its just me but when I go into batt-cfg it just runs whoami uid o
Batt-cfg root
Or something like that over and over again. It worked on beta 10 but not like this I don't understand

8/22 RC1 update does not have a working batt-diag, says not found. I am getting "89" when I do "pidof batt.sh"

imb951 said:
8/22 RC1 update does not have a working batt-diag, says not found. I am getting "89" when I do "pidof batt.sh"
Click to expand...
Click to collapse
Thanks for the notes on batt-diag. I'll look into it and release a fix this evening. Thanks.

Papa Smurf151 said:
OK I don't know if its just me but when I go into batt-cfg it just runs whoami uid o
Batt-cfg root
Or something like that over and over again. It worked on beta 10 but not like this I don't understand
Click to expand...
Click to collapse
hmm.. what rom are you running? It sounds like the code I've got in to detect root (and ask for it if necessary) is causing an issue with what you're running. All it does is a whoami to see if you are logged in as root, if not, it su's and relaunches itself.

I'm getting the same root problem with 8/22 nightly.
Sent from my HERO200 using XDA App

Papa Smurf151 said:
OK I don't know if its just me but when I go into batt-cfg it just runs whoami uid o
Batt-cfg root
Or something like that over and over again. It worked on beta 10 but not like this I don't understand
Click to expand...
Click to collapse
hmm.. what rom are you running? It sounds like the code I've got in to detect root (and ask for it if necessary) is causing an issue with what you're running. All it does is a whoami to see if you are logged in as root, if not, it su's and relaunches itself.

collin_ph said:
hmm.. what rom are you running? It sounds like the code I've got in to detect root (and ask for it if necessary) is causing an issue with what you're running. All it does is a whoami to see if you are logged in as root, if not, it su's and relaunches itself.
Click to expand...
Click to collapse
I'm using my red dawn rom with a modded ramdisk to allow for the battery tweak. The beta 10 worked and even the rc1 asked for su and I said allow the the whoami just kept going and going. I uninstalled via ur instructions on ur site and flashed again and same results

RC1 kept crashing my phone. Right after saving settings it would freeze them hard reset and get stuck at the htc screen. I've reverted back to beta 10. The only problem I've ever had with beta 10 is I would have random hard resets when charging. I really can't even pin point it on this tweak but its the only thing that I could think that would do it.

zachslavin said:
RC1 kept crashing my phone. Right after saving settings it would freeze them hard reset and get stuck at the htc screen. I've reverted back to beta 10. The only problem I've ever had with beta 10 is I would have random hard resets when charging. I really can't even pin point it on this tweak but its the only thing that I could think that would do it.
Click to expand...
Click to collapse
Were you doing the updates through ADB or terminal? When would it hard lock up.. during save changes?

CFS Tweaks and Decad3nce Kernel
I understand from reading the Kernel info, that the CFS on this tweak needs to be disabled first....did you make CFS tweaks on by default? Arent we supposed to flash the kernel first, then disable cfs tweaks and reboot? Im confused as to the order in which things are flashed. WIPE, ROM, GSHITZ, BLACKMOD, KERNEL#7, COLLINS RC1. Then go to term EMU and disable CFS, then save then go back into batt-cfg and choose option 1 768 and save and exit then reboot. Woudl that be correct?

[App BETA][Updated 10.17.11]viperMOD Voltage Control (post only if you are a tester!)

This is going to be the thread for everyone to post in when they are testing the app, regardless of device. Please only post in this thread if you are a tester to minimize on clutter.
Ok guys, I have a test version of the app ready and I need some testers! This app was put together by Smurph82 (Ben), me (Derek), and another friend of mine (Will) with Ben doing the majority of the coding. If Smurph82 asks you anything, ANSWER HIM! He is the guy who will get this fixed! Please bear with us as we get the bugs worked out and get this to be the best voltage control app out there!
Some things don't work and I need help figuring out what else isn't working. I'm looking for 2-3 testers for devices I don't officially support right now. (check the list in my sig of officially supported devices and make sure you're applying to beta test for a device not listed there) All testers will get the paid version of the app when done, assuming you provide me with feedback of this app. Here are a few rules...
0.) You must be on a HAVS/SVS kernel (exceptions Nexus S/NS4G with mathkid or Netarchy kernel). If you don't know what this means, please do not send me a request to beta test. You must also be on a ROM that supports init.d (99% of ROMs)
1.) If you are selected to be a tester, you WILL NOT send this app to anyone else and you will use it only on your personal devices.
2.) If you are not selected to be a tester, please don't blow up my PMs or thread complaining about it.
3.) You will provide me with some feedback about the app, what works and what doesn't, what should be implemented and/or taken out. I don't think this is an unreasonable request.
4.) To be an official beta tester, your submissions will BY PM ONLY. This information needs to be sent to me or I will ignore your PM. I don't have time to respond and ask for the information that I need. Please don't post in this thread for wanting to test, this thread is for the testers to post their results and collaborate with one another. Please include this with your beta testing submission:
Device:
ROM:
Kernel:
Please also keep replying with our whole conversation so I can reference it.
5.) I may be going to bed soon so if you get nothing from me tonight, I will hit you up tomorrow.
Thanks guys, I look forward to working with all of my beta testers!!
Known Issues:
[*]Landscape in 2nd tab doesn't scroll
Some voltages presets need to be implemented
Links are too small
[*]Netarchy kernel detection shows UNKNOWN
Shouldn't show init.d button if one doesn't exist
[*]App looks in the wrong place for SVS kernel voltages
Cannot save init.d file

Alright, I've run into one problem right off the bat but I think it will be easy to solve.
It says:
"File at /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs was not found
My frequency tables are at:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
I know it will work, I've been using the vipermod terminal script to change my voltages, it just can't find my frequency tables it seems.
EDIT: i messed up the file path for my tables (left out the /cp0) fixed now.

I am also getting the same issue of:
File at /system/etc/init.d/74havsvoltages was not found.
DEVICE: HTC EVO 4G
KERNEL: TIAMAT 3.3.7

Im getting file at /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels)havs was not found
Also I cant adjust voltages up or down as I keep getting a pop up saying "This is not a HAVS kernel"
MIUI 1.8.12 DEXT
HTC DESIRE
SVS stock kernel [email protected] 2.6.37
Dont like the contacts font colour either imho difficult to read

File at /system/etc/init.d/74havsvoltages was not found.
DEVICE: NEXUS ONE
KERNEL: IR 2.6.38.8_AVS-CM7_CFS_20110813_1517

Already off to a fantastic start lol
OK, so issues with SVS detection. On the main page, does it detect that you are running an SVS kernel? It should say "This is an SVS kernel" right?
Do you already have an init.d file there from the viperMOD script when you try to read it? If so, can you back it up, delete it, and try to generate a new voltage file from the app?
Thanks guys!

yes it detects that I have an SVS kernel. Tried deleting the 99voltages file in my init.d and still no dice.

-viperboy- said:
Already off to a fantastic start lol
OK, so issues with SVS detection. On the main page, does it detect that you are running an SVS kernel? It should say "This is an SVS kernel" right?
Do you already have an init.d file there from the viperMOD script when you try to read it? If so, can you back it up, delete it, and try to generate a new voltage file from the app?
Thanks guys!
Click to expand...
Click to collapse
device : nexus s
rom : oxygen 2.2.1
kernel : tried both matr1x 5.5 and netarchy 1.4.0
i am having the same issue. the main page does not detect SVS kernel. it says this is a UNKNOWN kernel. (and i thought netarchy and matr1x are the only kernel compatible to this.
gotta go to sleep now, i will check again tomorrow ..

ok viperboy, first off thanks! i have several initial observations. the app assumes you have the voltage script installed in order to work. i think this should be the opposite. if not detected on app install the app should install one for the user, otherwise you would still need to use the vipermod te script in order to use the app by saving changes on default settings to create the init.d script. second, at a hi density view of 200, the lettering in your about section is a bit too small and your links are barely viewable. this needs to be adjusted. and finally, if you make a voltage selection too low for your phone to handle and need to do a battery pull because your phone locks up, i LOVE how it automatically resets itself to kernel defaults negating the need for having to flash a reset zip, bravo!! however, it changes your customized cpu settings as well. in my case it changed my cpu levels from 128/499 smartass to 245/998 interactive.
evo 4g/decks 1.3b2/sz 2.2.1 cfs
Thanks bud
ropodope
499mhz is the new 998mhz.

Jake33108 said:
yes it detects that I have an SVS kernel. Tried deleting the 99voltages file in my init.d and still no dice.
Click to expand...
Click to collapse
Please explain a little bit further. It sees its an SVS kernel, then what happens? Can't create the voltages?
saryu said:
device : nexus s
rom : oxygen 2.2.1
kernel : tried both matr1x 5.5 and netarchy 1.4.0
i am having the same issue. the main page does not detect SVS kernel. it says this is a UNKNOWN kernel. (and i thought netarchy and matr1x are the only kernel compatible to this.
gotta go to sleep now, i will check again tomorrow ..
Click to expand...
Click to collapse
OK, no Netarchy/mathkid kernels show up as unknown. Thanks for the info.
ropodope said:
ok viperboy, first off thanks! i have several initial observations. the app assumes you have the voltage script installed in order to work. i think this should be the opposite. if not detected on app install the app should install one for the user, otherwise you would still need to use the vipermod te script in order to use the app by saving changes on default settings to create the init.d script. second, at a hi density view of 200, the lettering in your about section is a bit too small and your links are barely viewable. this needs to be adjusted. and finally, if you make a voltage selection too low for your phone to handle and need to do a battery pull because your phone locks up, i LOVE how it automatically resets itself to kernel defaults negating the need for having to flash a reset zip, bravo!! however, it changes your customized cpu settings as well. in my case it changed my cpu levels from 128/499 smartass to 245/998 interactive.
evo 4g/decks 1.3b2/sz 2.2.1 cfs
Thanks bud
ropodope
499mhz is the new 998mhz.
Click to expand...
Click to collapse
Well, it shouldn't install one for the user, it should just error. We don't want to set a bad voltage that is too low for your phone or anything!
The links are an easy fix, thanks for the input.
And as far as setting too low of a voltage, that's because it doesn't write the init.d file yet. You could still end up with the same problem as the script if you set a voltage too low and saved it. And it shouldn't have changed anything like that at all. Could you explain how it changed your CPU settings??

Quick update, it reads my init.d 74havsvoltages file that the script made now. But it still won't let me lower or raise anything.
When I hit the "Adjust Voltages" tab it says "A havs or svs file cannot be found. Are you sure your kernel supports this?"
I believe this is because its looking for my files under:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
and
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_svs
when my voltages are really at:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
Just out of curiosity does this require root privileges maybe? Because I never got a SU request for it.

Jake33108 said:
Quick update, it reads my init.d 74havsvoltages file that the script made now. But it still won't let me lower or raise anything.
When I hit the "Adjust Voltages" tab it says "A havs or svs file cannot be found. Are you sure your kernel supports this?"
I believe this is because its looking for my files under:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
and
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_svs
when my voltages are really at:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
Click to expand...
Click to collapse
Ok, small oversight on that. Thanks much!

naf007 said:
Im getting file at /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels)havs was not found
Also I cant adjust voltages up or down as I keep getting a pop up saying "This is not a HAVS kernel"
MIUI 1.8.12 DEXT
HTC DESIRE
SVS stock kernel [email protected] 2.6.37
Dont like the contacts font colour either imho difficult to read
Click to expand...
Click to collapse
If the app does not detect the HAVS file correctly it will not allow you to update as it would be have not files.

I know that viperBoy requested your specs for being a beta tester
but please provide me with your phone, ROM, and Kernel in your post so I can
better understand your problem. This was built on an Evo 4g, CM7, Tiamat 4.0.*. Thanks.
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs is the path that I knew development on my platform. I am working on this.

Already off to a fantastic start lol
OK, so issues with SVS detection. On the main page, does it detect that you are running an SVS kernel? It should say "This is an SVS kernel" right?
Do you already have an init.d file there from the viperMOD script when you try to read it? If so, can you back it up, delete it, and try to generate a new voltage file from the app?
Click to expand...
Click to collapse
It does detect that its a SVS on the main page
I deleted my file that I created with the script and tried to generate a new one but no change
HTC DESIRE
MIUI 1.8.12 DEXT XPART
Stock Kernel SVS [email protected] 2.6.37

I don't have an example of the /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
can someone please post me one thanks. Sorry the svs had not been implentment due to the fact that I only have one phone.

I'm restoring a backup right now, I'll post mine in just a second.

sure. i set the voltages too low on purpose in order to cause my phone to lock so that i would have to do a battery pull because i was curious to see if my kernel voltage defaults would be restored on reboot....and they were. i think that is great. i then reset them using the app to where i knew my phone would handle them. after doing so i took a look at my custom cpu settings which i have set to retain on reboot. when i did they were completely changed from 128/499 smartass to 245/998 (stock settings) along with the governor being changed to interactive. i just thought that was weird.
also the tapatalk app is not allowing me to reply to this thread. it keeps saying "failed to connect to forum. please check with the forum administrator if this problem persists". i have to reply from my laptop.
ropodope
499mhz is the new 998mhz.

Here's my file. All of my build info is in my sig.

Jake33108 said:
Here's my file. All of my build info is in my sig.
Click to expand...
Click to collapse
Thanks I will be working on this.

Milestone Stock with DSIfix makes sense

I'm testing 6 month various mods and stoxk Version to get an stable milestone firmware. Now I found my solution:
If anybody is interested in.
Milestone Froyo Stock Africa Kernel
DSIfix from kabaldan (many many thanks)
Overclock 900
Gingerbread theme
Launcher pro
On my stone it runs very stable, smooth and without any freezes/or reboots and no battery drain.
I have not found any Mod which works like this
Sent from my Milestone using XDA Premium App

Excelent
duddle said:
I'm testing 6 month various mods and stoxk Version to get an stable milestone firmware. Now I found my solution:
If anybody is interested in.
Milestone Froyo Stock Africa Kernel
DSIfix from kabaldan (many many thanks)
Overclock 900
Gingerbread theme
Launcher pro
On my stone it runs very stable, smooth and without any freezes/or reboots and no battery drain.
I have not found any Mod which works like this
Sent from my Milestone using XDA Premium App
Click to expand...
Click to collapse
Can you post the links to the files that your using??? ROM, KERNEL, THEME AND OVERCLOCK FILE??? i ll like to test it...

Hmmm if you talk about overall speed and stability, go for CM 6.3.0 then update to 6.3.1 via the CM update engine inside the rom. This plus the dsifix newest version = nothing beats it, even stock roms.

I've been running similar to this for quite some time, and NOTHING BEATS STOCK BATTERY LIFE. That is my biggest problem with all the custom roms.

b4 i bought my xperia play this is the setup i wished someone would make, but i had no idea how to go abouts it myself, if you could make a quick guide on how to achieve this setup im sure many would be very appreciative.

Give me a gew days please
At the moment i'm without real internet access
Sent from my Milestone using xda premium

so what are all those mods about then?

I've used Stock-ROM for a long time as well, but i was not able to get any modules working (DSIfix). how did you do that?
thx for your help!

Can you post nandroid backup of this ROM? I'm really want to try it.
Thanks

duddle said:
I'm testing 6 month various mods and stoxk Version to get an stable milestone firmware. Now I found my solution:
If anybody is interested in.
Milestone Froyo Stock Africa Kernel
DSIfix from kabaldan (many many thanks)
Overclock 900
Gingerbread theme
Launcher pro
On my stone it runs very stable, smooth and without any freezes/or reboots and no battery drain.
I have not found any Mod which works like this
Sent from my Milestone using XDA Premium App
Click to expand...
Click to collapse
Kernel from here:
http://and-developers.com/sbf:milestone221
I used the africa kernel (full sfb not service!) because it the newest one with less DSI errors but should also work with others
I use Androidiani OR
http://code.google.com/p/androidiani-openrecovery/
to root the phone NOT for overclock!!!
GB Theme:
http://forum.xda-developers.com/showpost.php?p=12366159&postcount=846
I like it - thanks sileshn
for dsifix on stock 2.2 you need
=> german language follow this link
http://www.android-hilfe.de/root-ha...sammen-mit-dsifix-ko-laden-4.html#post1854391
thanks tuxor! <=
some additional modules (I think important is the new symsearch.ko!
https://raw.github.com/nadlabak/and...gingerbread/prebuilt/lib/modules/symsearch.ko
https://raw.github.com/nadlabak/and...erbread/prebuilt/lib/modules/cpufreq_stats.ko
https://raw.github.com/nadlabak/and...gingerbread/prebuilt/lib/modules/overclock.ko
copy all modules to /system/lib/modules
should have permission 644 and owner root:shell (0:2000)
0)
backup your phone - I prefer nandroid!!!!!
If something went wrong your phone will not boot!
Then go back to androidiani or and fix the problem with console or recover your backup!
1)
if not already done:
copy mot_boot_mode to mot_boot_mode.bin
create a new one (with the same permissions and ownership)
/system/bin/mot_boot_mode:
--
#!/system/bin/sh
export PATH=/system/bin:$PATH
#run original script
mot_boot_mode.bin
for BOOT in "/system/etc/init.d/"*; do
.$BOOT
done
--
2)
create
/system/etc/init.d/00modules:
--
#!/system/bin/sh
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/dsifix.ko
insmod /system/lib/modules/cpufreq_stats.ko
insmod /system/lib/modules/overclock.ko
--
# then dsifix together with overclock should works fine
3)
/system/etc/init.d/10overclock:
--
#!/system/bin/sh
echo "5 900000000 62" > /proc/overclock/mpu_opps
echo "4 700000000 54" > /proc/overclock/mpu_opps
echo "3 500000000 47" > /proc/overclock/mpu_opps
echo "2 250000000 34" > /proc/overclock/mpu_opps
echo "1 125000000 32" > /proc/overclock/mpu_opps
--
additional benefit:
all apps where now shown in battery statistiks
dsifix - i tried version 2.4 - without any problems, no batt drain
at the moment I try 2.61 seems also works fine
please follow the thread of kabladan
http://forum.xda-developers.com/showthread.php?t=1210819
thanks to kabaldan for this great work!
I use link2sd (market) to expand the memory of the phone
(hint: format your sdcard with a second FAT partition for that - NOT ext2/3/4)
christian7301 from android-hilfe forum uses memhack from which also should work fine.
Hope that will help
If anybody can explain me how to make a nandroid backup without my personal data I will do that.

thanks !!
duddle said:
If anybody can explain me how to make a nandroid backup without my personal data I will do that.
Click to expand...
Click to collapse
if you are using a current OR you can choose which partitions should be backuped to nandroid. I guess you have to select all except 'Data'.

isn't gingerbread web browser better than stock?

bonanza123 said:
thanks !!
if you are using a current OR you can choose which partitions should be backuped to nandroid. I guess you have to select all except 'Data'.
Click to expand...
Click to collapse
So I tried to make a nandroid backup excluding personal data. The restore doesnt run.
The problem I realized - I deleted some core apps cause I dont use them. E.g. I use launcher pro so I deleted tbe default launcher.
The nandroid restore was succsessful but first boot of the device fails because of the lack of a launcher.
So at the moment I could not create a bootable nandroid - sorry
Sent from my Milestone using xda premium

I'll give this a go and make a nandroid backup for guys interested today.
Update : I'll make a nandroid of the full stock rom with fixes and a flashable zip with the fixes alone.

Flashable zip
Here is the flashable zip of the fixes mentioned in OP. The only requirement is that you have the ability to run AOR, meaning you need vulnerable recovery flashed. I tried this on a fresh flash of the ARAB sbf.
Please backup before flashing this. This is for stock milestone roms only.
This zip will accomplish the following.
1. Root your phone
2. Install busybox
3. Install modules and script to overclock your phone to the settings shown below. You can edit the 10Overclock file to your liking. I have used CM6 settings.
Code:
echo "5 1000000000 64" > /proc/overclock/mpu_opps
echo "4 800000000 59" > /proc/overclock/mpu_opps
echo "3 600000000 52" > /proc/overclock/mpu_opps
echo "2 400000000 40" > /proc/overclock/mpu_opps
echo "1 250000000 32" > /proc/overclock/mpu_opps
4. Activate init.d support. You can add additional scripts to this folder to run it, like apps2ext, Zeppe's Supercharger, Kernel Tweaks etc.
5. Install the latest DSI Fix 2.61 ( thanks to the master )
6. Install autoboot to recovery script. I have included an app, quickboot for it. Those who have APM can use that.
I have also added an awesome app called CPUStats which is very handy to see information about your CPU stats . Thanks to amossam the developer.
If you have any doubts, please ask. A few screenshots.

sileshn said:
Here is the flashable zip of the fixes mentioned in OP. The only requirement is that you have the ability to run AOR, meaning you need vulnerable recovery flashed. I tried this on a fresh flash of the ARAB sbf.
Please backup before flashing this. This is for stock milestone roms only.
This zip will accomplish the following.
1. Root your phone
2. Install busybox
3. Install modules and script to overclock your phone to the settings shown below. You can edit the 10Overclock file to your liking. I have used CM6 settings.
Code:
echo "5 1000000000 64" > /proc/overclock/mpu_opps
echo "4 800000000 59" > /proc/overclock/mpu_opps
echo "3 600000000 52" > /proc/overclock/mpu_opps
echo "2 400000000 40" > /proc/overclock/mpu_opps
echo "1 250000000 32" > /proc/overclock/mpu_opps
4. Activate init.d support. You can add additional scripts to this folder to run it, like apps2ext, Zeppe's Supercharger, Kernel Tweaks etc.
5. Install the latest DSI Fix 2.61 ( thanks to the master )
6. Install autoboot to recovery script. I have included an app, quickboot for it. Those who have APM can use that.
I have also added an awesome app called CPUStats which is very handy to see information about your CPU stats . Thanks to amossam the developer.
If you have any doubts, please ask. A few screenshots.
Click to expand...
Click to collapse
Brilliant work as usual. If your ever looking to train an apprentice, I'm a second year IT student looking to learn how

LuigiC6 said:
Brilliant work as usual. If your ever looking to train an apprentice, I'm a second year IT student looking to learn how
Click to expand...
Click to collapse
Thanks for the compliment, but in reality you'll have more tech brains than me.

I use the Claro - Brasil SBF and I got no DSI errors .
Maybe you want to test it too.

can anyone compare overall speed, multitasking abilities, gaming performance and battery life (maybe stock browser) of this solution to CM7?

MuF123 said:
can anyone compare overall speed, multitasking abilities, gaming performance and battery life (maybe stock browser) of this solution to CM7?
Click to expand...
Click to collapse
Compared to CM7 this rom is perfect. Excellent battery life, decent gaming performance, very speedy with no slow down, and excellent multitasking. Only downside is less customization abilities, but one could easily get past that

[Q] How to Overclock CPU & GPU that survives a reboot ??

I am new to overclock things, I am running on stock 2.3.6 today after a prolong research I managed to overclock my CPU and GPU. I've followed the following Method:
http://rootzwiki.com/topic/14511-opptimizer-projekt-milestone-overclock-for-omap4-devices/
I've done everything except the part i was not able to understand:
"Loading at Boot/Scripts:
The new update.zip's will install a basic init.d script to "/system/etc/init.d/00opptimize". If you've found settings that are "stable" for your device, and you'd like to run these at boot, you may edit this file accordingly. Be default, this script only loads the kernel modules. This requires your ROM to have init.d support to work. If you cannot find a method of getting init.d working, you can use Script Manager to execute this file at boot."
Now whenever I am restarting my phone it is going back to its stock speed, I just want to know that how can I set it to work even after restart.
I kindly request Jim, lkrasner, JRW 28,alteredlikeness,rdavisct,cogeary andApex_Strider to help me with this issue as i know our phone is capable of handling 1250MHz CPU and 384 MHz of GPU Speed.
Thank You.

john1989 said:
I am new to overclock things, I am running on stock 2.3.6 today after a prolong research I managed to overclock my CPU and GPU. I've followed the following Method:
http://rootzwiki.com/topic/14511-opptimizer-projekt-milestone-overclock-for-omap4-devices/
I've done everything except the part i was not able to understand:
"Loading at Boot/Scripts:
The new update.zip's will install a basic init.d script to "/system/etc/init.d/00opptimize". If you've found settings that are "stable" for your device, and you'd like to run these at boot, you may edit this file accordingly. Be default, this script only loads the kernel modules. This requires your ROM to have init.d support to work. If you cannot find a method of getting init.d working, you can use Script Manager to execute this file at boot."
Now whenever I am restarting my phone it is going back to its stock speed, I just want to know that how can I set it to work even after restart.
I kindly request Jim, lkrasner, JRW 28,alteredlikeness,rdavisct,cogeary andApex_Strider to help me with this issue as i know our phone is capable of handling 1250MHz CPU and 384 MHz of GPU Speed.
Thank You.
Click to expand...
Click to collapse
CPU overclocking can be tricky, if not downright frustrating as hell. Its a matter of testing, and running at slightly bumped-up speeds over the course of the OC'ing process to find a stable CPU frequency setting. Not all users can hit 1.2GHz or higher, whereas others can. It depends on the device, and nothing is really 'static' as far as "across the board" potential CPU clock speeds for our device. There is an init.d support .zip that can be flashed for roms that do not have init.d support (such as stock rom) but this will not work for ICS or JB versions since they are running newer kernels and as the init.d support is designed to work on the "older" kernel modules.
Sent from my MB865 using xda premium

I've downloaded moto_init_d-signed.zip and mo_simp_1.5_edison-signed.zip from http://code.google.com/p/opptimizer/downloads/list and flashed in CWM now I've init.d in my /system/etc/init.d
I've successfully overclocked my phone to 1250 MHz for CPU and 384 MHz for GPU Using:
# echo 3 1250000000 1390000 > /proc/overclock/mpu_opps
# echo 384000000 > /proc/overclock/gpu_opps
I've even confirmed my speed in setcpu and by using it says I am running on 1250 MHz, and my phone is very much stable I played modern combat 2 for around 1/2 an hour and used my phone for around 3-4 hours without any bootloop.
Only the problem is that I am not able to survive my overclock after reboot. After reboot it is reverting back to 1000Mhz

john1989 said:
I've downloaded moto_init_d-signed.zip and mo_simp_1.5_edison-signed.zip from http://code.google.com/p/opptimizer/downloads/list and flashed in CWM now I've init.d in my /system/etc/init.d
I've successfully overclocked my phone to 1250 MHz for CPU and 384 MHz for GPU Using:
# echo 3 1250000000 1390000 > /proc/overclock/mpu_opps
# echo 384000000 > /proc/overclock/gpu_opps
I've even confirmed my speed in setcpu and by using it says I am running on 1250 MHz, and my phone is very much stable I played modern combat 2 for around 1/2 an hour and used my phone for around 3-4 hours without any bootloop.
Only the problem is that I am not able to survive my overclock after reboot. After reboot it is reverting back to 1000Mhz
Click to expand...
Click to collapse
You have to physically change the echo table values using Root Explorer using the text editor. Look for this section in the 00pptimize file and change echo 3 at this code line:
# Droid3/Bionic/Atrix2 stock Settings
# echo 3 1000000000 1375000 > /proc/overclock/mpu_opps
# echo 2 800000000 1313000 > /proc/overclock/mpu_opps
# echo 1 600000000 1200000 > /proc/overclock/mpu_opps
# echo 0 300000000 1025000 > /proc/overclock/mpu_opps
Then, click back to save the .bak file and reboot. Changes should stick through reboot after this.
Sent from my MB865 using xda premium

It is reverting back to its stock after reboot even after editing echo values.
By the way thank you for your valuable replies I am working on it if I find a way I will post in general thread.

john1989 said:
It is reverting back to its stock after reboot even after editing echo values.
By the way thank you for your valuable replies I am working on it if I find a way I will post in general thread.
Click to expand...
Click to collapse
I will test also after FXZ'ing back to stock rooted 2.3.6. and let you know how I manage to OC this way. I PM'd you also, so I'll be getting back shortly with more info...
Sent from my MB865 using xda's premium carrier pigeon service

http://forum.xda-developers.com/showpost.php?p=27710171&postcount=118
this is the method PM'd by alteredlikeness to me.
Alteredlikeness I am bowing down your method works like charm and If XDA will allow me I will hit thanks button for minimum 1 million times
I would also like to thank Apex_Strider for showing patience and replying to all my questions.
Tomorrow I will post a fresh thread along with screen shots of overclocking that can survive even after reboot

john1989 said:
http://forum.xda-developers.com/showpost.php?p=27710171&postcount=118
this is the method PM'd by alteredlikeness to me.
Alteredlikeness I am bowing down your method works like charm and If XDA will allow me I will hit thanks button for minimum 1 million times
I would also like to thank Apex_Strider for showing patience and replying to all my questions.
Tomorrow I will post a fresh thread along with screen shots of overclocking that can survive even after reboot
Click to expand...
Click to collapse
Correct. I linked you to that post since it kind of shows how to get to and edit the 00opptimize file - also, make sure you delete the .bak that gets created - if there is a .bak file in the init.d folder, you will bootloop!

alteredlikeness said:
Correct. I linked you to that post since it kind of shows how to get to and edit the 00opptimize file - also, make sure you delete the .bak that gets created - if there is a .bak file in the init.d folder, you will bootloop!
Click to expand...
Click to collapse
Indeed, deleting the .bak file created after changing the echo table values is a key step. I forgot to tell him that, since I always delete without even thinking about it -done it so many times it almost comes as an involuntary response after editing the CPU frequency scaling!
Sent from my MB865 using xda's premium carrier pigeon service