[ANGLER] [8.0.0] [3.10.107] [GCC 7.2.1] Flash Kernel v3.1

Status
Not open for further replies.
Search This thread

nathanchance

Senior Recognized Developer / Contributor
Jul 22, 2015
13,760
50,106
29
Mesa, AZ
nathanchance.dev
So here's an odd one that I am trying to solve, I believe it comes down to the kernel being the issue, but I would like someone to inform me about this thought. I tried downloading Super Mario Run yesterday and wasn't able to. Found out that, if you have root installed it won't allow you to even search for the game in the Play store. So I clean flashed my phone with PureNexus and installed only this kernel. I was able to find the game in the Play store. Installs just fine, but as soon as I try to run it, the game loads up the Nintendo logo and then the game crashes completely back to the home screen. Remember, I don't have any root capabilities installed on the phone. Just this kernel. Is there anything I can do to see if the kernel is the case?

<note>
I know I should try to just install PN clean and try it without any kernel flashing, but I haven't just yet since I was trying to do this late at night last night. So that will be next attempt, but trying to figure out in this particular moment if the kernel may be causing a compatibility issue with the game.
</note>

No, there is nothing about the kernel that could cause that (I hide the real SELinux and verifiedboot status, only two things that can cause SafetyNet to fail on the kernel side). I just loaded it up and it worked fine.
 

CyberpodS2

Senior Member
Mar 27, 2012
2,813
1,240
NE Pennsylvania Boonies
So here's an odd one that I am trying to solve, I believe it comes down to the kernel being the issue, but I would like someone to inform me about this thought. I tried downloading Super Mario Run yesterday and wasn't able to. Found out that, if you have root installed it won't allow you to even search for the game in the Play store. So I clean flashed my phone with PureNexus and installed only this kernel. I was able to find the game in the Play store. Installs just fine, but as soon as I try to run it, the game loads up the Nintendo logo and then the game crashes completely back to the home screen. Remember, I don't have any root capabilities installed on the phone. Just this kernel. Is there anything I can do to see if the kernel is the case?


I know I should try to just install PN clean and try it without any kernel flashing, but I haven't just yet since I was trying to do this late at night last night. So that will be next attempt, but trying to figure out in this particular moment if the kernel may be causing a compatibility issue with the game.
Maybe not a fix in this case but this problem reminded me that some folks don't think to keep a stock kernel (the one that came with the rom you are running) on their phone. In this case you might have flashed it through TWRP and checked to see if it changes the outcome. If you don't know, just unzip the rom you download and copy the kernel.img into a folder named with the rom and build you are running. It certainly has saved me a couple times. Lol

Another advantage to doing this is whenever you switch kernels, you only have to flash back the original instead of dirty flashing the rom. If you have extras flashed into system it saves some time. That's not saying you don't need to back up before flashing anything new... [emoji1]

Sent from my Nexus 6P using XDA-Developers Legacy app
 
  • Like
Reactions: dohzboy

dohzboy

Member
Nov 7, 2014
49
3
Los Angeles
No, there is nothing about the kernel that could cause that (I hide the real SELinux and verifiedboot status, only two things that can cause SafetyNet to fail on the kernel side). I just loaded it up and it worked fine.

Figured out! Sorry for the trouble! It was as someone suggested in the PN thread, bootloader unlocked. So I installed Magisk and ran MagiskHide and it worked just fine.
 

igylan

Senior Member
Jul 15, 2013
453
132
So here's an odd one that I am trying to solve, I believe it comes down to the kernel being the issue, but I would like someone to inform me about this thought. I tried downloading Super Mario Run yesterday and wasn't able to. Found out that, if you have root installed it won't allow you to even search for the game in the Play store. So I clean flashed my phone with PureNexus and installed only this kernel. I was able to find the game in the Play store. Installs just fine, but as soon as I try to run it, the game loads up the Nintendo logo and then the game crashes completely back to the home screen. Remember, I don't have any root capabilities installed on the phone. Just this kernel. Is there anything I can do to see if the kernel is the case?

<note>
I know I should try to just install PN clean and try it without any kernel flashing, but I haven't just yet since I was trying to do this late at night last night. So that will be next attempt, but trying to figure out in this particular moment if the kernel may be causing a compatibility issue with the game.
</note>

