[ROM][OFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)

Search This thread
Official LineageOS 18.1 Updates Now Monthly!

Bad news & good news. LineageOS in the recent past supported only 2 Android versions @ the same time because of infrastructure, LineageOS automated builder, servers & volunteer staff limitations and with the current testing and eventual launch of LOS 20.0 (no ETA questions please), all 18.1 supported devices should be on the chopping block.

But this time the devs made an exception. This LineageOS Gerrit Code Review change removed 89 devices from the weekly build roster Drop 18.1 devices:

if maintainers are still active, their devices can be re-added as monthly.
And this change added 57 LineageOS 18.1 devices to the new monthly build roster: "I am alive, but very badly burned". Note that the S5 klte* family is on that lineage-build-targets list! :cool: 👍

Several of those legacy devices like the klte* cannot be promoted to official 19.1 or 20 as explained in LineageOS Changelog 26 - Tailored Twelve, Audacious Automotive, Neat Networking, Devoted Developers > Let’s talk about legacy devices chapter.

You can see the current LineageOS build roster in the hudson/lineage-build-targets on GitHub. At the present there are 105 devices supported with LineageOS 19.1 weekly builds & + the 57 LineageOS 18.1 devices.

An amazing achievement for a volunteer-based organization. ↑ (ツ)

I'm grateful for those LineageOS 18.1 devices that will get about 1 years' worth of monthly Android security bumps & some other changes. ٩(- ̮̮̃-̃)۶
***
 
Last edited:

antistress

New member
Oct 1, 2018
3
2
Hi, I've changed my LineageOS 17.1 for the 18.1 version on Aug 20th, 2022 (clean install) and everything was ok :)
But this week I've did my first 18.1 upgrade to the latest 18.1 (Oct 23rd, 2022) and since I've trouble taking pictures (OpenCamera), screenshots, opening PDF files (default file manager+MuPDF mini).

For instance :
taking a picture : "impossible d'enregistrer la photo"
taking a screenshot : "impossible d'enregistrer la capture d'écran. Les captures d'écran ne sont pas autorisées par l'application ni par votre organisation"
opening a pdf file : "only owner is able to interact with pending item content://media/external/downloads/2735. No document to open". BUT if i choose within the file manager "SD card", then "Download" I can access files that are store there.
can't rename a file store on my SD Card nor on my phone etc.

