yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] curiousrom:
Clean Install with TWRP

1- "3.5.1_9-0-klte" - Update to TWRP 3.5.2_9-0. Works great on my S5 G900M. See How To Update TWRP Using TWRP Itself.

2- "...TWRP wipe: Davik/ART Cache, System, Data, Internal Storage..." - Format Data is better than a simple wipe Data if you want a really clean install.

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.

3- "...install LoS and then boot into it. I go through the LoS start up, then power down, boot into TWRP, install Gapps..." - That's wrong. You must NOT reboot to system before installing an optional GApps package otherwise expect apps crashing & other issues.

You need to install LineageOS + a GApps package in one go without rebooting to System in between because of necessary hooks & permissions granted during install.

On A/B partitions devices you need to reboot to recovery to switch the active slot before installing the GApps package. That's not the case for the A only partition Galaxy S5.

I wrote this for Windows PC users & LineageOS 16.0 because Odin is so much easier to use compared to Heimdall to flash TWRP but the same steps works for 18.1: S5 super clean install except that you need a GApps ARM package for Android 11.

See this for the current official LineageOS GApps recommendations: https://wiki.lineageos.org/gapps.html

***
[Samsung Galaxy S 5 Unified Development] Tenaya43:
It is absolutely amazing how well things work when you do them the right way, in the right order.

With TWRP, I formatted, then wiped all the partitions. Then I installed LoS and MindTheGapps. After booting and startup, both the Camera and the Play Store work as expected. I'm still wandering around testing, but all looks good so far.

Thank you very much for your help.

Tenaya
[Samsung Galaxy S 5 Unified Development] pslag01:
First off, a big thanks to @haggertk for the incredible efforts to keep the S5 alive (mine: SM-G900P, kltedv).

Is there a way to retain the use of an external sd-card with a clean install of LOS 18.1? I understand the sd-card may be available w/a dirty install, but would prefer doing a clean upgrade. Both LOS recovery and TWRP (and LOS 17.1) have no issue with the sd-card, so I know it's not a bad card or corruption issue.

I clean-installed using LOS recovery with wipe/format (and MindTheGapps), but was not able to get the sd-card working. When prompted, I selected 'use as portable storage', but it says it's unreadable and I must format. After backing it up, I re-inserted, formatted, but it was still unusable. Same after restoring data to the card, it was still unusable/unreadable.

No sd-card is a showstopper for me, so I've reverted to LOS 17.1. I understand Android 11 has made significant changes to their storage model (e.g., scoped storage), but hopefully I'm just missing something and will be able to upgrade to 18.1 w/SD.
[Samsung Galaxy S 5 Unified Development] Tenaya43:
Goggle Maps works, too.

Tenaya
[Samsung Galaxy S 5 Unified Development] smartypantsphone:
I just installed 18.1 and ogapps on g900i, and my external sdcard is working...

Maybe you have it formatted wrong, I think I read it can't be ext/ntfs/fs, it should be exfat.
[Samsung Galaxy S 5 Unified Development] pslag01:
Thanks. I formatted it w/LOS 18.1 when it complained of not being able to read/mount it.

Verified on a linux box: W95 FAT32 (LBA)

Mounted in LOS 17.1: seen as 'type sdcardfs'

- /mnt/media_rw/ECA7-F9CD on /storage/ECA7-F9CD type sdcardfs (rw,nosuid,nodev,noexec,noatime,nodiratime,fsuid=1023,fsgid=1023,gid=9997,mask=18)

exFAT is newer (and faster), but FAT32 should be fine, yes?
[Samsung Galaxy S 5 Unified Development] x2k13:
Funny thing I came across:

Just for the thrill of it, I backuped the sd-card's contents and formatted it (in LOS 18.1) as removable storage, then back to adoptable storage, rebooted, then copied everything back, migrated app-data from internal to sd-card.

Using DevCheck (search for it on Play Store):

