yashsingh1/xdaforums huggingface dataset:
[X Play Original Android Development] PSxplay:
Support 6.0?

Will this kernel work with my Moto x play 6.0 ??
[X Play Original Android Development] Encrypter17:
Yes
[X Play Original Android Development] kingsizeriz:
Is there any way to reduce vibration intensity with this kernel? Currently using the r15 oc version. Very smooth.
[X Play Original Android Development] PSxplay:
which kernel version should i use?

Moto x play 6.0

squid_kernel_r15-lux-oc.zip

or

squid_kernel_r15-lux.zip
[X Play Original Android Development] Benjamin_L:
Both work and OC offers overclocking
[X Play Original Android Development] PSxplay:
Root guide

I want to root my xplay 6.0

Need a guide for it
[X Play Original Android Development] Benjamin_L:
In the general section there is a guide
[X Play Original Android Development] PSxplay:
Can i flash this kernel without twrp or it is must?and can i use my preloaded recovery for installing kernel?
[X Play Original Android Development] joyousfrank:
You could try, but as the OP says it's intended to be flashed in TWRP you probably should do it that way, in fact it's really easy.
[X Play Original Android Development] PSxplay:
can you explain me how??

---------- Post added at 03:28 PM ---------- Previous post was at 03:09 PM ----------

I am done with kernel flashing now how to enable notification led ???????

---------- Post added at 04:07 PM ---------- Previous post was at 03:28 PM ----------

Guys i am not able to switch on led light. Help please
[X Play Original Android Development] Benjamin_L:
How about taking some time to read and try before asking? Please. And tell us which rom you are using etc. Without any information no one can help.
[X Play Original Android Development] PSxplay:
Official MM 6.0

Kernel version r15

I have installed it via Twrp recovery. And in kernel version it is showing the right version,but in display option there is no option to toggle led light. I still cant figure out where is the problem. Hope you guys will try to help this thing figure out.

Ty
[X Play Original Android Development] Benjamin_L:
There's no way in stock to control the led. Apps which offer settings for led notifications can be used to setup the led for those apps. Otherwise there is no way. For SMS/messenger it should just work
[X Play Original Android Development] pijes:
When you flash squid kernel the notification led should work automatically.
[X Play Original Android Development] shanthasorooban:
What's the last kernel update version for Lollipop? r11e?
[X Play Original Android Development] dictionary:
Yes.
[X Play Original Android Development] Lennyz1988:
Is it normal for Kernel Auditor to disable the little cores as disabled? I'm running the latest squid oc.
[X Play Original Android Development] LuizHenrique91:
Please search on the thread.

Enviado de meu XT1563 usando Tapatalk
[X Play Original Android Development] Lennyz1988:
Sure I will do that if you can give me the words to search for.

Cores disabled doesn't give me any results, neither does the last 5 pages of this thread.
[X Play Original Android Development] LuizHenrique91:
"Little cores"

Enviado de meu XT1563 usando Tapatalk
[X Play Original Android Development] PSxplay:
R15 version stable with cm12.1?
[X Play Original Android Development] Benjamin_L:
.... Read the op. Latest 5.1 release is 11
[X Play Original Android Development] bartolaki:
Is there any easy way to disable led notification on squid kernel? I love this kernel but led notification is just too bright for me and want to turn it off completely...

Thanks
[X Play Original Android Development] b00tbu9:
I use xposed module Xled to disable it for each app
[X Play Original Android Development] Ajeyvm:
Hi.. Currently I'm using r11e build on lollipop.. Is it safe to flash r15oc build?? (MXP 5.1)
[X Play Original Android Development] kup0:
No. 11 is last build for lollipop

Lähetetty minun XT1562 laitteesta Tapatalkilla
[X Play Original Android Development] Darzon:
Can people take just 2 minutes to read the first post instead of asking the same stupid questions all over again ?!