I've read that using TWRP "Fix Contexts" Function could solve the problem but I don't have this function in my Recovery ( https://www.reddit.com/r/LineageOS/comments/7k1thi )

Thanks !
 
Last edited:
  • Like
Reactions: vlad3647

uglylove

Member
Jun 23, 2021
11
2
Hi, I've changed my LineageOS 17.1 for the 18.1 version on Aug 20th, 2022 (clean install) and everything was ok :)
But this week I've did my first 18.1 upgrade to the latest 18.1 (Oct 23rd, 2022) and since I've trouble taking pictures (OpenCamera), screenshots, opening PDF files (default file manager+MuPDF mini).

For instance :
taking a picture : "impossible d'enregistrer la photo"
taking a screenshot : "impossible d'enregistrer la capture d'écran. Les captures d'écran ne sont pas autorisées par l'application ni par votre organisation"
opening a pdf file : "only owner is able to interact with pending item content://media/external/downloads/2735. No document to open". BUT if i choose within the file manager "SD card", then "Download" I can access files that are store there.
can't rename a file store on my SD Card nor on my phone etc.

I've read that using TWRP "Fix Contexts" Function could solve the problem but I don't have this function in my Recovery ( https://www.reddit.com/r/LineageOS/comments/7k1thi )

Thanks !
Probably, you have file_contexts file issue after upgrade ROM. file_contexts are saved in root on our devices.
I assume you have file_contexts.bak too on your root. If it's, remove file_contexts and change name of file_contexts.bak to file_contexts.
Best solution for me compare with those files manually and edit file_contexts header of external storage with file_contexts.bak on your root.
 
Last edited:

antistress

New member
Oct 1, 2018
3
2
Probably, you have file_contexts file issue after upgrade ROM. file_contexts are saved in root on our devices.
I assume you have file_contexts.bak too on your root. If it's, remove file_contexts and change name of file_contexts.bak to file_contexts.
Best solution for me compare with those files manually and edit file_contexts header of external storage with file_contexts.bak on your root.
Thanks
But how can I access that file ? If I plug my phone via USB I can only see my SD card, and the same If I use default file manager (com.android.documentsui)...
 

Boatshow

Senior Member
Been using my S5 as a spare alarm clock. Anyone else having problems with the alarm not firing? I think it's affected by deep sleep/doze. When literally nothing else is running in the background I noticed the alarm can fire extremely late or it only fires whenever I wake the phone.

A few months ago I upgraded to a T-Mo Pixel 4A 5G with <30 charge cycles for $175. Just had to coax T-Mo to unlock the phone, took about a week. I installed LOS + Advanced Charge Control to cap the battery to 75%. It has backwards design features associated with newer phones but I've been happy. If you're in the market for an affordable plastic phone with 3.5mm, VOLTE and long support cycles I bet most people here won't hate it.

Thanks
But how can I access that file ? If I plug my phone via USB I can only see my SD card, and the same If I use default file manager (com.android.documentsui)...
You need root privileges to do this inside Android. If you're not sure, just boot into TWRP and the file manager should have root. If that doesn't work you can also open a terminal in TWRP.
 

nilpernil

Member
Dec 25, 2014
19
8
Barcelona
I came here to ask for the updated, I tought the s5 will be discontinued, but I'm happy this is not the case!!

I use my S5 to watch youtube vanced from the bed and as my alarm clock, i love it, it has the perfect size for that, I can hide behind the blanket like if I was 9 and start watching youtube till falling asleep ☺️☺️


Thanks to the dev's for maintaining the s5 and thanks lineage os too ❤️❤️❤️
 

antistress

New member
Oct 1, 2018
3
2
Thank you uglylove & Boatshow : I'll kept your tips for the next time, it will be useful for me. As for now, monthly update solves the problem without further intervention ! :)
Thanks again
 
  • Like
Reactions: vlad3647

jian1

Senior Member
Apr 14, 2014
54
1
So can I safely jump into this LineageOS thingy for S5 now? I don't want a buggy android experience and that was the main reason why I haven't flashed S5 for LineageOS....
 
Camera quality has nothing to do with Magisk and not running apps can be made to run with Magisk.
You misunderstood. I was referring to banking apps. Magisk can be detected, Zygisk or not. Don't use Magisk if you need banking apps, it just causes a lot of additional issues and a version later the apps devs found out how to detect rooted devices again. But okay, if you still want to live dangerously and have a potentially insecure and defunct device, go ahead.
 

wuko

Member
Feb 12, 2021
20
8
Hallo.
S5,klte: no problems
suggestion: for nationwide alerts by CB
there should be the same notifications like normal SMS (tone,led,vibration) not only vibration.
 

vanMacG

New member
Dec 16, 2021
4
2
Then you are lucky. I've heard from several people using the S5 with 18.1 who had no alert. Since I retired that phone in favor of Vayu, it's not my problem anymore. But it's the problem of all other users where that won't work. Just saying.
I just wanted to mention that it worked for me with 18.1, so it's not a problem in general.

Hallo.
S5,klte: no problems
suggestion: for nationwide alerts by CB
there should be the same notifications like normal SMS (tone,led,vibration) not only vibration.
I had a different sound than normal SMS + vibration. I think this behviour is intended, it should alarm you, not sound like a normal SMS...
 
  • Like
Reactions: x2k13

zimral.xda

Senior Member
@haggertk Cell Brodcast national disaster warnings don't work on LineageOS 18.1 (at least on the S5) in Germany (they had a nationwide CB test earlier). This needs to be fixed soon, since that is a vital function for peoples safety.
As far as i can see, this german "cell broadcast national disaster warning day" was a total DISASTER! There were mixed results from region to region, provider to provider and phone to phone. I have a total of five phones two actual Pixel5, one P4a, all have either Stock A13 or A13 based CalxyOS, and one 2016 iphoneSE with IOS 15.7. All had these alerts enabled but only an old (2017) Huawei P10 with a vodafone sim card received the alert. As far as i have infos out of the neighbourhood, mostly german Telekom (T-mobile) was not able to transmit this alert.
The CB "technology is at least 20 yeras old. It is unbelieveable, germany becomes a third world country more and more each day.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Hello,

    I don't use a SIM card on my S5. If Airplane mode is left on when rebooting or from a cold boot, 5Ghz Wi-Fi networks will not be visible unless Airplane mode is toggled again. I've been using my phone for a while now and thought the hardware might fail anytime. A quick google search leads me to this Reddit post from two years ago. The OP found a workaround as described above. Galaxy S5 and Lineage OS 18.1 as well.

    A quick search from here doesn't seem to show the bug reported. A quick dirty fix for this maybe is to automate the toggling of Airplane mode.
    1
    @curiousrom Does this method still work with the latest Magisk?

    Yes.
    ***
  • 46
    2okPze5.png



    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps) . LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

    Device source code:
    Kernel source code:

    Build Compatibility:
    The noted models are the only ones supported. If you have a model that isn't listed and ask politely then I might work to add compatibility.
    BuildModel
    klteSM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8
    klteactivexxSM-G870F
    klteaioSM-G900AZ, SM-S902L
    kltechnSM-G9006V, SM-G9008V
    kltechnduoSM-G9006W, SM-G9008W, SM-G9009W
    klteduosSM-G900FD, SM-G900MD
    kltedvSM-G900I, SM-G900P
    kltekdiSC-04F, SCL23
    kltekorSM-G900K, SM-G900L, SM-G900S

    Downloads:
    Installation Instructions:
    Reporting Bugs:
    Compatibility Notes:
    • Bootloader version doesn't matter. Anyone who tells you so doesn't know what they are taking about. My Developer Edition G900V is still running the original 4.4.2 KK aboot. My G900W8 is running the latest 6.0.1.
    • All builds except for klteactivexx and klteaio MUST be running a marshmallow (6.0.1) radio for RIL to work. If you are about to report that RIL/radio isn't working then I pretty much guarantee this is your issue.
    • You MUST be running a marshmallow (6.0.1) NON-HLOS for the fingerprint reader to work. If you are about to report a fingerprint reader problem then you either have old firmware (update it), your /data was previously encrypted and you performed a "clean" flash without FORMATTING /data (start over and FORMAT /data), or your reader is just broken.
    • 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.
    • The latest TWRP seems like it works, but if someone has issues then perhaps try using the actual supported recovery.
    Donations:
    • I absolutely don't personally accept them. If you really feel that this work deserves it, then find a local food bank or animal shelter/rescue and throw some money their way. You can also throw some the way of LineageOS, but we're actually doing pretty well right now.
    11
    Merry Christmas to you @haggertk and the Lineage team. Thanks for your work throughout the year. All the very best to everyone for 2022
    11
    Official LineageOS 18.1 Updates Now Monthly!

    Bad news & good news. LineageOS in the recent past supported only 2 Android versions @ the same time because of infrastructure, LineageOS automated builder, servers & volunteer staff limitations and with the current testing and eventual launch of LOS 20.0 (no ETA questions please), all 18.1 supported devices should be on the chopping block.

    But this time the devs made an exception. This LineageOS Gerrit Code Review change removed 89 devices from the weekly build roster Drop 18.1 devices:

    if maintainers are still active, their devices can be re-added as monthly.
    And this change added 57 LineageOS 18.1 devices to the new monthly build roster: "I am alive, but very badly burned". Note that the S5 klte* family is on that lineage-build-targets list! :cool: 👍

    Several of those legacy devices like the klte* cannot be promoted to official 19.1 or 20 as explained in LineageOS Changelog 26 - Tailored Twelve, Audacious Automotive, Neat Networking, Devoted Developers > Let’s talk about legacy devices chapter.

    You can see the current LineageOS build roster in the hudson/lineage-build-targets on GitHub. At the present there are 105 devices supported with LineageOS 19.1 weekly builds & + the 57 LineageOS 18.1 devices.

    An amazing achievement for a volunteer-based organization. ↑ (ツ)

    I'm grateful for those LineageOS 18.1 devices that will get about 1 years' worth of monthly Android security bumps & some other changes. ٩(- ̮̮̃-̃)۶
    ***
    10
    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.
    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.
    9
    S5 LineageOS 18.1 Update 2021-05-09 - Security Bump, Camera U.I. Fix & Kill App Option

    Using the built-in Updater I OTA updated S5 G900M LineageOS 18.1 klte build 2021-05-02 + MindTheGapps + Magisk 22.1 + TWRP 3.5.2_9-0 to build 2021-05-09: everything went smoothly & GApps + Magisk survived the update.

    There are a bunch of changes as you can see in https://download.lineageos.org/klte/changes/ but of note:

    After the automatic reboot as seen in the screenshot > Settings > About phone > press on Android version > Android security update: May 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 - May 2021 for details about the security fixes.

    With the change Snap: use translucent control background on 16:9 the stock camera is showing the full frame preview again (screenshot). There are other minor Camera changes.

    Interesting also there is a new Kill foreground app option in > Settings > System > Buttons > for Home, Back & Recents buttons which is useful when an app is frozen or you want to prevent it from using some RAM in the background (screenshot). Note that it may make it slower to open that killed app the next time you want to use it.

    BTW you can create a direct link to Updater & much more with the LineageOS Settings widget. I stacked a few of them on Home to create a LineageOS shortcut folder for quick access.

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