{
"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"
}
Click to expand...
Click to collapse
"This is your last chance.
After this, there is no turning back.
You take the blue pill -
the story ends, you wake up in your bed and
believe whatever you want to believe.
You take the red pill
- you stay in Wonderland and
I show you how deep the rabbit-hole goes."
- Morpheus, The Matrix
(Copyright belongs to the Wachowski Brothers... Larry and Andy)
Click to expand...
Click to collapse
Kernel Source: RedPill Source Based on N7100 Source Drop (until Rev1.00). Rev1.01 and beyond are currently based on N8000 sources. This Kernel is for the N7100 International Version Only!!!
MatrixPills Image by Corinne Wilger. Visit her site HERE.
What Some HyperDroid RedPill Users Have Said:
"so far this the only kernel which gives me the least wakelocks.. or hardly any.... good job..
i dont care about benchmarks which ppl are whining about.. i would say this kernel rockz" - xinfinityoO
Click to expand...
Click to collapse
"Batterywise the best kernel on my device - had not encountered just 2% loss in 7 hours at night for a very long time"- zikarus
Click to expand...
Click to collapse
"first impressions... blazing fast...smooth... hopefully no issues
(well never had one with previous releases anyways)...cheers pongster!"- jermitano
Click to expand...
Click to collapse
"I am stunned. The battery life looks great. Very smooth and stable and great response. Great work guys."- mariosraptor
Click to expand...
Click to collapse
"Awesome work! That's the least I could say. Real development and all that done during free time.
I've made donations but that won't be enough to show my gratitude. I know you don't do that for money but
that's the only way I can think of tell you all how grateful I am."- mbutandola
Click to expand...
Click to collapse
Click to expand...
Click to collapse
RedPill Features
Highlights
Exynos-Abuse Secured (Thanks to AndreiLux for the original low level patch & Samsung for the Official Fix)
SDS patch included
Ramfs from Stock Kernel + Busybox and its various functions in /sbin
Versions up to Rev1.00 were Based on Samsung Galaxy Note 2 N7100 Source Drop Release 1; Rev1.01 and up are based on N8000 Sources
Included patches for performance, stability and battery life
Init.d support
SetCPU, ROM Toolbox and Voltage Control Support
CPU Overclocking and Undervolting Support (Thanks to AndreiLux)
GPU Overclocking and Undervolting Support (Thanks to AndreiLux)
Enable or Disable File Syncing
(fsync disabled by default as I've tweaked the system for optimum latency designed for Flash Storage)
CFS Autogroup by Mike Galbraith Enabled
CPU Topology and Sched_MC enabled
AFTR and LPA enabled
A lot of tunables via sysfs included (Use ROM Toolbox or similar Utility to easily change it)
Git Implementation of SHA-1 for 12% faster boot time
CPU set at 1.6Ghz at Boot for faster boot time (Thanks to Imoseyon)
LZO compressed kernel using optimized values for the size of the kernel for faster boot time (Using faster lzo code from mainline)
CIFS Support (cifs.ko located in /lib/modules) | Tweaked Ext4 Filesystem
(Patches + Mount Options + Tweaked IO Schedulers leaning towards latency for Flash Storage)
sio | zen | row | noop | deadline (tweaked for better latency and balanced throughput for Mobile NAND based devices)
Tweaked the mount options for Ext4 to adapt to the current focus on latency
pegasusq CPU Governor (Thanks to AndreiLux for the some of the new governor specific logic he added)
WiFi Multicast Blocked (Thanks to Entropy512)
Using Google Toolchain 4.7 + compiler optimizations specific for that version (Thanks Google & Linaro)
Power Saving Features:
AFTR + LPA enabled
sched_mc enabled (set at 2 by default)
ARM CPU Topology enabled
No HZ enabled
Boot Time Features:
Used git Implem of SHA-1 for 12% Boot time improvement
Added [PATCH] arm: remove "optimized" SHA1 routines by Linus Torvalds
Added [PATCH] arm: remove stale export of 'sha_transform' Linus Torvalds
Set Clockspeed at 1.6Ghz at Boot time to ensure all critical tasks have enough power to perform them while
the governors/maxfreq isn't set yet. (Thanks to Imoseyon for this hack)
CPU Features
Supports CPU Overclocking and Undervolting (Thanks to AndreiLux)
Supports GPU Overclocking or Undervolting (Thanks to AndreiLux)
pegasusq CPU Governor pegasusq set as default (obviously)
Filesystem Features (Currently Supported)
ExFat (Using Proprietary Samsung Modules) *Stock based RedPill only
Fat32
Ext2/3/4
CIFS (cifs.ko is in /lib/modules)
Ext2Int for N7100 (Thanks to mattiadj for idea and base script that I used to get it fully working on N7100 and RedPill) (ExFAT and FAT32 only) *Stock based RedPill only
I/O Schedulers
SIO (2012 0.2 version) (tweaked for Flash) Set as Default
deadline (tweaked for Flash)
zen (Thanks to bbedward)
noop
row (Thanks to Tanya Brokhman)
Tweaked values in deadline and SIO I/O scheduler to give better than average throughput while attemting to improve latency (if not more aggressive). Based on our initial (indicative, not conclusive... yet) testing, having these in line with the vm dirty, expire, writeback values + ext4 mount options to "schedule" write outs as fast as the system can handle it works quite well to balance throughput with latency expected in a mobile device. We took the big picture view and tested our tweaks instead of copy pasting random "known" good values and challenged some assumptions even we had at the start. The result is a mobile device tuned for average throughput and balanced battery life with good latency (not the lowest latency out there, but given the benefits of better I/O throughput and potential battery savings + extending the lifetime of NAND Based storage I think it was a compromise worth taking) I could have tweaked it for extremely great throughput and battery savings but that wouldn't be fun to use. I hate micro-lags myself.
Our Test Data regarding I/O schedulers and Kernel Tweaks can be found HERE.
The blog post that describes what we are trying to do can be found on my blog post HERE. (Thanks to s2d4)
Memory Features
Custom minfree values tweaked for 2GB RAM
Tweaked vm values in sysctl that's optimized for latency
Display Features
Stock mdnie values for more vivid details on the current generation of AMOLED Displays
Performance Patches Enabled
Mike Galbraith's Ultimate CFS Performance Patch (CFS Autogroup)
*More info on this here: https://lkml.org/lkml/2010/11/20/91
Added the CGroup Patch:*Added [PATCH] cgroup: Provides a way of tasks grouping by timer slack value
by Kirill A. Shutemov Based on patch by Jacob Pan. Introduces per cgroup timer slack value
which will override the default timer slack value once a task is attached to a cgroup. It's useful in mobile devices where
certain background apps are attached to a cgroup and minimum wakeups are desired.
Experimental Latency Related Patches
Disabled "fsync disabled" by default
(can be enabled by doing an echo "0" > /sys/class/misc/fsynccontrol/fsync_enabled
in a terminal emulator or as a script for gscript or scriptmanager) (Or use STweaks to toggle it) (Thanks to Ezekeel)
Using the tweaked Ext4 filesystem + scheduler and mount options leaning towards latency + vm values in the kernel
makes the most of the speed of Flash Storage based devices. At the speed at which the data is written to and from the kernel
to the Fast Storage devices, you would only lose up to 1 second worth of data at most IF the kernel crashes.
I don't plan on that happening so I enabled the system to get the maximum possible performance in this area.
Tweaked Ext4 Filesystem (Patches + Mount Options + Tweaked IO Schedulers leaning towards latency)
Tweaked the mount options for Ext4 to adapt to the current focus on latency
3rd Party Kernel Apps Support
STweaks by gokhanmoral
ROM Toolbox by jrummy
SetCPU by michaelhuang
System Tuner
Voltage Control | ExTweaks by xan
Credits and Disclaimer
Credits: (Huge props to all the devs I've learned from by reading and studying their code)
faux123
Ezekeel
franciscofranco
supercurio
hardcore
Netarchy
Hacre/Ninpo
Chainfire
Erasmux
Imoseyon
gokhanmoral
Tegrak
Entropy512
AndreiLux
cattleprod
dvtonder
All the hardworking Kernel Devs at lkml.org
(Linus Torvalds, Jens Axboe, Mike Galbraith, etc.)
Special Mention to the following:
To my mates at the HyperDroid Dev Team: (who help me test and refine the features of our kernel for our ROM)
D.O.C. (formerly doctorcete) (for the friendship and being an example of diplomacy in
dealing with usual ****storm of questions from users who refuse to search and read)
kristofpetho (for his excellent work on the HyperNote and his patience with dealing with bugs that destroy the user experience)
Arighi (for the initial guidance on how to get the kernel booting and working & a lot of battery driven patches)
AF974 (for the Overcome based Recovery on S2 that's so bad ass I want to stay in recovery all the time.)
petsasj (for his great work on HyperDroidParts for S2 and all future Apps that are just pure awesomesauce!)
sicopat (for letting us use his server and helping us out with a lot of things smali)
s2d4 | phly-phantom | amerikian (for testing everything at the risk of the potentially time sucking Soft Brick...)
Disclaimer: I made this for my personal use and has been personally tested by me and my team (HyperDroid Dev Team).
While it may work for other N7100 International ROM's, we have not tested it personally.
You have the liberty to choose to use this Kernel and by flashing this Kernel you will have
surrendered your right to complain that you lost your Warranty. If you're smart enough to figure
out WHY you need a Custom Kernel, you SHOULD be smart enough to undo it if you need your
device serviced officially. If your device explodes, melts or otherwise disintegrates from its awesomeness
I shall NOT be held responsible.
Reposting the Kernel: Please don't repost this kernel anywhere else.
Keep the download links intact as I have taken the effort to provide fast links for everyone.
If you can't understand English well enough and feel the need to re-post this kernel on
a foreign language web site or forum, please let me know first and link to this page...
(Google Translate can make it easier to read in your Native Language)
RedPill Stable Change Log
Current and Future Changelogs can be found HERE.
Rev1.01
Completely Rebased on N8000 Source
Use newest and official Exynos-Abuse patch from Samsung (Thanks to AndreiLux for the additional patches re: static cma regions)
Fix Freezes for some Devices when transferring large files via USB
Fix SOD for some Devices
Change CPU Idle Settings back to stock
Remove Dynamic FSync (Ability to enable or disable FSync is still available)
Removed ROW I/O as sio/deadline/zen perform better in our tests
USB Charging Rate increased to 1700
Tweaked pegasusq for battery life (limit sampling rate in suspend)
Removed Conservative (as new tweaked pegasusq can save battery with the right settings)
Added Dynamic STweaks XML Implementation by AndreiLux (Thanks to AndreiLux)
Updated STweaks (Thanks to Gokhan Moral)
use get_random_int() to fix entropy depleting (Thanks to Jeff Liu)
Updated sensorhub driver, device sensors
SDS patch included (Thanks to AndreiLux)
Rev1.00
Exynos-Abuse Secured thru the low-level fix by AndreiLux (Thanks to AndreiLux)
Using Official Google Toolchain 4.6.x
Added the latest (v5.4) of the "faster crc32 algorithm" by Bob Pearson and Darrick Wong (Thanks to both of them)
Added faux123 Dynamic fsync (Thanks to faux123)
Enable Dynamic FSync and FSync Control to co-exist (Please read STweaks option to gain a better understanding)
Backported ROW I/O scheduling algorithm (Thanks to Tatyana Brokhman)
Revert to using original N7100 source bcmdhd drivers to fix WiFi for some users
Added ability to increase brightness to 255 (Thanks to nebkat)
Tick and workqueue updates from upstream kernel source (Please see commit log for details)
Remove ntfs auto mounting since people use ExFAT and FAT32 while NTFS can be loaded by 3rd party tools
Tweaked Ext2Int mount options
Tweaked System mount options
Rev0.10
Revert ExtSdCard mount points to default (To enable Ext2Int Tweak by mattiadj to work)
Added bbedward's zen i/o scheduler (Included in Stweaks options as well)
Added Option to OC to 1.8GHz after several weeks of testing for stability (Thanks to AndreiLux)
Added AndreiLux's STweaks Dynamic Config for CPU_UV, min/max freq and i/o scheduler (Thanks to AndreiLux)
Added updated pegasusq logic from newer Samsung sources (Thanks to AndreiLux for Original Port)
Added option in STweaks to swap internal and external sdcard (Thanks to mattiadj for original idea and script, which I then took and edited to ensure Full compatibility with N7100)
Added Proportional Rate Reduction for TCP (Thanks to faux123)
Tweaked deadline i/o scheduler
Rev0.9
Added Scoobydoo Sound (gokhanmoral's port of supercurio's Voodoo) (Thanks to gokhanmoral)
Added Scoobydoo specific Stweaks presets (Thanks to gokhanmoral)
Added sjkoon's Scoobydoo Sound fixes (Thanks to sjkoon)
Added android logging as a module (Use STweaks to toggle)
Rev0.8
Added STweaks support (Thanks to gokhanmoral)
Custom STweaks Entries specific to RedPill Features
Using Latest 201211 Linaro 4.7.3 Toolchain
Added NTFS Automounting support (for sdcard formatted as NTFS only, not OTG) Please Test if this works as I use FAT32
Added led blinking or fading choice from CM10 (Thanks to codeworkx and XpLoDWilD)
Rev0.7
Added UV Capability (arm voltages only) Implementation by AndreiLux (Thanks to AndreiLux)
Increase USB Charging rate by AndreiLux
Increased it even more to match AC charging rates (Experimental)
lowmemorykiller patches by Cyanogen Steve Kondik
Experimental optimizations to try and fix ZK camFW bug
Loads of Samsung OSRC updates c/o AndreiLux (Thanks to AndreiLux)
Wacom, Firmware, epen, sensorhub, camera firmware among others c/o AndreiLux (Thanks to AndreiLux)
Bug Fixes by AndreiLux on sound related source files
Rev0.6
Wakelock patch to save power (Thanks to Andrea Arcangeli)
Apply SCHED_FIFO to kthreadd (Thanks to Steve Muckle )
Testing latest Linaro 4.7 Toolchain
Camera Fix for ZKFI07 camFW (Thanks to nebkat)
Experimental Hotplug Awareness based on Load for Other Governors (Thanks to franciscofranco)
Updated lzop compression from current upstream version for a significant speed improvement (Thanks to Markus F.X.J. Oberhumer )
ARM: disable preemption in machine_shutdown (Thanks to Mike J. Chen)
Check source on github for detailed commit logs and messages
Rev0.5
Applied Vermagic patch to enable proper loading of proprietary modules (Thanks to jt1134)
Improved Latency of schedulers
Removed cfq and enabled sio as default io scheduler
Tweaked Pegasusq for smoother performance (Can be changed using SetCPU)
Ext4 patches from mainline for optimization and stability
Workqueue patches from mainline
Timer patch from mainline
Sched Race in Task Group Patch from mainline
Busfreq back to default voltages (for public release)
Fixed ExFat Loading Error (SLUB instead of SLQB)
LZO compressed kernel for more more speed
No Screen Sharpening (Only AndreiLux's Black crush fix which is in fact for the S3. Thanks for the Heads up AndreiLux)
Removed Auto EFS Backup to speedup boot process (You have an EFS Backup already, right?)
Rev0.4
Blocked multicast (Thanks to Entropy512)
Tweaked Pegasusq to start early in the boot process
CIFS built-in (no modules)
Tunneling built-in
Testing Out ezterry's 4.6.3 Toolchain
Fsync control by Ezekeel
Increased mmc timeout (Thanks to AndreiLux)
Added a few compiler optmizations for 4.6.3 Toolchain
Rev0.3
Sharpness Tweak by Hardcore (Thanks to hardcore)
Black Crush Fix by AndreiLux (Thanks to AndreiLux)
XZ Tweaked for faster boot and more efficient RAM
Enable 1.6Ghz at Boot time to speed it up just a bit more (Thanks to Imoseyon)
Various ARM topology patches
Enabled Timer Slack Controller
Rev0.2
Adjust tweaks in ramdisk
Tweaked CFQ
SMP fixes by Russel King
XZ compressed kernel (fast and small)
ARM topology
Sched_mc set at 2
Disabled Mali State Tracking
CIFS as a module
Rev0.1
Used N7100 source drop
Tweaked deadline and sio for throughput and better battery life
Tweaked conservative and pegasusq for slightly more aggressive performance
No UV
No OC
Using new SHA-1
Enabled Cleancache
Enabled Mike Galbraith's Sched Autogroup
Applied AndreiLux's sensor hub fix (Thanks to AndreiLux)
Using SLQB
CFQ by default
Using RWSEM Algorithm by Code Aurora
Tweaked kernel values using the redpill.sh in the ramdisk
Enabled init.d
Auto Backup of EFS
Using Toolchain 4.4.3
--------------------------------------------------------------------------------------
Naming convention:
x.y.z
"x and y" means they are stable releases tested by peers worldwide and have proven to be good enough to be a daily driver.
"z" is added to connote its an unstable release that is currenty being tested for new features introduced. Not for the faint hearted.
e.g. 0.2 is a stable release; 0.2.1 is an unstable test release
features in 0.2.1 that make the cut will make it 0.3 or the next stable release and so on...
RedPill Ultimate & AOSP Changelog
**AOSP (Will work with CM10 Based ROM's only)
Current and Future Changelogs can be found HERE.
Rev0.5
RedPill Stable PLUS:
AOSP specific Ramfs Tweaks
r3p0 mali
SLQB
jRCU instead of Tree Preempt RCU (Better for low latency and designed with small SMP systems like mobile devices in mind) (Thanks to Joe Korty)
mdnie, haptic, leds and touch leds patches by codeworkx and XpLoDWilD (Thanks to codeworkx and XpLoDWilD)
Added UV Capability (arm voltages only) Implementation by AndreiLux (Thanks to AndreiLux)
Increase USB Charging rate by AndreiLux (Thanks to AndreiLux)
Check source on github for detailed commit logs and messages
Rev0.6
Added gokhanmoral's additional bcmdhd-cm for CM10 (Thanks to gokhanmoral)
Experimental optimizations to try and fix ZK camFW bug
Rev0.7
Loads of Samsung OSRC updates c/o AndreiLux (Thanks to AndreiLux)
Wacom, Firmware, epen, sensorhub, camera firmware among others c/o AndreiLux (Thanks to AndreiLux)
Bug Fixes by AndreiLux on sound related source files (Thanks to AndreiLux)
Rev0.8
Added STweaks support (Thanks to gokhanmoral)
Custom STweaks Entries specific to RedPill Features
Using Latest 201211 Linaro 4.7.3 Toolchain
Added NTFS Automounting support for sdcard (Please test this as I use ExFAT)
Rev0.9
Added Scoobydoo Sound (gokhanmoral's port of supercurio's Voodoo)
Added Scoobydoo specific Stweaks presets (Thanks to gokhanmoral)
Added sjkoon's Scoobydoo Sound fixes
Remove Debugging but keep kallsyms for Scoobydoo
Rev0.10
Added bbedward's zen i/o scheduler (Included in Stweaks options as well)
Added Option to OC to 1.8GHz after several weeks of testing for stability (Thanks to AndreiLux)
Added AndreiLux's STweaks Dynamic Config for CPU_UV, min/max freq and i/o scheduler (Thanks to AndreiLux)
Added updated pegasusq logic from newer Samsung sources (Thanks to AndreiLux for Original Port)
Added option in STweaks to swap internal and external sdcard (Thanks to mattiadj for original idea and script, which I then took and edited to ensure Full compatibility with N7100)
Added Proportional Rate Reduction for TCP (Thanks to faux123)
Tweaked deadline i/o scheduler
Updated ramfs to 4.2.1
Rev0.11
Exynos-Abuse Secured thru low-level fix by AndreiLux (Thanks to AndreiLux)
Using Official Google Toolchain 4.6.x
Added Dynamic Writeback from 3.1 (Thanks to franciscofranco for the port)
Added the latest (v5.4) of the "faster crc32 algorithm" by Bob Pearson and Darrick Wong (Thanks to both of them)
Enable Dynamic FSync and FSync Control to co-exist
Backported ROW I/O scheduling algorithm (Thanks to Tatyana Brokhman)
Added ability to increase brightness to 255 (Thanks to nebkat)
Tick and workqueue updates from upstream kernel source (Please see commit log for details)
Remove ntfs auto mounting since people use ExFAT and FAT32 while NTFS can be loaded by 3rd party tools
Tweaked System mount options
Disable Ext2Int while I find a way to get around the new emulated mounts for multiuser support 4.2.1 brings (You can still use directory bind for some games and apps with large data requirements)
--------------------------------------------------------------------------------------
ULTIMATE VERSION HAS BEEN DISCONTINUED & DEPRECATED SINCE MOST FEATURES ARE FOUND ON STABLE
**Ultimate (Will not work with ExFat since I used SLQB)
Rev0.7
RedPill Stable PLUS: (New Features In Development will be on this Release)
SLQB
Busfreq Undervolting (less 100 mV)
LCD Undervolting
Touch LED Undervolting
jRCU instead of Tree Preempt RCU (Better for low latency and designed with small SMP systems like mobile devices in mind)
Added UV Capability (arm voltages only) Implementation by AndreiLux | gokhanmoral
lowmemorykiller patches by Cyanogen Steve Kondik
Check source on github for detailed commit logs and messages
Rev0.8
Experimental optimizations to try and fix ZK camFW bug
Loads of Samsung OSRC updates c/o AndreiLux (Thanks to AndreiLux)
Wacom, Firmware, epen, sensorhub, camera firmware among others c/o AndreiLux (Thanks to AndreiLux)
Bug Fixes by AndreiLux on sound related source files (Thanks to AndreiLux)
Remove all Debugging
Added STweaks support (Thanks to gokhanmoral)
Rev0.9
Using 201211 Linaro 4.7.3 Toolchain
Added led blinking or fading choice from CM10 (Thanks to codeworkx and XpLoDWilD)
Added NTFS Automounting support
Custom STweaks Entries specific to RedPill Features
Rev0.10
Added Scoobydoo Sound (gokhanmoral's port of supercurio's Voodoo) (Thanks to gokhanmoral)
Added Scoobydoo specific Stweaks presets (Thanks to gokhanmoral)
Added sjkoon's Scoobydoo Sound fixes (Thanks to sjkoon)
Added back android logging (Use STweaks to toggle)
ULTIMATE VERSION HAS BEEN DISCONTINUED & DEPRECATED SINCE MOST FEATURES ARE FOUND ON STABLE
--------------------------------------------------------------------------------------
FAAAQ's
Kernel Frequently Asked & Answered Questions (FAAAQ)
What exactly IS the RedPill?
The RedPill is a custom kernel for the Galaxy Note 2 (N7100) International version. It's aptly named to provide users a choice. This is how I would have built Samsung's stock kernel. So, I used the Samsung Source from their site as a base and added relevant patches that are built on the shoulders of giants... such as arighi, gokhanmoral, Entropy512, AndreiLux, codeworx, netarchy, hacre, franciscofranco, Ezekeel, imoseyon, Erasmux, cattleprod, hardcore, faux123, etc. and all the kernel hackers of the world that work on making this usable for all of us... I claim nothing to be original or created by myself... I simply put together features others have created that I personally would like to see and use in my own device and share it with the world because I can AND choose to do so... While I do bugfix the occasional compile error and test for near perfection, it's nothing compared to those who write most of the code for the Linux kernel. Major props to all of them!
Where is the source for building this Kernel?
You can find the source HERE. I love GPL and We should all support Open Source Software and its Developers. Please Note that Open Source doesn't mean all of this magically wrote and patched itself... it takes a lot of FREE time to do this and would appreciate if you let us know how you've improved the code.If you know what you're doing, you can easily build your own kernel too. *Please let me know if you have any improvements you feel should be included and send me a pull request. *If it tests okay, it may be included in the next release.
FYI, I'm not particularly fond of devs who release their source as tarballs. (I'm looking at 'ya Samsung!) I'm pretty sure you use a tool like git internally to manage all the changes and revisions. Why do you have to make it so hard for those that want to play with the source by releasing it in a tarball instead of publishing it on github or bitbucket? If you're a kernel dev that does this I consider you "open-forced" NOT "open source". If you don't want to use git and can't be bothered with it why not make a patch and upload that instead?
Does the RedPill support ROMs for N7105 and other N7100 variants?
As of the current Revision Released, I will not be working to making it work on a device I don't currently own. I only build kernels I can actually test myself. While "building blind" might work, I prefer to break my own device before someone else's as they probably paid good money and worked hard/smart to be able to afford the device. FYI, I'm also not in favor of devs who build blindly then ask for donations so they can support the device. I want to own my device, not let it be owned by those who donated their hard earned money to get you the device. I've seen too many "devs" build blindly then ask for a donation so they can support the device, only to find a newer, better and faster device comes out and then chooses to buy that instead of the device he built blindly for and actually got donations to buy it. Talk about Bait and Switch!
Why doesn’t the RedPill have high benchmarks?*
That’s done on purpose to keep YOU away. Seriously. The way the VM system is tweaked (dirty ratio’s, minfree values, etc.) + the focus on better latency in any type of load + a lot of other small tweaks all lead to good performance and battery drain in actual use (I like using my device and not keep it sleeping to bloat my battery stats, thank you). This may not give you the benchmark scores you want to be able to show off… which is good since it means YOU stay away from this kernel and continue to rely on benchmarks rather than actual usage.
Why should I even ROOT my device? Is a custom kernel more secure?
With the Exynos-Abuse Exploit out for ANYONE to use, you're probably better off rooting and installing a custom kernel that includes the fix of AndreiLux. (RedPill and Perseus as of this writing) Now I know it will void the warranty, as you all are aware of, but if the only way to secure your device and your personal data (You don't want anyone to see your google search terms and results as well as those "private" moments that you may have kept for yourself just like any normal person) is to root and install a secured kernel, what choice is Samsung giving you?
Can you imagine what a nefarious and talented malware developer could do with this? They could break your system and have a pop-up that says "Pay up to free your system from being one of my mobile drones"... OR "Donate to get the full features of your device" (This one actually happens a lot on XDA... some talented dev gives you partial features to lure you in... then WHAM, BAM, THANK YOU MA'AM... If you want the full features, please donate yada yada yada...) I digress, as always.
Now, would you rather wait till Samsung officially patches this exploit and run the risk of exposing yourself to the risks this exploit opens you up to? Don't assume malware devs aren't rushing their current code to try and pry their way into your system using this exploit. For all we know, they're busy trying to cover up a similar exploit and currently awaiting Play Store approval. Yes, even the Play Store Apps can compromise your system. Even if Samsung does act fast, (not as fast as AndreiLux since he fixed it in a jiffy) how sure are you that your system hasn't been compromised? You wouldn't even know it.
The best reason to root RIGHT NOW is to completely secure your system, now more than ever. If you need to claim a warranty, you can tell them:
a. I had no choice, you messed up, xda-devs cleaned it up.
b. Flash back stock kernel and remove any trace of root and your use of a custom binary.
c. Completely brick your phone and tell Samsung that the exynos-mem exploit was actually used by malware that zapped your system dead.
I'm not a fan of any of these choices since I believe warranties should be honored by the manufacturer, especially if the bug they created was the reason for the claim for warranty in the first place.
How do I know I'm secured from the Exynos-Abuse Exploit?
Don't rely on apps that tell you whether you're vulnerable or not as the low level kernel fix AndreiLux implemented doesn't need to change the permissions of the /dev/exynos-mem.
Try running Chainfires Exploit APK and try getting the exploit to say anything else but "FAILED"... or head over to the thread HERE and download the exynos-abuse binary and run it from a terminal.
$./exynos-abuse
Click to expand...
Click to collapse
If your shell changes from $ to # then the exploit was successful, if not then you're safe.
Can the RedPill be OC'd and UV'd?
It can be UV'd and OC'd.By default, I've decided to keep all voltages and clock speeds stock as experience has taught me that NOT ALL DEVICES ARE CREATED EQUAL. You can UV the CPU arm voltages and OC using 3rd party Apps that do that. (SetCPU, VoltageControl)
Can the RedPill GPU be OC'd and UV'd?
Yes. Thanks to AndreiLux. You'll need to use STweaks to fully configure this. YMMV as always.
Why a tweaked deadline and SIO I/O scheduler?
The deadline I/O scheduler by Jens Axboe has proven itself as a low overhead, high throughput and acceptable latency I/O scheduler. *When tweaked for NAND based Mobile devices, it does even better. *While it "starves" writes by default with a 2:1 Read:Write ratio, this can easily be tuned via sysfs.
Why is my favorite governor (whichever it is) not available?
Simplicity is the Ultimate Sophistication, as Leonardo Da Vinci eloquently said. *Based on extensive testing and user feedback, we gathered that these 2 governors included gave the best performance and battery life on our device. Simple choice to have only the best ones available based on actual testing and feedback. *I included only these governors so you all have a simple choice to make in finding your favorite one. *These are all tunable via sysfs so you can skew it towards battery or performance based on what is important for you. *Don't expect uber smoothness and 16 hours screen-on time though... *there will be compromises when leaning towards any of the two factors most users consider important in a kernel.
Why LZO Compression for the Kernel?
It decompresses much faster than any other, bar none. Since the kernel size and compression speed is not an issue when using LZO in the kernel. (You only decompress the zImage when booting. Compression is done when building the kernel) Don't believe me, believe the data right HERE.
Why ARM Topology and sched_mc?*(From linaro.org)
"The sched_mc function adds a power saving awareness to the Linux scheduler which is tuned for performance by default. When sched_mc is enabled, the scheduler tries to gather the running processes in a minimal number of cpus and clusters. This choice of the location of a process is done thanks to the cpu topology function which describes the affinity between cpus."
(more info HERE)
Why is my AndroidOS usage so high?
This is most likely a reporting error from Android itself. Use Better Battery Stats to closely watch what really eats your battery. That has shown to be more reliable. (If I were Android, I'd fold buy out BBS and fold its code in by default) If you still have doubts, do a real world battery test, as some have done, and they saw that their battery consumption actually remained the same or in some cases even improved. YMMV, of course. Let's not fall for "placebos" here and say that "hmmmm.... since AndroidOS must be high than my battery doesn't last as long!"
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Ultimate Version FAAAQ DEPRECATED SINCE MOST FEATURES ARE FOUND ON STABLE
Why SLQB? (According to its author, Nick Piggin)* (Only for the Ultimate Revision)
”SLQB is a slab allocator that focuses on per-CPU scaling, and good performance with order-0 allocations. Fastpaths emphasis is placed on local allocaiton and freeing, but with a secondary goal of good remote freeing (freeing on another CPU from that which allocated).” Using this on the Stable version breaks ExFat from working properly. Thus, the Ultimate version is for those who don't need ExFat support.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
HyperDroidDevs FAAAQ
Where do I report Issues or Get Community Support?
Use this thread to report issues, preferably with a last_kmsg, dmesg in a text file or a logcat. How do you do those? I'll let you use XDA's brilliant search function. And no, it's not broken, the search function that is. (I've heard that so many times... "Search isn't working so I posted a question here instead...")
Where are the HyperDroidDevs and their Team from?
We are an international team of crazy people who all have real life day jobs that are mostly not related in any way to Android Development. We're crazy enough to spend sleepless nights trying to make our devices (which we all personally own and have NOT been donated) better than how we received it. We come from all over. I am from the Philippines, where it's always FUN to be! We have Devs and Team members from Spain, Greece, France, Finland, Germany, Italy, Netherlands, Canada, USA, India, Poland, Philippines and even more countries.
How do I show my appreciation? Can I donate to you?
You can show your appreciation concretely in several ways:
Pressing the "Thanks" Button on XDA
Follow me on Twitter @sarcastillo and "Like" our Facebook Page
Report issues politely and completely
Donating any amount is completely up to you. *I look at donations as a "tip" for a job well done, rather than a "wage" or a "bounty" to get things done. *And Tipping is always up to you... the tipper. *I won't stop development if you don't donate, that's for sure, as I do this mainly for myself and my HyperDroid mates to begin with. I make more money running my own business than this hobby so “tips” are not a necessity… it just tells me how many people actually find the work useful enough to say thank you via a financial gesture.
This Kernel will ALWAYS be FREE to Download and USE, even if the time spent making it IS NOT FREE. *That's Open Source. (The time people spend on open source projects could have been used to spend more time with their families, for example. But the Devs commitment to get something done right is almost always tugging at him to Dev just a little bit more) *
*I've personally donated to Devs who've done things I would never have been able to figure out at the time they did figure stuff out. *Learning anything new takes time and time, in my book, is more important than money as I can't turn back time, while I can always earn money. SO I donate to Devs who spend their free time making Stuff better and easier for those of us who haven't figured out how to get it done.
Download Links
Download Links: (CWM/TWRP Version Only)
I've put the links down here to ensure you at least TRY to read the IMPORTANT info posted above.
Don't forget to enjoy the RedPill; it's Awesomeness Delivered!
RedPill
RedPill Stable Revision 1.42:
Click to download RedPill Rev1.42 (For Samsung Based ROM's for N7100) (DEPRECATED | NOT SUPPORTED)
RedPill Stable Revision 1.47:
Click to download RedPill Rev1.47 (For Samsung Based ROM's for N7100)
RedPill AOSP
RedPill AOSP Revision 1.47:
Click to download RedPill AOSP Rev1.47 (FOR CM10.1 and 4.2.2 based AOSP ROM's for N7100) (DEPRECATED | NOT SUPPORTED)
RedPill AOSP Revision 1.52:
Click to download RedPill AOSP Rev1.52 (FOR CM10.1 and 4.2.2 based AOSP ROM's for N7100)
One more for good measure
Really. One more.
Last one for me.
pongster said:
One more for testing
Click to expand...
Click to collapse
Mine again.
you had said that you would delete it in 5 minutes ,but what time is now?
Although my English is not good, I like xda forums very much, like the each friend! I hope you can point out my grammar mistakes to improve my English, thank you very much!
Thanks!!!
C-C-C-C-C-Combo breaker!
Edit: fail. Thanks guy above me -_- lol
Sent from my Galaxy Note II using Tapatalk 2
Y test thread??
Nice to see u here..looking 4ward to great themes now..
5 minutes over
Sent from my GT-N7100 using Tapatalk 2
Me
Sent from my GT-N7100 using xda premium
Woooooohhhhhooooo
Finally d kernel I was waiting for..
(Also waiting for siyah 2 b true)
Thank you so much pongster..
Used 2 loooove ur work on s2 and now on sn2..
Thank you very much..
Sent from my GT-N7100 using Tapatalk 2
Can use the kernel on hyper Rom? Thx
Sent from my GT-N7100 using xda premium
Obviously, this isn't really a test thread. I simply named it as such for the first 5 minutes so I could reserve the necessary posts I need to establish the HyperDroid RedPill Kernel thread.
DamBadz said:
Can use the kernel on hyper Rom? Thx
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
On HyperNote and other Samsung Based ROM's for the N7100
hiack said:
you had said that you would delete it in 5 minutes ,but what time is now?
Although my English is not good, I like xda forums very much, like the each friend! I hope you can point out my grammar mistakes to improve my English, thank you very much!
Thanks!!!
Click to expand...
Click to collapse
Please see my response in Post#18
I would never open Off-Topic threads anywhere. On any forum.
Related
LuPuS JellyBean 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"
}
This kernel can be used on any JB CM BASED JB 4.1 or 4.2
Disclaimer
Code:
[COLOR="DarkOrchid"]#include[/COLOR] [COLOR="Magenta"][/COLOR]
[COLOR="Blue"]/*
* Your warranty is now void.. LOL I guess you knew it already.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, you getting dumped or you getting fired because your phone
* bootloops and alarm does not go off. Please do some research if you have any
* concerns about features included in my kernel before using it! YOU and only
* YOU are choosing to make these modifications.
*/
[COLOR="Magenta"]#ifdef[/COLOR]
You have a [COLOR="DarkGreen"]question[/COLOR] post it in the [COLOR="DarkRed"]thread[/COLOR],
Instead of [COLOR="DarkGreen"]Pm'ing me[/COLOR], as other users may
experience you [COLOR="DarkRed"]problems[/COLOR]
[COLOR="Magenta"]#endif[/COLOR][/COLOR]
What Works --
Wifi - (flash modules)
Bluetooth
Everything Else that works on FXP and any other JB kernel
What doesn't work --
Anything that doesn't work on FXP and any other JB kernel
Added Io-schedulers --
- Noop
- Anticipatory
- Deadline
- CFQ
- BFQ
- SIO
- ZEN
Added Governors --
- lagfree
- brazillianwax
- smoothass
- scary
- savagedzen
- smartass
- smartassv2
- smartassH3
- interactivex
- minmax
- + the 5or6 that are there with FXP
Lulzactive - Thanks to Tegrak
Based on Interactive and Smartass. When workload is greater than or equal to 60%, the governor scales up
CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step.
When screen is off, frequency is locked to global scaling minimum frequency
Virtuous
Virtuous is a modded smartassV2 which gives even more battery time then smartassV2
Intellidemand - Thanks to faux123
This is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling,
and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such.
Intellidemand does not jump to highest frequency when screen is off.
Lazy - Thanks to Ezekeel
The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand.
Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state
on a step overriding sampling interval.
Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always
select the maximum frequency while the screen is off.
-Ondemandx:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.
-Lionheart:
Is a conservative-based governor. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.
To 'experience' Lionheart using conservative, try these tweaks:
sampling_rate:10000 or 20000 or 50000, whichever you feel is safer. (transition latency of the CPU is something below 10ms/10,000uS hence using 10,000 might not be safe).
up_threshold:60
down_threshold:30
freq_step:5
Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.
BadAss Governor:
Badass removes all of this "fast peaking" to the max frequency. Badass will also take the gpu load into consideration. If the gpu is moderately busy it will bypass the above check and clock the cpu with 1024Mhz. If the gpu is crushed under load, badass will lift the restrictions to the cpu.
Superbad -
A "superbad" super smooth rendition of a highly optimized "smartass" governor!
Darkside -
A "slightly more agressive smart" optimized governor!
Intellidemand2 - Thanks to faux123 and CosmicDan for mods
Uses d_bus ramping, quick and smooth and performance based, do not complain about battery drain on this
governor but it will make everything feel more like project butter
What else-----
-SLQB - (SLAB allocator with Queue)
This memory allocator is designed for small number of CPUs system (such as desktop or smart phone devices). This allocator is design to be simple and it is optimized for using order-0 pages as much as possible (order-0 pages are the simplest therefore quickest type of memory in a Linux system to allocate).
- Alot of changes to code to try improve smoothness ect
- Wifi signal lock on should now be quicker / stronger then before
--When LEDS change green, pink then blue press volume down to enter CWM Recovery
I would like to say a big thanks to -
slz.kiev - for amazing PACman ROM & Testing
FXP - Sources
Cyanogenmod - Souces
DooMLoRD - Everything he's done for XPeria
wechy77 - For helping me test
tempest918 - For the New Logo
xeozus
NobodyAtAll
Faux123
Erasmus
Leedroid
Phil3759
CTCaer
Anyone missing please PM me
Github Sources -b jellybean
https://github.com/garwedgess/semc-kernel-msm7x30
CWM source -- https://github.com/garwedgess/android_bootable_recovery -b lupus-cwm
LuPuS MENU
You can run lupus menu from terminal or scriptmanager or similar, you must run as root or script will exit with a message
in terminal
Code:
su
lupus
* information is in lupus menu
1/ CIFS Menu *
Enable
Disable
2/ zRam Menu *
Enable
Disable
Set zRam size ( default is 60)
3/ Frandom Menu *
Enable
Disable
4/ USB OTG *
Enable
Disable
5/ Clean and Remove tweaks
Remove init.d's
6/ Tweak Menu
Note all tweaks are preset from here and option to set as init.d's
Clean all temp files
SQLITE optimizations
LMK Optimizations
Network optimizations
Defend against ARP spoofing
Remove android logger
SDcard speed tweak
Flag blocks as non-rotational
7/ Performance Menu
Note all options are se by user input from here and option to set as init.d's
Set CPU frequencies
Set Governor
Set IO-Scheduler
Voltage Control
VM tweaks (explained below)
VM Tweaks
dirty ratio and dirty background ratio 1 & 2
This controls how often the kernel writes data to "disk" (in our case the internal microSD system card, not the removable microSD card). When your apps write data to disk, Linux actually doesn't write the data out to the disk right away, it actually writes the stuff to system memory and the kernel handles when and how the data is actually going to be flushed to the disk. These values represent a percentage, the higher the percentage, the longer it waits to flush, the lower the percentage, the more often flushes will occur. Now remember, we are dealing with solid state storage, not the traditional disk platter and spindle. So we are actually able to delay flushes a little longer with solid state versus a traditional hard drive disk.
dirty_expire_centisecs
How old "dirty" data should be before the kernel considers it old enough to be written to disk. It is expressed in 100ths of a second.
dirty_writeback_centisecs
This is the interval of when the writeback daemons periodically wake up and write "old" data out to disk. It is expressed in 100ths of a second.
min free kbytes
This is used to force the Linux VM to keep a minimum number of kilobytes free. The VM uses this number to compute a pages_min value for each lowmem zone in the system. Each lowmem zone gets a number of reserved free pages based proportionally on its size. Default is 2048kb.
overcommit_memory
This controls overcommit of system memory, possibly allowing processes to allocate (but not use) more memory than is actually available.
0 - Heuristic overcommit handling. Obvious overcommits of address space are refused. Used for a typical system. It ensures a seriously wild allocation fails while allowing overcommit to reduce swap usage. root is allowed to allocate slighly more memory in this mode. This is the default.
1 - Always overcommit. Appropriate for some scientific applications.
2 - Don't overcommit. The total address space commit for the system is not permitted to exceed swap plus a configurable percentage (default is 50) of physical RAM. Depending on the percentage you use, in most situations this means a process will not be killed while attempting to use already-allocated memory but will receive errors on memory allocation as appropriate.
Swappiness
A property for the Linux kernel that changes the balance between swapping out runtime memory, as opposed to dropping pages from the system page cache. Swappiness can be set to values between 0 and 100 inclusive. A low value means the kernel will try to avoid swapping as much as possible where a higher value instead will make the kernel aggressively try to use swap space.
VFS Cache Pressure
File system cache (dentry/inode) is really more important than the block cache above in dirty ratio and dirty background ratio, so we really want the kernel to use up much more of the RAM for file system cache, this will increas the performance of the system without sacrificing performance at the application level. The default value is 100, as a percentage, and what you want to do is lower the value to tell the kernel to favor the file system cache and not drop them aggressively.
If you like my work please consider buying me a beer or something else
by clicking the DONATE ME button, of course it isn't needed but greatly appreciated and keeps me motivated.
Changelog ...............
Code:
[hide]
[B][v1] [/B]
- Initial release
- 25 Governors
- 6 Io-Schedulers
- SLQB memory allocator
- Built with linaro 4.6 toolchains
- Swap
- Zram enabled
- Custom voltage control supported
- Supports USB OTG
- Supports ext2, 3 & 4
[B][U]v2[/U][/B]
- Couple of extra tweaks - improvements to battery
- Fixed Wifi issues
- Reverted my disabling of disabling sched_feautures if you get that :P
- Added USB OTG modules needed for USB OTG ( find attached zip at the end of the post)
- Added stable freq-table for higher OCing upto 2ghz
[B][U]v3[/U][/B]
- Completely scrapped previous sources and started fresh
- CWM fixed thanks @ Scritch007
- Built with Linaro 4.7
- Optimized for Linaro
- Thumbee
- Reverted to 1.6 max OC
- Lzo patched
- Use Google Snappy Compression / Decompression
- Added TINY RCU
- Fixed Battery drain ( Tester lost 0.2% overnigh with wifi on ) :victory:
- Uses uncompressed Image {why .img size is bigger)
- Custom improvements for overall smoother performance
[B][U]v4[/U][/B]
- built with latest linaro 4.7.3 (02-01-2013) - Thanks @ ChainFirex
- Added memcopy
- Added compaction
- Lowered vfs_cache_pressure
- LMK (lowmemorykiller) optimizations
- Improved CIFS support
- Enabled USB tether
- Disabled gentle_fair_sleepers
- Updated video drivers
- Clean up on wifi config
- Back-ported binder changes
- TWRP recovery - thanks @ championswimmer & TWRP team
[B][U]v5[/U][/B]
- Built with Linaro 4.7.3 (02-01-2013)
- Free'd RAM (disabled 720p) now 381mb - Thanks at Paul678
- Makefile optimisations (snapdragon & neon) - Thanks at Paul678
- Tweaked permormance on interactive governor - Thanks at Paul678
- Tweaked SIO io sched - Thanks at Paul678
- Free'd some RAM from loggers
- Reduce swappiness
- Fix PageHead
- Fix binder. use of uninitialized variable.
- Fix kernel/net Memory Leaks
- Eliminate kstrdup memory leak
- ipv4: force_igmp_version ignored when a IGMPv3 query received
- Fix Entropy Depleting (no more depleting) - Thanks @ Kees Cook
- enable ipsec tunnel support in kernel (Latest FXP Change)
- ARM7 optimsations + more in config
- TWRP v2.4 - Thanks @ Championswimmer, TWRP Team
- Thanks [user=4402161]@Wechy77[/user] for LuPuS TWRP theme
[B]v6[/B]
- Supports both 4.1 & 4.2 JB
- New IIO Scheduler ZEN thanks [user=2632235]@bbedward[/user]
- New Governor smartassH3 thanks [user=3057569]@Hero[/user]
- Tweaked Deadline IO scheduler
- Tweaked smartassv2
- Frandom
- SFB Net scheduler
- OC up to 1804.8MHz
- Logger backported from CAF
- Free RAM from logger
- LMK updated and optimized + various LMK tweaks
- Various ARM & RAM changes
- TinyRCU optimizations
- Optimized crc32 lib
- various VM changes
- Improved cleancache
- Undervolt LCD display, touch sensor proximity sensor & Wi-Fi thanks @ M66B
- Entropy tweaks
- Try fix for CRT animation [user=4266283]@paul678[/user]
- TWRP & CWM
- LuPuS Menu
- Auto Loading wifi
- All modules and init.d's included No need to flash anything after kernel
Plus alot more changes see [URL="https://github.com/garwedgess/semc-kernel-msm7x30/commits/jellybean"] for full list of credits and patches used[/URL]
[B]v6[/B]
- Latest changes to ALS and Button Backlight -- Thanks @ FXP
- Lowered OC to 1612.8Mhz
- Remove ALS and Button Backlight option from LuPuS Menu (no longer needed)
- Random reboots should be fixed ( for those who where having such issues )
[B]v7[/B]
- Fixed 3D from hanging under high intensity
- Fix pmem for HDPI Mike NG] (no more reboots??)
- CWM Recovery = VOLUME DOWN
- TWRP Recovery = VOLUME UP
- Clean up on LuPuS Menu
- Better wifi check
- KEY RESET ( Menu and POWER)
- Tuned Smartassv3 and SmartassH3 [user=2799345]@M66B[/user]
[B]v8[/B]
- Fixed reboot to recovery on 4.2 (not sure if i broke it on 4.1)
---- Custom CWM
- Clean-up of menu
- Added own wipe options menu -- with extra options
- Aroma File Manager from CWM --- Must have aroma ([COLOR=Red]aromafm.zip) placed on root of sdcard[/COLOR])
- Multi zip installer
- Reboot options - Power off re-added under this menu
- Pointless but people keep asking me for it so re-added wipe battery stats also.
- LuPuS themed...
- Fixed "dancing android"
[/hide]
[B]v9[/B]
- Added option to enable Quick Key Reset (enable / disable via LuPuS Menu)
- Tuned Governors
* superbad
* lionheart
* virtuous
* darkside
* conservative
* smartassH3
- Really use google snappy zRam (improves zRam)
- Added zCache
- Removed persistent RAM
- Removed some more kernel debugging
- uninterruptible sleep
- Update SIO & CFQ
- Added Ultra-KSM
- Removed optimized AES & SHA1 routines
- Updated TWRP to 2.4.4
*Fixed Mount USB Storage in TWRP
- Updated CWM to latest Official CWM source
*Removed reboot options
*Re-added power off and reboot system now to main menu
- Improved wifi-loading scripts
- Clean up of lupus menu
- Fixed root issue on some devices
- Reworked kernel logs (can be found in /data/local/tmp)
- Boot.d - If phone is taking a long time to start move suspicious init.d scripts to /system/etc/boot.d
They will be run in background and won't affect boot time.
LuPuS-Jellybean-DOWNLOADS
If you like my work please consider buying me a beer or something else
by clicking the DONATE ME button, of course it isn't needed but greatly appreciated and keeps me motivated.
480p
LuPuS_urushi_jBv9-ram.img
md5 = 3ff24d7e343beb483aa81d7bcfa1b5f5
[/LIST]
720p
LuPuS_urushi_jBv9.1-full.img
md5 = 1effb6e2ba80afbb55d1bd9d30a426fd
[/LIST]
Mirrors -- all LuPuS Kernels can be found here
www.goo.im/devs/wedgess
Wifi is built in to kernels ramdisk NO MODULES NEEDED
If your MD5 doesn't match re-download
Everithing works fine so far. See benchmark scores.
Sent from my Xperia Ray using xda premium
Wow...nice one! Really responsive! Just wanted to point out that in addition to all the features listed in the OP, that you can undervolt
with this kernel....didn't see it as a feature in the OP...
Thanks!
justmpm said:
Wow...nice one! Really responsive! Just wanted to point out that in addition to all the features listed in the OP, that you can undervolt
with this kernel....didn't see it as a feature in the OP...
Thanks!
Click to expand...
Click to collapse
Lol ye i forgot to add it in to op thanks for reminding me.
Edit- Put of couple of more things into 3rd post, anymore I can remeber will be added
Sent from my GT-I9300 On Official JB
wedgess said:
Lol ye i forgot to add it in to op thanks for reminding me.
Edit- Put of couple of more things into 3rd post, anymore I can remeber will be added
Sent from my GT-I9300 On Official JB
Click to expand...
Click to collapse
very smooth, but has a problem the wifi seems works not stablely, sometimes cause reboot and sometimes cannot been disconnected.
feelow said:
very smooth, but has a problem the wifi seems works not stablely, sometimes cause reboot and sometimes cannot been disconnected.
Click to expand...
Click to collapse
Did you reboot? I have no problem with wifi. Only at first boot I had this problems.
Sent from my Xperia Ray using xda premium
testing...
(thx for your effort sofar :good
1st impression: lower scores on Antatu than with standard PAC-kernel.
i'd like to have a better battery life, so now testing "virtuous/sio, 806/134".
or are there better suggestions?
(like to keep a snappy Ray )
"Custom voltage control supported" not working. The PAC romcontrol says: not supported by your kernel
Wechy77 said:
"Custom voltage control supported" not working. The PAC romcontrol says: not supported by your kernel
Click to expand...
Click to collapse
I don't think that part of RC has been activated....it also doesn't work with the kernel from champilnswimmsr's aokp build. I am using incredicontrol from the play store...but a lot of other apps will let you change the volts.
justmpm said:
I don't think that part of RC has been activated....it also doesn't work with the kernel from champilnswimmsr's aokp build. I am using incredicontrol from the play store...but a lot of other apps will let you change the volts.
Click to expand...
Click to collapse
is there a list of recommended (or safe) voltage settings for the Ray?
Yes i know in rom control it still says not supported not sure why but u can always use SetXperia app from playstore to change it
And poster who asked about safe settings. Try down step -25mv at a time and see what is stable for you. If u get reboots then its obviously not stable.
Or else safest way if your wortied then dont undervolt at all. What maybe stable for someone might not be stable for you
Sent from my GT-I9300 On Official JB
I tryed thi kernel for my CM10 rom. And it seems buggy. Antutu points is lower than on stock kernel, and the perfomance is bad too, including games and UI.
_TREM_ said:
I tryed thi kernel for my CM10 rom. And it seems buggy. Antutu points is lower than on stock kernel, and the perfomance is bad too, including games and UI.
Click to expand...
Click to collapse
lol ok first off this is not stock kernel so you can't compare it to STOCK,Ssecondly i'm not sure what governors, io scheds and frequencies you are using. People who have tested have reported it being smooth and performance being greater not worse. Also I obviously use my own kernels on my own device and my experience is the complete opposite of yours. You sure it not 'your' CM10 rom. Buggy!! how? please do elaborate.
Anyone else confirm what the above pster has said ??
Using it now for some hours with Virtous and SIO and looks very promising. Speed of ROM is for me the same and I dont play games. But Battery seems to be great! I left the screen off a lot and have like 95% deep sleep, so pretty well battery ;D I use FXP142.
EDIT: just tested the game "granny smith'. Runs good! But I didnt test with another kernel.
[GER]Roxxor said:
Using it now for some hours with Virtous and SIO and looks very promising. Speed of ROM is for me the same and I dont play games. But Battery seems to be great! I left the screen off a lot and have like 95% deep sleep, so pretty well battery ;D I use FXP142.
EDIT: just tested the game "granny smith'. Runs good! But I didnt test with another kernel.
Click to expand...
Click to collapse
Ye virtuous is supposed to be more battery friendly then smartassv2
Intellidemand2 would be best performanced based but not the best on battery.
Sent from my GT-I9300 On Official JB
Thanks for the great kernel, really liking the Superbad governor.
I left my ray on during the night, to see what the battery would do...
(i mean screen off, but wifi+3g on)
from 100 to 74% in 9 hours.
8:40 deep sleep (94%)
806/134 virtuous/sio
I cannot compare btw, usually i charge at nighttime, but usage seems quite high?
was hoping for about 90% battery left or something, but like i said, not tested with other kernels.
I think I caught a "wifi" bug. Yesterday the wifi cut out and wouldn't turn back on...after rebooting everything was fine for a few hours and then wifi stopped working. I am not sure if it is really wifi or something else, because if I go into settings I see that wifi is on, I can turn it off but it won't turn back on...if I leave settings and pull down the status bar it show wifi as "on"...when I go back into settings it shows wifi as "on"...and no networks are shown that can be connected. You can do this over and over and every time you reenter settings it says wifi is on. I think it also causes a wakelock from wifestatemanager.
I went into recovery and formatted system and reinstalled PACman v15...a few hours later the problem returned. I flashed in a different kernel and it seemed OK....now I have your kernel on ChampionSwimmer's AOKP ROM and I am waiting to see if the bug returns.
I am not sure if there is something specific I do that activates the bug, so I don't have a logcat of it happening. I attached a logcat of me trying to turn on and off wifi in settings. I also attached the battery stats report from Better Battery Stats in case the wakelock is informative....
Ladies and Gentlemen,
It gives me great pleasure to introduce to you an unofficial port of the Z1
Pimped Kernel
This is a kernel for CM11 based ROMs and uses -caf. If your ROM isn't faily new and doesn't use -caf then don't expect this kernel to boot. It was built inside Carbon and I have tested in there, it should boot CM/FXF, SlimKat, LiquidSmooth, Carbon, Omni, etc. I don't know how well it will boot PA/PAC/etc that are further away from this codebase but you are welcome to try. As this is a first build so expect some FCs and reboots, and and not all features will work. Please read the OP to see what is on offer. Things that won't work are LCD/Touchscreen/DT2W, and others may be prone to bugs.
This has kernel is built with Linaro SaberMod Toolchain 4.7 and -O2 etc optimisations (not as many as the slimkat kernel). Performance seems good, and the ability to underclock/volt and turn off cores should give extra battery life.
Please don't use this unless you know how to get out of trouble/bootloops/non-boot/lost recovery/etc. I nor Androguide.fr take any responsibility for dead or undead Z-Ultras
Kernel features are controllable through Androguide.fr's Pimp My Z1 app, (thread here).
{
"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"
}
Download:
togari-BluePimp-4.4.4-dt2w-ext4-20140810_1122.zip
Very minor change to LEDs, and boot splash http://forum.xda-developers.com/devdb/project/dl/?id=7497
test v0.3 for new 4.4.4 AOSP/cm-11 ROMs
togari-BluePimp-108-dt2w-ext4-20140709_1741.zip
old 4.4.4 and 4.4.2/3 ROMs
30/6/2014 4.4.4 build with dt2w
Build 4 31-05-2014
Build 4 31-05-2014 dt2w
Features (C&P from OP):
Sound Control: Faux123's GPL Sound Control 3
Color Calibration Control: LCD_KCAL interface ported to the Z1 by @DooMLoRD, gives full control over the RGB channels of the display
GPU OC: 200MHz / 320MHz / 389MHz / 487.5MHz / 533MHz / 600MHz frequency scaling steps
CPU OC: up to 2.26GHz
CPU Voltage Control: use TricksterMod for the moment
DoubleTap2Wake: double-tap the screen to wake-up the device
Intelliplug: Faux123's latest intelliplug hotplugging driver with eco mode (v5.0)
[*]MPDecision: showp1984's open-source & customizable msm_mpdecision hotplugging driver
Dynamic Fsync: Faux123's Dynamic File Sync v1.5
PowerSuspend: Faux123's power_suspend driver (replacing early_suspend)
Snake Charmer: Faux123's msm_cpufreq_limit CPU frequency limiter driver
Fast Charge: Faux123's fast_charge driver, allowing to set the amperage of the charger or USB port your device is plugged-in to
CPU Boost: Faux123's CPU Input Boost module (will soon add controls for it in Pimp My Z1)
GPU Wake-on-touch: allows touch events to wake the GPU if it was previously in slumber
KSM: Kernel Same-page Merging enabled
F2FS Support: Samsung's F2FS nand-optimized file system support
exFAT Support: Samsung's open-source exFAT driver
zRam Support: support for zRam memory compression
CPUPower: Linaro's cpupower PM driver
Async Fsync: Asynchronous file sync
MSM_Sleeper: Support for setting the max CPU frequency when screen is off through sysfs
Kernel mode NEON: NEON-accelerated XOR framework & support for NEON instructions in kernel mode
Overall Stats: CPU overall stats on a per-core basis
Compression: XZ Compressed & LZ4 compression algorithm support
Sched MC: Multi-Core Power Savings support
Sched SMT: Multi-Thread Power Savings support
Arch_Power: arch-specific power sched features enabled
Workqueue: backported from kernel 3.7, allows CPU hotplug to keep idle workers (learn more)
Toolchain: Built with Linaro GCC 4.8
Optimizations: Built with -O2 and many optimization flags
Kexec-hardboot ?: attempted to port @Tassadar's kexec-hardboot patches from the nexus 5, needs testing and confirmation that it works
Additional Governors:
Intellidemand
Intelliactive
Pegasusq
Nightmare
Hyper
Alucard
InteractiveX2
SmartassV2
Lagfree
Wheatley
Lionheart
Badass
Additional I/O Schedulers:
SIO (SImple Ondemand)
FIOPS (Fair Input/Output Per Second)
BFQ (Budget Fair Queueing)
VR
Additional TCP Congestion Algorithms:
BIC
Westwood
HSTCP
Hybla
HTCP
Vegas
Veno
Scalable
LP
YeAH
Illinois
Click to expand...
Click to collapse
Change Log:
http://forum.xda-developers.com/showpost.php?p=50603486&postcount=2
Sources:
Androguide.fr kernel sources: PimpedKernel
My additions for the ZU (see BluePimp branch): BlueEther
Credits:
Thanks to Androguide.fr fro bringing all of the together
Thanks to faux123 for all his contributions to the android kernel community, many of which are implemented here
Thanks to showp1984 for his msm_mpdecision hotplug driver
Thanks to DooMLoRD for all the cherry-picked features from his DoomKernel
Thanks to krabapel2458 for the inital port from DoomKernel of features like GPU OC, some governors and more.
And of course, thanks to FreeXperia and Kali- in particular, for the device bring-up
Click to expand...
Click to collapse
Disclaimer:
# Neither I nor any contributors to this kernel can nor will be held
# responsible for any damage or any kind of problem related to its use.
# You are using this piece of software AT YOUR OWN RISK.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
Click to expand...
Click to collapse
Disclaimer #3, I'm not responsible for dead or undead Z-Ultras from using this ROM and kernel, OC at you own peril
XDA:DevDB Information
Unofficial Pimped Kernel, Kernel for the Sony Xperia Z Ultra
Contributors
blueether, Androguide.fr, DooMLord, faux123, krabapel2458, FXP/CM, Kali-, reaper61616 (dt2w)
Kernel Special Features: Sound Control, GPU OC, Intelliplug, PowerSuspend, Dynamic Fsync, exFAT, F2FS, KSM, Intellidemand, Intelliactive, SmartassV2, InteractiveX2, Lionheart, Wheatley, Badass, Lagfree, BFQ, SIO, FIOPS, Westwood, Hybla, HSTCP, HTCP, Veno, Illinois, LP, BIC...
Version Information
Status: Testing
Created 2014-04-25
Last Updated 2014-08-09
What's working and not
Kernel Bugs:
Camera FCs - maybe more of a CM issue than this kernel
Tested ROMs:
Carbon - (non public test build): Working
Carbon - Build 8: Working
SlimKat: Working
LiquidSmooth: Working
FXF CM11: Working
CM11: Working
AOSP: Not tested yet
AOKP: Not tested yet
AICP: Not tested yet
Lungo: Not tested yet
PAC-man: Not tested yet
PA: Working
Chameleon OS: Not tested yet
GPe: Won't boot
Quick run down using Pimp my Z1:
CPU
Min/Max works after a save (pressing 'Done' does nothing?)
[*]Per core Looks to work
[*]Interactive/performance/ondemand and conservative all seem to work as expected
TCP not tested
GPU
Min/Max (200/450) Looks to work
[*]Performance/msm_cpufreq/msm_adreno-tz/powersave/etc all seem to work as expected
cpubw_hwmon reboots the ZU
Power Managerment
Multi-Core Moderate hard to tell if working
[*]Multi-Core Aggresive Looks to work as expected
[*]Intelli plug and eco mode - Look to work well except Pimp my Z1 FCs when trying to change # of cores and gets stuck on 1
Power suspend not tested
LCD Colour
Voltage controle - looks to be working
I/O, Memory and Misc. not tested but options look to work
Sound Control
Speeker Gain works
not tested the others
Touchscreen
None are active - as expected
And i am subscribed to this
Keep it up mate xD
joluke said:
And i am subscribed to this
Keep it up mate xD
Click to expand...
Click to collapse
Build 2 Uploaded.
2014-04-24
Updated to Linux kernel version 3.4.86
Re-added GPU OC up to 600MHz and hopefully fixed the issues some people had with it
Added zRam support (thanks to DooMLoRD)
Added msm_sleeper (thanks to DooMLoRD), controls coming to Pimp My Z1 soon
Added memutils optimizations (thanks to DooMLoRD)
Merged a lot of slimbus/slim-ngd/slim_msm/qdsp6v2/wcd9xxx & other audio-related optimizations from franciscofranco's nexus 5 kernel
Merged some OOM, ocmem & other memory-management-related optimizations from franciscofranco's nexus 5 kernel
Merged a fix for msm_z180 memory leak from franciscofranco's kernel
Some other random cherry-picks
Use caution when OCing the CPU/GPU
blueether said:
Ladies and Gentlemen,
It gives me great pleasure to introduce to you an unofficial port of the Z1
Pimped Kernel
Click to expand...
Click to collapse
Thanks, we will test. Good modifications.
Kernel v2 boots and works with slim kat ,thanks bro [emoji106]
t0pstar said:
Kernel v2 boots and works with slim kat ,thanks bro [emoji106]
Only display settings from the pimp my app don't work (dt2w,s2w ...)
Click to expand...
Click to collapse
Does the camera work? Just had a FC than couldn't connect
DT2W/S2W/etc all use a different touch-screen driver than we use on the ZU
blueether said:
Does the camera work? Just had a FC than couldn't connect
Click to expand...
Click to collapse
When I open camera directly after boot it works fine ,
when not I have also FC
Im using camera kk app and it works fine. Just first time camera is not moving (it stops on first "seen" frame), but it is on every kernel (maybe rom's, maybe app's bug) and after killing it in recent apps and starting again everything works fine
Strange for me is that this kernel has more governors etc, and i always thought that coz it we should have less ram, and there is more than ie unofficial slimkat kernel
Edot: Is there any chance for f2fs version in the future? Its a lot better than ext4, so it can make our ZUs fly even better than now
Sent using C6833 - Carbon KitKat/Pimped Z1 Kernel
ch3mn3y said:
Im using camera kk app and it works fine. Just first time camera is not moving (it stops on first "seen" frame), but it is on every kernel (maybe rom's, maybe app's bug) and after killing it in recent apps and starting again everything works fine
Strange for me is that this kernel has more governors etc, and i always thought that coz it we should have less ram, and there is more than ie unofficial slimkat kernel
Edot: Is there any chance for f2fs version in the future? Its a lot better than ext4, so it can make our ZUs fly even better than now
Sent using C6833 - Carbon KitKat/Pimped Z1 Kernel
Click to expand...
Click to collapse
after a bit of flashing and testing the no outgoing calls is a bug in the test build of Carbon not this kernel so all is good on this front.
This kernel boots the last couple of Carbon builds, back to at least the 19/4 so that's another plus.
I'd not really had the camera issue that many people had had in the last few weeks on the CM based ROMs so it's sort of new for me.
You made it!!! Congrats and THANKS! Perhaps it's time I go back to a non-stock ROM now, just to try this kernel...
I found other problem (at least for me) with pimp my z1. I cant set 2nd core governor, coz it always return to intelliactive last saved? (im not sure as sometimes it stays on last saved sometimes on earlier), now, as i know how it works, its not the problem to set governor I want, but its strange bug. I would use trickster but there I cant set different governors for every core (As i found out set governor is only for first core)
EDIT: Maybe someone answers: What is Pen Mode in this app? If it is what I think we dont need it as our phone support mostly everything as a pen. The same for gloves i think
Has anyone tried this Kernel on CM11, if so any problems?
Sent from my Xperia Z Ultra using Tapatalk
Next few things:
-
1. After reboot very often CPU governors are changed.
2. Additionaly to setting governors: They are setting itself. Before I set nightmare/nightmare/powersave/powersave and after going back to menu and againd CPU Control it was nightmare/<last saved?>/powersave/powersave. Now after reboot it was nightmare/nightmare/nightmare/nightmare (with per-core on) and after menu->CPU Control nightmare/intelliactive/powersave/powersave (intelliactive wasnt last saved or anything)
3. Sometimes after reboot Pimp my Z1 returns GPU settings to default ones
4. Power Managments, I/O tweaks, Memory managments too - Misc on the other hand are always remembered correctly
Yes I have "set on boot" on. Strage coz mostly (4/6 for now) everything is remembered correctly ie now after next "test" reboot
ch3mn3y said:
Next few things:
-
1. After reboot very often CPU governors are changed.
2. Additionaly to setting governors: They are setting itself. Before I set nightmare/nightmare/powersave/powersave and after going back to menu and againd CPU Control it was nightmare/<last saved?>/powersave/powersave. Now after reboot it was nightmare/nightmare/nightmare/nightmare (with per-core on) and after menu->CPU Control nightmare/intelliactive/powersave/powersave (intelliactive wasnt last saved or anything)
3. Sometimes after reboot Pimp my Z1 returns GPU settings to default ones
4. Power Managments, I/O tweaks, Memory managments too - Misc on the other hand are always remembered correctly
Yes I have "set on boot" on. Strage coz mostly (4/6 for now) everything is remembered correctly ie now after next "test" reboot
Click to expand...
Click to collapse
I'm wonder if it is more the app than the kernel?
I have managed to peg the first core at fill tilt once and another time to have all 4 core online all the time. The second issue can be solved by turning all the options off in Power Management, it's a known race condition by the looks.
~5% battery drain over night, but it looks like google services are causing wakelocks again on my ZU
Its hard to say coz there is bo more apps which can let to use most od options kernel has (ie trickstermod let set governor for all, i/o too for both memories). But i would think its app+phone compatibilty issue not kernel, but not sure about it
Sent using C6833 - Carbon KitKat/Pimped Z1 Kernel
Just flashed this kernel with the latest carbon rom and working great very fast will test for the next few days and see how the battery life is - thanks for the great kernel
Sent from my SM-T320 using XDA Premium HD app
blueether said:
~5% battery drain over night, but it looks like google services are causing wakelocks again on my ZU
Click to expand...
Click to collapse
After first night it was worse for me - 13%. It coukd be coz kernel was just flashed ot coz my set up, but its too much
But this second core governor annoying.me too. I found out that if i set it few times it stay till sometime after reboot (just after reboot and getting su rights, governors are right(. Anyone has similar problem? Can moving app to system/app helps?
Sent using TF300T - CyanogenMod 11.0/GEASS (F2FS)
ask
it work with this rom
http://forum.xda-developers.com/showthread.php?t=2606414&page=71
mimoun103 said:
it work with this rom
http://forum.xda-developers.com/showthread.php?t=2606414&page=71
Click to expand...
Click to collapse
No it wont, this is for AOSP/CM11.
The Port of DooMLorD's kernel is much the same feature wise and will work with monx's 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"
}
"I Don't Always Run Custom Kernels. But When I Do, I Run Vindicator"
-Worlds Most Interesting Man
Pushbullet Tag: vindicator
Vindicator OTA Updater App: https://play.google.com/store/apps/details?id=com.mcswainsoftware.vindicator.ota
if there are any bugs, contact developer Jacob
You can also follow me on G+ if you would like:
[email protected]
Intro:
This is the first kernel I've ever developed. I just started developing on android a few months ago so I'm brand new to this. I don't consider myself a developer, I'm just good at figuring things out, all credit goes to the real hard workers coming up with original ideas like Franco, Imo, Flar and Faux. Initially this was built as a kernel to compile with my ROM I'm working on but I decided I would let others get a chance to use it as well. 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.
For those looking for a similar experience, but much closer to stock, I suggest giving Zen Kernel a try!
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 phone blows up, its not my fault. If your phone somehow gains perpetual battery life, I'll take full responsibility.
Features:-Zen Kernel Base
-Android 5.1
-BFS Cpu Scheduler (Ported By @bbedward)
-Latest Linux 3.10.x
-Compiled With Uber ToolChain 6.0
-Compiled With Ofast, Strict-Aliasing, Graphite, A15 Tweaks, And Loop Nest Optimizations
-Various Other Build Optimizations
-Optional GPU OC To 700Mhz.
-GPU Initial Freq. Is 110Mhz Instead Of 240Mhz Saving Power.
-Additional GPU Steps
-CAF Power Saving Patches
-CPUIdle Driver Updated To Linux 4.0
-Slub Allocator Updated To Linux 3.18
-GPU UnderVolted
-Workqueue Updated To Linux 3.18
-Init Updated From Upstream
-Power Efficient Workqueues
-Low Power Ram Mode Enabled
-Kernel Same Page Merging
-ZenDecision Quad Core Driver
-Hotplug Affinity Enhancements
-Kexec Hardboot/MultiRom(See FAQ For Help)
-UKM Built In And Modified. Just Install Synapse App.
-Savocas Color/Gamma Control
-Lowered Regulator And Screen Voltages
-Lowered Screen Clock Speed
-Lowered Retention Voltages
-Moto QuickWakeup
-Faux's Simple GPU Governor
-Frandom (Efficient Random Number Generator)
-Hardware Floating Point Processing
-ZRam
-ZSMalloc
-I2C Min Freq. Reduced
-Cruft Free
-Slimmed Down(Increased Size Is Due To Optimizations & UKM Not Bloat)
-Tons Of Debugging Removed
-Many Misc. Optimizations
-35mhz Min Freq, 3.09ghz Max
-Several WakeLocks Removed, Such As Sensor_Ind and hsic.
-MPDecision Disabled By Default
-MSM HotPlug
-Mako Hotplug
-Adjustable Thermal With Lean Kernel Mods
-IntelliActive Governor Added
-FIOPS, ROW & BFQ IO Schedulers Added
-Tons Of IO Fixes/Performance Boosts
-No Force Encrypt. Changed To Encryptable.
-Crypto Optimizations For Enhanced IO Throughput When Encrypted
-Voltage Control
-Westwood TCP Algorithm
-PIE & HHF Network Schedulers(reduced latency)
-Tons Of CAF Commits
-Merged In Most Of Franco's Code
-Merged In Parts Of Faux123's Code
-Merged Significant Portions Of Lean Kernel Code
-Optimized RWSEM
-Many Parts Pulled From Upstream
-Merged In All CAF And Franco Interactive Commits Into Interactive
-Francos Conservative Governor
-CPU Boost Completely Removed(Replaced With Franco's)
-Wake Gestures
-F2FS Support
-LK Config
-Vibration Control
-Asynchronous FSync
-Init.D Support
-Potentially Something I Forgot...
Downloads:
[AFH] Kernel: https://www.androidfilehost.com/?w=files&flid=25836
Downloads also through app and pushbullet
Amazing Donors!:
JackPollard
Maybelle
Credits:
Imoseyon
bbedward
Flar2
Franco
Faux123
Linaro
Code Aurora Foundation
Cl3Kener
Engstk
Yank555
Mistertac (Best Tester Ever)
RIPng(DespairFactor)
Neobuddy89
apb_axel
Google
Motorola
If I Missed You Lemme Know!
XDA:DevDB Information
Vindicator Kernel, Kernel for the Nexus 6
Contributors
Xileforce
Source Code: https://github.com/XileForce/Vindicator
Kernel Special Features: I'm special.
Version Information
Status: Stable
Current Stable Version: 2.3
Created 2015-02-06
Last Updated 2015-05-3
Changelog:
1.0:
-Merged Latest Lean Kernel Code
-Merged Latest Franco Code
-Franco's Thermal Management Replaces Thermald
-Zram ported from Linux 3.19 upstream Using LZ4
-VM Memory Tweaks. (Vfs cache, swappiness,etc)
-I2C min frequency reduced from 50mhz to 19.2mhz
-Retention voltages dropper further
-Removed most Tracers
-Reduced Several Regulator Voltages
-Various CAF Patches
-Disable IO Stats
-Disable More Debugging
-Disable Gentle Fair Sleeper(better performance)
-ZSMalloc ported from Linux 3.19 upstream
-ZPool Ported from Linux 3.19 upstream
-Cut DMA latency in half
-Optimize SFCK Compression
-Reduce Swappiness
-Optimize Dirty Ratios
-Disable HSIC_Host wakelock by default
-Reduce Wlan wakelocks further
-Increase Bark/Pet Time
-Possibly More I Missed.
1.1:
-Savocas New Color/Gamma Control
-Lowered All Regulator Voltages Across The Board
-Lowered Screen Voltages And Screen Clock Speed(no detrimental effects noticed yet)
-Add Under clocked and Over clocked step for L2Cache
-Add 110mhz And 430Mhz GPU Slots
-Fix Simple On Demand Governor
-Additional Build Optimizations
-Integer Square Root Optimizations(3x faster)
-Lower GPU Bus Frequency @ 700mhz(battery and stability)
-Potentially Reduce BlueSleep Wakelock(testing report back please)
-Remove IO Debug
1.2:
-Merged Latest LeanKernel
-Added Option To Disable BlueSleep Wakelock Via Terminal
-Reduced BlueSleep By Default
-Readahead Optimizations
-More Voltage Reductions
-Power Suspend Updated To 1.7
-OC SlimBus
-Revert L2 OC
-Latest Franco Merged In
-Update To Linux 3.10.69
-Fix Ramdisk Issues
-Raise InteractiveX Default Screen Off To 730Mhz
-Lowered Power Draw Further At 35mhz
1.3:
-Added Motorola Quick Wakeup
-UKM Built In. Use Synapse App
-Added Aggressive Build Optimizations
-Merged In New Lean Kernel
-Greatly Reduced GPU Power Draw
-Added Bricked Hotplug
-Added MSM Limiter
-FSync Toggle
-Optimized LZ4 A Bit
-Some CAF Patches
-Increased Available Entropy
1.4:
-Merged In Latest Franco Code
-Removed Bricked Hotplug
-Defaulted Power Aware Scheduling On(Adjust In LkConfig)
-Added Power Efficient Workqueue(Better Battery Life)
-Optimized Timer Code
-Added Westwood TCP Alg.(Best One IMO)
-Updated UKM To Latest
-Updated MSM Limiter
-Numerous CAF/Linaro Patches
-Screen Power Draw Reduced Further
-USB Fast Charge
-Various Code Optimization Patches
-Added Toggles For Arch Power And Gentle Fair Sleepers
-Network Speed Tweak
-Don't Force Sync On Suspend
1.5:
-Kexec-hardboot/multirom support(Huge thanks to team member @jamcswain for porting that!) See FAQ For Help.
-Merged Lean 1.17
-Update To Linux 3.10.71
-Optimize Low Memory Killer For ZRam
-About 50 CAF Patches For Numerous Things(Thanks Neobuddy)
-WiFi Patches
-Crypto,IO,Memory Optimizations
-Entropy Optimizations
-DT2W Fixes
-Screen,GPU Patches
1.6:
-Android 5.1 (Massive Thanks To Imoseyon for merging it in)
-Latest Lean Merged
-Latest Franco Merged
-Mako Hotplug Updates
-Intelliplug V4
-Misc Fixes
-Default Power Aware Scheduler Off Again (Change In lkconfig)
1.7:
-Merged Latest Lean
-Merged Latest Franco
-Ramdisk Fixes For Roms(All Imoseyon)
-IO Boosts
-Updated Linaro ToolChain
-Boot Time Speedup(Jamcswains idea)
-InteractiveX Tweaked(Franco's Idea)
-Numerous CAF Patches
-Mako Hotplug Updates
1.8:
-Merged Latest Lean
-Merged Latest Franco
-Switched Toolchain To Custom Compiled Linaro
-Speed Up Boot Further
-Tons Of CAF Patches
-Audio Fixes/Patches
-800Mhz GPU Step
-MSM Limter Removed
-Added Moto Predictive Touch Driver(Better Responsiveness)
-Updated FB Notifiers
-Disabled MPDecision By Default. Mako Is Default Now
-FIOPS Is Default IO Scheduler Now
-Added Moto Low Memory Killer Optimizations
-CPUfreq and Ext4 Optimizations
-More Debugging Disabled
-Various Other Optimizations And Updates
-Update To Linux 3.10.72
-Probably Stuff I Forgot
1.9:
-Merged Latest Lean Kernel
-Fix USB OTG
-Fix Wake Gestures
-Default To QuadCore Mode For Mako
-Ensure 35Mhz Is Min Freq. on Boot(Fixes Weird Issue)
-Modified UKM/Synapse To Control Wakelocks (Misc Tab)
-Merged Latest Hydra Kernel Changes/Patches
-Fix Battery Drain On BlueTooth
-Frequency Mitigation Preventer V2 (In LKConfig)
-Stability Fixes
1.9.1:
-In Call Audio Fix
1.9.2:
-Updated With Official Multirom/Kexec Hardboot Patch
2.0:
-Merged Latest Franco And Lean Code
-Linux 3.10.73
-Several Memory Leaks Fixed
-Reboot/Bootloops Fixed
-!00's Of Patches
-SELinux Permissive By Default
-Compiled With SaberMod 5.0
-Screen Frequency Reverted To Stock
-Tweaked Interactive Touchboost Parameters Further
-Replaced IntelliPlug With MSM Mpdecision
-Added Back MSM Limiter
-FB Notifiers now Enabled By Default. Toggle Added To Synapse
-Merged In Some Hydra Kernel Ramdisk Fixes
-GPU OC Reduced Back To 700Mhz
-Add Power Aware Scheduling to Synapse (CPU Settings Page)
-Fix Synapse To Display CPU Bin On Front Page
-Revert FastBoot Mods For Now (Buggy)
-KCal Fixes
-MSM_HSIC WakeLock Now Enabled By Default With Divisor Of 5 (Change In Synapse Or LKConfig)
-Mako Hotplug Load Threshold Set Back To 80
-Misc Optimizations
2.1:
-Completely Rebuilt From Scratch Upon Zen Kernel With Input From bbedward
-Some features may be missing atm and may get added back in down the line.
-BFS Cpu scheduler. IMO a significant upgrade over CFS, the standard one used by almost every kernel. Should give better battery life and performance. THIS IS ONE OF THE BIGGEST CHANGES A KERNEL CAN MAKE
-Cleaned up the source and fixed issues.
-EXT4 and F2FS updated with upstream commits.
-Per CPU VMA Caching From Upstream
-BFQ and ROW IO Schedulers
-Touchboost Adjustments For More Butter
-Fauxs Simple GPU Governor
-Lowered the default voltage on 1.497ghz 10mv by default
-Compiled With Ofast Instead of Os (Ofast Is the heighest gcc optimization level, one step above O3. Os optimizes for size, rather than speed.)
-Compressed with optimized XZ rather than LZ4 to keep size down
-Latest lean and Franco merged in.
-Adaptive Low Memory Killer enabled
-So much stuff....and I honestly have no idea on how to write a changelog for a rebase...its an entirely new kernel...
2.2:
-Compiled With UberTC 6.0 (Figured We Would See How It Compares To SM 6)
-Compiled With Graphite Optimizations
-Compiled With Loop Nest Optimizations(An Extremely Aggressive Optimization)
-Compiled With loop-unroll-and-jam(A companion optimization to loop nest also aggressive)
-Small GPU Tweaks
-Greatly increased encrypted IO Performance
-Arm Specific Optimization Patches
-Added Heavy Hitter Filter(Another Network Optimization That May Also Reduce CPU Usage)
-Added Proportional Integral Controller Enhanced(Yet another network optimization algorithm designed to reduce latency and increase efficiency when doing latency sensitive things such as streaming)
-Optimize boot/compressed for Krait
-Addition Branch Optimizations and Inter Procedural Optimizations
-Support CM12.1 Ramdisk
-Optimize ROW and Deadline
-Add Bluesleep Wakelock Toggle
-Reduce Wlan_Ctrl Wakelock
-Default Wlan_rx wakelock divisor to 5
-Default msm_hsic divisor to 6
-Fix lkconfig frequency stuff
-Default below 40% frequency changing OFF
-Cleanup frequency mitigation stuff in lkconfig.
-Add Westwood
-Use amended interruptible threads (reduces cpu load)
-Disable add random on IO
-Reset cpu dma latency to stock...idk what it does so i shouldnt touch it...
-Revert Ram OC (IDK if it even worked)
-Add smb135x wakelock toggle
-A GPU Patch
-Raise default touchboost to 500ms.
-Optimize memcpy and memmove
-Significantly Optimize Console Framebuffer
-Enable non-cacheable streaming enhancement
-Add GPU Compile Optimizations
-Disable a lot more debugging
-Boot with 2.649ghz max freq for stability
-Add OC up to 3.033ghz. Highly unstable IMO but its an option for the brave.
-Cleanup Ramdisk
-Raise voltage a bit on 2.88 for stability.
-Disable useless resource counters to save processing power and battery.
2.3:
-Update CPUIdile Driver and CPUIdle Governors almost completely to linux 4.0(Several Years Worth Of Commits)
-Updated CPUFreq Driver Nearly To Linux 4.0
-Update Suspend/Sleep Driver Mostly To Linux 4.0
-Update SLUB Allocator To Linux 3.18
-Update Block(IO Stuff) From Upstream A Bit.
-Upstream Scheduler Patches
-3.09Ghz CPU Step Added (Likely Quite Unstable) Some People Like That Stuff
-Amperage On 3.03Ghz bumped up a tad for stability.
-Linux 3.10.75
-Frandom random number generator added(Extremely Fast Random Number Generator)
-Power Efficiency Patches From Code Aurora
-Fixed Crash When Switching CPU Govs.
-BFS Updates!
-Update Ondemand to Linux 3.18
-Default OnDemand To Simms22's Preferences
-Merged Latest Franco Code
-Merged Latest Lean Code
-Merged Latest Zen Code
-Franco's Conservative governor updated
-Some Interactive updates
-Color control updates
-ARM Specific Updates
-F2FS Updates
-GPU Driver Updates
-Memory Leak Fixes
-Stability Fixes
-Updated ToolChain
2.4:
-Updated To Linux 3.10.77
-Merged Latest Lean Kernel
-Merged Latest Zen Kernel
-Update Workqueue To ~ Linux 3.18
-Enable Ram To Enter Low Power Mode
-Update mm.h And Memblock from upstream
-Default IO Scheduler To BFQ. Its Been Tested To Be Best For Interactivity
-Upstream Init A Bit
-A Few Patches To SMP
-Upstream Cgroups And Memcg Significantly
-Disable RunQueue Stats. Pointless Bloat and CPU Overhead only needed for mpdecision
-Added Power Efficient WorkQueues Patch From Upstream(This Gives better battery life at the cost of a likely unnoticeable performance hit. Enabled by default. Toggle in synapse CPU settings page)
-Hotplug Efficiency Patch(Optimizes Hotplugging To Handle The Transfer Of Processes From One Core To Another Much Better)
-ZenDecision Added
-Added A Toggle For Mako(Currently Only Works To Disable Mako. Ill Work On It Further In 2.5 Credit to bbedward for this
-GPU Tweaks To Make It Smoother
-UnderAmped(Reduce Current For Every Frequency Up To 2.7ghz. Should Save Power. Experimental)
-Added KSM Tweaked For Android(Disabled By Default, Scans Few Pages, and does so very rarely. I didn't notice a battery hit with it on. Optimizes ram use)
-Franco Kernel Updater Profile Updates
-Ramdisk Modifications(May Fix Some Rom Issues)
-Fix For Ondemand Crashing(Hopefully)
-Misc Tweaks & Patches
-Hotplug Affinity Fixes
-Various Power Saving Patches
-Optimize Copy_Page For Modern Arm Processors
-Do Jiffies Conversions At Compile Time Rather Than Runtime(Saves The Cpu Work)
-Optimize For Our L1/L2 Cache Size
-Allow Options To Be Passed To Memory Barrier Instructions
-2 Patches To Improve File System Performance
-HRTimer Optimizations
-Make Binder Mutex Realtime To Reduce Chance Of SurfaceFlinger Being Blocked
-Keep Track Of ASID Allocations And Try To Reuse Them In Certain Cases To Improve Performance
-Don't Compile CPUIdle Ladder Governor. It doesn't get used anyways.
-Allow Rescuer Thread To Do More Work
-Reduce Runqueue Lock Contention
-don't use compound_head() in virt_to_head_page() this showed around a 1.8% performance improvement in some cases
-Small MultiCore Scheduling Improvement
-Definitely Some Stuff I Forgot
FAQ's
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, those are part of LK which means 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 ofnwhy 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 Phone! 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 with root support and navigate to sys/fs/pstore I then need the console one.
7. What Kernel Tweaking App Should I Use? What About For Tweaking Screen???:
I now Use synapse as my goto app for kernel tweaking since version 1.3. To control the screen I use the app made by Savoca who created the color control we use http://downloads.codefi.re/savoca/kcal
8. Why Add Zram? We Already Have 3gb 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. Wut Is A LZ4?
LZ4 is a compression algorithm used by the kernel. LZ4 is currently the fastest supported option in the Linux kernel and had to be ported from upstream. It is significantly faster than XZ compression which is what we used prior. The downside is it results in slightly larger file sizes due to a lower compression ratio. However with modern hardware this should be moot. The gains should theoretically be noticed as a general performance bump. Boots should be faster. IO should be marginally faster. Anything that's compressing or decompressing stuff, such as ZRam and encrypted devices will utilize this in a big way. Because its compressing and decompressing so much faster it can also be assumed it is saving battery via less CPU cycles.
10. 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
11. 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. The same goes for 98mhz. Hope this helps clear things up.
12. How Do I Disable BlueSleep Wakelock?
Open terminal emulator app. Type su then hit enter then type echo 0 > /sys/module/wakeup/parameters/enable_bluesleep_ws all on one line. It won't say anything but if you turn on Bluetooth and check your wakelocks you shouldn't see the wakelock there anymore. This needs to be set on each boot currently. If you experience Bluetooth connectivity issues don't disable this. To enable it again either reboot or run the same command with a 1 instead of a 0.
13. How Do I Use MultiRom???:
To use multi ROM first you must download the MultiRom App from this location http://tasemnice.eu/bordel/MultiROMMgr-v1.180.apk the play store version doesn't work with shamu yet. Then you will need to open it, go to settings and tap the version number until you are a developer. Then click override manifest URL and for manifest URL enter http://tasemnice.eu/multirom-test/manifest.json the. Go back to the main page. You should now 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.
Configuration Guide:
The following can be done using your favorite kernel tweaking app. I use synapse.
Clock Speed:
To begin I prefer to leave my max clock speed at the stock 2.649ghz. Set min CPU as low as it can go. As of current release this is 35. For the adventurous you can try 2.88ghz. Often I bump the voltage 12mVolts on 2.88 to be safe.
To find your CPU binning run this command in terminal emulator OR look at the first page in synapse near the bottom:
su (enter)
cat /proc/cpu/msm_acpu_pvs (enter)
(Put a space between cat and /proc)
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.
GPU:
As of Alpha 1.3 the GPU can now be over clocked to 700mhz. This is completely optional. To verify your over clock change the GPU governor to performance and see if it spikes to 700 every so often. If it does it worked! If it doesn't you may need to set the frequency to something else then back to 700 again. It remains to be seen what kind of benefits the GPU over clock will give but it is there for those who want it. The recommended GPU governor is the stock msm adreno one. If you encounter lag in games you can try changing it to performance temporarily while playing that game. Simple on demand is a more performance oriented governor.
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, Google, and Franco. It also hooks into Francos CPU Boosting interface. 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 interactiveX 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. The Conservative Governor is greatly modified by franco, Its no longer a super slow governor as it once was. It also hooks into his cpu boost control interface meaning you get cpu boost when using it. Conservative prefers the lower frequencies, however so if you find yourself having lag, you may want to switch to another.
PowerSuspend:
The only working options in V1.6 of the PowerSuspend driver are lcd_panel and Userspace which can be found in the miscellaneous section of FauxClock. I suggest leaving it at the default choice of LCD_PANEL. In FauxClock if you navigate to the cpu idle/stats area you will be presented with more options. You should see a list of C-states. For example C0: wfi and C1: retention. These are essentially low power states that the cpu can enter to save power. The higher the C number the deeper the sleep. Last I heard, the optimal configuration was to enable C0, C1, and C3. Paired with lowered Retention voltages, this should give you a very low idle drain.
Hotplugging:
Next go to hot plugging section and disable MPDecision(make poor decision) and enable intelliplug or, enable Mako Hotplug(Franco's) by either selecting user control as your hotplug, or disabling both mpdecision and intelliplug. Tweaking for them is split up below.
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) or even EcoConservative (2) which will only use a max of 2 cores. IntelliPlug is able to use a single core unlike Mako Hotplug.
Mako Hotplug:
As far as I know the only way to tweak Mako Hotplug is either through the terminal app, synapse or through Francos app. In Francos app select cpu manager, then Hotplug Control. The main one you will need is load threshold. The default is 80. The higher this number, the more load the cpu needs to be under before it will plug the 3rd and 4th cores. 80 is actually pretty good value for most people and it will use the extra 2 cores when it really needs them. If you want to force all 4 cores on for whatever reason, you can achieve this by setting the load threshold to 0. This will effectively disable hotplugging. Of course you can always find a middle ground as well.
Via Terminal:
The sysfs interface for mako hotplug is...
/sys/devices/virtual/misc/mako_hotplug_control
To adjust... Use echo commands...
Ex:
echo 0 > /sys/devices/virtual/misc/mako_hotplug_control/load_threshold
The above command would set the load threshold to 0.
Thanks Rignfool!
Voltage Control:
Next go to voltage control. I'm a Bin 5 and I can use a 48mVolt undervolt without becoming unstable. 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 and nearly everyone should use at least a -24mVolt UV. Also remember that if you are running an over clock you may not want to undervolt that frequency. If you find yourself running into freezes or random reboots remove the undervolt!
Thermal:
This kernel comes with the latest IntelliThermal Driver from Faux123, which is a highly configurable thermal driver, as well as Franco's Thermal Driver which is the stock option. It is recommended you use IntelliThermal over Franco's if you wish to customize the values. Change this option under the Thermal Manager section of FauxClock. The optimal settings that I have found are 70 degrees for frequency throttle, and then somewhere between 70 and 80 for core throttle temp, depending on how safe you want to be. Stock is 80 degrees. Leave all cores checked for both frequency throttling and core throttling. I also leave on GPU Thermal Control, but if you encounter periodic lag in games you may wish to disable it. I also leave Core Thermal Control on as well, though I'm not entirely sure what it does lol. Also FYI, the sliders beneath those two options are showing you the current status of them, they are not sliders you can move.....trust me...I tried for like 5 minutes before I realized and felt like a moron....
I/O Settings:
For I/O scheduler select FIOPS. FIOPS is superior to the other schedulers in nearly every way. It is a scheduler designed for flash storage which is what our phones use. My testing has shown that 1536 is the best readahead buffer. Less or more is detrimental.
ZRam:
ZRam is something designed to optimize the ram of a device. What typically happens when a device runs out of space in ram is it is forced to use something called swap. Swap is normally a partition of a hard drive or ssd depending on what is available where the ram can copy some of it's contents to free up space. The problem is even the fastest SSDs are many many times slower than ram. Android by default doesn't have swap, however it does use a low memory killer which essentially goes through and clears out apps that are in ram to free space. ZRam makes a compressed partition inside the ram itself which then acts as a swap partition. Basically when ram begins to fill up. It compresses data and sticks it in a sealed off area of the ram. This let's it stuff way more stuff into ram than normal. To enable ZRam I use fauxclock. Trickster for whatever reason does not work. In FauxClock go to memory settings, then set the Zram size to 300mb and click apply disk size. Then turn it on and set on boot. You have now essentially boosted the available ram via compression!
VM Settings:
There are numerous tweaks you can do to the VM. For this I use FauxClock but IK Kernel Aduitor can do this as well. In FauxClock navigate to memory manager. The first thing to tweak is an option called swappiness. This control is used to define how aggressive the kernel will swap memory pages. Higher values will increase agressiveness. I defaulted this to 10 however the default is 60. This will use more ram but give better performance. Next is VFS Cache Pressure. This controls the tendency of the kernel to reclaim the memory which is used for caching of directory and inode objects. The default used to be 200. Its now defaulted to 10 meaning more ram usage but more performance. Next up is dirty ratio and dirty background ratio. Some things pass through ram and stay there for a bit until they get flushed to the flash storage. These controls essentially dictate how long it should wait before flushing to the flash storage. The longer you can delay it the better performance and battery you achieve, at the cost of ram. Setting these higher will increase ram usage but increase performance. I recommend a background ratio of 30 and a dirty ratio of 50, however feel free to tweak them as you desire.
Color Control:
Next you may want to adjust Screen RGB, value, saturation, hue and contrast. WrinkleFree over in the Lean Kernel thread did extensive testing with a professional grade $1000 screen calibration tool. You can use this app http://downloads.codefi.re/savoca/kcal to control the screen.
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
As for saturation. I like to turn it up a bit and make the colors pop a bit more so I leave it around 65. But quite honestly saturation,value,contrast,and hue are going to come down to tweaking it and finding what you like most. Have fun!
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! Good work man.
Thanks for sharing.
It does support the CM Theme Engine, right ?
x0nar said:
Thanks for sharing.
It does support the CM Theme Engine, right ?
Click to expand...
Click to collapse
Yessir using it as we speak
Seems buttery enough. Will let you know the battery life on Bliss 2.0
x0nar said:
Seems buttery enough. Will let you know the battery life on Bliss 2.0
Click to expand...
Click to collapse
Good to hear so far. Don't forget to lower your min frequency . Also I recommend either Conservative or Interactive governors ATM as they hook into the new CPU boost. I'll be posting a full configuration guide probably tomorrow. Hope you like it.
New kernel , SUPER
Fauert said:
New kernel , SUPER
Click to expand...
Click to collapse
Hope you like it! No doubt I'll be hearing many bug reports when I wake up tomorrow
I've been testing this kernel on a few different Roms without any issues at all really so everyone should be happy with it.
If anyone gets any reboots though do try and get logs [emoji106]
Xileforce said:
Good to hear so far. Don't forget to lower your min frequency . Also I recommend either Conservative or Interactive governors ATM as they hook into the new CPU boost. I'll be posting a full configuration guide probably tomorrow. Hope you like it.
Click to expand...
Click to collapse
Looking forward to your guide.
Nice kernel. Jist one thing, may be is a feature i dnt know but only 2 cores online when i tried tu push all cores on, just stay with 2 or 1 core on. I changed the hotplug but still the same
Sent from my Nexus 6 using XDA Free mobile app
Bestplayer55 said:
Nice kernel. Jist one thing, may be is a feature i dnt know but only 2 cores online when i tried tu push all cores on, just stay with 2 or 1 core on. I changed the hotplug but still the same
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Are you trying to do this for a Benchmark?
Using the Faux app you can first set it to Intelliplug , then Performance (4) Cores and that should get you there.
If not, try setting it that way and reboot. I've noticed with this phone that I've had to reboot a lot for my changes to actually take correctly.
Cpu2 and cpu3 are stuck in performance...
And does anyone know where in sysfs to adjust mako hotplug?
rignfool said:
Cpu2 and cpu3 are stuck in performance...
And does anyone know where in sysfs to adjust mako hotplug?
Click to expand...
Click to collapse
Gotcha.. Well once Mr Xile wakes up I'm sure he'll have something for you, not sure myself.
Mistertac said:
Gotcha.. Well once Mr Xile wakes up I'm sure he'll have something for you, not sure myself.
Click to expand...
Click to collapse
I found it... And I learned a new Linux command in the process...
Haven't done a full battery test yet, but I seem to be getting the best I've seen so far.
Bestplayer55 said:
Nice kernel. Jist one thing, may be is a feature i dnt know but only 2 cores online when i tried tu push all cores on, just stay with 2 or 1 core on. I changed the hotplug but still the same
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Currently if you disable all hotplugs or if you use fauxclock to set it to usercontrol that enables Franco's mako hotplug. Thats why in an app such as faux you cannot easily force two cores online. However if you use Franco's updster app you can go to CPU manager then hotplug control and if you lower the load threshold it will hotplug more frequently. Setting this to 0 will force all cores online. Additionally as mistertac said. Using b intelliplug on either performance(4) mode or balanced(4) will use all 4 cores pretty frequently as well.
Vindicator Kernel
Supports F/I/S/K/L/T/W8 variants of 920 AND 925 devices
Intro:
This kernel was built to appeal to users who want something thats trimmed down as much as possible, yet still adds nice features that arent considered bloat. I spent a lot of time optimizing it and plan on spending several more hours just on optimizations. This kernel is also built with significant amounts of upstream code merged in, making it what many would deem a hybrid kernel. All credit goes to the real hard workers coming up with original ideas like Franco, Imoseyon, Ktoonsez, g.lewarne, etc. 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, upstreaming source, 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 phone blows up, its not my fault. If your phone somehow gains perpetual battery life, I'll take full responsibility.
Features:-COGA Source Based
-Universal Kernel! (Thanks to G.lewarne and Ktoonsez patchset!)
-VControl Kernel Control Script(Loosely Based On lkconfig by imoseyon)
-Compiled With Graphite, Loop Nest Optimizations, Ofast And Others.
-Various Other Build Optimizations
-WLAN_RX & WLAN_CTRL Wakelocks Reduced
-GPU OC/UC
-Interactive ScreenOff Max Frequency
-Improved LMK
-Dynamic ReadAhead
-Dynamic Fsync
-LEDFade
-VMA Caching
-Calibrated Power Coefficients
-Smoothened GPU Throttling Curve
-Lz4 Compression
-Interactive Governor Patches/Mods
-Timer/RCU System Upstreamed
-SensorHub Wakelock Toggle To Remove
-A53 UnderClockable To 200Mhz Oc To 1600Mhz
-A57 UnderClockable To 200Mhz Oc To 2500Mhz
-Slub Allocator Updated To Linux 3.18
-Synapse Support
-Memory Management Updates
-Arm Efficient Unaligned Access Enabled
-Reduced Scheduler Wakeups
-Nvidia Power Efficiency Patches
-Encrypted Performance Improvements
-Deep Sleep Fix
-Disabled IO Stats For Faster IO
-Memory Leak Patches
-Sleep/Suspend Patches
-3X Faster Integer Square Root Operations
-HRTimer Optimizations
-Avoid load Average Moire
-Scheduler Optimizations
-Power Aware Scheduling
-Sound Control
-Memcopy and String Optimizations
-Use Compile Time Constants For Jiffies Conversions When Possible(Reduces CPU Overhead)
-Workqueue Updated To Linux 3.18
-Optional Power Efficient Workqueues (Expanded to more modules than normal as well)
-Moto QuickWakeup Driver
-Frandom (Efficient Random Number Generator)
-Cruft Free
-Slimmed Down
-Tons Of Debugging and Tracers Removed
-Many Misc. Optimizations
-Optimized CFQ Scheduler For SSDs
-Tons Of IO Fixes/Performance Boosts
-ROW IO Schedule(Default)
-Voltage Control For Numerous Things
-Entropy Optimizations/Tweaks
-Many Parts Pulled From Upstream
-Init.D Support
-Installs SU
-Installs Busybox
-Potentially Something I Forgot...
Downloads:
[AFH] Kernel: https://www.androidfilehost.com/?w=files&flid=35336
If Coming From Arter Kernel:
Reflash TWRP recovery if using philz and flash this zip http://www.mediafire.com/?um57p83b3cb56x4 before flashing kernel.
Credits:
Imoseyon
Ktoonsez
AndreiLux
Arter97
G.lewarne
Samsung
Flar2
anarkia
hybridmax
Franco
Faux123
Linaro
Code Aurora Foundation
Cl3Kener
Friedrich420
Google
Motorola
If I Missed You Lemme Know!
XDA:DevDB Information
VindicatorS6-Unified Kernel, Kernel for the Samsung Galaxy S6
Contributors
Xileforce
Source Code: https://github.com/XileForce/Vindicator-S6-Unified
Kernel Special Features:
Version Information
Status: Stable
Created 2015-07-13
Last Updated 2015-12-7
Changelog:
R1:
-Initial Release
R2:
-Updated From Linux 3.10.61 To 3.10.83
-Updated Memory Management Tweaks
-Update Interactive Tunings
-Fix App Installing
-Fix Random Reboots
-Removed Overclocking For Now(Caused reboots)
-Removed Fsync Toggle(Caused app installs to fail)
-Added Asynchronous Fsync(Faster Fsync)
-Fixed Frandom Permissions
-Additional Entropy Optimizations
-Added Interactive Patches
-Trimmed More Stuff
-Interactive No Longer Scales Up The Frequency Below 5% Load(Better Battery)
R3:
-Lag Free Interactive Tweaks (Glewarne)
-Interactive Screen Off Max Frequency = (InteractiveX)
-InputBooster Removed(Touchboost)
-BOG8 Source Update
-Memory Management Update
-Better Frequency Selecting By Interactive
-Numerous Interactive Code Optimizations/Patches
-Added A Toggle To Remove SensorHub Wakelock In VControl
-Remove Task Packing
-Trimmed More Things/Debugging
-Removed Forced Full screen Updates
-Some Power Efficient Related Tweaks
-Additional Optimizations
-Many Misc Things.
-Cifs support
R4:
-COGA Based
-Compiled With Linaro 5.2 TC
-Compiled With Ofast vs Os
-Fully Tickless Kernel(faster more power efficient)
-Updated Memory Tweaks
-Added CPU OC Again!
-Fixed Big Cpu Settings Not Sticking
-More Interactive Tweaks
-Reverted Enforced Mode
-Async Fsync Replaced With Dynamic Fsync
-Power Aware Scheduling Option
-Updated To Linux 3.10.87
-Added DT2W
-Misc Patches
-Added Synapse Support
-Updated Nvidia Power Efficiency Patches
-Various Upstream Timer/RCU Updates
-Add LED Fade Patch
-Add Audio Control
-Add Various Voltage Controls
-Optimize ART
-Update VControl Options
-CFQ Optimizations
-GPU Throttling Smoothing
-Task Packing Toggle Fixed
-Task Packing Threshold Adjusted
-Added PowerSuspend Driver
-Updated Unification Patches
-Disabled Gentle Fair Sleepers(Ui Smoothness)
-Numerous Interactive Patches
-Removed InteractiveX
-Re-Added TouchBoost
-Enable Efficient Unaligned Access
R4.1:
-Reverted Back To Dynamic Ticks Kernel
-Enabled Fast No Hz(Power Efficiency)
-Enabled RCU Priority Boosting(Performance Increase)
R5:
-Honestly Almost Everything Changed But Here's Some From Memory
-Interactive screen off limited to 1ghz
-Hotplug optimizations
-Interactive Patches
-LMK Upstreamed
-GPU OC/UC
-Ramdisk and synapse updated
-DT2W Removed
-LED Fade added
-Fixed Lockscreen Crashes
-GPU Tweaks
-Strict Aliasing Optimizations
-Significant amount of power efficiency patches
-Sound Control Removed
-More garbage removed
-Optimized a few libs for A57
-Updated To COJ2
-Lots more
FAQ's
1. What Is VControl And How Do I Use It?:
VControl is a kernel tweaking "app" built into the ramdisk. It is accessed via terminal emulator. To use it simply download terminal emulator, Type "su" without quotes and hit enter. Grant terminal emulator super user permission and then type "VControl" without quotes. Please note that it is case sensitive. This will bring up a text menu and you navigate by simply entering the option number you want and hitting enter. It is currently a WIP. More will be added to VControl over time.
2. You Broke My Phone! 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 with root support and navigate to proc/last_kmsg.
3. What Kernel Tweaking App Should I Use?:
To Tweak the kernel, currently the only apps that work well are Kernel adiutor and Kernel toolkit as well as synapse. You can also use VControl for a limited number of things. Synapse is now built into the kernel so simply install the app.
4. What Do Power Efficient Workqueues Do?:
Typically when a task is created, it is bound to the cpu it was created on. This is great for performance due to maintaining cache locality. However its not the best for battery life. Power efficient workqueues attempts to schedule tasks on already awake cpus. A quick note about awake and sleeping cpus. A sleeping cpu doesnt mean the cpu is turned off or not hotplugged, nor does this mean it has to be deep sleeping. A core can be online and still be sleeping which means it uses very little power. This is why we are able to run with all 8 cores on all the time. Most of the time the majority of the cpus are sleeping. With power efficient workqueues, jobs will attempt to schedule on awake cpus which means we dont have to wake up the cpus that are sleeping already. This means we lose cache locality so we suffer a small (very small) performance hit but we potentially save noticeable amounts of battery. Enable for battery, disable if you plan on benchmarking or just want the extra power. They are off by default.
5. 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
6. What does Small CPU Task Packing Mean?:
Task packing Is a process done by the scheduler. What it tries to do is pack all tasks onto as few cores as possible. In this case, it only packs tasks for the low power(small) cores as we want to maintain maximum performance and spread the load out on the bigger cores. The advantage of packing tasks is that if we envision a scenario where there is a 40% load and that gets spread out across the 4 small CPUs at 10% load each all 4 small CPUs are awake and running at a low frequency. With task packing all 40% would be shoved onto 1 core and the other 3 would sleep. This provides energy savings. However there becomes a point where the frequency required to process the extra tasks becomes high enough that it would use less power to run two cores at half the speed rather than 1 core at a very high speed. In this scenario the scheduler will automatically let tasks spill over onto adjacent CPUs in order to maximize power efficiency. One down side to this is a small performance hit due to having to pull the other cores out of a sleep state in the event of needing immediate power. However I would guess most people couldn't notice a difference.
7. What is power aware scheduling?:
Power aware scheduling is a method of scheduling where we make the scheduler aware of the actual efficiency of the cores. As you know, the small cores are more efficient than the big cores. The existing method for scheduling work uses a more basic (if the load is above this point, then move it to the big cores) type of decision making. With power aware scheduling, the scheduler will schedule tasks based on its knowledge of the cores power efficiency. Typically this reduces performance, though it's likely not noticeable except for in some games. If you want more battery, enable this. If you want more performance or have lag in games disable.
More will be added as they come up and I think of them.
Annnndd 3!
Great, downloading for test, my device is i variant but should works fine, any recommend settings?
matheus_sc said:
Great, downloading for test, my device is i variant but should works fine, any recommend settings?
Click to expand...
Click to collapse
I personally use VControl to set my min freq to 200 for both, then I oc to 1600 on Apollo and 2200 on atlas. I then also disable fsync. That's it hope you like it! Let me know if you have any issues!
great job with another kernel!
I enabled CPU task packing, but when I check the current settings, it says "/sbin/VControl(239): cat: /sys/kernel/hmp/packing_enable: No such file or directory"
interestingkid said:
great job with another kernel!
I enabled CPU task packing, but when I check the current settings, it says "/sbin/VControl(239): cat: /sys/kernel/hmp/packing_enable: No such file or directory"
Click to expand...
Click to collapse
Thanks! Yea I had task packing enabled in a previous test but removed it prior to release. I decided to leave it in VControl in case I re add it. So just ignore it for now I'll probably remove it in r2
Sent from my SM-G920T using XDA Free mobile app
Xileforce said:
Thanks! Yea I had task packing enabled in a previous test but removed it prior to release. I decided to leave it in VControl in case I re add it. So just ignore it for now I'll probably remove it in r2
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
ok, that's fine, because this is running well for now!
---------- Post added at 09:49 AM ---------- Previous post was at 09:48 AM ----------
ok so another problem though with google account or play services, don't know which
when i tried to install an app from the play store, i get an error -504
interestingkid said:
ok, that's fine, because this is running well for now!
Click to expand...
Click to collapse
Glad to hear that! There's definitely still room for improvement.
Sent from my SM-G920T using XDA Free mobile app
Boots fine in i variant from Brazil, but dont show much option in kernel auditor. I cant change i/o for fiops too its normal?
interestingkid said:
ok, that's fine, because this is running well for now!
---------- Post added at 09:49 AM ---------- Previous post was at 09:48 AM ----------
ok so another problem though with google account or play services, don't know which
when i tried to install an app from the play store, i get an error -504
Click to expand...
Click to collapse
Weird! I had that earlier too! I cleared my play services cache, and the play store cache and rebooted and it went away so I didn't think anything of it... :/ great...well at least I've got something to do tomorrow....
Sent from my SM-G920T using XDA Free mobile app
Xileforce said:
Weird! I had that earlier too! I cleared my play services cache, and the play store cache and rebooted and it went away so I didn't think anything of it... :/ great...well at least I've got something to do tomorrow....
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
kk will do that
matheus_sc said:
Boots fine in i variant from Brazil, but dont show much option in kernel auditor. I cant change i/o for fiops too its normal?
Click to expand...
Click to collapse
Kernel adiutor doesn't work for IO Scheduler. I recommend trying an app called Kernel toolkit. I'll probably add IO schedulers to VControl in the next update. Also there aren't tons of options on it atm. Mostly because its tweaked to run well on interactive governor, however I'll likely add conservative and ondemand in r2 as well.
Sent from my SM-G920T using XDA Free mobile app
interestingkid said:
kk will do that
Click to expand...
Click to collapse
Hope it works! I'm not sure what in Kernel is causing it, and its gonna be a pain to troubleshoot but I can probably figure it out tomorrow.....I hope....
Sent from my SM-G920T using XDA Free mobile app
This kernel is very fast and good deep sleep 94% all perfect on my G925F
Gesendet von meinem SM-G925F mit Tapatalk
cobra11111 said:
This kernel is very fast and good deep sleep 94% all perfect on my G925F
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
That's awesome to hear! Hope it continues to work well for you.
Sent from my SM-G920T using XDA Free mobile app
Can to future implement smartassv2 or KT governor?
Gesendet von meinem SM-G925F mit Tapatalk
cobra11111 said:
Can to future implement smartassv2 or KT governor?
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
The problem with kts governor is it would require merging a lot of other stuff that I don't need in order to make it work :/ however smartass is standalone. Is there other kernels for s6 that have it? If so it would be an easy addition most likely
Sent from my SM-G920T using XDA Free mobile app
Xileforce said:
The problem with kts governor is it would require merging a lot of other stuff that I don't need in order to make it work :/ however smartass is standalone. Is there other kernels for s6 that have it? If so it would be an easy addition most likely
Sent from my SM-G920T using XDA Free mobile app
Click to expand...
Click to collapse
+1 for smartassV2 governor and maybe zzmove as an option
No others kernel got those for S6
Hello, XDA! Me and @Da-BOSS would like to publish the Ultimate Kernel - Zeus :victory: .
Without too much hassle, let's see what this Kernel brings to our beloved Note 9.
{
"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"
}
Behold the wall of features
Android Q kernel is based from Google sources Android-Q branch with applied on top of it Samsung's kernel sources.
Since there is no more ELS repository for Android Q kernels.. I made a branch on the same repository on Github called [ZeusELS] which is purely a completely stock kernel with linux upstreamed always to the latest :angel: that's if anyone wanted to develop a new kernel from scratch also.. ZeusELS is based from Google sources Android-Q branch with applied on top of it Samsung's kernel sources too ! :fingers-crossed:
Download links are always at the end of this post
ZeusROM Features for Android Q
[*] It is just simply a replicate of DevBaseROM from @_alexndr but with more debloats and Zeus Kernel ready inside... just flash it and it is ready
Kernel Features for Android Q
Imported N960FXXS4DTA5 kernel sources
Used updated ramdisk N960FXXS4DTA5
The kernel is now compiled with GCC 10.0.1 along with LTO [Link Time Optimization] using the latest updates available for [isl,mpc,mpfr,zlib,etc..] GCC is self compiled with all kind of flags optimizations applied for maximum performance benefits and increase code quality
Using GCC LTO with all fixes and optimizations which leads to faster kernel operations and less kernel code bloating which will lead to less kernel size in which allows me to make room and use O3 kernel optimizations which will increase kernel size a little bit for results in significantly improved hackbench performance, which is a sign that overall performance in the kernel is improved. It works especially well in conjunction with LTO.
Implemented/Using [W.B.T.] Write Back Throttling driver which increases IO performance and smoothness of the kernel operating generally.. what it does is...
[Enable throttling of buffered writeback to make it a lot
more smooth, and has way less impact on other system activity.
Background writeback should be, by definition, background
activity. The fact that we flush huge bundles of it at the time
means that it potentially has heavy impacts on foreground workloads,
which isn't ideal. We can't easily limit the sizes of writes that
we do, since that would impact file system layout in the presence
of delayed allocation. So just throttle back buffered writeback,
unless someone is waiting for it.]
Implemented hybrid poll mode With this hybrid scheme, we can achieve big latency reductions while still using the same (or less) amount of CPU.
Implemented various patches from 4.10/4.14/4.19 imported
Simple LMK! first in the history of Samsung smartphones with all updates and patches applied
Undervolted everything on the SOC from RAM,CPU,Camera,CPU Bus,etc..
Reduced SELinux expensive calls for audit and disabled entirely
Updated SchedUtil to the latest patches & updates
Updated SchedUtilX to the latest patches & updates
Implemented IOwait and Use it + Make IOwait boost more energy efficient
Re-adjusted Samsung values on nearly everything volts,battery,ram,etc..
Using the S10/N10 Values to our beloved Note9 for Exynos hotplugging drivers
Using CPU Assist driver and updated its values
Disabled all kind of Debuggings, loggings, tracings aggressively kernel size is under 30MB!
Boost DevFreq whenever a new frame kicks
Added PowerSuspend Driver which will help on battery saving extensively and integrated it to display driver
Using HTC's Fsync named [Asynchronous Fsync] and made it working as default for Note 9
Implemented Sched Yields to force sleep whenever it kicks in
Moved MMC driver to SCHED_FIFO thread to reduce the impact of
load on IO performance.
Applied O3 compiling flags to Crypto drivers for increase performance
Tuned Up ALMK [Adaptive LowMemoryKiller] values and use it by default
Adapted and Implemented Force Reclaim driver from Lenovo and use it by default
Killed Samsung's poor RBIN memory management
Implemented CMA from Qualcomms devices and Use it as a replacment of Samsung's RBIN here what does it do..
[CMA pages are designed to be used as fallback for movable allocations
and cannot be used for non-movable allocations. If CMA pages are
utilized poorly, non-movable allocations may end up getting starved if
all regular movable pages are allocated and the only pages left are
CMA. Always using CMA pages first creates unacceptable performance
problems. As a midway alternative, use CMA pages for certain
userspace allocations. The userspace pages can be migrated or dropped
quickly which giving decent utilization.]
Introduce and Implement and Use GCMA [Guaranteed Contiguous Memory Allocator] read below what it does..
[While demand for physically contiguous memory allocation is still alive, especially in embedded system, existing solutions are insufficient. The most adapted solution is reservation technique. Though it serves allocation well, it could severely degrade memory utilization. There are hardware solutions like Scatter/Gather DMA and IOMMU. However,
cost of these additional hardware is too excessive for low-end devices. CMA is a software solution of Linux that aims to
solve not only allocation but also memory utilization problem. However, in real environment, CMA could incur unpredictably slow latency and could often fail to allocate contiguous memory due to its complex design. We introduce a new solution for the above problem, GCMA (Guaranteed Contiguous Memory Allocator). It guarantees not only memory space efficiency but also fast latency and success by using reservation technique and letting only immediately discardable to use the area efficiently. It shows 15 to 130 times faster and more predictable allocation latency without system performance degradation compared to CMA.]
Implement binderfs for Andorid IPC
Wakelock Blocker is used by default and it already blocks the needed wakelocks by default
Added DropCache feature which will help with memory management on the long run
Tuned Adaptive LMK to work Asynchronously
Implemented ZRAM Deduplication feature which will..save amount of memory usage by zram. Read below the benefits...
[Android is one of the biggest users to use zram as swap and it's
really important to save amount of memory usage. There is a paper
that reports that duplication ratio of Android's memory content is
rather high. And, there is a similar work on zswap that also
reports that experiments has shown that around 10-15% of pages
stored in zswp are duplicates and deduplicate them provides some
benefits.]
Implemented ZSWAP same-filled pages handling feature look below what does it do..
[Zswap is a cache which compresses the pages that are being swapped out
and stores them into a dynamically allocated RAM-based memory pool. This patch adds a check to identify
same-filled page before compression of the page. If the page is a
same-filled page, set zswap_entry.length to zero, save the same-filled
value and skip the compression of the page and alloction of memory in
zpool. Improvemnt in preformance varies between 19% ~ 32% increased performance in store time & 49% ~ 85% increased performance in loading time]
Implement B-tree function and Made ZSWAP to Use it by default which will lead to the following IO bogo operations: * original: 73778.8 * btree: 393999
WireGuad using the latest version always
Added MoroSound!
Brought a collection of Paranoid Android & Xiaomi patches to our beloved Note9 devices
Tuned UFS net boost table
Speed up scatterlist to roughly a 2x performance gain & Speed up cache entry creation for mbcache2
Implemented some fucntions & drivers from 4.14 Kernel and use it on Note 9 [which have 4.9 Kernel]
Using Jump Lable on the kernel read below what does it do..
[This option enables a transparent branch optimization that makes certain almost-always-true or almost-always-false branch conditions even cheaper to execute within the kernel.
Certain performance-sensitive kernel code, such as trace points, scheduler functionality, networking code and KVM have such branches and include support for this optimization technique.
If it is detected that the compiler has support for "asm goto", the kernel will compile such branches with just a nop instruction. When the condition flag is toggled to true, the nop will be converted to a jump instruction to execute the conditional block of instructions.
This technique lowers overhead and stress on the branch prediction of the processor and generally makes the kernel faster.]
Using Jump Lable Relative References on the kernel read below what does it do..
[Reduce the size taken up by absolute references in jump label
entries themselves and the associated relocation records in the
.init segment, add support for emitting them as relative references
instead.This reduces the size of the __jump_table by 33%, and
gets rid of the RELA section entirely.]
Improve ION cache accounting
Added Fingerprint Boost Driver
Low Memroy Killer features... LMK Fast RUN, OOM Reaper, Process reclaim
Updated ZRAM & ZSWAP with LZ4,ZSTD,LZO compression algorithm
Implemented Devfreq Boost driver and updated it... look below what it does
"This driver boosts enumerated devfreq devices upon input, and allows for
boosting specific devfreq devices on other custom events. The boost
frequencies for this driver should be set so that frame drops are
near-zero at the boosted frequencies and power consumption is minimized
at said frequencies. The goal of this driver is to provide an interface
to achieve optimal device performance by requesting boosts on key
events, such as when a frame is ready to rendered to the display."
Introduced a centralized Energy Model (EM) management framework which aggregates the power values provided by drivers into a table for each performance domain in the system.
Using always the latest GCC 10 Build with LTO self compiled
Added battery Store mode [used to limit charging] advanced use only & Unstable power detection driver and made it optional through HKTweaks app (Google it)
Added battery charging control!! [The first on XDA & outside XDA]
Kernel size decreased from 39MB to 28~29MB from the debloating the kernel! [Truth to be told the Lightest Kernel on XDA & Outside XDA]
WireGuad using the latest version always
Added MoroSound! because many requested it
Optimized GPU futher by speeding up rendering frames to the display driver
Disabled security options that reported it might slow down kernel operation upto 30% [Thanks @arter97!]
Tuned UFS net boost table
Fixed CPUSet driver & updated block core for faster operations
Optimized block driver that should help shaving off a few cycles of the I/O hot path
Improve event-poll driver which make wakelocks less likely to happen
Improved/Optimized hrtimer, alarmtimer, timers drivers
Added Spinlocks, Qspinlocks, RWLocks, QRwlock, Atomic drivers & updated it
Optimized Dcache & ARM driver to improve cache-line alignments performance
Optimized CGroup to have a dedicated kmem_cache pool and avoid costly dynamic memory allocations.
Dynamtic Shedtune driver implemented and updated it with the latest patches
Clean up garbage/unused codes from CPU governers
Optimized IO up to 34% improvement in the I/O latency.
Removed a lot of garbage code and cleaned it up
Updated lib lz4 modules from 2013 to 2018/2019 including all updates which makes it possible to enable applications to use fast and/or high compression depending on the use case
State notifier driver enabled
Linux Up streaming kernel updated to the latest always
Applied PSI driver on RAM , CPU , IO Drivers... see what it does...
[When systems are overcommitted and resources become contended, it's hard to tell exactly the impact this has on workload productivity, or how close the system is to lockups and OOM kills. In particular, when machines work
multiple jobs concurrently, the impact of overcommit in terms of latency and throughput on the individual job can be enormous.
In order to maximize hardware utilization without sacrificing individual job health or risk complete machine lockups, this patch implements a way to quantify resource pressure in the system.]
Compiled it with GCC 10 with the latest updates applied & custom optimizations is used
Implemented FRANDOM
Fade Ramp Control
SELinux Permissive/Enforced
Boeffla WakeLock Blocker
Added Unstable Power Detection through HKTweaks app (Google it)
CPU Max Freq for LITTLE - Max Freq 2002MHz Min Freq - 455Mhz
CPU Max Freq for BIG - Max Freq 2946MHz Min Freq - 650Mhz
Sky's the limit.. OC'ed CPU Quad Core to 2.31Ghz & Dual Core to 2.65Ghz! [Default on stock kernel is 1.8GHz Quad & 2.3GHz Dual]
Implemented Power saving work-ques and made it optional for those who don't like power saving
Updated F2FS to the latest updates taken from Android-Q Google sources! needs ROM modifications to get F2FS working on /data partition
HMP is synced with Googles latest scheduler changes
Kernel Features for Android Pie
Imported N960FXXU4CSK1 kernel sources
Used updated ramdisk N960FXXU4CSK1
Implemented Devfreq Boost driver and updated it... look below what it does
"This driver boosts enumerated devfreq devices upon input, and allows for
boosting specific devfreq devices on other custom events. The boost
frequencies for this driver should be set so that frame drops are
near-zero at the boosted frequencies and power consumption is minimized
at said frequencies. The goal of this driver is to provide an interface
to achieve optimal device performance by requesting boosts on key
events, such as when a frame is ready to rendered to the display."
Taken SDCard drivers from Note10.
Introduced a centralized Energy Model (EM) management framework which aggregates the power values provided by drivers into a table for each performance domain in the system.
Possible fix for 1950Mhz to be forced to 2GHz
Added & enabled BBR tcp optimizations and networking operations optimizations... using fq_codel+bbr
[Observed a significant increase in BBR throughput (measured using netperf), in a basic wifi setup.]
Implemented further more CPU optimization for power consumption from Nvidia!! to Enhance power efficiency and adapted it to our Note9 device
Using always the latest GCC 10 Build with LTO self compiled
Optimized UKSM function and KSM along with it
Add ROW scheduling algorithm & ROW driver... mechanism of it is...
[The ROW scheduling algorithm will be used in mobile devices as default
block layer IO scheduling algorithm. ROW stands for "READ Over WRITE"
which is the main requests dispatch policy of this algorithm.
The ROW IO scheduler was developed with the mobile devices needs in
mind. In mobile devices we favor user experience upon everything else,
thus we want to give READ IO requests as much priority as possible.
The main idea of the ROW scheduling policy is:
If there are READ requests in pipe - dispatch them but don't starve
the WRITE requests too much.]
Added battery Store mode [used to limit charging] advanced use only & Unstable power detection driver and made it optional through HKTweaks app (Google it)
Added battery charging control!! [The first on XDA & outside XDA]
Made automated driver for read-ahead size decision when inserting any OTG/USB external storage on the device to optimize file processing performance.
Kernel size decreased from 39MB to 34.9MB from the debloating the kernel! [Truth to be told the Lightest Kernel on XDA & Outside XDA]
WireGuad using the latest version always
GFS - Gentle Fair Sleepers options provided to have more battery life
Added MoroSound! because many requested it
Initial support for Nethunter users
Optimized GPU futher by speeding up rendering frames to the display driver
Disabled some security options that reported it might slow down kernel operation upto 30% [Thanks @arter97!]
Added/Implemented UKSM
Brought a collection of Paranoid Android & Xiaomi patches to our beloved Note9 devices
Tuned UFS net boost table
Fixed CPUSet driver & updated block core for faster operations
Optimized block driver that should help shaving off a few cycles of the I/O hot path
Added SIMD & VSDO Technology
Added Power suspend driver and integrated it to display driver
Improve event-poll driver which make wakelocks less likely to happen
Improved/Optimized hrtimer, alarmtimer, timers drivers
Added Spinlocks, Qspinlocks, RWLocks, QRwlock, Atomic drivers & updated it
Added Dynamic Fsync driver and made it available with normal Fsync driver
Introduce CPUSet Assist driver for optimized multitasking
Optimized Dcache & ARM driver to improve cache-line alignments performance
Optimized CGroup to have a dedicated kmem_cache pool and avoid costly dynamic memory allocations.
Added Sweep2wake, Doubletap2wake and Sweep2sleep for Samsung Galaxy Note 9
CPU Input driver implemented and updated
Micro-optimizations for Ion driver, Binder, PCI Exynos drivers, hotplug driver,F-ECM driver.
CPU-Boost driver implemented and updated to the latest version including all kind of patches and updates from Sony,Xiaomi, and Nvidia
Dynamtic Shedtune driver implemented and updated it with the latest patches
Clean up garbage/unused codes from CPU governers
Optimized IO up to 34% improvement in the I/O latency.
Using Galaxy S10 + Note 10 HMP extracted drivers combined and implemented it to our be loved Note 9!
Introduced [Host Performance Booster] HPB driver from Pixel 3! & Adapted it to our Note9!! Please read below what HPB can do...
[HPB is essentially caching of the NAND chip’s FTL (flash translation layer) L2P (logical to physical) mapping tables into the hosts (SoCs) main memory. This allows the host driver to look up the target L2P entry directly without betting on UFS’s limited SRAM to have a cache-hit, reducing latency and greatly increasing random read performance. The authors of the feature showcase an improvement of 59-67% in random I/O read performance due to the new feature. It’s worth to mention that traditional Android I/O benchmarks won’t be able to show this as as those tend to test read speeds with the files they’ve just created.]
(Source of this info ---> Here)
Added Ainur audio driver for those who want to use DTS Audio mods
Applied PSI driver on RAM , CPU , IO Drivers... see what it does...
[When systems are overcommitted and resources become contended, it's hard to tell exactly the impact this has on workload productivity, or how close the system is to lockups and OOM kills. In particular, when machines work
multiple jobs concurrently, the impact of overcommit in terms of latency and throughput on the individual job can be enormous.
In order to maximize hardware utilization without sacrificing individual job health or risk complete machine lockups, this patch implements a way to quantify resource pressure in the system.]
Implemented AnyKernel Installer for the kernel so now Kernel will be flashed as a zip file! no more lockscreen/Samsung account issues (Make sure to clean install ROM if you have Samsung account issues)! [Big Thanks to @klabit87 for his awesome help! & @djb77 for his permission to use some of his scripts]
Updated Ramdisk to the latest build
Updated Kernel build base to the lastest available
Removed a lot of garbage code and cleaned it up
Updated lib lz4 modules from 2013 to 2018/2019 including all updates which makes it possible to enable applications to use fast and/or high compression depending on the use case
State notifier driver enabled
Linux Up streaming kernel updated to the latest always
Added IO governor & Updated to the newest version/patches:-
-Anxiety
-Maple
-SIO
-FIOPS
-Marrow
-Tripandroid
Implemented IO Switcher Driver (Taken from Oreo kernel) which will save more battery by switching IO Governor to 'Noop' when Screen Off and switch back to CFQ when is On for maximum battery and optimization + without need any user intervention... it does this automatically.
Fixed USB issues
Compiled it with GCC 10 with the latest updates applied & custom optimizations is used
Implemented FRANDOM
Fade Ramp Control
Compatible with DriveDroid
WireGuard Support
SELinux Permissive/Enforced
Boeffla WakeLock Blocker
Added Unstable Power Detection through HKTweaks app (Google it)
Using CPUAssist & StuneAssist
Implemented SchedUtilX CPU Gov and made it as default
Implemented Blu_schedutil CPU Gov
CPU Max Freq for LITTLE - Max Freq 2002MHz Min Freq - 455Mhz
CPU Max Freq for BIG - Max Freq 2946MHz Min Freq - 650Mhz
Sky's the limit.. OC'ed CPU Quad Core to 2.31Ghz & Dual Core to 2.5Ghz! [Default on stock kernel is 1.8GHz Quad & 2.3GHz Dual]
Implemented Power saving work-ques and made it optional for those who don't like power saving
Updated F2FS to the latest updates taken from Oreo!
CPU Input driver implemented and updated
Battery polling & NFS wakelock control
State notifier driver
SimpleLMK [Oreo feature for the moment]
GPU OC [Oreo feature for the moment]
And a lot more, that you need to find .
FDE.AI & L Speed & Nuked Script it's been tested for Zeus kernel & ROM and me as a Kernel Developer I officially support it. It is been tested for everything.. stability , performance and improved battery life
Everyone give full support to those developers @Paget96 , @FeraVolt :fingers-crossed:
====================================================================================================
ZeusROM Q Version
For N960F/FD users:-
GoogleDrive Download Link:-
Download Link Here
Mega Download Link:-
Download Link Here
MD5:- a1d7cc2991435c74cf843b0ff468e70c
For N960N users:-
GoogleDrive Download Link:-
Download Link Here
Mega Download Link:-
Download Link Here
MD5:- aa656b105dfcf00a8e76e33e11b7beb4
====================================================================================================
Kernel Q Version
Here
Kernel Pie Version
Here
Telegram Link
mod edit - link removed
I recommend using Hktweaks app through this link.. it fully supports Zeus kernel
Here
Credits:-
Samsung Open Source Release Center for the Source code
Google for AOSP Common Kernel Source
@osm0sis for Android Image Kitchen
@klabit87 for his scripts :highfive:
@farovitus for ELS
@djb77 for scripts
@Anastasis Vasileiadis for his help to provide the needed changes for NetHunter to work
@Arteush for providing a proper scripts to get it working with all TWRP (Especially his own ones)
@Eamon for compile script
And every one that made Android a beautiful world! :fingers-crossed:
XDA:DevDB Information
Zeus Kernel, Kernel for the Samsung Galaxy Note 9
Contributors
azZA_09, Da-BOSS, All users on telegram group
Source Code: https://github.com/THEBOSS619
Kernel Special Features: F2FS, Custom CPU BUS, Debloated Code, Power Suspend Driver, CPU OC, CPU Bus Mods, Driver Mods, Pocket Judge Idle, GCC Mods, IO Switcher, UFS Mods, DynFsync, Host Performance Boost[HBP], HMP mods, Ainur Audio, SIMD & VSDO
Version Information
Status: Stable
Created 2019-08-28
Last Updated 2020-04-14
In order to Install the Kernel:
- Flash the Kernel in TWRP
- Flash Magisk
Recovery to be used - https://forum.xda-developers.com/galaxy-note-9/development/recovery-twrp-galaxy-note-9-t3929901
Thanks a lot @Arteush and @yarpiin for your hard work!
Magisk to be used - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 - (Beta Version)
When you want to report a bug, provide logcat, ROM, Kernel Version and a way to replicate the bug.
For logcat, use https://github.com/Tortel/SysLog
How To Convert To F2FS Without Losing Data
Notice -You MUST have TWRP F2FS compatible recovery
1 - Backup your [Data] partition and your [Internal Storage](if possible)
2 - Warning backing up [Data] partition doesn't include your internal storage files like (Images,Musics,Video,etc..)
3 - Once finished, Convert /Data & /Cache Partition to F2FS
4 - Go to TWRP settings.. and tick [] at [Use rm-rf instead of formatting]
5 - Restore your backup.
6 - Done!
Sorry for the duplicates, use this thread till the other ones are deleted!
Thank you for your big contribution... the kernel wouldn't reach this level without you & your patience & most importantly your motivation & passion to keep pushing the kernel to the edge
Thank you from all my heart O
Thanks for your precious efforts my friend.
I am using latest kernel with latest ambasadii. Working like a charm.
How to keep the cpu freqiencf locked ?
I have no words to describe this!!! Kernel is super fast, super smooth and the apps are opening in lighting speed! I can't believe what im seeing here. THANK YOU, THANK YOU!
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 10:45 AM ---------- Previous post was at 10:01 AM ----------
samsung account failed to sign me in. maybe check this out.
Sent from my [device_name] using XDA-Developers Legacy app
karapoutsoglou said:
I have no words to describe this!!! Kernel is super fast, super smooth and the apps are opening in lighting speed! I can't believe what im seeing here. THANK YOU, THANK YOU!
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 10:45 AM ---------- Previous post was at 10:01 AM ----------
samsung account failed to sign me in. maybe check this out.
Click to expand...
Click to collapse
What baseband. CSG5 or CSG2
azZA_09 said:
-Go into TWRP recovery
-After that, Install Magisk
Click to expand...
Click to collapse
Could you provide correct links for:
- the F2FS supporting version of TWRP suitable for N960F
- the Magisk installer that can be installed using this TWRP
TIA.
jult said:
Could you provide correct links for:
- the F2FS supporting version of TWRP suitable for N960F
- the Magisk installer that can be installed using this TWRP
TIA.
Click to expand...
Click to collapse
Join telegram group and you will find everything you need the group is created for a reason... to provide support & to have everything you need for info :angel:
azZA_09 said:
What baseband. CSG5 or CSG2
Click to expand...
Click to collapse
CSG2
Sent from my [device_name] using XDA-Developers Legacy app
karapoutsoglou said:
CSG2
Click to expand...
Click to collapse
Update to csg5 and everything will work
jult said:
Could you provide correct links for:
- the F2FS supporting version of TWRP suitable for N960F
- the Magisk installer that can be installed using this TWRP
TIA.
Click to expand...
Click to collapse
Sure thing. Later today.
How do I switch to enforcing from permissive?
Thanks
Sent from my SM-N960F using Tapatalk
ALLDAT said:
How do I switch to enforcing from permissive?
Thanks
Click to expand...
Click to collapse
Kernel auditor, mtweaks or magisk selinux changer module. Your choice.
azZA_09 said:
Kernel auditor, mtweaks or magisk selinux changer module. Your choice.
Click to expand...
Click to collapse
Do you know where I can change that in ex kernel manager?
Sent from my SM-N960F using Tapatalk
ALLDAT said:
Do you know where I can change that in ex kernel manager?
Click to expand...
Click to collapse
I don't think you can do it
azZA_09 said:
I don't think you can do it
Click to expand...
Click to collapse
Thanks
Sent from my SM-N960F using Tapatalk
azZA_09 said:
Update to csg5 and everything will work
Click to expand...
Click to collapse
There is a CSG5 Baseband and a CSG5 Bootloader?