Use Phoenix kernel if you want oc on lollipop.
[X Play Original Android Development] Ajeyvm:
You might feel its stupid.. But I wanted confirmation, double check.. Chillax..
[X Play Original Android Development] dictionary:
Why, when you can just read the original post, which clearly states the answer. Or, do a thread search. It's even mentioned three posts above your initial question ...
[X Play Original Android Development] Ajeyvm:
Sorry for wasting your time guys! Woof so serious! Feeling like I did a terrible mistake.. I was flashing r15oc for my dad's MXP 6.0, I didn't read thread info, posted in a hurry.. Thanks for the quick response from kup0, I didn't flash to LP...
[X Play Original Android Development] anks095:
I flashed thid 15-oc kernel on Stock LP and everything was smooth except I lost my network functionality.if somehow this network problem can be removed then the kernel is the best.
[X Play Original Android Development] XxMikeMasterxX:
.......wow.
[X Play Original Android Development] blankingblank:
Oh... Bless ur heart..
[X Play Original Android Development] alresave:
Maybe you could try flashing the latest version made for LP (as other users already told you, all the info is on the OP). I think your network issue will be magically removed and the kernel will be the best.
[X Play Original Android Development] dev>null:
led on|off

[MENTION=6485916]squid2[/MENTION] Thank you for this great work, man! It really makes a difference.

Any chance you're planning in a future release to add a terminal command for switching led on|off ?

:angel:
[X Play Original Android Development] AtomicStryker:
Xposed / Gravitybox allows you to disable the LED if you so desire
[X Play Original Android Development] dev>null:
I know, but wanted to stay as stock and light as possible, without running additional modules and services ;)
[X Play Original Android Development] effingbadluck:
Can I flash this directly over ultra kernel?
[X Play Original Android Development] dev>null:
Sure. When you flash a kernel it overwrites the old one :good:
[X Play Original Android Development] XxMikeMasterxX:
I'm having some trouble getting LITTLE cluster values to stick on the lionfish governor.

I've noticed that the jump_level frequencies in the LITTLE cluster tunables section are identical to the BIG cluster frequencies so I'm wondering if maybe the LITTLE cluster is somehow confused with the BIG cluster and thus gets reset after a few minutes' use. I find the reset happens after the screen turns off and the device enters sleep or a reboot is performed.

I'm using Kernel Auditor 4.7 (latest from Play Store). Thanks for all support.
[X Play Original Android Development] dev>null:
[MENTION=6485916]squid2[/MENTION] is it possible to add init.d support in the future ? it would be great. Thank you again !!!
[X Play Original Android Development] cainacg:
same happens here, squid's kernel seems to be confused with the Kernel Aduitor, since older/previous builds of kernel. I dont know if this is a kernel bug or Kernel Aduitor bug.
[X Play Original Android Development] XxMikeMasterxX:
Yeah. I'd love to make the settings stick. I want the jump level higher than 800 MHz! 1.13 GHz please!
[X Play Original Android Development] K.khiladi:
Just saw this issue. Cpu tunables return to original for little cores after sometime.
[X Play Original Android Development] Sickaxis79:
I only have this issue using cm12.1 or cm13. Using stock and the issue is gone.
[X Play Original Android Development] XxMikeMasterxX:
Really, eh? Hm. For some reason it isn't working for me and a few others. Do you have any suggestions? What version of Kernel Auditor are you using, or are you using a different app?
[X Play Original Android Development] Sickaxis79:
Im also using Kernel Adiutor, but you can also try Trickstermod. I just returned to stock ROM because of this little kernel issue.Using the same kernel with stock rom and everything works fine again.
[X Play Original Android Development] XxMikeMasterxX:
Damn that's my setup, too - stock ROM 6.0 and squid r15 OC. Are you also using r15-OC?

I might try to revert to r15 and see if that helps. I don't use the OC frequencies anymore anyway.
[X Play Original Android Development] Sickaxis79:
Last week I used r15 and r15oc with stock mm and it worked without problems. Im now downgraded to lollipop stock again and using r11e.I don't know if it's kernel,rom or Kernel Adiutor related, but all kernels I tried with cm12.1 and cm13 had problems with the little cores that reverted to interactive and CPU settings that won't stick.
[X Play Original Android Development] squid2:
Most likely the issue is that you can't change the configuration of the little cluster when it is offline. During the bootup process for CM13, it disables clusterplug, onlines all cores, configures all cores, then enables clusterplug again. If you change certain little cluster settings while it is offline, setting changes won't work.

The proper process to configure the little cluster would be to disable clusterplug, activate all cores, change configuration, then reactivate clusterplug. Yes, I understand this is a bit awkward. I suppose you can script it.

You won't notice this on the stock ROM because it keeps all cores online (clusterplug is disabled by default).
[X Play Original Android Development] Sickaxis79:
That's some intresting info. Thanks for the explanation and great to hear it's normal for this moment. This explains a lot for me and others. :)
[X Play Original Android Development] Chaninoza:
isnt working here neither (Stock MM XT1563 with squid kernel 15oc)
[X Play Original Android Development] XxMikeMasterxX:
Hey [MENTION=6485916]squid2[/MENTION] -

