yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] zwliew:
zwliew_Kernel r5 for AOSP Lollipop

Pushed r5 for AOSP Lollipop! As stated, only for AOSP Lollipop like CM 12. I will push r5 for stock KitKat soon.

Get it at:

http://xdaforums.com/devdb/project/dl/?id=10007

Improvements:

Completely rebased from scratch

Compatible with latest BMc08GT CM 12 build (24/11/2014)

You can know see the kernel release in About Phone

Now using my custom conservative GPU governor which scales frequencies more conservatively

Improved tunables make scaling more balanced and frequencies stay on 1.7 GHz less often

Thread migration boosts are more intelligent in terms of when and how much to boost as it uses load information from scheduler

Enjoy :)
[Moto X Android Development] cupioscire:
device control gives me 1242Mhz as min CPU frequency and interactive as governor. Also under settings->about phone it says kernel certain r4.8.

Running cm12 24/11/2014

Gesendet von meinem Moto X mit Tapatalk
[Moto X Android Development] zwliew:
The min freq of 1.2 GHz is due to input boost, which boosts frequency on touch input. The release version in about phone is due to a small bug in my scripts, will fix in next release.

Rest assured, nothing is wrong with your configuration.
[Moto X Android Development] fakieskr8333:
What app is recommended to tweak kernel settings? I usually just use the features in ROM toolbox but the app won't install on 5.0.

And thanks for the kernel!!!
[Moto X Android Development] zwliew:
I don't recommend tweaking kernel settings as I've already pre-tweaked them. But if u really need to, device control does a pretty good job. However, they don't support most of the features that this kernel has.
[Moto X Android Development] fakieskr8333:
Oh OK, I won't touch them then since I never had much luck tweaking kernels anyway.
[Moto X Android Development] cupioscire:
[MENTION=5604178]zwliew[/MENTION] there's also a warning in kmsg

----------[ cut here ]------------

<4>[ 649.010102,0] WARNING: at drivers/cpufreq/cpufreq_interactive.c:381 cpufreq_interactive_timer+0x614/0x854()

Gesendet von meinem Moto X mit Tapatalk
[Moto X Android Development] zwliew:
Mind attaching the full dmesg? Don't seem to have it on mine.
[Moto X Android Development] cupioscire:
I have some problems to attach text files to my posts via tapatalk. Let's see what I can do..
[Moto X Android Development] fakieskr8333:
Maybe drop it on pastebin.Com or upload it to Dropbox and just post a link.
[Moto X Android Development] zwliew:
Either way, it is a minor issue and I'll do some debugging when I'm back at my laptop.
[Moto X Android Development] cupioscire:
So, sadly I wasn't able to catch the warning again, but there are some errors in kmsg log

http://pastebin.com/z3ER60tD

Edit: and there seems to be some other problems. Have a look in my dmesg

http://pastebin.com/ZVcnN0R2
[Moto X Android Development] adm1jtg:
[MENTION=5604178]zwliew[/MENTION] is stock development still halted till we get lp stock? Or will you be releasing an r5 stock?
[Moto X Android Development] zwliew:
r5 for stock KitKat will be released tomorrow.

There is nothing wrong with those logs.
[Moto X Android Development] cupioscire:
[MENTION=5604178]zwliew[/MENTION] so the warning seems to appear only after/within boot.

Here's the log http://pastebin.com/sWux3Tsh
[Moto X Android Development] gunnerv:
I approve of this. :3 I've been on my phone all day!

Sent from my Moto X
[Moto X Android Development] kenosis:
Waiting r5 for stock
[Moto X Android Development] zwliew:
r5 for stock KitKat

Aaand...here's r5 for stock KitKat! Don't worry you folks, I haven't forgotten you! :D

Download:

http://xdaforums.com/devdb/project/dl/?id=10016

Changelog is same as r5 for AOSP Lollipop, except with a few minor adjustments since yesterday:

1. Lowered input boost and hispeed freq by a step to increase battery life slightly and UI is still as smooth as ever

