[KERNEL][NON-TW] Marshmallow Kernels [N915T, N915G, N915F, N915FY]

[KERNEL][NON-TW] Marshmallow Kernels [N915T, N915G, N915F, N915FY] - Note Edge Android Development

Below you will find a couple of kernels that I put together for various roms and purposes. Most of these will be included into my other builds, but I thought that I would share them here as well, in case they are useful on any other roms. You are welcome to use and abuse these kernels or the source code for any purpose that you see fit!
It all started over a year ago when I wanted to add some governors to a kernel, and it didn't work very well. However, praise God, I learned a lot of things and was able to add the governors in! From there I played around with various sources and have put together some developer kernels as well (including kexec and other tools). None of my work is purely original, I typically beg or borrow from other kernel developers by looking at their source. Please feel free to use any of the materials here if it will help you in any way (including adding it to a different rom).
Feel free to comment if you have tried them on another rom, successful or not, or to leave feedback on these kernels as well. These can be flashed on any tblte variant of phone, but I have only personally tested them on tbltetmo. They should work on any tbltexx phone as well, and maybe others.
This is, however, specifically not for TW roms. This is for AOSP/CM etc., based roms.
Post #2: Thanks
Post #3: Marshmallow kernels
Post #4: Change logs
Source: https://github.com/alaskalinuxuser
Post created: 10/26/16
Last updated: 12/22/16

The big thanks!
As with any project, it starts somewhere, and while I want to give God the glory for my work, I also want to thank a few other people who helped me (directly or indirectly) along the way:
@OldDroid
@Mickey387
@deadman96385
The Emotroid Team

For AOKP 6.0.1, may also work with PAC and CM.
Download:
http://www.mediafire.com/file/zodtgo623rkj09f/AKLU-AOKP-M-TBLTE-intelliplug-20161222.zip
For PACROMS 6.0.1, may also work with AOKP and CM.
Download:
http://www.mediafire.com/file/bafiwx8epkiqteb/AKLU-PAC-M-TBLTE-intelliplug-20161222.zip
For SLIMROMS 6.0.1, may also work with LS.
Download:
http://www.mediafire.com/file/bb5ns8nq4ybt376/AKLU-SLIM-M-TBLTE-intelliplug-20161222.zip
Features:
- CPU over clocked to 2688 MHz.
- GPU over clocked to 633 MHz.
- Intelli_plug by @faux123!
- Bioshock, Darkness, Nightmare, and Lionheart Governors!
- CPU boost, DVSF input boost disabled so you can use CPU boost for input.
OLD KERNELS:
https://www.mediafire.com/download/3hdl2bl4j3eqbdw
https://www.mediafire.com/download/waz9bklaj808o90
https://www.mediafire.com/download/nh1oa058qdqa708
PAC/AOKP 6.0 baseline:
http://www.mediafire.com/file/h9b68aaon1yvr11/aokp_pac-mm-kernel-baseline.zip
Slim 6.0 baseline:
http://www.mediafire.com/file/bt4qw03m8jko53a/slim-mm-kernel-baseline.zip
Developer kernel for AOKP and PAC ROM:
https://www.mediafire.com/download/6q16143xjmf6hje
Features:
- Kexec enabled
- Modules enabled
- CPU over clocked to 2688 MHz.
- GPU over clocked to 633 MHz.
- Bioshock, Darkness, Nightmare, and Lionheart Governors!
- CPU boost, DVSF input boost disabled so you can use CPU boost for input.
- DANGEROUS! USE WITH CAUTION!
Notes:
May require a clean flash over fresh ROM. I have had trouble where I also needed to wipe coach after flashing. ATAGS is enabled. This kernel is potentially a security risk, but may allow you to play with multirom or other multiple boot options.

Change Log:
20161222
+ Added Intelli_plug by @faux123!
20161116
+ Over clocked CPU to 2688 MHz.
+ Over clocked GPU to 633 MHz.
20161115
+ Added the Bioshock Governor.
+ Added the Lionheart Governor.
+ Added the Nightmare Governor.
+ Added the Darkness Governor.
- Removed FIOPS I/O Scheduler.
- Removed ZEN I/O Scheduler.
Removed extra I/O schedulers due to recurrence of the random reboots.
20161114
+ Added ZEN and FIOPS I/O Schedulers.
20161109
+ Disabled DVSF INPUT BOOST, which locked the CPU at 1267 MHz when you touch the screen or use the SPEN. Now you can use CPU boost in Kernel Aduitor to select the amount of boost you want when input is detected (or not to boost at all).
+ Started over from the ground up to get rid of the random reboot problem.

Keep in mind:
Just something to keep in mind, these kernel features (more as they are added) are not always enabled by default. You will need tools like the Kernel Adiutor app to control, enable, or use these features.
Any are welcome to chime in on thoughts, requests, and settings! Be sure to stay tuned, more will be added regularly!

I am aware of kernel vulnerability CVE-2016-5195 "Dirty C0W" and am working on implementing a fix to secure these kernels from that vulnerability. If you need information about it, you can read up on it here:
https://github.com/dirtycow/dirtycow.github.io/wiki/VulnerabilityDetails

AlaskaLinuxUser said:
I am aware of kernel vulnerability CVE-2016-5195 "Dirty C0W" and am working on implementing a fix to secure these kernels from that vulnerability. If you need information about it, you can read up on it here:
https://github.com/dirtycow/dirtycow.github.io/wiki/VulnerabilityDetails
Click to expand...
Click to collapse
U could share the kernel buiding lol I've been trying so hard to find files for gpu/cpu can u point me to those? Also how would I turn zimage into a boot.img..... the android kitchen thing is a little confusing

Excellent work as always Alaska. It'd be fantastic if we could get some hotplugging alternatives alongside the governor's, as mpdescision never plays well with over or under clocking.
Also I don't want to nag, but any luck exterminating that damn touchboost up to 1.2-1..7 ghz on core 0 and 1? I've found that whenever the pen is hovering near the digitizer it locks both cores at 1.2 which aside from being wholly unnesacary, definatly isn't helping the meagre battery life. Was also wondering if power to the digitizer might be a kernel function. And if so, whether power could suspended from the array whenever the spen is inserted. Mostly shooting in the dark, but TW ROMS have the ability to disable detection of the pen being distant from the handset. Dunno if the sensors that perform that function are being called by AOSP or CM, but it might be worth looking into having an option to disable them to save more power.

beany23 said:
U could share the kernel buiding lol I've been trying so hard to find files for gpu/cpu can u point me to those? Also how would I turn zimage into a boot.img..... the android kitchen thing is a little confusing
Click to expand...
Click to collapse
Beany23,
I can put together a little how to if you would like, I like working on kernels, it is a great learning experience, and it is fun. I over clocked my kernel on my phone, and am testing stability right now. The oc is small, but I made no increase in voltage or amperage, so it is a free boost. I plan to post it tomorrow. Working on kernels is really a lot of fun.
Aaren11 said:
Excellent work as always Alaska. It'd be fantastic if we could get some hotplugging alternatives alongside the governor's, as mpdescision never plays well with over or under clocking.
Also I don't want to nag, but any luck exterminating that damn touchboost up to 1.2-1..7 ghz on core 0 and 1? I've found that whenever the pen is hovering near the digitizer it locks both cores at 1.2 which aside from being wholly unnesacary, definatly isn't helping the meagre battery life. Was also wondering if power to the digitizer might be a kernel function. And if so, whether power could suspended from the array whenever the spen is inserted. Mostly shooting in the dark, but TW ROMS have the ability to disable detection of the pen being distant from the handset. Dunno if the sensors that perform that function are being called by AOSP or CM, but it might be worth looking into having an option to disable them to save more power.
Click to expand...
Click to collapse
Aaren11,
Yes, I agree. I have disabled the boost in my testing, but then could not get the kernel to boot. The kernel I am working with has many of Mickey378's fingerprints on it, so I am sorting some of those out. Then I can delve more into those. For instance, when I run " make mrproper " it looks for /home/mickey/android...... And errors, so I am trimming his work while maintaining the great work he did to actually make it function for AOSP ROMs. I also am experimenting with other kernel sources like OldDroid's and others. Keeping in mind that only Mickey had a 100% fully functional ROM.
I do want to say though, I couldn't agree more, the mandatory touch boost is a pain. It should be adjustable, but it doesn't take when we set it.
But, work is progressing. One step at a time.
Sent from my unknown using XDA-Developers mobile app

