yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 G900V Network, Modem & Bluetooth Problems

haggertk's G900V modem package includes both modems + other firmwares as described in S5 Odin Flashable Modem & Bootloader: DQL1 modem.bin (2g & 3G), NON_HLOS.bin (LTE modem), rpm.mbn, sbl1.mbn, sdi.mbn & tz.mbn.

You have nothing to lose flashing haggertk's G900V modem package because your S5 has network problems & you can always flash again you current package. Size difference may be related to different compression methods & software used to create the package.

If it's not with Format Data & with just wipe data it's not really a clean install in my book as described in S5 super clean install.

That may be very well the cause of your problems. Newer SIMs have newer embedded software for provisioning & other stuff.

I asked how old is your SIM because on S3 i9300 LineageOS 14.1 for 2 weeks I could receive but not send SMS. Then I bought a Galaxy S5 SM-G900M & on LineageOS 15.1 official inserted that old SIM and still had the can't send SMS problem + was not getting LTE.

Went to my network provider's shop & got a new SIM & LTE appeared instantly on the status bar after booting it. And the SMS problem was solved.

SIMs are cheap anyway so what do you have to lose by getting a new one?

Custom kernels introduce new variables and makes troubleshooting impossible.

Additionally this thread is about official LineageOS 16.0.

Yes. Don't do it on a G900V.

A logcat is everything the device did since the last time you booted it to System. You can open it with WordPad, Notepad++ or similar & search it with different keywords. Errors are listed after E/. Some errors are expected & may be irrelevant.

To make the logcat short & relevant you could reboot, reproduce the problem and use SysLog to quickly capture a logcat (screenshot).

Besides capturing logcat (Main log), Syslog can also capture the Kernel log (dmesg) & Last Kernel log (last_kmsg which is important in case of unwanted reboot) & other logs without using a computer + adb or using a Terminal emulator on the phone.

SysLog's Play Store & Github pages explains how to give the app the required permission via adb if you don't have root:

adb shell pm grant com.tortel.syslog android.permission.READ_LOGS

Syslog on GitHub with F-Droid + Play Store links.

Or with MatLog you can search for Bluetooth for example & see in real time what's happening in logcat. You can also export that filtered logcat.

In MatLog you can also clear the logcat, hit record & reproduce a problem then quickly stop recording & save. (screenshot)

You can search that saved custom logcat in the app itself.

Similar is Logcat Extreme which I also use sometimes.

***
[Samsung Galaxy S 5 Unified Development] Droid9684:
Ok I have attatched 3 logcats. Before you had told me about the logcat apps available I had downloaded extreme logcat. But chose to go with two others Matlog and Syslog. In the logcats one is from system and the others include bluetooth stopped. During my phones operation I encountered the roaming off indicator (but LTE remained on oddly) and BT disappeared upon boot. After my 2nd boot I played music in a music app and immediately it stopped playing over bluetooth. I found many errors in the bluetooth log.

https://www.dropbox.com/s/hwnntk6uj84rr0u/logcat_09-24-2019_20-50-13 BT.txt?dl=0

(too large to attach as attachment)
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: S5 G900V Network, Modem & Bluetooth Problems

Sorry but searching your logcat found in your logcat 2019-11-08_21.20-SYS-BT_stopped.zip attachment with lineage returns zero results.

But I can find:

I/ActivityManager( 1015): Process com.aospextended.ota (pid 3680) has died: cch+4CEM

In mine I can find stuff like:

I/LineageSystemServer( 575): Starting service org.lineageos.platform.internal.LineageHardwareService

This thread is about official LineageOS 16.0 & I don't have any experience in troubleshooting logcats with custom kernels.

As seen in your dmesg.log: "(Boeffla-Kernel-4.1-TUNED@heilerbemerguy)".

As I posted above:

"ROM: 8.0.1 AOSP Extended (based on LOS 15.1)" - Do a full TWRP backup + an internal sdcard backup so you may return quickly to you current setup & try a S5 LineageOS super clean install & if the problem persist then report in this thread.

So meanwhile post in a "ROM 8.0.1 AOSP Extended" thread.

Good luck!

***

Edit: [MENTION=4073432]Droid9684[/MENTION] looking at your logcat it seems to be a problem with the RIL daemon service (Radio Interface Layer used by the radio):

11-08 21:08:14.424 I/chatty ( 9414): uid=1000(system) CallAudioModeSt expire 1 line

11-08 21:08:14.730 I/TelecomFramework( 9782): TtyManager: updateUiTtyMode -1 -> 0

--------- beginning of crash

11-08 21:08:14.750 F/libc ( 418): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x7 in tid 1074 (rild), pid 418 (rild)

