{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
C:
#include <android/disclaimer.h>
/*
Your warranty is now VOID
I am not responsible for any damage you made to your device
You have been warned
*/
WARN_ON(1);
This is a custom kernel for the Galaxy M21, shipped with Exynos9611, tested on M215FDDU3CVL1
The name "Grass" came from a character of Genshin Impact to fill the background.
Features
Disable Samsung securities, debug drivers, etc modifications.
Checkout and rebase against Android common kernel source, Removing Samsung additions to drivers like ext4,f2fs and more.
Based on A51 OneUI5 latest kernel sources.
Compiled with bleeding edge Neutron Clang 17, with full LLVM binutils, LTO (Link time optimization) and -O3.
Import Erofs, Incremental FS, BinderFS and several backports.
Supports DeX touchpad for corresponding OneUI ports that have DeX ported.
Lot of debug codes/configuration Samsung added are removed.
Upstreamed to 4.14.150 (for now, will be more)
Added wireguard driver, an open-source VPN driver in-kernel
More to come...
How to flash- The kernel is provided with AnyKernel3 zip, which can be just flashed on recovery, it will replace the kernel Image only to this kernel.
Download below
Sources
If you want to support my work
This will link to a friend's PayPal who always helps me.
Donate
Reserved
What is the major difference between the stock kernel and your grass kernel?
what does it improves after installing
why does it says oneui5 in the zip?
Abdur Rahim Oni said:
What is the major difference between the stock kernel and your grass kernel?
what does it improves after installing
why does it says oneui5 in the zip?
Click to expand...
Click to collapse
Just various ports and removing debugging increases perf a bit
OneUI5 cuz it's based on A51 OneUI5 and build script is like that
M215FDDU3CVL1 без перепробавал
все тврп рекавери
Just to be sure
is this a kernel or an upgrade to the firmware??
@Royna
w1nk1 said:
M215FDDU3CVL1 как разблакировать загрузчик без пк
Click to expand...
Click to collapse
You don't need a pc to unlock bootloader, but you need some device that detects USB like a tv or another phone if you've got an adapter.
But you will need a pc to do everything else, like flashing recovery/magisk.
I installed this with LMOdroid 4.1 GSI. Geekbench 6 CPU score before and after:
BobaBoi69 said:
Just to be sure
is this a kernel or an upgrade to the firmware??
@Royna
Click to expand...
Click to collapse
Hey friend BobaBoi69 ,
We need GrassKernel for A11 too. I'd love that.
Do you happen to know any custom kernel that works on anything A11 onwards? If yes pls share
OldNoobOne said:
Hey friend BobaBoi69 ,
We need GrassKernel for A11 too. I'd love that.
Do you happen to know any custom kernel that works on anything A11 onwards? If yes pls share
Click to expand...
Click to collapse
i am currently trying out naz kernel and honestly
switch to A12 LPOS REBORN it is an actual evolved and patched version i know the old one had problems but this one is a pure monster more like a beast mode monster
i love the thermal
BobaBoi69 said:
i am currently trying out naz kernel and honestly
switch to A12 LPOS REBORN it is an actual evolved and patched version i know the old one had problems but this one is a pure monster more like a beast mode monster
i love the thermal
Click to expand...
Click to collapse
Hi Bobaboi69 friend,
I'm Happy for you
A12 LPOS REBORN Kernel.. do you have link for the kernel or rom ?
Ref: [ https://forum.xda-developers.com/t/...21-2020-21-tukirom-v1-2.4588319/post-88590585 ]
Hey Friend,
I just upgraded one of my SM-M215G devices to official A13 and its OneUI5.1 Core Version (Baseband M215GDDS3CWD1-20230522142126). Though I'm not able to flash any A13 GSI on it using (TWRP-3.5.2-m21-v3.1-A12.tar) , the oem unlock button is partially greyed out but not fully, its still light blue color, dunno whats going on , I relocked the unlockd the bootloader 3rd time now with no interference in setup process but I feel Shamshung might have introduced Bootloader Unlock Waittime just like in case of Shaomi devices :-/
Click to expand...
Click to collapse
OldNoobOne said:
Hi Bobaboi69 friend,
I'm Happy for you
A12 LPOS REBORN Kernel.. do you have link for the kernel or rom ?
Click to expand...
Click to collapse
I have the rom itself
I have uploaded the link in thread
I have added you to the thread try downloading it from there
If you face any kinds of problems ping me right away @OldNoobOne
BobaBoi69 said:
I have the rom itself
I have uploaded the link in thread
I have added you to the thread try downloading it from there
If you face any kinds of problems ping me right away @OldNoobOne
Click to expand...
Click to collapse
Thanks friend Bobaboi69,
I am on baseband CWD1 and the Stock A13 (May Update) seems to be a R/O-System & No GSI boots past logo
I am scared to flash any ROM zips after I flashed Tuki1.2 coz my IMEI got erased when I tried to wipe phone & install Lineage 20 zip. I only upgraded from A11 Stock to A13 Stock just to try Grass Kernel. Grass Kernel is Faaaast
OldNoobOne said:
Thanks friend Bobaboi69,
I am on baseband CWD1 and the Stock A13 (May Update) seems to be a R/O-System & No GSI boots past logo
I am scared to flash any ROM zips after I flashed Tuki1.2 coz my IMEI got erased when I tried to wipe phone & install Lineage 20 zip. I only upgraded from A11 Stock to A13 Stock just to try Grass Kernel. Grass Kernel is Faaaast
Click to expand...
Click to collapse
Apparently my phone being the SM215F doesnt supprt A13 i am using the Current naz kernel which is keeping my phone cold and giving out better performance than before
But if the grass kernel seems to be working fine
Then stay within that kernel as it can be compatible with your model
BobaBoi69 said:
Apparently my phone being the SM215F doesnt supprt A13 i am using the Current naz kernel which is keeping my phone cold and giving out better performance than before
But if the grass kernel seems to be working fine
Then stay within that kernel as it can be compatible with your model
Click to expand...
Click to collapse
Thanks friend,
I'm not comparing Naz Kernel with Grass Kernel, I'm not qualified to make any comment on kernels except as a general user perspective but right now kernel is not my problem really, I just want to get 1UI5.1 Core out and install GSI like Elixir/Crdroid/Ancient/Derp etc. but the problem is my bootloader is not fully unlocked and shamshung got fastboot/d disabled. Binary 3 wont allow Binary 1/2 also i read somewhere that May Update Stock ROM is RO-ROM. Why is shamshung ruining its own business, they should give some freedom to their customers..strange behavior.
I never knew about Naz Kernels existence untill you mentioned it.
OldNoobOne said:
Thanks friend,
I'm not comparing Naz Kernel with Grass Kernel, I'm not qualified to make any comment on kernels except as a general user perspective but right now kernel is not my problem really, I just want to get 1UI5.1 Core out and install GSI like Elixir/Crdroid/Ancient/Derp etc. but the problem is my bootloader is not fully unlocked and shamshung got fastboot/d disabled. Binary 3 wont allow Binary 1/2 also i read somewhere that May Update Stock ROM is RO-ROM. Why is shamshung ruining its own business, they should give some freedom to their customers..strange behavior.
View attachment 5925235
I never knew about Naz Kernels existence untill you mentioned it.
Click to expand...
Click to collapse
The only way to fix this might be to downgrade to lower firmware version i.e the 2022 patch
As for me with my SM215F the bootloader option is not greyed out but still allows me to turn it on and off
Let me know it its working or not
OldNoobOne said:
View attachment 5925235
Click to expand...
Click to collapse
It's supposed to be like this. This means your bootloader is unlocked. Once unlocked, you can only re-lock it from download mode which is why it's greyed out in settings.
newt23 said:
It's supposed to be like this. This means your bootloader is unlocked. Once unlocked, you can only re-lock it from download mode which is why it's greyed out in settings.
Click to expand...
Click to collapse
Yes I got some help from Curstantine & so Bobaboi69 was right, after I downgraded from M215G A13 May 2023 stock Firmware to M215F A12 Sept 2022 Stock Firmware now GSI boots again. Yes bootloader unlocked but its going to be a challenge to flash Grass Kernel now. Im gonna try though. Thanks for all your help friends.
#EDIT: Grass Kernel (June 2023 version) booted, the older version booted too. I am going to try Mint Kernel too
Thats amazing good thing
OldNoobOne said:
Yes I got some help from Curstantine & so Bobaboi69 was right, after I downgraded from M215G A13 May 2023 stock Firmware to M215F A12 Sept 2022 Stock Firmware now GSI boots again. Yes bootloader unlocked but its going to be a challenge to flash Grass Kernel now. Im gonna try though. Thanks for all your help friends.
#EDIT: Grass Kernel (June 2023 version) booted, the older version booted too. I am going to try Mint Kernel too
Click to expand...
Click to collapse
BobaBoi69 said:
Thats amazing good thing
Click to expand...
Click to collapse
Thanks Friend,
I feel the devs are working with M215F DT and not M215G trees because the latter came later, so I had to downgrade to M215F A12 to get some things working again. Correct me if i'm wrong though.
P.S.:- (Just Imagining) I think to make the andoid custom developement model smoother & hassle-free both for the Devs and the users, XDA & others could perhaps introduce a crowd-funding option for every device released in the market so that the devs can get hold of the devices sooner and start building custom stuff for the devices & then the users won't have to wait for 2 years to get the best possible ROMS for their devices
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi there, everybody! I am still using Marshmallow on my phone for various reasons. But the latest clean Lineage 13 that we have is with March 2017 security patches - so it is quite old now. I saw that there is a new MM ROM in XDA - the Lineage OS 13 with MicroG patch one. But when I saw what MicroG is, I really didn't even think about flashing this ROM - I am not privacy-concerned because all the Google services are useful to me, and I don't like using custom kernels on Lineage. The stock one works the best for me.
So for people like me - who like the clean Lineage and don't want to have any issues with Google Services, I built a Lineage 13 from Source with the latest security patches from Google.
Again, I am not telling you the ROM with MicroG patch is bad. It's actually a pretty great ROM. I'm just uploading this one, so that people like you have choices - either flash this clean one, or the one with the MicroG patch.
It has root built in. You can find it in the developer options. No need to flash the extra ZIP.
ChangeLog:
Version 20180319:
Updated Lineage sources (including new fixes, improvements, etc.)
Theoretically should work better
1 March 2018 security patch
Using Squid Kernel 22b by default
Version 20171115:
Initial booting Release
Contains KRACK fix and BlueBorne fix
Rooted by default
Installation:
Download the ROM from the downloads tab on the top of this thread
Download OpenGAPPS (or other ones which work with Lineage)
Wipe the Data, Cache and Dalvik (ART Cache)
Flash the ROM
Flash the GAPPS (optional)
Reboot and enjoy!
Important:
Each build of this ROM is made via the Windows 10 Subsytem for Linux. If anyone has problems with building Android on WSL, simply PM me and I'll be glad to help you.
XDA:DevDB Information
LineageOS 13 (2018), ROM for the Moto G 2015
Contributors
nicolasmart, squid2, CyanogenMod (formely Lineage)
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.x
Based On: Lineage OS
Version Information
Status: Stable
Current Stable Version: 2017-11-05
Stable Release Date: 2017-11-05
Created 2017-11-05
Last Updated 2018-03-19
Nice initiative.. Is VOLTE is added in this ?
rahul9999 said:
Nice initiative.. Is VOLTE is added in this ?
Click to expand...
Click to collapse
I don't personally use VoLTE since my carrier doesn't have it yet. It should be there but I can't really test it out, so I would wait for you to tell me.
nicolasmart said:
I don't personally use VoLTE since my carrier doesn't have it yet. It should be there but I can't really test it out, so I would wait for you to tell me.
Click to expand...
Click to collapse
I would like to test but not possible for me.. hope someone confirm this..
I have a problem here in instalation.
The rom does not start. It stays on the first screen and nothing happens.
the ROM has a problem and is that it does not start when we just installed it, I hope and fix it, great.
ive been using this room for a few days and had no problems, the security patch level says October 1st though.
ironzy said:
ive been using this room for a few days and had no problems, the security patch level says October 1st though.
Click to expand...
Click to collapse
Whaat? It works for you? I can't get my device to boot on my own ROM XD. What SKU are you using? I'm on XT1451
nicolasmart said:
Whaat? It works for you? I can't get my device to boot on my own ROM XD. What SKU are you using? I'm on XT1451
Click to expand...
Click to collapse
not sure what SKU means, I flashed the squid kernel after flashing the rom and it all works fine, the battery life is awesome.
ironzy said:
not sure what SKU means, I flashed the squid kernel after flashing the rom and it all works fine, the battery life is awesome.
Click to expand...
Click to collapse
He mean to say which variant you're on.. like I'm on XT 1550 2GB Ram.. If you dont know how to check this then just remove back cover of you're phone & see Model no. mentioned..
rahul9999 said:
He mean to say which variant you're on.. like I'm on XT 1550 2GB Ram.. If you dont know how to check this then just remove back cover of you're phone & see Model no. mentioned..
Click to expand...
Click to collapse
xt1541
Im using LineageOS 13 25/05/2017 build. Please, can you update the same for Moto G3-TE (merlin).
My SKU (XT1557) .
Thanks in advance:laugh:
ironzy said:
ive been using this room for a few days and had no problems, the security patch level says October 1st though.
Click to expand...
Click to collapse
wft, ami does not work for me, it stays in the moto logo and does not advance.
I have the xt1540
Erick_Summer said:
wft, ami does not work for me, it stays in the moto logo and does not advance.
I have the xt1540
Click to expand...
Click to collapse
try doing a full wipe then flashing the rom and then the squid kernel, that's the way I installed it and it works fine.
ironzy said:
try doing a full wipe then flashing the rom and then the squid kernel, that's the way I installed it and it works fine.
Click to expand...
Click to collapse
Ooooh!!! I know why it works for you!! You changed the kernel! My kernel is just bad!!! OK. Replacing it with stock Squid Kernel
Project Update
Old build deleted. The new one is coming up tomorrow.
nicolasmart said:
Old build deleted. The new one is coming up tomorrow.
Click to expand...
Click to collapse
you compiled it wrong this time, it gives error when installing it by recovery
Erick_Summer said:
you compiled it wrong this time, it gives error when installing it by recovery
Click to expand...
Click to collapse
the rom doesn't install on the latest twrp
Erick_Summer said:
you compiled it wrong this time, it gives error when installing it by recovery
Click to expand...
Click to collapse
ironzy said:
the rom doesn't install on the latest twrp
Click to expand...
Click to collapse
The ROM is installable with twrp-osprey-3.1.1-r1, the newer version adds support for newer android version. I guess it also means dropping support for older version of android. But again this ROM doesn't boot for me even after flashing was successful.
ajaysingh23 said:
The ROM is installable with twrp-osprey-3.1.1-r1, the newer version adds support for newer android version. I guess it also means dropping support for older version of android. But again this ROM doesn't boot for me even after flashing was successful.
Click to expand...
Click to collapse
support wasn't dropped for older versions of android, the rom just needs changing to work with the new twrp, the micro g version installs fine on the latest twrp.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FRANKEN
KERNEL
Franken is a rom and kernel project made from bits and pieces of all the great development on our Pixel3XL.
We strive to bring performance and features to your device while keeping the idea of google and upstream at the front of the
project!!!!Big Thanks to unicornblood[josh] and bluecross-dev for base!
Features
Upstream 4.9.136
adreno boost
sultans boost
Wirequard
Anykernel
Advanced TCP
simple lmk
much much more
Flash instructions
$$$Must be Unlocked$$$
Flash Kernel in TWRP
Flash Mag
Reboot
***WE Always try and push good stuff but by no means are we responsible for your device if you blow it up dont blaim us!
Downloads
[url]http://lab.dirtyrom.com/p3xl/[/URL]
Telegram
[url]https://t.me/frankenRom[/URL]
Donations
[url]https://paypal.me/Dabug123[/URL]
Thanks
Josh unicornblood-base
freak
DespairDev-base-script
Bluecross-dev-base
nathan-upstreaming all kernels
Anyone i forgot
XDA:DevDB Information
FrankenKernel, Kernel for the Google Pixel 3 XL
Contributors
dabug123
Source Code: [url]https://github.com/Dabug123/android_kernel_google_bluecross[/URL]
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 2
Beta Release Date: 2018-11-10
Created 2018-11-11
Last Updated 2018-11-10
reserve for me
First!
Also on that note. To flash this from a different kernel. What are the steps? Need to flash stock boot.img first?
@dabug123 thanks for this kernel. Great performance.
Sent from my crosshatch using XDA Labs
Hey @dabug123 - nice selfie in the OP !
c_86 said:
First!
Also on that note. To flash this from a different kettle. What are the steps? Need to flash stock boot.img first?
Click to expand...
Click to collapse
I flashed kernel and magisk
Sent from my crosshatch using XDA Labs
c_86 said:
First!
Also on that note. To flash this from a different kettle. What are the steps? Need to flash stock boot.img first?
Click to expand...
Click to collapse
Havent flashed another kernel so idk ,safe bet go stock boot.img first ,but u can test and tell us
dabug123 said:
Havent flashed another kernel so idk ,safe bet go stock boot.img first ,but u can test and tell us
Click to expand...
Click to collapse
Flashed over bluecross with Franco kernel flash no problems. No issues with root.
Thanks for the new kernel.
just did a flashall and did everything from scratch (twrp, etc) and loaded this kernel, so far so good.
Hopefully battery life will get a bit better with this over stock
Thank you!
i flashed it over html5 kernel. snappy and works well. make sure you flash magisk after.
No rebooting in between . all at once. just do it.
Will try once I'm behind the PC
Option to disable fsync? ?
Have to ask as others will. Twrp touch working with this kernel?
c_86 said:
Have to ask as others will. Twrp touch working with this kernel?
Click to expand...
Click to collapse
Twrp 3.2.3.1 has fixed the touchproblem itself
spencer92a said:
Twrp 3.2.3.1 has fixed the touchproblem itself
Click to expand...
Click to collapse
I thoght I had read that too - but last night I flashed 3.2.3.1 and lost touch responsiveness - it was really bad - coudn't get past the first screen - tried unlockng with my pattern and touch wasnt working so I was just stuck. I know this isn't the place to discuss TWRP - but with your comment I thouhgt I would mention it - did you flash the new twrp yet? is touch working for you?
Regarding this new Franken kernel - thank you! nice to have more diversity -
Geekser said:
I thoght I had read that too - but last night I flashed 3.2.3.1 and lost touch responsiveness - it was really bad - coudn't get past the first screen - tried unlockng with my pattern and touch wasnt working so I was just stuck. I know this isn't the place to discuss TWRP - but with your comment I thouhgt I would mention it - did you flash the new twrp yet? is touch working for you?
Regarding this new Franken kernel - thank you! nice to have more diversity -
Click to expand...
Click to collapse
The 3.2.3.1 recovery zip has working touch with my kernel on my device.
It should be the same for all kernels here!
Also @_LLJY found a way to finally build the touchscreen driver inline kudos to him for that! So don’t worry, things will consolidate and get easier with time.
Geekser said:
I thoght I had read that too - but last night I flashed 3.2.3.1 and lost touch responsiveness - it was really bad - coudn't get past the first screen - tried unlockng with my pattern and touch wasnt working so I was just stuck. I know this isn't the place to discuss TWRP - but with your comment I thouhgt I would mention it - did you flash the new twrp yet? is touch working for you?
Regarding this new Franken kernel - thank you! nice to have more diversity -
Click to expand...
Click to collapse
I've flashed the new TWRP, on stock Kernel, first i waited some time then touch worked perfect
Freak07 said:
The 3.2.3.1 recovery zip has working touch with my kernel on my device.
It should be the same for all kernels here!
Also @_LLJY found a way to finally build the touchscreen driver inline kudos to him for that! So don’t worry, things will consolidate and get easier with time.
Click to expand...
Click to collapse
Thanks - I figured out what I did wrong - (I am a dummy) I originally flashed the new TWRP while I was rooted. If I had read the TWRP OP more carefully, I would have seen I needed to be on STOCK Boot Image. So - I flashed stock boot image, booted into twrp - flashed twrp - flashed Franken and then flashed magisk 17.3. Profit!
I know better frankly, READING the OP is your friend - all is working now - and back on topic - The Franekn Kernel is AMAZING! I can tell just by how smooth everything is after flashing - I know Antutu is not much of a "story teller" - but just the same, I ran Antutu and got a score over 289,000[ higher than I have ever gotten before - by a significant margin.
View attachment 4639919
This is just for the 3 XL and not the regular Pixel 3, right?
Sevael said:
This is just for the 3 XL and not the regular Pixel 3, right?
Click to expand...
Click to collapse
Kernel source is unified. It should work on both. I don't think there is anything specific to the xl in this kernel.
Sent from my crosshatch using XDA Labs
UPDATE B3
CHANGELOG
-FIX TOUCH
-MERGE QCACLD
-POWER SAVING
-tcp:add sociopath
MUCH MORE
DOWNLOADS
http://lab.dirtyrom.com/p3xl/FrankenKernel.P3XL.B3.zip
How is this different to the 'Official' Build?
From October 17th onwards, the Official builds had merged N9 sources which has ridden users the chance of flashing custom kernels due to the new N9 dependency. These builds aim to backtrack that, reverting to S9(+)'s Oreo Vendor, to gain custom kernel support again. Also, the firmware source used in the 'Official' builds have become fairly antique, so it was time for a refresh and use the latest and final Oreo source (BSB1) Samsung had to give, and an upstreamed kernel of latest (almost always) ELS thanks to @Eamo5's Endurance Kernel being baked into the builds.
Aside from these factors and a few more listed below, this is the LineageOS you know and love. Although LineageOS' nightly-build system is great, there is only so much change that can happen over a night. You can expect these builds updating to cover latest Security Patch a.k.a Monthly Builds, but maybe more if a great change is required.
Simple motive: Have a solid daily driver before the Pie Tree sources are dropped.
Screenshots
If you are on the App they may instead be at the bottom of the post
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's working:
As this build is based on the 'Official' LineageOS build, it complies with the device support requirements, which means including but not limited to these hardwares will work:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Audio
USB
GPS
NFC
Camera
Fingerprint Sensor - Noticeable speed improvement reverting to an S9(+) Vendor.
Software:
The build has overridden auto-generated fingerprint keys, with an official, whitelisted fingerprint from Samsung, which can also be found in MagiskHideProps. This ensures SafetyNet passes without the need for extra flashing - refer to above screenshot also.
F2FS Support - Instructions to switch from default ext4 to f2fs
Miscellaneous - Overlays:
- Dialer - Call recording enabled. If your country is not blacklisted (for legality reasons) you should see a 'Record' button during your call.
- Trebuchet - Notification Badges
- Files - File Operation Dialog Box, Default Show Internal Storage
- Settings - Default Enable Autobrightness for Night Time flashers; Default Disable Bluetooth and LED
- SystemUI - Button to Expand Notifications; Notifications fade on dismiss
- Snap: api v2 enabled for better quality pictures and remove green artefacts & flashing.
What's not working:
Samsung's own features such as Samsung Pay, KNOX, Theme Center, Game Launcher, etc. won't be ported to LineageOS. They may have their own implementation to similar functions, though.
Iris sensor does not work because AOSP upstream does not support that yet.
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port.
Encryption Support as of now, exploring for a workaround (if there is one).
Bugs:
Lock screen shortcut - Camera: Screen flashes white, and then Camera force closes using shortcut.
Work around: Install another app using Camera action (e.g. SnapChat) and set stock Camera to default for shortcut.
Instructions:
Make sure TWRP has been installed and is functional.
Download the latest build, Vendor and optionally GApps - Links found under the header below.
Reboot to Recovery
Wipe data and cache (required if you are not currently using LOS and are coming from OneUI or SamExp.)
Install Vendor image to Vendor partition.
Flash the latest build (and GApps if you downloaded it)
If you are on and beyond April Patch (OneUI), do not flash a found Oreo Firmware as you will lose Baseband (Sim, Network, RIL). There is also no need to change firmware.
Reboot to System.
If a new build is released, to update:
Downloading and flashing a later build, will automatically replace (wipe & install) the /system partiton and retain your compatible User /data partition and firewall due to LineageOS' addon.d supprort.
You also do not need to flash GApps again, as they too have addon.d support, backing up which GApps you have installed and holding them until after the /system partition wipe has been done.
Same applies to Magisk Root due to (you guessed it) addon.d support too. It holds your currently installed Modules until after the /system partition wipe has been done.
Therefore, due to these addon.d files surviving because of the way LineageOS.zip manipulates the wipe to the /system partition there is no need to wipe partitions manually. Just leave it to the lone flash.
However, do remove any system modified theme overlays (substratum) to ensure no loop on boot, which may then result needing to wipe.
Downloads:
Vendor: Included to the respective Device drives below
Samsung Galaxy S9 (G960F): https://drive.google.com/drive/folders/131WWohHbpeZroYaHISBPpPnhDKYA6kj2
Samsung Galaxy S9+ (G965F): https://drive.google.com/drive/folders/1cr-ivOdTj8lo3p9kYjGcxT1AvgFYy3M9
OpenGApps (Optional): https://opengapps.org/
Contact:
Telegram Group - Handle @invisibazinga2 a.k.a Lil' G-Raf
Contributors:
Big thanks to: @jesec ; @Synt4x.93 ; @Ivan_Meler ; @Eamo5 ; please check GitHub commit history for anybody that I may have missed out, you have all been great!
ROM Information
LineageOS Source: https://github.com/LineageOS
Android Security Patch: May
Android Version: 8.1.0
Kernel Version: ELS - 4.9.xx - Endurance Kernel - Version subjected to change with ELS updates.
Device Source: https://github.com/AzzyC
Thanks for the rom! What would be the best way of installing gcam here? I've tried installing the apk on the official build but the quality wasn't too nice. Tried to flash the libs as well and got a bootloop. Thanks for your work!!
enetzlsg said:
Thanks for the rom! What would be the best way of installing gcam here? I've tried installing the apk on the official build but the quality wasn't too nice. Tried to flash the libs as well and got a bootloop. Thanks for your work!!
Click to expand...
Click to collapse
Hey man! Yeh on the official build as the vendor was N9 based, our modded S9(+) libs wouldn't be compatible. Fortunately, just before writing this reply, I flashed the lib for my device (S9) and then installed GCam and it got going nicely! There is a 4.1_fix.apk (fixed for OneUI lib) and just a regular 4.1.apk (built on Oreo lib).
Let me know how it goes man! And appreciate your compliments ?
the screenshots look like pie roms... clock is on left side ..i thought finally a good lineage 16 build.. yet thanks for the 15.1 build though.. ??
i came from soldier rom pie and after installing the rom according to the instruction.
full wipe, vendor image than rom and gapps and lastly the firmware.
everything boots and works but the phone doesnt detect my sim card nor the latest wifi network i was connected too. it does sees my neighbors wifi, for some reason it doesnt detect mine. i tried to change the baseband for fixing the sim card problem but no luck.
please help me/ im on s9 g960f
kmo1997 said:
i came from soldier rom pie and after installing the rom according to the instruction.
full wipe, vendor image than rom and gapps and lastly the firmware.
everything boots and works but the phone doesnt detect my sim card nor the latest wifi network i was connected too. it does sees my neighbors wifi, for some reason it doesnt detect mine. i tried to change the baseband for fixing the sim card problem but no luck.
please help me/ im on s9 g960f
Click to expand...
Click to collapse
It seems as though you were on and beyond the OneUI April Patch, which in the description of the Firmware zip it clearly indicates a warning to not flash the zip. I can't say anymore than these warnings unfortunately, after that it is up to the User.
A common fix that people do, to get back to normal state, is flash the latest DevBase with all of its complementary files. The April Patch had introduced a version change from U2 to U3 which makes downgrading impossible, without side effects. Please heed to warnings more in the future. Thanks
AzzyC said:
It seems as though you were on and beyond the OneUI April Patch, which in the description of the Firmware zip it clearly indicates a warning to not flash the zip. I can't say anymore than these warnings unfortunately, after that it is up to the User.
A common fix that people do, to get back to normal state, is flash the latest DevBase with all of its complementary files. The April Patch had introduced a version change from U2 to U3 which makes downgrading impossible, without side effects. Please heed to warnings more in the future. Thanks
Click to expand...
Click to collapse
thank you and sorry. i installed back to soldier rom with his firmware and everything works fine. but i really want to try your rom, so what firmware should i install with it?
kmo1997 said:
thank you and sorry. i installed back to soldier rom with his firmware and everything works fine. but i really want to try your rom, so what firmware should i install with it?
Click to expand...
Click to collapse
Glad you're back to normal state!
Users has been able to boot and use the ROM just by installing the provided Vendor image and remaining on the same firmware. Let me know how it goes and if I can recommend other users to do the same, if they are in a similar situation. Thanks
AzzyC said:
Glad you're back to normal state!
If I remember correctly a User has been able to boot and use the ROM just by installing the provided Vendor image and remaining on the same firmware. Let me know how it goes and if I can recommend other users to do the same, if they are in a similar situation. Thanks and hope it works out!
Click to expand...
Click to collapse
yep, works like magic. thank you very much!
AzzyC said:
Hey man! Yeh on the official build as the vendor was N9 based our modded S9(+) libs wouldn't be compatible. Fortunately, just before writing this reply, I flashed the lib for my device (S9) and then installed GCam and it got going nicely! There is a 4.1_fix.apk (fixed for OneUI lib) and just a regular 4.1.apk (built on Oreo lib).
Let me know how it goes man! And appreciate your compliments ?
Click to expand...
Click to collapse
one ui lib didn't work out for me
I always noticed that oreo roms were laggy. I heard somewhere that it was a HWC bug, NOT that HWC was disabled. So... my question... does this unofficial version of lineageos lags like the other oreo roms?
Muntasir Mahmud Saif said:
one ui lib didn't work out for me
Click to expand...
Click to collapse
You tried a OneUI vendor lib, on an Oreo Vendor? Read the post again.
LavaSnake54 said:
I always noticed that oreo roms were laggy. I heard somewhere that it was a HWC bug, NOT that HWC was disabled. So... my question... does this unofficial version of lineageos lags like the other oreo roms?
Click to expand...
Click to collapse
Can assure there is no lag here, but you can find out by trying of course aha! The kernel definitely smoothens out the whole experience and with decent battery (see sceenshot for example result) and HWC is active.
AzzyC said:
Can assure there is no lag here, but you can find out by trying of course aha! The kernel definitely smoothens out the whole experience and with decent battery (see sceenshot for example result) and HWC is active.
Click to expand...
Click to collapse
Looks like a solid daily driver for me. Will definitely try it soon.
AzzyC said:
You tried a OneUI vendor lib, on an Oreo Vendor? Read the post again.
Can assure there is no lag here, but you can find out by trying of course aha! The kernel definitely smoothens out the whole experience and with decent battery (see sceenshot for example result) and HWC is active.
Click to expand...
Click to collapse
one ui lib bro..i am using that lib on my one ui currently for quite a few months..
Muntasir Mahmud Saif said:
one ui lib bro..i am using that lib on my one ui currently for quite a few months..
Click to expand...
Click to collapse
I don't see what is not to grasp here, you are flashing a Pie vendor lib on an Oreo Vendor. How would that work out? Didn't think I'd have to spell it out, but you've spammed this issue across 3 posts now:
Use the Oreo modded lib (not the Pie/OneUI lib), as this ROM is based on an Oreo Vendor, and the 4.1.apk (not the 4.1_fix.apk).
Hey guys!
I was doing a test run for a particular change and I thought I'd do a quick update for both devices. Starlte built just fine but I ran out of disk space when finishing star2lte so the compile failed (at 91% ?)
Not to fret, the May Security Patch has not yet been merged into LineageOS so this would have been just another build on April Patch. However, the included kernel has updated to latest of Endurance, though you can just flash Eamon's latest kernel zip to update and have the same effect.
Both devices will of course get an update when May Patch is out. Gracias bien
For starlte:
https://drive.google.com/drive/mobile/folders/131WWohHbpeZroYaHISBPpPnhDKYA6kj2
Gcam link please?
AzzyC said:
I don't see what is not to grasp here, you are flashing a Pie vendor lib on an Oreo Vendor. How would that work out? Didn't think I'd have to spell it out, but you've spammed this issue across 3 posts now:
Use the Oreo modded lib (not the Pie/OneUI lib), as this ROM is based on an Oreo Vendor, and the 4.1.apk (not the 4.1_fix.apk).
Click to expand...
Click to collapse
sorry if i did wrong or hurt your feelings but can you please provide those two files?
LavaSnake54 said:
Gcam link?
Click to expand...
Click to collapse
Muntasir Mahmud Saif said:
can you please provide those two files?
Click to expand...
Click to collapse
https://f.celsoazevedo.com/file/gcamera/GCam_5.1.018.177470874.41362666_IDan_N6_4.1.apk
AzzyC said:
https://f.celsoazevedo.com/file/gcamera/GCam_5.1.018.177470874.41362666_IDan_N6_4.1.apk
Click to expand...
Click to collapse
you are dope bro .thanks
Hello, I am trying to build and run a custom kernel on S21 Ultra Exynos (SM-G998B). Reason: support permissive SELinux policy.
I am running AUF6 firmware, downloaded AUF6 kernel source from Samsung, followed the included build instructions and with unmodified sources, ran included `build_kernel.sh `, and created a boot.img using AIK, and flashed the resulting .img file via TWRP.
Rebooting into system, the phone is stuck on displaying the boot logo. Reading /proc/last_kmsg through TWRP, logging stops right after 'Starting kernel...' message. At this point I am not sure what else I can do to resolve this. Please help.
P.S. my compiled Image size is 26M, while stock is 28M.
The tutorial I followed: https://pucarasec.wordpress.com/2020/06/16/debugging-the-samsung-android-kernel-part-2/
Another post with trying to build S21 kernel, with outcome, similar to mine: https://groups.google.com/g/android-platform/c/ljRkDbBE0lE/m/mr4MM0WGCAAJ
mzakharocsc said:
Hello, I am trying to build and run a custom kernel on S21 Ultra Exynos (SM-G998B). Reason: support permissive SELinux policy.
I am running AUF6 firmware, downloaded AUF6 kernel source from Samsung, followed the included build instructions and with unmodified sources, ran included `build_kernel.sh `, and created a boot.img using AIK, and flashed the resulting .img file via TWRP.
Rebooting into system, the phone is stuck on displaying the boot logo. Reading /proc/last_kmsg through TWRP, logging stops right after 'Starting kernel...' message. At this point I am not sure what else I can do to resolve this. Please help.
P.S. my compiled Image size is 26M, while stock is 28M.
The tutorial I followed: https://pucarasec.wordpress.com/2020/06/16/debugging-the-samsung-android-kernel-part-2/
Another post with trying to build S21 kernel, with outcome, similar to mine: https://groups.google.com/g/android-platform/c/ljRkDbBE0lE/m/mr4MM0WGCAAJ
Click to expand...
Click to collapse
I'm sure you know this already, but there's a magisk module that does that already.
If I was to build a kernel I would try and definitely build something that has smoother performance or slightly better battery life.
Keep up the efforts. It is a shame there are no custom kernels for the phone...
Burt Squirtz said:
I'm sure you know this already, but there's a magisk module that does that already.
Click to expand...
Click to collapse
If you are talking about this: https://github.com/evdenis/selinux_permissive , then having tried it it did not work. On their own XDA thread, they state 'The module will not work if your kernel compiled with always enforcing config, e.g., stock samsung kernels. It's not possible to enable permissive mode on such kernels'. Unless I am missing something here?
Ok. I managed to install a custom kernel. There is already one in development here: https://github.com/mohammad92/android_kernel_samsung_exynos2100
Here are the steps I took.
1. Downgraded firmware to 3AUDA.
2. I ran 'build_menu' script from the repository, and selected p3s target. Here, I ran into build errors, so I commented out 'export LLVM=1' from 'build_menu' script, and this produced a kernel image. While that matched original instructions from samsung kernel release, the result did not boot (same hang as before), so I put LLVM=1 back, and resolved build issues by installing clang on my host system. It seems like LLVM=1 is the trick here, as I now have a working custom kernel, and it is 'permissive'. Perfect. Attached is the zip file to be installed with TWRP.
mzakharocsc said:
Ok. I managed to install a custom kernel. There is already one in development here: https://github.com/mohammad92/android_kernel_samsung_exynos2100
Here are the steps I took.
1. Downgraded firmware to 3AUDA.
2. I ran 'build_menu' script from the repository, and selected p3s target. Here, I ran into build errors, so I commented out 'export LLVM=1' from 'build_menu' script, and this produced a kernel image. While that matched original instructions from samsung kernel release, the result did not boot (same hang as before), so I put LLVM=1 back, and resolved build issues by installing clang on my host system. It seems like LLVM=1 is the trick here, as I now have a working custom kernel, and it is 'permissive'. Perfect. Attached is the zip file to be installed with TWRP.
Click to expand...
Click to collapse
commenting that line will brake your image, we need llvm to make bootable kernel.
afaneh92 said:
commenting that line will brake your image, we need llvm to make bootable kernel.
Click to expand...
Click to collapse
Makes sense, however, this 'export LLVM=1' line is not present in the samsung's official build instructions that come with the kernel zip. Nor have I found any mention of this flag on any of the kernel building tutorials online and on this forum. Maybe I missed something, but this looks non-obvious for someone new to this.
mzakharocsc said:
Makes sense, however, this 'export LLVM=1' line is not present in the samsung's official build instructions that come with the kernel zip. Nor have I found any mention of this flag on any of the kernel building tutorials online and on this forum. Maybe I missed something, but this looks non-obvious for someone new to this.
Click to expand...
Click to collapse
By reading Makefile you can find it there.
afaneh92 said:
By reading Makefile you can find it there.
Click to expand...
Click to collapse
Yeah, I read the makefile. LLVM flag is supported there, but unset/unused by default, resulting in corrupt images. and you have to somehow know that you need to set it externally.
If someone build a good custom kernel wich improves battery and performance i will donate 100 usd
I want custom kernels too.
Would it be possible to make a bounty?
I'm interested in battery, hackability, booting time, stability and performance.
songoku1 said:
If someone build a good custom kernel wich improves battery and performance i will donate 100 usd
Click to expand...
Click to collapse
Are there some official XDA bounty program for this stuff?
timofonic said:
Are there some official XDA bounty program for this stuff?
Click to expand...
Click to collapse
Sadly no on my oneplus i use arter kernel and i absolutely lovibg it. Sadly for my s21u there isnt one :/
What's more important now is to stress samsung's opensource service to release the AUG4 kernel source
DaReDeViL said:
What's more important now is to stress samsung's opensource service to release the AUG4 kernel source
Click to expand...
Click to collapse
Already requested it.
interested in a custom kernel also, it's already a very good device but battery life needs to be better
afaneh92 said:
Already requested it.
Click to expand...
Click to collapse
Got it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DaReDeViL said:
Got it
View attachment 5368845
Click to expand...
Click to collapse
I will rebase my kernel soon
Ok
DaReDeViL said:
Got it
View attachment 5368845
Click to expand...
Click to collapse
Hope we will see a custom kernel soon
Any news?
It's simple. I threw together this kernel out of necessity for micro lag fixes and better battery life.
Please expect only necessary updates.
If you have an issue, please provide a detailed report and please provide a logcat
Enjoy.
V-1.0.9 Zip download link = https://www.androidfilehost.com/?fid=4279422670115732041
V-1.0.9 Boot Image download link = https://www.androidfilehost.com/?fid=4279422670115732040
##################################
OP9R BUILD/ZIP only
OP9R-V-1.0.9-ZIP = https://androidfilehost.com/?fid=4279422670115732053
the boot.img is not pre-rooted. Please use the zip to remain rooted.
Kernel Source = https://github.com/APOPHIS9283/Singularity_Kernel
apophis9283 said:
It's simple. I threw together this kernel out of necessity for micro lag fixes and better battery life.
If you use Evolution-X this will break Fsync toggle as I opted for Dynamic Fsync instead. Past that you tell me.
Please do not expect a ton of updates.
If you have an issue, logcat or GTFO.
There is no Telegram link.
Enjoy.
Zip download link = https://www.androidfilehost.com/?fid=4279422670115706910
Boot Image download link = Coming soon.
Kernel Source = https://github.com/APOPHIS9283/Krieg_Kernel/commits/13
Click to expand...
Click to collapse
Been using this for a while and very happy with performance..
Works smooth like a criminal
Thanks for release.
Running on OOS 13.
I missed custom I/O schedules & TCP algorithms.
Great to see that you had set Zram compression to zstd algorithm.
Cannot wait to see your next release !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ty dev for the kernel. Kernel is fine overall but scrolling performance could be a bit better.
Which device is your evo_defconfig for ?
I'm new to kernel building, just wondering .
hightech316 said:
Which device is your evo_defconfig for ?
I'm new to kernel building, just wondering .
Click to expand...
Click to collapse
This was actually an idea I had using EvoX for OP8T.
efx7n said:
View attachment 5798177Ty dev for the kernel. Kernel is fine overall but scrolling performance could be a bit better.
Click to expand...
Click to collapse
Thats probably because I use 300HZ timer interrupt frequency which I have no issue bumping to 1000HZ which Ill drop tomorrow for you all, along with a few minor changes.
I have updated the kernel. Addressing issue brought forth in the comments.
My camera doesn't seem to work . Everything else is doing great!
OOS Cam and Open Cam .
Running latest OOS13 stock .
Attached log.
hightech316 said:
My camera doesn't seem to work . Everything else is doing great!
OOS Cam and Open Cam .
Running latest OOS13 stock .
Attached log.
Click to expand...
Click to collapse
I missed that you were running stock. I probably should've mentioned that. This was only meant for custom ROMs. I am truly sorry I overlooked saying that.
Can u please try to add support for 9r. Coz both 8t and 9r are the same. Just some minor changes ig.
apophis9283 said:
I missed that you were running stock. I probably should've mentioned that. This was only meant for custom ROMs. I am truly sorry I overlooked saying that.
Click to expand...
Click to collapse
No worries .
OnePlus released their OOS13 kernel .
GitHub - OnePlusOSS/android_kernel_oneplus_sm8250 at oneplus/sm8250_t_13.0.0_op8
Contribute to OnePlusOSS/android_kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
How big of a pain would it be to take the blobs ( if that is even what is needed ? ) From that release onto yours ?
Or are they completely different and non compatible since one being AOSP and other OOS?
projektx said:
Can u please try to add support for 9r. Coz both 8t and 9r are the same. Just some minor changes ig.
Click to expand...
Click to collapse
This was based off EvoX's kernel. If they use it for the 9r as well it should work, but if it doesn't. Sure when I get time, I'll peek at it. The zip probably would fail but the boot.img would be fine. Just have a backup to flash if it fails.
Always nice when you pop in and bless us with some butter. Running great and thanks for your work as always
Does it work on OnePlus 8 Verizon (IN2019)? I am on Kaleidoscope Rom (Android 12).
Zombify01 said:
Does it work on OnePlus 8 Verizon (IN2019)? I am on Kaleidoscope Rom (Android 12).
Click to expand...
Click to collapse
Yes, I ran it on the IN2017 T-Mobile OnePlus 8 and it worked.
Unfortunately, I got rid of it because, as mentioned in the thread, FSync was replaced with Dynamic FSync. This prevents you from losing data if the screen is off, but not when it's on.
hammerhaigh said:
Yes, I ran it on the IN2017 T-Mobile OnePlus 8 and it worked.
Unfortunately, I got rid of it because, as mentioned in the thread, FSync was replaced with Dynamic FSync. This prevents you from losing data if the screen is off, but not when it's on.
Click to expand...
Click to collapse
EDIT: use the boot.img and not the zip, the zip enables dynamic fsync
Fsync is enabled always, it only syncs while screen off if you enable it. Dont touch dynamic fsync and it remains as fsync on as always.
Im also testing a twrp build I made for oos13 firmware a13, all partitions should mount. EROFS. I dont keep up with everyones work, I dont think theres a recovery yet that has that possibility but I could be wrong.
Must be on op8t f15 firmware with a rom that uses erofs. You should be able to mount all partitions. If you want to test, you can get with me on telegram. I am only using TG due to the nature of this.
Testing twrp
t.me
Also heres v-1.2 of the kernel boot.img only not pre-patched
apophis9283 said:
Must be on op8t f15 firmware with a rom that uses erofs. You should be able to mount all partitions. If you want to test, you can get with me on telegram. I am only using TG due to the nature of this.
Testing twrp
t.me
Also heres v-1.2 of the kernel boot.img only not pre-patched
Click to expand...
Click to collapse
Only OOS atm? Pretty sure the evoX filesystem isn't erofs.