[KERNEL][4.4.2][GPE/CM11][V500] dyn.Kernel r4 (03/21) | discontinued - G Pad 8.3 Original Android Development

dyn.Kernel
*Discontinued*
I want to share with you my own kernel builds. My focus is on performance improvements and energy efficiency.
Things I want to achieve:
- more battery life
- same more performance as stock
- smooth ui / games
- less heat
Highlights:
GPU idle detection:
We don't need high performance if there is nothing moving on the screen. Therefore the kernel will detect when the gpu is offline or at very low load (for litte moving objects, like battery charging animations). This feature is used for nearly all my other modifications.
Advanced Dynamic Scaling:
I have added additional values for idle (nothing moving), busy (action on the screen) and (touch)boost. Everything is explained below.
Dynamic Touchboost:
The touch boost is only active if something is rendered on the screen, that means the boost will pause as long as there is no movement, but it will resume when it is actually necessary. The boost is configured in boost_target_loads.
New Hotplug Solution:
I wrote a new hotplug driver which is completely configurable. You can change the behavior for every cpu core and gpu_idle state.
https://github.com/aventu90/android_kernel_lge_v500/blob/dyn/arch/arm/kernel/hotplug.c
All interactive and hotplug values explained (build r4+):
Many values are grouped into boost, busy and idle.
boost: A short period of time while or after touching the screen.
busy: The gpu has work to do, nearly always active when something is moving on the screen.
idle: The opposite from busy. A good time to save energy with conservative values.
Interactive governor:
I have added boost, busy and idle values to get the best performance / battery life in every situation.
Read this to understand what the new interactive governor values do: https://android.googlesource.com/kernel/common/+/android-3.4^/Documentation/cpu-freq/governors.txt
Hotplug driver:
You have different values for every gpu_idle and online-cpus state. So your phone will scale differently when playing games, doing nothing or just swiping on the screen. Here is an example:
pm_busy_up_threshold -> 55 60 65 100
1 CPU cores online: 55% up threshold
2 CPU cores online: 60% up threshold
3 CPU cores online: 65% up threshold
4 CPU cores online: 100% up threshold, because we can't get more
All values explained:
up_threshold: If the cpu load gets higher than x%, the hotplug driver will start counting up to max_up_counter
down_threshold: If the cpu load gets lower than x%, the hotplug driver will start counting up to max_down_counter
max_up_counter/max_down_counter: Every sample_time_ms the hotplug driver can count +1, -1 or nothing, when the max_ value is reached, 1 core can go on- or offline. Both counters will be reset when a core goes on- or offline.
sample_time_ms: It will take this long until the driver will check again all the things, mentioned above.
So the minimum time until a cpu core goes on or offline is: sample_time_ms * max_counter. For example:
busy_max_down_counter[3 cores online] * busy_sample_time_ms => 100 * 30ms = 3000ms = 3 seconds
You must set 4 values or 1 for sample_time_ms.
Configure the kernel (optional, build r4+):
If you want to use custom values, this is the best way for now:
1. Download the kernel_config.zip and extract it
2. Put the file somewhere on your sdcard
3. Install and open Script Manager
4. Click the file and select "Su" and "boot" (values will be automatically set at boot)
5. Click "start" and all values will be set
You can use an app like Kernel Tuner for undervolting.
Installation:
- make a nandroid backup first (boot)
- flash .zip via custom recovery (CWM/TRWP)
- flash SuperSU
Button combo for recovery:
http://www.youtube.com/watch?v=uo3YfszOPsQ
Github:
https://github.com/aventu90/android_kernel_lge_v500/commits/dyn
MD5
4cbae4bf1f6d39db020a131284d1c7a3 dyn.Kernel-r1-0110.zip
f63e212848f018a4d5615c997bed3757 dyn.Kernel-r2-0118.zip
a32828474a31dc2ae3f7885bae7caae3 dyn.Kernel-r2-0120-CM.zip
588af2b55f05f71d84ccb9bd845fd29d dyn.Kernel-r3-0204.zip
0ba565860bad16bb8ecfb94f28dad902 dyn.Kernel-r3-0204-CM.zip
511e888d74d24caa2328685c287c4738 dyn.Kernel-r4-0318.zip
247f49ef0e7d9474f500670cb9daa859 dyn.Kernel-r4-0321-CM.zip
Big thx to:
rmcc
djrbliss
Mahdi786
FranciscoFranco
Faux123
Hit thanks if you like it.
You can also buy me a coffee.
I'm testing all my builds and use them daily, but I am not responsible for any kind of damage on your device.
Which kernel should I choose?
There are V500 KitKat roms which work with G Pad 8.3 Google Play Edition stock code (GPE) or with code from Code Aurora Forum (CAF).
"CM" build for:
- CM11
- Mahdi-Rom 01/17 or later
- other CM/CAF based roms
build without suffix:
- Mahdi-Rom before 01/17
- AOKP
- PA
- SlimKat
- CMB
- other stock GPE based KitKat roms
This list could change quickly, please let me know.
Not made for V510 (GPE)!
(build r4+) clear your kernel app settings, compare them with the values from the 02kernel_config script

