Develop Bugs

[KERNEL][5.1.1/6.0.0][GCC 5.3] Omni kernel (06/03/2016)

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

[KERNEL][LineageOS 13/14.1] Steel 6/7 Kernel

-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

CarboniteKERNEL for the OnePlus 5

Hi OnePlus 5 peeps!
Today (June 27th), I graduated from high school!
In more important news, I finished upstreaming the OnePlus 5 kernel to the latest stable kernel version...
Whoa, what is this?
This is my personal kernel that I run as the OnePlus 5 is my daily driver.
I will not claim my work as the best at anything, but just know that I would not do anything to this kernel that could potentially ruin my own device.
Additionally, this is the kernel that comes built into CarbonROM.
There are three versions of this kernel:
AOSP aka AOSP/LOS build - Flash this on any source built custom ROM except for CarbonROM
CR-5.1 aka CarbonROM build - Flash this on CarbonROM
OOS aka OxygenOS build - Flash this version on OxygenOS
Main features:
Upstreamed Linux kernel version, went from v4.4.21 -> v4.4.79
Backported random driver from Linux v4.12 (latest and greatest)
Backported scheduler from Linux v4.9 (latest android kernel branch)
Upstreamed F2FS driver from f2fs-stable/linux-4.4.y
KGSL driver improvements
MDSS driver improvements
SOC driver improvements
Built using Optimization Level 2
Added maple io scheduler (default) by frap129
Added adreno idler by arter97 with tweaks from frap129
Vibrator motor control by flar2
Kcal control driver from EX kernel
Many wakelocks disabled
Switched to power efficient workqueues across the kernel
Built with Google's latest stable gcc-4.9
Anykernel 2.0 by osm0sis! Compatible with all OxygenOS based roms
Download:
Latest builds
OxygenOS boot.img
How to install:
1. Reboot into the latest stable TWRP build
2. Download kernel zip and make sure it is in your internal storage (/sdcard)
3. Reboot into TWRP
4. Double check here to see if you require any additional instructions
5a. Install -> Install image -> select oxygen-4.x.x-boot.img -> swipe to install
5b. Install -> select CarboniteKERNEL-XXX-Rx-OP5-N.zip -> swipe to install
6. Reboot
DISCLAIMER!
If you don't understand my instructions, that's too bad >
If you are unsure about what this thing is, I highly advise you do some research before going through with installing...
Updates will come as regular as I want them to, don't ask me when I'll release cause you'll know when it comes out >:'D
XDA:DevDB Information
CarboniteKERNEL for the OnePlus 5, Kernel for the OnePlus 5
Contributors
adinkwok, nathanchance, flar2, Lord Boeffla, osm0sis, etc
Source Code: https://github.com/adinkwok/oneplus5-kernel
Kernel Special Features: One of Taylor Swift's exes should write a song called "Maybe You're the Problem"
Version Information
Status: Testing
Created 2017-06-28
Last Updated 2017-08-02