Adoptable storage was ext4 (journaling linux fs, widely used) in LOS 17.1, turns out adoptable storage in LOS 18.1 is sdcardfs now (Samsung's invention, virtual fs).

Might be just a coincidence, but now the phone is booting faster, and the overall feel is a lot snappier.

I must admit, I haven't dug into how Android creates and handles volumes, especially when using adoptable storage on a fully crypted phone.

On Debian (which is my daily driver as desktop OS) it's done with LVM and LUKS/dm-crypt.
[Samsung Galaxy S 5 Unified Development] curiousrom:
LineageOS Snap Camera U.I. Not Showing the Full Image Preview

Edit: Good news, following a conversation with a dev this commit was merged & will be included in next build: Snap: use translucent control background on 16:9.

***

Here is a copy/pasta of a bug report I created in case an other dev can fix it if @haggertk does not have the time of inclination to do it. A logcat is attached to the report as well as the same screenshots as attached to this post.

LineageOS Snap Camera U.I. Not Showing the Full Image Preview

Expected Behavior​

When using the LineageOS stock Camera app (Snap) in both camera (Settings > Picture size > (16.9) 15.9 megapixels) & video mode one expects to see the full frame preview to be able to chose the image’s composition before taking a picture or recording a video like in LineageOS 17.1 and 16.0 before that.

Current Behavior​

In the Camera U.I. the view is cropped by the solid black overlay behind the buttons on the left & right side instead of using a light gray translucent overlay as seen in the attached screenshots.

Possible Solution​

Maybe the issue was caused by the camera_control_bg_transparent deletion in res/values/colors.xml found in the Merged commit Snap: reorganize api2 layout?

As a workaround I am using Open Camera but would rather use Snap most of the time if the U.I. can be fixed.

Steps to Reproduce​

As described above.

/device klte /version lineage-18.1 /date 2021-04-25 /kernel 3.4.113-lineageos-g4a34f0e /baseband G900MUBS1CQA3 /mods Galaxy S5 G900M LineageOS 18.1 klte build 2021-04-25 + MindTheGapps + Magisk 22.1 + TWRP 3.5.2_9-0 recovery

***
[Samsung Galaxy S 5 Unified Development] vlad3647:
3y

It worked for me ,boot into recovery, go to advanced options and "fix contexts".
[Samsung Galaxy S 5 Unified Development] zimral.xda:
OK, had an easy one (klte, german/european version): Fresh phone with A6 as it comes from Samsung. Whole factory stuff blown away by Heimdall and ADB. No google - nada, No root etc. Just back to the roots. All (very few - just 2) apps cryin' for "Play Services" thrown away. Ahhhhh, this baby is still fast with 2/16GB and without guggle. No problems with the SD cards (32 & 64GB)

Thx alot Mr. Haggertk

Ahh forgot: One additional thing, all term commands need to run under root -->sudo on my Linux Mint 19/20 desktop.
[Samsung Galaxy S 5 Unified Development] yoshkapundrick:
This is the first rom since your 14.1 that my bluetooth has worked with my 2005 car's bluetooth (version 1.1).
[Samsung Galaxy S 5 Unified Development] zimral.xda:
Me too :-) Seems to be a new trend to have no gapps....OMG... aunt Google, this hurts, doesn't it...
[Samsung Galaxy S 5 Unified Development] chillipig:
Yes I'm always careful to d/l the right package and flash it before first boot. 16.0 and 17.1 don't have the issue, there's nothing else I can do differently. As its seems to only be happening to one other person on here I'm going to assume its a DUOS specific issue as he doesn't mention which model he has, but if it were the G900F everyone would be reporting it.
[Samsung Galaxy S 5 Unified Development] lecorbusier:
For the insufficent memory issues:

Can be due to Adoptable Storage, despite enough free mem on internal & external storage.

But the S5 is also running out of space due to Los18. Many apps can no longer access sdcard, which some of them previously did w/o notice.

