This is a collection of add-on modules for the stock November 2016 boot image kernel, as found in the latest versions of the CM 12.1 and Fire Nexus roms by @ggow. This started as a personal project to see if I could compile a working kernel module for the PegasusQ CPU governor.
There are now ROM-specific packages depending on whether you are using CM 12.1 or Fire Nexus. So before downloading, check which ROM version and build date you are using to make sure you grab the right package.
Package for ROMs Based on 5.3.2.0 Boot Image
If you are using any of the following CM 12.1 builds:
-2016-11-21
-2016-11-22
OR any of the following Fire Nexus builds:
-24 November 2016
-02 February 2017
Then you need the package for 5.3.2.0 boot image. <--(Link updated as of 6 Feb 2017)
Package for ROMs Based on 5.1.4 Boot Image
If you are using any of the following CM 12.1 builds:
-2016-06-14
-2016-07-10
-2016-08-10
-2016-09-22
-2016-10-21
OR any of the following Fire Nexus builds:
-15 June 2016
-28 July 2016
-12 August 2016
-08 February 2017 (or later)
OR any build of Lineage-12.1
Then you need the package for 5.1.4 boot image. <--(Link updated as of 12 Feb 2017)
Instructions:
Download the correct package for your ROM
Flash in TWRP or FlashFire. (Can be "dirty" flashed; no need to wipe anything)
Use Kernel Adiutor or your favorite kernel tuner to set your desired parameters.
Notes:
If something goes wrong, or if you flash the wrong package and end up with a bootloop, flash this REMOVER zip to disable the script that loads the modules. The REMOVER zip should work on any ROM. I recommend downloading it and copying it to your SD card at the same time you flash the main package so that it's already on the device in the event you need to use it.
The hotplug drivers may need some experimentation to get right. Alucard seems to work pretty well out of the box, but is pretty aggressive. It may cause a lot of lag on games. Thunderplug may have an issue. In my brief test, it seemed to peg one of the cores at 100% continually, but YMMV.
If you find a combination of settings that work well for any of these modules, please let me know so I can consider changing the default tunables.
(Side note: I'm not a developer by any stretch and just did this as a self-challenge. If there are any other specific modules such as governors, hotplug drivers, or schedulers you'd like me to try, let me know. No promises, but we'll see what happens!)
Credits:
ByungChang Cha (for the PegasusQ governor)
@osm0sis (for the AnyKernel2 installer)
Change log
12 February 2017
-Built and started maintaining separate packages, one for Fire Nexus 2/8/17 build and newer, and the other for last CM 12.1 and Fire Nexus pre-2/8/17.
06 February 2017
-Added a bunch of TCP congestion control algorithms (Highspeed, Illinois, Vegas, Yeah, HTCP, LP, Veno, Hybla, Scalable, Westwood)
04 February 2017
-Added Smartmax CPU governor
-Added ThunderX CPU governor
-Added Alucard hotplug driver
-Added Thunderplug hotplug driver
-Added BFQ I/O scheduler
-Added TripNDroid I/O scheduler
-Added ZEN I/O scheduler
02 February 2017
Initial release
Awesome! How's performance and battery comparing to stock?
I wonder if you could make cpu or gpu OC. Or some gpu governor with better perf.
tonibm19 said:
Awesome! How's performance and battery comparing to stock?
Click to expand...
Click to collapse
I'm not sure. It's been a while since I used the Fire on a regular basis (my kids are the main users these days). But with PegasusQ, I noticed ~2% battery drain overnight (8 hours), and it seemed to me to be below average drain when in use with no noticeable performance penalty. Granted, I haven't tested it thoroughly, so I'm interested in comments from others.
tonibm19 said:
I wonder if you could make cpu or gpu OC. Or some gpu governor with better perf.
Click to expand...
Click to collapse
Unfortunately, I don't think overclocking is going to be possible with the locked bootloader. CPU/GPU overclocking requires modifying the kernel drivers and recompiling the kernel, but we can't boot custom kernels with the bootloader locked. Alternative GPU governors might be possible. I don't have the Fire in front of me right now, but is there a GPU tab in Kernel Adiutor?
@theophile2 - Works wonderfully on the Fire Nexus ROM and sticks even after reboot provided using a Kernel Manager. I now have renewed hype for this tablet, lol. This was hugely needed to enhance performance. I see you are planning on adding more governors down the line and I'm looking forward to it! Huge thanks for this advancement!
theophile2 said:
You can download a flashable ZIP here
Click to expand...
Click to collapse
Is there any way to put this into an existing installation w/o re-flashing the rom, i.e. either simply copy it or use FlashFire with just this zip (which exact settings in FlashFire)?
Sorry for this noob question, but I don't want to go through a whole recovery procedure if I get it wrong...
Marsu42 said:
Is there any way to put this into an existing installation w/o re-flashing the rom, i.e. either simply copy it or use FlashFire with just this zip (which exact settings in FlashFire)?
Sorry for this noob question, but I don't want to go through a whole recovery procedure if I get it wrong...
Click to expand...
Click to collapse
1. Select Flash Zip in FlashFire.
2. Select the Zip and flash it.
3. Look for any kernel manager in the Play Store.
4. Change your CPU Governor and set it to boot so it sticks after a device restart.
theophile2 said:
Alternative GPU governors might be possible. I don't have the Fire in front of me right now, but is there a GPU tab in Kernel Adiutor?
Click to expand...
Click to collapse
No, there isn't.
tonibm19 said:
theophile2 said:
I don't have the Fire in front of me right now, but is there a GPU tab in Kernel Adiutor?
Click to expand...
Click to collapse
No, there isn't.
Click to expand...
Click to collapse
There's one in EX Kernel Manager though, but it says "not supported" :-\
nirogu325 said:
1. Select Flash Zip in FlashFire.
2. Select the Zip and flash it.
3. Look for any kernel manager in the Play Store.
4. Change your CPU Governor and set it to boot so it sticks after a device restart.
Click to expand...
Click to collapse
Thanks, after some trial & error I'm now using "No Frills CPU Control" to set it on boot.
Added a bunch more modules and updated the OP with new link. Let me know how it works for you!
theophile2 said:
Added a bunch more modules and updated the OP with new link. Let me know how it works for you!
Click to expand...
Click to collapse
I suggest adding an update date in the thread's title as a heads up to users.
theophile2 said:
-Added BFQ I/O scheduler
Click to expand...
Click to collapse
I have admit when first reading about these replacement modules, it sounded rather nerdy to me, but I'm amazed how much more responsive the device is with pegasusq and bfq.
http://www.alliance-rom.com/wiki/governors-explained/
http://algo.ing.unimo.it/people/paolo/disk_sched/
Let's hope someone takes a week off, tries all possible combinations of these modules and reports back on stability and performance :->
Marsu42 said:
http://www.alliance-rom.com/wiki/governors-explained/
http://algo.ing.unimo.it/people/paolo/disk_sched/
Click to expand...
Click to collapse
Here's another reference link for those interested. This one's very detailed when it comes to schedulers advantages, disadvantages and many other things such as read-ahead: LINK
nirogu325 said:
Here's another reference link for those interested. This one's very detailed when it comes to schedulers advantages, disadvantages and many other things such as read-ahead: LINK
Click to expand...
Click to collapse
Based on that, could we have the ROW scheduler, pretty please with sugar on it :-> ? " It is a good all-round scheduler despite being biased to read operations. Your device may feel more responsive after selecting ROW because it was designed for mobile devices. Older devices may see more of a boost in performance compared to newer devices."
Btw; ZEN hangs my "No Frills CPU Control" app when trying to set it, while the others work fine.
Marsu42 said:
Btw; ZEN hangs my "No Frills CPU Control" app when trying to set it, while the others work fine.
Click to expand...
Click to collapse
ZEN is also force closing EX Kernel Manager here. Something's funny going on with ZEN.
Marsu42 said:
Based on that, could we have the ROW scheduler, pretty please with sugar on it :-> ? " It is a good all-round scheduler despite being biased to read operations. Your device may feel more responsive after selecting ROW because it was designed for mobile devices. Older devices may see more of a boost in performance compared to newer devices."
Click to expand...
Click to collapse
I looked at ROW, but most implementation I've seen require patching the kernel, which we can't do (locked bootloader). I'll keep my eyes out to see if there's an implementation that doesn't require this.
Marsu42 said:
Btw; ZEN hangs my "No Frills CPU Control" app when trying to set it, while the others work fine.
Click to expand...
Click to collapse
Zen works for me with Kernel Adiutor.
In other news, I just upped a new version that adds a new thing to get nerdy about: TCP congestion control algorithms. I've built modules for all the ones in the stock kernel that Amazon stripped out (Highspeed, Illinois, Vegas, Yeah, HTCP, LP, Veno, Hybla, Scalable, and Westwood).
In a nutshell, if you want max download/upload speed with no noticeable latency penalty, switch to Westwood.
BTW, Google submitted a kernel patch a couple of months ago to add a new algorithm they developed. I plan to check that out and see if it will compile against this relatively old kernel (3.10).
BTW, the new version of Fire Nexus uses boot.img from Fire Is 5.1.4, so I don't think this is compatible anymore. Is it?
EDIT: No, it is not. Bootloops.
PorygonZRocks said:
BTW, the new version of Fire Nexus uses boot.img from Fire Is 5.1.4, so I don't think this is compatible anymore. Is it?
EDIT: No, it is not. Bootloops.
Click to expand...
Click to collapse
Yeah I just tested it earlier and had no idea what was wrong :/ that explains it.
PorygonZRocks said:
BTW, the new version of Fire Nexus uses boot.img from Fire Is 5.1.4, so I don't think this is compatible anymore. Is it?
EDIT: No, it is not. Bootloops.
Click to expand...
Click to collapse
Yeah I just tested it earlier and had no idea what was wrong :/ that explains it.
PorygonZRocks said:
BTW, the new version of Fire Nexus uses boot.img from Fire Is 5.1.4, so I don't think this is compatible anymore. Is it?
EDIT: No, it is not. Bootloops.
Click to expand...
Click to collapse
That's odd. Nothing in the zip should be capable of causing a bootloop, even on an incompatible kernel. At worst, it should just "not work."
Related
[Kernel]***[M8] B14CKB1RD AOSP [11/27]***
B14CKB1RD
Kernel for the HTC ONE M8
~THE MOST UP TO DATE KERNEL FOR THE HTC ONE M8! YOUR ANSWER FOR PERFORMANCE AND SECURITY!~
B14CKB1RD is a custom kernel meant for AOSP KitKat based Roms. There are 8 governors and 8 I/O schedulers. It's built with the 4.10 sabermod toolchain and -O3 compiled for best optimizations and performance. It comes fully stable and suitable for what uses you want from your phone. From best battery life to best performance you can find for your phone. As usual happy flashing. Just note I am not responsible if you (the user) messes up your phone. I will always be around to help in any way i can so if any issues arise please feel free to send me a pm or ask in the thread. ABSOLUTELY NO TROLLING, BASHING, OR ARGUING on the post please. Actions will be taken and you will loose my personal support.
How to Install:
1. Boot to recovery
2. Flash Kernel .zip
3. Wipe Cache
4. Wipe Dalvik Cache
5. Reboot to profit
Click to expand...
Click to collapse
Features:
Governors:
Dancedance
Intelliactive
interactive
Ondemand
Optimax
Performance
Smartmax
Wheatley
I/O Schedulers:
Bfq
Cfq
Deadline
Fiops
Noop
Sio
Vr
Zen
TCP Congestion Controls:
Bic
Cubic
Highspeed
Htcp
Hybla
Illinois
Lp
Reno
Scalable
Vegas
Veno
Westwood
Yeah
After Install Instructions:
I personally Prefer the use of Trickster MOD for kernel tuning. if you want to switch to using trickster i recommend removing built in kernel tweaking app if possible. I used rom toolbox's app manager to do so. Trickster can be found on Play Store or on xda. For frequency changes to stick: In Trickster Mod, change to the frequency you want and tap on "Frequency Lock" to enable it and tap on the checkmark at the top right to apply and save
Notes:
Again, if you need any kind of support, do not be afraid to ask politely in this thread! Check back often, as I am patching this kernel on an almost daily basis to continue to update it, I am a stickler for security just as much as performance.
Click to expand...
Click to collapse
Credits & Thanks
@Snuzzo (for teaching me all he knows about kernel and his code used on many devices)
@REV3NT3CH ( for being a great source of support, guidance and inspiration. Also for allowing me to build his famous B14CKB1RD Kernel for our M8)
@savoca (for his work and code used on the m8 and many devices, for helping me with the zip script and for releasing the furnace kernel which I used as my starting point)
@xboxfanj (for his work, code, and answering my [at times silly] questions and sharing fixes with me)
and to any other devs i missed...all your work is very much appreciated. if you feel i should put you on the list let me know via pm and ill do so
XDA:DevDB Information
[Kernel]***[M8] B14CKB1RD AOSP [11/27]***, Kernel for the HTC One (M8)
Contributors
Damacy, REV3NT3CH
Source Code: https://github.com/VanirRezound/B14CKB1RD_kernel_m8
Kernel Special Features:
Linux Kernel 3.4.34 (We are updating the kernel often, we started on 3.4.0
UnderVoltage Control
DoubleTap2Wake
Battery Optimizations
Version Information
Status: Stable
Current Stable Version: 3.4.34
Stable Release Date: 2014-11-20
Created 2014-11-27
Last Updated 2016-08-13
A Special thank you to @jtommyj for the donation!
FAQs:
Q: Damacy, is there an available, up to date features list?
A: Yes there is! @JennyLikesSka' s FULL FRONTAL, uncensored, IN-YOUR-FACE Feature list!
Q: Damacy, do you have a Lollipop version of thsi kernel available?
A: Why yes I do! See the above post!
Q: Damacy, what ROM do you use for your phone and for your testing purposes?
A: I use EXODUS or Vanir, Here is the nightlies folder for EXODUS: http://www.vanir-exodus.from-me.org/exodus/m8/
Here's the nightlies folder for Vanir: http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/m8/
Q: Why do you have 2 different sources posted above?
A: I'm an IT guy by trade, and it comes down to 3 simple rules: BACKUPS, BACKUPS, BACKUPS!
Q: Damacy, why are you updating this once or twice (or more) a day or once a week?
A: I'm working on patching this kernel, and patching can either be really fast in the case of small patches, or large (like 3.4.12) that take much longer.
Q: What numbering system are you using for kernel versions?
A: I use the number of the patch as the number for the kernel version.
Q: Do you test every patch that you post?
A: Yes, I test EVERY patch that I post before I post it. I won't update the kernel with a patch that causes poor performance (In the case of 3.4.28 caused stuttering and made the phone unable to register with the network provider!)
Q: Why haven't you include feature _____ in the kernel?
A: I am slow to add new features to the kernel because patching is my main focus at the moment. @JennyLikesSka is the lovely feature queen! She adds features that she and I both think will add performance tweaks to the kernel.
Q: I hear you repeatedly mention 'patching' the kernel, what IS patching?
A: Patching is the means for updating the files used to compile the B14CKB1RD (Linux) kernel. Usually, patching is pretty quickly done, but in the case of HTC kernel files, this is the exact opposite. HTC removed all of the comments from the kernel files, so most of the patching I have to do manually (i.e. BY HAND! :X)
Q: How many patches ARE there?
A: In the current 3.4.X kernel line, there are a total of 106 patches. (Yes, dems a lotta patches!)
Q: "Do you have changelogs for these patches/updates. ? "
A: Yes I do! On the kernel source, there's a file called "PatchLog.txt" that has a list of the files changed by the patch.
Q: Damacy, this kernel is so bleedingly fast! Is this even legal?
A: Yes it is legal! >
Q: Does this kernel have a Flux Capacitor or TARDIS Framework inside of it?
A: Well, I think that would be best answered by asking Candle Jac
Awesome awesome work dude!! So happy to see a kernel built with the Sabermod toolchain. Keep it up, flawless
Hope you all enjoy it.... I know @Damacy here has spent many weeks, days and hours working on bringing my kernel to you guys. No need to really thank me...he did all the hard work for you guys to have it...with very minimal help from me
'Course, I find this after I jump on the L train!
Sent from my HTC6525LVW using Tapatalk
nice one! only thing i miss, is multi-rom support!
_moelle said:
nice one! only thing i miss, is multi-rom support!
Click to expand...
Click to collapse
this can be easily added
Nice kernel m8....thanks for the drop
Sent from my One M8 using XDA Free mobile app
Thanks for the kernel downloading and going to run it and see what it's all about
OK just flashed and I see that Faux Sound is on V32 do you plan on updating it to the latest v36
One more question just curious about the governor optimax never heard of this one
dandan2980 said:
Thanks for the kernel downloading and going to run it and see what it's all about
OK just flashed and I see that Faux Sound is on V32 do you plan on updating it to the latest v36
One more question just curious about the governor optimax never heard of this one
Click to expand...
Click to collapse
To answer your first question, we will get to it. This is a DevDB board post, so go ahead and request the feature. Kernel patching is my main priority at the moment.
To answer about Optimax... "This is based on ONDEMAND, like almost all governors that have arisen from XDA. It contains some enhancements from LG, particularly to freq boost handling so it will boost to a set level, almost like HTC's governor. It has different tunables to the HTC governor but it behaves pretty similar, the tunables it comes with default are a bit more conservative."
Can this kernel be used on Android L?
TouchscreenLover1 said:
Can this kernel be used on Android L?
Click to expand...
Click to collapse
I haven't tested it on L yet. I'm curious to see if it is.
Nice job, Larry!
xboxfanj said:
Nice job, Larry!
Click to expand...
Click to collapse
Thanks bro!
It IS a task to get it patched, but I've been learning a ton.
Thanks again for your input and putting up with my silly questions.
Thanks for the kernel!
Sent from my One M8 using Tapatalk
Any idea why trickster mod is not giving me the option to undervolt on this kernel? Normally there's a list of all the frequencies and I undervolt from anywhere between 50 and 65. Thx!
Damacy said:
I haven't tested it on L yet. I'm curious to see if it is.
Click to expand...
Click to collapse
Just reporting in, doesn't boot on latest cm12
Sent from my 831C using XDA Free mobile app
Maestertk said:
Just reporting in, doesn't boot on latest cm12
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Thanks. That'll be added on the list of things to add.
Damacy said:
Thanks. That'll be added on the list of things to add.
Click to expand...
Click to collapse
PM sent
I added an FAQ. I hope that this will answer a few of your questions! Not to mention I have followed up with some kernel updates.
Development Goals:
- stability
- energy savings due to more efficient ARM algorithms
- strictly no overclocking unless approved by the manufacturer or my source base integrates it (also, even if my source base integrates it, expect no support for it)
- no undervolting as well unless the manufacturer approves it since it's relatively pointless IMHO...
- all improvements should require MINIMAL user interaction (e.g. you don't need to do anything except flash the kernel or at the very least use SetCPU or the like to set fixed options)
- stability
*note: FAQ is at the 3rd post
Latest Kernel Here
Boot-B -> LBY29G
Boot-O -> LMY47O PH
Boot-M -> LMY47O India
OR
Boot-Universal -> custom recovery flashable zip for all ROMs (I hope :fingers-crossed
*there are significant ramdisk differences between PH and India versions which is weird
20150524_05XX:
- missed something in the previous commit
*this is why I don't like developing kernels on devices I don't use or stopped using actively :/
20150523_21XX:
- implemented minor config changes and a better fix for kernel ooops upon changing CPU governors
20150509_11XX:
- modified proportional frequency allocation algorithm to prefer minimum frequency more
20150503_17XX:
- improved power efficiency of entire kernel
20150426_09XX:
- optimized frequency scaling algorithm to minimize scaling to max during hotplug and under certain situations
20150423_22XX:
- ported one of my Kindle Fire modification which I just remembered could impact performance extremely well
20150417_14XX:
- reverted RCU patch mistakenly committed without dependency which caused RCU slowdown
20150412_20XX:
- numerous backports from linux 4.0 for timer, scheduler and ARM
20150411_21XX:
- numerous backports from linux 4.0 for timer, mutex and slub functionality performance improvements
20150411_18XX:
- kernel tweaks from imoseyon
20150410_17XX:
- timer optimization
20150409_17XX:
- disabled dithering since I think hardware doesn't need it (please report any sign of image degradation)
- now also in flashable zip form (please test as I don't have custom recovery)
20150408_23XX:
- merged Motorola's lowmemorykiller tree improvement
- applied latest ondemand patches to hotplug to improve frequency selection
20150407_14XX:
- recoded some MediaTek modifications with more optimal instructions
- removed more unnecessary kernel options
20150405_19XX:
- removed touch boost as it seems to be unnecessary
- removed some useless logging entries
- adjusted some code that prevented the frequency from being ramped down immediately
20150405_10XX:
- changed default IO scheduler to ROW imported from Lenok source with additional commits due to MediaTek changes
- modified readahead value to 512KB
20150403_16XX:
- bug fix due to incorrect scoping of the touch frequency modification causing excessive use of 747Mhz
20150402_06XX:
- integrated Mali commits by varun
- some minor optimizations
20150331_22XX:
- modified hotplug governor to use ondemand algorithm
- hotplugging now doesn't raise frequency to max before doing a hotplug operation
- touch boost frequency now set to 747Mhz instead of max to lower power consumption
20150329_16XX:
- finished porting all relevant commits from Lenok source to Sprout
- initial full release
- significant changes include:
enabling of full tickless mode
modification of some kernel libraries to use optimized ARM instructions
Disclaimer:
Flash at your own risk.
You can find my other kernels at:
http://intersectraven.euroskank.com/kernels
GitHub is at:
intersectRaven's GitHub
XDA:DevDB Information
intersectRaven's Android One Kernel, Kernel for the OEM Cross Device Development
Contributors
intersectRaven
Kernel Special Features:
Version Information
Status: Testing
Created 2015-04-03
Last Updated 2015-04-02
Special Thanks To:
DooMLoRD - some patches I integrated are from his repo
faux123 - some patches I integrated are from his repo
arter97 - some patches I integrated are from his repo
varun - Mali patches are from his repo and his generic kernel implementation
Other devs I neglected to mention.
FAQ:
1.) How do I flash this on my device?
You could use fastboot, flashify, or flash through recovery using the provided recovery flashable zips.
2.) How do I return to stock kernel?
Use the "fastboot flash boot" command using the stock boot image I provided in another thread here.
3.) Will you be releasing frequent updates?
Right now I don't see anything else needed to improve this kernel as I am quite satisfied with it. You could post suggestions BUT they must have MINIMAL USER INTERACTION or will only seek to enable editing of certain values.
4.) How do you verify that it flashed correctly?
Well, if it booted after fastboot showed the "writing" dialog, then it should be ok already. If you're ultra paranoid that maybe fastboot is lying to you or the NSA doesn't want you to know that it didn't overwrite the stock kernel which contains their secret spy stuff that wants to know how frequently you exercise you could enter the ff. command through adb:
cat /proc/version
and the kernel should show #7 and intersectRaven there together with the date that the kernel was compiled which is what I use to indicate the release.
Reserved 3
which is better thunderzap or yours? thanks
Androidoo said:
which is better thunderzap or yours? thanks
Click to expand...
Click to collapse
I guess it's not right to compare both kernel. Both are awesome, but this kernel are optimized for stock, while ThunderZap are optimized for both CM12.1 and stock.
Will this improve battery life
Sent from my Android One using XDA Free mobile app
Kohul Raj said:
Will this improve battery life
Sent from my Android One using XDA Free mobile app
Click to expand...
Click to collapse
Yes, depends on your usage. I notice a bit of increase in battery life, but that's all depends on your usage.
F4uzan said:
Yes, depends on your usage. I notice a bit of increase in battery life, but that's all depends on your usage.
Click to expand...
Click to collapse
Interesting. What version are you using currently? 20150402_06XX? Can you use the one after that (or the latest one released today) and observe battery life with your typical usage? Might be the bug I introduced due to an improper understanding of what a line was doing.
intersectRaven said:
Interesting. What version are you using currently? 20150402_06XX? Can you use the one after that (or the latest one released today) and observe battery life with your typical usage? Might be the bug I introduced due to an improper understanding of what a line was doing.
Click to expand...
Click to collapse
Sure, I'll try Gotta backup and reflash stock then.
-EDIT : I have flashed it, I'll test it for two days and I'll report the results
F4uzan said:
Sure, I'll try Gotta backup and reflash stock then.
-EDIT : I have flashed it, I'll test it for two days and I'll report the results
Click to expand...
Click to collapse
Thanks! You didn't have to if you're not on stock already so I appreciate it!
I'm happy because android one development is growing now
By the way, i'm in thunderzap kernel, can i flash this directly? or i have to go back to stock kernel then flash this? Thanks..
yonzz said:
I'm happy because android one development is growing now
By the way, i'm in thunderzap kernel, can i flash this directly? or i have to go back to stock kernel then flash this? Thanks..
Click to expand...
Click to collapse
This is for stock ROMs. Doesn't matter if you're using a different kernel, what's important is you're not on CM or any non-AOSP based ROM.
anyone can report the result please ? ?
Sent from my MITO_A10 using xda Forum
mrahmanda said:
anyone can report the result please ?
Sent from my MITO_A10 using xda Forum
Click to expand...
Click to collapse
I have used it for a day, there is a slight improvement in battery life.
Can you add USB OTG support and double tap to wake
stuck after android logo... using O for LBY ... build number LBY25G
acus123 said:
stuck after android logo... using O for LBY ... build number LBY25G
Click to expand...
Click to collapse
That's odd. Did you flash anything else before or is this pure stock Cherry Mobile One?
Way better than stock kernel. Performance has improved and battery drains slowly(Compared to stock kernel). I would prefer this kernel over stock anytime!
Regards.
PS: I would request the developer to make a flashable ZIP next time or can provide as an additional package because it's a bit inconvenient to open up PC and flash via ADB. Anyway, a great work!
I've tested the kernel extensively over few days and I can confirm battery improvements
Mod edit: Thread closed on owner's request!
exNoShadez-EAS Kernel
FEATURES
- Current LTS release -> Linux-3.18.114
- Energy Aware Scheduling
- Schedutil (default Cpu Governor)
- RCU infrastructure backport (with expert mode enabled)
- Cpu-Boost / Input Boosting (enabled by default)
- BINFMT_MISC support (NOT mounted on boot).
- Kernel Hardening/Protection (CopperheadOS/Grsec/Pax Marlin kernel hardening features)
- leds-qpnp: Notification LED control - V1.1c (Boeffla) - Adapted for Marlin
- Binder_rt = My own re-implementation of AOSP Binder that uses rt_mutexes; supporting priority inheritance
- Improved scheduling/determinism for high priority threads/tasks
- Backported Scheduling, Locking and Workqueue subsystem code from Newer Linux kernels.
- Audio Driver enhancements / backports (from Wahoo/Pixel 2)
- Sound/Audio driver Tweaks (bug fixes, scheduling improvements)
- forced Interrupt threading enabled
- Wifi Mac Address Randomization
- WireGuard VPN kernel module support (more info soon)
- KCal Advanced Colour control
- Improved ASLR (in kernel)
- USB Fast Charge
- Wake Gestures
- GCC 6/7+ Fixes
- Built with GCC-8.x-dev
- and more
Contains code from everywhere: Code Aurora, Flar2/Marlin, CopperheadOS, AOSP, Project-EAS, Freak7/Kirisakura, Linaro, Pixel 2 kernel sources, mainline linux and elsewhere. Modifications and backports by me, as well.
BACKGROUND
I wanted a kernel for My Pixel that had 'all of the things', it didn't exist... So I'm working on my own kernel. I try to balance Security/hardening, experimental features with high Performance and battery life. <- not an easy task! ... Some of the security features do come with overhead, but if you use apps that are CPU heavy / processing and/or require low latency - they will perform well (at the cost of chewing some battery life, of course).... Battery life and SOT are very reasonable though.
WARNING / VERY IMPORTANT: This kernel isn't compatible with installing TWRP ~> meaning; you must use the fastboot version of TWRP (used in RAM) , flash the kernel and NOT install TWRP to your system (the kernel is too big for TWRP to co-exist).... This may sound inconvenient, but there are a number of valid reasons to avoid reducing a kernel's size in order to support TWRP installation, in the boot partition.
***Fun facts on this subject below => in the 2nd post: PLEASE READ: to understand my motivation***
TWRP REMOVAL
*To remove TWRP from your system; You need the stock boot.img from your running/current firmware (which is inside of the factory image zips) or use the Nov Stock boot.img provided here. Then it's as simple as flashing the boot.img to wipe TWRP;
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Stock 8.1 July 2018 Boot.img => https://github.com/nine7nine/Apps/raw/master/SailfishStockJulyBoot.img
Now you can proceed with using the TWRP fastboot boot.img to flash my kernel, magisk/supersu or whatever else....
Fastboot twrp boot image => https://dl.twrp.me/sailfish/twrp-3.2.2-0-sailfish.img
WARNING: This shouldn't need to be said, but we did have someone who did this, so I'm adding a sticky/warning here; do NOT EVER re-lock your bootloader after flashing any kind of custom software, kernels, etc to your device - *it will brick your phone*. Meaning you are screwed would need an RMA / replacement device ... everyone in the XDA community should know better, but still; worth mentioning....
IMPORTANT:
Before asking questions; Please read through the thread (starting with the last few pages) - I shouldn't need to be repeatedly answering the same questions over and over again. It's good practice to get into the habit of reading through threads before asking questions in any thread on XDA, as more often then not; you're question has probably been answered. Thanks!
EXNS-EAS KERNEL DOWNLOAD:
JULY 2018 OREO 8.1 RELEASE exNoShades-eas Kernel Flashable zip
https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v2.8.2_f94351f.zip
It is stable, high performance and very responsive...
Important: You will need root; I don't support non-rooted devices && some features require it. I recommend using Magisk; https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 ...
NOTE: Make sure to flash the latest Magisk beta *before* flashing the kernel zip. ...
More Background / Important Notes:
Binder_RT:
My own port and re-implementation of the Binder Kernel Driver; a slightly modified version of The AOSP binder.
Binder_RT uses rt_mutexes as opposed to mutexes for locking in Binder, ion, ashmem, etc... rt_mutexes support priority inheritance and should improve determinism in Binder, speed up IPC, Ion and Ashmem => Allowing applications that require low-latency, tight deadlines, low jitter and deterministic behaviour to perform better ~ This re-implementation is proving to be the great for those types of applications. The goal here is to help ensure that the Kernel and Binder's high priority && time critical threads and tasks are properly prioritized... Example; audio buffers arriving on time / no buffer underruns... *Further development work is planned to research, experiment with and improve Binder_RT.
rt_mutex documentation, for those interested;
https://github.com/nine7nine/Marlin_exns-eas/blob/EXNS_EAS/Documentation/locking/rt-mutex.txt
https://github.com/nine7nine/Marlin_exns-eas/blob/EXNS_EAS/Documentation/locking/rt-mutex-design.txt
CPU-Boost / Input Boosting:
Touch inputs boost CPU frequencies (thus improves performance and responsiveness).
# Cpu-boot / Input boost settings
write /sys/module/cpu_boost/parameters/input_boost_enabled 1
write /sys/module/cpu_boost/parameters/input_boost_freq "0:1363200 1:0 2:1900800 3:0"
write /sys/module/cpu_boost/parameters/input_boost_ms 100
IO/ CPU Governors:
This kernel doesn't include a thousand io/cpu governors. IO-wise; CFQ is the default, but we've got a few in there. chose your poison, but know that the majority of my testing is centered around cfq and deadline. CPU Governor-wise the common Linux CPU governors are there; along with Sched and Schedutil....
Stick with Schedutil - on idle, it draws very little power and in most 'peak performance situations, it should do very well..... I'm getting great battery life, sot and performance.
Managing Kernel Settings:
Get EX Kernel Manager - my original code on github was forked from EX kernel, before rebasing it - but EXKM will give you access to 99% of my kernel's settings.
My 8.1 Kernel Sources: https://github.com/nine7nine/Marlin_exns-eas
Donations via PayPal very much appreciated. I do put a significant amount of energy and time into researching, development, testing / QA and also providing support/help to end-users... It's definitely not mandatory to donate; but If you appreciate the effort, see value or benefits from using my kernel on your device and can afford to; Use the "Donate to me" button or the below link... It makes a big difference. thanks!
https://www.paypal.me/jrdnjhnstn
Why TWRP Installations are NOT supported:
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
(and why I'm not using it!)
Most custom/android kernel devs are using the above configuration in kernel compilation, which is arguably very BAD... I understand that boot partitions are small and the desire to install TWRP to them, thus there is a need to reduce the kernel's size....and yes, this will achieve that - However;
1. SUSE, RedHat, etc (Enterprise linux) disable CONFIG_CC_OPTIMIZE_FOR_SIZE -> it's original use case has proven to be invalid. Even Google (in their own documentation) advise against using this; https://source.android.com/devices/tech/perf/boot-times ....
2. It suppresses useful compiler warnings....
3. As SOCs have become more powerful, google has come to the same conclusion that Enterprise Linux did back in 2012.
4. by turning off CONFIG_CC_OPTIMIZE_FOR_SIZE, we achieve better performance, boot time and better cache utilization.
Clark Williams / Redhat Bugzilla said:
* Cause: CONFIG_CC_OPTIMIZE_FOR_SIZE set with assumption that smaller code would yield hot cache lines and good performance
* Consequence: this config caused gcc to generate jump-to-jump code which causes cache line bouncing, hurting performance
* Fix: turn off CONFIG_CC_OPTIMIZE_FOR_SIZE
* Result:slightly larger kernel but better cache utilization
Click to expand...
Click to collapse
(The Above is quoted from Clark Williams, A Senior Software Architect @ RedHat -> https://bugzilla.redhat.com/show_bug.cgi?id=796297)
I know of no other way to significantly reduce kernel size. Disabling some debugging, unneeded features, etc helps - but not enough.... I am focusing on optimization, using newer builds of GCC/Linaro, performance enhancements, fixing compilation errors, etc, etc -> these things are more important than trying to support TWRP installation. Therefore; I do NOT support installing TWRP....
I like it so far, very good kernel.
Awesome! Always nice to have choices
I've seen you post around that you made x change to your own kernel, glad you finally made it public!
Does it have all of franco's wakelocks blocked by default?
グリッチ said:
Awesome! Always nice to have choices
I've seen you post around that you made x change to your own kernel, glad you finally made it public!
Does it have all of franco's wakelocks blocked by default?
Click to expand...
Click to collapse
hey, it includes franco's wakelocks stuff. I don't think all are blocked, I actually don't touch them in my init rc. ... but some are blocked by default, for sure. can be set by user...
yeah, I've got my kernel to a point now, where it is somewhat unique && is drawing in most of the best features from every custom kernel for the pixel (my opinion). very stable too, thus far. so makes sense to make it public.
it's got the RCU (read copy update) infrastructure from linux-4.9... a ton of core, sched, Walt, etc from linux-4.4+ (specifically, from EAS-Project / msm8998 OP5 - which was painful to backport. wish we didn't have a 3.18 kernel. lol) afaik, it's the only Marlin kernel with Dynamic Stune Boost and aside from CopperheadOS; the only marlin kernel with a subset of the PAX/grsec kernel security enhancements and the Mac randomization... also has all of the audio enhancements from the kernel ur running ?
siheals said:
I like it so far, very good kernel.
Click to expand...
Click to collapse
Hey! thanks for testing it out. let me know how things go, your impressions, etc.
I'll be updating this kernel constantly, so if u end up liking it; you can expect that it will always include security patches, linux LTS incremental patches, etc...
it's my daily driver, so i keep on top of it.
Superb! Thanks for clarifying.
I will give it a run when November update releases cuz I'm lazy >.< but am excited and looking forward to it ^_^
グリッチ said:
Superb! Thanks for clarifying.
I will give it a run when November update releases cuz I'm lazy >.< but am excited and looking forward to it ^_^
Click to expand...
Click to collapse
no probz. As soon as the november updates arrive, i will be adding whatever patches are needed... so expect that to be there...
i also pull from Code Aurora msm-3.18 for 8996, so my kernel gets updates to drivers, core, etc that google hasn't picked up yet.
Just Testing 3.18.79 + latest Code Aurura updates for today ....AND;
re-enabling a hardening feature that I thought was draining battery life (Likely not, was probably another removed patch - that isn't in the current release.)
I'll update the link later on and - on my github; where I link to for downloads; there will be older releases labeled - ie:
exNoShadez_eas.zip (current release / link) will become -> exNoShadez_eas_3.18.78_oct.zip,
when it is replaced by 3.18.79 + other updates / patchwork.... The current release will always be -> exNoShadez_eas.zip
UPDATE:
While I haven't updated exNoShadez_eas.zip link/version, * I have posted a zip with the above changes - I'll be testing it for a while before updating the link because it's hard to gauge battery life without a lot of testing / time spent.... So I would say, if anyone is eager - they can test it, but wait at least 12-24hours from testing the current available release - so you can actually make some sort of real-usage comparision.
link: https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_3.18.79_harden.zip
Glad to see you have posted this man. Setting up a pixel for my friend and as i was browsing the forums noticed you have a lot of good kernel work. Was literally about to PM you a few days ago for your kernel and then happened to see this post today. Can't wait to try it out!
Warrimonk said:
Glad to see you have posted this man. Setting up a pixel for my friend and as i was browsing the forums noticed you have a lot of good kernel work. Was literally about to PM you a few days ago for your kernel and then happened to see this post today. Can't wait to try it out!
Click to expand...
Click to collapse
All good, man.
It only makes sense that I would share my kernel, when I felt it was ready for that - just keep in mind, that for now - I have marked it as Beta / Testing, as it's pretty new (although, aside from the EAS code / Dynamic Stune Boost - the rest has been thoroughly vetted)....
So yeah, give it a run, let me know how things go! thanks
Unsure if I am doing something wrong or not, but when I try to flash your kernel I get an error stating : "New Image larger than boot partition. Aborting...."
EX Kernel flashed fine. Using TWRP 3.1.1-1
Warrimonk said:
Unsure if I am doing something wrong or not, but when I try to flash your kernel I get an error stating : "New Image larger than boot partition. Aborting...."
EX Kernel flashed fine. Using TWRP RC1.
Click to expand...
Click to collapse
Why aren't you using the newest stable version of TWRP?
RC1 = release candidate 1
afaik, latest release is 3.1.1-1 stable for the pixel.... https://dl.twrp.me/sailfish/
Using an old version might be your issue. Update, then try.
nine7nine said:
Why aren't you using the newest stable version of TWRP?
RC1 = release candidate 1
afaik, latest release is 3.1.1-1 stable for the pixel.... https://dl.twrp.me/sailfish/
Using an old version might be your issue. Update, then try.
Click to expand...
Click to collapse
Apparently I am using TWRP3.1.1-1 . The thread was called RC1 So I mistakenly assumes that was still the current version.
Warrimonk said:
Apparently I am using TWRP3.1.1-1 . The thread was called RC1 So I mistakenly assumes that was still the current version.
Click to expand...
Click to collapse
Can confirm this, I'm on 3.1.1-1 too and got this issue.
I'm running 8.0.0 (OPR3.170623.008, Oct 2017) build.
Keasby said:
Can confirm this, I'm on 3.1.1-1 too and got this issue.
I'm running 8.0.0 (OPR3.170623.008, Oct 2017) build.
Click to expand...
Click to collapse
kk. I'll look into this - I (obviously) do not have this problem..... What firmware images do you use?
I'm on Rogers/Canada, maybe the boot partition is a different size on some firmwares (?)....
I can also look at shrinking the boot.img, which could fix it. My boot.img is slightly bigger than the shipped boot.img and I do have an idea on how to shrink it a bit, you'll have to wait until later on for me to look at it though / not home right now.
nine7nine said:
kk. I'll look into this - I (obviously) do not have this problem..... What firmware images do you use?
I'm on Rogers/Canada, maybe the boot partition is a different size on some firmwares (?)....
I can also look at shrinking the boot.img, which could fix it. My boot.img is slightly bigger than the shipped boot.img and I do have an idea on how to shrink it a bit, you'll have to wait until later on for me to look at it though / not home right now.
Click to expand...
Click to collapse
32MB is the boot image max size AFAIK.
nine7nine said:
kk. I'll look into this - I (obviously) do not have this problem..... What firmware images do you use?
I'm on Rogers/Canada, maybe the boot partition is a different size on some firmwares (?)....
I can also look at shrinking the boot.img, which could fix it. My boot.img is slightly bigger than the shipped boot.img and I do have an idea on how to shrink it a bit, you'll have to wait until later on for me to look at it though / not home right now.
Click to expand...
Click to collapse
Maybe it's caused by the image size. Other custom Kernels are sized bout 13mb.
I'm running the Google Stock Build OPR3.170623.008, October 2017.
Hope you can fix it - TIA!
nine7nine said:
kk. I'll look into this - I (obviously) do not have this problem..... What firmware images do you use?
I'm on Rogers/Canada, maybe the boot partition is a different size on some firmwares (?)....
I can also look at shrinking the boot.img, which could fix it. My boot.img is slightly bigger than the shipped boot.img and I do have an idea on how to shrink it a bit, you'll have to wait until later on for me to look at it though / not home right now.
Click to expand...
Click to collapse
Personally I tried on these 2 firmwares:
sailfish-ota-opr3.170623.008
sailfish-ota-opr6.170623.012
The phone was originally a Project Fi device.. if that matters. Dev which firmware and TWRP are you using?
Warrimonk said:
Personally I tried on these 2 firmwares:
sailfish-ota->>>>opr3.170623.008<<<<<
sailfish-ota-opr6.170623.012
The phone was originally a Project Fi device.. if that matters. Dev which firmware and TWRP are you using?
Click to expand...
Click to collapse
I'm using the latest twrp-3.1.1-1 (but and idk if this makes a difference or not), I only use the twrp fastboot img (Ihave ZERO reason to actually install TWRP on my system).... and also, Others have installed and are using my kernel - so it must be a difference in firmwares / boot partition size (or image size)
Keasby said:
Maybe it's caused by the image size. Other custom Kernels are sized bout 13mb.
I'm running the Google Stock Build >>>>>OPR3.170623.008<<<<<, October 2017.
Click to expand...
Click to collapse
So yeah, I'm using a different build **OPR1.170623.027**, Oct 2017, Fi/Canada.... you both are having problems on >>>>>OPR3.170623.008<<<<< ~> Something is different in that build... If you like (and happen to have that image kicking around, you could send me the boot.img and I'll compare it to mine? later on)
I'm thinking it's not the kernel size, although - I do plan on making the kernel smaller on production builds, by reducing a lot of debugging that really isn't needed on a production build (I already have a defconfig for doing so);
What is Pantheon?
A Temple dedicated to all the gods.
That is what this kernel is for: dedication to everyone on the Nash.
Why upstream?
Well, DirtyUnicorns put it best on G+ : https://plus.google.com/+DirtyUnicornsOfficial/posts/2MpHCwKqh5J
This kernel will be updated to the latest Linux-stable within the coming weeks.
Features:
Upstream kernel from source
Edits to avoid Safetynet/CTS (If you have root, it will fail signature check inherently without SUhide or Magisk hide)
Built With the Latest Clang for Android with Linaro as the cross compiler
Over Clock / Under Clock on CPU Frequencies added:
Little CPU: 175 MHz, 230 MHz, 2035 MHz
Big CPU: 175 MHz, 230 MHz, 2476 MHz; 2592 MHz
Slight undervolt (our device is overvolted compared to other msm8998 devices)
UC GPU (added 180 Mhz step for battery savings when web browsing, low GPU usage)
OC GPU (changed 710 MHz to 750 MHz)
Same Adrenoboost tweaks as the Pixel 2 ElementalX kernel.
Wakelock fixes by Boeffla
Bugs/Issues:
hit and miss on MotoMods
Download:
Google Drive
Instructions:
Download ZIP to phone
Boot to TWRP.
Flash and follow prompts in Aroma
Reflash root if you want root.
Version Information
Status: Stale [no longer developed]
Current Stable Version: v2.3
Stale Date: 2018-08-14
Created 2017-11-08
Last Updated 2018-08-13
Source: https://github.com/Uzephi/Nash_AOSP
Git Branch: o8x-caf
Compiler: Clang 7.0.2svn
Cross Compiler: Linaro 4.9
Branch: Android 8.1.y
Kernel Version: 4.4.y
defconfig: nash_defconfig
Credits: @joemossjr - for collaborating and getting this working and debugging w/ me to get the best possible experience for our community. @invisiblek for all the work he's done for our device tree @npjohnson for his work on our device tree. @erfanoabdi for his amazing work getting treble running and his other work on our device.
Thanks and Mentions:
@Lord Boeffla for his wakelock code. @nathanchance for the assistance and amazing guides and keeping msm-8998 up to date with linux-stable @jbats for keeping up to date with linux-stable for me to merge into this kernel.
@flar2 for his work on our chipset, msm8998
All other developers shown in commit history.
(Quoted from Nathan Chance)
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.
Changelog:
Nov 8, 2017
Initial public release
Nov 15, 2017 v1.1
Updated cmdline to get CTS/SafetyNet working without the need of SUhide or Magisk hide.
Upstream to 4.4.76
Nov 22, 2017 v1.2
Put voltages in line with other msm8998
Upstream complete at 4.4.100
Nov 24, 2017 v1.3
Added OC/UC
Added wake lock blocking on redundant wakes.
Built with new toolchain - Linaro 4.9
Upstream to 4.4.102
Dec 17, 2017 v1.4
Added Zen, FIOPS, and SIO i/o schedulers
Replaced current wakelock blocking with Boeffla's cleaner code
Upstream to 4.4.106
March 2, 2018
Initial Alpha release for Oreo Stock
April 2, 2018
Initial Alpha release for AOSP
May 16, 2018
Stable release
June 16, 2018
Added 175 MHz for CPU and added other CPU optimizations.
August 13, 2018
Added Treble Support
Stock kernel for Oreo:
Status: stable.
Source: github.com/uzephi/Nash_Oreo
Download link:Google Drive
....... and so it begins. Oh yeah!
Sent from my Moto Z (2) using Tapatalk
Thank you! A new era starts 2day!
Sent from my Moto Z (2) using Tapatalk
Good job man! Thank you for your hard work. ?
If anyone is like me and just wants the kernel added to stock boot image, let me know and I can provide a boot image that is rooted, you'd do "fastboot boot boot.img" then flash with flashify. This is an awesome temp root method to not modify your stock boot image besides adding the kernel.
If anyone wants twrp with this let me know!
joemossjr said:
If anyone wants twrp with this let me know!
Click to expand...
Click to collapse
Would it be possible to get a TWRP built for the retail/German build posted below in the other thread?
I'd like to try this new kernel, running that stock room with the latest security patch.
Thanks
Amd4life said:
Would it be possible to get a TWRP built for the retail/German build posted below in the other thread?
I'd like to try this new kernel, running that stock room with the latest security patch.
Thanks
Click to expand...
Click to collapse
Its the same kernel it should work.
Sent from my Moto Z (2) using Tapatalk
Amd4life said:
Would it be possible to get a TWRP built for the retail/German build posted below in the other thread?
I'd like to try this new kernel, running that stock room with the latest security patch.
Thanks
Click to expand...
Click to collapse
Just flash the kernel in TWRP and reroot. no need for a new TWRP honestly. The performance and security improvements won't be noticeable in recovery.
Have any CPU governors, I/O schedulers or USB-related stuff been added yet? Our 835 chipset enables native alt displayport support for HDMI output through USB-C port but Lenovo stock kernel disables. Possibly due to conflict with headphone support? Not sure. Screw headphone via USB C, that is too much wear & tear, better to use high quality Bluetooth. Could you re-enable alt displayport output in kernel?
jhofseth said:
Have any CPU governors, I/O schedulers or USB-related stuff been added yet? Our 835 chipset enables native alt displayport support for HDMI output through USB-C port but Lenovo stock kernel disables. Possibly due to conflict with headphone support? Not sure. Screw headphone via USB C, that is too much wear & tear, better to use high quality Bluetooth. Could you re-enable alt displayport output in kernel?
Click to expand...
Click to collapse
OP explains everything. All changes are in OP. Tweaks to performance independent of governor and upstream done. Nothing else yet. Getting the tree to 4.4.97 first as stated in OP.
Android terminal TWRP installer and Pantheon Kernel
Android terminal TWRP installer should work with Pantheon Kernel:
https://forum.xda-developers.com/showpost.php?p=74444025&postcount=156
all credit for TWRP goes to @joemossjr
Uzephi said:
If anyone is like me and just wants the kernel added to stock boot image, let me know and I can provide a boot image that is rooted, you'd do "fastboot boot boot.img" then flash with flashify. This is an awesome temp root method to not modify your stock boot image besides adding the kernel.
Click to expand...
Click to collapse
Are you - or anybody else - able to realize a boot.IMG which, when booted with fastboot boot boot.img, it boots directly on TWRP as they made for Pixels?
It would be *very* useful for tweaking... :silly:
enetec said:
Are you - or anybody else - able to realize a boot.IMG which, when booted with fastboot boot boot.img, it boots directly on TWRP as they made for Pixels?
It would be *very* useful for tweaking... :silly:
Click to expand...
Click to collapse
Yes it will be handy. But is not available for now. And comparing our device every time with pixel is irelevant.the only thing in common are the A/B partitions. Nothing more. And that will come when it will come.
Sent from my Moto Z (2) using Tapatalk
blackwing182 said:
Yes it will be handy. But is not available for now. And comparing our device every time with pixel is irelevant.the only thing in common are the A/B partitions. Nothing more. And that will come when it will come.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Ehi boy, they sell chamomile, do ya know?
And A/B partitions in common with Pixels *are* rilevant since the method used to place recovery in boot.img is *exactly the same* (and development on Pixels is waaay ahead respect to our device, so why don't we should learn from what they have already solved?)
enetec said:
Ehi boy, they sell chamomile, do ya know?
And A/B partitions in common with Pixels *are* rilevant since the method used to place recovery in boot.img is *exactly the same* (and development on Pixels is waaay ahead respect to our device, so why don't we should learn from what they have already solved?)
Click to expand...
Click to collapse
[emoji25]?*
Whatever dude.
Sent from my Moto Z (2) using Tapatalk
enetec said:
Ehi boy, they sell chamomile, do ya know?
And A/B partitions in common with Pixels *are* rilevant since the method used to place recovery in boot.img is *exactly the same* (and development on Pixels is waaay ahead respect to our device, so why don't we should learn from what they have already solved?)
Click to expand...
Click to collapse
We are more like the pixel 2. msm8998, TWRP has decryption issues, etc. Just follow pixel 2 and let me know how ahead the pixel 2 is... Hell, I was able to temp boot with a pixel 2 kernel with our defconfig. I wouldn't recommend it, mods didn't work, vibration was off and a few other issues, but that is because it was Google source and not ours.
Uzephi said:
We are more like the pixel 2. msm8998, TWRP has decryption issues, etc. Just follow pixel 2 and let me know how ahead the pixel 2 is... Hell, I was able to temp boot with a pixel 2 kernel with our defconfig. I wouldn't recommend it, mods didn't work, vibration was off and a few other issues, but that is because it was Google source and not ours.
Click to expand...
Click to collapse
It was my impression too.
Have you tried to take a look to their bootable-only twrp?
What is Pantheon?
A Temple dedicated to all the gods.
That is what this kernel is for: dedication to everyone on the Nash.
Features:
Edits to avoid Safetynet/CTS (If you have root, it will fail signature check inherently without SUhide or Magisk hide)
Disabled CRC check
Built With Linaro as the cross compiler
Over Clock / Under Clock on CPU Frequencies added:
Little CPU: 175 MHz, 230 MHz, 2035 MHz, 2112 MHz
Big CPU: 175 MHz, 230 MHz, 2476 MHz; 2592 MHz
Slight undervolt (our device is overvolted compared to other msm8998 devices)
UC GPU (added 180 Mhz step for battery savings when web browsing, low GPU usage)
OC GPU (changed 710 MHz to 750 MHz)
Same Adrenoboost tweaks as the Pixel 2 ElementalX kernel.
Wakelock fixes by Boeffla
Added Zen, FIOPS, BFQ, and SIO IO schedulers
CPU wake boost driver
Option in Aroma to UC the Big Cluster to 1.9 GHz
Options in Aroma to set the Max frequency of both Clusters (the above option will override this for Big Cluster)
Bugs/Issues:
None! In Alpha Phase, it boots and works...
Download:
Google Drive Link
Instructions:
Download ZIP to phone
Boot to TWRP.
Flash and follow prompts in Aroma
Reflash root if you want root.
Version Information
Status: Beta
Current Stable Version:
Stable Release Date:
Created 2018-06-18
Last Updated 2018-07-04
Source: https://github.com/Uzephi/Nash_Oreo
Git Branch: oreo-8.0.0-release-nash
Cross Compiler: Linaro 4.9
Branch: Android 8.0.y
Kernel Version: 4.4.y
defconfig: nash_defconfig
Credits: @joemossjr - for collaborating and getting this working and debugging w/ me to get the best possible experience for our community. @invisiblek for all the work he's done for our device tree @npjohnson for his work on our device tree.
Thanks and Mentions:
@Lord Boeffla for his wakelock code. @nathanchance for the assistance and amazing guides and keeping msm-8998 up to date with linux-stable @jbats for being awesome on this device.
@flar2 for his work on our chipset, msm8998
All other developers shown in commit history.
(Quoted from Nathan Chance)
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.
Change Log:
2018-06-18
Initial Release - Alpha (No updates from Motorola since Nov 2017 per their Nash Git. See post 4)
2018-07-04
Updated with new tags pushed by Motorola on their Git.
Reserved x2
Disclaimer:
Motorola has not released source code for our device's kernel for the March or May Security updates. So if Feb, Mar, Apr, or May Android security patches had any kernel changes, this kernel does not have those in it. See below with link to open issue on Motorola's Github.
Issue has been fixed and issue 152 has been closed by me.
https://github.com/MotorolaMobilityLLC/kernel-msm/issues/152
first!
i was just trying to do my own stock kernel build and it failed miserably. gonna give this a go
Midnight_Rider said:
first!
i was just trying to do my own stock kernel build and it failed miserably. gonna give this a go
Click to expand...
Click to collapse
Everyone has permission to fork from my kernel, just give credits like OP states.
Unfortunately it seems that this kernel, just like your previous releases, causes my device to randomly freeze and reboot, sometimes throwing it into a loop. :/
I'm on stock 27.1.2 and there has been some improvement as far as wifi drops, but on rare occasions it still freezes and reboots. This is on a straight stock setup and a known issue for moto/lenovo by the way. Seems to happen most noticeably when something cpu or graphic intense it taking place. Wifi resume from screen off is a little slow, but better than 27.1 and completely dropping out. This isn't because of Pantheon, this is all stock moto.
I'm hoping with Pantheon the cpu wake boost will help with wifi resume and maybe an overclock with give that little extra to keep it from freezing/rebooting when demand is high. Hopefully after a little tweaking and testing those stock issues will be resolved and moto/lenovo can finally come to terms with their wonky kernel and wifi.
If they would just go a little more open source in those areas they'd have a killer phone because I don't have those problems when I run custom roms and kernels, just stock.
So thanks @Uzephi and the other devs out there for keeping things on the up n' up.
donjuro said:
Unfortunately it seems that this kernel, just like your previous releases, causes my device to randomly freeze and reboot, sometimes throwing it into a loop. :/
Click to expand...
Click to collapse
Sorry. This was made by request. I have not personally tested it. It has the same commits as my aosp kernel minus the upstream done to my aosp kernel. All modifications I have added outside of upstream to Linux stable have been added. These modifications run just fine for me on aosp. I will not go back to stock unless I have to. I would need a kernel panic log, which I think Motorola disabled on a ROM level. If you can PM me a last_kmesg I can look through it, but last I was on stock, I couldn't find it in the proc folder.
Thanks, i'm gonna test it!
no data /wifi drop/ no random boot, testing battery and performance
thanks mate
Whats the difference between this one and your previous stock kernel besides the underclock.
mookiexl said:
Whats the difference between this one and your previous stock kernel besides the underclock.
Click to expand...
Click to collapse
https://github.com/Uzephi/Nash_Oreo/commits/oreo-8.0.0-release-nash
Some optimizations that don't need to be discussed. Everything pushed on the 18th of June.
Edit: CPU wake boost. Little cluster getting 2112 MHz OC, WiFi driver fix and a few other fixes as well, like to the Adreno driver (GPU).
Uzephi said:
https://github.com/Uzephi/Nash_Oreo/commits/oreo-8.0.0-release-nash
Some optimizations that don't need to be discussed. Everything pushed on the 18th of June.
Edit: CPU wake boost. Little cluster getting 2112 MHz OC, WiFi driver fix and a few other fixes as well, like to the Adreno driver (GPU).
Click to expand...
Click to collapse
Thanks, testing now. I will add that stock plus your original oreo kernel has been the best experience I've had with this device thus far for battery and performance.
Not bad for a test run, been running sio i/o scheduler. Gonna tweak some more and see how good it gets.
@Uzephi, this caused a bootloop on Encrypted device.
pvsgh said:
@Uzephi, this caused a bootloop on Encrypted device.
Click to expand...
Click to collapse
No log, no go. I don't run stock to even test this. I can't fix if you just state it doesn't work. I need a log of when it happens.
Uzephi said:
No log, no go. I don't run stock to even test this. I can't fix if you just state it doesn't work. I need a log of when it happens.
Click to expand...
Click to collapse
The device was not even being detected by PC, so not sure how to capture the logs. I restored the stock kernel from backup for now.
pvsgh said:
The device was not even being detected by PC, so not sure how to capture the logs. I restored the stock kernel from backup for now.
Click to expand...
Click to collapse
Others have used it fine. The device is encrypted by default. There has to be something else that would cause a boot panic other than encryption when others who are encrypted did not run into the issue. Are you able to boot into recovery? If so, encryption and other stuff that would prevent a boot are fine as recovery will boot with the same kernel as system does.
Uzephi said:
Others have used it fine. The device is encrypted by default. There has to be something else that would cause a boot panic other than encryption when others who are encrypted did not run into the issue. Are you able to boot into recovery? If so, encryption and other stuff that would prevent a boot are fine as recovery will boot with the same kernel as system does.
Click to expand...
Click to collapse
Yes, I was able to boot into recovery after the bootloop. That's how I restored the kernel from backup.
I don't need the encryption on the device, just trying to avoid another format to remove encryption.
Just got this phone rooted yesterday, hoping to build a flashable stock debloated ROM for this phone in near future.