Database Develop

[Stock-Kernel-4.3] XzInnere v5.0 [Linaro] 29-March

Note!
Only for stock 4.3
Click to expand...
Click to collapse
Features
Gamma Control - HOW-TO
DoubleTap2Wake - HOW-TO
Sweep2Wake - HOW-TO
Advanced Xperia Recovery - HOW-TO (Only v5 and above)
Based on 10.4.1.B.0.101 kernel sources
Xperia Advanced Recovery Bootloader
CPU overclock upto 1.944 GHz
Undervolting
Built with Linaro 4.8.3 toolchain using -O3 optimisation
Updated Prima WLAN drivers
Additional CPU governors - SmartMAX | SmartMAX_eps | Intellidemand 5.0 | Intelliactive | Preservative
Tweaked SIO and added FIOPS, Zen, VR, BFQ (7.2) and ROW block schedulers
USB force fastcharge
Updated Ondemand and interactive governor
Compressed kernel using XZ
Tweaked voltage regulators
Interactive GPU Governor
Uses CPUQuiet from Nvidia
Click to expand...
Click to collapse
Installation instructions
Flash in CWM/TWRP
Click to expand...
Click to collapse
Un-Installation instructions
Use the AROMA Installer in the zip to uninstall
Click to expand...
Click to collapse
Credits
Sony - I love what they do and only wish they got more recognition. They deserve it.
faux123 - For almost all kernel features
DoomLord - For the RAMDISK
Click to expand...
Click to collapse
Donors
Source
http://bitbucket.org/nikhiljan93/xzkernel
Click to expand...
Click to collapse
XDA:DevDB Information
[Stock-Kernel] XzInnere [Linaro-4.8.3], a Kernel for the Sony Xperia Z
Contributors
alnikki25k
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 5.0
Stable Release Date: 2014-03-29
Created 2014-01-27
Last Updated 2014-03-28

