yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] ElPakoTech:
Hi,

I made a new one and you can download it here: https://github.com/pakaoraki/OTA/releases

Just let you know this build is signed with my own keys: so in the future if you want to update to an official or to another unofficial build, you will need to wipe and start over (or see this page https://wiki.lineageos.org/signing_builds.html to change keys for a dirty flash). It's also 100% source code from @Synt4x.93 so big thanks to him again.

I plan to do some other updates time to time to keep the ROM secure, and the OTA should be working. I am not a confirmed android/lineage dev so there is absolutely no guaranty that any issues come due to Lineageos updated code. If the main dev build again updated Rom in the future, I would recommend to use it.

After flashing properly data/system from Lineage Recovery this time, and installed the new build, the problem I had with settings is gone now: sor far, any issues. I also use MindTheGapps this time as Lineageos dev recommend it for 18.1 and everything is fine. Just let you know that I wasn't able to install it the first time with TWRP (got some errors), it is why I switched to NikGapps in the first place, which is working great too.
[Samsung Galaxy S9 & S9+ Cross Device Development] dreas74:
@ElPakoTech​

Thanks for your work!

I will test the build and give you feedback.

Nice , if we have a maintained LOS with current security patches.

Have you a paypal adress, that i can buy you a beer?

Regards

dreas
[Samsung Galaxy S9 & S9+ Cross Device Development] ElPakoTech:
I will do my own build anyway if there is no official support so I'm happy to share it. No need to tips but thanks :)
[Samsung Galaxy S9 & S9+ Cross Device Development] nijazka:
hi all, Google Pay work on this rom?
[Samsung Galaxy S9 & S9+ Cross Device Development] dreas74:
Hi @ElPakoTech,

i have testet your build and i am very happy with it.

Now works the storage path in lineage snap cam to external sd-card.

I have waited long long time for fixing of this feature.

So, i would like to say thanks for your work and i recommend a separate treat on xda for your builds.

@nijazka

I dont´t use google pay but safety check would be pass.

congrets

dreas
[Samsung Galaxy S9 & S9+ Cross Device Development] Abduljalal Ahman:
Hi does dual sim works for sm-g960N with this rom?
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Hello. I need help compiling Lineage 18.1. The following is the command that I used:

brunch lineage_arm64-userdebug

Unfortunately I get the following output with an error:

[...]

16:51:34 soong minibootstrap failed with: exit status 1

FAILED: ninja: ./build/blueprint/bootstrap/build.ninja:11: loading 'out/soong/.minibootstrap/build-globs.ninja': Exec format error

subninja ${myGlobs}

^ near here

I would really appreciate some help or ate least some advice on where to go in this forum for help. I think I am close to compiling a working version, but cannot find anything about this kind of error. Thanks!
[Samsung Galaxy S9 & S9+ Cross Device Development] gusnz:
You need to put your model name in there e.g. "brunch starlte" or "brunch star2lte" as per the official wiki instructions. That should get it building I hope! See my post a page back in this thread for tips if it runs out of RAM and crashes mid build.
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Thank you so much for your advice.

I tried to run the command "brunch starlte" (because I have an S9) and the following error resulted:

[...]

Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.

[...]

** Don't have a product spec for: 'lineage_starlte'

** Do you have the right repo manifest?

I am suspecting that the roomservice.xml I included from Syntax's repository may have not been configured properly. I just downloaded it as is and placed it in the

android\lineage\.repo\local_manifests

directory. Since I created this directoiry in the Windows environment, it appears read permissions did not exist for the folder in the emulated Ubuntu environment.

I have since enabled full permissions for the new folder using: 'chmod +rwx

android\lineage\.repo\local_manifests

' and so far the repo sync command appears to be pulling in more data than usuall; specifically syntax's files. I will keep you posted on the progress.
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Update: I was able to successfully compile LineageOS-18.1 for starlte and execute an update of the OS and Recovery!

Before I delve into what the problems were and how I solved them, it is important to note that I am working on Windows 10 using Ubuntu in virtual mode.

The problem with roomservice was a permission issue. I was downloading the roomservice.xml using windows and then placing it in the local_manifests folder through windows explorer. This resulted in a permissions problem when the compiler was trying to access it during repo sync. Further research revealed that I should really be working with WSL2, which offers better functionality than WSL1 but Windows explorer cannot browse Ubuntu directories (like was possible with WSL1). I just decided to start from scratch at this point, reinstalling Ubuntu and downloading roomservice into local_manifests in the virtual Ubuntu environment. There were no permission issues and repo sync fetched the additional files properly.

The problem with soong exec format error ninja actually ended up being a virtualization setting I had to enable in the BIOS. By habit, I always disable SVM in my BIOS since I never had to use it, until now that is. The error line is indicating that an executable cannot be run in the virtual environment, which requires CPU virtualization to be enabled. After enabling it in my BIOS, the compiling worked flawlessly.

The compile process took about 2 hours at 100% CPU usage (R5 3600, Pcie4 nvme, 16GB 3200), with no errors. The upload process was carried out in the Windows environment using Heimdall (for the new recovery), ADB (for the sideload in recovery), and zadig (per Lineage's standard guide). Since I was flashing 18.1 with the May 2021 security update over Synt4x's older 18.1, I just updated via ADB in recovery instead of a full format.

The starlte works perfectly and all my apps and settings are still there! I look forward to building whenever I need to; especially when security updates are released.

Many thanks to @Synt4x.93 for housing all the device specific repos and @gusnz for the helpful guidance!
[Samsung Galaxy S9 & S9+ Cross Device Development] :
Hi all,

wouldn't it be much better if you guys team up with each other? So there would be an OS for the entire community. I don't understand why everyone compiles for themselves.

Thank you.
[Samsung Galaxy S9 & S9+ Cross Device Development] gnarf49:
After reading the last few pages I also started my own builds - thanks very much to @Synt4x.93 for the S9 repo and @gusnz for the helpful hints!

In case any of you want to build with signature spoofing for MicroG:

1. Download the patch from the MicroG repo as described here: https://github.com/microg/GmsCore/wiki/Signature-Spoofing

2. Follow the official build guide + roomservice.xml step as per gusnz

3. Apply the MicroG patch before the "breakfast" step in the official build guide

4. git commit -a (otherwise build will fail with repo versioning error)

5. Continue with official guide
[Samsung Galaxy S9 & S9+ Cross Device Development] gnarf49:
Hi sinnl0s,

teaming up is (sort of) what we do here - building ad-hoc for own use is surprisingly easy with all the info found in this thread.

The tricky bit and for pros only would be to reliably build new versions for e.g. every security update, host somewhere for folks to download or even enable OTA update, and especially making sure everything is 100% safe & secure.
[Samsung Galaxy S9 & S9+ Cross Device Development] ElPakoTech:
Hi,

Many reason I guess, :-)

Because It's fun ! teaching yourself how to do it, making your own and learning how to do it, having a better understanding of how it works, this is something I like to do.

I also want to see If I can apply small patch, maybe try to resolve some bug in the future, not sure if my knowledge would be enough.

But I understand what you mean, and team up to make a build for everyone look like doing an Official support. It would be nice, but you need a good understanding of the source code. Also you need to follow the Lineageos requirements : https://wiki.lineageos.org/submitting_device.html , https://github.com/LineageOS/charter/blob/master/device-support-requirements.md

@sinnl0s , @gnarf49

Using WSL to build look tricky but I am glad you did it !

I used a docker image for making my builds : https://hub.docker.com/r/lineageos4microg/docker-lineage-cicd

- sources: https://github.com/lineageos4microg/docker-lineage-cicd

It work really fine to me, it's base on ubuntu 20.04 and updated for lineage 18.1. You can sign the build with keys and there is also options for MicroG signature spoofing if you want (I'm not using it).

