yashsingh1/xdaforums huggingface dataset:
[X Play Original Android Development] flopezm:
thank you very much for your work,

Thank you
[X Play Original Android Development] squid2:
There are no LED controls in the stock ROM unless you use a third party app to control them. The LED should start blinking by default when you receive a notification on the stock ROM.
[X Play Original Android Development] Abravanelsenor:
Faux Sound Control. (faux123)

Good afternoon, Squid!

You will deploy this feature into the kernel? I need this function.

I want to contribute monetarily, how do?

Greetings from Brasil!!!! Amazing your work!!!
[X Play Original Android Development] danger2u:
wich third party app do u recomand?

thanks for ur work again

no problems with last version of kernel
[X Play Original Android Development] XMoDuLeSx:
Suggestion please can the I/O schedule of external storage be set as default FIOPS with 512 read ahead buffer?
[X Play Original Android Development] DARKEASC:
My bad. I had the first TWRP version which was not flashing correctly. After install the v2 and flash the latest kernel, LED is working as you say, thanks!!!

Enviado desde mi XT1563 mediante Tapatalk
[X Play Original Android Development] Higgsy:
Kernel running great, thanks for developing for this device
[X Play Original Android Development] pyr0sphere:
Agreed. Have been changing the stock kernel setting to row with 512 read ahead. Squid's kernel seems to work just fine at the default settings
[X Play Original Android Development] squid2:
Squid Kernel r10

Today's release is a pretty nice one I think. As usual, I updated to the latest 3.10 series Linux from Kernel.org (3.10.90 in this case). On the new features front, I added the MDP5 KCAL colour control by [MENTION=4316709]savoca[/MENTION] and I incorporated optimized ARM crypto routines. On the optimization front, I cleaned up the defconfig to reduce size, and changed some configuration to significantly improve the performance of the virtual memory subsystem.

If you run a benchmarking tool like Antutu, you'll notice that the "RAM Speed" value will be higher on this build than on previous builds. If you're coming from r8, you may also notice that the "Storage IO" performance is higher than before, thanks to some optimizations (brought in from the lux kernel) that I added earlier in r9c.
[X Play Original Android Development] pyr0sphere:
Had just flashed the latest r9 release a few hours ago lol

Thanks for the new release :) will flash soon

PS: for those of you like me, who don't actually know what the MDP5 KCAL colour control is, here is a Youtube video:

https://www.youtube.com/watch?v=dESlxM9izxk
[X Play Original Android Development] Nico3d3:
Can't move apps to external sd card with r10 last build. I get a message telling me that there's not enough space available on the sd card (I have an empty 32go card so space is not a problem).
[X Play Original Android Development] squid2:
Just checked and can confirm your bug. I'm going try to fix it now.
[X Play Original Android Development] Nico3d3:
Is there anyway I could get a download link for r9e so I could use it temporarily?
[X Play Original Android Development] squid2:
http://www.mediafire.com/download/0pzgeybooshp1yc/squid_kernel_r9e-lux.zip
[X Play Original Android Development] Higgsy:
Nice I was thinking the display colours could do with tweaking!
[X Play Original Android Development] squid2:
Squid Kernel r10b

This new build should fix the r10 regression regarding moving apps to the SD card. If you encounter any other bugs please let me know and I'll fix them when I can.
[X Play Original Android Development] MonoIiths:
One thing that could go a long way toward development is if you don't intentionally release broken configs; and yes this is happening right now It's highly annoying.

Yes yes, I know you intentionally gutted .c files in USB and other places; I know all about it.

Edit: I really entered this device subforum wanting to help with development but found myself becoming annoyed at how you've made your stuff unusable; probably a feeling of proprietary ownership?

Please make it right, this is the most unfriendly behavior I've seen from a developer in a long time regardless of what I say to you
[X Play Original Android Development] Devhux:
So far r10 appears to be running smoothly for me. Don't move apps to SD card so I'll just keep this build
[X Play Original Android Development] MonoIiths:
And yes, your kernel is beautiful; I can't and don't want to take that away from you.

You did good work; you're just not being friendly in how you operate so as the only other person building for this device here I am; being less than friendly so we can resolve this obvious problem.

You're only boning the people who use the phone; I don't care if your configs are broken or not. If you don't fix them I'll just make my own but I'd really rather not?
[X Play Original Android Development] LenAsh:
Clearly there are some perceived issues regarding this kernel that are causing angst amongst some members.

