yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] medoko:
I know... and im sorry for that. ;)

Im modding my mobile phones since years (since cynanogenmod-times) but did not have seen such a hard way of getting to a functional device.

But with your last post, i think i will have all infos i need to bring my S10 from LOS 17 to LOS17.1

But who knows... Maybe i will come up with some more questions! :angel:

Danke und Grüße nach Frankfurt
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Fernix_:
I too am on ASIG, but with LOS 16. Idk if you're on los 16 or 17, but could you update me on if this worked or not?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] byteXpression:
Danke! ;)

Yes ,the good old Cyanogenmod-Times... All was easier back then.

I guess the phone manufacturer industry wants it to be complicated and raising the bar with every release.

But luckily we are one big global community of 'independent" and "free" developers.

:) No worries. and good luck with your upgrade process...
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] brgroover:
Any way to use Galaxy Weareable App with this build, without build.prop changes?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] dantexaiver:
this work with the Canadian variant G970w
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] dexn:
Yeah, also confused with how bluetooth is marked as "working", especially since it hasn't worked since I've been using this ROM. Can [MENTION=4610599]Ivan_Meler[/MENTION] please look into this? Are we doing something wrong, is there a setting we missed, or is it just simply broken and how can it be fixed. This is becoming quite a problem for me with answering calls.

If someone knows of an equally lite and fast ROM for the G975F with a true "working" section, please inform me so I can try it. I'm almost at the point of giving up on this ROM and going back to stock.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] byteXpression:
Just a thought for a potential workaround (because I don't have or use bluetooth devices and don't have any bluetooth headsets to test with)...

Open your bluetooth settings, find your device, and click the settings icon for that device. You should see some options for the device. If there is something like a "Phone audio" option uncheck this one (and keep "Media audio"). This should potentially redirect incoming phone calls to your normal phone speakers while music, etc. should be streamed via bluetooth.

I assume the problems are with the codecs (some are propriatary).

I guess there is still a bug in the bluetooth-audio-codec selection . Maybe [MENTION=4610599]Ivan_Meler[/MENTION] can look into it and make the selected changes permanent (not reverting back to the default settings all the time).

After that, maybe someone who is more familiar with bluetooth can test with different codecs to mitigate the problems?

What I found out so far is that if you have bluetooth off, you can not change anything in the codec section without reverting back to the standard settings. If you have bluetooth on, you can change it and it stays like it is as long as you are in the developer options, but reverts back to standard if you exit developer options. I wonder how this setting will behave if you have paired a bluetooth device and you change the codec? Can you test it?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] trancinguy:
Hi, I want to reinstall lineage and gapp and Magisk, can I skip all steps and just format twrp, or do I have to: format, multi Disabler, then lineage, then gapp, then Magisk and if I format, is the Sam firmware like modem and stuff deleted?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] byteXpression:
Hi trainguy,

Depends what you want to format and wipe.

Wipe system to remove Android (Lineage)

Wipe/format data to remove your data/files, etc.

Wipe recovery to clear TWRP or Ivan's old recovery from November or STOCK recovery, etc.

If you just want to reinstall LOS, GAPPs and Magisk (without changing your firmware) and you still have a running TWRP in your recovery you simply can wipe system and reflash multidisabler, LOS, GAPPS. No need to reflash boot for Magisk to work (if you have already installed the latest boot image from Ivan).

If you don't have installed Magisk enabled boot.img from Ivan, also flash boot in order to enable Magisk with LOS 17.1.

If you don't have TWRP in your recovery partition also use ODIN to flash TWRP and vbmetadisabler (for TWRP to work again).

Your other stuff like baseband/modem resides in other partitions. So you should be ok as long as you don't wipe/format your complete phone ;)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] d1845825:
Works great on my S10+, thanks Ivan!

I want to encrypt my files but apparently multi-disabler disable this so I looked at #17 but since the source code is available now, does anyone know how to enable encryption with fstab ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] byteXpression:
Yes, simply use the search function in the forum here. I explained it for FDE a couple posts back. See page reference 50, post #515.

Edit the following line in the downloaded fstab.exynos9820 with an editor:

/dev/block/platform/13d60000.ufs/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journ al_checksum,data=ordered,errors=panic wait,check,encryptable,quota,reservedsize=128M,len gth=-20480

to

/dev/block/platform/13d60000.ufs/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journ al_checksum,data=ordered,errors=panic wait,check,encryptable=footer,quota,reservedsize=1 28M,length=-20480

See also the post from flunkyball regarding this topic on how to change the fstab page reference 12, post #111.

But we only looked at FDE (at least I did for now).
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] d1845825:
Thanks. So if Lineage is already installed do I need to reinstall it and do the 4 blocks resizing and then the fstab or can I just edit the fstab.exynos9820 from the Lineage terminal and just reboot without losing my datas?

