yashsingh1/xdaforums huggingface dataset:
[X Play Original Android Development] Nico3d3:
I reinstalled the kernel to see if it would happen again and it didn't take long to see it happen again. Sound worked at first, then the phone got to sleep and when I re-opened it, there was no sound. This time, it happened even when the phone hasn't been in silent mode. In fact, the volume was set at max and still I wasn't hearing anything when I was playing something on the music app. Also, I tried MotoVoice command and the phone wasn't answering my command anymore. I had to reboot the phone to solve the problem. I was using the r8b kernel. Finally, no it's not happening with the stock kernel. The issue is the fact that there's no sound at all even when all volume sliders in Settings are set to max. Also MotoVoice stopped working. As I said earlier, I had to reboot to solve the issue.
[X Play Original Android Development] squid2:
Thanks for the clarification. I'll see if I can reproduce it when I get time. One last request - could you try the minimal kernel and report back if the issue happens there too?
[X Play Original Android Development] Nico3d3:
Just tried the minimal kernel this morning, I haven't seen the issue with sound yet but, MotoVoice doesn't work anymore so I guess I'll be back to the OEM kernel for now.
[X Play Original Android Development] LuizHenrique91:
Since Motorola didn't release the sources for kernel yet, on which kernel is the Squid based?
[X Play Original Android Development] ephumuris:
It does say somewhere in here it's based on 2015 Moto G I think.
[X Play Original Android Development] Nico3d3:
We're still waiting for Motorola to release the source code of the X Play kernel. I think what they are doing is against the GPL. Since they are using open source code, they are theoretically bound to release the source code as soon as the device get to market.
[X Play Original Android Development] squid2:
Indeed, they are violating the GPL by delaying the release of the source code. For now, I'm making do with a Moto G (osprey) kernel patched to support the hardware in lux.
[X Play Original Android Development] DrunkenDragon:
they have released moto x pure sources long back, moto x play was also released at the same time... man this makes the development delayed.
[X Play Original Android Development] NewAndreas:
My phone keeps freezing with the Minimal kernel. The image stays on the screen, and any input works after the phone starts working again (freezes for about five seconds.)
[X Play Original Android Development] squid2:
I haven't encountered any such issues myself. Could you capture a dmesg showing the period when the freeze happens?

With that said, since I don't have proper Motorola kernel sources and I'm improvising with modified osprey sources, bugs are likely at this point. I hope Motorola stops violating the GPL soon. They seem to have made a habit of delaying kernel source code releases for many devices this year.
[X Play Original Android Development] NewAndreas:
Well damn that was long: http://pastebin.com/zQb1exHw

i dunno how this works or if the freeze was captured
[X Play Original Android Development] ephumuris:
I wonder what the best way to bother them for it is?
[X Play Original Android Development] madcat1990:
Funny enough, they have now a fame of doing this :

http://www.xda-developers.com/gpl-license-controversy-once-more/
[X Play Original Android Development] Nico3d3:
Here is what we've been all asking for: https://github.com/MotorolaMobilityLLC/kernel-msm/tree/lollipop-5.1.1-release-lux
[X Play Original Android Development] HydrogenCyanide:
They release the source, hopes that this device gets better with some kernel tweaks and I buy it.
[X Play Original Android Development] XMoDuLeSx:
Worth buying its really cheap with insane battery life great screen and camera.

Soon there will be official support from CyanogenMod since source came out :fingers-crossed:
[X Play Original Android Development] brom25:
Thanks [MENTION=436307]squid[/MENTION] for your work on the device:good:

And how can you know it will be officially supported ? :confused:
[X Play Original Android Development] squid2:
Could you elaborate on what you mean by deep sleep problem? It sleeps fine here.
[X Play Original Android Development] Benjamin_L:
Sleeping fine here with r14. Are you sure its not an app? What does betterbatterystats say?
[X Play Original Android Development] raj wedhikar:
What if I want to use squid kernel without notification led?
[X Play Original Android Development] Benjamin_L:
Depends on the rom you plan to use
[X Play Original Android Development] jellysheep:
[MENTION=6485916]squid2[/MENTION]: Could you please post/upload the .config or lux_defconfig file used for your CM12.1 Squid kernel and tell from which Git branch you build it?

