yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] Chandresh204:
[MENTION=5736790]kingkaminari[/MENTION] can you make a flash able zip of the mod to change the system wide theme to dark and the colour mod you did in your ROM ?

thanks
[Moto G Android Development] miguelrivas:
Sounds nice jajaja I serious
[Moto G Android Development] DoctorStrange96:
Version 1.0.9 (yeah, now there's that second dot right there, 1.1 or 1.1.0 - NOT 1.10 anymore - wont come that soon) is up. This one is mostly miscellaneous tweaks.

Download

Remember to put the zip at the root of the internal storage (/sdcard)! Otherwise your wifi will be broken! You've been warned.

Edit: Credits to [MENTION=4723408]hurtsky[/MENTION] for all of the tweaks i merged. I forgot to credit him. :p
[Moto G Android Development] hurtsky:
thanks for me for that miscellaneous tweaks :o (cpuidle and others upstream driver updates) - please proper credits in forum also, it takes alot of time for all of that.

btw, you did not enable optimized rwsem in defconfig.. you also should regenerate defconfig because you disable perf and tracer..
[Moto G Android Development] DoctorStrange96:
Oh dear... I did this quite in a hurry and forgot to credit you properly (i mentioned you at the OP though). My bad! And thanks for those tweaks.

And... regenerate the defconfig? How? Edit: I know what you mean now. Anyways i'm gonna merge (almost) everything again, my current branch is a mess
[Moto G Android Development] DoctorStrange96:
My sources are a complete mess right now. Wait till i merge my tweaks into a new branch and then build the kernel from it.
[Moto G Android Development] Chandresh204:
[MENTION=5736790]kingkaminari[/MENTION], are the MotoActions app, MotoDisplay app, dependant on some addition to the kernel or are these just apps? Is it possible to port them ?
[Moto G Android Development] DoctorStrange96:
Maybe. But i believe they depend mainly on some extra hardware or software components not present in our device
[Moto G Android Development] Chandresh204:
I think our moto G has all the required sensors... Those apps work in moto E 2nd gen which also as accelerometer and proximity like moto G... And 3G version of moto E runs on snapdragon 200
[Moto G Android Development] DoctorStrange96:
I'm too lazy to build my kernel from a new branch right now. And even that new branch is messy.

So version 1.0.10 was built from the current branch.

Here it is

.

The difference is that i reverted hurtsky's rcu changes - one (or more) of them was (were) causing a kernel oops for some users. And i'm gonna revert some more unneeded stuff later
[Moto G Android Development] Akshay7273:
Just flashed it,everything works fine but i noticed that new governers sticks at max frequency...smartmax is still aswome...thanx for updates kaminari,keep it going
[Moto G Android Development] PanchoPonceN:
Booted GPE 5.1 from lost101 with ext4 partition. Everything seems to be working fine. I'll keep using this and report anything wrong.

Thanks for the effort!
[Moto G Android Development] :
Please don't add UKM/Synapse from Attacked's repo. It causes some issues I don't like, when I removed them from Attacked's zips the problems weren't there so I'm positive it was the cause.
[Moto G Android Development] lcosta2:
wifi don't work in xt1033 stock 5.1 :(
[Moto G Android Development] doomwithdon:
Works fine for me with the same stock 5.1 xt1033..lovely kernel.. but i dont get the option for sound control in kernel audiutor
[Moto G Android Development] jonas210678:
So I tested GPE Rom with F2FS Kernel and it is not working, it is only restarting to recovery.:(

But now I tested Identycrisis Rom again, with your newest non anykernel and Wifi is working fine:highfive:
[Moto G Android Development] xtrs84zk:
Good to see one more kernel! Testing on xt1032 with modified stock :)
[Moto G Android Development] santos_10:
Im using GPE 5.1 and is working ok!

The version that I used is "Mori" Non-AnyKernel because with "AnyKernel" I have an error when I flashed.
[Moto G Android Development] :
Question... Do you use Multirom? I'm trying to narrow down the Anykernel flashing problem. I can't even flash an Anykernel zip to CM12.1 unless it's installed as a secondary rom with Multirom. It seems like it won't extract the stock ramdisc.
[Moto G Android Development] santos_10:
No, I don't use Multirom, as I said I'm on GPE and I didn't try with CM12.1.
[Moto G Android Development] AssToast:
For anyone having WiFi not working, do a dirty flash of your rom and flash the kernel, seemed to work fine for me. I recommend booting up after flashing the rom to see if the WiFi works.

You can try to flash the stock kernel and modules found here if you don't want to wait a long time for your rom to flash.

http://xdaforums.com/showthread.php?t=2649763

Edit: Works on GPE 5.1.1 Optimized 1.2b by lost101! [MENTION=5736790]kingkaminari[/MENTION], I think adding this website to your main thread would greatly benefit users to learn about tweaking their phones with the settings included in your kernel. http://androidmodguide.blogspot.com/ (Remember to credit!)
[Moto G Android Development] DoctorStrange96:
None of my kernels will have UKM/Synapse support. All of them must be tweaked with Kernel Adiutor only.
[Moto G Android Development] DoctorStrange96:
Guys i forgot to announce that i'm back. So, with that being said, well... I'm back! The Kaminari + Attacked mix should be brewing soon. Plus i'll try to fix the bugs with the governors in 0.99
[Moto G Android Development] abeloman:
Can I try this on GPe 5.1?

Edit, sorry, I didn't read before, I'll try ASAP :)
[Moto G Android Development] Mchasard:
Thanks but WiFi doesn't work with I'd crisis rom 5.1 stock .... An idea ?

