yashsingh1/xdaforums huggingface dataset:
[X Play Original Android Development] dreinulldrei:
Well that's what I wrote. You can revert by flashing your (backup of) boot.img, but that will leave you with a non-functioning WLAN as this module needs to match the kernel and is replaced when Squid's kernel is installed.

Hence my idea to create such zip file. The wlan kernel module is protected while the system is up and running.
[X Play Original Android Development] Benjamin_L:
Why not just dirty flash your rom zip? won't take much longer
[X Play Original Android Development] AtomicStryker:
If you were cautious, you would always make a full twrp backup before flashing anything. I used to, but then i took an arrow to the knee ... no, kidding, i trust squid not to explode my system basically, i backup everything, and there is nothing of consequence on the phone that isn't in some cloud anyway.
[X Play Original Android Development] dreinulldrei:
Any completely mess up with stuff that's been installed, break root etc. pp.

You are welcome to do this, I don't want to.

So do I. Still I lose all changes made to the system since the last backup.

Either way, I asked if someone wants to chime it, I wasn't asking for feedback from those who don't want to. I think there's a lot of people surprised that after re-flashing their original boot.img, their WLAN is broken.
[X Play Original Android Development] scottdanpor:
Anyone able to get this working? No go for me on stock rom. I used root explorer to replace the files, set to rw-r-r. Rebooted, get no notification about any sensor suite and no LED. Tried it a couple times.

**Edit, ok UC Browser doesn't download the files properly, I used a PC and transferred them over, that worked
[X Play Original Android Development] Benjamin_L:
Nothing changes when you dirty flash the same rom you have installed, just the kernel changes. Why should it break something? I always do it this way.
[X Play Original Android Development] dreinulldrei:
So you do it like this fine, I have modified Boot and System (rooted 6.0.1).

Again, if this works for you, then "move along, these aren't the droids you're looking for." :)

Thanks.
[X Play Original Android Development] MaxlMuller:
LED is working!

Thanks! That worked for me! I'm using stock 6.0.1 rooted with Squid kernel v16. I used ES File Explorer to copy the files using root permission. Then rebooted, notification showed up, rebooted again, and done! LED is working again.
[X Play Original Android Development] diazepambr:
It's working here, Chrome don't downloaded the correct .txt file instead, downloaded the .html file from page , now it's works flawless

Thanks for all :)
[X Play Original Android Development] AjaySp:
worked perfect Thanks Mate
[X Play Original Android Development] BASS55:
I just have to say a big thanks to squid2!!! So much hard work, dedication and constant updates for our Niche Moto X Play!!! :cool:
[X Play Original Android Development] John5p:
Can't seem to get it to work. Stuck at step 5 because I'm not getting any notification after reboot.
[X Play Original Android Development] scottdanpor:
Browser probably doesn't download the files properly. Download with a PC and transfer the files over. That's what I did.
[X Play Original Android Development] John5p:
I did the same thing as diazepambr. Downloaded files from Chrome on PC and transferred files over, but didn't work.
[X Play Original Android Development] scottdanpor:
https://mega.nz/#!p9sy3LgL!EZvYrBG7L5EErJWF8MwlGfBgQZUUBGX9hvmzteZ2-wM

There's the same files
[X Play Original Android Development] zero995:
testing ....
[X Play Original Android Development] till69:
No notification because you have removed "\system\priv-app\STML0Updater"
[X Play Original Android Development] John5p:
How do you get it back? I was unaware had this file removed
[X Play Original Android Development] Benjamin_L:
[MENTION=6485916]squid2[/MENTION] anything else i could test for you?
[X Play Original Android Development] till69:
Got it from MarshmallowLux deodexed Rom
[X Play Original Android Development] John5p:
Mind if you share the link to the ROM you are referring to? And do you just dirty flash it?
[X Play Original Android Development] till69:
http://xdaforums.com/moto-x-play/development/rom-marshmallux-stock-based-rom-6-0-t3278040

No need to flash, just download, unzip and copy "STML0Updater" folder to "\system\priv-app", then reboot
[X Play Original Android Development] John5p:
Finally got the downgrade notification to pop up after reboot. I had to delete the STML0Updater folder and reboot the phone to shut down the moto sensor services. Then restore the STML0Updater folder and reboot the phone. No idea why I had to reinitialize the Moto sensor service to get the notification.
[X Play Original Android Development] zhyylz0201:
don't have LED