2. Fixed release version in About Phone displaying wrongly,

3. A few more optimizations in build
[Moto X Android Development] adm1jtg:
Loaded fine will report back after some time

Update: So far everything looks really good... Slow walkups gone and overall feels even snappier then v3.

Did you scrap faux sound... I tried using the faux sound app and it says non compatible kernel. And to answer next question I never tried the faux app on previous versions. Just curious loving the new r5
[Moto X Android Development] CsR0501:
Your kernel is amazing! [emoji2]

Thank you very much! [emoji111]

Enviado desde mi XT1058 mediante Tapatalk
[Moto X Android Development] mac1996:
I think we talked about it...but still cannot resist.. Any plans for making it compatible with aosp
[Moto X Android Development] gunnerv:
It is bro... To my understanding.

Sent from my Moto X
[Moto X Android Development] zwliew:
r5 for AOSP Lollipop: http://xdaforums.com/showthread.php?p=57131569

If you're talking about r5 for AOSP KitKat, it is discontinued and last release was r4,.
[Moto X Android Development] zwliew:
Of course it is. All AOSP ROMs for Moto X are based off CM.
[Moto X Android Development] yugonline:
Nexus Experience ROMS

Will this Kernel work with the Nexus Experience Roms ? :angel:
[Moto X Android Development] droids@m:
Am I the only one missing Fast charging in stock r5.....:p
[Moto X Android Development] zwliew:
Yes, since it is based off CM too.

I've reworked fast charge a little. I'll update post #3 in a bit but here is how it works.

In the next release, I'll set fast charge level to AC (1100mA) by default.

Fast charge control:

Directory:

/sys/kernel/fast_charge/

Files:

fast_charge_level
available_charge_levels

How to use:

Available charge levels are 0, 500, 700, 900, 1100, 1300 and 1500 or viewable in available_charge_levels (Forgot to put in 0, will fix in next release)

Define whatever fast charge level you want by:
echo [500/700/900/1100/1300/1500] > /sys/kernel/fast_charge/fast_charge_level

To disable fast charge:
echo 0 > /sys/kernel/fast_charge/fast_charge_level
[Moto X Android Development] droids@m:
I have set it to 1300 but still no effect I am sorry....
[Moto X Android Development] kenosis:
I can use text editor and change fast charge level value, right?
[Moto X Android Development] yugonline:
So which one should I download ? R4 or R4.1

I'm guessing R4.1 is just an update to R4 but can't be sure.
[Moto X Android Development] zwliew:
Are you on AOSP KitKat or Lollipop? Lollipop is r5. Kitkat last release is r4.1 and won't be continued.
[Moto X Android Development] yugonline:
Lollipop Cm12 Nexus Experience ROM.

I didn't find any CM12r5 so I thought Cm12r4.1 is the way to go.
[Moto X Android Development] mac1996:
Here's the link to download r5 http://xdaforums.com/devdb/project/dl/?id=10016
[Moto X Android Development] zwliew:
Was it working in previous builds? And are you charging on USB, not AC?

Note: Fast charge only increases the input limit of the USB, charge rate still depends on output rate of the USB port.

Please read the r5 AOSP Lollipop release post a few pages back before asking questions. I'm getting kind of sick answering a few pretty pointless questions instead of debugging the kernel...

AOSP KitKat has been discontinued so AOSP Lollipop releases are now tagged 'aosp' while stock KitKat releases are still tagged 'stock'
[Moto X Android Development] zwliew:
Sorry about FauxSound, I plan to add my own sound control.
[Moto X Android Development] s5610:
zwliew

Fast charge working by default, got 1.2 A current on my testing equipment ) The battery wasn't empty, so the current wasn't so high as at charge beginning. I saw 1.39 A current on previous kernel, so I know that high current charge is possible. The crucial abt it is that you should have thick USB cable and powerful charging adapter.

I see in Trepn monitor that second core awakes when I tap the screen. Is it intended to be so? Do we earn something here?