You are reminded that XDA encourages collaboration and the sharing of information, ideas, possible solutions and so on.

XDA does NOT support unwelcome criticism and argument.
[X Play Original Android Development] squid2:
The sources and configs on my GitHub are exactly what I build from. You can check the revision hash on the build name string and compare it to what I've tagged on GitHub. Many devs are using this kernel for their ROMs on osprey and lux. Here's the build script I just made today to simplify maintaining the 4 variants of this kernel: https://gist.github.com/sultanqasim/54f7befa22904f1914df

If you were having difficulty building my kernel, you could have asked me for help and I'd gladly do so.. Accusing me of tampering with sources and violating the GPL is ridiculous.
[X Play Original Android Development] koimr:
I've used Kernel Auditor to change things like that although lately I've just left things as-is. :)
[X Play Original Android Development] migue8282:
We must change something for Led features with the new version?
[X Play Original Android Development] squid2:
Squid Kernel r16d

This is a relatively large maintenance release of the r16 series. It includes fixes to compatibility with CyanogenMod 13, and security fixes. It also adds vibration intensity control for both qpnp-vibrator (surnia/osprey) and drv2605 (lux). You should be able to control vibration intensity via CyanogenMod, as well as manually via sysfs nodes at /sys/class/timed_output/vibrator/. I've also upgraded my compiler to Linaro GCC 5.3.

On lux, I've fixed a bug where external offlining of the big cluster will not cause all but one of the remaining little cores to also go offline. The associated bug in ClusterPlug has been fixed, regardless of how you find your system behaving. However, if you still have issues with this new version, do let me know (along with details of when and how it happens), and I'll try to fix it.

My phone battery rarely dips below 75%. I charge it to 100% overnight, take it out in the morning, and its typically 80% by bedtime when I plug it back in. As a result, I rarely get to test out behaviour when the battery is low. I might skip charging my device for a few days to test how it behaves when it runs low.
[X Play Original Android Development] sttehh:
WLAN does not work with new kernel and stock 6.0.1
[X Play Original Android Development] varounmirchi:
What do u mean by "external offlining" of the big cluster? I've noticed in kernel adiutor that the big cluster does go offline, but i dont quite understand why?

Also, is there a way to disbale the offlining? that is, keep the big cluster online at all times? coz i've noticed major performance drops when it goes offline and only the little cluster is active.

Using RR with squid kernel 16.
[X Play Original Android Development] LuizHenrique91:
"external offlining" means that something is shutting down the cluster, other than the kernel, like the battery saving profile of the Power HAL of Cyanogenmod.
[X Play Original Android Development] manan001:
Is it good to flash your kernel with latest 9april cm13 build
[X Play Original Android Development] dreinulldrei:
Can you check if the WLAN .ko gets updated? WLAN and Kernel versions must match...
[X Play Original Android Development] AtomicStryker:
WLAN working fine here. Installed 16d on Marshmallux 6.0.1 (stock basically). Dualsim works. I wiped cache/dalvik too.
[X Play Original Android Development] migue8282:
The Led works by default?
[X Play Original Android Development] K.khiladi:
this version as been described in OP has increased compatibility with cm13. So you got the answer.
[X Play Original Android Development] sttehh:
Mmmhh, tried update again. wlan.ko was updated.. And wlan is working now. Another miracle.. [emoji4]
[X Play Original Android Development] AtomicStryker:
I doubt it, squid would have mentioned this. I still have the LED fix in my setup.

