yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] sm4tik:
Your question was semi-answered right above your post, but for a minimum of 1 core

echo 1 > /sys/module/intelli_plug/parameters/min_online_cpus

As for the reason for two cores, I can't say, but after testing, two cores were kept more constantly at minimum cpu frequency than if I had set the minimum to one core only. With only one core, the frequencies seem to go all up and down, triggering a thrid active core more often etc. Given the fact that of the whole wakeup time, the cpu is idle only for an X amount of time, having a minimum of two cores running (more stable at the minimum cpu frequency) won't take a hit on your batterylife. On the positive side, it will (or should) make the phone more responsive.

I thought I'd post a feature request to add support for this feature to KernelAdiutor, but in the mean time echo is your friend. (or you can edit the file with a filemanager of your choice)
[E 2015 Original Android Development] Kenny13554:
Haha, I just realised that. It was pretty late already where I live when I wrote it, though ;)

And you are totally right. Both cores definitely stay more at the minimum frequency when permanently activated. It probably hast to do with the fact that a new task won't cause a boost in a governor as the two cores can take care of the cpu load...

Besides the possibility to change minimum and maximum amounts of cores in mpdecission, there used to be an option like "group tasks efficiently" that means loading as much as possible on one core. I wonder if that would stop/reduce the frequency races if only one core is active pemanently...
[E 2015 Original Android Development] hehk1234:
[MENTION=6485916]squid2[/MENTION] the version of your kernel R11E works on stock rom 5.1.1 XT1521 ? Thanks :)
[E 2015 Original Android Development] TechnoAnder:
Check the release history on the first post
[E 2015 Original Android Development] Sher1234:
Kernel Version r11e is supported by Android 5.1 & its derivatives

So it should definitely work on stock rom as well as cm12.1 or its based rom

Device - XT1521 India

OS - CM13 UNOFFICIAL

KERNEL - r15

Modem - 5.1 modem flashed
[E 2015 Original Android Development] hehk1234:
Almost everything works, but I get error in camera, now I use xinfinity kernel, build by Carlos Arriga
[E 2015 Original Android Development] bigblueshock:
Quite interesting. This is the 2nd time I noticed a reboot in several days.

I am on modem M8916_2020610.17.03.21.26R SPRINT_SURNIA_CUST. I assume thats the newest one I compared with the Boost.

The phone rebooted shortly after I turned wifi on. Not sure how to replicate it however. My phone hasn't been rebooted in over a day, and wifi has been off since last reboot.

I am on Teamsk's CM13

Edit: I am on Squid's r15
[E 2015 Original Android Development] Euphorion:
EDIT
[E 2015 Original Android Development] niix:
automatically turn on phone to fire alarm

**this was meant to be post on osprey but I guess it won't make a difference, so I won't post it again there

Hello [MENTION=6485916]squid2[/MENTION], thank you very much for all your effort!

I'd like to ask if implementing "alarm when phone is turned off" is theoretically possible to implement or if it is only possible on mediatek devices. I really miss this feature and I'd really like to know if it could be implemented on this kernel. :)

What I mean in case I haven't been clear is implementing the ability of the phone to turn itself ON first, and then fire an alarm. Many chinese devices running on Mediatek have this feature, plus sheduling turn ON and turn OFF time.
[E 2015 Original Android Development] niix:
Actually, Huawei Y300 runs on a Qualcomm Snapdragon 8225 and it does turn on on schedule, and can fire alarms when phone is Off. So I suppose this feature is not bound to Mediatek only. What do you think [MENTION=6485916]squid2[/MENTION] ?
[E 2015 Original Android Development] DiePirate:
[MENTION=6485916]squid2[/MENTION]

What kernel you recommend for otus?

Sorry for my english!
[E 2015 Original Android Development] RubenPCA:
D2TW

Might squid2 D2TW add many users it is helpful to us instead of pressing the release button, from and through
[E 2015 Original Android Development] atomomega:
DT2W drains battery
[E 2015 Original Android Development] gameSTICKER:
Only if enabled.
[E 2015 Original Android Development] PriPhaze:
well... whats the point on adding it to the kernel if you are not gonna use it? It would be the same thing as it is now.
[E 2015 Original Android Development] gameSTICKER:
Your statement if you are not gonna use it assumes that if you and I don't wanna use it, no one else should/wanna use it. That's not true. If the option (DT2W) is not even there, obviously no one can use it. But if the option is there, at least people can try it out and decide for themselves. XDA is all about openness and choices.

