yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] athulele:
New release? I can't see a download link anywhere
[Moto X Android Development] CsR0501:
Next to "Download:" [emoji29]

Enviado desde mi Moto X mediante Tapatalk
[Moto X Android Development] tdhite:
'New release' meant no Lollipip releases. This kernel will work 5.0 or 5.1 just fine.

I track interesting changes and will bring them in when interesting.
[Moto X Android Development] infectedorganism:
[MENTION=4988866]tdhite[/MENTION]

Would you mind putting out a new build synced with the latest CM12 sources?
[Moto X Android Development] CsR0501:
CM12.1... It would be great! [emoji2]

Enviado desde mi XT1040 mediante Tapatalk
[Moto X Android Development] tdhite:
This is cm12 or 12.1. There are no useful updates to the moto x kernel in CM. Why the ask, are you having troubles?

[edit] -- I long ago picked the quickdraw disable patch into the kernel sources, don't think I ever uploaded a fresh copy. Now I did. Check in a few minutes for updated OPs.
[Moto X Android Development] infectedorganism:
No, no troubles. I saw that there have been numerous commits since the last release, so I was curious if you could release a new version with those changes.

If there are no useful changes, disregard my request.

And thanks for the kernel. It is much appreciated.
[Moto X Android Development] JimJ2Mz:
What does disabling quickdraw help with, if you don't mind me asking? I'm not familiar with this.
[Moto X Android Development] tdhite:
It is just not useful for this device so no need to enable it in compilations.
[Moto X Android Development] JimJ2Mz:
Holy shizzles, a new build. Read posts so quick I missed that part. Sync'd with the latest sources. I'm pretty sure that doesn't do much but it sure does feel nice to feel up to date.

Thanks for pushing the updated build!
[Moto X Android Development] St.Noigel:
Is it new release? :good:
[Moto X Android Development] CsR0501:
[MENTION=4988866]tdhite[/MENTION] you are the man!

Thanks for your great support! [emoji111] [emoji16]

Enviado desde mi Moto X mediante Tapatalk
[Moto X Android Development] KD25:
I am new to flashing kernels and am trying to understand the whole mumbo jumbo. I flashed this kernel on CM12.1 and found out more governors and i/o schedulers. So if i am using the same governor and i/o scheduler that i was using on the previous kernel, flashing this kernel was pointless? To really use this fully i need to select the other governors and i/o schedulers that came with it? Also, i read the first post and found that the default governor will be smartmax and i should wait out a minute for the script to run every core as smartmax style but when i used a kernel control app i found out the governor to be interactive. Do i have to manually select the governor everytime? Lastly, which is the best governor and i/o scheduler that balances performance and battery life. I know its tough to answer and the answer is mostly based on the usage like playing a game or simple browsing. But really what's the best one for normal use. I'd like max battery but not at the cost of stuttering UI.
[Moto X Android Development] JimJ2Mz:
CM12.1? Good choice. As tdhite and many others have said, it's best to go with the Smartmax CPU Governor and the FIOPS I/O Scheduler. Also, I definitely recommend using Kernel Adiutor for kernel modifications.

As for myself, I've been using that Governor/Scheduler combination for a few weeks, and battery life is fantastic for me. I've nothing disabled and I manage to get ~4 hours SOT with around 24 hours on battery, from 100% to 10%. And that's with a lot of bluetooth music and YouTube videos, plus today's Google I/O streaming. It still does depend on your location and the apps you use, as well as the cellular signal. Some things just can't be changed, but this kernel will definitely help.

https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en
[Moto X Android Development] Drakonas:
[MENTION=4988866]tdhite[/MENTION] Do you have plans to add NFS support? I would love to be able to mount a folder remotely.
[Moto X Android Development] Tonystarki:
link of download build day 6?update?
[Moto X Android Development] athulele:
https://www.androidfilehost.com/?fid=23991606952609469

