yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] torch2424:
Hey Squid! I'm also having bootloop issues! Not like traditional bootloops, but oddly enough, my device boots just fine, however, about 5 minutes later, it reboots, and I also noticed slower performance. I was using the latest kernel for non cmda devices. However, data was working perfectly fine, thank you for the work squid!
[E 2015 Original Android Development] crazynapkinman:
Quick question about this kernel. Did it undervolt all processes or just the CPU?
[E 2015 Original Android Development] squid2:
Just the CPU. Perhaps I should create a test build with stock voltages to rule out the undervolting as a source of trouble.
[E 2015 Original Android Development] crazynapkinman:
I will gladly test for you

CDMA 4g LTE variant

Boost Mobile
[E 2015 Original Android Development] squid2:
Test builds of r4 without undervolting

I've made test builds of r4 with stock voltages. Those having issues with the standard (undervolted) version should try these out. I haven't tested these myself.

GSM Version: http://www.mediafire.com/download/6kyml12xpib47uw/squid_kernel_r4-noUV.zip

CDMA Version: http://www.mediafire.com/download/m2ag1akglp77lr1/squid_kernel_r4-CDMA-noUV.zip

I've been running a different version of my kernel with the same undervolt as r4 for a week without any issues. I don't know if my phone is just more undervolt friendly than usual, or if something else is at play.
[E 2015 Original Android Development] crazynapkinman:
Downloading now

---------- Post added at 08:57 PM ---------- Previous post was at 08:52 PM ----------

Flashed and booted without a problem. CDMA Boost Mobile variant
[E 2015 Original Android Development] squid2:
Ah, good. Watch to see if it remains stable over the course of a day or two. The normal r4 undervolted by 30-50 mV at the low end, up to ~100 mV at the high end. I guess that was too harsh for your phone.

Even with the stock kernel, not all phones run the same voltages. Qualcomm's vreg driver allows you specify voltage ranges for different frequency ranges, and specify a reference voltage for each range. They then test each individual chip to see how well it handles undervolting, and blow some fuses to indicate how much undervolting the device supports. The driver factors in the factory test results blown in fuses when computing the voltage for each frequency. Some phones (like mine) can handle greater levels of undervolting beyond the normal ranges.
[E 2015 Original Android Development] crazynapkinman:
Thanks. Would you know a place to find stock recovery? I would rather not have to flash entire firmware...

Or is that the only option to getting stock recovery?
[E 2015 Original Android Development] squid2:
Here is one signed for the Canadian region (CID 14): http://www.mediafire.com/download/d9u6cttjhcf6htq/surnia-stock-recovery-LXI22.50-CID14.img

It will run on all Moto E LTE models with an unlocked bootloader, but I'm not completely sure if it will allow OTA updates on all variants.

If you want to accept an OTA update, I'd suggest flashing everything to the correct signed stock version for your model beforehand.
[E 2015 Original Android Development] joex55:
SIM card error !!

i HAVE RUN INTO 1 PROBLEM THAT CAN BE DUPLICATED EACH TIME. iF I do a profile update I get an error Message that the SIM card is faulty. I love your work and hope there is a solution to this. Thanks joex
[E 2015 Original Android Development] tattooedgod:
A couple of ?

Are you going to add new governors like maybe smartass and any idea if you going to add gpu overclock maybe to 533mhz the moto g could do it so didn't know if any plans. Reason asking about that is that if you use gpu to render 2d objects it saves on power instead of using cpu. Also could we get fiops in I/O Scheduler runs things smooth. I'm not pick anything apart it's a great after market kernel just trying to help improve what great work you already put in.
[E 2015 Original Android Development] squid2:
I could add in a few more governors and schedulers to the next release. Personally, I'm happy with the ondemand governor and cfq schedulers, but I'm sure others have different preferences.

I had looked into CPU and GPU overclocking a couple weeks ago, but the 8916's device tree is a bit different from the 8226 in the G. I tried to implement device tree changes similar to those in the G kernels for GPU overclocking, but they didn't seem to change performance, suggesting that something else needs to be changed as well. I had also tried CPU overclocking to 1.4 GHz at one point (look in the history of the master branch), and the OS did report that the CPU was running at higher frequencies, but benchmark scores remained the same, suggesting that the CPUs were actually still capped at 1.2 GHz. If someone can figure out how to get CPU and/or GPU overclocking to work on the 8916, I'll gladly include it.
[E 2015 Original Android Development] squid2:
I presume you are on Boost Mobile. The current ramdisk I'm using for Boost is based off the GSM ramdisk with minimal modifications. I did this instead of using the Boost ramdisk because I wanted to disable the hidden carrier bloatware that the Boost ramdisk loads.

