Database Info

[KERNEL] OC/UV Kernel (test)

Hi,
avetny asked me to take a look at the g2x kernel to add OC/UV, so i did build a kernel with oc/uv added. You can read more about the kernel on the o2x thread. With this kernel you should be able to use Pimp My Cpu to manage cpuspeed/voltages on the fly.
I do not own a g2x device so i could not test this kernel, try at your own risk.
g2x-kernel-2.6.32.9-fakeShmoo-cpasjuste.5.zip : db7a11365e8520424f1ed579b666623f
EDIT :
Since i do not have the device, if someone wants to continue the work (fix wifi/bt) you'll find the sources and changes here : https://github.com/Cpasjuste/android_kernel_lg_p999/commits/fakeShmoo
Note that you NEED to add "init.d" support to the kernel initramfs :
Add at the end of the init.rc script :
Code:
# Execute files in /etc/init.d before booting
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
And maybe the "99complete" script to "/system/etc/init.d" :
Code:
#!/system/bin/sh
sync;
setprop mcr.filesystem.ready 1;

Thanks a lot for this. Look forward to giving it a go

Kernel boots fine, however,it breaks wifi. Will continue testing and see how everything else it

jlevy73 said:
Kernel boots fine, however,it breaks wifi. Will continue testing and see how everything else it
Click to expand...
Click to collapse
Arg that's strange, i don't see why wifi would be broken :/

Cpasjuste said:
Arg that's strange, i don't see why wifi would be broken :/
Click to expand...
Click to collapse
It is...when I flashed I say the wifi modules loading.
But wow, this kernel is fast. Smartbench just shot through the roof.

jlevy73 said:
It is...when I flashed I say the wifi modules loading.
But wow, this kernel is fast. Smartbench just shot through the roof.
Click to expand...
Click to collapse
Note that it's not OC by default. Could you try Pimp My Cpu on it to see if it work ? Thanks
For the wifi module, i'll wait for "avetny" if he knows anything.

Cpasjuste said:
Note that it's not OC by default. Could you try Pimp My Cpu on it to see if it work ? Thanks
For the wifi module, i'll wait for "avetny" if he knows anything.
Click to expand...
Click to collapse
That's what I mean by wow it's fast. I installed pimp my cpu and have it running @ 1200/300 while I do some benchmarking. Pimp my cpu is working very well.

jlevy73 said:
That's what I mean by wow it's fast. I installed pimp my cpu and have it running @ 1200/300 while I do some benchmarking. Pimp my cpu is working very well.
Click to expand...
Click to collapse
Ha that's very cool. Many thanks for the "bravery"
Just need to fix wifi now :x
I won't be able to do so myself without a device to test so some help will be required. The recovery install script just copy the "drivers/net/wireless/bcm4329/wireless.ko" module to "/system/lib/modules/wireless.ko" on the device. Maybe on the g2x the modules are located somewhere else.

Cpasjuste said:
Ha that's very cool. Many thanks for the "bravery"
Just need to fix wifi now :x
I won't be able to do so myself without a device to test so some help will be required. The recovery install script just copy the "drivers/net/wireless/bcm4329/wireless.ko" module to "/system/lib/modules/wireless.ko" on the device. Maybe on the g2x the modules are located somewhere else.
Click to expand...
Click to collapse
Let me check to see where the drivers are located.

jlevy73 said:
Let me check to see where the drivers are located.
Click to expand...
Click to collapse
Update: Yep it's located in /system/lib/modules
Upon quick look it appears as though the permissions for the .ko file might be incorrect. Let me try something to see if it helps.

jlevy73 said:
Update: Yep it's located in /system/lib/modules
Upon quick look it appears as though the permissions for the .ko file might be incorrect. Let me try something to see if it helps.
Click to expand...
Click to collapse
Your right, this could maybe be the problem.

jlevy73 said:
Kernel boots fine, however,it breaks wifi. Will continue testing and see how everything else it
Click to expand...
Click to collapse
Getting the same wifi problem.
But besides that everything seems to be working fine.

Tried playing around with the permissions but that didn't seem to help. Also BT appears to be break with this kernel.

Also confirmed wifi is broken with this kernel.

flak0 said:
Also confirmed wifi is broken with this kernel.
Click to expand...
Click to collapse
Can you try turning on BT and seeing if that's broken for you as well? Thanks

Is dmesg spitting out anything of interest?

Confirmed. I wonder if we push the original wireless.ko if.it will work?

Since i do not have the device, if someone wants to continue the work you'll find the sources and changes here : https://github.com/Cpasjuste/android_kernel_lg_p999/commits/fakeShmoo
Note that you NEED to add "init.d" support to the kernel initramfs :
Add at the end of the init.rc script :
Code:
# Execute files in /etc/init.d before booting
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
And maybe the "99complete" script to "/system/etc/init.d" :
Code:
#!/system/bin/sh
sync;
setprop mcr.filesystem.ready 1;

