yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] ludwig83:
Hey guys! I'm now on 18.1 (of course a clean flash) ....great ROM so far but I have the same problem as on 17.1 ...whenever I lose GSM it does not come back ...I receive the message that SIM Card is missing - service not available (Keine SIM-Karte - Dienst nicht verfügbar) ...someone else with a klteactivexx here with the same experience? Never had a problem with Lineage 16.0 ...hope for someone who can confirm my problem...

https://xdaforums.com/t/official-lineageos-17-1-for-galaxy-s5-klte-variants.4181821/post-84634419
[Samsung Galaxy S 5 Unified Development] x2k13:
@haggertk @curiousrom the journey goes on! 🙂
[Samsung Galaxy S 5 Unified Development] zimral.xda:
Many THX for givin' the good old S5 a continued life again. Will look for food/money for the local animal shelter, our cat comes from there :)
[Samsung Galaxy S 5 Unified Development] vlad3647:
Beautiful
[Samsung Galaxy S 5 Unified Development] bersem:
@haggertk thank you for your amazing work !! One question: Why arent navigation gestures enabled by default ?? Have to edit build.prop file to get it..

Regards !
[Samsung Galaxy S 5 Unified Development] haggertk:
The Galaxy S5 has physical keys, in particular, the home key. Since this key cannot be "hidden", our standards are that key disabler must not be able to be activated through normal user interaction.
[Samsung Galaxy S 5 Unified Development] Tenaya43:
First, I want to thank Haggertk and LineageOS for keeping the Galaxy S5 alive.

DISCLAIMER: I don’t know as much as I’d like about what’s behind the Android curtain. I’m especially ignorant about the Android file system, but I’m learning.

We’re in the process of switching from older Galaxy S2 Skyrockets (we keep our phones waaaaay too long) to SM‑G900Ts (newer, but still pretty old). For the past month or so, all three of our SM-G900Ts have been running unofficial 18.1 (20201225) with NikGapps Pico. This morning, I downloaded LineageOS 18.1-20210425-nightly-klte-signed and installed it on two of our SM-G900Ts via TWRP (which I had previously installed via ODIN).

We have two problems we didn’t have before:

In 20210425, the 18.1 camera app doesn’t work. It tries to open (quick flash of a black background), then immediately stops. Trying the camera app a second time, it again tries to start, again immediately stops and then throws up a "camera keeps stopping" message. If I tap OK, the message closes and the phone continues to work normally. The camera app in unofficial 18.1 works fine (one of our three phones hasn’t been updated yet). The problem doesn’t seem to be hardware: Open Camera works fine on 20210425 after being side loaded.

The Play Store app (installed by either Open Gapps or NikGapps) categorically refuses to install apps on 20210425, complaining there’s not enough space. The app offers to delete other apps to make space, but since there aren’t any (yet), it can’t. The problem doesn’t seem to be related to the size of the app: I tried to install a really small app (APK = 3.3KB) and that failed, too. The problem also doesn’t seem to be related to user partition space, I side loaded DiskInfo and it says Data/data/user/0 has 10.9GB free. Further, I can side load apps via APK: The not-small Open Camera, for example. The Play Store installs/installed apps just fine on 20201225.

Another quirk is that the phone s still running 20201225 refuses to run Google Maps (stops immediately after trying to start).

Yet another clue may be the fact that I haven’t been able to recreate whatever combination of OS version, GAPPS version and procedure I used to create the phone that’s still running 20210425. Perhaps I did something differently this time.

Does anyone else have these problems? If so, are there fixes? Did I do something wrong? Is there something I need to do differently?

Thank you in advance,

Tenaya
[Samsung Galaxy S 5 Unified Development] alansworld2010@gmail:
you somehow have a media storage issue they changed the permission set with the way apks communicate with "sdcard" internal storage for less vulnerabilities at the user app level....and stopped external sd support....we had a legacy media patch for old devices....now heres the catch if you flashed with the external sdcard in with older TWRP it thinks that external is internal SD then when u boot internal is blank external don't work and the play store thinks you used up....also any music app doesn't see media... this happened to me... what i did was cracked back and format data and wiped all partitions took external out wiped everything in twrp...went to download mode in odin reflashed full four file G900TUVU1GQC2_G900TTMB1GQC2_G900TUVU1GQC2_HOME.tar.md5

somethimes its nice to boot Android 6.01 then look in the newer threads and see how people complain so much about this and that and remember The TOUCHWIZ days....lol....

