yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] Sub_Zero2:
Edit: My default setting was GSM/WCDMA/LTE.

Selecting GLOBAL gives me the same result.

Interesting enough, selecting WCDMA/LTE gives "cellular network not available" upon making a call (so no hsdpa either during calls).

So it seems to be what [MENTION=4122877]curiousrom[/MENTION] pointed out it might be: A limitation in my network provider's network. Althought I've used my provider for years, I've just recently moved houses to a area which is the opposite of heavy populated. The limitation in the network might be to the base station I'm currently connected to. I'll try to test more later in another geographic area to try to confirm this theory.
[Samsung Galaxy S 5 Unified Development] Sub_Zero2:
Yes, it seems i was right. In a more populated area HSDPA is available during calls. Definately not a rom problem. Cheers everyone.
[Samsung Galaxy S 5 Unified Development] jdrch:
Is there going to be a new development thread since this one is named 16.1, or will the conversation continue here?
[Samsung Galaxy S 5 Unified Development] curiousrom:
I would say here for now.

I asked [MENTION=2693412]haggertk[/MENTION] 6 days ago if he could create a 17.1 thread but no reply so far.

Will PM him later today & also ask the OP of this thread who is retired & sold his S5 to ask if he could transfer thread ownership so we could change the topic & update the OP.

***
[Samsung Galaxy S 5 Unified Development] kurtn:
Non-official microG fork updated to 17.1

https://download.lineage.microg.org/klte/
[Samsung Galaxy S 5 Unified Development] curiousrom:
MicroG is Not Supported by LineageOS

It's important to note that the MicroG variant ROMs & their signature spoofing hacks + other mods are not official & not supported by LineageOS! :eek:

***
[Samsung Galaxy S 5 Unified Development] Username already in use:
Will wake on proximity be added to 17.1? I find this useful for minimizing wear on the hardware buttons. Tap to wake would be even better. Wasn´t this a feature back in Oreo (15.1)?

Thank you for keeping S5 alive!
[Samsung Galaxy S 5 Unified Development] lecorbusier:
Tap to Wake requires hardware support.

On my very first Android device, a tablet, there was only the power button to resume from standby and it being part of the main pcb i didn't want to wear it out. I had hope that you somehow could switch off the display or its backlight (TFT) and keep the touchscreen live, but to no avail.
[Samsung Galaxy S 5 Unified Development] 761gg1i3219:
Since upgrading to 17.1 the mic level problem has come again

Hey man, sorry to bother you again. Since I updgraded to 17.1 I had the same issue with mic recording.

I tried many things but cannot solve it:

When I manually edit with Amaze File Manager with root permissions /system/vendor/etc/mixer_paths.xml setting main mic level to 118 and then save it, as soon as I close the file the changes are reverted, if I open it again it shows the level at 95.

I then tried editing it with vim on Termux but it says the file is unwritable.

So I tried remounting /system as RW but it says it is not in /proc/mounts.

Then I tried mounting / (root) as RW and that works but nothing changes for mixer_paths.xml being unwritable.

At last I tried flashing your zip to set main mic volume at 118 but that doesn't work: mixer_paths.xml shows again 95 as level and there's no 52-mixer-paths.sh in /addon.d

I don't know what else to do, I was so happy after all this time to have found a solution to low volume recordings.

If you could help me I would be really thankful to you sir.
[Samsung Galaxy S 5 Unified Development] guest4711:
Because LOS 17 is SAR (system as root) you cannot mount /system r/w in normal mode.

So you could either

- use magisk to replace the file systemless (by mounting it over)

or

-prepare your own version of mixerpath.xml in /sdcard. Then use TWRP to mount system r/w in TWRP and copy it in place use the integrated filemanager.
[Samsung Galaxy S 5 Unified Development] 761gg1i3219:
Ok I tried but now when I try to record something in whatsapp or camera to record a video it says it can't start the recorder.

What I did:

-Reboot in Recovery Mode (TWRP 3.4.0)

-Mount -> check System

-Advanced -> Terminal -> mount -o rw,remount /system

-cp /sdcard/mixer_paths.xml (the file I modified) /system/vendor/etc

-mount -o ro,remount /system

-Reboot system

EDIT: I also noticed I cannot play any audio, it seems like the system is not reading mixer_paths.xml anymore
[Samsung Galaxy S 5 Unified Development] curiousrom:
Did you try the TWRP flashable zip found in my post linked above?