I'm not familiar with CDMA Android phones. Is the "profile update" feature important? If it is, I can use the normal Boost ramdisk (with all the associated bloatware).
[E 2015 Original Android Development] crazynapkinman:
I cannot even find "profile update" in settings or anywhere on the device... Boost Mobile user.
[E 2015 Original Android Development] joex55:
the profile is in settings system update. I would appreciate it if you made one for Boost like you said. Thanks
[E 2015 Original Android Development] squid2:
Squid Kernel r5

I've posted a new release, version r5. Downloads are up on the downloads tab.

I've reduced the amount of undervolting, hopefully that will solve the stability issues on the less undervolt-friendly devices.

Among new features, I've added the FIOPS I/O scheduler, updated the kernel to Linux 3.10.75, and included new f2fs drivers backported from Linux 4.0. I've also switched to the stock Boost ramdisk for the CDMA variant, hoping to fix the carrier-specific issues reported by [MENTION=2799284]joex55[/MENTION].

As with the last release, I haven't been able to test this new version for certain reasons. Try it out, and let me know if you have any issues.
[E 2015 Original Android Development] crazynapkinman:
R5 CDMA: Confirmed working on Boost Mobile variant. Using fiops I/O.

---------- Post added at 09:19 PM ---------- Previous post was at 09:18 PM ----------

Profile update is fixed for my phone as well

---------- Post added at 10:03 PM ---------- Previous post was at 09:19 PM ----------

Update: "Update Profile" still has issues. It completed but then caused the SIM Card error. Corrected itself, however. No reboot required. I just pressed "Continue" and it loaded my network sim.

---------- Post added at 10:05 PM ---------- Previous post was at 10:03 PM ----------

I don't know why you would ever use "update profile" anyway...
[E 2015 Original Android Development] joex55:
CDMA 5 is working good but the SIM error still is there but only if I use profile update. I only use profile update if I have a connection problem or to activate my phone after I swap phones.

Thank you
[E 2015 Original Android Development] fix-this!:
Phone seems to get very laggy on v5. Any chances of zen scheduler and maybe a few alternative cpu govenors?
[E 2015 Original Android Development] -FuFu-:
quick response :)

no reboot on cm12.1 with r10d after 36 hours uptime, i think i will stay on that version, but i will flash r10f in the next days for testing.
[E 2015 Original Android Development] xpmule:
No reboots today.

I didn't think i would get any..

I did my running around town routine today and before i had reboots on more than 1 day.

But that was with the second newest firmware package US Retail and the Telus 5.0.2 radio.

There may be something to what Squid said about possible reboots with the older radio NON-HLOS.bin

I'm running the newest US Retail with Stagefright fixes and no reboots and nothing logged.

And a week ago roughly i did have multiple random restarts i recall at least 3 or 4 times on different days.

I also see no reason to use the older radio.. i can still setup my phone with either one the same.

Before i updated to 5.1 i was only using r5

That one is for the old firmware / radio i think.. and don't recall any crashes with that.
[E 2015 Original Android Development] Knuxyl:
newest has wifi probs, auto turn on every now and then. idk what triggers it yet
[E 2015 Original Android Development] atomomega:
Newest Squid kernel?
[E 2015 Original Android Development] EB20XY:
I can't flash latest g-version on top of latest CM12.1 (from 20.11.) any more. :confused:

I produces in twrp an error to unmount /cache one time and always something like "full selinux activated", but no successful flash happens. :eek:

Can anyone reproduce that issue ?

Nevertheless the ROM CM12.1 is starting fine and works good.
[E 2015 Original Android Development] spiked_mistborn:
I just installed r10g over CM12.1 11-20 no problem on my xt1527. Have you tried wiping cache?
[E 2015 Original Android Development] iks8:
I'm using 10g on 5.1.1 aosp without any issues for now :D great job all is smooth and stable
[E 2015 Original Android Development] EB20XY:
yes, wiped cache and dvalik before.

Also I used 10g before on CM12.1. But since flashing 20.11. version vom CM I can not flash kernel ontop an can't understand why. The ROM itself is starting and running fine.
[E 2015 Original Android Development] atomomega:
Are you using the latest TWRP? Also, see if you have read-only enabled
[E 2015 Original Android Development] EB20XY:
Finally I could flash it again. :o

