[KERNEL][NPD90G] big-bum - almost stock - Nexus 6 Android Development

DOWNLOAD: here if you want to try it out.
HISTORY:
I've wanted to have the stock kernel stability and fixes from upstream. No fancy scheduelers, no fancy governors or other unorthodox modifications that could endanger the stability of the kernel, so this kernel was born.
FEATURES:
- stock google kernel (3.10.40) on which I applied the upstream 3.10.y patches, but only the things that our phone is using (WIP).
- there are also a few fixes from CM, flar2, franciscofranco that are cherry-picked from their repos. (This is where the + in the version comes from. And also because I was lazy to edit the build script to remove it)
- built with Linaro GCC 4.9.4 from @Christopher83. I choose 4.9.4 and not GCC5 or GCC6 since Gentoo which is known to be a bleeding edge distro doesn't consider GCC5 as stable. I've chosen Linaro because I tested a lot of other toolchains back in the days when I had my Nexus 5 and Linaro always felt better.
It's built with Linaro GCC4.9.3 with support for LTO. The reason for 4.9.y remains.
- the ramdisk is stock, so forceencrypt=yes and you must re-root after flashing this kernel. You can flash over other kernels, since I overwrite the existing ramdisk with the stock one.
INSTALLING:
Code:
adb reboot bootloader
fastboot flash boot boot-n.img
fastboot reboot
or use TWRP to flash the image.
TODO:
- continue patching. I currently applied only 23 patches. (3.10.40+23=3.10.63) The currently Linux kernel release for 3.10 branch is 3.10.102. I think that I can have 3.10.102 by the end of the month.
- I'm working on a LTOed build. Done.
REQUESTS:
- the only thing that I will add if requested is BFQ. Though BFQ won't work as you think on a mobile phone. See this
- I won't deny requests, but there is a 99% chance that the feature won't be added
Enjoy.
Source: https://github.com/StefanescuCristian/shamu
XDA:DevDB Information
[KERNEL][NPD90G] big-bum - almost stock, Kernel for the Nexus 6
Contributors
big_bum
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.10.63+
Stable Release Date: 2016-08-01
Current Beta Version: 3.10.96-lto
Beta Release Date: 2016-08-13
Created 2016-08-01
Last Updated 2016-08-13

A whole lot of people likes "unencrypted" kernel so you may consider making one for "no force encrypt".

^ I will consider this. I don't like the idea, but I think I can make two separate versions.
Also, new beta release today. I managed to build with LTO and added a few more patches from mainline.

can't wait to try this kernel. i know it's pretty much stock, but this should be good. always wanting to try new kernels and build my own lol. thank you sir

LTO is stable so all the builds from now on will use LTO. I'm thinking on trying some ArchiDroid build flags.
It might be placebo, but I like how the phone feels. Worst case scenario, LTO-ing and/or using other build flags than -O2 doesn't do anything. Best case scenario, we might gain a little performance in some operations.
Anyway, a beta build is available. (3.10.76-lto)

This is only for Android N correct? Abby chance you could release a MM edition?
tApPeD fROM mY nExUs 6

I won't support MM.
You could use this kernel image without ramdisk and put it in a flashable zip which builds the ramdisk on the fly, like ElementalX.
Just rename mm-test-dtb wih the name of the image in the zip and flash.
If it boots, then there's your kernel. If it doesn't, sorry.

Running N Preview 5 and every time I flash any of these imgs through TWRP, it won't boot past the Google logo. Any suggestions?

Do you have any specific modifications? What kernel are you coming from?
Does it get stuck or is it rebooting right after Google logo?
Sent from my VFD 1100 using Tapatalk

big_bum said:
Do you have any specific modifications? What kernel are you coming from?
Does it get stuck or is it rebooting right after Google logo?
Click to expand...
Click to collapse
I'm flashing on Tupac's stock lite DP5. No other mods besides debloating. It gets stuck at the Google logo. Let it sit for about a minute, then manually rebooted.
Sent from my Nexus 6 using XDA Labs