Now about DT2W draining battery, it's not like DT2W is going to kill your battery in hours. Actually it only has a marginal effect. And some people might find the battery drain worth for the convenience it offers. My Moto E ends the day with ~40% of charge. Even if DT2W takes another 5%, I'd be glad to enable it. See 2nd part of the post http://xdaforums.com/showpost.php?p=64988743&postcount=23
[E 2015 Original Android Development] PriPhaze:
The thing is that squid said quite a few posts back that he has no interest on implementing DT2W since it can bring too many stability issues and he just want to focus on improving the performance of the kernel and keep it up to date.

Now in my personal opinion about DT2W .. indeed is a cool feature but it's not as polish as it should be to be use in a daily basis.

Sometimes it will "lock" the screen completely and you cant do anything besides rebooting the phone by holding the power button plus the phone starts to get really laggy with the time until you gotta reboot and get that smooth experience again even if it will only last some hrs or a day. (I dont know if thats because of dt2w or the whole kernel itself to be honest).
[E 2015 Original Android Development] gameSTICKER:
Thanks for the clarification. I've used DT2W as a part of another Kernel, and I have experienced screen locking issues. Whether it was due to the feature or the Kernel, can't say. DT2W is there in some other actively developed kernels, so a user who needs DT2W can also try those kernels and check stability and battery drain.

Now whether or not Squid wants to add DT2W in his kernel (for stability or maintainability issues) that's purely his choice and I respect that. He has already given us a wonderful Kernel and he has right to decide which features get added in his Kernel so that he can focus his efforts :)
[E 2015 Original Android Development] EB20XY:
Super kernel. :highfive:
[E 2015 Original Android Development] crazynapkinman:
I must say this is by far the beat kernel for moto e. Stable as all get out. Been a year now since moto e and the development on this kernel is helping keep this phone alive. One of the best lower middle range phones money can buy. Thanks [MENTION=6485916]squid2[/MENTION]
[E 2015 Original Android Development] aksclusive:
Can I use the latest kernel for cm13 I am using it on my moto E 2015 LTE
[E 2015 Original Android Development] DroidFreak32:
Yes you can :).. And Pls don't quote the first post
[E 2015 Original Android Development] vicente001:
I flashed the kernel on caf 6.0.1 (surnia version) and my device dont boot, stay in the bootlogo...(not in the bootanimation)

(Tested normal and legacy version)

(My baseband is updated with a 5.1 xt1527 version)
[E 2015 Original Android Development] crazynapkinman:
Try clean install?
[E 2015 Original Android Development] NSDCars5:
Hey, I just flashed r15 on the new stock 6.0 firmware and now the device doesn't boot past the WARNING: BOOTLOADER UNLOCKED screen. Help?
[E 2015 Original Android Development] P0PETIN:
Which models got 6.0 stock? ?
[E 2015 Original Android Development] Sher1234:
xt1521 indian version of moto e 2015 lte
[E 2015 Original Android Development] P0PETIN:
I don't understand how Motorola updates are working but in their website says that the Moto e will remain on lollipop 5.1 that's why I find it weird
[E 2015 Original Android Development] Sher1234:
Motorola has announced Android Marshmallow update to Motorola Moto E 2nd Generation with 4G LTE only to limited regions which

US varient of E2 4G LTE is not in the list as well so it will not get the official 6.0 Update

Device-Motorola Moto E 2nd Generation 4G LTE (RETAIL ASIA SURNIA INDIA)

Hardware SKU- XT1521

Bootloader-Unlocked

System Status- Official
[E 2015 Original Android Development] P0PETIN:
Don't see why Motorola might be doing this but you're in luck for having official 6.0
[E 2015 Original Android Development] EB20XY:
Kernel 3.10.97 is released. Are there any useful commits for the Moto E 2015 ? :confused:

https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?id=refs/tags/v3.10.97
[E 2015 Original Android Development] hehk1234:
[MENTION=436307]squid[/MENTION] Sir, the rom you make for moto E2 Surnia, CM13 20/02/2016 with your kernel, have a little problem, the wifi control is not good, it drains battery very fast. Thanks Sir for your great work here :)
[E 2015 Original Android Development] Kenny13554:
This developer seems to have overclocked the Snapdragon 410:

