Thanks. Yea I had a few offers and through some weeks I'd have 3-4 interviews a day so it was a pretty busy process. I'll still be here though, SW is definitely one of the best opportunities in Cleveland I think.
[ZEN-KERNEL] 3.10-zen21 "Cheap and Easy" (May 20)
- Thread starter bbedward
- Start date
Thanks. Yea I had a few offers and through some weeks I'd have 3-4 interviews a day so it was a pretty busy process. I'll still be here though, SW is definitely one of the best opportunities in Cleveland I think.
Anyone running this with Android M preview two? I want to switch from Chroma and Zen to JDX and Zen, just wondering if this kernel is working for the second preview.
Sorry to but into your thread, but is there a port of this kernel to the OnePlus One? Or would you happen to know of a OnePlus kernel that supports BFS and F2FS? Private messages welcome (don't wanna take up too much space in your thread). Any information appreciates. Thanks!
Sorry but there is not. Oneplus One uses 3.4.x release of the linux kernel, while the nexus 6 uses 3.10.x. The difference you notice is probably nothing, but the port/work for it here is not directly compatible with the 3.4 kernel (I'd have to do it separately for that one).
F2FS I suspect would be no large obstacle though.
I am on the waiting list for the Oneplus two (like #3 million in line), and I'll 100% buy the new nexus later this year. So if I can ever get an invite for OP2 there will assuredly be a zen kernel there
The OP1 however not at this point.
Sorry but there is not. Oneplus One uses 3.4.x release of the linux kernel, while the nexus 6 uses 3.10.x. The difference you notice is probably nothing, but the port/work for it here is not directly compatible with the 3.4 kernel (I'd have to do it separately for that one).
F2FS I suspect would be no large obstacle though.
I am on the waiting list for the Oneplus two (like #3 million in line), and I'll 100% buy the new nexus later this year. So if I can ever get an invite for OP2 there will assuredly be a zen kernel there
Good to hear that Zen will be making it's way towards the new Nexus
If rumor is true and two new Nexus are released, disregarding price, would you opt towards the smaller one or the bigger one?
Good to hear that Zen will be making it's way towards the new Nexus
Almost assuredly the bigger one
Almost assuredly the bigger one
That's good to hear, because I will be aiming for the bigger one as well
I'm on the waiting list too, like 2.8 million, so I can't wait to see you there! I'll also be getting both new nexus devices in a couple months. Woot!Sorry but there is not. Oneplus One uses 3.4.x release of the linux kernel, while the nexus 6 uses 3.10.x. The difference you notice is probably nothing, but the port/work for it here is not directly compatible with the 3.4 kernel (I'd have to do it separately for that one).
F2FS I suspect would be no large obstacle though.
I am on the waiting list for the Oneplus two (like #3 million in line), and I'll 100% buy the new nexus later this year. So if I can ever get an invite for OP2 there will assuredly be a zen kernel there
I've never been one to chase wake locks or tune services. I leave everything on all the time, its easy enough to charge... Outlets are everywhere.
On stock or elite I got typically 3.5hr screen on, never over 4. Doing nothing other then flashing this kernel has taken me to over 5 hr screen on in the same usage conditions. Its been more stable as well with out giving anything up.
Awesome work.
On stock or elite I got typically 3.5hr screen on, never over 4. Doing nothing other then flashing this kernel has taken me to over 5 hr screen on in the same usage conditions. Its been more stable as well with out giving anything up.
Awesome work.
That's the I/O scheduler (BFQ). BFS = the CPU scheduler, it's not something you can change, as Zen is a BFS kernel as opposed to a CFS kernel.
Dang. Just had a freeze and reboot on this kernel.
Here's a log from /sys/fs/pstore/dmesg_ramoops-0
https://drive.google.com/file/d/0B7_ZbvLWniZgamFDTHBiUERLUWs/view?usp=sharing
Here's a log from /sys/fs/pstore/dmesg_ramoops-0
https://drive.google.com/file/d/0B7_ZbvLWniZgamFDTHBiUERLUWs/view?usp=sharing
I am unsure what all the files are, but custom kernels often add files to at least the system partition, such as init.d settings... Generally the recommendation is to not flash one customer kernel over another.
If your on stock, or at least what is stock for your rom, you should be fine to just flash the kernel, no wipes or special moves needed.
If you have been using a different custom kernel, it seems to be the general recommendation (not just for this kernel) to dirty flash your rom to get back to "stock" wrt your kernel, and then flash.
Pushbullet: https://www.pushbullet.com/channel?tag=zen
But you say I'm just a friend
Project Background
First of all. I like the nexus 6. Actually, I really really like the nexus 6. I think the device from factory performs quite marvelously, especially since the 5.1 update. Because of this, I am actually pretty content with running the stock kernel. "But BB...What about INTelligentSuperBOOSTXX5MillionPOINT5MegaBlast?!?!?!? Can you add this!?". While I appreciate all the great and free work that several great individuals do for the community. I personally don't see the need to alter any of these MSM/Board drivers a whole lot - not on these latest generation of devices. Things run pretty well I think.
"Why don't you just run the stock kernel then you sick low-life waste of space?"
Because, I still think improvements can be made.
I think there's a lot of good intentions out there to make improvements in the kernel-space, BUT:
I've observed a variety of things that were prevalent a couple of years ago and that are still prevalent today. (1) A lot of small things are changed - and advertised as a huge improvement, (2) some tunables are adjusted and advertised as a huge change/improvement but end up being a regression because they were never tested, or (3) some code is merged that causes regressions and it turns out that self-inflicted bugs are being chased around.
Zen is an attempt at improving the stock kernel. That's it.
Project Summary
The Zen kernel has always been oriented at improving the experience fordesktopmobile users as much as possible. This iteration of the series is no different. The goal is simple: Improve the experience.
BFS CPU Scheduler
BFS is an alternative CPU scheduler to the stock kernel's CFS. BFS features a simple single-runqueue O
BFS is tweaked towards human perception. It is not a real-time scheduler (like the SCHED_DEADLINE policy/scheduling in 3.14+) nor does it use runtimes+red/black trees to figure out fairness. It uses deadlines with the 6ms rr_interval based on the fact that humans cannot detect jitters until >= 7ms.
Anyway, not going to get into it much but you may find more information in post 2, or throughout this thread (I explained a bit more details about it around page 4).
Also, check these out:
BFS FAQ
BFS Wikia
Android/MSM 3.10 BFS Port
What is different about this and the 3.10-ck1 bfs v440 patch available on ck.kolivas.org
What does this mean
- Backport fixes and features (not SMT NICE) from up to bfs v460ish
- Some of Alfred Chen's upstream synchronization and refactoring of BFS methods (linux-3.18/19-gc branch)
- My own syncing with mainline as well as backporting
"How about the performance?"
- Suspend/Wake issues that were killer on bfs v440 for 3.10 are not present in this port - these issues have been resolved.
- You should NEVER report any issue related to this kernel upstream. Not android, linux, or BFS related. Do not report any issues anywhere but here.
This kernel is all about interactivity by default.
The default rr_interval is set to 6. The logic is the human eye cannot detect jitter until about 7ms. Try lowering it if you want to increase interactivity. Try increasing it to achieve higher thoroughput.
-------------------------
Zen/Shamu Features
- BFS CPU Scheduler
- @flar2 Wake Gestures
- @savoca KCAL Screen Color Control
- @imoseyon Vibration SysFS interface
- USB Fastcharge Support
- Fsync SysFS Interface
- Overclocking support
- Flar2 userspace CPU voltage control
- f2fs support and latest f2fs: f2fs/dev (even with ZenyKernel zip)
- FIOPS + BFQ + SIO in addition to the stock ROW, CFQ, Deadline, No-op I/O schedulers
- Several misc. CAF/msm + upstream updates/fixes.
- Forced encryption disabled. (Even With ZenyKernel zip)
- Added init.d support (ZenyKernel is up to your existing ROM/kernel)
- selinux adjustments for viper4android and other things (ZenyKernel is up to your existing ROM/kernel)
- Compatible with most ROMs, use ZenyKernel zip if there's compatibility issues.
- Added zRam support
- MPDecision disabled by default, replaced by touchboost listener + ZenDecision 2.0
- ZenyKernel based on @osm0sis AnyKernel2 to use for roms who break compatibility with stock ramdisk
I work based on real results from user experience, not numbers. I don't claim anything as a big deal if it isn't one. Zen is a no-nonsense, well-tested kernel making real improvements to interactivity in the kernel space.
---------
Releases
All of these builds are for android 5.1 and above, unless otherwise noted
Wipe /cache before flashing for best results
Versions
- Recovery Zip: Kernel+Ramdisk: Use this on a stock/stock-like rom, or on a rom without support for things like viper4android or init.d support. Flash in recovery.
- Boot.IMG: Kernel+Ramdisk: Same as recovery zip, except in the raw boot.img form. Can be flashed in fastboot, flashify, etc.
- ZenyKernel Zip: Kernel Only (+ no force encryption +f2fs support +zen settings): Will use the exact same ramdisk you already have. If you have issues with the other full versions, then dirty flash your rom and this on top of it.
3.10-zen21 "Cheap and Easy"
Changes:
- Compile with GCC 5.1
- Several bcmdhd/wifi driver updates
- Misc. CAF updates
- Fix come cores sticking to performance governor
3.10-zen21 Recovery Zip Download
3.10-zen21 boot.img (install via fastboot/twrp IMG) Download
3.10-zen21 ZenyKernel Zip (Use on top of ROM dirty flash if issues with the above two)
Legacy Releases
ZenDecision (zen20+)
You can still turn on MPDecision without any ill effects if desired
As of 5.1+ MPDecision is somehow responsible for at least the following:
User configurability is sacrificed when it is enabled. For example: changing minimum CPU frequency is not possible, nor is changing the touchboost frequency or duration possible. Simply disabling MPDecision results in the permanent disabling of CPUs in certain situations (until the user either reboots, or manually turns them on again).
- Raise MIN_FREQ to 1497MHz for 3 seconds on touch events
- Ensure CPUs come online after certain events, like thermal events (due to low battery for example)
ZenDecision is a simple "handler" for to keep CPUs online by the following logic:
Simple, not a complete replacement for MPDecision. Just a handler for the event of cores never coming back online. Touchboosting is now configurable through the standard cpu-boost module parameters.
- When screen comes on, make sure all CPUs are online if current battery level is above bat_threshold_ignore
ZenDecision tunables (/sys/kernel/zen_decision/):
- enabled (0=disabled, 1=enabled): Enable/Disable the driver from doing any work
- wake_wait_time (0-60000 ms, 1000 by default): How long to wait to execute CPU_UP work after screen comes online.
- bat_threshold_ignore(1-100, 0=disabled, 15 by default): The battery percentage to ignore CPU_UP operations. If current battery level is below this level, then the driver is essentially disabled.
How to enable overclocking (zen6+)
If your device is unstable at the overclocked frequencies, it is a hardware limitation with your device. Do not report it as a bug
To enable overclocking on zen6 or newer, you will need to use the recovery zip/aroma below.
You choose the max frequency you want, it pulls the boot.img from the device, adds a boot parameter specifying the OC frequency.
If you are not on zen6 or newer it will have no affect.
This does not install a kernel, you still have to install the kernel from one of the links above
Zen Overclock Enable v2
3.09GHz step only supported on zen20+
Thanks guys, and enjoy. Feedback is always appreciated.
XDA:DevDB Information
Zen Kernel, Kernel for the Nexus 6
Contributors
bbedward, purian23
Source Code: https://github.com/bbedward/ZenKernel_Shamu/
Kernel Special Features: Android/MSM BFS Port, kcal, gestures, cool stuff
Version Information
Status: Stable
Current Stable Version: 21
Stable Release Date: 2015-05-20
Created 2015-03-24
Last Updated 2015-05-20
apparently i cant read for the life of me, in OP this states that your ver. of mpdecision is enabled correct? or do i have to turn it on .
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
84Pushbullet: https://www.pushbullet.com/channel?tag=zen
But you say I'm just a friend
Project Background
First of all. I like the nexus 6. Actually, I really really like the nexus 6. I think the device from factory performs quite marvelously, especially since the 5.1 update. Because of this, I am actually pretty content with running the stock kernel. "But BB...What about INTelligentSuperBOOSTXX5MillionPOINT5MegaBlast?!?!?!? Can you add this!?". While I appreciate all the great and free work that several great individuals do for the community. I personally don't see the need to alter any of these MSM/Board drivers a whole lot - not on these latest generation of devices. Things run pretty well I think.
"Why don't you just run the stock kernel then you sick low-life waste of space?"
Because, I still think improvements can be made.
I think there's a lot of good intentions out there to make improvements in the kernel-space, BUT:
I've observed a variety of things that were prevalent a couple of years ago and that are still prevalent today. (1) A lot of small things are changed - and advertised as a huge improvement, (2) some tunables are adjusted and advertised as a huge change/improvement but end up being a regression because they were never tested, or (3) some code is merged that causes regressions and it turns out that self-inflicted bugs are being chased around.
Zen is an attempt at improving the stock kernel. That's it.
Project Summary
The Zen kernel has always been oriented at improving the experience fordesktopmobile users as much as possible. This iteration of the series is no different. The goal is simple: Improve the experience.
BFS CPU Scheduler
BFS is an alternative CPU scheduler to the stock kernel's CFS. BFS features a simple single-runqueue O earliest virtual deadline first design. There is no need for excessive balancing to achieve fariness on multiple runqueues - fairness is ensured by deadlines.
BFS is tweaked towards human perception. It is not a real-time scheduler (like the SCHED_DEADLINE policy/scheduling in 3.14+) nor does it use runtimes+red/black trees to figure out fairness. It uses deadlines with the 6ms rr_interval based on the fact that humans cannot detect jitters until >= 7ms.
Anyway, not going to get into it much but you may find more information in post 2, or throughout this thread (I explained a bit more details about it around page 4).
Also, check these out:
BFS FAQ
BFS Wikia
Android/MSM 3.10 BFS Port
What is different about this and the 3.10-ck1 bfs v440 patch available on ck.kolivas.org
- Backport fixes and features (not SMT NICE) from up to bfs v460ish
- Some of Alfred Chen's upstream synchronization and refactoring of BFS methods (linux-3.18/19-gc branch)
- My own syncing with mainline as well as backporting
- Suspend/Wake issues that were killer on bfs v440 for 3.10 are not present in this port - these issues have been resolved.
- You should NEVER report any issue related to this kernel upstream. Not android, linux, or BFS related. Do not report any issues anywhere but here.
This kernel is all about interactivity by default.
The default rr_interval is set to 6. The logic is the human eye cannot detect jitter until about 7ms. Try lowering it if you want to increase interactivity. Try increasing it to achieve higher thoroughput.
-------------------------
Zen/Shamu Features
- BFS CPU Scheduler
- @flar2 Wake Gestures
- @savoca KCAL Screen Color Control
- @imoseyon Vibration SysFS interface
- USB Fastcharge Support
- Fsync SysFS Interface
- Overclocking support
- Flar2 userspace CPU voltage control
- f2fs support and latest f2fs: f2fs/dev (even with ZenyKernel zip)
- FIOPS + BFQ + SIO in addition to the stock ROW, CFQ, Deadline, No-op I/O schedulers
- Several misc. CAF/msm + upstream updates/fixes.
- Forced encryption disabled. (Even With ZenyKernel zip)
- Added init.d support (ZenyKernel is up to your existing ROM/kernel)
- selinux adjustments for viper4android and other things (ZenyKernel is up to your existing ROM/kernel)
- Compatible with most ROMs, use ZenyKernel zip if there's compatibility issues.
- Added zRam support
- MPDecision disabled by default, replaced by touchboost listener + ZenDecision 2.0
- ZenyKernel based on @osm0sis AnyKernel2 to use for roms who break compatibility with stock ramdisk
I work based on real results from user experience, not numbers. I don't claim anything as a big deal if it isn't one. Zen is a no-nonsense, well-tested kernel making real improvements to interactivity in the kernel space.
---------
Releases
All of these builds are for android 5.1 and above, unless otherwise noted
Wipe /cache before flashing for best results
Versions
- Recovery Zip: Kernel+Ramdisk: Use this on a stock/stock-like rom, or on a rom without support for things like viper4android or init.d support. Flash in recovery.
- Boot.IMG: Kernel+Ramdisk: Same as recovery zip, except in the raw boot.img form. Can be flashed in fastboot, flashify, etc.
- ZenyKernel Zip: Kernel Only (+ no force encryption +f2fs support +zen settings): Will use the exact same ramdisk you already have. If you have issues with the other full versions, then dirty flash your rom and this on top of it.
3.10-zen21 "Cheap and Easy"
Changes:
- Compile with GCC 5.1
- Several bcmdhd/wifi driver updates
- Misc. CAF updates
- Fix come cores sticking to performance governor
3.10-zen21 Recovery Zip Download
3.10-zen21 boot.img (install via fastboot/twrp IMG) Download
3.10-zen21 ZenyKernel Zip (Use on top of ROM dirty flash if issues with the above two)
Legacy Releases
ZenDecision (zen20+)
You can still turn on MPDecision without any ill effects if desired
As of 5.1+ MPDecision is somehow responsible for at least the following:
- Raise MIN_FREQ to 1497MHz for 3 seconds on touch events
- Ensure CPUs come online after certain events, like thermal events (due to low battery for example)
ZenDecision is a simple "handler" for to keep CPUs online by the following logic:
- When screen comes on, make sure all CPUs are online if current battery level is above bat_threshold_ignore
ZenDecision tunables (/sys/kernel/zen_decision/):
- enabled (0=disabled, 1=enabled): Enable/Disable the driver from doing any work
- wake_wait_time (0-60000 ms, 1000 by default): How long to wait to execute CPU_UP work after screen comes online.
- bat_threshold_ignore(1-100, 0=disabled, 15 by default): The battery percentage to ignore CPU_UP operations. If current battery level is below this level, then the driver is essentially disabled.
How to enable overclocking (zen6+)
If your device is unstable at the overclocked frequencies, it is a hardware limitation with your device. Do not report it as a bug
To enable overclocking on zen6 or newer, you will need to use the recovery zip/aroma below.
You choose the max frequency you want, it pulls the boot.img from the device, adds a boot parameter specifying the OC frequency.
If you are not on zen6 or newer it will have no affect.
This does not install a kernel, you still have to install the kernel from one of the links above
Zen Overclock Enable v2
3.09GHz step only supported on zen20+
Thanks guys, and enjoy. Feedback is always appreciated.
XDA:DevDB Information
Zen Kernel, Kernel for the Nexus 6
Contributors
bbedward, purian23
Source Code: https://github.com/bbedward/ZenKernel_Shamu/
Kernel Special Features: Android/MSM BFS Port, kcal, gestures, cool stuff
Version Information
Status: Stable
Current Stable Version: 21
Stable Release Date: 2015-05-20
Created 2015-03-24
Last Updated 2015-05-2030To say I have been incredibly busy is an understatement.
However, I've finally received some incredible offers to start my career as a software engineer.
In celebration of the whole process finally coming to an end I will be finalizing and working on the reboot of zen kernel :highfive:29Hey guys,
I just wanted to toss this out there an say i'm proud of @bbedward! Today, he Graduates from the University of Toledo with his Software Engineering Degree (Computer Science & Engineering) with a Bright Future! He already has options at Oracle and GE as soon as he steps foot back in his hometown of Cleveland!
I honestly feel like his big brother with all the BS'n we've done over the past few years. He's taught me a lot (even though the punk is younger lol) and I'm pretty sure I've given him so good life morals to go by haha. Join me in Congratulating @bbedward for not only his awesome kernels and tons of XDA Community involvement/help through the years, but for generally being a cool dude. We'll surely look forward to what he has in store next for the tech community.
Thanks dude and Congrats
Purian2322@purian23's original name for the last release is applicable for zen15.
3.10-zen15 "Unbroken"
Changes:
- All the great changes of zen14 except without the BFS LLC cpumask selection - was an issue causer
- Updated kcal (I forgot to merge into 14)
3.10-zen15 Recovery Zip Download
3.10-zen15 boot.img (install via fastboot/twrp IMG) Download
3.10-zen15 AnyKernel Zip (Use for CM 12.1 or other roms that change ramdisk/sepolicy things)
