Llama Sweet Kernel Tweaks

[joaste]

15/02/2017
changed back to cfq scheduler.

Added cfq scheduler tweaks;
This time LG G4 executes and multitask faster even with a very low cpu profile.

(you will notice a big difference when opening-closing apps and when apps load tasks. A noticable easy example is at settings -> apps. We used to wait a couple of seconds, now we don't wait any more)

~EDIT: i also recommend my new cfq tweaks on your linux. I'm testing them since a week and i have a great difference in speed

@kessaras
I'm back on crdroid from imperium, and installed the latest llama kernel and your script (which I had used before on both stock and CM 14 based ROMS).

The strange thing is after boot, some parameters do not seem to be applied, like cfq as i/o scheduler, min 3 cores online, etc. However, it seems that some things are being applied such as turning on the mpdecision hotplug (which funnily enough I could not get to work with just crdroid and llama using Kernal Adiutor - only the first hotplug would work) .

Any ideas? I'm a bit stumped on this one

Any help would be much appreciated!

thanks

 

[kessaras]

@kessaras
I'm back on crdroid from imperium, and installed the latest llama kernel and your script (which I had used before on both stock and CM 14 based ROMS).

The strange thing is after boot, some parameters do not seem to be applied, like cfq as i/o scheduler, min 3 cores online, etc. However, it seems that some things are being applied such as turning on the mpdecision hotplug (which funnily enough I could not get to work with just crdroid and llama using Kernal Adiutor - only the first hotplug would work) .

Any ideas? I'm a bit stumped on this one

Any help would be much appreciated!

thanks

Will check it within two days. I haven't updated my rom since a month. I'll update and check.

 

[kessaras]

@joaste
i'm on cr 2.2 and llama right now and everything applies successfully. i don't see any problem here. something else you did wrong.
since i updated i'll stay with this rom a couple of days so we will find the problem.

What i did:
lineage 13 (old)
twrp > nandroid backup (so i can restore later)
advance wipe > system , data, cache , dalvik-cache
reboot to twrp
flash rom , kernel > reboot
~waiting~ > enabling su from settings and push script in init.d
installing a simplified busybox , because crdroid doesn't have it installed
reboot to twrp
flash aroma gapps , i prefer it because it debloats the rom at the same time > reboot
done

 

[tachiquan3]

Does anyone here knows how to online 2 little cores and 2 big cores only?

 

[kessaras]

Does anyone here knows how to online 2 little cores and 2 big cores only?

you can't.
That's something decided by the drivers for the CPU coming from LG.
The big cores get online when the small cores have a x% load or bigger and then they automatically get offline again.

Also if we don't use the hotplug, the same thing happens.
The big cores get a load when the small cores have a x% load or bigger.

So basically small cores do everything and the big ones get to do only the "very hard work".

~EDIT: your reason is what ? why do you want to turn the phone into a quad core ?
The only way is to turn it into a dual core and the big ones will come online/offline depended to the load. That will cause you huge lag and the phone will be super slow.
I can make a script for you if you really wanna turn it into a dual core
i checked it now, it can only be dual core with only 1 big core always on. not 2.
If you want something like that, tell me.

 

[tachiquan3]

Thanks for the fast reply. Yea youre right, big cores doesnt really care about little's load. What i did was i made a script to online 3 little cores and 1 big core only if needed. ?

 

[kessaras]

Thanks for the fast reply. Yea youre right, big cores doesnt really care about little's load. What i did was i made a script to online 3 little cores and 1 big core only if needed. ?

Yup that works. Also 2 + 1 is possible.

 

[tachiquan3]

Naah 2 cores lags. Anyway thanks i made a script for gpu and adreno idler. Now i wont use kernel manager apps hehe. ?

 

[joaste]

@joaste
i'm on cr 2.2 and llama right now and everything applies successfully. i don't see any problem here. something else you did wrong.
since i updated i'll stay with this rom a couple of days so we will find the problem.

What i did:
lineage 13 (old)
twrp > nandroid backup (so i can restore later)
advance wipe > system , data, cache , dalvik-cache
reboot to twrp
flash rom , kernel > reboot
~waiting~ > enabling su from settings and push script in init.d
installing a simplified busybox , because crdroid doesn't have it installed
reboot to twrp
flash aroma gapps , i prefer it because it debloats the rom at the same time > reboot
done

Thanks. I didn't install busybox. Could that be the issue?

Will try again when I get à chance.

 

[MaxFluteHD]

@joaste
i'm on cr 2.2 and llama right now and everything applies successfully. i don't see any problem here. something else you did wrong.
since i updated i'll stay with this rom a couple of days so we will find the problem.

What i did:
lineage 13 (old)
twrp > nandroid backup (so i can restore later)
advance wipe > system , data, cache , dalvik-cache
reboot to twrp
flash rom , kernel > reboot
~waiting~ > enabling su from settings and push script in init.d
installing a simplified busybox , because crdroid doesn't have it installed
reboot to twrp
flash aroma gapps , i prefer it because it debloats the rom at the same time > reboot
done

This Picture on the end of your post, where did you get this information?

 

[kessaras]

This Picture on the end of your post, where did you get this information?

Logcat.
But instead using just logcat and then trying to adjust my eyes to find what I need, I used
adb logcat > logcat.txt
Or if I didn't have A PC, from the phone terminal:
logcat > /sdcard/logcat.txt

Then I open the txt file and I easy search and find what I need

 

[joaste]

@joaste
i'm on cr 2.2 and llama right now and everything applies successfully. i don't see any problem here. something else you did wrong.
since i updated i'll stay with this rom a couple of days so we will find the problem.

What i did:
lineage 13 (old)
twrp > nandroid backup (so i can restore later)
advance wipe > system , data, cache , dalvik-cache
reboot to twrp
flash rom , kernel > reboot
~waiting~ > enabling su from settings and push script in init.d
installing a simplified busybox , because crdroid doesn't have it installed
reboot to twrp
flash aroma gapps , i prefer it because it debloats the rom at the same time > reboot
done

Well I just tried again with RR.

Same thing happens. CFQ does not get applied. Hotplugging does though.

Edit: Westwood is not being set either

Edit2: just tried 90less - alucard and hotplugging are set, but not the I/o scheduler and its parameters. Westwood is not set either.

 

[kessaras]

Well I just tried again with RR.

Same thing happens. CFQ does not get applied. Hotplugging does though.

Edit: Westwood is not being set either

Edit2: just tried 90less - alucard and hotplugging are set, but not the I/o scheduler and its parameters. Westwood is not set either.

H811 or H815 and which rom build and which llama are you flashing?
Init.d did have issues but on an older build and I think genesix fixed that on his last build.

Also when you moved from imperium to aosp did you wipe system and data?

There isn't much I can do, I don't know exactly what you are doing wrong.
The file paths in the script are 100% correct, all of them. If you execute it in adiutor (remove the sleep timer that waits for the rom to boot first) , you will see that everything applies.

So either there is another script in init.d that interfere with this script, either you didn't wipe before flashing rom and kernel and gapps , either you flashed older kernel build. Only those 3. Nothing else comes to my mind.

 

[joaste]

H811 or H815 and which rom build and which llama are you flashing?
Init.d did have issues but on an older build and I think genesix fixed that on his last build.

Also when you moved from imperium to aosp did you wipe system and data?

There isn't much I can do, I don't know exactly what you are doing wrong.
The file paths in the script are 100% correct, all of them. If you execute it in adiutor (remove the sleep timer that waits for the rom to boot first) , you will see that everything applies.

So either there is another script in init.d that interfere with this script, either you didn't wipe before flashing rom and kernel and gapps , either you flashed older kernel build. Only those 3. Nothing else comes to my mind.

Sorry for that.

H815
RR -09-02-2017 build (by tylerdurden)
Llama R7.2N from 09-02-2017

I just tried executing the script through KA init.d emulator and that works. However again, most things do not apply on boot, even with KA. I need to run the script manually through KA.

There are only the 90userinit and 00banner scripts in the init.d folder, in addition to the 90less script.

I'll update the RR build now to the latest (19-02-2017).

Thanks for you help!

 

[kessaras]

Sorry for that.
H815
RR -09-02-2017 build (by tylerdurden)
Llama R7.2N from 09-02-2017
I just tried executing the script through KA init.d emulator and that works. However again, most things do not apply on boot, even with KA. I need to run the script manually through KA.
There are only the 90userinit and 00banner scripts in the init.d folder, in addition to the 90less script.
I'll update the RR build now to the latest (19-02-2017).
Thanks for you help!

ok thats wierd. do in terminal

adb shell
su
. ./system/etc/init.d/90less

and gimme the result please.

~EDIT: download now my latest and test it. it hasn't any change as far as your problem, it has other fixes.

 

[joaste]

ok thats wierd. do in terminal

adb shell
su
. ./system/etc/init.d/90less

and gimme the result please.

~EDIT: download now my latest and test it. it hasn't any change as far as your problem, it has other fixes.

I'll have to try this later as I'm at work now.

Was also going to try switching to the RR build from genesix but will do your thing first when I get a chance.

Stay tuned!

Thanks again!

 

[kessaras]

This information is for everyone.

With the new systemless root method we can install our scripts, including this one of course, in /system/su.d.
This has an advantage.
The 90balanced script here will work for the stock lineage or stock MM LG kernel. Ok some tweaks will be missing, like the westwood tcp algorithm and a few more, but you will still gain a slim better battery life and performance. Have fun.

 

[joaste]

This information is for everyone.

With the new systemless root method we can install our scripts, including this one of course, in /system/su.d.
This has an advantage.
The 90balanced script here will work for the stock lineage or stock MM LG kernel. Ok some tweaks will be missing, like the westwood tcp algorithm and a few more, but you will still gain a slim better battery life and performance. Have fun.

Thanks kessaras.

I'm now on AICP with Llama. Putting the 90balanced script in the normal init.d folder works fine but putting it in the su.d folder under /system does not work for me.

 

[tachiquan3]

Nice

 

[marn3us]

Hi @kessaras, thanks for your work!

I have a quick question: my AOSP-based rom already has a script called "90userinit" in the init.d folder, is it still ok to use your scripts?