11-08 21:08:14.810 F/DEBUG ( 9876): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

11-08 21:08:14.811 F/DEBUG ( 9876): AospExtended Version: 'v5.8'

11-08 21:08:14.811 F/DEBUG ( 9876): Build fingerprint: 'Verizon/kltevzw/kltevzw:6.0.1/MMB29M/G900VVRU2DQL1:user/release-keys'

11-08 21:08:14.811 F/DEBUG ( 9876): Revision: '14'

11-08 21:08:14.811 F/DEBUG ( 9876): ABI: 'arm'

11-08 21:08:14.811 F/DEBUG ( 9876): pid: 418, tid: 1074, name: rild >>> /vendor/bin/hw/rild <<<

***

FYI: some ril related patches merged by S5 LineageOS dev haggertk: https://review.lineageos.org/q/owner:haggertk%40lineageos.org+branch:lineage-16.0+status:merged+ril

***
[Samsung Galaxy S 5 Unified Development] arylyl:
Hi, I have a question.

Are the SM-G901F and SM-G900F supported synchronously? That is, will the SM-G901F be supported for as long as the SM-G900F will be?

Thanks
[Samsung Galaxy S 5 Unified Development] kurtn:
No. Different maintainers. See lineageOS wiki.
[Samsung Galaxy S 5 Unified Development] KhizarrShahidd:
The problem has been solved, however I'm missing the android 9 so i wanted to ask, does the problem exist on Resurrection Remix based on Android 9 too?
[Samsung Galaxy S 5 Unified Development] Reverse-anastomosis:
A good place to ask would be the thread for whatever ROM you are considering. I think most active members of this thread are probably here because we use this ROM.
[Samsung Galaxy S 5 Unified Development] liquidraver:
anyone else having the problem that NFC stopped working with the latest build?

UPDATE: solved with new battery
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 NFC Battery Antenna

Thanks :good: for reporting back with the fix.

See Fake vs OEM S5 Samsung Battery with photos of the NFC battery antenna. Without it NFC will not work on the S5.

I have seen cosmetically perfect fake S5 Samsung batteries but without the NFC battery antenna depression as seen in the photos.

***

With thoughts & prayers or go to a AOSP thread. :rolleyes:

How many times do I have to tell you:

This thread is about official LineageOS 16.0.

This thread is about official LineageOS 16.0.

This thread is about official LineageOS 16.0.

One more time?

:eek: This thread is about official LineageOS 16.0! :eek:

You are a member of XDA since 2011. Don't you know by now that it's not a free-for-all like Facebook and threads have topics? :confused:

And please delete or trim (like I did above when quoting you) those huge quotes, you are cluttering the thread.

Alternatively you can ping a user with the @ mention like this [MENTION=4073432]Droid9684[/MENTION] instead of quoting a huge post.