It works fine on PN. Try turning off android debugging.
 
  • Like
Reactions: CyberpodS2

TRgamer

Senior Member
Mar 26, 2016
392
203
İstanbul
So here's an odd one that I am trying to solve, I believe it comes down to the kernel being the issue, but I would like someone to inform me about this thought. I tried downloading Super Mario Run yesterday and wasn't able to. Found out that, if you have root installed it won't allow you to even search for the game in the Play store. So I clean flashed my phone with PureNexus and installed only this kernel. I was able to find the game in the Play store. Installs just fine, but as soon as I try to run it, the game loads up the Nintendo logo and then the game crashes completely back to the home screen. Remember, I don't have any root capabilities installed on the phone. Just this kernel. Is there anything I can do to see if the kernel is the case?

<note>
I know I should try to just install PN clean and try it without any kernel flashing, but I haven't just yet since I was trying to do this late at night last night. So that will be next attempt, but trying to figure out in this particular moment if the kernel may be causing a compatibility issue with the game.
</note>
Just update Magisk and start running to rescue the princess :cyclops:
 

HikingMoose

Senior Member
Jun 20, 2011
1,537
534
43
Hey, does anyone follow or use the app Battery Charge Limit?

https://xdaforums.com/showthread.php?t=3557002

I've been using it since finding it probably a month ago. There's a lot of talk in the about some kernels that offer charge controls. Have you ever considered this @theflash? It would be an amazing edition to have charging stop at 80% at the kernel level. Options to limit the amperage and voltage of the charge would also be very, very beneficial to us with our devices that don't have user serviceable batteries.

It's good for thought anyway. Let's see if others are interested.


Sent from my Nexus 6P using Tapatalk
 
  • Like
Reactions: kouss77550

xSilas43

Senior Member
Jun 25, 2013
1,705
1,224
Hey, does anyone follow or use the app Battery Charge Limit?

https://xdaforums.com/showthread.php?t=3557002

I've been using it since finding it probably a month ago. There's a lot of talk in the about some kernels that offer charge controls. Have you ever considered this @theflash? It would be an amazing edition to have charging stop at 80% at the kernel level. Options to limit the amperage and voltage of the charge would also be very, very beneficial to us with our devices that don't have user serviceable batteries.

It's good for thought anyway. Let's see if others are interested.
it seems like this app already does the most of the work. that is a lot of extra work on nathans end when the app does most. there is a mod called xthermal fast charge which increases the charging amps, im sure you could mod that zip to lower it if you really wanted.
 

shadowstep

Senior Moderator / Moderator Committee
Staff member
Jun 6, 2014
6,921
17,347
33
Ambala Cantt
OnePlus 9R
Samsung Galaxy Watch 6
it seems like this app already does the most of the work. that is a lot of extra work on nathans end when the app does most. there is a mod called xthermal fast charge which increases the charging amps, im sure you could mod that zip to lower it if you really wanted.

Yep, that could totally be done without any issues. :)

Btw, @The Flash, damn! Love your new display picture! :cool:
 
  • Like
Reactions: nathanchance

HikingMoose

Senior Member
Jun 20, 2011
1,537
534
43
it seems like this app already does the most of the work. that is a lot of extra work on nathans end when the app does most. there is a mod called xthermal fast charge which increases the charging amps, im sure you could mod that zip to lower it if you really wanted.

Good thinking. I've never used xthermal. I only asked to see if others thought it would be beneficial. I think it would be tremendously beneficial to have control over charging like this at the kernel level instead of running 2 apps to do. But if it's a lot of work, that is fine. It was just a thought. Would help preserve our non user serviceable batteries, at least non serviceable compared to the old days.

I'll check out xthermal, but I've never unpacked an app and made changes to it, we'll see how this goes.
 

shadowstep

Senior Moderator / Moderator Committee
Staff member
Jun 6, 2014
6,921
17,347
33
Ambala Cantt
OnePlus 9R
Samsung Galaxy Watch 6
Good thinking. I've never used xthermal. I only asked to see if others thought it would be beneficial. I think it would be tremendously beneficial to have control over charging like this at the kernel level instead of running 2 apps to do. But if it's a lot of work, that is fine. It was just a thought. Would help preserve our non user serviceable batteries, at least non serviceable compared to the old days.

I'll check out xthermal, but I've never unpacked an app and made changes to it, we'll see how this goes.

