yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] jdrch:
That's what I do using a root-enabled file manager (ES Pro, in my case.) Alternatively you can also use a USB OTG cable attached to a USB thumb drive.

Yes, but I've never personally done it. I nandroid backup to a USB jump drive using an OTG cable.

The app sleeps/idles much better now than it used to - with the caveat that you often have to manually wake it to sync if you happen to leave the device idle for a long time or use a lot of other apps in between sessions. Yes, I remember back in the day when I'd have to kill the process when I disconnected from Wi-Fi to keep it from burning through battery life, but that's no longer the case, especially in the past month or so.
[Samsung Galaxy S 5 Unified Development] fbs:
I'm using a 64gb sandisk as portable storage with vfat.. I'm used to copying huge games (10-22gb) to it from my desktop from work, then I move to my home's desktop.. I've never saw a corruption or reboot/crash or missing files or slow transfer. The last one was a 22GB folder, with five 4GB files inside it..

I think if there was any bug about file size, folder size, huge copying or erasing, I should've trigged it already!
[Samsung Galaxy S 5 Unified Development] 10goto10:
To be fair, I never encountered the corruption bug while transferring files via USB from a PC to the MicroSD card. Transferring files wirelessly is a different story. Why? Is it because of the USB-MTP translation layer slowing things down just enough*? Memory corruption in the file cache/buffers? More investigation (and proper bug-report, elimination of variables and debugging) is needed.

Also, nandroid-backup-ing to a USB OTG drive is a clever idea! Thanks for the tip.

* (It is frankly ridiculous how you can transfer files faster over WiFi than using USB-MTP. This is anecdotally true for basically any android phone with eMMC internal storage or slower.)
[Samsung Galaxy S 5 Unified Development] jdrch:
Totally shooting in the dark here so apologize for the nebulous language, but it's well known that Android has timestamp issues for External storage (see Problem #3 here). This could conceivably lead to corruption for large network transfers. Just an idea.
[Samsung Galaxy S 5 Unified Development] 10goto10:
I don't think that's it. Corruption occurs when transferring files to the microSD from a USB OTG drive too. And it's easier to trigger the corruption by copying a bunch of relatively small files (a few MBs) instead of copying one huge file.
[Samsung Galaxy S 5 Unified Development] fitittome:
This reproduces the problem consistently

Device: SM-G900F

Baseband: G900FXXS1CQAV

Bootloader: G900FXXS1CQBW

LineageOS: 14.1-20170628-NIGHTLY-klte

TWRP: 3.1.0-1

Kernel: Stock

SD-Card: SanDisk 2Gb Micro

Addons: Diddley, zip, nothing

Method:

Formatted external sd-card in TWRP as vfat

Size 1881MB Free 1881MB

Copied four 219Mb files into root of /external_sd via USB from my PC

Wipe->Advanced Wipe Tick Micro SDCard->Repair or change file System

Size 1881MB as expected

Free 1881MB (unexpected)

Rebooted.

Toast notification of new SD-Card, acknowledge and confirm it as portable storage.

Load 'Files' observe sdcard1 showing 0.98GB free.

Tapping sdcard1 and triple dot->Storage Settings confirms 876MB used of 1.84GB

select the four file in 'Files' tap trash can, confirm Delete 4 files.

triple dot->Storage Settings still confirms 876MB used of 1.84GB (unexpected)

the four files do not appear as I back out, as expected.

main screen in 'Files' showing sdcard1 having .98GB free. (unexpected)

Reboot to TWRP recovery

Advanced->File Manager->external_sd no files as expected

Wipe->Advanced Wipe Tick Micro SDCard->Repair or change file System

Size 1881MB expected

Free 1881MB expected

Oddly, note that TWRP get the free space wrong, right at the beginning, as the files are copied onto the file system. Is there some commonality here? I notice that klte hasn't received the latest TWRP. It looks like the build failed a month ago. Could the latest, if it were available have anything to do with this?