Thanks for explaining the clusterplug functions, but I am still experiencing the LITTLE cluster reset on the stock MM 6.0 ROM. I'm using Kernel Auditor, but perhaps another kernel app would resolve the issue. Do you have any recommendations?

I guess I'll try r15 in the meantime (no OC) and see if that works. Perhaps I'm just one of the unlucky ones. :P

Any thoughts from you would be appreciated, squid.

MM 6.0

r15-OC

Stock everything else (Canada firmware)
[X Play Original Android Development] blankingblank:
Fwiw I'm on stock rom with stock kernel and never experienced this issue using kernel adiutor. Only tried ondemand besides interactive but no problems with the app getting the governor to stick on my end. Is it happening with all governors, or just lionfish?
[X Play Original Android Development] XxMikeMasterxX:
Good question. I think I've only experienced it in lionfish. As I mentioned in an earlier post, there's the option to change the jump_level to 1708 which is obviously above and beyond the LITTLE cluster's range so I originally thought there was some confusion in there.

I'm really licked with this one - I don't know what to do. I just tried r15 and it's the same...
[X Play Original Android Development] squid2:
Configuring the little clusters works fine when done correctly. Nothing is mixed up. The 1708 MHz option showing in Kernel Adiutor for the little cluster is a bug of sorts in the app. The governor itself doesn't provide any such options.

Try running the following commands in a shell:

echo 0 >/sys/module/cluster_plug/parameters/cluster_plug_active
echo 1 >/sys/devices/system/cpu/cpu4/online
chmod 0644 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo lionfish >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 0644 /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor
echo lionfish >/sys/devices/system/cpu/cpu4/cpufreq/scaling_governor
echo 1113600 >/sys/devices/system/cpu/cpu0/cpufreq/lionfish/jump_level
echo 998000 >/sys/devices/system/cpu/cpu4/cpufreq/lionfish/jump_level

The settings you put in will be applied.

Now, one thing that will happen is that if a full cluster is ever taken offline (as is done by clusterplug or sometimes by perfd in the stock ROM), the current architecture of the kernel will invoke destructors for the cluster's governor. When the core is reactivated, the kernel will initialize a new governor. This causes the settings of the governor to be reset. Most likely this is what you were noticing. This is not a bug in lionfish - this will happen with any governor as a result of the kernel's handling of big.LITTLE systems. It's a "feature" and not a "bug", though it is a rather annoying feature for this case.

I may look at changing the way the kernel handles governors for hotplugged big.LITTLE clusters at some point in the future, but for now, whenever the little cluster is taken down, it's governor will be destroyed, and then reinitialized when the cluster is activated.
[X Play Original Android Development] XxMikeMasterxX:
[MENTION=6485916]squid2[/MENTION]

Excellent explanation. Thanks so much. I initially wanted to verify that this pattern of re-initialization was happening with others in case I had done something to my kernel somehow. Please don't feel that it was a critique of any kind.

I will certainly run the commands I'm a shell. I don't recall the LITTLE sister ever going offlne, even in perfd, but evidently it does occasionally.

Thanks for considering readjusting it in future builds, squid, but obviously it isn't s high priority. Thanks again.
[X Play Original Android Development] squid2:
Adopted Storage

After many hours of debugging, I was able to track down the issue with Adopted storage on lux. It ended up having nothing to do with the f2fs update.

When I updated the some of the crypto code from Linux 4.4, it introduced the concept of internal ciphers (private kernel ciphers not meant to be used by normal external APIs). The new ARMv8 crypto routines I introduced were internal ciphers. They happened to have the same priority as the Qualcomm hardware crypto. By chance, MSM8916 devices happened to settle on Qualcomm ciphers, while MSM8939 devices settled on the ARMv8 ciphers.

The Qualcomm crypto drivers were not marked as internal and worked as usual. The new ARMv8 crypto drivers were marked as internal. The higher level cryptd driver had not been updated to permit the use of internal ciphers. As a result, the crypto engine would fail to initialize when the ARMv8 engine was selected.

I've now updated cryptd to allow the use of internal ciphers. This fixes support for adopted storage on lux. I've also bumped up the priority of the ARMv8 crypto to ensure it is always selected when possible over the slower Qualcomm crypto. As an added benefit, you will now get to make use of the new faster ARMv8 crypto instructions for adopted storage.
[X Play Original Android Development] squid2:
Squid Kernel r15b