Changelog:
Code:
r4:
- hotplug driver: another big update, all values are now configurable
- smartcover support
- updates for CAF build
- (03/21) Cyanogenmod ramdisk update
r3:
- major cpu interactive governor update
- - newest version from CAF
- - added a lot of dynamic values
- hotplug updates
- touchboost updates
- rewritten gpu interactive governor
r2:
- cherry-picks from Cyanogenmod/Code Aurora
- - 100% cpu idle bug should be fixed
- - great improvements in idle/sleep time
- - faster charging through bugfix
- hotplug: lower threshold for 4th core
- touchboost: gpu_idle stays false now for at least 100ms
r1:
- undervolting added
- new hotplug solution
- modified interactive governor is default
- franco's interactive gpu governor
- gpu idle detection
- franco's generic touchboost driver
- set readahead to 512kb
- other things (github)

Good to see some kernel love
Could you elaborate as to why you don't think cm11 won't work please?
Sent from my LG-V500 using XDA Premium 4 mobile app

whoamigriffiths said:
Good to see some kernel love
Could you elaborate as to why you don't think cm11 won't work please?
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
CM uses different kernel sources usually, but I am not sure if it is still compatible.

reborn90 said:
CM uses different kernel sources usually, but I am not sure if it is still compatible.
Click to expand...
Click to collapse
I can confirm that this doesn't work on cm
Sent from my LG-V500 using XDA Premium 4 mobile app

Stock ROM Supported ?
Does this support or do you plan to make one for the stock rom ?

naruto.ninjakid said:
Does this support or do you plan to make one for the stock rom ?
Click to expand...
Click to collapse
I could, yes. But there must be enough demand. I personally don't like manufacturer roms, they are often antiquated and overloaded, so it's up to the community.

reborn90 said:
I could, yes. But there must be enough demand. I personally don't like manufacturer roms, they are often antiquated and overloaded, so it's up to the community.
Click to expand...
Click to collapse
I believe many of us are running the stock ROM but you could do a poll or something to be sure. Anyway thanks for your work.

Thank You
reborn90 said:
I could, yes. But there must be enough demand. I personally don't like manufacturer roms, they are often antiquated and overloaded, so it's up to the community.
Click to expand...
Click to collapse
Thank you for branching out in this direction. I'm keen to try it but am currently on Malladus 4.2.2 because it's the only custom rom that works with XBMC.
Would your kernel on Mahdi change that?

Thanks man. Glad you like mahdi
Sent from my LG-V500 using Tapatalk

Exciting to see new kernel. Does this have the possibility of modifying the gamma or color? Also is this for only K it kat rooms or stock too
Sent from my SM-N900W8 using Tapatalk

Awesome!! So glad to see this here!! And many thanks to OP for the recommendation!!
Sent from my Nexus 5 using XDA Premium 4 mobile app

Moose0704 said:
Awesome!! So glad to see this here!! And many thanks to OP for the recommendation!!
Click to expand...
Click to collapse
Moose Mahdi is no joke..
Without Question.. The best ROM for the 8.3.. And now we have a Kernel.. :good: Nice Start to 2014..
Thank You OP for sharing this with us.