I don't know what modifications were made to that ROM. Can you provide the kernel image from that ROM to see the difference between the ramdisks?
Sent from my Nexus 6 using Tapatalk

big_bum said:
I don't know what modifications were made to that ROM. Can you provide the kernel image from that ROM to see the difference between the ramdisks?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Here is the boot image from tupac's rom. boot.imag
I wanted to ask, any possibility of adding wake gestures and color control?
I'm more interested in the wake gestures since my hardware buttons are not that good.
Thanks

I don't know what the problem might be, sorry.
I wanted to ask, any possibility of adding wake gestures and color control?
Click to expand...
Click to collapse
We alreday have wake gestures from stock, you can activate it with Kernel Adiutor. As for the color control, no.
PS: New beta build is up: 3.10.96

Hi,
Just to clarify: there's no 'no force encrypt'version as yet, yeah?

Will this ROM get ota update?
Sent from my Nexus 6 using XDA-Developers mobile app

Sky88 said:
Will this ROM get ota update?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
This is a kernel, not a rom.

madsurgeon said:
Hi,
Just to clarify: there's no 'no force encrypt'version as yet, yeah?
Click to expand...
Click to collapse
Not yet.
Just wait for Google to release N officially and to update the sources for the kernel and I'll make two kernels.
Sky88 said:
Will this ROM get ota update?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
This is a kernel.
Just wait for Google to release N officially and to update the sources for the kernel and I'll update it too.

Related

[DEV] For CM11 users, here's how you can use AOSP(Non CAF) kernels again

