Related
WARNING
Overclocking/undervolting could cause crashes with loss of data, or even damage hardware including the CPU or GPU.
Voodoo support included since 1.5, remove all non-Voodoo lagfixes before installing.
This works for me, but you are ultimately responsible for what happens to your device and your data - have backups, preferably on an external SD that you remove for initial testing.
These are unsigned and will not flash via stock recovery. Use ROM Manager to flash, with ROM Manager you also don't need to rename them as it can select any zip file from internal storage.
Features:
Voodoo lagfix support - should work correctly flashed over other Voodoo beta4 kernels, remove non-Voodoo lagfixes before installing.
BLN support to allow use of touch-button lights to indicate pending notifications when screen is off. The lights will light for all statusbar notifications, unless disabled in the app producing the notification (not all apps will have an option to do this, I don't think any stock Samsung apps do).
Stock voltages/clocks at boot, runtime configuration of clocks and voltages via sysfs, nilfs2 and ext2/3/4 filesystem support, two-stage user init - early scripts for mounting filesystems, late ones for running services. Default I/O scheduler is BFQ, BFQ/CFQ/anticipatory all perform roughly the same in benchmarks with multiple threads competing for I/O. Typical wakeup between instant and about one second, built with the binutils 2.19.1 / gcc 4.3.4 toolchain.
User clock/voltage configuration can be read from/written to /sys/devices/system/cpu/cpu0/cpufreq/freq_volt_table. Copy this file to get the defaults, edit your copy and write back over the original to update, or save your new file in /sdcard/sd/config, /sdcard/config, or /system/etc/config to have it applied on boot. The first column is CPU clock, the second GPU clock, the third CPU voltage, the fourth internal voltage. Changing values besides CPU clock/voltage is not recommended. You must keep 100MHz as the lowest speed. Clocks are in KHz, voltages in mV. Modify at your own risk, I find that my phone runs 1.2GHz @ 1.3V just fine, but yours may vary.
Be aware that your phone might appear to run fine with overclock/undervolt at first but crash later due to some error in calculation or data transfer - i recommend a good number of runs on something like Quadrant, and at least five minutes or so of SetCPU stress test for each frequency you add or change.
User inits must be placed in /system/etc/init.d, and properly named - names starting with "E" will run before /data and /dbdata are mounted, names starting with "S" will run right before startup is completed and normal Android services start. Inits are sorted by name, so you can follow the initial E or S with a number to change the order in which they will run. Scripts need not be executable, and will be run with the shell provided in initramfs for Voodoo support (busybox ash). If either /data or /dbdata is not a mount point after E scripts are completed, /user_early_init.sh will attempt to mount an rfs filesystem there from the usual location. If you want to mount a filesystem that is some other type, you will need to do so in a user script. If you want to format /data with another filesystem, you must edit the partition table to change the partition number - I have disabled the code in /sbin/init that rewrites the partition table, but if it finds something on standard /data partition that does not look like a valid RFS filesystem, it will reformat it.
If you want to build yourself, see the toolchains thread for known-working tools. Run
Code:
make ARCH=arm i897_defconfig
make ARCH=arm menuconfig [COLOR="blue"]optional[/COLOR]
make CROSS_COMPILE=/path/to/toolchain/arm-none-eabi- zImage [COLOR="blue"]change if using a different toolchain[/COLOR]
tar c -C arch/arm/boot/zImage >captivate_zimage.tar
Flash captivate_zimage.tar as PDA in Odin - see other threads for how to use Odin and where to get it. Use menuconfig to select a different initramfs source if you wish, by default an included one at usr/initrd_files will be used.
Starting with v1.4, create a .build_config file to change any variables and run build_kernel.sh to build tar flashable with Odin or update.zip. As of v1.5.2 you can also use .build_config to inject commands and files into update.zip builds.
CREDITS
raspdeep - the original OC code
curio - Voodoo lagfix original concept and script
neldar - BLN support
atinm - BLN port for Captivate
BusyBox, buildroot, crosstool-ng, nilfs2 - see respective projects for original contributors and source
v1.7ClockworkMod Recovery
flashable binary: mediafire mirror | github mirror
github source
BETA ClockworkMod Recovery replaces stock recovery
BETA support for backup/restore with Voodoo enabled
v1.6BLN Support
flashable binary: View attachment i897-unhelpful-v1.6.zip | mediafire mirror | github mirror
github source
BLN support - use the touch-button lights to alert of pending notification when screen is off.
Disable check for SGH-I897 device, since this can fail on Captivate hardware if an alternate ROM is flashed.
v1.5.3Bugfix release
flashable binary: View attachment i897-unhelpful-v1.5.3.zip | mediafire mirror | github mirror
github source
Revert from the config based on kepler_rev02_defconfig, suggested by the 9/6 code drop, to aries_rev02_defconfig. The config change appears to have been responsible for the power drain problems seen in v1.5.1 and v1.5.2.
v1.5.2Bugfixes and Voodoo lagfix support
flashable binary: View attachment i897-unhelpful-v1.5.2.zip | View attachment i897-unhelpful-v1.5.2.tar.7z | mediafire mirror | github mirror
github source
Odin-flashable tar file (inside 7z to allow upload to XDA), please use only to recover from bad flash of v1.5.1, the update.zip contains scripts that are important if you're running SRE.
Voodoo lagfix support
Restore correct stock voltage (1.275V) for 1GHz
Update sources and config from Captivate 9/6 source drop
Update modules from JH7 OTA
LZMA initramfs compression to reduce compressed kernel size / allow larger initramfs
Enhanced update.zip support allows developers to easily inject their own commands and files into update.zip on build, and allows run_programs scripts to produce screen output and can flash kernel/modem partitions directly.
v1.4.1BUGFIX for SRE users
flashable binary: View attachment i897-unhelpful-v1.4.1.zip | View attachment i897-unhelpful-v1.4.1.tar.7z | mediafire mirror | github mirror
github source
Bug with SRE + 1.4 causing storage to become unavailable should be fixed by this kernel, fix works on my phone but some have reported problem spontaneously ifxing itself.
v1.4Load OC/UV config from file, system early init (for developers).
downloads removed due to bugs
github source
Built with gcc-4.4.3
build_kernel.sh reads variables from .build_config, or from config file specified by $BUILD_CONFIG, so you can keep the script file clean.
Early system init - E* scripts in /sbin/init.d run before user early init, for developers to include startup scripts.
System init loading of OC/UV table - searches for config/freq_volt_table on external SD, then internal SD, then in /system/etc.
ADB checks uses the first shell found from the list bash, ash, /system/xbin/sh, /system/bin/sh, sh.
Correctly set cpufreq policy on table change - should fix resets of maximum clock to 1GHz after new tables are loaded.
v1.3.1OC/UV configuration
flashable binary: View attachment i897-unhelpful-v1.3.1.zip | mediafire mirror | github mirror
github source
Stock clocks/voltages at boot, user can add new clocks and change voltages at runtime - see above for details.
Modify stock init to avoid rewriting partition table at boot - change the partition table for internal SD, resize partitions or remake /data with a different partition number so it can be safely formatted with another filesystem.
v1.2Bugfix / update.zip / dev features
flashable binary: View attachment 389189 | mediafire mirror | github mirror
github source
Fix scaling bug, performance level was set past end of table on sleep
Scaling enhancement, selectable clock source for GPU
GPU clocked at 222MHz for all speeds except 100MHz, where it matches CPU clock
Basic build_kernel.sh script, edit to change configuration - builds unsigned update.zip with default kernel config by default
Add interactive CPU governor - enabled in build but conservative is still configured as the default
v1.1Bugfix release
flashable binary: mediafire mirror | github mirror
github source
Rework of user init, resolves lost-settings-on-boot issue for me.
v1.0Initial release for Captivate I897
flashable binary: mediafire mirror | github mirror
github source
nilfs2, ext2/3/4 filesystems
separate early and late user init
600MHz and 1.2GHz speeds, use SetCPU to enable 1.2GHz
fast scaling from low speed, skipping from 100MHz to 800MHzOther Downloads
User Init Scripts
mediafire, github - enable 1.2GHz overclock on startup
mediafire, github - start Mobile AP background service
Does this include the ability to clock at 1000 mhz?
Sent from my Nexus One using XDA App
You're my hero.
*edit*
_Opiate_ said:
Does this include the ability to clock at 1000 mhz?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yea it is, I have it set at 1200 in setcpu and I saw it hit 1000mhz a few times just watching it.
Yes, the scaling steps are 100MHz, 200MHz, 400MHz, 600MHz, 800MHz, 1GHz, and 1.2GHz. 1.2GHz is disabled at startup until the user enables it, so that the kernel can be used without overclocking.
Sent from my SAMSUNG-SGH-I897 using XDA App
So will this undo the MobileAP that was just put out. I know we had to flash a custom kernel to enable that. Will this undo it?
Clienterror said:
You're my hero.
*edit*
Yea it is, I have it set at 1200 in setcpu and I saw it hit 1000mhz a few times just watching it.
Click to expand...
Click to collapse
Never mind I just flashed it. No On demand?
Unhelpful said:
Yes, the scaling steps are 100MHz, 200MHz, 400MHz, 600MHz, 800MHz, 1GHz, and 1.2GHz. 1.2GHz is disabled at startup until the user enables it, so that the kernel can be used without overclocking.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Thats great. Hell just running it at 1000mhz is a slight improvement in Quadrant. Before when I was running the stock kernel I never saw it clock above 800mhz.
Also no wake up lag at all!!!!!!!!! Great fraking job man!!!!!
jhernand1102 said:
So will this undo the MobileAP that was just put out. I know we had to flash a custom kernal to enable that. Will this undo it?
Click to expand...
Click to collapse
This does not run wlp2pservice in the init.rc, but a user script can easily be written to do that - I already have one on my phone, I'm going to add a section for init scripts in the OP when I get the chance.
Can you toss up a donation link plz :-D
Unhelpful said:
This does not run wlp2pservice in the init.rc, but a user script can easily be written to do that - I already have one on my phone, I'm going to add a section for init scripts in the OP when I get the chance.
Click to expand...
Click to collapse
Thanks for the info...looking forward to trying this out once there is a script so MobileAP still works...
jhernand1102 said:
Thanks for the info...looking forward to trying this out once there is a script so MobileAP still works...
Click to expand...
Click to collapse
Yeah that's one reason I still use my Nexus One mainly. The ability to tether is built right in to Froyo. But I can wait for tethering till we have a kernel that will do both. I prefer to play with this kernel now. Lol
Sent from my Nexus One using XDA App
_Opiate_ said:
Yeah that's one reason I still use my Nexus One mainly. The ability to tether is built right in to Froyo. But I can wait for tethering till we have a kernel that will do both. I prefer to play with this kernel now. Lol
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yeah hopeful it can be put in the same kernel then we can have the best of both worlds...
I just found something strange. When I reboot and enter set cpu the phone say I have to chose my device again so I have to choose autodetect again.
Sent from my SAMSUNG-SGH-I897 using XDA App
do we just flash this with odin ? in the op there are many intrsuctions on putting stuff here and there i got lost
_Opiate_ said:
I just found something strange. When I reboot and enter set cpu the phone say I have to chose my device again so I have to choose autodetect again.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Every time I reboot it's all in Russian again like the first boot with JM5 lol.
Crizthakidd said:
do we just flash this with odin ? in the op there are many intrsuctions on putting stuff here and there i got lost
Click to expand...
Click to collapse
Yep, just use 7zip and extract the .tar then flash with odin3 as PDA.
Wow, unhelpful you are the MAN. Put up a donate link, I'll send a few beers your way.
Works!!
Unhelpful, you're probably one of the MOST helpful people on this forum. haha
minor bug, usb debugging doesn't seem to stay on between reboots.
and i can't seem to send emails using the gmail client anymore
IStern said:
minor bug, usb debugging doesn't seem to stay on between reboots.
and i can't seem to send emails using the gmail client anymore
Click to expand...
Click to collapse
ditto on the usb debugging, wont stay on between reboots
I have been experimenting with Kernel swapping tring to find the easiest and safest way without Soft Bricking your Tab. I am on Sprint 7" (SPH-P100) and on Stock EF-17 2.3.4, but this method should work on any (Rooted) CDMA Tab.
First find the CDMA ROM that has the Kernel you want to use, DL the ROM and Extract it to its own folder and go into the folder and find the Zimage. Copy the Zimage and paste on your Desktop. Now DL SGS Kernal Flasher from the Market (FREE) Back up your kernal in the APP. Mount your tab and open to veiw files. If there is a Zimage file in there, Delete it and put your new Zimage (Kernel) in its place and unmount your Tab.
Open SGS Kernel Flasher and hit Choose Kernal, Now goto parent directory and scroll all the way to the bottom and you should see Zimage, press on that then hit FLASH Kernel. Now you have a new OC Kernal without using ODIN or Heimdall!!
Right now I am using Galaxy Cubed 3 ROM's Kernel 1.6GHz on stock EF-17. I have found that I am Stable @ 1.4 GHz. On performance using SetCpu I am running 2350 Quadrants More than double the speed of the stock Kernel without VooDoo, or EXT4!! I have also Flashed Initial Contact kernel @ 1.2GHz.
I have done this on my Sprint Tab and it has worked Flawlessly.
Please do so @ your own Risk, as I am not responsible for your Tab. With that being said Happy Easy Kernel Flashing To ALL CDMA Folks.
I'm using froyo 3.4.3-36-1.7.
I want only ondemand scaling overclock with manually.
I found many modules in bootmenu 1.0.6 ext directory.
install overclock modules
- overclock_defy.ko
ondemand scaling modules
- nothing only settigns
the others are interactive, powersave, smartass, and userspace modules.
Is that corrent?
sorry poor my english.
Solved.
Only need overclock_defy.ko and it module name is overclock.ko not overclock_defy.ko
I use /system/etc/install-recovery.sh and greped /proc/kallsyms for mpu_opps_addr.
Hi,
I have seen people over-clock their HD2 to 1.5GHz,
Is this at all safe to do?
If so can it be done on an SD build for example Boxmax Runnymead V6.5
I understand you need a certain kernal, which one?
Thanks,
Alex
Yes it's safe
Your phone will go onto that speed only if it's needed and afterwards slow down.
I don't know the sd kernels but if you use dorimanx kernel for nand Roms (will work on every nand rom) you will have that feature.
Press the thanks button
Sent from my HTC HD2 using xda premium
alex.odell.2011 said:
Hi,
I have seen people over-clock their HD2 to 1.5GHz,
Is this at all safe to do?
If so can it be done on an SD build for example Boxmax Runnymead V6.5
I understand you need a certain kernal, which one?
Thanks,
Alex
Click to expand...
Click to collapse
To over clock on an sd build you have to edit your startup.txt .
Sent from my GT-I9100 using Tapatalk
I have last dorimax kernel,i use it since 3.2 version.Now it s about 1 mounth that my hd2 cpu is clocked @ max 1612Mhz and min 96Mhz (possible from 3.8)
Great performance with zram enabled,the phone is ultra fast and is not hot.
elesbb said:
To over clock on an sd build you have to edit your startup.txt .
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
How do you do that?
alex.odell.2011 said:
How do you do that?
Click to expand...
Click to collapse
The startup.txt should be in the same folder as the other sd rom files you download when choosing a rom. Just open it with notepad and make your changes.
chrisrj28 said:
The startup.txt should be in the same folder as the other sd rom files you download when choosing a rom. Just open it with notepad and make your changes.
Click to expand...
Click to collapse
I have no reference to "cpu frequencys" what text would I have to put, and where to set the min value to 384MHz to 1.5GHz.
Thanks guys
Isn't it possible to change CPU Frequencies by using SetCPU or is it SDCard relatet?
alex.odell.2011 said:
I have no reference to "cpu frequencys" what text would I have to put, and where to set the min value to 384MHz to 1.5GHz.
Thanks guys
Click to expand...
Click to collapse
This is the command you MUST use to set the overclock kernel speeds.
This is just an example , the 614400 is the speed in Khz . so Mhz would be 614.4 but the code in the text file must be in khz. It must be entered in between the quotes after the "set cmdline"
Code:
acpuclock.oc_freq_khz=614400 for 614.4 MHz. Choose multiples of 19.2 MHz
here i have an example of a simple startup.txt file also with the location of the cpu clock speed preset.
Code:
set mtype 2524
set ramaddr 0x11800000
set ramsize 0x1e400000
set KERNEL zImage
set initrd initrd.gz
set initrd_offset 0x00a00000
set cmdline "rel_path='Your path to android on SD' acpuclock.oc_freq_khz=614400"
boot
domimatik said:
Isn't it possible to change CPU Frequencies by using SetCPU or is it SDCard relatet?
Click to expand...
Click to collapse
SetCPU only "forces" which speeds to be used , the speeds must first be set by the kernel which is what the above command does in the startup.txt
Then you would use SetCPU to set the min and max frequencies of choice
elesbb said:
This is the command you MUST use to set the overclock kernel speeds.
This is just an example , the 614400 is the speed in Khz . so Mhz would be 614.4 but the code in the text file must be in khz. It must be entered in between the quotes after the "set cmdline"
Code:
acpuclock.oc_freq_khz=614400 for 614.4 MHz. Choose multiples of 19.2 MHz
here i have an example of a simple startup.txt file also with the location of the cpu clock speed preset.
Code:
set mtype 2524
set ramaddr 0x11800000
set ramsize 0x1e400000
set KERNEL zImage
set initrd initrd.gz
set initrd_offset 0x00a00000
set cmdline "rel_path='Your path to android on SD' acpuclock.oc_freq_khz=614400"
boot
SetCPU only "forces" which speeds to be used , the speeds must first be set by the kernel which is what the above command does in the startup.txt
Then you would use SetCPU to set the min and max frequencies of choice
Click to expand...
Click to collapse
Tried that but it didn't apply I did "1497600",
That just caused more lag?!?
Thanks
alex.odell.2011 said:
Tried that but it didn't apply I did "1497600",
That just caused more lag?!?
Thanks
Click to expand...
Click to collapse
did you then use SetCPU to set the Max clock speed ? and to set the proper governers ? and you have the code at the correct spot too right ? double and tripple check . also is it a multiple of 19.2 ?
elesbb said:
did you then use SetCPU to set the Max clock speed ? and to set the proper governers ? and you have the code at the correct spot too right ? double and tripple check . also is it a multiple of 19.2 ?
Click to expand...
Click to collapse
Ok I will reinstall android and try 1478400,
Alex
alex.odell.2011 said:
Ok I will reinstall android and try 1478400,
Alex
Click to expand...
Click to collapse
If you are doing everything correctly it should work without a problem . We will figure it out though
Hi guys tried it again,
No luck,
I am using Hasterin SenBT 8.6 (I think :S)
No luck, Maybe the kernal does not support OC,
Here is my "Startup.txt"
##BoxmaX S3.5 Runny v6.5##
set mtype 2524
set ramaddr 0x11800000
set ramsize 0x1e400000
set KERNEL zImage
set initrd initrd.gz
set initrd_offset 0x00a00000
set cmdline "rel_path=Android data_size=1024 acpuclock.oc_freq_khz=1478400 nand_boot=0"
boot
alex.odell.2011 said:
Hi guys tried it again,
No luck,
I am using Hasterin SenBT 8.6 (I think :S)
No luck, Maybe the kernal does not support OC,
Here is my "Startup.txt"
##BoxmaX S3.5 Runny v6.5##
set mtype 2524
set ramaddr 0x11800000
set ramsize 0x1e400000
set KERNEL zImage
set initrd initrd.gz
set initrd_offset 0x00a00000
set cmdline "rel_path=Android data_size=1024 acpuclock.oc_freq_khz=1478400 nand_boot=0"
boot
Click to expand...
Click to collapse
Can you link me to the ROM ? also are you able to boot at all ?
elesbb said:
Can you link me to the ROM ? also are you able to boot at all ?
Click to expand...
Click to collapse
Hi,
Yes it boots fine, running it now, great build I have 1.2GHz overclock as stock on build.
here you go...
http://forum.xda-developers.com/showthread.php?t=1256423
alex.odell.2011 said:
Hi,
Yes it boots fine, running it now, great build I have 1.2GHz overclock as stock on build.
here you go...
http://forum.xda-developers.com/showthread.php?t=1256423
Click to expand...
Click to collapse
Hmmm i see nothing about Overclocking on his thread , after you set the OC speed in your startup.txt can you still boot ? and check via SetCPU what the max cpu clock speed is at . it might be a simple format error .
elesbb said:
Hmmm i see nothing about Overclocking on his thread , after you set the OC speed in your startup.txt can you still boot ? and check via SetCPU what the max cpu clock speed is at . it might be a simple format error .
Click to expand...
Click to collapse
I have tried it again and it boots fine, when I go into SetCPU it just says the max speed is 1.2GHz ?!?!
Strange?
alex.odell.2011 said:
I have tried it again and it boots fine, when I go into SetCPU it just says the max speed is 1.2GHz ?!?!
Strange?
Click to expand...
Click to collapse
Hmm my only guess is the clock speed is hardwired into the kernel , id contact the dev of that ROM and ask him . It seems like OC is set by default
Sounds possible. Thanks for your help. 1.2GHz is still fast and safer I guess.
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Hello everyone , i have installed the RR ROM on J320F ! and i would like to limit CPU frequency to save power .
I tried several apps but none of them worked .. the system keeps changing the settings back.
Is there a way to do that ?
Thank a lot
With the latest version you can choose the low power mode to set the maximum at 1350MHz ... it's a first try so I'm not sure of all.
djeman said:
With the latest version you can choose the low power mode to set the maximum at 1350MHz ... it's a first try so I'm not sure of all.
Click to expand...
Click to collapse
Thanks for your reply Djeman.
Yeah i know that..But i would like to reduce it more.. 900 Mhz for example?! can I ?!
is there a way to change the whole cpu government?!
Change all nope, it's only interactive for now.
And all settings for the interactive mode are here => https://github.com/djeman/android_d...cm-14.1/rootdir/etc/init.j3xnlte_base.rc#L138
"hispeed_freq" is the value set in low power mode => https://github.com/djeman/android_v...en-source/libs/power/power_interactive.c#L218
You can set 900MHz, it's one of the 4 values defined for the cpu => https://github.com/djeman/android_d...s/base/core/res/res/xml/power_profile.xml#L20
I'm talking about the max frequency I don't know why but i can't set it to a values other than 1500 or 1350Mhz.. i can change the hi_freq to whatever i want but the the max frequency no ! so the cpu most of the time goes above that limit (hi_freq).
Because the max frequency do not changes, it's always 1500.
We have a scaling on 5 values and cpu hotplug to disable cores.
The value you can set is the scaling max frequency.
Available frequencies are here:
Code:
j3xnlte:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
1500000 1350000 1200000 900000 768000
You can set the maximum here:
Code:
j3xnlte:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
1500000
In low power I set it with the driver at 1350 (hispeed_freq value):
Code:
j3xnlte:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
1350000
Really sorry Djeman !! .. but i could not change it !!
Every time i change it with rootbrowser it change back to the original value
I tried TRWP Terminal but /sys partition seems to be Read-only i don't know !
same thing with adb shell !
I need to enhance my power driver ^^
With a new power mode between low and balanced profil and better profiles.
I found some examples in others projects => https://git.sphere.ly/dtc/device_motorola_msm8226-common/blob/m-dtc/power/power.h
But to enhance it I need to understand all parameters :x
You will find everything here if you want :
https://forum.xda-developers.com/galaxy-s2/general/ref-kernel-governors-modules-o-t1369817
You are right , it's a heavy task to tweak governor ! Especially if you cannot find any documentation online .
I had headache trying to modify system files.
There's some running services that restore defaults values everytime i edit them.
I'm giving up ??
Solved
Heyy @djeman , i have finally succeeded in setting up the frequency limit .
there is another file that should be modified simultaneously with "/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" .. this one :
/sys/power/cpufreq_max_limit
But apparently,you should first set the min frequency then the maximum otherwise the cpu will be locked in a single frequency.
I don't really know how and why ... but this works for me!
Here is my settings :
Code:
echo "768000" > /sys/power/cpufreq_min_limit
echo "768000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "900000" > /sys/power/cpufreq_max_limit
echo "900000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "900000" > /sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq
The CPU freq now is oscillating between 768 and 900 MHz cos the hispeed_freq and max are the same.
it is on 768 and on Demand ( 85 % loaded indicated here /sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads ) they scale up to 900Mhz.
I don't need 1500 Mhz .. I'm not running 3D games here or whatever
Hope these informations will be useful for someone
Yep all the discussion will be useful, you speak with the main dev
In one of the next update I will add a low power mode with your settings and a new mode between low and normal with my little downclock at 1350.
For now I'm analizing how works the fast dormancy, I think it's a good feature to reduce battery draining.
Fast Dormancy ! it's the fisrt time that i hear about this !
it seems effecient.
Good luck with that ?
Setcpu app not work
may be must custom in kernel
minhngt said:
Setcpu app not work
may be must custom in kernel
Click to expand...
Click to collapse
No , these apps will not work .Actually you don't need them.
If you want to Overclock the CPU than you can't .The current kernel doesn't support that yet.
But If you want to downclock the cpu you can create an init.d file that contains the script posted above with your preferred interactive governor settings.
Can you shown me the way to do it?
Tks so much^^
the easiest way( maybe ) :
1- Install ES File Explorer
2- Open ES explorer menu and scroll down and activate "root explorer" option (of course you must have rooted the system first).
3- Browse to /etc/init.d folder and create a new file with any name you choose (without extension)
4- copy and past these lines there :
Code:
echo "768000" > /sys/power/cpufreq_min_limit
echo "768000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "900000" > /sys/power/cpufreq_max_limit
echo "900000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "900000" > /sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq
5- Replace the max frequency 900000 Hz with whatever you want from these (768000,900000,1200000,1350000,1500000) and save the file.
6- Select the file, click 'properties' , click 'change permissions' and check the execute properties.
7- that's all .. Enter the developer options and activate "show cpu infos" to make sure that the frequency has been changed.