I would love to try the kexec-hardboot kernel if you'd be kind enough to share. Multirom on this dying device would be nothing short of a miracle.
Sent from my unknown using XDA-Developers mobile app

AlaskaLinuxUser said:
Beany23,
I can put together a little how to if you would like, I like working on kernels, it is a great learning experience, and it is fun. I over clocked my kernel on my phone, and am testing stability right now. The oc is small, but I made no increase in voltage or amperage, so it is a free boost. I plan to post it tomorrow. Working on kernels is really a lot of fun.
Aaren11,
Yes, I agree. I have disabled the boost in my testing, but then could not get the kernel to boot. The kernel I am working with has many of Mickey378's fingerprints on it, so I am sorting some of those out. Then I can delve more into those. For instance, when I run " make mrproper " it looks for /home/mickey/android...... And errors, so I am trimming his work while maintaining the great work he did to actually make it function for AOSP ROMs. I also am experimenting with other kernel sources like OldDroid's and others. Keeping in mind that only Mickey had a 100% fully functional ROM.
I do want to say though, I couldn't agree more, the mandatory touch boost is a pain. It should be adjustable, but it doesn't take when we set it.
But, work is progressing. One step at a time.
Sent from my unknown using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes plz the would be awesome!!!

Aaren11 said:
Excellent work as always Alaska. It'd be fantastic if we could get some hotplugging alternatives alongside the governor's, as mpdescision never plays well with over or under clocking.
Also I don't want to nag, but any luck exterminating that damn touchboost up to 1.2-1..7 ghz on core 0 and 1? I've found that whenever the pen is hovering near the digitizer it locks both cores at 1.2 which aside from being wholly unnesacary, definatly isn't helping the meagre battery life. Was also wondering if power to the digitizer might be a kernel function. And if so, whether power could suspended from the array whenever the spen is inserted. Mostly shooting in the dark, but TW ROMS have the ability to disable detection of the pen being distant from the handset. Dunno if the sensors that perform that function are being called by AOSP or CM, but it might be worth looking into having an option to disable them to save more power.
Click to expand...
Click to collapse
Just a quick comment, mpdescision is actually a really big battery saver, unless you use a hotplugging governor. You can check this for yourself:
Enable mpd, enable nightmare, turn on caffeine or set screen to stay on 5 minutes. Watch the screen. Open KA and watch the CPU settings screen. The CPU will drop to one core at 300 MHz and pretty much stay there.
Then, disable mpd, now watch the CPU screen, you will see 3 or 4 cores on at all times.
In my other kernels for other Samsung phones, I always leave mpd on, and I can still over/under clock/volt. So I intend to leave mpd, but I do agree we need to ditch the mandatory touch boost, especially for just having the spen out.
Sent from my unknown using XDA-Developers mobile app

New kernel is up!
Hi all! Praise God, another successful kernel build. This time is just some very light CPU overclocking without any negative battery drain! See main posts for details and downloads!
20161027
+CPU overclocked to 2688 MHz without increasing voltage or amperage. (+39 MHz)
See commit here: https://github.com/alaskalinuxuser/...mmit/9bb23d0d9cc805bf7e1b8e3fe829fcbb0542af31
{
"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"
}

AlaskaLinuxUser said:
Just a quick comment, mpdescision is actually a really big battery saver, unless you use a hotplugging governor. You can check this for yourself:
XDA-Developers mobile app
Click to expand...
Click to collapse
Errr...Alaska? I wasn't contending that mpdescision (a hotplug) is somehow less energy effcient than NO HOTPLUG. But it is one of the least effcient ones out there. Espceially when over or underclocking. Because Mpdesicion will override anything other than the stock clocks.
Also unless you disabled it, Nightmare does it's own hotplugging.

Aaren11 said:
Errr...Alaska? I wasn't contending that mpdescision (a hotplug) is somehow less energy effcient than NO HOTPLUG. But it is one of the least effcient ones out there. Espceially when over or underclocking. Because Mpdesicion will override anything other than the stock clocks.
Also unless you disabled it, Nightmare does it's own hotplugging.
Click to expand...
Click to collapse
"Nightmare
A PegasusQ modified, less aggressive and more stable. A good compromise between performance and battery. In addition to the SoD is a prevention because it usually does not hotplug."
http://ajgupta.github.io/android/2015/01/28/CPU-and-GPU-governors/
As you can see from my previous posts, if you disable mpd in KA, then you can watch the CPU cores. Nightmare will not turn them off except in rare instances on my phone with the screen on. That is one of the principle differences between Nightmare and PegasusQ.
Also, mpd is currently accepting my overclock input in the kernel. So mpd doesn't always have to cause problems with over/under frequencies, I am no expert, but I believe this stems from how the table is built.
In either event, there are a lot of really great hotplugging options, on that we agree. Now, less you think I am being facetious, I actually quite enjoy your input and discussion, so please don't take this as anything other than great discussion. The great thing about Android/Linux/kernels is that they are like ice cream, with so many flavors, everyone is bound to find one they like, or a combination that they think is the best, and there will always be a difference of opinion.
I also still have a lot to learn on the subject myself.

beany23 said:
Yes plz the would be awesome!!!
Click to expand...
Click to collapse
Beany23,
Still a work in progress, but for what it's worth, here is the guide:
http://forum.xda-developers.com/note-edge/general/guide-build-aosp-roms-kernels-note-edge-t3488840

AlaskaLinuxUser said:
Beany23,
Still a work in progress, but for what it's worth, here is the guide:
http://forum.xda-developers.com/note-edge/general/guide-build-aosp-roms-kernels-note-edge-t3488840
Click to expand...
Click to collapse
Can u tell me where the files are regarding cpu/gpu? And one more thing....I'm so glad someone has some love for this device lol great work and keep on keepin!

AlaskaLinuxUser said:
A PegasusQ modified, less aggressive and more stable. A good compromise between performance and battery. In addition to the SoD is a prevention because it usually does not hotplug.".
Click to expand...
Click to collapse
Dammit, I misread that very same passage. Ah well thanks for the correction.
AlaskaLinuxUser said:
Also, mpd is currently accepting my overclock input in the kernel. So mpd doesn't always have to cause problems with over/under frequencies, I am no expert, but I believe this stems from how the table is built..
Click to expand...
Click to collapse
That's definatley good news. On TW, any kernel with interactive would allow mpdescision to bump the clocks to stock values. Disabling mpdescision could make your under or overclock stick,but then you'd have no hotplugging.
AlaskaLinuxUser said:
I actually quite enjoy your input and discussion, so please don't take this as anything other than great discussion. The great thing about Android/Linux/kernels is that they are like ice cream, with so many flavors, everyone is bound to find one they like, or a combination that they think is the best, and there will always be a difference of opinion.
Click to expand...
Click to collapse
Likewise, I'm honestly beyond grateful someone finally started making non-TW ROMS and kernels for this device, and I'm always interested for a good Android discussion. Especially when it drives progress like this.

beany23 said:
Can u tell me where the files are regarding cpu/gpu? And one more thing....I'm so glad someone has some love for this device lol great work and keep on keepin!
Click to expand...
Click to collapse
The CPU Governor files are in the drivers/cpufreq/ folder, and all start with cpufreq_{DRIVERNAME.c}.
E.G. Nightmare = cpufreq_nightmare.c
You can read about it in more detail on Post #8 of the guide.

AlaskaLinuxUser said:
The CPU Governor files are in the drivers/cpufreq/ folder, and all start with cpufreq_{DRIVERNAME.c}.
E.G. Nightmare = cpufreq_nightmare.c
You can read about it in more detail on Post #8 of the guide.
Click to expand...
Click to collapse
I meant the frequency tables lol

Related

[Kernel] [2.6.38.8 (CM7)] HAVS/SVS + 1152MHz (09/17/11)

