yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] x2k13:
You beat me to it. I didn't know the bootloader of that device is un-unlockable. Good to know, learned something, which is nice. :)
[Samsung Galaxy S 5 Unified Development] Chris_0147:
There is any about líneage os 19.0 for galaxy s5 i want to be a tester
[Samsung Galaxy S 5 Unified Development] k24a1:
not sure if 19.x has been conceived yet.

also, my main question is, how does the performance fare on this dinosaur of a phone with android 11? i have an optimized 14.1 installed but it isn't cutting it in terms of adoptable storage. i know 17.1 was dog slow and took a while to start, but this phone obviously isn't going to be a speed demon with a newer version of android installed. i plan to use this as my daily until i get a new phone. should i install this ROM or should i go with something faster?
[Samsung Galaxy S 5 Unified Development] kurtn:
18.1 is fast enough. No idea how GApps can degrade performance.
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 LineageOS 18.1 Update 2021-11-14 - Android Security Bump

Using the built-in Updater I OTA updated S5 G900M LineageOS 18.1 klte build 2021-10-24 + MindTheGapps + Magisk 23.0 + TWRP 3.5.2_9-0 to build 2021-11-14: everything went smoothly as usual & GApps + Magisk survived the update.

There are a few minor changes listed in https://download.lineageos.org/klte/changes/ and some of them do not concern the S5 klte* family but most importantly it includes the monthly Android security bump: Bump Security String to 2021-11-05.

After the automatic reboot as seen in the screenshot > Settings > About phone > press on Android version > Android security update: November 5, 2021.

The Vendor security patch level just below it remains @ August 1, 2017 because the vendor is Samsung & it is not publishing security patches for it's S5 proprietary hardware related blobs anymore since August 2017.

See Android Security Bulletin - November 2021 for details about the security fixes.

Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 klte* up to date. :cool: 👍

***
[Samsung Galaxy S 5 Unified Development] curiousrom:
LineageOS 18.1 for S5 Performance & Adoptable Storage

I works fine if you respect it's RAM & internal storage limitations.

Battery usage is lower on my Galaxy S5 G900M LineageOS 18.1 klte compared to 15.1, 16.0 & 17.1.

YMMV depending on how much stuff you add on top of LineageOS and how many apps you have running in the background.

Battery & RAM usage depends a lot on the optional GApps package if you install one and the permissions you give to Google (Web & App Activity, Location History, YouTube History, Ad personalization, etc.) in https://myaccount.google.com/data-and-personalization

The more data you let Google collect, the more active Google Play services as you can see in > Settings > Developer options > Running services. Disabling apps auto-update in Play Store > Settings > Network preferences helps a lot also.

See the bottom of this post about optimizing MindTheGapps which I installed.

The S5 klte* maintainer haggertk recommends not choosing Internal storage for the Micro SD card (adoptable storage) when formatting the card in the device and posted about it here: "...my opinion is no one should use adoptable storage. It's a fragile mess and always has been since Google explicitly does not care about sdcards."

FWIW on my Galaxy S5 G900M when it was running LineageOS 16.0 with a SanDisk Ultra 64GB microSDXC UHS-I Card Class 10 & using SD Card Test I got Internal SD card Read 223 MB/s vs. Removable SD card Read 40 MB/s so that's why I don't use adoptable storage & don't move apps to it besides all the problems it may cause. Write speed is about the same @ 25~27 MB/s. (screenshots)

FYI from the post #1 > Compatibility Notes: "External SD cards don't support POSIX (ext*, f2fs) or NTFS filesystems anymore. If this affects you then just bite the bullet, copy any data off you really want to save, and reformat as exfat."

If you are talking about a cold or hot boot, 18.1 is faster.

If you are talking about waking up the device while in deep sleep, it's slow because Doze is very efficient in 18.1 & a bunch of stuff wakes up & wants to sync & do stuff that Doze blocks while in deep idle.

BTW that's why apps like Greenify for example are deprecated in 18.1.

