yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] roizcorp2:
nothing, but no March security patch while other roms based on this awesome dev's work already delivered

i've used many many custom roms over the years and the rule is there is no EOL announcement, they all die quietly, this is why i ask when i sense inactivity
[Samsung Galaxy S9 & S9+ Cross Device Development] Koffietijd:
@geronimoge, You are right!

I was using ZGCam from koopahtmaniac.com and that was working reassonable well. Just now installed this BSG's version: MGC_8.1.101_A9_PV0m_Eng.apk and that is working even better and more fluid. Thank you for pointing that out.

I'm running samsung starlte S9, with Lineageos 18.1 en Nikgapps
[Samsung Galaxy S9 & S9+ Cross Device Development] roizcorp2:
It looks like it has some problem write the pictures on the disk, did you managed?

the gallery app shows black images instead
[Samsung Galaxy S9 & S9+ Cross Device Development] Aprate:
I know for a fact that this is not EOL, the dev is still working hard on making a better LOS experience on Exynos 9810, which includes this phone.

Please have patiece, all the good comes with time :p
[Samsung Galaxy S9 & S9+ Cross Device Development] Koffietijd:
No problems at all. All working fine.

I think I used the camera libs from vendor pie.
[Samsung Galaxy S9 & S9+ Cross Device Development] Galaxy9plus-support:
This UNOFF 18.1 Rom is good. Battery life better than Official 17.1, +android 11 options. Wifi is fine / connect 2.4 / 5G no problem. GPS location is faster. Used for daily with zero problems. Phone runs 'with less temperature' when using GPS maps navigation ( see OSMAnd maps issue 17.1 - animated position option), running games runs significantly lower temp. Camera is fine, using open camera fdroid. Multiple bluetooth connections possible too ( headphones + file transfer simultanously ). Fast charging ( with adapter ) working, Fingerprint, NFC, hotspot and the torch working seemlessly. Does the torch seem brighter ???? ahhaha

One tiny bug, I need to reboot WITHOUT the 3.5mm earphone jack plugged in, otherwise the phones speakers default to off. ( just reboot with 3.5mm jack unplugged = fixed - both phone OR earphones can work )

Dont forget to encrypt AFTER fresh install in LOS options as default is off. TWRP 3.5.0_9 flashed as recovery. Make sure existing OS is Android 10 already ( or LOS 17.1 official already ). Check the "OEM" opton is also 'checking' otherwise you cant do any upgrade.

+++++++++++++++++++++++++++++++++++++

Bought a 9+ because its the most recent phone ( 2018) for LOS. Very happy to contribute BTC if theres a dev donate button somewhere.

+++++++++++++++++++++++++++++++++++++

Very happy NOT EOL.

Only problem, can't get 5G celular network on this phone with the new OS, maxed at 4G LTE

Is there a patch for that here ????? ( jokes )

:O

Yay to de-googled supported device OS
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
Sorry but I don't have this problem.
[Samsung Galaxy S9 & S9+ Cross Device Development] Mahmudruet:
I am using pixel experience now. Can anybody mention the quick differences between Pixel experience and Lineage for S9 so far.
[Samsung Galaxy S9 & S9+ Cross Device Development] sarius02:
I just noticed that Magisk stopped working for me. I'm pretty sure it worked before the update yesterday, now the Manager doesn't detect the installed Magisk. Tried to reflash in recovery multiple times - log indicated success - but still can't see it in Manager. I tried it with Canary as well as Beta/stable release channel, still no success.

There is a similar issue on the Magisk GitHub, although it seem like not anybody is experiencing this problem.

Does anybody else here has this issue and may know a possible fix for it?
[Samsung Galaxy S9 & S9+ Cross Device Development] Koffietijd:
I've had no problems with Magisk. I have installed version 22. Today I installed the latest release from the rom 21-3-2021, reinstalled Nikgapps core from 30-1-2021 and Magisk 22 again. Still evrything is working and Magisk is recognised.