But in the order CM12.1 => Kernel 10g ==> open gapps

In order CM12.1 => open gapps => Kernel 10g the problem occurs.

Perhaps latest gapps is anyway corrupt in updating patition details ? :confused:

Perhaps I just loaded the wrong gapps (4.0) or something.

Just made it again with latest micro (before nano) and now it seem no problem.

Thanks.
[E 2015 Original Android Development] PriPhaze:
You dont need to flash gapps every rom update do you?

I have not flashed it since i started using pac man like 1 month ago
[E 2015 Original Android Development] EB20XY:
thanks for the info.

also i just flashed latest twrp.

I didn't recognized, that squid made so many new subversions of it. :)
[E 2015 Original Android Development] Knuxyl:
Since a reboot I have not had any problems with the wifi. No other problems either :) Thank you for such a great kernel.
[E 2015 Original Android Development] ampelift:
Hi all , can i flash it on CAF-6.0 ?
[E 2015 Original Android Development] DroidFreak32:
I've tried. Twrp freezes. Caf already uses a fork of this kernel so there's no need to flash it[emoji1]
[E 2015 Original Android Development] pollazht:
The link to Q9Nap's TWRP flashable stock 5.1 rom for GSM models in 3rd post is dead. Could you replace it ?

Thanks in advance.
[E 2015 Original Android Development] Kenny13554:
Hey Guys,

unfortunately, Q9Nap's 5.1 zip seems to have gone missing (http://batakang.com/ftp/devs/mhous3...74921.surnia-LPI23.29-15-logo-boot-system.zip). Does anyone know an alternative download location for that file?

Thanks!

Kenny
[E 2015 Original Android Development] squid2:
[MENTION=1567974]Q9Nap[/MENTION] had taken down the file some time ago. The alternate way to flash the 5.1 stock ROM is through fastboot. You can find fastboot fishable stock software in the stock ROM thread.
[E 2015 Original Android Development] spiked_mistborn:
[MENTION=6485916]squid2[/MENTION] so far no reboots on r10g using interactive. It's been over a week now. Looks like you were probably right about the unpatched race conditions.
[E 2015 Original Android Development] Filz0r:
I think I'm having a problem with Bluetooth on the latest build. I have an Bluetooth headset, and lately, my phone soft reboots while listening to music.

I tried to see if there was a log at sys/fs/pstore but there wasn't anything recent.

BTW I'm running the latest build of CM 12.1

Thanks a lot for the work so far!
[E 2015 Original Android Development] xpmule:
No reboots now too.

I for sure had a few before but i had been using the radio file from 5.0.2

when i went with full 5.1 files i have had 0 reboots.

I knew the 5.0.2 version was only compatible with Squid's v up to r5

but i did not know it woudl still be a problem ONLY using the old radio files.

I think he said this was a known issue on previous page.
[E 2015 Original Android Development] thrasher194com:
I got stock 5.1 rom, twrp and r10g all seems good. No random reboot like cm12.1
[E 2015 Original Android Development] Filz0r:
Sorry but I checked and I had the 10d version installed by mistake, because of an CM 12 update, but I also I have random reboots when using Bluetooth audio... If anyone can tell me how can I get a logcat after this error, please do tell me
[E 2015 Original Android Development] spiked_mistborn:
Here you go

Please let us know which governor you were using, and also what is your baseband version.
[E 2015 Original Android Development] starkly_raving:
[MENTION=6485916]squid2[/MENTION] would just like to take a moment and applaud you on your support for this little unloved device. Your work as well as the work of other developers is a testament to why our dev community is so important... Keeping devices relevant passed their gloomy EOLs etc. Well done sir and stay motivated. [emoji106]
[E 2015 Original Android Development] Filz0r:
Here is a link to a logcat of the latest random reboot

https://drive.google.com/file/d/0B-X6n6ML6m_JQXMwU01VYy1zWDA/view?usp=docslist_api

And BTW I think that this only happens when LTE is off, but I can't give any guarantee
[E 2015 Original Android Development] squid2:
That log is a bit strange. It shows an error when executing a TrustZone call, and then triggers a TrustZone watchdog bark. It also shows that the device never completed boot, and died 24 seconds after powerup. I have no idea what's behind that one, but the log is probably not showing what you want it to show.
[E 2015 Original Android Development] Filz0r:
I think I've this only happens when I'm using performance mode instead of balance. It happened again this morning I'll try and send another log