That was the(later discovered) reason that many of my apps would crash after being restored from a Los17 TB backup and had to be removed, reinstalled from Playstore and configured from scratch for some extra hours of fun. After that internal free mem had shrunk by about 2gbytes in my case.

During the days of Kitkat(4.4), Playstore required a minimum of 250mbytes of free internal flash to update or install a single app.

Early this year i ran into the same problem with a bit less than 900mbytes free on my now retired Acer tablet.

And camera may crash and require a reboot or even reformatting of the sdcard, if you set it to save to sd. Especially when switching between picture and movie mode,and orobably when altering flash modes.

If you're going towards 1GB or less of free internal mem now, consider uninstalling apps or use Adoptable Storage, which has its very own quirks and is probably not even possible with Los18(hasn't support for ExtFS on sdcards been removed? AS requires encrypted Ext4, i used it on Cm14 & Co for security reasons, with internal free mem still being plenty. But too many issues.
[Samsung Galaxy S 5 Unified Development] chillipig:
Hi. Thanks for your reply but the 'insufficient space' problem is there before any backups are restored or changes are made. First boot as a new device, login to the Play store and updates immediatley fail with that message.
[Samsung Galaxy S 5 Unified Development] Lordicus21:
No Gapps for me, it slows too much down
[Samsung Galaxy S 5 Unified Development] jdrch:
The bug in which starting a dirty flash from TWRP (latest build v3.5.2_9-0) causes instant reboot back into recovery has returned in the 20210725 build.
[Samsung Galaxy S 5 Unified Development] Chris_0147:
It asks how this rom is going in the users who have the g900t model and the other question is arm or arm64. I ask it for the gapps
[Samsung Galaxy S 5 Unified Development] jdrch:
From the perspective of the ROM itself, all models function the same once you get it installed. The jailbreaking process turns whatever model you have into Google Play Edition(?) developer device, so no worries there. This is why the thread is named klte*.

The device's SoC is arm 32-bit, and so everything else associated with it is also arm 32-bit.
[Samsung Galaxy S 5 Unified Development] Chris_0147:
Ok thanks is there any ota update
[Samsung Galaxy S 5 Unified Development] Chris_0147:
This rom is more smoother than the stock rom
[Samsung Galaxy S 5 Unified Development] Chris_0147:
If you want, let's talk later so you can help me unlock the bootloader since this would be the second device that I root. Could you help me? @jdrch
[Samsung Galaxy S 5 Unified Development] jdrch:
Yes, the ROM is built weekly. New builds are posted at https://download.lineageos.org/klte

I haven't done that since 2016, so I don't know what the latest method is. I would not be of much help there.
[Samsung Galaxy S 5 Unified Development] Chris_0147:
you have the g900t model For what is the firmware option that appears in the rom post it is necessary
[Samsung Galaxy S 5 Unified Development] Nobby1960:
Download Magisk 23 from here. Please flash this ZIP archive in TWRP. The phone will now restart. Go to the Magisk manager app and follow the further steps.
[Samsung Galaxy S 5 Unified Development] Chris_0147:
Enforcing or permmisive
[Samsung Galaxy S 5 Unified Development] kurtn:
Sorry, there is so much misinformation.

There is no jailbreak in android

You dont need to root with magisk

Official magisk download is from github topjohnwu

Bootloader unlock procedure for every device is in wiki.lineageos.org

Unlocking doesn't turn your device into anything else.

And selinux is enforcing for each official builld that you download from lineageOS.org
[Samsung Galaxy S 5 Unified Development] kurtn:
The firmware is for people that did not update stock firmware for a long time. It seems like you did not unlock, yet. So search let your phone update first.
[Samsung Galaxy S 5 Unified Development] Boatshow:
Anyone remember the stuttering in Bromite/Chromium browsers I was talking about? You need to go to about://flags and disable "Use AAudio Driver" to reliably fix it.