Edit: I just found out that I had to reinstalll: MGC_8.1.101_A9_PV0m_Eng.apk camera as well.
[Samsung Galaxy S9 & S9+ Cross Device Development] Mahmudruet:
Can you help me out about how to download the rom. I have just found the github repository but do not understand how to get the flashable zip file.
[Samsung Galaxy S9 & S9+ Cross Device Development] sarius02:
In the very first post, there is a link named "Download". When you follow it, you get to a GitHub releases page with roughly 10 entries. There should be a file like "lineage-18.1-20210321-UNOFFICIAL-starlte.zip" for every device, this example would be for S9.

Beside I would please you to NOT post questions as this as replies to totally unrelated posts like mine ;)
[Samsung Galaxy S9 & S9+ Cross Device Development] sarius02:
Hmm, that's quite strange..

Just for curiosity, did you install via flashable zip/apk or did you patch your boot.img?

I was just able to "repair" my Magisk by using the latter, although I'm still fighting with the problems of the current Canary release
[Samsung Galaxy S9 & S9+ Cross Device Development] Koffietijd:
I flashed the Magisk 22 zip directly with TWRP 3.4xx using sideload from my pc. I installed NikGapps in the same sideload way. I use S9 (Starlte).
[Samsung Galaxy S9 & S9+ Cross Device Development] sarius02:
Hmm.. then TWRP may be the issue, as I have the latest release installed, which is 3.5.1_9 I think.

Anyway, thank you!! :)
[Samsung Galaxy S9 & S9+ Cross Device Development] Koffietijd:
wait, maybe I'm wrong here. I check my twrp version!

edit: 3.5.0_9-0

Edit: I just upgraded TWRP to the latest version. 3.5.1_9-0. Unfortunately still not 3.5.1_10

But also it looks like everything is working well here.
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
I'm having problems with Osmand+ and compass. It won't work when I'm switching compass mode in map view from 'north alwqys above' to other. So you don't have that issue?
[Samsung Galaxy S9 & S9+ Cross Device Development] Abduljalal Ahman:
Installed this rom recently and everything works exceptionally well, very impressed by the developers.

But one thing thats bugging me is the amount of ram system apps eat up and also what kind of kernel is best suited to play demanding games like genshin impact or pubg ? Cos right from the bat it gets pretty hot and slows down the game. But overall impressed with this rom. Keep up the good work.
[Samsung Galaxy S9 & S9+ Cross Device Development] Raden Yudha:
Installed this rom recently and everything works exceptionally well, very impressed by the developers.

Im installing White Wolf kernels. And my problem is when i charge while playing games like Mobile Legend or Etc My Battery cant Up And Run Down, but when not playing games everythings work great. Any some reason for my problem to solve that issue?

Thank You before :)

Regards for Developer this ROM!

Sorry for my bad English.
[Samsung Galaxy S9 & S9+ Cross Device Development] Reag:
Hi, I know nobody uses this feature, but is Wifi Direct working for anyone? I can see my device on other devices but I can't see anyone else.

Here's the log I get when I try to connect to my own device from another one.