This is the latest one. It's not updated daily.
[Moto X Android Development] tdhite:
The OPs are always up to date. The day I stop working updates I'll tell you all in this thread. I'm going to kept this going for the foreseeable future as we manage this kernel in PAC-ROM.
[Moto X Android Development] Tonystarki:
your kernel will be included in the pac rom?
[Moto X Android Development] tdhite:
Has been for quite a while.
[Moto X Android Development] orky87:
You're like the only guy doing us a favour in the kernel department for the x. Hope you continue to hang around or us battery sensitive folks are proper screwed. Keep up the good work! Cheers.
[Moto X Android Development] Pigatto:
Any date for the overclock support?
[Moto X Android Development] CsR0501:
Hey Mr. [MENTION=4988866]tdhite[/MENTION]

Sorry but the last kernel breaks the "ambient display" of the last CM12.1 nightly... I hope that you can fix that because this kernel works awesome! :)

Thank you!
[Moto X Android Development] infectedorganism:
Indeed. Here is the boot.img from a recent Pac ROM nightly.

https://www.dropbox.com/s/4qul87ep3b8exq9/boot.img?dl=0

Flash in TWRP. It will be the same TDHK kernel you are using now, but ambient display works.

I believe this is the missing commit. Excuse my ignorance if I am wrong.

http://review.cyanogenmod.org/#/c/96199/
[Moto X Android Development] CsR0501:
I'm gonna test and i let you a feedback... thanks for your interest! :good:
[Moto X Android Development] tdhite:
No prob. Look for it tomorrow.
[Moto X Android Development] tdhite:
Well, a day late :(. Still -- updated. See http://xdaforums.com/showpost.php?p=54248111&postcount=3 for downloads.
[Moto X Android Development] marbertshere:
Thank you for the update. I tried a different ROM for the first time yesterday and thought I was going crazy and somehow broke Ambient Display with some setting.
[Moto X Android Development] marbertshere:
[Deleted] When in doubt, reboot.
[Moto X Android Development] Likn'_ùs:
Many thanks [MENTION=4988866]tdhite[/MENTION]! Are there any news for the upcoming feature of Doubletap2wake?

Cheers,

L.

;)
[Moto X Android Development] marbertshere:
After turning on the cpu option in Developer Settings, I noticed that one core is running Smartmax while the other is Intelliactive. I have my CPU set to Smartmax and the IO scheduler to FIOPS. Is this normal or should both cores be on the same governor?
[Moto X Android Development] tdhite:
This is a problem with your ROM. Root access must be enabled at boot. Likely your build.properties file has root access off by default.

Fixup that and all will be well. If everyone wants, I'll add am installer mod to fixup build.properties to allow root access at boot.
[Moto X Android Development] marbertshere:
I'm not really sure which line to edit so I'll Google it. I figured enabling root access on boot in SuperSU would do the trick, but i guess not.
[Moto X Android Development] marbertshere:
Could someone help me out with getting both cores to run the same governor? My searches didn't turn up anything.

Also, does having the per-app profiles enabled in CM settings affect performance/battery life either way?
[Moto X Android Development] core2kid:
Can I flash to stock rooted 4.4.4 on an unlocked bootloader phone?
[Moto X Android Development] chaoslimits:
[MENTION=4988866]tdhite[/MENTION]

Any chance of F2FS support? Curious of F2FS formatted /cache partition. Thanks.
[Moto X Android Development] tdhite:
Already has f2fs.
[Moto X Android Development] md07:
in new version ?
[Moto X Android Development] marbertshere:
[MENTION=4988866]tdhite[/MENTION] Would you be willing to help me get your kernel functioning properly on my ROM? Either with the installer mod or by telling me what to edit in build.prop?

I'm sure you're busy but I would really appreciate any help. My searches didn't turn up anything. Thank you.

I'm running AICP, 5.1.1. when i turn on the Display CPU option in Dev settings it reads that core 0 is on Smartmax governor and core 1 is on Intelliactive.
[Moto X Android Development] Ishaan Gupta:
[MENTION=5736922]marbertshere[/MENTION]

I too am looking forward to try this kernel on aicp rom. I hope [MENTION=4988866]tdhite[/MENTION] helps us users in this.

I saw a few posts back someone saying that ambient display does not work.

Can you confirm if it works on aicp?
[Moto X Android Development] matt1313:
Can you explain this a little better?

Is it this line

persist.sys.root_access =

If so mines at 0 should I go to 1 or 2 or 3?

Can't find the difference.
[Moto X Android Development] marbertshere:
Ambient Display works if you use the 6-28 build that [MENTION=4988866]tdhite[/MENTION] has posted on op. He was super quick to fix that ☺
[Moto X Android Development] tdhite:
Set it to 1 and you'll be happy.
[Moto X Android Development] matt1313:
Very happy. Thanks
[Moto X Android Development] infectedorganism:
Mine is already set to 3 and intelliactive is still active on the second core. AICP ROM.
[Moto X Android Development] matt1313:
Set it to 1 reboot profit
[Moto X Android Development] infectedorganism:
It won't make a difference. 3 give root access to not only apps, but also adb upon boot.

/sys/devices/system/cpu/cpu1/cpufreq/* gets rewritten every time the core goes offline. When it gets rewritten, intelliactive is set as the scaling governor.

With mpdecision off, echo "smartmax" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor works (after boot). But again, with mpdecision on, it gets reset to intelliactive every time the core goes offline/online.
[Moto X Android Development] chaoslimits:
My xt1060 won't boot any 5.1.x roms with /cache formated as f2fs. Do you think it might be a Rom thing (I was under the impression that f2fs support was built in cm12.1).

Thanks.
[Moto X Android Development] infectedorganism:
Probably. I believe on Cyanogenmod, data is formatted for f2fs, but /system and /cache are ext4.

I'm ignorant on the matter, but it may be the fstab.qcom file that is causing it to not boot. It tries to mount /cache as ext4 when it is formatted as /f2fs.

Again, I could be completely off, but that is my guess *shrugs*
[Moto X Android Development] Ishaan Gupta:
No matter which governor I apply, core1 is always intelliactive. Core0 is fine though.

Also, the governor does not apply one minute after the boot. Even the userinit.d script does not run.
[Moto X Android Development] Ishaan Gupta:
I have set persist.sys.root_access=1

But it still does not apply smartmax to core1. Only core0 is set as smartmax.

It would be great if you add an installer mod to fixup build.properties.
[Moto X Android Development] chaoslimits:
I guess that's probably part of the problem. Editing the fstab (in boot.img) doesn't seem to be the fix and as far as I can tell, this kernel doesn't do anything to fstab.qcom. Thanks though.

Edit: Nevermind got it working! Thanks for the fstab tip [MENTION=4078274]infectedorganism[/MENTION]

Sorry for the offtopic posts.
[Moto X Android Development] marbertshere:
So is there a solution? Disable mpdecision on boot? Or is that a bad decision ? No pun intended.

Is it detrimental to have two cores using different governors?
[Moto X Android Development] tdhite:
Don't disable things. The property settings setup by the kernel installer should handle things. I'll take a look.
[Moto X Android Development] brickhayabusa:
Problems here?

I want to flash it, but i'm not sure, the cores don't shut down? Or anything?

I want it for my battery but if i understand if the cores are turned on all the time my battery drains no?

Thnx nwn
[Moto X Android Development] tdhite:
Please don't start false info dissemination. Goodness, who said anything like that? Mpdecision handles core shutdown. All someone is experiencing is that one of the cores is not up when the governor gets set. It's really no big deal.
[Moto X Android Development] marbertshere:
No man, nothing like that happens. I highly suggest this kernel.
[Moto X Android Development] bushako:
Active display wake on touch was working with stock cm kernel but after flashing this kernel it doesn't work anymore. Any suggestions? I'm running latest nightly CM12.1
[Moto X Android Development] brickhayabusa:
Sorry

lel :v

i only ask, i never want to create false info.

sorry nwn
[Moto X Android Development] infectedorganism:
The 6/28 kernel should work perfectly. Try toggling the settings.
[Moto X Android Development] bushako:
Okay just tried it again and it works. Thank you for this kernel I noticed that after switching to Smartmax governed the phones overall temperature isn't as high.
[Moto X Android Development] Ishaan Gupta:
[MENTION=4988866]tdhite[/MENTION]

Is wiimote supported on this kernel?

Edit : never mind, didn't work. I switched to cm12.1 just to try this kernel. It's really good. Thanks for you hard work. Keep up the good work.
[Moto X Android Development] EmilianoTalamo:
Any idea of why init.d is not working for me? I put a test file on the etc/init.d and it does not work at all.
[Moto X Android Development] infectedorganism:
It hasn't worked for me on any ROM/kernel I have tried *shrugs* You can use Kernel Adiutor to adjust your kernel settings. You can also use it to 'emulate init.d' which is an easy 'fix' for init.d scripts not executing at boot.
[Moto X Android Development] marbertshere:
Can anyone tell me how to get the governors working on both cores? My rom maintainer assures me it's an issue with the kernel but I'd like to know: is anyone running this on AICP? Are there any other aosp kernels for ghost?
[Moto X Android Development] Gustavo_s:
This set of patches fixes it on my custom kernel:

https://github.com/gustavoss/kernel-msm/commit/a8a31ac209eda20d1480d17466c659e52f34c9a0

https://github.com/gustavoss/kernel-msm/commit/82cbd16c0b6afc853d000695245168fa791e1b87

https://github.com/gustavoss/kernel-msm/commit/955088d864eb29b2fc7bb2ee3fc33ff2aef9bfc3

https://github.com/gustavoss/kernel-msm/commit/006887a7d1d5d5803720bdf765b7eacd6f9a8207

https://github.com/gustavoss/kernel-msm/commit/5856e494218de714b5e233c87d3425c538a3ea96

https://github.com/gustavoss/kernel-msm/commit/5393ddcc8df09f8594222efed14b0852eb6729d1

https://github.com/gustavoss/kernel-msm/commit/085a9b167bb8ce164210d6a6800c778c998477e2

https://github.com/gustavoss/kernel-msm/commit/fecef695e75812410988d1cecb718c5b60c5111b
[Moto X Android Development] CsR0501:
Do you gonna share ii? [emoji16]

Enviado desde mi XT1040 mediante Tapatalk
[Moto X Android Development] Gustavo_s:
Maybe, i want to add AnyKernel first to prevent incompatibilities among aosp roms.
[Moto X Android Development] tdhite:
Please explain how a kernel is somehow related to init.d. and then please never post here again.

Init.d is a ROM and init issue. Proposing that the kernel, absent totally opening the system to every security breach on the planet, can fix init.d is, well, total garbage.

Let me know precisely where any of that is incorrect and the exact patch in the kernel that affects init.d.
[Moto X Android Development] tdhite:
For the rest of you that might believe the gibberish about kernel patches fixing what is an init problem, I'll post a very simple init fix tomorrow (not a kernel fix) that rectifies all issues you see.

Wow. I need to read my own thread more often :).

:cowboy:
[Moto X Android Development] zwliew:
You probably misread his post. From what I can see, Gustavo_s was referring to a 'bug' that causes the CPUfreq governors of CPU0 and CPU1 to be unsynced.
[Moto X Android Development] tdhite:
I did not misread. That has nothing to do with the kernel.
[Moto X Android Development] tdhite:
I await the exact patch.
[Moto X Android Development] tdhite:
My point is, folks, the patches force a policy and preclude all others. If the poster actually understood that, (s)he would never drive that at the kernel layer. In brief, it doesn't actually fix a problem, it presumes policy a kernel should never presume.

So much work for two lines of init is very frustrating to see. This kind of code is where Android starts to take a nose dive, IMHO.

No matter, as I mentioned, I'll add a simple fix tomorrow.
[Moto X Android Development] marbertshere:
[MENTION=4988866]tdhite[/MENTION] thank you. Looking forward to bring able to fully experience your work
[Moto X Android Development] tdhite:
All,

For those having challenges with both cores setting to Smartmax, can you please do the following in a command shell (terminal) and give me the results of your core settings:

su
setprop sys.perf.profile 99

Wait about 10 seconds, then tell me if all cores were set. Remember, I don't have a phone to test so just need to know that info before I commit the init setup fix.

Thanks for any help.
[Moto X Android Development] marbertshere:
So it seems to set both cores to smartmax immediately after entering the line, but once the second core goes offline it reverts back to intelliactive again.
[Moto X Android Development] tdhite:
[KERNEL][AOSP 4.4.4/5.x|CAF][UNIFIED ghost | moto_msm8960dt][TDHK 06/28/2015]

What this says is the kernel and init tools I package in the kernel are correct. That intelliactive became the governor says, unquestionably, that you are running another tool that is setting CPU values, or your ROM is doing so. Why do I say that? Intelliactive is not the default governor, thus something is explicitly setting that. Also, no kernel patch in this kernel attempts to alter governors once set.

I'm not here to fix ROMS that are not PAC-ROM, where I am a core dev. But I might be able to assist if you tell me what tools you are using for tuning CPU settings (including built-in Settings facilities of your ROM).
[Moto X Android Development] Ishaan Gupta:
I too had the same issues. I tried this and as [MENTION=5736922]marbertshere[/MENTION] said it did the same on my phone.

I am using kernel aduitor which came preinstalled on my rom to set up the cpu governor on every boot.

The init.d script does not work automatically on my phone.

I am using aicp. I think the same is happening with cm12.1 users too. Correct me if I am wrong.

I no way I am accusing the kernel for this. Your help is greatly appreciated.
[Moto X Android Development] tdhite:
PAC-ROM, which is a CM12.1 derivative, and the repos under which this kernel is maintained by myself and [MENTION=4360710]skiwong20[/MENTION], has no reports of issues. No reports form CM folks, though the init.d script issue may be a prob.

With that said -- getting a moto x this evening for further testing. I'm sure I can fix the CM12.1 code on userinit (i.e., init.d) and commit it to the CM repos.

In the mean time, go get PAC-ROM, seriously, all this is built-in, and the settings app allows control of CPU, memory, etc. Not a plug, it's just everything you want and probably more.
[Moto X Android Development] marbertshere:
I'm also using AICP. As far as I know I'm not doing anything to tweak any cpu settings but I'll ask our maintainer if he has any idea. I appreciate your help. And im glad you're getting a phone [MENTION=4988866]tdhite[/MENTION]!
[Moto X Android Development] tdhite:
Hang in folks -- think I got the issue across any ROM. Might have to revert some code, though. lots of testing to do.
[Moto X Android Development] tdhite:
Ok -- all updated -- give the latest install a shot:

Downloads

As always, read the Disclaimer

Had to revert a revert (long story, but it's fine). Should be good.

:cowboy:
[Moto X Android Development] marbertshere:
Works great! Thank you! Was it a hard fix?
[Moto X Android Development] md07:
can I use this kernel for Stock 5.1 ?
[Moto X Android Development] koolguy366:
does this work on stock 5.1 root?
[Moto X Android Development] marbertshere:
This kernels designed for aosp ROMs. But there is a kernel for stock called zliew or something like that. Check out the forum for Android development.
[Moto X Android Development] ConstantHero:
7/20 release working perfectly on AICP. Both cores sticking to the correct governor.
[Moto X Android Development] EmilianoTalamo:
On Kernel Aduitor whenever I try to limit the CPU frequency for battery saving purposes, it only applies to one core (the 2nd core still ramps up to the max freq), is there any way that you can add compatibility to that app or the app developer should fix that? Either way, what kernel control app do you recommend, guys?
[Moto X Android Development] marbertshere:
I'm a big fan of kernel adiutor. It's also baked into the rom I'm using but I was using KA before flashing this rom.
[Moto X Android Development] grimez:
Loving this paired with Megatron's AOSP build... buttery smooth.
[Moto X Android Development] flopezm:
this kernel cant in rom stock 5.1?
[Moto X Android Development] ban.codrut:
1. Can You please add suport for Fast Charge ?

2. Idk why but once in a while the CPU1 minimum frequency jumps to 1.5 GHz ?

Plus the maximum frequency of that 2nd core goes 1.7 GHz every time it switches back online.
[Moto X Android Development] Tonystarki:
support for double tap to wake??
[Moto X Android Development] marbertshere:
Is listed in the OP under future development. So no, not yet.
[Moto X Android Development] CsR0501:
Hey! Somebody knows if the last CM nightly (08/06) works with the last version of TDH kernel? I'm in the job and i can't make a backup because i don't have enoguh memory :P

Thanks!
[Moto X Android Development] tdhite:
I'll cut a build this evening. The existing should be fine, but why try when it is just a bit away. Hang in . . .
[Moto X Android Development] perfoliate:
Looks like CM merged in a few ghost kernel commits last night.
[Moto X Android Development] tdhite:
Updated - 08-07-2015

Have at 'er -- let me know if there's troubles.

Read the Disclaimer.

Check the Changelog.

Download as you desire.

:cowboy:
[Moto X Android Development] Tonystarki:
build in https://www.androidfilehost.com/?fid=24052804347789375
[Moto X Android Development] ConstantHero:
8/7 up and running here. Very snappy and smooth mixed with AICPs latest build, no issues here.
[Moto X Android Development] Tonystarki:
Implement fast charger, and sound ? [MENTION=4988866]tdhite[/MENTION]
[Moto X Android Development] HydrogenCyanide:
It's safe to install the kernel if it's some weeks old?
[Moto X Android Development] infectedorganism:
Yes.
[Moto X Android Development] Drakonas:
While fast charging has been discussed (read OP), I am wondering if [MENTION=4988866]tdhite[/MENTION] plans to add Faux123's custom audio modules to his kernel. I would love to see this happen. You all would be amazed at the difference in audio quality when using Faux123's Audio App (on the Play Store) with the Moto X compared to stock audio. The Moto X has a Wolfson audio chip in it, and sadly stock Android never takes advantage of this. :b Right now with Resurrection Remix rom, the audio quality is so bland and the soundstage is very very small. Almost sounds as if it is mono audio.
[Moto X Android Development] infectedorganism:
[MENTION=4988866]tdhite[/MENTION]

Would you mind providing an update with the latest Cyanogenmod kernel commits for Ghost?

Thanks in advance
[Moto X Android Development] tdhite:
No problem, I'll build one today.
[Moto X Android Development] tdhite:
All updated -- see the Downloads Post.

Let me know how it goes.
[Moto X Android Development] CsR0501:
Thank you very much sir! :D... Everything works fine... I'll share my experience soon... :laugh:
[Moto X Android Development] lavero.burgos:
+1 for Faux custom audio modules implementation

Sent from my Moto X powered by Tapatalk
[Moto X Android Development] tdhite:
Updated 09/20/2015

Quick update -- some new kernel commits from the base.

See the Downloads Post.
[Moto X Android Development] Tonystarki:
[MENTION=4988866]tdhite[/MENTION] implement áudio modules in your kernel why not?
[Moto X Android Development] infectedorganism:
Taking into consideration those latest cyanogenmod kernel and rom (cgroups) commits, would you recommend changing to bfq, or sticking with fiops?

Thanks in advance.