Envoyé de mon XT1039 en utilisant Tapatalk
[Moto G Android Development] :
It works on Boost 5.1 Stock. Try different modules, maybe the modules from Butter Kernel or Mokey. Any idea why Anykernel zips will flash on I.D Crisis, but not Boost Stock, and only on custom roms installed as secondary with Multirom, but not when installed normally?
[Moto G Android Development] jonas210678:
Im using this Kernel at identycrisis. First time wifi was not working. But dirtyflashing Rom and than flashing not anykernel Kernel. Now it is working fine.
[Moto G Android Development] Mchasard:
Doesn't work for me... Thanks however....

Envoyé de mon XT1039 en utilisant Tapatalk
[Moto G Android Development] cris_webb:
For now, works great!

Thanks a lot.

Enviado desde mi XT1032 mediante Tapatalk
[Moto G Android Development] DoctorStrange96:
Which rom are you using? And whats the problem?
[Moto G Android Development] madman:
kernel oops ? I had many reboots yesterday after 1.09.. those oops caused it ?
[Moto G Android Development] DoctorStrange96:
Thats very likely. Maybe its the true reason, even
[Moto G Android Development] madman:
After upgrading to latest one, I received a call and the phone was just ringing without turning on the display.. Even power button was not helpful so I had to force reboot the phone.. Haven't changed anything in tweaks or settings apart from the kernel.

Is anybody having similar problem?
[Moto G Android Development] DoctorStrange96:
There's a different issue with every build [emoji14] . I fear i might have to stop with those builds for a while...

You can always go back to a previous build if the latest one is giving you trouble
[Moto G Android Development] DoctorStrange96:
Version 1.1 Alpha 1 is up.

Download

Clear your kernel adiutor / synapse data before flashing this.

Changes:

- Built from a new branch (Yeah I had to redo everything)

- Built using -O2 flag and with XZ compression

- Most of [MENTION=4723408]hurtsky[/MENTION]'s tweaks have been reverted (Except dt2w and some other ones I don't remember)

- Some other stuff

What's missing in comparison with other versions:

- Intelliplug and MSM Hotplug

- Intellidemand, Darkness & Impulse gov's

- Tripndroid I/O scheduler
[Moto G Android Development] DoctorStrange96:
1.1 Alpha 2 is ready. It mainly adds the stuff missing from 1.1 Alpha 1.

Download

Go take a look at the changelog below the OP to see what changed with this one.
[Moto G Android Development] miguelrivas:
You deserve heaven dude, thanks for dont forget us. Moto G users.
[Moto G Android Development] Nishblueweapon:
what settings u guys use for hardcore gaming?

PLease also share the undervolting tweaks for going whole day with more SOT
[Moto G Android Development] :
USB otg isn't working with the last build. Went back to 1.08r1.
[Moto G Android Development] SH1M4BD3:
Latest build break kexec Multirom user
[Moto G Android Development] DoctorStrange96:
Here comes 1.1 Alpha 3. Get it

here

.

Changes:

- Fixed broken USB On-The-Go