03-22 17:53:41.839 4686 4686 E wificond: Failed to get interface index from scan result notification
03-22 17:53:41.894 4686 4686 W wificond: Failed to get NL80211_ATTR_IFINDEXfrom NL80211_CMD_FRAME_TX_STATUS event
03-22 17:53:42.141 31568 31568 I wpa_supplicant: P2P: Received Provision Discovery Request from c2:ee:fb:59:93:13 with config methods 0x80 (freq=2412)
03-22 17:53:42.142 31568 31568 I wpa_supplicant: P2P: Set prekey state (NONE -> NONE)
03-22 17:53:42.142 31568 31568 I wpa_supplicant: P2P: Sending Provision Discovery Response
03-22 17:53:42.205 31568 31568 I wpa_supplicant: P2P-PROV-DISC-PBC-REQ c2:ee:fb:59:93:13 p2p_dev_addr=c2:ee:fb:59:93:13 pri_dev_type=10-0050F204-5 name='Android_5b8f' config_methods=0x188 dev_capab=0x25 group_capab=0x0
03-22 17:53:42.209 31568 31568 I wpa_supplicant: P2P: Received GO Negotiation Request from c2:ee:fb:59:93:13(freq=2412)
03-22 17:53:42.210 31568 31568 I wpa_supplicant: P2P-GO-NEG-REQUEST c2:ee:fb:59:93:13 dev_passwd_id=4 go_intent=6
03-22 17:53:42.214 31568 31568 I wpa_supplicant: P2P: Sending GO Negotiation Response with status=1
03-22 17:53:42.217 4932 5118 E WifiP2pService: Dropping GO neg request
03-22 17:53:42.217 4932 5118 E WifiP2pService: address: c2:ee:fb:59:93:13
03-22 17:53:42.217 4932 5118 E WifiP2pService: wps: setup: 0
03-22 17:53:42.217 4932 5118 E WifiP2pService: BSSID: null
03-22 17:53:42.217 4932 5118 E WifiP2pService: pin: null
03-22 17:53:42.217 4932 5118 E WifiP2pService:
03-22 17:53:42.217 4932 5118 E WifiP2pService: groupOwnerIntent: -1
03-22 17:53:42.217 4932 5118 E WifiP2pService: persist: -2
03-22 17:53:42.217 4932 5118 E WifiP2pService: networkName:
03-22 17:53:42.217 4932 5118 E WifiP2pService: passphrase: <empty>
03-22 17:53:42.217 4932 5118 E WifiP2pService: groupOwnerBand: 0
03-22 17:53:42.496 0 0 I : [3: watchdogd: 4374] s3c2410-wdt 10050000.watchdog_cl0: Watchdog cluster 0 keepalive!, wtcnt = fff5
03-22 17:53:42.613 5233 5411 E BtGatt.ContextMap: Context not found for ID 5
03-22 17:53:42.205 4686 4686 I chatty : uid=1010(wifi) /system/bin/wificond identical 5 lines
03-22 17:53:42.233 4686 4686 W wificond: Failed to get NL80211_ATTR_IFINDEXfrom NL80211_CMD_FRAME_TX_STATUS event

Thanks
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
I really love this ROM and flashed the update today.

My only problem is that I'll have lost root after each update.

So all the time I'm flashing LOS updates I'll have to:

- download LOS update

- extract LOS update

- choosing boot.img from LOS update and push to device

- choosing this boot.img within Magisk app and 'select and patch file' since it's the only shown option and wait until it's finished then

(the last following steps are different from the Magisk tutorial since my S9 isn't recognized in fastboot mode from no device. Also changing cables doesn't work)

- booting to recovery (TWRP), and using install mode

- switching to 'install img', choosing the new magisk_patched_*.img and flash as boot.img

- reboot to system with root again

Am I doing something wrong?
[Samsung Galaxy S9 & S9+ Cross Device Development] jomann:
You should be able to flash the MagiskApp.apk (after renaming to .zip) with TWRP. I think the problem is that Magisk only patches the kernel when you patch the image. When you are able to flash Magisk directly, it "installs" the patching tool and is then able to patch the kernel as needed.
[Samsung Galaxy S9 & S9+ Cross Device Development] testerS4:
My Magisk is also "shot down" after every system update. I have to manually install it again and again via TWRP. GooglePlay service was also broken. NikGapp also reinstalled.

I always switch between 17.1 and 18.1 to test changes. But so far the 18.1 is still too annoying for me. The constant reinstallation of various applications is not nice.

(sorry for Engl ... I use translators)

Device: G960F (starlte)
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
Well, as writen in Magisk tutorial you normally shouldn't use this option.

"[...] installing Magisk through custom recoveries on modern devices is no longer recommended. The custom recovery installation method exists purely for legacy support"

