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

My fingerprint scanner suddenly stopped working

I've changed fingerprint with the props thing for valid safetynet check maybe that's something to do with IT?

If i try to remove old fingerprints but IT delete 2 other 2 wont delete and get grayed out until i reopen fingerprint settings.

When i try use fingerprint on apps IT doesn't do anything and for unlocking it resets lockscreen but wont unlock i included screens

Its dutch but when adding IT instantly says fingerprint registration not complete try again or use another finger

PS: i fixed IT by removing pincode(IT delete fingerprints as well then) set new pincode and added new fingers so i think its a bug in the build)
[Samsung Galaxy S9 & S9+ Cross Device Development] Rebel25:
Thank you Neurotical,

Will this work on the star2lte as well?
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
I only compiled for starlte as I only own an s9.

If you want, when I compile for the next security update in a few days, I can also compile a star2lte for you to try.
[Samsung Galaxy S9 & S9+ Cross Device Development] esko1one:
possibly not related to this rom but ill ask anyway. i built the user version of this for my starlte aka s9 and everything seems to be working except i cant use twrp properly anymore because i cant decrypt my data partition. the password is 100% correct. i tried a few different twrp versions so far but no luck.

it always stop with the msg "E: Decrypt took too long, killing process. Failed to decrypt data."

is this a know issue? i got this phone second hand and quite like it but not being unable to use twrp is kinda annoying. i was going to use it to flash magisk and some other things.

perhaps im missing something?
[Samsung Galaxy S9 & S9+ Cross Device Development] Isovitisgr:
I would test an S9+ version as well if you kindly compile one!
[Samsung Galaxy S9 & S9+ Cross Device Development] Im1Random:
Thanks very much. Extremely fast and works nearly without any problems on my Galaxy S9 :D
[Samsung Galaxy S9 & S9+ Cross Device Development] Rebel25:
I would love to test the star2lte version for you.
[Samsung Galaxy S9 & S9+ Cross Device Development] Tom1369:
I think this is a know issue, which affects all Android versions since Android 9 (?). In fact, I had it on LOS 17.1, IODE 1.2 and LOS 18.1 all of them running Android 10 firmware. I still have the most recent TWRP installed and use it for flashing. But I cannot use TWRP to access (or backup) the encrypted /data partition. :(

Either you prevent encryption of your /data partition at all (by manipulating the fstab of your firmware or by flashing a corresponding image before the data partition is encrypted) or you use a different approach for backups.

Regards

Tom
[Samsung Galaxy S9 & S9+ Cross Device Development] esko1one:
i wasnt aware of that, ty for the explanation.

what happens if i flash magisk before i encrypt my data partition and encrypt it afterwards? will i be able to still use it to flash other zips? by manipulating the fstab, u mean it disables encryption altogether or only for the purpose of twrp?
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
lineage-18.1-20210707-UNOFFICIAL-star2lte:

(June security update)

https://github.com/Geoknyda/OTA/releases/tag/star2lte
[Samsung Galaxy S9 & S9+ Cross Device Development] Rebel25:
Thank you, I'll install, test and give you feedback

EDIT:

So far so good, everything I use seems to work perfectly. Thank you once again for the update.
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
That's amazing! I think I'll start a new thread for Nightlies of the S9/S9+.
[Samsung Galaxy S9 & S9+ Cross Device Development] Khalil777:
Hi, i want to install this on my s9+, i am currently on stock android OneUI 2.5.

I have downloaded all the files i need, my only question is does it matter if i flash the dm-verity file before flashing magisk V23.0?

I will update you on how this ROM performs, i'm very excited, the last phone i flashed was an s7 edge a few years back...hehe
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
[ROM][S9+/S9][UNOFFICIAL][LineageOS 18.1][Weekly]

All credit still goes to Synt4x.93 for the development and hosting of local_manifests that make this possible. I am just starting the thread to make it easier for S9/S9+ owners to find the Weekly builds.

Any help getting the kernel updated would be greatly appreciated! I got a version uploaded there with Synt4x's Lineage-18.1 branch of the kernel, which is version 4.9.218, but I don't know how to further upgrade it. I'm sure the community would appreciate your help in this regard and your name will certainly go on the list of contributors!
[Samsung Galaxy S9 & S9+ Cross Device Development] Khalil777:
Hi can you maybe assist me on how you did your installation? i was on stock OneUI 2.5, i tried flashing the star2lte of los 18.1 and NikkGapps with magisk V23.0 and everything installed successfully, when i then rebooted into system it went straight into download mode and just stays there all the time.

edit: managed to get it working, formatting was the solution thanks.

BTW Loving this rom! been using it all day for 2 days and have found NO issues. Thanks a lot for this ROM :)
[Samsung Galaxy S9 & S9+ Cross Device Development] Tom1369:
1) Magisk

