yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
I was able to compile using the following roomservice:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Repository44/android_kernel_samsung_universal9810" path="kernel/samsung/exynos9810" remote="github" revision="lineage-19.1" />
<project name="Repository44/android_device_samsung_exynos9810-common" path="device/samsung/exynos9810-common" remote="github" revision="lineage-19.1_rollback" />
<project name="Repository44/android_device_samsung_starlte" path="device/samsung/starlte" remote="github" revision="lineage-19.1_rollback" />
<project name="Repository44/android_device_samsung_star2lte" path="device/samsung/star2lte" remote="github" revision="lineage-19.1_rollback" />
<project name="Repository44/proprietary_vendor_samsung_exynos9810-common" path="vendor/samsung/exynos9810-common" remote="github" revision="lineage-19.1_rollback" />
<project name="Repository44/proprietary_vendor_samsung_starlte" path="vendor/samsung/starlte" remote="github" revision="lineage-19.1_rollback" />
<project name="Repository44/proprietary_vendor_samsung_star2lte" path="vendor/samsung/star2lte" remote="github" revision="lineage-19.1_rollback" />
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-19.1" />
<project name="LineageOS/android_device_samsung_slsi_sepolicy" path="device/samsung_slsi/sepolicy" remote="github" revision="lineage-19.1" />
</manifest>

I made "Repository44" specifically for my LOS 19.1 repos. I'll be updating the kernel as the Linux Long Term Maitenance team continues rolling out patches. I'll also be updating the AOSP security patches monthly as they roll out.

While I'll be keeping these repos up to date as best I can for anyone to use, I won't be publishing the compiled ROM for everyone, though as I cannot compile for more than one device; I use the S9.

If you have additional questions about errors compiling LOS 19.1, please let me know and I'll try my best to help.
[Samsung Galaxy S9 & S9+ Cross Device Development] l4jos:
Ok, understand. Maybe I try soon by myself. Building on VM caused problems with the breakfast command last time, that has something to do with memory. Can I ask you a few questions? Do you build on Ubuntu and would you like to share the build requirements (e.g. from apt)? Or by pm. Thanks in advance
[Samsung Galaxy S9 & S9+ Cross Device Development] gnarf49:
Hi Neurotical,

are you building with signature spoofing enabled for MicroG?

Hi all, is there any experience already with dirty flashing over an existing 18.1?

Thanks,

Georg
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Unfortunately I cannot get the spoofing patch integrated with 19.1, despite there being such files available by the developer. The process for patching doesn't appear to be the same as for 18.1.
[Samsung Galaxy S9 & S9+ Cross Device Development] slivercp:
Hi Neurotical

Thanks for working on trying to get 19.1 up and running on S9/S9+. I would like to see it working as well.

As a few things are not ready yet with the 19.1 build (like builds for S9+ etc.), would you be willing to do another release of the 18.1 build with the AOSP security patches of August included? That would be awesome but also understand if you do not find the time.

Thanks for your work in any case.
[Samsung Galaxy S9 & S9+ Cross Device Development] :
Hi @Neurotical,

first of all thank you very much for your work. Your ROM is still running fine.

Since there has been no news here for a while, I would like to ask if the ROM is still being maintained? Is there any news about your work on LOS 19.1?

Thanks and best regards,

sinnl0s.
[Samsung Galaxy S9 & S9+ Cross Device Development] divxguru:
Hi

i tried to download the latest version 2022-07-30 from the link https://github.com/Geoknyda/OTA/releases/tag/Weekly within the first post but the folder seems to be empty (no image file, only source code from Jun 24, 2021).

Also the direct link to the img file from the starlte.json

https://github.com/Geoknyda/OTA/releases/download/Weekly/lineage-18.1-20220730-UNOFFICIAL-starlte-kernel-4.9.325_wg_20220627_SPOOFING.zip

is not available anymore (Not Found).

@Neurotical could you please doublecheck?

Many thanks for your great work!
[Samsung Galaxy S9 & S9+ Cross Device Development] Speedmatze:
The files were still available on Sunday. I am guessing they were deleted due to inactivity.

I have compiled a 18.1 ROM last night from @Neurotical Sources. I will test it during the next days on my device. If everything works well I might provide a link if someone is interested.
[Samsung Galaxy S9 & S9+ Cross Device Development] NHJ1981:
Does anyone have the last build (lineage-18.1-20220730-UNOFFICIAL-starlte-kernel-4.9.325_wg_20220627_SPOOFING.zip) available and willing to upload it somewhere juste in case the phone needs to be restored?
[Samsung Galaxy S9 & S9+ Cross Device Development] ELF-21:
here it is: https://www.dropbox.com/s/v9hp5g7v5...-kernel-4.9.325_wg_20220627_SPOOFING.zip?dl=0

