yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] KonomiKitten:
I have a bet I know what is going on, if you're using TWRP to flash the kernel make sure you go into Mount and mount /system as writable, not read only! squid2's zip does not account for /system not being mounted and it doesn't attempt to it just reports success, try this and see if it works for you good luck. If it doesn't it might be your baseband.
[E 2015 Original Android Development] gameSTICKER:
As you said, if you've received official 6.0 update by OTA, that means you have 6.0 baseband (because baseband is ALWAYS updated in official OTA update). But the kernel version you're trying to use, i.e. 11e only works with 5.0/5.1 baseband. Even CM12.1's built-in kernel will not work with 6.0 baseband. So here are your options:

Use CM13 + latest squid kernel (anything above 11e will work) or built-in CM13 kernel

Downgrade your baseband + use CM12.1 + 11e kernel

Option 1 is simplest, as you'll not have to flash baseband. CM13 the new kid, you can give it a try if you wish.

If you are skilled enough, and can/want to flash baseband, I'd personally recommend option 2. CM12.1 is rock solid, feature complete, fast and stable for day to day use.
[E 2015 Original Android Development] rokban:
Squids cm13 unofficial with the latest kernel is rock solid ,fast and super stable. If someone has latest baseband they should try it at the least..
[E 2015 Original Android Development] debojyotidey:
I am currently running cm12.1(with built in kernel)....also i have used cm13 too
[E 2015 Original Android Development] :
Squids own recommendation is that devices need to use the updated 5.1 baseband to use his latest CM13, so anyone that hasn't updated or won't update and then run into trouble can't really complain-i was until a week ago, one of these people, having the older 5.0.2 baseband, but reluctant to flash it seeing as squids latest release of his CM13 was so stable.

After some ADB/fastboot issues (with my laptop, not the phone) I upgraded to the newer baseband, and I have had no issues at all.

I just find it strange that reading these posts some people using different moto E variants (ie XT1521, XT1523, and XT1526) have so many more issues to my own XT1524.

[MENTION=436307]squid[/MENTION]-are these variants really so different?

And what the hell is a proprietary blob?
[E 2015 Original Android Development] rokban:
I use XT1521 myself :) but I use only one sim.
[E 2015 Original Android Development] gameSTICKER:
As I said, your baseband (2020629) is clearly 6.0 baseband, you can NOT use a 5.1 ROM+Kernel with this. So you'll have to use either one of the two solutions I suggested.
[E 2015 Original Android Development] debojyotidey:
But it seems i am running a 5.1 ROM+KERNEL(maybe)
[E 2015 Original Android Development] :
As has been said and explained to you, I'm also sure if you have received the 6.0 mm ota update (that you quoted you had migrated from) you cannot run cm12.1 and kernel, I'm no expert but I'm sure I've read here you cannot down grade modem/baseband.

I think you should do what [MENTION=3361142]gameSTICKER[/MENTION] suggests, I think this is why your WiFi does not work, but I may be wrong.

I'm also puzzled as to after receiving the 6.0 ota update, why would you want or need to downgrade back to CM12.1?

I'm intrigued by this......is the new stock update that bad I wonder???

This is the first report/comment or instance I've found on XDA of anyone downgrading from the new 6.0 stock ROM back to CM12.1.....

What you do is obviously your own business, and in no way am I trying to berate/or be critical of your choice, but I'm a bit puzzled!!

Please tell me!

:-/
[E 2015 Original Android Development] debojyotidey:
Stock MM can not deliver performance any closer to cm12.1...... cm12.1 has been my favorite choice of all custom roms out there....but as u guys say that i CANNOT run cm12.1 because i have upgraded baseband doesn't seem valid to me,as my surnia runs it while i am typing this......i am a bit confused to....maybe it will solvve the issue....but my concept isn't getting cleared.
[E 2015 Original Android Development] KonomiKitten:
That's correct you can flash the old version of the baseband any time providing you have the modem files, I have personally gone between 5.0.2 to 5.1.1 to 6.0 baseband in my testing multiple times. squid2 linked to the modem thread in the original post but linking you to it here.

