Database Develop

[KERNEL] [AOSP/CM] [2.6.32.24] [HAVS][BFS][OC][UV] KiNgxKernel #2/#2 "Bout Time"

[KERNEL] [AOSP/CM] [2.6.32.24] [HAVS][BFS][OC][UV] KiNgxKernel #2/#2 "Bout Time"
I DO NOT have an HTC Incredible but will continue to cook kernels for it. My girlfriend has Verizon however, and I am saving for two devices, one of them being an HTC Evo. Any donations go toward my devices. Bear with me until then please
DO NOT FORGET TO READ THE ENTIRE POST ON MY SITE, THERE IS IMPORTANT INFO
So you guys asked and asked, and now you shall have your requests answered. I decided to port my kernel over for AOSP, CM, and Ruby ROMs. The cool thing about this is that all the other features my sense kernel has, this has with one exception: It works on vanilla ROMs! So any ROM you may like to use that does NOT have sense, this will work with. It has all the tweaks that you would need, without loss of stability. The first release is a BFS kernel, but I am sure there will be CFS kernels to come. BFS is functioning to well to pass on these new uniprocessor phones to pass up. At any rate, post any bugs with a logcat, and most importantly, enjoy!
This is compatible with any 2.2 AOSP or CM6 ROM
Code:
Also, a little info on HAVS and AVS:
The purpose of HAVS is to minimize the power used by the CPU by determining
and setting the optimal voltage. At the same time, the maximum voltage by
which HAVS can scale to is fixed to a specified voltage depending on the
CPU frequency in order to prevent scaling to a higher voltage than what is
normally used at a specified voltage. The optimal voltage is actively determined
for each frequency and temperature. HAVS actively adjusts the CPU voltage as the
CPU frequency and temperature changes.
Code:
While we are at it, some info on BFS:
What is BFS(Brain **** Scheduler):http://ck.kolivas.org/patches/bfs/sched-BFS.txt
FAQS about BFS:http://ck.kolivas.org/patches/bfs/bfs-faq.txt
Ang3lmack said:
Instructions, create android.tether folder on root of sd card and drop this file into it http://www.mediafire.com/?nh7spjjb46fzfww then install this version of wifi tether http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_2.apk , I take no credit for the fix, just copied from another thread
Incredible
Click to expand...
Click to collapse
ENJOY!
Credits: Cyanogen,, Koush for his any kernel .zip, and HTC for their kernel source code
Download: BFS Kernel #2 & CFS Kernel #2[/URL] Date: 10/28/10 1:10 AM PST
If you Like my work follow me on twitter:
All my code is on github:
I am not responsible for anything that happens to your device
ChEeRs

CFS Changelog
Kernel #2
- Kernel now patched up to 2.6.32.24
- Bug fix causing battery drain
- Reverted some UV levels causing instability
- CFS updates
* Implement different treatment for idle shares
* Fix CFS 'Over-scheduling' bug
* sched: Fix granularity of task_u/stime()
* sched, cputime: Introduce thread_group_times()
* sched: Fix select_idle_sibling()
* sched: cpuacct: Use bigger percpu counter batch values for stats counters
* sched: fix racy fair sched*trq
* sched: Cleanup select_task_rq_fair()
- EXT4 support now!
- EXT4 compiled as a module
- EXT4 filesystem bug fixes
* ext4: Fix potential quota deadlock
* ext4: Fix BUG_ON at fs/buffer.c:652 in no journal mode
* ext4: fix memory leaks in error path handling of ext4_ext_zeroout()
* ext4: Prevent creation of files larger than RLIMIT_FSIZE using fallocate
* ext4: Ensure zeroout blocks have no dirty metadata
* ext4: Consolidate inlign pages
- CIFS bug fixes for stability and security
* cifs: Fix a malicious redirect problem in the DNS lookup code
* cifs: don't attempt busy-file rename unless it's in same directory
* cifs: remove bogus first_time check in NTLMv2 session setup code
- Netfilter IPv6 bug fixes
- Memory leak fixed in firmware
- CPU Governor fixes
- Mutex bug fix
* mutex: Don't spin when the owner CPU is offline or other weird cases
- Using xen_clocksource_read now for scheduler (part of 2.6.32.18 patchset)
- vmscan: raise the bar to PAGEOUT_IO_SYNC stalls
- SLAB fixes
- drm: Only decouple the old_fb from the crtc is we call mode_set*
- arm fixes: arm: fix really nasty sigreturn bug
- RDS memory leak fixed
- mm: page allocator: update free page counters after pages are placed on the free list
- mm: page allocator: calculate a better estimate of NR_FREE_PAGES when memory is low and kswapd is awake
- So much more, check my code if you please
Kernel #1
- First AOSP CFS kernel
- Patched up to Linux Kernel version 2.6.32.21 (all commits an android kernel would need, no extra bloat) *All credit goes to the linux project, check my github for authors please*
- Bug fix causing battery drain
- CFS updates
* Implement different treatment for idle shares
* Fix CFS 'Over-scheduling' bug
* sched: Fix granularity of task_u/stime()
* sched, cputime: Introduce thread_group_times()
- EXT4 support now!
- EXT4 compiled as a module
- EXT4 filesystem bug fixes
* ext4: Fix potential quota deadlock
* ext4: Fix BUG_ON at fs/buffer.c:652 in no journal mode
* ext4: fix memory leaks in error path handling of ext4_ext_zeroout()
* ext4: Prevent creation of files larger than RLIMIT_FSIZE using fallocate
* ext4: Ensure zeroout blocks have no dirty metadata
* ext4: Consolidate inlign pages
- CIFS bug fixes for stability and security
* cifs: Fix a malicious redirect problem in the DNS lookup code
* cifs: don't attempt busy-file rename unless it's in same directory
* cifs: remove bogus first_time check in NTLMv2 session setup code
- Netfilter IPv6 bug fixes
- Memory leak fixed in firmware
- CPU Governor fixes
- Mutex bug fix
* mutex: Don't spin when the owner CPU is offline or other weird cases
- Using xen_clocksource_read now for scheduler (part of 2.6.32.18 patchset)
- vmscan: raise the bar to PAGEOUT_IO_SYNC stalls
- SLAB fixes
- SO much more, tired of typing
BFS Changelog
Kernel #2
- BIG update!
- Performance boost!
- More stable due to BFS overhaul
- Patched up BFS scheduler to BFS 330
- Patched in *NEW* BFS TEST patch that applies over 330 (from CKolivas himself)
* Major overhaul of queued changes
* Micooptimise multiplications/divisions to be shifts where suitable
* Drop the "skip_clock_update" concept as we update the niffies each time we
update the rq clocks, thus we want to update it more often
* Add a local last_task variable to each runqueue which keeps a copy of the
last non-idle task that ran on this CPU. Use this value to determine that a
task is still cache warm on this CPU even if it has run elsewhere in the
meantime. This improves throughput on relatively idle systems with >2 logical
CPUs
* Change SCHED_BATCH tasks to refill timeslices and reset deadline every time
they're descheduled as they've been flagged as latency insensitive, likely
fully CPU bound tasks. This should decrease the impact running batch tasks
has on other tasks
* Bypass rechecking deadline when we know that prev will run again in schedule
* Change all deadline accounting to use nanosecond values
* Rework try_preempt
* MUCH MUCH more check my patch code if you please
- Voltage tweaks for stability
- Compiled with toolchain optimizations
- Neon optimizations this time around
- Now based off of NEW fresh source code from HTC
- Default CPU governor changed to 'Interactive'
- Numerous small changes I won't list that htc did
- Removed bloat from kernel
- Merged all my commits into the new code so
- Still using BFQ I/O scheduler
- Voltage regulator changes (now using the correct one)
- HAVS code fixed (HAVS now functioning correctly!)
- HAVS code cleaned up
- LONGER battery life due to HAVS functioning correctly
- EXT4 now compiled as a module for those with bad boot.img sectors
- Minor patches to the BFS scheduler (the big one is wip)
- Fixed memory leak in vmem
- Voltage tweaks
- Kernel size squashed a bit
Kernel #1
- First kernel release
- Synced with the latest code drop from htc
- BFS Scheduler patched up to BFS330
- Applied and tweaked BFS330 test patch on top
- Voltage tweaks for battery life (245Mhz is $$$)
- Higher clock speeds will be MUCH more stable now! (1.113=ez)
- Battery charging tweaks to allow your battery to charge faster
- Be sure to wipe dalvik cache before flashing
- Compiled with neon arm optimizations
- Included tun.ko for OpenVPN support
- EXT4 support
- Underclocked for long battery life
- Using AVS voltage scaling system
- Compiled with neon optimizations
- ALL CPU governors supported
- Interactive governor supported
- Interactive governor set to default
- Using CFQ I/O scheduler
- BFQ I/O scheduler supported
- Quadrant scores are high, even if you are NOT OC'ed testers have reported
- Much much more I need to add, it is a first kernel release