- Fixed broken Kexec Hardboot
[Moto G Android Development] :
All is working fine now, and performance seems a bit better than the last few builds. Thank you very much again, sir! One thing I noticed in the last few builds or so, is fsync in Kernel Adiutor is turned off and can't be kept on, but looking in /sys/module/sync/parameters/fsync_enabled, it says it is enabled.
[Moto G Android Development] DoctorStrange96:
I also have that issue here. Maybe its an app issue. But it's enabled by default both in the kernel code and in sysfs.
[Moto G Android Development] abeloman:
Hi, I came back, I miss your kernel haha... Just to be sure, is latest build keeping the lowered voltage?
[Moto G Android Development] DoctorStrange96:
Heres the deal. I had a random watchdog reset here after disconnecting my phone from my pc (usb). So, as a precaution measure, i built

this

.

Changes:

- Reverted to linaro 4.9.4 toolchain

- Cpu voltages increased a bit (But still lower than average)

- Ram frequency decreased a bit (From 566 MHz to 533 MHz)
[Moto G Android Development] miguelrivas:
I don't know man, but I think it's better linaro 4.9.4 than sabermod, because playing Modern combat 5, when I had linaro, everything ok, with build 1.1 alpha 3 and sabermod I had lag sometimes, that's my case.

Thanks man, for everything.
[Moto G Android Development] Haggster66:
Just wow. After having taken a long break from flashing any custom kernels, and after some good evaluation of all available kernels I gave this one a try and I cannot say anything else other than I'm impressed.

I've been burned by too many amateurish attempts at custom kernels in the past (breaking stuff, causing constant reboots, you name it) but this one plays in another league; the perfect balance between modern kernel tech but without any compromises regarding stability. I'm currently running this "alpha 4" which is ten times more reliable than other kernels claiming to be stable/"final".

I'm using most of the recommended settings btw., and was using the stock kernel with tweaked settings before; this kernel has now fixed everything that had annoyed me about the stock kernel, namely too high constant GPU frequencies, too frequency hungry governors among other things.

Stability should always come first, therefore I'm happy to see that e.g. the voltages and RAM frequencies have been adjusted to more conservative values again, the same goes for choosing to go with Linaro again. Looking forward to see the next versions and seeing the first versions of this for a potentially ported Marshmallow ROM for Falcon in the future would be for teh win!!1!

I admire your professionalism.
[Moto G Android Development] DoctorStrange96:
Lol mate, i'm just a rookie here, i do this as a hobby. But thanks for the words anyways. Yeah, i always try to ensure stability first. Thats why i had to move to the 1.1 builds (the final 1.0.x builds were a mess, i dont recommend you to try them). People were having random issues often so i had to do everything from scratch and try and fix the problem(s). Regarding toolchains, yeah, i think Linaro is the best one for the job (sabermod gave me trouble a few times). And yeah, if some hero manages to port a stock marshmallow rom to falcon, and if moto doesn't take too long to release the new kernel sources, you should see a new version of this kernel compatible with that ported rom.

If i don't find any more serious bugs, then i'll "promote" this build to stable. Otherwise we'll stay in the alpha stage till the major issues have been gotten rid of.
[Moto G Android Development] kedar512:
[MENTION=5736790]kingkaminari[/MENTION] can you add mako hotplug?

It gives very good battery life.

Thanks
[Moto G Android Development] keepercito:
something wierd happen to me with the v1.1 alpha4, after flashing (zip on root directory, wiping cache and dalvik before and after flash) wifi doesn't have internet, the devices is connected to the wifi but no have internet and my wlan hasn't the trouble because in the moment i noticed this issue, i was listen music from spotify on my notebook... any idea about this???
[Moto G Android Development] :
Try flashing the stock kernel, wipe dalvik and cache, and any kernel control app data then reflash V1.1 alpha4. I recommend doing this when ever you flash a new build, and especially since the kernel was just rebuilt from scratch again. This used to be the recommended procedure when flashing a kernel but for some reason it seems everyone has been dirty flashing. I think if you dirty flash and have an issue, you should try a clean install and see if it fixes the issue.
[Moto G Android Development] Haggster66:
Makes sense. Just for clarification regarding flashing the stock kernel first: would it be enough to boot into recovery, flash the stock kernel and directly after this the custom kernel (during the same recovery session, i.e. without rebooting in between) or would a reboot in between flashing the kernels be necessary?
[Moto G Android Development] :
You should reboot after flashing the stock kernel.
[Moto G Android Development] AssToast:
You need the stock modules as well.

---------- Post added at 03:58 AM ---------- Previous post was at 03:57 AM ----------

Oh nvm, i though you were flashing back to stock.

Sorry for the double post as well, cant edit I the app.
[Moto G Android Development] DoctorStrange96:
The "final" (we all know a kernel release is never final :p) 1.1 release is up.

Download