I also have documentation that describes how to backup your partitions before you flash, I wasn't intending to give it out to anyone but I'm providing a link here just in case, my write up is here. Remember to backup your modem partitions just in case!

You also have to make sure you get the right version from the modem thread! Good luck.
[E 2015 Original Android Development] DroidFreak32:
Even I have downgraded to LP because I've been having problems with my sd card.. I mean I can't download stuffs in my card, can't edit my music collections (like album arts and other tags) and titanium backup can't backup anywhere except in android/data/com.kr...../ folder. But lollipop ROMs don't have any of these problems and they're extremely stable!
[E 2015 Original Android Development] gameSTICKER:
Obviously you're running a 5.1 ROM, but your baseband is 6.0 as evident from the screenshots. It seems you're not aware what baseband is, no issues, let me explain. Your phone software is made up of 3 parts, Baseband, ROM and Kernel. Baseband is different from ROM or Kernel. When you install a [custom] ROM or Kernel baseband is NOT installed with it. Usually, you only install [custom] ROM and Kernel, and you never have to worry about baseband at all. Now let's see what you can do now...

You can use either one of these options, I'm not sure why are you getting confused. If still all this sounds too complicated, just follow option 1 and you'll be done.

---------- Post added at 02:38 PM ---------- Previous post was at 02:00 PM ----------

A lot of us keep switching between CM 12.1 (or AOSP 5.1) and CM 13 (or AOSP 6.0) [based] ROMS. I don't think it's unusual, it just didn't get discussed too often, because maybe it's too obvious :) Your question about switching from stock 6.0 to CM12.1 is a two fold transition, 1) transition from stock stream to CM stream and 2) transition within the same stream between CM12.1 and CM13.

When you say you're puzzled i don't think you might be questioning "stock to CM" transition, because reasons for that are obvious. I think you might be questioning why someone would prefer CM12.1 over CM13. I've tried CM13 in past, but quickly switched back to CM12.1, let me tell you my reasons:

With all due respect to all the Devs, I'm not a dev but a general user. I use my phone for getting things done. Hence, I need a ROM which is reliable, stable and out of the way. I don't need bleeding edge features, I need stable features. CM12.1 is all that and more! CM13 is very much a work in progress (check commits), I'd rather switch to it after 6 months once all features are stable. At this point you might say that CM12.1 is "abandoned". This is a fallacy. In precise technical terms, CM12.1 is "feature complete". All the planned/needed (LP) features are there so there is no need to add any new feature if everything works. They've hit their milestone, that's it. Now CM12.1 is in maintenance mode, which is the holy grail for any software. And as a matter of fact, identified bugs are getting fixed in CM12.1 all the time (really, check commits). I hope that clears your confusion :)
[E 2015 Original Android Development] debojyotidey:
So ultimately what i need to do to use a squid kernel with cm12.1?
[E 2015 Original Android Development] :
Thanks for such a detailed reply, and let me be honest, I'm the worlds biggest fuss pot when it comes to rom stability.

I purchased my own XT1524 (EU retail) in the UK in December, as a replacement for a 5 month old XT1021 (Moto E 1st gen AKA Condor) that developed a fault with the screen.

It was 5 months into a 24 month pay monthly contract with Tesco mobile, but the fault it has was not covered by any warranty and I was left with no phone and a rolling contract......

Anyway, the 2015 E seemed a suitable if not better replacement, Tesco allowed me a £50 credit on my bill for the purchase after a lot of arguments (the 2015 E cost £69 and is locked to the Tesco network) and the first thing I did when I got home was unlock the bootloader, flash TWRP and install a custom ROM.

Why?

Back in July when I got the 1st gen moto e, the vendor (Tesco phone shop) said the device would be garunteed an android update "within a month of purchase..." It had Android 4.4.4 KitKat at point of sale, I duly expected an upgrade to lollipop by end of august, as promised.