http://xdaforums.com/moto-e-2015/orig-development/kernel-inazuma-r2-t3297564

There seems to be quite a debate about whether one can overclock this CPU or not. Any ideas/comments from your side, Squid?

Kind regards,

Kenny

edit: after some minor benchmarking it seems like this is NOT a workaround for the snapdragons CPU frequency restriction. Benchmarks are pretty much exactly the same, no matter what maximum frequency is set (i.e. 1.2 vs 1.4 Ghz).
[E 2015 Original Android Development] PriPhaze:
idk lol i got some pretty crazy aututu score...

But yea it actually feels the same, theres no noticable difference while using it

But the score is red so i guess is not verified or whatever, idk what it means but it have to mean something lol
[E 2015 Original Android Development] Fedray:
Hope we get Squid Kernel working in stock 6.0 soon! :)
[E 2015 Original Android Development] Kenny13554:
I used super pi for the cpu benchmark and there was no difference at all.... it's really disappointing :(
[E 2015 Original Android Development] crazynapkinman:
So is there a workaround for the OC restriction? Is it even possible?
[E 2015 Original Android Development] P0PETIN:
I installed the kernel and I think it was meant for lollipop anyways I got into a bootloop on cm13 maybe I didn't read carefully

---------- Post added at 12:22 AM ---------- Previous post was at 12:22 AM ----------

I just wanted to try the OC and UC
[E 2015 Original Android Development] Kenny13554:
Don't think so :(
[E 2015 Original Android Development] squid2:
I don't like to say things are impossible without knowing the hardware. However, I've never had any luck overclocking MSM8916 in past attempts or recent attempts. It would always benchmark about the same with or without the overclock.

Some testing another person did with the blu_spark kernel on osprey suggested that a 18% overclock yielded a speedup of approximately 2%. When I had tested it last year, I found a 1% speedup that I had dismissed as noise. Other reports also have suggested a small speedup is possible with blu_spark's overclock on osprey, but the speedup appears to be nowhere near where it should be for an 18% overclock. I'm not sure what the overclock was doing there or what frequency the hardware was actually running at, but something was evidently not right. I don't like running the hardware in ways that are not well understood, particularly for a measly 1 or 2% speedup, so I haven't bothered with providing an overclock option here.

One thing that's peculiar is that overclocking actually does work on MSM8939. A mild increase from 1561 to 1708 MHz resulted in a proportionate increase in single core Geekbench scores on lux, and so did bumping up the little cores from 1113 to 1209 MHz there.

Why does it work on 8939 but not 8916? I don't know for sure. However, one theory I have relates to the fact that the MSM8939 dtbs have a lot more frequency related settings specified than the MSM8916 dtbs. Perhaps some hardware defaults are being used on MSM8916, and maybe these hardware default tables lack certain settings for overclocked frequencies. This is just a wild guess. I haven't had time to mess with these, and after some scary experiences messing with these on my lux, I might not want to try misconfiguring these things and then bricking my device. Misconfiguring a regulator can actually damage hardware sometimes.
[E 2015 Original Android Development] crazynapkinman:
Nice reply. Appreciated. What about fast charge? Does the surnia hardware support its use?
[E 2015 Original Android Development] squid2:
By fast charge, are you referring to forcing 800 mA charge rates when connected to a computer's USB port? Charging rates are capped at 800 mA by the hardware, and the phone will charge at 800 mA as is when connected to a dedicated charger. To comply with the USB 2.0 specification, the kernel caps its current draw to 500 mA when connected to a computer's USB data port.

Some USB ports on computers (particularly USB 3 ports) are able to deliver more than 500 mA. Some people have implemented interfaces to ignore the 500 mA USB 2.0 limit when connected to a data port so that the phone can draw 800 mA when connected to a high current data port on a computer. When implemented properly and safely (as was done on the blu_spark kernel for osprey), it does work. It's not a feature I'm particularly interested in myself, so I haven't implemented it here, but it can be done.
[E 2015 Original Android Development] crazynapkinman:
I'm just asking about quick charge from an outlet. Like what the S6 has or most mother flagship devices.

Edit: Fast Charging*can be achieved in two ways

