{
"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"
}
"I Don't Always Run Custom Kernels. But When I Do, I Run Vindicator"
-Worlds Most Interesting Man
Pushbullet Tag: vindicator-n7
You can also follow me on G+ if you would like:
[email protected]
Intro:
This is a kernel I developed alongside @Xileforce for Nexus 7 2013, this IS an offical Vindicator Kernel and follows the same ideals and guidelines as the Vindicator Kernel for Nexus 6. I hope you like it and I won't be offended if you hate it. All ideas are welcome and I'll try to help as best I can. If you wish to use this kernel in a rom , feel free! Although I would love it if you let me know just for my own curiosity.
Goal:
Keep kernel as lean as possible while adding certain, desirable features and optimizing for maximum performance and battery life. The default settings should be optimal for a balance of battery and performance without a need to tweak.
Disclaimer:
If your tablet blows up, its not my fault. If your tablet somehow gains perpetual battery life, I'll take full responsibility.
Features:
-Quanta Kernel Base
-Android 5.1
-Linux 3.4.107
-Updated to Android M source
-XZ Compression
-Upstreamed cpuidle
-35mhz cpu step
-Compiled With Uber Toolchain 6.0
-Compiled With Strict-Aliasing, Ofast, Graphite, And Loop Nest Optimizations
-Various Other Build Optimizations
-Kexec Hardboot/MultiRom
-UKM Built In And Modified. Just Install Synapse App.
-Hardware Floating Point Processing
-ZRam
-ZSMalloc
-Slimmed Down(Increased Size Is Due To Optimizations & UKM Not Bloat)
-Tons Of Debugging Removed
-Many Misc. Optimizations.
-MPDecision killed
-Mako Hotplug
-Adjustable Thermal
-IntelliActive/Intellidemand Governor Added
-BFQ IO Scheduler Added
-Tons Of IO Fixes/Performance Boosts
-Voltage Control
-Westwood TCP Algorithm
-Many Parts Pulled From Upstream
-Wake Gestures
-F2FS Support
-Init.D Support
-Potentially Something I Forgot...
-Battery Life Extender
Donations:
I do not require a donation, nor will I demand a donation, but any and all donations are appreciated. Especially when I release my OTA app for this kernel, it'll go towards the server cost.
Downloads:
Caf builds end in -cm
Aosp builds end in -aosp
[AFH] Kernel: https://www.androidfilehost.com/?w=files&flid=32021
Downloads also through pushbullet
Source:
http://github.com/Orbit-/Vindicator-flo-aosp
Credits: @zaclimon for an awesome Kernel Base
xileforce
Franco
Faux123
Linaro
Code Aurora Foundation
apb_axel
Google
Asus
If I Missed You Let Me Know!
FAQ
1. How Do I Enable Mako Hotplug?
To enable mako hotplug use your favorite kernel control app like faux or trickster. As of 1.8 it is the default hotplug. In trickster you have to turn off both mpdecision and intelliplug. In faux you need to simply select User Control in the Hotplug Section. The hotplug can be configured using Franko Kernel Updater App.
2. Does This Work With CM12 Theme Engine?
Yes, this works with CM12 Theme Engine and should work on all ROMs properly.
3. How Can I Force All 4 Cores Online All The Time?
First you must enable mako hotplug. Then you need to use Franco's kernel updater app or another app that allows you to tweak mako hotplug settings. In fku app select CPU manager then hotplug control. Change load threshold to 0. Additionally if you just want to make it use 4 cores more often. Lower this number below 80 as desired. This should also be possible to tweak via terminal however I've never used that method.
4. Does This Have D2W, S2W, etc?
Yes, they are include in this kernel.
5. Help! I think its making me bootloop!:
This may only apply to specific ROMs and I'm unsure of why it would change anything but users have reported this to fix the issue. If you are trying a fresh install of a ROM boot on stock kernel first, reboot, then install this kernel.
6. You Broke My Tablet! Fix It!:
It will be quite hard for me to figure out what is going on if you don't provide details and a log of what happened. To get a log use any file manager and navigate to proc/last_kmsg. I need this file for debugging.
7. What Kernel Tweaking App Should I Use?:
I now use Synapse as my goto app for kernel tweaking.
8. Why Add Zram? We Already Have plenty of Ram!
Zram was added in build 1.0 as an experiment of sorts to see how much is was actually being used. V 1.0 introduced a bunch of tweaks to the kernel that essentially make it use more ram in order to give better battery life and performance. Zram was put in place to offset this in a way.
9. What Is Strict Aliasing And Why Should I Care?:
One of the big things Linaro does with improving Android's performance is fixing violations of what's known as "the strict aliasing rule." A pointer is said to alias another pointer when they both refer to the same location of memory. This is OK and not an uncommon thing to do. The strict aliasing rule is that pointers of different types should never refer to the same location of memory (aka alias each other). Strict aliasing allows a compiler to make some assumptions when compiling and optimizing code that it otherwise couldn't. It's actually one of the biggest optimizations you can do and it is fairly hard to add which is why most people don't. Here's a nice read up on it http://cellperformance.beyond3d.com/articles/2006/06/understanding-strict-aliasing.html#benefits
10. Come on man. 35mhz is pointless bro!:
A common misconception is that if two frequencies run at the same voltage. They use equal power. In fact this couldn't be less true. The equation for power draw has four variables. Two of which are frequency and voltage. Essentially it is the frequency multiplied by the square of the voltage. Then you would take that and multiply it by a few other things such as capacitance. However that is irrelevant for our purposes as it will not effect the relative results. This means that 35mhz running at 500mv will use about 3x less power than 98mhz at 500mv. Now we say well what about compared to 300mhz? I can stably run that at around 650mv. Maybe slightly less. This equates to about 15x less power usage at 35mhz. Well now that we know that. Who cares? Its not like 35mhz will even get used. Its too low! I beg to differ. I would almost guarantee that if you are not running mpdecision 35 MHz will be within the top 3 most used frequencies. Most likely the top used below sleep. And every time it uses that over 300mhz you are saving 15x the power. Additionally 35mhz also runs at a cache frequency of 35mhz as opposed to 300mhz cache frequency and runs a lower bus speed/voltage saving additional power.
11. How Do I Use MultiRom???:
To use multi ROM first you must download the MultiRom App from the Gooogle Play Store. Open it. You should have MultiRom and recovery boxes checked. Click install, reboot etc. To install a ROM. Download a ROM you like, go to twrp, click advanced,MultiRom,add ROM. Select internal storage and the Your zip file. Flash it but don't reboot! After that go back and select "list ROMs" select the ROM u just flashed still and click flash zip and select your gapps,supersu etc. After that simple reboot and select your new ROM on boot use the MultiRom app to manage your ROMs.
More will be added as they come up and I think of them.
If anyone wants to be a beta tester, email me at [email protected]. I'll be looking at email tomorrow.
First!
Re: [Kernel] Vindicator [Linaro 5.1/Strict-Alias/Graphite][5.1][Beta-0.1]
jamcswain said:
If anyone wants to be a beta tester, email me at [email protected]. I'll be looking at email tomorrow.
Click to expand...
Click to collapse
I want to be a better tester. I have one question though. The ROM I'm running is cm based and I'm getting different colors. Can you include a caf based kernel please. An d which is the best app to change settings with cz trickster don't let me change sound control
Edit: other than that the kernel looks great man. Its good and fast I'll test battery life for you on my next charge
Sent from my Nexus 7
hypemanisus said:
I want to be a better tester. I have one question though. The ROM I'm running is cm based and I'm getting different colors. Can you include a caf based kernel please. An d which is the best app to change settings with cz trickster don't let me change sound control
Edit: other than that the kernel looks great man. Its good and fast I'll test battery life for you on my next charge
Sent from my Nexus 7
Click to expand...
Click to collapse
Yes a caf base is coming soon
https://play.google.com/store/apps/details?id=com.af.synapse
That's the app that's supported
Hell yeah! Heard many good things about this kernel. It's really great to see it being developed for our beloved Flo. Sweet!
Just a quick heads up... I'm getting a boot loop. Running latest OptiPop which is 5.1.1 r2 and I have data and cache partitions set to f2fs. Any help is appreciated.
You stoped me flashing. Maybe it's a ramdisk problem? Flash stock kernel when flash this one. Give a feedback after that
And first request. Please add BLX\BLE http://forum.xda-developers.com/showthread.php?t=2469261
FireBlast said:
You stoped me flashing. Maybe it's a ramdisk problem? Flash stock kernel when flash this one. Give a feedback after that
And first request. Please add BLX\BLE http://forum.xda-developers.com/showthread.php?t=2469261
Click to expand...
Click to collapse
I'll look into it. I'm about to release an update anyway. Aosp and caf now
Oh yeah. I was planning on adding that in
Been running great on DU...
Installed it since you posted...
Thanks
Sent from the "DOG" pound on my N7 2013
Will give it a whirl...
And thanks...
Will let you know how it goes...?
New builds:
Aosp:
https://www.androidfilehost.com/?fid=23991606952607277
Caf:
https://www.androidfilehost.com/?fid=23991606952607307
Changelog:
-Rebase to Quanta
-Add caf build too
-Squash bugs
-Add bluplug
-Add more governors
-Add bfq
-Add 3.10 ZRAM
Looks like cm didn't boot. I'll fix that real quick
Don't know if this a bug, but I can't seem to get the MHz (94) to stick using synapse.
Everything else OK so far. This in on the initial release...
Thanks again....
https://www.androidfilehost.com/?fid=23991606952607307
NEW CM BUILD. Last one didn't boot
SHABBYLEA said:
Don't know if this a bug, but I can't seem to get the MHz (94) to stick using synapse.
Everything else OK so far. This in on the initial release...
Thanks again....
Click to expand...
Click to collapse
There isn't a 94mhz step
jamcswain said:
There isn't a 94mhz step
Click to expand...
Click to collapse
OK...on opening syn the min freq is 918. If I move the slider to the extreme left it indicates 94mhz. I save & when I reopen syn, the freq is back to 918.
Not at all saying this is a problem with the kernel, just what I'm seeing with syn...
Thanks.
Related
{
"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"
}
Elix-R V2.0 has been constructed from the ground up to bring you a revolutionary new experience. Based off the latest Google LRX21O Factory image all the ROM's
features and tweaks have been hand crafted into this ROM without any cherry picks, or any merges. There are several benefits to this one being is the ROM stays
true to Stock, NO BS, NO NOTHING. Another benefit is the ROM is rock solid virtually no bugs exist meaning no random crashes or speed bumps. Speed is a top priority
as well as it contains various optimizations to speed up the device as well as many small changes that give the ROM a speed boost. Lastly but not least is Simplicity.
The ROM has been custom themed with "Elixium UI" that brings an elegant and beautiful UI to the whole system. Hope you enjoy the ROM.
* Based Off LRX21O Factory Image
* Odexed (For Speed)
* Sensei Kernel
* Removed Forced Encryption
* Improved battery + Performance
* S2S and S2W
* Pre-Installed Gapps
* Incorporation of Elixium UI
* New UI_Tick sound
* Android 5.0.1 Merged (Hybrid 5.0.1 + 5.0)
* Android 5.0.1 Android Runtime merged for speed
* Roboto Condensed Font
* Awesome Wallpaper
* Pie Is Fixed
* Most Apps Up To Date
* Perfect harmony between performance and battery life.
* Tweaked System Transitions
* Debloated (Removed Uncommon Languages, Korean IME sorta apps, etc)
* Disabled Safe Media Volume
* Louder Tick + Lock Sounds
* Increased Wi-Fi Scan Interval
* Made Max Multiusers to 10 rather than 4
* Removed Battery Saving Mode Color
* Changed Default Settings (Usability)
* System Animations Optimizations
* Subtle Audio Optimizations
* LED When Charging + Low Battery
+ LOTS MORE
Download Elix-R V2.0.1 - Download
* NOTE - PLEASE UNMOUNT THE SYSTEM PARTITION BEFORE INSTALLING.
* NOTE - This ROM comes with an unencrypted kernel please flash an encrypted kernel if your system is encrypted before booting up the ROM (EX: Lean kernel).
* NOTE - If you have problems with signal please flash SuperSU (Right below ME).
* NOTE - If you would like ROOT please flash THIS afterwards.
* NOTE - If sprint is not working please flash THIS.
* NOTE - There is a weird bug when restoring from a google account. it causes the device to spazz out for 10 minutes while it stabilizes.
V2.0.1
First Release For SHAMU.!!!!
CREDITS
Google
Bigxie for his stock base ROM.
XileForce For his extensive patience and for being such a great tester.
RIPng for his kernel (Found HERE)
If I missed you please let me know so I can add you.
Donations are greatly appreciated but never required. If you would like to donate you can do so clicking the
link below my username or on Google Wallet to "[email protected]". Thanks and hope you enjoy the ROM.
Kernel Tweaking Starter Guide (Including Colors):
If you are having issues please notify RIPng ,The Kernel Dev, on his hangouts: [email protected]
This ROM comes pre packaged with the Sensei Kernel which allows for a variety of tweaking options.
The following can be done using your favorite kernel tweaking app. I use FauxClock.
Updating The Kernel:
Before we get started, you are going to want to make sure your kernel is the latest! RIPng, the developer of Sensei Kernel, frequently releases new builds so its highly likely the kernel packaged with the ROM is out of date. First go to your settings menu, then about phone, then look at the section titled "Kernel Version". You should see something like "3.10.61 ~SENSEI.R7". R7 is the version of the kernel. Now go to the kernel thread here: http://forum.xda-developers.com/nexus-6/development/kernel-sensei-kernel-t2956283 you will see in the title what version kernel is the current release. As of this writing it is R9 for example. To update the kernel, simply click the downloads link and find the latest version. Once downloaded just go into TWRP and flash the kernel. Do not wipe anything. You now have the latest Sensei Kernel
Clock Speed:
To begin I prefer to leave my max clock speed at the stock 2.649ghz, this is because I have a bin 5 CPU . Set min CPU as low as it can go. As of current release this is 300. For the adventurous you can try 2.88ghz. For people near or below bin 5, you will want the voltage for that frequency around 1155mVolts. If you really wanna over clock you can try 2.95ghz. Again I've found a voltage of ~1200mVolts to be sufficient for stability. I don't recommend attempting 3ghz unless you are above a bin 6.
To find your CPU binning run this command in terminal emulator:
su (enter)
cat /proc/cpu/msm_acpu_pvs (enter)
note that the number may be displayed at the beginning of the next line.
It will then display a number from 0-15. 15 being the best. Don't stress over it too much if you score low, its not the end of the world. It just means you need marginally more voltage to run each frequency.
Governor:
Most people will probably want to just leave this set to interactive. Its a really good governor that is being actively devolped by CAF and Google. Its "smarter" than OnDemand and generally considered to offer better battery life. If you want even more smoothness some consider OnDemand to provide a bit better performance, however you may get slightly worse battery life. This is because OnDemand ramps up to max frequency when there's is load put on the CPU and then slowly works its way down. Interactive scales through the frequencies on the way up and down which saves battery life but prevents it from jumping to max speed as fast if it is needed. Simms22 recommends using the OnDemand governor with "upthreshold" set to 98 and the sampling rate set to 15000. That is the default setting of the Trinity Kernel. Mistertac made the great suggestion of turning the max screen off frequency down to 600mhz if using the interactive governor. This will prevent any misbehaving apps from keeping CPU ramped up while screen is off and give better idle drain. The actual number you would have to type in would be 652800 for the screen off frequency. As of the latest update I recommend running the intelliactive governor, its basically an enhanced version of the interactive governor created by the brilliant faux123, it is designed to run with intelliplug, but works on mpdecision as well.
Hotplugging:
Next go to hot plugging section and disable MPDecision(make poor decision) and enable intelliplug. FauxClock allows you to further configure intelliplug. If you want more battery set it to Conservative (4) mode which will hotplug the CPU more conservatively and save you battery, essentially this means it will use less cores if it can. For most people, leaving it on Balanced (4) mode will be fine. If you want further battery savings you can set it to EcoPerformance (2) which will only use a max of 2 cores.
Voltage Control:
Next go to voltage control. I'm a Bin 5 and I can use a 24mVolt undervolt without becoming unstable. This means pretty much anyone can probably get away with this and its across the board battery savings so you may as well. Rember! Never set voltages to apply on boot until you have tested them for a few hours first! Most people can probably get away with a 36mVolt undervolt. Also remember that if you are running an over clock you may not want to undervolt. If you find yourself running into freezes or random reboots remove the undervolt!
I/O Settings:
For I/O scheduler select Deadline. As of the current available options Deadline is the best. I then proceeded to do a lot of benchmarking with different read ahead sizes. 1024 seems to be the optimal setting. Going larger degraded performance as did going lower. Newer builds of Sensei now include FIOPS scheduler which is widely regarded as one of the best for phones, so I suggest using that over deadline.
Color Control:
Next you may want to adjust Screen RGB. WrinkleFree over in the Lean Kernel thread did extensive testing with a professional grade $1000 screen calibration tool.
For the most truly color accurate screen at D6500K:
Red - 248
Green - 246
Blue - 255
If you prefer a slightly cooler screen and the tuning the iPhone uses which is D7400K:
Red - 237
Green - 235
Blue - 255
More info can be found about color calibration here: http://forum.xda-developers.com/showpost.php?p=57265483&postcount=620
These settings are meant to be used as a starting point. Depending on your cpu binning and desires you will probably want to tweak these slightly to fit your needs. I'll add more as new features get added, I learn more, and I think of stuff to add Hope it helps someone!
Sweet...loved this ROM on my N5
Sent from my Nexus 6 using XDA Free mobile app
I guess I should flash this, right?
RIPng said:
I guess I should flash this, right?
Click to expand...
Click to collapse
Of course, your contributions are greatly appreciated
Zyxxeil said:
Of course, your contributions are greatly appreciated
Click to expand...
Click to collapse
I wish we could get non intrusive nav on this device already Something like PIE or how CM used to hide the nav on kitkat.
looks really neat! it'll be nice to have a ROM where i won't have to worry about GAPPS issues
great. cant wait to test this out. glad to see new work coming to the n6
RIPng said:
I wish we could get non intrusive nav on this device already Something like PIE or how CM used to hide the nav on kitkat.
Click to expand...
Click to collapse
But, but, but you have all that screen
tflogic said:
looks really neat! it'll be nice to have a ROM where i won't have to worry about GAPPS issues
Click to expand...
Click to collapse
You don't have to flash gapps on this one as its based off the LRX21O Factory image which includes all gapps.
Zyxxeil said:
But, but, but you have all that screen
You don't have to flash gapps on this one as its based off the LRX21O Factory image which includes all gapps.
Click to expand...
Click to collapse
I just like full screen without nav, it looks more elegant in my opinion. On another note, how often do you release new builds? I publish new kernel updates far too frequently to ask you to rebuild each time
Zyxxeil said:
You don't have to flash gapps on this one as its based off the LRX21O Factory image which includes all gapps.
Click to expand...
Click to collapse
yup! that's what I meant to say
further down the line, will you keep including gapps with the rom or will you defer to PA gapps once TKruzze gets them up and running?
tflogic said:
yup! that's what I meant to say
further down the line, will you keep including gapps with the rom or will you defer to PA gapps once TKruzze gets them up and running?
Click to expand...
Click to collapse
Well since its based on factory Image I don't think you will ever have to.
---------- Post added at 11:38 PM ---------- Previous post was at 11:36 PM ----------
For those who don't know, he coded this whole ROM blindly since he doesn't have a nexus 6, and took it from a non booting 100% stock rom to a fully featured port of his nexus 5 rom in one day. It was amazing progress. He was pushing a new build like every 15 minutes, mainly because it took 10 mins to upload each time or he would've pushed them faster
RIPng said:
I just like full screen without nav, it looks more elegant in my opinion. On another note, how often do you release new builds? I publish new kernel updates far too frequently to ask you to rebuild each time
Click to expand...
Click to collapse
Maybe once a week. I will update the ROM with your new kernel each build
tflogic said:
yup! that's what I meant to say
further down the line, will you keep including gapps with the rom or will you defer to PA gapps once TKruzze gets them up and running?
Click to expand...
Click to collapse
I will always include gapps.
Xileforce said:
Well since its based on factory Image I don't think you will ever have to.
---------- Post added at 11:38 PM ---------- Previous post was at 11:36 PM ----------
For those who don't know, he coded this whole ROM blindly since he doesn't have a nexus 6, and took it from a non booting 100% stock rom to a fully featured port of his nexus 5 rom in one day. It was amazing progress. He was pushing a new build like every 15 minutes, mainly because it took 10 mins to upload each time or he would've pushed them faster
Click to expand...
Click to collapse
Yup, Most of the framework was already layed out with the Nexus 5 build just needed to port it over.
Plus its the first ever ROM to use Google's Factory Image. If any of you guys are interested in just the Factory Image as a ROM just let me know (Be warned its 750+MB in size)
finally a rom without bugs!
First bug, my recents button isn't working
RIPng said:
First bug, my recents button isn't working
Click to expand...
Click to collapse
Hmmm...mine is.
any special install instructions? just tried to flash and got the following message:
Wiping - Be patient it takes awhile
unmount of /system failed. no such volume
mount: failed to mount /dev/block/platform/msm_sdc.1/by-name/system at /system: Device or resource busy
Enjoy!
Script succeeded: result was [Enjoy!]
I assumed nothing was flashed because i didn't see the standard "progress bars". i restored my nandroid because i wasn't sure the flash worked. thanks in advance for your help/feedback.
cortez.i said:
any special install instructions? just tried to flash and got the following message:
Wiping - Be patient it takes awhile
unmount of /system failed. no such volume
mount: failed to mount /dev/block/platform/msm_sdc.1/by-name/system at /system: Device or resource busy
Enjoy!
Script succeeded: result was [Enjoy!]
I assumed nothing was flashed because i didn't see the standard "progress bars". i restored my nandroid because i wasn't sure the flash worked. thanks in advance for your help/feedback.
Click to expand...
Click to collapse
Unmount system first.
{
"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"
}
is proud to present BarePops
Navel - kernel
This is just the beginning, I hope. Let's see what more we can do?
Install insructions:
This should work on any ZV8 Stock based ROM. Just flash in recovery
Changelog:
Code:
V4.3 - 6-23-16
KCal - more options to adjust your screen
Might be other small things. It's been hectic lately
V4.2 - 6-13-15
Same as below+
f2fs
exfat
V4.1 - 6-9-15
same as below+
CPU OC
GPU over/underclock - 100mhz and 27mhz sleep
Linaro 4.9 toolchain
New fixed ramdisk
V4 - 6-1-15
back to -LGLS990 Source
Most everything below+
TCP congestion algroithms - Westwood, Vegas, Reno Veno and others
Smartmax gov
Intelliactive gov - Might cause random freezes/reboots
Intellithermal
Neon support
Oversharpening fix
Enabled KSM
Probably others that I forgot.
V3.5 5-18-15
All of V3+
intellidemand
power suspend - Faux
Overclock - won't work on Sprint until we can fix framework.res
other things I can't remember
There are a lot of tweaks in this that can't be done with Trickster. I would recommend using Faux or Kernel Adiutor - yeah, that's how it's spelled.
V3 - 5-14-15
All new from scratch using Verizon 23C source
Added govs-adaptive, lionheart, dancedance,wheatley,lagfree,
added schedulers-fifo, sio,vr,zen tripndroid,fiops
Fast charge
undervolt
Faux Sound
simple gpu ondemand governor - Faux
intelliplug -Faux
DriveDroid - untested
Selinux Permissive
SM4.8 toolchain
V2.7 - Linaro and Sabermod versions
Cleaned up of non-working/useless files
2 toolchain versions to see if I can find the SD Card issue for some
V2.6.1
Same as below +
Back to Linaro 4.9 toolchain
Minor changes for f2fs - still need to see if I can get it to work
Maybe fixed SD issues for some
V2.6
Same as below +
Fast Charge should be working for sure this time
f2fs file system support added. - Currently, our stock Rom's don't support this. At least as far as I've tried. I think I need to build a Rom.
V2.5
Clean from the ground up if you've been following.
Same as below+
Stereo call recording patch - I have no idea if this even works on Lollipop
Scheduler added BFQ
Back to SaberMod toolchain
Other optimizations that I can't remember...
V2.2
same as below +
Faux Sound
V2.1
Same as below +
Linaro 4.9 toolchain
Fast Charge
V2
Same as below +
Fix for interactive and intelliactive
Undervolt is now possible
V1
Selinux set to "Permissive"
Added shedulers-CFQ, FIFO, FIOPS,VR,ZEN, TRIPNDROID,SIO
Added governors - LAGFREE,INTELLIACTIVE, DANCEDANCE, WHEATLEY, ADAPTIVE,LIONHEART
Thanks, credits and SOURCE!! - Without these 2, it wouldn't have happened
@Tectas - https://github.com/tectas/android_kernel_lge_msm8974ac/tree/rin-lollipop
@Skin1980 - https://github.com/Skin1980/D855-kernel/tree/lollipop
My source - https://github.com/engine95/navel-990
Downloads: Navel
Navel-V4.3
Navel-V4.2
Navel Kernel folder - all Kernels
Navel_V1
Downloads for @jcfunk version:
NavelA-Kernel-1.4_JCFunkMODv1-ZV8.zip
XDA:DevDB Information
Navel Kernel, Kernel for the Sprint LG G3
Contributors
engine95, HPTesla, jcfunk
Source Code: https://github.com/tectas/android_kernel_lge_msm8974ac/tree/rin-lollipop
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 1969-12-31
Created 2015-03-25
Last Updated 2015-08-20
Reserved
Voltages for now
Here's the stock voltages in case you need them
One of those days. I'll get the mods to move this to the right place. Sorry
awesome! thanks engine!
OP updated with these install instructions!!! Sorry for another braincramp.
If you have SElinux Changer already installed:
You need to uninstall it first. Set it to "enforce" first. Then Settings>apps and clear "data" and "cache", Force stop then uninstall. Reboot. Then install the kernel.
Hopefully you made a backup first!
It may still work right, but just in case.
Just flashed. I seem to get random reboots anytime I change settings to anything other than the default settings.. I'm using trickster.. Maybe I'm doing something wrong because if I recall correctly, I use to have the same problem with Barrin anytime I flashed a kernel and messed with the settings... Thoughts?
Lurien said:
Just flashed. I seem to get random reboots anytime I change settings to anything other than the default settings.. I'm using trickster.. Maybe I'm doing something wrong because if I recall correctly, I use to have the same problem with Barrin anytime I flashed a kernel and messed with the settings... Thoughts?
Click to expand...
Click to collapse
I'm not sure what the issue would be. But if you had the same thing with BarRin, then maybe it's something with either or both SD's . Try pulling the ext SD and see if it happens. If nothing changes, then format int SD.
Did you have SeLinux changer installed. If so see the post above yours.
Other than that, Flashtool is my only other thought.
Also, MAKE SURE you don't set Trickster "on boot" until you're sure the settings work with your phone.
@ruthlessptizzle
Kernal runs good..i noticed there is no voltage control yet through faux...i dont know what all the different govs do to be messing with them just yet
Sent from my LGLS990 using XDA Free mobile app
I'm doing this kernel in stages as I'm learning this. I don't want to put out a kernel that doesn't work.
Overclocking, voltage control, kexec patch, faux sound, readaheads, are all on my todo list for starters. And that's in no particular order.
engine95 said:
I'm not sure what the issue would be. But if you had the same thing with BarRin, then maybe it's something with either or both SD's . Try pulling the ext SD and see if it happens. If nothing changes, then format int SD.
Did you have SeLinux changer installed. If so see the post above yours.
Other than that, Flashtool is my only other thought.
Also, MAKE SURE you don't set Trickster "on boot" until you're sure the settings work with your phone.
Click to expand...
Click to collapse
Thanks, I'll look into it. It's something very very random and doesn't happen often...when it does, the screen freezes for a couple seconds and phone reboots...
Help?
So I am new at this kind of stuff so I have a couple qustions.
First when ever I try to change the CPU governer or GPU governer, after a bit the screen would freeze and the device would reboot. I am using the trickstermod. Am I doing something wrong?
Also when the device reboots, am I doing any harm or is there a safety trigger to prevent damage?
Thanks.
I know if its not in the OP its probably doesn't, but does this support multiboot?
Thanks for all your work none the less!
JaceAlvejetti said:
I know if its not in the OP its probably doesn't, but does this support multiboot?
Thanks for all your work none the less!
Click to expand...
Click to collapse
Post #9 lists the items he is trying to implement into the kernel. Multiboot is on that list. Also I don't know if it would matter until there is an updated multiboot twrp available for us to us.
Sweet!!!
andrewwm said:
So I am new at this kind of stuff so I have a couple qustions.
First when ever I try to change the CPU governer or GPU governer, after a bit the screen would freeze and the device would reboot. I am using the trickstermod. Am I doing something wrong?
Also when the device reboots, am I doing any harm or is there a safety trigger to prevent damage?
Thanks.
Click to expand...
Click to collapse
Every phone is different. What works for one person, may not work for another.
The reboots/freezes means your phone doesn't like that combo. Try another. Just do not set it on boot until you know your phone can handle it.
Sometimes just changing the scheduler will make a governor work.
/me is going to install this right now.. I really cant imagine this phone running much better.. but here goes :highfive: :highfive:
@ruthlessptizzle
"Kernal runs good..i noticed there is no voltage control yet through faux...i dont know what all the different govs do to be messing with them just yet"
Governor's explained. http://forum.xda-developers.com/showpost.php?p=27955261
engine95 said:
I'm not sure what the issue would be. But if you had the same thing with BarRin, then maybe it's something with either or both SD's . Try pulling the ext SD and see if it happens. If nothing changes, then format int SD.
Did you have SeLinux changer installed. If so see the post above yours.
Other than that, Flashtool is my only other thought.
Also, MAKE SURE you don't set Trickster "on boot" until you're sure the settings work with your phone.
Click to expand...
Click to collapse
Seems like my phone didn't like trickster.. Using faux paid version right now.. No reboots so far..
Lurien said:
Seems like my phone didn't like trickster.. Using faux paid version right now.. No reboots so far..
Click to expand...
Click to collapse
Faux is great but just some settings ur phone just may not like and will reboot....im set to wheatly gov and also set to deadline....no issues so far
Sent from my LGLS990 using XDA Free mobile app
WoW Engine
Hello Engine,
I am blown away by the amount of projects you take on. How the heck are you accomplishing all this development? When did you start dabbling with Roms and Kernels? I want to get in to development, but just wasn't sure where to begin. I would mainly like to start with basic romndevelopment, if there is such a thing as basic.
Lastly, I apologize for posting in this thread, but when I saw that you are doing kernels now I was just blown away
Thanks Engine for all you do. Your an amazing guy.
Ripley22
{
"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"
}
WELCOME TO ELITE KERNELS!
Our main goal behind building these kernels is to create a setup that gives a balance between performance and battery life without straying too far from stock. We like to have our cake and eat it too. Our kernels include performance, memory, and scheduling tweaks that enables your phone to come to the party when you are hammering down on it and need performance ASAP, and to go to sleep faster than a basset hound on a warm summer day. We put these kernels together mainly for our own use; so what we release is what we personally use. We hope you enjoy them too!
Elite Kernel Members
@buckmarble
@brymaster5000
Special Features (added to stock options)
Storage
f2fs support
USB native mount(if rom supports)
Linux 3.10.40
Boot
Permissive Selinux
LZ4 Compression
Kexec Hardboot - MultiROM support
Anykernel 2 installer - ramdisk edits that don't overwrite your current boot.img tweaks
Forced Encryption.........just kidding.
Disabled BCL
Optimization
Neon
[*]Linaro 4.9.4 by @christopher83
Official Linaro 5.2
Graphite Loop Nest
CPU
[*]BFS (Brain F**k Scheduler) - a single runqueue deadline design
Stock CFS
Zen Decision and MP Decision available(MPD default)
cpuboost disabled
thermal control
voltage control
Faux Power Suspend
Generic Input Boost Driver
GPU
Simple Ondemand governor
Simple GPU Algorithm
[*]Adreno Idler by @arter97
Governors
[*]3.18 Interactive with generic input boost driver rewritten for it
Tweaked Conservative for generic input boost driver
Blu Active
ZZMoove(defaults to profile 7 when selected)
SmartMax
PMC - Performance May Cry
Elementalx
Nightmare
IO Schedulers
SIO
FIOPS
BFQ
ROW
Battery
USB Fast Charge
Miscellaneous
Wake Gestures + Camera Launch Gesture
LED Control Support
Color/Gamma Control
Frandom
Fsync
[*]Faux Sound Control
Advanced TCP Congestion Control
HSIC, SMB and WLAN wakelock control
Scripted control with Elite.sh in /system/su.d (/System/elite on MM)
power suspend driver
Upstream Linux patches
Swap/ZRAM enabled
Nougat 7.1.1
Elite_Shamu_N-11_05_2017 - October Patch (I know...it has a november date...)
Marshmallow 6.0.1
Elite_Shamu_M-09_19_2016
SUPERSEDED DOWNLOADS
Elite_Shamu_N-09_15_2017
Elite_Shamu_N-06_14_2017
URL="https://www.androidfilehost.com/?fid=889764386195900246"]Elite_Shamu_N-05_19_2017[/URL]
Elite_Shamu_N-04_09_2017
Elite_Shamu_N-03_18_2017
Elite_Shamu_N-02_19_2017
Elite_Shamu_N-01_07_2017
Elite_Shamu_N-01_02_2016
Elite_Shamu_N-12_17_2016
Elite_Shamu_N-11_12_2016
Elite_Shamu_N-10_06_2016
[Elite_Shamu_N-09_19_2016
Elite_Shamu_M-09_09_2016
Elite_Shamu_N-08_02_2016
Elite_Shamu_M-08_02_2016
Elite_Shamu_M-07_11_2016
Elite_Shamu_N-06_30_2016
Elite_Shamu_M-06_23_2016
Elite_Shamu_N-06_23_2016
Elite_Shamu_M-06_06_2016
Elite_Shamu_N-06_02_2016
Elite_Shamu_M-06_02_2016
Elite_Shamu_M-05_02_2016
Elite_Shamu_N-05_06_2016
Elite_Shamu_N-03_29_2016
Elite_Shamu_M-04_27_2016
Elite_Shamu_M-04_05_2016
Elite_Shamu_M-03_21_2016
Elite_Shamu_N-03_11_2016
Note - first need to flash unofficial SuperSU here.
Elite_Shamu_M-03_09_2016
Elite_Shamu_M-02_16_2016
Elite_Shamu_M-02_15_2016
Elite_Shamu_M-02_08_2016
Elite_Shamu_M-01_21_2016
Elite_Shamu_M-1_12_2016
Elite_Shamu_M-11_26_2015
Elite_Shamu_M-12_16_2015
Elite_Shamu_M-12_07_2015
Elite_Shamu_M-11_25_2015
Elite_Shamu_M-11_23_2015
Elite_Shamu_M-11_22_2015
Elite_Shamu_M-11_14_2015
Elite_Shamu_M-11_01_2015
Elite_Shamu_M-10_28_2015
Elite_Shamu_M-10_27_2015
Elite_Shamu_M-10_20_2015
Elite_Shamu_LP-10_09_2015
Elite_Shamu_LP-06_17_2015
Elite_Shamu_LP-06_10_2015
Elite_Shamu_LP-05_21_2015
Elite_Shamu_LP-05_15_2015
Elite_Shamu_LP-05_10_2015
Elite_Shamu_LP-05_04_2015
Elite_Shamu_LP-05_03_2015
What is enabled by default? We like to control our kernels with a script run at boot for defaults, although any kernel app can control the built in settings. Here is what we set as default upon boot:
Sweep left 2 sleep
Doubletap 2 wake
CFQ IO scheduler with 1536 read ahead
If you want to change anything you can open up /system/elite/Elite.sh and save and execute (or use your favorite control app). Current method for N Preview has script in /system/su.d/Elite.sh
Special Thanks
@flar2 for his wake gestures
@faux123 for his sound control and other goodies along the way
@bbedward for porting BFS to the nexus 6 - I was so happy to see this...havent used it since Gingerbread days
@osm0sis for his anykernel2 setup
@bsmitty83 for helping your old B-Team member to get ak2 running
@hellsgod for misc assistance and trouble shooting
@arter97 for the Adreno Idler
Our testers/friends - you know who you are...
BETA TESTING KERNELS
Elite_Shamu_M-02_24_2016
Elite_Shamu_M-01_21_2016-PMC
XDA:DevDB Information
Elite Kernel, Kernel for the Nexus 6
Contributors
brymaster5000, buckmarble
Source Code: https://github.com/Elite-Kernels/elite_shamu_N
Kernel Special Features: N2O
Version Information
Status: Stable
Created 2015-05-04
Last Updated 2017-11-05
Recommendations for flashing:
1. If you have flashed another kernel, we suggest you get back the kernel that the ROM you were on came with before flashing Elite Kernel. Easiest way to do this is dirty flash the ROM again.
2. If you think you are getting a bug that is kernel related, please report all of your current setup. Including ROM(and version), any other kernels you've flashed, if you have dirty flashed a ROM update, and any other information we might need and also include a log if possible.
Got it
Xileforce said:
I don't see it in the source but I could've missed it
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Tried flashing on the primary ROM. Multi ROM seems to be present.
Atleast secondary ones boot fine.
finally ! I saw that you were preparing this on the clean ROM thread
thks mate !
@op any recommanded control app and kernel profils (settings) ? am kinda new to these kernel things (I always try the default settings only to not scew things up)
ahmed534 said:
finally ! I saw that you were preparing this on the clean ROM thread
thks mate !
@op any recommanded control app and kernel profils (settings) ? am kinda new to these kernel things (I always try the default settings only to not scew things up)
Click to expand...
Click to collapse
We set these up out of the box to our liking so the recommended settings are the default ones. I use trickster when I do mess with things though.
First impressions: Been onboard 9 hours on Tesla rom (unofficial) a friend of mine builds for Shamu...Extremely smooth!!Slow drain on battery already seems noticeable to me. Played a zombie killer fps game and no stutters whatsoever. Using kernels default settings. Tks guys! :thumbsup:
Kernel up and running on AOSiP.
Smooth & Fast...
Now let's give it some time...
O no lag on a heavy graphic's game
Sent from the "DOG" pound...
https://github.com/bbedward/ZenKernel_Shamu/commits/sched_upstream_bfs_gc
You should be able to pull in the latest 4 BFS patches from the bfs_gc branch. I think I should have pulled them into the BFS_standalone branch but wasn't paying attention they are all minor, but good things from at least a developer perspective
Very happy to see the team pushing out quality goods yet again
bbedward said:
https://github.com/bbedward/ZenKernel_Shamu/commits/sched_upstream_bfs_gc
You should be able to pull in the latest 4 BFS patches from the bfs_gc branch. I think I should have pulled them into the BFS_standalone branch but wasn't paying attention [emoji14] they are all minor, but good things from at least a developer perspective
Click to expand...
Click to collapse
Good stuff man! Appreciate the lookout! I will get it updated.
Hell yes. Elite. Kernel shopping is complete. Thanks guys!
bbedward said:
https://github.com/bbedward/ZenKernel_Shamu/commits/sched_upstream_bfs_gc
You should be able to pull in the latest 4 BFS patches from the bfs_gc branch. I think I should have pulled them into the BFS_standalone branch but wasn't paying attention [emoji14] they are all minor, but good things from at least a developer perspective
Click to expand...
Click to collapse
Also wanted to say I greatly appreciate the way you have your git organized. From a devs perspective it makes it 100x easier to see how you implemented your changes. Very helpful. Thank you!
buckmarble said:
Also wanted to say I greatly appreciate the way you have your git organized. From a devs perspective it makes it 100x easier to see how you implemented your changes. Very helpful. Thank you!
Click to expand...
Click to collapse
this is the goal. It makes it easy to just do something like "git pull zen BFS_standlone" and only get the bfs stuff, etc. Also to not have to search through pages of commits to find a certain set of changes.
I get a little unorganized in the misc branches, but I can't have one for everything
bbedward said:
this is the goal. It makes it easy to just do something like "git pull zen BFS_standlone" and only get the bfs stuff, etc. Also to not have to search through pages of commits to find a certain set of changes.
I get a little unorganized in the misc branches, but I can't have one for everything [emoji14]
Click to expand...
Click to collapse
You're a cool dude. I love your attitude and willingness to share and help. Kudos!
Yup cool dudes here!!
Kernel running great so far, thanks!
May the 4th be with you kernel version posted in OP.
Buck added in some BFS patching. Thanks @bbedward.
Can I Flash this over my current kernel (Franco) Or do I need to re-flash my ROM first? Thanks for the work guys.
Diesel779 said:
Can I Flash this over my current kernel (Franco) Or do I need to re-flash my ROM first? Thanks for the work guys.
Click to expand...
Click to collapse
Go ahead.. I use root explorer and check system/init.d/etc and delete any scripts if they're there just to make sure nothing messes with the new kernel then flash 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"
}
Simple Kernel - Shamu
Simple Kernel is a kernel for Shamu that aims to be just that; a simple kernel. I believe in having too much stuff that really doesn't contribute to a better user experience should not be added into a kernel, and that's the ideology that I built this kernel with. I present Simple Kernel. I hope you enjoy it!
Features:
Sourced from latest Shamu kernel release (nougat-mr-1.5) up to July's security patches.
Upstreamed to 3.10.107 - Thanks to @The Flash for his guide to upstreaming a kernel
Built with vanilla Linaro GCC 7.1.1 - Thanks to The Flash's gcc build tool I used
Upstream F2FS support
LZO Compressed kernel - fast decompression at boot time
Power Suspend power management - Thanks to @faux123 and @Yank555
Hotplugs: Intelliplug v4.0 & Mako Hotplug + Stock - Thanks to faux123 and @franciscofranco
CPU governors: Nightmare & ElementalX + Stock - Thanks to @Alucard24 and @flar2
I/O Schedulers: Zen & Row(just enabled it) + Stock - Thanks to @bbedward
Intellithermal v3 - configurable thermal management - Thanks to faux123 Adjustable max temp for stock thermal monitor - Thanks to franciscofranco
Simple GPU Algorithm - configurable way to improve stock msm_adreno_tz governor - Thanks to faux123
KCAL Color Control - Thanks to @savoca
Zen-Tune v4.5 - improves overall responsiveness - Thanks to @frap129
Power Efficient Work queues - can save some battery - Thanks to neilbrown
Disabled BCL (for now, was causing me issues)
No force-encrypt or dm-verity
Safe GCC Optimization flags for Shamu - (-O2, -mtune=cortex-a15, -marm, -mfpu=neon-vfp4, -pipe)
Some misc fixes and stuff here and there
No excess/magical optimizations or patches
Look at my commit log for full list for everything in the kernel
Changelog:
Just look at commit log. Make it easy.
Installation:
Download latest build
If on another kernel, flash your ROM's (or stock) boot img in TWRP Recovery. If coming from Simple Kernel, proceed to step 3.
Flash kernel in recovery
Wipe Cache/Dalvik-Cache
Reboot
Done
FAQ:
Q: There was a random reboot or some other issue! What do I do?
A: Pull logs, send them to me. Address issues publicly in thread so everyone can benefit/chip in.
Q: Can you add XYZ feature/patch?
A: Perhaps I can. I am always open to adding things, as long as it maintains the soul of the kernel. Giving me a place to find it also helps. You can also create a pull request on Github if you have the commits.
Q: How do I pull a log that you asked for?
A: I use (play store, free) Kernel Adiutor to pull logs. In KA, go to Settings -> Debugging -> Driver Message & -> Last kmsg. Send me the txt files created in /sdcard. Not doing this when bringing up an issue will result in loss of my support and is not good practice when asking for help.
Q: What is F2FS? How do I convert to it?
A: Googling will do you well, this gives a good overview of what is is. This thread might help you decide if it's right for you. Read my instructions in my TWRP w/F2FS thread to see basic conversion instructions.
Disclaimer:
I am not responsible for anything that happens to your device. Period.
External Thanks:
designapp.io for the logo
Download:
See second post
XDA:DevDB Information
Simple Kernel, Kernel for the Nexus 6
Contributors
Black_Hat01, Contributors listed by-contibution
Source Code: https://github.com/BlackHat01/SimpleKernel-Shamu
Kernel Special Features: F2FS, Linaro Compiled - Smooth, Simple & Stable
Version Information
Status: Stable
Current Stable Version: r2
Stable Release Date: 2017-07-05
Created 2017-07-02
Last Updated 2017-07-05
Download
Download latest build - r2
So far so good...
With six ROM 3.9
"Sent from the Dog Pound"
cujo6801 said:
So far so good...
With six ROM 3.9
"Sent from the Dog Pound"
Click to expand...
Click to collapse
Good to know :good:
Cool thanks
Sent from my Nexus 6 using Tapatalk
About the LZO compressed kernel, I was under the impression that the boot would be faster if the kernel wasn't compressed at all. I don't know how large the uncompressed kernel is, but since it gets decompressed at boot anyway, perhaps it'd be better to just have it uncompressed to begin with?
espionage724 said:
About the LZO compressed kernel, I was under the impression that the boot would be faster if the kernel wasn't compressed at all. I don't know how large the uncompressed kernel is, but since it gets decompressed at boot anyway, perhaps it'd be better to just have it uncompressed to begin with?
Click to expand...
Click to collapse
An uncompressed kernel image would probably boot faster in our case since our CPU/RAM is fast enough to handle an operation as such. Only issue however is the uncompressed kernel sizes in at about 20 mb in our case, and is too large for our device's boot partition (I think around 16 mb), and won't be able to be installed to the device at all, producing an error saying the image is larger than the boot partition.
EDIT:
Also by "faster", I am comparing it to other popular compression methods such as xz.
Build r2 live
Build r2 is live with minor changes. Here's an overview of what's changed:
- Reverted Intellithermal and replaced it with franco's max temp tuner due to stability issues
- Merged latest July security patches from google
Happy flashing!
Black_Hat01 said:
An uncompressed kernel image would probably boot faster in our case since our CPU/RAM is fast enough to handle an operation as such. Only issue however is the uncompressed kernel sizes in at about 20 mb in our case, and is too large for our device's boot partition (I think around 16 mb), and won't be able to be installed to the device at all, producing an error saying the image is larger than the boot partition.
EDIT:
Also by "faster", I am comparing it to other popular compression methods such as xz.
Click to expand...
Click to collapse
LZO is going to be the best available. Also, Intellithermal is outdated. I would stay away from it. May I ask what issues you had with BCl. I always had it disabled in my kernel, I believe it to be the cause of early shutdowns that people report (especially when the power draw it too much).
apophis9283 said:
Also, Intellithermal is outdated. I would stay away from it.
Click to expand...
Click to collapse
Agreed. I decided to just give it a shot because I wanted to see if I could add some more options for as far as thermal drivers goes but it just doesn't do anything better than stock thermal throttling + Franco's userspace temperature adjustment patch, and like you said, was not updated since it's initial port to qcom devices by faux. Decided to squash it from here out.
apophis9283 said:
May I ask what issues you had with BCl. I always had it disabled in my kernel, I believe it to be the cause of early shutdowns that people report (especially when the power draw it too much).
Click to expand...
Click to collapse
This is actually a good point. I believe as of now, I will bring it back in the near future. I had some rebooting issues, and I *thought* BCL was the cause, but it now seems it is due to RQ Affinity (still working on getting it ironed out). Once I figure out the real cause of my very sparse reboots, I will most likely bring it back, as the upsides seem to outweigh its seemingly negatives(never really figured these out ), especially with Franco's BCL modifications.
Black_Hat01 said:
Agreed. I decided to just give it a shot because I wanted to see if I could add some more options for as far as thermal drivers goes but it just doesn't do anything better than stock thermal throttling + Franco's userspace temperature adjustment patch, and like you said, was not updated since it's initial port to qcom devices by faux. Decided to squash it from here out.
This is actually a good point. I believe as of now, I will bring it back in the near future. I had some rebooting issues, and I *thought* BCL was the cause, but it now seems it is due to RQ Affinity (still working on getting it ironed out). Once I figure out the real cause of my very sparse reboots, I will most likely bring it back, as the upsides seem to outweigh its seemingly negatives(never really figured these out ), especially with Franco's BCL modifications.
Click to expand...
Click to collapse
I had a toggle for BCL on mine. My source for it is since lost but that may have been added when Yoinx was part of my team. I had it off by default but people could toggle it on. Do you have it set to off? (RQ Affinity)? I started this on my PC but Ill upload screenshot of what I have going on.
Screenshots
apophis9283 said:
I had a toggle for BCL on mine. My source for it is since lost but that may have been added when Yoinx was part of my team. I had it off by default but people could toggle it on. Do you have it set to off? (RQ Affinity)? I started this on my PC but Ill upload screenshot of what I have going on.
Click to expand...
Click to collapse
I seem to not run into any rebooting with it set to 0 (so off). A BCL toggle would be great. If I could get that into my kernel that will guarantee BCL's return.
EDIT:
Looking at your setup, mine is quite similar, except of course the BCL switches. And currently affinity at 0 for testing.
Black_Hat01 said:
I seem to not run into any rebooting with it set to 0 (so off). A BCL toggle would be great. If I could get that into my kernel that will guarantee BCL's return.
Click to expand...
Click to collapse
This is blackbird kernels source with some of my commits and Ill link you to really old source of my kernel that Yoinx had. I had bad issues setting that to 0. Use RQ Affinity 1 and see if they don't stop. Trust me, I made a kernel for this device for the longest time. If there was a mistake to make I made it. Over a year, 2 version of Android. M and N. If you want..... Get me a log at the next reboot and I would be happy to help
https://github.com/B14CKB1RD-Kernel...2a3c94a/drivers/power/battery_current_limit.c
https://github.com/yoinx/Singularit...a36e6e1/drivers/power/battery_current_limit.c
apophis9283 said:
This is blackbird kernels source with some of my commits and Ill link you to really old source of my kernel that Yoinx had. I had bad issues setting that to 0. Use RQ Affinity 1 and see if they don't stop. Trust me, I made a kernel for this device for the longest time. If there was a mistake to make I made it. Over a year, 2 version of Android. M and N. If you want..... Get me a log at the next reboot and I would be happy to help
Click to expand...
Click to collapse
Almost laughed. Got a reboot while reading this. Anyways, I appreciate your willingness to help. Not by any means an expert here, and still new at making use of my own logs, so I'll take all I can get. Here's my kmsg from last reboot. This was with affinity 0, so affinity is ruled out as the cause of the reboots at least (had them with 1 too)
apophis9283 said:
https://github.com/B14CKB1RD-Kernel...2a3c94a/drivers/power/battery_current_limit.c
https://github.com/yoinx/Singularit...a36e6e1/drivers/power/battery_current_limit.c
Click to expand...
Click to collapse
Thank you so much for this. Will look into it tomorrow when I get on my PC.
EDIT:
Heading off to bed in a bit. Got work and classes tomorrow. Will read what you have to say in the morning. Thank you again.
Black_Hat01 said:
Almost laughed. Got a reboot while reading this. Anyways, I appreciate your willingness to help. Not by any means an expert here, and still new at making use of my own logs, so I'll take all I can get. Here's my kmsg from last reboot. This was with affinity 0, so affinity is ruled out as the cause of the reboots at least (had them with 1 too)
Thank you so much for this. Will look into it tomorrow when I get on my PC.
EDIT:
Heading off to bed in a bit. Got work and classes tomorrow. Will read what you have to say in the morning. Thank you again.
Click to expand...
Click to collapse
Im gonna look at it in a second. In the mean time here is my BCL file
Edit: Do the reboots only happen when using certain apps? I expected to see a watchdog bite for IRQ and I didnt.
apophis9283 said:
Im gonna look at it in a second. In the mean time here is my BCL file
Edit: Do the reboots only happen when using certain apps? I expected to see a watchdog bite for IRQ and I didnt.
Click to expand...
Click to collapse
Thanks. They seem to random, however, the apps that I can remember reboots occuring in are FX File Explorer, Clash of Clans(yes I play this ancient game), Google Camera(video), XDA Labs, and once while suspended.
Black_Hat01 said:
Thanks. They seem to random, however, the apps that I can remember reboots occuring in are FX File Explorer, Clash of Clans(yes I play this ancient game), Google Camera(video), XDA Labs, and once while suspended.
Click to expand...
Click to collapse
Try RQ Affinity value = 1. If not I have another idea
apophis9283 said:
Try RQ Affinity value = 1. If not I have another idea
Click to expand...
Click to collapse
Actually have been doing that since last night, alongside switching to Mako plug. No reboots with heavy usage this morning.
EDIT:
Guess the culprit would be intelli plug
Black_Hat01 said:
Actually have been doing that since last night, alongside switching to Mako plug. No reboots with heavy usage this morning.
Click to expand...
Click to collapse
Feel free to PM me if you need anything.
{
"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"
}
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 ROM 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.
I don't provide support for OneUI-pie & treble ROMs, asking me if I will ever do is just a waste of time.
INFO:
If you wonder what the hell RAD Kernel is... Then let me explain, RAD Kernel is a project oriented towards people who depend on their phone every day.
RAD Kernel is designed for maximum stability.
All kernel builds are thoroughly tested before Release.
As the title says RAD Kernel per se supports AOSP ROM(s), OneUI 2 ROM(s) and it's meant to be used with it for a better STABLE experience.
RAD Kernel will NOT work with any other ROMS except AOSP & OneUI-2 (i.e no OneUI-pie & treble support).
SUPPORTED DEVICES:
G950(N/F/FD)
G955(N/F/FD)
N950(F/FD)
FEATURES:
Linux 4.4.111
Compiled with Clang 9.
O3 optimizations.
Fast, smooth and great for Daily Use!
Permissive SE-Linux.
Boeffla Wakelock Blocker.
Interactive governor as Default.
Optimized Integer SQRT. for upto 3x faster operation.
Tuned Interactive governor for better balance between performance and battery.
CPU BIG up to 2314MHz.
CPU small up to 1690MHz.
GPU OC up to 572MHz
WireGuard.
Disabled CRC by default - 30% File system performance.
Fsync toggle enabled by default, can be changed in a kernel tweaker.
TCP congestion - bic as default.
Z-RAM enabled by default and set at 2592MB.
Z-RAM compression - lzo
HMP values tuned for better performance!
and the list goes on!
ROOT:
RAD Kernel DOES NOT come with pre-installed ROOT.
You can flash the latest MAGISK to get ROOT!
SUPPORT:
Telegram Group - Click here!
Telegram Channel - Click Here!
CREDITS:
Me, for developing without time and for the struggle to test new things.
Stricted for LineageOS development.
Dr.DoubtReaper for testing my kernel images.
Samsung Open Source for their Kernel source.
Topjohnwu for magisk!
Linus torvalds for Linux!
Thanks to anyone else who made this whole thing possible, you are part of it as well!
and all the people on GitHub whom i might have cherry-picked from!
XDA:DevDB Information
RAD Kernel for Exynos8895, Kernel for the Samsung Galaxy Note 8 (2017 Phone)
Contributors
Live0verfl0w
Source Code: https://github.com/Exynos-nigg/RAD-8895
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R4
Stable Release Date: 2021-01-07
Created 2020-10-05
Last Updated 2020-11-08
R4 (07/01/2021) [EOL]
BUGS:
DexOnPc is bugged, device wont be recognized (OneUI2 build only!)
DOWNLOADS:
Official Kernel Website - click here!
Google Drive - click here!
INSTALLATION:
NOTE! YOU NEED TO BE ALREADY ON AOSP/OneUI-2 ROM, BEFORE FLASHING THIS CUSTOM KERNEL
Download the provided zip for your device model.
Put the zip inside your storage.
Reboot to TWRP recovery.
Flash the zip and wait until it completes.
Reboot your device, and enjoy the Butter smooth experience.
CHANGELOGS:
R4(07/01/2021)
Added OneUI-2 support! (make sure to flash the OneUI-2 build)
Disabled logging and some debug stuff
Older changelogs below! =)
R3.5 HOTFIX(08/11/2020)
Unified installer zips!
Fix bootloop issues!
Switch from AK3 to AIK zips!
NOTE: This releases has no changes kernel side, but the installation zips have been changed!
NOTE: Sorry for the inconveniences caused because of the bootloops, this releases should (hopefully!) fix em =)
R3 (04/11/2020)
Disabled GFS (Gentle Fair Sleepers) for better UI performance!
Fix placebo tweaks blocker!
General optimizations!
Kill DVFS completely!
Remove excessive logging from decon, GPU drivers & touchscreen drivers!
Unified S8/S8+ kernel!
Set "westwood" as default TCP congestion algorithm!
NOTE: The kernel zips have different time labels on them because i did build them few days before but was just lazy to release them
R2 (13/10/2020)
Changed to Interactive on CPU!
Fixed sound not coming from earpiece!
Remove Audit dependency!
Enabled touch input booster!
Disabled Hotplug!
Change default IO scheduler to "deadline"!
Disable some logging!
This kernel build should be way smoother than R1!
R1 (05/10/2020)
Initial Release!
FAQ: (Read this before flashing the kernel and reporting bugs!)
Q. Gaming performace isnt good in this kernel!
A. Disable Samsung Hotplug from your preferred kernel tweaker app! Hotplug is disabled in builds from R2 onwards!
Q. Whats Fsync? should i disable it?
A. fsync transfers ("flushes") all modified in-core data of (i.e., modified buffer cache pages for) the file referred to by the file descriptor fd to the disk device (or other permanent storage device) so that all changed information can be retrieved even after the system crashed or was rebooted. This includes writing through or flushing a disk cache if present. The call blocks until the device reports that the transfer has completed. It also flushes metadata information associated with the file (see stat(2)).
Too scientific, didnt read! : In layman terms disabling Fsync gives you better performance with the risk of a Data loss/corruption during a system crash!
Q. I cant Flash NFS injector, FDE.AI, MAGNETAR and other tweakers on this kernel!
A. I have added a in-built kernel blocker to block installation of these so called "AIO kernel tweakers". You shouldnt install these tweaks in my opinion! If you still want to use a Tweaker, i prefer you use KTweak though i wont be providing support for issues if u have flashed any mods or anything of this likeliness!
Q. I have an issue and i have reported it in the XDA thread, yet nobody replied to me.
A. I might be slow in responding for issues reported in the XDA thread, if u want me to reply more faster, report it in the Telegram support group!
Q. My phone gets HOT while using this kernel!?
A. Short answer: It's your own issue, fix it yourself. Nobody makes a kernel just to burn your hands.
Long answer:
* Install Termux app from Play Store * Enable screen rotation, open Termux in landspace mode * Type this command: su -c top -d 2 * A list of processes will appear and refresh with 2s interval. Find which process consumes the most CPU usage with [%CPU] column and the package name in ARGS column. You should see the culprit of your issue.
Reminder: There is no such thing as "I have nothing in background but the phone still heats up". There definitely something happen and 99% of the time it's some of the rogue apps running in background.
Thanks to Diep Quynh for finding this one out!
I've tried it and for some reason left top corner of the screen never responded to touch. Ex: I couldn't turn on wifi from quick toggles n back arrow in some apps as I couldn't make a touch on left corner...
I didn't collect logs as I immediately reverted back to old kernel.
arjun.reddy said:
I've tried it and for some reason left top corner of the screen never responded to touch. Ex: I couldn't turn on wifi from quick toggles n back arrow in some apps as I couldn't make a touch on left corner...
I didn't collect logs as I immediately reverted back to old kernel.
Click to expand...
Click to collapse
Could you tell me which rom and device please?
Me or any of my testers didnt find this issue.
Live0verfl0w said:
Could you tell me which rom and device please?
Me or any of my testers didnt find this issue.
Click to expand...
Click to collapse
I am on Resurrection Remix Q Using NOTE 8 (SM-950F). I will flash the kernel again n let you know if it's replicable.
Finally new kernel for my note 8
I'll give it a try
and post feedback after testing for few days
I have small question
which is better... EAS or HMP?
Thanks
Alastal said:
Finally new kernel for my note 8
I'll give it a try
and post feedback after testing for few days
I have small question
which is better... EAS or HMP?
Thanks
Click to expand...
Click to collapse
As a dev i really cant compare, but u can try it and decide for urself:good:
I have this weird bug with the earpiece still not working on the new version of the Kernel
I am using the Official HavocOS rom on my Galaxy Note 8
Alessandro2003 said:
I have this weird bug with the earpiece still not working on the new version of the Kernel
I am using the Official HavocOS rom on my Galaxy Note 8
Click to expand...
Click to collapse
Its a ROM issue, which has been already identified by the rom dev, u can join their telegram group to know this
New kernel build is up guys! =)
Currently running the newest build, runs great, thanks for the work. 6h SOT and still 50% battery. Just wondering, any reason hotplug is disabled? Does it really impact performance that bad? Or is it just samsungs implementation? Tried to build a custom version using your source (with a big core oc and an undervolt), cant seem to for some reason. Once again, thanks for the great work. Any way to buy you a Coffee?
Hotfix build is uploaded, sorry for the inconveniences caused by the bootloop issues =)
Excudent said:
Currently running the newest build, runs great, thanks for the work. 6h SOT and still 50% battery. Just wondering, any reason hotplug is disabled? Does it really impact performance that bad? Or is it just samsungs implementation? Tried to build a custom version using your source (with a big core oc and an undervolt), cant seem to for some reason. Once again, thanks for the great work. Any way to buy you a Coffee?
Click to expand...
Click to collapse
Hi mate!
1. hotplug is disabled cuz in my tests i found em to degrade performance and doesnt make much of a difference battery life wise, hence disabled and yes its a samsung implementation.
2. For OC u can pick ace2nutzers a2n kernel commits, i have tested em and it works
3. as for the undervolt, i havent tried em and probably wont be =)
4. Thanks very much, i dont need coffee or beers and stuff, u can hit the thanks button =)
Thanks and regards,
Stay Safe!
I am using this kernel on android 10 oneui
after i flashed the kernel i had weird issue concerning samsung clear case
when i close the case the screen turn on and when i open the case the screen turns off!
it acts in the opposite manner!
N950N supported?
is there any way to change to enforcing?!
Excudent said:
Currently running the newest build, runs great, thanks for the work. 6h SOT and still 50% battery. Just wondering, any reason hotplug is disabled? Does it really impact performance that bad? Or is it just samsungs implementation? Tried to build a custom version using your source (with a big core oc and an undervolt), cant seem to for some reason. Once again, thanks for the great work. Any way to buy you a Coffee?
Click to expand...
Click to collapse
But how? Can you share your settings?