I never got the promised update, even though many people were posting on XDA that their moto e had got the ota update, the UK was left way behind Europe and other continents and still didn't have the update at the beginning of November!

So I unlocked the boot loader, flashed TWRP and installed CM13, it ran great on the 1st gen moto E until mid november when the screen packed up.

No damage, not dropped, no fluid ingress, just failed pixels that meant only half a screen was displayed!

It was a few days after I got my 2nd gen moto e that Motorola announced the 2015 E was going to get marshmallow after all, and knowing what I knew about the last update, I'm glad I'm running CM13 to be honest. I haven't tried CM12.1 because it makes no sence (to me) to use a lesser android version than the latest thats available, but I'm not going to say never.....

I've tried every marshmallow based ROM for surnia, but In its current configuration, of CM13 0320, squid kernel r15c, a gapps pico, updated 5.1.1 baseband, my surnia is as stable and pretty damn fast as its going to get, no errors or no issues, very good and very very pleased with it, but who knows, I may try the stock ROM if someone makes a flashable version ! ;)
[E 2015 Original Android Development] gameSTICKER:
And that's the beauty of the dev community, ROM diversity, and Android. We get to choose and keep what suits us. BE TOGETHER, NOT THE SAME! Enjoy your device :)

---------- Post added at 10:01 PM ---------- Previous post was at 09:42 PM ----------

Dear [MENTION=6560506]debojyotidey[/MENTION], my suggestion is again the same for a third time now.

Form your conversation so far, it seems you're relatively new to flashing. I highly recommend you to just install CM13 from here http://xdaforums.com/moto-e-2015/orig-development/rom-cyanogenmod-13-moto-e-lte-t3329100 and save yourself some pain.

Now as you say, if you definitely want use CM12.1 + 11e kernel, you'll have to downgrade your baseband. Download stock 5.1 ROM (according to your device) from here http://xdaforums.com/moto-e-2015/general/stocks-firmwares-moto-e-t3113235 then flash the baseband as described here http://xdaforums.com/showpost.php?p=64871207&postcount=3
[E 2015 Original Android Development] debojyotidey:
This is the precise answer i was looking for.thanks
[E 2015 Original Android Development] squid2:
Squid Kernel r16

Today's build brings a variety of small improvements and updates. I've merged in all the Kernel.org updates up to Linux 3.10.101. I've also brought in Motorola's latest cyanges to sync with MPD24.107-52 (lux 6.0.1) release. I've updated the WiFi driver from Qualcomm up to LA.BR.1.2.7_rb1.5, bringing in various bug fixes and addressing an issue with unhandled vendor commands causing log spam in CyanogenMod 13. I've also brought in various security and performance fixes from Google, including a change that should improve the performance of encrypted storage under heavy CPU loads.

I have returned to building from my main (non-legacy) branch for surnia to use the new WiFi driver. I don't know if the new kernel will work on old (5.0.2) modems or not. You can try it and let me know. If you get kernel panics when trying to enable/disable WiFi or do other such things when using an old 5.0.2 modem, you may have to stay back on r15c.
[E 2015 Original Android Development] Sher1234:
It is compatible with stock M 6.0/or not (r16 build)
[E 2015 Original Android Development] squid2:
All releases from r15c onward are compatible with the stock 6.0 ROM.
[E 2015 Original Android Development] Sher1234:
Ok thanks squid

And thanks for Awesome kernel
[E 2015 Original Android Development] gameSTICKER:
Any chance http://www.androidcentral.com/criti...d-android-patch-coming-nexus-devices-few-days (https://source.android.com/security/advisory/2016-03-18.html) will come to 11e or default CM12.1 kernel?
[E 2015 Original Android Development] squid2:
I had actually patched this vulnerability last year. Neither r11e nor the CM12.1 kernel should be vulnerable.
[E 2015 Original Android Development] ayush rao:
Great job man!!!! U never seize to amaze me
[E 2015 Original Android Development] silence911:
updating to r16 broke the camera on my x1527, I have to flash to the old version to get it to work again
[E 2015 Original Android Development] arpeggio16:
I like this kernel, especially the kcal. Do you have any recommended settings for the kernel for balance between performance and battery life?
[E 2015 Original Android Development] sm4tik:
Might be rom specific as not all of them have updated the blobs. I'm currently on Bliss with my XT1524 and had to wait until yesterday (or was it today?) for a new build with new blobs.

