19 replies to this topic

[wallacengineering]

DISCLAIMER:

You, and ONLY YOU are responsible for any damage done to your device. This is simply a Windows computer nerd experimenting with his Android and sharing his method. In short:

I CANNOT BE HELD RESPOSIBLE FOR ANYTHING THAT GOES WRONG!

METHOD DISCOVERED THAT CAN OVERCLOCK ANY CUSTOM ROM BASED ON THE ANDROID JELLY BEAN LEAK FROM XMAS 2012!

THIS WILL NOT WORK ON THE NEW JB OFFICIAL OTA

DO NOT ATTEMPT IF YOU ARE ON THE OFFICIAL ROM!

FOR XMAS 2012 JB LEAK ONLY!!!

This method will also allow you to set your own custom Overclocking Profiles and Values!

STANDARD METHOD INSTALLED WITH MOST ROMS DOES NOT WORK BECAUSE THE MODULES WERE DESIGNED FOR ICE CREAM SANDWICH, NOT JELLY BEAN! THE MOST COMMON ISSUE IS THE RESETTING OF THE STOCK MIN/MAX FREQUENCIES UPON SCREEN-OFF OR "SLEEP"

WORKING ON:

• AVIATOR 2.0.1 (EXTENSIVELY TESTED)
• FLYING JELLY (EXTENSIVELY TESTED)
• JELLYWIZ RSL7 (EXTENSIVELY TESTED)
• ANDROID AGGRESSION (TESTING - SO FAR: WORKING)
• ECLIPSE (TESTING - SO FAR: WORKING)

WARNING:

IF YOU PLAN TO SET UP YOUR OWN OVERCLOCKING VALUES, BE VERY CAREFUL! YOU WILL HAVE TO MODIFY CPU VOLTAGES AND IF YOU DO IT INCORRECTLY YOUR CPU COULD BE PERMANANTLY DAMAGED AND YOUR DEVICE MAY NEVER WORK AGAIN!

NOW BEFORE I SAY ANYTHING, I WANT TO THANK A COUPLE HARD WORKING DEVELOPERS FOR THEIR INCREDIBLE MODS AND INFORMATION:

Please Login or Register to see this Hidden Content

- Original Overclocking Idea Base (

Please Login or Register to see this Hidden Content

)

Please Login or Register to see this Hidden Content

- His Amazing Aviator "F18" ROM, OverClock Values Base and for dealing with me as I tear up his hard work with mega-mods lol (

Please Login or Register to see this Hidden Content

)

OK, HERE WE GO:

WHAT YOU WILL NEED:

- XT912 that is updated to the Jelly Bean OTA Leak from XMas 2012, and is ROOTED

- Aviator Utility for 2.0.1 ROM (

Please Login or Register to see this Hidden Content

) [SO FAR ITS WORKED ON ALL ROMS]

- ROM Toolbox Lite (Free App - Play Store)

- SManager (Free App - Play Store)

- CPU Benchmark (Free App - Play Store)

- SetCPU (FULL EDITION REQUIRED) (PAID App - Play Store)

PROCESS:

- Disable ALL security on your device (Screen Lock, SIM Lock, ect.)

- Install ROM Toolbox Lite, SManager, CPU Benchmark, and SetCPU to your device

- Download Aviator Utility and copy it to your SD Card

- Start ROM Toolbox Lite and on the first page and scroll down just a bit and select "Scripter". From here you will want to click "Fix Permissions" and then click "Run Script".

- One ROM Toolbox is finished, you will want to click "OK" and back out to the device Home Screen, then go into your Apllication Manager ("Manage Apps" from menu above "Syetem Settings" at Home Screen)

- Find any CPU apps that may have come pre-installed on your device ("No-Frills CPU Control" is very popular) and click it. Clear its cache and Data. Then, uninstall it. If there is no uninstall button, then it is "baked" into the system, and so just clear its Cache and Data (unless you feel comfortable with removing it, there are methods of removing system apps but it is just fine sitting there).

- Go back to the Apps Browser screen and then clear the Cache and Data for both "CPU Benchmark" and "SManager" Apps

- Reboot your device and upon starting allow it to idle for 3-5 minutes to allow all it to fully load

- Connect your device VIA USB to your Windows Computer. Pull down the notification bar and change the connection mode to "Mass Storage". You can now use your computer to browse your devices' SD Card, find and copy the Aviator Utility ZIP file, and paste it onto your computer.

- Pull down the notification bar and change the connection settings to "MTP" (Media Device), then goto device Home Screen and go into "System Settings"