I am just a bit confuse about one thing: the tag "dev-keys" instead of "released-keys" in the build name, not sure if it's normal as the process look different than the official docks (https://wiki.lineageos.org/signing_builds.html). But the build looks correctly signed so I guess it's ok.

Let me know if for some reason it's better to not use this docker image, I am very open to advice.

Today I uploaded a new build for starlte with security patchs from June 5 : https://github.com/pakaoraki/OTA/releases

I am currently running it and so far so good, no problem. I am happy to share it, but the build is signed with my own keys so dirty flash won't work (you will need fresh start with TWRP), but OTA is ok if you're already installled the previous one. For people who want to use it, let me know if you have any issues.
[Samsung Galaxy S9 & S9+ Cross Device Development] citizenserious:
Hi everyone,

does anyone have any knowledge about the build Synt4x.93 was sharing in his last post ( May 15) on Telegram as "[Godlike9810]"?

It wasn't shared over OTA and there were absolutly no comments about this one so I am a little confused about it. Synt4x.93 only stated that we should Backup our **** and reflash Gapps afterwards (which I am not using).

Thanks a lot to ElPakoTech, sounds amazing I would very much like to switch to your build but I do not want to reset my phone right now. There is no other way I guess?

This community right here is just amazing, sadly I am just a user without any skill set to contribute to new builds, nevertheless I would very much like to do so.
[Samsung Galaxy S9 & S9+ Cross Device Development] dreas74:
Thanks @ElPakoTech for the new build. i have dirty flashed it and no issues so far.

