LuckyK
A Custom Kernel
Based On JB-MR2 @Ziyan Release
Hello everyone, today I present my kernel for galaxy nexux, some notes ... Since November I joined this great forum, and start to learn about the world of programming. Possessing a Galaxy Nexus early to visit his section, and I see the first rom Lollipop created by @MwisBest, taken from his work, beginning to do research on the kernel, springs and everything around them. After various jobs, finished in ash with my hard disk burned, I decided to concentrate on the kernel, and so I ask if I can take his @Ziyan kernel, to work it and create something special, and month and about which work in this kernel, and are pleased to present its first Release.
A big Thank's goes to @Ziyan, @MWisBest, @bsmitty83 , @aosp, @freshgiammi, @boype, @imoseyon, @franciscofranco, @pattyboi, and other, for all their commit that I used
Special FeaturesCompatible with all variant (Tuna,Toro,ToroPlus)
Driver DDK 1.9
EXT4/F2FS
Overclock CPU/GPU
Special Control Smartreflex (preset)
FSync control
Vibration Control
Color Control
Fast FPE Emulator
Sound Control
Voltage Control
Driver Wi-fi 3.4
AnyKernel2 (thanks to @osm0sis)
Download:
Look in the Download Section ---> http://forum.xda-developers.com/devdb/project/?id=8795#downloads
The kernel now can be used very well in both EXT4 that F2FS, is very responsive and fluid. Always follow the recommended configurations.
Ziyan's source ----> https://github.com/Ziyann/omap
XDA:DevDB Information
[Kernel] LuckyK [5.x-7.x], Kernel for the Samsung Galaxy Nexus
Contributors
Fenix46, Ziyan, Mwisbest
Source Code: https://github.com/Fenix46/LuckyK
Kernel Special Features:
Version Information
Status: Beta
Beta Release Date: 2016-09-13
Created 2015-03-21
Last Updated 2016-09-13
Optimal Configuration
TCP Control: Cubic
Read Ahead Buffer Size: 128
Scheduler: CFQ
Freq. Min: 224 MHz
Freq. Max: 1.2 GHz
Governor: Interactive
Adaptive Brightness: ON
Vibration Intensity: 85
FSync: ON
GPU Frequency: 512 MHz
Configuration OC
TCP Control: Cubic
Read Ahead Buffer Size: 128
Scheduler: CFQ
Freq. Min: 224 MHz
Freq. Max: 1.53 GHz
Governor: Ondemandplus
Adaptive Brightness: ON
Vibration Intensity: 85
FSync: ON
GPU Frequency: 512 MHz
Changelog
V.2.2 ----> V.2.3
#Add optimization for KSM from kernel 3.10
#Add some commit for memcg from kernel 3.10
#Add more patch for OOM_KILL from kernel 3.10
#Add optimization for vmalloc, pagewalk and shmem from kernel 3.10
#Remove ANDROID_LOW_MEMORY_KILLER_AUTODETECT_OOM_ADJ_VALUES
<----------------->
V.2.1 ----> V.2.2
#Add optimization in Nohz from kernel 3.10
#Add some commit for Ondemand
#Add one patch for OOM_KILL from kernel 3.10
<----------------->
V.2.0 ----> V.2.1
#Revert old Patch in OOM_KILL
<----------------->
V.1.9 ----> V.2.0
#Add hack on ioremap
#Add percpu optimization from kernel 3.10
#Add OOM_KILL optimization from kernel 3.10
<----------------->
V.1.8 ----> V.1.9
#Add More Optimization for Block and CFQ
#Revert Commits For RCU
#Add 2 commits for lib
#Add optimization for binder
<----------------->
V.1.7 ----> V.1.8
#Add some patch for RCU
#Add optimization for MemBlock
#Add optimizations for Cpufreq and Kernel/Sched
#Add "hostapd" in zip flashable
#Add some patch for OOM_ADJ
#Add correct patch for camera (thanks @Ziyan)
<----------------->
5.1_V1.6 ----> 5.1_V1.7
#Some Update for DSS
#Fix Charging Offline
#ADD New driver for wifi
#Some update for stabilize
<----------------->
5.1_V1.5 ----> 5.1_V1.6
#Various Optimizations mm: vmscan, compaction
#Various Optimizations ext4: kvmalloc added, and kzalloc for better performance
#Various Optimizations Pstore
#Fixed Bug for CMHW
<----------------->
5.1_V.1.4 ----> 5.1_V.1.5
#Add various commits in "/mm" directory, for better stability
#Change GCC final, build with GCC 4.7 Google
#Fixed some file in "arch/arm/"... maybe now the CFQ works thanks to these commit
<----------------->
5.1_V.1.2 ----> 5.1_V.1.4
#Add 9 commits for F2FS, increse stability
#Change GCC
#increse Frame Buffer to 2mb
#Active Voltage Control
<----------------->
5.1_V.1.0 ----> 5.1_V.1.2
#Revert OndemandPlus with Interactive for better boot
#Add one String* in drivers/mmc/core/quirks.c for possible fix Bug old chip.
*NB: This string, is an optimization for GCC 4.9. Added hoping to remove the bug
<----------------->
19/03 ----> 23/03
#Switch interactive to ondemandplus
#Add 2 commits for net/ipv4 and ipv6 (for rom Zmod)
#Possible Fix for the bug chip VYL00M
Hell yea ! I've watching your git these days, and now the kernel is released ! Will try
seems to work well togheter with [ROM] [5.1] ZMoD (03/20).
Thank you for keeping my old phone snappy and up to date
Edit: boot loop at my end togheter with said rom
kongha said:
seems to work well togheter with [ROM] [5.1] ZMoD (03/20).
Thank you for keeping my old phone snappy and up to date
Edit: boot loop at my end togheter with said rom
Click to expand...
Click to collapse
excuse my English is not very good, you've had some problems with the kernel?
Sent from my Galaxy Nexus using XDA Free mobile app
Bootloops on AOSP wee better rom 5.1..
rambhanushali20 said:
Bootloops on AOSP wee better rom 5.1..
Click to expand...
Click to collapse
that ROM are you using? You made a clen flash?
My advice is ti install the ROM, to make a first start and then install the kernel. I'm using new Zmod ROM with my kernel and work fine. With FML 5.1 the kernel work, tried until yesterday.
Fenix46 said:
excuse my English is not very good, you've had some problems with the kernel?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
I believed I had installed it first but had not, sorry about the confussion in my first post. When I actially did install your kernel toghter with (clean installation) ZMoD it is boot loop.
kongha said:
I believed I had installed it first but had not, sorry about the confussion in my first post. When I actially did install your kernel toghter with (clean installation) ZMoD it is boot loop.
Click to expand...
Click to collapse
ah ok, you do one thing, installing the rom, gapps and superSU, start your smartphone, you restore the backup, and after installing the kernel, I always do this procedure, because the kernel is not compiled with any rom so if it is installed when you install the rom, you go into boot loop. follow my steps and you will have no problems
Fenix46 said:
ah ok, you do one thing, installing the rom, gapps and superSU, start your smartphone, you restore the backup, and after installing the kernel, I always do this procedure, because the kernel is not compiled with any rom so if it is installed when you install the rom, you go into boot loop. follow my steps and you will have no problems
Click to expand...
Click to collapse
Thats what I did
1. install the rom
2. gapps
3.superSU
4.reboot
5.install the kernel
and here its a boot loop
kongha said:
Thats what I did
1. install the rom
2. gapps
3.superSU
4.reboot
5.install the kernel
and here its a boot loop
Click to expand...
Click to collapse
strange, I don't why go in bootloop... I will try to understand why it behaves like this, however, to correct load a picture of my device, to show that I am using it without problems
Fenix46 said:
strange, I don't why go in bootloop... I will try to understand why it behaves like this, however, to correct load a picture of my device, to show that I am using it without problems
Click to expand...
Click to collapse
Maybe it was VYL00M bug. Other phone use that sick chip. Maybe you don't. Mine boot correctly
eternal70 said:
Maybe it was VYL00M bug. Other phone use that sick chip. Maybe you don't. Mine boot correctly
Click to expand...
Click to collapse
mm ... strange, because the base I used, I think he has already the fix, commissioned by Ziyan. I'll try to find a solution to the problem
New Release in download, this release is one test for chip VYL00M, because the bug was still present, maybe I have solved the problem.
With chip "V3U00M" the variant "V.1.0-test" dosen't work.. use the other release
Changelog added in the second post... let me know if the bug is still present ...
Amazing battery life, i got 3h15min SOT on ZMoD. Thank you @Fenix46
h4xx0rr said:
Amazing battery life, i got 3h15min SOT on ZMoD. Thank you @Fenix46
Click to expand...
Click to collapse
Thanks for feedback... these words are a big satisfaction
Sent from my Galaxy Nexus using XDA Free mobile app
The new version also dont work... Restarts again and again... And hangs at Google logo... Btw i am having VYLOOM chip nexus and i clean flashed it with latest FML build...
rambhanushali20 said:
The new version also dont work... Restarts again and again... And hangs at Google logo... Btw i am having VYLOOM chip nexus and i clean flashed it with latest FML build...
Click to expand...
Click to collapse
OK thanks, later placed a new zip for test
Sent from my Galaxy Nexus using XDA Free mobile app
New Version test for chip VYLOOM is ready for donwload, look your news...
NB: This version is compatible with the chip "V3U00M" ... but I do not recommend the installation because the performance is very low.
Test version 2 work on Zmod. I have VYL00M But first boot is very lazy and phone laggy 1-2min after first boot
Related
Hi
IMPORTANT: Before you continue reading!
At the moment this kernel is only for PrimoU devices
and NOT for PrimoC (CDMA) devices
IMPORTANT for CM users
If you want to use CM or a CM based ROM choose the correct kernel!
CM9 needs a different ramdisk.
With the permission from Adi_Pat I would like to announce my kernel build
All credits to this should go to Adi_Pat cause he did the hard work for
providing me with all I need. Therefore also the name has been
choosen to make this clearly visible.
This is just a first announcement.
I will upload the first image tonight
Principle #1:
Provide a kernel that is as close to stock as possible but provides
additional features that will improve functionality and/or performance
Some Q&A you might have
Q: what stands KISS for?
A: Keep It Simple, Stupid!
My aim is to provide a kernel that is 99.99% stock with just additional features
In the first build you will see
-OC (max 1.5)
-UV
-2 new goveners (lionheart, smartassV2)
-1 new scheduler (sio)
Q:will you provide a kernel with 2.0GHz?
A:No - since I want to provide a stable kernel and
my experiences showed that only using up to 1.5 is reliable
If you like to have higher frequencies you can
1) use Adi_Pats kernel
2) build your own kernel based on my changes and enable higher frequencies
Q:can I build my own kernel based on your changes?
A:sure. I will provide a patch file that can be applied on the original
sources provided from HTC
Q:how "close" is your kernel to stock?
A:actually if you dont use OC, UV and use govener=ondemand and
scheduler=deadline this IS stock kernel
Q:can you include feature "xy" in your build?
A:I will check and if it is not "against" principle #1 -Yes
Q:will you test your kernel builds?
A:yes. I will only provide images that have been tested to
1) boot without problems
2) have run through a basic test trying to include all important features
3) run some benchmarks to confirm that changes are not decreasing basic performance values
Q:how to install your kernel?
A:like titanium kernel
fastboot flash boot
regards
max
I provide a complete folder with all downloads
please look at the following "naming conventions" for selecting
the correct image for your ROM!
Images containing "OC-UV" will have presets
Images containing "CM9" are for CM9
Images containing "CM10" are for CM10
All others are for stock (sense) ROMs
Download:
http://www.mediafire.com/?e1chs7tzcsstc
github:
https://github.com/maxwen/primou-kernel-KISS
Build 201305210014
Changelog:
-reverted to BFQ v5.1 - v6 causes problems
-smartmax update
Build 201305141244
Changelog:
-upgrade to BFQ v6
-added smartmax CPU governor
Build 201305062354
Changelog:
-enabled fauxsound support
-added double tap to wake
allows waking up the device by double tapping on the lower part of the screen - disabled by default
sysfs interface:
Code:
/sys/android_touch/s2w_allow_double_tap
1 -enable 0 - disable
Code:
/sys/android_touch/s2w_double_tap_barrier_y
default 1300 - y-barrier below that taps will be recognized
Code:
/sys/android_touch/s2w_double_tap_duration
default 150 - time in ms for minimal duration between the two taps
Code:
/sys/android_touch/s2w_double_tap_threshold
default 150 - threshold how much longer the duration can be then duration
Build 201302150054
Changelog:
-added fast charge
to enable run
Code:
echo 1 > /sys/class/power_supply/battery/fast_charge
------------------------------------------------------------------------------------
Build 201212251804
Changelog:
-multi touch fix - thanks to d-panja3 for pointing me at this
------------------------------------------------------------------------------------
Build 201212180251
ChangeLog:
-added KSM support - see here how to use it
------------------------------------------------------------------------------------
Build 201212152225
ChangeLog:
-completely new S2W based on the work of nik3r and myself for the HOX+
------------------------------------------------------------------------------------
Build 201212021155
Changelog:
-switched to linaro 4.7 toolchain
-overhaul of compile flags
-improved lowmemorykiller
-added some arm specific fixes and enhancements
------------------------------------------------------------------------------------
Build 201211140025
KISS kernels will from now on only for sense ROMS
CM users use HELLBOY kernel http://forum.xda-developers.com/showthread.php?t=1954967
Changelog:
-added BFQ scheduler
------------------------------------------------------------------------------------
Chanelog Summary for all builds:
-new optimized ARM toolchain used
-some tweaks and fixes in vm
-added Proportional Rate Reduction for TCP - by Google http://research.google.com/pubs/pub37486.html
-added USB host support.
-added two-way call recording - Please consider local laws that prohibit using call recording!
based on patch found here http://forum.xda-developers.com/showthread.php?t=1048182
-added conservative govener
-switched RCU to CONFIG_TINY_PREEMPT_RCU - reduced memory usage
-enabled SFB net scheduler CONFIG_NET_SCH_SFB http://lwn.net/Articles/429449/
-applied patch for optimized sha1 algo https://patchwork.kernel.org/patch/1040902/
-applied patch for arm specific rwsem http://permalink.gmane.org/gmane.linux.ports.arm.kernel/92418
-xz compression - based on this patch http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=7001/2
-OC (max 1.5GHz, boot with 1GHz)
-UV
-2 new goveners (lionheart, smartassV2)
-1 new scheduler (sio)
------------------------------------------------------------------------------------------------
The "key" e.g. 201207112231 is the build id.
Actually this is just the timestamp when the image has been created.
When you report issues with a build please also provide this id
You can also find this in
Settings -> About -> Software Information -> More -> Kernel Version
Just some notes on the govener and schedulers:
Stock kernel is using govener ondemand and scheduler deadline
To get more information about all of those see here
http://forum.xda-developers.com/showthread.php?t=1369817
You can get the stock kernel sources from here
http://www.htcdev.com/ (registration required)
Or from here http://www.mediafire.com/?o0uudb56oxawvaw
To create the KISS sources apply the patch supplied with each build
Other Downloads:
Note:
If you download save or edit those scripts on a windows host make sure that
you are not changing the line endings to be DOS "style" (CR/LF) since they will
not work on your device.
So before pushing them to the device check with e.g. notepad++ or any
other windows editor that the line endings are UNIX "style" (LF)
USB host scripts
Contains helper scripts for USB host mode
Flashable from recovery
http://www.mediafire.com/?cj1buyxvwteiyqq
Simply zip file
http://www.mediafire.com/?ao391v55e3f4h7r
getcpuinfo script
Will print current settings like OC, UV and govener
Also works with Titanium kernel
http://www.mediafire.com/?emhetf9ctcb3l0g
01vdd script
For setting UV values
Also works with Titanium kernel
http://www.mediafire.com/?yj11n461vz23l4j
02setcpu script
Will set OC max 1.5GHz and govener smartassV2
with battery "friendly" govener tweaks
Also works with Titanium kernel
http://www.mediafire.com/?i79wlhjomh9bhyf
smartassV2-tune script
Allow setting smartassV2 govener tweaks for battery or performance
Call with argument "b" or "p"
Also works with Titanium kernel
http://www.mediafire.com/?e02s5ej5acacnaj
Swap script
Will enable 130m swap partition
See here for details http://forum.xda-developers.com/showpost.php?p=31441526&postcount=17
http://www.mediafire.com/?i9xc4hnfheztgir
KISS => Keep It Simple, Stupid!
hackworks said:
KISS => Keep It Simple, Stupid!
Click to expand...
Click to collapse
Thanks
hackworks said:
KISS => Keep It Simple, Stupid!
Click to expand...
Click to collapse
LMFAO!=)
Congrats on your kernel maxwen!
I will never forget it.lol
Great, i started with kernel compiling too, recently,, keep titanium tweaker in ur ramdisk, if possible, ill update u with the ramdisk builds, will add kernel specif features if u want, pm me
Hi
Sure. Will contact you after posting the first build.
regards
max
maxwen said:
Hi
Sure. Will contact you after posting the first build.
regards
max
Click to expand...
Click to collapse
Cool
Sent from my Nexus One using xda app-developers app
I like this kernel already!
Hi
First build uploaded
regards
max
Gonna flash this now, thanks for your work=D
Sent from my HTC One V using xda app-developers app
best kernel
Hi ..
im tested this kernel on the ROM myONEv works
kernel is very fast and stable.
best benchmark!
I'll try it once I got on my lappy
Sent from my HTC One V using xda app-developers app
Thanks for a nice kernel. So far the OC/UV is working great fro me.
What is the best recommended governor for wake / sleep ?
ckpv5 said:
Thanks for a nice kernel. So far the OC/UV is working great fro me.
What is the best recommended governor for wake / sleep ?
Click to expand...
Click to collapse
Use only CPUFreq and use smartAssV2 as it has both sleep and wake freqs...UV -50 should be good!
Hi
Actually there are a lot of things that you can tweak in the goveners
using the sys interface to make them perform best under certain "preconditions"
You can read this here which I also posted in the Adi_Pat thread
http://forum.xda-developers.com/showthread.php?t=1369817
This will give you some great insights on this issue.
Also about the "decision" which govener to use a.s.o
Regarding UV:
As already writen above -50 should be safe all the time
-100 works for me if I limit it to max 1.2GHz but not higher
Then I sometimes have freezes e.g. runnung AnTuTu benchmark
I still have to play with the UV settings to find the optimal ones
Regards
max
Hi
ATTENTION!!!!
Dont use sio I/O scheduler at the moment!!!!
I just discovered some strange during testing.
Stay with deadline this is stock
Will keep you informed if sio is really the reason
If it is it will be removed in next build
regards
max
EDIT: Even intensive testing has not given me the proof that the
sio scheduler was the reason.
Running this kernel with stock rom, wil I still get FOTA updates from HTC?
Chris.nl said:
Running this kernel with stock rom, wil I still get FOTA updates from HTC?
Click to expand...
Click to collapse
AFAIK this has nothing to do with the kernel in the first place
but with rooting. Someone may correct me if I am wrong
regards
max
Based on discussion on Semaphore Kernel thread, I'm glad that finally compiling using Linaro GCC 4.8 is possible now I've test this several months a go and still not boot until got some new idea arise in that discussion
Maybe this not a daily driver kernel, just feel free to try once and go back to other kernel :highfive:
Different from stock (changelogs):
build 20140324 for 20140323-NIGHTLY and newer
- Update iniram from 20140323-NIGHTLY
build 20140308 for 20140307-NIGHTLY and newer but not SNAPSHOT-M4
- Merge stock cm-11 & use initram 0307 nightly
build 20140214
- Revert s3cfb: tl2796: do not read calibration data on aries and use s3cfb: tl2796: detect invalid factory calibration data as on stock cm-11
build 20140211
- Add s3cfb: tl2796: do not read calibration data on aries from stock cm-11
- Use newer linaro toolchhain 14.01
- Update recovery to Mackay TWRP 2.6.3.0
build 20140111
- Update ramdisk to Tweak KSM Value
- Merge upstream CM-11
- Use newer linaro toolchhain 13.12
build 20140106
- Update ramdisk with Kitkat zRAM setting
- Fix lpm (charging when phone off)
- Cherry-picked optimize JPEG memory configuration & add ioctl to export memory configuration
- Only build with Mackay TWRP
build 20131231
- Fix outdated init file causing boot problem
build 20131221
- Ramdisk from cm-11-20131219-NIGHTLY-galaxysmtd
build 20131212/16
- Ramdisk from cm-11-20131206-NIGHTLY-galaxysmtd, unpacked using this tools.
- Compiled with linaro-toolchain-binaries 4.8 (32bit)
- Use Mackay TWRP 2.6.0.0 (-mtwrp) or Semaphore CWM 6.0.4.5 (-smcwm)
Additional changes in x-aries version:
Note: Video capture & playback (cma problem with or without ksm) mostly working.
In rare condition it need long time to start (5 minutes or more).
You can wait it if you have time (recommended) or simply restart your phone.
build 20140401
Compiled on this HEAD
- Update iniram from 20140331-NIGHTLY
- Enable KSM_CHECK_PAGE
- Enable Advanced TCP Congestion Control
build 20140324 for 20140323-NIGHTLY and newer
- Update iniram from 20140323-NIGHTLY
build 20140319 for 20140307-NIGHTLY and newer but not SNAPSHOT-M4
Compiled on this HEAD
- Add 2 patches to improve swap & revert aries-common: zRAM: only read one page at a time.
This time I prefer this kernel doc:
Code:
It is a logarithmic value - setting it to zero means "1 page", setting
it to 1 means "2 pages", setting it to 2 means "4 pages", etc.
Zero disables swap readahead completely.
The default value is three (eight pages at a time). There may be some
small benefits in tuning this to a different value if your workload is
swap-intensive.
Lower values mean lower latencies for initial faults, but at the same time
extra faults and I/O delays for following faults if they would have been part of
that consecutive pages readahead would have brought in.
over aosp guide:
Code:
By default, the Linux kernel swaps in 8 pages of memory at a time.
When using ZRAM, the incremental cost of reading 1 page at a time is negligible and may help in case the device is under extreme memory pressure.
To read only 1 page at a time, add the following to your init.rc:
`write /proc/sys/vm/page-cluster 0`
build 20140313 for 20140307-NIGHTLY and newer but not SNAPSHOT-M4
Builded at this HEAD
- Switch cflag from -Og (reverted to -O2 then) to -O3, the kernel size was much bigger & reduce user RAM to 416MB
- Use newer linaro toolchhain 14.02
- Add aries-common: zRAM: only read one page at a time
imo default linux value will give better performance, but I prefer to follow aosp guide like in stock cm.
build 20140311 for 20140307-NIGHTLY and newer but not SNAPSHOT-M4
- Add 1100 oc step from mackay and 2 other commits.
build 20140308 for 20140307-NIGHTLY and newer but not SNAPSHOT-M4
- Use initram 0307 nightly with 144 mb zram + minor change to cma & merge android-3.0 aosp
build 20140306
- Add 2 commits to improve swap/zram + ramdisk 0228 nightly with 256 mb zram size (not stable)
build 20140226
- Add 2 commits related to video for linux + merge stock cm-11 & android-3.0 aosp
build 20140214
- Same as aries version + some commits related to memory
build 20140212
- Add s3cfb: tl2796: do not read calibration data on aries from stock cm-11
- Add backport SLUB from Linux 3.3 from Hellybean GT-I9300 + another 4 commits.
build 20140209
- Merge android-3.0 kernel common.
- Enable CLEANCACHE, FRONTSWAP & ZCACHE
- Another CMA try.
build 20140207
- Add BLN & Fast Charge from Semaphore kernel.
Note for BLN: Need to manually rename lights.aries.so.bln in /system/lib/hw/ to lights.aries.so
Rename original file to lights.aries.so.cm or else for backup. Repeat this step in every rom flashing.
- Use newer linaro toolchhain 14.01
- Merge android-3.0 kernel common.
build 20140131
A bunch of patches from faux123, semaphore, codeaurora & linux-next, starting from here till this.
Some part maybe useless and here is the noticeable part:
- Update LMK, CMA and KSM.
- Use LZ4 compressor for zram.
- Add Semaphore Auto Brightness from stratosk (build as a module)
build 20140121
- Add ZRAM_FOR_ANDROID from faux123
- Remove KSM to prevent video recording failure
- Use LZ4 for initram
- Update recovery to Mackay TWRP 2.6.3.0
- Some cherry-pick related to CMA, low memory killer & binder
build 20140111
- Same as aries version exclude merge upstream (already added)
- Replace xvmalloc with zsmalloc for zram
build 20140106
- Same as aries version
build 20140105
- Add pawitp cma-test with 417mb memory (no need bigmem libs) and possible bugs.
- Fix lpm (charging when phone off)
build 20131231
- different boot logo
- add smartass2 cpu gov
build 20131221/22
- 1.32ghz OC step and revert sleep call gpio to prevent SOD
- 397mb memory (install bigmem lib by kasper_h separately for 720k video record fix)
- kernel config for smaller kernel size (mostly taken from semaphore kernel by stratosk)
- merged to aosp android-3.0 kernel common (big changes in wifi driver and interactive gov)
- update gpu driver to DDK [email protected] (as on mackay kernel and others)
- cherry-picked some commits related to zram, lzo and interactive gov
- display boot progress, etc..
Download
http://goo.im/devs/didhiy/aries_cm-11.0
http://goo.im/devs/didhiy/ariesbr_cm-11.0 (I9000B)
tips: check (sort by) modification time to find the latest build
Source:
Kernel
x-aries version
Ramdisk
Credits:
- pawitp
- stratosk
- kasper_h
- derteufel1980
- jugster
- alberto96
- unjustified dev
- all aries variant devs and community
Nice work. I have been looking at the sets of patches needed for Linaro 4.8, but didnt try building one yet.
Last I tried 4.8 was almost 3 months ago, and it didnt boot up, although it build fine.
Would you be willing to add the extra OC steps ( 1100 , 1300 and 1400 ) into the kernel ?
ts1506 said:
Nice work. I have been looking at the sets of patches needed for Linaro 4.8, but didnt try building one yet.
Last I tried 4.8 was almost 3 months ago, and it didnt boot up, although it build fine.
Would you be willing to add the extra OC steps ( 1100 , 1300 and 1400 ) into the kernel ?
Click to expand...
Click to collapse
maybe... right now, I just let it same as stock to see if there's any improvement
just flashed over mackay 4.1.3 and i get better score on antutu, 4985.
keep up good work.
florum said:
just flashed over mackay 4.1.3 and i get better score on antutu, 4985.
keep up good work.
Click to expand...
Click to collapse
thanks for testing & comparing, I think mackay compiled with linaro 4.8 will scored much better
didhiy said:
thanks for testing & comparing, I think mackay compiled with linaro 4.8 will scored much better
Click to expand...
Click to collapse
Wow!! That's amazing. See my score. I never managed to go beyond 4930 in the past.
Can you please describe me what is linaro 4.8 and how does it increase performance.
I flashed bigmem libs for KitKat by Kaspar_h but still got 368 MB of available RAM. Maybe it's my fault, but still curious to know if bigmem libs works on this kernel.
Thanks in advance
Sent from my GT-I9000 using XDA Premium 4 mobile app
Rohitdahiya said:
Wow!! That's amazing. See my score. I never managed to go beyond 4930 in the past.
Can you please describe me what is linaro 4.8 and how does it increase performance.
I flashed bigmem libs for KitKat by Kaspar_h but still got 368 MB of available RAM. Maybe it's my fault, but still curious to know if bigmem libs works on this kernel.
Thanks in advance
Sent from my GT-I9000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you can read the technical details here:
http://gcc.gnu.org/gcc-4.8/changes.html
in short words, it promising better optimization to the codes compiled with it
the memory size was set inside the kernel, installing bigmem libs won't change the size
This kernel is a beast,thank you very much didhiy!
@Rohitdahiya:
You should enable a bigmem setting to make the available amount of RAM bigger.
Flashing only the libs doesn't change the current configuration
Inviato dal mio GT-I9000 utilizzando Tapatalk
thank you for the wonderful kernel please make an option to enable bigmem or atleast 396mb as in case of mackay kernel... thank you
vigneshnallamad said:
thank you for the wonderful kernel please make an option to enable bigmem or atleast 396mb as in case of mackay kernel... thank you
Click to expand...
Click to collapse
I've upload a version with "x-" prefix, bigmem enable (397mb) + 1.32GHz oc steps and some configs changes to make a small kernel (mostly taken from semaphore kernel)
let me know if that version works too
download link was on op
Does this kernel have zram as it's based on stock?
Sent from my GT-I9000 using Tapatalk 4
zakitheracer said:
Does this kernel have zram as it's based on stock?
Sent from my GT-I9000 using Tapatalk 4
Click to expand...
Click to collapse
yes it have zram just like stok
didhiy said:
I've upload a version with "x-" prefix, bigmem enable (397mb) + 1.32GHz oc steps and some configs changes to make a small kernel (mostly taken from semaphore kernel)
let me know if that version works too
download link was on op
Click to expand...
Click to collapse
wow i got 5200 on antutu if u believe in benchmarks... but performance overall is wonderful...
edit : any plans of including smartass v2 and wheatly just a request as of now this is my daily kernel
edit 2 : see the score my phone is ready for android 5.0 with help of u devs
vigneshnallamad said:
wow i got 5200 on antutu if u believe in benchmarks... but performance overall is wonderful...
edit : any plans of including smartass v2 and wheatly just a request as of now this is my daily kernel
edit 2 : see the score my phone is ready for android 5.0 with help of u devs
Click to expand...
Click to collapse
temple run 2 is my only "benchmark" thanks for your nice report
Hope it's stable enough for daily driver too
I use same kernel configuration in sc-02b aries_ntt and epic4g, it's running fine for daily
Guys,
This kernel gives you to put in Mackay Rom 4.1.3 (kk 4.4)?
Thank you for your answers already.
Alexandre_Silva said:
Guys,
This kernel gives you to put in Mackay Rom 4.1.3 (kk 4.4)?
Thank you for your answers already.
Click to expand...
Click to collapse
I don't understand exactly what you mean, but I guess you can flash this kernel on top of mackay cm-11 rom and maybe mackay omni too (tested on my sc-02b only) with caution, mackay setting won't work!
didhiy said:
I don't understand exactly what you mean, but I guess you can flash this kernel on top of mackay cm-11 rom and maybe mackay omni too (tested on my sc-02b only) with caution, mackay setting won't work!
Click to expand...
Click to collapse
in mackay omni rom description kasper h has mentioned about other kernels rom not working... didnt try it yet... will test and report back if works
vigneshnallamad said:
in mackay omni rom description kasper h has mentioned about other kernels rom not working... didnt try it yet... will test and report back if works
Click to expand...
Click to collapse
I've download omni mackay 1217, after comparing initram between omni & stock cm-11 I've found no different except the binaries. Then I flashed that rom & my kernel (which have 1219 cm-11) & it boot fine.
make sure you have a backup & semaphore tar if you wanna try
didhiy said:
I've download omni mackay 1217, after comparing initram between omni & stock cm-11 I've found no different except the binaries. Then I flashed that rom & my kernel (which have 1219 cm-11) & it boot fine.
make sure you have a backup & semaphore tar if you wanna try
Click to expand...
Click to collapse
That's great will give it a try tomo of possible please include smartass v2 in our next version
vigneshnallamad said:
That's great will give it a try tomo of possible please include smartass v2 in our next version
Click to expand...
Click to collapse
no promise, but it's possible
Spirit Kernel
This kernel is ONLY for AOSP based ROMs. This will NOT work on the stock Moto roms.
I will update this regularly as I have time and will add new features and fixes as well.
If you have any feature requests or ideas that haven't been seen before, don't hesitate to post it here!!
PLEASE READ
How to report a bug?
Include the following in your bug report:
The ROM you are currently using + a link to the ROM's thread
A log, preferably dmesgs or kmsgs (use Google to find out how to pull these from your device)
The version of SpiritKernel you use (=rx, e.g.r3)
Bug reports not meeting these requirements will be ignored.
NO BUG REPORTS ON EXPERIMENTAL BUILDS!
Features
This Hybrid kernel contains features from great kernel devs with like faux,franco and neobuddy,optimized for titan to make it work.Initially there are less features but I will add much more soon
[*]Based on the Latest CyanogenMod sources
[*]Patched 3.4.106 kernel
[*]Governors: ondemand/userspace/powersave/performance/interactive/IntelliMM/inteliidemand/intelliactive/smartmax/pegasusQ
[*]Hotplug: MPDecision/MSM Hotplug/Intelliplug(default)
[*]Intellithermal v2
[*]DT2W/S2W/S2S Wake controls
[*]CPU Underclocking 192Mhz
[*]GPU OC 533Mhz | UC 100Mhz
[*]Add MSM Hotplug Driver
[*]Asynchronous Fsync extracted from HTC
[*]Sweep2Sleep driver
[*]Dynamic management of timer slack
[*]Slimbus OC thanks to neeobuddy89 and poondog
[*]increase Torch power 20mA
[*]Dynamic management of dirty page writebacks
[*]IO: BFQv7r7/FIFO/SIO/FIOPS/ZEN/VR IO Schedulers
[*]Faux Sound Control 3.2
[*]KCAL v2 by @savoca
[*]USB forced fast charge
[*]Stereo call recording support by skvalex
[*]Powersuspend from Faux and yank555-lu *updated to 1.8 after r8*
[*]Kernel Compression: XZ
[*]psx2usb controller
[*]Use Android device as USB keyboard/mouse
[*]optimized ARM RWSEM algorithm.
[*]Ultra Kernel Samepage Merging {UKSM}
[*]FRandom
[*]Dynamic FSync Control
[*]Added Simple GPU Algorithm
[*]WQ_POWER_EFFICIENT for bettery battery life. Hello Battery!!
[*]ANY Kernel
[*]Kexec hardboot patch for Multirom support
[*]TCP: HTCP/HSTCP/HYBLA/VEGAS/SCALABLE/LP/VENO/YEAH/ILLINOIS/WESTWOOD
Optimizations
[*]Compiled Using UBER 5.0.1 SaberMod 4.8 Optimized toolchain for better performance | UBER 4.9 Toolchain after r4
[*]Added optimized ARM RWSEM algorithm.
[*]Disable add_random
[*]Pocketmode and deepsleep for dt2w/s2w
[*]Optimized VFP Module
[*]FIx integer-overflow in veno,vegas
[*]Add sysinterface for GENTLE_FAIR_SLEEPERS
[*]NOATIME and NODIRATIME as default
[*]New 99LMK script by @Pizza_Dox
[*]Nvidia Patches to enhance power efficiency.
[*]Sched optimizations
[*]Increase battery level check interval
[*]writeback: increase bdi_min_ratio to 5
[*]block: cfq: merge tweaked tunables.
[*]Wait just 1 second for other CPU to halt
[*]net: combat buffer bloat
[*]PM: Introduce suspend state PM_SUSPEND_FREEZE
[*]Disable -fconserve-stack on ARM v2
[*]Enable power efficient workqueues by default
[*]do not use msm_run_queue_stats
[*]enable/disable cpu-boost via sysfs
[*]softirq: reduce latencies
[*]Built with Ofast flags
[*]Force SELinux permissive
[*]LowMemoryKiller management of non killable processes
[*]Headset High Performance Mode
[*]Allow CPU-supported unaligned accesses
[*]Enable UNALIGNED_ACCESS
[*]enable ARCH_POWER
[*]lower swappiness
[*]vfp: remove double entries
[*]Disable disable crc check for 30% extra performance in IO
[*]Optimized SLUB memory allocator
[*]Optimize Sfck Compression
[*]set sched_mc_power_savings to 2 (moar powarrrrrrr! saving)
[*]readahead to 256
[*]Built with Graphite flags
[*] Enabled Pipe Flag
TO-Do List
IntelliMM-intelliminmax
New Govs and I/Os
Intelliplug 4.0
GPU OC and UC
* Recommended app for tweaking the kernel: FauxControl,Kernel Auditor or TricksterMod
Recommended settings :
Governor: Intelliactive
I/O Scheduler: Fiops or row
TCP Congestion : Westwood
GPU Governor : Simple Ondemand Or Msm-adreno-tz
Hotplug : Intelliplug ( Keep screen off frequency to 787 MHz )
Powersuspend : Hybrid
Simple GPU Algorithm : On
How DO I flash this?
Reboot to recovery.
Install zip from SD Card.
Choose the SpiritKernel-Rx-titan.zip
Insatll and Reboot.
Changelog:
Click Me
Downloads:
Basketbuild
Source:
Github(branch:spirit)
Wiki containing changelogs,settings and more
Antutu Score: http://forum.xda-developers.com/showpost.php?p=59736983&postcount=136
Credits goes to these SUPERHUMAN for Inspiration and support (In no specific order)
faux123
Cl3Kener
slukk
luca020400
savoca
Anas Karbila
hurtsky
pinkflozd
YoshiShaPow
Flashhhh
flar2
vigneshrajagopalan
And more
XDA:DevDB Information
Spirit kernel for titan, Kernel for the Moto G 2014
Contributors
DC07
Source Code: https://github.com/DC07/spirit_msm8226
Kernel Special Features: Powersuspend,Ultra KSM,FRandom,Faux Sound,LCD KCAL,DT2W/S2W,Fastcharge and More
Version Information
Status: Stable
Current Stable Version: r13
Stable Release Date: 2015-04-21
Created 2015-03-16
Last Updated 2015-04-21
F.A.Q. - Read this before complaining!
1. My phone exploded, HALP!
A: I don't answer to problems without a log. The log file is in /proc/last_kmsg. Paste it on pastie.org and link it on your post. Logcats are useless for Kernel purposes, don't bother posting them.
2. This kernel works on Y or X rom?
A: Doesn't work with ROMs having different ramdisk or any derivates due to their irresponsibility of using a different ramdisk which needs patches that break stock rom users. Use a different rom and don't bother me.
3. OMG BETTARY SUCKZ, IT DEAD IN 45 MINUTAS, HALP!
A: As you can imagine I don't build kernels to decrease battery life. All the battery life problems come from your apps, either Facebook, or Maps, or some Location Service being enabled etc etc. Check your damn wakelocks and fix them, the kernel is not responsible for them.
4. How do I flash this?
A: Reading the OP, theres a reason why I added instructions on it.
5. What is a data loss? Did I just had one?
A: Data loss is simply having the connection cut for X periods of time, usually few seconds. Grey bars means the device is not connected to Google services for some weird reason, but you'll still have internet connection.
6. OP is arrogant, I'm gonna call the Internet Police?
A: Deal with it.
Settings recommended by our users
metalrules321 said:
Heres what I use and it gives me exceptionally good battery life and perfomance (may differ for others) /using faux-clock app
1.CPU Hotplug
-Intelliplug (I use fauxclock, so cant find the msm hotplug)
-Touch boost on
-Screen off frequency 787 mhz
-Hysterisis value : 8
-Profile : Ecoconservative
-Threshold value 350
2.Thermal Manager
-Intellithermal
-Frequency Throttle temp; 70
-Core throttle temp: 65
3.GPU manager
-Governor: msm-adreno-tz
-simple gpu algorithm
-gpu clock:320
-Simple governor (laziness); 5
-Ramp Threshold: 5
4. IO scheduler
-ROW (for both emmc and sd)
-Read ahead :1024
-Entropy: off
5.Memory Manager
-Zram: Off
-All the other options on
- Swappines:80
-VFS cache pressure : 120
-Dirty ratio:20
-background ratio:5
6.Same page merge
-Intelli ksm enable
-Activation treshold :24
-Cycles per activation 3
-Pages to scan:400
-Scan delay interval :500
7.Battery Control
-Throttling - On
-Temperature threshold :45
-Throttle frequency:787
8.Miscellaneous
- Powe suspend mode: Userspace
-powesuspend: On
-Dynamic file sync: on
-TCP congestion control:Westwood
*Sorry for an awfully long post *:silly:
Click to expand...
Click to collapse
@DC07 wrong kernel tree xd
https://github.com/CyanogenMod/android_kernel_motorola_msm8226/tree/cm-12.0
luca020400 said:
@DC07 wrong kernel tree xd
https://github.com/CyanogenMod/android_kernel_motorola_msm8226/tree/cm-12.0
Click to expand...
Click to collapse
The kernel just works fine with the trees I'm using ATM.
DC07 said:
The kernel just works fine with the trees I'm using ATM.
Click to expand...
Click to collapse
But not in new trees
Now our cm12 uses this kernel and if you flash this one you will broke media ( cannot play/record videos )
Yeah... Thankssss
luca020400 said:
But not in new trees
Now our cm12 uses this kernel and if you flash this one you will broke media ( cannot play/record videos )
Click to expand...
Click to collapse
Oh,I'll rebase it in the next build then.
Thanks for pointing it.
Guys is media [video recording and playing] broken?
As said by luca.Just wanted to confirm if I need to change the base.
Maybe can anyone check on latest CM12 build.
DC07 said:
Guys is media [video recording and playing] broken?
As said by luca.Just wanted to confirm if I need to change the base.
Maybe can anyone check on latest CM12 build.
Click to expand...
Click to collapse
YEa I'm sure
When I tested lp kernel on kk media was broken
And new lp kernel is a way better
Eager to use it on latest Builds and requesting to add kexec support if possible
Sent from my XT1033{LP} using TAPATALK
DC07 said:
Guys is media [video recording and playing] broken?
As said by luca.Just wanted to confirm if I need to change the base.
Maybe can anyone check on latest CM12 build.
Click to expand...
Click to collapse
For me, sometimes it works, but then other times won't.
In blisspop video works for a day...then well i moved to stock 4.4.4 for some testing and optimisation on it btw i'm on xt1068
Hello Guys,
After working off to a new base fixed everything in the new build.
Get it https://s.basketbuild.com/devs/DC07/Spirit/titan
Steps and feature list are on the OP.
Enjoy!!
Help
Hello im a new moto g user and i flashed the latest cm12 nightly. I really want to flash this kernel but im afraid that it wil screw up my phone. I flashed franco and it screw me up. Should i do it? I have backup stockrom
MotoGUser69 said:
Hello im a new moto g user and i flashed the latest cm12 nightly. I really want to flash this kernel but im afraid that it wil screw up my phone. I flashed franco and it screw me up. Should i do it? I have backup stockrom
Click to expand...
Click to collapse
Normal moto g or second generation?
And there isnt even franco kernel for this device lol so ofc you screw up.
If you indeed own a moto g 2nd gen (titan) and your are running latest cm12 nightly it is safe to flash this kernel.
Anas Karbila said:
Normal moto g or second generation?
And there isnt even franco kernel for this device lol so ofc you screw up.
If you indeed own a moto g 2nd gen (titan) and your are running latest cm12 nightly it is safe to flash this kernel.
Click to expand...
Click to collapse
Second gen
What
Sent from my Moto G 2014 using XDA Free mobile app
I did not think the new governors nor Min Freq: 96000
Is there anyway to disable the cpu being clocked at 19000 whenever I touch the screen? It's a feature of CM12, however is there anyway to disable this? I tried putting off mpDecision through Faux123 but it still goes to 19000 even with intelliplug and the user defined option. Any help appreciated!
Thanks,
iG0tB00ts
MotoGUser69 said:
Second gen
Click to expand...
Click to collapse
How the hell you have a Moto G 2nd Gen and flashed Franco Kernel? Franco Kernel is for 1st Gen. lol man you need new eyes, even glasses don't help in this case.
Sent from my Moto G 2014 using XDA Free mobile app
Neatkernel2.0 by gsstudios
This project is now no longer updated. I won't be using my sgs for a while.
It is compatible with all JB (4.1.2,4.2.2,4.3, 4.3.1) and KK (4.4.2, 4.4.4) ROMs based on AOKP and CM layout!
The Mission:
To continue giving support for the much loved kernel. New features and additions will be added to improve flexibility and speed to the already amazing kernel. My goal is to improve Neatkernel kernel as much as I can, without sacrificing stability.
DISCLAIMER:
ONLY FOR AOSP BASED ROMS
I'm not responsible for bricked devices or wrong version flashing
You are using this kernel at your own responsibility
——— !!!!!!!! YOU HAVE BEEN WARNED !!!!!!!! ———
FEATURES:
- Linux kernel 3.0.101
- Double Recovery
- Swap SD card
- OC up to 1500mhz
- BLN & CM LED
- Compiled with Linaro 4.9.4
- Fast charge
- Vibration intensity
- Deep Idle
- Governor ondemand
- Governor intelliactive
- Governor OndemandX
- Governor lagfree
- Governor wheatley
- Governor smartassV2
- Governor lulzactive
- Governor conservative
- Governor interactive
- Governor interactiveX
- Governor SavagedZen
- Governor minmax
- Governor brazilianwax
- Governor adaptive
- Governor ondemand
- Governor userspace
- Governor powersave
- Governor lionheart
- Governor perfomance
- bfq I/O scheduler
- cfq I/O scheduler
- deadline I/O scheduler
- fifo I/O scheduler
- noop I/O scheduler
- row I/O scheduler
- sioplus I/O scheduler
- vr I/O scheduler
- zen I/O scheduler
- Fast Charge support
- SWAP support
SWAP SD
the hard way is to modify /system/.neatkernel/swapsd from "swapsd=0" to "swapsd=1" and you External Card Will Be use like internal.
delete /system/.neatkernel/swapsd will go back to stock storage status.
CWM Recovery is by default.
To boot in TWRP just hit any volume keys after vibrate to boot into TWRP recovery.
THINGS TO DO:
- Why don't you tell me what to do
THINGS I WILL NOT ADD:
Code:
- LZ4 Compression (Our Boot partition is way too small to support this)
- Useless CPU governors such as Userspace
- Colour tuning support (Unless someone helps me with this)
- Higher thermal limits (We all know what happens if we do this)
- Higher overclocking/Lower underclocking capabilities (So you want less stability and more SODs?)
- Synapse support (Stweaks is the only app that can fully support this kernel)
- Linux Kernel version updates (My skills need to improve first before taking on something this big)
CREDITS:
mohammad.afaneh (For original Neatkernel source)
Domnesu (For providing builds for the galaxy s)
Christopher83 (For Linaro toolchain)
Chet Kener (For UBER toolchain)
Pawitp
Stratosk
DerTeufel
Kasper_h
neobuddy89
alberto96
DOWNLOAD:
Kernel downloads
See post 3
Video libs
DOWNLOAD links to Standard CyanogenMod video libs. WARNING! Download libs for your version of android!
JB_41_CM_libs.zip
JB_42_43 CM_libs.zip
KK_44_CM_libs.zip
CHANGELOG:
See post 2
KERNEL SOURCE:
Source code of the kernel can be found here:
https://github.com/gsstudios/NeatKernel_captivate
And for the original Neatkernel source:
https://github.com/mohammad92/NeatKernel_captivate
ISSUES:
Sometimes Camera video recording and Gallery video playing do not starts from first attempt. Do not panic! It is not bug it is feature of CMA memory allocation! Close Camera or Gallery. Try again. - Fixed in build b002
If video playback is crashes with error then you need to flash standard CyanogenMod video libs. This error is due to you use bigmem libs from previous ROM or KERNEL.
USEFUL LINKS
- CPU Governor and I/O Scheduler Guide
TCP Algorithm guide
HAVING PROBLEMS?
Check the troubleshooting guide before asking questions
HOW TO FLASH?
Check the troubleshooting guide
WHICH APP TO TUNE KERNEL?
Use devil tools
XDA:DevDB Information
Neatkernel 2.0, Kernel for the Samsung Galaxy S I9000
Contributors
gsstudios
Source Code: https://github.com/gsstudios/NeatKernel_captivate
Kernel Special Features:
Version Information
Status: No Longer Updated
Current Stable Version: b002
Stable Release Date: 2015-11-02
Current Beta Version: b001
Beta Release Date: 2015-11-02
Created 2015-11-01
Last Updated 2015-11-07
Changelogs:
--UNRELEASED VERSIONS--
Code:
- Nothing to see here :)
--RELEASED VERSIONS--
Code:
[B]Neatkernel 2.0 b002 (STABLE)[/B]
- CMA removed (Too many problems when enabled. A lot of related commits were reverted)
- Fixed BFQ, you can now set in kernel tuning apps
- Fixed Westwood not being default TCP algorithm
- SIOPLUS is now the default IO scheduler
[B]Neatkernel 2.0 b001 (BETA)[/B]
- Built with latest linaro 4.9.4 from Christopher83
[STRIKE]- Introduced BFQ io scheduler v7r8 [/STRIKE] - Broken. Fixed in next release
- Initial support for TCP algorithm changing
[STRIKE]- Westwood is now the default TCP algorithm[/STRIKE] - Fixed in next release
- Selinux changed to permissive, please confirm
Downloads
I test most of these builds to make sure they are stable. There may be some cases where I might not test out a build before releasing it. Kernels marked with '(STABLE)' are safe for everyday use, but only take this as a indication.
Which version to get?
galaxysmtd = international i9000 variant - This is the main version I will be building for
captivatemtd = SGH-i897
galaxysbmtd = Samsung Galaxy S B
vibrantmtd = SGH-T959
MAKE SURE YOU'RE DOWNLOADING THE RIGHT KERNEL. OTHERWISE YOU COULD BRICK YOUR DEVICE!
Main download link:
https://www.androidfilehost.com/?w=files&flid=42683
Mirror download link:
https://github.com/gsstudios/NeatKernel_captivate/releases
Beta builds and stable builds will only be uploaded on AFH and github.
Troubleshooting
(Probably one of the most detailed troubleshooting guides for kernels on XDA)
For general help, please use the Q&A thread
Q:How do I flash your kernel?
A: You flash kernels like flashing roms, except you don't have to factory reset your phone. If you can't flash the kernel for some reason, you can either flash philz recovery then flash the kernel OR you can just make your own kernel .tar file and flash via ODIN by following this guide: http://forum.xda-developers.com/galaxy-s2/development-derivatives/convert-kernel-zip-to-tar-t2994381
Q: Which kernel version build should I flash?
A: Flash the latest stable version if you want the most stable experience. Builds that have not been marked with 'Stable' are mostly stable, or haven't been tested enough to earn a stable tag. Either way, it's up to you which one you want to flash. Read the changelog for any important changes that might have occurred in a particular build.
Q: I get constant FCs after flashing your kernel!
A: Have you wiped your cache partition, dalvik cache and reset stweaks settings? If you've done all of these already, a logcat would be nice
Q: What is a TCP algorithm?
A: Congestion control strategies (or algorithms) are used by TCP, the data transmission protocol used by many Internet applications. The main goal of a TCP algorithm is to avoid sending more data than the network is capable of transmitting, that is, to avoid causing network congestion.
Q: Why not use XYZ toolchain?
A: See this post
Q: What is UBER?
A: After years of using different custom toolchains like Linaro and SaberMod, I found there were things I liked about both of them but also things that didn't sit quite as well with me. SaberMod always seemed to have UI lag (especially in scrolling) but opened apps well and Linaro always seemed to be buttery smooth but had terrible app opening speed. Linaro battery was also worse for me than SaberMod. After going back and forth between toolchains I finally had this epiphany! Why not just take all of the best parts of all toolchains and merge them into one? So I began bringing up my own toolchain from gnu.org. At first I patched in all of the AOSP toolchain pactches (much like how SaberMod did it originally however it is important that you realize that No! I did not copy and paste SaberMod into my source I'm simply stating that I used their idea of merging aosp into gnu.org) to my source. Then I went through and added all of the linaro patches that I could to the source. I also made sure that I had the very latest of every toolchain component. I then made very minimal changes to the aosp toolchain build folder to allow for building with these newer toolchain components and UBERTC was born!!! (Note: both Linaro and SaberMod both made lots of modifications to the toolchain build folder, UBERTC is the closest to the aosp build process)
Click to expand...
Click to collapse
Do you guys want UBER toolchain or Linaro toolchain for this kernel? If you want to know what I think, I think linaro will be better suited as for older devices, linaro usually performs better.
Kernel will be released sometime this week, hopefully by today, I will be able to upload.
There seems to be a problem with the Neatkernel script as the zip files are not being created properly. Will fix this issue soon.
Test builds are up, must be flashed using ODIN or heimdall. Won't be a 'official' release until I fix the zip issues.
regards, gsstudios
Update: All good now. Just renamed the zimage from the .tar file to boot.img, then it should be flashable in a zip file. This kernel is officially released now.
great work
many thanks
Next build will have CMA reverted. Bigmem is much more stable and reliable compared to CMA, but that means of course we get less ram. BFQ will now be able to be selected and Westwood is now the default TCP algorithm. I will decide whether to build with UBER toolchain later on the kernel development, right now the focus is on improving the stability of the kernel and porting new features.
regards, gsstudios.
Just flashed NeatKernel_galaxys_v2.0b002-[11-02]-[17-33].zip. Live OC is not supporting, Custom Voltages is not supporting... A lot of features from description of kernel are not supporting. Why it happened?
jupiter5700 said:
Just flashed NeatKernel_galaxys_v2.0b002-[11-02]-[17-33].zip. Live OC is not supporting, Custom Voltages is not supporting... A lot of features from description of kernel are not supporting. Why it happened?
Click to expand...
Click to collapse
Will be available hopefully in next build. Was supposed to edit the OP and add those features later.
Regards, gsstudios.
gsstudios said:
Will be available hopefully in next build. Was supposed to edit the OP and add those features later. Regards, gsstudios.
Click to expand...
Click to collapse
It will be great if you port this kernel to ICS.
may I know the ram for this kernel ? thanks
yah7733 said:
may I know the ram for this kernel ? thanks
Click to expand...
Click to collapse
v2b002 ram amount is about 382Mb
Due to the lack of activity on my i9000, I have decided to abandon this project and will no longer give updates to this kernel. The thread will remain open until it becomes unused.
regards, gsstudios.
:crying::crying::crying:
gsstudios said:
Due to the lack of activity on my i9000, I have decided to abandon this project and will no longer give updates to this kernel. The thread will remain open until it becomes unused.
regards, gsstudios.
Click to expand...
Click to collapse
OK. But you must to delete your feature list, cause it is fake most of all, unfortunately.
jupiter5700 said:
OK. But you must to delete your feature list, cause it is fake most of all, unfortunately.
Click to expand...
Click to collapse
Just think of it as incomplete. I just don't have the time to work on the sgs anymore (need more time on my sgs 2 as this is my main device, main development device). Sorry I couldn't bring all promised features.
Regards, gsstudios
Update: OP updated. This will be the last post on this thread. Seems like a good time to close it.
Vision1 Kernel
Working with LineageOS (Sync with LineageOS Kernel Source)
Kernel Version : 4.4.83+
CPU up to little/big 2.0/2.6 GHz
CPU down to little/big 69/69 MHz (300/300 MHz _nuc version)
GPU up to 710 MHz
GPU down to 180 MHz
blu_active, alucard, ondemand, interactive, performance, conservative, powersave, ... CPU Governors - interactive default
ZEN, VR, FIFO, MAPLE, SIO, SIOPLUS and FIOPS IO Scheduler - MAPLE default
IOsched switcher
Adaptive LMK
more TCP Cong - Westwood default
Adreno Idler - default on
Adreno Boost - default off
Backlight dimmer option - default off
Workque Power Saving - default on
Tunable Wakelock
Input Boost - default on
Touch Boost - default off
Soundcontrol
KCAL
DT2W
Wifi driver from CAF
Stock Camera Driver <- use all camera and better picture quality
NTFS FileSystem R/W
SafetyNet patched
Working with Kernel Adiutor (I prefer EX Kernel Manager)
Anykernel Installer
Fingerprint is useable as Homebutton
optimized UBERTC 4.9.4 with mixed -O2/-O3 + pipe + graphite flag
more...
Be careful!!! Make backup before flash. Please report if you find an issue. Thanks
Download @ XDA
Download @ AFH
Thanks to:
LineageOS for base
@RenderBroken for EAS port
codeworkx for working on base
flar2 for patches
sultanxda for patches
UBERTC for toolchain
more
XDA:DevDB Information
[KERNEL][4.4.83+][LOS] Vision1 - fast/smooth/battery-friendly, Kernel for the OnePlus 5
Contributors
AuxXxilium
Source Code: https://github.com/AuxXxilium/kernel-msm8998
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: Vision1_2017_08_23
Stable Release Date: 2017-08-23
Created 2017-08-11
Last Updated 2017-08-23
Changelog and more...
Upcoming
Vision1_2017_08_XX
--- anything to do?
Changelog
Vision1_2017_08_23
first build after a complete rebase of the kernel. all upstream patches and the most CAF patches are done. clean merge with all commits.
old and stable WiFi driver
no CPU UC/OC
Vision1_2017_08_21 <- wipe cache
new EAS version with patches from RenderBroken
bring back interactive as default and iosched switch to go to noop if screen is off
WiFi driver update
only little changes
Vision1_2017_08_20
2 versions: a normal one and one without underclock.
CAF - reduced some voltages or make them dynamic
CAF - performance and camera related patches
Build System optimizations
Vision1_2017_08_19
Biggest Bugfix-Build ever
pocket judge working
removed cpu input boost from big cluster
removed temp throttle from big cluster
and much more...
Vision1_2017_08_18
Linux Kernel 4.4.83
go back to UBERTC 4.9.4 <- is smoother than 5.3
some little changes
Vision1_2017_08_17
use UBERTC 5.3
go back -Ofast -> -O2 for stability
battery optimization
more compiler optimization
fix a charging related bug
fix an input delay
tristate-key sync with LOS
remove old camera driver
VisionOne_2017_08_16
new Camera Driver - now we can use all camera
new WiFi Driver
more LOS changes
Careful please: there is a version with new and old memory setup. LOS uses from today the new memory setup. i build both versions because not all custom rom have ported this.
VisionOne_2017_08_15_new_wifi
updated wifi driver from https://review.lineageos.org/#/c/185015/
more...
VisionOne_2017_08_15 <- wipe cache please
Dash fixed
Deepsleep fixed
Fingerprint Homebutton is working with 20170815 build from codeworkx
synced with LineageOS upstream
new CPU Steps 69MHz, 160MHz, 230MHz
set Touchboost --> default off / CPU Input Boost -> default on
Linux Upstream 4.4.79 -> 4.4.82
optimized UBERTC 4.9.4 compiler
mixed -O2/-O3/-Ofast compiler flag for stabilty and speed
more compiler changes
more...
VisionOne_2017_08_13_CAF <- wipe cache after flashing
Sync with CAF Upstream
something more
VisionOne_2017_08_13
Linux 4.4.21 -> 4.4.79
some little fixes for more smoothness
VisionOne_2017_08_12_fix - 177xxx in Antutu - see Screenshots
fix build
faster boot
some little fixes
VisionOne_2017_08_11
initial build
Reserved
Wow!! You are the man who made the best lollipop rom for OP2
I'm going to flash this one, If something goes wrong you'll gift me a new 1+5=?...
Just kidding, Thanks @AuxXxilium..
Amazing
Enviado desde mi ONEPLUS A5000 mediante Tapatalk
I'm going to try this one out right now..Thanks for ur efforts.
angelmakumbe said:
Wow!! You are the man who made the best lollipop rom for OP2
Click to expand...
Click to collapse
thanks. nice to see someone knows me after a long time away.
tested the kernel briefly on Unofficial RR, the UFS speeds seem to be much better than LK or Carbonite... missing the home button though flashing like crazy today, can't catch a break
@AuxXxilium as you've stated in OP home button is not usable, But mine is working fine..
OMG, you are alive still? Used to use your kernel before I learned how to make kernels
AuxXxilium said:
thanks. nice to see someone knows me after a long time away.
Click to expand...
Click to collapse
I remember you from the G2 times too, I used to follow your work back then, I'm happy to see you again. I'll definitely try your kernel and keep my eye on this thread!
Glad to see more kernel devs are supporting us folks on LOS. Flashing this kernel presently.
DespairFactor said:
OMG, you are alive still? Used to use your kernel before I learned how to make kernels
Click to expand...
Click to collapse
i know it's a joke.
thanks.!!
best kernel!!!
AuxXxilium said:
i know it's a joke.
Click to expand...
Click to collapse
Not a joke at all, I used to use your kernel on Nexus 5, I think?
DespairFactor said:
Not a joke at all, I used to use your kernel on Nexus 5, I think?
Click to expand...
Click to collapse
Oh that is nice. Now you are a great dev.
AuxXxilium said:
Oh that is nice. Now you are a great dev.
Click to expand...
Click to collapse
Thanks I am just a noob haha, you didn't want to believe me
I'm running latest Codeworkx build. Home button doesn't work with stock or vision kernel, but works with lightning kernel. Don't know why
Please be careful. i removed the latest version - because it crashes the dash charge. search for the problem and will fix it soon.