Also do you know what to select in TWRP backup to have a full backup so if I want to restore the os I wouldn't need to do all the steps again of installing Lineage?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] byteXpression:
You will have to unmound data in TWRP before you can resize it. As you shrinkt it, there is no guarantee that you don't loose data. However, it is only 16 K so the risk should be minimal. But again, there is a risk to it so better backup your data first!

After you have shrunk your data partition to make the 16K available for the encryption keys, you can change your fstab with your favorite editor. After that you can enable encryption via the security settings in LOS.

I don't use TWRP to backup any data, so I can not tell you that. But in order to keep your data you would have to backup the data partition. I use Titanium Backup and restore whatever is needed when I need it. You could also do a nandroid backup which should backup everything.

Here is a reference for you: https://www.xda-developers.com/how-to-backup-android/

PS: If you receive help via the forum it is always good to leave at least a "Thank you" ;)

Most credits should go to [MENTION=4610599]Ivan_Meler[/MENTION] for making this ROM possible!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] 2k4ever:
Thanks for you detailed instructions, byteXpression!

just to make sure: for a non 512 GB device, I simply detract 4 blocks from the current size of /dev/block/sda31, correct?

And is there anything model-specific (S10e in my case) that I have to keep in mind?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] oyashirochama:
Does this work with the 975N model of the S10+, it's ready with all steps up till flashing from twrp.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Ivan_Meler:
new build is up,

- Merged 4BTA8 kernel source

- Merged February security update

- Fixed MTP/USB tethering while ADB is enabled

- Synced with LOS source

This build works with older firmwares along with new G97*FXXU4BTA8 firmware if you are updating from previous build just flash the rom and wipe cache, dalvik cache and if you are using magisk flash new magisk image from same folder where you got rom from and you are ready to go, Also a PSA OpenGapps build from today (20200211) are broken and cause bootloops Build from yesterday works however New opengapps builds might be fixed but if you get bootloops try using older gapps build like this one
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Vardenf:
Did anyone had luck to make Galaxy Wearable work on this ROM?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Ivan_Meler:
you have to replace props containing manufacturer=samsung in odm/etc/build.prop vendor/build.prop and system/build.prop with any value other than Samsung, after that gear app and all of its plugins will work
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] El Dun:
[MENTION=4610599]Ivan_Meler[/MENTION] sorry that I bother you, but can you please add exfat support to your build if it isn't it too much effort?

I really like your rom and thanks for maintaining it, sadly I'm currently using the beyondrom (which is great too, but ... samsung stuff...) because I rely on exfat formatted usb drives.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Vardenf:
Well, did that (changed that particular entries to "lineage") and now phone boots to downloadmode. Did I miss something?

---------- Post added at 12:40 AM ---------- Previous post was at 12:09 AM ----------

Now it works - did fresh install (with full wipe), odm and vendor entries stayed changed, just had to change system entry which went back to samsung. Reboots well this time.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Bunk:
Thanks for your guide. With your help I'm running encrypted LOS now :)

2 remarks:

- Maybe add a link to the vbmeta_disabler.zip (I got mine from the LOS 16 thread: Google Drive link

- After editing the fstab a reboot is needed. Maybe add that specifically, otherwise encrypting will not work and may confuse others.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] byteXpression:
Yes, this is correct. Nothing special between the devices for this to work ;)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ennxo.binzoro:
Thanks for the vbmeta files. I was looking for it all night long...:good:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] byteXpression:
Hello [MENTION=4610599]Ivan_Meler[/MENTION], [MENTION=9350973]All[/MENTION],

are the bluetooth problems also solved with the new release (as some people reported here) - specifically the problems with BT phone calls?

---------- Post added at 11:49 AM ---------- Previous post was at 11:37 AM ----------

Great it worked for you this way, but why did you patch with Magisk so often? This is absolutely not necessary, because all you need is Ivan's boot image (which is already Magisk enabled). So basically your last step #8 is actually doing the whole trick for Magsik Manager to work. ;)

Patching the AF firmware file is only needed if you want to stay with Samsung STOCK rom and STOCK boot and STOCK recovery. But you overwrite those slots with TWRP (in recovery), LOS (in system) and Ivan's boot image (in boot). So next time, you can save you a little bit time ;)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Bunk:
[MENTION=8518487]byteXpression[/MENTION] Not tested bt calling het bit normal calling doesn't work. Starter fine but after a few minuten it got all scrambled.

[MENTION=4610599]Ivan_Meler[/MENTION] Auto brightness doesn't work properly in dark environments. It keeps hunting/changing brightness. Just like los16 did.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] giorgospav:
Hello, i want to ask if there is a way to automatically change to dark mode depending on the time of the day , like it was with styles in Lineageos 16.

