Welcome to AK Kernel Synapse Profiles HUB, Feel free to share your configs and profiles here.
AK Kernel Official Thread - Click Here
AK Kernel Official Website - Click Here
Big Thanks to @ak for all the hard work he has done for the AK KERNEL.
Instructions for How to Backup and Restore a profile in Synapse Click Here
@mamba720027's Profile Workshop Click Here
@Stylo King's ElementalX V2 Click Here
@Stylo King's Battery-EAS V1 Click Here
Instructions for How to Backup and Restore profiles in Synapse.
PS- Make sure you have set SeLinux to Permissive.
If you want to Backup a profile -
1. Input profile name (Should not have any special characters) and press enter
2. Press check mark at the top
3. Press backup current profile.
4. If the backup was successful you'll get a toast saying so
If you want to See the profile -
1. Press restart synapse and wait till it starts by itself
If you want to Restore a profile -
1. Place profile .tgz file in synapse profiles folder
2. Press restart synapse
3. Go into profile section and select profile you want (can't have any special characters) press the check at the top.
4. Press apply profile
5. Open synapse again and hit the "X" at the top and wait for settings to apply
6. Close synapse and open it again and press the X again
7. Repeat step 7 until the "X" no longer appears
If you want to Apply the profile on boot -
1. Go into settings and check apply on boot
2. Do not reboot for at least 2 minutes or the settings will get reset.
3. If you don't want to wait 2 minutes then uncheck stability check (you may get stuck in a boot loop if your settings make your phone SOD or RR)
NOTE : If a profile doesn't setup correctly, Clear synapse data.. Reboot if necessary.
Note 2 : For best results, Reboot and charge till 100% after applying a profile.
Reserved
///////////////////////////////////////////////////////////////
ROM - Pure Nexus
Kernel - AK Kernel
Mods - None
///////////////////////////////////////////////////////////////
interactive bat V5
Updated+ 3/29/16
//Settings//
:::A53:::
- CPU Min/Max 302/1708mhz
:::A57:::
- CPU Min/Max 633/2054mhz
- Interactive Governor
- 4+4 Cores Online
- Hot-plugging (MSM Performance Driver)
- GPU Min/Max 180/600mhz
- GPU Gov msm-adreno
- Memory Tweaks
- LMK Adjustment Preset
- Noop Scheduler
- Sound High Performance Speaker Boost +23
- Custom Gamma Profile
Click to expand...
Click to collapse
++Main New Adjustments++
- A53+A57 Interactive governor adjustments
- I/O Adjustments
- Memory Adjustments
- mamba_feat_hackachive v2 Gamma Profile (updated)
: Stock Gamma (KCAL 256,256,256 Hue 0, All other values 255)
Utilizing max available CPU speeds with mainly CPU governor adjustments to bias good battery performance with all the best AK kernel features available.
interactive bat V5
********************
ENexus Conservative V3
Updated+ 2/29/16
This profile is more of a battery saving setup that may lack certain performance in areas to meet a more battery saving need. A profile for those not always next to their chargers.
//Settings//
:::A53:::
- CPU Min/Max 460/1555mhz
:::A57:::
- CPU Min/Max 302/2054mhz
- Impulse Governor
- 2:2 Cores Online
- Hot-plugging (MSM Performance Driver)
- GPU Min/Max 180/450mhz
- GPU Gov msm-adreno
- Memory Tweaks
- LMK Adjustment Custom
- tripndroid Scheduler
- Sound High Performance Speaker Boost +23
- Custom Gamma Profile
Click to expand...
Click to collapse
++Main New Adjustments++
- New Impulse Gov adjustments/better speeds and power consumption
- Hot-plugging 2+2 cores on clusters reduce power consumption
- tripndroid Scheduler
- Misc general adjustments New
- mamba_feat_hackachive Gamma Profile (updated)
: Stock Gamma (KCAL 256,256,256 Hue 0, All other values 255)
Update reworks the impulse governor adjustments to achieve better speeds selection for workload & using less cores than previous versions to meet a lower power consumption and maintaining a stable and everyday user setup.
ENexus Conservative V3
************************************
Pure Flow V2
Updated+ 3/4/16
Not a lot has change or needed adjustment in V2 Update. Mostly changes in the memory section. Just a smooth performance profile.
//Settings//
:::A53:::
- CPU Min/Max 460/1708mhz
:::A57:::
- CPU Min/Max 480/2054mhz
- Ondemand Governor
- 4:4 Cores Online
- Hot-plugging (MSM Performance Driver)
- GPU Min/Max 180/600mhz
- GPU Gov simple_ondemand
- LMK Adjustment Stock
- SIOPlus Scheduler
- Sound High Performance Speaker Boost +25
- Custom Gamma Profile
Click to expand...
Click to collapse
++Main New Adjustments++
- Ondemand Gov adjustments moderate
- Hot-plugging workload adjustments
- SIOPlus Scheduler tweaked
- Misc adjustments/Memory
- mamba_feat_hackachive Gamma Profile (updated)
: Stock Gamma (KCAL 256,256,256 Hue 0, All other values 255)
Pure Flow V2
********************************************
Elemental HybridX
Updated+ 2/5/16
This profile is a mix of ElementalX+Impulse governor. Impulse works in a more performance manner on big cluster while ElementalX is more balance on smaller cluster. Everything is carefully adjusted to create a very fluid UI experience down to performance workload speed times. Power is not wasted on small tasks. This is just something I was testing some ideas out on.
//Settings//
:::A53:::
ElementalX Governor
- CPU Min/Max 460/1248mhz
:::A57:::
Impulse Governor
- CPU Min/Max 302/2054mhz
- 4:4 Cores Online
- Hot-plugging (MSM Performance Driver)
- GPU Min/Max 180/600mhz
- GPU Gov simple_ondemand
- LMK Adjustment Stock
- SIOPlus Scheduler
- Sound High Performance Speaker Boost +22
- Custom Gamma Profile
Click to expand...
Click to collapse
++Main New Adjustments++
- Gov adjustments moderate
- Hot-plugging workload adjustments
- SIOPlus Scheduler tweaked
- Misc adjustments/Memory
- mamba_feat_hackarchive Gamma Profile
: Stock Gamma (KCAL 256,256,256 Hue 0, All other values 255)
Click to expand...
Click to collapse
Elemental HybridX
*******************************************************
EAS Balance V3
Updated+ 4/16/16
[Profile For EAS-AK Kernel]
Using interactive governor instead of sched on EAS kernel in order to achieve better performance & battery.
//Settings//
:::A53:::
- CPU Min/Max 460/1708mhz
:::A57:::
- CPU Min/Max 633/2016mhz
- 4+4 Cores Online
- Hot-plugging (MSM Performance Driver)
- GPU Min/Max 180/600mhz
- GPU Gov msm-adreno
- Memory Tweaks
- LMK Adjustment Preset
- fiops Scheduler
- Sound High Performance Mode +23 Speaker
- Custom Gamma Profile
Click to expand...
Click to collapse
++Main New Adjustments++
- New Interactive gov adjustments for EAS
- Hot-plugging workload adjustment
- fiops Scheduler tweaks
- LMK Preset
- hackarchive Latest Gamma adjustments
::: - Stock Gamma (KCAL 256,256,256 Hue 0, All other values 255) :
:Thanks to @hackarchive for sharing these gamma adjustments to make our superamoled displays look even more awesome :::
EAS Balance V3
Thanks @ak for a great kernel & all his work.
Thanks @Stylo King for maintaining this thread.
Thanks @hackarchive for the gamma adjustments.
Thank you guys!
Sweet!
mamba720027 said:
@styloking
Here's just the link to profile for now. Will use this spot as a base as usual so it will update later
Interactive bat v2 profile
https://www.dropbox.com/sh/vjs48hxifjmwokf/AAAXl4bxwSKUvaJFQC2lV95sa?dl=0
Click to expand...
Click to collapse
Thank you mamba! I'm getting better battery life than your v1. I have a problem with my notification LED and sound cutting out when they come in. Any tweak I could do to help?
DJMartini said:
Thank you mamba! I'm getting better battery life than your v1. I have a problem with my notification LED and sound cutting out when they come in. Any tweak I could do to help?
Click to expand...
Click to collapse
Great!! :thumbup:
Haven't done stuff with the notification LED.
Only sound adjustment in Synapse/Sound "HPM" enable +23 to speaker boost. You could set that back to default -20 and see if its the reason and disable "HPM" see what happens.
Other than that if you use any audio mods you may want to disable to see if that's the cause of interference.
mamba720027 said:
@styloking
Here's just the link to profile for now. Will use this spot as a base as usual so it will update later
Interactive bat v2 profile
https://www.dropbox.com/sh/vjs48hxifjmwokf/AAAXl4bxwSKUvaJFQC2lV95sa?dl=0
Click to expand...
Click to collapse
No, I won't add it to OP until you quote me right :silly:
Stylo King said:
No, I won't add it to OP until you quote me right :silly:
Click to expand...
Click to collapse
lol, I always mix that quote thinge up
mamba720027 said:
lol, I always mix that quote thinge up
Click to expand...
Click to collapse
BTW your timing was perfect, 4th post from the OP is your Profiles workshop.. Swag
Stylo King said:
BTW your timing was perfect, 4th post from the OP is your Profiles workshop.. Swag
Click to expand...
Click to collapse
yea, I was lucky. Will work right in their nicely with the OP
Glad you got your 6P, now for some Stylo King magic. What color you got and capacity?
I got the Aluminum 64GB with CASEFORMERS ultra slim armor case below. Everyone I met like it.
mamba720027 said:
yea, I was lucky. Will work right in their nicely with the OP
Glad you got your 6P, now for some Stylo King magic. What color you got and capacity?
I got the Aluminum 64GB with CASEFORMERS ultra slim armor case below. Everyone I met like it.
Click to expand...
Click to collapse
Aluminium 64 Gigs Naked..I don't like cases
Stylo King said:
Aluminium 64 Gigs Naked..I don't like cases
Click to expand...
Click to collapse
Same here,first time I using a case :thumbup:
Op main thread updated, thanks a lot guys:
[ AK KERNEL NEXUS 6P PROFILES THREAD ]
This thread is for people to post their profiles with each other: Link
Thanks a lot
@Stylo King
@mamba720027
Manage this while optimising IO workloads, ROW adjustments & Memory
mamba720027 said:
Manage this while optimising IO workloads, ROW adjustments & Memory
Click to expand...
Click to collapse
Still tweaking that set up? ?
zandander said:
Still tweaking that set up? ?
Click to expand...
Click to collapse
I am, lol. Its even more snappy now and load times improved. This what IO looks like now
Jesus! That's reminiscent of AK kernel on the gnex. His kernel had the highest IO of any kernel back in the day. I'm excited for this one
zandander said:
Jesus! That's reminiscent of AK kernel on the gnex. His kernel had the highest IO of any kernel back in the day. I'm excited for this one
Click to expand...
Click to collapse
I'm excited myself @ achieving more improvement upon what I taught was most we could hit with IO but apparently I was wrong plus as I go along spending more time in that department I learn more stuff
Related
I proudly present to you
Nook On Fire Showtime V3.22
Nook On Fire Nemesis V2.4
Dear Nook Tablet users,
Welcome to the unbelievably Stable,Butter Smooth,Fast and Feature Rich: Nook On Fire Kernel!
This kernel is based on Official CM10.1 kernel sources.
I'll continue to add more features to the kernel in the future and when real life permits.
Oh, and yes: I built the kernel because I have fun doing so. But be not mistaken that I am a 'play-around kid': I dislike pulling in every little mod someone made. What I want is stability.
This kernel can be flashed on:
- SlimBean
- Official CM10.1
- LiquidSmooth
- AOKP Rom
- CarbonRom
- SGT7 Rom By TheForceUnleashed
You can use Trickster MOD Kernel Settings app from Google Play to control some aspects of this kernel
Link: https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod
I hope you enjoy my kernel
Nook On Fire kernel features:
*Up2date kernel Revision.
*Up2date CPU Schedulers.
*Up2date CPU Governors.
*Pushes Nook Tablet inbuilt hardware's to the maximum of their capabilities.
*Performance/battery carefully picked tweaks
*Default max CPU frequency: 1.20 GHz
*LCD Panel tweaked to reach manufacturer recommendations and reach maximum performance as the settings are taken by the datasheet pdf.
*ARM CPU topology! More info here
*More tweaks under the hood (check sources if you're interested)
*Lots more **** - flash and see for yourself
F.A.Q:
1. My device rebooted or crashed, how can I help?
A: Get me /proc/last_kmsg or logcat.
2. Battery sucks, my device is not entering deep sleep.FIX PLOX!
A: Fix it yourself, it's an app waking your device up not the kernel's problem
3. Do I need to wipe anything when flashing this kernel?
A: No.
4. No WiFi?
A: Rename /etc/firmware/ti-connectivity/wl1271-nvs_127x.bin -> wl1271-nvs.bin
5. Wrong MAC address?
A: This is a residue problem (dirty installation). Just delete wl1271-nvs.bin and reboot.
6. Does this kernel has X or Y mod?
A: Learn to read, everything you need to know is in the features list, changelog or public repo.
Changelog History:
Click to expand...
Click to collapse
Nook On Fire Showtime Kernel
V3.22 changelog
- OMAP4:Fix HSMMC 3/4/5 master clock
- Nohz/sched: don't go tickless when CPU is loaded
- LPDDR2 RAM timings optimization for 10% speed increase
V3.21 changelog
- 10! Yes 10 touch driver is back Thanks to Mik_os
- GPU is pushed to the limits 384Mhz from 307mhz
- I give back to gpu the volt juice it had it might need some adjustment still.
- Our cpu frequencies are changed
- Cpu frequencies are now these
200Mhz/600Mhz/999Mhz/1.1ghz/1.22ghz
V3.2 changelog
- Some more cherry picks
- 720p/1080p video playback seems fixed.
- Reverted previous hashcode commit about usb detection and power down.(was eating battery)
- Am declaring this release stable if no major issues surface.
- Kernel now is ready for serious heavy weight work.
V3.11 changelog
- Trying to fix 720p/1080p video playback issues
- Pushed a reverted commit about usb detection and power down from Hashcode for testing
- Repo Synced to RC5
- Second Showtime release but things show stable enough for me
- If no negative feedback i will declare next release stable So speak now or be silent forever.
V3 changelog
- First released kernel based on Kindle Fire 2 and I9100G (t1) source code.
- Linux Kernel 3.0.81
- More than 100 commits
- New features added and more to come
- Might need some fine-tuning as this is 1st release.
- Highly experimental so if you don’t need adventures stay with NOF-Nemesis for now
Nook On Fire Nemesis Kernel
V2.4 changelog
- I started borrowing code from Kindle Fire kernel, so for now we have code changes from them in:
- GCX
- USB
- MMC
- EMIF
- WIFI
And 2 Great Cherry picks from Hashcode that might fix kernel issues some Nook Tablets have
1. https://github.com/Ntemis/NOF-Nemesis/commit/f0f3f061f94544fb87c429d9e93ae417e00b3458
2. https://github.com/Ntemis/NOF-Nemesis/commit/0799813998b44dcfae0728cd8f16576931b4432f
Edit: Confirmed, now it boots on problematic nooks that couldnt use 1.2ghz previously.Welcome to 1.2ghz era boyz
V2.21 changelog
- Kernel 3.0.80
- Tried to boost io performance
- slub: zero page, trying to fix boot crashes
- Lowered cache presure from 100 -> 50
V2.11 changelog
- Galaxy Nexus Kernel processwith addictional code from franco: shorten freezer sleep time using exponential backoff
- Borrowed immoseyon interactivex governor and edit it to fuction on our interactive, when using interactive you now use interactivex.
- I tunalize interactivex header so we can use interactivex from Gnex.
- Watchdog driver borrowed from Gnex
V2.1 changelog
- Touch driver code review
- Accelerometer code review
- Kernel 3.0.79
- Some wireless code borrowed from Tuna
- Fix some issues with kernel power proccess and filesystem syncing
V1.73 changelog
- More Changes
- Upsteam Synced
V1.72 changelog
- Some more fixes and addictions
V1.70 changelog
- Linux Kernel 3.0.78
- Sio updates by Boy Petersen
V1.66 changelog
- Power related changes like Wakelock/Suspend
- Timer related issues
- Sleep and wake up changes
- Fixes in several mempolicy leaks in tmpfs mount logic
- OMAP4430 Cpu Governors Finetunning to:
Hyper/Conservative/Hotplug/Ondemand/PegasusQ and Wheatley
- Port Snappy and Frontswap and Reworked on Zram tweaks and enchancements.
- CM10.1 RC2 Synced
- Now when usb is plugged for charge etc, it wakes up :highfive:
V1.60 changelog
- Linux Kernel Upgrade to 3.0.77
- Finetuned page writeback for Vmalloc=128mb
- Upstream Sync
V1.52 changelog
- Fixed Smartass V2
- Added HYPER Cpu Governor
- Disabled Fair Sleepers for UI smoothness
V1.51 changelog
- Added SmartAss V2 Cpu Governor
- Reduced Cpu latency from 40ms to 15ms(testing)
- Since no reports came up after i released UnderVolt Kernel for test now UnderVolting is officially implemented into my kernel.
V1.50 changelog
- Add assembler versions of AES and SHA1 for ARM platforms. This has provided
up to a 50% improvement in IPsec/TCP throughout for tunnels using AES128/SHA1.
- ARMv7: Flush the vectors page using the base address.
- OMAP4: PM: fix overconsumption on OFF mode
- SIO I/O sheduler updates and tweaks finetunned to omap44xx
- CFQ I/O sheduler updates and tweaks finetuned to omap44xx
- Upgraded Linux Kernel to V3.0.76
V1.42 changelog
Changes are a lot more and you are more than welcome to read my github.
Some of them are:
- Low Memory Killer ported from 3.9 kernel
- Some ondemand tweaks to increase frequency early.
- Disable CRC in Mmc driver
- Read ahead fine tunning
- Mmc core: Fix possbile memory leak
- Interactive fixes and updates
- Ported Logger from mainline 3.9
- Decreased the amount of time the device waits after entering low power mode to freeze processes.
- Reduce System logging
- Prevent enqueue of hrtimer on dead CPU
- Another kernel Upgrade to 3.0.75
- Reverted some commits that i was suspecting them to be my troublesome ones.
They were causing troubles like hard power downs and lockups.
V1.35 changelog
- Reduced swappiness from 60 to 45
- Make kernel actually use arm cpu topology
V1.34 changelog
Some minor changes vs the previous kernel base.
I removed some things i didnt like.If you need them please ask for them.
-Fsync
-Ondemandplus
-Make sure you download the modules needed for new rebased kernel!
Nook On Fire Kernel :
V13.3 changelog:
- Finetuned newly introduced Governors for Omap4430 Cpu.
- Added SLQB low-level memory manager More info here
- I have disabled Fsync because it was causing major lags.
Anyone that want to use it it can enable it inside Trickster MOD Kernel Settings from Gplay.
V13.2 changelog:
- Added CPU governor: ondemandplus (more info here)
- Added CPU governor: pegasusq
* ondemandplus is an ondemand- and interactive-based governor that has additional power-saving capabilities while maintaining very snappy performance. (Is finetuned for omap4460 for now, i will fix that when i find more free time )
* pegasusq is an ondemand based governor with hotplugging (=disables the second CPU core when it is not needed). It even hotplugs after some seconds when the screen is on.
- Added ARM CPU topology: multi-core scheduling (enabled by default; saves battery by scheduling load among the CPU cores; more info here)
- Added Fsync and enabled it by default
fsync() transfers ("flushes") all modified in-core data of (i.e., modified buffer cache pages for) the file referred to by the file descriptor fd to the disk device (or other permanent storage device) so that all changed information can be retrieved even after the system crashed or was rebooted. This includes writing through or flushing a disk cache if present. The call blocks until the device reports that the transfer has completed. It also flushes metadata information associated with the file (see stat(2)).
Click to expand...
Click to collapse
- Some more tweaks for Speed
V12.1 changelog:
- Hardcoded Row frequencies by a research group of the xda community.
- Load frequency edits so we reach Gnex Kernel speed and responsiveness
- Tried to fix usb mounting freezes and usb cut outs.
- At This point i find the kernel enough stable and fast for any task you will need it to perform at.
V12 changelog:
- Kernel Updated to latest 3.0.xx(74)
- Updated Row I/O Sheduler to latest 2013 with all upstream fixes
V11 changelog:
- Major changes taken from francisco franco Tuna kernel aka Gnex
- Kernel major jump from 3.0.62 to 3.0.73!
- For wifi to work new modules compiled against kernel 3.0.73 needed and posted.
Notice:
From now on and if you are on same rom you only need to flash kernel, when you flash a new rom a modules package reflash is required or else wifi wont work.
V10 changelog:
- Wakelock changes taken from Samsung latest JB source code
- Suspend changes taken from Samsung latest JB source code
- Memory timings changes copied from B&N Nook HD source code.
V09 changelog:
- Boxer Lcd Panel at 59.1Mhz per datasheet with accompanied settings
- More compiler optimizations
V08 changelog:
- Use ARM Hardware Float instead of software. More info here: http://wiki.debian.org/ArmHardFloatPort/VfpComparison
- Use -O3 flags when compiling Gpu driver. ccflags-y += -O3 in drivers/gpu/makefile (Thanks Mnazim)
- Improoved page writeback tweaks
- Nook HD Panel Settings
- Epic Citadel force close fixed {61fps woot!}
V03 changelog:
- Nook HD source complete memory timings
- Cpu idle code tweaks
- Silicon Performance Enabled aka 1.2Ghz
You can find all releases :
Goo.im Link:
http://goo.im/devs/demetris/Acclaim/NookOnFire
Dev-host:
http://d-h.st/users/demetris/?fld_id=16788#files
Nook On Fire Showtime CWM/TWRP Links:
One Package flasher (Kernel+Modules) for V3.22 http://tinyw.in/bALo
One Package flasher (Kernel+Modules) for V3.21 http://tinyw.in/OFgN back Sorry
One Package flasher (Kernel+Modules) for V3.2 http://tinyw.in/uJfz
V3.2 Kernel Download Link: http://tinyw.in/xd7M
V3.2 Kernel Modules (required)!Download Link: http://tinyw.in/Mxoo
V3.11 Kernel Download Link: http://tinyw.in/5z0M
V3.11 Kernel Modules (required)!Download Link: http://tinyw.in/MBw0
Kernel
http://goo.im/devs/demetris/NookOnFire/NOF-Showtime-Kernel-V3.zip
Modules
http://goo.im/devs/demetris/NookOnFire/NOF-Showtime-Modules-V3.zip
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Nook On Fire Nemesis CWM/TWRP Links:
V2.4 Kernel Download Link: http://d-h.st/YEA
V2.4 Kernel Modules (required)!Download Link: http://d-h.st/sZa
V2.21 Kernel Download Link: http://d-h.st/G2S
V2.21 Kernel Modules (required)!Download Link: http://d-h.st/oOh
V2.11 Kernel Download Link: http://d-h.st/TMo
V2.11 Kernel Modules (required)!Download Link: http://d-h.st/6v4
V2.1 Kernel Download Link: http://d-h.st/ORM
V2.1 Kernel Modules (required)!Download Link: http://d-h.st/l3y
V1.73 Kernel Download Link: http://d-h.st/Dkf
V1.73 Kernel Modules (required)!Download Link: http://d-h.st/iWe
V1.72 Kernel Download Link:http://d-h.st/uCu
V1.72 Kernel Modules (required)!Download Link:http://d-h.st/aoj
V1.70 Kernel Download Link: http://d-h.st/agX
V1.70 Kernel Modules (required)!Download Link: http://d-h.st/flX
V1.66 Kernel Download Link: http://d-h.st/3pk
V1.66 Kernel Modules (required)!Download Link: http://d-h.st/W4y
V1.60 Kernel Download Link: http://d-h.st/X7K
V1.60 Kernel Modules (required)!Download Link: http://d-h.st/ayE
V1.52 Kernel Download Link: http://d-h.st/jiL
V1.52 Kernel Modules (required)!Download Link: http://d-h.st/IWe
V1.51 Kernel Download Link: http://d-h.st/Iz8
V1.51 Kernel Modules (required)!Download Link: http://d-h.st/LIH
V1.50 Kernel Download Link: http://d-h.st/G3m
V1.50 Kernel Modules (required)!Download Link:http://d-h.st/Fan
V1.42 Kernel Download Link: http://d-h.st/dVI
V1.42 Kernel Modules (required)!Download Link: http://d-h.st/Hvr
V1.35 Download Link:http://d-h.st/b9r
V1.34 Download Link:http://d-h.st/Z0D
V1.34 Kernel Modules (required)!Download Link: http://d-h.st/OrS
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Nook On Fire CWM/TWRP Links:
V13.3 Download Link: http://d-h.st/i7L
http://celticstorage.co.uk/cm10/NOF-Kernel-V13.2.zip
http://celticstorage.co.uk/cm10/NOF-Kernel-V12.1.zip
http://celticstorage.co.uk/cm10/NOF-Kernel-V12.zip
http://celticstorage.co.uk/cm10/NOF-Kernel-V11.zip
http://celticstorage.co.uk/cm10/NOF-Kernel-V10.zip
http://celticstorage.co.uk/cm10/NOF-Kernel-09.zip
http://celticstorage.co.uk/cm10/NOF-Kernel-08.zip
http://celticstorage.co.uk/cm10/NOF-Kernel-03.zip
Because of major kernel upgrade new modules needed also!
Modules for NOF V11 and UP!:
http://celticstorage.co.uk/cm10/3.0.xx_Modules.zip
Installation:
Copy zip archive to sdcard
Reboot to recovery
Select to install zip from sdcard
Navigate to archive
Flash and reboot.
Fastboot way:
Unzip archive, get boot.img out of it and,
Installation:
Enter fastboot mode from cyanoboot menu by holding N button and type:
Fastboot flash boot boot.img
Fastboot reboot
Profit.
Succulent Roms NOF Version Link:
http://celticstorage.co.uk/cm10/Succu-NOF.zip
Untested
Source:
https://github.com/Ntemis/kernel3NookTablet/tree/p-android-omap-3.0.y
Find Kernel sources here:
Nook On Fire Nemesis:
https://github.com/Ntemis/NOF-Nemesis
Nook On Fire:
https://github.com/Ntemis/NOF_kernel_bn_acclaim
If you find my work useful please press thanks button!
Credits to:
Kuzma30
chrmhoffmann
Hashcode
Mik_os
Rebellos
Mnazim
Fransisco Franco
Boype
Loosethisskin
Imoseyon
and all other developers who do not remember and whos code is now being used in our kernel.
Thank you very much.
{
"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"
}
thanks!
downloading now thanks for your contribution!:highfive:
What Is A Kernel?
Android (like many other Smartphone operating systems) runs on the Linux kernel. The Linux kernel was created in the early 1990’s by a gentleman named Linus Torvalds in Helsinki Finland. It’s incredibly stable, incredibly friendly, and incredibly difficult for the layman to understand and modify. Thankfully it’s also very popular so it has been ported on to a multitude of hardware, including our Android devices.
Think of the kernel as an interface layer between the hardware and software on your device. The kernel decides when things happen, such as the LED indicator gets lit. An application sends a request to the operating system to blink the LED. The operating system then sends the request to the kernel, which makes the light flash for the amount of time requested by the OS.
What sounds like a round-about way to get things done is also what makes the system so scalable and robust. Application developers only have to code in a way the operating system understands and the kernel makes it work on the hardware. This also keeps the application running in it’s own user-space and separate from the kernel. That means when you run the latest uber-cool app that wasn’t designed for your particular OS version, or is still very beta and it crashes, the kernel gives you the option to Force Close the application and the kernel can run untouched.
In a standard Android ROM (we will leave developer images and the like for another discussion) the kernel is bundled along with a set of instructions that tell the device how to load the kernel and the OS during boot. This is the boot.img that you see inside a zipped ROM that you're not able to easily open. The device knows to extract this image to internal memory (the ramdisk) and follow a series of scripts (init scripts) to load the kernel and then the other portions of the OS. That’s what’s happening while you’re watching the boot animation. Interestingly enough this is done the same way for a PC, your smartphone, an Android tablet, or even a smart Linux powered toaster. If you’re feeling exceptionally geeky, plug your Android phone into the USB port on your PC and let the PC boot from the USB device. No, it doesn’t actually load, but you can watch the animation while it tries to match up the hardware support with what’s inside your PC. As I said, Linux is amazingly scalable and as a result so is Android.
GOVERNORS
1) Ondemand:
Default governor in almost all stock kernels. One main goal of the ondemand governor is to switch to max frequency as soon as there is a CPU activity detected to ensure the responsiveness of the system. (You can change this behavior using smooth scaling parameters, refer Siyah tweaks at the end of 3rd post.) Effectively, it uses the CPU busy time as the answer to "how critical is performance right now" question. So Ondemand jumps to maximum frequency when CPU is busy and decreases the frequency gradually when CPU is less loaded/apporaching idle. Even though many of us consider this a reliable governor, it falls short on battery saving and performance on default settings. One potential reason for ondemand governor being not very power efficient is that the governor decide the next target frequency by instant requirement during sampling interval. The instant requirement can response quickly to workload change, but it does not usually reflect workload real CPU usage requirement in a small longer time and it possibly causes frequently change between highest and lowest frequency.
2) 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.
3) Conservative:
A slower Ondemand which scales up slowly to save battery. The conservative governor is based on the ondemand governor. It functions like the Ondemand governor by dynamically adjusting frequencies based on processor utilization. However, the conservative governor increases and decreases CPU speed more gradually. Simply put, this governor increases the frequency step by step on CPU load and jumps to lowest frequency on CPU idle. Conservative governor aims to dynamically adjust the CPU frequency to current utilization, without jumping to max frequency. The sampling_down_factor value acts as a negative multiplier of sampling_rate to reduce the frequency that the scheduler samples the CPU utilization. For example, if sampling_rate equal to 20,000 and sampling_down_factor is 2, the governor samples the CPU utilization every 40,000 microseconds.
4) Interactive:
Can be considered a faster ondemand. So more snappier, less battery. Interactive is designed for latency-sensitive, interactive workloads. Instead of sampling at every interval like ondemand, it determines how to scale up when CPU comes out of idle. The governor has the following advantages: 1) More consistent ramping, because existing governors do their CPU load sampling in a workqueue context, but interactive governor does this in a timer context, which gives more consistent CPU load sampling. 2) Higher priority for CPU frequency increase, thus giving the remaining tasks the CPU performance benefit, unlike existing governors which schedule ramp-up work to occur after your performance starved tasks have completed. Interactive It's an intelligent Ondemand because of stability optimizations. Why??
Sampling the CPU load every X ms (like Ondemand) can lead to under-powering the CPU for X ms, leading to dropped frames, stuttering UI, etc. Instead of sampling the CPU at a specified rate, the interactive governor will check whether to scale the CPU frequency up soon after coming out of idle. When the CPU comes out of idle, a timer is configured to fire within 1-2 ticks. If the CPU is very busy between exiting idle and when the timer fires, then we assume the CPU is underpowered and ramp to max frequency.
5) Interactivex:
This is an Interactive governor with a wake profile. More battery friendly than interactive.
6) Lulzactive:
This new find from Tegrak is based on Interactive & Smartass governors and is one of the favorites.
Old Version: 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.
New Version: Three more user configurable parameters: inc_cpu_load, pump_up_step, pump_down_step. Unlike older version, this one gives more control for the user. We can set the threshold at which governor decides to scale up/down. We can also set number of frequency steps to be skipped while polling up and down.
When workload greater than or equal to inc_cpu_load, governor scales CPU pump_up_step steps up. When workload is less than inc_cpu_load, governor scales CPU down pump_down_step steps down.
Example:
Consider
inc_cpu_load=70
pump_up_step=2
pump_down_step=1
If current frequency=200, Every up_sampling_time Us if cpu load >= 70%, cpu is scaled up 2 steps - to 800.
If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.
7) Lulzactiveq:
Lulzactiveq is a modified lulzactive governor authored by XDA member robertobsc and is adapted in Siyah kernel for GS2 and GS3. Lulzactiveq aims to optimize the second version of luzactive from Tegrak by a) providing an extra parameter (dec_cpu_load) to make scaling down more sensible, and b) incorporating hotplug logic to the governor. Luzactiveq is the first ever interactive based governor with hotplugging logic inbuilt (atleast the first of its kind for the exynos platform). When CPU comes out of idle loop and it's time to make a scaling decision, if load >= inc_cpu_load CPU is scaled up (like original luzactiveq) and if load <dec_cpu_load, CPU is scaled down. This possibly eliminates the strict single cut-off frequency for luzactiveq to make CPU scaling decisions. Also, stand hotplug logic runs as a separate thread with the governor so that external hotplugging logic is not required to control hotplug in and out (turn On and Off) CPU cores in multi core devices like GS2 or GS3. Only a multi core aware governor makes real sense on muti-core devices. Lulzactiveq and pegasusq aims to do that.
8) Smartass:
Result of Erasmux rewriting the complete code of interactive governor. Main goal is to optimize battery life without comprising performance. Still, not as battery friendly as smartassV2 since screen-on minimum frequency is greater than frequencies used during screen-off. Smartass would jump up to highest frequency too often as well.
9) SmartassV2:
Version 2 of the original smartass governor from Erasmux. Another favorite for many a people. The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.
10) Intellidemand:
Intellidemand aka Intelligent Ondemand from Faux is yet another governor that's based on ondemand. Unlike what some users believe, this governor is not the replacement for OC Daemon (Having different governors for sleep and awake). The original intellidemand behaves differently according to GPU usage. When GPU is really busy (gaming, maps, benchmarking, etc) intellidemand behaves like ondemand. When GPU is 'idling' (or moderately busy), intellidemand limits max frequency to a step depending on frequencies available in your device/kernel for saving battery. This is called browsing mode. We can see some 'traces' of interactive governor here. Frequency scale-up decision is made based on idling time of CPU. Lower idling time (<20%) causes CPU to scale-up from current frequency. Frequency scale-down happens at steps=5% of max frequency. (This parameter is tunable only in conservative, among the popular governors )
To sum up, 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.
11) Lazy:
This governor from Ezekeel is basically an ondemand with an additional parameter min_time_state to specify the minimum time CPU stays on a frequency before scaling up/down. 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.
12) Lagfree:
Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.
13) Lionheart:
Lionheart is a conservative-based governor which is based on samsung's update3 source. Tweaks comes from 1) Knzo 2) Morfic. The original idea comes from Netarchy. See here. 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.
14) LionheartX
LionheartX is based on Lionheart but has a few changes on the tunables and features a suspend profile based on Smartass governor.
15) Brazilianwax:
Similar to smartassV2. More aggressive ramping, so more performance, less battery.
16) SavagedZen:
Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.
17) Userspace:
Instead of automatically determining frequencies, lets user set frequencies.
18) Powersave:
Locks max frequency to min frequency. Can not be used as a screen-on or even screen-off (if scaling min frequency is too low).
19) Performance:
Sets min frequency as max frequency. Use this while benchmarking!
So, Governors can be categorized into 3/4 on a high level:
1.a) Ondemand Based:
Works on "ramp-up on high load" principle. CPU busy-time is taken into consideration for scaling decisions. Members: Ondemand, OndemandX, Intellidemand, Lazy, Lagfree.
1.b) Conservative Based:
Members: Conservative, Lionheart, LionheartX
2) Interactive Based:
Works on "make scaling decision when CPU comes out of idle-loop" principle. Members: Interactive, InteractiveX, Lulzactive, Luzactiveq, Smartass, SmartassV2, Brazilianwax, SavagedZen.
3) Weird Category:
Members: Userspace, Powersave, Performance.
Hi
When should this be flashed? Anytime? Immediately after the rom?
Thanks for your continuous work!
Sent from my NookTablet using xda app-developers app
Hi,
Yes should be flashed after the rom.
What gov are you recommending for this. It sure flies at 1200. Nice and smooth.
Don't like me...... BITE ME!!!
Too soon to tell, am updating Row and i am adding Smartass2 pegasusQ interactiveX soon.
I updated Lcd with Nook HD configs and it rocks, amazing clarity and performance.
Stay tuned
demetris_I said:
Too soon to tell, am updating Row and i am adding Smartass2 pegasusQ interactiveX soon.
I updated Lcd with Nook HD configs and it rocks, amazing clarity and performance.
Stay tuned
Click to expand...
Click to collapse
Sounds nice. Guess I'll use interactive for now. I'll let you know how it goes. If you ever need a tester for anything I am more than willing any time. Thanks for the work on this device.
Don't like me...... BITE ME!!!
Nice job. For completeness can you post a link to source? Might be there-- I did a quick search and didn't see it. Any point to adding the BFQ io scheduler? Or is that in the stock kernel, I cant' remember.
Hi demetris_I:
Is this kernel in any way related to kuzma30's kernel work?
@kur41
You have any other kernel in mind that can boot on Nook Tablet? :silly:
@fattire
BFQ io scheduler is already implemented
Hi. Thanks for your answer.
Do I really need to format the sdcard onto exfat? Didn't get it.. :/
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
LacerdaPT said:
Hi. Thanks for your answer.
Do I really need to format the sdcard onto exfat? Didn't get it.. :/
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
Nope.
Only if you need exfat filesystem support example files bigger than 4gb onto sd card.
New kernel released,
Flash, test, and report back.
Thanks
Edit:
Source changes pushed to git
YES!!! 1200mhz! Thank you!
Sooo far sooo good on CM10.1
Don't suppose 1300 or 1400 could be added for us to try on our devices. Or just mine... Screw them! I want it!
Thanks again for all your hard work! I REALLY appreciate it!
Merrell
Sent from my Barnes & Noble Nook Tablet using Tapatalk 2
Quick question -- will this kernel work with your Nooked CM10.1 (Succulent based) ROM? I've been running that for four or five days and loving it -- my Nook Tablet has never felt as quick and smooth. Thanks very much for all the great work you're doing.
paulbonner said:
Quick question -- will this kernel work with your Nooked CM10.1 (Succulent based) ROM? I've been running that for four or five days and loving it -- my Nook Tablet has never felt as quick and smooth. Thanks very much for all the great work you're doing.
Click to expand...
Click to collapse
Here is what you can do,
get this v08.zip package and the 3rd edition rom
copy the v08.zip once more in a folder and rename it to backup.zip
get boot.img from 3rd edition rom and replaced the boot.img in backup.zip
tranfer both into sd card and reboot to recovery.
flash v08 and reboot.
If it works your golden if not press power key to shutdown device and give another retry
If it fails again go flash backup.zip and report here that it doesnt work, so other know and you save them precious time doing the same.
demetris_I said:
Here is what you can do,
get this v08.zip package and the 3rd edition rom
copy the v08.zip once more in a folder and rename it to backup.zip
get boot.img from 3rd edition rom and replaced the boot.img in backup.zip
tranfer both into sd card and reboot to recovery.
flash v08 and reboot.
If it works your golden if not press power key to shutdown device and give another retry
If it fails again go flash backup.zip and report here that it doesnt work, so other know and you save them precious time doing the same.
Click to expand...
Click to collapse
Unfortunately this kernel won't work with that ROM. Just tried it, will not boot.
razzbaronz said:
Unfortunately this kernel won't work with that ROM. Just tried it, will not boot.
Click to expand...
Click to collapse
Yep, same for me
Sent from my SGH-T959V using xda app-developers app
Added Succulent kernel with NOF changes
Enjoy
P.s
Untested
Source:
https://github.com/Ntemis/kernel3NookTablet/tree/p-android-omap-3.0.y
I just flashed Beans ROM Build 4 and this thing is great. I also decided to flash the Faux kernel that he included in the Add-ons and I was wondering what are the best/recommended settings in the Faux123 Kernel Enhancement app. I'm new to this app as I've been using KTweaker for my KToonz kernel. Anyone have any suggestions?
Iskateforfree said:
I just flashed Beans ROM Build 4 and this thing is great. I also decided to flash the Faux kernel that he included in the Add-ons and I was wondering what are the best/recommended settings in the Faux123 Kernel Enhancement app. I'm new to this app as I've been using KTweaker for my KToonz kernel. Anyone have any suggestions?
Click to expand...
Click to collapse
This is from Faux123 himself:
FauxClock App recommended Settings"
CPU Control
Max clock - GHz 2.1 GHz for performance, 1.7 GHz for battery
Min clock - MHz 162 MHz for both
CPU Governor - Ondemand for performance, Intellidemand for battery
mpdecision - Off
Snake Charmer - OFF for performance, On for Battery
Eco Mode - Off for performance, On for battery
Set On Boot - On
SOC Control
Set On Boot - On
C0 - On
C1 - On
C2 - On
Voltage Control
Set On Boot -
Global CPU Voltage - Your preference
intellidemand gov control
Up Threshold - 75 for both
Boost Frequency - 0 for both
Two Phase Freq - 1350000 for both
Sampling Rate - 50000 for both
Optimal Freq - 1566000 for both
Synchro Freq - 702000 for both
Set On Boot - On
GPU Control
GPU Governor - ondemand for both
GPU Clock - 487Mhz for performance and 320 Mhz for battery
GPU Vsync Toggle - On for both
Set On Boot - On for both
I/O Scheduler Control
I/O Scheduler (eMMC) - FIOPS for both
Readhead Size (eMMC) - 1024 for both
Set On Boot - On for both
Misc Control
Dynamic File Sync - On for both
TCP Congestion Control - Westwood for both
Vibration Control
Set On Boot - On for both
Vibration Control - Your own Preference
Above is what I use personally. MAY NOT be optimal for all
Click to expand...
Click to collapse
Thanks a lot man!
Iskateforfree said:
Thanks a lot man!
Click to expand...
Click to collapse
no problem! Use the thanks button below my name!
Hey I'm having some trouble with the Beans ROM Custom settings. I'm running Build 4 and when I go into the custom settings to make the status bar transparent, it switched to to transparent but then when I lock and unlock the phone, it's back to being solid black. I've even changed it to transparent then rebooting so changes could take affect and still no change. Any suggestions?
{
"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.
Be Sure ! If you benefit to the other's you will see it's effect.
Imam Ali
LG G3_D850/1/2/5 - VS985 STOCK KERNEL
Gabriel-5
LOLLIPOP 5.0
BORN TO BE SMOOTHER AND SAVE MORE BATTERY
THIS WASN'T POSSIBLE WITHOUT @nikhil18 & @ZaneZam KIND ANSWERS
AND @airlessproject PATCHES AND @dorimanx
all credits goes to
@nikhil18, @airlessproject @ZaneZam @Tectas @faux123 @HolyAngel
and all friends in XDA have shared their knowledge
and i'm not a developer, just did for hobby
>> my git is here <<
Special Thanks to my Teammates
@BuLLeT_93 & @horsetastic
FLASH AT YOUR OWN RISK !!
CURRENT VERSION : Gabriel-0.8.3
Main Download Folder-MEGA
0.8.3 ( 21.12.15)
*Power suspend removed
*State notifier added (thx to neobuddy), mods were changed to work with S-notifier
*Hotplugs were updated to latest Dev's changes and working with S-notifier
*Cpufreq limiter updated to v 5.1
*Cputime updated
*Cpufreq were updated to latest Dev's change
Now it looks smoother with same kernel config :good:
0.8.2 ( 20.12.15)
*Initial Nitro version boot fail fixed
0.8.2 ( 12.11.15)
* Linux Kernel Version 3.4.110
* Bunch of Debug options were Removed, This will save CPU Cycle
* zzmoove updated to 1 beta 8
* zzmoove Thermal control is activated ( you can control it as well in cpufreq parameters, eg choose game profile and see its options . It will reduce CPU clock when reach Target Temp )
* zzmoove Native Hotplug : disable other hotplug driver and turn it on and vice versa
* Hotplugs and Cpu Governors were Updated
* Power suspend 1.7
* KCal were Updated
* Compiled with updated UBERTC 5.2.x
* Available in 2 version : "Default ( battery )" have stock parameters while "Nitro" is Tuned for Better Performance ( It's boosted version of Default or Battery version thus it can eat more battery and it's initial Nitro Release thus some parameters should be tune More )
Change-log Gabriel-Tastic 290715
Change-log 0.8.1-b 060815
Change-log 0.8.1-d 080815
UKM (synapse) mod by BuLLeT_93 - 120815
Synapse + UKM Package
send me your log if you got
any problems,see this instruction
for getting the log
Battery tips&tricks
This post will update with your informations and experiences about battery saving
[MOD] LCD TWEAKS (FPS - RESOLUTION) for Better Battery Life
[MOD] Lower AutoBrightness Values
[GUIDE] 'AUTOBOTS' Kernel Settings [Gabriel kernel] [Battery Life]
MODEM
The modem act as the Software bridge between the RIL driver and your phones Hardware (correct me if i am wrong)
Because of that you can directly (more or less) control how your phone signal is behaving by trying different Modems till you find one that suits your needs.
The modem images does have an impact on wifi, mobile networks and how fast they are able to scale up or down, battery runtime, as well as call quality sometimes.
While the g3 got a good signal most of the time the changes might not be this big, compared to other phones and their modem differences, but it is still a good thing to know you got the best reception possible
For me the 20A and 20p Modems are working better then the most others... But there will be people with other carriers etc for whose another might be the right!
@empulse92 said
here is his great MODEM collection
ZZMOOVE Profile Numbers
currently available profiles by ZaneZam and Yank555
------------------------------------------------------------------------------------------------------------------------------------------
(1)'def'-> Default -> will set governor defaults
------------------------------------------------------------------------------------------------------------------------------------------
(2)'ybat'-> Yank Battery -> a very good battery/performance balanced setting DEV-NOTE: highly recommended! ------------------------------------------------------------------------------------------------------------------------------------------
(3)'ybatext'-> Yank Battery Extreme -> like yank battery but focus on battery saving ------------------------------------------------------------------------------------------------------------------------------------------
(4)'zzbat'-> ZaneZam Battery -> a more 'harsh' setting strictly focused on battery saving DEV-NOTE: might give some lags! ------------------------------------------------------------------------------------------------------------------------------------------
(5)'zzbatp'-> ZaneZam Battery Plus -> NEW! reworked 'faster' battery setting DEV-NOTE: recommended too! ------------------------------------------------------------------------------------------------------------------------------------------
(6)'zzopt'-> ZaneZam Optimized -> balanced setting with no focus in any direction DEV-NOTE: relict from back in the days, even though some people still like it!
------------------------------------------------------------------------------------------------------------------------------------------
(7)'zzmod'-> ZaneZam Moderate -> NEW! setting based on 'zzopt' which has mainly (but not strictly only!) 2 cores online ------------------------------------------------------------------------------------------------------------------------------------------
(8)'zzperf'-> ZaneZam Performance -> all you can get from zzmoove in terms of performance but still has the fast down scaling/hotplugging behaving ------------------------------------------------------------------------------------------------------------------------------------------
(9)'zzinz'-> ZaneZam InZane -> NEW! based on performance with new insane scaling active. a new experience! ------------------------------------------------------------------------------------------------------------------------------------------
(10)'zzgame'-> ZaneZam Gaming -> NEW! based on performance with scaling block enabled to avoid cpu overheating during gameplay ------------------------------------------------------------------------------------------------------------------------------------------
(11)'zzrelax'-> ZaneZam Relax -> NEW! based on moderate (except hotplug settings) with relaxed sleep settings
For change zzmoove profiles
use this tut
thanks to @chacho_2me
Bullet_93 config
CPU
Max frequency 2457
Min frequency 268
Gov Lionheart with:
UP TRESHOLD 80
DOWN THRESHOLD 75
FREQ STEP 5
SAMPLING RATE 20000
Sync frequency 1190
CPU HOTPLUG
Mp Decision OFF
Intelliplug ON Balanced Profile
Histerysis 12
THERMAL
Control core and VDD Restricion both ON
GPU
Simple_ondemand Governor
Max frequency 389mhz
IO SCHEDULER
Tripndroid
Read Ahead 4096kb
VIRTUAL MEMORY
Dirty Ratio 10
Dirty Background Ratio 5
Dirty Expire 1000
Dirty Writeback 3000
Min free 4096
Overcommit ratio 50
Swappiness 70
Vfs_cache_pressure 50
Zram 600mb
Kcal config :
Saturation 38
Screen Hue 24
Value 128
Contrast 138
horsetastic bubmlemee v2
zzmoove profile number 5
Profile 5 tweaks;
Down threshold 80
Sleep down threshold 80
Freq limit sleep 268mhz
Sampling rate 100000
Smooth up 70
Up threshold 85
cpu max 2265mhz
cpu min 268mhz
multicore power saving disabled
input boost frequency 1267mhz
cpu voltage -25
mpdecision off
intelliplug on conservative
touch boost off
cpu max screen off frequency 268mhz
thermal control intellithermal
gpu msm-adreno-tz
gpu max 578mhz
i/o scheduler fiops
read ahead 2048
low memory killer very aggressive
Virtual memory zram to 0
TCP congestion algorithm westwood
Horestastic Bumblebee V3
CPU
Max Freq - 1958mhz
Min Freq - 268mhz
Governor - zzmoove (Profile Number 5 zzbatp)
Governor Tunables Changes;-
freq_limit_sleep 268mhz
sampling rate 100000 or 80000 if laggy
smooth up 75
smooth up sleep 100
up threshold 85
up threshold sleep 100
Multicore Power Saving - Disabled
CPU Boost Interval - 10ms
Sync Threshold - 1190mhz
Input Boost Freq - 1267mhz
CPU Voltage - Global -60
CPU Hotplug Either stock zzmove hotplug with both disabled or Intelliplug (both are great)
Balanced Profile
Touch Boost - Disabled (Enable if laggy)
Hysteresis Value - 12
Threshold Value - 722
CPU Max Screen Off Freq - 268mhz
Thermal - Core Control & VDD Restriction Enabled - All stock values
GPU Governor - Simple ondemand
Max Freq - 578mhz
Laziness - 5
Ramp Threshold - 4
I/O Scheduler - fiops
Read ahead - 2048
Low memory Killer - Very aggressive
Virtual Memory
dirt ratio - 10
dirty background ratio - 5
dirty expire centisecs - 1000
dirty writeback centisecs - 3000
min free kbytes - 4096
overcommit ratio - 50
swappiness - 30
vfs cache pressure - 50
laptop mode - 0
ZRAM - 200 (but this is personal choice really)
TCP Congestion Algorithm - Westwood (Or Cubic if desired)
Looks interesting...
Do you plan on making versions for the other variants? Like my D851
leald said:
Do you plan on making versions for the other variants? Like my D851
Click to expand...
Click to collapse
yea,i've an exam in next 2 week,i'll working on it
mostafaz said:
yea,i've an exam in next 2 week,i'll working on it
Click to expand...
Click to collapse
Looks promising...please work on sound quality also
Off topic:
Don't you have konkur?
cause i have...in 2 weeks
Wish you the best
reza1995live said:
Looks promising...please work on sound quality also
Off topic:
Don't you have konkur?
cause i have...in 2 weeks
Wish you the best
Click to expand...
Click to collapse
yea -wish ya luck
actually other kernels have faux sound and it's good enough, but i want do something different and add other sound engine,but in next releases
mostafaz said:
yea -wish ya luck
actually other kernels have faux sound and it's good enough, but i want do something different and add other sound engine,but in next releases
Click to expand...
Click to collapse
Don't worry I'm sure we all can wait...focus on your exam cause I know how important that is.
nice )
i like the 268mhz cpu step and gpu 27idle.
i missed that when i switched phones from oneplus to lg g3. thanks for the kernel will install.
i guess i can just flash it over my chupachups kernel?
What governors are in this Kernel?
Does not work with 20p, it restarts the phone all the time.
horsetastic said:
What governors are in this Kernel?
Click to expand...
Click to collapse
Smartmax, Smartmax-eps (extreme power saving), conservative (up/down treshold added), interactive(patched)
and other stock govs
No worry about the governors. I flashed it haha. Working nicely with cloudy 2.2 so far. Not been long of course. Any recommended settings for battery life?
I'm set on Fiops, 2048 read ahead, smartmax eps, 300000 Max off screen, 2.5ghz Max clock, simple on demand GPU, under clocked to 330. And some other bits I think.
Derpling said:
Does not work with 20p, it restarts the phone all the time.
Click to expand...
Click to collapse
thx for reporting
do you have d855 variants?which rom?
i got reset issue while trying to add cpu over clock feature,but now its ok,maybe i should reduce oc values
horsetastic said:
No worry about the governors. I flashed it haha. Working nicely with cloudy 2.2 so far. Not been long of course. Any recommended settings for battery life?
I'm set on Fiops, 2048 read ahead, smartmax eps, 300000 Max off screen, 2.5ghz Max clock, simple on demand GPU, under clocked to 330. And some other bits I think.
Click to expand...
Click to collapse
good
try change tcp cong to cube if u loose more power on wifi or data,but its good with that.
i will update 2nd post with batt tips,with info users will tell me,thx
OK great thanks. Any plans to add more governors? More battery saving options the better haha. Phone is a battery beast.
5 days before we didnt have any kernel dev now we have two....thanks for the kernel...also if you can post your kernel to a more known and "better" site than this arabic something site with slow speed!!!it could be great!!!thanks!
horsetastic said:
OK great thanks. Any plans to add more governors? More battery saving options the better haha. Phone is a battery beast.
Click to expand...
Click to collapse
yea,i will-but first must be sure that not buggy and works fine the release
also you can tune governor, got 5 hrs sot,50% brightness,camera,some call and text surfing the net and g+(cubic tcp)-max scr 960-260~2500 cpu-27~578 gpu-io sched 512 rowzram off-hot plug 1 -1 ,uv 25
give it a try
Weirdly the smartmax and smartmax eps governors don't seem to be very battery friendly lol.
On engines kernel Lionheart was good when on paper it shouldnt really be but Wheatley and DanceDance were bad when they should of been good. I don't get it?
Introduction
This is a kernel for XT1572/XT1575 built from stock sources (marshmallow-6.0.0-release branch) with cherry picks from other kernels and some ports/mods done by me. It started as a personal build tailored to my preferences but just thought I'd share in case somebody might find it useful. My main goal is building the smoothest kernel I can get so performance is top priority.
This kernel is for stock ROM MPH24.49-18*
Disclaimer
Although I have experience with Linux kernels on desktops and servers this is my first Android kernel. I've been running this kernel on my XT1572 for a few days and seems pretty stable but that doesn't mean it's risk free. In fact I wouldn't dare to install it if you don't have a proper backup and some basic skills to deal with unexpected situations.
Features
Aroma Installer
CPU profile scripts (see this)
Color control (KCAL)
Frandom
Updated to kernel version 3.10.101
Overclocking (a53: 1536MHz a57:2016MHz)
Underclocking (302MHz)
Additional CPU governors (ElementalX, Intelliactive, Lionheart, BioShock, BluActive, Wheatley, InteractiveX/Interactive, Impulse, Zzmoove)
Additional I/O schedulers (SIO, FIOPS, Zen, BFQ, SIOPLUS)
Bricked Hotplug
Updated ZRAM driver
Updated Lowmemorykill driver
Basic init.d support
KSM and UKSM
Voltage readings
Fsync on/off
Touchboost on/off
Vibration control
KEXEC Hardboot (MultiROM support)
Patched cdrom code (DriveDroid support)
DoubleTap2Wake/Sweep2Wake/Sweep2Sleep (EXPERIMENTAL)
Power efficient workqueues
Support for additional FS: NTFS, NFS, CIFS
Additional Xpad drivers (read this)
Device as USB trackpad/keyboard driver (read this)
WiFi module optimizations
Many minor optimizations
Optimization flags
UBER Toolchain 4.9
Installation instructions
Download ZIP and flash from TWRP/Flashify. Read the following notes carefully before flashing.
Important notes:
This kernel is still experimental, make a proper backup first
You need to be rooted
DO NOT play with DT2W/S2W before reading the release notes and the update
In case you want to tune some parameters (ie: CPU frecuencies) I recommend you install EX Kernel Manager, Kernel Adiutor or Kernel Adiutor-Mod.
If you're using Kernel Adiutor to control vibration or TCP congestion read this.
Questions? Read the FAQ before posting.
Download
Latest version is v0.14 (see release notes)
https://www.androidfilehost.com/?w=files&flid=49225
Donations
Although quite a deal of the important work has been done by the developers mentioned in the Credits section I spend many hours working on this. If you feel like helping me out I'd appreciate some tiny donations to cover some minor expenses.
Thanks to all of you who have donated, it's very much appreciated.
Profiles
One of the FAQ in most kernel related threads is "What are the best settings for .....?". This is the 10 million question since the usage pattern can be very different for each user. However, I understand less experienced users will appreciate some hints in this department, so that's why I'm posting some basic settings you can use as a starting point.
It's your job to further tune them to suit your needs. You should be able to modify these settings with whatever Kernel Control App you like the best, although not all settings are available in every app, in such a case tune those you can. The list is not complete (just the most importante settings) and is loosely based on Kernel Adiutor arrangement.
Please, keep in mind these are subjective values (based of personal preferences or popularity) and some people might like other settings for whatever reasons.
Performance Profile: Very smooth and responsive but average battery life
CPU
LITTLE Cluster
CPU Governor: bluactive
CPU Max Frequency: 1536MHz
CPU Min Frequency: 302MHzBIG Cluster
CPU Governor: bluactive
CPU Max Frequency: 2016MHz
CPU Min Frequency: 302MHz
NOTE: If you get N/A or weird values when trying to change settings on BIG cores it means both have been hotunplugged. To work around this select "performance" governor, make your desired changes and then select you previous governor.CPU Boost
Input Boost Frequency Core 1: 960MHz
Hotplug
MSM MPDecision
Minimum CPU online: 2
Maximum CPU online: 6
Max Cores Screen Off: 2
Idle Frequency: 384MHz
Thermal
Core Control: Off
VDD Restriction: Off
Temperature Throttle: On
GPU
Max Frequency: 600MHz
Min Frequency: 180MHz
Govenor: cpufreq
I/O
Scheduler: noop
Read-ahead: 1024KB
Balanced Profile: Above average battery life with good performance on most situations
CPU
LITTLE Cluster
CPU Governor: interactive
CPU Max Frequency: 1440MHz
CPU Min Frequency: 302MHzBIG Cluster
CPU Governor: interactive
CPU Max Frequency: 1632MHz
CPU Min Frequency: 302MHz
NOTE: If you get N/A or weird values when trying to change settings on BIG cores it means both have been hotunplugged. To work around this select "performance" governor, make your desired changes and then select you previous governor.CPU Boost
Input Boost Frequency Core 1: 960MHz
Hotplug
MSM MPDecision
Minimum CPU online: 2
Maximum CPU online: 5
Max Cores Screen Off: 2
Idle Frequency: 768MHz
Thermal
Core Control: Off
VDD Restriction: Off
Temperature Throttle: On
GPU
Max Frequency: 600MHz
Min Frequency: 180MHz
Govenor: msm-adreno-tz
I/O
Scheduler: noop
Read-ahead: 1024KB
Battery Profile: Good battery life at the expense of somewhat limited performance
CPU
LITTLE Cluster
CPU Governor: ondemand
CPU Max Frequency: 1440MHz
CPU Min Frequency: 302MHzBIG Cluster
CPU Governor: ondemand
CPU Max Frequency: 1632MHz
CPU Min Frequency: 302MHz
NOTE: If you get N/A or weird values when trying to change settings on BIG cores it means both have been hotunplugged. To work around this select "performance" governor, make your desired changes and then select you previous governor.CPU Boost
Input Boost Frequency Core 1: 960MHz
Hotplug
MSM MPDecision
Minimum CPU online: 1
Maximum CPU online: 3
Max Cores Screen Off: 2
Idle Frequency: 960MHz
Thermal
Core Control: Off
VDD Restriction: Off
Temperature Throttle: On
GPU
Max Frequency: 450MHz
Min Frequency: 180MHz
Govenor: simple_ondemand
I/O
Scheduler: noop
Read-ahead: 1024KB
Thanks To/Credits
vadimtk
flar2
franciscofranco
nimrodsv
anarkia1976
savoca
myfluxi
AudioGod
osm0sis
nychitman1
jollaman999
imoseyon
showp1984
HashBang173
neobuddy89
rehpyc
Alcolawl
soniCron
Spasticdroid
XDA:DevDB Information
Frankenclark, Kernel for the Moto X Style (Pure)
Contributors
dirtyhank
Source Code: https://github.com/dirty-hank/frankenclark/
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 0.14
Created 2016-01-10
Last Updated 2016-10-11
Changelog
v0.14 (2016-08-29)
Proper KCAL control (thanks to @Spasticdroid)
Updated xpad driver for compatibility with gamepads/controllers (thanks to @Spasticdroid)
Driver to use device as USB trackpad and keyboard (thanks to @Spasticdroid)
Misc minor updates (see github)
100Hz version uses stock compiler flags
v0.13 (2016-06-21)
Update to Linux Kernel 3.10.102
Misc minor updates (see github)
New start-up CPU governor profiles: bluactive, maddog and silverfish
v0.12 (2016-05-15)
Disable DT2W/S2W while phone call is in progress
New CPU governors: impulse, zzmoove
New and updated CPU profile scripts
Runtime CPU profile switcher script (see release notes)
Minor changes to Aroma installer
v0.11.1 (2016-05-01)
Aroma Installer update (see release notes)
v0.11 (2016-04-27)
Aroma Installer
Better camera focus
Less CPU usage from DT2W/S2W
Minor updates and bugfixes
v0.10 (2016-04-03)
Updated lowmemorykiller driver
BFQ and SIOPLUS I/O schedulers
Updated ZRAM driver (on by default)
User togglable WLAN wakelocks
Basic init.d support (see release notes)
Misc minor updates
v0.9 (2016-03-20)
Update to Linux Kernel 3.10.101
Bug fixes
Changes from Google update to N5X and N6P (see release notes)
v0.8 (2016-03-06)
Update to Linux Kernel 3.10.99
Power efficient workqueues
NTFS support
NFS and CIFS support (you'll probably need additional user space binaries)
v0.7.1 (2016-02-28)
Workaround for the dimmed screen upon unlock bug when DT2W/S2W is enabled
v0.7 (2016-02-21)
Hotplug thresholds tuned to keep BIG cores offline more often
KEXEC Hardboot (MultiROM support)
Patched cdrom code (full DriveDroid support)
DoubleTap2Wake/Sweep2Wake/Sweep2Sleep (HIGHLY EXPERIMENTAL, Read this)
v0.6 (2016-02-07)
Vibration control (non-haptic)
Relaxed CPU macros for better power usage
File hosting now on AndroidFileHost
v0.5.2 (2016-02-03)
Fixed USB and WiFi Tethering
Minor tweaks
v0.5.1 (2016-02-01)
Changes to installer
v0.5 (2016-01-31)
Update to Linux Kernel 3.10.95
InteractiveX governor (as patches to the interactive gov)
Bricked Hotplug
KSM and UKSM (disabled by default, use Kernel Adiutor to enable)
Many minor optimizations
WiFi module optimizations
Modules recompilation
Disabled core_ctl (due to broken module after some internal changes to kernel)
Voltage readings (any attempt to modify values is silently ignored)
v0.4.1 (2016-01-24)
Prevent msm_performance from messing with the user selected min/max CPU frequencies
v0.4 (2016-01-23)
New CPU governors (ElementalX, Intelliactive, Lionheart, BioShock, BluActive, Wheatley)
New I/O scheduler (Zen)
Default I/O scheduler set to noop with a read ahead of 1024kb
Fixed bug CVE-2016-0728
Minor optimizations
Introduce ZIP installer (Anykernel2)
v0.3 (2016-01-18)
Color control (KCAL)
frandom support
New optimization flags
ZRAM disabled by default
v0.2 (2016-01-14)
Updated to Linux kernel 3.10.94
Underclocking (302MHz)
v0.1 (2016-01-10)
First public version
FAQ
I get random reboots, what is happening?
This kernel overclocks both clusters by default (a53: 1536MHz a57:2016MHz) and although this is very safe for most devices some CPUs are in the lowest spot of the binning spectrum and can't handle O/C very well. In such a case use a kernel control app (see the OP for references) to limit the maximum CPU frequencies, play with them until you find stable values for your device.
What are the best settings for battery life/performance/whatever?
That's hard to tell as every user is different. You can find some basic profiles in the OP you can use as a starting point. Notice the differences between then and build you own.
Why do some BIG cluster settings display N/A?
Why can't I change some settings on the BIG cluster?
If you get N/A or weird values when trying to change settings on BIG cores it means both are offline ("hotunplugged"). To work around this select "performance" governor, make your desired changes and then select you previous governor. You can also disable hotplug, make the changes, and enable hotplug again.
DoubleTap2Wake doesn't work sometimes. How can I get it to work all the time?
When device goes into suspend mode first tap is often missed (I suspect this is caused by Moto Sensor Hub). If you tap three times and get the timing right you'll probably make it work most of the time. As an alternative, Sweep2Wake works almost all the time
DT2W/S2W is acting weird or disabling itself
Make sure Moto Display is disabled. Open the Moto app, click on the stars in the top right corner, select Display and set to Off
Can I use this kernel in ROM X/Y/Z?
This is for stock ROM MPH24.49-18 only. It'll probably work on any stock based ROM but not guaranteed.
I use stock ROM but WiFi is not working
Due to some internal changes all modules had to be recompiled (WiFi included). In order to expose the new modules without modifying the system partition I had to implement a hack that requires root. Make sure you're properly rooted.
What's the deal with ZRAM?
ZRAM is a technique to increase memory available to the apps at the expense of CPU time. Memory space from apps not being used is compressed into a memory swap area and uncompressed on the fly whenever needed. As you can imagine this compress/uncompress process burns CPU cycles, potentially leading to worse battery life, lag and higher temperatures. Since this device comes with 3GB I can only think of one scenario where ZRAM can be beneficial: heavy multitaskers who care more about apps not reloading than battery life. For the rest of users enabling ZRAM doesn't make much sense in my opinion, and that's why it's disabled by default.
UPDATE: v0.10 includes an updated ZRAM driver that improves performance significantly. So much so that the benefits seem to outweigh the costs and it's been enabled by default.
What's the deal with KSM/UKSM?
Since many apps use the same libraries/resources it's very likely that at any given time there are multiple copies of the same data on different memory locations. KSM/UKSM tries to take advantage of that fact by scanning memory pages periodically and consolidating that multiple copies into a single shared copy. Much as like ZRAM it can have a good effect on heavy multitasking performance but at the expense of CPU cycles, and thus it's only recommended in the same scenario as ZRAM. Disabled by default
Ok, so do I enable ZRAM/KSM/both/neither?
I honestly think most users will be better off not using neither. If you feel like you need extra RAM I'd try KSM first, then ZRAM. Using both at the same time is overkill unless you are an ultra multitasker, in which case you should probably get a 4GB device anyway
How do I get WiFi on 6.0.1?
It's a modem version mismatch issue, you need to downgrade the modem. See this post.
Love to see more options! Thanks for sharing!!
Yeah this will be very good
Only One think that would be awesome try to implement the double tap to wake
Awesome! More custom kernels are always welcome are there many governors to choose from?
krohme said:
Awesome! More custom kernels are always welcome are there many governors to choose from?
Click to expand...
Click to collapse
Right now only the stock governors are available but I plan on adding a few
Can't we install it through twrp???
guraki said:
Can't we install it through twrp???
Click to expand...
Click to collapse
Yes, TWRP supports boot image flashing
I lost root after the kernel install....
---------- Post added at 03:22 PM ---------- Previous post was at 02:39 PM ----------
Seems to work fine!!! Any battery life expectations?
guraki said:
I lost root after the kernel install....
---------- Post added at 03:22 PM ---------- Previous post was at 02:39 PM ----------
Seems to work fine!!! Any battery life expectations?
Click to expand...
Click to collapse
As I said on the OP my main goal is performance/smoothness, so I haven't specifically sought better battery life. That being said I'm getting about the same battery life as stock with better performance, that works for me.
Nevertheless, I'm very interested on how it works for other configurations and usage patterns.
@dirtyhank could you please add hotplugging to the kernel? Preferably one that allows you to select how many cores to run as well as which ones, as in run the two A57s and turn off the four A53s. Currently I'm running two A53s at 1.2Ghz and the remaining four cores are always off.
The screenshot is from Lolipop, and it is the only reason why I havent upgraded to MM. Turning off cores definitely makes a difference on battery life.
Also, if possible, adding a lower speed to the min speed. Will gladly test anything you thow my way. Thanks in advance.
Is there any chance for a CM13 version and a DT2W fork from elementalx?
sir-harlekin said:
Is there any chance for a CM13 version and a DT2W fork from elementalx?
Click to expand...
Click to collapse
DT2W maybe, CM13 unlikely.
very nice thank you! slowly slowly we getting more and more things. Just making sure this is only for stock based rom/s Thanks!!
cerobles1 said:
@dirtyhank could you please add hotplugging to the kernel? Preferably one that allows you to select how many cores to run as well as which ones, as in run the two A57s and turn off the four A53s. Currently I'm running two A53s at 1.2Ghz and the remaining four cores are always off.
The screenshot is from Lolipop, and it is the only reason why I havent upgraded to MM. Turning off cores definitely makes a difference on battery life.
Also, if possible, adding a lower speed to the min speed. Will gladly test anything you thow my way. Thanks in advance.
Click to expand...
Click to collapse
What kernel are you using on LP?
patt2k said:
very nice thank you! slowly slowly we getting more and more things. Just making sure this is only for stock based rom/s Thanks!!
Click to expand...
Click to collapse
Yep, stock ROM, I'll edit the OP
dirtyhank said:
Yep, stock ROM, I'll edit the OP
Click to expand...
Click to collapse
Awesome gonna flash this soon
I hope a port for CM based roms might be possible in the future! Thanks for sharing your work and replying so quickly!
dirtyhank said:
Yep, stock ROM, I'll edit the OP
Click to expand...
Click to collapse
Getting bootloop on TruePure rom 2.4. Anything I can try to avoid bootloops?