yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
Okay... I've been a bit busy with other things but, I took a deeper view at the issue I've, personally, experienced.

It looks like I had located something regarding the Official LineageOS 16.0 viewing the G900V as a G900F device.

I compared 2 TWRP Logs from separate clean flashes from separate LineageOS 16.0 builds (when they were new releases at the time) and I discovered the following identical statements from them both.

So I then took a look at a few of the TWRP Logs from the same installation for my G900T device and did not locate that specific type of Warning.

This is something that, I believe, [MENTION=2693412]haggertk[/MENTION] may want to take notice with.

I'm still going to be touching base with this again but, I just wanted to provide what I've found thus far.

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle" AND Nickname for "My Ex-Wife"}.
[Samsung Galaxy S 5 Unified Development] haggertk:
There is precisely zero to note. This is because we absolutely had to set a "short-enough" default build fingerprint or the override would cause the build to bootloop (see first two nightlies). It's cosmetic in recovery. It doesn't matter.

https://review.lineageos.org/#/c/242964
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
I'm not stating that this is an issue for everyone and I'm truly not trying to be argumentative or any such thing.

It just boggles me why, when I perform a clean installation (on the current builds too), it ends up resulting in my G900V device as a G900F that results in carrier issues?

I don't see any APN's available and only the Network Internet LTE Data works without any service for Phone nor messaging available. It doesn't register the towers it's connected to as Verizon.

Is there something I'm missing My Friend?

I truly want to understand and express my explanations the best I can via text.

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle" AND Nickname for "My Ex-Wife"}.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: G900V Shown as G900F? - G900V No Service Bug

1- Where exactly do you see your G900V shown as a G900F? LineageOS build date? Modem version?

2- [MENTION=4828250]Ibuprophen[/MENTION] - Did you try haggertk's SM-G900V modem package linked in S5 Odin Flashable Modem & Bootloader? It contains more than just the NON-HLOS.bin & modem.bin as seen in the screenshot:

rpm.mbn

sbl1.mbn

sdi.mbn

tz.mbn

3- What happens when you restore a EFS partition backup made when network connections & data was working properly? Can you see your APN settings in > Settings > Network & internet > Mobile network > expand Advanced > scroll all the way down to > Access Point Names (APN) > press current active APN & get the Edit access point panel?

4- How old is your SIM?

I am asking 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.

Some network providers do not provision the SIM properly or block provisioning on custom firmwares.

The workarounds: insert your SIM in an other phone with stock firmware, send an SMS & wait for 10 minutes for provisioning. Or get a new SIM.

***
[Samsung Galaxy S 5 Unified Development] 3bcooper:
Is hight touch sensitivity using more battery power?
[Samsung Galaxy S 5 Unified Development] joam280:
Hi, I have specific wifi disconnections.

It connects and disconnects at will
[Samsung Galaxy S 5 Unified Development] haggertk:
Show me something that demonstrates the G900V being identified as a G900F. Hint: as stated before, the fingerprint in TWRP is 100% meaningless.
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 Wifi Disconnecting

You did not give any troubleshooting info. :confused:

Exact phone model, LineageOS build date? What is your modem/baseband? Is it older that the one found in S5 Odin Flashable Modem & Bootloader? If so updating it may solve cellular network & Wifi connection problems.

How do you know it's the phone & not a wifi network or signal strength problem? Is the access point 2.4GHz or 5GHz? Post about other user w/ Wifi problems & troubleshooting here.

I attached a screenshot of GSam Battery Monitor > Chart & the nice solid bar is my Wifi connection. The white break is when I rebooted in TWRP & flashed a small minor mod. That's with connected to a Wifi access point 2.4GHz, LTE Data & sync enabled on S5 G900M w/ the most recent modem for that model.

When that screenshot was made I was running build 2019-03-18 but I'm getting the same excellent Wifi connection on S5 G900M LineageOS 16.0 klte build 2019-04-13 + Open GApps Pico + LineageOS Addonsu.

***

Sorry but there is nothing in your logcat which I attached to this post except stuff about Syslog itself. (open with WordPad or Notepad++ for example to keep the formatting)

Reboot & reproduce the problem then:

"how do I make a log..." - The free, quick & easy SysLog Play Store page explains how to give permission via adb if you don't have root.

Also in Syslog > 3-dots > FAQ > manually enable access which links to https://github.com/Tortel/SysLog > Readme.md.

Edit: try uninstalling Syslog, reboot & install again.

The LineageOS Wiki - How to submit a bug report links to LineageOS Wiki - How to capture logs (logcat) without root using adb.

***

¯\_(ツ)_/¯ but I guess not.

***
[Samsung Galaxy S 5 Unified Development] Eclipse1991:
Oh okay , so first I need to give the app the permission to nake the logcat visable ? Sorry for it, have never done it in the past and that was my first time. Will try to do it.

Gesendet von meinem MI 8 mit Tapatalk
[Samsung Galaxy S 5 Unified Development] kurtn:
Looks like audioFX has improved with April 13 build. There is some AudioPackage mentioned in change log.
[Samsung Galaxy S 5 Unified Development] Deydacar3:
Thanks, I will try it

Thanks, that sounds good. I will try it
[Samsung Galaxy S 5 Unified Development] shkedov:
My kltechn, when I bought it it had official Samsung Israeli ROM, and in the settings->about phone it said it's a pure g900f. When I went to change ROM, I had problems with the versions I downloaded, and then I found that in download mode it is actually a disguised g9006v, kltechn.

Then I downloaded correct files and everything is OK
[Samsung Galaxy S 5 Unified Development] fitittome:
Actually that's important with second hand devices. Download/Odin mode doesn't lie! That will tell you precisely what device you have, irrespective of whatever OS has been jammed onto the device in order to sell it!
[Samsung Galaxy S 5 Unified Development] mpower25:
I can't upload videos recorded with the camera app using WhatsApp. Any ideas?
[Samsung Galaxy S 5 Unified Development] curiousrom:
WhatsApp Sending Video Fail & Workaround

I also have the WhatsApp failing to send video bug. It happens sometimes but not always.

It can happen when sending videos from the stock Gallery > Share > WhatsApp or within WhatsApp > Chat > Attach or when using the camera button in a Chat in WhatsApp.

Then WhatsApp renders the video, offers the possibility to add a Caption & if you click Send as seen in the attachments, in the Notification curtain it shows as sending but in this example after 2 minutes there was no progression.

Then I get a "WhatsApp isn't responding" error popup.

If I click on Close app, it closes the uploading operation but not WhatsApp itself & the upload automatically restarts & is successful. So this is the workaround.

Since it happens after the WhatsApp rendering the video stage I don't think it's worth reporting the bug in the LineageOS bug tracker as the devs will invalidate the report and say they don't support third party apps just like the bug described in the WhatsApp Low Mic, Playback Volume Quirk & Tests post.

But I will create a bug report anyway the next time it happens & post the link in this thread.

***
[Samsung Galaxy S 5 Unified Development] synpax:
The instructions aren't clear. A video would be helpful.

It says to "download the latest build" but then there are three 'builds' listed, each of which is very different, with no explanation of which to choose.

I have just rooted my stock G900T phone using ODIN. I think I need to install some program to do the flashing, though (I haven't done this in a while).
[Samsung Galaxy S 5 Unified Development] curiousrom:
Installing LineageOS - S5 G900T

You don't need to root your S5 running the stock Samsung firmware to install LineageOS and you don't need "some program to do the flashing".

Since you used Odin I presume you are on a Windows computer, right?

You just need Odin to flash the TWRP custom recovery. Then copy the files to be installed to the external Micro SD Card, boot in TWRP recovery & flash them.

See S5 LineageOS Super Clean Install with optional wipe Data instead of Format Data & the Flashing TWRP Recovery on Samsung Firmware chapter.

For your S5 G900T just get the most recent build here: https://download.lineageos.org/klte

I described how I updated my S5's modem & bootloader & included Odin screenshots: S5 Odin Flashable Modem & Bootloader

***
[Samsung Galaxy S 5 Unified Development] fitittome:
Not that I ever suggest running 3rd party kernels, I reinstalled fbs's kernel to check something and my long dead compass, noticed by screen rotation, magically started working again. wtf! Confused!
[Samsung Galaxy S 5 Unified Development] mpower25:
Here the app doesnt crash. It just fails to upload after it reaches 50% of the progress.
[Samsung Galaxy S 5 Unified Development] ElIT3ShOOT3R:
There is a built in app locker which I found today buried in homescreen settings. WOW finally!!
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
Just an FYI in case you weren't aware.

TWRP v3.3.0-0 was just released.

Some notable changes were made too... :eek:

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle" AND Nickname for "My Ex-Wife"}.
[Samsung Galaxy S 5 Unified Development] curiousrom:
How To Update TWRP 3.3.1-0 Using TWRP Itself

Official changelog: TWRP 3.3.1-0 Released but see also the previous major update with multiple changes that are included in TWRP 3.3.1-0: TWRP 3.3.0-0 Released.

Downloads: TWRP for Samsung Galaxy S5 Qualcomm (klte family)

FYI: TeamWin/Team-Win-Recovery-Project/Issues

How To Flash TWRP 3.3.1-0 Using TWRP Itself

It's very easy to update TWRP by using TWRP itself as seen in the screenshots that were made while flashing 3.3.0-0 but it's exactly the same steps when flashing the newer 3.3.1-0:

Download the most recent @ the present twrp-3.3.1-0-klte....img & copy it to the external Micro SD Card.

Optional but recommended: To be on the safe side check the md5 or sha256 hash to make sure the download is not corrupted. In the screenshot I used the free Hash Calc (Checksum Utility) on the phone itself to check the sha256 of the copied twrp-3.3.1-0-klte....img file.

View attachment 4743581

TWRP > Install > Install Image > select twrp-3.3.1-0-klte....img > Select Partition to Flash Image: Recovery > Swipe to confirm Flash.

Do not do anything else in TWRP and > Home > Reboot > Recovery to check the new TWRP 3.3.1-0 version as seen in the last screenshot.

View attachment 4743582 View attachment 4743583 View attachment 4743584 View attachment 4743585

Notes:

You could also flash twrp-3.3.1-0-klte....img.tar with Odin3 & a Windows computer. See S5 LineageOS Super Clean Install >>> Flashing TWRP Recovery on Samsung Firmware chapter.

TWRP cannot flash .tar packages.

I tried 2 times to download the twrp-3.3.1-0-klte....img file using the phone itself & the stock LineageOS Browser but the download failed as it was much smaller than 9.54 MB.

I copy/pasted in the Hash Calc app the full sha256 data from the TWRP .img download page before making the screenshot but you can check visually only the last 4 digits calculated by the app & if they are the same then the file is OK.

I prefer to reboot to System afterwards before using the new TWRP.

I do not use the TWRP app as updates are not frequent, it wants to start at boot, run in the background & collect data for no good reasons. :eek:
[Samsung Galaxy S 5 Unified Development] mpower25:
I managed to upload short videos (30 seconds or less), after some retries. I hope this bug is addressed soon
[Samsung Galaxy S 5 Unified Development] jiml8:
Using either Startup Manager (from the play store) or 3C System Tuner Pro, you can prevent the Official TWRP App from starting when the system starts. Using Greenify, you can hibernate it when it is running.

This enables you to have the convenience of the app (which in fact is not used very often) while not dealing with the downside of having it running all the time.

I use these tools extensively to keep my device under control. I get excellent battery life, and I don't have anything running that I don't want running.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Tamings Apps

These apps are redundant & may actually affect negatively the battery life as LineageOS 16.0 has excellent Doze functions and built-in tools.

You can use LineageOS's Privacy Guard to prevent start @ boot, Run in the background & restrict other permissions according to your needs. See Remove Animations UI Speedup Test - Taming Google & Apps for more details & search Settings with battery to find other tools like Battery Manager & Battery optimization.

***
[Samsung Galaxy S 5 Unified Development] corvus1234:
Anyone has the problems with connectivity on klte (Samsung S5) on Lineage 16? On mine (upgraded from 15.1) everything works OK for couple of hours and then network stops (WiFi and cellular). Strangely ping works (e.g. from Termux), DNS resolution works, panel icons show connections but other traffic stops (web pages timeouts, Gmail does not work etc.). After reboot everything works again - for some 5-6 hours. Where to look for clues? :)
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 Connectivity Problems - WhatsApp Uploading Video Problem

Exact phone model, LineageOS build date? What is your modem/baseband & bootloader? Is it older that the ones found in S5 Odin Flashable Modem & Bootloader? If so updating it may solve cellular network & Wifi connection problems.

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.

Check No Network, No IMEI, No SIM & EFS Partition Restore Fix.

Did you double checked your APN settings? What is your network provider? Is your Wifi access point 2.4GHz or 5GHz?

If you are using Magisk have your tried disabling the modules if you use any? Or completely uninstalling Magisk to restore the stock boot.img?

"Where to look for clues?" - Reboot & reproduce the problem then:

"how do I make a logcat..." - The free, quick & easy SysLog Play Store page explains how to give permission via adb if you don't have root.

Also in Syslog > 3-dots > FAQ > manually enable access which links to https://github.com/Tortel/SysLog > Readme.md.

The LineageOS Wiki - How to submit a bug report links to LineageOS Wiki - How to capture logs (logcat) without root using adb.

You said you use Gmail so if you can make a Google Backup, you could do a S5 LineageOS super clean install and restore on first boot that Google Backup like I did & described in that post.

I don't have any network or Wifi connectivity problems on S5 G900M LineageOS 16.0 klte build 2019-04-16 + Open GApps Pico + LineageOS Addonsu and the most recent modem & bootloader for that model.

***

WhatsApp Video Uploading Problem

You can hope all you wish but without submitting a bug report (including a logcat) as linked above chances are next to nil that a LineageOS dev will look into it.

This said the LineageOS devs may invalidate the bug report and say that they don't support third party apps but may look in the logcat to see if it's a LineageOS or WhatsApp bug.

You did not say how you are trying to upload a video: is it when sending videos from the stock Gallery > Share > WhatsApp or within WhatsApp > Chat > Attach or when using the camera button in a Chat in WhatsApp itself?

You could try doing a full Chat backup then uninstall & reinstall WhatsApp. See those 2 WhatsApp FAQ pages:

https://faq.whatsapp.com/en/android/20887921 and https://faq.whatsapp.com/en/android/20950581

Check also Android > Troubleshooting > Connection problems: https://faq.whatsapp.com/en/android/22014642/?category=5245260

***
[Samsung Galaxy S 5 Unified Development] mpower25:
I'd probably go back to stock or buy a Xiaomi before doing such a complicated thing as using adb.

Never worked on any of the 3 S5s I ever had.

Besides, if the devs think a WhatsApp bug is not a LOS bug and won't address it for this reason, what's the use of having the hassle of making a logcat?

This bug has been reported here and elsewhere. Just look at XDA and you will find it. Almost everyone uses WhatsApp.

IMHO the devs are playing blind if they aren't looking into this.
[Samsung Galaxy S 5 Unified Development] fitittome:
Most of the population are perfectly happy with stock. It's not that they are idiots or anything like that, they just don't know any better.
[Samsung Galaxy S 5 Unified Development] gumble_HH:
TWRP bootloop after update

First of all, many thanks to the developers that brought Pie on our old phone. I was surprised, how stable and smooth it runs. Everythink works fine so far, even Magisk. :)

I came from Custom Rom "xXx NoLimits 6.1", wiped Dalvik, System, Cache, Data and Internal Storage and did Format data, then I installed LineageOS 16, Gapps and Magisk.

My system:

- Model: G900F

- Bootloader: G900FXXU1CRH1

- Modem: G900FXXU1CQK3

- TWRP 3.3.0.0

- OS: LineageOS 16 from 2019-04-04

- Gapps: MindTheGapps-9.0.0-arm-20190216_211054

- Magisk 18.1 / Magisk Manager 7.1.1

Now to my problem: I can't install any LineageOS updates. It always ends in a TWRP bootloop. I first tried to install an OTA update. The file (from 2019-04-11) was downloaded, then TWRP started and installed the new version without an error. Automatically also Magisk was (re-)installed right after that, also without an error. Then I wiped cache and dalvik. But when the phone rebooted, it showed the Lineage boot animation for several minutes (everything looked fine so far) but suddenly it started again and went into recovery mode.