Magisk and encryption of the /data partition are independent of each other and do not rule out each other. I am running an S9 with both encrypted /data partition and Magisk. No problems.

2) fstab

When the encryption is disabled, it is disabled for every application, TWRP and all other Apps. This is the reason, why I do not have encryption disabled on my S9. Nevertheless, if you are interested in tweaking the vendor image in order to disable encryption in the fstab, here is the guideline I found somewhere and adapted for my needs:

There also seem to be some no-verity-opt-encrypt images available that are said to reach the same effect when flashed, however, those that I tried on my S9 did not do the trick, while the aforementioned procedure did work (although I do not use it anymore).

Regards

Tom
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Can someone please help me get started on updating kernels?

The current kernel progression for this build is 4.9.118 -> 4.9.218.

I would greatly appreciate

any

help pointing me in the right direction to continue updating the kernel. If possible I would prefer using the github web-based repos (like the links shared above) and simply updating the kernel branch in my local_manifests/roomservice.xml to the most recent branch for merging with Lineage framework during the repo force sync. Can I do this by merging some official Linux kernel like 4.9.y with a new branch in my github repo? Can I pick and choose which changes are made?

Thanks in advance to anyone who can give me some advice!
[Samsung Galaxy S9 & S9+ Cross Device Development] esko1one:
thank you for the in-depth explanation.

i tried encrypting my phone with magisk on it and had some funky behaviour. the phone was constantly restarting every few minutes. might have been a magisk module though, but i lost track and didnt bother with it anymore, as i was already building a new build with with signature spoofing to use with microg.

so if i understood you right, i only loose the ability to use twrp properly because it cant decrypt the data partition. everything else should work as expected. that should be fine since i can use magisk to flash zips.
[Samsung Galaxy S9 & S9+ Cross Device Development] esko1one:
from the github you linked:

just a disclaimer, i have no idea how this works but i assume this should get you started?
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Thanks for the info! I already learned a little bit about updating the kernel locally on my computer from the instructions you linked to!

I tried downloading the 4.9.218 kernel but it only downloads as a zip file and has the same hierarchy as shown in the online github repo; there's no option I can see that allows me to download it as a tarball per the instructions :(

What would seem easier, if at all possible, would be being able to compare 4.9.218 directly to a newer kernel using the online web-based github repos, cherry-picking the updates, and merging them into a new branch. Then I would update my local_manifests/roomservice.xml to point the kernel project to the new branch.

So I guess I am looking for:

1) How to compare and merge web-based github repos, and

2) An appropriate kernel to cherry-pick updates from and then merge into a new branch of 4.9.218

I found this kernel, which seems pretty active and up-to-date. Maybe it's the kernel I am looking for?
[Samsung Galaxy S9 & S9+ Cross Device Development] Tom1369:
Correct
[Samsung Galaxy S9 & S9+ Cross Device Development] king1990:
The easiest way to upstream the kernel is to cherry pick the changes.

Go to your kernel dir and fetch https://github.com/aosp-mirror/kernel_common/tree/android-4.9-q

Then start cherry picking from the 218 up to newer version.

Remember you will get conflicts and will require some knowledge with coding to fix them correctly.
[Samsung Galaxy S9 & S9+ Cross Device Development] Galaxy9plus-support:
Is this the 'debug' version like synt4x, or the 'eng' or 'user' build going fwd?

And dont forget the crownlte build too as per the roomservice.xml from synt4x
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Yes, it is the userdebug version. I'll also run the crownlte in addition to starlte and star2lte on the next upload. Thanks!
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
So is the only way to do this by using my Ubuntu terminal on my local desktop? Like downloading the updated kernel tarball, comparing it to my current one, cherry picking the changes and then uploading the new one to my repo?

Or can the comparison and cherry pick between the two be done using Github's website repo explorer?
[Samsung Galaxy S9 & S9+ Cross Device Development] king1990:
Yes, it can be done remotely using git.