[MENTION=6485916]squid2[/MENTION] I'll just ask this here though I'm almost certain it's not kernel related, but do you have a clue why cache can't be formatted as f2fs? It's been a while, but I've tried it a few times and always ended up in a bootloop.
[E 2015 Original Android Development] squid2:
It's because of the fstab configuration. Both the stock ROM and CM13 expect the cache partition to be ext4. See https://github.com/CyanogenMod/andr...ommon/blob/cm-13.0/rootdir/etc/fstab.qcom#L11
[E 2015 Original Android Development] sm4tik:
Thanks for the explanation. Would adding (not replacing) an f2fs line for cache require much effort elsewhere or is there a sane reason not to have the possibility as data is already there anyway?
[E 2015 Original Android Development] kesavvel:
which version is stable for 5.1.1 i am using mokee latest release
[E 2015 Original Android Development] sm4tik:
#3
[E 2015 Original Android Development] Fedray:
When I try to change cpu freqs with Kernel Adiutor it shows only one option with "0Mhz", it's only me? I'm on XT1527 Latin America 6.0 stock

Edit: Nevermind, reinstalled Kernel Adiutor and got fixed, lol.
[E 2015 Original Android Development] LenAsh:
Thread cleaned - this is Development thread, not a sideshow debate.

I invite members to refresh their understanding of the Forum Rules, specifically this one:

2. Member conduct.

2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.

2.2 Nudity: XDA is used by people of all ages, including minors. It is unacceptable to post nude or pornographic imagery, which includes the exposure of male or female genitalia and / or female breasts.

2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.

2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.

2.5 All members are expected to read and adhere to the XDA rules.

If an air of tolerance evades anyone again.... guess the rest.
[E 2015 Original Android Development] Apipote:
Hello Masters!

Im very confused. I have a xt1527 of Argentina , with CM 13 and Squid TWRP . What kernel should I install if the baseband is the stock lollipop 5.0 ?

Tnx in advance .

Best regards
[E 2015 Original Android Development] PriPhaze:
Im from México hmm i installed the RETUS 5.1 New modem and i have the same model as you, the XT1527.

It works so i guess it should be the same for you even tho we are not in the same country
[E 2015 Original Android Development] Apipote:
Mmm i don't know what about CID.
[E 2015 Original Android Development] squid2:
Squid Kernel r16d

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

For MSM8916 devices (surnia and osprey), I've changed IntelliPlug to be disabled by default. I've also modified its code so that it has essentially no overhead when disabled. The reason I've disabled it by default is that I performed some idle current measurements with and without hotplug on MSM8916, and found the difference to be very small (2-3%). While hotplugging clusters (as I do on MSM8939) does yield significant measurable energy savings and improves performance, hotplugging individual cores seems to not make much of a difference to energy consumption, and worsens performance. I concluded that for the average user on MSM8916, it's better to not hotplug. If you still want hotplug, you can still enable it with something like Kernel Adiutor.
[E 2015 Original Android Development] EB20XY:
Thanks a lot ! :highfive:

Seems to work fine. :good:
[E 2015 Original Android Development] xpmule:
Thanks for the update and did you get a Bitcoin donation address yet ?

Squid i wonder is it possible to change the default PC connection mode back to MTP for Marshmallow?

Marshmallow sets it to Charging on the stock ROM.

And i tried changing the setting in the options but it did not stick.

Is that out of the scope of this Kernel MOD?

EDIT:

