Since I keep getting asked how to use the sysfs interfaces I have built into my kernel, I decided to do post on just those items. If you would like a more detailed explanation of sysfs, refer to http://en.wikipedia.org/wiki/Sysfs.
I’ve done a write-up on the VDD, smartass, and cpufreq sysfs interfaces. I also included a brief how-to for creating init scripts to make these changes on boot. All of these examples can be done via an adb shell. I’ve been using a ‘Nix of some kind since the early 90’s, so I’m very comfortable in a command line only enviroment. I still recommend trying these commands from the command line first, it’s how I test overclocking and undervolting, that way if something does not work, and the phone reboots, everything goes back to how it was.
Also, if there are any Android Java developers that would like to make an app automate these tasks for the standard users, I’d be more than willing to help with that. I’m no longer a Java developer, and have no intention of touching it again, I learned to hate it in the late 90’s on Sun Sparc’s and have no desire to go back. I’ll always be more comfortable in plain old C or maybe perl, you have to love a language that allows you to do this:
printf $a > $b ? “True” : “False”;
VDD sysfs usage:
The sysfs VDD interface for Static Voltage Scaling, SVS, uses /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels. The sysfs VDD interface for Hybrid Adaptive Voltage Scaling, HAVS, uses /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs. The first was implemented by sqn in his original patch, however the second was implement by myself so that I could have HAVS and a sysfs interface for VDD levels. Both files are similar in usage and function, below are examples of each.
To list the current values:
To change ALL voltages either up (+) or down (-), must be increments of 25mV:
echo "+25" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "+25" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
echo "-25" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "-25" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
To change just one frequency, you specify the frequency and the voltage, or for HAVS, the frequency and the voltage range:
echo "998400 1100" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "998400 1050 1100" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
Smartass sysfs usage:
The original smartass patch that I found did not have a working sysfs interface, there were slight issues with it, so I decided to fix it, since it’s very useful to have. All smartass control files are located at /sys/devices/system/cpu/cpu0/cpufreq/smartass.
The following is a list of each file, and it’s description:
The minimum amount of time to spend at a frequency before we can ramp down, default is 45ms.
When ramping up frequency with no idle cycles jump to at least this frequency. Zero disables. Set a very high value to jump to policy max freqeuncy.
When sleep_max_freq>0 the frequency when suspended will be capped by this frequency. Also will wake up at max frequency of policy to minimize wakeup issues.
The frequency to set when waking up from sleep. When sleep_max_freq=0 this will have no effect.
Sampling rate, I highly recommend to leave it at 2.
Freqeuncy delta when ramping up. Zero disables causes to always jump straight to max frequency.
Max freqeuncy delta when ramping down. zero disables.
CPU freq will be increased if measured load > max_cpu_load.
CPU freq will be decreased if measured load < min_cpu_load.
Current smartass defaults set in my kernels:
To read the current values (max_cpu_load as an example):
To set the current values (max_cpu_load as an example):
echo "80" > /sys/devices/system/cpu/cpu0/cpufreq/smartass/max_cpu_load
Controlling the current cpufreq policy, i.e., How to Over/Under clock without SetCPU:
There are also control files associated with the CPU frequency, cpufreq, driver located at /sys/devices/system/cpu/cpu0/cpufreq.
The following is a list of the important files and their descriptions:
Lists all available frequencies that the processor is programmed to handle. This doesn’t mean that all will work, just that it’s possible to tell the processor to attempt to use them.
Lists all available governors available for usage.
Lists the current operating frequency of the processor.
Gets/Sets the currently used governor.
Gets/Sets the maximum allowed frequency for the current policy, refer to scaling_available_governors for valid frequencies.
Gets/Sets the minimum allowed frequency for the current policy, refer to scaling_available_governors for valid frequencies.
To read the currently available frequencies:
To set the current governor to smartass:
echo "smartass" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
To change the maximum frequency:
echo "1536000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
How to make the settings take effect after a reboot:
The problem with using the sysfs interface for the preding is that it is only current as long as you do not reboot the device. This is a good thing if your attempting to overclock your device, and it locks up, as soon as it reboots, it goes back to the defaults until something tells it differently. In order to make these changes take effect after a reboot, you need to use an init script. If your current ROM has run-parts enabled, which I believe most do anymore, then the following will work. You also need to make sure that the init scripts that you put under /system/etc/init.d are executable, i.e., chmod 755 filename. Also, in order to save these files to /system/etc/init.d, /system needs to be mounted as read-write.
The following example init script is for undervolting the lowest frequency on a ThunderBolt with SVS, others are similar. This file needs to be located in /system/etc/init.d. Example filename would be 99vddlevels.
echo "245760 850" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
The following example would set the policies maximum frequency to 1.536GHz. Again, this file needs to be located in /system/etc/init.d, and for this example, is named 99overclock.
echo "1536000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Now for some fun stuff. If you would like to setup an init script to allow you to change the policy while the screen is on or off, there are a couple other sysfs files that are going to be of interest you. Those two files are /sys/power/wait_for_fb_wake and /sys/power/wait_for_fb_sleep. These are considered blocking files, in other words, if you attempt to cat the file, display it’s contents, it will not display until a condition is reached. The condition for wait_for_fb_wake, you guessed it, the screen wakes up. When the screen wakes up, cat /sys/power/wait_for_fb_wake will return awake. Same holds true for wait_for_fb_sleep, when the screen turns off, it returns sleeping. Knowing this will now allow us to create a script to deal with different states of the screen.
The following script will change the governor, minimum and maximum frequencies. When this script launches via run-parts, it will remain running until it is either killed or the device reboots. Note, if you decide to change the values after using the script for at least one boot, make sure to reboot for the changes to take effect, either that or kill off the process and restart it.
(while [ 1 ]
if [ $AWAKE = "awake" ]; then
echo $AWAKE_GOVERNOR > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo $AWAKE_GOVERNOR_FREQENCY_MAX > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo $AWAKE_GOVERNOR_FREQENCY_MIN > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
if [ $SLEEPING = "sleeping" ]; then
echo $SLEEP_GOVERNOR > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo $SLEEP_GOVERNOR_FREQENCY_MAX > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo $SLEEP_GOVERNOR_FREQENCY_MIN > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq