Related
I compiled CM11 with latest sources but it doesn't boot.
I did breakfast bacon and add TheMuppets prop. files repo, sync repos again. Bacon zip doesn't boot... The same build for Ville - it boots!
I am on latest TWRP. I don't know what I am missing.
Anyone?
Sent from Oneplus One
I resolved this. I synced Oneplus TheMuppets repo but I didn't sync oppo repo, too.
Sent from Oneplus One
mikronac.ns said:
I resolved this. I synced Oneplus TheMuppets repo but I didn't sync oppo repo, too.
Sent from Oneplus One
Click to expand...
Click to collapse
Are there pretty easy directions to follow for building CM11? I tried to follow this:
http://forum.xda-developers.com/oneplus-one/general/guide-building-lollipop-oneplus-one-t2947949
Except changing cm-12.0 to cm-11.0 and it did not work. Any tips?
Introduction
Hello all, I am bringing you this thread as a jumping off point to compiling kernels and working with upstream Linux. I will include a guide, some links, and some terms that will help you get started with modifying kernel source. This is also a good reference point for existing developers as I have consolidated all upstream patches into one repo. Let's get down into it!
What in the world is upstream Linux?
When an OEM sets up a device, they will pick a stable longterm branch from the Linux kernel to base their modifications around (drivers and such). In the case of Bullhead, they picked 3.10.73. Currently, the Linux kernel's 3.10 is updated to 3.10.105, as you can see on kernel.org. This means that Google is "missing" versions 3.10.74 to 3.10.105. Now, why does this matter? Well, the way that the Linux kernel runs its stable branches, the only things that get merged into there are bug fixes and security updates. That's it, there are no wonky features or unstable patches. The only way you get a patch into a stable branch is by having it be in the mainline branch first. Some developers have an aversion to adding upstream because they claim it is excessive and not necessary and they are partially right since not all the patches that come in are relevant to our architecture (arm64). However, upstream Linux is not unstable and by adding each version one at a time, you can verify this. I found only two patches between 3.10.73 and 3.10.105 that gave me issues and it is easy enough to either fix/revert them. Being up to date is good since you keep yourself protected from bugs and security issues that crop up. Google has been better about doing this lately with their monthly security updates but it never hurts to take matters into your own hands.
I suggest watching one of these talks given by Greg Kroah-Hartman, it is really interesting to see how the process goes:
https://www.youtube.com/watch?v=SPY0LyTU53w | https://www.youtube.com/watch?v=L2SED6sewRw
What did you do?
All I did was fetch the latest kernel.org patches from here and cherry pick them on top of the latest kernel source from Google.
I merge these patches by cherry-picking each version individually (3.10.73 to 3.10.74, 3.10.74 to 3.10.75, etc), that way I can verify that the kernel compiles fine and that there are no merge conflicts. Google will sometimes pick certain commits from upstream that are of a higher importance than others which can result in conflicts if you try to pick it again. Additionally, upstream might fix a bug one way and Google has done it another (which is not really good, Google should be pushing their fixes back to upstream so everything stays in sync).
What do I do with this?
I have created two repos below: one with the latest N security update branch with the latest upstream patches picked up on top of it (the bullhead-upstream branch) and another one with a plain AnyKernel source for you to modify (bullhead-stock is the most basic, bullhead-decrypt contains an fstab file that will disable both forced encryption and dm-verity). You are free to fork these or base other branches on them, that's the whole point of this post. I have verified that all the patches contain no major detectable issues. I would like some credit if you do use it but it's not required since the kernel is licensed under GPL Another reason I offer this is I have seen a lot of developers picking in upstream in patch sets, so you get one single commit for an upstream version. This is detrimental as you start to add your own patches as you cannot fully tell what was modified and for what reason without the individual commits. It might look cleaner but you don't get full history which hurts you in the long run.
Links
Kernel source: https://github.com/nathanchance/bullhead/tree/upstream-7.1.2
AnyKernel source: https://github.com/nathanchance/AnyKernel2/tree/bullhead-stock-decrypt
Toolchain source: https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/
How to compile
This will be a quick, step by step guide on how to compile this kernel from source. By using this process, you can start to make modifications to the kernel source and make a flashable zip.
Clone the kernel source, the AnyKernel source, and toolchain source
Code:
cd ~
mkdir Kernel && cd Kernel
git clone https://github.com/nathanchance/bullhead.git source
git clone https://github.com/nathanchance/AnyKernel2.git anykernel
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9 AOSP-4.9
Explanation:
First command: make sure you are in your home directory (or whatever directory you want to hold the kernel folder we are about to make.
Second command: make a Kernel folder and move into it
Third command: clone the kernel source from my repo into a folder named source
Fourth command: clone the AnyKernel source from my repo into a folder named anykernel
Fifth command: clone the Google 4.9 toolchain into a folder named AOSP-4.9
AnyKernel is the name of the zip we are going to make which allows the kernel to be flashed over any ROM.
A toolchain is a set of compiler tools that allow us to compile the kernel on any computer architecture.
Make sure you are on the correct branches
Code:
cd source && git checkout upstream-7.1.2
cd ../anykernel && git checkout bullhead-stock-decrypt
Explanation:
First command: move into the source directory and checkout the branch "upstream-7.1.2", which has all of the necessary patches in it.
Second command: move into the AnyKernel directory and checkout the branch "bullhead-decrypt". If you don't want to disable forced encryption, use the "bullhead-stock" branch.
Tell the compiler what you are are compiling
Code:
export CROSS_COMPILE=${HOME}/Kernel/AOSP-4.9/bin/aarch64-linux-android-
export ARCH=arm64 && export SUBARCH=arm64
make clean && make mrproper
make bullhead_defconfig
Explanation:
First command: point the compiler to the location of your toolchain. If you have done anything different with the folder locations, you will need to modify the "${HOME}/Kernel/AOSP-4.9" part.
Second command: tell the compiler which architecture we are compiling for. In this case, our device is an arm64 device.
Third command: clean out any compiled files and remove our previous defconfig.
Fourth command: tell the compiler which options we want in the kernel using the bullhead_defconfig.
A defconfig is a file that will tell the compiler which features we want in the kernel. No computer ever uses all of the options in the kernel since there are different drivers for various devices.
Make the kernel!
Code:
make -j$(nproc --all)
Explanation:
make tells the compiler to make the kernel (duh) and the -j$(nproc --all) tells the compiler to use the maximum number of cores your computer has available
Make the AnyKernel zip
Code:
cp -v arch/arm64/boot/Image.gz-dtb ../anykernel/zImage-dtb
cd ../anykernel
zip -r9 stock-upstream.zip * -x README stock-upstream.zip
Explanation:
First command: copies the completed kernel (Image.gz-dtb) into the AnyKernel folder
Second command: moves us into the AnyKernel folder
Third command: makes the zip file (named stock-upstream.zip) in the AnyKernel folder.
If you ever want to do this again, run these commands and go straight to step 3:
Code:
cd source && git clean -fxd && git pull
cd anykernel && git clean -fxd && git pull
NOTE: This thread is aimed to be a breeding ground for kernel development, a place to jump off if you will. I am happy to answer how to questions about building kernels or flashing the one I have provided but this is not supposed to be a general Q&A thread. Please use another thread or create your own in Q&A if you need assistance.
THIS. This is what I've been looking for ever since I bought and rooted my bullhead: an optimized stock kernel. I hope and pray that upstream patches are just the beginning, and later on, you'll have the time and inclination to add more optimizations. I don't care for other features. Just a kernel that works and performs is fine with me. If ever you need a tester for future builds, just give me a shout out and I'll be happy to assist. Thanks for sharing your work, mate.
I'd like to respectfully make a request. Talking a look at your Flash kernel thread and I found the optimizations I was referring to in my post above, namely:
Upstream Linux versions 3.10.74-3.10.103
Updated to the October security patch
Patches for some CVEs
Upstream patches from CAF and Linux
Compiled with the Linaro 6.2 toolchain, compiled regularly from Uber's source?*here
Makefile optimizations
Forced encryption and dm-verity disabled
If you can add these to the stock kernel, I'm pretty sure you'll find a user base for this setup (aside from me, of course). I'm sure a lot old timers like myself would a appreciate something that they can use right out of the box and not have to tinker with too much to get a good performance.
apatal said:
I'd like to respectfully make a request. Talking a look at your Flash kernel thread and I found the optimizations I was referring to in my post above, namely:
Upstream Linux versions 3.10.74-3.10.103
Updated to the October security patch
Patches for some CVEs
Upstream patches from CAF and Linux
Compiled with the Linaro 6.2 toolchain, compiled regularly from Uber's source?*here
Makefile optimizations
Forced encryption and dm-verity disabled
If you can add these to the stock kernel, I'm pretty sure you'll find a user base for this setup (aside from me, of course). I'm sure a lot old timers like myself would a appreciate something that they can use right out of the box and not have to tinker with too much to get a good performance.
Click to expand...
Click to collapse
This kernel is not meant to have anything other than the upstream Linux stuff, that's why it is labelled as reference. The only reason I include a kernel here at all is to prove that the additions are stable and cause no side effects. If you want those things, you can compile the kernel yourself (I can show you which patches and toolchain you would need).
Sent from my Nexus 6P using XDA Labs
The Flash said:
This kernel is not meant to have anything other than the upstream Linux stuff, that's why it is labelled as reference. The only reason I include a kernel here at all is to prove that the additions are stable and cause no side effects. If you want those things, you can compile the kernel yourself (I can show you which patches and toolchain you would need).
Click to expand...
Click to collapse
Noted with thanks! Great! When I get the time and resources to build my own kernel, I'll come back here for some pointers.
Btw, I saw a thread here about making your own ROM in the cloud. Is that something you can do as well for making a kernel?
apatal said:
Noted with thanks! Great! When I get the time and resources to build my own kernel, I'll come back here for some pointers.
Btw, I saw a thread here about making your own ROM in the cloud. Is that something you can do as well for making a kernel?
Click to expand...
Click to collapse
Definitely, I do all my building on a server.
The Flash said:
Definitely, I do all my building on a server.
Click to expand...
Click to collapse
Thanks! I'll take a look at it and see if I can figure it out.
Github and the kernel in the OP are updated to 3.10.104.
The Flash said:
Github and the kernel in the OP are updated to 3.10.104.
Click to expand...
Click to collapse
I supposed because of the upstream patch, third kernel already has the Dirty Cow fix, correct?
apatal said:
I supposed because of the upstream patch, third kernel already has the Dirty Cow fix, correct?
Click to expand...
Click to collapse
Yes.
Hi...Sir @The Flash,
This third command is Making FlashableZip?
OR
Non-FlashableZip?
•••
ZawZaw said:
Hi...Sir @The Flash,
This third command is Making FlashableZip?
OR
Non-FlashableZip?
•••
Click to expand...
Click to collapse
Flashable zip
The Flash said:
Flashable zip
Click to expand...
Click to collapse
Thanks Sir. :good:
3.10.105 released https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?id=refs/tags/v3.10.105
Sent from my Nexus 5X using XDA-Developers Legacy app
tuhinxp04 said:
3.10.105 released https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?id=refs/tags/v3.10.105
Click to expand...
Click to collapse
I am aware. I'm not actually doing this for this device anymore so there won't be an update.
Hi... @The Flash
I have one question, please reply me.
What is UBER?
UBER is a compliler as Google's ToolChain Prebuilt?
What different UBER and Google Toolchain?
I want to know,
Please explain me.
Thanks You Sir
•••
ZawZaw said:
Hi... @The Flash
I have one question, please reply me.
What is UBER?
UBER is a compliler as Google's ToolChain Prebuilt?
What different UBER and Google Toolchain?
I want to know,
Please explain me.
Thanks You Sir
•••
Click to expand...
Click to collapse
https://plus.google.com/+ChetKener/posts/YzMJEkzPQgp
The Flash said:
https://plus.google.com/+ChetKener/posts/YzMJEkzPQgp
Click to expand...
Click to collapse
Thanks You Sir.
•••
Hey @The Flash I've been reading through your "How to build Pure Nexus" thread and this thread and I believe that I have an understanding of how to properly setup an environment and compile a kernel for use. However, I still need some guidance as to how to pull commits from others sources and merge them into mine so that my kernel will have those features. The main features I want for my kernel are: LZ4 ramdisk compression (as seen in jollaman's and rachanta's kernels), F2FS compatibility, Overclocking for both the big and little clusters, and a kernel tick rate of 100Hz. If it is not too much to ask could you please show me an example of how to merge at least one of these features into my source so that when I compile my kernel it will have the feature?
HesThatGuy said:
Hey @The Flash I've been reading through your "How to build Pure Nexus" thread and this thread and I believe that I have an understanding of how to properly setup an environment and compile a kernel for use. However, I still need some guidance as to how to pull commits from others sources and merge them into mine so that my kernel will have those features. The main features I want for my kernel are: LZ4 ramdisk compression (as seen in jollaman's and rachanta's kernels), F2FS compatibility, Overclocking for both the big and little clusters, and a kernel tick rate of 100Hz. If it is not too much to ask could you please show me an example of how to merge at least one of these features into my source so that when I compile my kernel it will have the feature?
Click to expand...
Click to collapse
I can do overclocking because it is the easiest of those. Note that you will need some good git skills as well as fairly solid foundation of C to understand what is happening around the code when you run into conflicts.
1. Fetch the repo you want to get changes from (git fetch <url> <branch>)
Code:
git fetch https://github.com/Flash-Kernel/bullhead release-7.1.1
2. Find the commit hash you want to pick on Github and cherry-pick it
Code:
git cherry-pick e60c81d4839bb0f7efd3a79213467e7cbe77801d
3. If there are conflicts, it will make you resolved them first. You'll see conflict markers like so:
Code:
<<<<<<<<<< HEAD
STUFF THAT IS CURRENTLY THERE
==================
STUFF THAT IS EXPECTED TO BE THERE AFTER COMMIT
>>>>>>>>>>>>>
Sometimes, all the stuff that is currently there will be replaced by the stuff that is expected to be there. Other times, you'll have to be more fine about it and compare the diff on Github and see what is actually changing. It's a learned process, not really one that I can concretely teach.
As the title suggests, I am porting lineageOS and keep getting this error
/home/zane/Lineage/out/target/product/suzuran/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by '/home/zane/Lineage/out/target/product/suzuran/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes', missing and no known rule to make it
here is the full log https://paste.myself5.de/JfHg5EA2Je.sql
I have tried re syncing the repo and re downloading the source trees. nothing seems to be fixing this.. :/
Is this problem solved?
How did u solved this issue? @nzzane
Appears I didn't have the right proprietary blobs - and had SonyLOS repo running alongside, the two seemed to clash
So if you are getting this error make sure you have the right vendor files and not two different repos trying to do the same thing
nzzane said:
Appears I didn't have the right proprietary blobs - and had SonyLOS repo running alongside, the two seemed to clash
So if you are getting this error make sure you have the right vendor files and not two different repos trying to do the same thing
Click to expand...
Click to collapse
Sry i didnt get u. What do u mean two different repos?
Sent from my AO5510 using Tapatalk
Raja_12 said:
What do u mean two different repos?
Click to expand...
Click to collapse
If there is a repo named abc at github that supports i.e. FMRadio and another named xyz, that also supports FMRadio, it is neccessary that depending files are coming from the same repo. Actually the repo from LineageOS clashes with the one from SonyLOS and vice versa.
That's, what nzzane wanted to say IMHO...
Yea - so had two different repos conflicting
Lineage repo was trying to build from stock blobs, and SonyLOS repo was trying to build from just device sources (which my device tree wasn't set-up for)
nzzane said:
Yea - so had two different repos conflicting
Lineage repo was trying to build from stock blobs, and SonyLOS repo was trying to build from just device sources (which my device tree wasn't set-up for)
Click to expand...
Click to collapse
I get it. so how to overcome it. Do i have to remove one repo directory. currently im having 3 repos.
Raja_12 said:
I get it. so how to overcome it. Do i have to remove one repo directory. currently im having 3 repos.
Click to expand...
Click to collapse
It depends what each repo does, and how you want to build it (stock blobs or all device tree)
nzzane said:
It depends what each repo does, and how you want to build it (stock blobs or all device tree)
Click to expand...
Click to collapse
all device tree
Raja_12 said:
all device tree
Click to expand...
Click to collapse
Then one of the repos must be conflicting somewhere :S
nzzane said:
Then one of the repos must be conflicting somewhere :S
Click to expand...
Click to collapse
Yea sometimes I can't make clean or clobber. With one repo it works with other it didn't. So I have to maintain only one repo at a time.
I ran into another issue. Can u help
target arm C: audio.primary.msm8916_32 <= hardware/qcom/audio/hal/voice.c
In file included from hardware/qcom/audio/hal/voice.c:32:
hardware/qcom/audio/hal/voice_extn/voice_extn.h:194:71: error: unused parameter 'adev' [-Werror,-Wunused-parameter]
static int voice_extn_compress_voip_set_mic_mute(struct audio_device *adev, bool state __unused)
Sent from my AO5510 using Tapatalk
Introduction
Hello everyone! I am one of the members of the Substratum team and we constantly have people asking how to add support to ROMs. I have made a repo regarding all of our documentation here, in which I include steps to add support. Normally, it is easy to add support to most ROMs; however, Lineage has made some underlying changes to AssetManager and PackageManager that makes adding the patches a little difficult if you do not have some solid programming background. To help people who are familiar with building and git but not necessarily Java and C, I have created a series of reference repos that you can use to cherry pick the commits into your forks or local builds to easily have theme support! Please read this entire thread, I go over a lot of info and I will be upset if you do not read it all enjoy!
Information
Substratum currently uses OMS (Overlay Manager Service), Sony's theming framework, that allows for real time swapping of resources via overlays. This is accomplished through a series of commits, which include the core OMS framework, exposures so themes can overlay hardcoded resources, and a second set of framework commits to allow Substratum to do all of its operations without root access. You can read more about this in the main Substratum thread. We have made it so that it is easy to merge OMS and all of our exposures on AOSP or close to AOSP ROMs. Lineage is not one of those ROMs as they have based on CAF, which modifies AOSP to suit a large range of devices. Lineage has also modified core components like Package Manager for security reasons and some of those changes will conflict with OMS changes. I have merged the changes on top of Lineage and verified everything has worked properly. I will continue to maintain this as long as time permits. I plan to try and rebase the changes every day on Lineage updates but I may need to do it weekly depending on how much free time I have.
What do I have to do?
All you need to do is merge the changes from our repos into yours! Link: https://github.com/LineageOMS
This can be done in one of four ways (ONLY ONE):
1. Cherry-pick our changes
This will be the best option if you have forked Lineage and made any changes (basically basing a ROM on Lineage). Once you have merged these changes, you can track our progress on Gerrit and merge patches as they come down. The patches you need to pick will be either "committed with nathanchance" or "nathanchance committed".
Code:
git fetch <url> cm-14.1
git cherry-pick <first_sha1>^..<second_sha1>
Example:
Code:
git fetch https://github.com/LineageOMS/android_frameworks_base cm-14.1
git cherry-pick d6b3f93bec61769fab7ebf31e78bf0acb42bb2e6^..1e00bba63c5b6facec5a8beef1bb39863b251183
2. Pull our changes
This will be a good option if you have either forked Lineage and made no changes or do straight builds from their repos, as this will fetch and merge automatically. You can still cherry-pick if you want but this should result in no conflicts (basically a clean merge).
Code:
git pull <url> cm-14.1
Example:
Code:
git pull https://github.com/LineageOMS/android_frameworks_base cm-14.1
3. Sync using our manifest
This is good if you are just building straight from Lineage's sources. The one issue with this is you will be fully reliant on me for updates; Lineage often merges patches across a few repos and you may run into errors if ALL repos are not up to date.
From the top of your Lineage repo folder:
Code:
mkdir LineageOMS && cd LineageOMS
repo init -u https://github.com/LineageOMS/android -b cm-14.1 --no-clone-bundle --depth=1
repo sync -j$( nproc --all ) --force-sync -c --no-clone-bundle --no-tags --optimized-fetch --prune
4. Use the provided local manifest
This is good if you are just building straight from Lineage's sources. As with the above option, you MAY run into errors if a patch is merged across several repos and I have not update my repos with the proper changes.
From the top of your Lineage repo folder:
Code:
cd .repo
mkdir -p local_manifests
cd local_manifests
wget https://raw.githubusercontent.com/LineageOMS/local_manifest/master/substratum.xml
cd ../..
repo sync --force-sync
4. Use the provided local manifest
I would only recommend doing this if you are building straight from Lineage's sources and willing to build only when I rebase my changes. Lineage often merges patches across several repos and without every repo being up to date, you may get build errors.
From the top of your Lineage repo folder:
Code:
cd .repo
mkdir -p local_manifests
cd local_manifests
wget https://raw.githubusercontent.com/LineageOMS/local_manifest/master/substratum.xml
cd ../..
repo sync --force-sync
That's it! Super easy as it should be.
Support
If you run into any issues with merging patches, ask in this thread.
If you PM me on XDA... I will ignore you.
If you PM me on Hangouts... I will ignore you.
If you PM me on Telegram... I will ignore you.
See a pattern? This thread is the place for support, nowhere else.
If you run into issues with using Substratum itself, ask in the main thread.
Great!
This is great!
wew...this is great bro
This is great!
Wow, great :laugh:
Awesome!
Awesome, build successfully. Thx.
Finding beautiful themes now.
通过我的 Mi 5s Plus 上的 Tapatalk发言
Great it can't be easier thn this.
Is it possible to do for this build. Can anyone HELP me with video tutorial plz..
---------- Post added at 06:56 AM ---------- Previous post was at 06:41 AM ----------
akhilnarang said:
Great!
Click to expand...
Click to collapse
Iam using HTC desire 816.i have flash this build cm14.1-20161120-unofficial-a5dwg can u plz help me to how to do this.
actually i didn't understand......can anyone explain it in simple words.......am not a tech guy, am just a beginner in this world of custom ROM.
nareshnani142 said:
Is it possible to do for this build. Can anyone HELP me with video tutorial plz..
---------- Post added at 06:56 AM ---------- Previous post was at 06:41 AM ----------
Iam using HTC desire 816.i have flash this build cm14.1-20161120-unofficial-a5dwg can u plz help me to how to do this.
Click to expand...
Click to collapse
You need to build for yourself, you cannot do this to an already compiled build.
Sachin ET said:
actually i didn't understand......can anyone explain it in simple words.......am not a tech guy, am just a beginner in this world of custom ROM.
Click to expand...
Click to collapse
Unfortunately, if you cannot understand what I wrote, you need to do a lot of research into the world of git and custom ROMs, I cannot provide that to you in this thread. A good place to start would be my guide on how to compile from source: https://github.com/nathanchance/Android-Tools/raw/master/Guides/Building_AOSP.txt
I made my own manifest to build lineage with OMS here: https://github.com/DespairFactor/android
@cvxda @xamio
Sachin ET said:
actually i didn't understand......can anyone explain it in simple words.......am not a tech guy, am just a beginner in this world of custom ROM.
Click to expand...
Click to collapse
Bro lets wait our dev will do this for us,,,,
Thanks
[Thanks bro!!]
[¡Gracias, viejo!]
Firstly thanks for this guide. I followed the THIRD way to add Substratum Support in my ROM and I'm getting some error Permissive domains not allowed and the make fails. I am building LineageOS for Moto G4 Plus (athene). Error: https://hastebin.com/keyacadezi.vbs
Full output: https://paste.ee/p/GvyYN Anyone who can help in this, I'd be thankful
Device tree: https://github.com/tywinlannister7/android_device_motorola_athene
Kernel tree: https://github.com/LineageOS/android_kernel_motorola_msm8952
tywinlannister7 said:
Firstly thanks for this guide. I followed the THIRD way to add Substratum Support in my ROM and I'm getting some error Permissive domains not allowed and the make fails. I am building LineageOS for Moto G4 Plus (athene). Error: https://hastebin.com/keyacadezi.vbs
Full output: https://paste.ee/p/GvyYN Anyone who can help in this, I'd be thankful
Device tree: https://github.com/tywinlannister7/android_device_motorola_athene
Kernel tree: https://github.com/LineageOS/android_kernel_motorola_msm8952
Click to expand...
Click to collapse
Delete the file "sepolicy/themeservice_app.te" in your device tree. I removed CMTE's sepolicy as ours conflicts.
dont work with touchwiz roms or?
gtaelbordo said:
dont work with touchwiz roms or?
Click to expand...
Click to collapse
Are TouchWiz ROMs LineageOS? Then no, this is not applicable for TouchWiz ROMs. If you mean Substratum as a whole, probably not as TouchWiz is nowhere close to stock Android and this should be asked in the main Substratum thread.
Sent from my Nexus 6P using XDA Labs
HardcoreKernel for the Nexus 5X
Features
- Based on latest Google Release (April 2018)
- 3.10.108
- Compiled with Linaro 4.9
- Reduced kernel size
- Disable useless debug
- Wireguard support
Download
http://pc.cd/ru77
Kernel Source
https://github.com/HardcoreKernel/bullhead (8.1.0-hardcore13)
Telegram Channel
https://t.me/hardcorekernelchannel
PS:
Can be used as a clean base for creating custom kernels (8.1.0-linux)
Reserved
scafroglia93 said:
HardcoreKernel for the Nexus 5X
Features
- Based on latest Google Release
- 3.10.108
- Compiled with UberTC 4.9
Download
https://goo.gl/ZuiJos
Kernel Source
https://github.com/HardcoreKernel/bullhead
Telegram Channel
https://t.me/hardcorekernelchannel
PS:
Can be used as a clean base for creating custom kernels (8.0.0-linux)
Click to expand...
Click to collapse
3.10.108 ? awesome ! Thanks
What feature also included in this kernel (except the latest security patches from Google, 3.10.108 and UberTC?)?
AFK269 said:
What feature also included in this kernel (except the latest security patches from Google, 3.10.108 and UberTC?)?
Click to expand...
Click to collapse
No at the moment, my main goal is provide a simply kernel for all with the latest upstream made by Linux according to the latest reports made by Kernel Mantainer (Greg and Willy) about upstream lts kernel.
The other goal is to provide third-party developers with a base for creating their own custom kernel starting from a clean base so if you want add another features you can grab my kernel and edit without any problem with the support of latest Kernel LTS version 3.10.108
Edit
It's a simply google + linux
Thanks for this kernel.
Sent from my Nexus 5X using Tapatalk
scafroglia93 said:
No at the moment, my main goal is provide a simply kernel for all with the latest upstream made by Linux according to the latest reports made by Kernel Mantainer (Greg and Willy) about upstream lts kernel.
The other goal is to provide third-party developers with a base for creating their own custom kernel starting from a clean base so if you want add another features you can grab my kernel and edit without any problem with the support of latest Kernel LTS version 3.10.108
Edit
It's a simply google + linux
Click to expand...
Click to collapse
Adding wakelock control should be appreciated!
November's kernel source is available
AFK269 said:
November's kernel source is available
Click to expand...
Click to collapse
I know...
*Update*
HardcoreKernel-bullhead--20171107-1012
- Merge November Security Patch
what conflicts you had when merging upstream linux to base 3.10.73? did you merge or cherry-pick?
Yaznas said:
what conflicts you had when merging upstream linux to base 3.10.73? did you merge or cherry-pick?
Click to expand...
Click to collapse
All cherry-picked, check my source
scafroglia93 said:
*Update*
HardcoreKernel-bullhead--20171107-1012
- Merge November Security Patch
Click to expand...
Click to collapse
Why you don't do a kernel with some features to save battery and other optimisations and tools instead as just publishing the base as you looks like to be really experimented?
francos21 said:
Why you don't do a kernel with some features to save battery and other optimisations and tools instead as just publishing the base as you looks like to be really experimented?
Click to expand...
Click to collapse
Why complain? if you don't want to use it, move along.
francos21 said:
Why you don't do a kernel with some features to save battery and other optimisations and tools instead as just publishing the base as you looks like to be really experimented?
Click to expand...
Click to collapse
It's the same "base" used by Google plus the upstream to latest Linux kernel version.
If you want some features fork my kernel and work on it, it's simply
k4zkispr0xy said:
Why complain? if you don't want to use it, move along.
Click to expand...
Click to collapse
I'm not complaining man, I'm just asking why he don't compile his with useful features because he think that's simple but not really as to begin I don't have an access to linux during the week as my laptop don't support it.
@scafroglia93, Awesomeness! Nice work. ??
francos21 said:
I'm not complaining man, I'm just asking why he don't compile his with useful features because he think that's simple but not really as to begin I don't have an access to linux during the week as my laptop don't support it.
Click to expand...
Click to collapse
UPSTREAM it's the most useful features which you can find in a kernel
I cloned your source to my PC but for some reason the kernel version is 3.10.73 and not the 3.10.108.
AFK269 said:
I cloned your source to my PC but for some reason the kernel version is 3.10.73 and not the 3.10.108.
Click to expand...
Click to collapse
Well, the default branch is 8.0.0-base (1:1 Google) just git checkout 8.0.0-linux and you're okay