从我的 XT1562 上通过 XDA Forums PRO 发送
[X Play Original Android Development] dreinulldrei:
Yes... Because you haven't read the thread. It's been well explained over last couple of pages.
[X Play Original Android Development] jonytestXD:
I have a problem in cm13 official when I flash the kernel after reboot Mi phone says there's no space but in setting I have 5 gb free but the system keeps saying that there's no space free =(

Enviado desde mi XT1563 mediante Tapatalk
[X Play Original Android Development] thiagomz:
Should I flash with twrp ?
[X Play Original Android Development] ShlCar347:
The range of my WiFi has reduced significantly (2.4Ghz) I'm on AICP. The phone will scan my WiFi on the other end of the house but will just refuse to connect to my network, but as I get closer to my router the phone gets connected! Usually happens when the range goes below half on the indicator. I've tried disabling the 'avoid poor connection' option in the settings but that doesn't help.
[X Play Original Android Development] manan001:
[MENTION=6485916]squid2[/MENTION] are you still going to work on custom kernel?[emoji15]
[X Play Original Android Development] droider007:
Why not?
[X Play Original Android Development] till69:
r16 on 6.0.1 Stock: Connection to WiFi is slow, up to 5 secs while showing exclamation mark. Stock kernel connects in less than 1 sec.
[X Play Original Android Development] lokesh.acm:
For me, the wifi exclamation mark is always there for at least 5secs when I connect to my wifi, zte. But when I connect to other peoples' wifi, it connects ASAP. I'm guessing my modem is dying. I don't know :p
[X Play Original Android Development] JohnHorus:
Does anyone happen to know how to back up just the Kernel? I'd like to try this out once I get through setting up all my other root-related goodness, but I'd like to be able to flash the stock kernel back without having to restore a NAND backup.
[X Play Original Android Development] Benjamin_L:
[MENTION=6485916]squid2[/MENTION]: Funny thing is, when installing r16 on my cm13, it doesn't detect sim card as you already know. When i delete modemst1 and 2 partitions, it detects the sim card and asks for pin yet i get the no network error. does this tell you something? This is still with the german 5.1.1 modem
[X Play Original Android Development] squid2:
I don't really know what's going on for your device as it seems to work fine for most others. What really perplexed me was when you said that r14 works but r14b doesn't. Very little changed between r14 and r14b apart from a few small fixes to the audio drivers. You can see for yourself: https://github.com/sultanqasim/android_kernel_motorola_msm8916/commits/r14b

How the audio driver changes could break network detection on just your device and seemingly no other device is bizarre. Or maybe my reverting of fixes for false positive compiler warnings did it. But that would also be bizarre. So I really have no clue as to why your device has difficulty with recent versions of my kernel.

If you capture radio logcats from bootup (logcat -b radio) with the stock CM kernel and this kernel, I may be able to tell something from comparing the logs. Another thing worth trying would be to see if r16 works on your device with the stock Marshmallow ROM. I also wonder if a 6.0 modem makes any difference on your device.
[X Play Original Android Development] Benjamin_L:
Already tried with the single sim europe stock image as a base. Gives me bad reception (orange and red) for stock cm. didn't try with r16 then. Will provide you radio logs soon

CM pure, this time i had to pop the im card in and out to get it working: https://owncloud.lebsanft.org/index.php/s/tZnFnZRjLAALz8n

CM w r16: https://owncloud.lebsanft.org/index.php/s/YGgLJ4AWTGBEEgb
[X Play Original Android Development] droider007:
There is some serious lag when scrolling through google plus(only when there is media content on page)....otherwise scrolling is fine.....however this lag is absent on stock rom......using cm plus squid kernel r16
[X Play Original Android Development] kamarilla:
Led working following this steps. Thanks!! after last reboot led started working after a minute or two.
[X Play Original Android Development] soumitpl48:
You can do that using an app called Flashify.
[X Play Original Android Development] Benjamin_L:
[MENTION=6485916]squid2[/MENTION]: Wanna know the latest findings? ;) When setting fastboot oem config num-sims to 2, sim works after popping it out and in. When setting fastboot oem config num-sims 1 popping in and out doesn't work. This is all with the german 5.1.1. single sim modem.
[X Play Original Android Development] squid2:
Weird :eek: This seems to be blurring the distinctions of what devices and modems are single SIM and dual SIM.

