yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] ej2095:
Currently using Alexis Rom 2.2, can i just clear in TWRP and install this? Looking to degoogle my phone as much as i can
[Samsung Galaxy S9 & S9+ Cross Device Development] davitox87:
Thank you!
[Samsung Galaxy S9 & S9+ Cross Device Development] Callumpy:
Just done this 10 mins ago and it worked:

1. Boot into Android.

2. Activate Developer options (5 press on build number).

3. Turn of automatic system updates in Developer Options.

4. Go to time settings and deactivate Automatic Time.

5. Manually revert your date back over 7 days.

6. Search for a Software update, but DON'T install update (hit Pause).

8. Reboot your device.

9. Go into the time settings and reactivate Automatic Time

10. Search again for software update, don't install again.

11. Go to Developer Options.

12. Deactivate OEM Unlock and then Re-activate it

13. IMPORTANT: Your phone will reboot after activating OEM unlock, hold [Vol Down] + [Bixby] + [Power] as soon as it goes off to avoid booting into Android and setting the RMM again.

14. Flash TWRP from Odin and press [Vol Up] + [Bixby] + [Power] on the Download screen to boot into TWRP.
[Samsung Galaxy S9 & S9+ Cross Device Development] davitox87:
Anyone get OK google to work? I have nikgapps omni installed and I can't get it to work. I can toggle it and train the voice but when I back our its deactivated again...

I haven't flashed anything in over a good year or longer so I'm kinda out of the loop. Last I knew opengapps pico didn't work with OK google, but maybe its something else.

Thank you,

David
[Samsung Galaxy S9 & S9+ Cross Device Development] sarius02:
At first I also had problems activating it, but I couldn't even toggle and train (with NikGapps core or basic).

For me it started working, when I installed their "Google Vevlet" Addon. Maybe the latter could help you too?
[Samsung Galaxy S9 & S9+ Cross Device Development] davitox87:
Hey thank you for your suggestion. I tried it but did not have any luck. I don't know what else to do but I guess for now it's fine since I have everything else setup. Thanks again!
[Samsung Galaxy S9 & S9+ Cross Device Development] testerS4:
Thank you for this wonderful Rome.

The extended restart menu, which is no longer available in the developer tools, where can I find it? You write in the power settings. How is the path I couldn't find it yet.

(sorry for Engl ... I use translators)

Device: G960F (starlte)

LOS 17.1/18.1
[Samsung Galaxy S9 & S9+ Cross Device Development] testerS4:
That should work. But before that it is better to make a backup of ARom. In the event of a crash, you will get a functioning ROM again. I switch back and forth between three Roms to try it out. Unthinkable without TWRP.

(sorry for Engl ... I use translators)

Device: G960F (starlte)
[Samsung Galaxy S9 & S9+ Cross Device Development] testerS4:
@update 20210114

Today update was offered via OTA.

However, the installation ends in the boot loop of the LOS logo.

After about 1 minute, TWRP starts automatically.

However, I have already tinkered a lot with the system and installed EdXposed. Don't know if that might disturb the update?

(sorry for Engl ... I use translators)

Device: G960F (starlte)

Magisk 21.1 / EdXposed enabled
[Samsung Galaxy S9 & S9+ Cross Device Development] sarius02:
https://xdaforums.com/t/rom-s9-s9-unofficial-lineageos-18-1-23-12-2020.4203777/post-84263363

Maybe the same problem I had with the update before?
[Samsung Galaxy S9 & S9+ Cross Device Development] testerS4:
Can you please explain the procedure to me in more detail? I'm kind of on the line right now. In any case, I get back to my build from 20210110 at any time through a backup.
[Samsung Galaxy S9 & S9+ Cross Device Development] sarius02:
The procedure only applies if you use NikGapps. They screwed up their last build in December 2020 as @Synt4x.93 pointed out.

So if you use NikGapps, probably your best bet is to download the mentioned release (14/12/2020) from the link below and just dirty flash it in TWRP. This fixed a similar problem for me.