***
[Samsung Galaxy S 5 Unified Development] guest4711:
Have a look onto permissions and on the fileformat. You probably edited it on Windows and inserted DOS linefeeds (^M) instead of <CR><LF>?
[Samsung Galaxy S 5 Unified Development] 761gg1i3219:
Yeah, as I said in the first post I tried flashing it but again the mixer_paths.xml was showing 95 as volume for main mic and there was no 52_mixer-path.sh in addon.d even though the TWRP log said everything went well.

---------- Post added at 05:58 PM ---------- Previous post was at 05:54 PM ----------

I checked for permission mismatching but everything was normal.

I did not edited it on Windows, I copied it from /system/vendor/etc and edited it with Amaze File Manager text editing feature directly on the phone so I don't think that was the problem either.

For now, in order to have a functioning system I had to flash last update's zip. But the low volume recording problem remains unsolved.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Sorry, busy @ the present & did not take the time to read your post above fully.

Thanks for replying. :good:

***
[Samsung Galaxy S 5 Unified Development] 761gg1i3219:
No need to say sorry man, thank YOU for trying to help!
[Samsung Galaxy S 5 Unified Development] bersem:
New nightly is up.
[Samsung Galaxy S 5 Unified Development] curiousrom:
17.1 2020-10-18 Update

Only 2 changes in lineage-17.1-20201018-nightly-klte-signed.zip if you have official lineage-17.1-20201011 already installed & I am not sure that the android_packages_apps_TvSettings one applies to the S5 as you can see in https://download.lineageos.org/klte/changes/

Since that page changes all the time I attached a screenshot for posterity.

It's not necessary to install every updates if they don't have some significant changes. Many users update only one a month after the Android security bump is merged: https://review.lineageos.org/q/bump+security

OTOH that may be good to test how the updating process goes. If you report please specify the recovery version you have on your S5, Gapps & Magisk if any & if it's encrypted or not. :cool:

**
[Samsung Galaxy S 5 Unified Development] bersem:
Updated my KLTE through TWRP 3.4.0-0 not rooted , gapps and my phone isnt encrypted.

Regards !
[Samsung Galaxy S 5 Unified Development] curiousrom:
Thanks for the report but the LineageOS klte package for the S5 is a unified ROM & supports all those models: SM-G900AZ, SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L.

So which model exactly? ;)

***
[Samsung Galaxy S 5 Unified Development] bersem:
Lool there is only one klte or not? Intl. SM-900F ( signature ? )
[Samsung Galaxy S 5 Unified Development] curiousrom:
Humm... "SM-900F" that model does not exist. ;)

Technically only the S5 SM-G900F has the codename klte but the LineageOS klte ROM supports different models as you can see in https://wiki.lineageos.org/devices/klte

My S5 G900M codename is klteub but it is supported by the LineageOS klte ROM.

OTOH I can't install the Samsung stock OS for the G900F on it nor it's specific modem & bootloader packages.

The S5 G900V which is also supported by the klte ROM is a cdma phone with a locked bootloader that has it's own set of problems & preferred network settings.

So when reporting a bug or something it's better to say the model, the LineageOS version & it's build date as the minimum troubleshooting info.

For example: S5 G900M LineageOS 16.0 klte build 2020-09-20 (info which I cut & paste from a reference doc I keep for posts).

The signature info is not trustable because if you update it all the signatures in all your previous posts will also be updated on XDA & you may have more than one S5 variant.

Also when you quote a post like I just did above the signature is not included.

***
[Samsung Galaxy S 5 Unified Development] 761gg1i3219:
Sudden loss of connection

I am using 17.1

I was at home yesterday connected to the wi-fi. I opened Fennec to read the news but couldn't connect, so I switched off wi-fi and tried again with mobile data but no luck.

I then noticed there's an X near the empty Wi-Fi icon (even though in setting it says the signal strength is excellent) and an X near the Mobile signal (even though it is not empty and there's LTE written above it as usual).

I tried many things, including resetting all network settings and reconnecting to the wi-fi but nothing changes.

I then enabled verbose logging in developer options and under wi-fi name it says:

(NETWORK_SELECTION_PERMANENTLY_DISABLED) NETWORK_SELECTION_DISABLED_NO_INTERNET_PERMANENT=1

The weirdest thing is on mobile data I can receive and send messages in whatsapp and telegram but everything else with the internet does not work (browse the web, sync emails, etc).

I tried searching for this messages on the internet but had no luck.

I was doing nothing while this happened and the only thing I changed yesterday on the phone is that I moved stuffed to the sdcard through Settings > Storage > SD Card > Migrate Data