Antutu scores (3 runs after reboot / same exact settings + app's)

Marshmallow - squid_kernel_r16-surnia

------------------------------------------------

26391

*27714

27454

Marshmallow - squid_kernel_r16d-surnia

-------------------------------------------------

26741

26182

*27008
[E 2015 Original Android Development] squid2:
Since you suggested it, I got started with bitcoin today. My bitcoin address is bitcoin:18LQo2KpKDmmYUUC52GPmkDdjQyTsY6EmL

I've also put the bitcoin address on my XDA profile as an alternate donation URL.
[E 2015 Original Android Development] lenigma1too:
Squid i wonder is it possible to change the default PC connection mode back to MTP for Marshmallow?

Marshmallow sets it to Charging on the stock ROM.

And i tried changing the setting in the options but it did not stick.

Is that out of the scope of this Kernel MOD?

I'm wondering the very same. I'm forever changing charge to MTP. (I have 3 of the E2's working, for various purposes). I have searched media thread looking for the answer to change it back to default MTP, to no avail...
[E 2015 Original Android Development] xpmule:
Good you got a donation address Squid2 !

I don't have much Bitcoin or have any use for it but i should be able to send you around $15 worth soon.

Happy to give something back for all the great work you have done for this phone :)
[E 2015 Original Android Development] divayth:
What is the intended way to do that? I dont want to install a random app from the store, give it root, so it maybe does that. I have no problem using the linux shell but I cannot find any information on how to this on android via google.

Edit: Im using KernelAdiutor now because it is open source. Would still like to know how else you set those.
[E 2015 Original Android Development] squid2:
I was about to recommend Kernel Adiutor but I see that you've also found it. If you want to do configuration manually, you can go via sysfs. Various settings are found in various parts of sysfs, but most of the CPU related settings are located within /sys/devices/system/cpu and its subfolders.
[E 2015 Original Android Development] cmason37:
Anyone else experience sudden complete data loss? I tried to reboot into safe mode, only to find Android asking me for a password, then telling me my data is corrupt when I entered "defaultpassword" not only that, but my SD card was also wiped, so my gigabytes of downloaded music, backups, & pictures are also all gone. The odd thing about it all is, the phone was running fine before I rebooted, & showed no signs of corruption at all. I also rebooted using the power menu, not by long pressing the button, so I know it's not a power loss issue. I should aso point out the phone was just wiped, so it was a clena slate. The only thing I can think of that would make me lose data is the newest kernel release, since it was the only new thing I installed.
[E 2015 Original Android Development] xpmule:
You did not say "what"

I would have to ask a hundred questions here.

But i will keep it simple..

Did you install Marshmallow stock then install the Kernel ?

Why i ask is i am speculating maybe the newer security features of Marshmallow

triggered it to do a factory format on you.

I suspect this might happen if you are not rooted too (just guessing)

I would not expect much help if you make a vague question though.

That is like saying hey my Windows is broken..

What on Windows Phone or Windows 95 or Windows Biztalk Server ?
[E 2015 Original Android Development] Kenny13554:
[MENTION=6485916]squid2[/MENTION]: any news from the overclocking frontier? :D apparently with a different device (Lenovo A6000) people are able to over clock to 1.6 GHz (though it might have the same issue as surnia in terms of whether OC actually works or not):

xdaforums.com/lenovo-a6000/development/kernel-gods-kernel-r1-t3319373
[E 2015 Original Android Development] squid2:
Squid Kernel r16f

There have been reports of filesystem corruption involving the new Linux 4.6 f2fs version used in the r16d and r16e releases. This problematic f2fs version was also used in CyanogenMod 13 nightlies on April 9, 10, and 11. If you previously installed the r16d or r16e kernel, or previously installed the April 9, 10, or 11 nightlies, I would advise backing up valuable files to a non-f2fs storage volume before upgrading to this kernel version. There may be a risk of data loss when downgrading the f2fs, but it only affects some users.

This release brings back the older (Linux 4.5) f2fs. This is the same f2fs that was used from r15 to r16b. This release also brings updates to the zRAM driver.

Please accept my sincerest apologies for any data loss that may have occurred. Greater caution will be exercised before any future f2fs updates are attempted in CyanogenMod or this kernel.