It transpires that if I goto Settings->Storage->Portable Storage Eject (or via the Toast message) after deleting files the changes get written to the SD-card.
[Samsung Galaxy S 5 Unified Development] ASVP_MSFT:
Mic issues

Hi, I tried flashing this rom (latest version 07/05/17) today and I have encountered a microphone issue. When making or receiving calls or recording with voice recorder app (also screen recorder) the mic doesn't pick up sound. However in Snap camera when I record a video it works. I'm using a G900T on baseband G900TUVU1GQC2, TWRP 3.0.2-1. Also when flashing I got this error.

Patching system image unconditionally...

E:unknown command [log]

E:unknown command [log]

Any help in resolving this please? :(
[Samsung Galaxy S 5 Unified Development] simthadim:
Hi All,

I am sorry to come here with a non specific ROM question: more of an indirect question.

I am running into a Heimdall problem such that I am unable to install this ROM. "heimdall print-pit", the step recommended on the setup guide of this ROM to verify the heimdall connection, fails: "unable to download PIT file". A connection is established regardless. Found many posts online stating a similar issue. Any of you face this and solved it? I did update the driver with ziadig.exe.

Running heimdall v1.4.0 on windows x32. Same issue with heimdall V1.4.1 on Ubuntu 17.04 (64 bit)

No need to download the pit file, it's only in the manual (lineageOS website) to verify the connection. If you guys didn't and flashed TWRP directly, do let me know. The phone needs to be usable, so bit weary to flash TWRP with the 'heimdall print-pit error' in mind.

thx!
[Samsung Galaxy S 5 Unified Development] HulkSmashBurgers:
Try updating to the latest version of TWRP, 3.1.0-1

https://twrp.me/devices/samsunggalaxys5qualcomm.html
[Samsung Galaxy S 5 Unified Development] Atento:
Switching from/to front an rear camera causes reboot on latest nightly.
[Samsung Galaxy S 5 Unified Development] HulkSmashBurgers:
Works fine here. I always wipe cache & dalvik/art after update. Have you done that?
[Samsung Galaxy S 5 Unified Development] Atento:
No, I haven't. I did a clean installation though.

Did you dirty flash?
[Samsung Galaxy S 5 Unified Development] HulkSmashBurgers:
Yep. Haven't done a clean install in quite a while.

When I do a clean install, I always wipe boot, system, data, cache, and dalvik/art.
[Samsung Galaxy S 5 Unified Development] fitittome:
I am seeing issues with rear facing camera on the LOS Camera and Snap Camera App with the 12JUL nightly too. I'll check on a fresh install later.
[Samsung Galaxy S 5 Unified Development] Atento:
Tried Snap Camera, same issue.
[Samsung Galaxy S 5 Unified Development] SB4BBs:
In cm14.1 10/31 can't disable NFC. Must be a reasons of battery drain
[Samsung Galaxy S 5 Unified Development] Jonny:
I've just read the last 3 pages and there doesn't seem to be anything wrong, am I missing something?
[Samsung Galaxy S 5 Unified Development] pota--:
THX bro everythigs works fine ???
[Samsung Galaxy S 5 Unified Development] harise100:
On 31/10:

- Sensor Screen Rotation breaks while using the phone

- Plugging OSB-OTG causes reboot

- NFC is broken

Rest works for me so far.
[Samsung Galaxy S 5 Unified Development] shjeanpy:
Sorry, in 14.1 supersu don't give root access. I try to restaure my buck up apps by titanium but no way to get root. Same help please
[Samsung Galaxy S 5 Unified Development] gcd99br:
Have you activated developer settings? Go on about phone and do the trick...

---------- Post added at 10:54 AM ---------- Previous post was at 10:53 AM ----------

What's your variable and model?
[Samsung Galaxy S 5 Unified Development] maro777:
For me, the lack of access to the root activated developer settings.
[Samsung Galaxy S 5 Unified Development] gerrycooper:
SIM2 calls are muted on G900FD

I tested the 20161031 14.1 version on G900FD.

It looks good so far, very good job:)