After being a long time lurker here in XDA and having successfully fulfilled some requests on another thread, I thought I'd try to give something to the great community here.
You probably remember Ivan's kernels that provided the community with a version of intersectRaven's Hybrid AVS with 1113MHz overclocking. Unfortunately it looks like Ivan been very busy and is unable to update his kernels. So I have provided recent updates of intersectRaven's truly awesome kernels that includes the 1113MHz overclock for you all to enjoy. (I see this request a lot so maybe now intersectRaven won't be bothered by it again )
I absolutely take no creative credit in making these kernels as all I have done is used the open source code on intersectRaven's github and compiled it. The real credit goes to all the other coders here in this forum (cyan, pershoot, and especially intersectRaven).
When time permits, I'll try to update these kernels when improvements and/or bug fixes are made but I realistically only see myself updating these once or twice a week.
I'm open to requests (like no audio boost) and such. Just let me know the one kernel you want modified and if its within my ability, I'll make one for you when time permits. I have not yet made a super all-in-one compiling script, so it would take me far too long to make a requested modification on all versions. Edit: Due to having virtually no free time, I don't think I can get fulfill requests in a timely manner... I'll try but I can't promise it. So sorry everyone -_-;
If you have the time and the will, I highly suggest you learn how to compile for yourself as I find it pretty fun and rewarding to make something for yourself. Guides and instructions can be found throughout the XDA forum and also on Cyanogen's wiki.
Before updating with these kernels, all I ask is that you make a nandroid backup in case something goes wrong.
Q & A:
-What's the difference between CFS and BFS?
See this short post for the difference between Completely Fair Scheduler and Brain F*** Scheduler. In summery, CFS is better for multitasking, BFS is better for user interactions (keyboard, homescreen swiping, etc).
-What's the difference between SVS and AVS?
Static Voltage Scaling will change the voltage based on a set table created by the kernel maker. Example: At a certain speed, say 245MHz, 925mV is feed into the CPU. At 998MHz, 1225mV is used.
Adaptive Voltage Scaling will change the voltage depending on temperature and CPU needs. Personally, AVS is running rock solid for me but I can't say for sure if it will be for everyone so SVS kernels will continue to be made available.
-What is this "No Audio Boost Version"?
Many of the custom kernels posted in this forum and the kernels used by default in the CM6 roms have this feature where it increases the loudness of the speakers during calls. Its been reported that some bluetooth headsets are overly sensitive to the increased loudness and some have reported that it distorts the audio quality even though volume has been lowered by the user. Due to an overwhelming request to make a kernel without this feature, I have included a separate set with each release that does not boost the volume.
-Can you make a higher overclock version of your kernel?
I was really against this because when I first tried to do this, my phone got really hot. But the requests kept on coming so I revisted this and possibly discovered a way to keep the temperature under control by limiting the max voltage to 1300mV. You'll find a 1190MHz version of my kernel here (Mirror Link).. Most users should be able to handle 1152MHz without any problems but some won't on 1190MHz. You'll know when your CPU can't handle a certain speed if you start to experience a sudden decrease in performance, lag, force closes, and spontaneous reboots. This won't be alievated unless more voltage is feed to the CPU but I'm not comfortable going beyond 1300mV. Now before you try these kernels out I gotta say this. I am not responsible if these kernels result in damaging your phone. Its purely for testing purposes and I really dont recommend using it as your everyday use kernel. If you do continue to use it, you should limit the max to 1113MHz or better yet 1075MHz (see previous question for the reason) if you care about battery life.
-I'm getting a black screen whenever I launch the camera app. Why? (720p related question)
The latest kernels with the 720p code only works with roms that has the 720p stock camera app and now the HTC camera app on Enomther's [ROM] as of 8/10/10. The latest cm6 nightly that has the 720p camera app as well as a few other roms out there that are based on cm6. You can try flashing charnsingh_online zip that contains the updated camera app if you don't want to use the nightly but I don't know for sure if his camera app is compatible with roms under RC2. Another alternative is to send in a request for a custom kernel and I'll make one for you without the 720p code.
2.6.38 kernels:
(Tested on Cyanogenmod 7 Nightlies)
Grab the kernels here: Mediafire
-Changes since 090311
-Set default sleep ideal freq to 128mhz for smartassV2 governor
-Bug fix for 1190MHz kernels, properly set max voltage to 1325mV
-Compiled HAVS 1190MHz kernels for those phone that can handle it
-Changes since 062411
Rebase source from IntersectRaven's Github
Highlights include:
-msm: Add support for voice call recording
-PM: Back off suspend if repeated attempts fail
-lib/sha1: use the git implementation of SHA-1
-arm: remove “optimized” SHA1 routines
-Fix AVS thread not being started.
-Added erasmux’s Smartass governor Version 2
-Changes since 062311
-Fixed ext4 partition support on sdcard.
-Changes since 052711
-Rebase to kernel version 2.6.38.8 from IntersectRaven's Github, with it 2 new governors (InteractiveX and SavageZen)
-Changes since 052611
-Rebased kernel source from intersectRaven's Github With it comes the smartass governor (default set to ondemand because I like it better)
-Switched to Tiny Preempt RCU with RCU boost (To match with Cyanogenmod stock kernel)
-Revert WiFi souce code used in previous release. (Didn't want to take a chance in WiFi not working for some.)
-Changes since 042111
-Rebased kernel source from intersectRaven’s Github With it comes the smartass governor (default set to ondemand because I like it better)
-Switched to Tiny Preempt RCU with RCU boost (To match with Cyanogenmod stock kernel)
-Revert WiFi souce code used in previous release. (Didn’t want to take a chance in WiFi not working for some.)
-Changes since 040911
-Bug fixes relating to USB file transfer speeds and addressed probable cause of WiFi problems for some.
____________________________________________________
If you want, you can buy me a drink (I like orange juice)

Have these kernels been tried and tested? Does the following work:
- Youtube
- Camcorder
- Googles
- Flash
- Unmounting sd card
- Wifi locations
and can you tell us more about the battery life by using this kernel?
p.s. Thanks for posting this btw...

- Youtube Works
- Camcorder works
- Flash works
- sd card problem persists on the .34
- wifi works
EDIT:
I LOVE this kernel! THX wildmonkey ^^
i testet the .34 on both 2.2 and 2.1.... works so far!

RinTinTigger said:
- Youtube Works
- Camcorder works
- Flash works
- sd card problem persists on the .34
- wifi works
Click to expand...
Click to collapse
Thats gr8...what about battery life? how do yo fare by using this kernel?

nazrin313 said:
Thats gr8...what about battery life? how do yo fare by using this kernel?
Click to expand...
Click to collapse
Well....i like 800mV UV and OC, giving me the best balance between battery life and speed.
couldnt do an excact test on the time, but it lasts enough for my usage ^^

nazrin313 said:
Thats gr8...what about battery life? how do yo fare by using this kernel?
Click to expand...
Click to collapse
Speaking for myself, I've been averaging 1-2% on standby. I can't tell you what I get at the end of the day because I usually plug my phone in the charger when I'm in the car...
RinTinTigger said:
- Youtube Works
- Camcorder works
- Flash works
- sd card problem persists on the .34
- wifi works
EDIT:
I LOVE this kernel! THX wildmonkey ^^
i testet the .34 on both 2.2 and 2.1.... works so far!
Click to expand...
Click to collapse
Glad you like it! You know it was partly you that made me want to start this thread.

great! i am really looking forward to it!

wildmonks said:
Speaking for myself, I've been averaging 1-2% on standby. I can't tell you what I get at the end of the day because I usually plug my phone in the charger when I'm in the car...
Glad you like it! You know it was partly you that made me want to start this thread.
Click to expand...
Click to collapse
"partly"
^^
xD

everything including goggles seems working on 800 bfs.. 41 linpacks.. cool

That was my result with linpack and this kernel!
{
"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"
}

forgot to setcpu doh
44.738 mflops
upd.. and bootloop =)

just got my nexus one so you could say i'm kinda new to this^^
just wondering what the difference between CFS and BFS kernels are? and what are the pros and cons with 800 / 925 mV kernels?
i am running rooted stock froyo atm, so all i need to do is install a .34 kernel through recovory if i am right? do kernel installs requier a wipe?
thx

wildmonks said:
I'm open to requests (like no audio boost) and such. Just let me know the one kernel you want modified and if its within my ability, I'll make one for you when time permits. I have not yet made a super all-in-one compiling script, so it would take me far too long to make a requested modification on all versions.
Click to expand...
Click to collapse
I am running CM5.0.7.1 and I would love to have a kernel that did not include the audio hack, I have a feeling that everyone must be deaf because this thing sounds real bad at higher volumes ever since the audio hack was implemented. I get so much distortion in-calls that I have to turn the volume down to a level that negates any audio boost - so what is the point?
So.. yeah, if you are taking specific requests:
1. Stock speeds (or OC if it has to be, I can control that).
2. 925mV.
3. CFS (though I haven't messed with BFS since CM4.xx days on my G1, I still think it has a long way to go).
4. No audio hack.
Seems perfect to me.

mardox said:
just got my nexus one so you could say i'm kinda new to this^^
just wondering what the difference between CFS and BFS kernels are? and what are the pros and cons with 800 / 925 mV kernels?
i am running rooted stock froyo atm, so all i need to do is install a .34 kernel through recovory if i am right? do kernel installs requier a wipe?
thx
Click to expand...
Click to collapse
CFS: http://de.wikipedia.org/wiki/Completely_Fair_Scheduler
BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler

Just flashed it...camcorder, video playback, youtube and WIFI works as normal.
Brilliant kernel in terms of performance, as speedy as preshoots...
Linpack scores varies from 40-44 mflops
Quadrant score is a hefty 1495...
Now, im gonna test the battery life tonight...

nazrin313 said:
Just flashed it...camcorder, video playback, youtube and WIFI works as normal.
Brilliant kernel in terms of performance, as speedy as preshoots...
Linpack scores varies from 40-44 mflops
Quadrant score is a hefty 1495...
Now, im gonna test the battery life tonight...
Click to expand...
Click to collapse
when you say "test battery life tonight" does that mean you are going to leave the phone over night and see how much battery is consumed in standby or are you actually going to use the device?

hondaguy said:
when you say "test battery life tonight" does that mean you are going to leave the phone over night and see how much battery is consumed in standby or are you actually going to use the device?
Click to expand...
Click to collapse
Im gonna charge it to 100% then leave it whilst I sleep...Tommorow im gonna im actually gonna use it
from my own usage since installing Froyo here is what I have found from testing various kernels (Unplugged at 7am)
- Froyo Kernel: Lasted till 10pm ish (Display on > 3 hrs)
- Preshoot 33.4 kernel: lasted me till 3pm ish (Display on approx 2 hrs)
P.s:
Tested on quadrant again and I got a whopping 1668...thats the highest ive seen my phone do...

daveid said:
I am running CM5.0.7.1 and I would love to have a kernel that did not include the audio hack, I have a feeling that everyone must be deaf because this thing sounds real bad at higher volumes ever since the audio hack was implemented. I get so much distortion in-calls that I have to turn the volume down to a level that negates any audio boost - so what is the point?
So.. yeah, if you are taking specific requests:
1. Stock speeds (or OC if it has to be, I can control that).
2. 925mV.
3. CFS (though I haven't messed with BFS since CM4.xx days on my G1, I still think it has a long way to go).
4. No audio hack.
Seems perfect to me.
Click to expand...
Click to collapse
Here yah go:
2.6.33.5_AVS-925mV_CFS_NoAudBoost_v2_060210.zip
I think all those years of listening to loud music has affected my hearing so I need the audio boost
I tested it out and it seems audio levels are back to standard (noticeably lower) but let me know if it doesn't work or if there are any other problems with it.
Update: Doh! I found a bug that I introduced into this no audio boost version. Seems that I broke music playback O_O. I fixed it and updated the above link. Sorry to those that download the other version -_- . . .

Audioboost is so necessary, i cant use any kernels without!

RinTinTigger said:
That was my result with linpack and this kernel!
Click to expand...
Click to collapse
t0ol said:
forgot to setcpu doh
44.738 mflops
upd.. and bootloop =)
Click to expand...
Click to collapse
nazrin313 said:
Tested on quadrant again and I got a whopping 1668...thats the highest ive seen my phone do...
Click to expand...
Click to collapse
Interesting observation you all are getting. Must be the combination of BFS and OC? But I would not be surprised if battery life suffers a little... But very cool nonetheless

[ZEN-KERNEL] 3.10-zen1 "Dollar Drink Night" (April 19)

{
"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"
}
The buck stops here
Project Background
This kernel makes things BETTER. Without tons and tons of over exaggerated fluff
"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 TEGRA/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 for desktop mobile 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, nor is there a need for strict NICE values.
The goal of the Brain **** Scheduler, referred to as BFS from here on, is to completely do away with the complex designs of the past for the cpu process scheduler and instead implement one that is very simple in basic design. The main focus of BFS is to achieve excellent desktop interactivity and responsiveness without heuristics and tuning knobs that are difficult to understand, impossible to model and predict the effect of, and when tuned to one workload cause massive detriment to another.
Click to expand...
Click to collapse
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/Tegra 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
support for tegra yield notifiers
What does this mean
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.
"How about the performance?"
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
USB Fastcharge Support
Fsync SysFS Interface
Overclocking support to 2.5GHz
FIOPS + BFQ in addition to the stock ROW, CFQ, Deadline, No-op I/O schedulers
Several misc upstream updates/fixes.
zRam support
@osm0sis AnyKernel2
---------
Releases
Wipe /cache before flashing for best results
DIRTY FLASH ROM FIRST!
If you have any issues or if you are coming from another custom kernel.
DIRTY FLASH ROM FIRST IF COMING FROM ANOTHER CUSTOM KERNEL
3.10-zen1 "Dollar Drink Night"
First Release/Features:
BFS CPU Scheduler by Con Kolivas. Backport from v461 and Alfred Chen's -gc branch ported to android/tegra 3.10 by me
BFQ + FIOPS I/O Schedulers in addition to CFQ (default), ROW, Deadline
Interactive governor sync'd up with ZenKernel_Shamu
EXT4 from v3.10.y
Several misc. memory leak, race condition fixes, etc. picked from v3.10.y
CPU overclocking up to 2.5GHz
Wake gestures from @flar2
MM+VM Changes from upstream v3.10.y
2A Charging Support
Fsync toggle support
3.10-zen1 AnyKernel Zip (Use for any ROM)
Legacy Releases
3.10-zen0 "Warranty Voided"
Changes:
This is just experimental
Make sure it works
Changes
3.10-zen0 AnyKernel Zip (Use for any ROM)
Thanks guys, and enjoy. Feedback is always appreciated.
XDA:DevDB Information
Zen Kernel, Kernel for the Nexus 9
Contributors
bbedward
Source Code: https://github.com/bbedward/ZenKernel_Flounder
Kernel Special Features:
Version Information
Status: Beta
Current Stable Version: 1
Beta Release Date: 2015-04-19
Created 2015-04-19
Last Updated 2015-04-19

this is untested + experimental.
I fixed a BFS suspend issue in my first test kernel and resolved f2fs issues.
This is here because somebody suggested it to me as the general section is not a good place to be.

AnyKernel zip uploaded

Love your kernel on the nexus 6. And I'm sure I'll love it on the n9!
Thanks man!

omvir said:
Love your kernel on the nexus 6. And I'm sure I'll love it on the n9!
Thanks man!
Click to expand...
Click to collapse
Thanks, if I didn't think -Zen was the best option then it wouldn't exist

I wanted to try this but I guess I'll have to wait till the official 5.1 is out. I'm still running stock ROM with a custom kernel so that puts me on 5.0.1.

time_shock said:
I wanted to try this but I guess I'll have to wait till the official 5.1 is out. I'm still running stock ROM with a custom kernel so that puts me on 5.0.1.
Click to expand...
Click to collapse
Doesn't matter, this is on stock 5.0 base. I use AnyKernel so it's probably compatible with 5.1 too

bbedward said:
Doesn't matter, this is on stock 5.0 base. I use AnyKernel so it's probably compatible with 5.1 too
Click to expand...
Click to collapse
I see why you thought this I just copy pasted my n6 thread
Made some changes.

bbedward said:
Doesn't matter, this is on stock 5.0 base. I use AnyKernel so it's probably compatible with 5.1 too
Click to expand...
Click to collapse
I bootlooped on AICP....went back to Fire and Ice.
Sent from my Nexus 9 using Tapatalk

So in daily usage, what effect should I notice after flashing this kernel? I read lots of your QA and such but still unsure.

Phantom Pt. II said:
So in daily usage, what effect should I notice after flashing this kernel? I read lots of your QA and such but still unsure.
Click to expand...
Click to collapse
I'm not even sure this 0 build works I may have to package an entire ramdisk and quit trying AnyKernel because of all the different 5.1 and 5.0 stuff going on here.
But the point is to add things that matter and things that make a difference. You probably don't care about having 3 alternative random number generators built in the kernel, or about having slightly more optimized memcpy/memmove operations. Not that those things aren't necessarily good, but what's the difference you'll notice with and without those - nothing on the other hand maybe you care about real performance and battery improvements, fast USB charging ,upstream stability, etc, etc.
This is where Zen comes in. Cut out everything except what matters. BFS helps me make a real difference in the performance and battery department.
How does it benefit performance? Well the stock scheduler has lots of overhead with 1 run queue per CPU, huge balancing algorithms, huge fairness calculation algorithms, many tunables. Stuff that's probably pretty essential if you have 64+ logical CPUs where you need to have the separate runqueues to avoid contention issues that come from such a setup. BFS chooses 1 run queue shared by all the CPUs. By design it is able to be fair without big balancing algorithms, interactive without focusing on countless priority calculations, and perhaps most importantly if you run 4 jobs on 4 CPUs it will keep those CPUs busy with a consistent load. On the stock scheduler they may tell you to run -8 or so jobs on a 4 CPU system to keep things busy.
You see a focus on a power-aware CPU scheduler lately as well. What they are doing to achieve that is keep jobs on the left most CPU cores keeping the other ones idle more. On BFS, these power aware things are not applicable because it requires no such load balancer. BFS uses sticky tasks to keep jobs on a CPU which aids in allowing other CPUs to idle more frequently. So when you see 1 CPU get busy 1 CPU will scale in the CPU frequency driver rather than unnecessarily scaling multiple CPUs after balancing.
Anyway, why doesn't google use it if it's so good - because it isn't mainline essentially. It will never go mainline unless they add a pluggable CPU scheduler interface (not in the foreseeable future) because it isn't applicable for a wide variety of systems (specialized for light-NUMA desktop type workloads). Google has had it in an experimental android branch before, but going so far away from mainline takes away a big aspect of support that you get from staying mainline (you get a bug and you can't rely on mainline support)
Why have no other kernels implemented it if it's so good? (They have now, since I brought it here and on the N6) probably because they didn't think it was worth the time to bring back the newest implementation to 3.10 or they didn't have the know how (the official 3.10 -Ck BFS patch is quite old, and broken with suspending - which is why I started the back port/sync process to begin with) so maybe others tried it and gave up.
Anyway the difference between a non-zen nexus 6 and a zen nexus 6 is a noticeable one. It's the only one I believe makes a noticeable performance difference (without over clocking or ramping up frequency scaling). Many claim it makes a noticeable battery difference too, without sacrificing touch boost or killing frequency scaling (in other words, it isn't making lag for better battery life)
Anyway enough rambling. Its coming here to the nexus 9 because I want to continue to support 2014+ nexus devices with my kernels and perhaps one or two other flag ships (I touched the S6 but there's one kernel per variant, their default config is incomplete, typical Samsung mess)
Also there will be a 100% free and open source GPL zen app. Which I think has a brilliant framework and a lot of potential. But that's limited by my time currently.

Let me understand this?
OK, bfs seem to be really smooth but what I'm trying to understand is that bfs is like i/o scheduler right?

AllanJacques said:
Let me understand this?
OK, bfs seem to be really smooth but what I'm trying to understand is that bfs is like i/o scheduler right?
Click to expand...
Click to collapse
No.
1.) I/O scheduler handles how requests to the disks (EMMC/Sdcard in this case) are served (order served first, etc.)
2.) The requests to get disk time are all coming from the CPU. (From the tasks getting CPU time)
3.) The CPU scheduler handles when, for how long, and how to serve the tasks that want CPU time. All factors considered such as keeping things fair between all the CPU cores, tasks that will do blocking due to an I/O wait or synchronization locking.
--BFS (Brain F*** Scheduler) is the CPU scheduler in (3). It is the only well-known replacement to the stock kernel's CFS (completely fair scheduler). I'm sure there have been others since CFS, but I haven't really heard about any. Some one and dones mostly.
What you are thinking of are the I/O schedulers which are completely separate, and only related to how requests to the EMMC/Disk are served. You and many are confusing BFS (Brain F*** Scheduler, CPU/Process scheduler) and BFQ (Budget Fair Queueing, I/O, disk scheduler)
See (both BFS and CFS are preemptive schedulers):
http://en.wikipedia.org/wiki/Scheduling_(computing)#Short-term_scheduling
http://ck.wikia.com/wiki/BFS