- Select "Security and Screen Lock", then select "Unknown Sources" and make sure the check box is checked, then back-out and goto "Developer Options" and select "USB Debugging" and "Mock Locations" and make sure both check boxes are checked

- On your computer, Extract the Aviator ZIP file, go into the extracted folder, and double-click "Aviator Utility.bat"

- Follow the onscreen instructions through the menus: "Install Overclock", "1300MHz Overclock" "Press Any Key to Reboot"

- Once your device has rebooted, disconnect it from your computer (You can run off an AC outlet to charge if you wish, but do NOT reconnect to a computer)

AT THIS POINT IT IS TIME TO DECIDE WHETHER YOU WANT A CUSTOM OVERCLOCK PROFILE OR NOT

IF YOU DO, READ ON BELOW, OTHERWISE SKIP THE NEXT SECTION (ALL THE ITEMS LISTED WITH *) AND GO STRAIGHT TO THE NEXT BIG BLUE TEXT LABLED "NOW ITS TIME TO OVERCLOCK!"

CUSTOM OVERCLOCK PROFILE

WARNING: EXPERTS ONLY

*- Open the SManager Application, click "Browse As Root" and "Do Not Ask Me Again" and then click "OK"

*- Click the pointing-up aarow in the top-left hand corner until it shows that you are at just "/" (root directory), then navigate through the folders as follows (Each "/" represents that you have clicked that folder and gone into the next level): /system/ect/init.d

*- Click "Modules" and you should see a pop-up. Click "SU", "Boot", and then click "Edit".

*- Another pop-up should appear. Click "Open Directly", then click "SM Editor"

You should get this information EXACTLY:

!/system/bin/sh
#
#--------------------------------------------------------------------


# Load Modules
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/cpufreq_interactiveX.ko
insmod /system/lib/modules/cpufreq_hotplugX.ko
insmod /system/lib/modules/cpufreq_smartass2.ko
insmod /system/lib/modules/cpufreq_pegasusq.ko
insmod /system/lib/modules/cpufreq_boostedASS2.ko
insmod /system/lib/modules/cpu_control.ko
insmod /system/lib/modules/sio-iosched.ko
insmod /system/lib/modules/overclock.ko
echo "hotplug" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "hotplug" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo "sio" > /sys/block/mmcblk0/queue/scheduler
#OC Values
echo 0 300 1015 > /proc/cpu_control/tweak_cpu;
echo 1 615 1195 > /proc/cpu_control/tweak_cpu;
echo 2 850 1325 > /proc/cpu_control/tweak_cpu;
echo 3 1100 1395 > /proc/cpu_control/tweak_cpu;
echo 4 1300 1410 > /proc/cpu_control/tweak_cpu;

*- I like the default values exept for one thing, I like lowering the Min clock just a bit so in sleep my battery lasts even longer, then the second-state clock for a smoother transistion! To do this, take the Min Frequency line ("echo 0" line) and change the number "300" to 250 and the number "1015" to 1000 (The number "300" represents the frequency in MHz, and the number "1015" is the CPU Voltage in MilliVolts [mV]). Then, take the second-state line ("echo 1" line) and change the number "615" to 600 and the number "1195" to 1190.

Feel free to select your own settings accordingly, but remember to change the voltages with the frequencies as appropriate. I have NOT found a frequency chart for the Razr and so I just guessed and it seems to be stable.

*- After you are satisfied with your modifications, Press the Floppy Disc in the Top-Right hand corner of the screen to save the changes, then click the file again, make sure "SU" and "Boot" are highlighted, click "Run"; and ignore any errors you are presented with.