thanks in advance
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flunkyball:
Unfortunately I have to report that the bluetooth calling issue is unchanged with the latest release of yesterday.

In addition to that the touch screen seems to have lost some of its responsiveness comparable to the state it was with the initial release.

However, Ivan, keep up the good work; I really appreciate your effort.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Jab_:
Hello, I'm pretty new on the Samsung development scene, but had experience on oneplus/xiaomi respect to flashing. I have a few noob questions, because Samsung flashing seems kind of different.

1- The instructions in #1 post will be the only thing I need if I'm on stock G973FXXS3BSL4? (Lock BL, not root or TWRP) or do I need anything else?

2- How is performance and battery compared to stock rom?

3- I've been reading some coments about having to reboot to recovery instead to reboot normaly. How about that?, should I have to reboot to recovery instead or normal reboot every time I want to reboot the phone?

4- If I got into bootloop (for any reason), can I restore to stock rom with Odin?

5- Is there any video tutorial about flashing this rom?, I couldn't find any on YouTube

Battery life is really annoying for me, so, that's the main reason to flash LineageOS

Sorry for such a noob questions, and thanks in advance. Have a great day =)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] byteXpression:
Hi Jab,

To your questions...

1) Therer are plenty of descriptions here in this forum (just use the search function). But it seems everyone is doing it a bit differently :cyclops: It also depends on which version you are with the firmware and if you need root (Magisk) or not, etc.

See for example post #505 for your reference: https://xdaforums.com/showpost.php?p=81727315&postcount=505

2) Battery seems to be better.

3) As of the Februar versions of LOS17 you don't need to boot via the recovery for Magisk to work. You can simply boot to system (with the Magisk enabled boot images provided by Ivan).

4) Yes, absolutely. You always can go back to ODIN and TWRP and reflash. The downloader mode of Samsung is rock solid. At least I could not mess it up yet :angel:

5) Not to my knowledge. But with the advise here and the search function you will find plenty of information (see also topic 1 above).

Good luck! :cool:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Jab_:
Thanks man, that's was actually very helpful.

I have a couple more questions, tho.

1- Where can i get the vbmeta_disabler.zip?

2- What happens if I don't do the 2 FDE steps?

Thanks again
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Bunk:
1. Here: https://drive.google.com/open?id=1SPbvlDVwoMPtl4xQ7WpUuL5yXhYtI0_z

2. Nothing. Encryption is optional
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] BigSnake353:
Hello. Do you think there is a possibility to repair VoLTE and VoWiFi in the future?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] chong xda:
Any one has a better camera app for this ROM? Any one can port the original Samsung camera for this ROM?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] TheMrM00n:
Join the Telegram link. There, we have an apj of Zcam and a config file for it.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] chong xda:
Where the Tele group is?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] LuiseSarmiento:
Anyone experiencing force close when you open style & wallpapers? It only worked once and now i can't customize anything.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] BigSnake353:
https://xdaforums.com/showpost.php?p=81542269&postcount=390
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] gorgo80:
have a question, do not know if here is any Swedish members here. But we have a banking upp called BankID and also Swish, that we use for the Bank and to transfer money.

Do any know if this works with LOS?

And also payment apps like Netflix etc?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
Probably not working with Magisk (although I cannot be sure since I never used apps like that).
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] TheMrM00n:
My banks (spain) and netflix are working just fibe with magisk
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] medoko:
Im trying to get encryption to work on my S10 (128GB version).

Im curious about where to find the correct place to change the block size (reduce it minus 4 blocks).

This is my result, when i run "e2fsck -f /dev/block/sda31" on my device:

/dev/block/sda31: 15517/7274496 files /2.1% non-contiguous), 923804/29083648 blocks

Which number refers to the blocks: The 923804 or the 29083648 ?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] flunkyball:
29083648 is the total size of your partition in blocks. So in order to make 4 blocks available you need to shrink it from 29083648 to 29083644.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] marzupi:
BSL4 (german vodafone version)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] byteXpression:
Boot Warning Fix for the S10e, S10 and S10+

I have created a Boot Warning Fix for the S10 line to get rid of the annoying "Unlocked Bootloader Warning" message.

It replaces it with the LineageOS Logo (see attachment) and also fixes the red colored "Not running Samsungs Software Warning" message when you boot your device.

The patch will not affect your data or your installed LineageOS as it works on a different partition at boot time (firmware level).

But as always, no warranty is taken and you flash at your own risk!

Please find below the Boot Warning Fix for:

G970F - S10e

G973F - S10

G975F - S10+

Please unzip the corresponding attachment and flash BLF_97XF.tar in the

AP slot