It is my daily driver. See the posts I linked to in post#4

***
[Samsung Galaxy S 5 Unified Development] zimral.xda:
on sunday i updated my dev phone to build 2021-11-14 coming from 2021-10-31 Config is SM-G900F german/european version, no vendor brand, TWRP 3.5.2_9-0, open gapps "pico", no magisk, etc.

now my prod device too. Config is SM-G900F german/european version, no vendor brand, LOS Recovery, no gapps, no magisk, etc.

All good and battery drain seem to be very small again :cool: hope this waill stay so...

@Mr.haggertk: THX!
[Samsung Galaxy S 5 Unified Development] FerUMP75:
Thanks for you answer!
[Samsung Galaxy S 5 Unified Development] x2k13:
@haggertk Opening camera by double-pressing the power button still doesn't work. Error: No connection to camera. But the camera apparently opens behind that toast. This is annoying and doesn't work for months now. When will this be fixed? On LOS 19?
[Samsung Galaxy S 5 Unified Development] haggertk:
Can't fix it if I can't reproduce it, and double-press power opens camera just fine here.
[Samsung Galaxy S 5 Unified Development] haggertk:
Ah, only from lockscreen... yeah, I see it.

It'll be fixed when this is merged: https://review.lineageos.org/c/LineageOS/android_packages_apps_Snap/+/319052
[Samsung Galaxy S 5 Unified Development] Massedil:
I don't know if it can helps. For me, from the lockscreen the double tap on power open fine my camera app (which is Open Camera from F-Droid). I then tried to put Snap as default camera app and I can reproduce the problem "Error connecting to the camera".
[Samsung Galaxy S 5 Unified Development] x2k13:
Oh I just noticed the status of the fix is Abandoned. So I guess there's more to it than just the android.permission.SYSTEM_CAMERA permission issue?
[Samsung Galaxy S 5 Unified Development] x2k13:
@haggertk do you have an idea what might cause this?:

https://xdaforums.com/t/rom-officia...-samsung-galaxy-s5-klte.4267517/post-85929453
[Samsung Galaxy S 5 Unified Development] Hasan1122behj:
Hi. Thank for good rom . But , even the recording apps work and they record... But thére is no income voice or outcome voice in calling.

I use 18.1-20211114-NIGHTLY-klteduos versoin for g900fd
[Samsung Galaxy S 5 Unified Development] kurtn:
Call recording is restricted by country. https://github.com/LineageOS/androi...ler/callrecord/res/xml/call_record_states.xml
[Samsung Galaxy S 5 Unified Development] Ravi21:
Sir , any chance of available for Galaxy S5 G900H ?? My phone is dying :(:(
[Samsung Galaxy S 5 Unified Development] Fandroid Tech:
Lineage devs disabled it for your country because of 'muh laws', you can use a 3rd party call recorder. Check this thread, https://xdaforums.com/t/how-to-enable-native-call-recorder.3996233/page-2. I could recompile it without the block restrictions if it does not work, but I think that there are issues installing it.

Or you can use the Firefds Kit Xposed Module it will let you record without issues or the trouble of trying to edit the apk.

Your phone lost support at 14.1, there may be a newer unofficial lineage rom for your device https://lineageosroms.com/k3gxx/ .
[Samsung Galaxy S 5 Unified Development] jenssa:
Updating to the Nov 28 build sent my phone right into the Odin mode. I had to restore nandroid, but having some problems doing so, I'm not sure if the fault is with the update or my phone. Had no such problems with the previous updates, though. Anyone else having the same error?
[Samsung Galaxy S 5 Unified Development] kurtn:
Can you give details? Device type, previously installed version, add-ons?
[Samsung Galaxy S 5 Unified Development] jenssa:
It's samsung s5 klte, updated with the Nov 21 update of los 18.1 last Sunday, and the previous updates before that. I cannot rule out that the error might be due to the phone, though, as I restored my older s 5 on the present one (see my post of sept 15 on this thread), but until now I have had no problems with updating. I'm not sure what you mean by add-ons, but I can't think of any.
[Samsung Galaxy S 5 Unified Development] kurtn:
G900F or what? Gapps? Magisk? What recovery?
[Samsung Galaxy S 5 Unified Development] jenssa:
Yes, SM-G900F, BitGApps arm 11 (I think it was, but I may have changed to MindTheGapps at some point, I don't know how to check which one is on the phone now), Magisk-v23.0, and TWRP twrp-3.5.2_9-0-klte (I think, I would have to boot into recovery mode to check, does it matter?)
[Samsung Galaxy S 5 Unified Development] kurtn:
Mabe you should do a clean Installation. No magisk. No dirty switching between GApps installers. No twrp restores.
[Samsung Galaxy S 5 Unified Development] jenssa:
I have restored the phone; it's up and running again (on update of Nov 21). My question was only if others had the same problem as I experienced.
[Samsung Galaxy S 5 Unified Development] kurtn:
Fresh installed a G900F with twrp 2.5.2_9-0 and November 21 LineageOS. No encryption no GApps no magisk. OTAupdated to November 28. No problem.
[Samsung Galaxy S 5 Unified Development] jenssa:
Ok, thanks, then I know the problem lies in my phone.
[Samsung Galaxy S 5 Unified Development] solarisintel123:
Thanks for for build Japanase Galaxy S5(kltekdi)

But since Lineage-17.1, I'm using modified kernel with EXTCON enabled.

Without EXTCON, the Japanese Galaxy S5(SC-04F, SCL23) will not detect usb charge.

and charger mode is looping reboot.

Kernel with EXTCON enabled, EAR JACK will not detects.

Is there a way to fix it?

lineage_kltekdi_defconfig

CONFIG_EXTCON=y

CONFIG_EXTCON_MAX77804K=y
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 LineageOS 18.1 Update 2021-11-28

Using the built-in Updater I OTA updated S5 G900M LineageOS 18.1 klte build 2021-11-14 + MindTheGapps + Magisk 23.0 + TWRP 3.5.2_9-0 to build 2021-11-28: everything went smoothly as usual & GApps + Magisk survived the update.

There are just a few minor changes listed in https://download.lineageos.org/klte/changes/ but I updated anyway so I could post about it.

For some reasons some apps did not have their labels in the app's drawer but toggling off/on in Trebuchet's Home settings > Show icon labels in drawer fixed it.

Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 klte* up to date. :cool: 👍

***
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: S5 kltekdi Charging Issues

AFAIK there is no fix in the current LineageOS 18.1 builds @ the present for the S5 kltekdi charging issue.

The S5 klte* LineageOS maintainer haggertk never replied to this post. ¯\_(ツ)_/¯

He also posted this in reply to a Galaxy S5 (SC-04F) docomo edition user but there was no follow up by @Hamza Shahbaz nor by @haggertk:

***

Just curious: did you try booting in TWRP recovery & connect to a power adapter to check if it's charging?

***
[Samsung Galaxy S 5 Unified Development] solarisintel123:
in TWRP Reocvery, charging is working.
[Samsung Galaxy S 5 Unified Development] zimral.xda:
Updated my dev phone to build 2021-11-28 coming from 2021-11-14 Config is SM-G900F german/european version, no vendor brand, TWRP 3.5.2_9-0, open gapps "pico", no magisk, etc. All good, no problems so far.

Thx to Mr. haggertk.
[Samsung Galaxy S 5 Unified Development] D0n1elT:
Hey,

I'm still fairly new to the whole phone-flashing scene and I have some issues. Maybe someone can help.

I'm trying to install lineage-18.1-20211128-nightly-klte-signed.zip (without GApps or anything) onto a S5 klte using TWRP 3.5.2_9-0.

* First I've loaded the zip into /external_sd/TWRP (using adb push).

* I format data. (The thing where you have to type 'yes'.)

* I go back to advanced wipe and wipe:

* Dalvik / ART Cache

* System

* Data

* Internal Storage

* Cache

* Reboot into recovery

* I install the LineageOS 18.1 .zip from /external_sd/TWRP/lineage-18.1-20211128-nightly-klte-signed.zip

* I would now install open_gapps-arm-11.0-pico-20211125.zip and org.fdroid.fdroid.privileged.ota_2120.zip but I didn't this time.

* Wipe Cache/Dalvik

* Collect installation logs using adb pull

* Reboot system

* LineageOS starts and greets me with the installer thing.

* OS crashes (randomly?! Or if I press on the start button), it restarts. And it crashes and restarts while displaying the boot animation. So I get stuck in a bootloop.

Any help is much appreciated!

Installation logs:

klte installation logs

klte installation logs. GitHub Gist: instantly share code, notes, and snippets.

gist.github.com
[Samsung Galaxy S 5 Unified Development] kurtn:
The "installer thing" is the setup witard? Does it ask for language, time zone, wifi password? Can you setup without wifi?
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 G900F Bootloop - Old Bootloader

Thanks for providing very good troubleshooting info & linking to your recovery.log. :cool: 👍

You did everything right except that in the log it says "ro.boot.bootloader=G900FXXU1ANC9" and that bootloader is from Android 4.4.2 as you can see here.

Samsung vendor's firmware 6.0.1 is required for LineageOS 18.1 as mentioned in the post #1.

Follow the instructions in S5 Odin Flashable Modem & Bootloader and flash this file created by the LineageOS maintainer of the S5 klte* haggertk for your S5 SM-G900F: https://androidfilehost.com/?w=files&flid=325193

And you should be able to boot to System after that without having to re-install LineageOS.

Note: Don't install the TWRP app when offered in TWRP as it may causes bootloop because LineageOS is enforcing priv-app whitelisting rules.

***

BTW after you Format Data it's redundant to wipe Data & Internal Storage.

From TWRP FAQ: What is a data/media device?:

Format Data adds an empty encryption footer after the end of the Data partition for some future encryption related data if enabled.

Format data will destroy the content of your internal storage so backup to external SD card or computer before doing it.

Then Advanced wipe System + the caches before installing LineageOS.

***
[Samsung Galaxy S 5 Unified Development] D0n1elT:
You were fast and spot on.

I've installed a new bootloader using heimdall. Pretty easy and fast.

And it did *just work*! Cool!

Thank you very very much!

by the way, why the heck does the bootloader tar archive file end with *.md5??

Aren't .md5 files usually checksum files?

Although..

Unfortunately, I'm having issues with the camera and music app.

Both crash instantly on start.

Same issue as: (at least the camera one.)

https://xdaforums.com/t/rom-officia...samsung-galaxy-s5-klte.4267517/#post-84905497 and I can confirm, it's not a hardware issue. Open Camera works fine.

I have installed:

TWRP 3.6.0_9-0

Magisk v23 using TWRP (renaming .apk -> .zip) (rooted, magiskhide active)

lineage-18.1-20211128-nightly-klte-signed.zip

org.fdroid.fdroid.privileged.ota_2120.zip

open_gapps-arm-11.0-pico-20211125.zip

G900FXXU1CSA1_G900FXXS1CQA4_baseband_firmware.tar.md5

adb logcat:

Crashing Logfiles

Crashing Logfiles. GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

// EDIT:

eleven music app:

11-30 20:06:42.373 358 372 E vold : Failed to find mounted volume for /storage/emulated/0/Android/data/org.lineageos.eleven/cache/ maybe this is the problem?

by the way, I granted all permissions for both apps through the settings app.
[Samsung Galaxy S 5 Unified Development] dcarvil:
Yes, md5 files are checksum files. The Samsung files are tar files with an embedded md5 checksum created like this:

md5sum -t my-upgrade.tar >> my-upgrade.tar

mv my-upgrade.tar my-upgrade.tar.md5
[Samsung Galaxy S 5 Unified Development] D0n1elT:
Oh okay. yeah. Thats pretty reasonable.

By the way, I'm having issues with the recorder app.

It starts and I'm clicking on record:

Recorder app log

Recorder app log. GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

11-30 20:29:18.404 28979 28979 W ContextImpl: Failed to ensure /storage/emulated/0/Android/data/org.lineageos.recorder/files/Music: android.os.ServiceSpecificException: (code -22)

Once again: something with /data ...

I have a sd card installed, but it's still formated to FAT, I guess. (Upgraded Kitkat 4.4 straight to LOS 18.1)
[Samsung Galaxy S 5 Unified Development] curiousrom:
If you installed only the bootloader that may explain your issues.

If you installed the full custom firmware package re-install LineageOS after Format Data and Advanced wipe System + the caches.

FYI from the post #1 > Compatibility Notes: "External SD cards don't support POSIX (ext*, f2fs) or NTFS filesystems anymore. If this affects you then just bite the bullet, copy any data off you really want to save, and reformat as exfat."

As a rule of thumb I always use the device itself to format Micro SD Cards to avoid issues.

Copy the content of your card to computer and use the stock LineageOS Files manager to format to Portable storage.

***

I saw that release in https://twrp.me/site/update/2021/11/28/twrp-3.6.0-released.html but have seen bugs reported in the past after new releases so I prefer to wait a couple of weeks before installing them.

Some new releases were even removed from the TWRP severs because too buggy.

twrp-3.5.2_9-0-klte is known to work fine on the S5 & that's why I use it.

***
[Samsung Galaxy S 5 Unified Development] BigPulco:
Just installed yesterday...

HW: SM-G900FQ (assumed as "F")

SW: twrp-3.5.2_9-0-klte + lineage-18.1-20211128-nightly-klte-signed.zip + open_gapps-arm-11.0-pico-20211201.zip + Magisk-v23.0.zip

Clean Install... wipe everything also format data...

Seems works good...

Only headache left "yahoo mailing app" (famous fault "Something went wrong. Please try again later" which is indeed it does not let me to connect the yahoo server..., at the year 2021 what they are saying... )

Thanks to all of you.
[Samsung Galaxy S 5 Unified Development] x2k13:
I tried to flash the 3.6.0 image for jfl(texx) but that failed because the image is bigger than the partition, so I didn't bother to try on klte (which is my daily driver).
[Samsung Galaxy S 5 Unified Development] BigPulco:
Edit:

I managed to signing in with Yahoo. Necessary to cancel add_bloker SW ( I am using AdAway/root ) until signing in, than re-allow sure....
[Samsung Galaxy S 5 Unified Development] BigPulco:
I have a question:

As I understand from readings to disable FlipFlop:

Settings > Connected Devices > Connection Preferences > Smart Cover > Off

has to be, but I am unable to find "Smart Cover" under "Connection Preferences"... In another post it is written that if "Screen Lock Pattern" is used "Smart Cover" becomes invisible... So, I used Screen Lock at the beginning but when I find a way not to use I gave-up...so, now I am not using Screen Lock Pattern but Smart Cover still invisible...

Is this a fault?
[Samsung Galaxy S 5 Unified Development] kurtn:
The menu becomes visible as soon as the phone sees a magnet like that from a cover.
[Samsung Galaxy S 5 Unified Development] curiousrom:
How to Disable System Apps & Smart Cover

That's right.

That Smart Cover settings appears only after the first time the hall sensor (magnetic field) is triggered after a clean install. (screenshot)

The app detecting the cover & locking/unlocking the screen in LineageOS 18.1 is Settings > Apps & notifications > 3-dots > Show System > FlipFlap (org.lineageos.flipflap).

If rooted there are a number of third-party apps that can disable (they call it freezing) System apps in Settings > Apps > 3-dots > Show system when the Disable button is greyed out like SD Maid which I use for lots of stuff.

Be very careful & don't disable stuff without researching it otherwise brace for system freeze & boot loops. A recent full TWRP backup is a good thing when tinkering with this.

If not rooted you can use the adb command method described in How to disable any pre-installed system app bloatware on Android without root using adb. These tweaks will survive updates.

Just go to > Settings > Apps & notifications > 3-dots > Show System > app's name > Advanced > scroll all the way to the bottom to get the package name to be used in adb. In this case it is:

Windows Command Prompt: adb shell pm disable-user --user 0 org.lineageos.flipflap

Mac/Linux Terminal: ./adb shell pm disable-user --user 0 org.lineageos.flipflap

To enable: adb shell pm enable org.lineageos.flipflap

***
[Samsung Galaxy S 5 Unified Development] rellieberman:
Hi, Trying to install lineageOS on my s5 (klte) for the first time. lineageos recovery works fine and i used adb sideload to install the latest lineageOS (lineage-18.1-20211128-nightly-klte-signed) after installation i rebooted to system and the lineageOS logo appears for several minuets before the system automatically reboots to recovery stating "Can't load android system. Your data may be corrupt.

This happens with lineage-18.1-20211107 as well.

the firmware version i have installed is G900FXXU1CPI8 (for marshmallow in Israel) could this be the issue?

Thanks!

attached is the installation log + the log when recovery is rebooted after system doesnt
[Samsung Galaxy S 5 Unified Development] D0n1elT:
So, I just backup up the entire sd card and reformated it using the stock LineageOS Files Manager like said above.

Neither the camera app nor the music app start and 'adb logcat' spams the same thing over and over.

Crashing Logfiles

Crashing Logfiles. GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

I'll just reinstall everything cleanly...

Formatted SD card and Formatted Internal Storage..

// Edit:

After a fresh install, the LineageOS installer at the start said, that my sd card is not supported.

I followed the installer till the end. Everything works now. Including the Music and Camera Apps. ^^

// Edit 2:

After a restart, LineageOS tells me that the SD card is not inserted anymore and later that it's corrupted...

I'll check for bad block or smth on my computer...

// Edit 3:

A new SD-Card fixed everything.
[Samsung Galaxy S 5 Unified Development] jenssa:
I finally got around to do a clean reinstall after another failure today to update to this Sunday's build. It took me a few hours to get everything back because, for some reason, Titaniumbackup wouldn't allow batch restore, only restore app by app. The phone is now up and running, and hopefully it will "behave better" now that I have (hopefully) raised every trace of the nandroid backup from my old Samsung galaxy s 5. The lesson seems to be that it is not so easy just to install the content of an old phone onto another phone, even if it is the exact same type of phone.
[Samsung Galaxy S 5 Unified Development] rellieberman:
Finally managed to get lineage os 18.1 up and running! :)

The weird thing is that the flash only worked if I first flashed lineage 15.1 and then 18.1.

could someone explain why this would be the case?

Its quite puzzling because if the 18.1 flash broke (for example if flashing openGapps nano and not pico) I needed to reflash 15.1 before attempting another 18.1 flash.

By the way did anyone else face issues with the nano package?
[Samsung Galaxy S 5 Unified Development] curiousrom:
Broken Open GApps

Open GApps Nano & bigger for Android 11 (LOS 18.1) were broken again & causing bootloops.

Builds 0211202, 0211203, 0211204 were removed from the servers and 0211205 & 0211206 were skipped AFAIK as you can see in https://sourceforge.net/projects/opengapps/files/arm/

The problem is that Open GApps churns out automated daily untested builds & when Google changes the permissions & other stuff it breaks the packages.

***
[Samsung Galaxy S 5 Unified Development] Hasan1122behj:
Thanks for for respond 😊😊

And my problem is something else

I dont received or send any voice when calling at all i can just text or use internet but no calling

My problem is not that i can't record... My problem is i make call the ringing happend i pick up the phone and swipe to answer but no sound come in or out ...

I even changed some dialer app .. no change 🙏🙏