But the calls made and received by SIM2 are muted.

On SIM1 everything is okay.

Is there a possibility to fix?

Is there a changelog for new versions?
[Samsung Galaxy S 5 Unified Development] aogakid:
I didn't know about this, are there another apps that support this?
[Samsung Galaxy S 5 Unified Development] ThaiFighterGo:
Just dirty flashed klte 10/31 build. Tested NFC and it works. Used the tag in my truck and paired my blue tooth headphones w/ the NFC tag.
[Samsung Galaxy S 5 Unified Development] thiaguinhox:
[MENTION=2693412]haggertk[/MENTION]

Hello, I tested the version in cm14.1 G900MD / FD and use only one simcard in any of the slots, it works normal, but if you use the two Simcard while sim1 + sim2, SIM2 is muted during calls, nobody listens to me and I do not hear anyone.

I look fix.

Thank you
[Samsung Galaxy S 5 Unified Development] HAJT669:
Any sign of CMThemeEngine!?
[Samsung Galaxy S 5 Unified Development] candreva87:
+1, g900f
[Samsung Galaxy S 5 Unified Development] 343N:
so uh, i've been using 14.0, i just updated to the latest version, and a small but annoying bug exists here. changes to the battery icon in the status bar don't do anything

example:
[Samsung Galaxy S 5 Unified Development] haggertk:
OK everyone, I see the USB-OTG problem. Diagnosing it is difficult since without being directly connected to the phone we only get logs as long as WiFi stays up and it's compounded by the fact that we don't have last_kmsg.

That said, it worked fine before the first big update to 3.4.10, so it is bisectable. It might take a little bit, but I'm not likely to release any more builds until it gets fixed. I use OTG myself periodically, so I'm incentivized to figure it out.
[Samsung Galaxy S 5 Unified Development] haggertk:
I've gotten that report before (I really need to update the known bugs in first post). I'm going to need to try to reach out to other developers who have msim devices, since I don't have one in hand myself. I expect that like almost always it will be something easy and dumb that needs to get tweaked.
[Samsung Galaxy S 5 Unified Development] laurorual:
how did you dirty flash?

installed rom, then gapps, wipe cache and dalvik?
[Samsung Galaxy S 5 Unified Development] candreva87:
Are you still on cm 14 or 14.1?
[Samsung Galaxy S 5 Unified Development] gcd99br:
What's your variable?

---------------------------------------------------------

The reboot options on the menu is not showing... Only to me?
[Samsung Galaxy S 5 Unified Development] :
Just my 2 cents, [MENTION=2693412]haggertk[/MENTION]. But i'm guessing that this issue was fixed in a later linux-stable and/or fixed in linux-msm tree ad/or one of the galaxy s5 kernel trees that includes linux-stable on github... Out of curiousity, is Ozzy just using the straight up linux-stable patches to catch klte up to linux-stable manually or is he using on of the aforementioned kernel trees?

From my perspective, it might make sense to use linux-msm, since it is very similar to our tree, minus some of samsung's botchery and whatever cherry-picks/commits have been added by CM... but again, idk how Ozzy is going about merging all of the linux-stable tree. Anyway, I thought I'd point it out, as maybe it could save some hassle, if he is currently doing it all manually from linux-stable.
[Samsung Galaxy S 5 Unified Development] shkedov:
So I said to myself that I'll wait for this update before posting on JIRA. And they fixed it! :victory:

Thanks a lot devs!

BTW [MENTION=2667313]Atento[/MENTION], I'm with latest nightly (my first installation was clean, updates are flashed dirty via OTA) and no problems for me in switching between cameras, both directions. Just reporting. Good luck dude
[Samsung Galaxy S 5 Unified Development] Panzerknakker:
+1

rear to front works, back from front to rear reboots.