You know where to find the changelog.
[Moto G Android Development] DoctorStrange96:
And there's our Lite version as well. Despite being numbered 1.0, it shares its codebase with the original's 1.1.

Download

Go check the third post for more info.
[Moto G Android Development] Haggster66:
k-rad! very cool idea to offer a light version in order to avoid unnecessary kernel bloat; I'll go for lite since that one got all the features I'm using. will report back in case of any errors (which I'm not really expecting... have been running the last alpha for 48 hours without a single issue)
[Moto G Android Development] abeloman:
Yes, it works... Try it, go ahead... Or read the OP, or even the title...
[Moto G Android Development] padhu1989:
Deleted.
[Moto G Android Development] DoctorStrange96:
PSA: The CM13 version I've been planning to make was cancelled. It's really not worth the effort. There're already Optimus and Hurtsky's kernels - and both get their jobs done really well. So with that being said, we'll only see a Marshmallow version of this kernel if someone manages to port a stock 6.0 rom from titan. Thanks y'all.

My specialty is stock roms :p
[Moto G Android Development] bhumik147:
awesome work, just wondering if i want to revert to stock kernel, would i need stock kernel modules? if yes then pls guide me so that i can dump it from my stock rom,

i cant find those modules for xt1033 5.1 anywhere.

[MENTION=5736790]kingkaminari[/MENTION]
[Moto G Android Development] DoctorStrange96:
My own stock kernel zip has them. ;)
[Moto G Android Development] bhumik147:
Oh many thanks then, i think taking precaution is better than facing bricks :p
[Moto G Android Development] night_mare:
can any one mail me the zip file.. it is showing access denied to my account.. pls..
[Moto G Android Development] AssToast:
You could have asked for the file to be uploaded somewhere else.

It's not wise to post your email openly online.
[Moto G Android Development] DoctorStrange96:
Do you guys think i should switch the kernel from being xz compressed to lzo compressed again? I do. Xz kernels take a very long time to boot up. Lzo kernels take less time. Afaik the stock kernel uses lzo.

So yeah, should i switch or not? There'll be that tradeoff between faster boot times and increased file size, but that won't be much of a hassle for us, i guess
[Moto G Android Development] sathish saju:
Ya..lzo compression would be better

Sent from my Moto G
[Moto G Android Development] DoctorStrange96:
This same question has been turned into a poll - which you can find at the top of the page. Go check it out and vote!
[Moto G Android Development] DoctorStrange96:
Versions 1.1.1-Full and 1.0.1-Lite are up.

Downloads at the OP and at the third post, respectively.
[Moto G Android Development] sfoot13:
[MENTION=5736790]kingkaminari[/MENTION] do you have plans of compile it for marshmallow? cm13 based roms.

You kernel is incredible, it has a lot of features :o
[Moto G Android Development] DoctorStrange96:
No, i dont have any plans for cm-based roms (but i might still change my mind). I'll only build a marshmallow kernel if some brave soul manages to port titan's stock 6.0 rom to falcon
[Moto G Android Development] :
I've been thinking about taking a crack at that port, since it's the only way we're gonna have stock 6.0.
[Moto G Android Development] DoctorStrange96:
I support that, mate... Go ahead! You'll need to do some hackery to get everything working (especially dual sim) but it shouldnt be too hard
[Moto G Android Development] :
Yeah, I think the main problem will be finding the time to do it after work. We'll see.

Edit: has the 6.0 update even been released yet? If anyone can locate it and share a link I would really appreciate it.
[Moto G Android Development] miguelrivas:
Excellent, if you do that man.
[Moto G Android Development] cervi_alcorta:
Why access denied?
[Moto G Android Development] Haggster66:
Running the lite version of the kernel released yesterday, working perfectly just like before.

Regarding the kernel compression algorithm: If I understand this correctly, the kernel size that is affected by this, is only the size of the kernel in physical form, i.e. the way it is saved on the SD card, is that correct? This means that the kernel in RAM will have the same size, no matter what algorithm is used, right? Or will the kernel in RAM, while the system is running, be smaller if you use Xz?

In the latter case I'd be in favor of Xz, however if it doesn't affect the kernel's size in RAM at all, I'd tend to be in favor of LZO.
[Moto G Android Development] DoctorStrange96:
The kernel in RAM will always have the same size, regardless of the compression algorithm used. What changes is the decompression speed - lzo kernels take less time to be decompressed to ram.
[Moto G Android Development] Haggster66:
Cool, then I think not using LZO is almost pointless. I don't really think that the size of the kernel on the SD card (or on the filehost) matters that much. Seems to be a non-issue, really.