This is a maintenance release for the r15 series. I've merged in Linux 3.10.98, bringing with it associated security and stability fixes. I've also corrected an issue that prevented the ARMv8 crypto features I added in the last release from working properly. I have raised the priority of ARMv8 crypto in the kernel so that it is now the preferred crypto engine for use by the Marshmallow adopted storage feature. Regular full disk encryption will continue to use Qualcomm's (slower) hardware encryption engine as that is dictated by the configuration of the ROM.

This build should fix adopted storage on lux.
[X Play Original Android Development] lehoule:
I have to ask, do you plan on keeping an oc'd version of each release?

That small overclock changed my life.
[X Play Original Android Development] squid2:
The r15b includes the overclock. All releases for lux from now on will keep the slight overclock as it does improve performance measurably and I haven't noticed any significant impact on heat or battery life.
[X Play Original Android Development] lokesh.acm:
Man this kernel is doing great for me. Happy I rooted. Thanks for the kernel. On its default settings I get more battery than the stock one. Thanks a lot???
[X Play Original Android Development] Karanso:
Kernel r15b freeze Boot Logo,

back to Kernel r15 oc - works fine
[X Play Original Android Development] stazz83:
Flashed 15b over the 15oc version and wiped cache and dalvik afterwards. The phone booted properly and seems it's all working well here.
[X Play Original Android Development] Benjamin_L:
All fine here in crDroid
[X Play Original Android Development] LuizHenrique91:
I just flashed the r15b over the r15-oc. Didn't clean anything and it worked.

Enviado de meu XT1563 usando Tapatalk
[X Play Original Android Development] droider007:
Sorry for offtopic....but can anyone do this for x play? [MENTION=6485916]squid2[/MENTION]