Thanks!
[Moto X Android Development] zwliew:
That is mpdecision waking up the 2nd core on touch input. I actually had a new hotplug driver to get rid of mpdecision and its input boosting, but I scrapped it in r5 as I plan to redo it in the future.

Thanks for confirmation that fast charge works too :)
[Moto X Android Development] KokoReyes:
Theres no init.d Support?
[Moto X Android Development] zwliew:
Nope, there are quite a few universal ways to enable init.d with any kernel so I scrapped that.
[Moto X Android Development] adm1jtg:
You can use init.d toggler from playstore
[Moto X Android Development] KokoReyes:
OK thanks bro :highfive:
[Moto X Android Development] VerneVerne:
I'm on sprint stock 4.4.4 and am getting the telephony crashing after installing r5. Any other sprint users having problems with the latest?
[Moto X Android Development] zwliew:
Oh no, I totally forgot about Sprint...I'll rectify it in the next release.

In fact, I'll push out a release almost immediately to fix this problem.
[Moto X Android Development] zwliew:
zwliew_Kernel r6

r6 has been pushed.

This is a quick update to fix compatibility with Sprint users on stock.

Stuff like overclocking of slimbus, F2FS updates and 2 series of patches which improve battery life were ported over from previous releases.

New:

We are now using the generic (cur_load * max_freq / max_load) CPU frequency calculation, which should improve performance in most scenarios, especially low load scenarios due to fairer frequency scaling.

Downloads:

I'm now uploading to AndroidFileHost to try it out.

Stock KitKat: https://www.androidfilehost.com/?fid=95832962473396614

AOSP Lollipop: https://www.androidfilehost.com/?fid=95832962473395508

Enjoy :highfive:

Sprint users like [MENTION=4142579]VerneVerne[/MENTION], can you report back on whether Sprint compatibility is fixed? Thanks. :)
[Moto X Android Development] VerneVerne:
Running R6 now. Sprint installer crashed twice right after the boot completed but that didn't seem to create any issues. Thank you for the fix.
[Moto X Android Development] KokoReyes:
Thanks!!
[Moto X Android Development] adm1jtg:
Just loaded 10 min ago and already have had a random reboot. What files can I pull to help?
[Moto X Android Development] zwliew:
/proc/last_kmsg. Thanks.
[Moto X Android Development] adm1jtg:
http://pastebin.com/749BrZhB

Let me know I had a second reboot before i could snatch the file
[Moto X Android Development] droids@m:
I am happy to report the fast charging works fine for me in r6 when at 1100 I get constantly .9mA
[Moto X Android Development] mac1996:
Hiii I want someone to help me

.. I don't think it's normal.... I have tmo 1053 unlocked cm12 nx5 experience... Flashed the kernel through latest twrp 2.8 after that it does not reboot to the system but to the recovery... It keeps doing that... It won't load into the system, every time I turn on the device goes to the twrp and I tried to flash back to stock through bootloader but after few seconds it automatically reboots to twrp.... Please help
[Moto X Android Development] zwliew:
Ensure that you installed the AOSP Lollipop version and not the stock KitKat version.
[Moto X Android Development] orangestrawberry:
Did you clear cache and dalvik?

---------- Post added at 10:29 AM ---------- Previous post was at 10:28 AM ----------

Installed latest r6 on aosp and all working smooth
[Moto X Android Development] s5610:
Awesome! Give it a try (1056 @ stock 4.4.4 GB ), normal flight up to now. Best kernel out there :good:

P.S. I'm not sure, but perhaps the first boot ended with reboot, heard vibro sound meanwhile house cleaning, but after that, and up to now - solid work.
[Moto X Android Development] zwliew:
Please state whether you are using AOSP Lollipop or stock KitKat when reporting bugs, and provide a /proc/last_kmsg after a random reboot.
[Moto X Android Development] jakereeves31:
Is the link dead? The page didn't load for me.
[Moto X Android Development] Travisdroidx2:
Stock r6 worked fine for me. I had to use the mirror download as the primary one would not launch the download.
[Moto X Android Development] smohanv:
Flashed stock r6 on the top of stock r4. Wiped dalvik and cache. Keep booting and doesn't work for me. Don't know what is going wrong. Flashed back stock r4