I'd like to do some experiments with it, and think it is based off your squid_linux_mr1 branch, but there is no lux_defconfig file in it.

Thanks a lot!
[X Play Original Android Development] squid2:
I actually used the squid_marshmallow branch for my last CM12.1 build with the lux_defconfig with one minor modification. I turned off CONFIG_MSM_CHECK_CAMERA_ACTUATOR to support the older blobs. I just make that modification in tree without pushing that one change, hence the commit hash that differs from the one you see on my github.
[X Play Original Android Development] b00tbu9:
Hi squid2. I have tested it with the kernel without grrenify and amplify. In that case also phone is unable to wake up from sleep. I had to force reboot. I am using stock MM with your kernel with lion*** governor for big and interactive for small with one step lower low cpu frequency.

I used 14/13b

---------- Post added at 06:34 AM ---------- Previous post was at 06:28 AM ----------

I removed all grrenify n amplify stuff in stock still not working[emoji20]

---------- Post added at 06:37 AM ---------- Previous post was at 06:34 AM ----------

Also [MENTION=6485916]squid2[/MENTION] can you let me know what all flags to disable for removal of LED notification.

---------- Post added at 06:41 AM ---------- Previous post was at 06:37 AM ----------

[MENTION=6208501]Gopinath15[/MENTION] were you not able to wake your phone...?

---------- Post added at 06:54 AM ---------- Previous post was at 06:41 AM ----------

yes I put it to Lionfish governer
[X Play Original Android Development] blankingblank:
I'm on stock 6.0 with stock kernel. Started playing around with cpu governors using kernel auditor and noticed frequent random reboots when using different governors for big and little clusters. I wonder if your deep sleep problems would disappear if u set both clusters to use the same governor?
[X Play Original Android Development] dictionary:
Your issue is lionfish. For whatever reason, it doesn't play well for some devices.
[X Play Original Android Development] K.khiladi:
I am using "on demand" for both big and little clusters and it works well till now. Just 4 percent battery drain in 7 hours and 30 minutes although the alarm of phone rung twice and I had to turn it off.
[X Play Original Android Development] Gopinath15:
Specifically it happened with lionfish governor. Phone switched off when the sceen was locked for a longer time. I had to reboot manually. Using r14 with interactive now. Works fine atm.
[X Play Original Android Development] blankingblank:
I did the same but mainly for performance. I thought since on demand ramps up cpu to max freq immediately that it would net some improvements in overall responsiveness. At first i was convinced the ui was smoother with less judder, but then I noticed something when my battery fell below 15 percent. The default action it seems is to turn off all big cores and use only the little cluster in order to conserve battery, and I noticed that even with only the little cores active that the ui responsiveness in general, opening/switching apps, was exactly the same. Switched back to interactive and everything feels the same lol
[X Play Original Android Development] b00tbu9:
So the culprit is lionfish in the Kernel :D
[X Play Original Android Development] Chaotick:
CM13 latest and Squid kernel r14 => flashed 2 hours ago and runs good. Lionfish works fine for me :)
[X Play Original Android Development] nplezka:
Hey guys, is anyone having problems in speakerphone calls? Microphone doesn't work on indian stock 6.0 (it works on normal call and earphones) and the other can't hear me and I don't know if it's kernel related (I'm on latest Squid kernel)
[X Play Original Android Development] K.khiladi:
Nope, just made a call and the other person could clearly hear me.

Edit - yes on HANDSFREE MODE I do have this issue. I too am on stock.

---------- Post added at 08:05 PM ---------- Previous post was at 08:04 PM ----------

What do you mean by deep sleep?

It seems scary to me. ?

Just changed the big cluster to lionfish while little one is on demand to test.

---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------

The main thing I noticed is reduced booting time and I feel so relieved. On stock it would take so long to boot up and I hated it.i wanted to change it but didn't knew how to.

Now I am so happy. ?
[X Play Original Android Development] b00tbu9:
It just means your phone does not wake up when it is in locked state.. with Stock don't use lionfish
[X Play Original Android Development] Brehon:
I had the same problem with this kernel in combination with 17th Jan CM12.1 release. No speaker microphone.
[X Play Original Android Development] carl_oak:
Deep sleep doesn't mean that. It means your phone is hibernating. Also, I'm using lionfish on stock and had no problem with it.
[X Play Original Android Development] Zobat:
Only stock has no speakerphone issue i understood.
[X Play Original Android Development] erypo2000@gmail.com:
How can I flash the original kernal from my firmware? XT1562_LUX_RETASIA_DS_6.0_MPD24.65-18_cid7_subsidy-DEFAULT_CFC_V2.xml
[X Play Original Android Development] scottdanpor:
You just restore the boot partition from your backup. You did create a backup right?

From install instructions: " I recommend making a nandroid backup before flashing."

If not, now you get to wipe your entire phone using fastboot in order to return to stock, unless anyone knows of a flashable stock kernel, I have not seen one yet.
[X Play Original Android Development] eskamhl:
It's not a problem if you haven't made a backup of the stock kernel because you can always flash the boot.img through fastboot. The problem lays in the fact that this kernel replaces some system files and you'll have to restore also those ones in order to have everything working.

Anyway I'll make a flashable stock kernel late tonight if it's still needed :)
[X Play Original Android Development] K.khiladi:
This kernel is just great. One main thing I loved about it is the boot time gets reduced (ofcourse after making changes in cpu governor). That was one main thing I hated in Stock rom with stock kernel.