Edit: here's the link to the latest log https://drive.google.com/file/d/0B-X6n6ML6m_JdUY5d1J5RnFOMWs/view?usp=docslist_api
[E 2015 Original Android Development] zedaale:
What are the adjustments we you can do with MDP5 KCAL colour control?

I've just bought my moto g3 and don't like the colour callibration very much. I'm trying to figure out if it can be changed or if it is possible to change values (RGB, Gamma) with this kernel before unlocking the bootloader and voiding warranty.

Thanks a lot.
[E 2015 Original Android Development] squid2:
With this kernel, you can adjust RGB levels along with hue, saturation, and gamma.
[E 2015 Original Android Development] pdiddyfan:
Anyway to find some good profiles to use for the Moto E that's work in the KCal app? I have some, but the values are higher than the app allows.
[E 2015 Original Android Development] squid2:
Squid Kernel r11e

Despite the large version jump, this is a fairly minor update for MSM8916 (the rest of the r11 releases were focused on MSM8939 specific features which is why I didn't release them for MSM8916). This build fixes some race conditions in the CPUFreq code for the Lionfish/Conservative/Ondemand CPU governors. It also includes other minor bug fixes.

[MENTION=4978031]spiked_mistborn[/MENTION] - let me know if the occasional kernel panics you had with Lionfish go away on this build.
[E 2015 Original Android Development] spiked_mistborn:
Thanks! I'll let you know. I've missed the power savings from Lionfish, hotplug, and undervolting.
[E 2015 Original Android Development] jacoghi:
Man, let me tell you something. This kernel of yours, is just ridiculous! ;). Seriously, I've never seen such a thing! Thanks for sharing this, simply amazing.
[E 2015 Original Android Development] xpmule:
i wonder if i use stock Rom how much am i missing out on ?
[E 2015 Original Android Development] spiked_mistborn:
The newest version of the kernel should work on the stock rom as long as you are on version 5.1. It should speed things up a little, and improve your battery life. There are recommended governor settings in the OP. If you have TWRP installed just make a backup of the boot partition (or do a full backup if you don't have one already) in case you want to go back to the stock kernel.
[E 2015 Original Android Development] xpmule:
Too late for the backup LOL

I backup but with Squid's kernel etc..

If i want stock kernel i re-flash stock firmware and start over..

Also last time i tried to get info about " governor settings" it ended up in drama.

If i am not mistaken you need a custom ROM to change those options..

Which is why i posted what you quoted ;)

See what i mean NOW ?

I actually just did a TWRP backup to SD card and copied it to my PC too.

Before i apply his new build just updated.

Too recap.. i get the LED mod and misc stuff but if i am on stock rom

and i did nothing with any governor settings stuff anywhere then what am i missing ?

Is there a way to switch governor settings on up to date stock 5.1 roms ?

I'm running the newest one with all Stage Fright patches.
[E 2015 Original Android Development] spiked_mistborn:
I use an app called No-frills CPU control to adjust the governor, but there are many similar ones out there. It's the same for stock or cm; you just need to have root access. Don't worry about people giving you a hard time for asking questions, all of us had to learn how to do these things.
[E 2015 Original Android Development] atomomega:
Well, for one, you will be missing out on tweaking your kernel settings to get either better performance or better battery life, depending on what you need.