Anyone experienced the same.
[Moto X Android Development] orangestrawberry:
R6 aosp fine for hours but then phone slowed to unusable. Had to revert back to other kernel. Any ideas?
[Moto X Android Development] Travisdroidx2:
Flashed the stock r6 over r5 about 7 hours ago and everything is running great here.

---------- Post added at 10:54 PM ---------- Previous post was at 10:53 PM ----------

Has been fine for me. Did you get a bad download? Check MD5sum?
[Moto X Android Development] smohanv:
Should r6 be flashed on top of r5 or can be flashed on r4.

---------- Post added at 09:14 PM ---------- Previous post was at 09:05 PM ----------

Also, I am running nitrox booster. Could this be a reason?

Let me try uninstalling nitrox.
[Moto X Android Development] UllyTheBestHD:
installing the r6 update
[Moto X Android Development] smohanv:
Finally flashed r6 with success. It was nitrox booster causing the issue. I uninstalled nitrox and flashed r6. Clean install and works fine.

Hope this helps anyone using nitrox.
[Moto X Android Development] KokoReyes:
Flashed r6 on kitkat, no problems, just wiped dalvik and caché, moto x 1053 running kripton
[Moto X Android Development] UllyTheBestHD:
Flashed the aosp r6 on my moto x cm12 build (latest) and i founded a bug, the swiftkey restarted vibrate normally, but when with every keyboard i want use the emojis , they (the keyboards) crashes .. why?? it's so annoying...i came back to r5
[Moto X Android Development] ss12108:
Just wanted to try to contribute a bit here. Ran each version to r3 without a hitch. Tried r4 and had a bunch of random reboots. Assumed it may have been the undervolting, so went back to r3 and have been running fine.

Decided to give r6 a chance and have had a bunch of random reboots since installing. Just had one a couple of minutes ago so decided to grab the last_kmsg to see if it may help the dev - http://pastebin.com/mcu1GPSU

I'm running a stock 4.4.4 droid maxx with no tweaks or anything installed. Again, r3 no problem, r4 I had issues with reboots, r6 the same. Let me know if the last_kmsg tells you anything or if you want me to try something.
[Moto X Android Development] adm1jtg:
I have found similar to you but having very good luck with r5 so far. Can you try r5 as well and let me know if you have any issues. So far I have not, I also had issues with r4 and r6 and no issues with r3
[Moto X Android Development] ss12108:
And here's another that just happened. Plugged in my phone to an AC outlet and instant reboot - http://pastebin.com/aiDkisz0

---------- Post added at 11:11 PM ---------- Previous post was at 11:07 PM ----------

One more for good measure while sending my last pastebin haha - http://pastebin.com/mYJSDTkv

---------- Post added at 11:11 PM ---------- Previous post was at 11:11 PM ----------

I will try that and post back.

---------- Post added at 11:51 PM ---------- Previous post was at 11:11 PM ----------

R5 so far so good
[Moto X Android Development] cupioscire:
Got reboot on r6 running cm12. Looks like kernel panic.

http://pastebin.com/6ent6mDx
[Moto X Android Development] smohanv:
Though it looks okay to me yesterday, it is random booting after flashing r6...

OP must be reading all our comments..