Be aware that when you set "fastboot oem config num-sims 2", it sets some persistent properties that stay after doing "fastboot oem config num-sims 1" until you wipe data (or more simply delete the persistent property files it sets within /data). Otherwise, your device would be in a "half dual SIM" state that would act weird.
[X Play Original Android Development] Benjamin_L:
Which files are changed?
[X Play Original Android Development] squid2:
Persistent properties are stored in /data/property/persist.*

The persistent properties affected by the num-sims utag are:

persist.radio.force_get_pref

persist.radio.multisim.config

persist.radio.plmn_name_cmp

ro.telephony.ril.config

Delete these files after setting the "num-sims" utag setting back to 1. I may look at automating this later.
[X Play Original Android Development] JohnHorus:
[MENTION=6485916]squid2[/MENTION] Thanks so much for all the work you put into this! Definitely notice an increase in speed over the stock kernel!

I don't mean to sound ungrateful, as I know that a lot of work goes into what you've already done, but is there any way you could look into adding Sweep to Sleep and Sweep/Tap to Wake features into it? Since using the ElementalX and Hypernova kernels on my M8, I've become heavily addicted to them, and often find myself sweeping the navbar on the Moto X in vain.

I understand that the battery drain is quite low if the phone supports touch-sensitivity for the screen without actually keeping the display on. It seems like the low-power state Moto built for active display would work well for it, though I'm no expert. Would love to know if it's possible to look into adding them in the future!
[X Play Original Android Development] yeeahnick:
[MENTION=6485916]squid2[/MENTION] Lots of love from Quebec! I flashed your kernel last night and noticed a performance boost instanstly, now im going to wait and see how the battery goes. Got LED working and thats a huge plus for me. Is Kernel Adiutor the recommended app to manage your kernel? Last question, are there any future plans to add a feature to customize the Vibration Intensity? The default is WAY too strong making silence mode useless because the vibration is louder then the minimum notification volume lol. I use GravityBox to manage the LED duration (works good) and in that section there is an option to change the vibration pattern, when I test the feature with the test button the vibration changes but when I apply the setting it has no effect in real time. Do you think its a problem with Gravity Box or something needs to be activated in your kernel for the setting to stick?

Thanks x100
[X Play Original Android Development] YayoD801:
Work in android 6.0.1?

Work in android 6.0.1?
[X Play Original Android Development] dreinulldrei:
Read OP? :)
[X Play Original Android Development] scottdanpor:
r15b 'works' on 6.0.1 but the LED does not. r16 works in 6.0.1, and LED works after making a simple modification. See post #1088 for steps.

This information has not been included in OP.
[X Play Original Android Development] JaviLerma:
Hi, this kernel support OTG?

In Surnia does not.

Thz
[X Play Original Android Development] jprcs:
Solution for the bootloop start http://xdaforums.com/showthread.php?t=3349822

Enviado desde mi XT1562 mediante Tapatalk
[X Play Original Android Development] ShlCar347:
Yes, OTG works on the Moto X Play.
[X Play Original Android Development] Quatro7:
What is OTG?

Wysłane z mojego XT1562 przy użyciu Tapatalka
[X Play Original Android Development] Benjamin_L:
https://en.wikipedia.org/wiki/USB_On-The-Go
[X Play Original Android Development] tomi001:
And now is the batterylife better than stock?
[X Play Original Android Development] K.khiladi:
Battery life was always better than stock kernel when using the lionfish governor of squid kernel.
[X Play Original Android Development] yeeahnick:
Honnestly I havent had time to stress test the battery that much. What I can confirm is that standby time has improved. Browsing the web is also much smoother. Havent had any reboots or performance stabitlity issues. So far I have no reasons to go back to stock kernel especially now that I have the LED working and managed to reduce the vibration intensity (although I have to apply the setting after each boot for the vibration) no big deal because I almost never reboot that phone.

Give it a try I recommend it, you can backup stock kernel with Flashify and restore it if you do not like squid kernel.