Take a look into how to use git, learn few commands and you will be ready
[Samsung Galaxy S9 & S9+ Cross Device Development] Rebel25:
I had TWRP and a custom Kernel on OneUI 2.5. I formatted System, Data & Cache. Then installed everything.

The other way is the try out the way that LineageOS says. They currently do not have a 18.1 for star2lte but the commands are basically the same across devices.
[Samsung Galaxy S9 & S9+ Cross Device Development] espacesimo1:
hi,

thank you for this rom , work perfectly .

i made a video for this rom .
[Samsung Galaxy S9 & S9+ Cross Device Development] Khalil777:
Hi thanks for your help, i got it to work. i think my issue was that i wiped vendor when flashing from stock.

This ROM is Awesome, i'm loving it, been tweaking my phone for 2 days now! haha
[Samsung Galaxy S9 & S9+ Cross Device Development] OpenMinded:
use YouTube Vantage or NewPipe
[Samsung Galaxy S9 & S9+ Cross Device Development] Queeq:
@Neurotical I'm not sure if there are any specifics in kernel build for Android, but for desktop/server systems it's pretty straightforward:

1. git clone from kernel.org (e.g. git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git) and checkout the relevant branch (e.g. linux-4.9.y). The branches are named by version: linux-<major>.<minor>.y (there is literal "y").

2. Then you can run `make help` from the cloned repo that will show you a bunch of options you can use to proceed with the build.

