Database Develop

[Kernel][Sense] 2.6.35.14 - Gingertiny-v2 (Updated 04/25/13)

Changelog
Notes on the new interactive governor below.
04/25/13
interactive governor updates from Tinykernel (Galaxy Nexus)
new sysfs path for fast charge - still compatible with incredicontrol
additional TCP congestion scheduler options with a default scheduler of cubic
10/04/12
New interactive governor backported from Incredikernel GB. Smartassv2 still default
Removed rarely used CPU governors
08/10/12
added mamarley's fastcharge USB patch to enable fastcharge without needing to unplug the charger
enabled KSM (Kernel Samepage Merging) - no change needed to make it active
03/11/12
Added Lazy governor - credit to Ezekeel
Enabled Smartass and Conservative governors
02/25/12
Disabled smartass,interactive,conservative governors
Disabled CFQ and BFQ governors as they were found not to be a efficient on flash devices
New I/O scheduler - SIO
New CPU governor - lagfree
smartassV2 is default governor again
Tweaked deadline scheduler for performance
Applied different zram patch, should be more stable, and removed memory tweaks in zram script (have to disable/enable to reset)
12/31/11
Patch kernel to 2.6.35.14
Tweak intellidemand and interactiveX governors for battery life
Ext4 patch for performance
Add ZRAM and swap support and add script to toggle ZRAM - see bottom of OP for more info
12/25/11
Increase min and max voltages by 25 for all non-OC frequencies
Added faux123′s intellidemand governor (thanks faux123!) - similar to ondemand but with screen off
Added imoseyon’s interactiveX governor (thanks imoseyon!) - interactive with screen off
12/01/11
Revert config setting that was causing freezing issues
Allow overvolting up to 1375 for more stability in overclocking
Revert default smartassv2 settings back to those of pre-11/6 kernel
Fix permissions on sysfs which were causing force closes in some apps
Use new ondemand,performance, and conservative governors
11/19/11
Tweak ondemand governor
Interactive governor fix
Update BFQ to v3-r1
Add and enable Tiny Preempt RCU (should perform even better than Tiny RCU)
11/10/11
Adjust smartassv2 scaling (see github for details)
Fix touchscreen issue that occurs on some devices
config: set tiny rcu (lower memory footprint)
add 1152000 and 1190400 CPU frequencies - only try if you're adventurous
various behind-the scenes fixes
11/06/11
Add interactive governor
Add smartass governor
Increase smartassv2 ideal wake frequency to 998Mhz - should help performance (if you don't like, underclock to 768 - this may change in a future release)
Add BFQ I/O Scheduler
HAVS+Sysfs interface (use Incredicontrol or boot scripts - see incredikernel.com and incredikernel thread for more information)
Fixed wifi not starting on certain ROMs such as McTwist - hopefully
11/02/11
Added unified panel driver from incredikernel and gingertiny-v1 for better responsiveness
Added msm_vibrator from gingertiny-v1 for smoother haptic feedback with smartass
Enabled TUN VPN support
10/31/11
Features:
Rebased on HTC official Incredible gingerbread .13 kernel
Audio Boost (Thanks Chad0989 for letting me use your source for this)
USB Fast Charging (Thanks Chad0989 for letting me use your source for this)
compressed kernel further for better support with boot manager
support for 128Mhz as well as overclock up to 1113
3/5 point multitouch support on supported devices
lowered wifi voltage
OC up to 1.113Ghz
Built in modules for cifs, smartassv2, conservative, ext4, ntfs (read only)
HTC's perflock removed
Ext4 driver used to mount ext2/3 filesystems (default in cyanogenmod and incredikernel)
Enabled swap support (need app like swapper from market to utilize)
SD Card and EMMC mount should work properly on all Sense ROMs now.
incorporated some tweaks from incredikernel
support for wifi-n (2.4ghz only - hardware limitation)
Audio Boost and USB fast charging are disabled by default in this version (I don't like audio boost). You can enable audio boost in the same way you enable USB fast charge.
10/23/11
Ext4 driver used to mount ext2/3 filesystems (default in cyanogenmod and incredikernel)
Updated to new OJ driver from Cyanogenmod kernel
[*]Sysfs interface for SVS (can now use incredicontrol) Not working properly
10/15/11
Fixed G-sensor issue (calibration, 3d-home screen, auto-rotate should work now)
10/08/11
Adjusted smartassV2 parameters for better performance
10/05/11
Set smatassV2 as default governor
incorporated some tweaks from incredikernel
added support for wifi-n (2.4ghz only - hardware limitation)
09/29/11
Added smartassV2 (erasmux)
09/20/11
Tweaked smartass governor to resolve reboot issues reported with using smartass (please let me know - it seems better for me so far)
Enabled swap support (need app like swapper from market to utilize)
Enabled compcache support (if ROM has uitility installed I can work on a script, currently I can't get the utility to work)
09/01/11
set max speed to 998 as phone would overclock at boot regardless of setcpu/overclocking app's setting which caused bootloops for phones that couldn't handle overclocking (Thanks Chad for the tip!)
08/31/11
Initial Release
Audio Boost (Thanks Chad0989 for letting me use your source for this)
USB Fast Charging (Thanks Chad0989 for letting me use your source for this)
compressed kernel further for better support with boot manager
support for 128Mhz as well as overclock up to 1113
3/5 point multitouch support on supported devices
lowered wifi voltage
OC up to 1.113Ghz
Built in modules for cifs, smartass, tun, conservative, powersave, ext4
HTC's perflock removed
Bootup frequency increased to 998
Known issues:
Beats will not work. This is not a specific issue with this kernel but rather that the support is not built into the stock kernel. It worked in the port but I'm not sure what needs to be changed.
Incredicontrol force closes when trying to open the HAVS tab. This only seems to happen at boot and clears up. Since it clears up on it's own, I don't think it's a kernel issue though but I'm leaving it on here so people are aware.
*Disclaimer*
Please do not report bugs if you overclock or undervolt/overvolt differently than what is set by default. It adds too many variables. Set CPU max back to 998 and report a bug then if it doesn't go away after that.
I am not supporting the older .10 kernels at this time though if you decide to still use it I may need your assistance to get Beats audio working.
*Note*
1. Just because it's been asked before about what ROMs this kernel supports, this kernel does not need to be built to support any particular ROM but is confirmed to be working fine on many of the most popular Gingerbread Sense ROM by multiple users and several leading devs. If it does not work on your ROM let the dev know first in case it's a known issue.
2. Smartass (v1 and v2) has a built in min speed of 245 and will go to the set min speed only when the screen is off. Due to the nature of the governor, don't use a screen off profile with Smartass. It has been reported to cause issues. If you want a screen off profile use a different governor.
OC voltages are set to the same as 998 Mhz. Sense is a tricky animal when it comes to voltage adjustments. I had about 10x the issues with undervolting on sense froyo as on aosp, but maybe it's because that kernel was undervolted more.
*Important*
If you get random reboots or freezes on the new kernels (10/31 or 11/2), I will need the logs of that:
If it's a reboot grab the file /proc/last_kmsg using adb or root explorer. For adb setup please do a search on xda or the internet.
It would be adb pull /proc/last_kmsg for the adb command.
For root explorer just copy to the sdcard. It's a text file so you can post it online and post the link here or attach to your post when you report the issue.
If it is a freeze try to use logcat and output to a file when you're trying to reproduce it. Google logcat usage if needed. Also grab the last_kmsg after rebooting.
Release kernel found at
incredikernel.com
Update: 11/15/12 - I've added a mirror for my files on goo.
http://goo.im/devs/tiny4579/inc/kernels
Source Code(Dev Only, not flashable)
Github.com Kernel Source
All releases are built from the master branch.
The config for the kernel is in arch/arm/configs/incrediblec_defconfig.
I use the GCC 4.4.3 toolchain for this kernel due to GCC 4.6 causing build issues.
Below is a link to the original tiny-gingersense source which is a hybrid kernel running off code released for the Evo Sense kernel as well as some code from the Froyo Incredible sense kernel. This one uses the master branch as well and the same config filename and toolchain as v2.
Original tiny-gingersense kernel source
Frequently Asked Questions:
Some key differences between smartass and smartassv2 so users can decide which they prefer and learn a bit more about the differences:
Smartass
1. Screen off profile built in maxed at 384mhz.
2. Wakeup frequency is 998mhz.
3. Min screen on is 245mhz.
4. Improved by Chad to run better on our devices.
5. Purely load based, no ideal value.
Smartassv2
1. This is the same exact governor in Erasmux's Nexus One kernel (github.com/erasmux/n1-kernel)
2. Ideal wake frequency is 768 (also default that can be changed).
3. Screen on min is actually 128mhz).
4. No screen off profile.
5. Ideal sleep frequency 245mhz.
6. Improved upon from erasmux's version, not Chad's.
Basically the smartassv2 ideal wake frequency allows the phone to favor a certain speed to attempt to save battery life. It can still go above ideal wake and below ideal sleep so there's no caps on max and min while awake or sleep.
Some tips/info on various governors:
Smartass/smartassv2/interactive:
Use 128 min so the governor can scale as it needs to. Max speed I'd recommend at least 768Mhz.
Ondemand:
Try 128 min and if it lags use 245 min. Max speed I'd recommend at least 768Mhz.
Performance:
Only recommended for benchmarks but speed will always run at max.
InteractiveX:
Same as interactive except it has an auto screen off set to the min. Ideal with 245 min in setcpu but try 128 for battery life but it you have wake lag then set to 245.
Intellidemand:
Based on ondemand with a built in screen off. Any speed settings should be fine.
Interactive:
Some new features with this one. Starting with 10/4/12 release I am using the interactive kernel from Google which features a new kernel option called input_boost.
It is off by default but can be enabled by writing a 1 to /sys/devices/system/cpu/cpufreq/interactive/input_boost. Also there is another parameter for interactive called hispeed_freq in the same location. The hispeed_freq is where the governor jumps to first. Hispeed_freq by default is 614400 to help save battery. In the older interactive governor there was a maxspeed freq which meant the governor was a bit jumpier to the max speed. This should be a good blend of performance and battery.
ZRAM, what is it and how to I add it? (starting officially with 12/31/11)
If you are familiar with swap space in linux or virtual memory in Windows it is a similar concept. Except instead of using the hard drive as swap space it compresses swap space in RAM for faster access times than conventional swap. This will also wear out our storage memory less than typical swapping.
Enable ZRAM is simple thanks to a script built by imoseyon which is provided in the kernel zip file. To enable, use adb shell or download a terminal app and run zram enable. This will persist across reboots (if init.d is setup in your ROM) so if you don't want it anymore run zram disable and it will remove the bootscript and deactivate it.
You need to have root privileges to enable/disable zram. Run the su command in terminal emulator to request root.

Way to go! But I bet this was a headache to put together.
Let me know if you need a beta tester and the slots haven't filled up.

godsmacked4653 said:
Way to go! But I bet this was a headache to put together.
Let me know if you need a beta tester and the slots haven't filled up.
Click to expand...
Click to collapse
Check your PM.

Is this the beginning of a whole slew of custom kernels for the inc ?
How is the battery life on this?

i can test if needed

Exciting stuff...
any idea or have you looked at how difficult it would be to enable 5 pt multi touch in the future? or GPU+?

Hit me up... I'd love to test.

Love to test. Would begging help. Lol
Sent from my ADR6300 using Tapatalk

Ok, got the 5 testers I want. Actually I found 6 so I'm good for now.

tiny4579 said:
Hi all!
Good news! I have successfully initially ported the HTC Incredible kernel to gingersense using the Evo gingerbread source as a base and pulling from the Inc's froyo source code. I have spent significant time over the past few weekends trying to get this work and I have something usable finally. (I never ported a kernel before but am satisfied with what I have here).
Thanks Chad for inspiring me to do this port and giving me pointers along the way!
What works:
1. 3g+wifi
2. all modules from modules thread are built in+cifs added as well (perflock_disable is not needed on this kernel)
3. camera - initially had trouble, it wouldn't boot with camera enabled. 720p video SHOULD work as well
4. artifacting issues should be resolved
5. overclock works (1.13Ghz)
I would like to have some testers prior to releasing it as open beta. I want 4 additional testers, have 1 already. The first 4 to volunteer to test (via PM or this thread) will get a PM with a link to test the kernel. It will flash like any other kernel. I would like to post tomorrow night so please give feedback.
Known issues:
May be overheating issues. Though I cannot confirm issue. Battery temp is fine for me.
It is a port. Not everything will necessarily work 100%.
Haptic feedback and vibration are currently broken. Will look into it.
Github.com Kernel Source
Click to expand...
Click to collapse
try changing the inc-kepad.kl to incrediblec-keypad.kl in the /usr folder of the rom

Damn...
Sent from my ADR6300 using xda premium

And amazing work man!!

runs nice so far...
i do miss haptic

JoelZ9614 said:
try changing the inc-kepad.kl to incrediblec-keypad.kl in the /usr folder of the rom
Click to expand...
Click to collapse
Tried it but no go. Thanks for trying to assist me though.

Checked up on GPU+. It is not needed as the changes needed to implement it have already been done in the stock HTC kernel.
5-point multitouch will be tricky as my panel has never worked with more than 2. I remember Chad trying to get it to work for everyone but it was tricky even for him. I think certain phones will just not work with it. I can see if I can at least enable it and have others test. If you're going to test, make sure that it works currently on say a Froyo Sense ROM or your AOSP ROM of choice first.
Going to bed so no more requests tonight.

Ran through some quick tests and everything looks to be working, and working well. I'm running godsmacked's senseless 2.0 with lp+. Gps locks on quick. Camera, gallery, etc all good. Overclocking stable so far, and definitely makes a notable difference. I will do more in depth testing tomorrow. Thanks for the breakthrough!

baboonsRus said:
Ran through some quick tests and everything looks to be working, and working well. I'm running godsmacked's senseless 2.0 with lp+. Gps locks on quick. Camera, gallery, etc all good. Overclocking stable so far, and definitely makes a notable difference. I will do more in depth testing tomorrow. Thanks for the breakthrough!
Click to expand...
Click to collapse
Is your haptic feedback working with the kernel?

love to be a tester too.

Great job Tiny!! This had to be very difficult to port. Your work is much appreciated.

Tiny, I PMd you about the vibrator, should be an easy fix.
And I would also like to commend tiny for doing the work on this. It has lifted a bit of a burden off of my shoulders since I simply didn't have the time to put work into it myself. He's quite adept and problem solving and was able to continue when he ran into a problem with just a little bit of guidance. I trust that he will put out a good kernel.

[KERNEL][04 APR] GLaDOS V2.11

Aperture Laboratories presents​
GLaDOS V2.11​
The latest innovation in human-smartphone interaction. Our scientist have shown in extensive tests that humans operating our kernel on their devices experience 67% more joy in life while simultaneously the likelihood of being maimed or killed by falling space debris is significantly reduced. Also preliminary human trials indicate that it might offer some protection against lethal dosages of gamma radiation and blows to the head with a rod-like object.
Features:
Based on stock Android kernel 3.0.8 IMM76D
CPUfreq governor 'lazy'
Live OC version 1
Custom Voltage version 1
Battery Life eXtender (BLX) version 1
Power saving state DEEP IDLE version 2
Touch Wake version 1
Backlight Dimmer (BLD) version 3
Backlight Notification (BLN) version 9
Brain **** Scheduler (BFS) version 0.357
SLQB memory allocator
Voodoo Color version 2
Voodoo Sound version 10
CIFS
TUN
Bigmem (+20 MB more available RAM)
USB OTG build 5
Download:
http://goo-inside.me/devs/aperture/GLaDOS-NexusS (thanks to goo-inside.me for hosting)
Always make a backup of your /efs/ directory (http://forum.xda-developers.com/showthread.php?t=1138873) before installing custom kernels or ROMs.
During installation the cache partition, Dalvik-cache and modules, init.d scripts and bootsounds from previously installed kernels are cleaned.
Source code:
https://github.com/Ezekeel/GLaDOS-nexus-s/tree/glados
Do not use profiles, they are unnecessary and only lead to instabilities.
If you experience any problems and are on a nightly or kanged ROM, try the latest stable version of that ROM first. I will not give support or answer any questions if you do not try this before reporting a problem with the kernel.
If you experience stability problems like reboots, freezes, FCs and SoDs and you did OC or UV, first try changing back to the stock settings. If this solves the problems, your OC/UV configuration is not stable. There are some indications that OC/UV settings which run fine at high battery charges might still cause problems at lower battery charges. So to be safe always check that your OC/UV configuration runs fine at low battery like 5%.
I do not offer support/help/recommendations on OC/UV. If you decide to do so and your device is unstable you are on your own. Check http://forum.xda-developers.com/showthread.php?t=1335429 for help.
If you experience the problem that the DEEP IDLE state is not properly used (according to the idle_stats), read the last section of http://forum.xda-developers.com/showpost.php?p=18299324&postcount=1.
When reporting a bug always include information about your ROM and hardware model. Also be as precise as possible when describing the problem. Just because a single person is experiencing a problem, it does not mean there actually is a problem with the kernel. I always wait until at least one other person can confirm the issue before I look into it. So if you see someone posting a bug report, do not be shy and feel free to confirm the issue or if you do not have the problem let me know that too.
When asking for a feature you would like to see implemented in GLaDOS always provide a link with information about this tweak and preferably also a link to the source code.
Aperture bootanimation courtesy of rascarlo (www.twitter.com/rascarlo)
For users unfamiliar with init.d scripts I recommend NSTools by arifhn (http://forum.xda-developers.com/showthread.php?t=1333696) for managing the various tweaks.

Changelog
GLaDOS-V2.11
Added kernel patches for Android 4.0.4 update.
Fixed bug with Touch Wake.
The kernel installer no longer modifies the ramdisk for adding init.d support.
GLaDOS-V2.10
Added USB OTG build 5 by sztupy.
Fixed small bug in Custom Voltage.
Fixed bug in Live OC.
Changed to new bootanimation by Rascarlo (many thanks!).
Changed default V1 gamma values for Voodoo Color to stock settings.
GLaDOS-V2.9
Fixed two small bugs in LiveOC.
Fixed small bug in Lazy.
Reduced display frequency back to stock settings.
GLaDOS-V2.8
Fixed a bug in LiveOC.
Fixed optimized compiler flags.
GLaDOS-V2.7
Fixed TouchWake issue of long powerkey presses causing the touch controls to be disabled without delay on next screen off.
For BLN the blink interval and blink time can now be adjusted in the sysfs interface. Also BLN is disabled by default.
For lazy the sampling rate is initialized to a default of 15000.
GLaDOS-V2.6
Fixed the problem of the CAM module being active all the time preventing DEEP IDLE from being used.
GLaDOS-V2.5
Fixed bug.
Removed several unnecessary kernel drivers and features.
Removed kernel debug and logging features.
Included logger as a module.
GLaDOS-V2.4
Fixed bugs in Live OC.
GLaDOS-V2.3
Fixed the freeze/reboot problems when changing the frequency limits.
GLaDOS-V2.2
Removed the limit of the minimum frequency to 200 when the GPU is active.
Preliminary bandaid to DEEP IDLE compensating for various bugs in ROMs.
GLaDOS-V2.1
Added Voodoo Color version 2 and Voodoo Sound version 10.
GLaDOS-V2.0
Update to Android kernel 3.0.8 for ICS 4.0.3 IML74K.
GLaDOS-V1.12
Fixed the camera problems caused by Bigmem (increases available RAM by 21MB now).
GLaDOS-V1.11
Added Bigmem option (increases RAM available for the system by 26MB).
GLaDOS-V1.10
Added DRAM scaling to Live OC.
Flash memory I/O tweaks.
Added Tiny Preemptive RCU.
Updated the optimized CRC32 algorithm.
Removed CFQ I/O scheduler.
GLaDOS-V1.9
Added OC frequency states 1.4GHz and 1.2GHz.
GLaDOS-V1.8
Fixed the problem of the touchkey backlight lighting up when touched while the screen is off.
Increased display frequency to 72Hz necessary to achieve 65fps.
GLaDOS-V1.7
Fixed the increased battery drain while in SLEEP when DEEP IDLE is enabled.
Fixed the problem on the NS4G of DEEP IDLE not being used while 4G is enabled.
GLaDOS-V1.6
Disabled most logging and debugging kernel config options.
Included logger and TUN as modules.
During installation the cache partition, Dalvik-cache and modules, init.d scripts and bootsounds from previously installed kernels are cleaned.
Removed '98touchscreen' init.d script.
Aperture bootanimation and -sound courtesy of Euphorie (http://forum.xda-developers.com/showthread.php?t=1061627).
GLaDOS-V1.5
Fixed problems with setting voltages and min/max frequency with SetCPU.
Fixed problems with the vibrator and DEEP IDLE.
Improved stability of wireless connection.
GLaDOS-V1.4
Updated to latest toolchain arm-2011.03-41
Optimized compiler flags
Added optimized RWSEM
Fixed BLD bug for i9023 of the touchkey backlights not getting re-activated on touch
Changed to advanced TCP congestion scheduler VENO
GLaDOS-V1.3
Improvements to JHash.
Improvements to CRC32.
Fix memory leak in CPUfreq stats module.
Removed PMEM. I do see any improvement regarding the available RAM, but removing unused code is never a bad idea.
GLaDOS-V1.2
Fixed 'Screen v1 gamma hack' not working for Voodoo Color.
GLaDOS-V1.1
Fixed BLN problems for i9023.
GLaDOS-V1.0
Initial release.

Oh this is going to be good.
...Thanks E
Sent from my Nexus S 4G using xda premium

oh man... downloading now
thank you so much for providing this!

Stock android uses deadline scheduler or VR?
A bit off topic, but did anyone ever toy with SIO, NOOP and CFQ on Nexus S?

Wow
Testing right know

can i flash this on my rooted stock 2.3.6? that is the latest for my country.

Ezekeel's own kernel?
Ezekeel's own kernel?!
I knew you have only provided kernel devs with MODs.

Very tempting... Will leave it a few releases before I jump from Matr1x but expecting this to be very good!
I'd be interested in seeing what people's battery life is like on this kernel compared to others, as that's the main selling point for me!

just ran a quadrant benchmark, ~1000 point increase from franco's 06 kernel on carbon c02 rom with 110 liveoc

i'm try ...

v3rk said:
just ran a quadrant benchmark, ~1000 point increase from franco's 06 kernel on carbon c02 rom with 110 liveoc
Click to expand...
Click to collapse
so its better than franco's? and does it include the latest deep idle fiX?

Finally a kernel of a master hehe
Sent from my Nexus S using xda premium

Oh em gee. Here we go!
Sent from my -=Nexus MV=- powered Nexus S c",)
--
MarkVis

After flashing no more lights in soft keys
Edit:
Solved

thegtfusion said:
so its better than franco's? and does it include the latest deep idle fiX?
Click to expand...
Click to collapse
lol
read up who made deepidle-fix. and all those other kernel-tweaks. this kernel comes from the horse's mouth so to speak, or how this is said in English.
now let's see if it's stable.

Yusei said:
After flashing no more lights in soft keys
Click to expand...
Click to collapse
Use bln app to see if it's enable.

MarkVis said:
Oh em gee. Here we go!
Sent from my -=Nexus MV=- powered Nexus S c",)
--
MarkVis
Click to expand...
Click to collapse
If i am in you, I'd have chose which kernel to include in next nexus mv release
Inviato dal mio Nexus S

report: Oh yeah this is awesome syrup, my phone loves it.
Edit : everything good on this side.
Sent from my Kush'd Google Nexus S 4G using xda premium

Ezekeel, can you put this kernel taking around 65fps in 3D graphics globe?
Btw, this rocks.

[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][9.0] Extended kernel v1.5

Extended kernel, for Android 9.0 ROM's (ks01lte).
Disclaimer:
use this kernel at your own risk. Flashing it without any knowledge of what you're doing may brick your device. I'm not responsible for any software/hardware damage.
Click to expand...
Click to collapse
only Pie is supported.
Features/Changelog:
v1
built with 4.9.x-sabermod GCC toolchain
* Custom CPU governors: Nightmare, Alucard, and Intelliactive.
* GPU: Adreno idler by arter97 disabled by default for better responsiveness, Simple GPU governor by faux123.
* Sound Control V3.
* Screen: KCAL support for post processing control [v2].
* Custom Schedulers: Fiops, Fifo, VR, SIOPlus, Tripndroid, ZEN.
* USB/AC Fastcharge V1.3.
* Optimizations: reducing the amount of debug logs!!, add clean Ramdisk files.
v1.5
* Built with the Bleeding edge GNU GCC 8.2.1
* BACKPORT: Power Efficient Workqueues from Kernel 3.10
* Add Link Time Optimization support v3
* CPU Underclock and Overclock: 268MHz to 2496MHz
* GPU Underclock and Overclock: 100MHz to 600M
* Add New Custom CPU governors: Elemental-X and zzmoove.
* Enable KSM and and support for UKSM
Downloads
MEGA
Thanks to:
@kyasu
@jprimero15 aka Lolz-Kernel
and all the authors of commits in Extended kernel github repo!
XDA:DevDB Information
Extended kernel, Kernel for the Samsung Galaxy S4
Contributors
darkness
Source Code: https://github.com/1bdellatiF/platform_kernel_samsung_msm8974
Version Information
Status: Beta
Current Beta Version: v1.5
Beta Release Date: 2019-07-20
Created 2019-07-20
Last Updated 2019-08-01

Reserved

Reserved +

Bóng tối đang đến

Is there a zzmoove governor in this kernel?

Will test for week with intelliactive governor and NFS magisk module. Will update again after a week. Thanks for the kernel!
AOD fixed by wiping cache and dalvik-cache

@darkness I just found this thread. If you are interested in adding more govs, I have the source to add the following (the below list includes default ones as well) to the Havoc-OS kernel, ie @kyasu LOS Kernel
==================CPU==================
abyssplugv2
arteractive
badass
bioshock
conservative
conservativex
dancedance
darkness
dyna-interactive
electroactive
impulse
intelliactive
intellimm
interactive
interactivex2
lazy
lionheart
nightmare
ondemand
ondemandplus
optimax
pegasusq
performance
powersave
slim
smartassH3
smartmax
tripndroid
uberdemand
userspace
wave
==================IO==================
bfq-iosched
cfq-iosched
deadline-iosched
fifo-iosched
fiops-iosched
noop-iosched
row-iosched
sio-iosched
sioplus-iosched
tripndroid-iosched
vr-iosched
zen-iosched
Click to expand...
Click to collapse
XerusKunZE said:
Is there a zzmoove governor in this kernel?
Click to expand...
Click to collapse
I have seen a lot of people get excited about ZZMove. I think it is a LOT of effort to configure correctly, and if not configured correctly its really bad. And on top of that, I think the true battery saving advantages are over rated as compared to if you get Doze working correctly.

XerusKunZE said:
Is there a zzmoove governor in this kernel?
Click to expand...
Click to collapse
New build is available v1.5
New Custom CPU governors: Elemental-X and zzmoove.

DiamondJohn said:
@darkness I just found this thread. If you are interested in adding more govs, I have the source to add the following (the below list includes default ones as well) to the Havoc-OS kernel, ie @kyasu LOS Kernel
I have seen a lot of people get excited about ZZMove. I think it is a LOT of effort to configure correctly, and if not configured correctly its really bad. And on top of that, I think the true battery saving advantages are over rated as compared to if you get Doze working correctly.
Click to expand...
Click to collapse
Which CPU governor has the minimum battery consumption

darkness said:
Which CPU governor has the minimum battery consumption
Click to expand...
Click to collapse
If you want the ABSOLUTE min battery consumption without compromise, then the Gov does not really matter. Simply set your max CPU to the lowest frequency available.
The real practicality is about selecting a gov that provides YOU the best compromise for how YOU personally use your phone. eg I don't use my phone for gaming, while others might.
My personal experience is that there are two main paths for battery consumption. Screen on and screen off. Screen on is heavily affected by Gov, so the most conservative you can bear. And if you are really committed for small gains, adjust the ramp-up etc
see:
https://forum.xda-developers.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957
https://forum.xda-developers.com/showthread.php?t=1767797
https://forum.xda-developers.com/nexus-4/general/guide-android-governors-explained-t2017715
For screen off, then Doze becomes the controlling factor, BIG TIME! I got my phone into doze in 30 sec of screen off, and the battery consumption is brilliant!
To investigate your current state, see:
https://forum.xda-developers.com/showpost.php?p=79135309&postcount=74
That post and the following one shows the difference how my phone is either screen on or in Doze. As compared to a LOS device which sits in maintenance (a higher battery state) for some time after the screen is off.
Doze's deep-idle is your batteries lowest power state, apart from off
PS, not that it means anything, I personally run Tripndroid CPU Gov (and sched) based on how it is described and from personal checks where it appears to like the lower frequencies while still staying very responsive. It jumps around a bit which to me means it is attempting to find the the lowest appropriate freq, while some act more like a min-max, ie not the lowest appropriate, but min when not in use and max when in even the lowest use. I don't notice any lag.

share the link resurrection remix v7.0.2 ks01ltexx

onenett said:
share the link resurrection remix v7.0.2 ks01ltexx
Click to expand...
Click to collapse
is there a please in there somewhere?
https://github.com/ResurrectionRemix/platform_manifest

I tried version 1.5, but it got stucked on splash screen and goes to download mode. Sometimes the system boots fine, but as soon as I shutdown my phone the problem persist again... I tried to reflash my rom and reflash the kernel but the same thing happens. I tried to wipe dalvik cache and cache, still the problem is the same. I'm using Havoc 2.7

XerusKunZE said:
I tried version 1.5, but it got stucked on splash screen and goes to download mode. Sometimes the system boots fine, but as soon as I shutdown my phone the problem persist again... I tried to reflash my rom and reflash the kernel but the same thing happens. I tried to wipe dalvik cache and cache, still the problem is the same. I'm using Havoc 2.7
Click to expand...
Click to collapse
A last_kmsg may help the dev decipher where its failing.

DiamondJohn said:
PS, not that it means anything, I personally run Tripndroid CPU Gov (and sched)
Click to expand...
Click to collapse
I've switched to the Impulse CPU Gov, as it appears to quickly scale down and like the lower frequencies and switch off (hotplug) other cores, while still being very responsive ie I haven't noticed any lags. It was created by the main dev who worked Oreo crDroid.
I *may* of also noticed that when plating music with the screen off, sometimes there was a stutter when using Tripndroid and switching songs, and I haven't had this occur with Impulse, as yet. I also have an app that momentarily switches the screen on between songs, to display the cover art, which I am sure wouldn't help.
It could be a random thing, but it looks good thus far.

just flashed, i do see more options for cpu frquencies but i don't see gpu frequencies like 100mhz or 600mhz???

Latest one cause bootloop in Havoc 9.0

Hi, i has benn flased last reléase, bootlock after reboot, somebody have this bug?
Thanks.

Samsung S4 GT-i9505 Kernel
Hello, can anyone tell me where I can download the most updated Kernel for S4 GT-i9505?

Hello to everyone
Would this kernel work with android 10 ?