reborn90 said:
dyn.Kernel
I want to share with you my own kernel builds. My focus is on performance improvements and energy efficiency.
Things I want to achieve:
- more battery life
- same more performance as stock
- smooth ui / games
- less heat
Highlights:
GPU idle detection:
We don't need high performance if there is nothing moving on the screen. Therefore the kernel will detect when the gpu is offline or at very low load (for litte moving objects, like battery charging animations). This feature is used for nearly all my other modifications.
Advanced Dynamic Scaling:
The interactive governor will now use different values for up_threshold, timer_rate and min_sample_time for every cpu_core and gpu_idle state. If the gpu is busy, the governor will use values for more performance and if it is idle, it will use conservative settings.
The current values, feel free to suggest other.
Code:
/* up_threshold, timer_rate, min_sample_time */
static unsigned int interactive_val[GPU_STATE][ACTIVE_CORES][TUNABLES] =
{{
/* gpu idle */
{100, 40000, 10000},
{100, 40000, 20000},
{100, 40000, 30000},
{100, 40000, 40000}
},{
/* gpu busy */
{90, 20000, 40000},
{90, 20000, 40000},
{95, 20000, 60000},
{95, 20000, 80000}
}};
Dynamic Touchboost:
The touch boost is only active if something is rendered on the screen, that means the boost will pause as long as there is no movement, but it will resume when it is actually necessary. It will double the actual cpu load and calculate the frequency, the maximum is input_boost_freq. This aggressive calculation offers a smooth ui, but it can also save battery, because you will often don't need input_boost_freq when the screen is touched.
New Hotplug Solution:
The load is calculated with the average of all active cores to get the performance we actually need. Most of the time two cpu cores are online to guarantee enough performance for ui interactions. After some time and not touching the screen, only 1 core will stay online to save a bit more battery.
It will use different up and down thresholds for each gpu_idle and cpu core state.
Code:
/* down threshold, up threshold */
static unsigned int hotplug_val[GPU_STATE][ACTIVE_CORES][TUNABLES] =
{{
/* gpu idle */
{0, 70},
{40, 80},
{50, 90},
{60, 100}
},{
/* gpu busy */
{0, 60},
{30, 60},
{30, 70},
{40, 100}
}};
https://github.com/reborn90/android_kernel_lge_v500/blob/dyn/arch/arm/kernel/hotplug.c
Recommended settings (default):
Interactive governor:
dynamic_scaling: true (strongly recommended)
input_boost_freq: 1350MHz
input_boost_freq_duration: 1500ms
Interactive gpu governor:
up_threshold: 60
down_threshold: 25
sample_time_ms: 60
You can use an app like Kernel Tuner for undervolting.
Installation:
- make a nandroid backup first (boot)
- flash .zip via custom recovery (CWM/TRWP)
Github:
https://github.com/reborn90/android_kernel_lge_v500/commits/dyn
MD5
4cbae4bf1f6d39db020a131284d1c7a3 dyn.Kernel-r1-0110.zip
Big thx to:
FranciscoFranco
Faux123
djrbliss
Mahdi786
Hit thanks if you like it.
You can also buy me a coffee.
I'm testing all my builds and use them daily, but I am not responsible for any kind of damage on your device.
The Kernel should work with (need confirmation):
- AOKP
- PA
- SlimKat
- CMB
- other stock based KitKat roms
It does not work with:
- CM11
Not made for V510 (GPE)!
Recommended ROM: Mahdi-Rom
Click to expand...
Click to collapse
can u make a kernel for stock rom? thanks for this btw

So glad for this kernel. Would be ecstatic if gamma adjustments ala faux kernel could be implemented
Sent from my SM-N900W8 using Tapatalk

UV every Step about 50mv looks good

RaiderWill said:
Moose Mahdi is no joke..
Without Question.. The best ROM for the 8.3.. And now we have a Kernel.. :good: Nice Start to 2014..
Thank You OP for sharing this with us.
Click to expand...
Click to collapse
Totally agree! Very happy right now!!

+1 for gamma adjustments and if you can adjust the colors to remove the yellow whites. And a kernel for stock?
Sent from my LG-V500 using XDA Premium 4 mobile app

Any impressions from an actual user?

mzfckr993 said:
Any impressions from an actual user?
Click to expand...
Click to collapse
Yep been running on mahdi. Runs great
Sent from my Nexus 5

Related

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

