[KERNEL][7.x.x][SHAMU] * Simple Kernel * [r2 - 07/05] - Nexus 6 Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​Simple Kernel - Shamu
Simple Kernel is a kernel for Shamu that aims to be just that; a simple kernel. I believe in having too much stuff that really doesn't contribute to a better user experience should not be added into a kernel, and that's the ideology that I built this kernel with. I present Simple Kernel. I hope you enjoy it!
Features:
Sourced from latest Shamu kernel release (nougat-mr-1.5) up to July's security patches.
Upstreamed to 3.10.107 - Thanks to @The Flash for his guide to upstreaming a kernel
Built with vanilla Linaro GCC 7.1.1 - Thanks to The Flash's gcc build tool I used
Upstream F2FS support
LZO Compressed kernel - fast decompression at boot time
Power Suspend power management - Thanks to @faux123 and @Yank555
Hotplugs: Intelliplug v4.0 & Mako Hotplug + Stock - Thanks to faux123 and @franciscofranco
CPU governors: Nightmare & ElementalX + Stock - Thanks to @Alucard24 and @flar2
I/O Schedulers: Zen & Row(just enabled it) + Stock - Thanks to @bbedward
Intellithermal v3 - configurable thermal management - Thanks to faux123 Adjustable max temp for stock thermal monitor - Thanks to franciscofranco
Simple GPU Algorithm - configurable way to improve stock msm_adreno_tz governor - Thanks to faux123
KCAL Color Control - Thanks to @savoca
Zen-Tune v4.5 - improves overall responsiveness - Thanks to @frap129
Power Efficient Work queues - can save some battery - Thanks to neilbrown
Disabled BCL (for now, was causing me issues)
No force-encrypt or dm-verity
Safe GCC Optimization flags for Shamu - (-O2, -mtune=cortex-a15, -marm, -mfpu=neon-vfp4, -pipe)
Some misc fixes and stuff here and there
No excess/magical optimizations or patches
Look at my commit log for full list for everything in the kernel
Changelog:
Just look at commit log. Make it easy.
Installation:
Download latest build
If on another kernel, flash your ROM's (or stock) boot img in TWRP Recovery. If coming from Simple Kernel, proceed to step 3.
Flash kernel in recovery
Wipe Cache/Dalvik-Cache
Reboot
Done
FAQ:
Q: There was a random reboot or some other issue! What do I do?
A: Pull logs, send them to me. Address issues publicly in thread so everyone can benefit/chip in.
Q: Can you add XYZ feature/patch?
A: Perhaps I can. I am always open to adding things, as long as it maintains the soul of the kernel. Giving me a place to find it also helps. You can also create a pull request on Github if you have the commits.
Q: How do I pull a log that you asked for?
A: I use (play store, free) Kernel Adiutor to pull logs. In KA, go to Settings -> Debugging -> Driver Message & -> Last kmsg. Send me the txt files created in /sdcard. Not doing this when bringing up an issue will result in loss of my support and is not good practice when asking for help.
Q: What is F2FS? How do I convert to it?
A: Googling will do you well, this gives a good overview of what is is. This thread might help you decide if it's right for you. Read my instructions in my TWRP w/F2FS thread to see basic conversion instructions.
Disclaimer:
I am not responsible for anything that happens to your device. Period.
External Thanks:
designapp.io for the logo
Download:
See second post
XDA:DevDB Information
Simple Kernel, Kernel for the Nexus 6
Contributors
Black_Hat01, Contributors listed by-contibution
Source Code: https://github.com/BlackHat01/SimpleKernel-Shamu
Kernel Special Features: F2FS, Linaro Compiled - Smooth, Simple & Stable
Version Information
Status: Stable
Current Stable Version: r2
Stable Release Date: 2017-07-05
Created 2017-07-02
Last Updated 2017-07-05

---

Download
Download latest build - r2

---

So far so good...
With six ROM 3.9
"Sent from the Dog Pound"

---

cujo6801 said:
So far so good...
With six ROM 3.9
"Sent from the Dog Pound"
Click to expand...
Click to collapse
Good to know :good:

---

Cool thanks
Sent from my Nexus 6 using Tapatalk

---