I tried then to install the Lineage update directly through TWRP (not over OTA updater) - with the same results. Also newer versions of Lineage brought no success. The phone always boots to the recovery and booting to system (through TWRP) results in a restart.

Strangely when I re-install the version from 2019-04-04 (which was installed first), the phone will reboot normal again and everything is fine.

What could be the problem? I didn't try to do a full wipe and install a new version - I guess, that would work. But I'd like to find a solution for updating.

When I searched the web for a TWRP bootloop after OTA update, I found out, that many LG users have this problem - but I found no solution for our phone.
[Samsung Galaxy S 5 Unified Development] fitittome:
There is a known problem with Magisk that shows these symptoms. Try without.
[Samsung Galaxy S 5 Unified Development] guest4711:
If using Magisk use stable (18100). All newer ones result in booting into download mode..
[Samsung Galaxy S 5 Unified Development] lopsided98:
Since yesterday, my phone has been running hot when wifi is enabled. I noticed that the phone was hot when I unplugged it from the charger in the morning. Turning off wifi causes the phone to cool off. I was running an old unofficial build from January, and I have made no changes or updates to my phone that I can think of in the last few days. To try to fix the problem, I dirty flashed to the latest official build, which shows the same symptoms. I then wiped my phone, but the problem still occurs.

I noticed high cpu usage by system_server, which goes away when turning off wifi. When wifi is enabled, even when the screen is off, I get GC messages in logcat about once a second:

04-19 18:40:39.497 564 577 I system_server: Background concurrent copying GC freed 932621(31MB) AllocSpace objects, 0(0B) LOS objects, 42% free, 24MB/42MB, paused 171us total 189.131ms
04-19 18:40:40.117 564 577 I system_server: Background concurrent copying GC freed 749477(24MB) AllocSpace objects, 0(0B) LOS objects, 42% free, 23MB/41MB, paused 161us total 202.284ms
04-19 18:40:40.682 564 577 I system_server: Background concurrent copying GC freed 737812(24MB) AllocSpace objects, 0(0B) LOS objects, 42% free, 24MB/42MB, paused 1.554ms total 205.745ms
04-19 18:40:41.302 564 577 I system_server: Background concurrent copying GC freed 750753(25MB) AllocSpace objects, 0(0B) LOS objects, 42% free, 22MB/39MB, paused 256us total 187.839ms

These messages only occur every once in a while when wifi is disabled. This seems to indicate that something is allocating memory (and then quickly releasing it, not leaking it) at a high rate when wifi is enabled. This probably explains the high cpu usage by system_server.

I am normally connected to the "eduroam" network at my school, which uses WPA2 Enterprise, but it also happens with an unsecured public network. It almost seems like this problem was triggered by an external factor, such as a change in how the wifi access points are configured. I will test to see if it still happens when certain networks are not in range.

Does anyone have any further suggestions about how to debug this? Is there a way to figure out what is allocating and freeing memory at a high rate?
[Samsung Galaxy S 5 Unified Development] lopsided98:
I did more testing, and it only seem to occur in certain locations. I can reliably reproduce the problem near a few dorms, including the one I live in, but in other buildings it does not occur. The system_server GC messages begin as soon as the phone begins to connect to the network. The problem does not occur when there are networks in range but the phone is not connected to them.

I'm wondering if it is related to the large number of access points in range. Scans show that my phone can detect somewhere between 12-26 access points for the "eduroam" network. I have not compared this number to the cases where the problem does not occur, but I suspect there might be fewer. This still doesn't explain why the problem suddenly started happening.
[Samsung Galaxy S 5 Unified Development] lopsided98:
g900pvps3cqd1
[Samsung Galaxy S 5 Unified Development] fitittome:
It's dated, try updating it, def worth a shot.
[Samsung Galaxy S 5 Unified Development] lopsided98:
I have an SM-G900P (forgot to mention that before), and as far I can tell that is the latest baseband. Where would I find a newer one?