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

Search This thread
QR Codes Scanning Issue





What happens if you use the stock Camera app to scan the QR codes?

Try with the S5 further away and using the telephoto to zoom in.
***
The QR reader of the stock camera app works, always did. But it seems that a lot of apps use a different method to activate the QR reader or use a different library. Unfortunately it's not so easy to find out what they use because of closed source code.

Furthermore, QR codes on e.g. scooters are like 2x2 cm in size and with the S5 being further away doesn't work at all because all you get is a blurry white and black something. And there's no zoom function.
 
Last edited:
  • Like
Reactions: curiousrom
Hello Guys, anybody knows how to enable native call recording with Magisk?

For people looking for a workaround if you are currently in a location where call recording is illegal or requires 2 party consent, the simple & free Axet's Call Recorder Module for Magisk works to record both side of the conversation.
***
 
  • Like
Reactions: bmwdroid

Skulldron

Senior Member
Jan 29, 2016
308
422
Galaxy S5 LTE (SC-04F/SCL23) (kltekdi) Charging Fix



Thanks for the pointer. :cool: 👍

It got me searching the Changes for kltekdi >>> ARM: configs: lineage_kltekdi: Re-enable CONFIG_EXTCON by dev haggertk:



Next build with that change should be on 2023-02-18 if all goes well with the LineageOS automated builder.

I wonder if you guys still have an S5 kltekdi: @Skulldron @solarisintel123 @Hamza Shahbaz @ArvixxBesin @vd6x @gw1024gb @hk133hk @Jesus Army @tortnoise @EojjN @omegoz .

Seem like this guy had the right fix pointer all along, way back on Nov 28, 2021:


***
I was the user report XD. Already tested and confirmed dont worry :)
 
  • Like
Reactions: curiousrom

djdisodo01

Member
Apr 29, 2018
44
9
i found that qr code reader on firefox also doesn't work properly
this one has open source so it may help finding it out
 

wuko

Member
Feb 12, 2021
23
8
Hi,
klte,TWRP3.7.0.normaly I use the recovery.IMG for an OT systemupdate and then reflash TWRP. is there an oportunity for an OT update with TWRP??
 

jian1

Senior Member
Apr 14, 2014
58
1
So is this firmware really stable now? I am still stuck with A6.0.1 that came originally with the phone...
 

Lederhose

Member
Apr 29, 2016
26
2
I have sent large files with Whatsapp and now the phone's internal memory is full. Whatsapp saves all sent and received data in a folder in user memory: /sdcard/Android/media/com.whatsapp/Whatsapp/Media/, but in there are only a few images etc. left. The system must have moved most files somewhere where I can't access them.
I have seen this Whatsapp folder content getting moved before when I filled the memory up with large files as browser downloads and everything got moved back as soon as I deleted the downloads.
Now the system settings app info shows that Whatsapp uses 4GB, but Whatsapp itself also can't access its files as the storage manager built into Whatsapp only shows a few MB. I want to delete only the large sent files from the Whatsapp folder; where do I find those now? I can access the whole file system with the TWRP file manager.
 

kurtn

Senior Member
I have sent large files with Whatsapp and now the phone's internal memory is full. Whatsapp saves all sent and received data in a folder in user memory: /sdcard/Android/media/com.whatsapp/Whatsapp/Media/, but in there are only a few images etc. left. The system must have moved most files somewhere where I can't access them.
I have seen this Whatsapp folder content getting moved before when I filled the memory up with large files as browser downloads and everything got moved back as soon as I deleted the downloads.
Now the system settings app info shows that Whatsapp uses 4GB, but Whatsapp itself also can't access its files as the storage manager built into Whatsapp only shows a few MB. I want to delete only the large sent files from the Whatsapp folder; where do I find those now? I can access the whole file system with the TWRP file manager.
That issue us off topic here. But uf i search large files or folders, i do it with DiskUsage app.
 

Lederhose

Member
Apr 29, 2016
26
2
That issue us off topic here. But uf i search large files or folders, i do it with DiskUsage app.
I used X-plore for that but the files were nowhere to be found (in the user accessible file system). I have deleted some other files to get at least about 500 MB free and rebooted into recovery to search a bit manually in the root file system with the rudimentary TWRP file manager, but couldn't find them. Now when I checked again with X-plore the files were suddenly all back again in the usual Whatsapp folder, as mentioned in my first post.
I guess this is a bug in the memory management of the system, maybe somehow cured by rebooting. Maybe also connected to the bug where Playstore and other app installers fail to install, stating lack of free memory, despite lots of free space available, which is also "fixed" by rebooting the device, as discussed before in this thread.
 

kurtn