Better to stay with r4 at the moment..
[Moto X Android Development] cupioscire:
I agree, but it's definitely a kernel panic (yes in r6) and I thought it would be hemlock for debugging.
[Moto X Android Development] Travisdroidx2:
R6 has been nothing but good to me. No reboots or issues. Xt1060 here.
[Moto X Android Development] zwliew:
I'm dropping AOSP Lollipop and focusing solely on stock KitKat now, guys. Sorry. All these kernel panics should hopefully get fixed next release.
[Moto X Android Development] ss12108:
FYI I'm back on r5 stock kitkat and was having some app FCs this morning. Most frequent was Google maps and waze when trying to use nav, but also some gapps process and Amazon Kindle. Kept happening over and over on my way to work with Bluetooth connected. I bumped the voltage up +25 and haven't had a FC since.
[Moto X Android Development] jakereeves31:
I've only had one reboot on r6 since installing yesterday on stock Droid MAXX.
[Moto X Android Development] ss12108:
I'm wondering if it's an undervolting issue, because some devices can just handle less power better than supposedly identical devices. Especially since r5 had less undervolting than r6, and r5 was more stable out of the gate than r6 for me, and now that I went +25 on r5 I'm completely stable.
[Moto X Android Development] vasili_defy:
Hi [MENTION=5604178]zwliew[/MENTION],

Been using your kernel from the day one of its release. Thanks for your effort.

Presently I have started using Drive Droid but don't know if your kernel supports or has the patches inbuilt, for the reference I have posted the link to the main thread ..

http://xdaforums.com/showthread.php?p=39293985

Thanks again ,

Also for all the Lollipop users, -r6 version perfectly works on the latest release by [MENTION=3150613]bkjolly[/MENTION].

Sent from ISS above ,using XDA app.
[Moto X Android Development] zwliew:
I'll add the required patch in the next release. However, I've abandoned AOSP so only stock kernels will be released.

Edit: It seems the kernel already has a similar patch.
[Moto X Android Development] dray_jr:
So I haven't ran all the way through the post but I noticed that at the beginning of the stock kernel builds I was getting a lot better battery life than I am now on the R 5 & R 6 builds and I haven't changed any thing else about my phone except for update the kernel anybody else notice this I'm on a sprint Moto X on 4.4. 4
[Moto X Android Development] bkjolly:
lol how did you even find it?
[Moto X Android Development] damagedbits:
It would be awesome if you could add the smartmax govener to your kernel :)
[Moto X Android Development] zwliew:
r6.12 (r7 Preview)

Sorry for the wait, people on stock. I'm finally back on stock KitKat and can now actually test my recent releases for it. The kernel panics and battery issues should be fixed.

However, since this is a preview release, I cannot guarantee it.

New feature: Due to popular demand, I've adapted sweep2sleep for Moto X. It is enabled by default, and you can swipe from left to right or vice-versa on the navigation bar to sleep the device. Now theoretically, you never have you touch your power button again, try it out!

Note: As I've abandoned AOSP, there will be no more releases for AOSP. The last release was r6. Please do not install this or any future releases on AOSP.

Download:

https://www.androidfilehost.com/?fid=95832962473396613

As always, enjoy! :)
[Moto X Android Development] St.Noigel:
I flash it. sweep2sleep works fine for me ) :good:

Thanx for your work, Sir!
[Moto X Android Development] ConstantHero:
6.12 running very well. S2S is a nice feature rarely use the physical power button now. Thanks for great and fast development.
[Moto X Android Development] kenosis:
Is 6.12 for Stock KK?
[Moto X Android Development] zwliew:
Yes, and I'll only be developing for stock KitKat from now on. No more AOSP for me.

Glad you guys enjoy it! I've been working for a while to clean it up and adapt it for Moto X. I guess it worked out well! :good:
[Moto X Android Development] kenosis:
Thanks for reply. Installing right away... :)
[Moto X Android Development] vasili_defy:
[MENTION=3150613]bkjolly[/MENTION] by flashing new kernel !:D

Sent from ISS above ,using XDA app.
[Moto X Android Development] St.Noigel:
I post it ))))