Got it!
One last question, BFS rr_interval can be tweaked? What does it do?

AllanJacques said:
Got it!
One last question, BFS rr_interval can be tweaked? What does it do?
Click to expand...
Click to collapse
You have millions and millions of tasks/processes going through the CPU in seconds.
Each task is waiting in line to be scheduled.
When BFS schedules said task, it is allowed to run for a maximum of RR_INTERVAL.
So by default at 6 (ms), a task cannot run for more than 6ms at a time. If it will take longer than that it will be "preempted" by another task, and will have to go back in the queue and wait until it is scheduled again (given a deadline).
If you raise it to 300, for example, a task will be allowed to be running for up to 300ms at a time. (Maybe a task has to wait for for disk time, which may take 100ms or something, etc.)
It is said that the lower value would mean lower latencies seen by the user, and a higher value would see higher thoroughput. 6 is default because it is determined the human eye can't detect jitters below 7ms. You can try lowering it/raising it. See what works best.

I used to always get battery drain on brain f kernels back in the day when it first came out. I look forward to any improvements since then.

dictionary said:
I used to always get battery drain on brain f kernels back in the day when it first came out. I look forward to any improvements since then.
Click to expand...
Click to collapse
The old implementations never sync'd up very well with mainline suspend/wake stuff. Since ~3.12 or so they have - and the one on this kernel (and the N6 kernel) do as well :good:

bbedward said:
The old implementations never sync'd up very well with mainline suspend/wake stuff. Since ~3.12 or so they have - and the one on this kernel (and the N6 kernel) do as well :good:
Click to expand...
Click to collapse
That makes me happy. Will report findings. Thanks again

Working well on CM 12.1 unofficial!
I know this isn't the kernels fault, its googles fault but the interactive governor tunables suck! Do you have any suggestions ? Can you work your magic? Currently its kind of stuttery!

omvir said:
Working well on CM 12.1 unofficial!
I know this isn't the kernels fault, its googles fault but the interactive governor tunables suck! Do you have any suggestions ? Can you work your magic? Currently its kind of stuttery!
Click to expand...
Click to collapse
I will sync it up with the same interactive of zen on the N6. Looks like the tegra version of interactive is a bit older.

[Kernel] Render Kernel][R1]

R1 is HERE!!!
Things to note:
I had been working on this release for some time now. About 3 weeks. I have been getting a feel for the n6 and where I think I can gain some optimization and not lose performance/battery. I use MSM_Hotplug as the default hotplug. I have tuned to to what I believe will give you just as fast an experience than with the Stock "All 4 cores online" MPDecision. Except I am keeping up this performance with only 2 cores enabled. I could not be happier with what I have been able to pull off. If you look through my source you will see that I have tried to piece together a cohesive kernel without just mass importing from another. My plan for this kernel will be to have one that is deliberately constructed and as lean as possible. I am going to aim at keeping out as much cruft as possible. Lastly, note that I do this work for myself first and for you all second. I work 2 jobs and have a family that comes first. I love Android Kernel development and ope to get others involved as well. Lets keep this thread interesting with development discussion and trials. Also, I am not against some OT as long as it doesnt devolve into baselessness and drama.
Kind Regards,
Render

Reserved

Welcome to Shamu!

Glad you finally made it bro.
Whole family is here now.

First Blackbird and now Render did I accidentally wander back into the G2 forum?

Same performance as all cores online with only 2? Alright I certainly have to try this out to see if that could be the case.

RENDER!? Here on the N6? You made the G2 another beast. I love Hydra Kernel but I'm really glad to check this out.
Good to see you again man.

TransportedMan said:
Same performance as all cores online with only 2? Alright I certainly have to try this out to see if that could be the case.
Click to expand...
Click to collapse
Please do and let me know!
Now to hedge my bet a little, we all know if I were multi-tasking, of course running 4 cores is always better than 2. What I am talking about is the User Experience (UX). The UX is comparable to using the Stock Hotplug driver but I am using Neobuddy's Modded MSM_Hotplug. That coupled with other changes I have made around the kernel allow me to use 2 cores as long as you are touching the screen, 1 core only after a certain amount off time when you stop touching the screen. Of course when you open an app or do something intensive like that, the 3rd and 4th core can/will online to accommodate the extra load till the load is below a certain threshold and then the normal 2 cores online while touching the screen algorithm kicks back in. Using this setup allows for a smooth UX while keeping battery drainage to a minimum but is able to scale properly when the need kicks in.
So what this means to those of you that do not understand the above, this kernel is battery conscious and smooth while scrolling and browsing and will kick into overdrive when needed like during gaming and other heavy, intensive processes like using Titanium Backup.
This is why I like to balance different changes in the kernel to make sure the UX is not messed with. Just remember, I run my own kernel and it would drive me nuts if there was needless lag all over the place!
bleached45 said:
RENDER!? Here on the N6? You made the G2 another beast. I love Hydra Kernel but I'm really glad to check this out.
Good to see you again man.
Click to expand...
Click to collapse
Hey! Glad to be here. I have been wanting to get a phone that uses the newer 3.10.x based kernel and could not pass up the great deal I got for my N6! Also, I too really enjoy Neobuddy's work and you will see many things that I use of his. We share alot of the same Design goals I believe so there will be some things that will feel familiar and some that will be new.
But I could have kept making more and more changes to the current kernel and decided that I had to release now or I never would anytime soon. I need more ppl to test my kernel and there is no better way than releasing it to the wild!

What a reminder of the good old days of the G2.
Your purchase of the N6 means we will really get the max out of our N6 as well.
Welcome to this great community.

Hi Render
Welcome to the N6 family
Kernel is fantastic, great battery
But is this normal on the screen?
Thanks in advance
And enjoy the time here :good:

danmaman said:
Hi Render
Welcome to the N6 family
Kernel is fantastic, great battery
But is this normal on the screen?
Thanks in advance
And enjoy the time here :good:
Click to expand...
Click to collapse
Thanks!
Yes, that is supposed to happen. Those two SYSFS's are not present in my kernel because they did not work anyways. Our sound driver doesnt allow for us to make changes to those variables. Now, the reason you see the error is because Synapse back end sees that we are using Faux's Sound Control and expects all 5 SYSFS entries to be there when infact there are only the 3 that are really used.
Same with Franco's. I just modded the OG Sound Control driver to remove the unneeded cruft.
Thanks for the report! Glad to clear that up.

RenderBroken said:
Thanks!
Yes, that is supposed to happen. Those two SYSFS's are not present in my kernel because they did not work anyways. Our sound driver doesnt allow for us to make changes to those variables. Now, the reason you see the error is because Synapse back end sees that we are using Faux's Sound Control and expects all 5 SYSFS entries to be there when infact there are only the 3 that are really used.
Same with Franco's. I just modded the OG Sound Control driver to remove the unneeded cruft.
Thanks for the report! Glad to clear that up.
Click to expand...
Click to collapse
OK no problem... I understand
Now I'll do a full charge, and let's see how the kernel runs :good:
Thanks a lot

One of my favorites on my vs980 LG g2, glad to see it on Shamu! I'll be testing this with mokee later today, if I can wait that long.
Also, is it against the rules to ask you to add a patch?
I use my Nexus 6 as a keyboard for my server computers to navigate through BIOS settings, I use an app called "USB keyboard". But the app needs this patch to run here

noidea24 said:
One of my favorites on my vs980 LG g2, glad to see it on Shamu! I'll be testing this with mokee later today, if I can wait that long.
Also, is it against the rules to ask you to add a patch?
I use my Nexus 6 as a keyboard for my server computers to navigate through BIOS settings, I use an app called "USB keyboard". But the app needs this patch to run here
Click to expand...
Click to collapse
Hey! Glad to see you here. And, no, its perfectly fine to make a request. I will always consider them and if it makes sense, I will make the changes requested. Also, that was something I was going to merge in anyways! I will go ahead and queue it up for R2.

Hello,
Thank you for this release!
The default settings are ok for day-to-day use please? Or is it better to set everything up myself? (im not very familiar with synapse and that UKM thing). If something really needs to be set up by user i would use Kernel Adiutor.

Droidphilev said:
Hello,
Thank you for this release!
The default settings are ok for day-to-day use please? Or is it better to set everything up myself? (im not very familiar with synapse and that UKM thing). If something really needs to be set up by user i would use Kernel Adiutor.
Click to expand...
Click to collapse
I actually use Kernel Aduitor myself. I have not updated my UKM in awhile. It looks like I will be needing to make some changes to make it compatible with SHAMU. Also, of course the default settings are good. I think only a few things were left out when I released. One being setting the default gov to Interactive. It scales better than SmartMAX imo. Also the Min and Max Freqs were not set to stock like I want the default settings to be. I cannot remember anything else but even with those things missing, the kernel runs freaking great. I am really excited for the future of this kernel.
ATM, I am getting 1.5 Hours SoT per 25% but that is also with using wifi 100% of the time and Bluetooth connected to my headset listening to music and audiobooks all morning. This measurement was about 5 hours of use. I have listened to about 3 hours of music/audiobooks and have been connected to wifi for about 3 hours. I am what I consider a moderate to heavy user. I also use my phone for work so I have 3 email accounts syncing along with their calendars (I have two jobs). So all in all, I am pretty impressed considering I have the settings setup to be smooth without sacrificing performance and battery too much. What is the point of having such an awesome phone if you deal with lagging and stuff. I will alwasy opt for a smooth UX while building this kernel. I assume everyone can at least get to a charger at the end of the day so I am not too worried about making a marathon build. But I am sure you can tune this kernel to be one though. More features are incoming that may help.

Droidphilev said:
Hello,
Thank you for this release!
The default settings are ok for day-to-day use please? Or is it better to set everything up myself? (im not very familiar with synapse and that UKM thing). If something really needs to be set up by user i would use Kernel Adiutor.
Click to expand...
Click to collapse
Hi mate
i use the default settings with smartmax....and i'm happy with it:good:

Hi,
Thanks all! Will flash and keep setting as they come.

Droidphilev said:
Hi,
Thanks all! Will flash and keep setting as they come.
Click to expand...
Click to collapse
:good::good:
I only changed vibration... That's it

[KERNEL][AOSP][AnyKernel] Gamma Kernel for D855/D852/D851/D850/VS985/LS990