I hope it's what you're looking for
[Samsung Galaxy S9 & S9+ Cross Device Development] :
It appears that the original user has removed the builds from their GitHub. There are various forks I have found that are continuing

Neuroticals great work.​

For Galaxy s9 ( starlte ) use this link for the latest builds ( inc security updates from LOS ) kernel 325

Releases · pakaoraki/OTA

Contribute to pakaoraki/OTA development by creating an account on GitHub.

github.com

For Galaxy s9+ ( star2lte ) use this link for the latest builds ( inc security updates from LOS ) kernel 300

Releases · WalterEight/OTA

Contribute to WalterEight/OTA development by creating an account on GitHub.

github.com

otherwise Neurotical still has the local_manifest to build your own each month as LOS makes security updates available

local_manifests/roomservice.xml at lineage-18.1 · Geoknyda/local_manifests

Contribute to Geoknyda/local_manifests development by creating an account on GitHub.

github.com

The battery IS replaceable ( with the help of a hair dryer ), so this phones useable life extends even further if you can handle not having the latest camera tech.

Merry Xmas
[Samsung Galaxy S9 & S9+ Cross Device Development] citizenserious:
I found this:

https://t.me/ExyBrick

https://t.me/Godlike9810

[Lineage-20.0] [20/11/2022] [OTA]

initial release:

- userdata uses f2fs file based encryption ()

- kernel upstreamed to 4.9.332

- backported fscrypt v2 from android-4.14-stable

- backported f2fs updates from android-4.14-stable

- backported inline encryption support form android-4.14-stable

instructions:

- flash Lineage Recovery

- boot into recovery and sideload rom.zip, and gapps/magisk if you want

- format /data

- reboot

etc:

- data wipe mandatory due to inline encryption support

- TWRP not supported!

- If you have issues with TWRP don't report it here, lineage recovery is included with each build and the only method of installation I'll support

- tested with MindTheGapps 13.0.0-arm64-20221025

main contributors:

- synt4x93

- krazey

- josip

crownlte:

https://images.krazey.de/images/lineage-20.0-20221120-unofficial-crownlte.zip

https://images.krazey.de/images/lineage-20.0-20221120-recovery-crownlte.img

star2lte:

https://images.krazey.de/images/lineage-20.0-20221120-unofficial-star2lte.zip

https://images.krazey.de/images/lineage-20.0-20221120-recovery-star2lte.img

starlte:

https://images.krazey.de/images/lineage-20.0-20221120-unofficial-starlte.zip

https://images.krazey.de/images/lineage-20.0-20221120-recovery-starlte.img

source:

https://github.com/ExyHyperBrick
[Samsung Galaxy S9 & S9+ Cross Device Development] slivercp:
Thanks a lot for sharing this. This is great. Do you know whether I can simply flash those images over @Neurotical ROM images I already have installed and keep the data? Or do I need to clear the data first for it to work?
[Samsung Galaxy S9 & S9+ Cross Device Development] itspuk:
I still use the July 30 version for starlte from neurotical. How would I go about updating it to the one from pakaoraki? Can this be done ota or do I have to flash via twrp? Cheers
[Samsung Galaxy S9 & S9+ Cross Device Development] Speedmatze:
OTA will not work. You need to flash via Lineage Recovery (or TWRP).

Dirty installation (without wiping data) might work. However, there might be glitches. So there is no garantee that everything will work flawlessly...
[Samsung Galaxy S9 & S9+ Cross Device Development] itspuk:
So I'm a (lucky) idiot. I dirty flashed los 19.1 over 18.1. phone got stuck in twrp splash, phone not getting recognized by my pc. I eventually managed to get into download mode, flashed new twrp version via Odin and could then restore my twrp backup. I thought that was it...

I would like to upgrade to 19.1 bc support for Android 11 starts fading already, but I don't feel like going through the hassle of trying to get my banking app to run again etc :(
[Samsung Galaxy S9 & S9+ Cross Device Development] Speedmatze:
Yeah, things like that can happen when you are changing versions.

TWRP might have been a cause here.

You could try:

- Backup with TWRP

- Flash Lineage recovery

- Flash LOS 19.1 in Lineage recovery

Might work, might not...

If that fails restore TWRP with Odin and then restore backup.

I'm in the same boat. I'm also still on 18.1 with microG, banking apps, Android Auto incl. Screen2Auto, Exchange accounts etc. working. Took me long enough.

