yashsingh1/xdaforums huggingface dataset:
[X Play Original Android Development] squid2:
This is the thermal core control at work. It's not a bug. The stock kernel behaves exactly the same way. Thermal core control shuts down cores witch a mechanism that prevents turning them back on prematurely (to avoid overheating). Once it determines that it is safe to reactivate the core, it will come back online with the exact same settings it had originally.

BCL (battery current limiting) is another mechanism that also shuts off the big cluster in cases where the battery is on the low side, and high load has caused battery voltage to drop below a threshold. It does this to prevent continued high load from driving battery voltage even lower and browning out the device. Once again, this mechanism works the same way it does in stock (though the threshold is lower here, so that you can the the big cores longer).

Kernel Adiutor and similar utilties would report 0 MHz min and max frequencies for a cluster if the first core of the cluster is offline. This is not a bug, the settings are not being lost. Offline cores just don't report frequencies.

Under some conditions, BCL, thermal core control, thermal-engine, and ClusterPlug may interact in a manner that can lead to only one core in the little cluster being left online. This state does result in laggy performance. I had modified the behaviour in the CM kernel to make sure the entire little cluster is online when it is supposed to be online (by repeatedly trying to online offline little cores when we want them online, if permitted by thermal core control). The patch that does this hasn't yet made it over to this kernel yet, though it will be in the next version when I get around to releasing it. I've been a bit busy with work, life, and other projects on the go, so I haven't been doing much on this for the past couple weeks.
[X Play Original Android Development] Benjamin_L:
No need to hurry, I just found it strange that it does not only turn off the cores but also sets the min and max freqs to 0. Will try with your kernel when you will release it :)
[X Play Original Android Development] JohnHorus:
Not charging

[MENTION=6485916]squid2[/MENTION] I keep running into this problem where I plug my phone in and it refuses to charge - rebooting has fixed it in the past, but every time it happens it takes more and more fighting to get it to charge! Do you have any idea if it could be the kernel causing it?

Edit- I should note that I charge it while off, so I don't know if it would begin happening while on, but I assume so. The last couple times it happened I booted and powered off while plugged in(which fixed it in the past,) and it didn't start charging again, so I tried powering on for longer before shutting off again, and it didn't seem to be charging while it was left on, either.
[X Play Original Android Development] maninder singh bali:
i mean that I did fresh installation of the stock Operating System and used the same kernel. the asphalt 8 has the problem not the kernel. the kernel cannot mess with this single game. if there is a problem with the kernel then all the games should experience this . the Real Racing 3 is much heavier that asphalt 8 and its running without any problem.
[X Play Original Android Development] drmuruga:
Kindly add double taP to wake feature in your kernel. Even my old moto e has this feature . Please try to add this feature for lovely phone.
[X Play Original Android Development] JohnHorus:
cores 2, 3, and 4 randomly offlining

[MENTION=6485916]squid2[/MENTION] I tried flashing back to stock to warranty the device, but I was unable to lock it. After getting it all set up again, I've noticed that cores 2, 3, and 4 of the big cluster keep randomly going offline. Do you have any idea why this might be? I'm on stock, so there should be no hotplugging. They don't seem to come back online until I reboot.

edit: Not always the same cores, either. Mostly 3 and 4, but sometimes just 4, and sometimes 2, 3, and 4. Never seems to affect the little cluster.
[X Play Original Android Development] LuizHenrique91:
The device is warm and trying to cool down.
[X Play Original Android Development] JohnHorus:
Really? I've never seen that before, and it's definitely felt warmer than it did. I keep opening my kernel app to frozen speeds too, I feel like something is wrong, though I'm not trying to dismiss your answer.
[X Play Original Android Development] LuizHenrique91:
No problem. One thing I noticed is that the battery temperature is the main reason that makes the phone feel warm. Sometimes the phone is warm because of the battery and the CPU is not that hot. Sometimes (when the day is cold, for example), the battery is cold, so the phone feels cold, but the CPU can get warm anyway.
[X Play Original Android Development] The Analog Kid:
Downloaded a bad zip file here... Nothing inside of it

From my ROOTED XT1563 using XDA-Developers mobile app
[X Play Original Android Development] Benjamin_L:
Seems it doesnt exist anymore
[X Play Original Android Development] The Analog Kid:
Now, that IS bad.... It's more or less what I was looking for