Gonna have to try this for sure.
Sent from my ADR6300 using XDA App

OMG This is freaking EPIC!
*refreshes page like the maniac I am.

Just got out of my work to post this up for you guys
Time for a breather now
It's live

haha, thanks King, I've been waiting for this!
One little bug though, while installing from nandroid it says something like:
blah blah blah
blah blah blha
blah HTC Evo
blah blah
haha, might want to fix that sometime xD

Switching roms again to try this!
Sent from XDA App
Virtuous 2.6 Rom
#4 King Bad F*cking **** Kernel
Revolution
8"

Hell yesssssss.

Awesome!!!!!! Thank You!!!
Sent from my ADR6300 using XDA App

Not too shabby...
Not as insane as some of the scores I've seen flying around the forums, but overclocked to top speed this isn't too shabby for the very first Quadrant run...

Trying it out now on Ruby. I LOVE your work, King!

Interactive governor, 1.13ghz, Ruby 1.1.1
Excellent work. Just need to see how well the battery lasts now. More beer money to you my friend.
This + Ruby = EPIC
Gotta see how this runs on CM6

I'm assuming based on md5sum that the beta you had posted is slightly different than this release... i had one reboot (at idle) on the beta... just updated to this release... keep up the great work.

WTF??? Over 1600 without overclocking? Witchcraft! I wouldn't believe it if I didn't see it on my own Dinc.
Nice job, bro.

Wow, just hit 1859 on quadrant @ 1.15!

can someone use this on ruby and see if BT audio connects? (ie some headphones). Not BT Phone audio, but music...
on the normal one it doesn't, i'm curious to see if it does with this one. about to load it up on cm6 nightly...

Ok, sorry for the NOOB-ish question but, I decided to try out Jager ROM and I am really liking it. I want to try a different kernel but I am not sure which one to use. The regular King's kernel or this AOSP based one?
How can I tell which ROM's are AOSP-based vs. something like SkyRaider? I was using SR and KK BFS kernerl and that was a great combo!

WOW, this is awesome!!! Just hit 1852 quadrant and 40.343 linpack set at 1190 on performance. First try on Cyanogen 6.0.2. I have screen shots on my phone but haven't figured out how to post them here yet, lol.
The first boot after recovery had a system force close and I didn't think it would work, but after a battery pull, my phone started normal.
Thanks for the wonderful kernel! If this is the first, I can't wait to see what the future brings!

That dude is the king! @1.19GHz
Sent from my ADR6300 using Tapatalk

Could I use this with the latest Vanilla Skyraider?

[KERNEL][GPL][8 DEC] franco.Kernel | BLX | DEEP IDLE | LIVEOC