Since CM11 changed to CAF, here's a zip to be able to use AOSP kernels again. There's really only one note to adhere - You MUST use the kernel ramdisk from CM's kernel as there is stuff in there that is needed, so if you just flash a AOSP kernel that is built as a boot.img, IT MAY NOT BOOT. Special Note - For Franco's kernel(and others maybe) all you need is to do is use the CM(or mod his) init.d to get it working properly, using the full CM ramdisk may cause the phone not to sleep(high Android OS usage in battery stats)
Now for those that want to know the specifics, these 10 libs are what control it
Code:
hw/gralloc.default.so
hw/gralloc.msm8974.so
hw/hwcomposer.msm8974.so
hw/memtrack.msm8974.so
libexternal.so
libmemalloc.so
libmemtrack.so
liboverlay.so
libqdutils.so
libqservice.so
This is neat. Haven't tried CM11 yet, but when I do, this will be good.
Sent from my Nexus 5 using Tapatalk
So for a CAF based rom my best bet for running a third party kernel would be to let the rom boot with its ramdisk, flash this fix (Thank you by the way.)
Let that boot,
Then while in recovery flash the custom kernel?
Would it do any justice to unzip the Decaf build, replace the boot.img with a third party kernel boot.img and just flash that in recovery?
Sent from my Nexus 5 using Tapatalk 2
melbourne408 said:
So for a CAF based rom my best bet for running a third party kernel would be to let the rom boot with its ramdisk, flash this fix (Thank you by the way.)
Let that boot,
Then while in recovery flash the custom kernel?
Would it do any justice to unzip the Decaf build, replace the boot.img with a third party kernel boot.img and just flash that in recovery?
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
Well it's not going to boot with 3rd party kernel so you flash the non CAF zip immediately after flashing the nightly. Then flash the custom kernel. Then reboot.
Sent from my Nexus 5 using Tapatalk
Was able to flash elemental kernel on latest cm nightly with this. Works great
Tikerz said:
Well it's not going to boot with 3rd party kernel so you flash the zip immediately after flashing the kernel. Then boot.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Fasho.
Fiddle time tonight!
Sent from my Nexus 5 using Tapatalk 2
melbourne408 said:
Fasho.
Fiddle time tonight!
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
You like to fiddle , your mom told you to stop.
Sent from my Nexus 5 using Tapatalk
unforgivenmercy said:
You like to fiddle , your mom told you to stop.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hahaha you got me.
Saw I, Frankenstein with the family.
Haven't felt my heart race in years. Really enjoyed it. Screw ripened potatoes.
Sent from my Nexus 5 using Tapatalk 2
anyone try with Franco yet?
dmo580 said:
anyone try with Franco yet?
Click to expand...
Click to collapse
Yes, it works. Flash CM11, flash non CAF zip, then last flash the custom kernel. You'll have to do this for each nightly until CM breaks it again.
Sent from my Nexus 5 using Tapatalk
Can someone point me to the source, where was changed to CAF? Thanks.
Tikerz said:
Yes, it works. Flash CM11, flash non CAF zip, then last flash the custom kernel. You'll have to do this for each nightly until CM breaks it again.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Is volume control an issue though? I believe certain apps like Play Music or whatever fail to allow volume to be properly controlled with Franco. I will test now and report back.
Edit: Volume control works but then you lose custom color settings
Any tried this on latest nightly 29/7??
dmo580 said:
Is volume control an issue though? I believe certain apps like Play Music or whatever fail to allow volume to be properly controlled with Franco. I will test now and report back.
Edit: Volume control works but then you lose custom color settings
Click to expand...
Click to collapse
Is this why all my music and alarms were at max volume at all times before?
rockingondrums said:
Is this why all my music and alarms were at max volume at all times before?
Click to expand...
Click to collapse
Are you on Franco? Starting Nightly ~0118 or so, the conflict started due to the audio commits and as a result the volume control for media started spiraling out of control on Franco kernel. I'm not sure about alarms because I already use 6/7 volume which is pretty loud, so 7/7 probably wouldn't be noticeable unless I did a heads up comparison.
But basically, while this non-CAF patch allows you to gain control of the volume back, a lot of Franco kernel features will be broken. Basically CM and Franco commits are in conflict right now, so unless Franco decides to support CM's latest moves or someone cherry picks commits for Franco kernel, it's gonna be hard to get the best of both worlds.
dmo580 said:
Are you on Franco? Starting Nightly ~0118 or so, the conflict started due to the audio commits and as a result the volume control for media started spiraling out of control on Franco kernel. I'm not sure about alarms because I already use 6/7 volume which is pretty loud, so 7/7 probably wouldn't be noticeable unless I did a heads up comparison.
But basically, while this non-CAF patch allows you to gain control of the volume back, a lot of Franco kernel features will be broken. Basically CM and Franco commits are in conflict right now, so unless Franco decides to support CM's latest moves or someone cherry picks commits for Franco kernel, it's gonna be hard to get the best of both worlds.
Click to expand...
Click to collapse
Yeah, I was. I've got an itch to switch (again) anyway. I'm the opposite of you; I always have media at max, but my alarm fades in. It took me a few rude awakenings to figure out why.
rockingondrums said:
Yeah, I was. I've got an itch to switch (again) anyway. I'm the opposite of you; I always have media at max, but my alarm fades in. It took me a few rude awakenings to figure out why.
Click to expand...
Click to collapse
I personally just want color control. To me, features are more important so CM comes first unless there's a very similar AOSP-ROM that offers some key features I need. So I'll try to run CM and just ditch Franco if necessary Thank goodness the colors on the N5 aren't as bad as the stock N4. I just powered on my N4 and almost barfed.
dmo580 said:
I personally just want color control. To me, features are more important so CM comes first unless there's a very similar AOSP-ROM that offers some key features I need. So I'll try to run CM and just ditch Franco if necessary Thank goodness the colors on the N5 aren't as bad as the stock N4. I just powered on my N4 and almost barfed.
Click to expand...
Click to collapse
I just want to get rid of mp decision. BTW, I used this patch with Trinity's latest beta on cm nightly and audio in the alarm stream broke again, as well as torch.
One thing you can't do is just can't flash whatever kernel you want when it's built as a boot.img onto a ROM like CM, as the ramdisk for CM & AOSP are different, so you will have issues. To get them to work, decompile it, see if the kernel has specific kernel related changes in the ramdisk, decompile a CM kernel and pull the CM ramdisk, mod the ramdisk with the changes of the kernel that you want and rebuild the boot.img with the CM modded ramdisk with the kernel zImage of the kernel you want, that's basically what I do for Franco's kernel that's in my thread, it's Franco's kernel with a CM ramdisk that was modified to include all the changes he usually does.
I haven't really get the point. So if i want to use CM based rom and wanted to use AOSP kernel (non caf) i need to flash the CAF kernel and then flash the non caf zip?
Confused here
Sent from my Nexus 5 using Tapatalk

