yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] HydrogenCyanide:
I want to be a beta tester :)
[Moto X Android Development] Ejvyas:
I thought this was only for stock but I can't find those words anywhere now. Did something change ? Will this work with cm 12?

Sent from my Moto X
[Moto X Android Development] zwliew:
Still only for stock, sorry
[Moto X Android Development] Travisdroidx2:
R11.5 so far so good. Phone sleeps well with 11.5.

Xt1060 Dev edition here.
[Moto X Android Development] hbar98:
What else have you done to your system? Looks like you haven't had any wakelocks for hours! I just checked mine, and Google Services has nearly 2,000 in the last 6 hours. That can't be just the kernel.
[Moto X Android Development] Travisdroidx2:
Eclipse ROM, r11.5 kernel with no tweaks. WiFi advanced settings and turned WiFi to never stay on during sleep.
[Moto X Android Development] kicker22004:
Well this is version 11.5 beta, this is an average day of use for me and I have to say that this kernel is rocking, battery seems better on this soak Test for me.
[Moto X Android Development] Travisdroidx2:
After day two this kernel is still rocking. Time for prime time :) Great job!!
[Moto X Android Development] abuttino:
Can I upgrade right from Faux to this or will I have to flash the stock system and boot partitions?
[Moto X Android Development] Travisdroidx2:
Kernel is running very smooth. 5 stars given my friend! Thank you sir
[Moto X Android Development] kicker22004:
I can confirm the android fc error that another user had on sprint (with Sim card in). I'm on republic wireless 4.4.2 and experience the same error until I restore my system. It is definitely something different with the sprint variants. Here are my logs.

Says my logcat is to large to attach.. Here you go.

https://docs.google.com/file/d/0B2aLFCgkLH9bYUdsMkJKYW5vdTQ/edit?usp=docslist_api
[Moto X Android Development] zwliew:
Do [MENTION=4789604]Kittiesoncrack[/MENTION] and you experience this on r1? Is it the same phone FC?
[Moto X Android Development] kicker22004:
Mine was on r2 and it just errors about no service then Sim error. My device is Republic Wireless 4.4.2 stock, it is based off of the sprint device.
[Moto X Android Development] zwliew:
Can you try it to see if it happens on r1?
[Moto X Android Development] ss12108:
Running r2 on a stock unlocked Maxx with no issues.
[Moto X Android Development] Kittiesoncrack:
I was on r1.9,

Tried R2 and R1 and they had the same problem

I can restore system to get it working again

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

Are you suppose to wipe cache or dalvik?
[Moto X Android Development] ConstantHero:
I've always wiped cache/dalvik before and after flashing a kernel, don't know if it matters but just for good measure.
[Moto X Android Development] zwliew:
So r2 with stock system modules works?
[Moto X Android Development] dray_jr:
ok so i finally got around to flashing your kernel on my Sprint 4.4.4 Rooted Moto K.

Ok well on first boot my phone started FC on the phone file even thou i was on the home screen not the dialer.

so i tried to install the stock kernel that you have uploaded and the same FC happened

Now i have completely wiped my phone and installed your kernel and we will see if it work or no i will post back.

edit at 10:32

so i did a factory reset and then installed your kernel. once the phone turned on it started FC right from the start so i have come to the conclusion that your kernel is not working on the Sprint Moto X. i hope you can find a fix so us Sprint users finally have a custom kernel that works correctly for us.

Thanks for your effort and i hope to see more work from you

Edit:

well with much trial and error. i could not get my phone to work after installing your kernel. i tried installing the stock kernel zip that the OP uploaded and i still got FC. so i did a facotry reset and i still got FC. the only way i was able to get my phone to start working again was to restore from my nandroid backup that i had made.

so be very careful when installing this kernel make sure you make a nandroid backup before you do anything because if this kernel dose not work the only way you will be able to get your phone working again is by restoring from a working nandroid backup .

hope this helps everyone
[Moto X Android Development] zwliew:
If u use my kernel + stock modules (not in the OP download, your own stock modules), does it work
[Moto X Android Development] dray_jr:
what do you mean stock Modules?
[Moto X Android Development] zwliew:
The files and folders in system/lib/modules on your stock sprint 4.4.4

Rom
[Moto X Android Development] dray_jr:
so explain to me what u want me to do/try and i will give it a shot
[Moto X Android Development] zwliew:
Take my r2 zip file, replace the files and folders in system/lib/modules with our stock ROM respective files. Then install and feedback
[Moto X Android Development] dray_jr:
ill give it a shot allready remade the kernel zip making another nandroid backup then installing ill let you know