{
"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"
}
DESCRIPTION
This is a custom based Kernel for the D855/D852/D851/D850/VS985/LS990 variants of the LG G3 with performance enhancements and bug fixes that I have been using personally for a few months, thought it is time to share since I have had no inconvenient bugs and quite a big performance increase and smooth UI benefits. The intention is to have a minimal light-weight kernel that is fine tuned for the device.
FEATURES
User space voltage control
Backport MSM devfreq features from 3.18 Kernel for the smoothest experience, includes adding cache fabric frequency scaling and better bus utilization as well as the mincpubw governor
User space display color calibration (KCAL)
Deeper memory controller power savings on suspend (deeper power savings while sleep)
Two new L2 cache frequency steps: 1.88 & 2.03 GHz, allows for better multi-core utilization and hit rates
Wireless roaming disconnecting is now fixed
IRQ Balancer enabled with proper SELinux support to spread out the interrupts of our SoC
IntelliPlug to allow lower thermal dissipation by keeping some cores alive to distribute loads and keep frequencies lower accross SoC die
Reduced heat when using wireless chargers
Memory and cache subsystem optimizations, you will feel it int the UI
Adreno Idler to get better GPU frequency utilization and battery life [removed as msm-adreno now idles properly]
Interactive governor tweaks to focus on lower frequencies while still maintaining fluidity in the UI
BFQ IO scheduler set by default to avoid slow-downs on task intensive scenarios
No overclocking was chosen to avoid unnecessary heat, optimizations were focused on other different areas
Kernel Samepage Sharing enabled with deferred timer by default to gain some memory usage optimizations
Compiled with GCC 6.x optimized toolchain and -O3 plus other hardware specific flags
Undervolted the Adreno 330 GPU voltage rail to keep things cooler, and reduced the GPU min frequency to 27 MHz while keeping it's temperature cool to reach 620 MHz overclock
Default thermal values work ok, since GPU voltage rails and others were shaved a few mV
100 Hz tick to prevent excessive battery usage, the smoothness of the UX does not come alone from raw processing -- there are many other changes in the subsystem that helped achieve the fluidity
An ultra low value in the interactive min_sample_time so that the interactive governor does not hover on excessive frequencies
Heavily tuned the GPU bandwidth and bus requirements to match closer the capabilities of the device and thus preventing micro-stutters
Optimized the MSM crypto engines thanks to @waau
Updated the KGSL drivers so that we can use the Adreno userspace drivers version Adreno-MOB30M-for-LG-G3-AOSP.zip
DOWNLOADS
AnyKernel: Click Here (Check Top of the Post, Download Tab)
SOURCE
D85X-Kernel-Gamma GitHub Source
NOTES
I recommend turning NFC off for way better idle battery consumption :victory:
KNOWN BUGS
FM Radio is causing hangs, still needs investigation
<< If you like my work here is my hat, please donate! >>

XDA:DevDB Information
Gamma Kernel , Kernel for the LG G3
Contributors
Omar-Avelar
Source Code: https://github.com/oxavelar/D85X-Kernel-Gamma
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 90.0.0
Stable Release Date: 2018-05-10
Created 2016-08-09
Last Updated 2018-05-13

Thank you for this kernel, I have a question:
Fast charging is implemented?
Thanks again

@Omar-Avelar Download link for d855 leads to d851 version and vice versa..
Sent from my caseless LG G3, because I believe in myself

Is there a sound mod for headphone gain?

download link need to update, will try it and report.
THANK YOU!!!!!

after instelling the kernel on my d855 with the xenon rom it doesnt charge via usb in the pc... i am at work right now and cant check in the wall socket.

@agdish84, I have now updated the links, thanks... I missed that.
Hey @jochem86, USB charging is working on CM ROM's so I wonder if Xenon ROM is doing anything funky, mmm... I will check if Xenon has anything strange but it is not touching anything charge related.
This Kernel does not support USB force fast charge because fast charging will cause batteries to age faster. It's a trade-off, and usually ends up providing more heat. Not sure if I will put support on forced USB fast charge or not.

Omar-Avelar said:
@agdish84, I have now updated the links, thanks... I missed that.
Hey @jochem86, USB charging is working on CM ROM's so I wonder if Xenon ROM is doing anything funky, mmm... I will check if Xenon has anything strange but it is not touching anything charge related.
This Kernel does not support USB force fast charge but might do add it in the week if a lot of people feel the need of it. [Btw, personally this is the main reason why I did not enable fast charging enabled sysfs force control - URL]
Click to expand...
Click to collapse
Dirty flashed the xenon again and it charges again without any problem. I have to say some other roms it doesnt charge in usb when i am using it... with xenon it doest but very slow, that is normal. But also in deep sleep, it doenst charge a bit... i guess in xenon the fast charge is enabled and other roms not bu default. i hope you figure out whats messign it up.

jochem86 said:
Dirty flashed the xenon again and it charges again without any problem. I have to say some other roms it doesnt charge in usb when i am using it... with xenon it doest but very slow, that is normal. But also in deep sleep, it doenst charge a bit... i guess in xenon the fast charge is enabled and other roms not bu default. i hope you figure out whats messign it up.
Click to expand...
Click to collapse
Thanks for the update, and do let me know how do you feel this Kernel in terms of performance against the others you've used. It doesn't have to be immedeatly, use it for a while and give me some feedback on things you see are working good too, thanks a lot

Omar-Avelar said:
Thanks for the update, and do let me know how do you feel this Kernel in terms of performance against the others you've used. It doesn't have to be immedeatly, use it for a while and give me some feedback on things you see are working good too, thanks a lot
Click to expand...
Click to collapse
That was my intention to give you my experience but my batt was pretty low so i changed it back to stock kernel... as i am on my work right now but for those few minutes i tried it felt pretty smooth.

Omar-Avelar said:
Thanks for the update, and do let me know how do you feel this Kernel in terms of performance against the others you've used. It doesn't have to be immedeatly, use it for a while and give me some feedback on things you see are working good too, thanks a lot
Click to expand...
Click to collapse
In terms of performance? Oh yes, give me time to flash CM13 and test UI smoothness, I have feeling this is right thing for that. Waiting for this for a long time.

@Omar-Avelar do you have any plans on adding gamma control? I'm really enjoying myself atm running it with Zephyr os rom. Ty for your hard work!
Sent from my caseless LG G3, because I believe in myself

AICP booted, the 10 seconds I have had it on it seems really snappy, will let you know how it goes.

stuck on splash screen after installing...
D855 32GB - Fullmics ROM