FYI: I am using lionfish governor .
[X Play Original Android Development] Benjamin_L:
Hey [MENTION=6485916]squid2[/MENTION] i flashed stock 5.1.1 again and updated to 6.0 from there. Installed cm afterwards. Same issue. Stock cm works fine, r16 doesnt detect the sim card
[X Play Original Android Development] fshero:
How did you managed to reduce the vibration? I haven´t found any solution, yet. My phone is the whole day on silence mode because of the heavy vibration. :(

I only found a way to make the vibration intervall shorter with Xposed + Gravity Box , but this doesn´t reduce the intensity and is only working randomly.
[X Play Original Android Development] Pastignon:
Hi everyone,

I've been lurking around this thread for 3 weeks now, as my plan was to purchase a Moto X Play before my dear Nexus 5 dies (that power button man...). I've now purchased it, and rooted the **** out of it when it arrived. 6.0.1, rooted with Squid Kernel already seems amazing. I even managed to make the LED work thanks to the method explained on the last 3 pages, everything is working smoothly. I can also report standby battery is better with Squid Kernel (barely any drop actually). So, really, thanks to all of you, it's awesome to have such a dedicated community for an upper mid-range smartphone.

My question is, are apps like f.lux dependant on the kernel ? I've installed it as I did on my N5, and I can't make it work. The only difference between the two devices is the custom kernel, and I figured maybe it would be the reason why. So, is Squid Kernel incompatible with f.lux ? Is anyone using it ?

Thanks in advance :)
[X Play Original Android Development] dskid807:
My Moto X Play keeps switching off/not waking with the lionfish governor enabled, it's the dual sim version. Any ideas?
[X Play Original Android Development] LuizHenrique91:
You probably had different governors set on different clusters.

If you are using Cyanogenmod, I suggest you to wait some days until the new cluster plug is incorporated. The new cluster plug will let the governors set as you wanted.

Currently, when one cluster os offline, the governor is reset to the default when this cluster gets online.

Enviado de meu XT1563 usando Tapatalk
[X Play Original Android Development] squid2:
Squid Kernel r16b

I've posted a new build with the new version of ClusterPlug and some minor CM13 compatibility changes. It's meant to work with the April 7th nightly of CM13 that will be coming out soon. The stock ROM should continue to work with this as usual, though I haven't actually tested this build on stock.

I had plans to change the handling of governors through hotplug so that tunables and sysfs permissions aren't lost. Unfortunately, in later testing, I encountered some issues with edge cases with my patch. So I've held back this change, and the governors will continue to behave as they did before. I plan to look into this for the next release when I have more time (this release is an interim version for CM13 nightly compatibility). I also plan to look into the issue where setting different governors for different clusters breaks things.

For now, you must set the same governor for both clusters, else you will face issues with the device not waking from sleep. Also, for governors other than interactive, settings will be lost on hotplug. Interactive implemented a mechanism to internally cache tunables on teardown and restore them when the cluster is re-plugged, so settings persist for interactive. I will try to improve this for the next release.

If you use kernel Adiutor, you will notice one odd thing when you bring up the CPU settings pane of the app. The first core of the little cluster will appear online, even if the cluster is supposed to be off. This is not a bug. ClusterPlug 2 will not force a core offline if you manually online it, and vice versa. Kernel Adiutor tries to online the first core of every cluster when you open the CPU page. The little cluster is normally offline, and Kernel Adiutor will online the one core when you open the CPU settings page. This is actually somewhat convenient. To change the governor, you currently need to change both governors to match. To properly change a governor, at least one core of a cluster needs to be online. Thus, the procedure to change the governor would be to change both governors while at least one CPU of each cluster is online. After performing the governor change, you can manually offline the little cluster, and ClusterPlug will work as usual.
[X Play Original Android Development] manan001:
Hi [MENTION=6485916]squid2[/MENTION] in stock version we can active little core and big core can be deactivated or both the core can be made to work together. So can it be made similar to it?? Based on you kernel he was able to do this

http://xdaforums.com/showthread.php?t=3232434
[X Play Original Android Development] yeeahnick:
I use GravityBox (payed version).

Ultimate notification control/Default Settings.

I have Override vibrations checked, Vibration pattern (0,50), Replace original vibration unchecked.

Seems to work flawlessly with every app, the only down side is that the setting doesnt stick after a reboot. All you have to do after a reboot is simply open GravityBox and close it.

I really hope vibration intensity features will be added into kernel in the near future because the default ones are louder then lowest volume nofitication sounds lol.

Let me know if it works for you =)
[X Play Original Android Development] fshero:
This is exactly what I meant with Xposed+GravityBox. :p