Note!
Only for stock 4.3
Click to expand...
Click to collapse
Features
Gamma Control - HOW-TO
DoubleTap2Wake - HOW-TO
Sweep2Wake - HOW-TO
Advanced Xperia Recovery - HOW-TO (Only v5 and above)
Based on 10.4.1.B.0.101 kernel sources
Xperia Advanced Recovery Bootloader
CPU overclock upto 1.944 GHz
Undervolting
Built with Linaro 4.8.3 toolchain using -O3 optimisation
Updated Prima WLAN drivers
Additional CPU governors - SmartMAX | SmartMAX_eps | Intellidemand 5.0 | Intelliactive | Preservative
Tweaked SIO and added FIOPS, Zen, VR, BFQ (7.2) and ROW block schedulers
USB force fastcharge
Updated Ondemand and interactive governor
Compressed kernel using XZ
Tweaked voltage regulators
Interactive GPU Governor
Uses CPUQuiet from Nvidia
Click to expand...
Click to collapse
Installation instructions
Flash in CWM/TWRP
Click to expand...
Click to collapse
Un-Installation instructions
Use the AROMA Installer in the zip to uninstall
Click to expand...
Click to collapse
Credits
Sony - I love what they do and only wish they got more recognition. They deserve it.
faux123 - For almost all kernel features
DoomLord - For the RAMDISK
Click to expand...
Click to collapse
Donors
Source
http://bitbucket.org/nikhiljan93/xzkernel
Click to expand...
Click to collapse
XDA:DevDB Information
[Stock-Kernel] XzInnere [Linaro-4.8.3], a Kernel for the Sony Xperia Z
Contributors
alnikki25k
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 5.0
Stable Release Date: 2014-03-29
Created 2014-01-27
Last Updated 2014-03-28
Reserved
HOTPLUG CONTROL, GOVERNORS, SAMPLE CONFIGS:
Thanks to n3ocort3x
With cpuquiet + load stats governor u get a brilliant battery life while keep it snappy.
I recommend leaving the governor on load stats (hotplug depended on load) to get the best results.
If you want to keep it balanced, and yeah, most users want that:
governor: smartmax
cpuquiet governor: load_stats
If you want ultimate performance:
governor: interactive (up treshold 65) or smartmax (lower tresholds)
cpuquiet governor: load_stats
SMARTMAX GOVERNOR
===============
awake_ideal_freq 594000
boost_freq 1242000
suspend_ideal_freq 384000
touch_poke_freq 1242000
Leave the rest untouched
Click to expand...
Click to collapse
For a more power-saving governor (Recommended)
New! Preservative
Click to expand...
Click to collapse
Thanks to bedalus
This is just for the record, and for those interested. The previous version of Preservative worked like a combination of smartass and conservative. It would scale straight up to the optimum frequency if there was any load (like smartass), then scale up one step at a time (like conservative) if the load was above the required threshold. This worked pretty well, and helped keep the frequency low. But sometimes it was keeping it low for too long, and a few users (myself included) noticed occasional hangs, presumably caused by a pile up of critical code that didn't get executed in time.
To improve responsiveness, but keep the frequency as low as possible was quite a challenge. I took the existing logic and chucked most of it in the bin...
(Remember, it's keeping the frequency low, and not UV that saves power - read this thread, especially post #2 for more background on this issue)
...what came to replace it was a fairly original hybrid, inspired by ondemand. Ondemand works by jumping to the top frequency when there is any load. This is usually overkill. So, you might have been at 100% CPU utilisation at 384MHz, so ondemand will jump straight to 1512MHz. However, when it gets there, the utilisation is now only 30%, so it will scale down to 486MHz.
Preservative now works a little like this. Whatever frequency it is currently at, if the utilisation hits 100%, it will scale up. But scaling up to max like ondemand? In the example above, this was the worst kind of overkill. Scaling up to max just to find scaling up one step would have been sufficient. But do we need to scale up one step, or as many as possible? There's no way to know for sure. You have to scale up before you can measure if the extra CPU cycles were enough or not.
This issue is what Preservative attempts to overcome: if the load is high, it will scale up, but not always to max. Let's label the frequency steps: 384=A 486=B 594=C 702=D 810=E 918=F 1026=G 1134=H 1242=I 1350=J 1458=K 1512=L
Conservative would take 11 calls to the governor to get from A to L, if L was required. Ondemand would go straight there. Ondemand is often overkill, conservative is often underkill. I'd like a compromise. Here's what Preservative would do:
Code:
L <- 4th step selected by preservative
K <- 3rd step selected by preservative
J <- 2nd step selected by preservative
I
H
G <- 1st step selected by preservative
F
E
D
C
B
A <- sat here until there is load
It splits the difference between whichever frequency it is at and the top frequency, and jumps there. If it is still under high load, it will do it again. So if it is idling, then needs to get to the top, it takes three more calls than ondemand, but seven less than conservative. Not only that, but it has also skipped over a large chunk of the slower steps that conservative would crawl through.
Scaling down also works in a similar way. Preservative will work out what step would be sufficient to manage the load, then jump halfway to that step on the first call. This is because, unlike ondemand, there is no down-threshold. Preservative will scale up when the load exceed the up threshold, but as soon as this is no longer the case, it will start attempting to scale back down to save power. It does not wait for load to reduce to drop below a certain point. Loads fluctuate. If went straight back to A, only to come back back to L, it would have to scale through G J and K again. However, dropping to G then D then B before A means if it does have to scale back up towards L, it doesn't have as far to climb, meaning less calls to the governor, and that the best step can be achieved quicker.
There has also been an adjustment to the up threshold. When the device is idle, the up threshold will automatically adjust to be more relaxed about scaling up. This means while the device is idle (e.g. when you are just reading some text) it becomes increasingly sensitive to changes in demand. When you touch the screen it will extremely responsive.
Conversely, when the device is hitting the top frequency, the up threshold will become increasingly strict. So if you are gaming, and putting a lot of load on the CPU, it will aim to be as efficient as possible, and only scale up if it really has to, to ensure that no cycles are wasted at these high power hungry frequencies.
Whenever it goes from hitting L to hitting A, or visa versa, the threshold will reset to default. The sysfs location of this tunable remains at:
Code:
/sys/devices/system/cpu/cpufreq/up_threshold
It will accept values of up to 127, higher being more power-saving. The default is 100, but editing the file changes this value. If you want to use a different value on a permanent basis, add the line
Code:
[B]echo 84 > /sys/devices/system/cpu/cpufreq/up_threshold[/B]
to /etc/init.d/00config
and it will then restore your setting of 84 (or whatever) every time you reboot. Remember it will be overwritten if you flash updates to the kernel, so make a copy of your edited file. However, I believe 100 is a pretty good default.
Click to expand...
Click to collapse
Reserved
Changelog
Next-Release-TO-DO
XzI - v6
Kitkat - 230 Sources
Massive changelog
Large amounts of debugging code removed
Click to expand...
Click to collapse
Current-Release
XzI - v5
Intelliactive CPU governor
New! Advanced Xperia Recovery Bootloader
New! Preservative CPU Governor (Read more)
Kernel mode NEON
MSM CPU Frequency Limiter / a.k.a Snake Charmer(in faux app) support
Kernel Futex tweaks
MSM Memcopy enhancements from Motorola Mobility
Higher Bus Speeds @ Lower cache clocks = Higher performance @ Lower Temperatures + More Power Savings
Generic tweaks
Click to expand...
Click to collapse
Previous releases
XzI - v4
Sony 10.4.1.B.0.101 Sources
Tap2Wake/Sweep2Wake using evgen method
New Power-Aware Workqueue algorithms
AROMA Installer
XzDualRecovery
Lots of debugging removed
BFQ-v7r1
Interactive GPU Governor
Removed Simple GPU Governor
Removed MultiROM
Click to expand...
Click to collapse
XzI - v3
MultiROM Xperia for Xperia Z - http://www.youtube.com/watch?v=9f9gG1sRNog
- Initial implementation. Not functional. Just testing boot.
Revert Power-Supply drivers back to 4.2.2
Intellidemand Governor 5.0
Click to expand...
Click to collapse
XzI - v2
Lower undervolt to 600 mV
Sound Control 2.0
Gamma Control
SLUB updates
Updated Adreno drivers
Use O3 Optimisation
Tune BFQ
System Config Clean-up - Quite experimental
Click to expand...
Click to collapse
XzI - v1
Initial Release
Click to expand...
Click to collapse
Download
Click here
Click to expand...
Click to collapse
MultiROM
Coming Soon
Placeholder
Cool! Good job. What would you say is the advantage in this kernel over XzKernel?
Kocayine said:
Cool! Good job. What would you say is the advantage in this kernel over XzKernel?
Click to expand...
Click to collapse
Almost no setup needed. Everything works with a good default configuration. Uses a completely different hotplug governor.
alnikki25k said:
Almost no setup needed. Everything works with a good default configuration. Uses a completely different hotplug governor.
Click to expand...
Click to collapse
I guess including DoubleTap in the kernel would make it too much like your other kernel, right?
Kocayine said:
I guess including DoubleTap in the kernel would make it too much like your other kernel, right?
Click to expand...
Click to collapse
Yup. May not include that. But will have Gamma control.
No sound control right?
alnikki25k said:
Yup. May not include that. But will have Gamma control.
Click to expand...
Click to collapse
You sure you cant make a version with doubletap? I dont need very advanced kernel, just some governors and stuff and now I got used to the tapping as well : (
BTW, how about the wakelock fixes and so from XzKernel, are they included here?
beniamin24 said:
No sound control right?
Click to expand...
Click to collapse
This is just the first release. It'll be added next.
my phone reboots after trying to undervolt in trickster mod app
braacic17 said:
my phone reboots after trying to undervolt in trickster mod app
Click to expand...
Click to collapse
It works for me. Clear all settings in TricksterMOD and try again.
alnikki25k said:
It works for me. Clear all settings in TricksterMOD and try again.
Click to expand...
Click to collapse
nope. still not working i tried everything even in faux123 app but it just reboots.
well its not so important for me right now. kernel is awesome and i can see better battery life on my xz 4.3 !!
thanks ! :laugh:
alnikki25k said:
Yup. May not include that. But will have Gamma control.
Click to expand...
Click to collapse
When you include gamma control I'll switch to this kernel
Sent from my C6603 using xda app-developers app
What about exFAT? Is it work properly?
-totonio- said:
When you include gamma control I'll switch to this kernel
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
.. and doubletap.. then we got all that is needed
Not for deodexed right?
Inviato dal mio C6603 utilizzando Tapatalk
Exactly what i need, a battery oriented / balanced kernel, while keeping it slim.. Keep up the good work!
Waiting for gamma control.. ??
Edit Note: i've missed the part which state that double tap wont be included here.. Sorry..
Sent from my C6602 using Tapatalk

[KERNEL][3.10.71][KCAL] Velocity v1.1

*** Disclaimer
I am not responsible for any kind of damage to your device,
or in case it explodes, your surroundings.
Please use it at your own risk!
Click to expand...
Click to collapse
Features :
-O3, Cortex-A53, NEON, VFPv4 optimizations
Compiled from latest Linaro GCC 4.9.3 2015.02 Toolchain [Christopher83]
Upstreamed to 3.10.71 from kernel.org, from 3.10.28
Asynchronous Fsync ported from HTC Devices
Dynamic Fsync v2.0 [faux123/varunchitre15]
PowerSuspend v1.7 driver support (replaces EarlySuspend) [yank555.lu & faux123]
Android early_suspend/late_resume PM kernel driver framework has been
deprecated by Google. This new powersuspend PM kernel driver is a replacement
for it.
Conserves battery much better.
Triggered by Screen on/off.
Intelli_plug v3.9 driver [faux123]
Intelligent hotplug cpu driver with eco mode.
KCAL - Advanced color control
Disabled MMC CRC check for extra 30% boost in IO
Reduced debugging = More performance
Simple GPU Algorithm [faux123]
FIOPS, BFQ + stock I/O Schedulers
Filesystems support : NTFS, F2FS
Sysfs implementation for changing vibrator intensity [varunchitre15]
Zswap, Frontswap and znswap [faux123]
Support for kernel-mode NEON [faux123]
Increased charging current to 1.2A
Frandom - Fast Kernel Random Number Generator driver added
Added ARM NEON Crypto functions
Click to expand...
Click to collapse
Download :
Velocity v1.1 <- Mirror
Velocity v1.0 <- Mirror
Camera Fix
Changelog :
v1.1
- Added KCAL - Advanced color control (Thanks to @savoca for his great job) check this thread for more info
- Numerous fixes from android kernel_common 3.10 and 3.10.y repos.
- Enabled Conservative governor
v1.0
- Initial release
Installation :
1. Download and save the latest zip to your phone
2. Flash this zip from any custom recovery (eg. TWRP, CWM, Philz)
3. If camera doesn't work, perform steps 1 & 2 for the zip containing camera fix
Recommended Settings :
Min. CPU freq. : 400MHz (Under this might cause SOD)
GPU Governor : simple_ondemand
I/O Scheduler : FIOPS
Read-ahead size : 1536 kB
Intelliplug profiles :
* For general use : Eco Performance/Eco Conservative
* For gaming : Balanced/Disabled
Kernel apps : FauxClock, Kernel Adiutor, Trickster MOD
Credits :
@varun.chitre15
@faux123
@Christopher83
XDA:DevDB Information
Velocity Kernel, Kernel for the YU Yureka
Contributors
neomanu
Source Code: https://github.com/neomanu/android_kernel_yu_msm8916/tree/cm-11.0_exp
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v1.1
Stable Release Date: 2015-03-11
Created 2015-03-07
Last Updated 2015-03-11
Reserved
ooo new kernel...
hello bro first of all thanks for contributions towards Development of yu yureka..
Now downloading...
FEEDBACK AFTER SOME HOURS OF PLAYING....
Hey, can I flash it directly on other custom kernel
screen shots??
ankurvvvv said:
screen shots??
Click to expand...
Click to collapse
Its a kernel not a rom. What do you need screenshots of?
My bad. too excited with my new Yureka that not paying attention to anything
flashed this kernel and used it for 5 hrs.
Good BATTERY command.
i attended a con-call for 90 plus minutes and battery drained only 5%
No lag while using basic games like clash of clan or clash of lords
Issues identified
screen black out while on call, you cant control your calls like add new call or check text while you are on phone calls. but no issue in voice and reception.
while making call you cant drop call as screen goes black out.
No heating issue as far i observed.
colour reproduction is good.
seems need little fine tune can make this kernel a must install.
All the very best to develops
Regards
question
MIUI custom ROM supported???
sunilnair007 said:
flashed this kernel and used it for 5 hrs.
Good BATTERY command.
i attended a con-call for 90 plus minutes and battery drained only 5%
No lag while using basic games like clash of clan or clash of lords
Issues identified
screen black out while on call, you cant control your calls like add new call or check text while you are on phone calls. but no issue in voice and reception.
while making call you cant drop call as screen goes black out.
No heating issue as far i observed.
colour reproduction is good.
seems need little fine tune can make this kernel a must install.
All the very best to develops
Regards
Click to expand...
Click to collapse
you are talking about proximity sensor issue , is it right?
Sent from my AO5510 using XDA Free mobile app
Review after using a whole day.
1. First & best intelli_plug driver - loved the live and smooth activation and deactivation of cores acc to load. only single core runs while using light apps (whatsapp,hike,tapatalk etc) i.e. full utilization of a single core.
2. Highly customizable using the FauxClock pro app.
3. cpu temp was usually higher (50-60 degrees) than my last kernel (Tz).
4. As @sunilnair007 posted the screen goes black while call. But one thing i noticed was when i press just at the side of proxi sensor the screen wakes up Exactly same as the Yureka proximity issue but on all other kernels the proxi was working fine on my phone (stock, thunderzap)...
5. i didn't used the phone for an hour or so i.e. phone was in deep sleep the i tried to wake up the device by the power button several times but finally had to remove battery and put again and booted the device :c
and after turning on the battery was 12% (earlier it was above 75%) and it was increasing by itself >.> battery usage graph ss --- i.imgur.com/y9QCyCz.png
and after keeping it turned off for sometime and restarting the battery got stable at 46% and started decreasing as per usage. (so got much less battery backup)
How to make best use of it.
Installed this kernel.
However, it seems very complex to make best use of it by a person like me who is not used to Custom Kernels. Before this I have used ThunderZap2, and Xcelerate, without much of tweaking. In Xcelerate for example, I found that different cores where shutting down by default. Here all the core are working by default. Obviously with this Kernel it seems I will have to do some tweaking.
I have also installed Kernel Adiutor as recommended in OP. However, information on recommended setting is too sketchy.
Would like to more detailed information as how to tweak / set this kernel to make best use of it.
tons of thanks to you bro... for kcal addition
Bro thanks a lot for adding kcal colour management to YU yureka..
Very nice bro..
One thing bro the hotplug is only working with 4 cpu of first cluster only...
I'm using kernel audiutor beta...
And please rommended any setting to run it cooller because comparing to other custom kernel it run little high temp..
Otherwise working grate.....
[KERNEL][3.10.71][KCAL] Velocity v1.1
Seems developer worked hard and results are visible.
No complaints so far testing since morning.
Need 2 days time to give a stable review.
Best wishes and please keep this spirit intact
Regards
Tarry! said:
5. i didn't used the phone for an hour or so i.e. phone was in deep sleep the i tried to wake up the device by the power button several times but finally had to remove battery and put again and booted the device :c
Click to expand...
Click to collapse
Noticed this too. Pressing the volume buttons once/twice, when it is unresponsive, wakes it right back up.
esukhdev said:
Here all the core are working by default. Obviously with this Kernel it seems I will have to do some tweaking.
I have also installed Kernel Adiutor as recommended in OP. However, information on recommended setting is too sketchy.
Would like to more detailed information as how to tweak / set this kernel to make best use of it.
Click to expand...
Click to collapse
Firstly, I'll try to simplify the recommended settings.
Secondly, hotplugging is not enabled by default.
Enable it by going to CPU Hotplug in Kernel Adiutor and enabling Intelliplug.
DGEEEK said:
One thing bro the hotplug is only working with 4 cpu of first cluster only...
I'm using kernel audiutor beta...
And please rommended any setting to run it cooller because comparing to other custom kernel it run little high temp..
Otherwise working grate.....
Click to expand...
Click to collapse
Set the Intelliplug profile to Eco Conservative/Eco Performance to hotplug upto 7 cores.
I'm looking into the cluster problem as mentioned.
To run cooler, try reducing the max frequency.
Tarry! said:
1. First & best intelli_plug driver - loved the live and smooth activation and deactivation of cores acc to load. only single core runs while using light apps (whatsapp,hike,tapatalk etc) i.e. full utilization of a single core.
2. Highly customizable using the FauxClock pro app.
3. cpu temp was usually higher (50-60 degrees) than my last kernel (Tz).
4. As @sunilnair007 posted the screen goes black while call. But one thing i noticed was when i press just at the side of proxi sensor the screen wakes up Exactly same as the Yureka proximity issue but on all other kernels the proxi was working fine on my phone (stock, thunderzap)...
5. i didn't used the phone for an hour or so i.e. phone was in deep sleep the i tried to wake up the device by the power button several times but finally had to remove battery and put again and booted the device :c
and after turning on the battery was 12% (earlier it was above 75%) and it was increasing by itself >.> battery usage graph ss --- i.imgur.com/y9QCyCz.png
and after keeping it turned off for sometime and restarting the battery got stable at 46% and started decreasing as per usage. (so got much less battery backup)
Click to expand...
Click to collapse
Regarding point 5 , I faced same behavior in TZ as well xccelerate kernel.I don't understand the problem.the battery completely drained out and more heat on backside of the mobile.whenever if i would make any changes on IO SCHEDULER or governed faced the issue.
Sent from my AO5510 using XDA Free mobile app
androidgalaxyman said:
Regarding point 5 , I faced same behavior in TZ as well xccelerate kernel.I don't understand the problem.the battery completely drained out and more heat on backside of the mobile.whenever if i would make any changes on IO SCHEDULER or governed faced the issue.
Sent from my AO5510 using XDA Free mobile app
Click to expand...
Click to collapse
The issue is that if you set performance profile to "Power save", gov "ondemand" & min frequency lesser than 500MHz, phone sleeps to death & you have to hard reboot to get back on. Its a known bug and is present in stock kernel too. Check if settings i stated are the reason for you. Doesn't happen with "Interactive" because it never scales lower.
Sent from my AO5510 using XDA Free mobile app
@neomanu , Do I need to wipe cache and dalvik cache while flashing this kernel over any ROM. Also I have flashed a custom kernel previously and now I want to flash this, so Should I simply follow your instructions or need to wipe something.
No Need to wipe anything. To give u extra boost you can wipe dalvik cache which will rebuild cache again and its always good. no need of cache or data wipe
Is this kernel support's volte?
Sent from my AO5510 using XDA-Developers Legacy app

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

Categories

Resources