yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] ToriRobobo:
I recently updated my Galaxy S5 SM-G900T from CM13 (Android 6.0.1) to Lineage 14.1 (Android 7.1.2), but I've been having problems with data connection. Whether it's LTE or 3g, I can't seem to get any connection from data even though the triangle icon is still lit. I've tried troubleshooting with T-Mobile, checking the APN, different settings like preferred network type, and using Odin with a baseband I found, but still nothing.

More info:

I'm on the July 5 klte nightly.

In SIM status, my signal strength is around -98 dBm 43 asu. Service state is In Service. Not Roaming. Cellular network state is Disconnected.

T-Mobile said they're refarming towers which might affect speeds, but I don't see how that would cause the issue when data was ok before Lineage.

3g Data seemed to work a little bit after the switch to Lineage (I was over data cap so speed reduced), but later it stopped and hasn't worked again even after they raised my data cap.

When I tried my SIM card on another T-Mobile phone, the data worked, so it's not the SIM card.

I was told to download the baseband and install with Odin. SM-G900T_GPI1_Baseband_Firmware.tar.md5 from androidfilehost, haggertk Nov 27, 2016 (sorry can't link yet).

I had used Odin 3.12.3 from odindownload.

Using that, I did get the green pass, but I didn't notice anything change on the phone's download mode (not sure if I'm supposed to see anything change). The data issue still isn't fixed.

The baseband version before Odin was G900TUVS1GPI1, and it's still that after Odin. He pointed out it may be the same version and that file may not be the latest. I'm not sure what the latest is or if I did anything wrong in the process.

Fingerprint scanner seems to work fine.

So I'm not sure what's causing it. What do I do now?

Here's the log from Odin:

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin engine v(ID:3.1203)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> SingleDownload.

<ID:0/004> NON-HLOS.bin

<ID:0/004> aboot.mbn

<ID:0/004> modem.bin

<ID:0/004> rpm.mbn

<ID:0/004> sbl1.mbn

<ID:0/004> sdi.mbn

<ID:0/004> tz.mbn

<ID:0/004> RQT_CLOSE !!

<ID:0/004> RES OK !!

<ID:0/004> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)
[Samsung Galaxy S 5 Unified Development] TheATHEiST:
Flash to latest stock first or just flash bootloader/modem then try again with wipe/flash LOS.
[Samsung Galaxy S 5 Unified Development] jdrch:
This is probably your issue. For an update jump that large, you probably need to clean install in addition to updating the non-OS portion of the phone's firmware.
[Samsung Galaxy S 5 Unified Development] @richardnote2:
Please help. How to install boeffla in linegae rom
[Samsung Galaxy S 5 Unified Development] ToriRobobo:
I did clean install the first time, but I never did update from 6.0.1 or update anything else. How would I update the non-OS portion of the firmware? Is that the same or different from the bootloader and modem/baseband?

https://www.sammobile.com/firmwares/galaxy-s5/SM-G900T/

Do you mean the GQC2 one? I see my GPI1 is not the latest then.

If I flash this in download mode with 3.09/3.12 Odin (I assume it's just drop in ap/pda and green pass) do I need anything like Kies or Smart Switch? Will it wipe and start a new ROM just like how I wiped for LineageOS and rebooted? Would I still have TWRP in order to wipe again and clean install LOS? Am I missing something with all this?

Stock firmware from Sammobile right? Like this link?

https://www.sammobile.com/firmwares/galaxy-s5/SM-G900T/

Or do you mean something else?

I also found the bootloader and modem for the GQC2 here:

https://xdaforums.com/tmobile-galaxy-s5/general/recent-odin-flashable-bootloaders-t3574276

I'm guessing flashing the former is cleaner in case some other firmware related issue crops up right? And would all of these need just Odin?

Sorry if I don't know these things.
[Samsung Galaxy S 5 Unified Development] TheATHEiST:
Yes. Flash latest in Odin. Then do full wipe and install LOS.
[Samsung Galaxy S 5 Unified Development] fitittome:
[MENTION=8398583]ToriRobobo[/MENTION] as the others have said, I think it is probably much more straight forward for you to revert to Samsung stock using their slow Super Switch software. Once you have the latest Samsung Stock on your phone you can then test your Mobile connectivity and make notes of the APN settings etc. So long as you are confident it is all working properly, then go for installing TWRP and LineageOS.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
So after that playstore update I uninstalled that google playstore instant apps. Well it came back along with a "you have been signed out of your google account". Seems they no longer recognize this device as the send text option don't work and inputting the PW looks like it works but when don't the triangle and notice are still there. Tried removing instant apps again,clearing all the google playstore caches + dalvik-cache and nothing. It's very annoying lol.
[Samsung Galaxy S 5 Unified Development] @richardnote2:
Hello. Can someone help me. The rom drains my battery so fast any tips? Any help?
[Samsung Galaxy S 5 Unified Development] heshan_1010:
In my case turning off the wifi when I'm not connected to any network helps a lot. I'm also using the app Naptime in the play store.
[Samsung Galaxy S 5 Unified Development] fitittome:
Use GSam Battery Monitor and spend hours fiddling. Or make sure baseband up to date and do a clean install.
[Samsung Galaxy S 5 Unified Development] @richardnote2:
How to update baseband?
[Samsung Galaxy S 5 Unified Development] fitittome:
Good tip. I really like this app, good for privacy too. Wi-Fi Matic (Toggle WiFi based on location) - https://f-droid.org/app/org.cprados.wificellmanager

---------- Post added at 12:47 PM ---------- Previous post was at 12:30 PM ----------

https://xdaforums.com/showpost.php?p=72475340&postcount=6937
[Samsung Galaxy S 5 Unified Development] bitnerd:
Has anyone been able to encrypt an S5 recently? I reloaded a bunch of phones with the latest lineage build and can encrypt the other types but it fails on the S5 ones I have (t-mobile and Verizon). The process will run for about 30 seconds and then just reboot like normal
[Samsung Galaxy S 5 Unified Development] fitittome:
Just tried on a fresh install of the 12JUL nightly with latest baseband on an G900F. No probs.
[Samsung Galaxy S 5 Unified Development] bitnerd:
Interesting. I've tried it a dozen times on multiple S5s and it keeps failing. Tried it once on each of the other devices and it just works

I'll have to see if I can find some kind of error log and keep trying
[Samsung Galaxy S 5 Unified Development] street_samurai:
Two builds ago there were a bunch of fixes for encryption. If you haven't tried recently may be worth trying again.

I too encrypted my phone two weeks ago with no problems.
[Samsung Galaxy S 5 Unified Development] fipsy:
I have these problems with any filesystem type. With ext4 on the internal sdcard as well as with exFAT or vfat on the external card (tried both). Copying and deleting files to the /data partition doesn't produce any problems just copying to /sdcard or external card. So it maybe a problem with mounting parameters. But then everyone should encounter this issue. Baseband version is G900FXXU1CQA3.

I had these problems from the first moment after I flashed LOS 14.1 with Odin in March.
[Samsung Galaxy S 5 Unified Development] fitittome:
I got a free space issue to reproduce but on reflection I am not at all certain its the same thing. Others were seeing data corruption.

https://xdaforums.com/showpost.php?p=73039412&postcount=7426

I think it needs a bullet proof, simple way, to reproduce. Grab a logcat and get it onto the current Bugbash as it's open until the end of today.
[Samsung Galaxy S 5 Unified Development] fipsy:
But this is a VERY bad design as it let's your internal sdcard run full in a copule of days without reboot. My sdcard normally has about 6 GB of free memory. As I'm working quite a lot with big files on the internal card due to speed reasons (video editing and things like that), my internal card is running out of memory within a few tenth of minutes without rebooting and this even causes crashes with data loss and files in lost+found. This is absolulety inacceptable! I can't reboot every 20 minutes when editing videos. And this is not a bug but a feature? :eek:

These are problems we had at last in the early 80ies with MS-DOS 1.0.

By the way: It's not a refresh bug in files app. It's the same with every file manager (also tried ES, Root Explorer, Total Commander).
[Samsung Galaxy S 5 Unified Development] fitittome:
I 100% agree! :) But I think if it's logged on Bugbash as "my SD-Card always corrupts", without a logcat and a simple way to reproduce the problem the JIRA Police will close it straight away! Just saying. ;) I will take some time out and log what I have done in that previous post, but I am not certain that it's the same issue. Do you see what I mean? I dunno!
[Samsung Galaxy S 5 Unified Development] bitnerd:
Just wiped and installed the latest build. Set up a pattern lock, didn't install root or any apps, and encryption failed again 30 seconds after it started to run
[Samsung Galaxy S 5 Unified Development] fipsy:
I'm not sure if I would take the risk to corrupt my phone when trying to reproduce a crash with data loss. I just established the phone with a lot of work for my daily use. I could make a nandroid backup, take a new external sdcard and reproduce the issue. But I will not be able to accomplish this today.

I see - but I think it's the same issue. It's not too complicated! Just copy a file, delete it afterwards and watch the free space while doing this. Should be reproducible for everyone in a minute. :p

Another strange thing: Computing free memory seems to be a general problem on LOS 14.1. The actual busybox states about 2.8 TB of internal sdcard memory on my S5:

# busybox df -m
Filesystem 1M-blocks Used Available Use% Mounted on
tmpfs 197039 166 196873 0% /dev
tmpfs 197039 0 197039 0% /mnt
/dev/block/platform/msm_sdcc.1/by-name/system
557753 334084 223669 60% /system
/dev/block/platform/msm_sdcc.1/by-name/userdata
2797741 1337889 1459852 48% /data
/dev/block/platform/msm_sdcc.1/by-name/cache
45903 979 44923 2% /cache
/dev/block/platform/msm_sdcc.1/by-name/apnhlos
4486 488 3998 11% /firmware
/dev/block/platform/msm_sdcc.1/by-name/modem
3728 3086 642 83% /firmware-modem
/dev/block/platform/msm_sdcc.1/by-name/efs
3210 1004 2206 31% /efs
tmpfs 197039 0 197039 0% /storage
/dev/block/loop0 22033 1103 20930 5% /su
/data/media 2797741 1337889 1459852 48% /mnt/runtime/default/emulated
/data/media 2797741 1337889 1459852 48% /storage/emulated
/data/media 2797741 1337889 1459852 48% /mnt/runtime/read/emulated
/data/media 2797741 1337889 1459852 48% /mnt/runtime/write/emulated
/dev/block/vold/public:179_65
443825 216207 227619 49% /mnt/media_rw/0695-B70B
/mnt/media_rw/0695-B70B
443825 216207 227619 49% /mnt/runtime/default/0695-B70B
/mnt/media_rw/0695-B70B
443825 216207 227619 49% /storage/0695-B70B
/mnt/media_rw/0695-B70B
443825 216207 227619 49% /mnt/runtime/read/0695-B70B
/mnt/media_rw/0695-B70B
443825 216207 227619 49% /mnt/runtime/write/0695-B70B
[Samsung Galaxy S 5 Unified Development] street_samurai:
I'd grab a logcat (if possible) and post it and maybe someone can help you with it.
[Samsung Galaxy S 5 Unified Development] bitnerd:
Yeah managed to find a computer around here I could use for a bit. Logcat is located here. If anyone has time to look through it I would appreciate it
[Samsung Galaxy S 5 Unified Development] fitittome:
"Orig filesystem overlaps crypto footer region" hmm. That maybe the clue. No idea how to fix it. :( Maybe some body has come across similar before?
[Samsung Galaxy S 5 Unified Development] bitnerd:
Glad you noticed something that was probably the problem in there. There are too many errors and warnings for me

Hmm, I've reformatted over and over but apparently that's not good enough
[Samsung Galaxy S 5 Unified Development] fitittome:
Check out the summary on this link. There is a link back to XDA on there. Maybe? The fastboot stuff mentioned does not apply to S5. https://forum.fairphone.com/t/encrypt-phone-with-fairphone-open-os/15474
[Samsung Galaxy S 5 Unified Development] fipsy:
I made some more attempts. It is an issue with mounting parameters - as I earlier supposed.

https://www.kernel.org/doc/Documentation/filesystems/ext4.txt:

discard	Controls whether ext4 should issue discard/TRIM
nodiscard(*)	commands to the underlying block device when
blocks are freed. This is useful for SSD devices
and sparse/thinly-provisioned LUNs, but it is off
by default until sufficient testing has been done.

I remounted the sdcard with the additional parameter "discard" and after this modification deleting files immediately changed free space to the proper value. I can't understand why this parameter isn't used. Especially as the internal sd is a kind of SSD and sparsely in space, too!
[Samsung Galaxy S 5 Unified Development] fitittome:
Genius! But it does say:- "it is off by default until sufficient testing has been done". Need to figure out a way to get a dev to check it out. Probably Bugbash, I guess.
[Samsung Galaxy S 5 Unified Development] j1gga84:
Is the issue with crashing camera already fixed/reverted?

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Samsung Galaxy S 5 Unified Development] fitittome:
No. Stick to the previous nightly if camera is important.
[Samsung Galaxy S 5 Unified Development] fipsy:
I think the last sentence of this description is meanwhile obsolete as TWRP recovery successfully uses discard when mounting partitions. I never had problems with TWRP. And TWRP really writes a lot. ;)
[Samsung Galaxy S 5 Unified Development] bitnerd:
Thanks for pointing out the error message I needed to look for in the log.