with Odin for this to work. Please have the "Reboot Option" checked in Odin.

Your device will reboot after the patching and should start normally again without any annoying boot warning messages anymore.

PS: The fix can be reverted again by flashing the original Samsung firmware (if you revert it, you only need to reflash the BL slot with the BL firmware).
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] byteXpression:
If interested, I can also make the fix available for S10e or S10plus.

But would like first some feedback for the S10 (if it works for you).

Added the fixes for S10e and S10+ (see posting above).
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Fernix_:
From the screen caps it looks really nice, but maybe you could make some variants changing the colour scheme to black and green instead of green and white so it isn't so bright at night, for example. It could also look cleaner if you removed the xda edition thing
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] medoko:
As one last step to go, i wanted to use encryption (FDE) in my S10...

I follwed byteXpressions guide and succeeded with it

-> see (not only) encryption guide entry #505: https://xdaforums.com/showpost.php?p=81727315&postcount=505

But: When i boot into TWRP, i do not get a dialog to enter my PIN code (i used to encrypt the phone initially) which im sure it should pop up (to decrypt the phone). Therefore, i cannot create a backup (as i do not see any mounted drives/folders).

Any ideas what went wrong?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] byteXpression:
TWRP is not compatible with FDE encryption. You will have to do an "online nandroid backup" or you could use Titanium Backup.

Maybe the devs of TWRP will implement it in the future, but currently TWRP is not able to decrypt FDE data partitions natively.

It may be possible to mount the data partition manually via the Terminal within TWRP (but I haven't looked into it yet).

---------- Post added at 06:39 PM ---------- Previous post was at 06:20 PM ----------

Hi Fermix, sure I could do that, but this screen will only be displayed for about 10 seconds during boot time (so should be no problem during night time ;)). Either you click on the Power Button to continue or it will auto continue after about 10 seconds and boot to System. I used those colors as these are the original LineageOS colors. But a black one would be no problem. as well ;). But again, it is only displayed during boot time (as an overlay to the warning messages coming from Samsung Knox due to an unlocked bootloader).
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Fernix_:
Ah so this only replaces the bootloader unlocked prompt? Not the splash screen with the red text? Still, thanks for taking that feedback into consideration.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] byteXpression:
It replaces the bootloader unlocked promt with the LineageOS bootloader screen and also fixes the red text during boot time. So both error messages are gone ;)

During boot time you will see your normal boot screen (but without the red error text). ;)
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Fernix_:
Cool. Would it be possible to just have the same image, that being the one you made, on both screens? Or maybe even a custom one?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Bunk:
Would love this for the S10e!

---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------

Let me quote myself. Normal calling does work normally so it wasn't an LOS related issue.

[MENTION=4610599]Ivan_Meler[/MENTION] Bluetooth calling is (as mentioned before). Tried calling in my BMW but the other side sounded like Donald Duck, kicked in the balls (really). Unusable.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] dlvdmeer:
Hi,

I just installed this release and for the most part it works.

Pretty cool that you no longer have to boot to recovery to have root access via Magisk.

I did notice a few issues with this release though:

- Magisk works but installing a module (I have tried a couple so far) will show a popup after installation and pressing Reboot with the text "factory reset" and after that it just reboots to the animated logo and stays there forever. So Magisk is only for root access and not to be used with any modules?

Fortunately I have not yet used FDE because I am waiting for everything to be stable and working for me so I was able to recover my system via a TWRP backup

- Double tap to wake up the display. There were some comments that this was working and that people tried it themselves but I can't seem to get this working. I've turned off Settings -> Display -> Advanced -> Lock Screen Display -> Always on

Is there another setting I forgot?

- Netflix is not working. Some people got it working by sideloading it but I downloaded it from Netflix itself (https://help.netflix.com/en/node/57688) but installing this app will show the message "This device is not supported by the app" - What am I missing?

Should I sideload another version? Use a patched version or something?

- I assume the same applies for Disney+ ?

- Updating Magisk from within the manager will create a non bootable system

Thanks

(edit: added some extra text)

---------- Post added at 10:53 PM ---------- Previous post was at 10:45 PM ----------

It would be great to also have this for the S10+. Looks a lot better than those "scary" messages.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Fernix_:
I have a question before installing this. At which point during Ivan's installation guide do we flash the magisk boot img, and using what, ODIN or TWRP?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Keule-Tm:
It should be an img file. You cannot flash img files directly in Odin, afaik (and you shouldn't try). It is the last step, if I remember correctly (but do me a favour and look that up in Ivan's post (and you could do that yourself before asking;)).
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Fernix_:
Well that's what i remember, but I figured it was better safe than sorry. Ivan's post doesn't specify when to flash the image, he just says to flash it to boot slot, hence the confusion with ODIN