theres no need to reflash gapps or magisk.
[Samsung Galaxy S9 & S9+ Cross Device Development] gusnz:
If you're brave you can follow the instructions on the Lineage Signing Builds page; I did this to switch to from 17.1 official release-keys to 18.1 test-keys for my build, before rebooting. Dangerous but worked! Note that if you want to switch to someone's dev-keys (as ElPakoTech suggests they're using) you would have to edit them into the script.
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
How did you get github to accept such a large file to upload? I tried it but it said it was too big.

On another note, maybe we could keep regularly checking in on this sub to just let each other know the compile worked with each new security update. I can confirm that the LOS 18.1 compile with June 5th security update works, just as you completed it 😀
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
Is there any chance to get regularily updates without having to make a clean install? I assume not.

I'm asking since it always takes me many hours until the device is set up as needed.

So propably I'll switch to ArrowOS hoping that updates will be delivered there for the next year or so.
[Samsung Galaxy S9 & S9+ Cross Device Development] murtzsch:
I've also built it and dirty flashed it, looking at logs (dmesg/logcat) I can see my kernel logs are flooded when the screen is on :

" [3: kworker/u17:2: 5042] [SSP]: MSG From MCU - SSP_batch_full 60 60 0

Any of you ever encountered this issue ?

edit: looks like it's gone with the lineageos-18.1 branch instead of 4.9.118.

still having weird issues, probably related to old vendor files
[Samsung Galaxy S9 & S9+ Cross Device Development] gnarf49:
Hi murtzsch, I see the same messages. Kernel 4.9.118, and vendor files ~1y old FXXU9.
[Samsung Galaxy S9 & S9+ Cross Device Development] ElPakoTech:
You can actually upload until 2GB as "released":

"Each file included in a release must be under 2 GB. There is no limit on the total size of a release, nor bandwidth usage."

https://docs.github.com/en/github/a...y/releasing-projects-on-github/about-releases
[Samsung Galaxy S9 & S9+ Cross Device Development] ElPakoTech:
Hi, I having the same messages too. I'm a bit confuse, what do you mean by lineage-18.1 branch / 4.9.118 ? The branch we use is Lineage 18.1, the kernel version is 4.9.118, right ?

The vendor I used is G960FXXU8DTC5 that I flashed to use Official Lineage 17.1 (April 2020).
[Samsung Galaxy S9 & S9+ Cross Device Development] murtzsch:
roomservice.xml ( https://github.com/synt4x93/local_manifests/blob/lineage-18.1/roomservice.xml#L3 ) uses revision="4.9.118".

With this branch I was getting constant kernel log flood. (enough to make logd/adb logcat crash).

I replaced 4.9.118 by lineage-18.1 in roomservice, I'm now running 4.9.218.

There're still a lot of repeated kernel logs (errors and warnings).

Iodé says the kernel sources they use is https://github.com/LineageOS/android_kernel_samsung_universal9810 but there's no 18.1 branch, and it looks like the same as https://github.com/synt4x93/android_kernel_samsung_universal9810/ branch lineageos-18.1, the one I'm now using.

For ArrowOS it looks like they're also using the same branch.

In the mean time synt4x93 has recently commited to his GCC branch. (but it's still based on 4.9.118)

I'll post a dump of the repeated kernel logs I'm getting.
[Samsung Galaxy S9 & S9+ Cross Device Development] Plabon7:
new to this forum. Please let me know which is the code name for s9 plus? i was three files as starlte star2lte and crownlte
[Samsung Galaxy S9 & S9+ Cross Device Development] noahthedominator:
Star2lte is the exynos s9+
[Samsung Galaxy S9 & S9+ Cross Device Development] Cyubei:
How to hide status bar when playing games? Its always there idk how to remove it
[Samsung Galaxy S9 & S9+ Cross Device Development] HouseOfBricks:
In the settings theres a "force fullscreen" for legacy apps, just search settings and you'll find it. It doesn't work for all apps but you might as well give it a shot ¯\_(ツ)_/¯
[Samsung Galaxy S9 & S9+ Cross Device Development] Cyubei:
Alr did that but it didnt work. Guess ill go back to resurrection remix
[Samsung Galaxy S9 & S9+ Cross Device Development] ugurkayaoglu5@gmail.com:
Hello location failed help me
[Samsung Galaxy S9 & S9+ Cross Device Development] Gueste4555:
Bonjour je souhaiterais savoir si une fois que la rom saura installer sur mon galaxy s9 plus SM-G965F je pourrais importer les contacts de ma carte sim sur l'application. Afin de pouvoir téléphoner et envoyer des messages. Merci d'avance. Cordialement

Translation: Hello I would like to know if once the rom will be able to install on my galaxy s9 plus SM-G965F I could import the contacts from my sim card into the application. In order to be able to phone and send messages. Thank you in advance. cordially
[Samsung Galaxy S9 & S9+ Cross Device Development] teamacc:
Should be good.

Contacts app -> settings -> import -> sim card

Untested.
[Samsung Galaxy S9 & S9+ Cross Device Development] Reag:
I can't believe how many times this has to be repeated. VOLTE will never work on any custom ROM. Never. The files required for this are proprietary. The only choice is to use stock or a rom based on it(Alexis rom).
[Samsung Galaxy S9 & S9+ Cross Device Development] Gueste4555:
Bonjour, j'aimerais savoir quelle version du twrp vous me conseillez pour pouvoir installer la rom sur mon appareil.

Translation: Hello, I would like to know which version of the twrp you advise me to be able to install the rom on my device.
[Samsung Galaxy S9 & S9+ Cross Device Development] Jariic:
Hello, I have been trying to install this ROM but i am having trouble installing Magisk and backing up the phones software

I get the two errors

Updater process ended with ERROR: 1

Error installing zip file /external_sd/Magisk-V16.0.zip'

Failed to imput '/data' (Invalid arguement)

If anyone can help me it would be appreciated

Also OEM unlock is on and so is usb debugging
[Samsung Galaxy S9 & S9+ Cross Device Development] LiNe1771:
Use twrp 3.3.1.0/3.3.1.1, not 3.4.0.0

Use magisk v20.4 or 21.1, not v16.

And your data (internal storage) is encrypted, you need to wipe your data first.
[Samsung Galaxy S9 & S9+ Cross Device Development] stepstra:
Thanks again for this rom. Two issues I found so far:

1. The Live Display shows some weird colouring (some blue and yellow tones appear like neon colours, so it is actually brighter in night mode instead of warmer)

2. The developer options offer no "Extended restart mode" (like reboot into recovery for example)
[Samsung Galaxy S9 & S9+ Cross Device Development] armindoriedel:
This Rom is compatible with Snapdragon 845.?
[Samsung Galaxy S9 & S9+ Cross Device Development] LiNe1771:
No, this exynos version.
[Samsung Galaxy S9 & S9+ Cross Device Development] Synt4x.93:
Thanks for the feedback.

1. Will look into this

2. You can enable advanced restart menu in the power menu settings, a different place than it was in android 10
[Samsung Galaxy S9 & S9+ Cross Device Development] Synt4x.93:
Also a lot of people messaging me asking what twrp version for android 11, doesn't matter just use twrp v3.4 or lineage recovery
[Samsung Galaxy S9 & S9+ Cross Device Development] ugurkayaoglu5@gmail.com:
hi gps not working can you help me. andorid 10 works but there is no 11 gps.
[Samsung Galaxy S9 & S9+ Cross Device Development] adrian0541:
I used the ZIP file in the link via TWRP and the camera stop working. I don't know if it installed the files for the wrong version. Any idea of how to install the camera correctly or how to repair the originals Lineage OS 18 camera files?
[Samsung Galaxy S9 & S9+ Cross Device Development] HouseOfBricks:
I don't know if you can repair the LineagOS camera files, but the zip you downloaded isn't meant to be flashed in the recovery. It just contains the APK for the GCAM and some camera profiles intended for different exynos devices.

It was made by Koopahmaniac and you can download the latest APK for ZGCAM from their website
[Samsung Galaxy S9 & S9+ Cross Device Development] murtzsch:
I've been trying 4.9.219 but it did not make any change WRT the recurring "dhd_rpm_state_t" error/warning logs.

I've just upgraded BL & CP to G965FXXUFFUE1, looks like the error/warning logs are gone.
[Samsung Galaxy S9 & S9+ Cross Device Development] king1990:
Pick this commit to suppress these logs

drivers: ssp_debug: suppress SSP log spam · ArrowOS-Devices/android_kernel_samsung_universal9810@1816b82

ssp_debug uses pr_info to constantly print useless information to dmesg. This makes identifying actual issues in dmesg needlessly more difficult. Remove the primary abuser of the ssp_debug to grea...

github.com
[Samsung Galaxy S9 & S9+ Cross Device Development] juanantofb:
Hi all, sorry for my english, only speak spanish.

Is mandatory clean ron compiled by

@ElPakoTech?

Now have LOS18 21 march

Thank.
[Samsung Galaxy S9 & S9+ Cross Device Development] gnarf49:
Thanks murtzsch for the hint with user build!

Same here, works fine and excessive logging is gone.

Two more hints:

- User can be dirty-flashed on top of userdebug, no problem, only Magisk root needs to be reinstalled via adb

- To get user build, run "lunch" where the official guide says "breakfast starlte". You'll get a list of available targets, choose user build then continue with mka bacon final step
[Samsung Galaxy S9 & S9+ Cross Device Development] Galaxy9plus-support:
Throw us a bone champ !!!

can you write the steps to self build a little more "newbie" proof :P

no idea about roomservice or breakfast step , you mean the "building" section of that github address then building tab ?

And that github > lineago with microG refers to LOS 15/16 , huh ?

Thanks :)
[Samsung Galaxy S9 & S9+ Cross Device Development] gnarf49:
No problem :)

Here's my complete build activities A-Z. Please note this is NOT a script, do one by one. Read the official build guide first, it tells what packages to install to be able to build android.

I run this on the latest Ubuntu, things may be different on other Linuxes or even Ubuntu versions.

Have fun!

---------------------------------

# prep folders and copy roomservice.xml + SigSpoof patch

mkdir -p ~/bin

mkdir -p ~/android/lineage

# Get and copy Syntx roomservice.xml and MicroG patches and copy to build directory.

# set PATH so it includes user's private bin if it exists

if [ -d "$HOME/bin" ] ; then

PATH="$HOME/bin:$PATH"

fi

source ~/.profile

# gr configure git

git config --global user.email "YourEmailHere"

git config --global user.name "YourGitAccountNameHere"

# enable caching

export USE_CCACHE=1

export CCACHE_EXEC=/usr/bin/ccache

ccache -M 50G

cd ~/android/lineage

repo init -u https://github.com/LineageOS/android.git -b lineage-18.1

# ---------------- from here for rebuilds ----------------

# ensure roomservice.xml and patches are copied/updated at this point

repo sync

cd ~/android/lineage

source build/envsetup.sh

# signature spoofing patches for MicroG

cd ~/android/lineage/frameworks/base

patch -p1 -i android_frameworks_base-R.patch

git commit -a

cd ~/android/lineage/

# choose build type user

lunch

# instead of brunch which may be too much for 16GB RAM

mka bacon -j 4
[Samsung Galaxy S9 & S9+ Cross Device Development] Galaxy9plus-support:
Awesome !!

Boosted swap to 10G, so -j 4 threads, with 12GigRam + 10Gig swap, building ....

How serious should I take the warnings? Should it really build perfectly without any warnings?

If it produces a file, I'm going to dirty flash ( no wipe ) straight over the @Synt4x.93 UNOFFICIAL 18.1 .... we'll see tomorrow morning .... building ...

+++ Update +++

built the user version, a few warnings but got the green

#### build completed successfully

installed right over @Synt4x.93's unofficial LOS 18.1 ( no wipe etc ) thru recovery menu

no data lost ( pics/ settings/ files/ apps/ msg/ phone log / contacts etc)

about >> android version >> android security update shows 5-june-21 security update

Will run as daily, but everything looks fine. Settings Icons have changed ( updated??)

YAY !!!

NB googles EXPOSURE APPS - covid19 as per

Android Help

Official Android Help Center where you can find tips and tutorials on using Android and other answers to frequently asked questions.

support.google.com

is NOT on the device, MicroG steps Not installed on my user build

Tnx heaps to @Synt4x.93 for the S9 repo and @gusnz + @gnarf49

Gr8 community !!
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
FYI:

Was able to successfully compile 18.1 (using roomservice.xml from synt4x) in windows 11 using WSL2 :) Compile and repo sync appear to take less time than in windows 10.
[Samsung Galaxy S9 & S9+ Cross Device Development] Galaxy9plus-support:
did you build the

eng

user

userdebug

build? whats the difference? besides reports of a very active logfile on the debug version?

( debug - which is the one @Synt4x.93 was building for this thread )
[Samsung Galaxy S9 & S9+ Cross Device Development] Rebel25:
Are there any newer LineageOS 18.1 builds?
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Yeah it shows as the userdebug version. The log file was quite active but the ROM performs properly and can be flashed over the existing ROM to keep all information on the phone.

lineage-18.1-20210704-UNOFFICIAL-starlte:

(June security update)

https://github.com/Geoknyda/OTA/releases/tag/starlte