[Kernel] [3.10.104] WinXkernel [Alpha 0.7] 02/01/17]

After compiling roms for some time now i decided to dabbled in the arts of kernel building and modding.
Ok now i am back and i present you Winxkernel for nougat 7.1.1 stock rom. This time i will be able to continue work and update
this kernel when new sources and patches come out for our device. I have made a new website and I have also created a Google+ community page for this kernel and anything else i decide to work on. please share around. even if you dont like my work, maybe someone else might. i know that i will never be able to create a kernel like the greatest devs eg, yank, nathan, frap and franco, but i will certainly hope to learn from them about anything they have to give and possibly lend a hand.
Here is the download link
XDA:DevDB Information
WinXkernel, Kernel for the Huawei Nexus 6P
Contributors
winxuser
Source Code: https://github.com/winxdroid/kernel_angler
Kernel Special Features:
Version Information
Status: Alpha
Created 2016-08-10
Last Updated 2016-12-30
02/01/17
Update zram, zmalloc and add zpool
updated adreno gpu drivers
added ardreno idler
http://winxdroid.byethost8.com/Nexus-6p.html
30/12/16:
updated linaro to 6.2
added BFQ
couple interactive patches
exfat support
fsync on/off support
latest patches from 3.10 common branch
updated ICE driver
16/12/16:
upstream to latest f2fs updates for 3.10
add saftey net bootloader check (doesnt work with december security patch )
franco sound control
live display driver
removed maple
fixed kcal ( you can now change settings )
01/12/16
add msmhotplug
KCAL driver
fiops scheduler
maple scheduler
f2fs data and cache support
30/11/16
Rebased source to clean angler with 3.10.104
A few camera updates from CAF
16/08/16:
Cleaned up source
Added KCAL support
Added F2FS support
updated linaro toolchains
10/08/16:
Used android-msm-angler-3.10-marshmallow-dr1.6-1 as base
Updated to 3.10.102
Used lastest Linaro GCC 6.1 update
i will add the new security patches in for the next build
Thanks bro
Brokerzhang said:
Thanks bro
Click to expand...
Click to collapse
no worries, this kernel will also be in a rom im going to work on
Thanks.
Will it work on DP5?
leots1234 said:
Thanks.
Will it work on DP5?
Click to expand...
Click to collapse
Don't think so. But you could always try,, make sure you backup your boot partition first.
leots1234 said:
Thanks.
Will it work on DP5?
Click to expand...
Click to collapse
A kernel for M will not work on N due to defconfig changes (camera and some sensors will most likely not work).
Added to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
Good job mate. Can't wait to try your rom+kernel combo.:silly:
Will have an update in a couple days, not going to be home and I don't have a remote connection to my computer so I can't do it while I'm not home lol.. I have redone the sources so it shows all commits of changes up to 3.10.102, I will add the vulnerabilities patches for the next version and add f2fs support and kcal driver support
Sent from my Nexus 6P using XDA-Developers mobile app
winxuser said:
Will have an update in a couple days, not going to be home and I don't have a remote connection to my computer so I can't do it while I'm not home lol.. I have redone the sources so it shows all commits of changes up to 3.10.102, I will add the vulnerabilities patches for the next version and add f2fs support and kcal driver support
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
kernel updated guys, if there is anything you want in this kernel let me know and ill try and add it
someone who has my kernel installed, or can quickly install it can you scan for vulnerabilities please, I know I patched one, just need to know the others. I'm not home and won't be for a fair few hours, and I'm currently running N and not M
Sent from my Nexus 6P using XDA-Developers mobile app
Hey winxuser, I see that you have moved on from the i9305. Have fun with the 6p, and N!
P.S. Why were you inactive for so long?
limjh16 said:
Hey winxuser, I see that you have moved on from the i9305. Have fun with the 6p, and N!
P.S. Why were you inactive for so long?
Click to expand...
Click to collapse
Yeah I moved away from the i9305 when my phone stopped working and I got my 6p.. and there wasn't much more I could do, I'm not that great of a developer to have been able to completely fix the radio issue. I know the radio issue is kinda fixed but I think that's a big dirty hack to use cm12.1 as a radio backup for radio to work... I have been active since but no one really needed me anymore over there..
Sent from my Nexus 6P using XDA-Developers mobile app
hey guys im back, after some time of just trying out other things which has made me frustrated hahaha.
so i am back with a new kernel for N dev preview 7.1.1 only, im currently on dev preview 2 and its working well. i have also finally after a long time created a new website for my development, and i have also created a google+ community which is here https://plus.google.com/communities/101442640267768818970
Very nice website. Trying out the nougat build right now.
Can someone please tell me how can I change to f2fs on dp2 ?!
NOTilyass said:
Can someone please tell me how can I change to f2fs on dp2 ?!
Click to expand...
Click to collapse
The New kernel doesn't support f2fs just yet, will add it in to the next version
NOTilyass said:
Can someone please tell me how can I change to f2fs on dp2 ?!
Click to expand...
Click to collapse
F2fs make a difference on the 6P? Only tried it on the OnePlus One.