Senior Member
I used X-plore for that but the files were nowhere to be found (in the user accessible file system). I have deleted some other files to get at least about 500 MB free and rebooted into recovery to search a bit manually in the root file system with the rudimentary TWRP file manager, but couldn't find them. Now when I checked again with X-plore the files were suddenly all back again in the usual Whatsapp folder, as mentioned in my first post.
I guess this is a bug in the memory management of the system, maybe somehow cured by rebooting. Maybe also connected to the bug where Playstore and other app installers fail to install, stating lack of free memory, despite lots of free space available, which is also "fixed" by rebooting the device, as discussed before in this thread.
Do you use sd card as adopted storage? That's often buggy.
 

mostafa3bdou

Member
Jul 8, 2022
25
6
Hello Guys, Did anyone face any problem after applying daylight saving time?
I see my mobile clock didn't update the time automatically, is there any solution for that?
 

Alu-Digital

New member
Apr 27, 2023
2
1
Hi, everybody!

First of all, @haggertk, thank you for your amazing work!



ISSUE

Samsung Galaxy S5 klte-duos (Model SM-G900MD) restarting during the boot or a few moments after a boot complete if LTE is enabled.


CENARIO

- I have 03 (three) Samsung Galaxy S5 klte-duos (Model SM-G900MD).
- Everything was working fine until two or three updates ago (Feb/2023 or Mar/2023, maybe Jan/2023).
- After the update, if the SIM card is inserted AND LTE is enabled, the phones will restart during the boot or a few moments after a boot complete.
- All three units are having this problem and it started at the same moment.
- It doesn't matter if the phones only have LOS installed or has other apps installed (MicroG, for example).
- The carrier's network signal is always present and good.

- Removing the SIM card, the problem stops.
- Keeping the SIM card, but disabling LTE, the problem stops.
- Keeping the SIM card and enabling ONLY LTE, make things worse: the phone reboots more rapidly.

- According to www.frequencycheck.com, this phone is totally compatible with LTE and my carrier in Brazil (https://www.frequencycheck.com/carr...s5-duos-4g-lte-a-samsung-pacific/claro-brazil)


WHAT I'VE TRIED SO FAR TO SOLVE THE ISSUE

- I looked for a similar problem and solution as much as I could (XDA Dev, Reddit, stackoverflow, etc)
- I followed all the steps during the updates.
- I reinstalled LOS three or four times, as if doing a version upgrade, following all the steps on the LOS website.
- I tried using the second SIM card slot
- I put a piece of paper over the SIM card to make it thicker, imagining a bad contact problem.
- I tested with 3 different SIM cards, from different carriers, including a brand new SIM card.
- I tested these SIM cards on a Motorola G7 Power. Everything worked out fine on G7.
- Disabled WIFI
- Changed batteries. I have 6.
- Changed network settings to GSM and WCDMA (stops problem), GSM only (stops problem) and LTE only (makes worse, as mencioned above)

The problem persists on all phones.


WHAT I'VE TRIED SO FAR TO BYPASS THE ISSUE

Set network to GSM only.
I tried this command "adb shell settings list global | findstr preferred" and the output was:
preferred_network_mode1=9
preferred_network_mode2=9
preferred_network_mode3=11
preferred_network_mode=1
(More info at https://stackoverflow.com/questions/25319129/how-to-change-preferred-network-type-over-adb-android)

Then I tried all four commands below. Only the first one wasn't enough.
adb shell settings put global preferred_network_mode 1
adb shell settings put global preferred_network_mode1 1
adb shell settings put global preferred_network_mode2 1
adb shell settings put global preferred_network_mode3 1

As expected, the settings became:
preferred_network_mode1=1
preferred_network_mode2=1
preferred_network_mode3=1
preferred_network_mode=1

After this, the reboots stopped.


WHAT I DIDN'T TRY YET

- Return the phone to stock rom. It didn't seem useful, because everything had been working fine for years.
- Flash the boot.img file presented on the LOS Klteduos download builds page. There is no instruction to do so.


WHAT I AM ASKING

How to get LTE working again without starting continuous reboot?


Thanks!
 
Last edited:
  • Like
Reactions: curiousrom

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    it is impossible that it does not go into download mode you have to hold down power + home + volume down for a few seconds until you feel it vibrate with odin connected
    1
    Hello. I'm having issues with a G900P that won't let me make calls. Yesterday, when I installed the ROM, it allowed me to make calls, but today, when I try to call, it restarts the network, and when the call ends, it reconnects to the network.
    Switching networks is normal for custom ROMs on Samsung. They don't have VoLTE to make calls in 4G network. So they switch to 2G/3G for calling.
    1
    Love the S5 but the battery drain issue is forcing me not to use this device. I have the G900T variant and the battery drains very fast. I have other batteries but still the same result. Anybody got some suggestions? Thank you in advance.
    I can use my G900F at least one complete day before charging it. If the screen is ON, battery last 3 hours. I don't have any Google Apps.
  • 49
    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: 👍
    ***