---------- Post added at 11:24 PM ---------- Previous post was at 10:57 PM ----------

Brazilian version, I guess. Which one it is?

---------- Post added at 11:36 PM ---------- Previous post was at 11:24 PM ----------

Is your XT1563 the Mexican version? Which kernel version are you using?

---------- Post added at 11:44 PM ---------- Previous post was at 11:36 PM ----------

I already thanked you, but there is no more files in there anymore...
[X Play Original Android Development] Benjamin_L:
Why not use the real thing? It's not that the kernel is bloated in any way.
[X Play Original Android Development] manub2:
Hi, I tried as you wrote but I failed. Now I have to choose between asphalt 8 and a better phone!
[X Play Original Android Development] The Analog Kid:
Yeah... you're right. I think I'll try 14b. After reading the whole thread (really), it seems to be the right choice

From my ROOTED XT1563 using XDA-Developers mobile app
[X Play Original Android Development] Benjamin_L:
Why 14b?
[X Play Original Android Development] The Analog Kid:
Because after 14b Master squid2 started to make some major changes and I noticed people has been dealing with 'all sorts' of issues ever since (I think I have enough of that with stock 6.0 MM) Also, I've checked the download rating. I guess is the second most downloaded version of them all. That must mean something... Anyway, I think it's a good starting point... and I already did it. And let me tell you that after four hard resets, device is finally booting. I'll be back with a story...

From my ROOTED G730-U251 using XDA mobile free

---------- Post added at 08:43 AM ---------- Previous post was at 08:30 AM ----------

Alright... phone is back, and first thing I noticed: LED is working!... Sorry, I know this is no full test... But I got to say it! So that said, I'll be back with more

From my ROOTED XT1563 using XDA-Developers mobile app
[X Play Original Android Development] The Analog Kid:
I knew it. From all the issues here, I got to have the newest one. Can someone explain why I've lost both SIM 1 & 2 IMEI numbers in "settings/IMEI info", while both IMEI numbers still show in "settings/SIM info", right after flashing kernel version 14b? Luckily, I still have signal (the thin white line between battery and Wi-Fi icons)... This is new. Isn't it?

From my ROOTED XT1563 using XDA-Developers mobile app
[X Play Original Android Development] dreinulldrei:
All fine here... MM 6.0.1. Don't think this is a generic issue...
[X Play Original Android Development] The Analog Kid:
Wait a minute... I've found this "EFS_backup" folder in SD card containing these suspicious zip files. Are these generated by squid kernel or TWRP?... as far as I have searched, here's the missing IMEI!

http://xdaforums.com/galaxy-s2/general/guide-recover-imei-9-steps-t1264021/page2

From my ROOTED XT1563 using XDA-Developers mobile app
[X Play Original Android Development] Jeklund:
I'm having pretty well the exact same issue. I'm going to do a nandroid backup and try flashing back to stock to possibly fix it. My phone is basically just static at 15% in the charger. I've also ruled out the charger and cable specifically by trying different ones.

Edit:I I've booted into recovery and as stated earlier it appears the phone is trying to cool down which is why its not charging. It is however not hot and charging in recovery. I believe its got some sort of bug right now as it says my cpu temp is 429493709 C....
[X Play Original Android Development] JohnHorus:
Thanks for the info! I've tried just leaving it plugged in overnight, and in the morning it was at 100%, though I have no idea what's going on internally so it makes me worry that there's some damage to the phone. At this point, I'm just curious whether it's the phone's hardware, a bug in the stock ROM, or squid's kernel that's causing it. (Seems weird that it would be any sort of software, as the phone is off, but maybe it has to do with the firmware that handles turbo charging.)

If you could let me know what your experience is running full stock, I'd really appreciate it! Thanks again!
[X Play Original Android Development] Jeklund:
I've already flashed and booted into full stock, It did not allow the phone the charge. Once I flashed TWRP and booted in it had the same buggy cpu temp as prior. It seems for me right now the phone will charge only in recovery unfortunately. Also had a complete brain fart while flashing back and lost all my pictures so now I'm trying to see if there is anyway to recover them from the internal memory...
[X Play Original Android Development] JohnHorus:
The data should still be there, but it will be marked as garbage and the system will overwrite it with any new data. The most important thing is to not let the phone download or update anything to the internal memory. I've not had much experience recovering data on Android, but this article seems to have some instructions. Best of luck getting as much as you can back!
[X Play Original Android Development] Jeklund:
Thanks, recuva is a great tool but doesnt really work with MTP Devices. I've attempted to follow a guide and copy the whole partition to my pc then convert and run recuva on that but am having issues getting the partition off.

