yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
I would love to maintain it officially. In fact I reached out to the Lineage team about doing just that in September last year.

They responded back outlining how there are a lot of procedures to follow, including needing a team to manage the device tree and other repos. There were also some things that me not being a programmer just can't provide like being able to independently bug fix compile errors when changes are made by the LOS team that are incompatible with the S90/S9+. Right now I rely on the community to help with these fixes and I just copy them. It's worked so far because there are, humbly, more knowledgeable people maintaining device trees than I.

That leaves me in a position where I am learning from the experts and this wonderful community in a collaborative effort to keep the LOS 18.1 going for the S9 and S9+ :)
[Samsung Galaxy S9 & S9+ Cross Device Development] Dark Repear:
Oh That's Sad.Maybe You Can Try Apply To Become the official Maintainer for this phone like dot os Or Pixel Experience since There is no developers maintain it. and maybe it easier to recompile.if you really want to become the official Maintainer of lineage for this phone.why don't you reach out to them that helped you with the codes and error to compile for this ROM maybe You Can work With Them... Good Luck On Dev World.And Thank You Very Much For this ROM Hope You Can Update the security patch occasionally. 😀😀
[Samsung Galaxy S9 & S9+ Cross Device Development] citizenserious:
At first, congratulations on the new born son, I am glad to hear he is well and so are you, nice to have you back :)

I have not forgotten about the post above, and still willing to help.

But I kind of stuck, I could not figure out what you meant exactly with your repos and the "roomservice.xml". And also could you recommend a tutorial? I have a dual boot computer with Windows and Linux, so I think it would be better to try it directly on Linux. I am not sure which tutorial I should follow exactly, would be nice if you could give me a hint where to start best :)
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Thanks so much! He's a happy baby and we are happy parents :)

Your question is a big one, so I'll start at the beginning and we can move on from there one step at a time.

I am only familiar with running Linux (Ubuntu) in a Windows virtual environment. The first step would be to install that using this guide: https://docs.microsoft.com/en-us/windows/wsl/install. The next step would be to build LOS using this official guide here: https://wiki.lineageos.org/devices/starlte/build.

When you get to the part about extracting proprietary blobs, you can skip that and instead use a 'roomservice.xml' file. You will see that I created a 'local_manifests' repo on my Github account that houses the xml file you'll need. Download it and place it in the ~/android/lineage/.repo/local_manifests directory of your Ubuntu system. Then you should be able to start the build.

If you have any issues, please let me know and I'll do my best to share and help :)
[Samsung Galaxy S9 & S9+ Cross Device Development] Asdia:
What a pleasure to see the notification of an available update again :) Congratulations on this birth. I wish you the best. Thank you for keeping this ROM alive!
[Samsung Galaxy S9 & S9+ Cross Device Development] pumori:
Next time you say goodbye before leaving for fathership :cool:

Best reason in the world for adapting the focus...

Great having you back!
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
FYI January 15 update:

New Wireguard kernel patch upgrade:

20210606 (June 6, 2021) -> 20211208 (December 8, 2021)

Available via OTA or OP.

Have a great day!

:coffee::)
[Samsung Galaxy S9 & S9+ Cross Device Development] Gueste4555:
Je me suis toujours demandé si la rom Lineage os offrait la possibilité de basculer entre plusieurs comptes d'utilisateurs. quelqu'un pourrait-il me guider?

Translated by GT: I've always wondered if the Lineage os rom has the ability to switch between multiple user accounts. could someone guide me?
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
In the settings menu you will see an "accounts" section. Use this to add and manage multiple accounts.
[Samsung Galaxy S9 & S9+ Cross Device Development] Gueste4555:
THANKS
[Samsung Galaxy S9 & S9+ Cross Device Development] francoism90:
@Neurotical Did you tried building for LOS19 yet? Building this with the 19.0 sources, get me stuck on the boot animation. :/
[Samsung Galaxy S9 & S9+ Cross Device Development] king1990:
Use arrow trees if want to boot los19. Old tree need few modifications to make bootable) usable.
[Samsung Galaxy S9 & S9+ Cross Device Development] francoism90:
Could you please give more details? Because I'm trying to build it, but I'm keep getting stuck when doing this with los19 sources.

ArrowOS indeed boots fine. :)
[Samsung Galaxy S9 & S9+ Cross Device Development] king1990:
All trees are here https://github.com/ArrowOS-Devices