I have you and dhacker`s pages on bookmarks since I used Razr M )))
[Moto X Android Development] adm1jtg:
No issues at all and swipe to sleep addition is awesome
[Moto X Android Development] jakereeves31:
Indeed it is!
[Moto X Android Development] Travisdroidx2:
I have had the test build feeze twice and reboot. For some reason it won't pull a logcat but I did get the dmesg. https://www.dropbox.com/s/79jgesfyx7n1iln/dmesg.txt?dl=0

Stock KK running Eclipse 4.4.2 xt1060

Is the new test build undervolted more that r6?
[Moto X Android Development] zwliew:
The new build isn't undervolted. For reboots, /proc/last_kmsg is the one you should pull.

cat /proc/last_kmsg

Were you doing anything in particular when it froze?
[Moto X Android Development] Travisdroidx2:
Each time was right after a reboot. 3 times now. There is no last_kmsg when I look in proc/last_ksmg. There is a ksmg without the last_ksmg but the file has 0 bytes in it.
[Moto X Android Development] ss12108:
[MENTION=5604178]zwliew[/MENTION] was r5 undervolted -75 by default? R6.12 is running flawlessly so far and I'm curious to test how far I can push UV without losing stability.
[Moto X Android Development] zwliew:
r6.12 is not undervolted by default. Undervolting is bugged in r6.12 and results in an instant reboot in my case. I'll fix it in r7.
[Moto X Android Development] s5610:
I'm using r6.12 and I must admit that battery life was excellent on previous build, and it is on last one too, even w/o undervolting. My phone activity never endured so long on one charge - 2 days on medium load. Awesome, great project, I do press thanks every time I see new build )

P.S. Swipe to sleep doesn't work. I swipe and nothing happens. If I can some how help in debugging, please, give instructions.
[Moto X Android Development] zwliew:
Swipe on the navigation bar(or where it would be on your screen) either left to right or vice-versa.
[Moto X Android Development] s5610:
Yep, I tried everything, right-left, left-right, slow, fast, landscape, portret... Null feedback on my attempts. Maybe a cache clean must be performed? I will return on system backup copy then flash again r6
[Moto X Android Development] virusalone:
I had such problem after the first installation with cache wipe. but then I dirty flashed r6.12 and everything works good for me now.

I am on Kryptonite 1.4. Moto x 1032
[Moto X Android Development] zwliew:
I never actually wipe cache after installing any of my kernels. It is generally useless to do that.
[Moto X Android Development] zwliew:
It is written in OP. Stock
[Moto X Android Development] adm1jtg:
Loaded... all working find so far... Will report back as i have more use on the phone.

Thanks for all your hard work
[Moto X Android Development] isaakmg:
The kernel works fine. Thanks for your works friend.
[Moto X Android Development] zwliew:
r1.9 is released! :highfive:

As stated in OP, "decimal place" releases are considered test releases.

It's not quite a stable r2 release, but it's close enough. Main things left are to iron out any

possible

bugs and make the experience more enjoyable.

Otherwise, enjoy!
[Moto X Android Development] maxou88:
Nice ;)

I have one question, do you use your own kernel on your device ?

I think tonight i test your kernel.

The experience is very better than stock ? thanks
[Moto X Android Development] caviera:
Is there any way to flash back to default kernel?
[Moto X Android Development] rebretz000:
That's what I was wondering also. I assume we can just fastboot the stock kernel back in but a flashable zip would be nice.
[Moto X Android Development] mikeoswego:
In addition to boot.img, the flashable kernel zwliew_ghost_r1.zip replaces some files in /system/lib.

I made a modified version of the zip supplied by [MENTION=5604178]zwliew[/MENTION] that restores the original boot.img and lib files. This is from my XT1060 Dev Verizon on 4.4.4. I think but am not sure that these files are the same for all 2013 Ghost varieties. The attached file is a flashable zip. (This works for me, make sure you have backups before using this, or any other, flashable zip!)
[Moto X Android Development] makysssdroid:
Work greats stock 4.4.4 xt1056 whit device control

---------- Post added at 08:51 PM ---------- Previous post was at 08:43 PM ----------

What kernel control use for best tunning
[Moto X Android Development] mikeoswego:
Kernel zwliew_ghost_r1.9.zip changed an additional file in /system/lib/modules.

Here is another flashable zip that will revert to stock that will revert this additional file.

Added: This Kernel restore zip is for a Verizon XT1060 Moto X and I've renamed the upload..