Edit:

ok well same Fc as before com.android.phone

looks like it has to do with a network connection because every time i hit ok i get signal bars and then when the Fc comes back up i have no signal bars

yea this kernel def has some major issues with CDMA devices. the signal bar icon is flashing full and no signal, the sim or sd notification icon is flashing. and then the constant FC.

see this is the same thing us Sprint and Verizon user run into with every kernel. because we are CDMA devices no ones kernel seems to work for us. then to top it off not one Developer yet has tried to make there device CDMA compatible they just continue to work on there kernel for GSM and we get no love :(
[Moto X Android Development] kicker22004:
I already tried that and got nowhere with it. I'll do it again and get you the logs tho.
[Moto X Android Development] dray_jr:
here is a link to the Kernel source code that Motorola released the Sprint kernel source is spouse to be there somewhere but i dont have any idea
[Moto X Android Development] zwliew:
Can both of you and anyone else with such problems supply me your stock /system/lib/modules and boot.img? Boot.img can be found in /dev/block/platform/msm_sdcc.1/by-name/boot

I'll see what I can do.

Edit: oh, the build number you have would be good too. BTW, does faux123 kernel work for you guys?
[Moto X Android Development] kicker22004:
I've made a zip from your kernel with my boot.img and modules so that i can return to stock easily so here you go. Anything you want me to test let me know (i've Favorited this thread so i'll get updates now)

Build # KXA20.16-1.24-1.12

No to Faux123... however the AOSP TDHK kernel will boot and have working signal but graphic glitches.
[Moto X Android Development] zwliew:
You can upgrade straightaway.
[Moto X Android Development] 690sid:
does this kernel not support screen color calibration?
[Moto X Android Development] zwliew:
It doesn't, no kernel for Moto X does.
[Moto X Android Development] 690sid:
can it be added though? after using the "LiveDisplay" on CM12, the stock just seems too blue... Is it possible to add something like that?
[Moto X Android Development] zwliew:
So far, nope sorry :\. Most colour control interfaces are from the updated MDSS subsystem (which we don't have). LiveDisplay is built upon that, or if the device doesn't have it, LiveDisplay uses software post-processing from the OS level.
[Moto X Android Development] zwliew:
Disabling hot(un)plugging

I believe most of you have heard that Google and Motorola engineers had decided to disable hot(un)plugging on the Nexus 6 in Android 5.1. Thus, Nexus 6 became a full quad-core device 24/7.

TL;DR: Skip to bottom for instructions

There are several advantages to this implementation which I'll briefly state:

1. Less latency

2. Faster race to idle

3. Better task scheduling

If executed well, this can very well bring about battery savings and performance improvements. Therefore, I've decided to try it out.

Here, I have 2 kernels zips. One is r11.6, the other is r11.7-mpdecision.

r11.6

r11.7-mpdecision

Both kernels are very similar, only differing by a few commits. The major difference is that r11.7-mpdecision has mpdecision disabled. Therefore, r11.7-mpdecision runs on full dual-core mode, while r11.6 has normal hot(un)plugging.

I need YOUR input, on how each of them fares in terms of battery life and performance. After testing out each of them, please vote in my Google+ community on what you think. With your feedback, I can better optimize and make r12 a better release.

TL;DR: Try out each of these kernels, and vote on the Google+ poll for feedback

Kernels:

r11.6

r11.7-mpdecision

Google+ polls:

Battery life

Performance
[Moto X Android Development] kenosis:
Let me try 11.7 first
[Moto X Android Development] athulele:
Testing 11.7 right now. Seems good till now.
[Moto X Android Development] DaRkRhiNe:
Tried 11.6. It was the best of all the releases till now. Will try 11.7 now :good:

Thank you for all your hard work.:good:
[Moto X Android Development] Gustavo_s:
I've been working to port KCAL color calibration from nexus 4 to moto x:

https://github.com/gustavoss/kernel-msm/commit/622585edd36a17d883edc0b07381344a5e7099b5

It works, you can calibrate RGB values, but sometimes it reboots the device, so it's not stable.

I gave up, maybe you can find what is wrong.
[Moto X Android Development] kicker22004:
Ive been using 1.7 for a few days now but can't decide if its better on battery yet as I've restarted my phone a bit playing with modding my systemUi.apk. but man is it smooth and stable.
[Moto X Android Development] zwliew:
r12 - 20150317

I've decided to stick with mpdecision enabled for this release. If anyone of you wants to continue trying out mpdecision disabled, you can type in "stop mpdecision" in the terminal, or use Trickster Mod/Kernel Adiutor to disable it.

Download:

http://128.199.239.125/ghost/releases/zwliew_Kernel-ghost-r12.zip

Changelog:

Huge compiler optimizations

Upstreamed to v3.4.72

Intelligent boosting of cpufreq on thread migrations, which is basically when a task migrates between 2 CPUs

F2FS updates from Linux v3.18 --> storage speed improvements

Dynamic FSync

Improvements in timer and cpufreq selection for interactive governor (Check out GitHub for more info)

Limiting max cpufreq to 1 GHz on suspend (tunable: /sys/module/cpufreq_limit/parameters/suspend_max_freq)

Other performance and power improvements
[Moto X Android Development] :
I have the 2014 and I was wondering if this kernel could possibly be developed for that device as well? I'd be willing to help out but I haven't toyed around with kernel development yet. I understand everyone else love their Moto X stock but I'm pretty sure a few of us wouldn't mind a kernel or two over at our subforum. This looks great BTW!
[Moto X Android Development] DaRkRhiNe:
And how to enable it back on ? "Enable mpdecision"?
[Moto X Android Development] zwliew:
Type

$ start mpdecision

in terminal.
[Moto X Android Development] hbar98:
I went back to 11.7 from 12. With 11.7 I had better performance and the battery was about the same or slightly better.

When I flashed 12, I went ahead and manually stopped mpdecision. However, the phone was laggy. I would swipe on the home screen, and sometimes 2 seconds later it would actually move. I did some checking, and Core1 was totally offline. I loaded up some apps and messed around with the phone and Core1 never turned on. So I flashed back to 11.7
[Moto X Android Development] droidfreak007:
sorry if i sound like a noob but whats the difference?

im currently on 11. flashed this a few days ago. wondering if to upgrade to 12
[Moto X Android Development] Travisdroidx2:
Why flash r12 and then disable mpdecision? I am running r12 they way it was made and I am not getting any lag. In fact mine seems snappier.
[Moto X Android Development] hbar98:
The dev said that anyone wanting to keep trying mpdecision disabled to do so. I'm troubleshooting an issue with Pandora crashing when the screen goes off. With mpdecision turned off the app didn't crash as frequently, and it lasted longer before it eventually did crash.

And I did try r12 for a while before disabling mpdecision. My phone lagged with it enabled and with it disabled (looking back, the way I worded it makes it look like I immediately disabled it: I didn't). And like I said, even with it disabled, which should have had both cores running 24/7, core1 wouldn't turn on. So for my use, I went back to 11.7.
[Moto X Android Development] zwliew:
You could try enabling CPU1 manually after disabling mpdecision. You probably had a little bad luck, disabling mpdecision right when CPU1 was being offlined.

Type

$ stop mpdecision
$ echo 1 > /sys/devices/system/cpu/cpu1/online

in terminal.

What disabling mpdecision does is mainly stopping any hot(un)plugging of CPU1 from going on. So, it was possible that CPU1 was being offlined right when you disabled mpdecision. Thus, CPU1 was left offline.

The main changes are as stated on the changelog. Sorry, but what are you looking for?
[Moto X Android Development] Travisdroidx2:
Gotcha, yes everyone's devices run different. Also set up different between users. Now I understand why you did what you did for troubleshooting. Hope I did not come across as rude. Was not intended that way.
[Moto X Android Development] droidfreak007:
Which is better? mpdescision enabled or disabled? which do u recommend for a good balance of battery life and performance?
[Moto X Android Development] hbar98:
[MENTION=5604178]zwliew[/MENTION] I'll flash r12 and do those commands and see how it runs!

[MENTION=4251564]Travisdroidx2[/MENTION] No worries! I did not take offense at your questioning. Now, if you had called me an lolnewb, then we'd have words!

---------- Post added at 03:58 PM ---------- Previous post was at 03:38 PM ----------

Forgive me, I'm still learning *nix commands. You said to use "$ echo 1 > /sys/devices/system/cpu/cpu1/online", but that throws an error. Should I instead use "$ echo 1 /sys/devices/system/cpu/cpu1/online"? Without the > sign?
[Moto X Android Development] Kiristiba:
Hi, nope the > is essential but the command starts with echo not with the $ sign and it must be executed as root! :)
[Moto X Android Development] DangeloGH:
the best...

the best of all...

I play https://play.google.com/store/apps/details?id=com.naturalmotion.clumsyninja&hl=pt-br in every kernel to test...

in this r12 the game is runing like a top smartphone.
[Moto X Android Development] flick36:
Lollipop

Do you have plans to support Lollipop?
[Moto X Android Development] hbar98:
He said that he would... but first, Android Lollipop needs to be released for our phone (which it has not, only the soak test which isn't a wide release), and second, the source code from Motorola will have to be released. And since he's in school now, it may be a little while before he releases a compatible kernel.

You can always search this thread for answers as well. That's how I found out what his plans were for lollipop.
[Moto X Android Development] zwliew:
The $ should be omitted. So in reality, Type the commands I typed in the previous post, excluding the $.

stop mpdecision
echo 1 > /sys/devices/system/cpu/cpu1/online

[MENTION=3041825]hbar98[/MENTION], what he said. ^

For now I recommend mpdecision enabled, A.K.A. leaving everything the way it is. We still need to undergo more testing with mpdecision disabled to make a judgment.

I have plans to support Lollipop, but since my Moto X is broken again, I need to find some internal testers before I launch a Lollipop version.

[MENTION=4339033]flick36[/MENTION], what he said. ^
[Moto X Android Development] droidfreak007:
installed r12 yesterday. got two random freezes which caused a reboot since then.

going back to r11 which was more stable for me.
[Moto X Android Development] hbar98:
& [MENTION=5604178]zwliew[/MENTION]

Thanks for the pointers, though I didn't put the $ in front... I knew *that* much at least! hah!

Even after executing the command as root, it still threw up errors, so finally I just did it over adb, thinking that I must be doing something wrong in terminal.

I got the setting to change, verified it in Trickster, and went on my merry way. Phone was responsive, battery drain was about the best I've had, but I'm still having the Pandora crash issue.

Here's what's going on, in case anyone has any suggestions on how I can fix this: When I use Pandora and the screen goes off (either by timing out, or by me pressing the power button to turn off the screen), after a song or two, Pandora will crash. It will keep playing music, but the app will be frozen. The phone will be really laggy as well until I either manually stop Pandora or get the "This app isn't responding" box to pop up. I've sent several reports to Pandora, but they are slower than molasses in winter with updating their app.

This has happened since r10 and higher with this kernel, but doesn't happen on stock. I've tried mpdecision on and off, and when it is off Pandora seems to last a little bit longer before it crashes (which is why I wanted to disable mpdecision on r11, to see if maybe some improvement from r11.7 to r12 made any difference), but it still crashes.

Today I reflashed r12 and cleared the cache and then left it alone to see if that will make any difference with Pandora, though, and this is very unscientific and highly open to interpretation, my battery performance is noticeably worse with mpdecision enabled then when it is off.

If anyone has experienced a bug like this, have you figured out what is going on? Is there something else I can try to see if it would stop Pandora from crashing with the screen goes off?

Thanks for the great kernel, and thanks for any support!

EDIT!

Erk! I meant to say that I'm on r12, not r11
[Moto X Android Development] Travisdroidx2:
R12 has been flawless for me. Gaming is smooth and fast. And as you can see the device goes into a nice deep sleep. XT1060 Dev edition. Great work!
[Moto X Android Development] Kiristiba:
Hi,

I use your kernel since r11. I got two random reboots since I'm on r12 too. I went back to 11.7 to see if the problem is really kernel related.
[Moto X Android Development] DangeloGH:
I got some random reboots yesterday, on r12
[Moto X Android Development] adm1jtg:
I ran Pandora for well over three hours continuous yesterday with no issues at all using r12. Have you tried uninstalling and re-installing Pandora

And just for the record after 2 days not a single reboot
[Moto X Android Development] Travisdroidx2:
Same here R12 for a couple days and not a single reboot.
[Moto X Android Development] zwliew:
Standard procedure. Please get the last_kmsg right after a random reboot for me to debug.

cat /proc/last_kmsg > /sdcard/last_kmsg.txt

Then attach the last_kmsg.txt and send it to me.

Thanks.
[Moto X Android Development] hbar98:
No luck. Uninstalled the app and reinstalled it, rebooted, app still crashes after the screen goes off. If the screen stays on the app runs fine.

I also haven't had any reboots... just the one app crashing.
[Moto X Android Development] adm1jtg:
Only time i had crashes like you describe is when i was using v4a. Since this kernel now supports faux sound i use that now. If its not pandora capture the logs like recommended but also think about what other sound based apps/sound replacements you might have on your phone as your likely having a conflict
[Moto X Android Development] Hasuris:
fauxsound and v4a work very well together. I've been using these for months now. While fauxsound feels gimmicky, i can't live without v4a.

No issues with r12 so far.
[Moto X Android Development] adm1jtg:
Like I said when I used v4a in the past and I ran pandora streaming usic at the same time as a gps app either google or tomtom it would lockup my phone. Never could figure out why but as soon as I uninstalled v4a the problem went away.
[Moto X Android Development] DaRkRhiNe:
r12 is very smooth and battery life is also great. But sometimes it lags during the animations. Like while closing whatsapp...
[Moto X Android Development] adm1jtg:
Can you do the following download from playstore logcat extreme. This program allows you to turn on logcat on your phone and then save it to a file.

So start logcat extreme, then make Pandora crash like you mentioned above, go back to logcat extreme, save the file and post it here so we can see what's causing your error.
[Moto X Android Development] hbar98:
I was just investigating that very thing! I'll see if I can do it when I'm not in the car... that's when I listen to Pandora... safety first! heh..

---------- Post added at 02:20 PM ---------- Previous post was at 01:51 PM ----------

Okay, so I had some free time at work and was able to make it crash. Hopefully the logs will help! It took a few songs to get it to crash, but once it did I waited a few moments and then emailed the log to myself.

Here's the drive link to the txt file. Too big to post here.
[Moto X Android Development] adm1jtg:
Ok if you could please try this for me do EXACTLY the same process again that you used in this first test but make sure bluetooth is off for the entire test so use headphones or speaker. Let me know if still crashes like before.

Oh and lets pull a kmsg file BEFORE you redo test and after. The easiest way to get this for me is as follows:

Cause the error to happen as you just did when we pulled the logcat

Reboot the phone

go to /proc folder off the root of your filesystem, copy the last_kmsg file and post it

repeat the process as i asked for above with bluetooth off for both logcat and last_kmsg. If pandora doesn't crash at all with bluetooth off no need to capture the files just tell me that
[Moto X Android Development] hbar98:
Yeah, I'll do that. For the record, I wasn't streaming through bluetooth the last time... just had it on. Was listening through the phone's speaker.
[Moto X Android Development] adm1jtg:
Just updated the above post with additional instructions
[Moto X Android Development] hbar98:
I was in the middle of a test, so I'll post what I have so far and continue trying to get pandora to crash.

Logcat, Pandora crash, bluetooth off.

Last_kmsg after Pandora crash, rebooted, bluetooth off.

You also want the following, if I read your instructions correctly: last_kmsg after a pandora crash with bluetooth off before I reboot, and a last_kmsg before and after a pandora crash with bluetooth enabled. If that isn't correct let me know and I'll see what I can do!

As you can see, Pandora crashes when bluetooth is off as well.

(edit) Got another last_kmsg. Last_kmsg after pandora crash, bt off, before reboot.

I need to get a few things done, so if you need any other reports or anything, let me know and I'll get them done later today.
[Moto X Android Development] kenosis:
Running fine on R12.
[Moto X Android Development] Travisdroidx2:
4 days on r12 and running great! No reboots or any issues at all.
[Moto X Android Development] testuser0072:
Yeah, R12 seems to be the best kernel so far for our Moto X (KK 4.4.4). I have a lot of apps installed but kernel is very stable and battery life is really great.
[Moto X Android Development] flick36:
I've been running R12 for a 26 hrs without charging the phone, (sorry no screenshot had to reflash due some wifi problem) and it was really smooth and everything was fin, very happy with the kernel.
[Moto X Android Development] seafood99:
R12 is the best!
[Moto X Android Development] sruel3216:
anyone running krypton 4.4.4 xt1060 xposed with r12? i flashed the other day and got 3 reboots in an hour while it was in my pocket. does anyone know the stock kernel voltage? maybe il try raising them to stock values.

thanks
[Moto X Android Development] automaddux:
I thought I saw in the change logs that this kernel sites support lollipop, am I wrong?
[Moto X Android Development] mac1996:
Nope excpet one version/release
[Moto X Android Development] automaddux:
So... Which one? And does this also work for stock?
[Moto X Android Development] adm1jtg:
I am on xt1053 but running krypton and xposed with r12 and no issue at all in days
[Moto X Android Development] sruel3216:
hmm interesting lol