As long as you are rooted, even on stock 5.1.1 you can use Kernel Adiutor to switch governors on-the-fly (and tweak many other kernel settings) or as [MENTION=4978031]spiked_mistborn[/MENTION] recommended, you can use No-Frills CPU to switch governors (if that's the only thing you want to tweak since it offers minimal options).
[E 2015 Original Android Development] xpmule:
Thanks guys that is useful info.

I think No-frills CPU control was mentioned almost 50 pages ago but i forgot..

The other one sounds interesting too.

My point was a lot of new users may not knows these things exist at all.

And they may not know what is possible.. it's not talked about much.

If i was Squid i would have mentioned the 3rd party tools to mod the Kernel setup in the first post.

EDIT:

Well it's been working great ..this 11e version.

I got No-Frills and changed to Lionfish and it seems way snappier i think.

Like i mean in anything i do and especially the UI when going from off to on.

I wish i had looked into it sooner but was more concerned with other Moto-e stuff.

I am suppose to be using CDMA for example but with other firmware's all i ever get working is GSM.. so that exhausted me tinkering for ever.. and failing.

Anyway great job on the kernel Squid.

Do you have a Bitcoin address posted somewhere for donations ?

I don't have much right now but some of us fans might want to send ya some coins.
[E 2015 Original Android Development] P0PETIN:
[MENTION=6485916]squid2[/MENTION] I don't know if this is kernel related or WiFi driver related but when I try to spoof my MAC address the phone is unable to do it but when done on my Galaxy S5 it works also on my ZTE Warp Sequent, What do you think squid? I tried on stock also on CM12.1 but with your latest kernel and btw you rock dude! Thanks for the hard work!
[E 2015 Original Android Development] spiked_mistborn:
[MENTION=6485916]squid2[/MENTION] I had one reboot on lionfish (pstore) about 24hrs after installing r11e, but it's been good since then. Current uptime is 112hrs, so I don't know if that was just an anomaly or what. I don't feel like a single reboot is a big enough sample size to say conclusively what the cause is. I did have one reboot on the stock cm kernel prior to installing r11e also, but I think I overwrote the logs. I won't have time until this damn writing class is done in a couple weeks to test on a clean install, plus I'll probably wait until the 6.0 builds stabilize more because of the annoying app-to-sd bug that has been in all 5.x based builds so far.

Edit: Looks like I spoke too soon. I had a reboot while I was sleeping, but it looks like it's wifi related. I am back on the 5.0.2 baseband to do some lte band 12 testing, and I know there is a potential issue with this baseband and wifi. pstore

[226674.510610,0] wcnss subsystem failure reason: boot_crash_debug.c:156:apps_wcnss_reset_req interrupt detected!.
[226674.510635,0] subsys-restart: subsystem_restart_dev(): Restart sequence requested for wcnss, restart_level = SYSTEM.
[E 2015 Original Android Development] EB20XY:
3.10.94 is out. Are there any interesting commits in ? :)
[E 2015 Original Android Development] squid2:
Yep, that looks like the old baseband issue causing the wcnss crash.
[E 2015 Original Android Development] squid2:
I've merged it into my Marshmallow branch but there aren't any really notable changes in it so I haven't done a new release just for it.
[E 2015 Original Android Development] EB20XY:
The "Marshmallow branch kernel" works only on 6.0 or also on 5.1.1 ?
[E 2015 Original Android Development] pixiebob:
with new rom XT1524_SURNIA_RETEU_5.1.1_LPI23.72-66, and last kernel r11e all working except camera.

back to kernel stock and camera working.

will be great to build new kernel fully compatible with last stock rom
[E 2015 Original Android Development] Cissmayazz:
I can confirm this. Camera works in snapchat but not in the stock camera app or in Google camera.

BTW can you please give me the link to the stock 5.1.1 kernel? Many thanks
[E 2015 Original Android Development] pixiebob:
original kernel stock is inside XT1524_SURNIA_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml.zip , file is: boot.img.

you can flash it easily with application like rashr
[E 2015 Original Android Development] squid2:
Ah, the Europe version is 5.1.1 with a different build number from the USA 5.1 model. Your build version is the same as the osprey stock ROM. Try flashing the osprey stock version of my kernel: http://xdaforums.com/devdb/project/?id=11960#downloads

The squid_kernel_r11e-osprey-stock.zip version is what you want
[E 2015 Original Android Development] hydroman202:
I have a surnia xt1526, sprint. If I tried to flash the us retail version (which I'm not sure would work), but if it did, would your kernel work on it still?
[E 2015 Original Android Development] pixiebob:
you are right , this is the good version for us , camera working this time , really thanks squid .
[E 2015 Original Android Development] Fedray:
This works in 5.1.1 right?

Edit: Flashed latest kernel and looks like yes, all working atm.

Edit2: Needed to flash osprey kernel because of camera, now all working :)
[E 2015 Original Android Development] stevedensmore:
Is there anyway to stop the screen from occasionally glitching out (flashing black and blue)?
[E 2015 Original Android Development] Fedray:
I have the same question :p actually im not sure if its because of kernel, if someone wanna try it happens when u open some menus like in google chrome or twitter
[E 2015 Original Android Development] atomomega:
I had the same problem with the screen, but not anymore since I moved to PAC ROM + squid
[E 2015 Original Android Development] squid2:
Squid Kernel r12

Just to be clear, this version of the kernel is only for CyanogenMod 13 and derivatives. In particular, it is meant to work with the December 25th build I posted. It won't work on ROMs built with older sources. It won't work on the stock ROM.

As you can see in the changelog on the first post, this build contains a bunch of incremental improvements to performance and reliability. This should be the smoothest version of the kernel I've ever posted here.