[ROM] [DISCONTINUED] idprophecy's unofficial optimized LineageOS 15.1 builds

Hello, I've been building LineageOS 15.1 nightlies just for my experimental purposes. After running this for a few weeks, I decided to share it with you guys. Can be used as a daily driver, but it is experimental due to my changes.
FEATURES:
CAUTION: SMOOTHNESS REDEFINED !!!
(The main goal is to bring performance improvements without affecting the battery life)
Snapdragon LLVM Compiler 4.0.14 (target)
The latest Google's Clang (host)
Bleeding edge GCC 7.x toolchain based on UBER (components like gcc, isl, gmp, mpc, mpfr, etc. are always up to date)
Custom externals (mainly from BenzoRoms sources, it is more up to date and optimized)
SQLite, Skia, Libpng, Jemalloc, Bionic, zlib, libjpeg-turbo
Kernel with optimizations, additional tweaks and updates
based on the LineageOS 15.1 kernel, also I suggest to use this, the stock one
UBER-ified JustArchi's ArchiDroid Optimizations (partially because of soong)
O3, Graphite, Strict Aliasing, OpenMP, etc.
SDCLANG LTO implemented and applied on several parts which have impact on performance (won't be that soon, again because of soong)
Patches related to overall responsiveness, smoothness and user experience
A few additional practical settings/tweaks
OTA Updates
Kexec-hardboot patch merged
microG GmsCore should work (not tested)
OMS support with pre-baked Substratum app and ThemeInterfacer
I try to compile builds as soon as there are new updates available using Arch Linux environment (full clobber after previous build)
Everything else is exactly like in the official LineageOS builds.
CHANGELOG:
This ROM is from the biggest part identical with LineageOS since it's been based on it.
If there is some change from non LineageOS side, I will let you know. Otherwise you can check ROM changes in the LineageOS changelog.
BUGS:
Same as on the LineageOS:
DOWNLOADS
MEGA FOLDER (primary)
ANDROID FILE HOST (mirrors, can be delayed)
OpenGApps
INSTALLATION INSTRUCTIONS
Same as for the LineageOS
NOTE: I recommend using the latest TWRP, I personally use one made by Kutep0v, it works just fine.
1. (Optional) Nandroid Backup
2. Be sure you are using a right firmware
3. WIPE OPTIONS
a) Clean flash (if coming from an another ROM or the OFFICIAL LINEAGEOS 15.1 due to a signature)
Factory Reset, Wipe System, Data, Cache, Dalvik
b) Wipe System, Cache, Dalvik (optional, might help in rare situations sometimes)
c) Dirty flash (without wiping anything, just flashing)
4. Flash ROM
5. (Optional) Flash GApps (OpenGApps recommended)
6. (Optional) Flash Custom Kernel (stock is recommended)
7. (Optional) Flash Magisk as a root solution (or something else)
8. Reboot
SOURCES
ROM
KERNEL
LineageOS
NOTE: Please consider before reporting a bug if it is regarded on official LineageOS too or not. Also do not report bugs running mods, some tweaks or custom kernels or I don't know what. Anyway, feel free to PM me in case of question, suggestion, etc. I am willing to help.
Huge thanks to LineageOS, JustArchi, BenzoRom, Flash-ROM, AOSPA, Matssa56, Substratum, Qualcomm, DU, FranciscoFranco, sultanxda, crdroid, PureNexus, los-kenzo, pav2805, shantur, RomHut, Matthew Booth, UBERROMS and to all people who has been reporting bugs, giving me suggestions or just for even small "thank you". Many of features have been added due to requests by you guys (mostly @Gawd). You're part of these builds too!
Stay fab!
P.S. do not call me a dev.
UPCOMING CHANGES/IN TESTING:
- DISCONTINUED
CHANGELOG (from non-LineageOS side)
As of the
19th October 2018
- Update SQLite (3.25.2)
- Update Google Clang (r339409b)
27th September 2018
- Update SQLite (3.25.1)
- Update Google Clang (r339409)
2nd August 2018
- Update libjpeg-turbo (2.0.0)
- Update libpng (1.6.35)
2nd July 2018
- Update SQLite (3.24.0)
28th June 2018
- Stability fix (now for sure)
27th June 2018
- Stability fix (or not)
24th June 2018
- Switch to the newer Snapdragon LLVM Compiler and GCC 7
18th June 2018
- Initial Oreo release
Eta eta eta xd
I've been testing @idprophecy ROM from day one. Well built and looking forward to enhancements and improvements. He's also compiled a 3.10 kernel, that I use with this build.
Mecca EL said:
I've been testing @idprophecy ROM from day one. Well built and looking forward to enhancements and improvements. He's also compiled a 3.10 kernel, that I use with this build.
Click to expand...
Click to collapse
Can you share the kernel? And how is it different from @erorcun's
Thanks.
Gawd said:
Can you share the kernel? And how is it different from @erorcun's
Thanks.
Click to expand...
Click to collapse
Same as from @erorcun. Nothing special changed. Just a few optimizations and compiled using the same toolchain as ROM is compiled in. My builds are in exact MEGA FOLDER in which ROM is. They've been there for really long time (first anykernel builds with ramdisk fixes). I had no time to update it, maybe during this week. (But it is not what this thread is about)
Any chance you'd build the root zip for us?
Sent from my A0001 using Tapatalk
nolsen311 said:
Any chance you'd build the root zip for us?
Click to expand...
Click to collapse
If you mean ROM with re-enabled native LineageOS root, will try to include it in tomorrow nightly.
idprophecy said:
If you mean ROM with re-enabled native LineageOS root, will try to include it in tomorrow nightly.
Click to expand...
Click to collapse
That's exactly what I mean, thank you!
Sent from my A0001 using Tapatalk
Great to see you got a Rom up too. Been working on one myself, PM me if possible.
nolsen311 said:
That's exactly what I mean, thank you!
Click to expand...
Click to collapse
Included in the latest build.
idprophecy said:
Included in latest build.
Click to expand...
Click to collapse
Now that's QUICK
I'm trying to install the idprophecy 20170125 build over official LineageOS 20170123 but in twrp i got this error:
Can't install this package on top of incompatible data.
Please try another package or run a factory reset
Updater process ended with ERROR: 7
Error installing zip file lineage-14.1-20170125-UNOFFICIAL-bacon.zip"
Why is incompatible? Isn't a LineageOS build?
gulp79 said:
I'm trying to install the idprophecy 20170125 build over official LineageOS 20170123 but in twrp i got this error:
Can't install this package on top of incompatible data.
Please try another package or run a factory reset
Updater process ended with ERROR: 7
Error installing zip file lineage-14.1-20170125-UNOFFICIAL-bacon.zip"
Why is incompatible? Isn't a LineageOS build?
Click to expand...
Click to collapse
Most likely a signature error.
Mecca EL said:
Most likely a signature error.
Click to expand...
Click to collapse
There is something i can do to update and avoid the error?
Could be a bad download?
gulp79 said:
I'm trying to install the idprophecy 20170125 build over official LineageOS 20170123 but in twrp i got this error:
Can't install this package on top of incompatible data.
Please try another package or run a factory reset
Updater process ended with ERROR: 7
Error installing zip file lineage-14.1-20170125-UNOFFICIAL-bacon.zip"
Why is incompatible? Isn't a LineageOS build?
Click to expand...
Click to collapse
These are due to the data changes, probably signature, in the "official" lineage builds. Once you switch to the official builds, you'll probably have to stay there unless you want to factory reset.
That's the purpose of the experimental builds posted by lineage, to migrate data. Going backwards is probably not going to work.
Sent from my A0001 using Tapatalk
nolsen311 said:
These are due to the data changes, probably signature, in the "official" lineage builds. Once you switch to the official builds, you'll probably have to stay there unless you want to factory reset.
That's the purpose of the experimental builds posted by lineage, to migrate data. Going backwards is probably not going to work.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Good point, forgot to mention, added to OP.
Awesome speed with your 3.10 kernel, very nice ROM and thx for your work.
OnePlus One - Tapatalk
I have been using your kernel for about 2 days now, and maa..an that is so smooth. I can definitely observe better memory management. Using it with the official LineageOS nightly.
Would have to try this ROM definitely, can't say about it now.
Your 3.10 kernel is lit. ?
Gawd said:
I have been using your kernel for about 2 days now, and maa..an that is so smooth. I can definitely observe better memory management. Using it with the official LineageOS nightly.
Would have to try this ROM definitely, can't say about it now.
Your 3.10 kernel is lit.
Click to expand...
Click to collapse
Which one are you using? Just noticed that linaro 5 is newer than linaro 6...

[KERNEL][8.1.0][3.10.108] HardcoreKernel Nexus 6P

HardcoreKernel for the Nexus 6P
Features
- Based on latest Google Release (May 2018)
- 3.10.108
- Compiled with Linaro 4.9
- Reduced kernel size
- Disable useless debug
- Wireguard support
Download
http://pc.cd/8YL
Kernel Source
https://github.com/HardcoreKernel/angler
Telegram Channel
https://t.me/hardcorekernelchannel
PS:
Can be used as a clean base for creating custom kernels (8.1.0-linux)
Reserved
Always good to see a new kernel on the scene! Only request I have is for f2fs support
Thank you for your contribution to the Nexus 6p / Angler community!
Mrcactuseater said:
Always good to see a new kernel on the scene! Only request I have is for f2fs support
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
Might have been negligence on my part, but I figured if it was made for 8.0, it would work on 8.1.
My phone said it was corrupt and had the red warning triangle and kept bootlooping.
Reflashed boot.img and system.img via fastboot and am back up and running.
Just posting in case anyone else on the 8.1 beta wanted to flash it.
E30Nova said:
Might have been negligence on my part, but I figured if it was made for 8.0, it would work on 8.1.
My phone said it was corrupt and had the red warning triangle and kept bootlooping.
Reflashed boot.img and system.img via fastboot and am back up and running.
Just posting in case anyone else on the 8.1 beta wanted to flash it.
Click to expand...
Click to collapse
This kernel isn't developed for 8.1
I know that now, lol.
No big deal, I didn't lose any data.
*Update*
HardcoreKernel-angler--20171107-1025
- Merge November Security Patch
*Update*
HardcoreKernel-angler--20171206-1452
- Based on 8.1.0
- Merge Linux 3.10.108
HardcoreKernel Channel
https://t.me/hardcorekernelchannel
@scafroglia93 Can you make a version for 4 cores users?
fuadhdmini said:
@scafroglia93 Can you make a version for 4 cores users?
Click to expand...
Click to collapse
I'm very busy with other devices and work but if I find two minutes I try to change
scafroglia93 said:
I'm very busy with other devices and work but if I find two minutes I try to change
Click to expand...
Click to collapse
Thanks! Appreciate!
Added to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
Is this compatible with the 8.1 Dev preview? I don't want to flash stock 8.1 yet because people are having problems with it, but I want a new kernel, lol.
E30Nova said:
Is this compatible with the 8.1 Dev preview? I don't want to flash stock 8.1 yet because people are having problems with it, but I want a new kernel, lol.
Click to expand...
Click to collapse
No it's based on 8.1.0 stable
*Update*
HardcoreKernel-angler--20180105
- AnyKernel2
- Linaro 4.9
- Merge January Security Patch
*Update*
HK-angler-8.1.0-20180206
- Merge February Security Patch
Will I able to tweak with the system with the EX kernel manger app?
I must have a screen calibration.
HeroPlane said:
Will I able to tweak with the system with the EX kernel manger app?
I must have a screen calibration.
Click to expand...
Click to collapse
1- Sure
2- No at this moment but you have the latest patchset from Linux

[KERNEL] [CLANG 7.0] TitanX kernel v3.5

TitanX Kernel​Hi XDA, here is the TitanX standalone kernel, this is my build and version. Joe's is in all of his roms that he compiles.
This kernel is compiled with Clang 7.0 from Dragon TC and GCC 7 linaro
Feature List (to save space): https://docs.google.com/document/d/1tA9uth8Y8yQMliwocKRy2Qx2lJmvk7RiimoCLiASNVs/edit?usp=sharing
Changelog (to save space): https://docs.google.com/document/d/1UvNirSLUZQ2vfP_m8DGf7wp6VCKDDHhU2klDBOOczNw/edit?usp=sharing
Update Schedule
Stable builds will be released every week if possible
I will be making a test build, but it's on a different website linked here
All new kernels posted on kernel.org will be merged in and pushed 24 hours afterwards
Download link
https://drive.google.com/open?id=1-vY5nZoIp-doytF7Yi5nFij2PZLktve4
Sources
https://github.com/TitanOsRom/los_marlin_titanx
Mods, Do not clean this thread, I like any discussion in forums. Feel free to suggest features as needed
Thanks for your work but does this kernel support Android P DP3? Really want to give it a try.
Queentus said:
Thanks for your work but does this kernel support Android P DP3? Really want to give it a try.
Click to expand...
Click to collapse
I believe that it should work, but the official commits are not in the kernel. I have tried it on DP3 and it worked well, give it a go!
do it work on the sailfish too?
Sh0X31 said:
do it work on the sailfish too?
Click to expand...
Click to collapse
Yes it does
The testing branch has been updated and merged with P. Stable version of this will be released on Tuesday. Feel free to check it out on the link in the OP.
Great kernel so far, the GPU OC seems to do wonders (unless it's some other tweaks/mods).
Found one bug, I can't change vibration strength (this is using EX Kernel Manager).
I don't believe vibration control is added, but I will work on it. Also there is a poll to see which kernel base we should use, I am using lineage right now
Delete
Mods, please close this thread as this branch is no longer in development, it is replaced by KingKernel

Categories

Resources