Hardware based Charging(including Chargers and Chip set enhancements such as*Qualcomm Quick Charge 2.0Kernels (including kernel tweaks)capable of increasing charge rate whether it is USB or wall outlet charging

This what I speak of. Does this phone have the capability?
[E 2015 Original Android Development] squid2:
No, the surnia hardware can only charge at a max rate of 800 mA at 5V. It already charges at that rate. Only lux is able to do fast charging because of its special fancier charging hardware, and it already handles this natively.
[E 2015 Original Android Development] crazynapkinman:
Thanks!
[E 2015 Original Android Development] P0PETIN:
Lux?
[E 2015 Original Android Development] brunosp7:
can someone help me? I want to install android MM with f2fs format and i don't know how to do it :P, can someone explain to me?

i'm currently on CM12.1 with squid kernel 11e and i just installed squid TWRP 3.4.5 recovery

also could you tell me which MM ROM is better?

thanks in advance

sorry for my bad english
[E 2015 Original Android Development] crazynapkinman:
No clue about f2fs. Most stable MM ROM for surnia devices is Temaseks CM13.

Sorry I can't be more helpful with the install
[E 2015 Original Android Development] brunosp7:
thank you! i will download it and give it a try

f2fs is a new file system that works faster (reading and writing) than the traditional storage format and as the new squid kernel support it i want to install android with that file system

sorry for my bad english
[E 2015 Original Android Development] llaalways:
@ squid2, I had flashed your late kernel on my sprint moto e 1526 last night,

squid_kernel_r15-surnia-legacy.zip and squid_kernel_r15-surnia.zip

the wifi does not work and SIM card missing.

Then I flashed squid_kernel_r7-CDMA.zip, and everything works fine.

Could you make later version of kernel works for CDMA?

Or tell me how if there is a way to combine squid_kernel_r7-CDMA.zip with later version.

Another question, is it possible to add a power menu with options such as power off, reboot, reboot to recovery, reboot to bootloader?
[E 2015 Original Android Development] squid2:
Are you running Lollipop ROM? R15 is intended for marshmallow only.
[E 2015 Original Android Development] llaalways:
Yes, I am using stock ROM.
[E 2015 Original Android Development] squid2:
R11e was the last version to support lollipop. Try that.
[E 2015 Original Android Development] :
So you knowingly flashed those zips you quote on your stock ROM (5.1) when r15 is categorically listed by squid as "for marshmallow only"

Maybe you can explain why you did this?

Once I have stopped laughing we will give the advice necessary.

I don't say this to be a jerk or be mean, but please read all of squids instructions before flashing to avoid the errors you describe.

Flash the r7 zip you say works, or the zip squid recommends for a lollipop ROM.

Never go against what a developer puts on the instructions, it will save you alot of embarrassment and problems to your device......

Seriously, I've learned the hard way by bricking devices a few years ago by flashing stuff not recommended for the device I was using......

I'm using r15 because I'm running an android 6.0 marshmallow custom ROM on my xt1524 moto e2.

Only flash for your device, not something that's not designed or doesn't work with it.

Good luck.
[E 2015 Original Android Development] nerak11111:
Best kernel

Bro thanks for this awesome kernel, I was finally able to increase the screen color and its very fluid in games

keep your work, regards :laugh::laugh:
[E 2015 Original Android Development] sm4tik:
It's under developer options, advanced reboot.

Edit.. oops, sorry forgot you're on stock.
[E 2015 Original Android Development] Hempsader:
Can i install this rom on my version?
[E 2015 Original Android Development] :
This is not a ROM, its a kernel.......

Did you read squids (the developer) notes on installation and search your answer before asking your question?

If this was a ROM I think it would say ROM rather than KERNEL........

Pfffffff
[E 2015 Original Android Development] Hempsader:
My bad ,i never installed a kernel or rom whatever ,i can find some step by step tutorials pls ?,i want 6.0 .
[E 2015 Original Android Development] ayush rao:
Which model no. do u have
[E 2015 Original Android Development] Hempsader:
Xt1524 ,5.0.2
[E 2015 Original Android Development] PriPhaze:
You need to unlock the bootloader and then install TWRP through adb (thats how i still do it but maybe you could use flashify? someone said it works too )

Squid TWRP last version would be what you need, and from there you can start flashing roms

If i were you i would start digging up a little bit in this forum, start reading carefully and dont rush just cuz you are excited.
[E 2015 Original Android Development] :
I agree.

I wasn't trying to be mean to anyone, but so many people come here asking what to do or how to do it without taking a few hours to just read the loads of information that's out there, all they have to do is search........

There's too many people adopting an "I want it, give it too me" attitude these days, not a direct criticism of any individual, just an observation, and I'm noticing way more "my device is bricked, help me" posts in the help and troubleshooting sections of device forums......

I know inexperienced people have to start somewhere, I had to too, but only after sitting down for hours at a time reading everything and following the excellent tutorials on here.

Yes, I made some mistakes in the past, I bricked a huawei y300 by not following precise instructions, and some people have wrongly assumed I'm a sweaty nerdy teenager sitting at a laptop in a dark bedroom full of cigarette smoke..........I'm accually a 43 year old very happily married man of 3 grown up children and I work in a factory 60 hours a week!

Android and all its customisation is my passion and my life, much to my wife's annoyance.......... :D

---------- Post added at 01:05 AM ---------- Previous post was at 12:48 AM ----------

[/COLOR]

I agree.

I wasn't trying to be mean, but so many people come here asking what to do or how to do it without taking a few hours to just read the loads of information available here on XDA.

I have an xt1524 too, I only unlocked my bootloader, flashed twrp and flashed a custom ROM just a month ago.

As I have experience of rooting and custom ROMs with other devices, it's easy (when you know what you are doing) to unlock my bootloader was even easier as my laptop runs Linux, not windows, adb is already installed.......

Please please please do not try anything you are unsure of, and also don't try anything until you are confident you can do it.

Never rush and ALWAYS follow instructions.

Ask questions in the right places, there are loads of forums here on XDA for unlocking the bootloader and installing twrp or custom recoveries.

I would not suggest flashing custom kernels (like this) until you have a bit of experience!

Until then, have a read in the correct forums, please don't ask about flashing marshmallow in a forum for a custom kernel, ask your question in the correct place and people will be happy to help you.

I suggest a good ROM to start with (in my opinion) is resurrection remix, its android 6.0.1 marshmallow based and has loads of customised settings, its the ROM I currently use, or you could try CM13.

These are currently the only fully stable marshmallow roms ive tried, their are more, i just havent tried them.

Don't try those I suggested or anything else until you have slowed down, took a look at the correct procedures and tutorials on unlocking the bootloader of your XT1524, flashing recoveries and ROMs.

Good luck!
[E 2015 Original Android Development] squid2:
Squid Kernel r15b

This is a maintenance release for the r15 series. I've merged in Linux 3.10.98, bringing with it associated security and stability fixes. I've also corrected an issue that prevented the ARMv8 crypto features I added in the last release from working properly. I have raised the priority of ARMv8 crypto in the kernel so that it is now the preferred crypto engine for use by the Marshmallow adopted storage feature. Regular full disk encryption will continue to use Qualcomm's (slower) hardware encryption engine as that is dictated by the configuration of the ROM.

The surnia r15b build comes from the legacy branch, so old modems should still work. This build is intended for CM13 (and compatible ROMs) that are still using camera drivers from Lollipop. Once we update CM13 for surnia to make use of the new camera drivers, I will update this kernel to support the new drivers used by the 6.0 stock ROM. Today's build will not work on stock 6.0.
[E 2015 Original Android Development] KonomiKitten:
Any chance of an updated kernel for 5.1/CM12.1? I haven't made the jump to CM13 yet because I want to stick to CM nightlies and Motorola left my phone on 5.0.2. Thanks again.

Moto E 2nd Gen LTE Surnia XT1521, CM12.1 Nightly, Squid Kernel r11e, Open GApps 2016.01.05
[E 2015 Original Android Development] squid2:
I'm maintaining this kernel for four devices and CyanogenMod for five devices, so my time is limited. Maintaining an additional branch for people who don't want to upgrade their ROM would make make maintenance more tedious for me, as I'd have twice as many variants to build and support, and it can only get worse as the number of legacy version variations grow.

Thus, I have no plans to support Lollipop any more. CM13 works fine now, and we'll go official eventually once some issues preventing officialization are sorted out. It shouldn't be difficult to get the new stock Marshmallow ROM working on the other surnia variants either.