3. If you put kernel config file in there (named as .config), it'll pick it up and you'll have an option to choose how to apply newly introduced options to it (on patch releases there are usually none or they're trivial). E.g. you can use `make listnewconfig`, `make oldconfig`

4. Build it. For Debian-based systems I used this command: `make -j8 KDEB_PKGVERSION=4.14.1.queeq deb-pkg` - 8 jobs (coz I had 4 cores with hyper-threading), and package it as .deb with the given version. You'll definitely need some other options, especially as it has to be cross-compiled to different architecture (I never did this).

The above applies to Linux build system. Build dependencies are make, gcc, libssl-dev and dpkg-dev (last one you wouldn't need). There could be some other dependencies needed for cross-compilation.

P.S. Also cherry-picking tens or possibly hundreds of commits one by one is very annoying task. If you want to merge the upstream you can try to simply `git merge`, but there could be conflicts. I've no idea how complicated it may be to resolve them so just try.
[Samsung Galaxy S9 & S9+ Cross Device Development] Galaxy9plus-support:
5th July security update ready on this build if you are compiling your own.

How to check when its available besides going thru the make process and checking

~/android/build/core/version_defaults.mk

once complete for the security update date ?

Also checking the

//source.android.com/security/bulletin

for the monthly date and

https://lineageos.org/blog/

changelog

isnt helpful. How to know what patch is ready to build before I go thru the whole process ???

Need to keep the device patched to the latest at all times to be able to use as a daily for work :P
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
To check for security update version of Lineage 18.1 before building your own: https://github.com/LineageOS/android_build/blob/lineage-18.1/core/version_defaults.mk#L243

There is a build with July security update and an upstreamed kernel here: https://xdaforums.com/t/rom-s9-s9-unofficial-lineageos-18-1-weekly.4302901/

I am upstreaming the kernel daily and building these new builds daily as well.
[Samsung Galaxy S9 & S9+ Cross Device Development] Rupdabe-GalaxyS6EdgePlus:
Thank you very much.

Could you recommend an alternative firmware only for the camera for s9+? Because the camera from lineage is very bad.
[Samsung Galaxy S9 & S9+ Cross Device Development] Galaxy9plus-support:
:LOL: face palm, of course, thnx Neurotical
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
You could try a GCam port like this one:

https://xdaforums.com/t/gcam-exynos-version-from-bsg.4246095/
[Samsung Galaxy S9 & S9+ Cross Device Development] deboopi2:
I'm willing to install a custom rom but I have my doubts for certain applications.

Since I'm running on a S9 plus I have a 2x zoom lens and the galaxy can work with it.

Is there a camera app already installed on lineage or not?

Whatever the case can you install the Samsung camera app and does it work?

Is google camera a good alternative, does it support a 2x zoom?

I also have a galaxy watch and therefore I use Galaxy STore that can install apps directly on the watch, does this store app still work on Lineage or is there an alternative?
[Samsung Galaxy S9 & S9+ Cross Device Development] awaisiqbal:
It have flashed ROM. It is working quite good. I have checked info through diskinfo and found that most of partitions have ext4 format Does it support f2fs system. If it is then can it be converted from ext4 to f2fs ?
[Samsung Galaxy S9 & S9+ Cross Device Development] OpenMinded:
would you mind specifying exactly what you did to build this? I am using the lineage for microg docker based build and it currently succesfully builds 17.1. I would like to build 18.1 with OTA and sign it myself and provide the OTA like you do.

There are fragments of info across this thread, it would be great if you or anyone else can put them together.

Thanks!
[Samsung Galaxy S9 & S9+ Cross Device Development] Linusrg1:
Thx for this ROM especially the kernel you made for it l. I'm sure your lineage os build is great but I haven't tested it as I don't use lineage. But it has allowed me to make quite a few roms that are based off of this ROM's kernel. Thanks!
[Samsung Galaxy S9 & S9+ Cross Device Development] Davy-Jones:
Hey,

anyone also got problems with:

- flickering screen while scrolling

- artefacts / blocks in dark pictures

- problem with GPS-positioning

- slow mobile data

- device get's hot sometimes

- very high battery use sometimes, till restart

Thank you.
[Samsung Galaxy S9 & S9+ Cross Device Development] Im1Random:
I never had any of this problems with my Galaxy S9 (only with HDMI output my TV sometimes flickers when scrolling). Maybe try wiping everything again and do a complete reinstall
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Try updating your baseband modem firmware. It's probably out of date.

https://xdaforums.com/t/rom-s9-s9-unofficial-lineageos-18-1-weekly.4302901/post-85415659
[Samsung Galaxy S9 & S9+ Cross Device Development] Davy-Jones:
Hey Neurotical,

thank you. I did, but without a change. :(

Strange.
[Samsung Galaxy S9 & S9+ Cross Device Development] dreas74:
Hi @ElPakoTech

I have seen you have updated you build on 03.08.

Can you provide a changelog or something?

That would be good to know wether a update is necessary or not.

Thanks

dreas
[Samsung Galaxy S9 & S9+ Cross Device Development] ElPakoTech:
Hi,

I did the last build because I noticed a very annoying bug on the previous one: the keyboard doesn't respond well, and some input were ignored. So for example, when you're typing a text, some letters/word were missing and you had to be very slow to avoid any lost letters. Same issue when entering a code to unlock the phone for example. Since yesterday on the last build, the problem seams to be solved.

Initially, I wanted to build at least once a month for security patch, but I also like to make some build time to time to keep rom updated from LOS sources when I can (I don't have a precise schedule). So basically, the last build will be the most updated.

There is the full LOS 18.1 changelog here : https://www.lineageoslog.com/18.1

And here the link to the list of merged commit (I excluded devices and kernels changes to match our build): https://review.lineageos.org/q/bran...ndroid_kernel+-repos:LineageOS/android_device, so you can check all changes between two dates.

Changelog is good point, I will see what I can do. Maybe first, I think i'll just add "security patch version..." in description when it get updated.

About bugs, I notice also a keyboard flikering when I use chrome (and only chrome). I also want to update baseband as suggested by Neurotical.
[Samsung Galaxy S9 & S9+ Cross Device Development] Davy-Jones:
I'll try to flash 18.1 once again. The problems are really to big.

Could sb kindly tell, what's the easiest way to do a new 18.1 flash on the existing 18.1? I'm not into ADB, I'd prefer a way using TWRP only. Thank you.
[Samsung Galaxy S9 & S9+ Cross Device Development] Im1Random:
You dont need ADB to do a reinstall only a usb stick or sd card to store the zip files. In TWRP wipe system, cache and dalvik. Then install the lineageos zip (and other zips like magisk if needed) again. Of course making a backup of the data partition isn't a bad idea in case something goes wrong
[Samsung Galaxy S9 & S9+ Cross Device Development] Davy-Jones:
Hey, thank you. I did this, but - no change. Problems still the same. Guess I will flash 17.1 again.
[Samsung Galaxy S9 & S9+ Cross Device Development] Davy-Jones:
Hey Guys,

just one more request: To reinstall 17.1 (while using 18.1) - can I also wipe system, dalvik and cache and flash 17.1 again, or Do I have to do a Full wipe /factory reset?

Thank you.
[Samsung Galaxy S9 & S9+ Cross Device Development] ElPakoTech:
I am not sure about the issues you have installing 18.1 as the build available are pretty stable.

I will recommend you to use lineage recovery instead of TWRP and wipe system/cache and dalvik again regardless of installing LOS 17.1 or LOS 18.1.
[Samsung Galaxy S9 & S9+ Cross Device Development] Davy-Jones:
Hey Guys,

I eventually gave it a last try with 18.1 after doing a factory reset - and - it worked! The noticed problems are gone - by now.

Great. Thank you, for your support.
[Samsung Galaxy S9 & S9+ Cross Device Development] BlackVoltage:
Hi,

my Samsung Galaxy S9 runs with Lineage 17.1 (lineage recovery) ... seems there are no further updates (till january 2021 I got one about every 2 Weeks).

Therefore (and coz of newer and so on) I would like to use Lineage 18.1

A few Questions regarding that:

1. )Is that ok - or would I have the same or even more (update) problems? Coz 18.1 seems not official for S9?

2.) How to make a backup (like with clockworkmod tool I uses years ago)? I want to restore the backup after installing clean 18.1

3.) What else should I know (made a lot of custom rom installations but mostly years ago on my htc desire)

Thank you very much in advance!

Best regards

BlackVoltage

Edit: titanium backup - was One of my earlier tools. Would it work to make a backup within 17.1 and recover after updating to 18.1?

Will your 18.1 here work as good as formerly oficial 17.1 ?
[Samsung Galaxy S9 & S9+ Cross Device Development] Davy-Jones:
Hey,

there are no updates for S9 17.1 since the day you named, because the support came to an end. 18.1 is an unofficial ROM, so there are no updates also. (I think?)

Greetings
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
The 18.1 Unofficial is currently maintained in this thread: https://xdaforums.com/t/rom-s9-s9-unofficial-lineageos-18-1-weekly.4302901/
[Samsung Galaxy S9 & S9+ Cross Device Development] Davy-Jones:
Hey,

thank you very much for this information. I read this Thread, but - please apologize - I'm not into the Custom ROM world very good. Just trying to understand, how things work.

I installed your Version from march, I think. What's the easiest way, to update it to the latest version from August? I read sth in the thread, but I don't understand it, really. Apologizes.

Can I save the zip on my phone and just flash it over the old 18.1 from march? Or can I wipe system, data + cache and flash the latest version after that in TWRP?

Thank you so much for help.
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
You can dirty flash the latest unofficial 18.1 over the March 18.1 from this thread :)
[Samsung Galaxy S9 & S9+ Cross Device Development] Davy-Jones:
I tried and it worked very well. Thank you so much for sharing the OS and your support.

