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

[curiousrom]

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!

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. ٩(- ̮̮̃-̃)۶
***

 

[antistress]

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 !

 

[uglylove]

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.

 

[antistress]

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]

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.

 

[Lederhose]

Edit: Just read that updates are now monthly.

 

[nilpernil]

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

 

[kurtn]

Updated klte to November security patch release. Monthly 18.1 builds seem to run stable

 

[antistress]

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

 

[jian1]

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....

 

[kurtn]

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....

It's not buggy. Maybe you get a small degradation in camera quality. And some very security sensitive apps will not run. Like video streaming or banking

 

[x2k13]

It's not buggy. Maybe you get a small degradation in camera quality. And some very security sensitive apps will not run. Like video streaming or banking

As long as it's an official ROM and you're not messing around with Magisk this shouldn't happen.

 

[Not-Aus]

As long as it's an official ROM and you're not messing around with Magisk this shouldn't happen.

Camera quality has nothing to do with Magisk and not running apps can be made to run with Magisk.

 

[x2k13]

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.

 

[x2k13]

@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.

 

[vanMacG]

@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.

Worked on two S5 without a problem for me.

 

[x2k13]

Worked on two S5 without a problem for me.

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.

 

[wuko]

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]

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...

 

[zimral.xda]

@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.