Then flashed new 18.1 clean using the lineage recovery..... so that means I had to flash twrp once in odin to install the new recovery file to install the official build because I dont like hemidall

... with lineage gapps https://androidfilehost.com/?w=files&flid=322935
[Samsung Galaxy S 5 Unified Development] Andresine:
Google maps only works in incognito mode, in normal mode does not works . I hope it will be fixed
[Samsung Galaxy S 5 Unified Development] ludwig83:
works fine on my device ...
[Samsung Galaxy S 5 Unified Development] kurtn:
No, there is a magnet in her pocket. It triggered the plip flap smart cover feature.
[Samsung Galaxy S 5 Unified Development] Lakeerie:
Well, that could be the reason. My Handy has only a silicone cover, while my wifes handy has a cover with a magnet. Thanks
[Samsung Galaxy S 5 Unified Development] x2k13:
Yes, I accidentally put the phone next to a fridge magnet, that way I found out it works like this. I guess @jenssa & @Lakeerie had some magnet close to the phone as well.
[Samsung Galaxy S 5 Unified Development] jenssa:
When I updated the latest build (05.16.2021) the phone didn't boot and was sent into los recovery. It was unable to boot whatever I did, I even restored backup in twrp to no avail. I had to restore everything from scratch. Did anyone else have this problem?
[Samsung Galaxy S 5 Unified Development] curiousrom:
Failed Update 2021-05-16 & Failed TWRP Restore

You don't provide any info like device model, recovery version, exact names of the files you flashed & how, if you flashed anything else besides LineageOS and a GApps package (name?), logs, etc. which makes it very difficult to troubleshoot.

See Failed OTA Update BiTGApps - Script: Capture Bootloop Logcat

BTW don't install the TWRP app when offered in TWRP as it may causes bootloop because LineageOS is enforcing priv-app whitelisting rules. That may explain why you failed to restore a backup with TWRP.

In TWRP you need to restore only System, Data & Boot partitions. You can restore other partitions when trying to solve other specific issues.

No. See my post 1 page back: S5 LineageOS 18.1 Update 2021-05-16 - Lost Some Shortcuts

***
[Samsung Galaxy S 5 Unified Development] jenssa:
I'm sorry, I just wanted to hear if anybody else were experiencing the same problem, but I appreciate your offer to hjelp. The phone is a SM-G900F. I had installed Los 18.1, originally 20210425 which I had updated to 20210509 in the updater on the phone. There was no problem then, so I figured there might be something wrong with the 20210516 build. I had installed twrp 3.5.2_9-0 and MndTheGapps 11.0.0 arm-20211020_134931 and Magisk -v22.0. It worked OK, although it was rather slow. For some reason the Los recovery came back when the update failed, but I used that to factory reset the device.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: Failed Update 2021-05-16 & Failed TWRP Restore

That's extra weird.

In Updater's Preferences did you select Update recovery after installing TWRP as seen in the screenshot?

If so, that won't work because it's for Lineage recovery.

How did you install TWRP?

BTW thanks for the additional troubleshooting info. :cool: 👍

***
[Samsung Galaxy S 5 Unified Development] pmduper:
sm-g900i

Updated kltedv build via ota from 20210509 to 20210516.

ROM only, all went smooth. Thoroughly tested out on the road today and as expected it was faultless. Battery performance is very respectable. Thanks Lineage team for all you do.
[Samsung Galaxy S 5 Unified Development] OldButNotObsolete:
Registered to Say Thanks!

Thanks to @haggertk and all the Devs / contributors for the amazing work on the S5.

It has kept alive and usable, my phone, my wife’s phone, and even my mums, so has saved us a fortune from as far back as CyanogenMod and more recently LOS 16.1, and now LOS 18.1.

We have and will continue to "Pay it Forward" !!

Note: I'll summarise my own experiences with 18.1 in a separate post, in case it helps others.
[Samsung Galaxy S 5 Unified Development] kurtn:
Thank you @OldButNotObsolete

You triggered me to search

https://androidfilehost.com/?w=files&flid=325193 and

Latest Samsung Galaxy S5 firmware

Download the latest Samsung firmware for Galaxy S5 with model code SM-G900F. Check out our free download or super fast premium options.

www.sammobile.com

Both show recent updates, but the numbers don't match.
[Samsung Galaxy S 5 Unified Development] x2k13:
Today I encountered one thing, after the latest update, which I never have seen before.

Sometimes, out of the blue, the lock screen shows "Fingerprint hardware not available", and biometric unlock via fingerprint doesn't work anymore, obviously. After reboot it works again.

Is this a known bug? 🤔
[Samsung Galaxy S 5 Unified Development] jenssa:
No, I did not select update recovery. My preferences are as shown in your screenshot. I have installed twrp in various ways, both by adb sideload in los recovery and by flashing it in Odin. I do not recall which method I used on this specific occasion. I now have a suspicion that somehow my factory wiping didn't wipe everything, even if I used los recovery. The reason is that I had installed MindtheGapps before the update, but now I decided to change into BitGapps because I thought it runs better on the phone, only that I think that MindtheGapps might perhaps still be there. (I'm not sure how to ascertain which package I have, though.)

Anyway, the phone now runs moderately Ok, except for some lagging. Magisk hides root from my banking apps and google pay, so I am happy. I'm only a bit hesitant to update los until I understand what went awry last time.

BTW: Thanks for your kind assistance. You really do not need to spend time on this problem, but if you have a suggestion I would, of course, appreciate it. It is fun to customize the phone, although I would prefer not to undo the whole set up right away.
[Samsung Galaxy S 5 Unified Development] x2k13:
Just to make sure everything *Gapps related is gone, boot to TWRP, mount /system, go to to the 'addon.d' directory, then delete the Gapps survival script (something like 60-gapps.sh, might be named differently), then flash the latest LOS .zip, and after that the Gapps package you want to use now.

Now you should only have the Gapps of the package you flashed without unwanted remains of the one you used before, because flashing the LOS .zip will overwrite everything that's been there before, given that the survival script simply isn't there anymore.

Hope that helps.
[Samsung Galaxy S 5 Unified Development] lecorbusier:
Wiping too thoroughly you might lose the device's Google certification. A restore of a TWRP backup might fix it, otherwise it's back to Touchwiz 6.0.1 and forth again.

Some issues of the beginning have already been fixed, like the black overlays in the camera app.

What still annoys me is that every app supporting Bluetooth produces a BT error message from time time, even if BT is not used by the app and switched off completely.

Since the last Magisk update device passes SafetyNet check again, but i didn't encounter problems before, not even on my Note 10.1 with a rom, where SELinux is set to permissive, with no way to pass the check.

But i didn't dare to reinstall the one of my two banking apps, which refused to work on both my rooted devices since about a year. Can it be that this one just checks for an unlocked bootloader and that's it?
[Samsung Galaxy S 5 Unified Development] curiousrom:
Play Store Device Certification

FWIW a few days ago did a clean unofficial LineageOS 14.1 install on a Galaxy S3 i9300 + Open GApps Pico: uncertified in Play Store. That's Format Data (not just a simple wipe) + advanced wipe of System & the caches in TWRP.

Rooted with Magisk, enabled MagiskHide in it's settings, rebooted: certified.

Otherwise one can try https://www.google.com/android/uncertified/ Note that it may take 1 day or 2 before it shows in Play store. An app may help you find that "Google Services Framework Android ID": https://play.google.com/store/search?q=Google Services Framework Android ID&c=apps

***
[Samsung Galaxy S 5 Unified Development] grzesiek11:
Thanks for the ROM. It runs great, however I have one question:

Any particular reason why this is the case? I need a POSIX filesystem not only because of the >4 GB limit of FAT32, but also because I need POSIX permissions on my SDCard. My setup on LOS 17 was perfect, now it's kind of lacking.