BTW: I was the only one who voted "against" LZO, just ignore that vote ...and we'd arrive at 100% in favor of LZO ;)
[Moto G Android Development] DoctorStrange96:
Motorola themselves use LZO to compress the kernels. Most of the devs here at xda choose to use XZ, though. But using XZ results in a significant (and for me, unacceptable) increase in boot time (at least with the stock rom - AOSP/CM kernels boot up fast even when XZ-compressed)
[Moto G Android Development] Haggster66:
Yeah, that not an acceptable tradeoff.

Over the years I got the impression that a lot of custom ROM devs and custom kernel devs seem to think that the engineers who are creating the official stock kernels and stock ROMs have no clue what they are doing, so the hobby devs seem to change a lot of stuff around. But out of experience it seems obvious that the engineers employed by smartphone manufacturers (and Google's own team) are doing the things the way they are doing them for an actual reason, lol :)

I've seen a lot of tweaks that actually backfire and a lot of supposedly amazing optimizations that basically lead to crashes or instability in the end. I think the "art" behind it all is to actually find the best optimizations possible without sacrificing *any* stability or performance at all. You could basically call this "educated tuning".

In that context I'm e.g. also not surprised that this kernel is more stable when compiled with Linaro (which is created by a team of paid engineers) compared to toolchains that have been created by some hobbyists.

Anyway, I digress... yeah... there's a good reason why the stock kernel is using LZO, I guess. Another good reason to keep it that way ;)

BTW: That new Impulse governor seems to be really good, it seems to keep less cores active than e.g. Yankactive. I've been using Dance Dance all the time, since it keeps the frequency to a minimum when the screen is off and doesn't jump around to the max frequency all the time, but lately I've had cases where all four cores were constantly using the max frequency at the same time even though I was doing nothing on the phone ...I wonder if that is/was a bug in the dance dance governor or if there was some background process hanging and causing 100% CPU (cannot remember whether it said if the CPU was 100% utilized). Has anybody else had that problem? (this can be really annoying; imagine you're traveling and this happens to you... your battery will be sucked empty in no-time)
[Moto G Android Development] lost101:
New 5.1 Stock Kernel sources for Falcon are now available:

https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-LPB23.13-58​
[Moto G Android Development] DoctorStrange96:
Apparently LPB23.13-56 and LPB23.13-58 are the same thing, since the last commit is the same. But there's a new "lollipop-5.1.1-release-falcon_gpe" branch, which is essentially the falcon branch with some fixes cherry-picked from the peregrine branch I've been using. But thank you anyway! :D
[Moto G Android Development] DoctorStrange96:
Yeah, I agree with that first part. The manufacturers' engineers (and Google's own engineers) know what they're doing. And thats what i try to do with this kernel - find the best optimizations without breaking anything. And regarding toolchains, yeah, Linaro is the way to go if you want stability.

Regarding the governors, yeah, i think DanceDance is bugged too. I also had a case like yours. I was using Alucard but i think its bugged too (sticks at 998MHz). So i switched to Impulse
[Moto G Android Development] DoctorStrange96:
I forgot to say that version 1.1.2 is up. You can find the original version's download link at the OP and the Lite version's right above the FAQ.

The only change with this one is that both Alucard and Dancedance governors say Auf Wiedersehen (German: goodbye).
[Moto G Android Development] abeloman:
I had bootloops with the previous version (1.1.1)... Using stock 5.1 US, and I had to wipe dalvik and cache, otherwise phone didn't boot up...
[Moto G Android Development] :
Strange, I had no trouble like this.
[Moto G Android Development] DoctorStrange96:
Every now and then i have some bootloops here - but thats because BatteryService crashes due to an NPE somewhere else. Dunno if this is related to the kernel though
[Moto G Android Development] abeloman:
I don't know, but right now I'm using last version on GPe and I don't have that problem, everything is working fine... It's weird, maybe something related to the stock firmware...
[Moto G Android Development] Haggster66:
Hi! I wanted to write earlier, but yeah, for the first time since I started using this kernel, I got a spontaneous reboot with the previous version (the one from last week) as well. Will now try the latest one.

I'm on stock 5.1. (non-GPe)
[Moto G Android Development] lost101:
Here is another new release, MMI-LPB23.13-61 - this time for Peregrine.

Edit: Sorry, checked last commit - also the same. Nothing new.
[Moto G Android Development] DoctorStrange96:
Looks like all LPB23.13-xx releases are / will be the same thing :p