I thought you really managed to reduce the vibratiation by itself not only the vibration interval. This method is a compromise, but no real solution for me. Let´s hope for a better method in near future.

But thanks for your help. :good:
[X Play Original Android Development] yeeahnick:
If you use my settings you can barely feel or hear the vibration, I tested ON and OFF and the vibration is way softer. Change the 250 numbers to 50, remove 1 or 2 intervals and you will see what I mean =)

Edit: Your right it doesnt directly change the intensity BUT it does feel much better after you apply my settings.
[X Play Original Android Development] JohnHorus:
Am I doing something wrong that I'm not ever seeing cores go offline on the latest release? (16b)

I don't recall ever manually toggling the settings. How would I reset that to make sure, so ClusterPlug doesn't think I've manually altered any of the core's states?
[X Play Original Android Development] LuizHenrique91:
Which ROM you use and what is the version in case it is CM?
[X Play Original Android Development] JohnHorus:
stock 6.01, I didn't realize the ROM affected hotplugging. Is there any way to change that?
[X Play Original Android Development] LuizHenrique91:
I think stock ROM doesn't have clusterplug enabled. The normal behavior is to keep all the cores online all the time.

Somebody correct me if I'm wrong, but I think that it's the normal behavior.
[X Play Original Android Development] JohnHorus:
Dengit! Is there any way to enable that, or do I need to use CM for hotplugging?
[X Play Original Android Development] LuizHenrique91:
I don't know any way to do this. I don't think it's possible on stock.

The changes in clusterplug for the latest release of the kernel that squid mentioned are related to the new clusterplug he implemented on Cyanogenmod. Now the kernel is compatible.
[X Play Original Android Development] Ev0luti0n_:
Guys.. Just installed the new lux nightly from squid. My led still works fine(apparently), and on short testing everything seems fine. Is it advisable to wait a few more weeks to install this kernel to make sure everything is super stable or just go for it?
[X Play Original Android Development] LuizHenrique91:
The kernel is stable. You can just flash it and it will work.
[X Play Original Android Development] droider007:
Clusterplug is disabled by default on stock rom....thats why both clusters are online on stock rom :)
[X Play Original Android Development] tshohel7:
I'm Facing A Problem, If I Change CPU Governor To Lionfish Via Kernel Auditor, My Phone Rebooted Automatically Also Turn Off The Phone Automatically. Any Solution For This. Thanks
[X Play Original Android Development] dskid807:
Is there a way to turn off the phone waking on proximity, or is that a motorola thing?
[X Play Original Android Development] Lattesarebuff:
what do you think are the best kernel settings for battery life, yet not comprising on smoothness?
[X Play Original Android Development] LuizHenrique91:
I'm trying lionfish with input boost at 960MHz

My feeling is that smoothness is almost the same as default settings and battery life is a little better. But I didn't use this setup for sufficient time to be sure.

Enviado de meu XT1563 usando Tapatalk
[X Play Original Android Development] Ev0luti0n_:
I think you can resolve that in the phone settings?
[X Play Original Android Development] dzesiu2002:
if you dont have option in settings then you can turn it off in Moto app.
[X Play Original Android Development] baskwo:
Version 16c is up on github. I decided to start compiling the kernel for my own and I've succeed. So if you guys want it, it's in my dropbox https://www.dropbox.com/sh/nwzr19irhwy551x/AACEuUJEKpVwRz7ugK42zjCpa?dl=0

I've upload a photo that show a proof that I'm on 16c.

I'm reminding you that this is not official! I don't have the "ok" from squid that my kernel is fine. But it's working for me...

Commits for 16c is in attached file.
[X Play Original Android Development] Benjamin_L:
Strange baseband you have there. Which stock rom is it from?
[X Play Original Android Development] baskwo:
I'm with koodo in Quebec. Using latest cm13
[X Play Original Android Development] Benjamin_L:
Interesting. Asia, Europe, india etc all have the same versions. So this is a vendor specific one it seems
[X Play Original Android Development] baskwo:
Probably because I don't remember flashing an other one.
[X Play Original Android Development] LuizHenrique91:
[deleted]
[X Play Original Android Development] Ev0luti0n_:
I tried searching around, but didn't find anything. Does this kernel have a control panel where we can tweak the settings like processor speed and voltage, or is it ''install and forget''?