Also, exFAT caused data loss twice in a month for me (and then never broke again... because I stopped using it. I have backups, don't worry, but it was irritating anyways), while both F2FS and FAT32 are really stable.
[Samsung Galaxy S 5 Unified Development] x2k13:
exFAT != FAT32

exFAT - Wikipedia

en.m.wikipedia.org
[Samsung Galaxy S 5 Unified Development] grzesiek11:
Where did I say it's the same? I even stated that FAT32 is stable for me and that it isn't the case for exFAT.
[Samsung Galaxy S 5 Unified Development] x2k13:
You wrote you need a filesystem that can handle files >4 GB. FAT can't do that, but exFAT can. You didn't say it's the same, right. Let me explain why I mentioned that:

exFAT (Microsoft) and f2fs (Samsung) are optimized for flash memory/sd-cards in terms of prolonging lifetime. That's why it is used on mobile devices. FAT32 is not, it's aimed at HDDs and when it was released, flash memory/sd-cards didn't even exist.

Using ext* on flash memory/sd-cards is *not* recommended, because a journaling filesystem (which ext4 is) is seriously lowering the lifespan of your card, because journals are constantly written to it and increase degradation of your card (read: sd-cards break much sooner and you don't want that).

POSIX has nothing to do with filesystems, it's a programming/command line interface standard. You probably mean UNIX permissions, like 0777 or 0644, etc..

What do you need that for on a sd-card?
[Samsung Galaxy S 5 Unified Development] grzesiek11:
OK, so I see I worded it wrong and you misunderstood me because of that. Sorry, I'll try to explain it better.

In the original post it is stated that since support for "POSIX filesystems" (I'll get to that later) and NTFS is dropped, the user should move to exFAT.

This assumes that the only point to use these filesystems was to support big files, hence the OP's comparison to exFAT, which also does have this feature.

So what I meant was I don't only need that feature.

I didn't say that FAT32 is good for your SDCard, only that it doesn't render data unusable every so often as opposed to exFAT (that is my experience, if you have no problems using exFAT then good for you).

I never said anything about EXT4, but you can disable the journal. I still wouldn't recommend it for flash storage, but it's possible.

Also notice that the lack of support for it on SDCards also means lack of support for hard drives plugged in with USB OTG.

OK, so on that topic, yes, calling F2FS and EXT4 "POSIX filesystems" is not correct, but that's what OP did and I reffered to their post.

You can however call these "filesystems which implement POSIX features" and it would be correct, so "POSIX filesystems" can be a mental shortcut.

In the case of permissions, yeah, "UNIX permissions" might be a better way to describe that, but "POSIX permissions" can refer to the standard that defines these permissions. I wouldn't say it's incorrect.

Giving apps direct access to the SDCard - for (much) better transfer speed and also if the app doesn't support SAF at all.

Debian installation that I chroot into.

Creating symlinks from /data/data folders of apps that take a lot of space on the data partition.

Yeah, my use case is a bit specific, but I believe I should be able to do whatever I want with my phone. That's why I'm asking if there is any technical reason for this feature not to be supported anymore.
[Samsung Galaxy S 5 Unified Development] Vini69:
Just installed a fresh LOS 18.1 after a full wipe, nice ! Will report on full experience later.

At the moment I am trying to solve a serious issue related to the external SDcard, exfat formatted.

Everything works ok at first, but when sustained write is performed to the external SDcard, i.e. saving offline google map region, or using RAR to backup a chunk of data from internal to SDcard, the phone suddenly just reboots at some point and refuses to mount the SDcard saying it's corrupted and needs to be formatted.

Checked and fixed on my PC, no issue, mounted in other phones with no issue whatsoever, but back in my S5 the card is reported corrupted and is not mounted, and LOS insists to format it!

So I guess there is a discrepancy between what LOS thinks is on the SDCcard and the actual SCcard content ? Any way to "reset" the state of the SDcard seen by LOS, or a way to force a check/remount, so I won't have to reformat it and lose the card ID which screws up a bunch of programs accessing it, i.e. signal encrypted backup for example... ?

Although LOS won't mount the SDcard and is reporting it as corrupted, I have no problem accessing it (R+W) from TWPR.

Any idea or tips welcomed ! Thanks.

PS: Similar issue reported in this thread: https://xdaforums.com/t/extsdcard-corrupted.4235107/post-84509657
[Samsung Galaxy S 5 Unified Development] moreorless:
Good Rom! Works good for now. Installation was flawless. I did a fresh install and using the the lineage recovery.

I just noticed that my messaging apps like Telegram and Signal don't show the notification dot on the app which I put on the down quick access section of home screen.

Can't figure out what is causing this.

Having the G900F with the latest patch lineage-18.1-20210516

EDIT:

It's not only those messenger app - even the normal stock SMS app doesn't show any indicator dot but I activated that feature in the notification settings. Very weird.
[Samsung Galaxy S 5 Unified Development] x2k13:
Here's what you can do as a workaround, not ideal and it just covers the symptoms until someone finds a fix for the source of this issue.

You need a Linux distro, I prefer Debian, and the command line/terminal.

1. Backup the sd-card's contents to disk

2. Format the card with mkfs.exfat via terminal

Let's assume the sd-card's ID is BA04-0336 and is mounted as /dev/sdd1 (you can check that doing lsblk, it will show all block devices on the system, including the sd-card).

The following command will reformat the card with that very same ID so you can just insert it back and your phone won't notice the difference:

mkfs.exfat -i BA040366 /dev/sdd1

Copy all the stuff you saved to disk back to the reformatted card, insert it in your phone.

Boot - Enjoy.

🙂
[Samsung Galaxy S 5 Unified Development] Eadn33:
Can confirm same issue with LOS 18.1. Had this occur repeatedly on 17.1. When upgraded to 18.1, I chose to also backup necessary files and wipe and reformat my SD card. Went a couple of weeks on 18.1 with no problems, but recently had what you described above. While "repairing" the card in Windows fixed this issue for me when it occurred on 17.1, this time that did not work. I could still read all of the files in Windows, but Lineage insisted card had problems and required reformat. I again backed up files, wiped and reformatted and has been working OK again for a week or so.

So, I don't have the answer, but confirm it is not just you having the issue.
[Samsung Galaxy S 5 Unified Development] tayfundokuyucu:
I experienced similar problem yesterday. Started more than ten video downloads in Udemy to Sd card, I get sd card corrupted message.

Copied the contents to the pc with several files can not be read message.

18.1-20210509-NIGHTLY-klte
[Samsung Galaxy S 5 Unified Development] bgatos:
Is there anyone having issues with location services or is it just me? :)

In google maps I need to start incognito mode first and then switch back to normal to be able to locate myself (to get the blue dot on map).

Outdoor gps works fine but many apps keep popping up msgs like 'your device not capable of positioning'. Wifi, bt location scanning are on and google location is enabled. Airplane mode is off.

I'm coming from android 10 and the location services worked just fine there. (there was a battery saver mode as well)

My device: SM-G900F, latest lineageos 0516, latest magisk v23 canary. MindtheGapps for android 11 arm. Clean install, factory reset.

Thanks a lot!
[Samsung Galaxy S 5 Unified Development] kurtn:
No GApps/MicroG?
[Samsung Galaxy S 5 Unified Development] bgatos:
MindtheGapps for android 11 arm.

Thanks. Sorry, left out. Edited my post.
[Samsung Galaxy S 5 Unified Development] ludwig83:
Hey Guys! I reflashed Bootloader - Modem - Firmware this week and now I'm thinking about a proper backup. When I go from LOS Recovery to TWRP, can I allow system changes (modify) or do I have to take: read only - currently I use Magisk too. What would be the best way?

By the way...reflashing DID change something...Im now allowed to use more providers...dont know if I will have to pay for roaming in my country :D
[Samsung Galaxy S 5 Unified Development] pcslide:
kltechnduo	SM-G9008W

Cellular doesn't work on 20210515-nightly, it reads sim card info, but doesn't make connection to China Mobile's network.

before flashing LOS 18.1, I updated Samsung firmware to G9008WZMS1CRH1(Latest) through Odin, and then updated modem to G9008WZMU1CTI1 through Samsung auto-update.

I then flashed lineage-17.1-20210417, the handset made connection without problem.
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 kltechnduo - China Mobile Network Issue

Thanks for the detailed description. :cool: 👍

With the WiFi off, did you try turning off your S5 SM-G9008W, switching the SIM to the other slot & turn it back on?

My S5 G900M LinegeOS 18.1 klte is not a dual SIM so the path may be different on your model: > Settings > Network & internet > Mobile network > Advanced > Access Point Names > APN > and make 100% sure that they are identical to your network provider's recommended settings.

Can you send & receive SMS? Did you try with an other SIM?

In your model's changelog: https://download.lineageos.org/kltechnduo/changes/ I see under Changes included in lineage-18.1-20210515-nightly-kltechnduo-signed.zip: apns: Enable IPV6 for China Mobile.

Maybe it's related to your issue? ¯\_(ツ)_/¯

If all the above fails, to rule out that change, backup all partitions except Cache to the external SD Card using TWRP then after wiping only the Dalvik / Art cache & Cache, flash the previous build: lineage-18.1-20210508-nightly-kltechnduo-signed.zip and you will not lose your third-party installed apps, data & settings.

If you still can't connect to China Mobile revert by restoring only System, Data & Boot partitions from the backup you just made. You can wipe only the Dalvik / Art cache & Cache partitions if you wish.

***