Checking dmsg now

I can also confirm that the kernel works well with OC/UV but WiFi does not work. Bluetooth isn't working for me either.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

OC'd @ 1.7ghz but still shows 1.5ghz

I'm running ARHD 7.3 and also flashed the Sultan Kernel (this) but Android is still showing 1.5ghz in the "about phone" section.
Do I need to flash the kernel before I install the ROM?
thx in advance:laugh::good:

It is so. You can't do nothing about it. Some kernel devs modify that value and write 1.8GHz for example it was on SebastianFM's Overclocked kernel if I remember correctly.
And remember, flashing a kernel before flashing a ROM is like pushing the gas pedal of a car before starting the engine.
Plus, when you flash the ROM, it will replace your kernel with its own.
The Revelation™ ushered in a revolution... Right on, SebastianFM!

Anti_simlock said:
I'm running ARHD 7.3 and also flashed the Sultan Kernel (this) but Android is still showing 1.5ghz in the "about phone" section.
Do I need to flash the kernel before I install the ROM?
thx in advance:laugh::good:
Click to expand...
Click to collapse
don't look what says in about phone
about phone takes the info from the build.prop file(if i am not wrong)
to see your current freq use setcpu,kernel tuner or system tuner
also do a test with antutu benchmark and it will show you your current cpu freq in the results

rzr86 said:
about phone takes the info from the build.prop file(if i am not wrong)
to see your current freq use setcpu,kernel tuner or system tuner
also do a test with antutu benchmark and it will show you your current cpu freq in the results
Click to expand...
Click to collapse
+1
Anti_simlock said:
I'm running ARHD 7.3 and also flashed the Sultan Kernel (this) but Android is still showing 1.5ghz in the "about phone" section.
Do I need to flash the kernel before I install the ROM?
thx in advance:laugh::good:
Click to expand...
Click to collapse
If you want to change what shows up in about phone, mount system as rw, open /system/build.prop in a text editor. Scroll down and you'll see a section named about phone. Edit whatever you want.
Happy to help.

[Q] CPU's rude frequencies

Hello xda!
Theres something strange going on with my Sensation..
I can not set up my own frq's.
Everytime I set some it goes higher. For example..
I am @ 1080-475 I switch the window to set some profiles and back to the main. bah.. Current max: 1134.. 1450.. 1552.. 1134.
Bar I set before should lock it @ 1080 and it does but just in practice.
I was trying to set some other governors with no succes. It goes higher everytime.
Root acces was given, ROMs tested.
I got phone from my brother. Is it even possible to change some hardware settings or wtf is it that block my ideas????

Lynxen said:
Hello xda!
Theres something strange going on with my Sensation..
I can not set up my own frq's.
Everytime I set some it goes higher. For example..
I am @ 1080-475 I switch the window to set some profiles and back to the main. bah.. Current max: 1134.. 1450.. 1552.. 1134.
Bar I set before should lock it @ 1080 and it does but just in practice.
I was trying to set some other governors with no succes. It goes higher everytime.
Root acces was given, ROMs tested.
I got phone from my brother. Is it even possible to change some hardware settings or wtf is it that block my ideas????
Click to expand...
Click to collapse
what rom do you have?
insert this line in init.qcom.post_boot.sh file
echo the value > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
in the <the value> put your desired freq
do the same for cpu1
then reboot
note: put the lines where it starts with :
case "$target" in
"msm8960")

rzr86 said:
what rom do you have?
insert this line in init.qcom.post_boot.sh file
echo the value > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
in the <the value> put your desired freq
do the same for cpu1
then reboot
note: put the lines where it starts with :
case "$target" in
"msm8960")
Click to expand...
Click to collapse
I am using SlimKat and Viper. Same bug excist @ both of the roms. Kernels provided with shantur, sebastian and libelty are bugged.
I've changed those values with no results. Once I was trying to set maxcpu_info my root explorer stucked @ saving process. Sth was remaking values @ 1540000 mhz just after rootacces was given to explorer. Some deep **** is going down there.
That's why Sensations are overheating, it's same bug threw all stock kernels/rom @ this forum.
Max values can not be set! They re permanent for some reason - failed coding I suppose.
Libelty Kernel fix Vipers issues. There's no kernel working with KK.

Lynxen said:
I am using SlimKat and Viper. Same bug excist @ both of the roms. Kernels provided with shantur, sebastian and libelty are bugged.
I've changed those values with no results. Once I was trying to set maxcpu_info my root explorer stucked @ saving process. Sth was remaking values @ 1540000 mhz just after rootacces was given to explorer. Some deep **** is going down there.
That's why Sensations are overheating, it's same bug threw all stock kernels/rom @ this forum.
Max values can not be set! They re permanent for some reason - failed coding I suppose.
Libelty Kernel fix Vipers issues. There's no kernel working with KK.
Click to expand...
Click to collapse
liberty's and sebastianFM's kernel aren't bugged
i have changed cpu frequencies successfully
in vipers rom disable pnpmanger from venom tweaks
then put your desired cpu freq
about slimkat rom i can't tell you somethig because i have never used that rom
also in stock kernels you can't changed nothing
they do not support overclock or underclock