I found the solution here. Looks like it also affects 2020 Xperia phones so I'm not sure what the common theme is.
[Samsung Galaxy S 5 Unified Development] reyanshzuber:
anyone having mic issues during calls?
[Samsung Galaxy S 5 Unified Development] Chris_0147:
Not me at the moment all good with the mic
[Samsung Galaxy S 5 Unified Development] Chris_0147:
I have already been able to unlock the cell and install this rom to it and everything very well without problems next week I will try havoc 4.5 (I have a suggestion in a rom of a tablet that had something called low memory killer deamon ( lmkd)
[Samsung Galaxy S 5 Unified Development] dcarvil:
What sort of issues? The S5 has historically had a problem with low mic volume on calls. The solution for that is to boost the mic volume in mixer_paths.xml. See this post - https://xdaforums.com/t/rom-officia...-samsung-galaxy-s5-klte.4267517/post-84960197

I haven't checked to see if the patch has been applied to later builds.
[Samsung Galaxy S 5 Unified Development] x2k13:
I used this flashable .zip, works great so far, no issues on 18.1.

[LOS14/15/16/17 Android7/8/9/10] MIC GAIN and a little Speaker gain too!
[Samsung Galaxy S 5 Unified Development] root4123:
Hey Guys, thanks for keeping the S5 alive, still a great phone! I have a small question, is it possible to add support for the SM-G901F ? I just got this one but the hardware is somewhat different as in the original S5 (SM-G900F) , which is greatly supported. This phone has a 32bit - Qualcomm Snapdragon 805 APQ8084 (28nm), Krait 450 and Adreno 420 : https://wiki.lineageos.org/devices/kccat6

I tried building from within a ubuntu VM with build tools and all needed packages but its missing some needed repository's which aren't available for LoS18.1. Only files from LoS16 in the lineage repo.
[Samsung Galaxy S 5 Unified Development] kurtn:
You are right. Kccat6 support ends with lineageOS 16.0 - it is still buildable and you still get some security patches. But your postin this theread is off topic. Your phone looks the same but needs a completely differen ROM
[Samsung Galaxy S 5 Unified Development] rootkitty:
@Boarshow thanks very much for the reply.

Just wondering if when you flashed 18.1 with TWRP, did it replace TWRP with the LineageOS Recovery?

Do I have to reflash TWRP after Flashing LOS18.1?
[Samsung Galaxy S 5 Unified Development] Chris_0147:
Mobile data not working on sm-g900t
[Samsung Galaxy S 5 Unified Development] kurtn:
No. The recovery repacement is not triggered by rom flashing. Twrp is replaced by lineageOS recovery if you allow "update recovery" in setup wizard, or updater settings.

LineageOS recovery has all features you need for updating lineageOS. If you have special reqirements, you can flash twrp whenever you want. Use odin or heimdall or a root installer.
[Samsung Galaxy S 5 Unified Development] curiousrom:
FYI: Open GApps for Android 11 Build 2021-07-27 & 28 Causing Bootloop

***
[Samsung Galaxy S 5 Unified Development] kurtn:
So sad, now that they are officially recommend

Redirecting…

@npjohnson

https://review.lineageos.org/c/LineageOS/lineage_wiki/+/313591
[Samsung Galaxy S 5 Unified Development] Boatshow:
@rootkitty Flashing 18.1 doesn't replace TWRP. You should update TWRP to the latest version beforehand though. Old versions apparently have compatibility issues.

Regarding low mic volume, very old posts suggest it's caused by dust buildup. The primary mic's hole near the charging port supposedly has a membrane to resist water and dust apparently builds up on it.

I don't have issues with it so I haven't tried it, but here's allegedly how you're supposed to clean it:

-Grab some canned air with a nozzle

-Take the back cover off the phone

-Take out the screw closest to the mic

-Put the nozzle in the screw hole and slowly blow air through it
[Samsung Galaxy S 5 Unified Development] Garry58:
I occasionally get bootloops with some updates. Not sure why and if it's even ROM related. Just a reminder to always make backups (I only make a backup of Data partition). If something goes wrong, just make a clean install (rom + mindthegapps) with a Data backup. It solves the problem for me.
[Samsung Galaxy S 5 Unified Development] reyanshzuber:
person from other side of the call cant here me. im thinking dev already included the patch in the latest build
[Samsung Galaxy S 5 Unified Development] x2k13:
Source?
[Samsung Galaxy S 5 Unified Development] reyanshzuber:
nevermind. its just what i though sorry
[Samsung Galaxy S 5 Unified Development] x2k13:
No need to be sorry, I just thought I might have missed that.
[Samsung Galaxy S 5 Unified Development] supachris:
Does anyone also notice a higher battery drain in the current version 20210728? My wife's klte needs 40% over night with WiFi off. BBS and Android battery stats say only "Mobilfunk Standby", assuming cellular standby in English. I reverted to 20210704 and let all other things at the same, now the battery drain is normal again at about 1..2% per hour. Strange...
[Samsung Galaxy S 5 Unified Development] curiousrom:
All 18.1 builds from 20210724 through 20210729 Deleted From LineageOS Servers

For which S5 variant is that? Link to download page please?

Anyway all 18.1 builds for all supported devices from 20210724 through 20210729 were removed from the LineageOS servers because of bad commits.

These new commits reverted them:

Revert "Use the original device ID when the injected event is unchanged"

Revert "InputManagerService: Flag when an injected event is a real input" - "...This is causing input lag on some devices with active accessibility filters..."

For example klte build 20210725 was removed as you can see in https://download.lineageos.org/klte

***
[Samsung Galaxy S 5 Unified Development] supachris:
Oh, sorry, there was a typo. I meant 20210718, updated via built in OTA updater. The phone is a SM-G900F klte.
[Samsung Galaxy S 5 Unified Development] mefairo:
Yes, i had los 16 and installed 20210718 and also have huge drain... And also cant fast charge anymore.. los16 has no problem.. if you say 20210704 is ok then i will give a try
[Samsung Galaxy S 5 Unified Development] supachris:
Hm, I'm not really sure if it's okay. It's obviously more battery drain than in LOS 17.1 but less than 20210718. At least at my wife's phone. But it may also be the battery is getting down and the effects are overlaying. It's a replacement battery from Polarcell, about one year old. I ordered a new one and will test. If there is also a big drain, I will go back to 17.1 (have twrp backup from before upgrade to 18.1).
[Samsung Galaxy S 5 Unified Development] mefairo:
İ can tell you its about rom :) because i change and test the roms with clean install and 18.1 is battery drainy... 2 weeks ago i could use my g900f with 4-5h SOT at 16 and 17.1 now its 2h max with 18.1. But again my biggest problem is that fast charging is not working anymore at with me. Takes 4h for full charge.
[Samsung Galaxy S 5 Unified Development] supachris:
Strange. The first two or three weeks my wife was not complaining about more drain. I will test to go back to 17.1
[Samsung Galaxy S 5 Unified Development] x2k13:
20210801 flashed successfully, OpenGApps 24 July 2021, all good.
[Samsung Galaxy S 5 Unified Development] jerfsonpaiva:
I tried a lot of versions of lineage and OpenGApps. Anyone work.