I don't want to upgrade and go through the hassle of setting all that up again. I will probably wait for LOS 20 and try to skip 19.1.
[Samsung Galaxy S9 & S9+ Cross Device Development] NHJ1981:
Did you install mindthegapps for android 12 after dirty flashing the 19.1 rom?
[Samsung Galaxy S9 & S9+ Cross Device Development] itspuk:
I only flashed the ROM and nothing else. I'm not even sure which gapps I have installed rn. Maybe nikgapps? I don't know whether this can explain it? So another thing I forgot :D anyways, may only problem I have with the ROM is that I can't Chromecast YouTube (vanced) anymore. Everything else works fine. Although now that nothing severe happened I'm tempted to try again. Can always go back...
[Samsung Galaxy S9 & S9+ Cross Device Development] NHJ1981:
That's the latest Gapps recommended package for lineageos19.1 : https://androidfilehost.com/?fid=15664248565197177719

I'm tempted to also do a dirty flash a bit later in the month, from previous experience as instructed by rom maintainers on different phones, i'd do these things :

1.Install Latest TWRP

2. Go to /data/system folder and delete : locksettings.db (lockscreen pin/pattern/code)

3. Wipe dalvik/cache

4. Flash Lineageos 19.1

5. Flash the latest recommended mindthegapps for android 12 (it should take care of obsolete/incompatible gapps by removing them)

If the phone proceeds to boot normally, i'd then flash magisk
[Samsung Galaxy S9 & S9+ Cross Device Development] q76:
The kernel this device uses just received its last point release and is now EOL:

Linux 4.9.337 Released To End Out The 2016 LTS Series - Phoronix

www.phoronix.com

Also it looks like LineageOS 20 is already a thing:

Changelog 27 - Thriving Thirteen, Amazing Aperture, Careful Commonization

X_X

lineageos.org
[Samsung Galaxy S9 & S9+ Cross Device Development] m0m0331:
It looks like since April of this year, LOS 20 is a thing for the S9 Exynos:

[OFFICIAL] LineageOS 20 for the Galaxy S9/S9+ Exynos

LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...

xdaforums.com

If not permitted, pls remove.
[Samsung Galaxy S9 & S9+ Cross Device Development] Seorzan:
nfc not working in los20, is it working in los18/19?
[Samsung Galaxy S9 & S9+ Cross Device Development] Gogi_M:
Hello friends.

I need exactly the last 'Geoknyda' build from @Neurotical: (see msg above)

lineage-18.1-20220730-UNOFFICIAL-starlte-kernel-4.9.325_wg_20220627_SPOOFING.zip

which originally was on his Github (here).

The link from ELF-21 (see msg above) does not work either.

Could someone share it with us one more time please?
[Samsung Galaxy S9 & S9+ Cross Device Development] Gogi_M:
Hello @itspuk. Still you have this 'July 30 version for starlte from neurotical' ?

May be you could share it with me?
[Samsung Galaxy S9 & S9+ Cross Device Development] itspuk:
Sorry, I think I've done all the updates OTA. What I still have a zip file of is:

lineage-18.1-20220129-UNOFFICIAL-starlte-kernel-4.9.299_wg_20211208_SPOOFING.zip

Lemme know if this could be useful.

By the way, @Speedmatze are you still on 18.1 or did you find a satisfying solution? Cheers
[Samsung Galaxy S9 & S9+ Cross Device Development] Khalil777:
That would be awesome if you could get OTA working

Also i think i had issues because my initial installation was done through twrp, going forward i will be using heimdall and adb sideload and hopefully the dirty flashing will work.

Thanks a lot for all your help.

Currently waiting for my phone to fully charge so that i can setup encryption. Seeing that TWRP cannot access my device after encryption, how would you suggest i do a full backup? i assume via adb backup probably, is there a better method?

I'm actually a comp sci student and i'm trying to learn as much as i can, maybe even someday i will be contributing on here, i'm very much interested but i'm still a noob haha
[Samsung Galaxy S9 & S9+ Cross Device Development] francoism90:
Does anyone know how to make the smart cover to work? :)

It seems FlipFlap should provide this, but I cannot seem to find it?
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
If I want to keep TWRP as recovery and do an update of ROM and kernel, how do I do so?

Is a dirty flash of the ROM enough?

Or do I have to flash the kernel.img in recovery for the boot partition as well?
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
I'd try this one, I'm pretty happy with it:

https://xdaforums.com/t/gcam-exynos-version-from-bsg.4246095/
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Khalil777 in this thread tried that, but realized it cannot be done. It is required to install the Lineage recovery with the ROM and do a factory reset for the first install. Afterwards, all that is required to update to new weekly ROMs is to install the new weekly recovery via OTA and/or dirty flash the new weekly ROM and all data will then be retained.
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
Thanks. So I have to do that or I can just dirty flash the new ROM build from you but will keep the old kernel since I'm already on your build?
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
If you're already on my build and recovery all you have to do to upgrade weekly is:

Run OTA

or

Flash the recovery using heimdall in download mode

Sideload ROM using adb in recovery

Wipe cache

Reboot

No complete format necessary :)
[Samsung Galaxy S9 & S9+ Cross Device Development] waynea:
Hiya

got another question!! with this ROm do i still have to flash the dm-verity removal patch? or is this now included in the ROM?
[Samsung Galaxy S9 & S9+ Cross Device Development] Khalil777:
You could keep TWRP and just flash the recovery.img via Heimdall but then you'll need to reinstall TWRP and then install the ROM via TWRP which is more work, it's easier to just sideload the ROM via adb sideload command.

Also, updating the kernel has tremendously increased my battery life! I'm currently on kernel 275, this is exponentially better than what I was getting from the previous kernel versions.
[Samsung Galaxy S9 & S9+ Cross Device Development] francoism90:
I didn't, just followed the (old) LineageOS S9 guide. I'm not using TWRP, just the provided LOS recovery.
[Samsung Galaxy S9 & S9+ Cross Device Development] waynea:
Hiya

need some help please with my S9 starlte

I flashed TWRP with Odin, apparently successfully and I can boot into recovery easily.

Booting to download mode shows FRP and OEM locks are OFF, Secure boot = enabled

However if I then try to flash the Lineage ROM it throws the error

Failed to map file 'external_sd/lineage-18.1 (etc)

Error installing zip file 'external_sd/lineage-18.1 (etc)

plus..

failed to mount 'cpefs (RO file system) but I dont know whether this is significant

This looked like a TWRP error, but I have tried it with every version I can find for the S9 .

The stock meanwhile is stick in a bootloop (and it still shows 'secured by knox'

Any ideas to fix? in theory I could reflash stock through Odin, but I sort of think the same issue will recur....(Ill actually post this on the TWRP thread as well..)
[Samsung Galaxy S9 & S9+ Cross Device Development] aureljared:
Try using the Lineage Recovery instead of TWRP, you can download it from the same page as the ROM.

In my experience I couldn't flash GApps in TWRP, something about /system not being mounted in the right path. Lineage Recovery worked right away.
[Samsung Galaxy S9 & S9+ Cross Device Development] waynea:
hiya and thanks for quick reply. I think im stuck with TWRP though, there are only unofficial versions of the S9 ROM as Lineage discontinued full support - and so there is no Lineage Recovery that I can see either...
[Samsung Galaxy S9 & S9+ Cross Device Development] aureljared:
@Neurotical uploads recoveries along with the ROMs here: https://github.com/Geoknyda/OTA/releases/tag/Weekly

Just get the one for your device :)
[Samsung Galaxy S9 & S9+ Cross Device Development] waynea:
Oooh.....missed that! Many thanks I'll try that next..another day though
[Samsung Galaxy S9 & S9+ Cross Device Development] waynea:
OK tried it now. Flashed lineage recovery with odin and it flashed OK and can boot into it.

But when I try yo flash the lineage ROM it fails after asking me to bypass signature verification.

Screen goes black and shuts down. Restarting takes me back to the Samsung stock boot loop
[Samsung Galaxy S9 & S9+ Cross Device Development] aureljared:
Strange. Did you enable OEM unlocking and format /data before flashing Lineage? That's what I did to successfully flash mine.
[Samsung Galaxy S9 & S9+ Cross Device Development] waynea:
Yes I did...this is the first real disaster I've had in flashing lineage
[Samsung Galaxy S9 & S9+ Cross Device Development] cybermiguel:
Does it have Dolby Atmos? Full camera experience? Can those be downloaded?

Thanks in advance. =)
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
It comes with Lineage's AudioFX sound tuner. I did not see Dolby Atmos available in Aurora store for download.

The stock camera is functional with HDR and other features. OpenCamera has a better selection of features to choose from, so it would be a good idea to download that from Aurora store.
[Samsung Galaxy S9 & S9+ Cross Device Development] gusnz:
Hi @Neurotical, thanks for porting some recent kernel patches! I tried to build your 4.9.275 kernel with Wireguard added but got an error:

net/wireguard/socket.c:139:40: error: called object type '<dependent type>' is not a function or function pointer

dst = ipv6_stub->ipv6_dst_lookup_flow(sock_net(sock), sock, &fl,

Vanilla synt4x93's kernel built with Wireguard was OK last month. Without the Wireguard patches your kernel's building normally, although I did have to export TEMPORARY_DISABLE_PATH_RESTRICTIONS=true prior to the WG build as it didn't like some of the common 9810 file setup process.

Thanks if you can see if you can build Wireguard? According to their build status page it's 4.9.275 compatible.
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Thanks for the feedback. I checked the kernel configuration and it appeared to be missing: IP: Foo (IP protocols) over UDP (NET_FOU) as per https://www.wireguard.com/compilation/

So I updated the kernel to enable this required feature: IP: Foo (IP protocols) over UDP (NET_FOU) [ ]->[*] and compiled a new ROM for you to try; it's uploaded to my support repo. To do this I made two small commits (one for starlte and one for star2lte) on the 4.9y_beta branch of the kernel in my repo.

I was able to install Wireguard from F-Droid and browse the app. However, I don't have a subscription to a VPN that supports Wireguard so I couldn't try configuring a server. Please let me know your experience :)
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
FYI:

OTA feature enabled in today's build

To receive future updates via OTA, please install 20210718 build.

Have a great day!
[Samsung Galaxy S9 & S9+ Cross Device Development] ElPakoTech:
Hi,

It’s really nice to see people continuing to work on maintaining kernel for Samsung S9/S9+, thanks a lot.

Is it OTA working for you now ? I started doing my own build few weeks ago and I had no issues with it (https://github.com/pakaoraki/OTA).

I’m curious about the fact that the original developer stop working on the "Lineage-18" branch on January and start to work on "4.9.118" instead: do you have any idea why ? Or if they had some issues with the 4.9.218 at that time ?

I did also some research of all forks and I found some patches :

-“Updated exynos fbdev driver “:

https://github.com/Ralayax/android_kernel_samsung_universal9810/commits/lineage-18.1

-Here some patch for "wireguard-linux-compat":

https://github.com/lolorc/android_kernel_samsung_universal9810-1/commits/lineage-18.1

https://github.com/lolorc/android_kernel_samsung_universal9810-1/commits/lineage-18.1-test

I didn’t test any, but I just wanted to share this with you, if it can help improving kernel.
[Samsung Galaxy S9 & S9+ Cross Device Development] waynea:
Update on boot loop.

I managed to flash twrp 3.4.0.0 and then an earlier version of the ROM.

I had earlier cleared cache and dalvik, and repaired the system file system.

This time it flashed OK! At least TWRP did not throw any errors

But still the boot loop persists. Any other suggestions? If going to let the battery run down overnight
[Samsung Galaxy S9 & S9+ Cross Device Development] teamacc:
Hold volume up (might be down, memory kinda fuzzy) (might need to add bixby too to this) + lock for 10+ seconds, until the system reboots, keep holding it until the splash screen shows up. Hold it still, until the splash screen disapppears. At that point the device is shut down without needing to drain the battery.
[Samsung Galaxy S9 & S9+ Cross Device Development] gusnz:
Thanks for looking into it! Should have read more of the WG docs myself :). Looks like the config option is still commented out with a leading # in the 4.9y_beta source though.

To check it worked, you don't need a server, in the Wireguard app check its Settings. If it says "Go userspace backend" the kernel module failed, if it says "Kernel module backend" it worked.
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Okay, I tried compiling the kernel too and got the same error. I think to pinpoint the issue we will have the patch every iteration of the kernel, starting at 4.9.219 and observe which batch of patches causes the failure. I did save every iteration as a separate branch in my repo, so if you have the time you can try that process. I'll try as well when I have time and see if I can fix the problem.

Note:

I did have an error installing the Wireguard recommended apps using:

$ sudo apt-get install libelf-dev linux-headers-$(uname -r) build-essential pkg-config

In particular linux-headers-$(uname -r) returned an error mentioning WSL2.

Could the compile problem be related to improper kernel header configuration as a result of using WSL2? Maybe the Wireguard team can help us?
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Update on Wireguard:

Kernel 4.9.223 compiles well with the wireguard patch. But when I build the ROM with the patched kernel it still shows 'userspace' in the Wireguard app. Apparently root is required for Wireguard to check and see if kernal functionality is available. I haven't tried rooting with the patched 4.9.223 kernel yet.

I tried the next kernels, but had to skip patches for 224, 225, 226, and 227 so far... I am not sure how many more patches I have to skip to get to the next one that works well with the Wireguard patch, but I'll keep trying.