Can someone please help me troubleshoot this?

EDIT: I also tried connecting to another wi-fi hotspot and it says the same thing
[Samsung Galaxy S 5 Unified Development] AloneDisaster:
Thanks for author and community

Kltekor (g900k)

Lineage OS 17.1 Official 20201015

Pico GApps

Tuned Kernel 20200521

Boeffla Undervolting light

29% constant brightness

Powersaver profile on setting
[Samsung Galaxy S 5 Unified Development] blikkk:
Use private DNS?

Adguard server sometimes fault.
[Samsung Galaxy S 5 Unified Development] 761gg1i3219:
I am using Adguard but through Dnscrypt-proxy Magisk module and I also have Cloudfare as backup DNS.

I tried disabling it but nothing changed. Still same error.
[Samsung Galaxy S 5 Unified Development] bersem:
U tried static ip config ?
[Samsung Galaxy S 5 Unified Development] 761gg1i3219:
It works, but why?

It connects to the wi-fi and the Xs near the wi-fi and mobile icons disappear. I don't know how to set static IP for mobile data to test it though.

I'm glad it's not an hardware problem but why does it work? What's the problem with DHCP that suddendly doesn't work?

Hope to find a way to go back to normal because I can't even use dnscrypt this way or mobile data for something that isn't whatsapp or telegram.

Really appreciate your help man, if you know how to help me further that'd be great. :good:
[Samsung Galaxy S 5 Unified Development] bersem:
If u can make a clean flash to be sure otherwise check your router settings. Maybe u have to change your IP range, broadcasting channel. What about other devices in your network ? Same ? DHCP assign works ?

According your statement that the mobile data not working too hmmm... But i think its not a hardware fault of your S5. Something ( corrupt ) blocks your traffic out or your router.

Hope it helps

Regards !
[Samsung Galaxy S 5 Unified Development] blikkk:
Use terminal, command: ping 1.1.1.1

Is there an answer?
[Samsung Galaxy S 5 Unified Development] 761gg1i3219:
I have no problems with other devices, and even my S5 was working fine then suddendly stopped working while idle.

I will try make a clean flash and see if it solves the problem.

Thank you for your help.

---------- Post added at 10:25 AM ---------- Previous post was at 10:22 AM ----------

While using DHCP with the errors I reported no answer.

In the static IP config to make it work I set 1.1.1.1 as DNS.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: Sudden loss of connection

Your second post adds essential relevant troubleshooting info that should have been included in your first post about your problem IMO.

You tried to disable what exactly?

Remove the module, disable Adguard, undo the DNS change, forget the WiFi network in Settings & reboot to see if the problem is solved.

***
[Samsung Galaxy S 5 Unified Development] 761gg1i3219:
Should've explained better: I am using the dsncrypt-proxy Magisk Module which lets you list some DNSs to connect to, in my list there's Adguard DNS, Adguard DoH DNS and Cloudfare.

I already tried to disable the module and forget the wifi network and reconnect but, as I said, nothing changed.

The only thing that worked was using static IP.

Anyway I am doing a clean install now and see what happens.
[Samsung Galaxy S 5 Unified Development] 761gg1i3219:
Update on connection loss

A little update on the situation: I clean flashed the OS, installed all the apps I had previously (including all Magisk modules) and everything works fine by far.

Hoping everything keeps working, the error I had remains a mystery.

Thanks a lot to all the people who helped me!
[Samsung Galaxy S 5 Unified Development] dcarvil:
I had the same problems with mixer_paths.xml you did. I finally rolled my own Magisk module as follows:

In /data/adb/modules, create directory mixer_paths/system/vendor/etc/. (I had to use Termux to create the directories. For some reason, my file manager could not create them.) Place your edited mixer_paths.xml file in that directory. In /data/adb/modules/mixer_paths, create a module.prop file with the contents:

id=<string>

name=<string>

version=<string>

versionCode=<int>

author=<string>

description=<string>

Reboot, and you should be using the edited mixer_paths.xml. See https://github.com/topjohnwu/Magisk/blob/master/docs/guides.md#magisk-modules for more info on Magisk modules.

The mixer_paths directory structure should look like this:

├── mixer_paths

│** ├── module.prop

│** └── system

│***** └── vendor

│******** └── etc

│*********** └── mixer_paths.xml
[Samsung Galaxy S 5 Unified Development] 761gg1i3219:
I will try that immediately!

This method should resist updates right?