About the LZO compressed kernel, I was under the impression that the boot would be faster if the kernel wasn't compressed at all. I don't know how large the uncompressed kernel is, but since it gets decompressed at boot anyway, perhaps it'd be better to just have it uncompressed to begin with?

---

espionage724 said:
About the LZO compressed kernel, I was under the impression that the boot would be faster if the kernel wasn't compressed at all. I don't know how large the uncompressed kernel is, but since it gets decompressed at boot anyway, perhaps it'd be better to just have it uncompressed to begin with?
Click to expand...
Click to collapse
An uncompressed kernel image would probably boot faster in our case since our CPU/RAM is fast enough to handle an operation as such. Only issue however is the uncompressed kernel sizes in at about 20 mb in our case, and is too large for our device's boot partition (I think around 16 mb), and won't be able to be installed to the device at all, producing an error saying the image is larger than the boot partition.
EDIT:
Also by "faster", I am comparing it to other popular compression methods such as xz.

---

Build r2 live
Build r2 is live with minor changes. Here's an overview of what's changed:
- Reverted Intellithermal and replaced it with franco's max temp tuner due to stability issues
- Merged latest July security patches from google
Happy flashing!

---

Black_Hat01 said:
An uncompressed kernel image would probably boot faster in our case since our CPU/RAM is fast enough to handle an operation as such. Only issue however is the uncompressed kernel sizes in at about 20 mb in our case, and is too large for our device's boot partition (I think around 16 mb), and won't be able to be installed to the device at all, producing an error saying the image is larger than the boot partition.
EDIT:
Also by "faster", I am comparing it to other popular compression methods such as xz.
Click to expand...
Click to collapse
LZO is going to be the best available. Also, Intellithermal is outdated. I would stay away from it. May I ask what issues you had with BCl. I always had it disabled in my kernel, I believe it to be the cause of early shutdowns that people report (especially when the power draw it too much).

---

apophis9283 said:
Also, Intellithermal is outdated. I would stay away from it.
Click to expand...
Click to collapse
Agreed. I decided to just give it a shot because I wanted to see if I could add some more options for as far as thermal drivers goes but it just doesn't do anything better than stock thermal throttling + Franco's userspace temperature adjustment patch, and like you said, was not updated since it's initial port to qcom devices by faux. Decided to squash it from here out.
apophis9283 said:
May I ask what issues you had with BCl. I always had it disabled in my kernel, I believe it to be the cause of early shutdowns that people report (especially when the power draw it too much).
Click to expand...
Click to collapse
This is actually a good point. I believe as of now, I will bring it back in the near future. I had some rebooting issues, and I *thought* BCL was the cause, but it now seems it is due to RQ Affinity (still working on getting it ironed out). Once I figure out the real cause of my very sparse reboots, I will most likely bring it back, as the upsides seem to outweigh its seemingly negatives(never really figured these out ), especially with Franco's BCL modifications.

---

Black_Hat01 said:
Agreed. I decided to just give it a shot because I wanted to see if I could add some more options for as far as thermal drivers goes but it just doesn't do anything better than stock thermal throttling + Franco's userspace temperature adjustment patch, and like you said, was not updated since it's initial port to qcom devices by faux. Decided to squash it from here out.
This is actually a good point. I believe as of now, I will bring it back in the near future. I had some rebooting issues, and I *thought* BCL was the cause, but it now seems it is due to RQ Affinity (still working on getting it ironed out). Once I figure out the real cause of my very sparse reboots, I will most likely bring it back, as the upsides seem to outweigh its seemingly negatives(never really figured these out ), especially with Franco's BCL modifications.
Click to expand...
Click to collapse
I had a toggle for BCL on mine. My source for it is since lost but that may have been added when Yoinx was part of my team. I had it off by default but people could toggle it on. Do you have it set to off? (RQ Affinity)? I started this on my PC but Ill upload screenshot of what I have going on.

---

Screenshots

---

apophis9283 said:
I had a toggle for BCL on mine. My source for it is since lost but that may have been added when Yoinx was part of my team. I had it off by default but people could toggle it on. Do you have it set to off? (RQ Affinity)? I started this on my PC but Ill upload screenshot of what I have going on.
Click to expand...
Click to collapse
I seem to not run into any rebooting with it set to 0 (so off). A BCL toggle would be great. If I could get that into my kernel that will guarantee BCL's return.
EDIT:
Looking at your setup, mine is quite similar, except of course the BCL switches. And currently affinity at 0 for testing.