zip flashed manually in twrp-3.1.1-0-klteduos, wiped cache and dalvik.

G900FD, 14.1-20170712-nightly-klteduos, BL G900FDXXS1CQD2, CP G900FDXXU1CQA4

edit: Used Open Camera v1.39 (latest) and built in Kamera

edit2: need sometimes several switches between rear and front to reproduce reboot.
[Samsung Galaxy S 5 Unified Development] eurohunter:
flash doesn't work on the camera that comes with the rom?

---------- Post added at 02:48 AM ---------- Previous post was at 02:33 AM ----------

Yes, it is happening to me as well. G900P latest nightly. built in camera and Open camera. Switching from front to rear camera reboots my phone.

Other cameras (Google camera and Footej) make my phone reboot as soon as I open them in rear view.
[Samsung Galaxy S 5 Unified Development] fitittome:
As it happens on a fresh-clean install without anything else installed, like Gapps etc. I've logged a JIRA, maybe vote on it? :-

https://jira.lineageos.org/browse/REGRESSION-832
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Guys, the camera issue in the latest build is likely because of some recent commits (not fully sure) in the kernel source code. I'm using my own custom kernel (SmartPack) and solved that issue by reverting that commit (don't know its a permanent solution).
[Samsung Galaxy S 5 Unified Development] Panzerknakker:
Tested your 3.4.113-g82af9b3-dirty klteduos kernel. Open Camera hangs after some flipping and finally reboots.

Edit: Could not find this version in your git repo.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
mm... either I'm (my prediction) wrong, or the issue is more device specific (Mine using kltekor).

Here is my github repo and the commit is still there though I reverted this specific commit from my local repo...
[Samsung Galaxy S 5 Unified Development] fitittome:
Skimming the information in the previous posts it looks like this:-

SM-G900T = OK

SM-G900M = BROKEN

SM-G900F = BROKEN

SM-G900FD = BROKEN

SM-G900P = BROKEN

It would be really helpful if the the users signature contained the model/variant/baseband info etc.
[Samsung Galaxy S 5 Unified Development] shkedov:
Also SM-G9006V = OK

(I have a kltechn device)
[Samsung Galaxy S 5 Unified Development] 10goto10:
Besides repeated camera switching crashing the device, I found that camera document scanning apps also crashes the device. Doesn't matter if I use the flash or not. (App is TurboScan, SM-G900F, 20170712 nightly.)
[Samsung Galaxy S 5 Unified Development] street_samurai:
July 12th build:

SM-G900W8 (G900W8VLS1DPF3) = BROKEN in Snap Camera

Also there is no option in any camera to turn Flash on. (although this was missing in previous builds too).

There were a bunch of camera related updates in the last two builds so I'm sure something just got borked along the way.
[Samsung Galaxy S 5 Unified Development] j1gga84:
G900F - broken

I can also not do video recordings anymore but I think this is ROM related because it should work on a clean install..

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Samsung Galaxy S 5 Unified Development] HosseinMoradi2007:
emergency numbers issue

i have an old issue with emergency numbers in my G900FD

if i call an emergency number using google dialer from stock gapps the call is made and i can talk but there is no UI to see or end the call
[Samsung Galaxy S 5 Unified Development] J-Lindo:
Running the LOS July 12th build on a G900V, baseband QD1, LOS kernel, 3.1.0-1 TWRP. Tried switching cameras on both Snap and stock 10+ times, never crashed or rebooted the phone.

Edit: Okay, NOW I'm having issues with Snap. When I open the app, it appears to open as normal and the camera view shows, but freezes after about a second, and reboots the phone. Happened multiple times, including after doing a Force Stop.

Stock camera seems somewhat better, but when I tried to catch a panorama of a rainbow, it crashed while it was processing the full image. Not sure if it's related, but hey, just throwing it out there.

Edit: Cleared the data, and Snap started working again (for now). Hooray!
[Samsung Galaxy S 5 Unified Development] marty_s13:
G900I here. Phone reboots if I switch cameras a number of times.
[Samsung Galaxy S 5 Unified Development] vbShellX:
had same problem

