yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 LineageOS 18.1 Update 2021-05-23 - Lost Settings Widget Shortcuts

Using the built-in Updater I OTA updated S5 G900M LineageOS 18.1 klte build 2021-05-16 + MindTheGapps + Magisk 23.0 + TWRP 3.5.2_9-0 to build 2021-05-23: Magisk survived the update but minor annoyance: some Lineage widget created shortcuts were lost on Home page.

There was no spectacular changes in https://download.lineageos.org/klte/changes/ but updated anyway so I could post about it.

I use the stock LineageOS Trebuchet launcher and these were shortcuts created with the LineageOS Settings widget & stacked to create a Settings folder as seen in the screenshot.

Contrary to last week's update, a shortcut to an album created with Simple Gallery Pro and shortcuts to some web pages created with the Chrome browser survived.

The change devicesettings: Add strings for "Disabled" + wake on pick-up does not concern the S5 klte variants because the "wake on pick-up" gesture is not supported as you can see in > Settings > System > Advanced > Gestures.

Note for klteaio & klteduos users: as you can see in the Lineage automated builder run 20210523 the builds failed for your devices so you will have to wait for next week's run to get a new update.

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

***
[Samsung Galaxy S 5 Unified Development] zimral.xda:
klte update is just running in the bedrom. My wife and my daughter currently use most of the bandwith for streaming and my phone channel has a lower prority, so this may take a few more minutes..... :cool:

Result: All good! As mentioned yesterday in the Pixel2 thread, 5x6 grid has now 5 instead of 6 hotseat icons. i am just using 5 so this doesn't hurt me much.

I love this old S5, so thx alot Mr. haggertk !
[Samsung Galaxy S 5 Unified Development] Raldor:
Hello, I have found a small performance issue with this ROM, as well as a possible solution. This could also be related to the problem reported by Boatshow above.

Though general performance is great, I've noticed some intermittent stuttering during games.

While looking for a way to fix this I found out that switching the CPU governor from "interactive" to "ondemand" with kernel adiutor eliminated the stutters.

Then I thought it might be an issue with the interactive governor, so I tried setting its "sync_freq" parameter to "1728000". Well, this did the trick! I believe this is intended to be the default value, but for some reason it is set to "0" instead.

Thank you for you time haggertk, and please let me know if it is necessary to report this through gitlab.
[Samsung Galaxy S 5 Unified Development] Eadn33:
Appears to me from changelog that power button screenshot may be returning in next build.
[Samsung Galaxy S 5 Unified Development] Boatshow:
Does that actually work? I couldn't get most of the governor settings to do anything. From what I've read the MPDecision hotplugger overwrites governor settings as long as the binary is running.

Seems like my h.264 playback stutters are app related bugs. I fixed the Bromite stuttering by changing a flag. For Chromium based Android browsers go to chrome://flags and disable WebRTC Hardware Video Decoding.
[Samsung Galaxy S 5 Unified Development] GeoTchy:
Hello !

First thanks to maintain my old G900F always up to date and smooth :)

I upgraded from last 17.1 build (with opengapps) to 18.1 (with bitgapps) and all seems working fine (including external sdcard it seems). I followed the lineagos upgrade wiki to proceed. So without clearing my data.

And like i wrote, all is working except gmail whish is always crashing... even if reinstalled, clear related data...

Then i don't know if this issue is already known or not... i already read that there was some issue in Android 11 related to goolge apps and webview / chrome. Perhaps also related to that.