While this reserved post is not being used, enjoy this video! (Find me at 0:50s and twice at 2:54 :silly

For OxygenOS users:
Code:
[B]If you are on OxygenOS and are coming from another custom kernel:[/B]
Download the latest stock.4.X.X-boot.img
You [B]must[/B] flash the boot.img before flashing the kernel!
[B]If you are on OxygenOS are switching to a different custom kernel:[/B]
Download the latest stock.4.X.X-boot.img
You [B]must[/B] flash the boot.img before switching kernels!
For AOSP/LOS/RR/etc users:
Code:
[B]If you are coming from another custom kernel:[/B]
You [B]must[/B] reflash your ROM build before flashing this kernel!
[B]If you are on AOSP/LOS/RR/etc and are switching to another custom kernel:[/B]
You [B]must[/B] reflash your ROM build before flashing another kernel!
Why is it like this?
I have included some ramdisk modifications that set the default settings for this kernel. When you come from a different custom kernel, the ramdisk changes from that kernel may conflict with the changes I intend to have. Likewise when you switch to a different kernel; my ramdisk changes may conflict with the changes they intend to have. When you flash the stock boot.img, it replaces the modified ramdisk with a clean one, removing these conflicts.

And it's here, get it while it's hot folks! First upstreamed kernel for the OP5

Thanks for joining the party :highfive:
Sent from my OnePlus5 using XDA Labs

gz on graduating! and thx for the kernel :=

Congratulations on the graduation buddy,
Just flashed and I had charging cycling on and off (using dash charger in car on freedom v1.1). Flashed EX and charging is fine. Need charge ATM but maybe a little later I can help you get a log.
Sent from my OnePlus5 using XDA Labs

congratulations! awesome... so smart!!!!!!!

rav101 said:
Congratulations on the graduation buddy,
Just flashed and I had charging cycling on and off (using dash charger in car on freedom v1.1). Flashed EX and charging is fine. Need charge ATM but maybe a little later I can help you get a log.
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
Hmmm never noticed this... I guess the graduation drinks are getting to me. I'll re-upload a stable build without upstreaming as that's definitely the culprit.

What an amazing day for you (Congratulations!) and the OP5 community!
I was really loving and enyoing all your efforts you did for the OPO (Pure Nexus port) and the amazing Carbon ROM.

adinkwok said:
Hmmm never noticed this... I guess the graduation drinks are getting to me. I'll re-upload a stable build without upstreaming as that's definitely the culprit.
Click to expand...
Click to collapse
I'm the first to report so let's see if anyone else has the same issue. I will also try for logs later on though I do have a lot on today (so might be this evening).
I didn't actually reboot or get to try a different charger to help diagnose so don't want you doing more work that you need to for what could me my issue
Sent from my OnePlus5 using XDA Labs

rav101 said:
I'm the first to report so let's see if anyone else has the same issue. I will also try for logs later on though I do have a lot on today (so might be this evening).
I didn't actually reboot or get to try a different charger to help diagnose so don't want you doing more work that you need to for what could me my issue
Click to expand...
Click to collapse
I can confirm the issue because while I was bringing up the upstream branch I ran into this issue with dash charging and I thought I solved it. Time to debug!
Edit: link updated without the upstreaming, everything else still stands though

adinkwok said:
I can confirm the issue because while I was bringing up the upstream branch I ran into this issue with dash charging and I thought I solved it. Time to debug!
Edit: link updated without the upstreaming, everything else still stands though
Click to expand...
Click to collapse
No problem buddy,
Be good once it's all resolved and we have the benefits of upstream kernel code as well!! Your time and effort is appreciated!
Sent from my OnePlus5 using XDA Labs

@rav101 happy to see u around buddy

dukat0s said:
@rav101 happy to see u around buddy
Click to expand...
Click to collapse
For sure my friend.
How you finding the OP5?
Sent from my OnePlus5 using XDA Labs

rav101 said:
For sure my friend.
How you finding the OP5?
Click to expand...
Click to collapse
Cool my friend !like it.just got rid of my s8+. Was bored

Is DT2W working for you guys?

bartelamo said:
Is DT2W working for you guys?
Click to expand...
Click to collapse
Seems to be a problem among a few custom built kernels, we're looking into it.

bartelamo said:
Is DT2W working for you guys?
Click to expand...
Click to collapse
adinkwok said:
Seems to be a problem among a few custom built kernels, we're looking into it.
Click to expand...
Click to collapse
It's because OOS has a hal that already uses a switch for dt2w.

New update, still looking into the gestures issue.
However, Dash Charging is fixed on the upstream kernel so here it finally is! I also added a bunch of sched patches, a thermal patch, and some other misc stuff from the latest CAF branch.
Adin-Kernel-R2-OP5-OOS-N.zip

[Kernel] [MIUI] [PIE] LoverOriented Kernel

I am very happy here in this time the device is released more than two years, it probably means we have been with our phone for years.
also LoverOriented Kernel still be here, I am honored if you flash this kernel on your device.
For the builds for MIUI PIE, please follow my telegram channel:
MOD EDIT: TG link removed
Features:
Based on latest caf pie tag with latest ACK upstream merged
FULL support for MIUI userspace(OTA, nightmode, vibration tweaks.....)
PELT EAS which backported from android-4.14
Effective use of userspace perf boost under EAS, make it works with dynamic sched boost
Build with the newest Clang 10 with Polly and LTO optimization
Port ALL optimizations from sultanxda's kernel, and up-to-date it
Max 24w QC3.0 Fast charging, and unliminted PD Fast charging (Remove thermal files by yourself if really need it)
KCAL Advanced color control
Undervoltage CPU, safety
Zram support with upstream lz4 compression algorithm, and max swappiness is 200 now
Optimized network scheduling
FS fsync toggle on/off
F2FS support with arter97's GC
Optimized CFQ io-sched
...... there is more
Donation:
MOD EDIT: TG link removed
Kernel source:
https://github.com/wloot/android_kernel_xiaomi_msm8998

Mi room 9.8.15 beta work?

thank you for your job.

Another kernel for chiron, will try soon
Thanks for your hard job

Works on eu?

Devager said:
Works on eu?
Click to expand...
Click to collapse
Yes

It works very well. Thank you

A known issue could not be added to some modules for the machine at kernel root to change the automatic settings of the ROM. The other is not working well.

ttl fix module is activated ?

Which version is stable? ?

Devager said:
Which version is stable?
Click to expand...
Click to collapse
i am use 390

Thanks !! It runs very good

Your kernel sounds awesome. Is the Wireguard Module present?

Wloot never answered any questions outside of her husband.

你的内核工作得很好，但是设置应用程序有问题。我已经重新启动了。不知道如何解决问题，当你不提供细节Your kernel is working well, but there's a problem with the settings app. I've rebooted. Don't know how to solve the problem when you don't give details?

4.4.194 works great, thank you @wloot

สุรินทร์ พลโธา said:
你的内核工作得很好，但是设置应用程序有问题。我已经重新启动了。不知道如何解决问题，当你不提供细节Your kernel is working well, but there's a problem with the settings app. I've rebooted. Don't know how to solve the problem when you don't give details?
Click to expand...
Click to collapse
run su -c "dmesg | grep device_verify" in terminal, and give me outputs

wloot said:
run su -c "dmesg | grep device_verify" in terminal, and give me outputs
Click to expand...
Click to collapse
4 ..4.194 Fix It Really a 553 solved by reboot 2-3 times thanks for reply

สุรินทร์ พลโธา said:
4 ..4.194 Fix It Really a 553 solved by reboot 2-3 times thanks for reply
Click to expand...
Click to collapse
i see that the recent reply are both by you just now:silly::silly:

4.4.194 [41] It works very well. Thank you for your permission to work in the background.

[Kernel] [All ROMs] [ALL VARIANTS] Glassrom kernel

This is the stock kernel that ships with glassrom (or will ship with it)
5g variants are not yet supported
It is based off kirisakura kernel with additional hardening from my side.
You get this:
All the features from kirisakura kernel
Removed qualcomm's rmnet drivers
COMPAT_VDSO is disabled to enable full vDSO ASLR
KSPP patches have been applied
Clang control flow integrity (https://source.android.com/devices/tech/debug/cfi)
Backward edged control flow integrity:
Strong protections enforced by shadowcallstack (https://source.android.com/devices/tech/debug/shadow-call-stack)
Weak protections enforced by adding stack canaries to everything and ensuring ASLR is of a decent enough quality
Compiled with -O3 and Polly for maximum performance
Wireguard driver has been removed
AVB depends on the ROM. Flashing it on glassrom/oxygenos will definitely cause it to boot with enforcing AVB. On other ROMs this shouldn't happen
Selinux forced enforcing patch from Samsung
Yama is enabled and set to SCOPE_NO_ATTACH
Uses sdfat driver to provide vfat and exfat drivers
Todo:
Port Linux-hardened patch
fix fingerprint on oos
Notes:
Flashing it on oxygenos will break dt2w
Flashing the kernel regardless of ROM or device combination will break twrp ramdisk boot. The only way to boot twrp is using fastboot boot, installing it to the ramdisk will always lead to a kernel panic. This is not a bug and will not be fixed
Download: see release post https://forum.xda-developers.com/showpost.php?p=81105101&postcount=8
Source:
https://github.com/GlassROM-devices/android_kernel_oneplus_sm8150
Donations:
Most of the hard work was done by @Freak07 so check out his thread and buy him a coffee

anupritaisno1 said:
This is the stock kernel that ships with glassrom (or will ship with it)
5g variants are not yet supported
It is based off kirisakura kernel with additional hardening from my side.
You get this:
All the features from kirisakura kernel
Removed qualcomm's rmnet drivers
COMPAT_VDSO is disabled to enable full vDSO ASLR
KSPP patches have been applied
Clang control flow integrity (https://source.android.com/devices/tech/debug/cfi)
Backward edged control flow integrity:
Strong protections enforced by shadowcallstack (https://source.android.com/devices/tech/debug/shadow-call-stack)
Weak protections enforced by adding stack canaries to everything and ensuring ASLR is of a decent enough quality
Compiled with -O3 and Polly for maximum performance
Wireguard driver has been removed
AVB depends on the ROM. Flashing it on glassrom/oxygenos will definitely cause it to boot with enforcing AVB. On other ROMs this shouldn't happen
Selinux forced enforcing patch from Samsung
Yama is enabled (does nothing significant for now)
Todo:
Set Yama to level 3 (breaks magisk)
Port Linux-hardened patch
Notes:
Flashing it on oxygenos will break dt2w
Flashing the kernel regardless of ROM or device combination will break twrp ramdisk boot. The only way to boot twrp is using fastboot boot, installing it to the ramdisk will always lead to a kernel panic. This is not a bug and will not be fixed
Download:
https://mirror.apexcdn.net/files/glassrom/unsigned.zip
Source:
https://github.com/GlassROM-devices/android_kernel_oneplus_sm8150
Click to expand...
Click to collapse
Fingerprint is broken on oos

Kaz205 said:
Fingerprint is broken on oos
Click to expand...
Click to collapse
Yeah sorry about that. I'll make a version for oos soon
I did test it for a short while on oos but did not test it enough

Merged in the latest kernel from kirisakura git and also merged in 4.14.156
It boots fine but I don't have a good internet connection to be able to upload it
Will do so soon

anupritaisno1 said:
Merged in the latest kernel from kirisakura git and also merged in 4.14.156
It boots fine but I don't have a good internet connection to be able to upload it
Will do so soon
Click to expand...
Click to collapse
Thanks! Does this one work with OOS?

MrGimpGrumble said:
Thanks! Does this one work with OOS?
Click to expand...
Click to collapse
I eventually plan to stop supporting oos
OOS is proprietary for one and such a system is almost never secure. And if you don't believe me just look at their past vulnerability announcements. Almost all oxygenos vulnerabilities come from the fact that oneplus finds loopholes around Google's CTS. Who knows what other holes they've opened up that Google forgot to add checks for
Further, oos has many "memory optimisation" drivers that directly try to access ram and break most of the security features I'm implementing. Most custom ROMs do not have these and the drivers can be safely disabled
I will also add that this kernel is almost functionally identical with kirisakura kernel. Yes I might merge upstream slightly faster but other than that there is no difference that you would notice. The only difference is that I'm enabling all the security features that must be enabled - especially CFI and shadowcallstack which come standard on any Google pixel device
As for wireguard I just think running a VPN in kernel space is a very bad idea. Not to mention I have confirmed that on Android the tunnel leaks ipv6 traffic if you're not careful and no, disabling ipv6 is not the solution. The userspace go implementation is much safer and I mean it. The userspace implementation almost never leaks ipv6 traffic. Not to mention Go is a much safer language than C

okay new update is in the attachments
changes: linux 4.14.156
upstreamed to oos open beta 6 (doesn't mean fixed fingerprint yet)
upstreamed wifi driver and audio driver to latest caf tag (LA.UM.8.1.r1-12200-sm8150.0)
yama is now at level 3
all upstream changes from kirisakura. except for wake gestures as lineagehw seems to already have those
oos users should disable smart boost from settings

okay new build is here
changelog:
linux 4.14.157
upstreamed sdfat driver
fixed a weird kernel panic that happened on anything other than oxygenos when the device was fast charging from a very low battery

anupritaisno1 said:
okay new build is here
changelog:
linux 4.14.157
upstreamed sdfat driver
fixed a weird kernel panic that happened on anything other than oxygenos when the device was fast charging from a very low battery
Click to expand...
Click to collapse
work on pa?

ryshd296 said:
work on pa?
Click to expand...
Click to collapse
Please test it and let me know
It should boot on any ROM that can enforce selinux

anupritaisno1 said:
Please test it and let me know
It should boot on any ROM that can enforce selinux
Click to expand...
Click to collapse
This sent me into an immediate Qualcomm crash dump upon booting on both stock OOS and Omni for OnePlus 7t global variant.
Previous releases as well, not just the newer release.

scott.hart.bti said:
This sent me into an immediate Qualcomm crash dump upon booting on both stock OOS and Omni for OnePlus 7t global variant.
Previous releases as well, not just the newer release.
Click to expand...
Click to collapse
Please duplicate the crashdump message exactly
Especially send the "PC at" line and the error message if present
If the error message is blank please mention that it is
If you get a PC at __cfi_check_fail message please mention this

@scott.hart.bti still waiting for your response
Please send the crash log if possible

Do i need ma
gisk companion for this?

psychemisha said:
Do i need ma
gisk companion for this?
Click to expand...
Click to collapse
No you don't
However somewhere around ob4 maintaining compatibility with oxygenos became next to impossible without breaking custom ROMs
I think most users are still on OOS. If not I can just release builds for custom ROMs

Costum plz

is the development stopped?