Are there any disadvantages, doing dirty flashs every 3-4 weeks, when wiping the cache after flashing?
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
Great! There are no disadvantages of dirty flashing if you are using the same build base. To make it easier all you have to do is use OTA on your phone (Settings -> System -> Advanced -> Updater) and you'll get the most recent build I upload. This includes Kernel updates (security & performance), LOS updates (security & performance), and monthly AOSP security updates.
[Samsung Galaxy S9 & S9+ Cross Device Development] Davy-Jones:
Soo cool. Thank you, again.
[Samsung Galaxy S9 & S9+ Cross Device Development] Davy-Jones:
Aaand - here I go again. Sorry. :-(

This evening there was an Update via OTA and I tried. I downloaded and startet the file, the phone went into TWRP, flashing was good, no problems. The phone startet again and then - bootloop. The LOS logo was shown for about 2-4 min and after that, the phone boot back into TWRP.

I could fix it by wiping dalvik, system and cache und flashed Version 08.08. and Nickgapps and Magisk again.

First try by only flashing Version 08.08. did not work -> still bootloop.

Did I do smth wrong, do I have to prepare sth?

Thank you, Guys.
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
From what I understand, using the recovery file that comes with this build is the best way to get best compatibility. You may have to start fresh with full wipe, install recovery that comes with the weekly, then install ROM. This will only have to be done once because each weekly updates the Recovery (if you choose it to).

There are posts in here or the other thread that get TWRP working, but there are several steps taken to make that work, making using LOS with TWRP cumbersome; especially with encryption.
[Samsung Galaxy S9 & S9+ Cross Device Development] Davy-Jones:
Thank you.

Guess I will flash Updates every 4-6 weeks manually.

Thank's for your support.