NikGapps - Browse /Releases at SourceForge.net

A Custom Google Apps Package that Suits Everyone Needs!

sourceforge.net
[Samsung Galaxy S9 & S9+ Cross Device Development] TarekElsakka:
Does screen mirroring work on this build?

I usually use Smart View to mirror my phone to my car screen (BMW iDrive), but are there good alternative apps since proprietary Samsung apps won't work?

Thanks a lot!
[Samsung Galaxy S9 & S9+ Cross Device Development] testerS4:
Yes, I thought so. Yesterday I just couldn't find version 20201214. during the day the oldest was from 20201218. I tried this one, but also the boot loop there. Now when I'm back on the PC, I'll look for the link to 20201214. Thank you first
[Samsung Galaxy S9 & S9+ Cross Device Development] akmoy92:
Works VoLte and VoWifi?
[Samsung Galaxy S9 & S9+ Cross Device Development] sarius02:
As far as I know, they both don't work and probably won't ever work on anything that is not based on One UI due to Samsung using a proprietary implementation which can not easily be ported to AOSP.
[Samsung Galaxy S9 & S9+ Cross Device Development] TarekElsakka:
Thanks for this incredibly fast ROM. YouTube Vanced isn't working, however, as it says "YouTube won't run without Google Play services, which are not supported by your device" and I don't know how to fix this. I used "NikGapps-core-arm64-11-20201214-signed.zip", should I try the full version instead?

EDIT: I installed the "stock" gapps and that didn't help. I then updated the YouTube app from PlayStore and now it works. Does that mean Vanced isn't compatible with this ROM? Thanks!
[Samsung Galaxy S9 & S9+ Cross Device Development] sarius02:
Hm, I have been using the most recent (non-root) version of both YouTube Vanced and YouTube Vanced Music sice I installed the ROM in September. Never had any issues with it (although I couldn't install the root version).

So to answer your question:

This ROM is definitely compatible with YouTube Vanced and vice versa.

I used NikGapps core and basic, both worked well. (But as YouTube Vanced comes with it's own microg service, it shouldn't depend on Gapps in any way.)

Also I never had the stock YouTube App installed. (Also disabled it when I used Vanced in stock ROM.)

Did you tried installing YouTube Vanced as part of NikGapps or with the official Vanced Manager?

I never tried installation via NikGapps but the Manager worked just fine for me.

Hope you can fix your problem! (Edit: didn't see it's already running after YouTube update from Playstore🙈 anyway..)

Best regards!
[Samsung Galaxy S9 & S9+ Cross Device Development] testerS4:
Thanks for the tip with the NikGapps. That fixed my OS.
[Samsung Galaxy S9 & S9+ Cross Device Development] detlev24:
Thank you @Synt4x.93! I'm currently giving build 14-01-2021 a try.

Does anybody encounter issues with connecting to hidden (SSID) Wi-Fi networks? I saved a few, enabled auto-connect but the phone cannot find those networks. On the other hand, Wi-Fi networks that transmit their SSID do work. // Edit: I found my mistake! There's a setting "Hidden network -> Yes", which needs to be applied and apparently cannot be changed on previously saved connections. 😅

I'm currently using this gallery app, as I found some files to appear pixelated while editing in standard AOSP gallery.
[Samsung Galaxy S9 & S9+ Cross Device Development] leobassin:
Hi @Callumpy, thanks for the tip, which is really appreciated. I did try that, many, many times. It just doesn't work : RMM stuburnly stays to Prenormal while OEM is activate in the Developer Options, no matter what I do.

I as replied today to @YAOHER, I don't think we'll ever succeed, from what I have been told by Chimera themselves. They said that sometime in June 2020, as part of their latest Android 10 update, Samsung locked entirely RMM, for good, and there's no way to disable it. From my knowledge on the subject (which is pretty limited), I don't think it is possible if your device is running Android 10 past June 2020. I'd love someone to confirm that, but no one has so far, and it's not because of lack ot trying...

What I did is I returned my Samsung S9 Plus to the reseller, handed him some money and got a brand new device with stock Android 8.0. I then did the 7-day wait so OEM could be enabled, which worked (finally!!!), then installed TWRP, then Lineage 15.1 (but I had to install VENDOR-27_ARI9.zip before that, because it wanted Android 8.1, and not 8.0) + Magisk + DM-Verify + GAPS (pico), then it booted on Lineage 15.1 like a charm. I still can't believe it's working...

I am now going to upgrade to LineageOS 16.0, then 17.1, then 18 if that's available. Let's cross fingers!
[Samsung Galaxy S9 & S9+ Cross Device Development] Gueste4555:
Bonjour je voudrais savoir si la rom est compatible avec le chargement sans fil? Je pense que oui, mais j'aimerais que quelqu'un me le confirme parce que j'ai un doute. (désolé pour mon mauvais anglais, j'utilise un traducteur). Cordialement.