---

Black_Hat01 said:
I seem to not run into any rebooting with it set to 0 (so off). A BCL toggle would be great. If I could get that into my kernel that will guarantee BCL's return.
Click to expand...
Click to collapse
This is blackbird kernels source with some of my commits and Ill link you to really old source of my kernel that Yoinx had. I had bad issues setting that to 0. Use RQ Affinity 1 and see if they don't stop. Trust me, I made a kernel for this device for the longest time. If there was a mistake to make I made it. Over a year, 2 version of Android. M and N. If you want..... Get me a log at the next reboot and I would be happy to help
https://github.com/B14CKB1RD-Kernel...2a3c94a/drivers/power/battery_current_limit.c
https://github.com/yoinx/Singularit...a36e6e1/drivers/power/battery_current_limit.c

---

apophis9283 said:
This is blackbird kernels source with some of my commits and Ill link you to really old source of my kernel that Yoinx had. I had bad issues setting that to 0. Use RQ Affinity 1 and see if they don't stop. Trust me, I made a kernel for this device for the longest time. If there was a mistake to make I made it. Over a year, 2 version of Android. M and N. If you want..... Get me a log at the next reboot and I would be happy to help
Click to expand...
Click to collapse
Almost laughed. Got a reboot while reading this. Anyways, I appreciate your willingness to help. Not by any means an expert here, and still new at making use of my own logs, so I'll take all I can get. Here's my kmsg from last reboot. This was with affinity 0, so affinity is ruled out as the cause of the reboots at least (had them with 1 too)
apophis9283 said:
https://github.com/B14CKB1RD-Kernel...2a3c94a/drivers/power/battery_current_limit.c
https://github.com/yoinx/Singularit...a36e6e1/drivers/power/battery_current_limit.c
Click to expand...
Click to collapse
Thank you so much for this. Will look into it tomorrow when I get on my PC.
EDIT:
Heading off to bed in a bit. Got work and classes tomorrow. Will read what you have to say in the morning. Thank you again.

---

Black_Hat01 said:
Almost laughed. Got a reboot while reading this. Anyways, I appreciate your willingness to help. Not by any means an expert here, and still new at making use of my own logs, so I'll take all I can get. Here's my kmsg from last reboot. This was with affinity 0, so affinity is ruled out as the cause of the reboots at least (had them with 1 too)
Thank you so much for this. Will look into it tomorrow when I get on my PC.
EDIT:
Heading off to bed in a bit. Got work and classes tomorrow. Will read what you have to say in the morning. Thank you again.
Click to expand...
Click to collapse
Im gonna look at it in a second. In the mean time here is my BCL file
Edit: Do the reboots only happen when using certain apps? I expected to see a watchdog bite for IRQ and I didnt.

---

apophis9283 said:
Im gonna look at it in a second. In the mean time here is my BCL file
Edit: Do the reboots only happen when using certain apps? I expected to see a watchdog bite for IRQ and I didnt.
Click to expand...
Click to collapse
Thanks. They seem to random, however, the apps that I can remember reboots occuring in are FX File Explorer, Clash of Clans(yes I play this ancient game), Google Camera(video), XDA Labs, and once while suspended.

---

Black_Hat01 said:
Thanks. They seem to random, however, the apps that I can remember reboots occuring in are FX File Explorer, Clash of Clans(yes I play this ancient game), Google Camera(video), XDA Labs, and once while suspended.
Click to expand...
Click to collapse
Try RQ Affinity value = 1. If not I have another idea

---

apophis9283 said:
Try RQ Affinity value = 1. If not I have another idea
Click to expand...
Click to collapse
Actually have been doing that since last night, alongside switching to Mako plug. No reboots with heavy usage this morning.
EDIT:
Guess the culprit would be intelli plug

---

Black_Hat01 said:
Actually have been doing that since last night, alongside switching to Mako plug. No reboots with heavy usage this morning.
Click to expand...
Click to collapse
Feel free to PM me if you need anything.