MIC ISSUE - YES I CHECKED IT. IT'S NOT WORKING WHILE THE PHONE IS ON SPEAKER OR HANDSFREE MODE.

If the developer can look into it, that would be great. ☺
[X Play Original Android Development] K.khiladi:
Mine is stock ☺

---------- Post added at 01:56 AM ---------- Previous post was at 01:39 AM ----------

Nope that's not the case. I on stock rom with latest version of this kernel. The mic issue is present. The other person can't hear me while the phone is on speaker mode.
[X Play Original Android Development] ephumuris:
At least we know its not a CM issue.
[X Play Original Android Development] jellysheep:
Thanks a lot! Which toolchain (which package on which distro) do you use to compile?

It compiles fine with arm-none-eabi- on Arch Linux (used your build_cwm_zip.sh script), however it doesn't boot up the kernel (no ADB, no boot animation).
[X Play Original Android Development] squid2:
I've heard of such issues happening with certain compiler and kernel configurations. For CM12.1, I just use the GCC 4.8 bundled with CM's source trees. For the standalone kernel builds I post here, I use Linaro GCC 5.2 https://releases.linaro.org/compone...5.2-2015.11-x86_64_arm-linux-gnueabihf.tar.xz
[X Play Original Android Development] b00tbu9:
Hi Carl I just explained the issue. That's all
[X Play Original Android Development] anks095:
The latest kernal is only for cm 13?and i have seen the latest posts which making me confuse as some one have said that he has used the kernal with cm 12.1.....so this kernal is only for cm 13 or can be used with cm 12.1?
[X Play Original Android Development] b00tbu9:
It is clearly mentioned at the OP only for CM 13 not for 12
[X Play Original Android Development] Denni2306:
Are there any plans for the adjustment of the voltage and overclocking?

Gesendet von meinem XT1563 mit Tapatalk
[X Play Original Android Development] carl_oak:
One nice thing would be to adjust vibration strength. Is that possible or is it buggy to add? Thanks
[X Play Original Android Development] Benjamin_L:
Would love to see that
[X Play Original Android Development] K.khiladi:
I read about different type of cpu governers about what they do from here http://ajgupta.github.io/android/2015/01/28/CPU-and-GPU-governors/

but can someone tell me about lionfish governer?
[X Play Original Android Development] Benjamin_L:
I think squid said its a modified conservative tuned for the play and or other moto devices
[X Play Original Android Development] K.khiladi:
That's great then. Battery life is very good with lionfish governer and no deep sleep problem till now as reported by some.
[X Play Original Android Development] mw1man:
Lionfish

The Lionfish governor combines traits of the conservative, ondemand, and interactive governors. It is designed to maximize battery life without noticeably impacting performance. It responds quickly to heavy loads (similar to ondemand and interactive) while staying within the region of optimal CPU performance per watt. With moderate loads, it periodically votes to raise, maintain, or decrease the frequency. When there are enough votes to change the frequency, it is ramped up and down gradually. The voting mechanism reduces frequency jitter compared to ondemand and conservative.*squid2's*testing had found that this governor uses*moderate frequencies (where efficiency is optimal) more effectively than interactive, ondemand, and conservative. This improved frequency distribution results in a moderate reduction in CPU power consumption while maintaining responsiveness comparable to the interactive governor.
[X Play Original Android Development] jellysheep:
My bad, I was building a Marshmallow commit of your repo and booting on CM12.1, of course it didn't work.

