-STEEL 6/7 KERNEL-
This is my kernel based on the LineageOS stock kernel! I try to keep it as optimized as possible while adding a few features here and there. Suggest or request features, I don't care as long as it's logical. I hope you like it! Everyone has a different taste though.
-CREDITS-
ZaneZam, Lord Boeffla, Yarpiin, anupritaisno1, Pranay Narang, FranciscoFranco, the XOS team, LineageOS, osm0sis, aviraxp and maybe a couple others, i'm sorry if I forgot someone!
-FEATURES-
• CPU underclock to 302mhz on big and little clusters.
• GPU underclock to 27mhz.
• GPU default governor is simple_ondemand.
• Zram disabled.
• CPU Governors: interactive, ondemand and performance.
• Franco wakelock blocker.
• SLIMbus overclock.
• Fingerprint boost.
• Kcal control.
• Spectrum support with 4 preconfigured profiles.
• Headphone audio boost.
-DOWNLOADS-
Google Drive
-COMPATIBILITY-
It is most compatible with LineageOS 14.1/13 and most ROMs based on it. It should work on AOSP/CAF ROMs but not all features are guaranteed.
-BUILD INFO-
I use UBERTC 4.9.4 and Kubuntu Linux 17.
XDA:DevDB Information
Steel 6/7, Kernel for the OnePlus 2
Contributors
Nick80835
Source Code: https://github.com/Nick80835/Steel-Kernel-OP2-Lineage
Kernel Special Features: It boots!
Version Information
Status: Stable
Current Stable Version: 2017-08-01:16
Current Beta Version: ---
Created 2017-06-22
Last Updated 2017-08-01
Known Issues: Tell me please! Seriously.. tell me.
Nick80835 said:
Known Issues:
• DT2W can only be enabled and disabled using a kernel settings app for LOS14.1 based ROMs, for AOSP and CAF based ROMs the switch in the settings app should work if it is there.
• Incompatible with Boeffla Config app.
Click to expand...
Click to collapse
why isnt Boeflla config app compatible?
suraj.das said:
why isnt Boeflla config app compatible?
Click to expand...
Click to collapse
I believe it's an issue with the kernel version or a value I need to fix back to default.
Nick80835 said:
I believe it's an issue with the kernel version or a value I need to fix back to default.
Click to expand...
Click to collapse
Hmm.. It worked for me when I was modifying boeffla kernel for personal use. Ill take a look into your source once its up ?
suraj.das said:
Hmm.. It worked for me when I was modifying boeffla kernel for personal use. Ill take a look into your source once its up ?
Click to expand...
Click to collapse
I think I accidentally modified a few things I should have left in place, before I finish putting the source up I'll look and see if I can fix it.
Nick80835 said:
I think I accidentally modified a few things I should have left in place, before I finish putting the source up I'll look and see if I can fix it.
Click to expand...
Click to collapse
So now it's Boeffla app compatible?
CounterC said:
So now it's Boeffla app compatible?
Click to expand...
Click to collapse
No, and won't be because this kernel has too many changes to work properly with the app. I apologize if this is inconvenient. It has been working fine with Kernel Adiutor all day for me though. :fingers-crossed:
Just uploaded an update, I added touchboost back, I removed Boeffla sound and Boeffla controls altogether. I basically refreshed the audio system, still based on PDesireAudio 10.0 due to issues with 10.1. The default IO readahead is now 128kb.
Edit: This kernel works with SuperSU and MagiskSU just fine. I've tested MagiskSU and it passes safetynet. SuperSU doesn't pass safetynet.
I'm working on adding LZ4 Fast compression/decompression to my kernel and I was wondering if anybody who may see this could help? Any tips or info are welcome, I'm trying to learn as much as possible.
Nick80835 said:
No, and won't be because this kernel has too many changes to work properly with the app. I apologize if this is inconvenient. It has been working fine with Kernel Adiutor all day for me though. :fingers-crossed:
Click to expand...
Click to collapse
You need to recover almost every part of Boeffla ramdisk.
aviraxp said:
You need to recover almost every part of Boeffla ramdisk.
Click to expand...
Click to collapse
I don't plan on doing that so I just removed it. The boeffla config app doesn't provide all the options and functionality that my kernel has so it's really bottlenecking it's array of options. The kernel works fine, flashes fine and builds fine as it is and I see no reason to hold it back in such a way. I based this kernel on Boeffla kernel for a good reason, compatibility with ROMs and his great AnyKernel implementation.
Nick80835 said:
I don't plan on doing that so I just removed it. The boeffla config app doesn't provide all the options and functionality that my kernel has so it's really bottlenecking it's array of options. The kernel works fine, flashes fine and builds fine as it is and I see no reason to hold it back in such a way. I based this kernel on Boeffla kernel for a good reason, compatibility with ROMs and his great AnyKernel implementation.
Click to expand...
Click to collapse
Then I assume things like swipe2awake are broken now?
aviraxp said:
Then I assume things like swipe2awake are broken now?
Click to expand...
Click to collapse
Sadly, yes.
Nick80835 said:
Sadly, yes.
Click to expand...
Click to collapse
Then remove Boeffla swipe2wake helper. I think it can be simply removed through reverts, or build your own kernel auditor with Boeffla implentations.
aviraxp said:
Then remove Boeffla swipe2wake helper. I think it can be simply removed through reverts, or build your own kernel auditor with Boeffla implentations.
Click to expand...
Click to collapse
I thought I did remove it, where is it exactly?
Edit: You, and anyone else, can message me on telegram, my username is @Nick80835
Just uploaded a small update after a long testing period. It's safe to say it's stable for use! I fixed a couple bugs, removed zram compression (not used, a waste of space), removed a little bit of bloat and set some settings to their proper values.
Nick80835 said:
Just uploaded a small update after a long testing period. It's safe to say it's stable for use! I fixed a couple bugs, removed zram compression (not used, a waste of space), removed a little bit of bloat and set some settings to their proper values.
Click to expand...
Click to collapse
would be helpful if you state update date in the title of thread
Uploaded a very tiny update, only change is the default GPU governor is now simple_ondemand
Hey at least implement pdesireaudio correctly
Well I don't feel like publicly saying **** about other's work (since the kernel is really good, awesome job man) but if you really want pdesireaudio working maybe you should pm me
Again nice work man, good kernel
Related
Overview:
This is a custom kernel based on Omni sources for our legendary i9000. This is only for 5.1.1/6.0.1 roms and no other version of android will be suppported
It works on any Omni based 5.1.1/6.0.1 rom.
>The zip you will download is flashable via recovery.
>> Use devil kernel manager or NStools to edit the kernel settings.
Features : - Multiple CPU governors (lulzactive, smartassV2, wheatley, lagfree, ondemandX)
- Tweaked smartassV2
- BFQ, Zen, VR & SIOPLUS I/O schedulers added
- Tweaked VR
- New TCP algorithms (westwood is default)
- Bigmem, up to 430mb
- CMA (MM only for now)
- Kernel compressed with XZ
- Compressed initramfs
- Dynamic page writeback
- Dynamic Fsync
- Custom ARM & INT voltages
- Voltages fixed for more stable OC
- Selectable GPU OC (not working properly for now)
- Fast charge
- BLX
- Live OC
- FULL O3 optimisations
- Call volume hack
- Touchwake
- BLN
- Zram
- Swap / Zram optimisations
- LMK tweaks
- SLQB memory allocator
- NEON optimized crypto routines
- Voodoo color
- SquashFS support (module)
- EXfat support (module)
- 720p patched bigmem libs
- Built from the latest Omni source
- Built using custom Cortex-A8 optimized UBERTC 5.3 toolchain of @Cl3Kener
Todo:- Backport more things from higher linux versions and fix remaining conflicts ...
- Fix GPU OC ... Well we have live OC, not worth the time i guess.
- Make CGROUP_TIMER_SLACK work
- GPU driver to DDK [email protected]
- Make a better (and more fancy) updater script
- Fixing the remaining issues [...]
What I wont do : - Enable TV out
- Upgrade linux version
- Add useless CPU governors or I/O schedulers
- make your phone as fast as a i9500
Please use it at your own risk! I am not responsible for any damage that may occur to your device.
Download :
Latest android 5.1.1 kernel :
Kernel_ION.zip MD5 : 2060f96fbffc98a1f2fae9108066b69a
http://www50.zippyshare.com/v/zVr8YvZ4/file.html
Latest android 6.0.1 kernel :
Kernel_CMAEXP.zip MD5 : 236f89a961b559c666a1c064aaccd728
http://www43.zippyshare.com/v/Yxm6WDuA/file.html
Old versions :
https://mega.nz/#F!3x5VTbiQ!87aMOGoDBuQZmiELhKlUkQ
Thanks:
@humberos
@DerTeufel1980
@kasper_h
@Alberto96
@Ezekeel
@xc-racer99, for his help on setting up my Github
@(°_o)
Anyone else who helped me
Source Code:
https://github.com/Coldwindofnowhere/android_kernel_samsung_aries
Custom built UBERTC with A8 optimisations : https://bitbucket.org/Coldwindofnowhere/
XDA:DevDB Information
Omni kernel, Kernel for the Samsung Galaxy S I9000
Contributors
Coldwindofnowhere, xc-racer99
Version Information
Status: Beta
Created 2015-10-02
Last Updated 2016-03-06
>If you like my work, hitting the thanks button won't hurt you<
good luck
Thanks for sharing ! I really want to check this kernel out, can someone tell me what is the recommended Omni LP release to be used with this kernel? A link in PM or a reply would be great.
Sent from my Nexus 7 using Tapatalk
idCyber said:
Thanks for sharing ! I really want to check this kernel out, can someone tell me what is the recommended Omni LP release to be used with this kernel? A link in PM or a reply would be great.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=61937705
Gesendet von meinem SM-G900F mit Tapatalk
idCyber said:
Thanks for sharing ! I really want to check this kernel out, can someone tell me what is the recommended Omni LP release to be used with this kernel? A link in PM or a reply would be great.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
If you can , that would be great if you test if on different 5.1.1 roms and tell me if it works or not
Coldwindofnowhere said:
If you can , that would be great if you test if on different 5.1.1 roms and tell me if it works or not
Click to expand...
Click to collapse
This kernel works with Code rom 5.1.1 the latest build and mostly everything work perfectly. However, to test this i ported it to my good old vibrant. The only issue is since Im guessing devil kernel manager doesnt support vibrant cant seem to change any values in devil. Thanks for building this kernel
falconscrest123 said:
This kernel works with Code rom 5.1.1 the latest build and mostly everything work perfectly. However, to test this i ported it to my good old vibrant. The only issue is since Im guessing devil kernel manager doesnt support vibrant cant seem to change any values in devil. Thanks for building this kernel
Click to expand...
Click to collapse
Assuming you used the kernel source (github.com/omni) to port to the vibrant, you won't have any options other than bigmem. The source code linked there doesn't have things such as Fast Charge, etc.
However, you can see if support for them is there by manually putting a "1" in the file /sys/kernel/fast_charge/force_fast_charge
(ie echo 1 > /sys/kernel/fast_charge/force_fast_charge from a terminal/adb shell).
Also, look out for selinux issues. If selinux is in enforcing mode, the Devil Manager may or may not be able to access the sysfs paths. Run "setenforce 0" to put it to permissive mode.
Speaking of source code, @Coldwindofnowhere have you uploaded the complete kernel source you used somewhere? I'd be curious to see it. Thanks for taking this project on!
xc-racer99 said:
Assuming you used the kernel source (github.com/omni) to port to the vibrant, you won't have any options other than bigmem. The source code linked there doesn't have things such as Fast Charge, etc.
However, you can see if support for them is there by manually putting a "1" in the file /sys/kernel/fast_charge/force_fast_charge
(ie echo 1 > /sys/kernel/fast_charge/force_fast_charge from a terminal/adb shell).
Also, look out for selinux issues. If selinux is in enforcing mode, the Devil Manager may or may not be able to access the sysfs paths. Run "setenforce 0" to put it to permissive mode.
Speaking of source code, @Coldwindofnowhere have you uploaded the complete kernel source you used somewhere? I'd be curious to see it. Thanks for taking this project on!
Click to expand...
Click to collapse
I didnt use the source code to do anything just replaced the boot image with that of vibrant and it seemed to boot up just fine and i could switch between smartass v2, and other addition. the only thing cant change the bigmem option over xl. It was just random since i have no clue how to build stuff.
falconscrest123 said:
I didnt use the source code to do anything just replaced the boot image with that of vibrant and it seemed to boot up just fine and i could switch between smartass v2, and other addition. the only thing cant change the bigmem option over xl. It was just random since i have no clue how to build stuff.
Click to expand...
Click to collapse
Ah, ok. I could be wrong, but I think if you replaced the boot.img with one from the Vibrant, then you're not even using the kernel from here. Weird that you still had the smartassv2 option...
If I'm wrong, someone please correct me
431mb ram possible??
xc-racer99 said:
Ah, ok. I could be wrong, but I think if you replaced the boot.img with one from the Vibrant, then you're not even using the kernel from here. Weird that you still had the smartassv2 option...
If I'm wrong, someone please correct me
Click to expand...
Click to collapse
Im not sure either because i have all govenors mentioned above while i can tweak everyone of them using kernel aditor apk and plus i can also toggle fast charge which wasnt present in omni rom for the vibrant. I have uploaded some screenshots and it is from code rom.
xc-racer99 said:
Assuming you used the kernel source (github.com/omni) to port to the vibrant, you won't have any options other than bigmem. The source code linked there doesn't have things such as Fast Charge, etc.
However, you can see if support for them is there by manually putting a "1" in the file /sys/kernel/fast_charge/force_fast_charge
(ie echo 1 > /sys/kernel/fast_charge/force_fast_charge from a terminal/adb shell).
Also, look out for selinux issues. If selinux is in enforcing mode, the Devil Manager may or may not be able to access the sysfs paths. Run "setenforce 0" to put it to permissive mode.
Speaking of source code, @Coldwindofnowhere have you uploaded the complete kernel source you used somewhere? I'd be curious to see it. Thanks for taking this project on!
Click to expand...
Click to collapse
Sure, i'll set a github soon, but trust me there are only minimal changes to the origianl code (even if adding liveOC seems harder since i only got build errors xD).
Btw i won't build anything this week, i'm busy with exams.
Github is up !
Coldwindofnowhere said:
Could someone help me to setup my github please ? (PM me)
Click to expand...
Click to collapse
Check your PM, let me know if you need more help.
Hey.
I tested it on 5.0.2 . stuck on bootanimation. Better mention that its for 5.1.1 .
Can you add support or please tweak it for 5.0.2
Now iam using RR lp 5.0.2
I removed some apps. And it have the same apps like omni. Its works faster than ever. Working theme engine. Only removed music and added apollo.
Has anyone have a bug where when you call someone the speaker mode work fine but the audio stops working when you turn off speaker mode
I had no problem with original omni kernel any fix because this is an awesome kernel
falconscrest123 said:
Has anyone have a bug where when you call someone the speaker mode work fine but the audio stops working when you turn off speaker mode
I had no problem with original omni kernel any fix because this is an awesome kernel
Click to expand...
Click to collapse
That's weird, i haven't changed anything concerning the audio in the kernel. You're using it on a vibrant right ? This might be the problem. I'm gonna try to reproduce this bug on my i9000 and see ....
Edit: try this http://www42.zippyshare.com/v/aZ6XgBlE/file.html
DO NOT FLASH, IT DOESN'T WORK (except if you want to give me a log or if you're really curious)
Any feedback on the vibrant version ?
Coldwindofnowhere said:
Any feedback on the vibrant version ?
Click to expand...
Click to collapse
The kernel didnt even flash no errors nothing whenever i flashed via twrp it would instantaneously reboot to recovery. Thanks again for atleast trying to fix the issue.
Coldwindofnowhere said:
Any feedback on the vibrant version ?
Click to expand...
Click to collapse
Bro. Can you add fast charge and the governers in omni kernal 5.0.2. Please
Thanks
Disclaimer:
I and XDA are not liable in a broken and bricked devices, doing so, take a nandroid backup and be cautious. Do at your own risk.
Click to expand...
Click to collapse
Info:
This kernel is based from the last google commit "2e34ea8". I hadn't seen a custom kernel in G1 work in MM update. The phone is much good but sadly the development of custom stuffs are bit poor. So it drives me to create a custom kernel. I think the battery of stock kernel is good enough, but it also lacks something IMHO. So basically I only added few things in this kernel(also knowing that this is my first custom kernel that ever made). I had cherry pick the things I think it suits my taste.
Click to expand...
Click to collapse
Features:
KCal Color Changer
CPU Freq can be control
AutoSMP Driver
Intelli Plug Driver
Simple GPU Algorithm
ExFAT Support
PM Kernel Driver
FSync Control
SELinux Permissive Mode On
Fast charging
Frandom
Zpool
LCD Notifier
I/O Scheduler:
sio
bfq
fiops
Some tweak and add small features
Click to expand...
Click to collapse
PS: I am a beginner and newbie on this stuff and still learning.
Credits:
@arvinquilao , for the patience at guiding me in this stuff.
@savoca, @neobuddy89, @faux123, @itsmerajit, @varunchitre15, @sandymanu for some sources and learning
XDA:DevDB Information
Eon Kernel, Kernel for the OEM Cross Device Development
Contributors
PineappleOwl
Source Code: https://github.com/PineappleOwl/msm-seed/tree/eon6.0
Kernel Special Features: KCal Support, Fast Charging, Intelliplug
Version Information
Status: Beta
Created 2016-01-20
Last Updated 2016-02-12
Some stuffs
Download Link:
eon-seed-1.0_boot
eon-seed-alpha_boot
Click to expand...
Click to collapse
Changelog:
February 12, 2016 [1.0]
Code:
Remove AutoSMP
Initial Port of Fast Charging
Add Frandom
Add Zpool
Add LCD Notifier
January 2016[ALPHA]
Code:
KCal Color Changer
CPU Freq can be control
AutoSMP Driver
Intelli Plug Driver
Simple GPU Algorithm
ExFAT Support
PM Kernel Driver
FSync Control
SELinux Permissive Mode On
I/O Scheduler:
sio
bfq
fiops
Some tweak and add small features
Just like flashing a normal boot.img
Go to bootloader, then
fastboot flash boot nameofboot.img
Click to expand...
Click to collapse
Also work with chainfire systemless root!
Or we can just flash it with an app like rashr if rooted
hyperay said:
Or we can just flash it with an app like rashr if rooted
Click to expand...
Click to collapse
Maybe flashify too
PineappleOwl said:
Maybe flashify too
Click to expand...
Click to collapse
I'm rashr user so I used that as example
are you will come Double tap wake up? Commintment on github page.
kaankulahli said:
are you will come Double tap wake up? Commintment on github page.
Click to expand...
Click to collapse
Dont know yet, but I tried working and researching on it for week but nothing happened.
I even check the source of Yuphoria's custom kernel and I hadn't see it working on Marshmallow.
Also I checked the Lenno Kernel from Moto E, it had DT2W but not working on us.
How's the SoT so far? I'm getting roughly 10minutes = 1% battery drain on my Cherry Mobile G1 with intersectRaven's kernel. I want to try this out if it's better in terms of battery life.
Flashing.... Thanks
Very impressive kernel dude! But here's some issues:
All 4 cores scaled at max freq
No sim after systemless root
But hey, I viberated colors and increased contrast. Screen looks amazing very big thanks!!!!
nhmanas said:
Very impressive kernel dude! But here's some issues:
All 4 cores scaled at max freq
No sim after systemless root
But hey, I viberated colors and increased contrast. Screen looks amazing very big thanks!!!!
Click to expand...
Click to collapse
Then I'll make the default value , a not-so-max freq. sir
The sim? Hmm Im pretty sure it is working. Currently, I have no problem with the sim sir
PineappleOwl said:
Then I'll make the default value , a not-so-max freq. sir
The sim? Hmm Im pretty sure it is working. Currently, I have no problem with the sim sir
Click to expand...
Click to collapse
Thank you for reply.
But I'm pretty sure sim isn't detected on your kernel. It got back when I flash stock kernel again
PS: This problem occurred after I flash systemless root. It was normal before root
Tengri biz menen
Help, i flashed the kernel but how did you improve the screen color? I downloaded KCAL color changer but I get an "Unfortunately, Color Changer has stopped." When I move 1 slider.. Does this require root?
nhmanas said:
Thank you for reply.
But I'm pretty sure sim isn't detected on your kernel. It got back when I flash stock kernel again
PS: This problem occurred after I flash systemless root. It was normal before root
Tengri biz menen
Click to expand...
Click to collapse
Does the stock rom have a conflict with it too, the systemless root?
Janjako16 said:
Help, i flashed the kernel but how did you improve the screen color? I downloaded KCAL color changer but I get an "Unfortunately, Color Changer has stopped." When I move 1 slider.. Does this require root?
Click to expand...
Click to collapse
Yes , it needs root permission sir.
PineappleOwl said:
Disclaimer:
Info:
Features:
Download Link:
PS: I am a beginner and newbie on this stuff and still learning.
Credits:
@arvinquilao , for the patience at guiding me in this stuff. @savoca, @neobuddy89, @faux123, @itsmerajit, @varunchitre15, @Sandymanu for some sources and learning
XDA:DevDB Information
Eon Kernel, Kernel for the OEM Cross Device Development
Contributors
PineappleOwl
Source Code: https://github.com/PineappleOwl/msm-seed/tree/eon6.0
Kernel Special Features: KCal Support
Version Information
Status: Alpha
Created 2016-01-20
Last Updated 2016-01-20
Click to expand...
Click to collapse
Does this kernel support FM Radio?
Is this kernel will be updated? I really like this one!
BronzieSmurf said:
Does this kernel support FM Radio?
Click to expand...
Click to collapse
Its stock based sir so the FM Radio is working fine
nhmanas said:
Is this kernel will be updated? I really like this one!
Click to expand...
Click to collapse
Yes sir. I will.
Can I flash this on CM13?
wow. finally! an intelliplug driver. thanks!
thanks
ill try this one
Dirty Unicorns 6.0.1 is probably the best marshmallow rom for amami so far , although it has some problems: camera app cannot take pictures at 20.7mp, and exfat-formated sdcard is not supported.
So I made a kernel to fix these problems. You can flash with twrp or flashfire.
Kernel_Amami_AOSP_6_20160709.zip contains aosp kernel built with exfat-nofuse and some other features, as well as other executables or libraries needed to identify and mount exfat(vold , blkid etc.) This may work with other aosp 6.0.1 based roms, but I never tried by myself.
2016.06.18 : I ported some features from other kernels like M5 kernel. Features included:
1. Various cpufreq governors, hotplug drivers and i/o schedulers
2. KCAL color control by @savoca
3. Faux Sound Control V3
4. CPU/GPU OC & UV
5. Vibrator intensity control
6. Ultra-ksm
7. Kexec-hardboot
8. Dynamic Fsync 1.2
9. Mac80211 injection patch and HID patch for keyboard support
10. Sysfs interface to Enable / Disable CRC on the data blocks
11. Exfat and Paragon NTFS(UFSD)
12. Zram
13. Merge upstream patches up to 3.10.102
MtkCamera.zip contains camera app from Mediatek devices with lollipop. It can take 20.7mp photos(3936 x 5248) and has some useful features like visual effects and qrcode scanner.
Modified kernel source : https://github.com/KuronekoDungeon/android_kernel_sony_msm
Download : https://drive.google.com/folderview?id=0B-DoK6BdpB2fZEZ5eG5NcnhYNFU&usp=sharing
If you're interested, Myself5 is willing to release M5 for Amami, but needs a maintainer, since he doesn't have a Z1c anymore. Maybe you can work with him on M5 for AOSP...
levone1 said:
If you're interested, Myself5 is willing to release M5 for Amami, but needs a maintainer, since he doesn't have a Z1c anymore. Maybe you can work with him on M5 for AOSP...
Click to expand...
Click to collapse
Is he working on a 3.10.9x kernel ?
maz-1 said:
Is he working on a 3.10.9x kernel ?
Click to expand...
Click to collapse
This is from main thread latest version...
levone1 said:
This is from main thread latest version...
Click to expand...
Click to collapse
cool, I guess I will be a tester then.
maz-1 said:
cool, I guess I will be a tester then.
Click to expand...
Click to collapse
He did say that testers won't really help. Without a device of his own, he'll need a maintainer.
levone1 said:
He did say that testers won't really help. Without a device of his own, he'll need a maintainer.
Click to expand...
Click to collapse
Well, I mean I will build, test and submit fixes if possible. But I'm afraid I don't have the time and knowledge to take over all the maintenance. Any other volunteers?
maz-1 said:
Well, I mean I will build, test and submit fixes if possible. But I'm afraid I don't have the time and knowledge to take over all the maintenance. Any other volunteers?
Click to expand...
Click to collapse
maybe we can jointly maintain ?
CLINTZ9 said:
maybe we can jointly maintain ?
Click to expand...
Click to collapse
Sounds good.
maz-1 said:
Sounds good.
Click to expand...
Click to collapse
cool !
CLINTZ9 said:
cool !
Click to expand...
Click to collapse
I've already ported a bunch of features to aosp kernel, just check out the commit history.
What left to be done : GPU governors, A few hotplug drivers/cpufreq governors not ported(hotplug : alucard , mako , intelliplug , cpufreq : HYPER, OndemandPlus, Nightmare , ElementalX, maybe more) , some of these features need to be modifeid or abandoned.
maz-1 said:
I've already ported a bunch of features to aosp kernel, just check out the commit history.
What left to be done : GPU governors, A few hotplug drivers/cpufreq governors not ported(hotplug : alucard , mako , intelliplug , cpufreq : HYPER, OndemandPlus, Nightmare , ElementalX, maybe more) , some of these features need to be modifeid or abandoned.
Click to expand...
Click to collapse
Hi, I install this, work well, but camera still laggy . What do you think, how else you can improve the image processing? The picture was much too sharp ... but it's better than before.
And...you can also add in your kernel any functions like as KryptonianKernel or AdvancedKernel
John.D.. said:
Hi, I install this, work well, but camera still laggy . What do you think, how else you can improve the image processing? The picture was much too sharp ... but it's better than before.
And...you can also add in your kernel any functions like as KryptonianKernel or AdvancedKernel
Click to expand...
Click to collapse
Laggy camera is a driver issue, just wait until sony updates software binaries for amami.
Hmm, why you delete MTKCamera? You have another app for taking photo in 21mp?)
MTKCamera cannot use frontcam. I think @SpiritCroc will try to add 20.7mp option to SnapdragonCamera, so wait for a new release.
maz-1 said:
MTKCamera cannot use frontcam. I think @SpiritCroc will try to add 20.7mp option to SnapdragonCamera, so wait for a new release.
Click to expand...
Click to collapse
I already added it, will probably be in next weekly
maz-1 said:
I've already ported a bunch of features to aosp kernel, just check out the commit history.
What left to be done : GPU governors, A few hotplug drivers/cpufreq governors not ported(hotplug : alucard , mako , intelliplug , cpufreq : HYPER, OndemandPlus, Nightmare , ElementalX, maybe more) , some of these features need to be modifeid or abandoned.
Click to expand...
Click to collapse
check your whatsapp inbox
What's 'jhead exif fix' file in your Gdrive link?
levone1 said:
What's 'jhead exif fix' file in your Gdrive link?
Click to expand...
Click to collapse
libjhead with this patch :
https://gist.github.com/updateing/2b58ebd4a8c75780443f28f514e9bb39
Photos token by Android N may contain wrong exif infomation and cause app crash on marshmallow/lollipop.
need help - CPU GOVs and frequencies
Hi,
first of all thanks for the kernel! I'm just migrated from RR Lollipop to MM DU ROM (today to the build of 17. June). I have strange issues with the kernel.
I can not change the CPU govs. More critical: The minimum CPU frequency is shown to be 1.8 GHz. Whatever I try, I cannot get the values gov/freq to stick.
Always when I reopen an tuning app, the settings are reverted.
Root seems to work fine. Also tried to disable SE-linux via terminal ("setenforce 0"). The same.
(Combinations I tried: kernel audiutor, performance control, system tuner... also on DU (3. june) + kernel (5. june)
Can somebody help me out?
Who can permanently adjust the CPU settings on DU with/without this kernel?
Thanks in advance!
Hi oneplus2 people!
This is my modified kernel with some kernel optimizations and some compiler optimizations.
The goal of abyss is to achieve improved performance/battery without the cost of stability.
I will not be overhauling this project with changes that are not logical to add.
This kernel should work on the latest 7.x.x roms like CyanogenMod.
It might work on other roms, but there will be little support for them.
How does one achieve this?
- build kernel with an optimized toolchain
- use compiler optimization flags (experimental)
- remove redundant code
- improve existing code with more efficient code
- etc. (most are not so easy to explain)
This kernel is built with mdalexca's latest UBER GCC 4.9.
Is there actually a performance improvement?
With all the changes added up, there should be. Whether or not one notices the difference is another thing.
For those interested in how the kernel optimizations will benefit/work, please look at my github source and read the commit messages.
For those interested in how the compiler optimizations/hacks will benefit/work, please look at this article.
Downloads:
Latest release
BasketBuild
Source:
GitHub
This was made by request from dsst22 who also tested this bad boi like crazy.
XDA:DevDB Information
abyss kernel for the OnePlus 2, Kernel for the OnePlus 2
Contributors
kwoktopus, dsst22, OnePlus, grarak, The Flash, arter97, Lord Boeffla, frap129, Linux, Google, CAF, a bunch of other major OEMs
Source Code: https://github.com/abyss-kernels/oneplus2
Kernel Special Features:
Version Information
Status: Nightly
Current Stable Version: 1.20
Stable Release Date: 2016-12-05
Created 2016-12-05
Last Updated 2016-12-13
Key Changes:
- upstream interactive governor (with Flash 1.0 profile by The Flash) (Google and CAF)
- upstream cpufreq driver (Google and CAF)
- upstream cpu-boost driver (Google and CAF)
- upstream random driver from Linux 4.1.31 (performance..!)
- slub/slab/slob/vmalloc patches
- flar2's slightly modified thermal driver
- using Linaro's power efficient workqueues throughout kernel
- using Adreno idler by arter97 to reduce frequency scaling without performance cost
- using power efficient "relaxed" macros throughout kernel (assembler)
- KCAL Control Driver by Savoca
- Android-Keyboard patch, use your device as an external keyboard!
- too many to list here, check out my source
How to install:
Place zip in to your internal storage
Place current ROM zip on to your storage
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
Flash kernel zip
Reboot
Don't like the defaults?
Use Kernel Adiutor to change the settings!
Frequently Asked Questions:
Is this a custom kernel?
I was asked this question once, and it posed as a real good question. I do not consider abyss to be a "custom kernel" per se, but more so as a modified kernel. The patches and features that go into this kernel do not make it customizable. What they do is improve what has already been implemented. It is like swapping a car's engine for a better one rather than just adding LED flooring lights and fancy car mats.
Can you add [this] and [that] feature?
Something I pride myself with this kernel is that it does not have a bunch of random, useless features or patches mashed into it. Everything put into this kernel is thought out and tested. I see a lot of works being made popular because it has [this] and [that] feature when really, it's nothing revolutionary. As a matter of fact, most things added to any kernel will not make it 5x better than any other kernel. Most of the time, simple is better; and in this case it definitely is!
For me
Thanks! I'll give it a go.
Giving it a go
Yess! Been waiting for this ever since i saw your OP2 repo!
Does this kernel install on a f2fs formatted system?
suraj.das said:
Yess! Been waiting for this ever since i saw your OP2 repo!
Click to expand...
Click to collapse
You can thank @dsst22 for helping with testing, or else you would have waited a very long time :silly:
socialdistortion said:
Does this kernel install on a f2fs formatted system?
Click to expand...
Click to collapse
I have not made any file system changes to the kernel. If the stock CM kernel supports, then this one will too.
Is kcal support present..??
chl1810 said:
Is kcal support present..??
Click to expand...
Click to collapse
unfortunately no.
good to see new kernel for our device, thanks and good luck
suraj.das said:
unfortunately no.
Click to expand...
Click to collapse
I wish it had
chl1810 said:
I wish it had
Click to expand...
Click to collapse
I can remember the YoshiShaPow falcon kernel
chl1810 said:
I wish it had
Click to expand...
Click to collapse
In the future
PeterImmel said:
I can remember the YoshiShaPow falcon kernel
Click to expand...
Click to collapse
You can probably see how much I've grown as a developer since then too :angel:
Works on a f2fs filesystem based rom. Testing it now...
Edit: No obvious bugs at the moment. Is it possible to implement some sort of charging control. The USB charging speed is super slow (on both this kernel and stock CM kernel).
kwoktopus said:
In the future
Click to expand...
Click to collapse
Nice!! thank you!!
Pretty smooth haven't found any bugs. Love the simplicity.
I can't imagine what it would be like with a little over clock.
adame09 said:
Pretty smooth haven't found any bugs. Love the simplicity.
I can't imagine what it would be like with a little over clock.
Click to expand...
Click to collapse
I trust the engineers that designed the chip to choose a safe maximum clock speed. Here's a pretty good article on the risks vs benefits, which outline some strong points.
But, if I were to add it, I would set the max value at boot to stay as stock values; so I'll leave it up to @dsst22 to decide.
I'll try this out for you dude. Impressive what you've done.
Code:
****Disclaimer: I'm not responsible if you destroy your device. Use at your own risk.
Introduction:
I saw a lot of demand/requests for a LOS compatible, F2FS kernel and wanted to make one. This kernel installer includes the kernel with F2FS drivers built-in and the required ramdisk changes to make F2FS mount. Energy Aware Scheduling is baked right into tabp0le kernel. You will get the best battery life and performance this device has to offer. You can find out more about EAS here. This kernel is built for stability, battery life and features without compromising performance. Overclocking is not going to happen. Please do not flash this on any ROM not based off LineageOS.
Note: The 4.0+ versions will ONLY work with Oreo. Please do not try and flash on Nougat!
Bug Reporting:
Please only report bugs and do so in the following format:
Device Firmware base:
Kernel Version:
Device ROM, version and date of release/nightly:
Governor:
Scheduler:
Any changes made within a kernel manager:
Any bootup scripts:
Brief description of bug:
Intended behavior:
Actual behavior:
Steps to reproduce bug:
Do this
Do that
See the bug
****Attach a logcat or you will be ignored****
Features:
F2FS /data support
F2FS /cache support
[*]Disabled verifiedbootstate check (will allow CTS/SafetyNet to pass on unlocked bootloader)
Forced fast charge on USB 2.0 (cherry-picked from CleanSlate Kernel by @tbalden
Double tap fingerprint sensor to sleep
Battery/sleep improvements
Option to disable/enable wakelocks: Bluedroid, wlan_rx, wlan_ctrl, wlan, IPA_WS
Option to disable/enable magnetic cover sensor
Sweep2Sleep option
Disable fsync option (will break reboot to recovery if disabled)
Separate options for I/O schedulers on internal/external storage
I/O enhancements
I/O Schedulers: noop, deadline, cfq, fiops, sio, fifo, sioplus, tripndroid, vr, zen, maple
Governors: sched, schedutil, alucardsched, darknesssched, conservative, ondemand, userspace, powersave, performance, interactive
Requires:
CM/LOS 14.1/AOSP/CAF based ROM
Highly Recommended:
ROM with full EAS support built in
ROM with Marlin or Vox Populi PowerHAL
Changelog:
02.12.18 - v3.03
Add WireGuard support
11.13.17 - v4.0-O
Oreo release
08.27.17 - v3.02
Merge latest caf
Update wifi drivers to latest U11 drivers
Patch kernel all the way up to Linux version 3.18.65
07.31.17 - v3.01
Rebase of latest caf
Fix EAS errors/cgroup errors
Far too much to list on this changelog
06.21.17 - v2.09
Get caught up with upstream
Remove cmdline incompatible with EAS
Many EAS tweaks
Remove force-encrypt
Much more, not going to list it all. See my github
Click to expand...
Click to collapse
Install:
Flash in TWRP.
Install your favorite kernel tweaking app for full functionality. EX kernel manager is my recommendation.
To get F2FS working, you need to research yourself. There are plenty of threads that tell you how.
Download:
Download Repo
Additional Credits:
Thanks to @crpalmer for all his hard work on the HTC 10 LOS kernel
Thanks to @Captain_Throwback for helping me get F2FS working
Thanks to @tbalden for force fast charge code & other code I borrowed too
Thanks to @flar2 for a bunch of code I borrowed from ElementalX
Thanks to @franciscofranco for a bunch of code
Thanks to @CrazyGamerGR for a bunch of code
Thanks to @Eliminater74 for taking a lot of his time to help me make this a reality and for first porting EAS to the HTC 10
Thanks to @Cuffuffles for giving me ramdisk edits to use with AnyKernel2 for EAS to work with LOS
Thanks to @RenderBroken for proper ramdisk settings & EAS v1.2 commits
Thanks to my testers: @rav101, @Meowdib (If I forgot you let me know)
Click to expand...
Click to collapse
tabp0le Sources:
tabp0le EAS Kernel Source
tabp0le AnyKernel2
Original Sources:
LineageOS Kernel
Original EAS Kernel Source
EAS v1.2 Kernel Source
AnyKernel2 by @osm0sis
XDA:DevDB Information
tabp0le HTC 10 EAS CAF/LOS/AOSP Kernel, Kernel for the HTC 10
Contributors
tabp0le
Source Code: https://github.com/tabp0le/android_kernel_htc_msm8996
Kernel Special Features: Energy aware scheduling (EAS), F2FS support, Fast charge USB, much more..
Version Information
Status: Stable
Current Stable Version: 3.04-Nougat | 4.0-Or
Stable Release Date: 2017-11-13
Created 2017-02-27
Last Updated 2018-02-12
Reserved
Reserved
Thanks,but can't find it.
Thanks, but the is no download in the repo.
I think this is the link.
https://cloud.spryservers.net/s/YlwSeyCizqLCyNm?path=/tabp0le-EAS
In v0.9 DoubleTap2Sleep on the fingerprint worked better imo..
I have to disable this function and so I changed it to stock behavior for now.
Fixed the OP with link. Oops!
2 threads?
Hi @tabp0le ! Can you share your EX KM settings (all tuning parts) ? Thanks for the kernel (and the rom).
ali nz said:
2 threads?
Click to expand...
Click to collapse
Yes, the EAS kernel and original kernel are updated differently and have different version numbers. It's too confusing for me to leave them in the same thread.
ordeniz said:
Hi @tabp0le ! Can you share your EX KM settings (all tuning parts) ? Thanks for the kernel (and the rom).
Click to expand...
Click to collapse
Right now I'm not using any custom settings. You could ask @INDIAN-MAfIA what he uses on Nebula, or look at the Nebula EAS thread because those EAS settings should all work here too.
Hi @tabp0le
I just tried your RR builds and while I do know that these are your private builds for your own use its just that they are the best damn AOSP builds! Most feature rich and stable builds at the moment. Hence I had a small request. It's okay if you don't want to implement it. So here goes… could you please implement an option so that the stock android colour scheme could be used for the settings and brightness slider and such? It previously used to be green and teal(? I think. Not good with colour names. I just remember quick settings used to be a different shade of Gray. Like in stock rom) Now it's Gray and blue. Like in the brightness slider and downloads bar. Could you please implement something that allows me to use the old colours? Thanks.
tabp0le said:
Yes, the EAS kernel and original kernel are updated differently and have different version numbers. It's too confusing for me to leave them in the same thread.
Click to expand...
Click to collapse
No...i mean 2 threads for EAS?
jhadsfi said:
Hi @tabp0le
I just tried your RR builds and while I do know that these are your private builds for your own use its just that they are the best damn AOSP builds! Most feature rich and stable builds at the moment. Hence I had a small request. It's okay if you don't want to implement it. So here goes… could you please implement an option so that the stock android colour scheme could be used for the settings and brightness slider and such? It previously used to be green and teal(? I think. Not good with colour names. I just remember quick settings used to be a different shade of Gray. Like in stock rom) Now it's Gray and blue. Like in the brightness slider and downloads bar. Could you please implement something that allows me to use the old colours? Thanks.
Click to expand...
Click to collapse
Thanks man! Best suggestion i have for the color is using substratum to customize.
ali nz said:
No...i mean 2 threads for EAS?
Click to expand...
Click to collapse
One is barebones EAS no tweaks.
tabp0le said:
Thanks man! Best suggestion i have for the color is using substratum to customize.
Click to expand...
Click to collapse
I could find themes for pixel ui which rom has but not for aosp ui which I want. Thanks anyway though. Awesome work on kernel and rom.
jhadsfi said:
I could find themes for pixel ui which rom has but not for aosp ui which I want. Thanks anyway though. Awesome work on kernel and rom.
Click to expand...
Click to collapse
Thanks man. AOSP is pixel actually. AOSP is whatever google says it is in a given year. Nexus is AOSP for MM, Pixel for N. Just the way it goes. I think theres a new tool out there now that you can do the customizations yourself without an entire theme. Not sure what it's called but I think it was in XDA news the other day.
tabp0le said:
Thanks man. AOSP is pixel actually. AOSP is whatever google says it is in a given year. Nexus is AOSP for MM, Pixel for N. Just the way it goes. I think theres a new tool out there now that you can do the customizations yourself without an entire theme. Not sure what it's called but I think it was in XDA news the other day.
Click to expand...
Click to collapse
Oh haha. I thought pixel had some proprietary code so it wasn't AOSP. Guess I was wrong. Thanks for the tip. I'll search for it.
I flashed latest v1.01 but in Ex kernel manager and in phone info i see v0.9. I've already tried to flash again v1.0.1 without success, but in ex kernel manager i see termal throttling option that wasn't there in v 0.9. What could have happened?
Edit: i'm on dirty unicorns 11.1 now
AntoRei said:
I flashed latest v1.01 but in Ex kernel manager and in phone info i see v0.9. I've already tried to flash again v1.0.1 without success, but in ex kernel manager i see termal throttling option that wasn't there in v 0.9. What could have happened?
Edit: i'm on dirty unicorns 11.1 now
Click to expand...
Click to collapse
I know DU has problems with EAS. The thermal settings should all be the same. Not sure what you are seeing. Anyone else having problems flashing 1.01?
tabp0le said:
I know DU has problems with EAS. The thermal settings should all be the same. Not sure what you are seeing. Anyone else having problems flashing 1.01?
Click to expand...
Click to collapse
It's better to use stock kernel? I'd like to use your kernel