grymmy said:
stuck on splash screen after installing...
D855 32GB - Fullmics ROM
Click to expand...
Click to collapse
Fulmics is stock based from what I have read (I've never installed it personally). But I am glad to hear that you tried it out there but too bad it doesn't work on Fulmics!
I will add some notes to the thread to let other people know.

Jagdish84 said:
@Omar-Avelar do you have any plans on adding gamma control? I'm really enjoying myself atm running it with Zephyr os rom. Ty for your hard work!
Sent from my caseless LG G3, because I believe in myself
Click to expand...
Click to collapse
I think I will do that, it might be about the only things that are do needed and won't interfere as much with stability. Gimmie a few weeks to get some free time.

Omar-Avelar said:
Fulmics is stock based from what I have read (I've never installed it personally). But I am glad to hear that you tried it out there but too bad it doesn't work on Fulmics!
I will add some notes to the thread to let other people know.
Click to expand...
Click to collapse
thank you for such speedy feed back. I'm about to install Zephyr os rom and test...thanks again

Using this kernel made me love my phone again. Was using Latest CM 13 and UI was time to time laggy and slow. Flashed this kernel and device runs smooth as butter. Love that kernel does not overclock anything so i know that i don't shorten life span of my cpu. Kudos to @Omar-Avelar for developing something like this!

Could you add DT2S and DT2W on your kernel?
#ParanoidAndroid

Phone heats up a lil while charging... Didn't use it or anything, just picked it up to see the time and it felt rather warm to me, using zephyr rom and a lil undervolting. Btw, during regular usage phone is stone cold, kudos!
Sent from my caseless LG G3, because I believe in myself

[KERNEL][MM/N][Kettle - 6th Feb] The LateAutumn Project

{
"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"
}
Hi all, its been a while LA went public, and thanks to you all, it received good responses. So I thought, it's time to revamp the intro.
First of all, like all other great(Linux) things, this kernel also falls under FSF's GPL(General Public License), which is probably the most comprehensive open source license till date. I just wanna quote two agreements from the license :
Code:
[SIZE="2"]15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.[/SIZE]
A few months ago, we've had a burst of mods and kernels, and some great kernels took birth on the occasion. They all offered great flexibility of customisations, and a whole lot of other features. They were great no doubt, however with great choices comes great confusion. So I thought to come up with a kernel which will include the bare minimum customisations and fit(as close as possible) to all type of users, giving a good balance between stability and performance. Which won't hesitate to go to the extreme limit when the situation demands, but will stay right in the middle in most others. And so, I decided to bring my own kernel, the LateAutumn.
It's probably pretty late, but it's probably the most beautiful till date.
I won't say anything more.
Try it, and say yourself.
Features :
CPU overclocked to 1.8GHz
GPU overclocked to 720MHz
Stock Lineage source (**requires confirmation from @nicknitewolf**)
SELinux permanently Permissive
Adreno Idler ( enabled by default )
Faux Sound Control 3
MSM Hotplug ( disabled by default )
Various wake gestures
- DoubleTap2Wake ( disabled by default )
- Sweep2Wake ( enabled by default )
- Sweep2Sleep ( enabled by default )
kexec-hardboot patched
Compatible with all N ROMs
Checkout the downloads tab for Version 5.1.1 Kettle!
XDA:DevDB Information
LateAutumn, Kernel for the Xiaomi Redmi 2
Contributors
iamsubhranil, ketut.kumajaya, ashish94, codeharuka, premaca
Source Code: https://github.com/iamsubhranil/android_kernel_wingtech_msm8916_lineage
Kernel Special Features: All overclock, Incredible balance
Version Information
Status: Stable
Current Stable Version: 5.1.1
Stable Release Date: 2017-02-06
Current Beta Version: 2.2.6
Beta Release Date: 2016-09-28
Created 2016-09-25
Last Updated 2017-02-06

Reserved
Version 2.0 Beta - 26/09/2016
Stock CM source
OC CPU to 1.8 GHz and OC GPU to 720 GHz
Version 2.2.6 Beta - 28/09/2016
Adreno Idler added
SELinux policy set to Permissive (permanently)
Added USB fast charge and enabled by default
Added more generalized flashing method
Version 2.3.2 Stable - 29/09/2016
SELinux is now Permanently Permissive
Added Mako Hotplug and set as default
Improved stability and performance largely by tweaking various parameters
This update however, disables MPDecision permanently from the first boot as a fail-safe. As long as the kernel stays, you're "forced" not to use MPDecision, as the tweaked balance between CPU-Hotplug will be lost and overall performance may decrease. You can however, enable MPDecision after renaming mpdecision.bak in /system/bin to mpdecision and flashing another kernel before next boot. If you still feel the need to use MPDecision, please vote above. Thank you for understanding.
Version 2.4 Stable - 03/10/2016
Added MSM hotplug and set as default
Add Westwood TCP/CA and set as default
Because a lot of people reporting lag after the Mako build, I encourage everyone to flash this build and report back. Thank you.
Version 2.5 Stable - 19/10/2016
Added FauxSound 3 and enabled by default
DT2W is still a WAP. Stay tuned.
Version 3.0 Stable - 20/10/2016
Added DT2W and enabled by default!
Latest CM updates
Version 4.0 Grey - 20/10/2016
LA is now N compatible
N build is up. Perfectly compatible with all N (CM) ROMs out there. This is the first CM custom kernel to support N out of the box. That means enjoy the versatility of N with the stability of LA.
But wait, did I just say "N build"? My bad. There's no "N build" as such because it is the same kernel that supports both N and M ROMs at the same time. It is your LA. Just ready for a new home, along with the old one.
From this build on, LA will contain a codename, preceding with the n-th letter, which will specifically be a late autumn or winter item, here n denotes the release number.
So what are you waiting for? Flash it now and leave your comments about how can the kernel be made specifically for you. It's my kernel, in your way.
Version 4.1 Heat - 29/11/2016
Latest CM updates
kexec-hardboot patch enabled
For all the people wanna know about this stuff, it is basically done for the sake of MultiROM. This process goes deep into low level access of RAM and memory, but at the bottom line, what it does is loads another kernel into RAM at runtime(kexec), initiates a full reboot(hardboot), and jumps to the new kernel code directly from the RAM in the next boot. For the people who aren't using MultiROM, no worries.
Version 4.2 Iceberg - 07/12/2016
Implemented KCAL support
Sorry for the long wait. Got studies and stuff. Thank you for your patience.
Version 5.0 JackFrost - 07/01/2017
Completely rebased to LineageOS source!
A very happy new year guys ! And what is the more perfect way to start a new year than with something completely fresh, completely new? LateAutumn is now completely rebased to LineageOS source, with a more cleaner build than ever. You'll get all the same degree of performance that this kernel has made you used to, along with a higher degree freedom, higher degree of stability, and the breeze of something completely new. Which means you have now more less reasons to worry about, more reasons to live. Work, play, refreshment? That's all this new year's about.
Version 5.1.1 Kettle - 06/02/2016
Compiled with Linaro 4.9 toolchain
Latest Lineage updates
The headphone jack may still be broken. Send logs, and I'm doing something about it.
Disable any "Apply on boot" parameters in apps like Kernel Adiutor and try the default settings first. If you're still not satisfied, go apply any parameters after boot.
For downloads, please check the downloads tab.
Before use, disable everything in Settings=>Developer options=>Hardware Accelerated Rendering

Reserved
I'm overwhelmed to see your responses, queries and feature requests. But hey, XDA already has three good places to do so.
For requesting a feature, use this template
For review, use this template
For submitting errors and more preferably bug reports, use this template

Sounds great,i test and report soon for sure,Greeetz!

Can't eagerly wait for this kernel btw ?
Sent from my 2014813 using Tapatalk

It will surely drain the battery in an hour and might heat up to much... But good to see an fully overclocked Gpu nd Processor... Would like to take benchmarks.... Good work

anandmore said:
@iamsubhranil, there is no download tab here.
Click to expand...
Click to collapse
My bad! Check out now.

Riyanx55tu said:
It will surely drain the battery in an hour and might heat up to much... But good to see an fully overclocked Gpu nd Processor... Would like to take benchmarks.... Good work
Click to expand...
Click to collapse
Sadly, none of this happening at my side. But can't wait to see the actual scenarios :fingers-crossed:

will you consider to build for MIUI 8 5.1 with F2FS support?

OrGiMaSu said:
will you consider to build for MIUI 8 5.1 with F2FS support?
Click to expand...
Click to collapse
Nice proposal. Will keep it in my to-do lists. But please don't ask for any ETAs.

Will you please consider doing a 1.4ghz oc build too? Like we have seen in berzerk kernel.
Thanks

deleted

X.lord said:
Will you please consider doing a 1.4ghz oc build too? Like we have seen in berzerk kernel.
Thanks
Click to expand...
Click to collapse
I can't see the point of it. It already has 1.8. One can easily limit that to 1.4 using any kernel app he wants. So no, i won't consider that.

Thanks for your efforts
Any recommended settings for battery life?

iamsubhranil said:
I can't see the point of it. It already has 1.8. One can easily limit that to 1.4 using any kernel app he wants. So no, i won't consider that.
Click to expand...
Click to collapse
Yes i know that was a dumb request to make but @Ashish94 maintained two seperate builds 1.4ghz and 1.8ghz so i just thought maybe you can do that too. Nevermind
Btw its great to see a new kernel for our device.

Saurabh_Umadikar said:
Thanks for your efforts
Any recommended settings for battery life?
Click to expand...
Click to collapse
First test and tell if there's any affects in battery life
I'll however, as i have said in the OP, include any modification that'll unleash the best without giving a ball of fire in our hands

Feature request: can you make this kernel permissive like berserk please? many of us out there having trouble with viper4droid and other things and after every reboot turning the enforcing to permessive is a pain. I am using your kernel underclocked to 1.4 ghz and 400 mhz, while turning it up to 1.7 ghz when heavy tasking, having no trouble/ battery issues.
To other folks, if you are having battery issues, underclock your device and use 1.8 when only needed.

Would like to wait for miui lp build!

I've been using this kernel for a few hours and its working very well.. everything seems nice and smooth:good:
a liittle bit more battery drain while doing intense tasks as compared to stock cm13 kernel, but hey its OC at 1.8ghz so nothing much to complain.. Just one thing to take care of, selinux enforcing is breaking sound mods as some sound mods require selinux set to permissive by default.
Good job dev.

Two questions. Have this kernel msm hotplug? No problem with playing songs with latest builds of CM?

Better Mobile App

welcome