you can pick the commits to your tree or just use the same trees (common tree and kernel tree)
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Okay I'll re-run the repo init with LOS 19.0 branch and try and compile.

EDIT: It didn't work. This will take some time to figure out.
[Samsung Galaxy S9 & S9+ Cross Device Development] francoism90:
You can checkout my modified ArrowOS sources based on the exynos8920 ones (credits to both of them). It boots, but it keeps stuck at the boot animation.
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Did you use the LOS 19.0 recovery that outputs with the ROM?\
[Samsung Galaxy S9 & S9+ Cross Device Development] francoism90:
No, that didn't enter recovery. I'm using TWRP for that reason.

I didn't replace the rootdir + recovery.. maybe the fstab was wrong?
[Samsung Galaxy S9 & S9+ Cross Device Development] francoism90:
Here's the last proc log with the LOS19 sources.
[Samsung Galaxy S9 & S9+ Cross Device Development] zebdo:
great work! just a question though;

why not start official support, is something missing?

_______________________

edit:

nevermind, i searched the thread and have seen your previous reply, something about your "limited skillset"

i say you've got all the lineage nuance down and probably capable of continuing official support; i'd love to help out in any way I can, I've got a dev background but android development is new to me, it'll be a great learning experience

_______________________

edit edit:

gratz on becoming a father!
[Samsung Galaxy S9 & S9+ Cross Device Development] king1990:
as I said los19 was built and booted fine using arrow trees
[Samsung Galaxy S9 & S9+ Cross Device Development] francoism90:
I know, and I already built and got arrow up-and-running using their provided instructions.

However LOS has more features and I'm missing things like livedisplay, etc.
[Samsung Galaxy S9 & S9+ Cross Device Development] king1990:
You can build los using different trees , we already got los19 booted and working fine. I also made a tree with livedisplay support.

Check here

GitHub - baddar90/android_device_samsung_universal9810-common at aosp-livedisplay

Contribute to baddar90/android_device_samsung_universal9810-common development by creating an account on GitHub.

github.com

Use also arrow kernel to get everything booting and working fine
[Samsung Galaxy S9 & S9+ Cross Device Development] francoism90:
Oh wow! Thanks! :)
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Thanks for your input regarding building LOS 19.0 :) I have no issue building and maintaining a weekly LOS 19.0 variant for everyone, replacing the 18.1 variant, but I cannot build both 18.1 and 19.0 on the same Linux machine.

This means that if I am to experiment further with LOS 19.0 I will have to halt LOS 18.1 releases until I can figure out how to get the 19.0 to work. I don't want to stop the 18.1 weekly releases right now because the kernel and security patches are up to date and I want to keep this level of security going.

I do see that some repos are used to make the LOS 19.0 build work. What would be of great help from this community would be sharing the following:

Are you using the repo init -u https://github.com/LineageOS/android.git -b lineage-19.0 for the 19.0 build?

What are the contents of the roomerservice.xml that you are using with the LOS 19.0 build?

What recovery are you using with the LOS 19.0 build?

With this information for successful LOS 19.0 builds and flashes I will still be able to keep the weekly 18.1 release coming while you, the community, work out the proper repos to use for a functional 19.0 build :) Hopefully with this info we can get a 19.0 build going with the same kernel and security patch updates.
[Samsung Galaxy S9 & S9+ Cross Device Development] francoism90:
GitHub - francoism90/android_device_samsung_starlte

Contribute to francoism90/android_device_samsung_starlte development by creating an account on GitHub.

github.com

GitHub - francoism90/android_device_samsung_exynos9810-common

Contribute to francoism90/android_device_samsung_exynos9810-common development by creating an account on GitHub.

github.com

GitHub - francoism90/android_kernel_samsung_exynos9810

Contribute to francoism90/android_kernel_samsung_exynos9810 development by creating an account on GitHub.

github.com

I tried building LOS 19, but I get a lot of SELinux errors everytime I compile it and it ends up in a bootloop when I want to use it.
[Samsung Galaxy S9 & S9+ Cross Device Development] Speedmatze:
First of all: Congratulations to your new born! Best of all reasons to take a break and adjust to the new life.

Second: Still great to have you back.

Thank you for keeping our S9s alive with your continued ROM support.

I would just have one request:

I am using LOS with MicroG instead of Gapps and need MS Exchange connectivity to sync a calendar. Until LOS17.1 it was easy to get this to work with the standard Email app. Unfortunately that is no longer included in LOS18.