***
[Samsung Galaxy S 5 Unified Development] liquidraver:
Thanks for the info. It has an antenna, it worked for a long time, then stopped working, that's why I thought it's software related. Maybe it was a cheap battery with a cheap antenna, or it got damaged when I dropped (which I don't remember)
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: S5 NFC Battery Antenna

If you look at the first attached photo in Fake vs OEM S5 Samsung Battery top right you can see that the battery's silver wrapper is slightly kinked or a little bit damaged.

That's where the S5 connects to the NFC antenna. If the battery is not inserted properly the S5 connector can be above the wrapper hence a bad connection & the NFC not working.

It's a weird way to connect to the NFC antenna and weird that the antenna is on the battery & not in the device itself.

***
[Samsung Galaxy S 5 Unified Development] liquidraver:
Wow!

I've pushed the antenna where you said, and pushed a couple of times the battery's center, and the NFC is back.

thanks!
[Samsung Galaxy S 5 Unified Development] Az Biker:
* * * REMINDER * * *

Please remember that this is a thread regarding LineageOS 16.x, not any other Roms or any kernels.

If your troubleshooting includes helpful information when using another Rom ("My WiFi worked fine on another custom Rom, but it doesn't work on this one" or "does this Rom play well with custom kernels that use xyz modification/or whatever?" are acceptable as they deal directly with troubleshooting THIS Rom and do not name, advertise, or open discussion about other Roms or kernels.

Also, if someone posts something anyone feels might be a violation of Forum Rules, disrespectful rude, insulting, off-topic, etc. , PLEASE simply REPORT the comment, and do not attempt to punish, enforce the rules, or attack the member posting these kinds of comments. REPORT the comment and move on, allowing moderation staff to handle the situation.

All comments that violate forum rules, that are not specifically related to the Rom will be deleted to remove any clutter or material that could start an argument. Ain't nobody got time for that :good:

Thanks for everyone's help on this!

tl;dr

-Only discuss THIS Rom in this thread, using information about other Roms is acceptable if it directly help troubleshooting, but naming the other Rom is not necessary.

- Please REPORT all issues believed to be in violation of the rules, don't engage, condemn, attack, or insult anyone; report the comment and let moderators handle it.
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 LineageOS 16.0 Update 2019-11-12 - Big Security Bump

FYI in the S5 LineageOS 16.0 update 2019-11-12 or newer there is a Bump Security String to 2019-11-05 commit that includes a total of 18 changes marked under Severity as High (15) & Critical (3). That page includes only CVE (Android Common Vulnerabilities and Exposures database) links and they are not very informative.

The Android Security Bulletin—November 2019 does include links to the references and the vulnerability details the security patch addresses.

Downloaded & installed successfully via the LineageOS built-in OTA Updater & after the automatic reboot as seen in the screenshot: > Settings > About phone > press on Android version 9 > Android security patch level: November 5, 2019.

View attachment 4874309

The Vendor security patch level 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 & nobody can do anything about it.

In the full LineageOS changelog: https://download.lineageos.org/klte/changes/ you can see a long list of commits including a few related to Bluetooth & NFC.

As that page is updated all the time I attached a screen grab for posterity.

View attachment 4874335

Not mentioned in the klte Changes page is commit Update Chromium Webview to 78.0.3904.96 because it's under branch Master instead of 16.0.

WebView is listed as Android System WebView in > Settings > Apps & notifications > 3-dots > Show System and is used by the LineageOS Browser & several other third-party browsers & apps. There is an extensive changelog in https://chromium.googlesource.com/chromium/src/+log/78.0.3904.96

View attachment 4874669

***

This security patch & several others were made by S5's LineageOS dev & one of the 9 Lineage directors haggertk as you can see in this LineageOS Gerrit search: owner:haggertk@lineageos.org branch:lineage-16.0.

So BIG THANKS :good::cool: to Mr. haggertk & the rest of the LineageOS team for your continuous support of our old devices.

***

That was updating to 2019-11-12 via the built-in LineageOS OTA Updater on a Galaxy S5 G900M LineageOS 16.0 klte running build 2019-11-10 + Open GApps Pico + LineageOS AddonSU, no custom kernel or system mods of any kind.

Note that you can create a direct link to Updater & much more (like to Privacy Guard Advanced for example) with the LineageOS Settings widget instead of navigating to Settings > System > Advanced > Updater.

***
[Samsung Galaxy S 5 Unified Development] ozzycao:
Hello brothersI need help: how do I access my wifi network settings and change DNS to 1.1.1.1? I didn't find the famous "modify network" or "Show advanced options" buttons. I'm using the las build of lineage 16.
[Samsung Galaxy S 5 Unified Development] curiousrom:
WiFi Settings & DNS

1.1.1.1 is the DNS address of cloudflare. You don't need to change your Wifi settings AFAIK.

Check Enable Private DNS with 1.1.1.1 on Android 9 Pie

More DNS choices: https://en.wikipedia.org/wiki/Public_recursive_name_server

Settings > Network & internet > Advanced > Private DNS > enter hostname.

You need to put a hostname in there not just numbers in Pie. For example: 1dot1dot1dot1.cloudflare-dns.com

I leave it to automatic.

***
[Samsung Galaxy S 5 Unified Development] Massedil:
Hello,

I now have 3 galaxy s5 (2 klte and 1 kltedv).

For 2 of them (klte & kltedv), GPS fix is very quick (less than 1 minutes first time and few seconds after).

And, for the third klte, GPS fix is very slow: few satellites are visible on the satstat app, and the precision is poor (50-200 meters compared to 5-15 meters for the 2 others).

1. How can I check the drivers version of the GPS sensor?

2. Can I reinit them?

3. What do you advice to fix the poor GPS quality of the last klte?
[Samsung Galaxy S 5 Unified Development] ozzycao:
EXCELENT! Thank you very much!
[Samsung Galaxy S 5 Unified Development] curiousrom:
Galaxy S5 GPS Problem

Missing troubleshooting info: exact klte models, basebands & OS.

For example LineageOS 16.0 klte for S5 is a unified firmware & supports all those models: SM-G900AZ, SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L.

The GPS chip is a radio, not a sensor. On the S5 it's a GPS/GNSS receiver. It's the modem/baseband/radio that is the interface with the OS.

Did you try updating your modem/baseband/radio? See S5 Odin Flashable Modem & Bootloader.

Did you try outdoor with an unobstructed view of the sky for more than 10 minutes?

With an internet connection you could try GPS Test by Chartcross > 3-dots > AGPS > Clear and update. (screenshot)

Did you make sure that in your OS settings > Location that GPS is enabled?

If everything fails install the most recent stock Samsung firmware for your S5 to rule out a hardware problem. Added benefit: this will update your bootloader, modem & other firmwares.

***

You are welcome. BTW don't be shy & hit the Thanks :good: button on the posts that you find helpful.

***
[Samsung Galaxy S 5 Unified Development] Sobhan Mazaheri:
Files are not displayed in music or gallery!

Hi Guys

After restarting my device, I don't see files such as music and photos and videos in external storage (SD card) in the Music and Gallery apps:(

But I see them in the file manager !!! I should remove the memory card once and restart it to fix the problem.

Is there a solution to this?:confused:
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: Files are not displayed in music or gallery!

Did you setup your Micro SD card as Portable storage or internal storage (a.k.a adoptable storage)?

See this bug report: Snap (camera) when selecting SD stores somewhere where not visible in Gallery (after restart)

And this bug report about switching from internal to portable storage & addressed in the commits linked below: No option to change storage location in Camera app.

Currently on my Galaxy S5 G900M LineageOS 16.0 klte build 2019-11-12 + Open GApps Pico + LineageOS AddonSU, stock Gallery shows only the 2 photos I just took in the /storage/{Micro SD Card ID}/Android/data/org.lineageos.snap/files/ album while Simple Gallery Pro on F-Droid shows correctly 900+ photos which is the same number as seen in the stock Files explorer & a third-party file explorer.

Note that the Files album is also not seen in stock Files explorer > Images.

Actually the Files album disappeared from Stock Gallery after the OTA update but was visible again after taking a photo with the stock Camera.

For some reasons the number of photos in Gallery get resetted after an OTA update or reboot once in a while and in > Settings > Apps & notifications > Gallery > Storage > Clear Storage + doing the same in Media Storage & rebooting does not fix the problem. You could try Clear Storage in Music too before rebooting.

Make sure you don't have any .nomedia files in your Music & photos folders because that prevents indexing.

As a workaround try Simple Gallery Pro & a third-party file explorer.

I don't have any problems seeing the content of my external SD Card Music folder in the Music app & can also see it in stock Files explorer > Audio.

***

There are 2 merged patches related to the camera & SD card that will be included in build 2019-11-14 or newer. Let's see if it has any effects of the Files album mystery disappearance:

Snap: Handle SDCard-removed case - android_packages_apps_Snap

Snap: Don't spam exceptions - android_packages_apps_Snap

***
[Samsung Galaxy S 5 Unified Development] RuKaDa:
I wonder if anyone already has installed 20191114-nightly-klte version and have the same issues...

I have tried with clean install (all wipes made) but every time it boot I get a Bluetooth error: "Bluetooth keeps crashing".

I really don´t know what happen, on my previous installation (20191108-nightly-klte) everything was working great, could it be because of gapps version (pico).

I am on latest modem and bootloader on my G900F

Thanks you to all developers and to @curiousrom for your great effort and support
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 LineageOS 16.0 - Bluetooth keeps crashing

On my Galaxy S5 G900M LineageOS 16.0 klte OTA updated via Updater from 2019-11-12 to build 2019-11-14 + Open GApps Pico + LineageOS AddonSU Bluetooth works fine:

With Bluetooth enabled on the S5 & no Bluetooth devices connected I reboot to system & no Bluetooth crash.

Connected a cheap Bluetooth headset & played the stock Music app for 45 minutes & no crash. Captured a logcat & no Bluetooth crash. Music app is org.lineageos.eleven in the logcat.

Note that in > Settings > Security & location > Location > Advanced > Scanning > I have both Wi-Fi scanning & Bluetooth scanning off.

Now it has been reported in this thread that on some S5 devices with some Bluetooth devices in LineageOS 16.0 that Bluetooth keeps on disconnecting or crashing. Nobody has found an explanation so far.

You could try with your Bluetooth device off, Bluetooth turned on in the S5 > Settings > Connected devices > Previously connected devices > Forget, reboot, connect device (and write down the name) reproduce the problem & capture a logcat.

You could search the logcat with your device's name or "crash" or "beginning of crash" or "has died" to find a line similar to: Process com.android.bluetooth (pid 6027) has died...

Note that the pid # changes for every device setup.

You could attach that logcat to a post but I'm far from being a Bluetooth expert but some other users may find something in it.

You could also post in & attach it to [MENTION=9533319]Reverse-anastomosis[/MENTION]'s bug report: Bluetooth Crash and include device model + setup description.

Check the bottom of the S5 G900V Network, Modem & Bluetooth Problems post about capturing a logcat.

If you search Settings with Bluetooth you can find a bunch of options in Developer options but I never touched any of those so far.

"...I have tried with clean install (all wipes made)…" - You could try with a Format Data instead of a simple wipe data as described in S5 LineageOS super clean install

"...on my previous installation (20191108-nightly-klte) everything was working great" - Maybe it's some app you installed. I had a Bluetooth crash on a previous build & in logcat it showed that it was when VLC scanned media.

Or the recent commits included in build 2019-11-12 or newer:

DO NOT MERGE Store BLE keys using the address from the ble_auth_cmpl_evt - android_system_bt

DO NOT MERGE: AdapterService: Check the PIN code length before using - ndroid_packages_apps_Bluetooth

***

BTW thanks for the thanks.

***
[Samsung Galaxy S 5 Unified Development] Massedil:
As always, thank you for your help !

GPS OK klte :

SM-G900F

baseband: G900FXXU1CQK3

LOS: 16.0-20191018-NIGHTLY-klte

kernel: 3.4.113-lineageos-g2df84e6 #1 Fri Oct 18 14:03:13 UTC 2019

GPS fix is very quick and precision is accurate (5-15 meters)

GPS OK kltedv :

SM-G900P

baseband: G900PVPU3BOK4

LOS: 16.0-20191112-NIGHTLY-kltedv

kernel: 3.4.113-lineageos-g2df84e6 #1 Nov 12 13:01:03 UTC 2019

GPS fix is very quick and precision is accurate (5-15 meters)

GPS KO klte

SM-G900F

baseband: G900FXXU1CQK3

LOS: 16.0-20191110-NIGHTLY-klte

kernel: 3.4.113-lineageos-g2df84e6 #1 Sun Nov 10 18:52:00 UTC 2019

GPS fix is very slow and precision is poor (50-200 meters).

Yes, I have the exactly same "modem/baseband/radio" on my 2 klte (G900FXXU1CQK3).

Yes. With the 3 phones. The only one with a problem is my last klte.

I have already done it with the free SatStat app from F-droid (https://f-droid.org/en/packages/com.vonglasow.michael.satstat/) > 3-dots menu > "Reload AGPS data".

Yes, and it works because for the 3 phones, there is some GPS that are seen.

But for my last klte the connexion is very poor.

1. So the "driver version" of the GPS radio is "G900PVPU3BOK4" ?

2. Nothing to send a software reinitialisation impulsion ?

3. What do you advice to fix the poor GPS quality of the last klte?
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: Galaxy S5 GPS Problem

1. No. You said baseband G900FXXU1CQK3 for the bad klte so that's the firmware (a.k.a. Samsung proprietary blobs) used.

2. No that I know of.

3. As I wrote above: If everything fails install the most recent stock Samsung firmware for your S5 to rule out a hardware problem. If you still have GPS problem with the stock ROM then you have a hardware problem.

It could be the GPS receiver which cannot be changed as it is welded on the motherboard or the GPS antenna.

***

Thanks for the thanks.

***
[Samsung Galaxy S 5 Unified Development] Massedil:
1. Yes, my mistake. Both klte have "G900FXXU1CQK3" !

2. Ok.

3. I have tried with a stock ROM. Problem is still here. :/

I now believe that this is a hardware problem.

The phone vendor said that the screen have been replaced. May be there is a contact problem between the GPS chip and the antenna ?

Does anyone know where exactly is the GPS chip and where is the antenna if I want to check the good contact between the GPS chip and the antenna ?

I've looked here https://www.ifixit.com/Teardown/Samsung+Galaxy+S5+Teardown/24016 but I don't understand where is the GPS antenna and the contact with the GPS chip.
[Samsung Galaxy S 5 Unified Development] jdrch:
Yes. Instructions here (you'll have to modify them according to your S5 variant.)
[Samsung Galaxy S 5 Unified Development] RuKaDa:
First things first,

@curiousrom

Thank you very much for all your effort trying to help, I have to say that you provide us all an awesome support and I really appreciate, thanks.

Well, I really didn´t provide all the info, sorry about that, I did made it like super clean install tutorial (Advanced Wipes+Format Data). The Bluetooth error was at first boot, right after a clean install and I still don´t know what went wrong... :confused:

So I went with the hardest way, unroot and flash latest stock firmware with odin... root again and install latest TWRP :p

Right now and after a couple of hours and a little patience I was able to install latest nightly without any error and everything is running smooth :) :victory:

Anyway, and again, thank you so much for your help and your awesome support :good: