yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] hydroman202:
Thanks for all your hard work!

Im fairly sure your already aware of this, but do you happen to know what exactly the problem is concerning the cdma lte bug for virgin and sprint users? The only reason im asking is because once i know the problem, maybe i could possibly go about looking for a solution. Sorry for this being off topic, i just thought i would ask.
[E 2015 Original Android Development] thrasher194com:
r12 on cm13 is running great.
[E 2015 Original Android Development] jacoghi:
Squid, are you moving completely to cm 13 from now on?
[E 2015 Original Android Development] squid2:
For Lollipop 5.1, the r11e build will probably be the last. However, I will add support for the 6.0 stock ROM once it comes out and Motorola releases kernel sources.
[E 2015 Original Android Development] adrianocolvero:
WIFI not working on cm13 build 25/12 with r12. Wifi turns on but don't connect, keeps on obtaining IP adress forever.

Surnia XT1523.

EDIT: i tryed a clean install of ROM + kernel and now it's working fine. Thank you Squid.
[E 2015 Original Android Development] Anandabasak:
[MENTION=6485916]squid2[/MENTION] can u pls make a kernel for cm13 otus......pls pls pls ....no custom kernels are there for otus cm13
[E 2015 Original Android Development] dandrumheller:
[MENTION=6485916]squid2[/MENTION] I've been seeing random soft reboots on, now, several MM builds on my sprint prepaid xt1526. To this point I've tried Resurrection Remix, the most recent build of Temasek CM, and Temasek ROM with your MM kernel flashed over it. In all cases, I'm not seeing any generation of a last_kmsg in /proc after these reboots.

I'd like to try to help chase the issue, but I can't without logs. I've been out of the loop on chasing this kind of stuff since early Kit Kat on the LGOG. Are kernel crash logs going somewhere else now? Anything I can do to force logs?

Thanks! Looking forward to your continued development on the E 2015.

Dan
[E 2015 Original Android Development] squid2:
On 3.10 series kernels and newer, the logs go to into the /sys/fs/pstore/ directory after a kernel panic. Soft reboots though (where it goes straight to the boot animation and doesn't go into the bootloader and buzz the vibrator) won't generate any logs there because the kernel didn't panic. Soft reboots happen when there is an issue in higher level code (above the kernel). Try my CM13 build and see if you encounter crashes there. It has been fairly stable for me.
[E 2015 Original Android Development] dandrumheller:
Thank you for the info regarding the logs. Guess I've been too far from the bleeding edge for too long ?. These are indeed soft reboots.

I'll give your CM build a shot - guess I should have done that first.

Edit : through set up and getting all my apps reinstalled on your 12/25 CM build. So far it has been 100% stable. Definite improvement on the other builds. Running the kernel included in the build.

Only oddity (or maybe intended behavior) is that mobile network settings are all greyed out. I assume this is due to me not having a sim installed - but they were selectable in other builds, and toggling between sim and nv modes would hide the annoying no sim icon in the status bar.

Thanks for getting me pointed in a stable direction!
[E 2015 Original Android Development] pixiebob:
with squid_kernel_r12-surnia and cm-13.0-20151225-UNOFFICIAL-surnia it's working great and stable on my xt1524.

i obtain better battery life thanks to squid kernel and doze feature

lollipop rom it's the past now :)

.
[E 2015 Original Android Development] DirtyPISTOLA:
Is the new kernal for cm 13 safe to use on the caf 6.0 rom he did use your kernal on there right?
[E 2015 Original Android Development] Agusyc:
Oops... I tested it on PAC-Rom 5.1.1 before I read this and it didn't boot. I got scared! D:

Anyone knows if it works on PAC-Rom 6?
[E 2015 Original Android Development] JaviLerma:
Hi [MENTION=6485916]squid2[/MENTION], i have a bug, I flash 5.1.1 xt1524 version in my xt1527, all ok, but the camera does not work with your kernel. Please fixit before developer for 6.0. Thaks in advance
[E 2015 Original Android Development] squid2:
See my earlier post about the 5.1.1 stock ROM: http://xdaforums.com/showpost.php?p=64409583&postcount=630
[E 2015 Original Android Development] Knuxyl:
I would greatly appreciate continual upgrades to 5.1.1 kernel because I will not be updating to android 6.0.
[E 2015 Original Android Development] soupysoup:
Really? So the Dev should just continue working on 5.1.1 even tho development has all but stopped just bcuz u don't want to update, even tho 99% of his other users want 6.0, if u don't mind me asking, why won't u be updating, and if u want continued support for 5.1.1, learn how to build kernels
[E 2015 Original Android Development] -FuFu-:
Me again :D

I also updatet my Device with the latest RETEU 5.1.1, flashed the latest cm12.1 and flashed the ospray-stock kernel to try, all works fine but i got random reboots.

I dont know if its right, that i post my issue here or in the ospray thread, hope its right here.

I attached a screenshot and the pstore log. for the moment im back on the stock cm12.1 kernel
[E 2015 Original Android Development] squid2:
The log indicates a crash in the WiFi/modem linked subsystem (wcnss). There were issues where old modems would crash when running new WiFi drivers. For CM12.1, the surnia r11e kernel should work. You only need the osprey kernel on the 5.1.1 stock ROM. Also be aware that for my r12 and newer kernels to work (as well as any version of the osprey kernel), you need to update your modem to the version that comes with 5.1/5.1.1 (or newer), else you will experience wcnss crashes.
[E 2015 Original Android Development] -FuFu-:
thanks

i just flashed the new 5.1.1 reteu complete (with modem partition) cause of the wifi crashes with the older modem software with this kernel first 2 or 3 days no issus but today 3 reboots.

maybe i will flash the stock firmware again and try a clean cm12.1 with the r11e kernel

and i think the baseband version in the screenshot is the latest, or not?
[E 2015 Original Android Development] rokban:
This r12 can be used in temaseks cm13 based ROM?
[E 2015 Original Android Development] atomomega:
Please read the OP, it's right there.
[E 2015 Original Android Development] rokban:
Thanks and I am sorry for such a silly question, there was some specific doubt but no excuses.
[E 2015 Original Android Development] squid2:
Squid Kernel r14

I've posted a new release with over 500 commits since the r12 release. I brought in Motorola's changes from the osprey Marshmallow ROM, many of CAF's changes from LA.BR.1.2.7, and security and bug fixes back ported from Linux 3.12.52 (since Linux 3.10.x appears to be EOL or approaching EOL). Some graphics driver updates from CAF appear to have somewhat improved GPU performance for certain operations (mainly GUI animations). These improvements are most noticeable on MSM8939 but MSM8916 appears to have benefitted too.

The r14 release is intended for Marshmallow ROMs (such as CM13). I have only tested it on CM13. It will work with Motorola's Marshmallow stock ROM once they release it for surnia, though I don't think it is out yet. I know the camera will not work on the USA Lollipop 5.1 stock ROM. I don't know for sure if this will work or not on the Europe and Asia 5.1.1 Lollipop ROM. If you are feeling adventurous, make a backup then try it out on your 5.1.1 stock ROM.

I know that the Marshmallow situation for this device is not great at the moment. The old December 25th CM13 build I posted still works, and I'll look at making another CM13 build that works properly when I get time.

Be aware that this kernel requires you to be running the modem provided with the 5.1/5.1.1 stock ROM or newer. You will experience wcnss crashes if you run this with an older modem (original 5.0.2 modem).
[E 2015 Original Android Development] Sands207:
I'm using r14 on Resurrection Remix 6.0.1 and it's been smooth sailing so far. Good work Squid.

Sent from my Virgin Mobile Moto E via CM 13
[E 2015 Original Android Development] ts_firehawk:
Ok, quick question: my device has never seen the 5.1(.1) update (XT1514 variant). Can I flash another variant's modem?
[E 2015 Original Android Development] squid2:
Hmm, I hadn't thought about your variant. The XT1521's modem might work but it might not. If it doesn't I may have to go back to an older WiFi driver as I did for the older surnia kernels to support old basebands.
[E 2015 Original Android Development] rajit:
[MENTION=6485916]squid2[/MENTION] hi buddy, hope I am not going #Ot .. Yea lil bit i guess :p .. I want your help to undervolt my otus ,i mean i want to implement it on my kernel :) hope u will not ignore this :p
[E 2015 Original Android Development] EB20XY:
I have a similar question. Is there any 5.1.x stockrom for europe with a newer baseband official out for europe ?

I never get any update in Stock. That was one reason to switch to CM for me.

And if there is any usable baseband, is there any option to flash it without going back to stock ?
[E 2015 Original Android Development] pixiebob:
r14 is not compatible on CAF6.0.1 surnia, unable to boot
[E 2015 Original Android Development] gameSTICKER:
I observed that in this kernel, "vm.dirty_expire_centiseconds" has a lower value than "dirty_writeback_centiseconds". However as per official kernel documentation and all other Linux distros, "vm.dirty_expire_centiseconds" has a higher value than "dirty_writeback_centiseconds". Is the reversal done on purpose?

NOTE: I'm still on r11e, not sure if it has changed in newer versions.
[E 2015 Original Android Development] dandrumheller:
boots up fine on Vatsal's latest crDroid build.
[E 2015 Original Android Development] deega:
It'll boot on my XT1526/CAF-6.0.1 build 85 but no wifi. Modprobe is looking in /lib/modules but CAF has no symlink on / to /system/lib.
[E 2015 Original Android Development] pixiebob:
with stock kernel of this rom it's also the case wifi don't work
[E 2015 Original Android Development] ts_firehawk:
There is any way to backup the modem? If yes, I can just back it up and flash XT1521's modem.
[E 2015 Original Android Development] squid2:
There is a reteu XT1524 5.1.1 release here: https://www.google.com/url?q=https:...sntz=1&usg=AFQjCNE4A7VUiqYW_M7pU0Ucuc3hl5Hw-g

It might be useful to start a modems thread where people post modems for different regions and ROM versions so that people don't have to download the whole ROM to get one file.
[E 2015 Original Android Development] dandrumheller:
It appears to me that Wanam's partitions backup tool will back up modem partitions. I have made a backup in this way, but have never restored. YMMV

This would be a great idea - was very effective and helpful in the LG Optimus G community. In addition to making it easier to access, I think it would clarify what modems work where and on what ROMs. In my brief hunt to try to get my Sprint XT1526 working on ATT, lack of clear modem info was causing a lot of confusion for me.
[E 2015 Original Android Development] ts_firehawk:
I ended up downloading both firmwares, so that doesn't really matter now lol. I'm waiting until CM13 gets a bit more stable (in other works, I'm waiting for camera to work) to try the new modem + r14 kernel. Lets hope it gets fixed soon.
[E 2015 Original Android Development] dandrumheller:
Fair enough. There are some CM13 based builds with functional camera now.
[E 2015 Original Android Development] jacoghi:
Heads up for people wondering on r14, it doesn't boot on the stock 5.1 rom.
[E 2015 Original Android Development] blcistheking:
r11e is the last for 5.1.
[E 2015 Original Android Development] EB20XY:
Thank for the info.

But if there is such a dependency, it would be good to read about that in the 1st post, perhaps with hints how to make it work in case of an orignal baseband (of 5.0.2).
[E 2015 Original Android Development] dandrumheller:
the requirement IS in the first post. In bold.
[E 2015 Original Android Development] Sands207:
[MENTION=6485916]squid2[/MENTION] is it possible to enable fast charge in the kernel?
[E 2015 Original Android Development] jacoghi:
Squid, I'm seeing two wakelocks on the kernel, called event0 and event4, at least according to bbs. Any ideas on what are these? Thanks again for your amazing work on this
[E 2015 Original Android Development] EB20XY:
You can reflash the original modem if the new makes any problems or is not working better in your area. ;)
[E 2015 Original Android Development] ts_firehawk:
I got somewhat scared that flashing another baseband might kill the device. I have terrible experiences with devices that got bricked (RIP Moto X 2013), so I'm a bit more cautious now. I think I'll just wait.
[E 2015 Original Android Development] EB20XY:
If you flash a modem from any stock ROM of your device it can not brick.

You can get back to the old modem if wanted.
[E 2015 Original Android Development] ts_firehawk:
Well, we have 2 conflicting opinions here. Some one that I'll not remember the name said that the device can be bricked and you said that it can't. I guess I'll hold a bit, but sooner or later my anxiousness will win and I'll flash it anyway. I'm pretty much waiting for the official CM13 builds.
[E 2015 Original Android Development] EB20XY:
You are right.

But if that is true, you can also not flash a Stock-ROM, if it come with a different modem. :)
[E 2015 Original Android Development] soupysoup:
Flashing a modem will not brick your device, at most, if by chance say you flashed a modem for another device u may break radio, but that's about it, as long as you flash the modem intended for your device, there is no chance for a brick
[E 2015 Original Android Development] ElDainosor:
I tested on my XT1527, Movistar Argentina one. No need to flash modem, and works on Resurrection Remix 6.0.1
[E 2015 Original Android Development] squid2:
Squid Kernel r14b

I've posted a new kernel build that should fix the issue with low/poor call audio present in the last build.
[E 2015 Original Android Development] deega:
r14b playing nicely with CAF 6.0.1 85

Only issue I had with previous build of this kernel on the previous build of CAF was no wifi. I've got wifi now. Thanks!
[E 2015 Original Android Development] dandrumheller:
So far so good on latest crDroid. No calls yet to test improved call audio.

Edit: did you make any changes for battery performance? First full charge run since switching, and this thing is a beast! Location services on, Google Now on, gmail syncing. Trying out using chrome instead of FB app, and using old FB messenger to avoid the wakelock issue in the new one. This is heavy usage for me, mostly browsing on chrome, tapatalk and g+. Other than the FB/messenger changes, zero effort towards battery savings. All default kernel settings

This is a pace for 11+ hours SoT on 24 hours off charger. Insane.
[E 2015 Original Android Development] Dunci10:
So, this may be a dumb question, but its something that has bothered me for the last 2 devices I have owned, and noticed no one has ever asked this question on either device. Is there anything about overclocking devices anymore? Back years ago when I had my HTC Evo, then Evo3D, to overclock the cpu, and graphics we just had to flash a custom kernel, install a CPU management app, and run the crap out of it. I fell out of messing with phones for awhile, and when I came back to it, I bought an HTC Desire 510, big mistake of a phone that was, was a huge HTC fan until I owned that. No one ever asked about overclocking on that device, and I chopped it up to no one could figure out how to get a complete running kernel without soo many hickups with the system, just wasn't a very good device. Then I got my Moto E, and I love this phone, haven't even found anything to replace it with, but yet as long as I had this device, no one has asked anything about overclocking. So now I am asking, is there a possibility to overclock this device, not that its slow, just I like pushing the performance of my devices, or is it that they are already shipped now to the point where they are at their peak performance without being able to bump it up without crashes, or burning up, or is it just something that no one deals with anymore? I for one would love to see overclocking again... Sorry for the huge story.
[E 2015 Original Android Development] dandrumheller:
check sirhc's Cypher ROM thread. Soupysoup was talking to him about maybe working up a custom kernel for him, and mentioned looking into possibility of OC.

Definitely seems to be dying out - was very common back in the Aria and SGS2 days. Less so on the LGOG. My guess is that the trade offs in stability and battery life aren't really worth it any more, since routine use requires a lot smaller percentage of total processor power now.
[E 2015 Original Android Development] fivefour:
It's been tried, it doesn't work.
[E 2015 Original Android Development] crazynapkinman:
Any chance for fast charge support?

---------- Post added at 01:29 PM ---------- Previous post was at 01:28 PM ----------

@squid2 I am back in the flashing mood with Android 6. Will gladly test for this device. CDMA Boost mobile.
[E 2015 Original Android Development] DonTin:
Led notification working now on 5.1!

I disabled the Moto App (assist, actions, display) and the led notification started working. It also fixed animation glitch on screen lock and added a bit of battery life.

Rooted Moto E 2015 XT1527 LTE

Stock android 5.1

Squid TWRP

Kernel: Squid kernel r11e lionfish, fiops, min 400
[E 2015 Original Android Development] squid2:
Squid Kernel r15

This new build contains a lot of small changes that contribute to a slightly more polished overall experience. In terms of upstream updates, I brought in Linux 3.10.96 and a new f2fs version backported from Linux 4.5. Beyond that, there are a ton of cherry picks from newer Linux versions (up to 4.4). I included a ton of updates and optimizations to various parts of the kernel library (zlib, CRC, math code, list, and bitmap data structures etc). I updated the CFQ scheduler, and it now defaults to IOPS mode, making it much more competitive, and even beating BFQ and FIOPS at some benchmarks. I updated the pseudorandom number generator in the kernel to use a better algorithm and run more efficiently. I also added an extra parameter to IntelliPlug to specify the minimum number of CPUs you want online. I've set the default for this parameter to 2.

I brought in a bunch of changes to make use of more ARM specific instructions and replaced old instruction combinations with newer more effcient assembly instructions. These are mainly micro-optimizations, but they can have a measurable impact put together. I also backported support for using the new ARMv8 crypto instructions in 32 bit mode. All our MSM8916 family ROMs are presently using Qualcomm's hardware crypto engine instead of software crypto, so you won't notice much of a difference in disk performance for encrypted storage. However, any kernel routines using software hashing or crypto will see a major speedup. Userspace code using kernel crypto can also benefit. If a ROM is compiled with Qualcomm hardware accelerated encryption disabled, you will likely see performance benefits there too. I've heard that ARMv8 accelerated software encryption tends to be faster in practice for disk encryption than Qualcomm hardware encryption, as the soft crypto is lower latency.

[MENTION=4275144]Renan Lazarotto[/MENTION] - don't worry, you haven't been forgotten. I've been a bit busy lately, but I'll try to do a one off surnia build to support old basebands later tonight.
[E 2015 Original Android Development] ts_firehawk:
What an awesome dev we have here! While I thank you for being so kind, I don't think I'll need it anymore - I ended up selling my phone since I got a new one. If you where going to it only for me, I guess that there is a little less work for you now :D Thank you, really!
[E 2015 Original Android Development] spiked_mistborn:
I'm still using the old baseband, so if you do decide to do this I would use it for sure. I've generally just been avoiding toggling WiFi and it's been OK otherwise. I don't want to give up LTE band 12 support though because it works very well in my area.
[E 2015 Original Android Development] squid2:
Legacy Modem Variant

I've posted a build of r15 with old WiFi drivers to support old basebands. The file is labelled "squid_kernel_r15-surnia-legacy.zip". It is built from the "squid_mm_legacy" branch on my github.

If you have an up-to-date baseband on your device, use the normal (non-legacy) variant. Only use this legacy variant if no new basebands are available for your device or you are staying on an old baseband for a compelling reason. I don't plan on updating the legacy variant beyond this one off build (to reduce maintenance effort) unless a major regression is found.
[E 2015 Original Android Development] hydroman202:
Just to be clear, this latest build is only for marshmallow right?
[E 2015 Original Android Development] squid2:
I've only tested it on Marshmallow and it's intended for Marshmallow. It won't work properly on CM12.1 and derivatives, or the 5.1 stock ROM. It might work on the Eurasian 5.1.1 stock ROM, but I haven't tried and make no promises. Same applies to both the legacy and normal r15 variants. The only purpose of the legacy build is to support users running old modems that date back to the 5.0 ROM most of these devices shipped with.
[E 2015 Original Android Development] dwane3:
squid_kernel_r15-surnia-legacy.zip,stock 5.1.1,work fine,but no sim card..Please fix this.Thanks.
[E 2015 Original Android Development] Knuxyl:
i really wish this worked on stock 5.1.1. I have no intentions of updating. Is there anyway to make is cross compatible? That would be awesome. My CDMA device doesn't have full support for marshmallow
[E 2015 Original Android Development] atomomega:
As much as I'd like to see this happen too, you have to realize that by doing that [MENTION=6485916]squid2[/MENTION] would be forced to support 2 kernels for the same device, which is not very practical or efficient development-wise
[E 2015 Original Android Development] sm4tik:
Thanks for your kernel and the update. I've had it installed since I unlocked the bootloader a couple of months ago, steady and stable. Before I go asking elsewhere I thought I'd ask you if you know if kernel adiutor is missing support to set the min. online cores as I can't see it in intelliplug settings? If that's the case, in the mean time before it get's implemented, can you point me to the file I can echo 1 to.

Thanks, s.
[E 2015 Original Android Development] squid2:
Ah, yes, kernel adiutor won't show the parameter since it's unique to my kernel. All the intelliplug settings are located at /sys/modules/intelli_plug/parameters (or something very close to that, don't remember for sure if it is a dash or underscore).
[E 2015 Original Android Development] sm4tik:
kk. I was actually wondering why I hadn't seen it before, but didn't give it much of a thought as it felt quite a natural addition and I thought was an upstream thing. And yes, it was something very close to the path you gave. XD
[E 2015 Original Android Development] Kenny13554:
Did you change the minimum amount of active cores to "2" in your most recent version? I think it used to be just one core to be permanently activated... And if you did change it to "2", why exactly did you choose to?

Kind regards,

Kenny

P.S. I remember there being the possibility to change the minimum and maximum amount of cores for mpdecision within kernel adiutor. Perhaps you can use that for your kernel as well...
[E 2015 Original Android Development] Thexmastermind:
"Sultan@sprocket" should've displayed under kernel version?
[E 2015 Original Android Development] fondblackradiance:
yes