yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] skiwong20:
yeah does..check the cm 11 branch

https://github.com/tdhite/android_kernel_motorola_msm8960dt-common/commits/cm-11.0
[Moto X Android Development] ##W4TCH0UT##:
Oh.. Thanks.
[Moto X Android Development] CsR0501:
Liquid Smooth V 3.X

Works fine in the last LS V3.X... Looks like one core works and when is fully used just then the other core works.

When i wanna see the CPU states in Kernel Tweaker the second core usually is offline... Am i wrong?
[Moto X Android Development] tdhite:
Second core is off-line as often as possible. That's not just SmartMax, rather most governors try to do that. SmarMax backs off more quickly, though, so might be off-line more than you're used to.

The easy way to see it all is (depending on ROM), go to Settings | Developer Options, scroll down and check "Show CPU info" on. That will show your cores on the top of your screen. Then just touch-n-drag your screen around. Most ROMs boost the CPU pretty hard when you touch/move the display to give a nice smooth feel, which cranks up the CPUs.
[Moto X Android Development] robbi24r:
Never flashed a kernel before. Do I just flash in TWRP and go from there?
[Moto X Android Development] DonKilluminati23:
Best to flash kernel after a fresh rom install, but yes just go into recovery and flash, I usually wipe cache after flashing a kernel also.
[Moto X Android Development] tdhite:
No need to wipe caches at all after a kernel flash -- they have nothing interesting by relation. If you really wanted, you could clear /devlog if you have access.

:cyclops:
[Moto X Android Development] robbi24r:
Anybody recommend a good kernel controller?
[Moto X Android Development] CsR0501:
Thanks! I understand... But in LS the two cores works together...

BTW... I confirmed that your kernel rocks!... Super smooth and the battery life is unbelievable! [emoji111]
[Moto X Android Development] tdhite:
Your cores still work together, they just don't both fire up if not really, really necessary. If you want to experiment, you are welcome to build the kernel and play around with the lines here:

https://github.com/tdhite/android_k.../drivers/cpufreq/cpufreq_smartmax.c#L127-L128

Those load values tell the governor when to bump up or down the frequency to deal with the need for more CPU. There's actually more to it than that, but it's a good play to start playing if you want to tweak even more (though it's awfully good with Rad Ryan's tweaks, as you noted).

Interestingly, note that we are not adding *tons* of mods to the kernel. Rather targeted adds that deal with specific issues. A lot of kernels just add gobs of toys and ask folks to figure the world out. for instance, I've seen some add all sorts of I/O schedulers that in fact have no value to flash memory. For example, some schedulers try to schedule disk activity based on 'distance' (the length a head would have to move between writes, for example) -- not useful to flash so why even add it other than the 'this kernel has gobs of features' goal.

Anyway -- onward and upward. Still working the dt2w / s2w toys. Faux123, of course, is the master of that and the merges are in, just have to tweak for a bit.
[Moto X Android Development] imparables:
Have been using this on the Mokee ROM for a bit now. Has been running very smooth with good battery life.

Nice work, thanks.

Sent from my Unlocked VZW M-O-T-O XxX
[Moto X Android Development] CsR0501:
I think i was wrong... Two cores works together is not necessary all the time because your kernel works better that Liquid Smooth's kernel...

The battery life is really awesome... I can't believe it!

For the suggest... I don't understand too much... I'm new in this but I hope do it in the future

Thanks for the great kernel... And thanks for your support and interest... Recommended in Spanish threads! [emoji111][emoji2]
[Moto X Android Development] tdhite:
Updated the OP with added instruction ...

All,

I updated the OP because I've seen a few reboots after wiping Dalvik cache that ticked me off. The gist is the added instruction:

IMPORTANT!!! If you wipe Dalvik Cache, let the phone boot completely once, then reboot again (long story, but AOSP roms set a property on Android that triggers your selected 'performance' settings (e.g., performance, balanced, whatever), when you clear Dalvik that property set trigger runs rather late and the init.d script delay setup by this kernel to force smartmax onto the CPU cores might already have happened, so you end up with the old governors (ick!). Reboot and all should be fine.

Just make a note of it -- if you wipe Dalvik: reboot from recovery, let it boot up fully (and give it some room to finish rebuilding the Dalvik cache (or ART rebuild if you use ART), then reboot clean one more time. Done.
[Moto X Android Development] ellcid:
This kernel its amazing
[Moto X Android Development] imparables:
Yes it is....

Sent from my Unlocked VZW M-O-T-O XxX
[Moto X Android Development] CsR0501:
I have an issue... When I turn on my phone and let it the screen off... The phone freeze and the screen don't turn on again... When i press the power button for 10 seconds the phone reboot and the process that I explicate happens again and again and again... [emoji29]

The only way for the phone works normally is unlock the phone when this turn on... I don't have to let it charge or let it the screen turn off...

Sorry my bad English... I'm Peruvian [emoji111]

Enviado desde mi Moto X mediante Tapatalk
[Moto X Android Development] robbi24r:
I think I was having a similar problem with a couple of roms the other night. I believe I found a solution by turning off the daydream function under the display tab.
[Moto X Android Development] Gundabolu SC:
Same thing happened to me!!! I thought I was the only one... Looking at all the positive comments I thought I messed up something... :D

After phone boots up if the screen is turned off it turns back on only after a reboot! ;(
[Moto X Android Development] tdhite:
Interesting -- the kernel has no modifications relative to the screen -- only governor and disk i/o schedulers.

So, can one of you do me a favor (I suspect some other mod on the phone is related to the issue) and send me the out put of this:

1) Make sure the phone is booted and the screen is ok;

2) plug it in to USB

3) adb shell

4) su

(then 'accept' for all time for now when super user comes up);

5) Reboot and get the screen to fail (however that happens, I can't reproduce this at all on a clean phone with this kernel);

6) plug it in to USB again

7) adb shell

8) su

9) dmesg >/sdcard/dmesg.txt

10) reboot and send me that file (/sdcard/dmesg.txt).

Something is bugging the screen, and I'll find it, even if it's some other mod fighting the kernel or something.
[Moto X Android Development] CsR0501:
I can't do this right now 'cause i'm in the office :crying:.. I'll do it in 7 or 8 hours when i go to my home...

Somebody can do this for all of us plz?

BTW... Thank's for your attention! :good:
[Moto X Android Development] tdhite:
I use FIOPS -- the kernel we put in PAC-MAN Rom has always had BFQ and others. FIOPS is simply my favorite for battery, performance, really all of it.

That's my opinion.
[Moto X Android Development] jco23:
[MENTION=4988866]tdhite[/MENTION]: I tried flashing your kernel on Nexus Rom Experience (9.8.2), and I did not get a mobile data signal. your kernel worked perfectly before (9.8.1 and older). could there be a setting I am missing or perhaps it's the updated CM commits?

thanks!
[Moto X Android Development] marbertshere:
If be very surprised if it has anything to do with the kernel. I'm on AICP and was having some problems with mobile data on a few nightlies but now it's all good.
[Moto X Android Development] tdhite:
The kernel is not at issue. I submitted ( a while ago ) a fix for the telephony/data issues, but CM is pretty broken in this area until they merge that: http://review.cyanogenmod.org/#/c/110384/ .

We merged that long ago into PAC-ROM (since I authored it, wee http://review.pac-rom.com/#/c/13403/), so load PAC if you are having troubles -- you won't need to flash this kernel as it's built in with PAC.

Anyway -- one day the basis telephony will fix on the merge, it just takes time for whatever reasons.
[Moto X Android Development] marbertshere:
CM12.1 based roms have a battery saving mode. I'm guessing it changes the governor to a power saving governor when your power is low. Since I'm using your kernel and use the Smartmax governor as my default, will the Power Saving mode work as designed or should I just disable it? If smartmax gives me better battery life then I just want to stick to that.
[Moto X Android Development] infectedorganism:
Once 'battery saver' is enabled due to low battery, I don't think it changes the governor. I believe it just disables animations, background data, sync, etc.

Either way, I leave it on balanced and achieve on average ~ 5 hours of SOT per day.
[Moto X Android Development] jco23:
Correct. Power saving mode only kicks on at a certain threshold (15% on stock, but some roms may allow this to be tweaked).

The change in mode is simply fewer (if any) background syncing.
[Moto X Android Development] marbertshere:
Delete delete
[Moto X Android Development] jco23:
update: [MENTION=4988866]tdhite[/MENTION] - looks like the issue with mobile data was NOT solely attributable to the kernel (which you already knew/claimed), as I've had a few days whereby I had no mobile data signal on the stock kernel. however, a simply reboot fixed it all cases.

I re-flashed this kernel, and all seems well (still can't get processor to stick on smartmax after reboot though). but still my favorite/preferred kernel. thanks!
[Moto X Android Development] mrdunlop:
So this kernel works with current cm?

---------- Post added at 05:38 AM ---------- Previous post was at 05:33 AM ----------

Just saw this and I was having data issues like crazy with the last few nightlies, good to know all is good, I am hoping to have the AICP back! The last couple were tuff to use with the data issues. Glad the Kernel is still working strong!

Edit: Just tried this Kernel on the latest CM AICP nightly, and it is def broken. This Kernel does not allow the sim card to mount, thus it is no longer usable. Same issue as with with the previous nightlies.

Hate to say it, but this Kernel needs to be updated
[Moto X Android Development] jco23:
i don't think the kernel needs to be updated so much as the ROM needs to be setup correctly. I've read a lot of issues that folks are having with recent nightlies on AICP and CM. I have not experienced any of those on NeXus Experience ROM (then again, there are no nightlies, just the latest stable release).
[Moto X Android Development] athulele:
CM recently merged the 5.1 kernel from motorola and hence this kernel won't work on the newer nightlies

[MENTION=4988866]tdhite[/MENTION] - here's the new kernel from cm - https://github.com/intervigilium/android_kernel_motorola_ghost
[Moto X Android Development] mrdunlop:
You may be correct, as a couple nightlies ago, several of the features were broke. They are slowly fixing them. In any case, be it the kernel or ROM, I how they get worked out as my battery hasn't been the same, missing this kernel.
[Moto X Android Development] mrdunlop:
Thank you for clearing it up! Looking forward to an update!
[Moto X Android Development] tdhite:
We already integrated everything in PAC-ROM. Will cut a build very soon.
[Moto X Android Development] ashatter:
We are still waiting for the new version. Any good news lately?
[Moto X Android Development] raff28:
does this kernel available for lollipop 5.1 stock rom?
[Moto X Android Development] orky87:
For the impatient fans simply flash the latest PAC ROM and back up the boot partition in the Recovery then simply restore it to whatever preferred ROM one uses. Done!
[Moto X Android Development] tdhite:
Moderators, please close this thread. We have done everything we could to date, and leave all in good shape as we keep the kernel updated in PAC-ROM.
[Moto X Android Development] athulele:
Thanks for all your work tdhite!

Could you please point us to the source of PAC-ROM kernel?

Clicking gitweb in your gerrit results in an error saying "not found"
[Moto X Android Development] tdhite:
https://github.com/split-screen/android_kernel_motorola_ghost should get you there.
[Moto X Android Development] athulele:
Thanks! I'll build it and share the zip here if you don't mind :D
[Moto X Android Development] tdhite:
So long as you give proper credits, no problem.
[Moto X Android Development] athulele:
I'll just share the zip in this thread. All credits to you. :good:

I'm having some errors while compiling though. :( If I fix them, I'll post the zip.
[Moto X Android Development] orky87:
Any success ?
[Moto X Android Development] athulele:
No. It's giving some errors with exFAT drivers apparently. I'll try to build it later with a different toolchain/
[Moto X Android Development] Ignaciodnb:
bootloop in mokee 5.1.1 rom :(

(with last twrp)
[Moto X Android Development] varunpilankar:
need DoubleTap2Wake feature.. any progress for it??!!
[Moto X Android Development] tdhite:
It's ok -- don't need logs. I figured out what's up. Long story short -- it relates to what's called "early suspend" and I just have to fix that up a little. It's gonna take a few days.

So here's the deal -- for now -- reboot the phone and when it comes up, just make sure you unlock the screen when it boots (most ROMs get to to the lock screen on boot). So long as that first unlock of the screen is in place, the setup goes ok.

sigh -- always something :)

Your choice while I fix 'er up. Either live with really bad battery, or just make sure to unlock the screen when it first boots. Hang for a fix. I got my HTC M7 device to do it finally finagling around with it. I'm using the same kernel code there, so I was able to nab the trace.
[Moto X Android Development] CsR0501:
Ok... I came to my home running but it's ok [emoji28]

I'll wait for your fix... I can live with the unlock on every boot! [emoji16]... The great kernel deserves! [emoji111]

Thanks man... You rocks too!

Enviado desde mi Moto X mediante Tapatalk
[Moto X Android Development] lslacker:
Has anyone tried this kernel with liquid smooth? Wondering if there's any conflict with the baked in oc/governor settings available
[Moto X Android Development] tdhite:
Here is your answer. Yes: http://xdaforums.com/showthread.php?p=54281284
[Moto X Android Development] CsR0501:
With this kernel, liquid smooth fly! [emoji111]

Try and tell us! [emoji6]

Enviado desde mi Moto X mediante Tapatalk
[Moto X Android Development] k3mik4l:
Would this work with AICP I'm running a test build for moto x. I believe it uses CAF.
[Moto X Android Development] CsR0501:
Like i see... It's based in CM... so it must works... make a nandroid backup first and test... :good:
[Moto X Android Development] tdhite:
Nandroid, flash it, if it fails, restore your original boot.img.
[Moto X Android Development] flyers00:
I just wanted to let you know that this kernel is working great with CM11, I have encountered no issues. Battery life is very good. Nice job on putting this together
[Moto X Android Development] tdhite:
Startup Black Screen Bug Fixed

All,

Wanted to let you know I have the startup issue some folks ran into fixed on the HTC devices. Will cherry-pick it over to Moto X this evening after a bit more testing (though it looks good).

The bug was actually a locking error in SmartMax -- it obviously never worked and frankly any machine using early_suspend within the governor is subject to it. The deal is when calling "register_early_suspend" the kernel will call the governor in the middle of that call if the device is suspended (screen off, basically). The original code locked the cpu so it could write info. Alas, the cpu was already locked by the register_early_suspend call, so that's a nested lock -- poof!

Now you know why you could'nt wake the screen up (even though the phone was still working). The governor was borked at that point.

Anyway -- as I said, plan on an updated flash tomorrow.

--- Update ---

Tested on multiple devices and now works. On Moto X, it's tough to prove in all honesty because the issue is highly timing related (long story). None the less, after so many reboots and with certain message logs on to show operations, one surmises the thing works. I'm leaving a few messages on so you can see operations a little. You'll just do:

dmesg | grep smartmax

And that'll say things like "early_suspend" or similar. What you won't see (I believe) is a kernel panic or exception. Update coming in the morning for fresh download. I'm also switching the way one sets smartmax. It's as simple as:

setprop sys.perf.profile 99

The flash installer appends a property handler to /init.target.rc and magic will then happen any time you set that system property. Of course a delayed init.d script sets that property a minute after boot (it is in /usr/local/userinit.d/99-tdhk).

:cowboy:
[Moto X Android Development] tdhite:
Kernel updated [07/28/2014]

The title of the post says it all -- updated with the fix for some reboots causing 'blank screen' to stick.

The Downloads Post has the link.

As always read the DISCLAIMER.

The Change Logs have a little more info.

Enjoy -- let me know how it goes.

:cowboy:
[Moto X Android Development] flyers00:
Just flashed the update and everything seems to be running fine. I was using the older version with CM11 and I'm still at 40% battery, about 16 hrs. Smartmax and sio. Thanks for the kernel ,nice job
[Moto X Android Development] robbi24r:
Pardon the noobness, but what's sio?
[Moto X Android Development] flyers00:
Here is a link that explains the Governors and I/O schedulers for most kernels. There are other references around but this should help.

http://xdaforums.com/showthread.php?t=1989824
[Moto X Android Development] bsilvertab:
Since flashing this Kernel many of my phone calls have dead air on the first try. Second try on the call it works just fine. Any ideas on how to fix it?
[Moto X Android Development] jakereeves31:
Same here. I was wondering what was causing that. Haha
[Moto X Android Development] insanitybit:
Why -03? Have you benchmarked this over -02?
[Moto X Android Development] flyers00:
After a couple days using this I'm having the same issue
[Moto X Android Development] tdhite:
First I've heard of an issue -- no prob -- let's get 're looked at. Can you send me logcat and dmesg logs after failed call?

PM is fine to keep the board uncluttered of logs.
[Moto X Android Development] flyers00:
No problem, I will send you a pm with a logcat when I get home. Great job so far

I just sent you a PM with a few logs. Hope they help
[Moto X Android Development] skiwong20:
As for this first flash of kernel...i would not relate these sound issue with the kernel its self but more toward the actual device files.."CM maintian". i have not seen any improve from it...that are found in the roms. i would like to know which rom? you guys choice to flash with. thanks i am tinkering to see if i can reproduce this issue..

edit: clean flash with PAC everyday..no direct sound call issue on first try..not found in logcat.
[Moto X Android Development] tdhite:
Hi all,

having dug through logs and kernel messages, in fact the kernel is operating correctly. There are setup issues with the device that are in process of fixes by CM and others. For example -- recent commits are attempting to address the sound routing issues for your phones: see http://review.cyanogenmod.org/#/c/65952/ for an example. That routing fix is in the kernel discussed in this thread already, but that alone won't fix sound routing issues.

A ROM includes code from "device trees" that determine device setup when your phone boots and other low level operations. Work there also is addressing the sound problems. Alas, those are entirely dependent on your ROM dev integrating them into their builds.

I am a PAC-Rom dev, so I use that ROM almost exclusively for day-to-day work, particularly on HTC M7 devices, but our maintainer for the Moto device (@skiwong20) already mentioned we are not seeing problems with sound routing similar to the bug reports here. PAC is quite up to date, so possibly give that a try. As for the kernel, I'm so sorry -- it has all 'known stable' support code for supporting the device trees in correctly routing audio..

I'll keep looking in the background to see about anything we can do.
[Moto X Android Development] CsR0501:
No problems here!

The best kernel! [emoji111]

I'm gonna download PAC right now... I love that ROM but since it's stop in 07/10 I change the ROM...

Let me test and I'm gonna tell you...

Sorry my bad English... I'm Peruvian! [emoji16]

Enviado desde mi Moto X mediante Tapatalk
[Moto X Android Development] flyers00:
Thanks for the update related to the kernel and info found in the logs. I'm going to keep using the kernel and possibly try out PAC ROM.
[Moto X Android Development] CsR0501:
I really... really miss long press action for navigation bar and for the ring... But the ROM runs smooth with tdhk kernel! [emoji111]

Enviado desde mi Moto X mediante Tapatalk
[Moto X Android Development] bsilvertab:
I am using Carbon Rom. Did wipe and flash a new version of that ROM and still having problems... which should remove the kernel that was flashed. My guess it is a problem with that ROM.
[Moto X Android Development] matt1313:
I'm running LS 3.2 and sound bug is there. Kerel is sweet though just annoying that every call I make I have to toggle speaker phone to get it to work.
[Moto X Android Development] kitcostantino:
Running the latest build of Leo's Carbon Rom. http://xdaforums.com/moto-x/development/rom-t2818695 flashed this kernel in twrp 2.7.1.1 and have no phone or speskerphone issues as of yet. (did a few test calls). Thank you for this kernel!!!
[Moto X Android Development] tdhite:
You should upgrade to the July 27th build. Has a bug fix you'll want.
[Moto X Android Development] kitcostantino:
Ha ha. Yeah, i had a randim reboot to black screen earlier today and had to restore the backup. just clicked on your name on the dl link (and host) and found the 7/28 build..it ran beautifly prior to that. here goes with the new one. ;) off the subject a bit, is flashify okay for kernel flashing in general? i flashed the 7/16 build in twrp 2.7, but i think flashify is easier. thank you man.
[Moto X Android Development] nexuspur:
Schedulers: SmartMax, interactive, ondemand, userspace, powersave, performance (more coming)

this should be governors or i am wrong? XD
[Moto X Android Development] jakereeves31:
It says those are the governors in the OP...
[Moto X Android Development] tdhite:
I just fixed it.

:o
[Moto X Android Development] nexuspur:
hehe :)

is this kernel based on 3.4.0 or 3.4.y? thx
[Moto X Android Development] KokoReyes:
Thanks for this kernel, im gonna try this ?
[Moto X Android Development] tdhite:
Updated 08/10/2014

Upgraded the kernel today, now keeping two versions:

1) Enhanced -- includes all features of the 'Current' version plus upstream Motorola kernel source commits beyond that which exist in the standard CM sources;

2) Current -- features lf this kernel committed solely on top of standard CM sources.

Downloads post has both, as always read the Disclaimer, and the Change Logs lists summary info regarding the changes.

:cowboy:
[Moto X Android Development] nexuspur:
-solved-
[Moto X Android Development] CsR0501:
Aosp / stock???

Hmm... a little question... This kernel works on STOCK rom too? :confused:
[Moto X Android Development] jakereeves31:
It says AOSP in the thread title.
[Moto X Android Development] nexuspur:
Hey to all,

can someone give some feedback about this kernel? i havent my device yet so i cant test it.

thx
[Moto X Android Development] damagedbits:
I've been using it on Paranoid Android 4.5 beta as a daily driver with default settings and its been perfect so far. Haven't had any lag or random reboots; seems to be pretty stable.

Sent from my xt1060
[Moto X Android Development] mslam02:
Link says 404 not found for me??
[Moto X Android Development] tdhite:
Both work for me. What are you looking at?