I've written many new kernel threads, so I'll just try to make this one simple, easy and light to read.
So, let me give you a little background on me: most of you don't know me as I only bought this device few days ago, but I'm a kernel dev for two other phones, the LG P500 and the Ideos X5. Worked on both .32 and .35 trees and my works became very popular, which can be seen by following the links in my signature - specially in the P500 community.
There are plenty of kernels to choose already, so why release another one? Simply because what I have to offer none of the other kernels had. What do I bring? Performance. How do I achieve that? Check the changelog and you'll understand...but not yet, lemme finish!
I have to say this: this kernel is based on KalimochoAz sources, so every changes up to his last pushed sources it's his job, so credits to him, I take no credit from his job.
I didn't start this kernel project for recognition or anything like that, I just want to share what I did for myself, maybe someone will find it useful
So let's get started, below you'll see what I changed on top of KalimochoAz source:
8th December
* Deep_idle code deleted, and re-added. Everything is exactly as Ezekeel has in his kernel, this might, or might not help with the data loss and whatever. If you still have problems please consider disabling deep_idle and see if it helps
* Deep_idle is off by default - changeable with NStools
* Calibrate.c reverted back to the .35 implementation
* Updated CRC32 library to the latest implementation directly from its creator
* Fsync disabling code deleted and re-implemented with a different implementation
4th December
Too many changes, so I'll be just brief and simple:
* CFS autogroup tweaks
* CFS optimizations
* Readahead values automatically calculated by the kernel for the optimal performance
* Several optimizations to lib files
* Added dm-cache (http://visa.cs.fiu.edu/ming/dmcache/)
* More stability
* Much more...
25 November
* Fsyncs disabled - more IO speed, more battery (less IO operations)
* Compiled with the optimized Mjolnir toolchain
* Added 1,2ghz step
* New default colors for the SAMOLED screens
* Cgroup: speed up access to cgroupfs mounted entries in /proc/mounts
* One or two more minor tweaks and optimizations
23 November
* No more BFS code and BFS builds. I want to make sure this is stable enough. If you want BFS compile it yourself. I hope this fixes the data/gsm drops
* Minfree settings unlocked forever
* Readahead value bumped to 1024
* BLN/touchwake fix
17 November
* Patched up to the latest deep_idle version from Ezekeel
* SAMOLED colors tweaked, should be a lot better now
* Few stability updates and reverts to ensure everything is up and running without issues
* Interactive governor added again
* Interactive patched up with around 10/15 patches
* Minor tweaks and optimizations
13 November
* Based on the latest testing builds, which includes:
* Some defconfig options change for a more leaner kernel
* Delete two cflags to ensure maximum Hummingbird performance
* Internal sdcard remount bug fixed
* Minfree settings unlocked by users demand
* Deep_idle implementation changed (it's the same that I used in the last testing version)
* Added latest deep_idle patch that when the phone vibrates it uses the TOP=ON idle state
* Removed obsolete screen dimmer
* Updated BLN to latest v9
* Lazy governor changes based on morfics lazy changes
* Remove Big Kernel Lock tracing
* Some stability patches from the kernel mainline
8 November
* PMEM disabled as herring doesn't use it - this way we recover 12,5mb ram
* Ext4 mounted with special flags directly on the kernel source - more performance without needing init.d scripts
* Writeback settings now working correctly and are not overwritten by the ramdisk
* Minfree settings are now correctly set and are not overwritten by the ramdisk
6 November
* Latest deep_idle bugfix from Ezekeel
* Added Ezekeel's custom_voltage mod. For more info about it visit the respective thread. Yes it's compatible with SetCPU, maybe with Proton too, I didn't test it
* Added back BLD, touch wake and screen dimmer
* Improved CRC32 algorithm - it's used for many kernel functions
* CFS version: Cgroups: introduce timer slack subsystem - Provides a way of tasks grouping by timer slack value. This functionality is useful in mobile devices where certain background apps are attached to a cgroup and minimum wakeups are desired
3 November
* Latest deep idle bugfix from Ezekeel
* Offering two separated downloads, one CFS and another BFS. Don't ask me which one is better, try it and see, I'll be really mad if I get questions like that
* Idle_stats show 0 in every field - don't worry about that, it happens because of my cpu_idle 3.1 backport, but I assure you deep idle is working. Again I'm not answering questions like "WHY IS IDLE STATS 0?!?!? HALP PLZ".
* 'screenoff_maxfreq' is disabled by default. If you want that behavior write this in the terminal: echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/lazy/screenoff_maxfreq
2 November
* Newest deep idle bugfix from Ezekeel
* Reverted back to CFS because stock users had mounting problems with the sdcard and some users had data/wifi drops and I don't want that
1 November
* First and entirely BFS kernel with the newest 0.413 version
* Optimized the tunable BFS parameters for extra interactivity and smoothness
* More debugging disabled - I'm pretty sure 99% of the debugging flags are now disabled
* All the latest bugfixes and implementations from Ezekeel, including live_oc up to 150, lazy maxfrequency_screenoff enabled by default and all the other small fixes to ensure maximum stability
* Small changes to the lowmemorykiller
* Added optimized RWSEM algorithm
* Added some minor improvements and tweaks
* Sorry devs that wanted logcat, it's still a module because I suspect I'll have to update this build again with some extra fixes from Ezekeel in a very near future thus not making much sense to release two kernels now, one with logcat on and other with it off because that takes time to compile. If you desperatly need logcat go to my .config and change CONFIG_ANDROID_LOGGER=m to CONFIG_ANDROID_LOGGER=y and recompile it
27 October
* Latest deep idle and live oc bugfix from Ezekeel - should fix that extra battery drain reported by some users
* Changed lowmemorykiller.c - minfree settings already incorporated in the file. Settings kanged from morfic's tweak file, thanks
* Add cleancache - driver to cache clean pages
* Fixed ext4 disk write performance regression
* Small power management fix to back off suspend if repeated attempts fail - avoid continually trying to suspend in situations in which a driver is repeatedly rejecting suspend or a pending wakeup interrupt is not handled, burning CPU in the continuous suspend attempts
* Lib file added for the users where BLN didn't work
* Logcat module added inside /system/modules. If you want to use logcat just load the module with insmod
24 October
* BLX added again by default and patched up to the latest fix from Ezekeel
* Deep idle patched up to the latest fix from Ezekeel
* Live OC added and patched up to the latest fix from Ezekeel. To overclock you need to do this in the terminal or in an init.d file: echo 110 > /sys/class/misc/liveoc/oc_value. The 110 value means that both cpu frequency and bus frequency will be increased by 10%. You can increase this value as much as you want, as long as you increase the voltages otherwise the device won't handle it, but that's obvious.
* Changed dirty_writeback values from morfic to increase smoothness
* Overclock frequencies removed. The device is fast enough with 1000,800,400,200 and 100 frequencies. If you want to overclock use Live OC, it's enough to make it fly
* Conservative governor tweaked - smooth as butter
* Removed a ton of debugging ****
* Deadline I/O scheduler made default - after much testing it seems to produce the best and more regular results
* Swappiness disabled
* For more information visit my github, this are the most important changes
21 October
* Latest Deep idle bugfix from Ezekeel
* sched: disable GENTLE_FAIR_SLEEPERS
* Remove few obsolete governors
* BLN fix for MIUI users - now it should be propely set and full working
* Just 3 more tweaks:
PM QoS: Correct pr_debug() misuse and improve parameter checks
mmc: core: put eMMC in sleep (cmd5) mode before suspend
vmscan: prevent background aging of anon page in no swap system
19 October
* UV **** is fixed, SetCPU and Proton should work fine now
* Config_HZ increased to 1000 by request of an user
* Small tweak to VR
* Compiled with special Cflags from netarchy
* Calibration tweaks for touchscreen from netarchy
18 October
* Update cpu freq. to allow UV interface - you can modify the voltages on the fly going to /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table with an easy layout
* Auto BLN added again - it works now out of the box without the need of an extra app
* Add Lazy governor by Ezekeel
* config edited again, removed alot of **** options that are not needed at all - this way the kernel is even leaner
* cpu_idle backport from 3.1 - maybe helps with the BSOD problem
* Tweaked VR scheduler to work better for flash devices like our Nexus
* Ext4 tweaks
* A lot of USB tweaked code
* More fs tweaks to decreast CPU usage on unecessary ****
* More TCP/IP tweaks
* vfs_cache_pressure -> 25
* dirty_background_ratio -> 60
* dirty_ratio -> 90
* vm_swappiness -> 30
* Sysfs interface for deep_idle created by Ezekeel was added. If you want to disable deep_idle run this command: echo 0 > /sys/class/misc/deepidle/enabled
* Screen refresh rate increased to 65hz, everything should be even smoother (thanks morfic)
* If you want more detailed information about all the tweaks added you can visit my github
----------
* No more debugging **** in the kernel. No logcat, no dmesg, no debug_kernel etc etc, this **** is clean on that logging stuff that only consume CPU cycles in the background
* CFS scheduler tweaked with custom settings
* dirty_writeback value increased from 5*100 to 15*100, reducing unnecessary I/O activity, thus releasing a few CPU cycles
* Deep Idle mod by Ezekeel (latest version)
* Few patches to lowmemorykiller.c hopefully to optimize memory usage
* Add VR I/O scheduler and made default. A lot of performance gain comes from this one.
* Also enabled BFQ scheduler to be an option with no-frills
* init/calibrate.c port from 2.6.39. Better loops per jiffy calculations
* vfs_cache_pressure 100->50
* Add Stochastic Fair Blue (SFB) network scheduler and make it default. This is a network packet scheduler, should make internet usage a lot smoother
* Changed TCP_congestion scheduler to TCP_Veno. TCP Veno module is a new congestion control module to improve TCP performance over wireless networks. The key innovation in TCP Veno is the enhancement of TCP Reno/Sack congestion control algorithm by using the estimated state of a connection based on TCP Vegas. This scheme significantly reduces "blind" reduction of TCP window regardless of the cause of packet loss.
* Tiny RCU is the default RCU engine. More explanation on this RCU here http://lwn.net/Articles/323929/
* Kernel compiled with -O2, meaning the code is more optimized instead of being compiled for size
* WiFi = PM_FAST in standby
* Optimized the config options for CFS Autogroup in the .config file, it should be perfect now
* Again more and more debugging disabled
* Obviously some minor changes and tweaking, but that can all be seen in my github below
https://github.com/franciscofranco/Nexus-S
Downloads: http://androtransfer.com/franciscofranco/Nexus_S/ (thanks sixstrings for the FTP hosting)
Please give me your feedback
Enjoy

niiice..

I knew you were gonna release this lol
Sent from my Nexus S using XDA App

mathkid95 said:
I knew you were gonna release this lol
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
When I bought my Nexus I thought "No, I'm not compiling any kernels for it, no more flashing endlessly in a loop every night."... I guess I wasn't successful
Jokes aside, better share it to the community instead of being selfish and use it only myself - I'm kinda happy with the result and maybe I can make someone happy too, that's my goal!

Is this just for the Nexus S or will it run on the 4G also?
Sent from my Nexus S 4G

franciscofranco said:
When I bought my Nexus I thought "No, I'm not compiling any kernels for it, no more flashing endlessly in a loop every night."... I guess I wasn't successful
Click to expand...
Click to collapse
typical crackflasher

Sweet, I'll give it a try!

FL0OD said:
Is this just for the Nexus S or will it run on the 4G also?
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Hmmm... good question. I used CM's kernel sources, like I mention in the op. Considering that probably S and 4G versions of CM7 share the same kernel, I'm mostly certain that it will work. Just do a backup of your installation and try it out, I'm kinda curious as well.

franciscofranco said:
Hmmm... good question. I used CM's kernel sources, like I mention in the op. Considering that probably S and 4G versions of CM7 share the same kernel, I'm mostly certain that it will work. Just do a backup of your installation and try it out, I'm kinda curious as well.
Click to expand...
Click to collapse
No smoke or fire so I am good to give it a whirl. Thanks for sharing this.
Sent from my Nexus S 4G

franciscofranco said:
Hmmm... good question. I used CM's kernel sources, like I mention in the op. Considering that probably S and 4G versions of CM7 share the same kernel, I'm mostly certain that it will work. Just do a backup of your installation and try it out, I'm kinda curious as well.
Click to expand...
Click to collapse
Should work just fine.
Sent from my LG-P999 using Tapatalk

Oooooh no. Must resist urge to flash. Screw it. I'm giving in.
Sent from my Nexus S MV from the XDA Premium app.
Sadly I'm having all the stability issues I had with the CM7 kernel only now some of my news apps cause a reboot. :-(

After a very short test: fast as morfics kernel (Quadrant 4200 by 1,2GHz) and internet is really smooth, special on 3G.

Performance is pretty good, battery life isn't terrible. I get better with morfic's TEUV, but that's kind of expected. Overall it's a nice kernel, I'll stick it out a few days and give it a true test.

So far, quick, stable, battery charges quicker than normal, and charges to 100%. Ran some quadrant standards and it seemed to be on par with other performance kernels. I am running this with Oxygen 2.3.1. Looking forward to running this through the day tomorrow. Good stuff.
Sent from my Nexus S 4G

Welcome to Nexus S. Haha.
I flash your kernel and everything was good. No FC, no bootloop, everything went fine

new kernel~!!
must flash~
But heading to mountains in an hour... will definitely flash when i come back.
i want stable phone before heading into the mountains... ><

caleb1783 said:
new kernel~!!
must flash~
But heading to mountains in an hour... will definitely flash when i come back.
i want stable phone before heading into the mountains... ><
Click to expand...
Click to collapse
You know you want to put it on the sdcard, and flash, just real quick, then flashing back to your stable kernel just before taking off.
You know it's calling you, you know you can't wait, you live in the now, you are a crackflasher.

missing BLN.

Just flashed it and getting a bsod when waking the phone as I do with other kernels with deep idle.. I don't seem to get it with morfic's test builds though..
Other than that it is very fast and the internet seems a lot smoother...
Sent from my Nexus S using XDA App

franciscofranco said:
When I bought my Nexus I thought "No, I'm not compiling any kernels for it, no more flashing endlessly in a loop every night."... I guess I wasn't successful
Jokes aside, better share it to the community instead of being selfish and use it only myself - I'm kinda happy with the result and maybe I can make someone happy too, that's my goal!
Click to expand...
Click to collapse
e~~~this kernel will cause the phone cant be wake up when i off the screen ,i am charging right now~~~

[KERNEL][stable: M1 (2.6.39.4) - exp: Alpha 31 (3.1.10)] Kowalski Kernel

This kernel supports both new and old bootloader and apparently it's also the favorite kernel of the MIUI team (****ing thieves...) !
This is not a "phonsole" kernel, it's not made for draining your battery in a nanosecond because "it's cool to play tegra3 designed games on the p990", so there is overclock, but done "The Right Way™".
Our phone is quite powerful on its own, but LG and Nvidia made a really crappy job on optimizing it. I'm just working to make it a bit better and to provide a reliable, stable and battery friendly kernel to all those people who actually use a phone... as a phone...
There are experimental/unstable versions that i release every now and then for public testing. Official kernels are released when the beta testing phase is done and 100% of the feedback is positive. Don't ask for ETA or you'll be fish slapped... badly !. This of course is not valid in case a nasty bug slips in the release, in which case i'll do my best to fix it within a few hours.
Features
* Compiled in release mode (all debug stripped)
* Battery friendly, performance aware
* 3G modem runtime/suspend idle mode support
* Enhanced wifi power management
* Runtime wifi power management control via sysfs
* Bluetooth deep sleep without disconnections
* OC up to 1.2 GHz on stable releases and up to 1.5 GHz on experimentals
* Dynamic FSync by Faux123, backported from Linux 3.4
* 32M ramhack on the new bootloader, 24M on the old one (for now)
* ROW scheduler by Qualcomm, backported from Linux 3.4
* BFQv5 scheduler, backported from Linux 3.4
* Dynamic Interactive governor, backported from Linux 3.2
* Interactive governor aligned with Google's upstream sources (Linux 3.4)
* Simplified cpu hotplug, the second core will turn off in deep sleep mode
* Single/Dual core mode
* Support for notification lights on compatible roms
* Proportional Rate Reduction for TCP to increase network reliability
* Westwood TCP congestion algorithm enabled by default
* Support for NTFS (read only) and HFS+ filesystems
* Support for NFS 3/4
* Support for custom leds brightness from userspace
* Support for USB fast charge [ Don't keep it active when connected to a pc or it may damage your usb ports. It's meant for fast charging when using car/plane adapters for example ]
* And loads more...
* Comes bundled with Kowalski Manager by wfd
Q & A
Q: Battery !!! Why it's so baaaad ! My phone doesn't sleep !!!
A: Well, don't get it badly, it's not really my problem, is it ? 99.999% is an app you have installed that's preventing deep sleep...
Q: App X crashes ! OMG I lost my sdcard ! Noooo all my data are gone !!!
A: Read again on top, not my fault, sorry. I try my best to give out a stable kernel, but "**** happens" and i can't control it...
Q: I get tons of bsods, my phone doesn't wake up from sleep, it freezes and omg... it just exploded !!!
A: No dmesg / logcat, no party. And please don't post messages like those in the thread if you're not ready to attach a log to the post.
Q: When will you enable gpu overclock, road runner speed mode or wile e. coyote immortality ?
A: Never... on a second thought... maybe... who knows ?
Q: When will you release the new version ? It's a week we're using the old one !!
A: Is it stable ? Then please allow me to fish slap you with a huge trout !
Downloads
All downloads for Kowalski Kernel are in this folder on DevHost.
Updates will be pushed to those folders based on the kernel version, and a change log will be filled in the next post accordingly. Kernel releases will be announced in the thread.
The downloads labeled as "kowalski-*-XXX-YYYbl" are obviously the kernels for [YYY=old || YYY=new] bootloader and XXX represents the version number.
* In Kowalski Manager on kernel 2.6.39.4 you can change the power management settings of the wireless card:
- PSP Power Saving Mode ---> your wifi card will use Max PSP when asleep. The kernel default is to sleep in Fast PSP mode.
- Awake Power Management ---> your wifi card will use Fast PSP when awake if enabled, otherwise will use CAM mode.
- Hotspot Power Management ---> when enabling hotspot mode, your wifi card will use Fast PSP if enabled, otherwise the default is to use CAM mode.CAM (Constantly Awake Mode)
Keeps the client adapter powered up continuously so there is little lag in message response time.
Consumes the most power but offers the highest throughput. Is recommended for desktop computers and devices that use AC power.
Fast PSP (Power Save Mode)
Switches between PSP mode and CAM mode, depending on network traffic. This mode switches to CAM when retrieving a large number of packets and switches back to PSP after the packets have been retrieved.
Is recommended when power consumption is a concern but you need greater throughput than that allowed by Max PSP.
Max PSP (Max Power Savings)
Causes the access point to buffer incoming messages for the client adapter, which wakes up periodically and polls the access point to see if any buffered messages are waiting for it. The adapter can request each message and then go back to sleep.
Conserves the most power but offers the lowest throughput. Is recommended for devices for which power consumption is the ultimate concern (such as small battery-powered devices).​Source will be pushed to my github about 2 or 3 days after a release, to make sure that no major bugs are introduced in the public repository.
This kernel can be compiled with any gcc 4.6.X that supports graphite loop optimizations, so if you want to compile it by yourself you'll have either to build your own toolchain (for example using crosstool-ng), or use one of the many linux prebuilt ones (for example Linaro or CodeSourcery). Make sure they're 4.6.X. Earlier versions may complain a lot and generate and unstable kernel. Newer versions (aka 4.7+ won't produce a bootable kernel at all unless source modifications are done).
Please don't rip-off my work. Please don't kang this kernel. Please don't c&p from my github without proper credit. I'm a nice guy, but i will report you.
Thanks
* wkpark for unlocking the ics bootloader and his genius ideas for implementing ramhack
* linus, well, for the linux kernel
* massimo69, stonebear, tetsuo55, wfd and carloit for taking the risks of testing possibly harmful pre-releases
* qualcomm, because codeaurora is awesome !
* benee, for his perfect any-kernel installer !
* wfd, for his fantastic Kowalski Manager App !
* hjunii for forward porting and cleaning up all the LG crap to kernel 3.1.10 !
On a side note... i'm not really responsible if you decide to test it and your phone melts... right ?
-

Change Log and How-Tos
Change Log
100p5 - 2013/03/03
* Fix derp in voltage table​
100p4 - 2013/03/02
* OC to 1.2GHz max
* Re-introduced the ability to modify the voltage table
* Global kmsg cleanup. Removed tons of useless/annoying debug messages
* OC code refactor and fixes. Thanks to Tonyp for finding the AP20 tech docs
* Fixed max suspend frequency race condition
* Disabled async compaction in the new lmk. Really not playing nice with the 3.4 code
* tspdrv (vibrator) code cleanup and fixes. Hopefully no more "dildo bug"
* Lots of 3G modem related fixes and introduction of the idle mode during runtime and suspend​
100p3 - 2013/02/19
* Fixed Dynamic Fsync code and added reboot/shutdown forced flushing of buffers
* Added Max CPU Frequency when screen is off
* Fixed wifi suspend issues​
100p2 - 2013/02/16
* Disabled OC for releases
* 1st attempt to fix wifi hang upon resume
* Probable fix for excessive wifi drain when ap is out of range
* Support for Faux123 Dynamic Fsync​
100p1 - 2013/02/13
* Fixed USB Mass Storage freezes
* Fixed audio input not working on some phones​
100 - 2013/02/12
* Added OC possibility (thanks to wkpark for the initial patch and to civato for pushing it to github)
* Tweaked the voltage values and enabled a bit of 2d OC
* Fixed the slow charge bug on the old bootloader
* Aligned USB Fast Charge code between old and new bootloaders
* Enabled EMC scaling aligned with the cpu speed
* Enabled RTC (Real Time Clock) support for the battery monitor
* Added fsync control from sysfs
* Added async memory compaction to the lmk
* Locked min cpu speed when using camera (snappy !)
* Tweaked a bit the interactive governor presets
* CPUs unaligned access
* Various patches to the lmk
* Various fixes to the voltage regulator
* Tons of patches to the android binder
* Tons of patches to the linux memory management
* Tons of patches to ext4
* Tons of patches to the mmc host​
011p4 - 2013/02/03 - Bugfixes and some goodies
* Backported OnDemand governor from kernel 3.2
* Added Boost Pulse support in the kernel for Interactive and OnDemand governors
* Added tegra.power.so blob to the installer
* Optimized CFQ and BFQ schedulers
* Fixed shutdown crash
* Fixed USB fast charge on the old bootloader
* Updated Kowalski Manager to the latest version​
011p3 - 2013/01/28 - Bugfixes Release
* Fixed wifi parameters persistency
* Fixed USB fast charge on the old bootloader
* Reverted "disable aio" commit that was causing lousy sdcard r/w speeds and some lag
* Updated Kowalski Manager to the latest version (with icon !)
* Tweaked the LMK values a bit​
011 - 2013/01/26
*Added USB Fast Charge mode
*Net: Various ipv4 related fixes from kernel 3.4
*Wifi: Lowered default dBm of the wifi card to 19dBm (<3 my health)
*Wifi: Raised scan time for wifi from 3s to 8s (<3 my battery)
*Wifi: fixed compatibility between 10, 10.1 and ICS
*Wifi: fixed battery drain
*Wifi: removed background scan (let Combo Scan do the job)
*Row: Multiple patches from 3.4
*Row: Implemented urgent requests (speedy gonzales style)
*Disabled LG FOTA crap in muic (and hopefully autofix some bugs)
*Disabled android compaction process (let's have the new awesome lmk do the job)
*Modified kernel entropy generation (the new black apparently)
*input: monotonic input events (fasteeeer, i said faaaaaaaster)
*increased slightly timers ticks/second (oh, this is going to be felt a lot)
*gpio timers from kernel 3.8
*android logger from kernel 3.8
*prepared makefiles for gcc 4.7.X (the next step)​
010 - 2013/01/19
*Added the possibility to change leds brightness from userspace (sysfs)
*Simplified kernel flags, removed useless bloat, smaller kernel
*Backported the lowmemorykiller from kernel 3.4
*Unified wifi driver for compatibility with cm10, cm10.1 and ics
*Disabled the cpu boost when connecting usb (badly done by nvidia)
*Compiled Zram as a module, installed a init.d script to enable it
*Moved from lzo to google's snappy as compression for zram
*Fixed a couple of regressions from nvidia kernel 2.6.32 linked to bsods when suspending/resuming
*Switched to Interactive as default governor. Seems snappier for now with the latest version
*Enabled low level kernel tegra irq timers
*Added all the TCP Congestion Algorithms available in the kernel
*Backported from kernel 3.4 the latest patches for
- ROW I/O Scheduler
- Interactive Governor
*Backported from kernel 3.4 the BFQv5 I/O Scheduler
*Tons of patches from upstream related to
TCP Networking
ARM suspend/resume and smp routines
USB memory corruption and possible lockups
Kernel Timers
009p1 - 2013/01/13
* Disabled tegra cpu frequency locking
* Added a small cpu boost when usb cable is inserted [ may prevent bsods ]
* Added one more wifi interface to sysfs [ wake_pm (bool) to set PM_FAST/PM_OFF when screen on ]
* Re-enabled the conservative governor
* Updated toolchain to a more optimized one
* Compiled with "graphite" flags for a bit more kick
* Fixed the LMK so it doesn't kill kernel threads​
007 - 2013/01/13
* Full changelog that lead to this release in my CM10 thread at the second post​
How-Tos
Change the default TCP Congestion Algorithm
To see what algorithms are available you can, in a terminal/adb console, type: "sysctl net.ipv4.tcp_available_congestion_control"
To change the default congestion algorithm, type: "sysctl -w net.ipv4.tcp_congestion_control=one_of_the_names_that_came_out_before"​
Change the Wifi Power Management modes
In a terminal/adb shell navigate to /sys/kernel/wifi_pm.
You can change the high power management setting by typing: "echo 1 > max_pm" to enable it, or "echo 0 > max_pm" to disable it (cam / psp modes).
This setting will enable/disable the PSP power saving mode when the phone is asleep. Be careful, not all the routers are happy with it.
You can change the awake (screen on) power management setting by typing: "echo 1 > wake_pm" to enable it, or "echo 0 > wake_pm" to disable it (off / cam modes)​
Change the leds brightness
In a terminal/adb shell navigate to /sys/class/leds/star_led.
You can change the high value setting by typing: "echo XXX > max_brightness" to modify it, where XXX can be a value between 0 (off) and 255 (max).​
Change WiFi TxPower
Interestingly enough, Broadcom/LG decided that they want us all dead in a very short time so they set the default txpower of the wifi chip to 32dBm (that's a whopping 1.6 Watts in power). Considering that the US FCC sets a top limit of 30dbM/1W for antennae and that the EU sets a max power of 20dBm/100mW for consumer products, i'd say that Broadcom and LG are quite some nice companies... also wonder how they went past controls with this one...
Anyway, i packed a flashable zip that will install the "iwconfig" and "iwlist" binaries to /system/xbin in your phone. After flashing this one you can, from a terminal, modify the txpower value in real-time depending on your needs (if at home 5 mts from the router, or in a park 100 mts from the access point). For now a binary, soon an apk to handle this, so bear with me and wait
You can download the package from here
To check the current txpower value
Code:
su
iwconfig wlan0
To set the new txpower value
Code:
su
iwconfig wlan0 txpower XX (where XX is the value in dBm)
On this link you can find a W -> dBm conversion table that might come in handy
Side notes: 1) To use iwconfig your wifi must be on and 2) When you turn it off/on or reboot, the setting will be reset to 32dBm for now.​
Alsa Mixer
There ya go, for all of you a little deaf that love some real crackling from your phone's speakers
Packaged in a nice cwm flashable zip (alsa_mixer.zip) that you can find here is a collection of binaries that will be installed in /system/xbin and that will allow you to alter a bit the volumes of your phone. Of course you'll have to slap the values that you like in an init.d script once you find them, or they won't persist on reboot.
For example, to boost a bit the speaker volume, you can type: alsa_amixer sset "Speaker" "60" (max is 63) and to see the current setting you type: alsa_amixer sget "Speaker"
I suggest that you look into the alsa_amixer help and experiment a bit with the values. You can't break anything, and a reboot will reset all the values to default ​
-

Plans and Wishlist
What I'm working on
* Double tap to wake
Wishlist
* OTG Support
* HDMI
What will make it into the next kernel release
* Surprise

Kowalski manager
This app is only for use with [email protected] kernel, tested on CM10, CM10.1, ICS
Features
* PSP power saving mode enable/disable
* Hotspot power management enable/disable
* High power management enable/disable
* TX Power level regulation
* Softbuttons leds brighness regulation
* Internal/external sdcard read ahead values change
* USB fast charge enable/disable
* Restore all setting after boot
Bugs
Please, tell me
Change Log
020 - 2013/06/10
*Added 2nd core auto hot plug switch
*Fixed couple of bugs
*Updated Dutch translation
019 - 2013/06/02
*Show light sensor value on brightness tab
018 - 2013/05/28
*Added switch to sound tab for on/off restore sound settings after call
*Added radio buttons to switch MultiCore Sched PM modes
*Added possibility to set brightness settings as custom defaults and reset to them
*Added Backlight settings tab
017 - 2013/03/19
*Added single core mode switch
016 - 2013/03/06
*Added dynamic fsync switch
*Added call hangup receiver to set alsa speaker volume to manager settings
015 - 2013/02/18
*Added headphone volume setting via alsa_amixer
*Added alert on fast charge switch. Thanks Tony
014 - 2013/02/15
*Added speaker volume setting via alsa_amixer
*Added Portuguese translation, thanks to chevellemendes!
012 - 2013/02/12
*App redesigned to support pager tabs
011p8 - 2013/02/08
*Added Dutch translation, thanks to majoortje!
*Updated Spanish translation, thanks to sobaquete!
011p6 - 2013/02/04
*Added Czech translation, thanks to Keltek!
*Added Finnish translation, thanks to _kankea!
011p5 - 2013/02/03
*Added Danish translation, thanks to Custom40!
*Added Franch, Italian, Serbian translations, thanks to Massimo69!
*Fixed rotation issue
*Removed iwconfig dependency
*Added Spanish translation, thanks to Massimo69!
*Added Polish translation, thanks to Rayman96!
011 - 2013/01/28
Compatible with Kowalski Kernel only since 011p3!!!
*Added Croatian translation, thanks massimo69!
*Added wake_pm enable/disable
*Changed paths for wifi power management setup
*Fixed a lot of potential freezes
*Added blue icon from 60nine!
*Added German translation, thanks TonyP!
*Now works on 4.0.4​
Download
Application already included in Kowalski kernel since 011
Thanks
* pengus77 for his amazing kernel and second life for our device
* aremcee, without him we would not have CM10.x at all
* all wonderfull devs, who makes us happy with our p990
Big thanks to our translators
German - TonyP
Croatian, Spanish, Franch, Italian, Serbian - Massimo69
Danish - Custom40
Polish - Rayman96
Czech - Keltek
Finnish - _kankea
Portuguese - chevellemendes
Russian - me
If you have some corrections, please pm authors. If you want to add your native language in app, please pm me.​

Cool! You have done some great work already and it's fantastic that there is more to come.

thanks for your hard work!
1 question: what about cm10.1 compatibility?

Luk_Optimus said:
thanks for your hard work!
1 question: what about cm10.1 compatibility?
Click to expand...
Click to collapse
Nope.

Luk_Optimus said:
thanks for your hard work!
1 question: what about cm10.1 compatibility?
Click to expand...
Click to collapse
Read the first line in the first post please... it's even in bold...

stonebear said:
Nope.
Click to expand...
Click to collapse
so not compatible to the official cm releases. that's sad somehow...

Luk_Optimus said:
so not compatible to the official cm releases. thats sad somehow...
Click to expand...
Click to collapse
"Official" cm releases are so filled with bugs that we should call an exterminator lol
First let's try to get a 10 stable, then we move to 10.1... that's the plan and i won't deviate that soon from it.

pengus77 said:
"Official" cm releases are so filled with bugs that we should call an exterminator lol
First let's try to get a 10 stable, then we move to 10.1... that's the plan and i won't deviate that soon from it.
Click to expand...
Click to collapse
sounds good! sadly, there is (as far as i know) no cm10 rom for the old bl...

Cool stuff! :highfive:

Luk_Optimus said:
sounds good! sadly, there is (as far as i know) no cm10 rom for the old bl...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2097807
http://forum.xda-developers.com/showthread.php?t=2078474
http://forum.xda-developers.com/showthread.php?t=2059372
http://forum.xda-developers.com/showthread.php?t=2030775
just to cite a few... and the downloads on get.cm are still there for cm10 if you want it...

Hi!, thanks for this release.
I have one question that I cannot answer from the OP... why is there a separate file for the PSP module? Should I flash it after the kernel or it's not mandatory? Is it valid for both BL versions?
Thanks

Awesome, your kernel runs excellent on my O2X(now at 13/01). No SODs whatsoever and very stable since first releases.
If people have SOD problems, it is not always kernel related. I have swapped my device for a new one after lots of black screen issues and with the new one I have almost 0 issues even with the same ROM+kernel.
It seems our device has many different (good and horrible)hardware revisions, I suggest to swap your device at the retailer if it is possible within your warranty.

sobaquete said:
Hi!, thanks for this release.
I have one question that I cannot answer from the OP... why is there a separate file for the PSP module? Should I flash it after the kernel or it's not mandatory? Is it valid for both BL versions?
Thanks
Click to expand...
Click to collapse
Updated op. It's valid for both bootloaders and it's not mandatory. The psp module will enable the PM_MAX flag when the phone is asleep, so make sure your router/ap supports PSP mode (if it has a broadcom chip then it does for sure) or your phone will lose packets when in deep sleep.
The gain in battery life though is gigantic... you decide

The Kernel work in P.A.C.Man fine too... Both Bootloader

About led lights I noticed that if I put "always on" with a very dim light this setting doesn't apply system-wide. If I receive a mail with gmail all fine but if I get a text via a third-party app like whatsapp or viber the light goes full brightness (but it respects the "always on" setting). I had to set a custom brightness for every application manually.

-sandro- said:
About led lights I noticed that if I put "always on" with a very dim light this setting doesn't apply system-wide. If I receive a mail with gmail all fine but if I get a text via a third-party app like whatsapp or viber the light goes full brightness (but it respects the "always on" setting). I had to set a custom brightness for every application manually.
Click to expand...
Click to collapse
This is rom related, i'll look into it on my cm10 thread. Please here post only things related exclusively to the kernel

[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?