Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*If you find this Guide Thread helpful, feel free to hit the "thanks" button below!
I know there are several posts that have been made regarding the overclocking method(s) for the ATRIX 2 both on this forum, as well as some others, however; many of these posts are somewhat old, and I am just providing a guide thread here on XDA since most of the original threads were still beta at the time. This being the case, I take no credit for the instructions I will outline below, but will credit those who deserve to be credited for their efforts they have made in getting these methods to work stably. I am simply compiling some information that users may find helpful in the overclocking process. This is specifically geared toward ATRIX 2 owners who want to have a working knowledge of overclocking and how to accomplish this. If I have missed anything, or if the information is either A) outdated, or B) there is another "newer" more approved method in achieving overclock WITHOUT init.d support, please let me know and I will update the OP...
*Make sure you have a backup in place before attempting any of the following steps, and PLEASE understand how to flash the FXZ file to return to stock if you run into any surprises -though, if you follow the instructions exactly, I would be surprised if you would find the need to do so...
First & Foremost:
*DISCLAIMER: I cannot be held responsible for any and all damage related to Hardware loss or data or Software, which the user might cause while overclocking there device. Additionally, I am taking the liberty to assume that anyone who attempts to Overclock their device understands the risks involved. Such risks include, but aren’t limited to: failure of hardware, voiding warranties, and data corruption. While many users enjoy overclocking their own devices, they should do so knowing such risks involved.
*CPU overclocking is something that you should fully understand BEFORE attempting! Remember that the ultimate goal is speed with stability. Extreme clock speeds are merely academic exercises if the overclocked system can't run your device's operating system and/or applications reliably.
*Please note that the guide thread is based on a more generalized approach to give best results for the majority of users; just because someone's CPU processor runs at 1.25 GHz (or even higher) DOES NOT ENSURE that yours will!
CPU Overclocking Overview:
What Is "CPU"?
The term "CPU" is an abbreviation for Central Processor Unit. Essentially, the CPU is the brains of your device's system. It is the internal component which carries out the instructions of a program by performing the basic arithmetical, logical, and input/output operations of the system. Your Android's CPU is responsible for handling all instructions it receives from hardware components and applications running on your device. The CPU performs operations on data held in the computer memory -the RAM. The CPU relies on an "Operating system" (Android OS) for input and output of data, interaction with the user and for storing information.
What Is CPU Overclocking?
If you think overclocking sounds like an ominous term, you may have the right idea. Basically overclocking means to run a microprocessor faster than the clock speed for which it has been tested and approved. Overclocking is a popular technique for getting a little performance boost from your system, without making any changes to the actual device's hardware. Because of the performance boost found in overclocking, it seems to be something desired by users who demand more from their device, such as heavy gamers, and may perhaps be even somewhat of a novelty for those that really don't need such performance increases. All CPUs have a fundamental clock rate, from which all of the other clock rates inside the CPU are derived. Various sections of the processor take this fundamental clock rate, which acts as a kind of standard timekeeper, and multiply it to get an internal clock speed for a particular section of the CPU. In conjunction with overclocking, the CPU core voltage (VSel or uVolt as it may be referred to) is sometimes raised above the default setting to stabilize an overclocked CPU.
What Is "Clock Speed"?
Clock speed: Given in megahertz (MHz) or in gigahertz (GHz), the clock speed determines how many instructions per second the processor can execute. The higher the value, the more powerful the CPU. In overclocking your device's CPU, you must be somewhat familiar with it's hardware, and it is always a procedure conducted at your own risk. When overclocking there are some problems and issues you'll have to deal with, such as excessive heat, random reboots, and/or operating system freezes. Even though your device's CPU can be overclocked, it doesn't mean your RAM modules will stably support some of the higher CPU clock speeds that others have seen.
What Are The Risks Involved?
Overclocking comes with many risks, such as overheating, random system rebooting, and system freezing, so you should become familiar with all the pros and cons before you attempt it. Additionally, overclocking isn't supported by some of the Android Operating System kernels (ICS/JB -at least not as of yet) which means overclocking your CPU may not work on all Android versions -and will obviously void your warranty and leave you with an inoperable CPU if you overclock too high and damage the CPU in the process. Overclocking may also decrease the lifespan of the CPU, cause failure in critical components and may even result in some data corruption, as well as an increase in unexplainable crashes and freezes, as previously mentioned.
VSel & uVolt (Undervolting) Overview:
What Is Undervolting?
Undervolting is the practice of modding an Android device to run at a lower voltage than the stock settings. The idea behind kernel undervolting is to reduce that stock voltage to the bare minimum required to run the phone at factory settings. The main battery saver is a low VSel1 (the lowest voltage at the lowest speed), because your phone runs at this speed most of the time. Underclocking VSel1 is not a good idea, because below the default 300 MHz it takes noticeably longer before your phone responds to an incoming call in standby mode. Reducing VSel1 too much makes your phone hang or reboot when it's idle, but you can reduce VSel1 within reason to increase standby time. If you cut VSel1 from 33 to 20 the processor uses 40% less power most of the time, which can make the difference between your phone lasting a full day or blacking out before you get a chance to plug it in. (There are more ways to stretch your battery without "dumbing" down your smartphone)
Lowering the intermediate voltage at medium speed (600 MHz by default) saves a bit of juice when you're playing with your phone a lot, because VSel2 is the typical setting when you're using your phone. If you use your phone as an mp3 player on a long trip you may notice the difference. Your phone rarely runs, or should rarely, at top speed. It spikes at VSel3 occasionally, but even with QueueTube streaming, Wi-Fi Ruler scanning, GPS Status looking for satellites, and Dolphin HD loading pages in the background my processor spent most of the time at 600 MHz instead of the default maximum (800 MHz) or my custom 1.25 GHz CPU frequency scaling.
What are the "Pros" Regarding Undervolting?
The pros, as mentioned before, are increased battery life and cooler temperatures. It should be noted at this juncture that there is controversy regarding whether or not undervolting truly provides increased battery life; there are those that believe it makes no difference, and unfortunately much of the evidence is circumstantial or based on hearsay, since usage patterns, rogue apps, and any number of other factors can contribute to a perceived difference in battery drain or conservation. Undervolting can help battery life, up to a point, although once the voltage drops below a certain threshold, the battery life actually suffers due to errors caused by the baseband radio not getting enough power. Suffice it to say, it is possible to safely take it to mean that undervolting does in fact provide better battery life than stock settings.
What Are The "Cons" Regarding Undervolting?
On the flip side, undervolting has its pitfalls. Undervolting a phone too much can cause serious errors to appear as the power-starved processor starts to error out. The radio from above is a perfect example, but there have also been numerous other errors that result from extreme undervolting. These errors can range from random reboots to the phone locking up when the WiFi is turned on, and quite often there is no indication that the undervolting is the cause. The very worst case scenario for undervolting your Android device is that you may in fact "soft brick" the phone; the lack of voltage during boot could conceivably corrupt the phone’s firmware, leaving the phone unusable.
[GUIDE] Comprehensive Guide To Overclocking The ATRIX 2 (ICS 4.0.4 ONLY)
Modules :
Filesystem
ntfs.ko (read/write support)
cifs.ko (with extra attributes)
Kernel hacking
symsearch.ko (Unexported symbol finder by Skrilax_CZ)
CPU scaling governor (back ported from other dev)
cpufreq_interactiveX.ko [@] (interactiveX V2 governor by imoseyon)
early suspend support and hotplugging
cpufreq_hotplugX.ko [@] (hotplugX governor by imoseyon)
early suspend support and tweaks
cpufreq_smartass2.ko [@] (SmartassV2 governor by erasmux)
cpufreq_pegasusq.ko [@] (Samsung multi-core governor)
based on modification done by Gokhanmoral
cpufreq_boostedASSv2.ko [@] (a modified smartassv2 governor)
ported from BMc08GT
CPU/GPU frequency control
cpu-control.ko [@] (Tweak CPU frequency & voltage to your like)
my 1st kernel module. based on milestone overclock & opptimizer.
I/O scheduler
sio-iosched.ko (Simple IO scheduler by waninkoko)
based on Noop, Deadline and V(R) IO schedulers. In android world, simple is better
modules with [@] mark requires symsearch.ko to operate
Disclaimer : I don't write all of these modules. Only make a few changes/tweak for it to work on our device. Enjoy!
Kernel version : 3.0.8
Kernel source : 67.42.17.XT910S.SKT.en.KR
Compiler setup : CodeSourcerey arm-2012.03-56-arm-none-eabi (-O2 optimization)
Build revision : Project Lense build
Change logs:
0.1.1
- Add Simple I/O scheduler.
0.1.2
- Recompile with -O2 flag. I notice some instability when using -O3 flag
- Tweaked sio scheduler
- Add tweaked pegasusq governor.
0.1.3
- Add cpu overclock/underclock module
- Add boostedASSv2 governor
**For best practices, only load module when it's needed. That would save some kernel memory.
Source code :
ttps://github.com/whirleyes/extra_kernel_module
Download link :
extra_kernel_modules_0.1.3.zip - contains all the modules
init.d_n_governor_installer_0.1.3.zip - optional. init.d installer (load all modules to memory on startup).
Update : Add a preview of Tweakerz app.
- Include all kernel module. Module are loaded from app storage.(no install /alter system partition.)
- Load/unload kernel module on-the-fly (No save setting or set on boot option)
- Set CPU voltage/freq via GUI (No persist option yet)
Easy Install method: (For init.d)
Reboot to recovery
Install extra_kernel_modules_0.1.zip
Install init.d_n_governor_installer.zip (Thanks to core720)
Install guide for adding init.d script via Script Manager - SManager app
1.Extract all *.ko files from extra_kernel_modules_0.1.2.zip to /system/lib/modules
2.Open Script Manager, Create new script / modify existing script
Code:
#!/system/bin/sh
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/sio-iosched.ko
3.Save to /system/etc/init.d/
Q: How to load a cpufreq governor
1.Load symsearch.ko
2.Load your choice of governor
3.Enable it
Code:
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/cpufreq_interactiveX.ko
echo interactivex > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Q: What is the best cpu-freq governor
Maybe this will help you choose/tweak
CPU Governors explained
Pegasusq Governor
Q: How to load cpu frequency/voltage (underclock/overclock)
1.Load symsearch.ko
2.Load cpu_control.ko
Code:
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/cpu_control.ko
Q: How to change cpu frequency & voltage
echo id frequency(Mhz) voltage(mV) > /proc/cpu_control/tweak_cpu
Example:
Code:
echo 0 196 980 > /proc/cpu_control/tweak_cpu
echo 1 500 1195 > /proc/cpu_control/tweak_cpu
echo 2 750 1320 > /proc/cpu_control/tweak_cpu
echo 3 1000 1388 > /proc/cpu_control/tweak_cpu
echo 4 1350 1410 > /proc/cpu_control/tweak_cpu
ICS kernel default voltage&frequency table
Code:
Id Freq Volt(mV)
0 300 1025
1 600 1200
2 800 1325
3 1000 1388
4 1200 1398
GB kernel default voltage&frequency table
Code:
Id Freq Volt(mV)
0 300 1025
1 600 1200
2 800 1313
3 1000 1374
4 1200 1375
** voltage min : 830mV, max : 1410mV
More/Details about cpu_control.ko module
To view ICS default frequency-voltage table
Code:
cat /proc/cpu_control/opp_table_default
To view current frequency-voltage table
Code:
cat /proc/cpu_control/opp_table_current
To view current CPU & GPU frequency
Code:
cat /proc/cpu_control/frequency_current
[GUIDE] Comprehensive Guide To Overclocking The ATRIX 2 (2.3.6)
PREREQUISITES:
A Rooted ATRIX 2: (for obvious reasons) Check THIS THREAD as well as THE BEGINNER'S GUIDE for references and instruction for rooting your device.
Clockworkmod Recovery (CWM): You can find the installation procedure for this in THE BEGINNER'S GUIDE as well.
If your ROM does not support init.d: download the mo_simp_1.5_edison-signed.zip and flash in CWM Recovery.
Root Explorer: This application will allow you access to the init.d folder to edit your echo table values. You can find this application HERE.
SetCPU: This application will provide verification of your CPU overclocking settings. You can find this application HERE.
Terminal Emulator: You can find this application HERE.
Instructions For Users WITHOUT init.d Support Already Running (Stock/Rooted 2.3.6. etc):
1) Download the latest mo_simp_1.5.x_YOUR_DEVICE.zip
2) Move the mo_simp_1.5.x_YOUR_DEVICE.zip to the root of your SD card
3) Flash in Clockwork Recovery
Optional for Motorola Devices:
4) If your ROM does not have init.d support, download this file and flash from CWM Recovery: moto_init_d-signed.zip
5) Reboot your ATRIX 2 after you have flashed the mo_simp_1.5.x_YOUR_DEVICE.zip and/or moto_init_d-signed.zip
*Note, this will remove any old kernel modules, or init.d script you may have. Backup your old init.d script before flashing -if any!
Basic Usage:
*These are the basic terminal commands, to be entered as Root or "su". The Milestone Overclock interface exists as four individual files located at /proc/overclock/*
6) Switch to "SuperUser" (NOTE: All commands must be done as SuperUser. Switch from the "$" symbol that you will see when you first open the Terminal Emulator to the "#" symbol simply by typing in "su" -without the quotation marks!):
What you will see when you open Terminal Emulator initially:
Code:
[email protected]:/$ export PATH=/data/local/bin:$PATH
[email protected]:/$
What you should see AFTER typing in "su" (without quotation marks):
Code:
[email protected]:/$ export PATH=/data/local/bin:$PATH
[email protected]:/$ su
[email protected]:/#
7) Next, type this command in Terminal Emulator: cat /proc/overclock/*
Code:
cat /proc/overclock/*
Below is what you should see in Terminal Emulator after entering: cat /proc/overclock/*
Code:
[email protected]:/$ export PATH=/data/local/bin:$PATH
[email protected]:/$ su
[email protected]:/# cat /proc/overclock/*
//RAZR Stock
freq_table[0] index=0 frequency=300000
freq_table[1] index=1 frequency=600000
freq_table[2] index=2 frequency=800000
freq_table[3] index=3 frequency=1000000
freq_table[4] index=4 frequency=1200000
cpumin=300000 cpumax=1200000 min=300000 max=1200000 usermin=300000 usermax=1200000
clk_get_rate=300000
mpu_opps[5] rate=1200000000 opp_id=5 vsel=61 u_volt=1375000
mpu_opps[4] rate=1000000000 opp_id=4 vsel=61 u_volt=1374000
mpu_opps[3] rate=800000000 opp_id=3 vsel=55 u_volt=1313000
mpu_opps[2] rate=600000000 opp_id=2 vsel=43 u_volt=1200000
mpu_opps[1] rate=300000000 opp_id=1 vsel=26 u_volt=1025000
1.5-mapphone-yokohama
//Droid3, Bionic, Atrix2 Stock
freq_table[0] index=0 frequency=300000
freq_table[1] index=1 frequency=600000
freq_table[2] index=2 frequency=800000
freq_table[3] index=3 frequency=1000000
cpumin=300000 cpumax=1000000 min=300000 max=1000000 usermin=300000 usermax=1000000
clk_get_rate=300000
mpu_opps[3] rate=1000000000 opp_id=3 vsel=61 u_volt=1375000
mpu_opps[2] rate=800000000 opp_id=2 vsel=55 u_volt=1313000
mpu_opps[1] rate=600000000 opp_id=1 vsel=43 u_volt=1200000
mpu_opps[0] rate=300000000 opp_id=0 vsel=26 u_volt=1025000
1.5-mapphone-yokohama
8) Read all current settings: (useful for verifying that the frequency table and opp tables match)
9) Next, read just mpu_opps info for the Droid 3, Bionic, and ATRIX 2 Stock:
Code:
[COLOR="DarkOrange"]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[/COLOR]
10) Write the new frequency & voltage: (Format: echo /proc/overclock/mpu_opps)
*Note: Change only the top frequency/voltage on ATRIX 2 by typing in the full code line "echo 3 1125000000 1375000 > /proc/overclock/mpu_opps" (without quotation marks)
Code:
echo 3 1125000000 1375000 > /proc/overclock/mpu_opps
11) To verify the changes made to echo 3, type in "cat /proc/overclock/mpu_opps" (without quotation marks)
Code:
[email protected]:/# cat/proc/overclock/*
echo 3 1125000000 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
*Note: Voltage can be set as a VSEL or uV value. Max VSEL for most Motorola devices is 63.
Code:
# insmod /system/lib/modules/symsearch.ko
# insmod /system/lib/modules/overclock.ko
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. By 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.
11) Reboot after making changes.
12) Open SetCPU to confirm whether your CPU echo values stuck through rebooting. Also, make sure that the "Set On Boot" box is left un-ticked, so as to not have the changed CPU clock speed set upon reboot, and to further test to make sure you are able to run higher CPU clock speeds.
Instructions For Users WITH init.d Support Already Running (Custom ROM WITH init.d Built-In):
1) Open Root Explorer, and navigate to: system>etc>init.d>00pptimize (See Explanatory Images Below)
2) Next, open the 00pptimize file and open using Text Editor (See Explanatory Image Below)
3) Then, after opening the 00pptimize file using text editor, scroll down until you see the section of code highlighted in red below:
4) Make sure your permissions are set to "R/W" instead of "R/O" in Root Explorer!
Code:
# RAZR stock Settings
# echo 5 1200000000 1375000 > /proc/overclock/mpu_opps
# echo 4 1000000000 1374000 > /proc/overclock/mpu_opps
# echo 3 800000000 1313000 > /proc/overclock/mpu_opps
# echo 2 600000000 1200000 > /proc/overclock/mpu_opps
# echo 1 300000000 1025000 > /proc/overclock/mpu_opps
[COLOR="Red"]# 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
# LG Thrill 4G/Optimus 3D Froyo stock Settings[/COLOR]
# echo 3 1008000000 1350000 > /proc/overclock/mpu_opps
# echo 2 800000000 1260000 > /proc/overclock/mpu_opps
# echo 1 600000000 1100000 > /proc/overclock/mpu_opps
# echo 0 300000000 930000 > /proc/overclock/mpu_opps
5) Now, using the Text Editor in Root Explorer, change the echo 3 table value from "echo 3 1000000000 1375000 > /proc/overclock/mpu_opps" to something like: "echo 3 1100000000 1375000 > /proc/overclock/mpu_opps" (without the quotation marks)
6) Next, click the "back" button.
7) Root Explorer will ask you to save changes. A window will show after you have made changes, and will say:
Warning
You have made changes to this file.
Do you want to save these changes before exiting?
Click "Yes" to save. The newly made changes will be saved to a file that will be called "00pptimize.bak".
8) Now, find and delete the "00pptimize.bak" file created after you made your changes by long pressing this file and choosing the "Delete" option.
9) Finally, exit out of Root Explorer and reboot your device.
10) Once you have rebooted, open SetCPU and you should see your CPU frequency scaling value you changed from 1000000000 to 1100000000, or check the settings by using Terminal Emulator and typing "cat /proc/overclock/*" -what you should see is a clock speed that was 1GHz and is now 1.1GHz. Also, leave the "Set On Boot" box un-ticked until you have fully tested the new CPU clock speeds and are certain they are at a stable frequency.
11) You can continue this process using small incremental jumps from 1.1GHz to 1.12GHz, to 1.14GHz, to 1.16GHz, etc. until you find a your highest stable running CPU clock speed.
*I have been able to slowly work my way up to run my CPU at 1.25GHz stably, but you may find that your device can either handle more or less clock speed. Again, handle with care, and patience in achieving your highest stable clock speed is something you need to take into consideration throughout this entire process!
UNDERVOLTING GUIDE: Updated: 08/09/2012
Please Reference THIS THREAD For Loading/Changing CPU Voltages.
Credit Goes To:
whirleyes
CPU GOVERNOR SETTING EXPLANATION: Updated: 08/09/2012
Please Reference THIS THREAD For CPU Governors Explained.
Credits goes to:
http://icrontic.com/discussion/95140...m-tuner-tegrak
http://forum.xda-developers.com/show....php?t=1369817
*I recommend that after you make changes to the clock speed, you run your device for 5-10 minutes. Open applications, play a quick game, browse the web, etc. to make sure that your device can handle the new clock speeds before making any further increases to the CPU.
**You can also underclock in the same manner that you have used to overclock, but by changing the echo table values at echo 0 to something like "echo 0 240000000 1025000 > /proc/overclock/mpu_opps" -which is always a good idea when overclocking to give the CPU a load relief when using CPU settings like "performance". This will run your CPU at its lowest frequency scaling to 240MHz rather than at 300MHz, but again, experimentation/patience/extensive testing is a must!
Credits: tekehuna,cogeary, JRW 28, alteredlikeness, whirleyes, 00pptimizer Project via RootzWiki, and probably more to come to credit. Please let me know if you can add to/provide more info/correct me on misinformation/or should be listed in credits also and I will update the OP!
Good one bro very useful for noobs
Sent from my MB865 using xda app-developers app
Mods, can you sticky this?
Sent from my ATRIX 2 using my toes
Fantastic! I've always said "I'll try out overclocking when I have time to do the research" but I guess now I won't have an excuse. Thanks a bunch. :good:
iarejohnsmith said:
Fantastic! I've always said "I'll try out overclocking when I have time to do the research" but I guess now I won't have an excuse. Thanks a bunch. :good:
Click to expand...
Click to collapse
Glad you found this thread useful! I know overclocking can be a bit daunting when you think about it, but it really is quite easy after a few basic commands are learned and preformed a few times. If you need any more guidance in your OC'ing, please feel free to PM me, and I'll step you through anything you might be unsure of!
Thanks for taking the time for this. Realy appreciate it. :good:
So who all did this?
I believ OCing to 1.2 Ghz wudnt cause any problems as it is the same chipset(OMAP 4430) as in Razr(1.2 Ghz Clocked)?
djabhi003 said:
Thanks for taking the time for this. Realy appreciate it. :good:
So who all did this?
I believ OCing to 1.2 Ghz wudnt cause any problems as it is the same chipset(OMAP 4430) as in Razr(1.2 Ghz Clocked)?
Click to expand...
Click to collapse
I'm clocked at 1.25GHz stable. Some have been known to hit as high as 1.3GHz. Seems as though there's nothing consistent (across the board) for all ATRIX 2's to be able to clock to. You'll just have to experiment and test at some length to find your highest possible CPU clock speed that's stable and reliable...
Sent from my MB865 using xda's premium carrier pigeon service
"9) Finally, exit out of Root Explorer and reboot your device."
This step is unnecessary as you can just run the shell script for it to take effect instantly.
I actually recommend people copying this shell script elsewhere outside of the init.d directory so it doesn't run at startup, and only copy the script back over when you've extensively tested for random reboots. Altering the startup script files and rebooting to test increases your likelyhood of bootlooping.
Note: For the atrix 2 at least, it IS possible to adb into your phone and replace, move, or remove the files in the init.d directory before they run at startup; I've had to do this to get out of a overclock-related bootloop at least twice...
IIRC, in my case it was spamming something like this in a command line while the phone booted up
Code:
adb shell "su -c "mount -o rw,remount /dev/null /system"&&"rm /system/etc/init.d/Oc3""
(may need more quotation marks lol)
It would be 00pptimize in the context of your posting (adb must be enabled in the phone development settings obviously)
moofree said:
"9) Finally, exit out of Root Explorer and reboot your device."
This step is unnecessary as you can just run the shell script for it to take effect instantly.
I actually recommend people copying this shell script elsewhere outside of the init.d directory so it doesn't run at startup, and only copy the script back over when you've extensively tested for random reboots. Altering the startup script files and rebooting to test increases your likelyhood of bootlooping.
Click to expand...
Click to collapse
This is true, and I suppose I can include a caveat in the OP to let users know.
moofree said:
Note: For the atrix 2 at least, it IS possible to adb into your phone and replace or remove the files in the init.d directory before it runs at startup; I've had to do this to get out of a overclock-related bootloop at least twice...
IIRC, in my case it was something like spamming this in a command line while the phone booted up
Code:
adb shell "su -c "rm /system/etc/init.d/Oc3""
It would be 00pptimize in the context of your posting (adb be enabled in the phone development settings obviously)
Click to expand...
Click to collapse
As far as using adb, I didn't reference any methodologies to include this, as some users may not have any knowledge/experience with using it. Again, I can look at this more closely and possibly include something in the OP that will give more instruction concerning this usage soon.
This Guide Thread is one I am going to update as newer overclocking methods and/or shortcuts are discovered and tested. I also have intent to write an undervolting section as well. I want this guide to be one specifically for the ATRIX 2 community, and further I want to maintain it to keep both accuracy and understandability as well as open for suggestion(s) -as you have made; and I thank you.
Sent from my MB865 using xda's premium carrier pigeon service
Excellent guide, will try it out tonite, any suggestions on what vsel to give on different clocks, like 300/600/1000 or 300/600/1100 ?
nikolain said:
Excellent guide, will try it out tonite.
Click to expand...
Click to collapse
Let me know (PM me) if you have any questions...
Sent from my MB865 using xda's premium carrier pigeon service
nikolain said:
Excellent guide, will try it out tonite, any suggestions on what vsel to give on different clocks, like 300/600/1000 or 300/600/1100 ?
Click to expand...
Click to collapse
Apex_Strider said:
Let me know (PM me) if you have any questions...
Sent from my MB865 using xda's premium carrier pigeon service
Click to expand...
Click to collapse
Any suggestion on Voltages ?
nikolain said:
Any suggestion on Voltages ?
Click to expand...
Click to collapse
You shouldn't try to go any higher than vSel=63 at echo 3, or you'll likely experience problems. There's other init.d files that have uVolt as well as vSel. The uVolt is a more fine tuning of voltages, but like I said you can edit the vSel at echo 3 to vSel 63 and you should be golden...
Sent from my MB865 using xda's premium carrier pigeon service
the ICS leak from searet is using 1200mhz clock speed. Isnt it high? it working well now just maybe if some expert can give me some hints.
Titankahn said:
the ICS leak from searet is using 1200mhz clock speed. Isnt it high? it working well now just maybe if some expert can give me some hints.
Click to expand...
Click to collapse
I am not on the leaked ICS AT&T version, so I really can't answer to this. What exactly are you wondering about? I know there's been some question as to why some ICS leaks have users clocked to 1.2GHZ and others at the stock 1GHz. That been sort of a mystery. Further, since I've not flashed the leak to be able to test higher click speeds myself (curious as to what the maximum stable clock speed might be with ICS) so I just have no insight. Yet...
Sent from my Atari Falcon030
Hey Apex, quick question,
Every time I try to underclock echo0, to say, 240mhz, I'll reboot and SetCPU says its UC'd, but phone won't fall below echo1 value at idle, in this case 600mhz. If I reset echo0 too 300mhz, its fine. And it doesn't matter what the GPU is set, still the same. Maybe voltage change is warranted?
Sent from my ATRIX 2 sill on GB
captaincado said:
Hey Apex, quick question,
Every time I try to underclock echo0, to say, 240mhz, I'll reboot and SetCPU says its UC'd, but phone won't fall below echo1 value at idle, in this case 600mhz. If I reset echo0 too 300mhz, its fine. And it doesn't matter what the GPU is set, still the same. Maybe voltage change is warranted?
Sent from my ATRIX 2 sill on GB
Click to expand...
Click to collapse
What rom are you running, or are you rooted/stock? Since I'm running Lithium v1.3.1 it (obviously) has the 00pptimize folder with all the code needed to over/underclock in the 00pptimize from unit.d folder. I've underclocked to 220MHz at echo table 0 with no voltage changes, and have seen no ill-effects as result. How are you modifying the echo tables, Terminal Emulator or Root Explorer?
Sent from my Atari Falcon030
I'm on lithium 1.3.1, using root explorer, but, this happens on any rom. I've been changing values in OC3, instead of uncommenting in 00optimize.
Om a side note, I can OC to 1335mhz, 48 hour stable.
Sent from my ATRIX 2 still on GB
Remember to have the screen turned ON while you apply the script!!!
Hi guys!
Today i want to share with you a script i specifically tailored for our 4C, to decrease high battery drain just by tuning parameters of the interactive governor.
As many of you know, on the Nexus 5X forum there is a huge post about different profiles created to achieve the same purpose, and almost all of them works with our device (personally tested)
[GUIDE] Advanced Interactive Governor Tweaks; Buttery smooth and insane battery life!
I raccomed to read it!
One of them in particular was extremely good battery wise but i felt some lagginess here and there (talkin about HawkTail 1.2)
So i decided to make a script myself and share it with you, the idea behind it is to force the CPU to scale better with loads and making the Big cores in use more frequently by tuning some of the kernel parameters.
Plus we will have the GPU idling @ 180MhZ instead of 300MhZ (like in the Nexus 5x) and a switch to noop scheduler.
Performance wise and taking in example the latest stable ROM from Xiaomi.eu (8.0.5) we will have a decrease of about 5k point in Antutu (I'll attach two screenshots, the 71K was the result without tweaking, plus just by switching back to CFQ scheduler you'll get 2K points back but NOOP is more battery friendly)
So here you go, this is my script TAO.
Using it is pretty simple and you have a couple of options: [ROOT IS NEEDED]
Since it's a script, if your rom have INIT.D folder support, you can just move the file under /etc/Init.d and reboot the device. The script will make a log file under /sdcard/TAO.log that you can check if anything went wrong.
The second option, if your rom doesn't have Init.d folder support, just use Kernel Auditor and a text editor.
Open the downloaded file in a text editor, select all and copy the text.
Then open Kernel Auditor, and in the menu look for init.d, enable the "Emulate Init.d" and then click the "+" symbol. It will ask to add a name (let's set it to TAO for coherence), then OK. It will open a new window where we have to paste all the text previously copied, save it by pressing the icon on the top right. Now we can just reboot the device or click the newly created item and select execute.
Third option is to run it manually from terminal.
Plus, i'll add my Thermal-engine-8992.conf that you guys can use to change the thermal throttling values. Download it and replace it in /system/etc/ , set it with permission 644 and reboot.
This modded thermal will move up the limits, long story short, your device will continue to perform even if it gets hot.
Enjoy! & report back for feedback
Remember to have the screen turned ON while you apply the script!!!
P.S.
Files are zipped, extract them!!!
UPDATE
Minor update - use_sched_load set to 0 for both cores
Correction made for the log file
UPDATE 0.7
Since @solis_f is having some problem with the big cores, and this could be a common problem to many others too i've decided to add something in the script that will force the big core online so you should not have any more problem executing the script. Let me know
UPDATE 0.8 - Experimental
Updated Target_loads for both Little and Big cores.
Little core min freq. to 384 MhZ.
Input boost @ 787 MhZ instead of 600 MhZ.
hispeed_load disabled for both cores.
Updated values for UpMigrate.
Enabled core_ctl for big cluster:
With this update, you'll have your big cores Offline most of the time, but they will comes online when needed.
Yours perfd (/data/system/perfd/default_values) with this version have to look like this:
Code:
ihf;787200
iahd;38000
ighl;200
itl;39 460800:5 600000:62 672000:10 787200:81 864000:90 960000:99
gpu_default_pwrlvl;5
sst;33
smil;20
sminr;3
sitl;65
sum;66
sdm;54
cbmf;1525
cbhdr;90
cbhip;16
ihf0;787200
iahd0;38000
itl0;39 460800:5 600000:62 672000:10 787200:81 864000:90 960000:99
imst0;0
ighl0;200
imf0;0
itr0;30000
its0;-1
iiib0;1
intb0;0
ibd0;0
ihf4;1248000
iahd4;38000
itl4;53 768000:64 864000:72 960000:79 1248000:99
imst4;0
ighl4;200
imf4;20000
itr4;30000
its4;-1
iiib4;1
intb4;0
ibd4;0
P.P.S.
Over two hundred downloads, but not even half of you gives me feedback...
UPDATE 0.9
Sorry for the delay, many things to do IRL.
This version is what i'm using now, should be smoother then v0.8, hope you like it.
nice one, will try this
Did you try to run Antutu several times in a row, so we can see is the result of 66k almost constant. Since as we all know, results can degrade towards 44k because of overheating..
predragiPredrag said:
Did you try to run Antutu several times in a row, so we can see is the result of 66k almost constant. Since as we all know, results can degrade towards 44k because of overheating..
Click to expand...
Click to collapse
I did not, but degradation of score is dictated by the thermal config. That's why i modded that too, and pushed the standard limits...
Let me show you with an example:
Code:
[SS-SKIN-XO-THERM-PERF]
algo_type ss
sampling 250
sensor xo_therm_buf
device cluster1
set_point 43000
set_point_clr 37000
time_constant 0
device_max_limit 800000
This is taken from the original file, and it covers the big cluster... when it reach 43° celsius, the thermal throttling will limit the max frequency of the cluster to 800MhZ
Code:
[SS-SKIN-XO-THERM-PERF]
algo_type monitor
sampling 5000
sensor quiet_therm
thresholds 46000 48000 50000
thresholds_clr 44000 46000 48000
actions cluster1 cluster1 cluster1
action_info 1632000 1248000 960000
This is the same part but modified by me, i've added more step... as you can see thermal throttling for big cluster will work once the big cluster reach 46° and it will cut the max frequency to 1632MhZ, then at 48° 1248MhZ and at 50° at 960MhZ
The hot-plug, that put the cores offline, on the original file for the big cluster is marked at 42° for core 4 and 45° for core 5.
On my config file both cores will be hot-plugged once they reach 52°.
TL;DR if you use my thermal-engine conf file, you will get more consistent score on several runs.
Nice to hear that will try this when I have more time to play with my phone and report back.
Great work and thanks for sharing this
GoldGanja said:
Hi guys!
Today i want to share with you a script i specifically tailored for our 4C, to decrease high battery drain just by tuning parameters of the interactive governor.
As many of you know, on the Nexus 5X forum there is a huge post about different profiles created to achieve the same purpose, and almost all of them works with our device (personally tested)
[GUIDE] Advanced Interactive Governor Tweaks; Buttery smooth and insane battery life!
I raccomed to read it!
(...)
Enjoy! & report back for feedback
P.S.
Files are zipped, extract them!!!
Click to expand...
Click to collapse
Hi,
I can not apply root because of he problem between pokemon go and root, (I am playing pokemon go with my 8 years old son a father-son activity and he loves it)
I am using a dev miui rom and i did tune my thermal-engine and remove the input boost using the TWRP file manager to apply the files.
This rom does not have init.d folder could i call your script from init.qcom.post_boot.sh? if so, do you know how to?
best regards,
John
You should look for some sort of systemless root, and magisk to masquerade root and be able to play Po Go on a rooted phone. I don't think you can chain load the script within post_boot.sh and by the way to modify it you should have super user permissions. Anyway keep up the father and son activity, is way more important!
Sent from my Mi-4c using Tapatalk
GoldGanja said:
You should look for some sort of systemless root, and magisk to masquerade root and be able to play Po Go on a rooted phone. I don't think you can chain load the script within post_boot.sh and by the way to modify it you should have super user permissions. Anyway keep up the father and son activity, is way more important!
Sent from my Mi-4c using Tapatalk
Click to expand...
Click to collapse
thanx, my son does not talk about anything else...
About the chain load the TS rom does that with ts_power.sh file.
Code:
# ts power scripts permissions
chown -h system /system/etc/ts_power.sh
chown -h system /data/ts_power.sh
Code:
# Call ts_power.sh, if found
if [ -f /data/ts_power.sh ]; then
logi "Call /data/ts_power.sh set_profile $profile"
sh /data/ts_power.sh set_profile $profile
elif [ -f /system/etc/ts_power.sh ]; then
logi "Call /system/etc/ts_power.sh set_profile $profile"
sh /system/etc/ts_power.sh set_profile $profile
fi
I will try to see if it works using your script.
About systemless root, i don't want to be in the middle of the cat and mouse thing. Today google update and tomorrow there is another hide root.
I did replace the thermal engine using the twrp file manager. It works.
Nice share bro. Thermal engine + init.d script is good battery backup for mi4c.
Hello,
could you make patched files available and the place where they should be placed ?
I don't want to root my phone but I want to give your optimisation a try. It is possible with TWRP to replace the files in the file manager. More work but it can be done without root. Therefore however I will need the allready patched files....
A little more "complicated" even... might it not be possible using TWRP to flash these files ? I have no idea how that would work exactly but I can imagine it would be possible to create a flashable zip that replaces these files... It currently goes beyound my abbilities though unfortunatly but maybe someone can help with that.
Thanks for your share @GoldGanja , looks interesting.
But i think the thermal-engine.conf would cause more overheating as it is already (for me reduce overheating is the most important), but i like the way to reduce the clockspeed step by step. Maybe i will try it with lower values.
The modified governer looks great. I think this will help with heating too. But on this there aren´t laggings ?
Thank you! i hope this fix my battery drain and the heat, i'll report if i see changes
@nachtwacht
Even if i make a zip file to use with twrp, this will only be useful for the thermal-engine conf file...because the other one is a script i've created and so there is no other file to replace. As stated ROOT is needed, i'm sorry.
@Danny94
thermal-engine.conf per se will not increase or decrease over-heating, of course one could make a conf file to be more restrictive on the temps and brutally decrease the performance but i don't see the need of this because i don't have any over-heat problem within my device with the script i've made. A major cause of over-heating is the input-boost frequency that by default is set to 1248MhZ, while if you run my script it will be 600 MhZ. Farther i have no lags at all...give it a try and report back. More feedback I have about it, the better I can adjust some parameters.
@HYBRIDEMON
Thanks!
@GoldGanja
Yeah i will try tomorrow if i get some free time.
Wich Rom do you use ? I have at almost all roms overheating problems. After 10 min+ of 3d gaming i have ~55°c + (On my old phone Thl 5k i could play the same game hours, don´t get over 45 °c and no lagging or something - and yeah its not the best phone).
With your thermal config the device throttles later. So it will heat higher, until it shut down big core etc. As hotter it becomes as more difficult its to cooldown. Sure if you won´t reach 52°c would be perfect one. But maybe i will replace the values with lower, else it looks very good.
I can't find tao.log at sdcard.
Script is applied or not?
I copied to etc/init.d and set 755 permissions.
Edit:
Finally I applied manually and I have 2 errors with big cluster settings.
Enviado desde mi Mi-4c mediante Tapatalk
@dany94
I'm using last stable from xiaomi.eu (8.0.5). Anyway, if you get to know how the gears of the thermal engine works, do what is best for your usage. Feel free to change the numbers on my file if needed
siba01 said:
I can't find tao.log at sdcard.
Script is applied or not?
I copied to etc/init.d and set 755 permissions.
Edit:
Finally I applied manually and I have 2 errors with big cluster settings.
Enviado desde mi Mi-4c mediante Tapatalk
Click to expand...
Click to collapse
I think you are using a CM TS rom, right? well, for that you have to do two things.
First, set the battery mode to QUICK, because on BALANCE there is the hotplug of the BIG cores. Then re-run my script.
If that's not the case, maybe the device was just a bit hot, and the hotplug kicked in by the thermal-engine...let it cool down first or use my thermal-engine conf.
Second, rename my file to userinit.sh and place it under /data/local if you want the settings to be applied at each boot.
GoldGanja said:
Even if i make a zip file to use with twrp, this will only be useful for the thermal-engine conf file...because the other one is a script i've created and so there is no other file to replace. As stated ROOT is needed, i'm sorry.
Click to expand...
Click to collapse
Maybe I was not clear or, more likely I do not completely understand which is a fact for sure
Let me clear up the first part, then hopefully in the end I will also better understand
Your script chances several files if I understand correctly ? scaling_min_freq for example is the first one you change in the script ?
Could we not update all the files that you change using TWRP ?
My guess is, (that's just me trying to understand better.....) that I think that using TWRP it is possible to change these files without root, but in reality it is not because the phone is not rooted ? Maybe because only the complete system can be changed and not single files ? (without root)
I do know that in the end, for me it is possible to root my phone, apply the settings, and then unroot it again.... which hopefully have my phone working like it never was rooted... it's just a risk I would like to avoid if in any way possible, therefore I am investigating and trying to get it all clear for me, sorry for that
GoldGanja said:
@dany94
I'm using last stable from xiaomi.eu (8.0.5). Anyway, if you get to know how the gears of the thermal engine works, do what is best for your usage. Feel free to change the numbers on my file if needed
I think you are using a CM TS rom, right? well, for that you have to do two things.
First, set the battery mode to QUICK, because on BALANCE there is the hotplug of the BIG cores. Then re-run my script.
If that's not the case, maybe the device was just a bit hot, and the hotplug kicked in by the thermal-engine...let it cool down first or use my thermal-engine conf.
Second, rename my file to userinit.sh and place it under /data/local if you want the settings to be applied at each boot.
Click to expand...
Click to collapse
I'm using Resurrecction Remix.
Thanks for your answer.
Enviado desde mi Mi-4c mediante Tapatalk
I was pretty sure you will do such a good job for Mi4c! Well done!
Edit: btw big cluster values are not getting applied
solis_f said:
I was pretty sure you will do such a good job for Mi4c! Well done!
Edit: btw big cluster values are not getting applied
Click to expand...
Click to collapse
What ROM are you using?
Sent from my Mi-4c using Tapatalk
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR PHONE BY IMPLEMENTING THIS MODIFICATION!!
IMPORTANT: THIS IS A RELATIVELY NEW TWEAK I HAVE IMPLEMENTED ON A DEVICE I DO NOT USE AS A DAILY DRIVER. I HAVE ONLY BEEN USING THIS ARISTO AS A TEST FOR 4 DAYS WITH THIS MOD IN PLACE (AT THE TIME OF THIS WRITING). I DO NOT KNOW HOW STABLE THIS IS, OR IF ANYTHING WILL RANDOMLY KNOCK OUT MY TWEAKS, BUT SO FAR SO GOOD. BUT . . . . ALWAYS REMEMBER, YOUR MILAGE MAY VARY!! PLEASE SHARE YOUR EXPERIENCE WITH THIS TWEAK SO WE CAN IMPROVE ON IT'S STABILITY!!
So here's the story . . . .
My girlfriend got a free LG Aristo from MetroPCS when she switched carriers, which was a damn good deal IMHO. After using it for a month or so, she's pretty happy with it, aside from the usual gripes that come with low-midrange devices. I repair phones and computers for a living so I wanted to tinker with it and see what, if anything, could be done to give it that little bit of extra 'oomph' in performance, battery life, etc. Since it's her only device I didn't wanna risk depriving her of her phone if anything went sideways, so I kept my eyes open for an Aristo to pop up, and the other day, one did! One of my clients texted me asking if I wanted to buy a broken Aristo for parts, and considering the only thing wrong with it is a cracked screen, I jumped on it.
So, now that I have the guinea pig Aristo to play with, I did a quick search to see what kind of dev community this device had here, and on XDA. I stumbled accross this post with a working TWRP v3 (BTW, mad props to messi2050 for the TWRP v3, no-verity-opt-encrypt script link, and tutorial! MANY THANKS!).
I was a little surprised that the Aristo has an easily unlockable bootloader, so I give credit to LG for giving folks the option to do what they want with THEIR device.
With the bootloader unlocked and TWRP installed, I went ahead and formatted the /data partition to disable encryption (AFTER MAKING A NANDROID OF CORSE!!). After rebooting back into TWRP, I transfered the no-verity-opt-encrypt script and Magisk v13.2 and flashed them (IN THAT ORDER).
Magisk was a must since my girl plays Super Mario Run, and a few other games/apps that check Safety Net, and I'm happy to report that with Magisk v13.2 installed, Safety Net passes without issue.
Now comes the issue of LG underclocking the Snapdragon 425. Looking at it from LG's perspective, I understand the logic behind this implementation; a lower max_freq is definitely gonna give you a bit of extra battery life, and since low-midrange devices like the Aristo are unlikely to be used for anything more than calling/SMS/MMS, web browsing, YouTube, and light gaming, they probably figured that that bit of extra performance wouldn't be missed by most people buying this device.
The Snapdragon 425 has a max CPU clock speed rated at 1.4GHz, however, the LG Aristo tops out at 1.25GHz (1.248GHz). Using flar2's EX Kernel Manager (I use ElementalX on ALL of my other devices, but his kernel manager app works with ANY kernel), I couldn't get the max-freq to stick at 1401MHz. Strangely, it would max out at either 1248MHz, or 1094MHz, and even setting it to apply on boot proved futile. Then, I noticed that the frequency range in CPU-Z was '960MHz - 1.25MHz', so then I headed for the source:
/sys/devices/system/cpu
In this folder you will see the following folders:
cpu0
cpu1
cpu2
cpu3
Interestingly enough, the max rated frequency of '1401000' is listed in the 'scaling_available_frequencies' file of each core, meaning that specific frequency can be controlled by the kernel (CPU governor) if directed via each core's 'cpuinfo_max_freq' file.
(NOTE: This guide will walk you through changing the max_freq only for cpu0, however, the method for cpu0 is identical for cpu1, cpu2, and cpu3, so just repeat the steps for each cpu core)
Step 1.) Open the folder 'cpu0' [/sys/devices/system/cpu/cpu0]
Step 2.) Inside the 'cpu0' folder, find the folder 'cpufreq' [/sys/devices/system/cpu/cpu0/cpufreq]
Step 3.) Inside the 'cpufreq' folder, find the file 'cpuinfo_max_freq' [/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq]
Step 4.) Open it with a text editor (I am using Solid File Explorer w/ Root add-on which has a built in text editor, but ES File Explorer, Root Explorer, etc. all have built in text editors)
Step 5.) Change the value from '1248000' to '1401000' (WITHOUT ' ' MARKS OF COURSE!!)
Step 6.) Save the file after making the changes.
Step 7.) Repeat the above steps for the remaining 3 A53 cores. If you need to follow the guide for each core, just change the 'cpu0' in STEP 1 to 'cpu1', then 'cpu2', etc.
Step 8.) After making the changes to each core and saving your edits, exit out of your file manager and reboot (Now, if you go back to look at your edit after saving the cpuinfo_max_freq, it will appear as if your edit did not stick, but trust me, it will stick when you reboot).
Step 9.) After rebooting, open your root file explorer and check the edits you made to each core's 'cpuinfo_max_freq' file. They should now all read '1401000'.
Step 10.) Open your preferred kernel editor/auditor app and change the max frequency to 1401MHz, and this time it will stick. If it does not stick, simply change your CPU governor to 'Performance', then set the max to 1401MHz and that should make it stick. After that, close your kernel tweaking app and open CPU-Z or some other app that shows the current CPU frequency and check that it's locked at 1401MHz. Once you see that it's locked at 1401MHz, go back into your kernel tweaking app and change the governor back to your desired setting (I'm using Interactive), then check to see that the CPU max frequency is still locked at 1401MHz.
Step 11.) DON'T FORGET TO SET YOUR KERNEL EDITOR/AUDITOR TO APPLY THE CHANGES ON BOOT!! For some reason, if you don't set on boot it will randomly change the max speed between 1094MHz and 1248MHz.
Step 12.) PROFIT!!
NOTES:
- Solid File Explorer automatically mounts /system -rw when you open it. I'm not sure about other root file explorers, so make sure you mount /system -rw or your edits will not save/stick
- This is a relatively new tweak, so if anyone can expand on what I've covered here, please do!!
It won't let me save the edited text
Nice work!!! Also looking at the LG. K20 as well as the LG Tp450(Stylo 3+). I am curious to see if LG intentionally underclocks all...or at least the only ones this poor bastard can afford...LoL
Doesn't seem to work for me. Max CPU frequency frozen at 960 MHz ?
Introduction:
This will remove the performance throttling of our S8 when using it heavily (gaming, movie streaming, or any demanding stuff we do on our phone). Oh and benchmarks also. There has been numerous threads of disabling DVFS from previous Exynos phones such as Note and Galaxy S4 and so on...
Note: This tweak will not INCREASE your phone's performance as is, but to remove limiting factor such as heat when it comes to heavy usage of phone. Removing throttling could cause too much heat to your phone or worse.... could cause device and physical harm to you. Be cautious and be warned when using this. I'm not responsible for any damages that this tweak would do to you.
Verdict: Heat generated was acceptable, but this depends on every users with different setups/installed apps on their phone/usages.
Requirements:
1. Rooted Galaxy S8 Exynos (this could work probably in S8+/Note 8 Exynos variant????)
2. Kernel Adiuotor (preferred) or any tool that has Init.d support.
Steps:
1. Download Kernel Adiutor from Playstore.
2. Open the app and go to Menu > Tools > Init.d.
3. Toggle the Init.d to enable script at boot.
4. Click "+" button and name it anything you want then click ok.
5. The editor will open, now copy and paste this script in the editor.
#!/system/bin/sh
chmod 0000 /sys/devices/14ac0000.mali/dvfs
chmod 0000 /sys/devices/14ac0000.mali/dvfs_max_lock
chmod 0000 /sys/devices/14ac0000.mali/dvfs_min_lock
6. Then click save button.
Now you can click the script and execute it or reboot to check if the script has been executed.
To check if the script is executed you may use Root Explorer Paid version and go to this directory,
/sys/devices/14ac0000.mali/
and look for dvfs file, if you see that the permission is --- or blank, that means the script has been applied.
Let me know if this works for you all.
Benchmarks are nothing but tbh, it will show if throttling affects the result. I haven't captured the 1st result but I got 130kish when he devices was 50~60°C.
I run the script and quickly rerun Antutu again. See attached image below.
https://en.wikipedia.org/wiki/Thermal_runaway
Your choice.
Will this also work on my s9+. On my s8 it works like a charm.
How to remove if this one is applied?
Just reboot ur phone
This is like to remove rev. limiter. Engine gone to blowww.
It work s7
Tank you . Now it give a life on my divice . No down clock aft few min on gaming . Happy .
can I do this with adb as well? I just purchased the S10+ ( exynos ofc) and I dont want to root it, not because I cant but if want to sell it some buyers will not be interested without no google pay, netflix , samsung pay etc. If I can do this with a adb command I would really like to know.
I think this disables GPU Throttling only not CPU right?.. Does anyone knows a way to disable the CPU Throttling? Im running a custom kernel on S7 FLAT EXYNOS Overclocked to 2600MHZ but after 2 minutes frequency drops to 2394MHZ Due to cpu throttle.
Edit: I dont care about the battery i just want a gaming phone and i know the risks.
s8userhere said:
How to remove if this one is applied?
Click to expand...
Click to collapse
Reboot
The app is made with Tasker, with focus on functionality over UI, so you may find the UI unpolished. The tasker project XML can also be found in the attached files.
Purpose
To apply and manage set of kernel settings (called "profiles" within the app). Also supports shell scripts.
Features
[ROOT REQUIRED]
– Loading profiles (+quick shortcut to swap between two profiles)
– Saving the current kernel settings in a new profile (or only some of the settings)
– Updating a profile file with the current settings (with this feature you can load a profile, then tweak in any kernel manager app and then update the loaded profile with the new settings)
– Comparing profiles (compares two profiles and outputs only the different settings with respective values for each)
– Load shell script files (such as the ones in the AKT zip file – see Downloads section – or others) *
– Convert shell script file to profile file** and profile file to shell script file
– Open/rename/delete files with a very simple file browser (tap and hold)
– Set a profile and/or script to be loaded on boot
– Uses cache for profile files, so applying a profile, which you have applied before, happens instantly.
– When applying profiles temporary changes the permissions of all non-writable files from the profile to apply all settings, after which restores them to the original permissions.
* loading scripts: when applying a script you will be asked if you want to temporarily change non-writable permissions to apply all values. If the script is more complex (such as with if/else statements) it is advised not to chose that option, since the script will not be applied correctly. In that case just choose "apply script as is". Also note that some scripts may require busybox, so you may need to install that to be able to apply them.
** converting shell scripts to profile files: the "echo" lines are converted to paths and values in the profile file. In more complex scripts (with if/else statements for ex.), multiple echo lines may cause incorrect settings to be applied if converted to a "profile file". If you know the script is such, it is not advisable to convert the script to profile. You may instead, apply the script and then save the current settings as a new profile.
Downloads
Downloads can be found in the attached files. There are two files named "AKT OP3" and "AKT OP3T". They are the scripts from the AKT thread. If you're familiar, you may find it useful. I would not advise using them on other devices.
Compatibility
The app should work on any device with two big and two little cpus. Generally any device should be supported but the saving functionallity might not correctly save the governor settings of one of the clusters, if the chip is too different. Made on OnePlus 3 and tested on a few other devices. No incompatibility reports received yet. The caveat is that some devices might need to adjust the font size in the settings for proper text visibility.
XDA: DevDB Information
Kernel Profile Manager, App for all devices with 4 cores and big.LITTLE architecture.
Besides the "Save settings as new profile", all features are device-independent and should work on any device. If you have a device with more cores or different architecture, you can use the "Update profile" feature to save settings, or better yet – pm me to add support for your device.
Contributors
Arstoien
Version Information
Status: Stable
Current Version: 1.25
Created 2018-06-03
Last Updated 2018-07-21
Changelog:
v1.25
– change: instead of holding down the "load profiles" option to swap between two profiles, the shortcut is now swipte-to-the-right
– new feature: holding donw "load profiles" option allows to compare the last applied governor to the current system settings. If you have made any manual changes (or the system for some reason has restored some of them, you will get a report with the changed values and option to reapply them
– change: change the tooltip of "load profiles" to describe the above features
– bugfix: minor workflow bugfixes
v1.24
– UI bugfixes
v1.23
– performance boost when loading file lists
– changed the SU check on app start for better user experience when granting root access
– "active profile" label resets to "none" on boot, if the profile is not applied (when the boot service is not activated)
– other minor bugfixes
v1.22
– bugfix: "apply on boot: shell script" could in certain situations not work properly
v1.21
– bugfix: when saving or updating profile the app would save the I/O scheduler in a way that would not be applied correctly afterwards
– bugfix (very minor): updating a profile could cause an extra redundant line after an empty line in the profile file
v1.20
– initial public release
Wow, thank you! That's awesome, a new toy!
On first glance everything seems to apply correctly...
Can i use these script (.sh) files with ek kernel manager?
Sam Nakamura said:
Wow, thank you! That's awesome, a new toy!
On first glance everything seems to apply correctly...
Click to expand...
Click to collapse
Thanks for the feedback. Hope you enjoy it!
anaknin said:
Can i use these script (.sh) files with ek kernel manager?
Click to expand...
Click to collapse
yes, you can also use the "profile" files with ek kernel too – just load them appropriatelly (I believe governor profiles or something similar).
I updated the "Compatibility" section of the OP, just to make some things clear, since the "save" function might not work well with some devices. If anyone faces something similar, I'd be glad to hear and it'll probably be an easy fix. Just don't have anyone with such device around me.
ask best balance tweaks suggest?
puturaya20 said:
ask best balance tweaks suggest?
Click to expand...
Click to collapse
Very difficult to say. It depends a lot on what you're looking for and your usage. I am currently using the latest FusionOBeta on OnePlus3. If you have OP3/3T, you can pm me and I'll share it. I think it's close to being stable and released pretty soon.
Arstoien said:
Very difficult to say. It depends a lot on what you're looking for and your usage. I am currently using the latest FusionOBeta on OnePlus3. If you have OP3/3T, you can pm me and I'll share it. I think it's close to being stable and released pretty soon.
Click to expand...
Click to collapse
hmm okay bro,how paste AKT_Scripts.zip ? paste in folder?
puturaya20 said:
hmm okay bro,how paste AKT_Scripts.zip ? paste in folder?
Click to expand...
Click to collapse
Unzip all files in any folder. Then, in the app, choose "load shell script file", navigate to the script you like and select it.
Update with one bugfix.
I would be very happy if a user with different cpu would assist me in testing the app, so it would offer better support for saving settings.
Also any feedback is appreciated.
Arstoien said:
Unzip all files in any folder. Then, in the app, choose "load shell script file", navigate to the script you like and select it.
Click to expand...
Click to collapse
How Look working script after select?
puturaya20 said:
How Look working script after select?
Click to expand...
Click to collapse
Open an app, with which you can see the values of the governor. Check them before and after the script. If you use KPM you can save the governor settings before and after the script and then compare.
Note that applying the AKT scripts takes a while, so give it some time. And make sure to have installed busybox in advance
Arstoien said:
I would be very happy if a user with different cpu would assist me in testing the app, so it would offer better support for saving settings.
Click to expand...
Click to collapse
What do you mean by "different CPU"? Different like SD820 vs SD821 or different like i.e. SD6xx or SD4xx or even completely different like Exynos, Mediatek?
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
What do you mean by "different CPU"? Different like SD820 vs SD821 or different LIKE i.e. SD6xx or SD4xx or even completely different like Exynos, Mediatek?
Click to expand...
Click to collapse
I meant other snapdragon series. Exynos and Mediatek would also be interesting to look at, I don't know how big the differences are and how easy it'd be to support them. In any case I need someone to test with such device.
Arstoien said:
Open an app, with which you can see the values of the governor. Check them before and after the script. If you use KPM you can save the governor settings before and after the script and then compare.
Note that applying the AKT scripts takes a while, so give it some time. And make sure to have installed busybox in advance
Click to expand...
Click to collapse
Thanks u bro
v1.22 Changelog:
– bugfix: "apply on boot: shell script" could in certain situations not work properly
@puturaya20 you may want this one, if you're going to use the function.
Thanks for your work, Arstoien!
I have 1.20 installed which is functioning great with the FusionBT 15 script.
Just wanted to update to 1.22 but it doesn't install. Neither does 1.21 btw.
Do I have to uninstall 1.20 before installing a new version? If so, does it keep my settings?
ericvanb said:
Thanks for your work, Arstoien!
I have 1.20 installed which is functioning great with the FusionBT 15 script.
Just wanted to update to 1.22 but it doesn't install. Neither does 1.21 btw.
Do I have to uninstall 1.20 before installing a new version? If so, does it keep my settings?
Click to expand...
Click to collapse
Thank you for the feedback!
Yes, it seems you are correct – I did not foresee that. The issue seems to be that I had reinstalled Tasker and even though I had set the package name to be the same and version to be higher, it is no longer compatible as an update to verison 1.20 or lower. After version 1.21 there should be no more issues with updates, so unfortunately I'd have to suggest to uninstall and then install the latest version.
If by "settings" you mean – lose whatever you have set up in the "settings" screen of the app, then yes, you will lose that. You will not lose any files you have created or modified though – only the info stored within the app's interface. So the app will no longer remember which is the last applied profile, etc.
No worries...problem solved by uninstalling 1.20 and installing 1.22 directly afterwards.
Had the scripts and profiles saved in a separate directory so changed settings to the correct directory and applied FusionBT again.
So up and running again! ??
Any idea when we can expect the new FusionBT profile? ?
ericvanb said:
No worries...problem solved by uninstalling 1.20 and installing 1.22 directly afterwards.
Had the scripts and profiles saved in a separate directory so changed settings to the correct directory and applied FusionBT again.
So up and running again! ??
Any idea when we can expect the new FusionBT profile? ?
Click to expand...
Click to collapse
Rather soon I'd imagine. Only minor tweaking is being done recently.
Been following these threads for quite some time. Own an HTC 10 and with the help of ZeroInfiniti have found a way to run his Engine and AKT and getting them to stick. Just wanted to say I appreciate all you guys hard work developing and maintaining. Been using AKT final 1.6 zip. Project Zhana battery. Getting fantastic results. 6+ hours on screen. About to try the new AKT app tomorrow.