What is a Tachyon?
Wikipedia calls it a "hypothetical" particle that most scientists claim doesn't exist.
That is what this kernel is: A kernel for Treble, something Motorola claims they never will release for our device.
Why upstream?
Well, DirtyUnicorns put it best on G+ : https://plus.google.com/+DirtyUnicornsOfficial/posts/2MpHCwKqh5J
This kernel will stay updated to the latest upstream from Linux-stable tree maintained by @nathanchance on git for msm
What is EAS?
Energy Aware Scheduler is a scheduler that knows how much energy is used on each frequency and how much power it uses to give best power/performance ratio. This kernel is slowly getting updated to the latest EAS patches from Linaro.org. For more information, check the below link.
https://www.linaro.org/blog/energy-aware-scheduling-eas-project/
Features:
Upstream kernel from source
Edits to avoid Safetynet/CTS (If you have root, it will fail signature check inherently without SUhide or Magisk hide)
Built With the Latest Clang for Android with Linaro as the cross compiler
OC GPU (changed 710 MHz to 750 MHz)
Same Adrenoboost tweaks as the Pixel 2 ElementalX kernel.
Wakelock fixes by Boeffla
EAS implementation (still work in progress)
Bugs/Issues:
hit and miss on MotoMods
Download:
Google Drive
Instructions:
Download ZIP to phone
Boot to TWRP.
Flash and follow prompts in Aroma
If you need to flash any GSI zips to boot your GSI, flash them again.
Reflash root if you want root.
Version Information
Status: Beta
Current Stable Version:
Stable Release Date:
Created 2019-02-06
Last Updated 2019-02-06
Source: https://github.com/Uzephi/Nash_AOSP
Git Branch: o9x-tachyon
Compiler: Clang 8.x.x
Cross Compiler: Linaro 7.x
Branch: Android 9.0.y
Kernel Version: 4.4.y
defconfig: nash_defconfig
Credits: @joemossjr - for collaborating and getting this working and debugging w/ me to get the best possible experience for our community. @invisiblek for all the work he's done for our device tree @npjohnson for his work on our device tree. @erfanoabdi for his amazing work getting treble running and his other work on our device.
Thanks and Mentions:
@Lord Boeffla for his wakelock code. @nathanchance for the assistance and amazing guides and keeping msm-8998 up to date with linux-stable @jbats for keeping up to date with linux-stable for me to merge into this kernel.
@flar2 for his work on our chipset, msm8998
All other developers shown in commit history.
(Quoted from Nathan Chance)
A note about donations
Quite a few people have asked to donate to me in the past and I have turned them down. I am not in this for the money, this is my hobby, something I truly enjoy. If you truly want to donate to something (it is not expected in the slightest), I recommend an entity like the Open Source Initiative, the Free Software Foundation, XDA, or any one of the people I have thanked in the OP. Additionally, you are free to copy any and all of my work; the only thing I request is that you not ask for donations as well (though I can't really enforce this lol). Thank you.
Changelog:
08/14/2018:
Initial release
02/06/2019:
Rebase for Pie
EAS Progress:
Schedutil is a form of EAS. I am currently working on fixing it to get it more in line with how smooth EAS runs on the Pixel. (yes, that means Energy Aware has always been in the AOSP kernels, we just never talked about it. Now that I am updating it to the lastest from Linaro, I am being open about it).
Known issues: GSIs don't work.
Hey there Uzephi. This is for the latest 8/14 build of lineage, right? Because after flashing, I'm stuck on the lineage splash screen.
fossiltkm said:
Hey there Uzephi. This is for the latest 8/14 build of lineage, right? Because after flashing, I'm stuck on the lineage splash screen.
Click to expand...
Click to collapse
Apparently the Tamien vibrator changes haven't been merged yet and are still in Gerrit. I am reverting and will release the fixed kernel in about half an hour.
Updated. same Download link, will now work with Lineage Official that released today. (old build worked on test-keys on 0808)
Uzephi said:
)
Click to expand...
Click to collapse
hi mate, so basically this kernel is not for stock rom right?
thanks
ilovemeow said:
hi mate, so basically this kernel is not for stock rom right?
thanks
Click to expand...
Click to collapse
It's only for Treble. The kernel mounts vendor, so even DU won't boot it.
4.4.148 updated, pushed, and uploaded to Drive. No other changes
sorry for my stupidity, but which roms are actually compatible with this kernel?
Debuffer said:
sorry for my stupidity, but which roms are actually compatible with this kernel?
Click to expand...
Click to collapse
Any ROM built for the Z2 force that is treble enabled. Currently running into a no boot with GSI images and working on fixing that. Currently I think that's only Lineage officials built after 08/14. I don't know if DU has gone treble yet.
link updated to 4.4.150. added back CRC as well. Still no verification if that fixed GSI boot issues
anyone else have screen flip recovery issues after flashing this? everytime my recov screen does a 180 no matter if its twrp, lineage rec, etc
jasperbastianrain said:
anyone else have screen flip recovery issues after flashing this? everytime my recov screen does a 180 no matter if its twrp, lineage rec, etc
Click to expand...
Click to collapse
Its a known issue. Stock lineage kernel does this as well. Best thing to do is just boot twrp.
Edit: 4.4.152 merged and Gdrive updated.
4.4.153 has no changes for us. I merged just to be in line with linux-stable but not releasing a build.
Uzephi said:
Its a known issue. Stock lineage kernel does this as well. Best thing to do is just boot twrp.
Edit: 4.4.152 merged and Gdrive updated.
Click to expand...
Click to collapse
I've only had this issue with this kernel, every other kernel I've tried stock or custom have all been able to load twrp correctly. For some reason though I haven't been able to flash any ROMs with the newest twrp, I always have to use 3.2.2.1 official or the 3.2.2.1 for treble.
Updated to 4.4.154. If you are having issues with TWRP, try flashing the installer after the kernel, I haven't had an issue doing it this way.
will this work with Lineage Unofficial builds??
blake .l said:
will this work with Lineage Unofficial builds??
Click to expand...
Click to collapse
Yes
Hi, i want build this rom for my own. But I can't find the right sources on github. on first site is only a link to kernel. The LOS sources aren't available because los isn't supported it.
Could you please tell me where I can find the source for
- device
- device-msn8953-common
- vendor
- vendor-msn8953-common
I have tried a lot sources from github, but always get a lot of errors which I can't solve.
Many thanks
Hi developer, why aren't you telling me where I can find the sources ??
Hello,
I am new to this, and this is my first post. I have tried finding the most suitable place to ask this, please tell me if there is a better place my questions.
I am currently trying to build lineageOS 17.1 for my Xperia Z. I have previously built lineage 15.1, which used to be officially supported, but this is my first time trying myself at an unsupported release.
I have followed the steps on the official build guide up to the the breakfast command step. I know I need to include manifests for the device tree and kernel, and thought I could simply use those made available by lineage from the 15.1 and 16.0 releases, and could add a revision="lineage-xx.x" tag accordingly. I am attaching the .repo/local_manifests/roomservice.xml which I am now using.
My problem: When running the breakfast yuga command I still get an error because it queries the lineage-17.1 branch of the LineageOS github repository. I don't understand why this is happening. isn't the explicit use of the revision="lineage-xx.x" tags in my manifest supposed to tell breakfast to not use the default lineage-17.1 branch? I am including the complete error log bellow (there are other errors there, but now I am more interested in finding a solution to this current problem).
As mentioned in the error log attached, one can set the ROOMSERVICE_BRANCHES environment variable to use other branches as backup, and this would solve the problem, but I don't understand why I should have to use this since I am explicitly mentioning which branch I want to use in my roomservice.xml.
Thank you in advance.
Hi all
I have problem in compiling kernel source for Moto G9 Plus. There are apparently 2 versions of kernel source for Moto G9 Plus. There is one source in this link that 's the stock kernel (company released kernel ver. 4.14.117) and the other source that 's released by the experts community in this link.
I can build the community released kernel source, easily through clang or gcc but I can build the stock kernel neither by clang nor gcc (aosp or my host ubuntu or gcc-linaro versions) and I face with different types of errors consecutively (related to compiler version or configuration and code syntax)!
The main question and ambiguity for me is that if it is possible for a company to release a source code, erroneous and buggy or it can be built with a special compiler config or version or under a specific condition?!
Thanks in advance
Sapper Morton said:
The latest tag is available here:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QPAS30.19-Q3-32-50-5
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QPAS30.19-Q3-32-50-5
github.com
As for the compiling errors; audio drivers, wlan and etc, are not included in that repository, you should included yourself:
https://github.com/MotorolaMobilityLLC/vendor-qcom-opensource-audio-kernel
https://github.com/MotorolaMobilityLLC/vendor-qcom-opensource-wlan-qcacld-3.0
About the Toolchain, you got that right, usually OEMs will use the default compiler that's matching the release tag.
The custom tree you linked in has these and more resolved; not to blame Motorola or Lenovo, but CAF itself, so a learning curve is necessary.
Click to expand...
Click to collapse
Thanks for your help
but now another question is how can we understand which additional source (just like above two other sources you mentioned alongside the original source) is needed when we want to compile a kernel source?
hi
I have compiled stock kernel of Moto G9 Plus (odessa) based on the tutorial on this link successfully. when I replace the stock kernel (in boot.img) with the new compiled one (Image.gz), the phone has no problem in boot process but it's touch screen does not work and I can not login to the OS. can anyone help me to understand the issue and help to fix the problem?
note:
I know 3 commits (1, 2, 3) is needed to solve the issue about working the core kernel (kernel modules not compiled and not integrated with the core) correctly with kernel modules existing inside the OS from before (thanks @erfanoabdi for explanations and the commits!)
deheshjou said:
hi
I have compiled stock kernel of Moto G9 Plus (odessa) based on the tutorial on this link successfully. when I replace the stock kernel (in boot.img) with the new compiled one (Image.gz), the phone has no problem in boot process but it's touch screen does not work and I can not login to the OS. can anyone help me to understand the issue and help to fix the problem?
note:
I know 3 commits (1, 2, 3) is needed to solve the issue about working the core kernel (kernel modules not compiled and not integrated with the core) correctly with kernel modules existing inside the OS from before (thanks @erfanoabdi for explanations and the commits!)
Click to expand...
Click to collapse
Hi, just curious how your kernel worked out? Is there any chance you are planning on sharing your work? This device could really benefit from a good custom kernel for stock sdcardfs A11, and one for asop(A11&A12) roms.
Hey y'all, I've been recently working on a device tree for the X606F (codenamed "achilles6_row_wifi").
I do not have much experience on this topic, so I am essentially doing this blindly, basing it off other's work. I am currently only targeting the X606F, but X606X/V may also be supported.
I am looking for someone to collaborate with, I have an Android build machine ready to test changes. As I saw that Android 12 GSIs boot, I tried to build LineageOS 19.1, but ended up in the usual "black-screen bootloop", I don't know how to debug this so I am looking for someone to help
Link to the tree: https://github.com/UsrBinLuna/device_lenovo_achilles6
Credits
Yahoo-Mike for their recovery tree
Sushrut1101 for DumprX
did u remove the qcom references yet
areallydumbperson said:
did u remove the qcom references yet
Click to expand...
Click to collapse
yes
Hi,
Were you able to make any progress or was it abandoned?
Abandoned OP hasn't done any commits in ages