30 minutes in initial loading screen.

I've tried only lineage, withouth OpenGApps and still the same behaviour.

I wipe all the partitions and tried format o exfat and the problem still ocurr. Please, Help.
[Samsung Galaxy S 5 Unified Development] kurtn:
If nothing succeeds, you still can flash original firmware with odin.
[Samsung Galaxy S 5 Unified Development] zimral.xda:
20210801 just flashed, no GApps. All good too.
[Samsung Galaxy S 5 Unified Development] jerfsonpaiva:
Can anyone tellvme the File System of all partitions of your phone?
[Samsung Galaxy S 5 Unified Development] x2k13:
I hope you didn't wipe the EFS partion without having a backup. If you did, you're in trouble.
[Samsung Galaxy S 5 Unified Development] x2k13:
Just for the record, the last usable OpenGApps build is from 24 July. All builds after that are corrupted and can't be installed.
[Samsung Galaxy S 5 Unified Development] Nobby1960:
All ext4 - the internal SD is formatted in FAT32.
[Samsung Galaxy S 5 Unified Development] Garry58:
If you're reformatting your phone, change Data to F2FS. Your apps will load faster.
[Samsung Galaxy S 5 Unified Development] zimral.xda:
i have heard about that. Luckily i do not use google apps/services just the pure LOS rom.
[Samsung Galaxy S 5 Unified Development] zimral.xda:
i noticed a very strange behavior of my klte with the 20210801 build this night. GSAM battery monitor shows a very large loss of battery power during the night hours when i was in bed and the phone was lying on my desk doing nothing. I am currently charging and charging seems to work with the normal speed (90% in ~~1h:15min) as usual ...i'll keep an eye on that...
[Samsung Galaxy S 5 Unified Development] 2008304673:
Does it support signature spoofing? Cause I wanna use MicroG instead of gapps.
[Samsung Galaxy S 5 Unified Development] zimral.xda:
Hmm, thx for coming back. Battery is the same as before, buyed it earlier this year. It is now ~4.5% usage per hour doing nothing. No apps running so far except GSAM. Before i had ~0,8% per hour. I had no problems with earlier builds until the latest as of July-04 and July-18. However the "faulty" July-25 was working with a little more usage as of ~ 1.2 to 1.5% per hour.