Would it be possible to include the old version into your ROM to get MS Exchange back (as described here )?
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Just out of curiosity, before I dig into this further, have you tried using the MS Outlook app from the Aurora Store?
[Samsung Galaxy S9 & S9+ Cross Device Development] Speedmatze:
Yes, tried it and it is not great. More importantly though it is blocked as client from the Exchange server in question because of security issues. I could probably get around that by faking the client ID but that would not be worth the trouble for that app...
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
I tried checking out the link referenced: https://github.com/bananer/android_manifests/blob/master/apps_from_17.1.xml but it is no longer available. Is there another source for this manifest?
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
So if we sync the LOS 19.0 repo and use the following repos in our roomservice.xml:

https://github.com/ArrowOS-Devices/android_kernel_samsung_universal9810 (branch Arrow-12.0)

https://github.com/ArrowOS-Devices/android_device_samsung_universal9810-common (branch Arrow-12.0)

https://github.com/ArrowOS-Devices/android_device_samsung_starlte (branch Arrow-12.0)

https://github.com/LineageOS/android_hardware_samsung (branch lineage-19.0)

The compile will work? Are these only items you included in your roomservice.xml when compiling LOS 19.0 for starlte?

What about the proprietary_vendor_samsung repo? Would this one suffice?

https://github.com/Geoknyda/proprietary_vendor_samsung (branch lineage 18.1)
[Samsung Galaxy S9 & S9+ Cross Device Development] CyderXDA:
you can. and you don't need the android_hardware_samsung I think. Just use kernel, common trees, devices trees and vendor from arrow and build, then it should build and boot.
[Samsung Galaxy S9 & S9+ Cross Device Development] king1990:
hardware/samsung is not needed, we only uses livedisplay and touch hidl, I added livedisplay in this branch https://github.com/baddar90/android_device_samsung_universal9810-common/tree/aosp-livedisplay and will add touch hal later but to start up you can use the above repos until I make a clean los19 branch.

for vendor, use the one in arrowos devices will fix ok google.

The rom will compile and boot fine as tested before. Goodluck
[Samsung Galaxy S9 & S9+ Cross Device Development] king1990:
the common tree does not look good at all , I don't think it will work like that. use my branch for livedisplay and all other repos from arrowos devices (don't use hardware/samsung).
[Samsung Galaxy S9 & S9+ Cross Device Development] Speedmatze:
Here are the contents of the xml file:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- commented out in https://github.com/LineageOS/android/blob/lineage-18.1/snippets/lineage.xml -->
<project path="packages/apps/Email" name="LineageOS/android_packages_apps_Email" revision="lineage-17.1" />
<project path="packages/apps/Exchange" name="LineageOS/android_packages_apps_Exchange" revision="lineage-17.1" />
<project path="packages/apps/UnifiedEmail" name="LineageOS/android_packages_apps_UnifiedEmail" revision="lineage-17.1" />
</manifest>
[Samsung Galaxy S9 & S9+ Cross Device Development] francoism90:
Thanks for your honest feedback. :)

I'll checkout livedisplay and others in hidl.

Just one question, should we also use vibrator and power? It seems to work fine using the ones seen in 9820.

Also about SELinux rules, I notice this is missing, why?

PS. I'm just trying to learn, just asking for feedback.
[Samsung Galaxy S9 & S9+ Cross Device Development] king1990:
The vibrator and power hal are already precompiled and used in the tree. Selinux is not missing. Trees are enforcing, only encryption is the major bug.

First boot your build then you can modify the tree as you like using this tree as a base.

Also try to keep authorship , your commits in the kernel tree are without any authorship which is not encouragd in open source work.
[Samsung Galaxy S9 & S9+ Cross Device Development] francoism90:
This is what I'm asking about SELinux (most of the things I'm comparing against 9820 sources):

BOARD_SEPOLICY_TEE_FLAVOR := mobicore
include device/lineage/sepolicy/exynos/sepolicy.mk
include device/samsung_slsi/sepolicy/sepolicy.mk

Also why is it pointing to private and not vendor? Aren't the policies 'vendor' related?

Thanks!
[Samsung Galaxy S9 & S9+ Cross Device Development] king1990:
You don't need to modify anything if your aim to boot los19. Use arrow trees and you will be fine. However I can't help you with your trees specially when there are two devs working on completely new trees. I would suggest to use the available trees which are perfectly fine or wait till new trees are made public.
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
FYI weekly update includes:

Security patch updated to January 5, 2022.

MS Exchange feature added.

Legacy LOS 17.1 e-mail app added.

Now available via OTA or OP.

Have a nice day :)
[Samsung Galaxy S9 & S9+ Cross Device Development] jer194:
Thanks for maintaining this ROM!

For those who want to use microg instead of Google Apps,

would you mind to add Signature Spoofing Support from here:

docker-lineage-cicd/src/signature_spoofing_patches/android_frameworks_base-R.patch at master · lineageos4microg/docker-lineage-cicd

Docker microservice for LineageOS Continuous Integration and Continous Deployment - lineageos4microg/docker-lineage-cicd

github.com

lineageos4microg so far does not seem to provide ROMs for starlte

(probably because there is no official LOS 18.1).
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
mkdir ~/spoofpatch && cd ~/spoofpatch && wget https://github.com/lineageos4microg/docker-lineage-cicd/blob/master/src/signature_spoofing_patches/android_frameworks_base-R.patch && wget https://github.com/lineageos4microg/docker-lineage-cicd/blob/master/src/signature_spoofing_patches/packages_apps_PermissionController-R.patch && wget https://github.com/lineageos4microg/docker-lineage-cicd/blob/master/src/signature_spoofing_patches/frameworks_base_config.xml

mkdir -p ~/android/lineage/vendor/lineage/overlay/microg/frameworks/base/core/res/res/values && cp ~/spoofpatch/frameworks_base_config.xml ~/android/lineage/vendor/lineage/overlay/microg/frameworks/base/core/res/res/values/config.xml
cd ~/android/lineage/frameworks/base && patch -p1 -i ~/spoofpatch/android_frameworks_base-R.patch
cd ~/android/lineage/packages/apps/PermissionController && patch -p1 -i ~/spoofpatch/packages_apps_PermissionController-R.patch

With this custom script I was able to successfully add in signature spoofing support (y)(y)(y)

I will be releasing a ROM update OTA in the next few hours :)
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
FYI new update includes:

Signature spoofing support.

Available via OTA or OP.

Have a great evening :) :cool::giggle:
[Samsung Galaxy S9 & S9+ Cross Device Development] jer194:
Cool, thanks a lot!

It also enables the 'google-less' exposure notification framework,

for the Corona Warn App eg.
[Samsung Galaxy S9 & S9+ Cross Device Development] leap_ahead:
Any info how to flash lineage recovery from stock ?
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Samsung Galaxy S9+ (star2lte) - LineageOS ROMs

LineageOS ROM Samsung Galaxy S9+ (star2lte) Official roms Download last nightly build (2019-02-21)LineageOS 15.1 – [ Android 8.1 (Oreo) ] Previous version (nightly) (2021-01-21) LineageOS 17.1 – [ Android 10.0 (Queen Cake) ] [Recovery file (2021-01-21)] Previous version (nightly) (2021-01-14)...

lineageosroms.com

This official Lineage guide for the Starlte explains how to upload the custom recovery. It explains how to use heimdall to flash a recovery file using the following command:

heimdall flash --RECOVERY <recovery_filename>.img --no-reboot
[Samsung Galaxy S9 & S9+ Cross Device Development] HQwarp:
Thank you @Neurotical for your effort on the building the ROM, for a moment I thought I needed to get back to the not so great Arrow OS. Congratulations on the newborn!

I see that there are attempts to use Arrow OS sources. Let me add two other features to the not working well list on Arrow OS and more reasons to use Lineage sources.

First, the build-in keyboard Arrow OS has doesn't support dictionaries and spell check for many languages that are supported build-in by LOS. Besides English, Spanish, and maybe another language, other languages have very basic or non at all support. It is important for people that love their privacy, especially now with your help with adding spoofing to the ROM.

Second, Arrow OS has a battery optimizer feature that has too many bugs, even if the feature is not enabled. In my setup, I needed to reformat my phone, because, of a bug that appears from time to time that prevents charging the battery. This is hugely inconvenient especially when this feature is disabled all the time and I never use it.
[Samsung Galaxy S9 & S9+ Cross Device Development] Speedmatze:
Just installed the new version. Exchange integration and signature spoofing are working nicely!

These additions of the last two build have just made (installation and update) life much easier for non-google users.