It's not an app, it's a flashable zip that modifies the thermal-engine.conf file present in /system/etc/. All you need to do is extract the .conf file from the zip once you download it, make changes to it, replace it in the zip file and flash. Profit! :)

Link to Xthermal's thread, in case needed.
 
  • Like
Reactions: nathanchance

HikingMoose

Senior Member
Jun 20, 2011
1,537
534
43
It's not an app, it's a flashable zip that modifies the thermal-engine.conf file present in /system/etc/. All you need to do is extract the .conf file from the zip once you download it, make changes to it, replace it in the zip file and flash. Profit! :)

Link to Xthermal's thread, in case needed.
I looked into it yesterday and found the numbers he changed. But after usimg accubattery and ampere to test my charging rates, I think I'll stick with what I have. The recommended 0.5 charge rate for us would be 1.72 A, and my Samsung chargers yield 1.45 A. So I'm actually charging a little less than 0.5C. Which is fine by me.

Sent from my GT-N5110 using Tapatalk
 

snoprosledneck88

Senior Member
Nov 18, 2011
352
191
I was always worried about my battery going bad. So I would short charge my phone, never let it get below 30%, and wouldn't use fast chargers. And to be honest I found d it to be a waste of time. Don't get me wrong I'm sure it helps but not enough for the Hassel. I have charge my Nexus 6 and 6p with the factory speed charger and leave it on over night and will use them down to 5 or 10%. Phones get the same battery life as before. I look at it this way. If you only charge to 80% and only let it go down to 30% the you are only using 50% of you battery so in hindsight you might as well have an abused battery that only works to 50% of it's capacity. Charge it up and use it, why make a smart phone a dumb phone. Now if you wanna charge slower I could handle that but all the other nonsense, no thanks
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 198
    UsFSxNO.png

    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
    Hopefully you enjoy :)


    Thread Rules

    1. 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.
    2. Keep things civil, I do NOT tolerate flaming of any kind.
    3. 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:

    7.1.2 (v1.x-v2.x): https://github.com/nathanchance/angler/releases
    7.1.1 (4.x): Main
    7.0 (3.x): Main
    6.0.1 (1.x): Main

    Do not mirror my kernels!


    Installation
    If you are on stock:

    • If you are on the stock kernel: flash the kernel zip and reboot
    • If you are on a custom kernel: flash the stock boot image matching your build number, flash the kernel zip, and reboot
    If you are on a custom ROM:

    • If you are on the kernel that came with your ROM: flash the kernel zip and reboot
    • If you are on a custom kernel: dirty flash your ROM zip, flash the kernel zip, and reboot
    Upgrading from one Flash version to the other:

    Just flash the kernel zip and reboot


    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-02
    128
    IT 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:

    1. Grabbed kernel source straight from Google fresh
    2. Picked upstream Linux commits from kernel.org, fixing conflicts again (as I had messed some up before)
    3. Added known working patches (like governors, I/O schedulers, file systems, and such)
    4. Went through the remaining patches, evaluating what the patch exactly did, and locating the original source to see if it had been altered
    5. Left out anything that was not relevant or helpful to our version
    6. Cleaned up dmesg a ton, by removing spammy logs and warnings that should not have been happening
    At the end, I have a much cleaner and stable kernel. You may notice that some of your favorite features are missing, that's not by accident. The part that got me really down a little bit ago is I felt like this process was going to be a waste. People have so many preconceived notions about kernels, like that they will give so much more battery and performance and it's hard as a developer to shake off those things. I've seen so many people in both this thread and a few others rave about and disparage this kernel for completely subjective and inaccurate reasons. While I don't necessarily care about number of users, it's disheartening to see something that I put out for free without absolutely no expectation of reimbursement get a bad rap. But I've just decided to ignore it or correct it when I can. If someone blames my kernel for their drain, so be it. I do this because I use my kernel myself and I like doing it, I hope you guys can respect that. Also, bug reports are going to change a bit. If I cannot reproduce your issue myself, I'm not going to fix it. Simple as that, I cannot go on wild goose chases for issues I don't experience. Logs will still be required but steps to reproduce will be as well. Anyways, off my soapbox lol, enjoy the kernel guys.
    122
    Alright 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/Personal
    122
    The 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)
    99
    Alright 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.