So i will use another email client for the moment, because it seems that lineage team decided to remove the email built-in apps :(

Just i hope, if it's recognize has an issue, that it will be fixed in next builds :)

Thanks ! and long life to your team !
[Samsung Galaxy S 5 Unified Development] zimral.xda:
Hey, u can use the LOS17.1 mail client as mentioned here (Post #9-12) this works great.

https://xdaforums.com/t/lineageos-email-app-com-android-email-on-stock-rom.3812153/#post-84949095
[Samsung Galaxy S 5 Unified Development] mrmarioman:
Just upgraded from 17.1. Did a semi clean install (kept media and docs). And so far everything works fine. And it's definitely snappier. Many thanks to Haggertk.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Upgrade 17.1 > 18.1 + BiTGApps & Gmail Issue - MindTheGapps

Try this: Gmail app's info > Storage & cache > Clear storage. Then back, uninstall Gmail & reboot. Play Store > install Gmail & test.

FWIW on Galaxy S5 G900M LineageOS 17.1 klte + Open GApps Pico + TWRP 3.5.2_9-0 upgraded to LineageOS 18.1 klte + MindTheGapps for Android 11 ARM + Magisk & everything works fine including Gmail.

Made a post about it here: Galaxy S5 LineageOS 17.1 Upgrade to 18.1 + OTA Update Success Using TWRP.

That post includes a list of the apps installed MindTheGapps and a tip: you can disable the Google's search app with it's optional personal data hungry Assistant in it's app info.

FYI the wiki https://wiki.lineageos.org/gapps.html recommends MindTheGapps for Android 11 @ the present.

If you look at the Thanks and Credits chapter in the bottom of the page of https://gitlab.com/MindTheGapps/vendor_gapps there is a bunch of LineageOS devs mentioned including haggertk.

Maybe you could report your Gmail issue also in the thread [CUSTOM][GAPPS] BiTGApps for Android?

An other S5 klte* user (@jenssa) had an issue with BiTGApps. See my reply here: Failed OTA Update BiTGApps - Script: Capture Bootloop Logcat - Magisk SafetyNet Test and create a TWRP backup + a Google Backup before updating just to be on the safe side.

***
[Samsung Galaxy S 5 Unified Development] Vini69:
Follow-up on corrupted external extfat sdcard

Test case :

1/ spotify updates its cached files located on the external extfat sdcard

2/ spurious reboot occurs

3/ upon reboot, the scdard is corrupted and can't be mounted

Diagnosis:

Checking manually the sdcard using fsck.exfat identifies the corrupted files, which are preventing the card to be mounted : see attached log

- fsck.exfat identifies the corrupted files but is enable to fix anything, whatever the option

- fsck.exfat Lineageos version 1.04 (checked in by haggertk)

GitHub - LineageOS/android_external_exfatprogs

Contribute to LineageOS/android_external_exfatprogs development by creating an account on GitHub.

github.com

- fsck.exfat current version 1.12

GitHub - exfatprogs/exfatprogs: exFAT filesystem userspace utilities

exFAT filesystem userspace utilities. Contribute to exfatprogs/exfatprogs development by creating an account on GitHub.

github.com

Although this makes no difference because of pending issue #117 : Can't repair corrupted exfat

Can't repait corrupted exfat · Issue #117 · exfatprogs/exfatprogs

Fsck doesn't manage to correct error. Master branch exfatprogs version : 1.0.3 [check_inode: 726] size 4210715009 is greater than cluster heap: /DCIM/100MEDIA/P0580058.MP4 [check_inode: 726] size 4...

github.com

- Inserting the sdcard into a PC, Windows detects the issue and offers to "scan and repair" the drive. Once the sdcard is "fixed", it can be used in the PC without problems. Although, a Windows "scanned and repaired" sdcard will still appear as corrupted in Lineageos and can't be mounted.

Options:

1/ On another device that can mount the sdcard, delete manually the previously identified corrupted files ; it's usually sufficient to fix the issue.

2/ Otherwise, backup the sdcard content, reformat (also restore the volumeid), then restore the backup.

Other thoughts :

Under stress writing to the sdcard, lineageos can reboot unexpectedly. Since this is not an isolated incident, this should definitely be investigated, since as a result the sdcard will be more likely corrupted and the actual tools don't allow to repair it.

I am not sure how to recover the log files preceding the reboot, once the device as rebooted. if someone can instruct me how to do so, I'll post them the next time this happens, which is unfortunately too frequently.
[Samsung Galaxy S 5 Unified Development] x2k13:
Thanks for testing this thoroughly. I can confirm the same behaviour with NewPipe, doesn't matter what version is used. Selecting the sd-card as download folders (audio and video) results in instant reboot when downloading anything to that folders.

When downloading to internal storage, all good. Copying files from internal storage to sd-card via any file manager doesn't cause trouble at all. Maybe it's related to storage access framework?
[Samsung Galaxy S 5 Unified Development] :
Someone tried to install 18.1 latest official build on SM-G900T but it reboots after a couple of seconds/minutes randomly and never get back up into system (bootloop). He did a clean flash: did factory reset, sideloaded lineage, sideloaded mind the gapps, sideloaded magisk v23 and rebootet into system. I made a eng build so debug is enabled by default.

Log is attached (*:E)
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 SM-G900T Failed to Boot

If you are using TWRP (version?) try a Format Data (instead of a simple wipe or factory reset) + Advanced wipe of System & caches.

After the initial install of LineageOS + GApps only to keep it simple, booting to System, setup & test on the S5 you can flash later at anytime the Magisk...zip in recovery.

"...sideloaded magisk v23" - What did you sideload exactly? If it's a ...apk that will not work to root the S5 klte*

From Galaxy S5 LineageOS 17.1 Upgrade to 18.1 + OTA Update Success Using TWRP:

Old versions of TWRP may fail to apply OTA updates. See How To Update TWRP Using TWRP Itself.

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

Several S5 klte variants users reported failed to boot on 17.1 with a modem older than Android 6.0.1. This may also cause No Network or No Service issues on 17.1 & 18.1. See S5 Odin Flashable Modem & Bootloader.

"...I made a eng build so debug is enabled by default" - Did you try with an untouched installation package downloaded from https://download.lineageos.org ?

I don't now what is the log you attached to your post but that's not a logcat of a failed boot to System. ¯\_(ツ)_/¯

***
[Samsung Galaxy S 5 Unified Development] x2k13:
Double-pressing power doesn't open camera correctly.

Camera starts, but throws an error like "can't connect to camera", then closes.

When opened from home screen, no problemo.
[Samsung Galaxy S 5 Unified Development] OldButNotObsolete:
Ditto for my G900F, with Super Clean Install of:

18.1-20210509-nightly-klte-signed,

MindTheGapps-11.0.0-arm-20210412_124103

twrp-3.5.2_9-0-klte

.

I've not Upgraded to later Builds yet.
[Samsung Galaxy S 5 Unified Development] :
Thx, I will tell him to do so.

That's not true cause i did exactly the same on my klte (G900F). Sideloaded magisk apk and it worked without any problems.

Thx, I will make sure He didn't installed the Twrp App. It wasn't an OTA btw.

That's not the problem. It boots for the first time without problems and then it just restarts after a couple of second and never boots again. The setup is shown for the first boot, He can Set up his OS and then it randomly restarts and ends up in a bootloop.

Yes but with the untouched userdebug variants adb logcat is not possible by default. And because it randonly crashed i made a eng build so we can get a log. The log is directly before the device restarts.
[Samsung Galaxy S 5 Unified Development] zimral.xda:
No Problem on my european G900F. Lastest build as of 23th of may, no gapps*, no root*, no TWRP. Double pressing power starts camera. My only problem is the minor camera quality compared to a Pixel2/3 :cool:
[Samsung Galaxy S 5 Unified Development] x2k13:
I found out this bug is just occuring if camera is set to save to sd-card. When set to internal, it works as it should.

Looks like more and more issues are piling up due to the mysterious sd-card malfunctions discussed earlier in this thread. Didn't happen on 17.1, so I tend to think A11 has a pretty unstable sd-card implementation.
[Samsung Galaxy S 5 Unified Development] Eadn33:
Note that there were several similar reports of SD card problems on 17.1, typically seemed to occur during writing to the card.
[Samsung Galaxy S 5 Unified Development] Eadn33:
Power button screenshot is back with today's build. Also tried out the new option to move the volume panel to the left side of the screen, which could be nice depending on how you typically hold your phone.

Phone is working very well on 18.1. I had been looking for a new phone due to the rumored end of support for phones without VOLTE in the US, but just saw Verizon at least has decided to wait until the end of 2022 to go through with that, so the S5 lives on.
[Samsung Galaxy S 5 Unified Development] Raldor:
Here is how to reproduce this using smartpack kernel manager:

Go to this menu:

Set sync_freq from '0', which is the default, to '1728000'

This should fix the game stuttering issue I talked about.

By the way, here is how I knew the correct value is 1728000:

That value seems to be correct by default. But I guess sync_freq is being read from one place and not the other.

It works at first, but it resets after a few minutes.

Here are some CPU frequency graphs that show what's happening. They were taken while running temple run. The three on the left show the behavior before the fix, the three on the right show after. There is a noticeable difference in the graphs for cores 1 and 4: with sync_freq at 1728000, there is a sort of frequency floor while the game is running, which appears to be the correct behavior.

Here's a small list of games that are affected by this stuttering problem: Temple run, temple run 2, jetpack joyride, subway surfers, alto's adventure.

Some more information: I'm on the microg build, and using magisk. Unfortunately this device is my daily driver so right now I can't test if the problem is caused by microg or magisk, though that seems unlikely.

If somebody else can reproduce this issue, and test the fix I described, please post in this thread. I would appreciate it.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: S5 kltekdi Charging Issues

Hey guys, is there a follow-up on this?

Is the charging issue fixed in the new kltekdi builds?

***
[Samsung Galaxy S 5 Unified Development] vd6x:
I updated the latest build, the problem still persist
[Samsung Galaxy S 5 Unified Development] bgatos:
By any chance, does anyone use the investing.com app? Do you have 'Theme' in Settings? I had this menu item on android 10, but after installing the latest Galaxy S5 Lineageos 18.1 the menu item simply disappeared, so there is no dark mode option now. And the app does not inherit dark mode from phone settings.

Any help much appreciated!

// European Klte, latest lineageos, latest magisk canary, mindthegapps, latest investng.com app from play store. clean install, factory reset.
[Samsung Galaxy S 5 Unified Development] x2k13:
From my experience a lot of stuttering actually doesn't come from the CPU as such, but the low ammount of RAM on this old phone. Apps in background get killed constantly, making the App in foreground stutter regularily.
[Samsung Galaxy S 5 Unified Development] Vini69:
FYI, I have issued a bug report regarding the sdcard write reboot + corruption issues

Phone reboots randomly when writing to external exfat sdcard, generaly corrupting the sdcard. (#3571) · Issues · LineageOS / issues / android · GitLab

Phone reboots randomly when writing to external exfat sdcard, generally corrupting the sdcard. Expected Behavior 1/ Phone should not...

gitlab.com
[Samsung Galaxy S 5 Unified Development] moreorless:
OK got it. Was my own epic fault :D

I revoked the right of Trebuchet for accessing "notifications" and so there was no notification dot on the apps on messages.

This issue on layer 8 is solved by myself :)
[Samsung Galaxy S 5 Unified Development] ludwig83:
No Sim Card - Service not available / but only after losing Telephone Provider Signal (#3419) · Issues · LineageOS / issues / android · GitLab

Klteactivexx clean flash - Lineage Recovery with LineageOS 18.1 and MindTheGapps. Everytime I lose my Telephone Provider Signal - either in the coutryside or in a garage -...

gitlab.com

...what I did the last 2 weeks or so....

1. Flashed Bootloader - Modem - Firmware from Filehost

Downloads for : Samsung Galaxy S5 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com

did not resolve the issue

2. went back to Stock Rom ...just to be sure that its not a problem of my device....

made a new Backup with TWRP and after that I flashed 18.1 again...

ends up in the same behavior

Mr. @haggertk ...could you please take a look at my problem with the klteactivexx?!
[Samsung Galaxy S 5 Unified Development] grzesiek11:
I responded to your issue on GitLab, but it might be worth it saying it here as well.

TL;DR I have what likely is the same issue, but with a FAT32 partition. My system is also heavily modded, I tested without mods, but I can't be sure. Can you try formatting your SDCard partition as FAT32 to test this?

EDIT: OK, I'm stupid, there is a major difference - the device used - I'm on klte. It would be worth trying anyways though, maybe it's the same issue across different devices. The kernel panic looks the same. Nevermind, this was confirmed on different variants as well.
[Samsung Galaxy S 5 Unified Development] lecorbusier:
SDcard corruption may be caused by a recent Google security patch. I experienced this once with the "new" unofficial LOS17 for the Samsung P605, coming from unofficial 14.1,where this never happened before. But others started complaining about the same issue, after this antique rom got a recent security patch.
[Samsung Galaxy S 5 Unified Development] haggertk:
It's (likely) not. I've found an issue in the legacy paths of the recent sdfat (Samsung exfat driver) revision. I haven't been able to recreate the bug/assert after the fix. After getting a second confirmation I'll upload the merge the change.

Every kernel < 4.8.y that had updated to sdfat 1.4.5 is affected.
[Samsung Galaxy S 5 Unified Development] Vini69:
I have been testing @haggertk sdfat patch for the past 24h and I haven't experienced any spurious reboot nor sdcard corruption so far, whereas normally my phone would reboot several times a day and the sdcard card would generally end up being corrupted.
[Samsung Galaxy S 5 Unified Development] mrmarioman:
getting an error with netflix, won't launch (error 501-99) which according to their website is a problem with the OS.
[Samsung Galaxy S 5 Unified Development] SGS5Korea:
Direct download to sd card causes reboot, is that normal?

This issue has been around since the first build of unofficial lineage os 18.1 on my kltekor.
[Samsung Galaxy S 5 Unified Development] mrmarioman:
i restarted the phone and it gave a "corrupt sd card" notification. i guess that's why netflix (and another app) wasn't working as they're stored in the sd card.

Then I turned off/on the phone and... it's all okay again, sd card working all right. huh.
[Samsung Galaxy S 5 Unified Development] Eadn33:
See Post Nos. 244 and 245 above. Today's update includes a change that may fix your issue.
[Samsung Galaxy S 5 Unified Development] Eadn33:
Just in case someone else experiences the same - I updated my SM-G900V to the 18.1 2021-06-06 build today and the process went fine, but when restarted I had no LTE. Immediately thinking EFS partition problem (had been common for me prior to 17.1) I restored the EFS without success. I double checked Mobile Data was turned on :)and it was. Eventually found that after update the APN had switched to a different provider on its own. Switched back to my provider and works fine again.
[Samsung Galaxy S 5 Unified Development] SGS5Korea:
Ah i see my lovely kltekor receive sdfat update in next build.
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 LineageOS 18.1 Update 2021-06-06

Using the built-in Updater I OTA updated S5 G900M LineageOS 18.1 klte build 2021-05-30 + MindTheGapps + Magisk 23.0 + TWRP 3.5.2_9-0 to build 2021-06-06: everything went smoothly.

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

***
[Samsung Galaxy S 5 Unified Development] MeisterManuel23:
Just updated my klteduos to the latest build and it got stuck at the Samsung boot screen (kernel intialize), I figured that Magisk (23) )was the culprit and now it boots into the system but as soon as I try to reinstall it it gets stuck at the boot screen again. Any advice?

With the previous build (0530) and Magisk 23 everything was working fine.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Fail To Boot with Magisk after Update

Revert to previous working state & disable the "Boeffla-Config autostart" I see in your second screenshot as well as the modules you installed.

See the Magisk script in this post: Failed OTA Update BiTGApps - Script: Capture Bootloop Logcat.

Check the excellent Magisk and MagiskHide Installation and Troubleshooting guide and also the XDA Magisk support thread for help.

***
[Samsung Galaxy S 5 Unified Development] Vini69:
Same story for me on klteduos with lineage-18.1-20210606-nightly-klteduos-signed.zip

- Update from TWRP with Magisk 23 but getting stuck at the Samsung boot screen

- Removed Magisk 23, booting ok but loosing root, retrying with Magisk and getting stuck again at the Samsung boot screen

- Reverting to lineage-18.1-20210530-nightly-klteduos-signed.zip with Kernel patch for sdcard write issue from @haggertk (https://www.androidfilehost.com/?w=files&flid=325822) and Magisk 23, everything's working ok
[Samsung Galaxy S 5 Unified Development] MeisterManuel23:
Should I also apply that sdcard patch you mentioned? If yes, how do I apply it?

So far I had no issues and everything was working fine. In the future it should be merged anyway I guess?

I thought about flashing the previous version and then adding Magisk. That should do it for now
[Samsung Galaxy S 5 Unified Development] Vini69:
Do everything in TWRP as follow:

1- uninstall Magisk (uninstall.zip)

2- Flash lineage-18.1-20210530-nightly-klteduos-signed.zip

3- Flash boot_klteduos_issue-3571_2021-06-03a.img (select image + kernel options)

4- Flash Magisk (so it uses the patched kernel)

5- Clean cache

6- Reboot

If you proceed in this order, everything should work fine, including the sdcard. It does for me.

Also, if you have no audio on sim calls (sim1/slot1) you need to edit /system/build.prop and set the following entry to true:

ro.multisim.audio_follow_default_sim=true

The exfat sdcad patch is already merged in lineage-18.1-20210606-nightly-klteduos-signed.zip (https://review.lineageos.org/311513) but unfortunately this latest build doesn't boot with Magisk on klteduos. I see there are a few more kernel patches since yesterday, we'll have to wait until the next build to check if they have an impact on the boot with Magisk.
[Samsung Galaxy S 5 Unified Development] haggertk:
The additional patches fix security vulnerabilities. I could only hope that they permanently prevent magisk from working, but they should not impact in any way.
[Samsung Galaxy S 5 Unified Development] Not-Aus:
If Magisk stopped working, we'd need another root solution!
[Samsung Galaxy S 5 Unified Development] kurtn:
We already have two root solutions. We have adb root and we have custom recoveries.
[Samsung Galaxy S 5 Unified Development] Vini69:
So far this issue has only been reported by 2 users using the klteduos variant... any one with this issue on other variants with the latest build ?
[Samsung Galaxy S 5 Unified Development] haggertk:
Or, you know, don't bother with rooting in 2021 AD.