As i know my old klte very well this is a significant change now. i dont use it currently in production only at my desk in standby for incoming calls, thats the reason why i know its behavior very well :)
[Samsung Galaxy S 5 Unified Development] curiousrom:
That's not possible.

It's doing something but you don't know what.

If you use fingerprint for screen lock try removing them all and use PIN of something else instead.

Check this test I made on 17.1, did not try on 18.1 yet: S5 Screen Lock Fingerprint Battery Tests @ Idle - BetterBatteryStats

***
[Samsung Galaxy S 5 Unified Development] zimral.xda:
Dont worry i'll watch it over the day. As mentioned it is not really productive currently. All tasks are killed except GSAM. No fingerprint or lock screen or screen saver. I am working over 40 years in software development, datacenter support/networks and application support. I've seen alot of impossible things in my IT- life..... :cool: ...and dont forget the users: "i did nothing...really, ..nothing..."

update: BTW it is now at 4,0% per hour....total of 88... very interesting. What about this old tale that sometimes a battery has itself to "arrange" with a ROM - is this a fairy tale ? Or are there "Gremlins at work" ? :)

Start at 1300 CET: 4.5% per hour

Update 1500 CET: 3.1% per hour

Update 1700 CET: 2.8% per hour - ~17% in 6.5 hours

Update 2355 CET: 1.6% per hour - Strange

Update 2021-08-03 1100 CET: 1.2% per hour
[Samsung Galaxy S 5 Unified Development] kurtn:
No. Go to lineage.microg.org
[Samsung Galaxy S 5 Unified Development] supachris:
This is similar to my wife´s klte. 3...5% per hour. BBS showed 97% deep sleep nevertheless. Rolled back to 17.1 with same app setup and opengapps pico and same sync settings, the battery consumtion is down to less than 1% per hour.

Since she was complaining so much, I cannot experiment too much, unfortunately...
[Samsung Galaxy S 5 Unified Development] zimral.xda:
You need to have a "user-acceptance-test device" :) I still have my other prod klte as a backup with 17.1. I run that from spring 2020 until spring 2021 when i installed 18.1 on the phone i used with 16.x . It has the same setup, a good battery. Each year i keep my current one and update the other (older) one to the new LOS version. Therefore its easy to compare them lying side by side and depending on that i can agree with your experience above. :)