Thanks for the link! It now boots and works fine.
[X Play Original Android Development] erypo2000@gmail.com:
It would be great to get a flashable stock kernel. :)
[X Play Original Android Development] eskamhl:
This, as the name says, is from the Brazilian MPD24.65-18 firmware but it should work with every stock rom ;)
[X Play Original Android Development] erypo2000@gmail.com:
Thank you so much!
[X Play Original Android Development] 70x7:
I just flashed lastest version of this kernel but led isn't active. I'm with stock mm rom. What shall I do?

Enviado de meu XT1563 usando Tapatalk
[X Play Original Android Development] scottdanpor:
It's best to stick with the previous version. You'll lose speakerphone mic with the latest version.
[X Play Original Android Development] 70x7:
I flashed Squid 13b and led still doesn't work. I have to install some app to make it work?

Enviado de meu XT1563 usando Tapatalk
[X Play Original Android Development] scottdanpor:
No, it should just work. How are you testing it?
[X Play Original Android Development] 70x7:
Just waiting the led turns on with screen turned off.

Enviado de meu XT1563 usando Tapatalk
[X Play Original Android Development] scottdanpor:
Did you send yourself an email or text? You gotta receive a message obviously. I test by sending myself an email and quickly shut off the screen. When I receive it the light works.

-More specifically, the screen lights up (Moto display), then turns off, then the light flashes.-

Edit: Actually I just checked and it does flash right away when the screen lights up.
[X Play Original Android Development] 70x7:
Unfortunately doesn't work [emoji20]

Enviado de meu XT1563 usando Tapatalk
[X Play Original Android Development] krishna_g_c:
For me the kernel doesn't get flashed and i stay on stock kernel whatsoever. Tried with r14, r13, r13b. BTW I'm on stock MM.
[X Play Original Android Development] 70x7:
It's true! Same here!

Enviado de meu XT1563 usando Tapatalk
[X Play Original Android Development] scottdanpor:
Sounds like a problem with TWRP. Did you get the one from Squid2? http://xdaforums.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656
[X Play Original Android Development] krishna_g_c:
I guess I'm on an older version of TWRP. Lemme get the new one.

---------- Post added at 06:37 PM ---------- Previous post was at 06:18 PM ----------

Okay I did it. That worked. AWESOME! :D
[X Play Original Android Development] K.khiladi:
It works for sure.
[X Play Original Android Development] 70x7:
It's ok?

Led still doesn't works. Can it be related to Xposed Framework?

Enviado de meu XT1563 usando Tapatalk
[X Play Original Android Development] scottdanpor:
You can try it without, but I'm using Xposed framework. Looks like you have the kernel installed, it should just work, there's nothing to set up. Something must be interfering with it but I can't say what.
[X Play Original Android Development] dreinulldrei:
Had the same issue. Never found out what it was...
[X Play Original Android Development] Jay_B:
I had the same issue installed xposed changed the led time and rebooted phone n bingo led srtarted working after sone time.
[X Play Original Android Development] K.khiladi:
That's a known issue.
[X Play Original Android Development] AnoopKumar:
I know.. ;)I just wanted to let him know that its a issue from kernel side. So if he fix it , I can release the phoenix kernel marshmallow version :fingers-crossed:
[X Play Original Android Development] K.khiladi:
Not many care about it ? (including me)
[X Play Original Android Development] dictionary:
Well, I don't know who the not many are, but I know many DO care about speakerphone. Unless you're talking about his kernel release
[X Play Original Android Development] K.khiladi:
There's always gonna be some who care and some who don't care about this single issue in the kernel. I don't keep a tab on that. ?

I never use the mic while being on speaker mode as I find it awkward.

The positives are much more about this kernel.
[X Play Original Android Development] dictionary:
The fact is, that a LOT of people care about it. There are lots of other phenomenal things about this kernel, but that doesn't mean that it isn't an issue. It's very crucial for a lot of us, please don't try to make it seem like it is moot for most everyone.
[X Play Original Android Development] scottdanpor:
There's lots of us who use the speakerphone mic. Some people use it while driving, that makes it a pretty significant issue for them.