rzr86 said:
liberty's and sebastianFM's kernel aren't bugged
i have changed cpu frequencies successfully
in vipers rom disable pnpmanger from venom tweaks
then put your desired cpu freq
about slimkat rom i can't tell you somethig because i have never used that rom
also in stock kernels you can't changed nothing
they do not support overclock or underclock
Click to expand...
Click to collapse
It's possible to scale CPU frequency in slimkat ROM too.

Deleted

Old thread.

You're the best, mate

minimale_ldz said:
You're the best, mate
Click to expand...
Click to collapse
Much appreciated and hope you all find it usefull to use. Just saw soniCron released a new script called "hawktail" based on a total different technique using an extreme low timer_rate. Shall try to translate that also next week and if it works ill add this in the thread.

Make a donation link. We love you.

Hi guys! And thanks for your work, @Sickaxis79!
A noob question here. Could these scripts be applied to another governor? Precisely, impulse which is supposed to be similar to interactive?
Sent from my XT1562 using Tapatalk

stazz83 said:
Hi guys! And thanks for your work, @Sickaxis79!
A noob question here. Could these scripts be applied to another governor? Precisely, impulse which is supposed to be similar to interactive?
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
Im afraid that ain't possible. Impulse governor use some different tunables, but you can for example use one interactive script for the big or small cpu and use impulse governor for the other cpu.

Applied the two profiles with latest squids kernel and cm13. Working Great so Far. I guess i have to manually disable touchboost everytime?

Leni_YO said:
Applied the two profiles with latest squids kernel and cm13. Working Great so Far. I guess i have to manually disable touchboost everytime?
Click to expand...
Click to collapse
Yes, its best to disable touchboost. Touchboost is a kernel/rom extra feature. Im also using latest squid kernel with stock rom and dont have this feature and forgot to disable it by default. I will check if i can update the script so its also disables touchboost. Im used to create and edit init.d scripts, but json files k.a. uses are a total different language, but ill try.

Master Mike, how are these scripsts working with optimized init.qcom.post_boot.sh you posted once. Should it be restored to default/stock one or can it all work together? Thanks

minimale_ldz said:
Master Mike, how are these scripsts working with optimized init.qcom.post_boot.sh you posted once. Should it be restored to default/stock one or can it all work together? Thanks
Click to expand...
Click to collapse
No problem. Post_boot script contains the stock settings and applies them first when the phone startup.

Sickaxis79 said:
No problem. Post_boot script contains the stock settings and applies them first when the phone startup.
Click to expand...
Click to collapse
Is KA changing them after boot anyway if it's got some scripts applied?

minimale_ldz said:
Is KA changing them after boot anyway if it's got some scripts applied?
Click to expand...
Click to collapse
Reboot reverts all stock settings unless you enable the checkbox "on boot". It will always first launch your normal stock settings and after the phone finished starting up it will launch the k.a. scripts.In the settings menu you can set the timer how many seconds after boot the scripts will launch.
You can always launch them manually when you dont want to apply them on boot. Just tap on the 2 scripts you imported and it will ask to launch them and finished.
Edit: K.a. overwrites the normal stock settings after youre phone booted temporarily.

Sickaxis79 said:
Reboot reverts all stock settings unless you enable the checkbox "on boot". It will always first launch your normal stock settings and after the phone finished starting up it will launch the k.a. scripts.In the settings menu you can set the timer how many seconds after boot the scripts will launch.
You can always launch them manually when you dont want to apply them on boot. Just tap on the 2 scripts you imported and it will ask to launch them and finished.
Edit: K.a. overwrites the normal stock settings after youre phone booted temporarily.
Click to expand...
Click to collapse
Got it, thanks

Can't import ghostpepper profiles, k.a. says the file is malformed. Great work btw, keep it up.

too bad i have the free version ...

thanks for your work, the script works very well in resurrection rom and optimus kernel, can someone upload the stopperfd script? the KA doesnt work for me creating the script

I've reached over 7hrs SOT on the first run after applying the profiles with 75% Charge left. Good job!

zenez said:
thanks for your work, the script works very well in resurrection rom and optimus kernel, can someone upload the stopperfd script? the KA doesnt work for me creating the script
Click to expand...
Click to collapse
You can also do this using a terminal emulator
Type: "su" (root permission) and "stop perfd".

Sickaxis79 said:
No problem. Post_boot script contains the stock settings and applies them first when the phone startup.
Click to expand...
Click to collapse
Thanks for answering for me.

ViperX85 said:
Can't import ghostpepper profiles, k.a. says the file is malformed. Great work btw, keep it up.
Click to expand...
Click to collapse
BUMP