So I thought I'd do it the right way. But unfortunately it doesn't seem to work.
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
Yesterday i flashed the release 21-03-2021.

Today my phone was getting really hot, I noticed it while having a call.

A few minutes ago I wanted to check my phone again and it was off.

It seems as the battery went from 100% to 0% within minutes.

Anyone else with this problem?
[Samsung Galaxy S9 & S9+ Cross Device Development] Galaxy9plus-support:
No I dont have that problem, I can switch from nth, to direction of travel etc without problem. osmAnd 3.9.10 from fdroid
[Samsung Galaxy S9 & S9+ Cross Device Development] Galaxy9plus-support:
I dont even notice a temp change on LOS 18.1, but i make a habit of "force stop" apps after I have finished with them. Settings > apps and notifications .. this displays the last 3 apps, click on the app > force stop. frees up phone resources. Yes, you can force stop "phone" and "messaging" service too, phone still receivces incoming / make outgoing calls, and SMS likewise. Just "force stop" after the conversation. Battery live depends on my use, but I go all day at screen 55%, and using Pixel Battery Saver app ( adds small black dots that you cant see ) and permanent dark mode - even in daylight its fine. bluetooth off, location off, wifi off, data off when not needed. you get prompted to turn data on for MMS messages. Email needs data obviously, 9 Plus.

Not using Gapps at all. Using the updated version from 21-3-21
[Samsung Galaxy S9 & S9+ Cross Device Development] jomann:
I could certainly be wrong, but I think custom roms will typically fall under "legacy support". The tutorial also seems to focus completely on stock roms and using Odin for flashing which doesn't apply (or isn't necessary?) for custom roms.
[Samsung Galaxy S9 & S9+ Cross Device Development] Koffietijd:
Is it possible to update the underlying image like vendor from the newest stock on Starlte/S9 exeynos? Without reinstall everything?
[Samsung Galaxy S9 & S9+ Cross Device Development] jomann:
crDroid has a firmware link for the S9/S9+ that references PDA, CSC, and modem direct installs for Odin and TWRP. I don't see anything for Vendor, but you may try backing up the current VENDOR partition and using TWRP to flash a new vendor.img from the latest stock rom. Make sure you aren't changing Android version.
[Samsung Galaxy S9 & S9+ Cross Device Development] mbonell:
Do I just flash with twrp to use gcam?
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
I'd start without flashing, for example using gcam with BSG port from here.
[Samsung Galaxy S9 & S9+ Cross Device Development] mbonell:
Thanks, latest version seems to work as well.
[Samsung Galaxy S9 & S9+ Cross Device Development] Leon:
Well, some people reported software brick on camera after using it, so I don't know anymore. But as far I remember it was working fine for me. And yes, it's for twrp, but I don't remember if its only libs for front camera or u will find as well the apk in config folder.
[Samsung Galaxy S9 & S9+ Cross Device Development] Galaxy9plus-support:
A few things missing on this model phone with this ROM,

i) app / hardware to use the heart beat sensor on back of phone ( without the white flash light / camera )

ii) edge notification lighting as part of LOS ( third party apps + ads is an option)

iii) gesture on rear fingerprint sensor ( swipe up on sensor and swipe down can be configured )

iv) gesture to "tap" on rear of device to map to an action

But the LOS 18.1 is fine otherwise, this is just for those looking for a total replacement to Samsung / Android
[Samsung Galaxy S9 & S9+ Cross Device Development] alterechtschreibung:
Thread starter @Synt4x.93 Thread starter Synt4x.93 Can you please include Signature-Spoofing for microG?

Signature Spoofing

Free implementation of Play Services. Contribute to microg/GmsCore development by creating an account on GitHub.

github.com

docker-lineage-cicd/src/signature_spoofing_patches at master · lineageos4microg/docker-lineage-cicd

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