Would you be able to boot into TWRP and tell me what your cpu temp says at a time when you are unable to charge.
[X Play Original Android Development] The Analog Kid:
Forget about it. This is from my previous Moto G 2014, for which I cared to make this backup with "EFS backup" app. But I just forgot to do the same for my current one... Darn

From my ROOTED XT1563 using XDA-Developers mobile app
[X Play Original Android Development] JaviLerma:
Hi, I'm on stock 6.0.1, what version recommend you?

Enviado desde mi XT1563 mediante Tapatalk
[X Play Original Android Development] Benjamin_L:
Latest
[X Play Original Android Development] The Analog Kid:
I got your point. Seems a practical idea, indeed...

From my ROOTED XT1563 using XDA-Developers mobile app
[X Play Original Android Development] The Analog Kid:
So... No one's ever had "IMEI unknown" issues after flashing squid kernel?... Really?

From my ROOTED XT1563 using XDA-Developers mobile app
[X Play Original Android Development] Benjamin_L:
Nope
[X Play Original Android Development] Gopinath15:
Did anyone tried squid kernel with du official rom. I have gotten few issues. Random reboots with du. Not sure if it's kernel or du itself isn't compatible (op of du says don't complain if you use other kernels.. Though I love squids kernel :P. Help me if both work together for you ppl
[X Play Original Android Development] diegomartinezlovey:
how to enable led notifications?? i have stock 6.0.1..thanks
[X Play Original Android Development] scottdanpor:
You just install the kernel, there's nothing else to do.

Ah wait... there's the 2 files you need in recent builds... lemme find em...

Here's the procedure
[X Play Original Android Development] manan001:
Hey [MENTION=6485916]squid2[/MENTION] no noise from your side bro
[X Play Original Android Development] dreinulldrei:
What noise?
[X Play Original Android Development] diegomartinezlovey:
i put the files sensorhubfw.bin & sensorhubver.txt in system/etc/firmware after reboot and not working
[X Play Original Android Development] scottdanpor:
The problem tends to be the way your browser saves the files. The second must be downloaded in "raw" mode. I had to use a PC.

Or, I made an alternate download link you can use with your phone...

https://mega.nz/#!p9sy3LgL!EZvYrBG7L5EErJWF8MwlGfBgQZUUBGX9hvmzteZ2-wM

Make sure you set permission properly.
[X Play Original Android Development] JohnHorus:
Pretty sure I checked this last night, and if I remember it was like 28. I'll make sure to check next time it has the issue, though at this point I'm pretty much about to just throw the thing in the trash and go back to my old phone. Complete waste of money.
[X Play Original Android Development] Jeklund:
Yeah I'm pretty much getting to that point too. My phone only charges in TWRP, It just stopped reading ANY sd card, and my screen is cracked lol
[X Play Original Android Development] HerySean:
Hello, can anyone teach me how to flash the Kernel? last time i flashed it, my phone was bricked.
[X Play Original Android Development] K.khiladi:
Kernel only breaks device when its not meant for your device or there's some bug in it.

Just download the latest version of kernel and flash it through twrp. that's it.
[X Play Original Android Development] convolution:
does this have the double tap to wake feature?
[X Play Original Android Development] LuizHenrique91:
No.
[X Play Original Android Development] Yogesh_Dude:
Does its latest ver has double tap to wake n chop chop gesture???
[X Play Original Android Development] scottdanpor:
No chop chop, I use xposed torch.
[X Play Original Android Development] HerySean:
Yes ,see did downloaded the latest version and flashed it but all it showed was bootloader warning sign and that's it, it frozed at that point and then black screen and it stayed on that black screen for 30 minutes then I had to restore my backup.

Do I need to do something else before flash the kernel?
[X Play Original Android Development] The Analog Kid:
Well... after a few days, this is my report on r14b, r15b, and r16f versions: r14b deleted my SIM info. No big deal. It was just the info; signal was still active and so far that's apparently only on me. Aside from that, it worked like a charm, with no perceptible issues. Tested for a little more than 24 hours. r15b is another charm; no deleting, no funny stuff, no issues at all. Tested for about 36 hours... As expected, r16f is the best of them all so far. Silky smooth quick. Improved, faster boot. Just noticed a small delay in downloads bigger than 5 MB. Still testing but with no problems at all. It's all fun except for a tiny, very little bit of extra battery drain, but nothing to feel worried about. 24 hours on test now. BTW, Kernel Adiutor's not able to change a thing about vibration intensity, but that's on Kernel Adiutor... I suppose. For me, that explains why squid2 hasn't even touched r16f in about a month. All tested as shipped. I'll mess with it later. Maybe not

From my ROOTED XT1563 DS using XDA-Developers mobile
[X Play Original Android Development] The Analog Kid:
You must take your device's Android version into account and bootloader unlocked (which obviously you already have) before flashing "the latest". From r12 up, it's for MM... and wipe cache and dalvik AFTER flashing kernel. Refer to post 1

From my ROOTED XT1563 DS using XDA-Developers mobile
[X Play Original Android Development] K.khiladi:
Refer to OP for which version you should flash. If you are on LP, then you need to flash a different version and not latest.

On MM, the latest should work flawlessly as no user had any problems about it.

Automated reply by JARVIS
[X Play Original Android Development] HerySean:
Yes,I did it, it worked. thank you
[X Play Original Android Development] fcesf:
Can I flash ultra kernel under the squid kernel or have a normal kernel back again? I noticed battery draining slightly quicker than stock.. I haven't make a backup of the kernel.. I don't want to loose my data and install all again.. Using marshmallux 2.0 squid 16f
[X Play Original Android Development] MonoIiths:
I just built AOSP earlier

I guess CM has exported these needed .c files elsewhere or something; maybe the kernel I downloaded had errors during unpacking that caused these files to... somehow not unpack? They are needed to build period. Maybe this has changed in very recent updates.

Do you know why these .c files are no longer required in CM but are elsewhere?

Either way the sources for that kernel will not build without changes in USB and some other .c files which are missing; but I have not fired off a build with it in CM so I'll apologize here, you are probably right and these are probably local files in Cyanogen. I'm not repoing the source to confirm soooo.

It's really not because it happens all of the time, when Camera is broken in kernel source that already has missing .c files all over the place, but does work under the authors already compiled release It's pretty easy to draw that conclusion because chances are; it's already being considered at that point

It's not that unreasonable esp. considering as I said; I see it all the time.

That being said I'll apologize for being ruthless and assuming you were making a scumbag move; feel free to hold it against me but never think that's an unreasonable assumption

---------- Post added at 09:49 AM ---------- Previous post was at 09:41 AM ----------

Either way; allow me to push an updated version of it with proper configs so AOSP can be built for it by other folks
[X Play Original Android Development] squid2:
The kernel does not need any external or additional sources to build. Just follow the instructions in the file called "BUILDING" at the root of the source tree. All the build infrastructure, including the flashable zip making stuff is there. The builds in this thread come from the "squid_linux_mr1" branch and use the "msm8939-lux_defconfig". Be aware that one file in the WiFi driver triggers a false positive array bounds warning on some compilers. It doesn't happen on Linaro 4.9.3 (that I use), but on the CM12.1 branch I recently disabled that warning for the particular file that was triggering it so that other compilers can be used.

If you have any other questions, feel free to ask here or PM me. In the future, please don't jump to conclusions or make accusations before contacting the person involved. Thanks.
[X Play Original Android Development] MonoIiths:
I built AOSP and I'm telling you it does need additional things.

If you would like to know more feel free to PM me

Feel free to talk to me like I don't know what I'm doing, but remember you hit CyanogenMod first and I hit AOSP so... the requirements are clearly very different here so I feel I'll have to wing it :>
[X Play Original Android Development] Nico3d3:
I don't want to start a flame war and, by the way, I love the work of Squid2, his kernel work great on the Moto X Play and he's quick to correct bugs. I'd just like to ask what is so different between AOSP and the original X Play firmware? The original firmware is already really close to AOSP Android. A few apps are added but none of them are superfluous. That's why I don't quite understand why it would be so hard to build for AOSP. Anyway, I don't want us to hijack the Squid2 kernel topic so, we should start a new thread if we want to discuss about a way to compile a kernel for AOSP.
[X Play Original Android Development] Methodikull:
If one wanted to flash back the original kernel, how would one go about doing so?

I bought this phone a couple days ago and it's actually a huge disappointment. I want to get the Nexus 5X instead. I'm looking to return the phone but I've already rooted, installed custom firmware and installed the custom kernel. Is there a way to revert to stock kernel?
[X Play Original Android Development] paugustin:
It's easy, just restore the boot that you backed-up before flashing the kernel :D

If you haven't done so then look for the thread that lists the stock firmware, download the one for your device, extract the boot.img and fastboot flash it.
[X Play Original Android Development] Toxina:
[MENTION=6485916]squid2[/MENTION] is it possible that you look into the way the big.LITTLE cores work (and adjust them)? i just tested it and below 20% battery the big cores - all 4 of them are deactivated. if i plug it into my charger theyre back activated. and when the phone is over 20% (i was at 22%) the big cores are all active again.

also antutu benchmark is around 34k if all cores are active. and only around 26k when the big ones are off.

edit : fyi this happens both with your kernel + stock kernel.

edit : added pictures with unplugged + low battery (big cores inactive) & plugged + low battery (all cores active)

take a good look at the CPU integer & float point - its more than the double when i plugged my phone into the charger.

edit again, lol : also the gpu doesnt reach its 550mhz EVER, the maximum it gets to is 400 (also tested on stock + ur kernel)
[X Play Original Android Development] squid2:
The reason behind this is to save the battery. When your battery is below 20%, you usually want to make the most of what's left rather than burn through the remainder to get maximum performace all the way down to zero. I could look into how this is implemented and perhaps add a tunable for the battery level at which this kicks in. This is also probably what was causing issues with battery below 20% on ROMs using the hotplugging kernel on BoulZorDev.

My planned focus for the next release is power management on big.LITTLE systems. I don't yet have a specific plan for exactly what I'll implement, but I'll look into it over the next few weeks.
[X Play Original Android Development] Toxina:
a tuneable really would be amazing, since is stupid to force people to have an even laggier device :).