http://xdaforums.com/showthread.php?p=63908047
[X Play Original Android Development] manan001:
Flashed latest 15b kernel every thing working well..
[X Play Original Android Development] TheLaptopClick:
I know others have asked this question, but how do you enable the LED notification light? I'm running stock MM with r15b
[X Play Original Android Development] lokesh.acm:
I flashed r15oc and the led was on by default.
[X Play Original Android Development] manan001:
For stock you need to use some app. You can check it in play store
[X Play Original Android Development] lokesh.acm:
I use stock ROM. I got the led without the app :)
[X Play Original Android Development] TheLaptopClick:
Strange how it doesn't work for me, even with Light Flow and Light Flow Legacy installed...
[X Play Original Android Development] lokesh.acm:
Sorry buddy. No idea :(
[X Play Original Android Development] live4speed:
Really liked this kernel & the additional features it brings to my device like notification light, OC, UC, UV etc. Absolutely fantastic ?? ?
[X Play Original Android Development] saintsimon:
Hmm, my MXP got noticeably hotter with OC, so I went back to regular kernel. :/
[X Play Original Android Development] Benjamin_L:
Which rom? Mine is not any different to non-oc
[X Play Original Android Development] joeanca:
I experienced some heating issues as well, but it is always smart to let the kernel settle a few hours and even a few days. As of now now overheating on 15b + temaske's 02-28s build. Thanks squid!
[X Play Original Android Development] saintsimon:
Stock ROM and more than a week after install, I moved back to regular clocking. That is good enough.
[X Play Original Android Development] squid2:
If you don't like the overclock, you can always turn down the max frequency one step.
[X Play Original Android Development] pijes:
from my experience, for normal usage (no games), running at 1.3ghz max is more than enough.
[X Play Original Android Development] lokesh.acm:
I've set the big cores to max 1113mhz and 200 is the min. Little cores are off expect one which has the max @998mhz. GPU [MENTION=1989751]400[/MENTION]mhz and low mem killer is set to 'low' .. No problems in browsing, taking pictures, switching between apps, typing, calling or running day to day apps but while gaming ( pacman, temple run and beach buggy) I see slight performance drops here and there and that's when I enable all the little cores (same frequency). Graphics are set to the max. No performance issues so far. Multitasking also great. ☺ :thumbup:
[X Play Original Android Development] blankingblank:
Just wanna say thanks for the kernel, Squid... latest version is running great.

Quick question also, is there a way to change the led blinking duration via terminal, maybe? I tried light manager, but it's not worth having an extra background service running for something so minor
[X Play Original Android Development] ronak123456:
I just flashed the latest kernel squid_kernel_r15b-lux.zip and I am finding it funny to explain but thats what it has happend lol..

I am using bliss 6.0.1 ROM

I flashed this kernel, everything worked fine till i went to the kernel auditor app.

Now what i see was the BIG are offline and disabled and little are working ( also, there is only interactive option available, and when i tap on it to change..it just show blank box, so there is no other option to chose )

After sometime, my Big are working and little went offline LOL..!!

Still cant find option to change from interactive or lionfish etc....!!
[X Play Original Android Development] ShlCar347:
Thanks for this latest update. It fixed the Adopted Storage bug, and it works very well. Thank you so much!!
[X Play Original Android Development] Lavesh05:
i am on stock mm and have flashed dis kernel. i want to revert back to stock kernel. how to do that???
[X Play Original Android Development] K.khiladi:
There was a flashable stock kernel zip available but I don't know who made it.

Moreover this kernel changes something related to wifi, so don't know if after flashing stock kernel everything will work fine.
[X Play Original Android Development] Lavesh05:
cant find that stock kernel zip :(
[X Play Original Android Development] droider007:
If you flash stock kernel....your wifi will stop working......flash whole stock rom again..
[X Play Original Android Development] lokesh.acm:
[MENTION=6485916]squid2[/MENTION] Some help here? My battery is currently @26% and the big cores have turned off and I couldn't force start them. Any idea how I can enable them? Or is it just not possible?
[X Play Original Android Development] live4speed:
How about restoring TWRP backup? Will wifi work then?
[X Play Original Android Development] LuizHenrique91:
If the backup was only of /boot, i think it won't work. You might restore a backup of /boot and /system.
[X Play Original Android Development] XxMikeMasterxX:
Keep looking on the forum. I know there is a stock flashable zip somewhere. If worse comes to worse, extract the kernel from the stock image and make a flashable zip yourself.
[X Play Original Android Development] :
I finally decided to root my Moto X Play. I'm still on stock.

I flashed Squid2's 15b kernel. The improvement in battery performance is amazing. Everything is silky smooth.

Thanks Squid2!!!
[X Play Original Android Development] Sickaxis79:
Use stock rom.
[X Play Original Android Development] lokesh.acm:
I'm on stock ROM only. I know it's like a battery saving feature but 26% is too early.
[X Play Original Android Development] dictionary:
Working great, thanks!!
[X Play Original Android Development] danger2u:
testing

thank u

how can we setup the functions available on ur kernel?

Inviato dal mio XT1562 utilizzando Tapatalk
[X Play Original Android Development] DrunkenDragon:
Kernel auditor is best
[X Play Original Android Development] danger2u:
someone else got a strange power off phone after instaling the last kernel version?

Inviato dal mio XT1562 utilizzando Tapatalk
[X Play Original Android Development] vbob:
Yep, I rolled back to r8b, its more stable then the r9
[X Play Original Android Development] DARKEASC:
Trying r9d in stock, no problem so far, is it posible to enable LED notifications?

Enviado desde mi XT1563 mediante Tapatalk
[X Play Original Android Development] squid2:
What do you mean by strange power off? It turns on and off fine for me.
[X Play Original Android Development] Nico3d3:
Testing r9d now, I'll use it as a daily driver to see if there's any bugs remaining. For now, I've only seen one bug and it's not a big problem. I can't reboot to recovery anymore using this Reboot app. Anyway, I can still get to recovery by holding vol-up and power button at the same time... Anyone knows which I/O scheduler gets the best performance? Thanks for your great work Squid2, it gets better everytime. Once, we are sure that the kernel is stable, it would be nice to have interactiveX and/or asswax cpu governor.

Edit: I meant to say I'm testing r9d not r9c, I was aware that r9d fix the screen gitches
[X Play Original Android Development] squid2:
If you're on r9c, do upgrade to r9d, since it fixes the screen glitches.

As for the reboot to recovery issue, I've been encountering it too actually. It's minor but I'll look into it.
[X Play Original Android Development] squid2:
Squid Kernel r9e

I have a new build up that fixes the reboot to recovery regression in r9c/r9d. If you're on my latest CyanogenMod build build and want to fix this issue, flashing this zip should do it on CM too.
[X Play Original Android Development] dictionary:
Haven't flashed latest, but r9d is running very warm for me. Stock ROM.