github.com
[Samsung Galaxy S9 & S9+ Cross Device Development] smallz2k:
Wheres the rom download link? Im not used to using 'github' to download anything which is were the download link goes?

Thanks.
[Samsung Galaxy S9 & S9+ Cross Device Development] Jackychans:
great job.

Is this rom able to pass safetynet natively (without using additional tricks such as Magisk) ?
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
Just take the latest date and choose the version for your model at 'Assets'.
[Samsung Galaxy S9 & S9+ Cross Device Development] muammil:
I lost baseband after flashing this rom. No imei. Any solution?
[Samsung Galaxy S9 & S9+ Cross Device Development] testerS4:
hopefully made a backup beforehand? Without that, never fumble with the device.

(sorry for engl ... I use translators)

Device: G960F (starlte)
[Samsung Galaxy S9 & S9+ Cross Device Development] owenjm:
Thanks for this amazing ROM @Synt4x.93 ! Everything that is supposed to work is working perfectly, smoothly and flawlessly. I really hope that this is lined up to be an Official release so that updates keep coming through automatically?

One thing to note -- like many ROMs for this device, it's missing a gps.conf file in /system/etc to provide the ephemeris data links for other systems. Without the correct file, GPS works but only locks onto GPS satellites; with the file, I'm able to connect to BeiDou, GLONASS, Galileo and QZSS sats and get a faster and more accurate fix.

For anyone like me who was coming from an Oreo vendor / bootloader, I had success doing the following with TWRP 3.2.3

Factory reset / full system wipe

Flash DTC5 vendor

Flash ROM

Flash GAPPS

Flash Magisk 21.4 (didn't dare use the latest Magisk.app, those instructions are clear as mud and greatly scare me!)

Flash DTC5 bootloader

Flash latest SoLdieR9312 flashable firmware (ETF5_r7 in my case -- was worried if this would cause problems, but it seems fine)

There was thankfully no need to revert to stock with Heimdall (which I had thought was required, and is what had put me off upgrading to a Android10-vendor-based ROM for the longest time).

I migrated my apps with Migrate (as apparently TiBu no longer works, sadtimes), and that more-or-less worked provided you don't try to restore permissions.

Feels like my phone has a new lease of life :)
[Samsung Galaxy S9 & S9+ Cross Device Development] gnarf49:
The gps.conf seems to have changed location, I found /vendor/etc/gnss/gps.xml on my S9 running on last official MicroG 17.1 from 18/Jan/2021. Galileo is enabled but I have never seen it being used (trying with SATSTAT). GPS and GLONASS working perfectly fine always, sometimes a Beidou signal is received.
[Samsung Galaxy S9 & S9+ Cross Device Development] Cecillatour:
Use Frija to download Samsung stock ROM. Unpack it and flash CP part (which contains modem) via Odin.
[Samsung Galaxy S9 & S9+ Cross Device Development] owenjm:
gps.xml != gps.conf

There's nothing wrong with the gps.xml file in vendor, but you need a separate (and very different!) gps.conf to find the other satellite clusters. (Yes, you will get an occasional GLONASS or BeiDou without it - but I see 32+ satellites for my fix, which I suspect is a lot more than what you're seeing ...)

The GPS works tolerably without the conf file, but it's so much faster to get a cold fix (and should be more accurate in suboptimal conditions) with it.
[Samsung Galaxy S9 & S9+ Cross Device Development] SirBoss1st:
Will it eventually become an official version?
[Samsung Galaxy S9 & S9+ Cross Device Development] Confuserix:
Just have flashed my Galaxy S9+ Duos but I had no success although I strictly followed the installation procedure given here: https://wiki.lineageos.org/devices/star2lte/install

First I made sure to have an exynox CPU and that Android 10 is installed and downloading the correct recovery image. Then I have installed adb following the advice given here: https://wiki.lineageos.org/adb_fastboot_guide.html

and checked it via "adb shell". It was answered by "daemon started at tcp:5037"

My Heimdall version is that from the link within the LineageOS guide.

