[Kernel] Render Kernel][R1] - Nexus 6 Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
for CM13.x and Android 6.x​
Code:
/* *** Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* BOOM goes the Dynamite
*/
I am releasing this kernel because I like to share my work and have had requests to do so and, lastly, because we needed yet another kernel released for our beloved N6! I started out at XDA because I wanted to learn and share what I have learned. My goal with this kernel is to be a very fast and stable build that offers some things that the other kernels do not. I also want to initiate Development Discussions among the community. This will be a noob friendly thread as long as users follow two rules. First is to do some research before asking. Most likely your question has already been asked. If not in this thread then in another. Remember to always search first! Second is BE RESPECTFUL. You do these two things and even the most hardened Dev will assist you.
Wanna be notified of an Update? Here is my PushBullet Channel!!
https://www.pushbullet.com/channel?tag=renderkernel
Current Features
General List:
* Linux 3.10.102
* Built with Custom Built HYPER Toolchain 4.9 from @frap129
* NEW State_Helper by @neobuddy89
* MSM_Limiter by @neobuddy89 - More like a Swiss army knife! adds Per-Core Functionality!
* State Notifier Driver by @neobuddy89 !
* Govs - SmartMAX, ElementalX
* IO Scheds - FIOPS, ROW, DEADLINE, NOOP, and ZEN Schedulers
* Franco's Sound Control
* Complete Color Calibration Thanks to @savoca
* USB Fast Charge (ON/OFF Toggle)
* New LZ4 Compressor/Decompressor: Just plain fast!
* F2FS Support
* Simple_GPU_Algorithm from Faux!
* Added Sysfs for GENTLE_FAIR_SLEEPERS ARCH_POWER
* Quick Wakeup
* KEXEC Support (MultiRom)
* Power Aware Scheduling
* Voltage Control
* Wakelock Control - Kernel Aduitor ONLY for now
I recommend Synapse combined with UKM for Kernel Tuning
Synapse Play Store Link
Render-UKM
Download:
Kernel Downloads
Instructions:
* Boot into Recovery
* (Recommended) Make a complete backup of everything!
* Flash Zip
* Reboot
THANKS!!!!
First I want to say thank you to everyone who has answered my questions and responded to my pm's when I know they are busy with their own lives. Pretty much everyone I have come into contact with here on XDA has been truly helpful and respectful. Here is a list of people that had helped me in one way or the other:
Neobuddy89, ak, myfluxi, Dorimanx, Savoca, Faux123, DespairFactor and Many More!
Thank you guys! Without your contributions to the community we would not have the level of performance, stability and interaction that we have today
Special Thanks!
Donators: @nfin1te, @MrDarkKV, @V1TRU, @Really now @erad1
XDA:DevDB Information
[Kernel] Render Kernel][R1], Kernel for the Nexus 6
Contributors
RenderBroken, rignfool
Source Code: https://github.com/RenderBroken/SHAMU-kernel
Kernel Special Features:
Version Information
Status: Testing
Current Stable Version: R3
Stable Release Date: 2016-04-12
Created 2016-02-28
Last Updated 2016-12-07

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

Related

[ROM][5.0.2] Beanstalk 5.0050 [Lollipop][Jewel] 3/24