Translation: Hello I would like to know if the rom is compatible with wireless charging? I think so, but I would like someone to confirm it to me because I have a doubt. (sorry for my bad english, i use a translator). Cordially.
[Samsung Galaxy S9 & S9+ Cross Device Development] Synt4x.93:
Yes it is compatible with fast/slow wireless charging
[Samsung Galaxy S9 & S9+ Cross Device Development] Synt4x.93:
For 17.1/18.1 you need Q bootloader and vendor, I've shared them in the telegram group so just flash those 2 and the rom :) official/unofficial
[Samsung Galaxy S9 & S9+ Cross Device Development] Gueste4555:
bonjour et merci pour votre réponse j'ai deux dernières questions pour vous: 1. si je mets à jour mon twrp actuel et le met à jour vers la dernière version actuelle et que je mets à jour lineageos via les paramètres , est ce que le faitd'avoir mise à jour twrp avant cela posera t-il problème? 2. La rom démarre-t-elle sans problème? (Désolé pour mon mauvais anglais, j'utilise un traducteur). Cordialement

Translation: hello and thanks for your reply i have two last questions for you: 1. if i update my current twrp and update it to the latest current version and i update lineageos through settings, will the will having updated twrp before this be a problem? 2. Does the rom start up without problem? (Sorry for my poor English, I am using a translator). cordially
[Samsung Galaxy S9 & S9+ Cross Device Development] LucasBR.:
Thank you very much for the rom, for dedicating your time to develop this rom, it is wonderful. I wanted to report a bug that is happening, when I record a video using the standard camera app the video does not appear in the gallery, only after a long period of time the video appears in the gallery, it did not happen when I was using the rom a little time, it started to happen after the last updates, I don’t know if it’s just happening to me, I apologize if it’s my ignorance I don’t know, sorry for the translator, and thanks again for the rom.
[Samsung Galaxy S9 & S9+ Cross Device Development] sarius02:
Hmm, this problem is quite strange. I just tried it and did not experience any delay. I'm on the latest update and use nearly the whole time since it was published. But what I noticed are changes in the camera app between the last couple of updates. So maybe this is a problem of the lineageos team currently adapting snap, after all the source code of lineageos 18 is not yet officially released as far as I'm concerned.
[Samsung Galaxy S9 & S9+ Cross Device Development] sarius02:
Hi together.

I'm experiencing strange behavior with the spell checker.

My daily driver keyboard is Gboard (downloaded from PlayStore, not installed as Gapps addon). The configured system languages are 1. English, 2. German although I'm usually writing in German.

When using the AOSP spell checker, every German word I write gets marked as false which is actually pretty annoying (spell checker is configured to use all system languages). My solution to this was to change the spell checker to the one from Gboard which is working fine.

But the actual problem for me is that the spell checker resets to AOSP spell checker after a couple of hours. I just wanted to ask if anyone of you is experiencing similar issues.

I suppose that it is a problem within the lineageos source code that @Synt4x.93 can't do anything against, but maybe somebody knows how to report this to the lineage team so they can fix it in their code base?

Best regards!
[Samsung Galaxy S9 & S9+ Cross Device Development] sinkoo1979:
Did you set gboard as default keyboard? You can always disable AOSP keyboard
[Samsung Galaxy S9 & S9+ Cross Device Development] sarius02:
Yes, Gboard is set as the default keyboard. I'm pretty sure that I already tried disabling AOSP keyboard, but I will try this again. (But even if AOSP keyboard is disabled, the AOSP spell checker remains active.)
[Samsung Galaxy S9 & S9+ Cross Device Development] rvk123:
Hey Synt4x.93, (or everybody else, who can help me)

I just tried to flash "lineage-18.1-20210131-UNOFFICIAL-starlte" I found in the Telegram Channel today.

What I did:

- Run Odin as admin

- Flash twrp-3.5.0_9-1-starlte.img

- Wipe Data

- Install Lineage-18

- Install G960FXXU9ETF5_vendor image I found in the Telegram Channel

- Install BL_G960FXXU9ETF5 Bootloader I found in the Telegram Channel

- Install Magisk-v21.4

- Install NikGapps-stock-arm64-11-20210130-signed

The Lineage OS starts after this just fine, but still I have a problem:

My Sim Card is not detected.

I can remove it, rejoin it etc. but still - no success.

I went back to Stock Rom - no problem with the Sim Card.Sim Card is working in Stock Rom without any trouble. But everytime I install the OS, Cim Card not detected.

I don't know where I was taking the wrong way. Is anybody here, who can explain my mistake?

Thank you in advance
[Samsung Galaxy S9 & S9+ Cross Device Development] orgler:
If you revert to the stock Rom and then go back lineageos do you always flash vendor and bootloader image? That should be fine if you're coming from an up to date and working stock Rom, shouldn't it? I never do it, though I'm personally on crdroid 7.2 Rom and since I'm using it as a daily driver I don't want to give this latest lineageos Rom a try currently.
[Samsung Galaxy S9 & S9+ Cross Device Development] rvk123:
If I don't flash vendor and bootloader, the OS didn't start at all ... so yes, I do flash like I described in my post every time. (Or) I don't get, what is wrong in doing so.
[Samsung Galaxy S9 & S9+ Cross Device Development] akmoy92:
How can i find changelog?
[Samsung Galaxy S9 & S9+ Cross Device Development] sarius02:
Well, my advise would be to first flash the latest (entire) stock ROM available in your region. When I switched from stock to lineage back in December, I was on the current DBT version of that time. Didn't flash any additional bootloader files so alike.

Then try going to TWRP and carefully install all the ROM stuff (if you have time maybe lineage only for the moment without root, etc) and try booting it up. Do not flash any files from stock afterwards, as those may alter things set by the custom OS.

If TWRP says "no OS installed" at reboot, just ignore it and boot to system anyway.

Also, if you have one, you could try to restore an EFS backup, as this can also mess with SIM detection.

Anyway it's kind of strange that you've got this problem. I'm also on Jan 31th build and my cellular network is working just fine. (Although I updateded through OTA.)

So I would suppose that it's either a problem of your hardware or installation procedure.
[Samsung Galaxy S9 & S9+ Cross Device Development] sinkoo1979:
Don't flash vendor or bootloader. The stock rom vendor and bootloader should be enough for you to flash Lineage OS. And flash nikgapps first before magisk.
[Samsung Galaxy S9 & S9+ Cross Device Development] pumori:
I know it's not recommended, but could it work dirty flashing from 17.1 OFFICIAL?

By flashing gaaps and magisk right before rebooting.

Honestly I'm a bit lazy reinstalling the whole stuff ;-)
[Samsung Galaxy S9 & S9+ Cross Device Development] sarius02:
I mean it could.. best way to know is trying it out, can't happen more than a soft brick so you eventually have to reflash anything anyway. But even if it works, please do a clean flash before filing any bugreports for the ROM you dirty flashed 😉
[Samsung Galaxy S9 & S9+ Cross Device Development] gfavre:
Hello, I am currently under lineage OS 17.1 which only miss two things for me : ANT+ and FM Radio.

Does any of those two works in 18.1 ?

Thank you very much.
[Samsung Galaxy S9 & S9+ Cross Device Development] leobassin:
Hi @Synt4x.93. I'm defintely interested in trying this. Could you tell me when you posted it on Telegram or where to find the info? I've checked the group around the date you posted this but was unable to find it.
[Samsung Galaxy S9 & S9+ Cross Device Development] pumori:
Let's talk in images: We have a Ferrari but no keys for it...

Means: ANT+, FM, VoLTE, Wifi-Calling,... All these techniques are integrated, but SAMSUNG won't give us (AOSP) these keys :-(
[Samsung Galaxy S9 & S9+ Cross Device Development] gfavre:
Oh, sad new. Then I guess it's not only Iris scanner that have to go to the "BROKEN" list.

Off topic here : does this also mean ANT+ and FM radio will never work under 17.x or it could as it's not AOSP ?

Thank you very much for your answer.
[Samsung Galaxy S9 & S9+ Cross Device Development] oxıgən:
ANT+ does work? FM Radio will never work because our SOC doesn't have it. simple as that. And you can thank samsung for not providing VOLTE. And that's for any ROM.
[Samsung Galaxy S9 & S9+ Cross Device Development] skvalex:
There are couple problems I noticed:

- After 2 hours setting up all the apps I use, I decided to encrypt the phone - it failed (phone rebooted to recovery every time), so I had to format /data in TWRP and start again. This time I tried to encrypt the phone just after I could open Settings after initial setup - it worked.

- I can't use speaker mode in Telegram anymore as the callers hears loud echo of themselves. I guess it applies to other VoIP apps too, but I have not tested.
[Samsung Galaxy S9 & S9+ Cross Device Development] Tiago Saraiva:
ROM very stable to use. Good work.
[Samsung Galaxy S9 & S9+ Cross Device Development] Tiago Saraiva:
The Godlike Kernel is the same from the LOS 18 or there is any difference?
[Samsung Galaxy S9 & S9+ Cross Device Development] gfavre:
I haven't updated to 18 so I don't know if ANT+ works under it (but it doesn't under 17.1).

FM Radio might be only for US : https://www.androidpolice.com/2018/...radio-us-unlocked-galaxy-s9-s9-latest-update/
[Samsung Galaxy S9 & S9+ Cross Device Development] kevin#34:
is this version working on S9 International F version with Exynos 9810?

thanks
[Samsung Galaxy S9 & S9+ Cross Device Development] jomann:
I don't see the models listed explicitly, but the downloads cover crownlte, starlte, and star2lte which are only the F, F/DS and N variants of the Note 9 (SM-N960x), S9 (SM-G960x), and S9+ (SM-G965x).

I have the S9, N variant (SM-G960N), and it seems to work fine EXCEPT for wifi, but I don't think others are having that problem. See post #111 above.
[Samsung Galaxy S9 & S9+ Cross Device Development] kevin#34:
thanks mate, mine is SM-960F single sim... so it should work (?)
[Samsung Galaxy S9 & S9+ Cross Device Development] jomann:
Yes, it should, but it isn't official and there are no guaranties. Make backups and understand the process before you start. If there's a problem you'll already know how to revert to what you have now or try something else.
[Samsung Galaxy S9 & S9+ Cross Device Development] kevin#34:
sure, thanks
[Samsung Galaxy S9 & S9+ Cross Device Development] savelbys:
Hello,

Samsung Galaxy S9+ | star2lte here, i dirty flashed through TWRP lineage-18.1-20210131-UNOFFICIAL-star2lte (make a backup before with TWRP for safety!) and it is working. I had the latest official LineageOS 17.1 release before.

The only problem that i have (i had this with 17.1 too, because of that i tried now 18.1) i changed my sim card with a new one - other provider/number etc. it is also recognized (have to put in the PIN), but the mobile data does not work. Under settings there is no telephone number, sim status "not ready" IMEI not written... WLAN is working.

I resetet APN's and manually entered the settings.

There is written "only emergency calls"
[Samsung Galaxy S9 & S9+ Cross Device Development] Abduljalal Ahman:
Any kernel you guys wish to share to have better performance and battery life?
[Samsung Galaxy S9 & S9+ Cross Device Development] Tiago Saraiva:
Try this:

https://xdaforums.com/t/kernel-twrp-tw-g-n96xx-q-los17-white-wolf-kernel-11-11-2020.3866571
[Samsung Galaxy S9 & S9+ Cross Device Development] jomann:
A dirty flash is probably not the best idea when the device is already having issues. Regarding the SIM issue, it sounds like your S9+ may still be SIM locked. In my experience, custom ROMs don't have the code to show this clearly and you will need to reflash the latest Android 10 stock ROM to verify. At the least you will be able to confirm your SIM works on a stock ROM. This will also update other important partitions like VENDOR.
[Samsung Galaxy S9 & S9+ Cross Device Development] jomann:
If it works well on the previous version you may want to revert and confirm the problem is resolved. That can be useful information for the devs.

BTW, nice collection of devices. I have the same: 2 x s5, 2 x s7, and an s9.
[Samsung Galaxy S9 & S9+ Cross Device Development] pumori:
Good news! I will try the dirty flash as well. Did you also dirty flashed Magisk? If yes is SafetyNet check still sucessfull? Want to avoid the painfull process of reinitiating all the banking apps stuff.
[Samsung Galaxy S9 & S9+ Cross Device Development] gfavre:
Does this mean you were able to pass SafetyNet under lineage 17.1 ?

If so, how did you do it ?

Thanks.
[Samsung Galaxy S9 & S9+ Cross Device Development] Koffietijd:
In starting post there is mentioned:

ONEUI2 (10) OR NEWER FIRMWARE

How do I know what version I use? Does this come with stock?

Can someone explain this to me?

I'm using LOS17.1 for a long time now on StarLTE
[Samsung Galaxy S9 & S9+ Cross Device Development] sarius02:
When you're on stock, you see the one UI version in device info right in the software/Android section.

If you haven't used unofficial binaries in a while, it's probably best when you just flash the latest stock just to make sure you are on the current version
[Samsung Galaxy S9 & S9+ Cross Device Development] Koffietijd:
Okay Thank you. I've had given it a try. Just without going back to stock first.

LOS18.1 is running just fine. I installed gcam: ZGCAM_7.4_V1.03359.apk which is working fine too.

Is there a way to get the phone "Google Play protected"?
[Samsung Galaxy S9 & S9+ Cross Device Development] savelbys:
Yes, i dirty flashed Magisk and it works, i don't know if SafetyNet check is working.

@jomann thanks

I will factory reset all now and install the newest stock rom, because my SIM Card is not working with mobile data (had the same problem with 17.1 - new SIM card)

@Koffietijd do you using gapps/micro G? I want to use GCam too, but without gapps/micro G if there is way for it, because i only need gcam from google
[Samsung Galaxy S9 & S9+ Cross Device Development] Koffietijd:
I was wondering, with this rom, will there ever be an update via: Settings - system - updater?

Or is that update reserved for Lineageos stable?
[Samsung Galaxy S9 & S9+ Cross Device Development] Koffietijd:
No problemen at all. :cool::)
[Samsung Galaxy S9 & S9+ Cross Device Development] savelbys:
But now i have the same problem as before, mobile data is not working/SIM Card is not recognized.

Still showing "only emergency calls" no phone number, no IMEI, Sim Status not available, but I have to enter the SIM PIN at restart.

I flashed the newest TWRP through Odin v3 14.4 and i did format data + advanced wipe and did a complete reset and deleted all (system, data, cache, dalvik, internal and sd card - only efs and vendor not) rebooted, flashed rom here, than white wolf kernel, and then magisk. With the stock ROM it was working, i saw the beams too.

What is the issue here?