Then I flashed the phone via heimdall as recommended, using the recovery image:

lineage-18.1-20210321-UNOFFICIAL-star2lte-recovery.img

It was loaded very quick to the phone completely (loading bar).

But even after 10 minutes waiting, I got no display report, that the flashing process is finished. Instead, the display showed the following lines (only the first five lines):

ODIN MODE

DOWNLOAD SPEED: FAST

PRODUCT NAME: SM-G965F

CURRENT BINARY: Custom (0x4)

KG STATE: Checking

....,

After rebooting, I got a distorted display and with the help of a magnifying glass I could read the message, that the software did not fit the check. I assume, that Samsung Knox did prevent to start up the phone with LineageOS. But I have bought the phone as a used device and so we don't have the 7 days limit for new devices.

After about 10 minutes, the phone rebooted automatically in the Samsung original software. I am lucky, that I had not bricked the phone.

But how should I proceed now, to flash LOS 18 on it? And I fear now, that I am next time not so lucky and really would brick my phone!

Any idea what I did wrong?
[Samsung Galaxy S9 & S9+ Cross Device Development] Confuserix:
Sorry to say, that my S9+ is broken in a strange way: While I tried to set it up with the original Samsung stock firmware, which seemed to work at first, I got a message on the display, that Samsung wanted to install an update, dated from April 1st.

I made the mistake, to agree to that update. After it has been installed, the phone rebooted automatically and it showed up a very distorted display with some dim green lines at the top of the display. No error messages did show up.

While I was writing this text, suddenly the phone rebooted again and showed a regular screen from stock ROM and showing a message, that the apps would be optimized. The progress bar was creeping slowly. When it finished at 100%, the regular main screen showed up and now the phone seems to work regularily.

But I am sure now, that I will run into problems again, as soon as I reboot again. And this probably will prevent me from further trying to flash my S9+ with LineageOS.

What should I do????
[Samsung Galaxy S9 & S9+ Cross Device Development] seandpa:
Is it possible to activate signature spoofing to use microG on this version of lineage 18.1? Sorry if question has been asked already!
[Samsung Galaxy S9 & S9+ Cross Device Development] Confuserix:
Concerning my two requests here:

I have found the reason for my problems: I thought, my S9+ would have been rooted, because OEM-unlock would tell me. Instead it is still unrooted, because VaultKeeper and Knox are preventing it.

I have found some advice here:

How to Unlock Bootloader on any Samsung Device [New VaultKeeper Method]

In this guide, we will sho you how to unlock the bootloader on any Samsung device, keeping in mind the new VaultKeeper mechanism.

www.droidwin.com

But they tell, that you have to enter the DownloadMode by pressing volume-down + power + bixby. And then you get a screen, offering three options. The second one should be available by pressing the volume up button some seconds in order to start the root process.

But on my screen, I do not have this option! And I do not know, how this option can be gone. You can see it on my two Screenshots. On the second screen, it is remarkable, that in the fifth line is showing up: KG STATE : Checking

And Warranty Void: 1 (0x0000) is set. In spite, the Current Binary is Samsung Official.

So what can I do, to get rid of the problems and get real root? I am on Linux and don't have access to Windows / Odin.
[Samsung Galaxy S9 & S9+ Cross Device Development] kelmer_cunha:
Hi there.

It will works on Exynos version?

Can I use Gcam?

Thanks
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
Yes & yes (at least a port)
[Samsung Galaxy S9 & S9+ Cross Device Development] kelmer_cunha:
Thank you so much.

Best regards.
[Samsung Galaxy S9 & S9+ Cross Device Development] roizcorp2:
when watching full screen youtube videos on firefox the bottom edge is cut while i get a substantial black edge on top. Anyone has it as well? ( i do not wish to use youtube app)
[Samsung Galaxy S9 & S9+ Cross Device Development] owenjm:
Not on Firefox Nightly -- all displaying as it should.