after delete camera data

everything ok

after a few pictures the problem returns
[Samsung Galaxy S 5 Unified Development] thaidroid:
I use Cameringo Lite camera, Dirty Flashed latest build and no problems switching front and back or anything else that I have noticed.
[Samsung Galaxy S 5 Unified Development] fitittome:
It looks like [MENTION=2693412]haggertk[/MENTION] has rolled back the Camera changes but as nightlies are now weeklies there will be a wait for the new build. It was an odd problem, perfectly reproducible yesterday, but when I switched ADB on to get a logcat of the reboot the phone behaved perfectly! Anyway, I have learnt that you can waste half a day without a logcat!!!!!!! Please post them.........
[Samsung Galaxy S 5 Unified Development] haggertk:
Well, it's odd. And as you say, not readily reproducible. Because of that, it might take a while tracking down the real cause. If it is kernel like my JIRA note mentioned, it's hard to bisect a failure that does fail every time.

Anyway, I'm kind of leaning towards blobs now since the failure does happen on a rebased klte kernel I'm working on... /shrug
[Samsung Galaxy S 5 Unified Development] fitittome:
Apologies, I misunderstood the jira comment. I did manage to get a logcat off a fresh G900F and post it to jira. I guess it would help if others could post their logcats too, I'll get them uploaded.
[Samsung Galaxy S 5 Unified Development] J-Lindo:
I'm a bit new at this catching and uploading logcats business, but I'm happy to say I made my first one! Try as I might, I could not get Snap to misbehave like it did to me yesterday. However, there still seems the problem with stock camera's panorama, which this time actually crashed the app. I managed to get a logcat when it did that. I've attached it to my post, but if someone can point me the right direction for the proper place to put it, I'd be most appreciative. In the meantime, I'll keep trying to get Snap to do its thing. I'm thinking I'll try re-flashing the new nightly and see if that does anything.
[Samsung Galaxy S 5 Unified Development] FirebirdDE:
Does anyone else have other random reboots, unrelated to camera usage? I have opened a bug in Jira, but cannot really find a reliable way to reproduce the issue yet.

https://jira.lineageos.org/browse/REGRESSION-840
[Samsung Galaxy S 5 Unified Development] fitittome:
Congrats! Me too. :) Let me know you model no and baseband, I can see the logcat, and I will re-post it to the Jira.

---------- Post added at 08:29 PM ---------- Previous post was at 08:26 PM ----------

No! Rock solid on G900F with latest baseband and twrp. Its a pain, but have you tried with clean install?
[Samsung Galaxy S 5 Unified Development] J-Lindo:
Sorry, figured you'd've seen my last post xD I'm on a G900V with baseband QD1. Thanks a bunch! Also, I just got to work, and Snap is giving me hell again. So I'll let it be until I get home tonight and attempt a logcat with it.
[Samsung Galaxy S 5 Unified Development] j1gga84:
I have an app not starting anymore.

What could be the reason for that? I have a log attached that shows the error.

Some security related issue. I am using SuperSU, not magisk if that is helpful in any way.

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Samsung Galaxy S 5 Unified Development] simonsalo:
Hello. I have just switched to a galaxy s5 sm-g900m. Where exactly is the Lineage download for this device? The link on the first page just goes to a general lineage download page. Then under samsung there are several Galaxy s5 official version downloads. which one is the SM-G900M for Brazil?
[Samsung Galaxy S 5 Unified Development] Atento:
It is KLTE, which is under lineage os download web page
[Samsung Galaxy S 5 Unified Development] street_samurai:
Seems like most people here use Lineage Root or Magisk. I think you'd have more success asking in the SuperSu forums. They'll probably want a logcat not a screenshot.