Reserved
HOTPLUG CONTROL, GOVERNORS, SAMPLE CONFIGS:
Thanks to n3ocort3x
With cpuquiet + load stats governor u get a brilliant battery life while keep it snappy.
I recommend leaving the governor on load stats (hotplug depended on load) to get the best results.
If you want to keep it balanced, and yeah, most users want that:
governor: smartmax
cpuquiet governor: load_stats
If you want ultimate performance:
governor: interactive (up treshold 65) or smartmax (lower tresholds)
cpuquiet governor: load_stats
SMARTMAX GOVERNOR
===============
awake_ideal_freq 594000
boost_freq 1242000
suspend_ideal_freq 384000
touch_poke_freq 1242000
Leave the rest untouched
Click to expand...
Click to collapse
For a more power-saving governor (Recommended)
New! Preservative
Click to expand...
Click to collapse
Thanks to bedalus
This is just for the record, and for those interested. The previous version of Preservative worked like a combination of smartass and conservative. It would scale straight up to the optimum frequency if there was any load (like smartass), then scale up one step at a time (like conservative) if the load was above the required threshold. This worked pretty well, and helped keep the frequency low. But sometimes it was keeping it low for too long, and a few users (myself included) noticed occasional hangs, presumably caused by a pile up of critical code that didn't get executed in time.
To improve responsiveness, but keep the frequency as low as possible was quite a challenge. I took the existing logic and chucked most of it in the bin...
(Remember, it's keeping the frequency low, and not UV that saves power - read this thread, especially post #2 for more background on this issue)
...what came to replace it was a fairly original hybrid, inspired by ondemand. Ondemand works by jumping to the top frequency when there is any load. This is usually overkill. So, you might have been at 100% CPU utilisation at 384MHz, so ondemand will jump straight to 1512MHz. However, when it gets there, the utilisation is now only 30%, so it will scale down to 486MHz.
Preservative now works a little like this. Whatever frequency it is currently at, if the utilisation hits 100%, it will scale up. But scaling up to max like ondemand? In the example above, this was the worst kind of overkill. Scaling up to max just to find scaling up one step would have been sufficient. But do we need to scale up one step, or as many as possible? There's no way to know for sure. You have to scale up before you can measure if the extra CPU cycles were enough or not.
This issue is what Preservative attempts to overcome: if the load is high, it will scale up, but not always to max. Let's label the frequency steps: 384=A 486=B 594=C 702=D 810=E 918=F 1026=G 1134=H 1242=I 1350=J 1458=K 1512=L
Conservative would take 11 calls to the governor to get from A to L, if L was required. Ondemand would go straight there. Ondemand is often overkill, conservative is often underkill. I'd like a compromise. Here's what Preservative would do:
Code:
L <- 4th step selected by preservative
K <- 3rd step selected by preservative
J <- 2nd step selected by preservative
I
H
G <- 1st step selected by preservative
F
E
D
C
B
A <- sat here until there is load
It splits the difference between whichever frequency it is at and the top frequency, and jumps there. If it is still under high load, it will do it again. So if it is idling, then needs to get to the top, it takes three more calls than ondemand, but seven less than conservative. Not only that, but it has also skipped over a large chunk of the slower steps that conservative would crawl through.
Scaling down also works in a similar way. Preservative will work out what step would be sufficient to manage the load, then jump halfway to that step on the first call. This is because, unlike ondemand, there is no down-threshold. Preservative will scale up when the load exceed the up threshold, but as soon as this is no longer the case, it will start attempting to scale back down to save power. It does not wait for load to reduce to drop below a certain point. Loads fluctuate. If went straight back to A, only to come back back to L, it would have to scale through G J and K again. However, dropping to G then D then B before A means if it does have to scale back up towards L, it doesn't have as far to climb, meaning less calls to the governor, and that the best step can be achieved quicker.
There has also been an adjustment to the up threshold. When the device is idle, the up threshold will automatically adjust to be more relaxed about scaling up. This means while the device is idle (e.g. when you are just reading some text) it becomes increasingly sensitive to changes in demand. When you touch the screen it will extremely responsive.
Conversely, when the device is hitting the top frequency, the up threshold will become increasingly strict. So if you are gaming, and putting a lot of load on the CPU, it will aim to be as efficient as possible, and only scale up if it really has to, to ensure that no cycles are wasted at these high power hungry frequencies.
Whenever it goes from hitting L to hitting A, or visa versa, the threshold will reset to default. The sysfs location of this tunable remains at:
Code:
/sys/devices/system/cpu/cpufreq/up_threshold
It will accept values of up to 127, higher being more power-saving. The default is 100, but editing the file changes this value. If you want to use a different value on a permanent basis, add the line
Code:
[B]echo 84 > /sys/devices/system/cpu/cpufreq/up_threshold[/B]
to /etc/init.d/00config
and it will then restore your setting of 84 (or whatever) every time you reboot. Remember it will be overwritten if you flash updates to the kernel, so make a copy of your edited file. However, I believe 100 is a pretty good default.
Click to expand...
Click to collapse

Reserved
Changelog
Next-Release-TO-DO
XzI - v6
Kitkat - 230 Sources
Massive changelog
Large amounts of debugging code removed
Click to expand...
Click to collapse
Current-Release
XzI - v5
Intelliactive CPU governor
New! Advanced Xperia Recovery Bootloader
New! Preservative CPU Governor (Read more)
Kernel mode NEON
MSM CPU Frequency Limiter / a.k.a Snake Charmer(in faux app) support
Kernel Futex tweaks
MSM Memcopy enhancements from Motorola Mobility
Higher Bus Speeds @ Lower cache clocks = Higher performance @ Lower Temperatures + More Power Savings
Generic tweaks
Click to expand...
Click to collapse
Previous releases
XzI - v4
Sony 10.4.1.B.0.101 Sources
Tap2Wake/Sweep2Wake using evgen method
New Power-Aware Workqueue algorithms
AROMA Installer
XzDualRecovery
Lots of debugging removed
BFQ-v7r1
Interactive GPU Governor
Removed Simple GPU Governor
Removed MultiROM
Click to expand...
Click to collapse
XzI - v3
MultiROM Xperia for Xperia Z - http://www.youtube.com/watch?v=9f9gG1sRNog
- Initial implementation. Not functional. Just testing boot.
Revert Power-Supply drivers back to 4.2.2
Intellidemand Governor 5.0
Click to expand...
Click to collapse
XzI - v2
Lower undervolt to 600 mV
Sound Control 2.0
Gamma Control
SLUB updates
Updated Adreno drivers
Use O3 Optimisation
Tune BFQ
System Config Clean-up - Quite experimental
Click to expand...
Click to collapse
XzI - v1
Initial Release
Click to expand...
Click to collapse
Download
Click here
Click to expand...
Click to collapse

MultiROM
Coming Soon

Placeholder

Cool! Good job. What would you say is the advantage in this kernel over XzKernel?

Kocayine said:
Cool! Good job. What would you say is the advantage in this kernel over XzKernel?
Click to expand...
Click to collapse
Almost no setup needed. Everything works with a good default configuration. Uses a completely different hotplug governor.

alnikki25k said:
Almost no setup needed. Everything works with a good default configuration. Uses a completely different hotplug governor.
Click to expand...
Click to collapse
I guess including DoubleTap in the kernel would make it too much like your other kernel, right?

Kocayine said:
I guess including DoubleTap in the kernel would make it too much like your other kernel, right?
Click to expand...
Click to collapse
Yup. May not include that. But will have Gamma control.

No sound control right?

alnikki25k said:
Yup. May not include that. But will have Gamma control.
Click to expand...
Click to collapse
You sure you cant make a version with doubletap? I dont need very advanced kernel, just some governors and stuff and now I got used to the tapping as well : (
BTW, how about the wakelock fixes and so from XzKernel, are they included here?

beniamin24 said:
No sound control right?
Click to expand...
Click to collapse
This is just the first release. It'll be added next.

my phone reboots after trying to undervolt in trickster mod app

braacic17 said:
my phone reboots after trying to undervolt in trickster mod app
Click to expand...
Click to collapse
It works for me. Clear all settings in TricksterMOD and try again.

alnikki25k said:
It works for me. Clear all settings in TricksterMOD and try again.
Click to expand...
Click to collapse
nope. still not working i tried everything even in faux123 app but it just reboots.
well its not so important for me right now. kernel is awesome and i can see better battery life on my xz 4.3 !!
thanks ! :laugh:

alnikki25k said:
Yup. May not include that. But will have Gamma control.
Click to expand...
Click to collapse
When you include gamma control I'll switch to this kernel
Sent from my C6603 using xda app-developers app

What about exFAT? Is it work properly?

-totonio- said:
When you include gamma control I'll switch to this kernel
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
.. and doubletap.. then we got all that is needed

Not for deodexed right?
Inviato dal mio C6603 utilizzando Tapatalk

Exactly what i need, a battery oriented / balanced kernel, while keeping it slim.. Keep up the good work!
Waiting for gamma control.. ??
Edit Note: i've missed the part which state that double tap wont be included here.. Sorry..
Sent from my C6602 using Tapatalk

[KERNEL][AOSP/CM][3.4.107][GCC 5.0]Spirit.Kernel for peregrine-r3[21/04/15]

Spirit Kernel
This kernel is ONLY for AOSP based ROMs. This will NOT work on the stock Moto roms.
I will update this regularly as I have time and will add new features and fixes as well.
If you have any feature requests or ideas that haven't been seen before, don't hesitate to post it here!!​
PLEASE READ
How to report a bug?
Include the following in your bug report:
The ROM you are currently using + a link to the ROM's thread
A log, preferably dmesgs or kmsgs (use Google to find out how to pull these from your device)
The version of SpiritKernel you use (=rx, e.g.r3)
Bug reports not meeting these requirements will be ignored.
NO BUG REPORTS ON EXPERIMENTAL BUILDS!​
Features
This Hybrid kernel contains features from great kernel devs with like faux,franco and neobuddy,optimized for titan to make it work.Initially there are less features but I will add much more soon
[*]Based on the Latest CyanogenMod sources
[*]Patched 3.4.107 kernel
[*]Governors: ondemand/userspace/powersave/performance/interactive/IntelliMM/inteliidemand/intelliactive/smartmax/pegasusQ
[*]Hotplug: MPDecision/MSM Hotplug/Intelliplug(default)
[*]Intellithermal v2
[*]DT2W/S2W/S2S Wake controls
[*]CPU Underclocking 192Mhz
[*]GPU OC 533Mhz | UC 100Mhz
[*]Add MSM Hotplug Driver
[*]Asynchronous Fsync extracted from HTC
[*]Sweep2Sleep driver
[*]Dynamic management of timer slack
[*]Slimbus OC thanks to neeobuddy89 and poondog
[*]increase Torch power 20mA
[*]Dynamic management of dirty page writebacks
[*]IO: BFQv7r7/FIFO/SIO/FIOPS/ZEN/VR IO Schedulers
[*]Faux Sound Control 3.2
[*]KCAL v2 by @savoca
[*]USB forced fast charge
[*]Stereo call recording support by skvalex
[*]Powersuspend from Faux and yank555-lu *updated to 1.8 after r8*
[*]Kernel Compression: XZ
[*]psx2usb controller
[*]Use Android device as USB keyboard/mouse
[*]optimized ARM RWSEM algorithm.
[*]Ultra Kernel Samepage Merging {UKSM}
[*]FRandom
[*]Dynamic FSync Control
[*]Added Simple GPU Algorithm
[*]WQ_POWER_EFFICIENT for bettery battery life. Hello Battery!!
[*]ANY Kernel
[*]Kexec hardboot patch for Multirom support
[*]TCP: HTCP/HSTCP/HYBLA/VEGAS/SCALABLE/LP/VENO/YEAH/ILLINOIS/WESTWOOD
Optimizations
[*]Compiled Using UBER 5.0 GCC
[*]Added optimized ARM RWSEM algorithm.
[*]Disable add_random
[*]Pocketmode and deepsleep for dt2w/s2w
[*]Optimized VFP Module
[*]FIx integer-overflow in veno,vegas
[*]Add sysinterface for GENTLE_FAIR_SLEEPERS
[*]NOATIME and NODIRATIME as default
[*]New 99LMK script by @Pizza_Dox
[*]Nvidia Patches to enhance power efficiency.
[*]Sched optimizations
[*]Increase battery level check interval
[*]writeback: increase bdi_min_ratio to 5
[*]block: cfq: merge tweaked tunables.
[*]Wait just 1 second for other CPU to halt
[*]net: combat buffer bloat
[*]PM: Introduce suspend state PM_SUSPEND_FREEZE
[*]Disable -fconserve-stack on ARM v2
[*]Enable power efficient workqueues by default
[*]do not use msm_run_queue_stats
[*]enable/disable cpu-boost via sysfs
[*]softirq: reduce latencies
[*]Built with Ofast flags
[*]Force SELinux permissive
[*]LowMemoryKiller management of non killable processes
[*]Headset High Performance Mode
[*]Allow CPU-supported unaligned accesses
[*]Enable UNALIGNED_ACCESS
[*]enable ARCH_POWER
[*]lower swappiness
[*]vfp: remove double entries
[*]Disable disable crc check for 30% extra performance in IO
[*]Optimized SLUB memory allocator
[*]Optimize Sfck Compression
[*]set sched_mc_power_savings to 2 (moar powarrrrrrr! saving)
[*]readahead to 256
[*]Built with Graphite flags
[*] Enabled Pipe Flag
TO-Do List
IntelliMM-intelliminmax
New Govs and I/Os
Intelliplug 4.0
GPU OC and UC
* Recommended app for tweaking the kernel: FauxControl,Kernel Auditor or TricksterMod
Recommended settings :
Governor: Intelliactive
I/O Scheduler: Fiops or row
TCP Congestion : Westwood
GPU Governor : Simple Ondemand Or Msm-adreno-tz
Hotplug : Intelliplug ( Keep screen off frequency to 787 MHz )
Powersuspend : Hybrid
Simple GPU Algorithm : On​
How DO I flash this?
Reboot to recovery.
Install zip from SD Card.
Choose the SpiritKernel-Rx-titan.zip
Insatll and Reboot.
Changelog:
Click Me
Downloads:
Basketbuild
Source:
Github(branch:spirit)
Wiki containing changelogs,settings and more
Antutu Score: http://forum.xda-developers.com/showpost.php?p=59736983&postcount=136
Credits goes to these SUPERHUMAN for Inspiration and support (In no specific order)
faux123
Cl3Kener
slukk
luca020400
savoca
Anas Karbila
hurtsky
pinkflozd
YoshiShaPow
Flashhhh
flar2
And more
XDA:DevDB Information
Spirit kernel for peregrine, Kernel for the Moto G
Contributors
DC07
Source Code: https://github.com/DC07/spirit_msm8226
Kernel Special Features: DT2W/S2S+S2W/FRandom/Powersuspend/Hotplugs/GPU OC/UC/CPU Underclock/GCC 5.0 Compiled and More
Version Information
Status: Stable
Current Stable Version: r3
Created 2015-03-13
Last Updated 2015-04-21

Reserved for Changelogs and Reviews
F.A.Q. - Read this before complaining!
1. My phone exploded, HALP!
A: I don't answer to problems without a log. The log file is in /proc/last_kmsg. Paste it on pastie.org and link it on your post. Logcats are useless for Kernel purposes, don't bother posting them.
2. This kernel works on Y or X rom?
A: Doesn't work with ROMs having different ramdisk or any derivates due to their irresponsibility of using a different ramdisk which needs patches that break stock rom users. Use a different rom and don't bother me.
3. OMG BETTARY SUCKZ, IT DEAD IN 45 MINUTAS, HALP!
A: As you can imagine I don't build kernels to decrease battery life. All the battery life problems come from your apps, either Facebook, or Maps, or some Location Service being enabled etc etc. Check your damn wakelocks and fix them, the kernel is not responsible for them.
4. How do I flash this?
A: Reading the OP, theres a reason why I added instructions on it.
5. What is a data loss? Did I just had one?
A: Data loss is simply having the connection cut for X periods of time, usually few seconds. Grey bars means the device is not connected to Google services for some weird reason, but you'll still have internet connection.
6. OP is arrogant, I'm gonna call the Internet Police?
A: Deal with it.
Settings recommended by our users: Copied shamelessly from my titan thread
metalrules321 said:
Heres what I use and it gives me exceptionally good battery life and perfomance (may differ for others) /using faux-clock app
1.CPU Hotplug
-Intelliplug (I use fauxclock, so cant find the msm hotplug)
-Touch boost on
-Screen off frequency 787 mhz
-Hysterisis value : 8
-Profile : Ecoconservative
-Threshold value 350
2.Thermal Manager
-Intellithermal
-Frequency Throttle temp; 70
-Core throttle temp: 65
3.GPU manager
-Governor: msm-adreno-tz
-simple gpu algorithm
-gpu clock:320
-Simple governor (laziness); 5
-Ramp Threshold: 5
4. IO scheduler
-ROW (for both emmc and sd)
-Read ahead :1024
-Entropy: off
5.Memory Manager
-Zram: Off
-All the other options on
- Swappines:80
-VFS cache pressure : 120
-Dirty ratio:20
-background ratio:5
6.Same page merge
-Intelli ksm enable
-Activation treshold :24
-Cycles per activation 3
-Pages to scan:400
-Scan delay interval :500
7.Battery Control
-Throttling - On
-Temperature threshold :45
-Throttle frequency:787
8.Miscellaneous
- Powe suspend mode: Userspace
-powesuspend: On
-Dynamic file sync: on
-TCP congestion control:Westwood
*Sorry for an awfully long post *:silly:
Click to expand...
Click to collapse

Great! I will test it today if I can. This is for lollipop right?

rodsayd said:
Great! I will test it today if I can. This is for lollipop right?
Click to expand...
Click to collapse
Yes.AOSP/CM based roms only! No stock

Wow
Loved the features! Great work mate! :good:

Gr8 to see a kernel
Do tell me if u have any problems!!

it is possible to have cpu overclock for gaming please
I cant find avy kernel with working oc for cpu , just a little be very nice if is possible thank
Continu good work sorry my bad english

DC07 said:
Spirit Kernel
This kernel is ONLY for AOSP based ROMs. This will NOT work on the stock Moto roms.
...​
Click to expand...
Click to collapse
Would you add the intelliactive governor and the RAW IO? Whille keep the Intelliplug out?​

Great Kernel
Excellent! Thanks to @DC07 for your great job!
I hope greats news in the future! :fingers-crossed:

Nice work - thanks for that! I really appreciate the minimum frequency and OndemandPlus Nevertheless I got a bug which prevents my phone from going into deep sleep.
Can anyone confirm or provide a fix?

BlueFlame4 said:
Nice work - thanks for that! I really appreciate the minimum frequency and OndemandPlus Nevertheless I got a bug which prevents my phone from going into deep sleep.
Can anyone confirm or provide a fix?
Click to expand...
Click to collapse
I didn't encounter any problems with the phone going to deep sleep when I tested it bro, I did have problems with the headphones not working but it got fixed... Did you check with WakeBlocker to see which app(s) are not letting it go to sleep?

hhrokarvi said:
I didn't encounter any problems with the phone going to deep sleep when I tested it bro, I did have problems with the headphones not working but it got fixed... Did you check with WakeBlocker to see which app(s) are not letting it go to sleep?
Click to expand...
Click to collapse
So I let my phone settle overnight and it goes into deep sleep now. The causing wakelock was PowerManagerService.Wakelock which is now gone. Looks like some app went nuts - thanks for your support, mate!

Just want to know if it's work for KK rom and specially for slim rom in 4.4.4?
Thanks

patgou.007 said:
Just want to know if it's work for KK rom and specially for slim rom in 4.4.4?
Thanks
Click to expand...
Click to collapse
It works on CM based ROMs.. Won't hurt to give it a try thou

Right to make a try but before, just want to be sure that this kernel is for kit kat rom.

patgou.007 said:
Right to make a try but before, just want to be sure that this kernel is for kit kat rom.
Click to expand...
Click to collapse
I guess since 99% of us are already on Android 5.x.x nobody can answer that question, make a Nandroid or use Flashify and backup your current kernel,
if it does not work or behave well you can simply restore your backup/kernel backup and report if it works or not, for other users
cheers

Right. I 'll try later and report. Thanks

Damn, this Kernel is really noice !
I tried it on BlissPop v3.0 - well this ROM is amazingly fast and awesome out of the box but with this Kernel i feel a slightly performance boost.
I had also some little micro animations lags here and there, with this Kernel, they are completely gone and my device is flying as * like never before on Android 5. :good:
One thing though, WIFI does not work, the button to activate it is simply grayed out.
Regards

gr3ud said:
One thing though, WIFI does not work, the button to activate it is simply grayed out.
Click to expand...
Click to collapse
judging by your screen shot, your phone may be in airplane / battery save mode cause low battery, and maybe thats why your wifi may be disabled ?

Hastaloego said:
judging by your screen shot, your phone may be in airplane / battery save mode cause low battery, and maybe thats why your wifi may be disabled ?
Click to expand...
Click to collapse
WiFi still works in Low battery mode, it just restricts the background data from the apps. He is also not in Airplane Mode because we can see full signals for the SIM Card, and it would have been an airplane logo in place of that.
I've tested it too, No WiFi but other stuff works perfectly, not to mention the performance is also good.

[Kernel][5.x.x][ArchiDroid-GCC5.2] DatKernel for i9082 [r21][O3 & Ofast][02122015]

​
What is it?
DatKernel is a fully customizable Kernel, with lots of new options that our Grand was never supposed to have. Have you ever thought of the perfect balance between battery life and craze performance? Here we go.
I first started compiling in October this year, inspired by @codekidX kernel and decided to build my own Kernel. I struggled some time to learn how to and implement my first functionalities and my first toolchain was Linaro 4.9 from @Christopher83. Since then, I've built hundreds of times with dozens of toolchains and, since everything is pretty much stable and different from other kernels around SGGD development, I had to share with you guys to further improve this kernel.
For me, the biggest problem were related to constant reboots caused by overflow in RAM or by incorrect execution when I started many apps. Couldn't open my maps with bluetooth playing music on my car and *BUM*, rebooted. Also, the performance was a little laggy sometimes, due to lack of upstreamed source. So let's waste no more time:
List of features​
Toolchain and Compiling
Compiled with ArchiDroid's 5.2 toolchain, thanks to @JustArchi for his amazing job. GCC5.2 is very very stable.
Most of the kernel compiled with -O3 flags, but a lot of parts are compiled using -Ofast (goodbye O2 and Os hehe).
Using all the graphite optimizations that were possible to our phone, along with cortex-a9 tweaks.
Kernel Features
Dynamic management of dirty page writebacks, thanks to @faux123
Asynchronous file sync, thanks to @faux123
Dynamic filesync, thanks to @faux123
zram is enabled. It was backported also from @faux123 mako Kernel, and I did some commits to adapt it to 3.0.101, to lz4 support and to Zsmalloc.
Optimized ARM RWSEM / CRC32 algorithms, thanks to @coderdoid
Implemented frandom, thanks to @Ryuninferno
Updated Kernel Freezer and implemented Input Touchboost, thanks to @franciscofranco
Backport LMK RB trees from Motorola, thanks to @faux123
Lots of commits from 3.4.x and 3.12.x which came from CM's repos and @DespairFactor and @myfluxi. Some of them were crucial and obviously 3.0.101 lacked support of it.
Drivers like thermal, staging (LMK, binder, logger, gpio) and others were updated to last on CM-13.0, with some backports.
Ultra KSM implemented and enabled (UKSM)
vmpressure updated to CAF.
Boeffla-sound, thanks to @Andip71
cgroup_timer_slack and also dynamic cgroup_timer_slack management.
Boottime (it's useful for viewing boot time, implemented just because...). Thanks to @k2wl !!
oom_kill.c from @faux123 mako Kernel. This was a little hard to backport, but now I see how big the changes are until 3.4.xx
Zsmalloc which proved to be very useful when replacing Xvmalloc (the latter seems to be depracated).
Check my GitHub for much more awesome stuff...
Governors and I/O Schedulers
Updated and tweaked BFQ, SIO and DEADLINE. Also comes with CFQ, Noop, ROW and Sioplus.
Governors updated to @dorimanx version: ondemand, alucard, darkness, impulse, intelliactive, performance and zzmoove.
Interactive governor was updated according to @myfluxi repo and blu_active is the same used on @eng.stk kernel.
Do you want to see any governor here? Please request and I'll try to implement it!
CPU Hotplug drivers
intelliplug (aka intelli_plug) is implementes and working fine with intelliactive, with default options enabled.
zzmoove also offer lots of hotplugging options which are VERY stable, not a single random reboot or freezing during my usage with it.
Do you want any other CPU HOTPLUG driver? There are lots of options, if you want any of them, request it.
Attention
I'm not experienced as a Android Dev, as you can see most of features here were backported or upstreamed.
You can request features, but don't expect them to be implemented asap, because there are lots of tests to do. Please don't request DT2W and S2W, because they do not work properly on our phones (too much waste of battery for small benefits).
Also, if I have to backport or Upstream anything, be sure that is not as easy as it seems, cause 3.0.101 is pretty outdated nowadays, but we can't go much further than this.
Disclaimer​
If your phone is bricked, exploded, vanished or something like this after installing this kernel, it's not my responsability. I'm sharing with you my personal builds and you're using at your own risk.
Be sure that I'll help you as I can, but this is supposed to be a kernel adapted to my usage and may not work for yours. Follow the instructions correctly and don't forget to hit thanks if you liked the initiative.
DO YOU WANT TO CUSTOMIZE YOUR EXPERIENCE? GO TO POST #2.
DO YOU WANT TO DOWNLOAD IT? GO TO POST #3.
Please, be kind on the comment section. I'll try to help you as much as I can
XDA:DevDB Information
DatKernel, Kernel for the Samsung Galaxy Grand Duos i9082
Contributors
neves4
Source Code: http://github.com/Neves4/DatKernel/
Kernel Special Features: This kernel is built with -O3 and -Ofast flags, with an optimized toolchain from GCC5.2. Lots of upstream code, new govs, zram, hotplug and a whole new experience in smoothness.
Version Information
Status: Beta
Current Beta Version: r20
Beta Release Date: 2015-11-27
Created 2015-11-27
Last Updated 2015-12-02

CUSTOMIZE YOUR EXPERIENCE​
This part is still under construction, so bare with me!
How to customize the governors?
Most of the governors on XDA are based on some of the basic ones. As, I'm not the creator of any of these governors, I will only show you my personal recommendations and some links for you to read more. Let's go!
Interactive-based Governors
This are the new ones, which derived from very updated code, which is said to replace ondemand on the future. I really like these governors, as they're blazing fast and battery-life is almost the same as default ondemand. They're impulse, intelliactive, blu_active and interactive:
interactive: Upstreamed to lates on Code Aurora Forums (CAF), it is a very fast governor. Scales depending on load and goes really fast from minimum to max frequency. The battery is "OK" with this one, and you can tweak it to become exactly as you like, just by following this thread instructions: [GUIDE] Advanced Interactive Governor Tweaks; Buttery smooth and insane battery life!, by @soniCron.
RECOMMENDATION: I've tweaked it for best performance already, so give it a try on default.​
intelliactive: More performance focused than interactive, but achieves a great balance between battery-life and performance. You can tweak it using the same thread by soniCron that I told you in interactive.
RECOMMENDATION: The frequencies are on par with my i9082 common usage, and it fells a little better than interactive, but they're almost the same on benchmarks.​
impulse: This one is focused on battery-life and works just fine, with some lag here and there (not that it really lags, lil stutters). You can tweak it using the same thread by soniCron that I told you in interactive.
RECOMMENDATION: Again, this one is tweaked for our i9082 and can save some battery if you use it on default.​
blu_active: @eng.stk made this one, it's probably the fastes on interactive-based, but it's not very stable on my phone. You can try for yourself and see if is there any random reboots.
RECOMMENDATION: For now, you can try it, it's very snappy and smooth but not that stable. See if default works for you.​
Ondemand-based Governors
Apart from being a little outdated, they still work great and bring really impressive results under the table. The governors ramp up and ramp down in defined steps, according to demand, but if you're multi-tasking, it stays on very high frequencies. The governors are: alucard, darkness, nightmare and ondemand.
ondemand: Not much to say. It's the default governor because it's very stable and you can find much information about it on this link: CPU Governors, Hotplugging drivers and GPU governors
RECOMMENDATION: Use it by default, rock-solid stable.​
Darkness: It works fast and is a new gov. Liked it, it's good by default.
RECOMMENDATION: Use it by default, may be stable.​
Nightmare: This one originated Darkness, and is probably the same with bigger code.
RECOMMENDATION: Same recommendations as Darkness, use it by default.​
Alucard: Pretty impressive governor, made by @alucard_24 and maintained by @dorimanx.
RECOMMENDATION: Default is OK, it's the best under ondemand-based governors.​
Conservative-based Governors: zzmoove
Maintain the phone on lowest possible frequency whenever possible. The only governor 'round here is zzmoove and DUDE: it's great. Thanks to it, I have a Crazy-smooth experience and awesome battery-life, so I really liked the way it works.
zzmoove: Created by @ZaneZam and maintained by him and @Yank555, this governor focus is to maintain frequency as low as possible. In order to do that, it limit frequencies whilst the screen is off or hearing music, in example, so it's very adaptive to your usage if you tune it right. It has 9 profiles, which are described below, on "Click to show content"
* ------------------------------------------------------------------------------------------------------------------------------------------
* - (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 -
* ------------------------------------------------------------------------------------------------------------------------------------------
RECOMMENDATION: I selected for default "zzinZ", profile 9, because it really is what I want: lagless when using, low frequencies when not using. And I got it, so I suggest you to have a look.​
What about I/O Sched?
Well, I've never worried much about I/O sched. When pawitp put BFQ as default on CM12.1, I thought that it was really good, but really unstable as well. The two I like the most are: SIO and Deadline for general usage (multitasking). If you like to play heavy games, use ROW. You can try the others and actually read this article that talks everything about I/O Schedulers: I/O Schedulers - Android Modders Guide
Damn, need that Hotplug asap!
i9082 phones, have lots of power and sometime doesn't need all cores online. That's where come hot-plugging, some cores can be turned off with no overhead or noticeable lag.
The options are: intelli_plug and zzmoove hotplugging feature.
intelli_plug: The first option is a widely spread hotplug driver, made by @faux123 and it works great for what it's doing. I recommend tweaking it for you needs and the best governor to integrate with it is intelliactive, made by faux123 as well. It'll actually waste battery instead of saving if you are a power user that loves lots of multitasking, because it'll be constantly turning CPU1 on and off. Note that while using this, make sure your tasks with Screen Off are not that big, because your phone must handle that with just 1 core, which can lead to a kernel freeze (than you have to reboot). It's recommended if you usage is very light and you want a 2 days long battery.​
zzmoove hot-plugging: The second one is a more concise approach, because you'll need only the governor to handle hot-plugging. Here you can activate the hotplug on governor's tunables (change to disable_hotplug = 0 and disable_hotplug_sleep = 0) and it works by shutting down CPU1 whenever the load is not that big. Again, if you're a power user, beware that this can actually shrink you battery time, so use hotplug if you doesn't need much complex things to be done when screen is off.​
frandom - Don't forget to use this script in your init.d folder
Create a new file named "00frandom" and in order to frandom work, you need to use this code:
Code:
#!/system/bin/sh
# Script to launch frandom at boot by Ryuinferno @ XDA
insmod /system/lib/modules/frandom.ko
chmod 644 /dev/frandom
chmod 644 /dev/erandom
mv /dev/random /dev/random.ori
mv /dev/urandom /dev/urandom.ori
ln /dev/frandom /dev/random
chmod 644 /dev/random
ln /dev/erandom /dev/urandom
chmod 644 /dev/urandom
My Recommendation​
zzmoove really got me, because it works like interactive but it tries to always lower the frequency, which is great. Apart from that, intelliactive is very fast, almost the same as interactive. So, for craziness zzmoove and for performance, intelliactive (UNDER CONSTRUCTION, JUST A QUICK PREVIEW).
### Anything else there is to customize is in Kernel Adiutor, which is a great app thanks to @Grarak

Download here!
DOWNLOADS​
First things first: how to install?
Backup your EFS partition and do a full nandroid of your system. Never did the latter, but my backup of EFS partition saved me multiple times when I was a noob in flashing.
Download last version which will be attached on my GitHub Release page (download the zip). Will try to attach it to the thread here as well.
You're installing for the first time? Factory reset your phone and install the lastest version of CM12.1 from @pawitp. Be sure to do this before anything weird happens. You're advised! (the reason is that when you flash different kernels, sometimes they're on different kernel version on crucial parts, which leads system to incompatibility)
Already installed once? Just dirty flash it then and profit.
Reboot your phone.
Lemme download this, bro!
FOLLOW THE SETTING UP HERE /\. It's the same for all kernels you've used, but please, EFS partition backup is a must.
The last version will be on my GitHub's release page, on this link:
To download it, click on "DatKernel-rXX.zip" under Download tab on Latest release. Trouble downloading it? PM me so I can send it to you!
>>>> CLICK HERE TO DOWNLOAD <<<<​

Thanks, nice to see a new kernel.
Will try it when ready

@RichyE with you want to try it now, I just uploaded r20 to GitHub, give it a shot!
https://github.com/Neves4/DatKernel/releases/tag/r20
Download "DatKernel-r20.zip" file.
And for now, I'm having crazy smooth results with zzmoove, try it
Oh, and remember to have CM-12.1 ready to reflash, just in case something goes wrong.

SWAP
is this swap enabled(for swapping the sdcard memory to increase the ram)??

ayush.gl said:
is this swap enabled(for swapping the sdcard memory to increase the ram)??
Click to expand...
Click to collapse
It is enabled on configs, but when I type "free" in terminal it shows no swap device being used, which is weird. Can you try it and see what happens when you type free in terminal?

Flashed it on RR first boot gave problem, had to pull batery but after that it worked.
Even a couple of reboots went smooth

@RichyE is it working OK now? I'm sorry to hear you had trouble...
Have you tried the new govs?
Thanks

@neves4 It's working now without a problem
At the moment trying zzmoove and Sioplus

Zzmoove (or kernel??) giving a little trouble I think.
Sometimes the phone doesn't switch on and I have to pull battery.
Switching back to my originel kernel for the moment and will try another time.

everything was smooth but YouTube app hangs a lot!

I just flash it normally and using zzmove and sioplus and no problem it works very smooth :good:

RichyE said:
Zzmoove (or kernel??) giving a little trouble I think.
Sometimes the phone doesn't switch on and I have to pull battery.
Switching back to my originel kernel for the moment and will try another time.
Click to expand...
Click to collapse
Hey Richy, we can maybe solve this problems. I've sent you a PM, take a look
aditya_pan said:
everything was smooth but YouTube app hangs a lot!
Click to expand...
Click to collapse
Bro, what are your configs? Are your using BFQ or hot-plugging?
abhishekcma said:
I just flash it normally and using zzmove and sioplus and no problem it works very smooth :good:
Click to expand...
Click to collapse
Thanks for trying it

I am going to try your kernel soon but is it stable enough to be used as a daily driver????
And one request if you don't mind can you develop ROM for our device with marshmallow support???

@neves4 is it kit kat compatible?

neves4 said:
Hey Richy, we can maybe solve this problems. I've sent you a PM, take a look
Bro, what are your configs? Are your using BFQ or hot-plugging?
Thanks for trying it
Click to expand...
Click to collapse
I was using zmoove governor and sioplus as the io scheduler. I didn't know what hot-plugging was, so didn't mess with it. appreciate your effort man.

Do you plan to make it compatible for aosp 6?
Sent from my GT-I9082 using Tapatalk

hi
thanks for the kernel..will trry it soon.
i have one doubt.
zzmove needs hotplugging and as far as i know our kona platform restriced it in kernel code.
thats why RichyE have problems with zzmove.
anyways may be you have solved that..good luck...

sai milind said:
I am going to try your kernel soon but is it stable enough to be used as a daily driver????
And one request if you don't mind can you develop ROM for our device with marshmallow support???
Click to expand...
Click to collapse
Hey man, it's completely stable for me. Smooth, fast and with great battery, I'm using r20 with no random reboots for 120 hours, and I'm a power use (always using bluetooth, with 3G on and GPS on High Accuracy). If you want to be sure that it's going to work, do a clean install and install lastest CM12.1 that it'll be stable as a rock
And about the ROM with marshmallow support, I'm waiting until pawitp gets AOSP-6.0 stable, because there are some complications to make it work on our phones
daneal2u said:
@neves4 is it kit kat compatible?
Click to expand...
Click to collapse
Good question! I've never used KitKat, because I used to own an iPhone. Since this kernel is based on Frost Kernel source code, I'm almost sure it works on KitKat, and the others to 4.1.2. Can you try it and report back? Be sure to have a copy of the ROM you're using, because anything goes wrong, you just have to flash the ROM back.
aditya_pan said:
I was using zmoove governor and sioplus as the io scheduler. I didn't know what hot-plugging was, so didn't mess with it. appreciate your effort man.
Click to expand...
Click to collapse
Thanks for the answer
It's known that zzmoove has problems with big loads, so I think that when you were using YouTube, you were probably using other apps on background, which made system a little unstable. Can you try interactive or intelliactive and see if the same happens?
rishabh56 said:
Do you plan to make it compatible for aosp 6?
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
I would love to, but AOSP 6.0 is still not stable for our phones, as pawitp is still fixing some stuff. But as soon as everything is OK there, I'll be doing AOSP-6.0 compatibility patches if needed

AzurE Kernel 3.10.108 [UPDATED] (15-11-17) {MM/N/O} {UBER 8.0.0}

AzurE KERNEL
FOR YUser, BY YUser
AzurE Kernel (Azure is the blue color of the sky), developed by me, Panchajanya Sarkar aka @Lynx_0608, is a feature packed kernel, fully developed from latest Sources,
Compiled with Latest UBERTC(7.2.1) and LINARO(7.2.1-snapshot), it promises to give stability, maintaining performance and battery life.
Main Features :
~ Display --
*Support for kCAL Colour Control v2.0 (enhances Colour Vibrance and Intensity). Tweaked By Me
*Up-to-date LiveDisplay Driver.
*Support for Colour Enhancement (Updated).
~ Governors Support --
*Relaxed [Tweaked By Me] [Battery-Friendly]
*Barry-Allen[Updated]
*Darkness
*Interactive[Tweaked By Me][Init-D Emulation]
*Ondemand
*Userspace
*Performance
--Removed Powersave governor(was lagging heavily)
~Hotplugs Available --
*AiO Hotplug (Developed by Shoaib Anwar)
~I/O Schedulers --
*Noop
*Deadline
*Row[Tweaked By Me]
*CFQ
*BFQ
*Maple
*ZEN
~CPU Details and Frequencies --
*Max Frequency - 1612 MHz
*Min Frequency - 200MHz
*1612 MHz is the most stable Overclock for YUreka/+, stock Voltage is maintained for a better battery life
*11 Proper and equally Oriented Frequency Steps with 200MHz gap in between
*Support For Power-Efficient Workqueues for a Battery Friendliness
*Fast Idling of CPU
~GPU Details --
*Altered GPU-Frequency Table for more Power-Savings without noticeable decrease in Performance.
*Adreno-Idler was having little issues, so will be adding in next build
~Memory --
* Swap, FrontSwap, and zSwap techniques (z-RAM provides better performance at the cost of Battery)
*Memory Compaction (improves performance).
*CleanCache Driver (improves I/O performance).
*zsmAlloc with Page-Table Mapping techniques (improve memory performance).
*zRAM with LZ4 compression algorithm (improves performance by saving memory).
~Battery --
*ARCH_Power to reduce Power-Consumption and increase Battery-Life.
* PowerSuspend algorithm (improves Battery-Life).
*10 Wakelock Toggles introduced(turn them off for a better battery life)
*QuickCharge V 1.0 (Special Thanks to Shoaib Aanwar)(Tweaked Max Current to 1450mA)
~Memory Optimizations And Tweaks --
*Based on the latest sources of Lineage for Yu Yureka/Yureka PLUS.
*Compiled with UberTC 7.2.1 Optimized for 64-BIT and LinaroTC 7.2.1 -snapshot.
*Touch-Boost and CPU Boost Removed, Who uses It??
*Lowest Possible CPU-Usage (a lot of tweaks have been implemented system-wide).
* HMP Aware and Power-Aware Task Allocation (should improve Performance and Battery-Life).
*Faux Sound Control v4.1 (Special Thanks To Shoaib Anwar).
--And Many More Features Included, Try Them Out!!
Points to Be Noted--
1> Works Best On Lineage-Based ROMs, AOSP/CAF based ROMs too work FINE!!
2>For Best Control, Try out The Latest Kernel Auditor-PAID, PlayStore.
3> For Best Results, I recommend to use either Use AiO Hotplug or Core Control.
4>Don't flash AzurE Oreo on Nougat/Marshmallow ROMs
~ Download Links, Refer to 3rd Post or Click Here
Special Thanks To-
-- Akash (Telegram - @aka_xh) for Helping alot from the very beginning
-- DarkenVamp for teaching me how to use GitHub:victory:
-- Shoaib Anwar for helping me in adding stuffs, He also developed Quick Charge, Shoaib's Core Control, Modified Faux Sound and many more....
XDA:DevDB Information
AzurE Kernel, Kernel for the YU Yureka
Contributors
Lynx_0608
Source Code: https://github.com/Panchajanya1999/Azure-N/tree/cm-14.1
Kernel Special Features: Just Scroll Upwards As Of Now, for LATER BUILDS, Refer To ChangeLog
Version Information
Status: Stable
Current Stable Version: V 1.o
Stable Release Date: 2017-10-25
Created 2017-10-28
Last Updated 2017-11-19

Reserved
Recommended Settings--
~Performance --
--CPU
*Big Clusters - 1612MHz Max; 200MHz Min
*Governor - Interactive for Both Clusters
--GPU
*Frequency - 550MHz Max
*Governor - msm-adreno-tz
--Tweaks
*Turn Off Core Control, Or set the thermal value at 75 C
*U Know better than me!!!!
~Balanced --
--CPU
*Big Cluster - 1113MHz/800MHz
*Small Cluster - 800MHz
*Governor - Barry-allen on Big Cluster, Barry-Allen/Interactive on Little Cluster
--Hotplug
*AiO Hotplug - Big Cluster set at 2
Little Cluster set at 4
--Core Control
*Thermal - Set Thermal Slider at 55C/60C
Note -- Either Use AiO Hotplug, Or Core Control!!!
--GPU
*Frequency - 550MHz
*Governor - msm-adreno-tz
~Powersave/Battery friendly --
--CPU
*Big Clusters - 400MHz Max, 200MHz Min;
*Small Clusters - 800MHz Max, 200MHz Min;
*Governor - Big Clusters - Relaxed/Darkness; Small Clusters - Relaxed/Interactive
--Hotplugs And Thermal
*Enable either AiO Hotplug or Core Control
*AiO Hotplug - 2 For Big Clusters,2 for Small Clusters
*Thermal/Core Control - Turn it on,Set Slider to 50C
--GPU
*Set 310MHz Frequency alongwith Ondemand Governor
You Can Set it accordingly to your own wish!!

F.A.Q. --
1. My WiFi doesn't works after flashing this kernel.
Extract wlan.ko from the .zip of kernel (located under system/lib/modules/) and place it in root/system/lib/modules/ overwriting the one already present there. Then, set the permission of the file to rw-r-r and reboot the phone. Use ES File Manager with Root Permission to do this.
OR
Place the .zip of the kernel in Internal Storage and then re-flash the kernel.
OR
Check free space in /system partition. Atleast, 25 MB of free space should be there in /system partition as less space prevents the wlan.ko file to get copied successfully.
OR
Flash the latest version of SuperSU.
OR
Change the ROM.
2. Which Android Versions does this Kernel supports?
AzurE Kernel supports Marshmallow and Nougat ROMs. However, not every Kernel Version supports every Android Version. Check Changelog of the specific Kernel Version before flashing it.
3. Does VoLTE works on this Kernel?
Yes, if the ROM supports VoLTE, then this Kernel will also support VoLTE. However, if the ROM doesn't supports VoLTE, then this Kernel won't too.
4. How long are you planning to continue development of AzurE Kernel for Yu-Devices?
As long as I have my Yu Yureka PLUS with me, I'll keep the development active.
5. I have a feature-request!
Well, feature-requests are accepted only when I find the said feature to be having some practical use or substantial positive effect. Whether I include the feature or not, is purely my decision.
6. Why don't you answer my queries? I have asked 10 times already!
It takes much time in developing and testing a Kernel. So, it is difficult for me to keep track of every query too. However, if your query is a genuine one (i.e., not a duplicate question or a question, the answer of which isn't present in the First Post or the Changelogs), then I'll surely answer it.
7. Kernel Adiutor shows blank space in Governor and Frequency Panel of CPU TAB.
When Core 0 gets disabled (due to Core Control or State Helper HotPlug), Adiutor fails to get Frequency and Governor information and hence shows 0MHz in Frequency Panel and Blank Space in Governor Panel. This is normal. In this case, if you need to change Governor or Frequency, then you need to disable Core Control or State Helper HotPlug as the case may be. After this, force close Adiutor and then re-open it. This will make Adiutor get CPU information again. Also, if you don't want to face this situation again, then disable HotPlug Boost Toggle (this will make the kernel to not disable Core 0 and hence, such situation won't arise).
8. The HotPlugs aren't working! After sometime, all the cores come online.
After manually changing the CPU Governor or Frequency, all the Cores will come online even if any HotPlug is enabled. So, you just need to re-enable any HotPlugs you were using in order to disable the Cores again.
9. My whole big Cluster is offline! I can't enable it anyway!
Well, my kernel uses Core Control v2.0 (built by me) and hence, it has the ability to disable the whole big Cluster (including Core 0) if temperature rises above 55 C. When the temperature comes below 55 C, the big Cluster is brought back online again. This is normal and is done to reduce heat. Moreover, if you don't want Core 0 to get disabled, then you can Disable the HotPlug Boost Toggle (available under CPU TAB).
10. The CPU Frequencies are locked. I can't change them. This is a very serious BUG.
I wouldn't call it an issue or a BUG. It is a feature. My kernel uses a Custom Thermal Driver. It reduces the Frequencies to keep the temperature of the Kernel within safe limits. Hence, sometimes, when the temperature is above a certain degree, the Thermal Driver locks the Maximum Frequency so as to lower the temperature of the SoC. However, in my kernel, everything is user-configurable. So, if you want more performance and can bear some heat, then you are free to set the Thermal Settings according to your preference. These settings are available under the Thermal TAB of the Modded version of Adiutor only.
11. I don't have a 1.5A Charger. Should I use Quick Charge or not?
Let me clear this in a simple yet detailed way.
To use ThunderCharge's 1250 mA value, one needs a Charger capable of supplying 1.25A. So, if you're using a 1A Charger and you have set 1250 mA in ThunderCharge, then it won't work. The Charging will only occur at a speed of 1000 mA which your Charger supports.
Similarly, Quick Charge requires a 1.5A Charger for it to work fully. However, this doesn't means that using a 1A Charger with Quick Charge will affect Charging Speed negatively. So, if you're using a 1A Charger, then Quick Charge will draw only 1000 mA.
As for the Dynamic Current Panel, it shows the Value requested from the Charger, not the Actual Value drawn.
BTW, if you are using the Stock Charge and Yu Yureka phone, then Disable Quick Charge.

Download Links(UPDATED) And ChangeLogs-
ChangeLogs :- 15th November, 2K17 {Oreo and Nougat/MarshMallow}
*Compiled Using UBER 8.0.0 ToolChain
*Latest CAF(LA.BR.1.2.9_rb1.27) commits are merged
*UKSM - Ultra Kernel Samepage Merging
*Zen Interactive Tuning: Auto Tunes the kernel for responsiveness at the cost of throughput and power usage.
*Enabled F-Sync
*Decreased time to Enter Sleep Extensively
*Relaxed Governor is tuned a bit!!
*AluCARD HotPlug Updated to Latest Version
*Tuned for more memory
Download:-
Oreo [15-11-17] :- AndroidFileHost
Nougat [15-11-17] :- AndroidFilehost
~AzurE Nougat/Marshmallow & Oreo
ChangeLogs :- (8-11-17)
*Fully Updated To Linux Version 3.1.108!!! Previous Version was not fully Updated, so there was some issues.
*Merged latest Lineage Commits(I forgot this),
*Added NEW TCP congestion Controls, Check them out in Network/Misc tab in Kernel Auditor
*Enabled Aggressive Multi-Core Power savings (Thanks To Sanyam Jain).
*Fixed Memory Leaks.
Note : This ChangeLog is same for both Nougat/MarshMallow and Oreo!!!
`
~Download :-
Nougat/MarshMallow -- AndroidFileHost
~
Oreo -- AndroidFileHost
Updated (30-10-17)
Changelogs: -
*Now U can Turn off Core-0 - Device probably won't reboot anymore
*Boot using 5 cores. In Details, many users were facing bootloops, because, the kernel was configured to boot on all 8 cores, at max frequency, which was 1612MHz, so this drew a lots of battery power, and weak batteries resulted in bootloops. Remember, Splashloops(Device Looping at YU logo, no bootanimation) is most probably caused by lesser system space <25mB, U have to ensure a system space of 25mB, before reporting it here
*Alucard Hotplug - Added Alucard Hotplug, AND please, use only one Hotplug at once, Either AiO or Alucard;
*Re-Enabled CPU Boost again
;_;
Download Link :- AndroidFileHost

There r two Build's which one I have to falsh ...

fshafi3 said:
There r two Build's which one I have to falsh ...
Click to expand...
Click to collapse
Your Wish,
It totally depends upon You bruh,
Uber is bit Better
Sent from my YU5510 using Tapatalk

can I use it on lineage OS 15.0(8.0)
Thanks in advance

Has anyone tested yet if this kernel works with Oreo ROMs too..??

Awesome kernel
I'm using rr7.1.2 final build with in azure uber , its fully stable but one request YouTube or online play back drain only 2hrs backup?others wise 4hrs backup
Its awesome to compare velocity 15 nogut build
Sorry my bad English*:good:

luck_y said:
can I use it on lineage OS 15.0(8.0)
Thanks in advance
Click to expand...
Click to collapse
Check YuForums,
Android Oreo Is supported,
Sent from my YU5510 using Tapatalk

Da_Gamer_pk said:
Has anyone tested yet if this kernel works with Oreo ROMs too..??
Click to expand...
Click to collapse
Check YuForums
Sent from my YU5510 using Tapatalk

How can I enable quick charge??
Please replay with screenshots

Will this work on Nitrogen Os, Oreo Version?

Raman Arora said:
Will this work on Nitrogen Os, Oreo Version?
Click to expand...
Click to collapse
Yes it's working

Hello Guys,
Many of the YUsers were Complaining about "Battery Drain, Heating and Lagginess" faced, when using Oreo ROMs, e.g. - NitroGen OS, Nougat ROMs like Resurrection Remix etc.
So, I spared some time, looked into the matter and Finally, the kernel has been UPDATED!!!
ChangeLogs :- 15th November, 2K17 {Oreo and Nougat/MarshMallow}
*Compiled Using UBER 8.0.0 ToolChain
*Latest CAF(LA.BR.1.2.9_rb1.27) commits are merged
*UKSM - Ultra Kernel Samepage Merging
Spoiler: UKSM over KSM,
* Ultra KSM. Copyright (C) 2011-2012 Nai Xia
*
* This is an improvement upon KSM. Some basic data structures and routines
* are borrowed from ksm.c .
*
* Its new features:
* 1. Full system scan:
* It automatically scans all user processes' anonymous VMAs. Kernel-user
* interaction to submit a memory area to KSM is no longer needed.
*
* 2. Rich area detection:
* It automatically detects rich areas containing abundant duplicated
* pages based. Rich areas are given a full scan speed. Poor areas are
* sampled at a reasonable speed with very low CPU consumption.
*
* 3. Ultra Per-page scan speed improvement:
* A new hash algorithm is proposed. As a result, on a machine with
* Core(TM)2 Quad Q9300 CPU in 32-bit mode and 800MHZ DDR2 main memory, it
* can scan memory areas that does not contain duplicated pages at speed of
* 627MB/sec ~ 2445MB/sec and can merge duplicated areas at speed of
* 477MB/sec ~ 923MB/sec.
*
* 4. Thrashing area avoidance:
* Thrashing area(an VMA that has frequent Ksm page break-out) can be
* filtered out. My benchmark shows it's more efficient than KSM's per-page
* hash value based volatile page detection.
*
*
* 5. Misc changes upon KSM:
* * It has a fully x86-opitmized memcmp dedicated for 4-byte-aligned page
* comparison. It's much faster than default C version on x86.
* * rmap_item now has an struct *page member to loosely cache a
* address-->page mapping, which reduces too much time-costly
* follow_page().
* * The VMA creation/exit procedures are hooked to let the Ultra KSM know.
* * try_to_merge_two_pages() now can revert a pte if it fails. No break_
* ksm is needed for this case.
*
* 6. Full Zero Page consideration(contributed by Figo Zhang)
* Now uksmd consider full zero pages as special pages and merge them to an
* special unswappable uksm zero page
*Zen Interactive Tuning: Auto Tunes the kernel for responsiveness at the cost of throughput and power usage.
*Enabled F-Sync
*Decreased time to Enter Sleep Extensively
*Relaxed Governor is tuned a bit!!
*AluCARD HotPlug Updated to Latest Version
*Tuned for more memory
Download Links :-
Spoiler: Oreo - AndroidFileHost {15-11-17}
https://www.androidfilehost.com/?fid=817906626617947473
Spoiler: Nougat/MarshMallow - AndroidFileHost {15-11-17}
https://www.androidfilehost.com/?fid=889964283620766945
Special Thanks to
**@Sinnavjot a.k.a Navjot Singh
**@Jakwarlord
Thank You guys for Co-Operating with me
In case u feel any problems, feel free to share. We YUsers are Happy2Help

we have to do settings manually?

sohail sheikh said:
we have to do settings manually?
Click to expand...
Click to collapse
Yes
Sent from my YU5510 using XDA Labs

Hi,
Does this kernel enable for support of usb serial devi els like cp210x, ftdi?

[KERNEL][OREO-PIE][TREBLE] Schwifty Kernel [vR5] | AOSP | 12/12/18 |

The Schwifty Kernel (Yeahhh, Get Schwifty)
Hello guys welcome to the Schwifty Kernel! If you watch the show "Rick and Morty" you will understand why I named it this if you don't understand well either youtube it or just don't worry and enjoy the sh*t out the kernel anyways hehe. Alright lets get Schwifty, here's all the info about the kernel in a way that will help you decide how you want to set up your phone! The second post will contain changelogs and third post, well not sure yet. But enjoy!!​
Basic Specifications/Information:
Based On Axon 7 LoS 16.1 Kernel Source
Updated to the latest linux kernel source (3.18.126)
Built with Custom CrossTool-NG Toolchain (GCC: 8.2.0)
Allow 5-10 to settle in after booting up for better usage
Take the time to read all the information to get an understanding on the kernel (Will help with less bug reports)
If you report a bug please search before posting and give all information about your issue (Such as rom, kernel version, kernel setup... ect)
I will edit the page with dates when there is something new added such as govenors, schedulers ect...
I/O Scheduler Information - I/O:
NOOP - Inserts all the incoming I/O requests to a First In First Out queue and implements request merging. Best used with storage devices that does not depend on mechanical movement to access data (yes, like our flash drives). Advantage here is that flash drives does not require reordering of multiple I/O requests unlike in normal hard drives.
DEADLINE - The goal of the Deadline scheduler is to attempt to guarantee a start service time for a request. It does that by imposing a deadline on all I/O operations to prevent starvation of requests. It also maintains two deadline queues, in addition to the sorted queues (both read and write). Deadline queues are basically sorted by their deadline (the expiration time), while the sorted queues are sorted by the sector number. Before serving the next request, the Deadline scheduler decides which queue to use. Read queues are given a higher priority, because processes usually block on read operations. Next, the Deadline scheduler checks if the first request in the deadline queue has expired. Otherwise, the scheduler serves a batch of requests from the sorted queue. In both cases, the scheduler also serves a batch of requests following the chosen request in the sorted queue.
BFQ - Instead of time slices allocation by CFQ, BFQ assigns budgets. Disk is granted to an active process until it's budget (number of sectors) expires. BFQ assigns high budgets to non-read tasks. Budget assigned to a process varies over time as a function of it's behavior.
ZEN & ZEN v2 - Based on the Noop, Deadline and SIO I/O schedulers. It's an FCFS (First come, first serve) based algorithm, but it's not strictly FIFO. ZEN does not do any sorting. It uses deadlines for fairness, and treats synchronous requests with priority over asynchronous ones.
MAPLE(8/30) - is based on the Zen and Simple I/O schedulers. It uses ZEN's first-come-first-serve style algorithm with separate read/write requests and improved former/latter request handling from SIO. Maple is biased towards handling asynchronous requests before synchronous, and read requests before write. While this can have negative aspects on write intensive tasks like file copying, it slightly improves UI responsiveness. When the device is asleep, maple increases the expiry time of requests so that it can handle them more slowly, causing less overhead.
Governor Information - CPU:
Interactive - Interactive scales the clockspeed over the course of a timer set by the kernel developer (or user). In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. It is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency. Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above. Interactive is the default governor of choice for today's smartphone and tablet manufacturers.
Ondemand - Ondemand is one of the original and oldest governors available on the linux kernel. When the load placed on your CPU reaches the set threshold, the governor will quickly ramp up to the maximum CPU frequency. It has excellent fluidity because of this high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand was commonly chosen by smartphone manufacturers in the past because it is well-tested and reliable, but it is outdated now and is being replaced by Google's Interactive governor.
Performance - Sets the frequency at the maximum available frequency. This governor always returns UINT_MAX as frequency so that the DEVFREQ framework returns the highest frequency available at any time.
Powersave - Sets the frequency at the minimum available frequency. This governor always returns 0 as frequency so that the DEVFREQ framework returns the lowest frequency available at any time.
Userspace - Sets the frequency at the user specified one. This governor returns the user configured frequency if there has been an input to /sys/devices/.../power/devfreq_set_freq. Otherwise, the governor does not change the frequnecy given at the initialization.
GPU Governors:
Adreno Idler - It is an idling algorithm, an efficient workaround for msm-adreno-tz's overheads. Main goal is to lower the power consumptions while maintaining high-performance. Since msm-adreno-tz tends to *not* use the lowest frequency even on idle, Adreno idler replaces msm-adreno-tz's algorithm when it comes to calculating idle frequency(mostly by ondemand's method). The higher frequencies are not touched with this algorithm, so high-demanding games will (most likely) not suffer from worsened performance.
Simple - An open-source alternative to Qualcomm's closed-sourced governors. Developed by Faux123, it is highly customisable which will allow more fine-grained control over how the GPU scales up and down.
simple_ondemand[/b] - As the name implies, it is a simpler version of the CPU governor ondemand. simple_ondemand will ramp up the frequency when a load is detected. It has a good balance between performance and battery savings.
msm-adreno-tz - The default GPU governor used by Qualcomm for their adreno GPUs. It is based on the ondemand governor but is biased towards performance, therefore it should give better performance in games but less battery life.
Performance - As the name suggests, this keeps your GPU running at the max frequency. This is a governor if you want the best possible experience in games but you don't care about your battery life.
Powersave - Like the CPU governor, this keeps your GPU running at the lowest possible frequency. Best battery life, extreme lag in games.
Userspace - This governor basically allows the user is able to set a desired frequency for the GPU to run at.
cpubw_hwmon - A hardware monitor based governor that attempts to determine bandwidth (BW) needed by CPU and other hardware. Because it samples bandwidth using polling intervals, it has been made to be biased towards performance to compensate for the possible slower response times during heavy loads.
MSM Cpufreq - The MSM CPUfreq governor determines the CPU to DDR bandwidth vote based on the current CPU frequency of all the active CPUs. In other words, this governor scales based on CPU usage which could mean more performance.
Other Information:
Moved Core Control To Kernel - Moved core control from out-of-tree module into the kernel proper. Core control monitors load on CPUs and controls how many CPUs are available for the system to use at any point in time. This can help save power. Core control can be configured through sysfs interface.
Moved Core Control Trace Events To Scheduler
Added A Knob To Disable The core_ctl (Core Control) - The CPU hotplug tests does not work with core_ctl compiled statically into kernel. Provide an interface to disable the hotplug by core_ctl.
Updated the performance is cpufreq
Lots of UPSTREAM changes to cpuidle and schedulers
Some under and overclocks with how the phone idles and returns
Added a State Notifyier
Added CAD Project
Imported Boeffla Wakelock Blocker v1.1.0
Updated Kcal Support
Fixed Various Issues
Low Persistence Fixed For DayDream
Selinux Switcher Between Permissive & Enforcing (Please install the Magisk SELinux Manager)
And a whole lot of other sh*t, view the github to see all the changes
Credit:
@OrdenKrieger
@Unjustified Dev
@Skrem339
Tester:
@kingracer
@KevinX8
@Masterjuggler
@Choose an username...
@docentore
@Infy_AsiX
Disclaimer: I do not and will not take any responsibility towards anything that happens to your phone after flashing.
If you would like to donate a beer or a blunt feel free, its not obligated though! Each donation is appreciate by being added to OP!
​
XDA:DevDB Information
[KERNEL][OREO][AOSP] Schwifty Kernel | Custom | 6/8/17 |, Kernel for the ZTE Axon 7
Contributors
SaintZ93
Source Code: https://github.com/SaintZ13/schwifty_oreo_axon7
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v1
Stable Release Date: 2018-06-24
Created 2018-06-25
Last Updated 2018-06-24

Install Instructions:
Boot To Recovery
Flash Schwifty Kernel
Wipe Dalvik & Cache
Re-flash Magisk
Downloads:
Stable Release: vR5 Changelog (12/12/18)
Download:
https://www.androidfilehost.com/?fid=11410963190603873368
Click to expand...
Click to collapse
MD5: ef8222968aaea32fed85245d53599c56
Kernel Size: 13.6MB
Stable Release: vR4 (Treble & Non-Treble)
Changelog (8/30/18)
Download:
https://androidfilehost.com/?w=files&flid=281523
Click to expand...
Click to collapse
MD5: Treble - 55fb1a7e7dade9f560725f5bc135e4d7
Non-Treble - 69d034f21ba8b39330633c1b96bf8c97
Kernel Size: 13MB
Stable Release: vR3 (Treble & Non-Treble)
Changelog (7/30/18)
Download:
Treble said:
https://www.androidfilehost.com/?fid=5862345805528062503
Click to expand...
Click to collapse
Non-Treble said:
https://www.androidfilehost.com/?fid=5862345805528062511
Click to expand...
Click to collapse
MD5: Treble - f30ef3e8220146331f657195d46bc8b8
Non-Treble - dc055bcc684df594820e741c3e912be2
Kernel Size: 10.6MB
Stable Release: vR2
Changelog (7/3/18)
Download:
https://www.androidfilehost.com/?fid=11050483647474833482
Click to expand...
Click to collapse
MD5: 5f275eb139681e005f28986c6649560b
Kernel Size: 10.9MB
Schwifty Kernel: Initial Release (6/24/18):
Download:
https://www.androidfilehost.com/?fid=674106145207498193
Click to expand...
Click to collapse
MD5: c30d7ed7c4e7b2843f3ae83e9e75509b
ROM Size: 10.9MB

Reserved

Trying this right now, so far it seems to be stable. Battery life seems to be less right now but that may be due to other factors I'm still investigating.

Nice,new kernel.But why should i use this,and not Hellsgate?

Predatorhaze said:
Nice,new kernel.But why should i use this,and not Hellsgate?
Click to expand...
Click to collapse
Although fast, hellsgate kernel hasn't been kind to my device's stability personally speaking.
This could be more stable, since it doesn't seem to add hoards of features (and potential complications with them).

Predatorhaze said:
Nice,new kernel.But why should i use this,and not Hellsgate?
Click to expand...
Click to collapse
Try searching Schwifty kernel on Google, this kernel isn't new If I remember correctly there were great reviews for this kernel on the other device(LG V20). I don't mean that Hellsgate is not as good, I'm just saying this kernel has its own unique advantages(while Hellsgate is a mighty kernel with loads of features and great performance, so it's also no worse)

About DAC
DAC is working in this kernel?

Very nice kernel, it's stable, the battery holds very nicely and it's powerfull, the UI doesn't lag.
Thanks for your work!

is F2FS supported?

leska said:
is F2FS supported?
Click to expand...
Click to collapse
I tried, it seems so. F2FS and encryption working on my device (exfat also).

Good battery life. Fast and smooth. Stable.
Thank u!

Running this kernel for for about 12 hours now. Seems solid and I find my device to be snappier vs HellsGate. Battery life appears to be solid as well.

del

can someone report about battery life? and does this include COFB(Conservative Optimized For Battery), and it optimized for battery ? (Everything from CAD kernel)

Could you please build this for stock B12? Everything except wifi and hotspot works.

hmm on my device the kernel is a real battery killer.. can barely reach 2.5h screen on time where hellsgate gives me double
switching back now...

Guido83 said:
hmm on my device the kernel is a real battery killer.. can barely reach 2.5h screen on time where hellsgate gives me double
switching back now...
Click to expand...
Click to collapse
What kernel/ROM did you flash this over?

EBeatFLA said:
What kernel/ROM did you flash this over?
Click to expand...
Click to collapse
AEX latest build

New build will be coming within the next couple of days guys, stay tuned! Check the github for new changes.