also thanks for replying & all the hard work youve done so far!
[X Play Original Android Development] paugustin:
You know you can shut down the power save mode and change the threshold at which it kicks in?

On the battery page, click on the 3 dots on the top right of the page an choose "power save".
[X Play Original Android Development] squid2:
Ah, didn't know about this. Thanks for the tip. Not sure if this is what turns off the big cluster at 20% though, as it looks like power saving mode is supposed to kick in at 15% by default.
[X Play Original Android Development] Tim3tripp3r:
I shortened up the original quote as only the last is relevant to this post.

I attached a screenshot taken with kernel adiutor and it shows the GPU @550

Just a FYI for you to ponder.

I am just monitoring with KA - nothing has been changed I'm still on stock kernel.
[X Play Original Android Development] Toxina:
kernel adiutor does, but try cpu z (go to the appstore) and youll see that the gpu never goes above 400mhz even if you use userspace as the governor, set at 550mhz :)

---------- Post added at 08:07 AM ---------- Previous post was at 08:05 AM ----------

the phone wasnt in power save mode. otherwise the top and bottom would be highlighted in orange.
[X Play Original Android Development] XMoDuLeSx:
Doesn't need to be in power save mode, the stock kernel and rom are bugged so let's wait for the marshmallow update
[X Play Original Android Development] Methodikull:
Didn't know that was the kernel. Thanks.
[X Play Original Android Development] lennis:
Working in motorola x play dual sim ?

Enviado desde mi Aquaris M5 mediante Tapatalk
[X Play Original Android Development] leonardoroza:
Yes

Moto X Play Nice
[X Play Original Android Development] danger2u:
to go back to stock kernel ,must flash only the recovery or all the system?

thanks
[X Play Original Android Development] paugustin:
Please just read a few post back.
[X Play Original Android Development] Abravanelsenor:
Closed! I pay! I need this function! I'm from Brazil , how to proceed? Regards.

---------- Post added at 06:23 AM ---------- Previous post was at 06:22 AM ----------

yes!