I managed to get it to work on one of the phones using the following

ls -l /dev/block/platform/*/by-name/userdata
umount /dev/block/mmcblk0p26
fsck.f2fs /dev/block/mmcblk0p26
mkfs.f2fs /dev/block/mmcblk0p26 22136735

This found the name of the device that was used by userdata and reformatted it to be 64k smaller. I then restored my backup on that new filesystem. When I tried the encryption this time it worked fine

Thanks for the help
[Samsung Galaxy S 5 Unified Development] wieman01:
It finally worked for me two builds ago. I deliberately did not enable any sort of lock screen and encryption worked perfectly fine for me on a fairly recent install. Try again without the lock perhaps.
[Samsung Galaxy S 5 Unified Development] bitnerd:
And I should have put this in when I wrote that post - that device name and block sizes are specific to my phone. Please make sure to use the proper device and sizes if anyone else attempts this

I remember I had a hard time removing the encryption from my phone in the past so who knows what I did to it to get it this way. But now it works great again
[Samsung Galaxy S 5 Unified Development] fitittome:
[MENTION=5110154]fipsy[/MENTION] [MENTION=4114467]10goto10[/MENTION]

SD-Card Bugbash https://jira.lineageos.org/browse/BUGBASH-814

[MENTION=3305075]bitnerd[/MENTION] [MENTION=5110154]fipsy[/MENTION]

Thanks. Tonight is the night that I realize everyone smarter than me.
[Samsung Galaxy S 5 Unified Development] dud root:
Smart lock by location not working on kltedv 12-7. I've tried deleting and readding
[Samsung Galaxy S 5 Unified Development] fitittome:
One thing. I see the file deletion/free space problems and my sd-card is vfat not ext4! :confused:

edit: vfat also has the same mount option as ext4 for the same purpose.
[Samsung Galaxy S 5 Unified Development] fipsy:
I just wanted to mention what you said in your edit. :)

It also occurs on my (64 GB) SDXC sd-card which is exFAT formatted.

So now, as we have found the reason for this issue and also a very simple solution, we may hope that the developers are prudent and add this mounting parameter... :cyclops:

---------- Post added at 12:59 PM ---------- Previous post was at 12:34 PM ----------

@fitittome: I just see that your submission on bugbash has been rejected! Sorry, but I'm lost for words...

Do they want to tell us that data corruption is a feature of LOS?!

If they are not willing to change this I will create a shell script that is executed after booting with SManager (great app!) and remounts the sd-cards with proper parameters. But this would be a very dirty solution.
[Samsung Galaxy S 5 Unified Development] fitittome:
It's the Jira Police! :( I didn't submit a logcat because I did my testing a few weeks ago and was on a machine at work. Bugbash is only open on the weekend....... So I submitted it without one and got busted. :( Luckily, I had a spare S5 at home and was able to reproduce and pull a similar logcat at 5am this morning!!!! They did say it would be re-opened once the logcat was submitted. :fingers-crossed:
[Samsung Galaxy S 5 Unified Development] fipsy:
Okay, I'll help you and cross my fingers, too! :D

Just on the edge: Is someone interested in a patched linker binary for LOS14.1? Since Android 5 you are not allowed to execute binaries from arbitrary folders in the filesystem. It's called PIE (position independent executable security check) and was introduced by Google for security reasons. Trying to execute your own binaries from any folder results in the linker error: "error: only position independent executables (PIE) are supported". There is a quite good guide for patching the linker to avoid this error: https://www.alphagamers.net/threads/guide-bypassing-pie-security-check-android-5-0-up.242363/. I created a TWRP installable ZIP with the patched linker. Perhaps someone maybe interested. I use it because the Online Nandroid App doesn't work anymore and so I modified the onandroid script from Ameer Dawood (https://xdaforums.com/showthread.php?t=1620255) to work with LOS14.1. Now I make a nandroid backup automatically two times a week with SManager and upload it to my ftp server with FolderSync App. This wouldn't be possible without a patched linker.
[Samsung Galaxy S 5 Unified Development] Brasscat82:
Is the camera bug a legitimately confirmed bug in LOS? 'Cause my Snap camera is fully functional..

if there's anything I can do to help the devs, I'd be willing. Just need some detailed instructions to.get what they need.

g900R4, Resurrectionremix 7.1.2 7/15
[Samsung Galaxy S 5 Unified Development] darzur:
Does your Snap Camera work from the Lockscreen? I'm asking because mine very often hangs when opened from the lockscreen (locked with finger) and then I have to stop it and open from home screen...
[Samsung Galaxy S 5 Unified Development] FlexiPack:
I'm also getting the reboots when using the camera. (build lineage-14.1-20170712-nightly-klte - no mods) It's intermittent and happens when using different functions of the camera. So far it's rebooted when

launching the camera from home screen

Double pressing the power button to launch camera

switching HDR on/off

I'm going to try the previous build, can I dirty flash the previous build over the current one?
[Samsung Galaxy S 5 Unified Development] fitittome:
You will see that on most variants, just revert to 7JUL nightly. You are meant to RESTORE (normally via a TWRP backup) to roll back. This works flawlessly. Flashing an earlier nightly over a more recent one may well cause problems., not something I would recommend just in case.....
[Samsung Galaxy S 5 Unified Development] FlexiPack:
Thanks for the info. I came straight from CM13 so don't have a backup to roll back to. Do you know if it's likely to be fixed on the next nightly?
[Samsung Galaxy S 5 Unified Development] jdrch:
Yeah start updating weekly with as new builds are released.

Instructions here.

Sorry for the delay in replying; I was out of town yesterday.
[Samsung Galaxy S 5 Unified Development] fitittome:
No idea, the dev has it in hand. https://jira.lineageos.org/browse/REGRESSION-832
[Samsung Galaxy S 5 Unified Development] jdrch:
SM-G900V rebooting on Snap camera being opened too on this end. I saw the changes are being rolled back, so I'll wait for this week's build to see if that's fixed.
[Samsung Galaxy S 5 Unified Development] j1gga84:
What is the reason for switching to weeklies? Don't tell me that LineageOS 14.1 already comes into final stage.. ;)

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Samsung Galaxy S 5 Unified Development] jdrch:
See the official LineageOS blog for the answer. It's in their 1st 2 or 3 posts.
[Samsung Galaxy S 5 Unified Development] jeremywh7:
that ext4 readme is old

Discard is very thoroughly tested now; that part of the readme was last updated in Nov 2009.
[Samsung Galaxy S 5 Unified Development] fitittome:
Wow. I remember admiring that table some time back. You have good info there... Or maybe painful experience? Great work.
[Samsung Galaxy S 5 Unified Development] jdrch:
Thanks :). And it's both over the years. That particular post, however, was driven by the need to document what I was doing so I could easily repeat it later, not a problem.
[Samsung Galaxy S 5 Unified Development] jeremywh7:
Nice work there. :) So, that tells me it might be safer/easier to update via OEM ROM update, then flash back to custom. :eek:

Figured I'd do a bit more sleuthing... :cowboy: [also the most emojis I've used in one post :-| ]

F2FS' documentation added Discard in April 2013; defaulted on.
[Samsung Galaxy S 5 Unified Development] jdrch:
Thanks but technically that's not what I said. What I said is update the non-ROM and non-recovery partitions of the phone with stock partitions from your carrier/OEM. Make better sense now? There's nothing to "flash back to" after the process because all you've done is change the version number of what was already there, not replace it with something new.
[Samsung Galaxy S 5 Unified Development] milesius:
Hi jdrch,

After reading the instructions on your page I have some questions I am sure you can answer. I am trying to use an S5 G900V on T-Mobile, with LineageOS 14.1 and for the most part it works. However, my data drops from time to time and the connection to tmobile network seems flakey.

Am I supposed to download the G900V files from SamMobile to update those other partitions? It sounds like this would fix my issues.
[Samsung Galaxy S 5 Unified Development] jdrch:
Yes, I would update the firmware partitions with the G900F files from SamMobile 1st to see it fixes the issue. Failing that, I'd do a nandroid backup and then clean flash 14.1. If your data problems disappear, then something's wrong with your current installation and I'd just junk it and start from scratch. If they still exist then it may either be a T-Mo issue or you may need to rebuild the phone's NVRAM (warning, that last part is a very long shot in the dark, but it's based on a similar GPS problem I had last year).
[Samsung Galaxy S 5 Unified Development] ToriRobobo:
Thanks for the help. So if I do it this way, it's just as thorough as reverting to stock, but without having to redo everything? I'll try this first then and hope it works (if not, I'll revert or try something else).

I tried to 7zip extract the tar.md5 file in the zip from SamMobile here https://www.sammobile.com/firmwares/galaxy-s5/SM-G900T/

The file: G900TUVU1GQC2_G900TTMB1GQC2_G900TUVU1GQC2_HOME.tar.md5

It gives me an error: tar.mdf there is no correct record at the end of archive. It also pauses at the end (100%) on the modem file and doesn't close on it's own with 1 error count, so I don't know if everything was extracted correctly. How do I fix this?
[Samsung Galaxy S 5 Unified Development] jdrch:
Let me try extracting it on my own when I get home and let you know. Might be tomorrow before I'm able to give you a definitive answer.
[Samsung Galaxy S 5 Unified Development] j1gga84:
You mean here:

https://lineageos.org/

I don't find any Infos there..

Regards

Gesendet von meinem SM-G900F mit Tapatalk