(CONTINUED IN POST # 2)

[wallacengineering]

*I would advise against going above a Max Clock of 1350MHz to avoid extreme overheating or below a Minimum Clock of 225MHz to avoid laggy unresponsiveness and random crash-reboots due to low voltage

*I personally enjoy the 250 min and 1300 max because it is undervolted enough to yeild amazing battery life but overclocked just enough to get blazing-fast performance, and my device gets warm while gaming but not enough to cause any sort of concern.

NOW IT IS TIME TO OVERCLOCK!

(If you skipped the Custom Profile section, note that the stock overclock profile is set to 300MHz Min, 1300MHz Max)

- Reboot your phone twice without running any apps to ensure the file settings were set correctly, allow the device 3-5 minutes to "settle and load" after each reboot.

- Go into "SetCPU", set your Min/Max, and click "Apply on Boot", then at the top, click the "Profiles" Tab and click the small plus symbol at the Top-Right corner of the screen. Then click the small Plus symbol next to "Turn this profile on when..." and select "Screen On/Off and press the button till the light is on and it says "On", then click "OK"

(This is what corrects the Jelly bean ROM overclocking issue as SetCPU will force-apply the settings on every Screen-On)

*- If you created a custom profile with a minimum Clock under 300MHz, you will need to create an additional profile or modify the existing one for screen-OFF as well. This is because the values reset to stock 300 min, 1200 max on screen-off if this method is not applied!

- At the bottom-left corner of the screen underneath your new profile, you will find a small check box next to "Enable Profiles". Click it and make sure it is checked.

- Press HOME and then reboot your phone

CONGRADULATIONS, YOU ARE NOW TRULY OVERCLOCKED ON THE JB LEAK!

[Memnoch73]

Just some clarification here... There are currently no Roms working on the JB soak which will become the OTA. This is for the Xmas leak correct??? Can you change some of your wording as using OTA is going to be confusing for some?? At least until some roms come out for the Soak and you can test this.

Thanks

[wallacengineering]

Just some clarification here... There are currently no Roms working on the JB soak which will become the OTA. This is for the Xmas leak correct??? Can you change some of your wording as using OTA is going to be confusing for some?? At least until some roms come out for the Soak and you can test this.

Thanks

Yes if you read the frist few lines in the OP you will find it explains that this is NOT for the Soak. This is for the JB leak released at XMas.

Also, it is true that no ROMs are working on the Soak as of yet. This is because the Kernel was patched and updated and so will require fresh thinking and fresh ROMs build completely from scratch. I would estimate a few weeks wait on this.

[ZKK007]

Looks good!

[wallacengineering]

Just some clarification here... There are currently no Roms working on the JB soak which will become the OTA. This is for the Xmas leak correct??? Can you change some of your wording as using OTA is going to be confusing for some?? At least until some roms come out for the Soak and you can test this.

Thanks

Editing my OP and Title now

[wallacengineering]

Looks good!

Thanks!

It looks like now we know how to modify the existing ICS Kernel-Based Modules to run on Jelly Bean correctly. All we would need to do is program a fix in for the sleep on/off and then enable auto-run everytime to associate it with the modules file.

Only problem is my expertise does not go that far! lol I wish I was as awesome as you Developer guys!

Do you think once we all get the Soak Test as an OTA, that whirleyes will be able to update the module for us?

[ZKK007]

Thanks!

It looks like now we know how to modify the existing ICS Kernel-Based Modules to run on Jelly Bean correctly. All we would need to do is program a fix in for the sleep on/off and then enable auto-run everytime to associate it with the modules file.

Only problem is my expertise does not go that far! lol I wish I was as awesome as you Developer guys!

Do you think once we all get the Soak Test as an OTA, that whirleyes will be able to update the module for us?

I'm not sure. I remember reading that whirleyes stopped development on the Razr so probably not from him. It's above me too so sorry I can't be of any help there!

[razzrmaxx]

Man I appreciate this post really... it should be added to the book of revelations lol j/k

[ZKK007]

I just wanted to mention NOT to try and use any of the modules on the latest .16 official JB release. There are a few modules ( including cpu_control.ko) that will restart your device. I believe you need cpu_control.ko module in order to overclock.

In my experience I wasn't even able to get past the Safe Strap screen. The modules from Whirleyes (Which many people use and some Devs use for their ROMs) need to be updated to the latest kernel. I am unsure when this will happen, but you can keep an eye on Whirleyes thread here:

Please Login or Register to see this Hidden Content

Some of the modules for the governors may still work (I know HotplugX wasn't working), but I just wanted to let everyone know to proceed with caution

[wallacengineering]

I just wanted to mention NOT to try and use any of the modules on the latest .16 official JB release. There are a few modules ( including cpu_control.ko) that will restart your device. I believe you need cpu_control.ko module in order to overclock.

In my experience I wasn't even able to get past the Safe Strap screen. The modules from Whirleyes (Which many people use and some Devs use for their ROMs) need to be updated to the latest kernel. I am unsure when this will happen, but you can keep an eye on Whirleyes thread here:

Please Login or Register to see this Hidden Content

Some of the modules for the governors may still work (I know HotplugX wasn't working), but I just wanted to let everyone know to proceed with caution

HE IS ABSOLUTELY RIGHT ^^^^^^^^^^^^^^^^^^^^ BE SURE TO READ HIS WARNING AND OP THOROUGHLY. THIS METHOD DOES NOT WORK ON THE OFFICIAL OTA! YOU WILL BOOTLOOP OR BRICK YOUR PHONE!!!

ALSO, THAT IS VERY BAD BECAUSE I DO NOT THINK THERE IS AN UNBRICK UTILITY FOR THE OFFICIAL OTA YET!!!

THIS MEANS THAT IF YOU ARE ON THE OFFICIAL OTA AND YOU BOOTLOOP OR BRICK, GAME OVER, YOU ARE SCREWED!

Thanks for the reminder ZK, updating OP now...

[razzrmaxx]

HE IS ABSOLUTELY RIGHT ^^^^^^^^^^^^^^^^^^^^ BE SURE TO READ HIS WARNING AND OP THOROUGHLY. THIS METHOD DOES NOT WORK ON THE OFFICIAL OTA! YOU WILL BOOTLOOP OR BRICK YOUR PHONE!!!

ALSO, THAT IS VERY BAD BECAUSE I DO NOT THINK THERE IS AN UNBRICK UTILITY FOR THE OFFICIAL OTA YET!!!

THIS MEANS THAT IF YOU ARE ON THE OFFICIAL OTA AND YOU BOOTLOOP OR BRICK, GAME OVER, YOU ARE SCREWED!

Thanks for the reminder ZK, updating OP now...

Nevermind! It should be added to the book The apocalypsis lol
Sent from my DROID RAZR HD using Tapatalk 2

[Kebob]

One thing that I would change here is forget all of the script manager junk and just use init.d. Its much cleaner and saves a lot of time, also it starts in the boot up of the device so you don't need to wait for the script manager app. If you need help with this let me know, I can probably make a utility to do this.

[ZKK007]

Just wanted to mention dtrial has updated the modules for JB .16.

Please Login or Register to see this Hidden Content

I'm working on putting the required overclocking modules and scripts in the Aviator Utility.

Please Login or Register to see this Hidden Content

, I'm sure you will be keen to test these and get it running

[ZKK007]

Just letting you know I am uploading the Aviator Utility now. I have included instructions in the utility since it seems that the screen off=reset freq values is still happening. So your method (smanger and setcpu) are the known way at the moment. There are a few threads on here so perhaps someone else figures out an easy way

[wallacengineering]

Just letting you know I am uploading the Aviator Utility now. I have included instructions in the utility since it seems that the screen off=reset freq values is still happening. So your method (smanger and setcpu) are the known way at the moment. There are a few threads on here so perhaps someone else figures out an easy way

Thanks for filling me in, I will get to testing as soon as I can! Thanks a lot ZK! I will update OP and title once I have tested this on a few .16 ROMs

[ZKK007]

Thanks for filling me in, I will get to testing as soon as I can! Thanks a lot ZK! I will update OP and title once I have tested this on a few .16 ROMs

BTW, since I included the modules (thanks to East2West) it should eb able to work on any .16 rom

[ZKK007]

So I've been messing around with underclocking a little bit and I've got a question to ask. I lowered the bottom value to 250mHz and lowered the voltage. When I looked at CPU spy it showed that the phone would use the 600mHz bracket and not really go lower, other than deep sleep. The 300mHz bracket was barely used. The same results were also shown in setCPU app.

Do you think that the CPU apps weren't showing the 300mHz frequency bracket because I changed it to non standard 250mHz?

Once I changed the init.d script back to 300mHz and rebooted, the 300mHz bracket in the CPU apps was showing normal usage (the majority of total time). I just wanted to know if anyone knew if in this case the CPU apps are not worth looking at due to non standard values? Thanks!

[garywojdan81]

So I've been messing around with underclocking a little bit and I've got a question to ask. I lowered the bottom value to 250mHz and lowered the voltage. When I looked at CPU spy it showed that the phone would use the 600mHz bracket and not really go lower, other than deep sleep. The 300mHz bracket was barely used. The same results were also shown in setCPU app.

Do you think that the CPU apps weren't showing the 300mHz frequency bracket because I changed it to non standard 250mHz?

Once I changed the init.d script back to 300mHz and rebooted, the 300mHz bracket in the CPU apps was showing normal usage (the majority of total time). I just wanted to know if anyone knew if in this case the CPU apps are not worth looking at due to non standard values? Thanks!

If your using the stock kernel or the kexec kernel, they only have the 5 slots & I think they're hard-coded in. So I don't think it'll recognize much variation from the hybrid modules & init.d scripts. That's why the values don't stick well w/o using something like setCPU to run an active profile.

Sent from my XT912 using Tapatalk 2

[twtaylor369]

This is absolutely awesome. Wish I had looked for this sooner. My RAZR runs so much better. Thanks for the hard work and great instructions!

Sent from my Motorola Galaxy s3 using Tapatalk 2