I also don't think a kernel can make the LED work in MM by itself ... since the "driver" is broken. In Lollipop the LED is just off, in MM it is broken.
[X Play Original Android Development] Benjamin_L:
Only in 6.0.1. where motorola disabled it completely
[X Play Original Android Development] Ebrahim Ali:
Does this latest update 16d work for the stock rom 6.01.Sorry to ask but I'm just making sure before I flash?
[X Play Original Android Development] sttehh:
It works.
[X Play Original Android Development] Ebrahim Ali:
Cool I'll be flashing then
[X Play Original Android Development] ShlCar347:
The r16 series is having some issues with the WiFi connectivity. 5GHz WiFi is working fine, however the 2.4GHz struggles a bit when I take the phone away from the router. The r15b build wasn't having this issue. And thanks for porting official CyanogenMod for the Moto X Play!
[X Play Original Android Development] sttehh:
Decreasing vibration intensity with current kernel and kernel adiutor works great on stock rom too.. ☺
[X Play Original Android Development] yeeahnick:
Can you reboot and see if the setting sticks because it does not for me. Intensity is back to 100% in Kernel Adiutor after each reboot, even if "Apply on boot" is activated =(
[X Play Original Android Development] treibstoff:
Same here
[X Play Original Android Development] sttehh:
You are right. After reboot, it's set back to 100 %.

So I have to do it manually, which was working.
[X Play Original Android Development] squid2:
Squid Kernel r16e

[MENTION=5679117]LuizHenrique91[/MENTION] and others who inquired about disabling the big cluster when the battery is low

I decided to run my battery low this weekend to see what happens. ClusterPlug worked as it's supposed to (activating the little cluster when the big cluster is disabled). With regards to the big cluster being disabled when you use the camera and the battery is low, what happens is that something called BCL (battery current limiting) kicks in. What BCL does is limit the maximum current you can draw from the battery when the voltage is running below a threshold. The reason this is done is that you can brown out the device if you draw high current with a low battery. Batteries have an internal resistance, so their voltage drops as load current increases. The big cluster is faster and can draw more current, so BCL disables it to reduce maximum current draw. BCL can also slow down certain clocks. If the voltage goes too low, the device will shut off by itself. Motorola configured BCL to prevent the device from dying under load when the battery is low.

BCL is triggered based off battery voltage rather than the reported percentage you see in Android. Battery voltage can vary a a particular percentage based off loading conditions. As a result, you may have noticed that there isn't a particular battery percentage that this kicks in at, but rather it seems to happen under certain loading conditions when the battery is low. Using the camera is a relatively heavy loading condition (you must realize that for this camera sensor resolution, the ISP may be processing a gigabyte of raw sensor data per second). As a result, this can push the battery voltage below the threshold and activate BCL. Bootup is another heavy loading condition, so booting up with a low battery will cause BCL to disable the big cluster.

BCL is required to avoid having the device die under load with a low battery, so I don't want to break or disable it. However, I understand that having the big cluster get disabled at 30% battery under modest loading is a bit annoying. So what I did is alter the voltage threshold that BCL kicks in from 3.7V to 3.63V. For reference, the device shuts off at 3.5V. Now, when you load the device at 30% battery, it will probably not disable the big cluster, but below 20% it likely will still do so. This is a safe and reasonable compromise.

So to summarize, this update should lengthen the period for which the big cluster can be used. I also updated zRAM to sync with Linux 4.4 upstream.
[X Play Original Android Development] LuizHenrique91:
This explains why the big cluster wasn't disabled when the battery was under 30%, exactly!

So the BCL is the reason why the device shuts down when battery is ~5%? In this case, voltage goes under 3.5V and then, even with some mAh, the phone shuts down anyway?

Thanks for clearing this up. I'll download the new version.

Enviado de meu XT1563 usando Tapatalk
[X Play Original Android Development] Diegouk:
r16e + stock 6.0.1 working fine here, thanks a lot dude!!

Enviado desde mi XT1563
[X Play Original Android Development] judokapol:
Can you add some more governors like smartassv2 or luzlactive ??

Enviado desde mi XT1562 mediante Tapatalk
[X Play Original Android Development] JohnHorus:
Touchboost settings not saving

[MENTION=6485916]squid2[/MENTION] I can't seem to get touch boosting to work correctly on r16e. Never tried it on earlier versions, but I've seen people saying it was working, so I don't know what the cause is.

It will only boost if I set the first core of either cluster, and when it boosts, it boosts all four cores of that cluster. However, none of the frequency settings except for cores 4 and 8 will save. Unless core 1 or 5 are set, though, no boosting actually happens when I touch the screen(so it's effectively not persisting through a reboot at all.) It does save the period of time that the boosting is supposed to occur, for whatever reason.

Not sure if it's related, but I also can't get the adaptive LMK being on to persist through a reboot.
[X Play Original Android Development] lilloscar:
Hello all! my question is:

How can I activate again the double twist to launch camera app?

It worked fine even installed resurrection Rom & squid kernel.

The last thing I installed today was Xposed framework v81 but I didn't know if was this the reason it didn't work anymore
[X Play Original Android Development] kvskmcafee:
[MENTION=6485916]squid2[/MENTION] I don't know why, but with r16d and r16e kernels, I am frequently losing mobile signal when preferred network type is chosen as LTE or 3G. Signal stays stable only when I choose 2G as network type. This problem was not there with earlier kernels (r16, r16b and r16c). I am an Indian user with RR 5.6.7 ROM on my MXP. There are no problems other than this. Any suggestions?

I can confirm that signal stays stable when I flash a kernel other than r16d and r16e irrespective of the network type selected (LTE/3G/2G).
[X Play Original Android Development] manan001:
Ya even i did notice the same that network signal has weakened.
[X Play Original Android Development] squid2:
That's odd. Nothing radio related has changed in the kernel between r16 and r16d/e. Signal has been fine for me.
[X Play Original Android Development] dreinulldrei:
All fine here so far but will keep an eye on it. Is there anything radio related in the kernel? I always assumed that network connectivity was directly handled by baseband and kernel only acts as the "API" to access it...
[X Play Original Android Development] JohnHorus:
I've had no issues with signal, either. Running 16e now. I'll post back here if I encounter anything like that.

Any ideas why touchboosting won't save for me? Has anyone else encountered anything like that? On CM, I get a notification and everything when boot settings are applied.

EDIT: So while I don't recall getting the boot-settings notification on stock, it seems touchboosting settings still don't save on CM. However, they do save using EX Kernel manager (a paid app made by flar2 for his kernels.) I did try this on stock, and I don't recall it working then, but perhaps I did something wrong, as it definitely seems to work on CM.

Strange that Adiutor doesn't work though, I've only heard good things about it. [MENTION=6485916]squid2[/MENTION] Do you know if there are multiple methods to handle settings at boot? I don't mean any offense, but could it maybe be due to something in the kernel interacting differently with the two apps? I have no idea, myself, I know nothing about this.

DOUBLE EDIT: Flashed back to stock as I wasn't so happy with CM (buggy QS tiles,) I can confirm that both CM and Stock, the input boost settings stick with EX Kernel Manager, but not with Adiutor. Weird. Not sure if anything else is bugged in Adiutor, I didn't notice anything but I didn't really mess around with much else.
[X Play Original Android Development] yeeahnick:
OMG I dont know what just happened?!??!?!?! I flashed latest kernel on the 10th using it with stock rom. Everything has been perfect since. Today I decide to reboot my device and for some reason it was taking for ever to boot. Decided to turn off phone and retry. It booted and said it was updating apps, same thing that it does after a system update. After that was done a message popped up saying "Theres an internal problem with your device, and it may be unstable until you factory data reset".

Seems like it actually did some sort of FACTORY DATA RESET by itself since I have lost root and all app data. I can still boot in TWRP but when I try to restore a nandroid it says cannot mount system =(

Also before the reboot my battery was at 30%, after reboot it was at 6% ????

Is it a bug or my phone really has a problem???
[X Play Original Android Development] cute_prince:
The new f2fs drivers might be causing this issue.
[X Play Original Android Development] yeeahnick:
Thanks for the reply. Thats what I think also but I thought it only affected CM users and not STOCK ROM users

I was able to reinstall root and used titanium backup to restore app data but now I am unable to activate WIFI, it worked before I restored root and app data =(

When I go in status my MAC address shows 01:00:00:00:00:00:00

edit: just noticed I was back to stock kernel....? flashing squid kernel fixed WIFI
[X Play Original Android Development] K.khiladi:
Same here. I am using RR and after I installed a theme and rebooted. This popped up. Fortunately I had a titanium backup. I am stock RR kernel.

Automated reply by JARVIS
[X Play Original Android Development] squid2:
Yep, the new f2fs has breaking changes that are causing problems. I'd recommend r16d/e users to make backups of their data to a non-f2fs volume and be careful while we sort out this f2fs fiasco.
[X Play Original Android Development] GtrCraft:
Well I saw this too late, all my whatsapp media is gone...
[X Play Original Android Development] K.khiladi:
Is this just your kernel related or a bug in cm13 as then it would affect other Roms based on Cm?

Automated reply by JARVIS
[X Play Original Android Development] brom25:
happened to me too

whatsapp backups automatically to google drive, might be worth checking there.
[X Play Original Android Development] yeeahnick:
So what is causing this bug exactly? Can it happen again? What provokes it?

FYI the bug occurred on stock rom for me.
[X Play Original Android Development] K.khiladi:
It's because of I think kernel which implemented f2fs

Automated reply by JARVIS
[X Play Original Android Development] GtrCraft:
Turned that off
[X Play Original Android Development] varounmirchi:
So if my ROM is on ext4 only, NOT f2fs, I can install the latest version, right? Currently I am on 16(no alphabet) version.
[X Play Original Android Development] GtrCraft:
No, data is always on f2fs. That's how Motorola made it. Do not flash 16d/e
[X Play Original Android Development] varounmirchi:
Yep, just checked.
[X Play Original Android Development] mw1man:
I am on r15 b. Al fine here
[X Play Original Android Development] dreinulldrei:
I would recommend recompiling latest build with older f2fs Code OR simply bumping the version number for 16b to 16f. People tend to not read all threads and will grab the latest build to flash it. This will give some time to fix and avoid more people bricking their devices.
[X Play Original Android Development] Benjamin_L:
I guess [MENTION=6485916]squid2[/MENTION] is already working on a new release
[X Play Original Android Development] dreinulldrei:
Yes I am aware of this. But people can still download the broken build and it is the last one here... Just saying it's a problem for the average user .
[X Play Original Android Development] Ebrahim Ali:
Hi

I'm using 16e on the stock rom and haven't encountered this issue yet. Does anyone know what triggers it?
[X Play Original Android Development] GtrCraft:
rebooting or just when you use the phone

---------- Post added at 10:48 AM ---------- Previous post was at 10:48 AM ----------

Duhhhh
[X Play Original Android Development] K.khiladi:
I guess both the latest squid kernel and twrp build have this problem.

Automated reply by JARVIS
[X Play Original Android Development] GtrCraft:
Yeah they do
[X Play Original Android Development] K.khiladi:
Just noted that the cm13 nightly dated 12 moves to moto f2fs. Is it for avoiding this issue?

Automated reply by JARVIS
[X Play Original Android Development] Ebrahim Ali:
The only thing I've noticed is that my phone froze when I was using an app once so I turned the phone off and when I turned it back on it boot looped a couple times but then turned on normally. No data loss or anything. Do you think I should flash an older version of TWRP and Squid kernel just to be safe?
[X Play Original Android Development] Benjamin_L:
I guess it's more likely one of the things causing this. For more see http://xdaforums.com/showpost.php?p=66327292&postcount=1221
[X Play Original Android Development] K.khiladi:
I am on RR and thus wanted to know whether it's squid kernel, twrp or cm13 and now I think it's all of them but since cm13 12 April build has reverted to moto f2fs, the problem with cm13 has been resolved. Now for me the question is on which cm13 RR is based upon.

Automated reply by JARVIS

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

Yup

Automated reply by JARVIS
[X Play Original Android Development] GtrCraft:
Yes, but don't flash it with the newest twrp or squid kernel 16d/e

You should, and maybe format your data partition
[X Play Original Android Development] Benjamin_L:
CM is using the old f2fs version now and newest squid kernel and twrp the newer one, that's what creating troubles as far as i understood it.

I really wonder why we're not using ext4. Benchmarks on the old nexus4 didn't show any improvements of f2fs compared to ext4 and ext4 is much more stable imho.
[X Play Original Android Development] GtrCraft:
If the RR build is from before april 8th you are safe. Or flash the boot.img from the cm 12/04 nightly. It's in the kernel and twrp, not rom

---------- Post added at 11:57 AM ---------- Previous post was at 11:41 AM ----------

Because Motorola is using f2fs on /data by default
[X Play Original Android Development] Ebrahim Ali:
So to confirm I should flash TWRP 3.0.0 and Squid kernel 15?
[X Play Original Android Development] GtrCraft:
3.0.2-r1 and 16b are safe enough
[X Play Original Android Development] Ebrahim Ali:
Thank you. Someone noted that this happened on the stock rom when they tried to restart the phone. I restarted my phone a couple of times to see it that happens. What happens was the phone bootloop ed sometimes but started normally with no data loss or error messages. Anyhow I'll flash the stable recovery and kernel tonight.