Beanstalk 5.0.XXX for HTC EVO 4G LTE
Source: https://github.com/scotthartbti
Please thank scott.hart.bti who is the creator of Beanstalk ROM and the Cyanogenmod Team whose work is the base of this ROM!
{
"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"
}
Changelog​
Kernel Source
Downloads
Beanstalk Build Folder ​
XDA:DevDB Information
Beanstalk Lollipop Jewel, ROM for the Sprint HTC EVO 4G LTE
Contributors
fizbanrapper, scott.hart.bti
ROM OS Version: Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: HBOOT 2.10+, Captain Throwback's TWRP 2.8.1.0
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-01-01
Last Updated 2015-03-24
Reserved
Notables
Quirks
No boot animation
Bugs
Reserved
Kernel_Time (preview)
I'm currently developing a Lollipop custom AOSP kernel for the Jewel. Kernel_Time will not be its name once it's actually released. This is just a taste of what's in store. The link above is sourced from CM, but cross-compiled with Linaro 4.9.3 optimized for Cortex A15. The difference is like night and day, with just that one change.
I've added quite a bit to the kernel already, but am not going to release it until I've added more features (Publishing the kernel source is required for GPL compliance, and it's more of a pain for me to make changes once I've published the source). Waiting to release the kernal also gives me a chance to test each feature and governor on my device to make sure that they work.
If there is a kernel feature you'd like to see in the release version, if it's not on the list of added features or features on deck, please respond and there's a decent chance I'll add it.
Features added already
Sweep2Wake
SweepUp2Wake
Double tap to wake
Force fast charge
Voltage control
CPU Governors
wheatley
pegasusq
intellidemand
intelliactive
lagfree
badass
smartmax
interactive
conservative
ondemand
userspace
powersave
ondemand
performance
GPU Governors
performance
ondemand
simple
interactive
conservative
IO Schedulers
noop
deadline
row
cfq
bfq
sio
fiops
zen
TCP Congestion Control
cubic
reno
Optimizations
LZ4 Compression-Decompression
-Wstrict-aliasing=3
Features on deck
Sweep2Sleep
Optimizations
Considering adding -f-strict-aliasing if the situation is all gain. Not willing to sacrifice stability or features for it.
IO Schedulers
none on deck
CPU Governors - None - Lots added already. Let me know what others you'd like to see though!
GPU Governors - None - I haven't experimented with them much myself, so give me your list.
TCP Congestion Control- None - Give me your list.
Current issues
Though the kernel is at least as stable as CM's (as as of this writing), there are some bugs in a few features.
Can't always save voltage modifications
Sweep2Sleep doesn't work at all
Pocket detection is supposed to keep the device from waking in your pocket, but doesn't currently work.
HTC Logo feature references need to be removed as it isn't part of the touchscreen on the Jewel. Those features will never work on this device.
希望这个rom越来越好
Nice. I'll try and flash this in the next couple of days.
Don't burn yourself out, bro. But damn if you're not bringing forward all of my favorite roms.
Would like if the kernal would allow 2 way recording of phone conversations by way of mic and earpiece instead of by using speaker if possible......thanks...nice work your doing.
Garros said:
Would like if the kernal would allow 2 way recording of phone conversations by way of mic and earpiece instead of by using speaker if possible......thanks...nice work your doing.
Click to expand...
Click to collapse
Is there a custom kernel out there that has this feature somewhere (of course it would be a different device)?
I'm considering releasing the kernel. Ideally I'd get some help with the code, but I honestly don't know if there is any interest here from anyone who is capable of assisting.
Does anyone want to assist with the kernel that can collaborate via github? Anyone know how to use pull requests etc?
I had made a lot of progress on the kernel, but had to undo a lot. I spent a lot of time trying to fix the code to get O-3 optimizations working, but it make the kernel less stable. I've reverted those changes and am now trying to focus on sweep2wake and double-tap to wake. I was hoping to get those things working before releasing the kernel, but that's been difficult so far.
Here is the thread about the kernals that work. Some HTC and Nexus 6 I believe....thanks for considering it....
http://forum.xda-developers.com/showthread.php?t=1441643
Garros said:
Here is the thread about the kernals that work. Some HTC and Nexus 6 I believe....thanks for considering it....
http://forum.xda-developers.com/showthread.php?t=1441643
Click to expand...
Click to collapse
Thanks. I'm reassessing how to go about things. I started off by forking cm and adding features from there, but after spending over a hundred hours on it, done of the features still don't work quite right.
So I put that on the back burner for a while and tried to just fix bubba kernel and go from there, with frustrating results.
I'm still working on it, but have no idea when I'll have something to release. If I could figure out how to fix the bugs in voltage control, I'd feel ok with releasing the cm-forked version. If I could get Wi-Fi working, I'd release the bubba-forked version. It's really a matter of which I can fix first.
the 2 of latest update give me no boot at all.. kernel is fine.. i use the kernel on cm12 nightly n running smooth and battery friendly..
Thanks for keeping the Jewel alive a little longer.
I mentioned earlier in one of your kernal threads about the ability to record phone conversations without having to use the speaker. The below ROM/kernel records good from just the phone line, I think it is 4.3 on new partition layout for the jewel. Could this be used or would it be helpful for a 5.02 ROM?
Thanks again...
http://forum.xda-developers.com/showthread.php?t=2528953
Garros said:
Thanks for keeping the Jewel alive a little longer.
I mentioned earlier in one of your kernal threads about the ability to record phone conversations without having to use the speaker. The below ROM/kernel records good from just the phone line, I think it is 4.3 on new partition layout for the jewel. Could this be used or would it be helpful for a 5.02 ROM?
Thanks again...
http://forum.xda-developers.com/showthread.php?t=2528953
Click to expand...
Click to collapse
Thanks. I'm doing my best, but it's getting harder by the day. Unfortunately that thread doesn't help. It's a ported ROM, so no sources have been published, and it's a Sense ROM, so it would not have been AOSP compatible even on 4.3. The feature is on my list, but there are a few other things I want to fix first.
This is a good opportunity to update the handful of people out there who are still using this phone. I purchased a new build machine a few weeks back. I set things up and got a few ROMs out, but then I started having problems. I was running the machine through a remote desktop connection from windows 7 to windows 7. On the build machine, linux was configured through VirtualBox. I started having strange issues, and then it stopped working altogether. Around this time I made the realization that building via VirtualBox will always limit me to only building with 4 of my processors 8 cores, so I decided to change directions and go back to dual boot.
Yesterday I installed the linux distro. The tough part is configuring the remote session properly. I want to have the same UI as if I were running the machine locally. Once I get that done, I'll be cookin with gas.
Via VirtualBox, my ROM compilations were as low as 12 minutes (prebuilt chromium, after running make installclean). I was only running on 4 cores due to the VB limitation. I also realized that my SSD was connected to a SATA2 port instead of a SATA3 port, so I fixed that. That increases the upper limit from 3 GB/s to 6 GB/s. Tonight I'll be doubling the memory too (RAM should arrive today in the mail). I'm really curious what my build times are going to be after doubling the number of cores, amount of memory and the transfer rate of my SSD. I'll have to sync all of the repos again, but that shouldn't take long with a 105 Mbps connection.
After I've got everything set up, the increased speed should allow me to spend a lot more time on building features and correcting problems. I can't fix anything while I'm sitting there waiting for my machine to get done compiling something for me to test.
PAC-ROM looks like it will be available in just a few weeks or maybe even days. I've been successfully building pre-alpha versions and they've been working well, so expect to see that as another ROM option in the near future.
Sent from my LG-D855 using XDA Free mobile app
fizbanrapper said:
PAC-ROM looks like it will be available in just a few weeks or maybe even days.
Click to expand...
Click to collapse
I like the sound of that. PAC is my primary.
I posted a new build. Everything works great except no boot animation. I know what the problem is and I'll be fixing that soon. With the camera issues in Bliss, I think this will be what I run on a daily basis.
Also posted a new Bliss build. Bliss camera status unfortunately, is unchanged.
I'm working on a LiquidSmooth build too. PAC-man will be coming soon, and there are a few other things I'm experimenting with too.
Sir I have high respect for you. My Evo 4g lte decided to disable itself to me back in August last with the screen not lighting up. About the beginning of the year I decided to see if the thing even decides to turn on and to my dismay the screen lit up. Since then I've been keeping up with the latest of Android on this phone and I appreciate the time that you've been putting this phone into relevance. I do believe with the success the Moto G has been having that this phone can have the same chance having relevancy almost having somewhat the same specs and persuade others to keep rocking this phone. If it wasn't for my personal phones discrepancy, I would still be rocking this phone as a daily but alas at the time I moved on to a Nexus 5. Rarely do I post something seeing as I don't post catlogs or anything substantial that isn't obvious to the devs but three years removed for this phone I feel like standing up for it.
I was having build issues for quite a while and just noticed yesterday that the my roomservice.xml got written over, but was missing the vendor blobs, so the ROM wouldn't boot. All is well now... well except for the missing boot animation, which has always been a problem with Bean since the move to LP.