Thank you!
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Thanks HQWarp and Speedmatze. I am glad that the ROM is performing well enough for your needs!

As you probably know already, I do my best to promptly add in any additional features as requested that make your experience better :) Added on top of that, we get the latest kernel patches right from the LTS team, LOS patches from the LOS team, and monthly security patches form AOSP. Pretty nice package for a great phone and even better community :)
[Samsung Galaxy S9 & S9+ Cross Device Development] waynea:
so with dirty flash there will be no loss of data or anything?
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
That is correct :)
[Samsung Galaxy S9 & S9+ Cross Device Development] waynea:
many thanks for such prompt help!!
[Samsung Galaxy S9 & S9+ Cross Device Development] Khalil777:
I've been using this ROM for a week now and i have encountered ZERO issues, my only complaint is the camera app that is pretty bad with how it handles light, but i'll be trying some GCams, hopefully they work well.

Thanks again for this, i'm also going to update to the latest kernel, for that do i need to only flash the recovery image? I'm currently on the 08/07/2021 weekly build.
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
That's how I have been testing the kernel updates; I've just been updating the recovery and then dirty flashing the ROM. Works well every time. OTA also works fine to receive the kernel updates.
[Samsung Galaxy S9 & S9+ Cross Device Development] francoism90:
Many thanks! Will it eventually become an official project (again)? :)

Edit: I'm stunned how good this ROM works compared to the original Samsung one. It's blazing fast and so far encryption, magisk, etc. seem to be working fine. :)

How can one donate?
[Samsung Galaxy S9 & S9+ Cross Device Development] Galaxy9plus-support:
Outstanding knowledge and support Neurotical

Greatly appreciated by many more I'm sure :)
[Samsung Galaxy S9 & S9+ Cross Device Development] Khalil777:
Hi

i was on lineage-18.1-20210708-UNOFFICIAL-star2lte

i flashed lineage-18.1-20210714-UNOFFICIAL-star2lte-kernel-4.9.275 as well as the recovery image and now its just stuck at the boot image, even after restoring a TWRP backup i made yesterday stucks at the boot image, any ideas? i restored boot system vendor and data from TWRP and still no luck.
[Samsung Galaxy S9 & S9+ Cross Device Development] rpbica:
Hi guys

I'm coming from one of Synt4x's ROM builds.

I have it encrypted.

Do I have to decryoted, dirty flash, and them encrypt it again?

Thank you very much!
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Okay, I compiled a few other versions with older kernels for you to try.

Check out the downloads for your star2lte in my support repo.

When we find a kernel that works for you, I can upload newer ones until we find the one that doesn't work and we'll stop there.
[Samsung Galaxy S9 & S9+ Cross Device Development] duptup4:
hello, i really want to install this rom but i am afraid there is no beginner guide to install it

i am currently on Alexis Rom 2.4 Android 10 One UI 2.5

please if anyone can mention very simple steps at beginner level how to install this rom.
[Samsung Galaxy S9 & S9+ Cross Device Development] aureljared:
Fantastic work with the upstreamed Jul 14 build! Running rock-solid on my starlte, dirty flashed over Jul 8. Also got to pass SafetyNet through MagiskHide (+ Props Config, Universal SafetyNet Fix).
[Samsung Galaxy S9 & S9+ Cross Device Development] Khalil777:
okay i clicked on the support repo link but it takes me nowhere specific and i don't know where to find your files.

i did manage to get my phone up and running, i restored again via TWRP and it didnt want to boot so i dirty flashed the lineage-18.1-20210708-UNOFFICIAL-star2lte which is what i was on when i made the backup, and then it booted.

I would still like to update the kernel though, if you don't mind helping me with that.

Thanks a lot
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Thanks for the feedback, and I am super glad you got it back up and running!

Please try this updated link to the support repo:

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

There are several older kernel versions for you to try. When you find the newest one that works for you, I will compile newer ones for you at smaller increments for you to try. I can have new ROMs & recoveries compiled and uploaded to the support repo for you within 15 minutes, so this approach should be a fluid experience for you :)

I'll be checking this thread often for your updates/requests :)
[Samsung Galaxy S9 & S9+ Cross Device Development] Khalil777:
Thanks a lot, busy downloading all the files now and will start at the oldest version. SO as you said earlier i should flash the recovery.img (can i do that via TWRP?) and then the rom after that and wipe cache and reboot right?