It's easy to work around though, just install the previous build and everything works. That's what I did.
[X Play Original Android Development] AnoopKumar:
View attachment 3618762 Benchmark of upcoming kernel
[X Play Original Android Development] K.khiladi:
But if you read my post clearly I denoted this problem as an "issue".

I said that for some it is an issue and for some it isn't. I didn't forced my opinion on anyone else. I just stated mine. That's it.

---------- Post added at 09:15 PM ---------- Previous post was at 09:11 PM ----------

Everyone has different usage scenario for their devices.

My use of this device doesn't need me to use the speakerphone for calls.

Although someone would find it extremely important while some other wouldn't even care about it.

That's what opinions are. ☺
[X Play Original Android Development] dictionary:
All we're saying, is the way you're speaking about it, is like it doesn't matter to a majority of people. I think that's false. It breaks functionality. If he took out lionfish, or some other optimizations that mattered to you, I'm sure you'd be saying something. Like, I don't ever use NFC, but if it broke, and the majority of people used it, can I say that "not many people care about it", implying that Squid should focus his efforts elsewhere first, because it isn't important. The ISSUE, matters to a lot of people, so don't try to downplay it by saying that not many people DO care about it. That's false. That's all I'm saying. It's not a differing of opinions on if I think it's important or if you do.

Regardless of all this, I know Squid will take of us who DO think this is very important, and is looking into it. I just hate the attitude that since this problem doesn't matter to someone, they can make it seem like it doesn't need to be fixed. (regardless of you not saying it, by speaking about it so nonchalantly gives off the impression of such)
[X Play Original Android Development] K.khiladi:
I never said to squid that its not an issue at all. Although like other users, I confirmed it. He knows about this issue. He knows better than me. It's not a big issue to me but for many others it maybe. I never said it doesn't need to be fixed. It should work properly as it's meant to. Moreover I am no one to tell him on what he should do focus next.

If you thought of my comment as that way, I can't help you then. It's your thinking.
[X Play Original Android Development] dictionary:
*shrug*
[X Play Original Android Development] koimr:
I'm going to agree with [MENTION=2190489]dictionary[/MENTION].

If you don't want your comments to be misunderstood then you should write clearly. There is a big difference (to me) between "I don't care about it" and what you wrote which was "not many care about it (including me)" - one is very clearly an opinion (which, btw, adds absolutely nothing to the conversation) whereas the other comes across as something that's been discussed and collectively dismissed.

Sorry everyone for being off-topic, I just wanted to be clear as when I first read his post in question I DID think this was no longer considered to be an issue and not being looked at (I too am looking very forward to a speakerphone fix).
[X Play Original Android Development] K.khiladi:
I wrote clearly enough.

There's always going to be a section of people which either care for a particular issue or those who don't care for it.

I don't care about it doesn't mean it has to be dismissed as an issue. I mean it's not my kernel so I dismiss it.

Again I just gave my particular opinion.

Someone doesn't like it. I can do nothing about it.

Everyone is free to agree or disagree.
[X Play Original Android Development] 70x7:
Wich module you used to change led time?

Enviado de meu XT1563 usando Tapatalk
[X Play Original Android Development] Zobat:
But I do!

:)
[X Play Original Android Development] K.khiladi:
That's good then ☺
[X Play Original Android Development] koimr:
I don't know what [MENTION=4479268]Jay_B[/MENTION] used but I've used XLED(Xposed LED) before when I was on stock LL with an earlier version of this kernel and it seemed to work fine. Obviously changing the colours didn't work but I was able to mess with the duration and delay, etc.
[X Play Original Android Development] Jay_B:
Sorry rechecked have Gravity Box with xposed and used Gravity box to change led time.
[X Play Original Android Development] pijes:
Sorry, which version was it that doesn't have the mic bug?
[X Play Original Android Development] dictionary:
The one right before r14.
[X Play Original Android Development] squid2:
Squid Kernel r14b

I've posted a new build that fixes the speakerphone mic and call audio level/quality regressions caused by the CAF updates in the last r14 build. I've also patched a recently discovered potential security bug in the kernel (CVE-2016-0728).
[X Play Original Android Development] pijes:
The date in release history seems off