Because actually I was successful in changing mixer_paths.xml yesterday night and wanted to report here: I used TWRP terminal to mount /system as RW, changed the file with vi and then remount /system as RO, but I guess this process has to be done after every update.
[Samsung Galaxy S 5 Unified Development] Hawaiihemd:
I'm just starting with 17.1 coming from 15.1. A few aesthetic complaints aside it's running pretty slick I think. But I seem to have run into a bug with the camera app.

My setup is as follows:

ROM 17.1-20201018-NIGHTLY-klte

Build lineage_klte-userdebug 10 QQ3A.200805.001 1b83b07703

Baseband G900FXXS1CQA9

Recovery TWRP-3.4.0

OpenGapps pico 2020-Oct-21

Magisk 20.4

Clean install after formatting data.

When I take a photo with the standard camera app set to internal storage, the picture is taken and saved to /storage/emulated/0/DCIM/Camera as expected.

When I set the app to external storage, the app behaves as if it did take the photo, the snapshot in the lower left corner it's updated, but no file is saved to /storage/--id--/DCIM/ or any subdirectory.

App permission for storage is given. But the app did not ask for write permission to the external storage as other apps do the first time you try.

Any ideas? Can anyone reproduce?

Thanks in advance.
[Samsung Galaxy S 5 Unified Development] dcarvil:
Yes, this method will survive updates, as long as the data partition is not wiped. The TWRP method will not.
[Samsung Galaxy S 5 Unified Development] kurtn:
There are many official bug reports about that behaviour. Workarounds are

- use internal storage

- use other camera app

- use other gallery app
[Samsung Galaxy S 5 Unified Development] curiousrom:
17.1 Path of Taken Photos - External Storage

Tap on the photo preview in the Camera app (thumbnail after taking a photo) then 3-dots > Details & you will see where the photo is saved when external storage is selected.

Same when viewing in Gallery > Files album > photo > 3-dots > Details.

Since LineageOS 16.0 the path was changed to /storage/{Micro SD Card ID}/Android/data/org.lineageos.snap/files/ .

S5 maintainer haggertk said in this bug report Snap (camera) when selecting SD stores somewhere where not visible in Gallery (after restart) "This storage location is on purpose for P: https://github.com/LineageOS/androi...mmit/9b4755c0ce090a14dfb7599a238b044dcdfd5ee4 ":

"...Android P not allow apps to write/read SD Card public area and

only allow apps to access the application private area. So save

to specific path."

I'm still on 16.0 so can't check that on 17.1 @ the present.

***
[Samsung Galaxy S 5 Unified Development] Hawaiihemd:
Well I guess that's what I get for being inactive for about three years. I had no clue. :o

Thanks guys.
[Samsung Galaxy S 5 Unified Development] rootkitty:
Charging Problem / Battery % Usage

I went throght the calibration procedure and when I restart the phone it shows about 92%., so I guess the battery isn't 100%, but it seems to have a resaonable amount of life (several hours of run time and about what would be expected for a 2 year old battery).

The % remaining guage behaves strangely, the rundown seemed reasonable, but at the end I had about an hour of run time left at when the guage was showing <10%. In the past the phone would die fairly quickly once the level go that low. I was suspecting a calibration issue because it was looking like the % remaining number should have been about 8-10% higher.

When I have the phone sitting on my desk plugged in to the charger, I can get it to charge to 100% byusing caffine to keep the screen active, but if I let the screen blank and don't touch the phone, charging tends to stop when fully charged (as expected), but doesn't resume again. Previously the phone would intermittently apply short brusts of charge to keep the battery topped up. Now if I leave the phone on my desk overnight, in the morning I find that the battery is run down to about 50%. I have a charger that shows current draw and when I have been watching it it reads zero amps, which tells me the phone isn't trying to charge.

The problem seemed to show up when I updated in June, but I can't really tell since the phone has spent almost all it's time sitting on my desk plugged in due to the pandemic.

Is this likely the result of a dirty flash? Bad battery? Hardware problem?
[Samsung Galaxy S 5 Unified Development] Brhmnst26:
There is no bug, just tricky one

when you have changed the camera storage to external, also change the album to custom and cancel and change it back to deffault

Andddd...booom your pictures will be saved on External/DCIM/Camera/
[Samsung Galaxy S 5 Unified Development] jenssa:
Thanks a lot, I share my experience with flashing it here:

https://xdaforums.com/showpost.php?p=83773517&postcount=1472
[Samsung Galaxy S 5 Unified Development] androiddude7899:
Super stable
[Samsung Galaxy S 5 Unified Development] curiousrom:
New Official 17.1 Thread