Have you tried removing SuperSU and trying the app with Lineage's root?
[Samsung Galaxy S 5 Unified Development] @richardnote2:
Im using boeffla latest. But when i reboot my phone and where in boeflla is configuring the settings. It goes hang and freeze and suddenly reboot continually. How to fix this. I cant ise my phone.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Wrong place... should be addressed by Lord Boeffla. So, ask in Boeffla Kernel Thread...
[Samsung Galaxy S 5 Unified Development] J-Lindo:
Aha! Good [MENTION=7978913]fitittome[/MENTION], I managed to create a logcat as Snap froze and rebooted the phone. I had to open and close it a few times, but about the third or fourth time is when it crashed (I didn't need to swap cameras for it to trigger).

Only thing though, the logcat didn't seem to write anything at the time of death. But, then again, I have no idea how to read a logcat, so it could very well be there. So here it is!

Again, model G900V, baseband QD1. Perhaps I ought to just put it in the signature :p
[Samsung Galaxy S 5 Unified Development] furkaan28:
[MENTION=2693412]haggertk[/MENTION]

i tried to get a logcat and filtered some errors

https://pastebin.com/tDRYcepH

Edit: g900f klte
[Samsung Galaxy S 5 Unified Development] fitittome:
Thanks but what Model? What Baseband?
[Samsung Galaxy S 5 Unified Development] FirebirdDE:
Thanks! No, I have not, because (IMHO) nothing in Userland should ever lead to a Kernel Panic - this is definitely a kernel bug. But it is a good hint that the bug doesn't affect everyone, obviously one of my apps triggers it. I'll dig deeper when I find the time.
[Samsung Galaxy S 5 Unified Development] fitittome:
You maybe able to get some log info after the random reboot by doing something like this in terminal if you have the addonsu installed:-

su
cat /proc/last_kmsg > /mnt/sdcard/last_kmsg
[Samsung Galaxy S 5 Unified Development] FirebirdDE:
I know, I already included the panic message from last_kmsg in the original Jira bug report :)
[Samsung Galaxy S 5 Unified Development] chainzy:
Is the rotation issue for images being looked at? My mms messages are still coming through rotated the wrong way
[Samsung Galaxy S 5 Unified Development] fitittome:
I don't recall anyone else mentioning this. I may just be you. You probably need to do a fresh install and make sure your baseband etc. is up to date. If you are still getting the problem you will need to get logcats just prior to the msg being received then post the problem up onto JIRA. It will be a BUGBASH and they accept them over the weekend only. Providing its accepted the problem will be allocated to someone to deal with.
[Samsung Galaxy S 5 Unified Development] chainzy:
I posted a while about it and someone mentioned that lineage has a issue with rotation as it was happening to them aswell. I recently updated baseband, and clean flashed the latest nightly for kltedv and its still happening. Happens with all my mms messages. What's the best way to capture a log for receiving a mms so I report that.
[Samsung Galaxy S 5 Unified Development] fitittome:
Maybe they reported it? Check JIRA.

Check the report bugs section here:- https://wiki.lineageos.org/
[Samsung Galaxy S 5 Unified Development] fitittome:
SD-Card problems

I know I got 'something' that was consistently reproducible but I am now not at all certain it is the same as what some of you others [MENTION=4114467]10goto10[/MENTION] and [MENTION=5110154]fipsy[/MENTION] were getting with SD-Card corruption etc. You know, what I am reproducing may just be a 'refresh bug' in 'files' app as I didn't see any corruption, 'per se'. As BUGBASH is open I was thinking someone should log the corruption problem with proper logcats and all. :fingers-crossed:
[Samsung Galaxy S 5 Unified Development] systemcrash:
Yeah, had a few random reboots on the latest 'nightly' lineage-14.1-20170712-nightly-klte-signed.zip - all but one happened when I was using the camera app. One was when my phone was unlocked and I was doing something else. It was late and I wasn't too sharp to catch exactly what caused it. *shrug*

Rolling back to lineage-14.1-20170705-nightly-klte-signed.zip

G900F