I've had zero issues with the EXKM kernel manager since the developer upgraded it for "O" :good:
[ANGLER] [8.0.0] [3.10.107] [GCC 7.2.1] Flash Kernel v3.1
- Thread starter nathanchance
- Start date
- Status
I've had zero issues with the EXKM kernel manager since the developer upgraded it for "O" :good:
@The Flash do i flash magisk before or after flashing your kernel when doing a fresh start after clean wipe?
I didn't get a log but on ABC ROM O version, it flashes and boots but as soon as screen comes on it reboots automatically and that's a repeat process. Can't get it running.
He didn't say before because after doesn't work.
A user asked what flash suggests would be the best way to do it, and he responded with the safest way to not have issues.
I realize there are a lot of places I could ask this question, but since many here have switched to a different file system I figure you guys would have the skinny. I want to know if there is anything outside the SDCARD folder that would need to backed up before a complete wipe. I need to do some surgery on my phone and if it goes south, I wanna have everything I can get off it.
OK, so I am running builds of ABC rom that I am building from source, android O of course. When I flash flash kernel it boots, but as soon as the screen turns on it reboots, like a panic almost. I got the console ramoops for you.
No, there shouldn't be.
I don't actually see any panic, it just says it's going to reboot to the bootloader. Guess I'll look into it when I have time (which I don't have much of).
It does it every single time. I flash kernel, reboot it happens, I cannot get it running, lolo. thanks!
There are some references on the net about some Moto devices getting stuck booting to bootloader instead of system.
There is a parameter switch for fastboot to clear it but I've never seen it referenced on the 6p. Might be the solution but I've never used it so proceed with caution...
Search for fastboot fb_mode_clear
Sent from my Nexus 6P using Tapatalk
There is a parameter switch for fastboot to clear it but I've never seen it referenced on the 6p. Might be the solution but I've never used it so proceed with caution...
Search for fastboot fb_mode_clear
Sent from my Nexus 6P using Tapatalk
I'm also getting with my kernel. I don't think it's kernel related, since flashing other things (ARISE Magnum Opus with magisk compatiblity enabled, specifically) can trigger the same reboot regardless of the kernel I'm using. I haven't had time to pull my own logs yet, but I do know that it's rebooting to recovery for a factory data reset (at least in my case). Currently, I think it's one of Oreos new security features being triggered, and going down to wipe to protect the device. The only hole in my theory is that it doesn't happen with stock Oreo.
EDIT: After scrolling through Franco's thread, I found that his kernel seems to be triggering the same (or similar) behaviour on stock. This hardens my theory that it's a new O security measure, since you and I are using a common kernel base source (your 8.0 base branch
), but Franco isn't, making it less likely to be something in the source.
Last edited:
Hmm... So does that mean if we were on the stock recovery, it'd automatically do a factory reset?I'm also getting with my kernel. I don't think it's kernel related, since flashing other things (ARISE Magnum Opus with magisk compatiblity enabled, specifically) can trigger the same reboot regardless of the kernel I'm using. I haven't had time to pull my own logs yet, but I do know that it's rebooting to recovery for a factory data reset (at least in my case). Currently, I think it's one of Oreos new security features being triggered, and going down to wipe to protect the device. The only hole in my theory is that it doesn't happen with stock Oreo.
EDIT: After scrolling through Franco's thread, I found that his kernel seems to be triggering the same (or similar) behaviour on stock. This hardens my theory that it's a new O security measure, since you and I are using a common kernel base source (your 8.0 base branch
I'm also getting with my kernel. I don't think it's kernel related, since flashing other things (ARISE Magnum Opus with magisk compatiblity enabled, specifically) can trigger the same reboot regardless of the kernel I'm using. I haven't had time to pull my own logs yet, but I do know that it's rebooting to recovery for a factory data reset (at least in my case). Currently, I think it's one of Oreos new security features being triggered, and going down to wipe to protect the device. The only hole in my theory is that it doesn't happen with stock Oreo.
EDIT: After scrolling through Franco's thread, I found that his kernel seems to be triggering the same (or similar) behaviour on stock. This hardens my theory that it's a new O security measure, since you and I are using a common kernel base source (your 8.0 base branch
Sigh lovely... LOL, guess I'll have to try and pull logs myself too. Truth be told, I haven't even flashed stock Oreo yet, I've been too enveloped with OP5 kernel stuff.
hey guys, hope i can ask this question here.
i am using the flash kernel v 3.0 and i am on PN , would like to know why 2 of the cores are off? i use EXKM.
2 cores are offline.
and they do not change/turn back on even when i am changing profiles within the CPU section.
is that just the feature of flash kernel v3.0?
i am using the flash kernel v 3.0 and i am on PN , would like to know why 2 of the cores are off? i use EXKM.
2 cores are offline.
and they do not change/turn back on even when i am changing profiles within the CPU section.
is that just the feature of flash kernel v3.0?
No, sounds like thermal throttling.
Not an issue for me, I include a full fstab, not patching it.
Sent from my OnePlus5 using XDA Labs
- Status
Similar threads
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
198
Introduction
Hello everyone, this is my personal kernel for the Nexus 6P. While I am not a super star kernel developer, I do know my way around it. My philosophy on kernels is pretty simple:
- Follow upstream Linux always
- Stable kernel rules work best
- Security and stability are paramount
- Features will be added only as needed
Thread Rules
- I refuse to acknowledge/respond to bug reports that do not include clear steps to reproduce, a logcat, and a console ramoops (if random rebooting) or a dmesg (any other issues). Follow this guide to do this. More on bug reporting policy here.
- Keep things civil, I do NOT tolerate flaming of any kind.
- OT is allowed.
Features
Here are the major features of the kernel (feel free to explore Github)
- Updated to the latest security patch on the latest Android version (August on Oreo)
- Updated to the latest Linux upstream version (3.10.107)
- Several CVE fixes
- Upstream patches from CAF and Linux
- Touchboost force disabled
- High brightness mode
- KCAL color control
- Adreno Boost
- Wake gestures (sweep2wake, doubletap2wake, sweep2sleep, and camera launch gesture)
- Faux Sound Control with high performance audio
- ZRAM from 3.18
- Maple I/O scheduler
- Wakelock controls
- TCP algorithms: bic, cubic, highspeed, htcp, hybia, illinois, lp, reno, scalable, vegas, veno, westwood (default)
- F2FS support (latest from here)
- Compiled with a Linaro 7.2.1 toolchain built with crosstool-NG (located here).
- Makefile optimizations (courtesy of @adinkwok)
- Forced encryption and dm-verity disabled
- Hides bootloader unlock from SafetyNet (can still fail through other means)
- Flashed with AnyKernel2 (thanks to @osm0sis)
Downloads
8.0.0 (v3.x): https://github.com/nathanchance/angler/releases
Legacy downloads:
Do not mirror my kernels!
Installation
If you are on stock:
If you are on a custom ROM:
Upgrading from one Flash version to the other:
Changelog
Latest post
Kernel: https://github.com/nathanchance/angler/commits/8.0.0-flash
AnyKernel: https://github.com/nathanchance/AnyKernel2-archive/commits/angler-flash-public-8.0.0
Frequently asked questions
1.1 Q: I am having an issue, can you help me?
1.1 A: I am not an amazing kernel developer but I will certainly try my best. First, start by reading the release posts, as I may make note of a particular issue. Also search the thread to see if I have discussed it before. If you see nothing, please provide me with a dmesg/last_kmsg and logcat, your ROM/kernel version, and a detailed description of the issue, following this guide. If I can't reproduce reliably though, I'm not going to fix the issue.
1.2 Q: Can you add xyz feature?
1.2 A: If you link me the commits or tell me what kernel you had the feature in, I can take a look at them. I will not go digging super hard for commits and I will ignore requests that don't include this information. I won't promise that I will merge every request but I will always take it into consideration.
1.3 Q: How do I control the kernel?
1.3 A: I'd recommend using either @flar2's EX Kernel Manager or @Yoinx's Kernel Adiutor-Mod; both are extremely solid and have given me no issues.
1.4 Q: What ROM are you on? What are your settings?
1.4 A: Currently, I am on Dirty Unicorns and my settings are available here
1.5 Q: OMFG MY BATTERY SUXXXX PLS FIX!!!
1.5 A: The kernel doesn't drain any battery, use an app like BetterBatteryStats to figure out what app is screwing with your phone.
Thanks to:
@neobuddy89 for always providing great fixes and being a shining example of a great kernel developer
The various other developers for their patches (@ak, @Buckmarble, @flar2, @franciscofranco, @frap129, @imoseyon, and @Yank555 to name a few)
@osm0sis for AnyKernel2
@DespairFactor for helping me with some kernel compilation issues
@kwoktopus for giving me good advice on Makefile flags and other patches
@kantjer for being a beta tester along the way!
@malybru for my nifty new signature!
@phantom146 for the thread banner and default profile GlassCannon
All of you guys for viewing the thread
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.
Kernel source links
8.0.0: https://github.com/nathanchance/angler/tree/8.0.0-flash
7.1.2: https://github.com/nathanchance/angler/tree/7.1.2-flash
7.1.1: https://github.com/nathanchance/angler/tree/7.1.1-flash
7.0: https://github.com/nathanchance/angler-old/tree/release-7.0
6.0.1: https://github.com/nathanchance/angler-old/tree/release-6.0.1
DISCLAIMER: I openly welcome off topic in my threads. Mods, please do not clean off topic discussion and users, do not complain about off topic discussion here. I may direct you to another thread if it is so suited but I won't have the discussion cleaned. Thank you.
XDA:DevDB Information
Flash Kernel, Kernel for the Huawei Nexus 6P
Contributors
nathanchance
Source Code: https://github.com/nathanchance/angler
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v3.1
Stable Release Date: 2017-09-17
Created 2016-08-11
Last Updated 2019-07-02128IT IS HERE!
DOWNLOAD: http://nchancellor.net/Downloads/Kernels/
Welcome to Flash Kernel 2.0 so to speak; this kernel has been completely rebased from the ground up. I have learned a lot in these past few months about what should and shouldn't be added for the best overall experience. So rather than fix my source in steps, I just decided to start from scratch so to speak. Here's what I did:
- Grabbed kernel source straight from Google fresh
- Picked upstream Linux commits from kernel.org, fixing conflicts again (as I had messed some up before)
- Added known working patches (like governors, I/O schedulers, file systems, and such)
- Went through the remaining patches, evaluating what the patch exactly did, and locating the original source to see if it had been altered
- Left out anything that was not relevant or helpful to our version
- Cleaned up dmesg a ton, by removing spammy logs and warnings that should not have been happening
122Alright guys, I am going to be changing up how I do things around here.
1. Kernels will no longer be versioned as they will become daily, built from my personal branch. What this means for you is that you will get the kernel as I customize it (my custom settings from the OP as well permissive SELinux at boot) and some stuff may or may not be broken.
2. I will no longer be taking bug reports (I will attempt to fix the Android Auto issue as a grandfathered thing). If it works, perfect; if not, it's most likely not a problem for me so I won't care.
3. The thread will be closed for now (my Telegram channel will still be open for chatting and hanging out and the thread may be open eventually).
I have become very worn out checking my threads all the time and maintaining multiple branches so I am going to simplify it. The experience should not change, only the process. Thanks for everything and I will still be around XDA in various capacities, I just don't have the time to continue maintaining the thread as I would like.
Nathan
Updated kernels will be served here (first one will be up in an hour or so): http://nchancellor.net/Kernels/angler/7.1.1/Personal122The end of an era
It's with a heavy heart that I announce the end of Flash Kernel development for the Nexus 6P. I simply do not have the time to support this, DU for the 6P, and Flash Kernel for the OnePlus 5. I didn't want it to come to this but the recent issues with pretty much all custom ROMs has caused me to make this decision. For the record, I don't think these issues are because of the kernel but to eliminate it as a factor, I'd need to rebase the kernel from scratch and there is zero way I'm going to be able to do that. Rather than give you guys false hope or tarnish the kernel's name, I am just going to bow out. Joe Maples is most likely going to continue working on Electron so if you want a good kernel to migrate to, that one is it. However (and I say this having loved my time on the device), I would highly consider upgrading your device. The 810 was really a terrible chip in the long run and either an 821 or 835 device is going to make a HUGE improvement. I can consistently get 5-6 hrs of SOT without any issues on the OnePlus 5; I only did that in the first couple of months with this device. The Pixels (1 and 2), Essential Phone (once they get kernel source released and maybe shore up some camera issues), and the OnePlus 5 are all awesome destinations and should hold up much better than this device.
It was great learning and talking with you guys in here. You're always welcome in Telegram (I will leave this chat open) or in my other threads.
The Flash (Nathan)99Alright this thread is reopened for the time being, I will be revamping the OP here shortly with some new rules for how this thread is going to run.
1. I refuse to accept/respond to bug reports that don't include a logcat, dmesg, and if applicable, a ramoops
2. The kernel will boot with my personal settings (these can be changed after boot by a kernel manager) and while I will try to keep the OP up to date, you will need to read my init script to know for sure what is being set.
3. There will be no changelogs or versions; I will build when I am able to and the changelogs will be my commit lists:
https://github.com/Flash-ROM/kernel_huawei_angler/commits/n7.1.1
https://github.com/Flash-Kernel/AnyKernel2/commits/angler-flash-personal-7.1.1
Other than that, have fun and enjoy the kernel.