[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?

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

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

[D85X][F400][LS990][VS985][NOUGAT->7.1][OREO->8.0] Solid Kernel V2.56 [05/08/2017]

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Solid Kernel aims to be a stable, minimalist and powerful kernel for everyone, no extreme overclock or experimental things that may affect your device health.
Reworked GPU Drivers
Bricked HotPlug
FIOPS Scheduler
CPU Voltage Control
Uber 8.0 Toolchain
FSync On/Off Support
XZ Algorithm Compression
USB Mouse/Keyboard Patch
KCAL Post Processing Drivers
Simple Sound Control
EXFAT & F2FS Support
USB Fast Charge Support
Simple Thermal Driver
Custom CPU-BOOST Solution
27MHz GPU Clock
Dynamic GPU Governor
Permissive SELinux
PowerSuspend V1.7
GPU Min-Max Governor
/dev/frandom Support
PAY ATTENTION : My kernel is really minimalist so don't expect to have a lot of governors or things like that.
If you like my work then consider to buy me a coffee, it keeps me awake while I develop and it's always appreciated!
Click here to donate!
Download: Solid_Kernel_V2.56
XDA:DevDB Information
Solid Kernel Nougat, Kernel for the LG G3
Contributors
Loller79
Source Code: https://github.com/Solid-Kernel
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 2.56
Stable Release Date: 2017-12-23
Created 2017-07-02
Last Updated 2017-12-22
Ah Solid Kernel! One of my favorite when I was on stock LG ROM.
So this one is for AOSP and CM right?
IAM_TheFlash said:
Ah Solid Kernel! One of my favorite when I was on stock LG ROM.
So this one is for AOSP and CM right?
Click to expand...
Click to collapse
I'm using it on LineageOS 14.1, it should work on every ROM that's based on the Lineage source code.
Glad that you liked my stock kernel, feedback is always good to receive! (especially if it's positive )
I forgot to say that this kernel runs by default at 1,4GHz guaranteeing better smoothness than you get while on 2,4GHz with the stock lineage kernel, this means less heating -> less thermal throttling -> buttery smooth.
You can obviously ramp up the CPU clock even with the simplest kernel app if you don't like this setting, but you'll see little to no performance gain since my kernel is well optimized, we're obviously talking about simple gaming and normal usage, it's pretty obvious that with heavy gaming you'll get better fps with higher CPU clocks.
Thanks for the new kernel.
What's up with GPU Extra libs? Do you recommend us to flash it? I don't play games by the way.
Sent from my LG-D855 using Tapatalk
ceza1380 said:
Thanks for the new kernel.
What's up with GPU Extra libs? Do you recommend us to flash it? I don't play games by the way.
Click to expand...
Click to collapse
They might give some improvements, still totally optional though.
I see you are using linaroTC, did you consider using different one like uberTC?
ppajdek said:
I see you are using linaroTC, did you consider using different one like uberTC?
Click to expand...
Click to collapse
Oh I've always used Linaro since I started developing kernels, maybe I should try something different, nice idea
That's why feedback is useful guys, keep it up and future releases will be even better thanks to your opinions and ideas!
New releases will be compiled with Uber Toolchain 8.0!
{
"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"
}
Running since 20 hours. Running great and very smooth. No stutters or lags whatsoever. Only change i did was to drop min cpu to 1. Near empty to full charge took between 2 and a half to 3 hours.
rahulkrathod said:
Running since 20 hours. Running great and very smooth. No stutters or lags whatsoever. Only change i did was to drop min cpu to 1. Near empty to full charge took between 2 and a half to 3 hours.
Click to expand...
Click to collapse
That's great to hear, the charge was a bit slow in your case, mine takes max 1 hour to fully charge...I'll look into it.
Great work, but UberTC 8 is new and probably have many bugs, i would start with very stable version 4.9.3, then 5.3 and then 6.0 eventually.
Its old changelog here but it gives general idea about versions.
ppajdek said:
Great work, but UberTC 8 is new and probably have many bugs, i would start with very stable version 4.9.3, then 5.3 and then 6.0 eventually.
Its old changelog here but it gives general idea about versions.
Click to expand...
Click to collapse
Well, 8.0 compiled like a charm and works without problems, shouldn't be much of an issue IMHO.
Good to hear that, if there are no issues then thats awesome
ppajdek said:
Good to hear that, if there are no issues then thats awesome
Click to expand...
Click to collapse
Yeah, no issues at all.
V2.4 will come out tomorrow!
Loller79 said:
Yeah, no issues at all.
V2.4 will come out tomorrow!
Click to expand...
Click to collapse
well, you are full of surprises, thank you!
Sent from my LG-D855 using Tapatalk
Loller79 said:
Yeah, no issues at all.
V2.4 will come out tomorrow!
Click to expand...
Click to collapse
Do you plan to add 27 MHz GPU step?
Sent from my LG-D855 using Tapatalk
ceza1380 said:
Do you plan to add 27 MHz GPU step?
Click to expand...
Click to collapse
Maybe, let's see if it works with the current structure.
Will you tell us about the gpu libs? I want to know what it's going to do before I flash it.
Loller79 said:
That's great to hear, the charge was a bit slow in your case, mine takes max 1 hour to fully charge...I'll look into it.
Click to expand...
Click to collapse
So fast charging is enabled yeah?
I hope the 2-3 hours to full charge of the guy before was just some bug
khnoizer said:
Will you tell us about the gpu libs? I want to know what it's going to do before I flash it.
Click to expand...
Click to collapse
They give slightly better smoothness.
darisito said:
So fast charging is enabled yeah?
I hope the 2-3 hours to full charge of the guy before was just some bug
Click to expand...
Click to collapse
Well as I said before my phone charges in less than a hour.

Categories

Resources