FYI see this new thread: [Official] LineageOS 17.1 for Galaxy S5 klte + Variants

The S5 klte + variants LineageOS maintainer is haggertk but he seemed uninterested in creating an S5 17.1 tread on XDA or he is too busy so I went ahead and created one. If he wants a transfer of that thread's ownership I will gladly do it.

***
[Samsung Galaxy S 5 Unified Development] A3du11ah AS:
Hello, is there any way to enable gestures, the option is missing.
[Samsung Galaxy S 5 Unified Development] jdrch:
Is today's build crashing and rebooting for anyone else?
[Samsung Galaxy S 5 Unified Development] kurtn:
Just reported in official thread. Dirty flash older version
[Samsung Galaxy S 5 Unified Development] jdrch:
Ah, there's finally an official thread. Last time I checked, one didn't exist. Thanks for the quick reply!
[Samsung Galaxy S 5 Unified Development] curiousrom:
[Official] LineageOS 17.1 for Galaxy S5 klte + Variants

***
[Samsung Galaxy S 5 Unified Development] TomInfo:
Patch for LineageOS 16.x

Hi,

Why has there been no LineageOS 16 Build since 04.10.2020?

I thought, when a new version is released, the previous version will be changed to weekly or monthly.

I don't want to switch to 17.1 yet, but I still want to have the latest security patches.

Thomas
[Samsung Galaxy S 5 Unified Development] kurtn:
Official lineageOS nightlies only get built for one android generation. There was an exception for a device but not for our S5.

You can switch without loosing data or setup.
[Samsung Galaxy S 5 Unified Development] TomInfo:
thx for the information.

So I have to wait a little bit. 17.1 seems to be a little bit buggy.

Is 17.1 slowing down s5 very much?
[Samsung Galaxy S 5 Unified Development] Massedil:
I use it since few days and performances seems as good as with 16.0.

The only annoying thing I had to notice for now is sometimes a Bluetooth bug.
[Samsung Galaxy S 5 Unified Development] g000n:
Android 9 is more compatible with this device than Android 10
[Samsung Galaxy S 5 Unified Development] g000n:
Why is there 3 threads for LOS?

It would be good if devs contributed to the main official 17.1 one: [OFFICIAL] LineageOS 17.1 for Galaxy S5 klte + Variants | XDA Developers Forums (xda-developers.com)
[Samsung Galaxy S 5 Unified Development] clockstoper:
Try this it will work

The battery icon menu is inside system> statusbar > system icons >battery You can enable and disable it there
[Samsung Galaxy S 5 Unified Development] Gitanitos:
I have the same issue on LOS 15.1 and 16.... The only thing I do is restart several times until SMS function "arrives" again.

Enviado desde mi SM-G950F mediante Tapatalk
[Samsung Galaxy S 5 Unified Development] curiousrom:
SELinux Permissive vs. Daily Driver?

My S5 G900M running official LineageOS 15.1 klte is my daily driver but was thinking of trying haggertk's unofficial 16.0 beta but then I stumbled on this post:

Then I found in this reply https://android.stackexchange.com/a/152329 to a How dangerous is the fact that SELinux is in “Permissive” mode? question.

So I fired up MatLog and searched in the logcat of my 15.1 setup for: avc :eek: & it returned several results with avc: denied.

I guess I will be waiting for a 16.0 version with SELinux enforcing.

Just curious for you guys that does not make you nervous a little?

***
[Samsung Galaxy S 5 Unified Development] fitittome:
SELinux Enforcing is mandatory for Official release. These releases are a work in progress to ensure the core 16.0 OS is stable and reliable. I don't think anyone is pretending that it ticks all the Charter boxes yet, but it's getting closer and closer. Whilst I think it's stable enough to use as a DD, it's only to permit some meaningful feedback to the dev from a vanilla device.
[Samsung Galaxy S 5 Unified Development] Nielsie89:
I installed lineage os v1019 with gapps. And now my gyro is nog werking anymore. Is thuis a known issue?
[Samsung Galaxy S 5 Unified Development] ozzycao:
Hi, jbird1978. Thank you for your help. I'm using the latest version of Haggertk (lineage-16.0-20181019-UNOFFICIAL-klte). And everything works fine except for receiving and sending SMS. It's a g900m, with clean install and picogapp.

Before, I used the brunowp8 version (lineage-16.0-20181012-UNOFFICIAL-klte) and SMS worked correctly.