yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] :
using just Apps/root should be fine, unless u plan on using root with adb. ie; when connected to your computer...

generally speaking, adb and root both introduce security concerns, so if ur not using root with adb, disable it... personally, i also disable adb unless i am using it.

it shouldn't, but there does appear to be somethjng going on here (i'm experiencing the same thing). i set my device so that when it's plugged in - it doesn't sleep... then it charges fine... idk, maybe there is an issue with wakelocks, that's what i suspect anyway...

and user builds are not the default because all cm roms are userdebug builds and IIRC, u lose some functionality/flexibility, if building user builds.
[Samsung Galaxy S 5 Unified Development] RemusW:
SMS issue

Update,

I am able to receive SMS messages but despite having full signal bars and credit on my phone i can not send them.

Also the same sim card works fine in another phone and sends and receives SMS message without issue.

thanks again for all your hard work bringing these roms to us we all appreciate it.
[Samsung Galaxy S 5 Unified Development] jwenthold:
just an FYI, I used the opengapps stock package and everything works nicely
[Samsung Galaxy S 5 Unified Development] godofsalt:
Just AWESOME CM14.1

Honest, coming from the Nightly Build from CM13, this is rather awesome. If anyone differs, go someplace else....

Now the only issue that I have come across is Titanium Backup, only true backup of its kind, since the actual first build.

Yes, I learning how to live without it. Sort of! Would anyone know, i have something close to T. B.??? Not some BS app. Something rather simple a a true back up. Been trying that new Apps2Sd, but too much other than that BS.

Anyway, this CM14.1 is truly awesome. Can deal with any sort of isssue that I have seen.

Sir, I thank you very much. I truly know how much work, plus the time that you have put in here. Than you.
[Samsung Galaxy S 5 Unified Development] james_rokr:
How can I root this rom?

I mean SuperSU (2.78) breaks my WIFI and there's no way for accesing developer menu of CM14.1 (it crashes)
[Samsung Galaxy S 5 Unified Development] :
don't install supersu, it breaks things currently.

does dev. settings crash AFTER you have installed supersu, or just generally? ... it would seem to be working for most people... maybe try a clean install to verify...
[Samsung Galaxy S 5 Unified Development] aogakid:
Crashes when you open it or you can't activate it?
[Samsung Galaxy S 5 Unified Development] james_rokr:
It crashes as soon as I try to open it after activating it on about menu, it isn't SuperSU the cause behind this problem, for it happens just after a fresh intallation of CM14.1 and OpenGapps (7.1 pico), so in other words, I can't even access the Dev menu, for the whole menu FC's when I try to go in there
[Samsung Galaxy S 5 Unified Development] rayzor666:
Have you checked the service centre number in service mode. I had the same issue
[Samsung Galaxy S 5 Unified Development] aogakid:
Do you have any module/xposed/app-root installed? Try to wipe dalvik&cache then flash the ROM with gapps
[Samsung Galaxy S 5 Unified Development] Corypeach:
I'm having trouble with the apk installer not working on 10/31 kltevzw. It says problem parsing package. Am I missing something?

And yes it is a dirty flash and I know I should try a clean flash I'm just curious if someone else has this problem or if there is a simple fix
[Samsung Galaxy S 5 Unified Development] alex19EP:
Check permissions for it and enable all

Отправлено с моего SM-G900F через Tapatalk
[Samsung Galaxy S 5 Unified Development] Corypeach:
Thanks that fixed it :good:
[Samsung Galaxy S 5 Unified Development] galaxyornothing2:
Do not install supersu after flashing. Instead go to settings, about phone and activate developer options. Open and go to root access an activate apps and adb. You are now rooted.
[Samsung Galaxy S 5 Unified Development] mattnin:
Does anyone have any tips to take low light pictures? Using the TW stock camera, the S5 can take excellent pictures with no flash and low light. In Lineage, it seems there is always some blur. Is there maybe a way I can increase the shutter speed? I've tried snap camera on the play store but still getting blur.

Why does everyone refer to the lineage camera as snap? Is it the same as snap camera on the play store?
[Samsung Galaxy S 5 Unified Development] Bobcus Leper:
Hi,

I have been able to take excellent TW quality photos on the stock camera app on LOS. The trick is to have stable hands when taking photos with HDR on, because of the slow shutter speeds. If you still get blurry photos, try turning your ISO to HJR, which will emphasise faster shutter speeds over less grainy photos.
[Samsung Galaxy S 5 Unified Development] fitittome:
It's really confusing isn't it? I think it's called the Snap Camera because it's optimised for Snapdragon. I could be wrong on that though.

It's originally from the same place that I get my Snapdragon optimised browser from.https://www.codeaurora.org/ I'm still working out how all this links in with what Lineage are doing.

As you have discovered there is also a Snap Camera HDR on the Play store by a company called Marginz software. It is different. But it's an amazing camera that does pretty much everything you could ask on an S5. Costs about the same as a pint of beer. :) It's the one I use and like.
[Samsung Galaxy S 5 Unified Development] Bobcus Leper:
Hmm... It must be the only CAF camera for AOSP (CAF stands for Code Aurora Forum for all who don't know).
[Samsung Galaxy S 5 Unified Development] fipsy:
Hello again ;)

After having been abstintent to this thread for a month (I had enough other things to do) I have now read all posts since the beginning of August. I was hoping that the problems with the external SD card, which I had repeatedly criticized, would perhaps finally been solved. Unfortunately far from it! But I am glad that I am no longer (as I was in march) the only one who has serious problems with exFAT formatted SD cards. It's nice to see that there is now rumburak's app to do a test. In my case, the app always returns an error (red) for the exFAT formatted SD card. Also for LOS version 2017-08-23 with SuperSU 2.82 SR3. The last working version was 2017-07-26. And unfortunately, this doesn't seem to have changed at all!

The error that it is no longer possible to receive media with WhatsApp (photos / videos) when the WhatsApp media folder is bound to a folder on the exFAT formatted SD card with Apps2SD is still present! And I think it has the same reason as all the other problems mentioned here in relation to the SD card. As [MENTION=7978913]fitittome[/MENTION] said: All this stuff with exFAT, SD card and MTP is a big mess on Lineage OS 14.1!

I am very disappointed about the development of Lineage OS and I once again return to the version from end of july. Really depressing!
[Samsung Galaxy S 5 Unified Development] fitittome:
I maybe wrong, I'm not a programmer, I don't know the history. I noticed that qcamera2 is included into quite a few devices on Github. Trying to untangle what goes on with CAF and Google releases jut completely confuses me.

---------- Post added at 06:36 PM ---------- Previous post was at 06:31 PM ----------

Just a big mess in general, but what do I know? I don't think it's specific to Lineage. It just doesn't work very well. this is an interesting article.
[Samsung Galaxy S 5 Unified Development] fipsy:
You may be right. But that doesn't explain why some things still worked in the LOS version from the end of July that now doesn't work anymore! So the LOS developers must have messed things up in connection with the SD card.

Edit: I have just read your linked article and commented out in /system/build.prop the line

ro.sys.sdcardfs=true

Now rumburak's app shows that everything is ok (green) for the external SD card. And suddenly WhatsApp also works with Apps2SD again! It is again able to receive media! So it's proved that the issue was related to sdcardfs.

Are there any disadvantages when disabling sdcardfs? If not, then I've found the solution to my biggest problem.
[Samsung Galaxy S 5 Unified Development] fitittome:
I was still seeing the free space issue with sdcardfs disabled but if it resolves your problems that's good news.

If sdcardfs is disabled the system falls back to fuse, I think.

Maybe it would be best to disable sdcardfs for the time being?
[Samsung Galaxy S 5 Unified Development] Cartoon69:
Yes, but this (on my phone) results in very poor multitasking, where it can take 30 seconds to switch app and where even the last used app is frequently closed. If my memory serves me, this started around beginning of August.

I am not sure if this is a general problem, or just something on my phone. I see a few others reports similar problems, but I just wanted to see if others had the same problems and maybe I can just wait and it will be fixed at some point, or I need to do something more proactively (like checking updates for bootloaders and various other pieces, tho my modem/LTE firmware has been updated).
[Samsung Galaxy S 5 Unified Development] jaholm:
This also fixed the bug with jpg files beeing 0 bytes in length when created on external sd card (with snap camera an XinternalSD )
[Samsung Galaxy S 5 Unified Development] fipsy:
Yes it does. And the free space error has also gone away. I copied 1 GB to the internal card, deleted it and the free space was the same as before. But it is very annoying to comment out the sdcardfs-line with the vi editor in the TWRP-shell after every new flash process!

BUT: I now also have the NFC error! It is exactly as [MENTION=5665105]iscario[/MENTION] and [MENTION=7405113]shinobusensui[/MENTION] described! It has nothing to do with baseband or modem, nor with the battery nor depends on the model (I have G900F). If I flash the LOS version 2017-08-02, NFC works fine, but if I flash the 2017-08-30 version, NFC doesn't work anymore. When I try to activate NFC in the settings, it becomes green at first, but immediately afterwards it turns grey again on its own. Just as described by shinobusensui. So the developers must also have messed up NFC!

At the beginning of the year I had already feared that Lineage OS would not achieve the quality of Cyanogenmod, but I hadn't thought that it would become that terrible. :(
[Samsung Galaxy S 5 Unified Development] fitittome:
Umm. I double checked the free space issue this morning (I thought I may have screwed up disabling sdcardfs! but I hadn't!) I am still seeing the same issue regarding free space. With and without sdcardfs being disabled! Also, I sat down quite happily with two 900F's yesterday with the 30AUG nightly and Bluetoothed back and fore without issue. These were two S5's with upto date firmware (Baseband: G900FXXU1CQA9 Bootloader: G900FXXU1CQH1), one had addonsu installed the other didn't. No custom kernels, themes, supersu, magisk or anything like that.

I'm not saying there isn't a problem, but whatever the problem is, it's not effecting everyone.
[Samsung Galaxy S 5 Unified Development] Hawaiihemd:
Maybe this could be interesting then: https://xdaforums.com/showthread.php?t=2664332
[Samsung Galaxy S 5 Unified Development] fipsy:
[MENTION=7978913]fitittome[/MENTION], [MENTION=5880102]Hawaiihemd[/MENTION]: I gladly gave you a "Thanks", but my 8 thanks for today are used up. ;)

That's VERY strange! I tried it again with the ES File Explorer just for you: Occupied space on /storage/emulated/0 before: 5.66 GB. Then copied 822.97 MB to /storage/emulated/0 (into the root directory). Used space afterwards: 6.47 GB. Then file deleted. Used space afterwards: 5.66 GB (without doing anything). I use SuperSU not addonsu. But I don't think it has anything to do with that.

I use Baseband G900FXXU1CQA3 and Bootloader G900FXXU1CQB3. Since I don't have any other problems with it, I don't want to change baseband and bootloader.

I absolutely agree with you! As you can see, it's the same with the freespace bug.

---------- Post added at 02:07 PM ---------- Previous post was at 01:58 PM ----------

Thanks for the advice! That's exactly what I needed! :D
[Samsung Galaxy S 5 Unified Development] fitittome:
ES file Explorer. Why does it need to know my Device ID & call information? I don't like it already.

Yes ES File Explorer works just fine. LineageOS supplied Files does not! FFS. :(
[Samsung Galaxy S 5 Unified Development] Nixda99:
Users with external SDCard Problems -> Try FAT32 / awesome GPS Performance now

Had the same problems with saving files on external SDCard since the August builds

(no Video in Snap camera, 0 byte files on extSD after update Offline maps in Osmand), but I have solved this problem.

My external SDCard was formatted with exFAT, because I thought, it is necessary for 64GB cards.

But it is not! Backuped all files from extSD to a PC, format the external SD in rom and copy the files back.

The rom formatted the extSD with FAT32 file system, but I don't know if it also works, if the PC format the SD with FAT32.

Can use the whole 64GB, no problems anymore with apps that will store data on extSD.

Had often 1 or 2 GPS Fix drops after starting the GPS app (with older builds of 14.1 and AOKP before). A fix with old GPS data need min. 30 seconds.

With the new 30.08. build, the GPS is working like in stock rom, 3-4 seconds for the first fix after long time without GPS and no fix drops.

1-2 seconds with fresh GPS data. Awesome!!!:good::good::good:

With Fat32 on extSD the new rom with the new kernel is a dream, also better battery consumption:D. Thanks to [MENTION=2693412]haggertk[/MENTION] and the LOS team.
[Samsung Galaxy S 5 Unified Development] fipsy:
I once got the pro version for 0,10 €. And I really like it. I also used Total Commander and Root Explorer. But ES simply is the best.

This is getting crazier and crazier. I don't understand it any more. It seems to me completely absurd.

Concerning NFC: It looks like a kernel-related problem. It only occurs on my smartphone when I use the Boeffla kernel beta8. With Stock-Kernel or Boeffla beta7 the problem does not occur. This explains the differences between users. Hence the question to [MENTION=5665105]iscario[/MENTION] and [MENTION=7405113]shinobusensui[/MENTION]: Do you use the LOS Stock kernel or another one (e. g. Boeffla)?

---------- Post added at 06:21 PM ---------- Previous post was at 05:57 PM ----------

The big disadvantage of FAT32 is that the size of files is limited to 4 GB. For example, recording long or large (4k) videos can cause serious problems. In addition, the cluster size is much larger than with exFAT, so that many small files waste a lot of space.
[Samsung Galaxy S 5 Unified Development] jdrch:
Same. The Pro version has none of the adware and has more features and capabilities than any other file manager I've tried.

---------- Post added at 13:10 ---------- Previous post was at 13:05 ----------

I noticed the GPS bug this morning when using Waze. Basically the phone seems to lose GPS location ever 30 to 90 seconds, regaining it within 5 seconds each time.

---------- Post added at 13:12 ---------- Previous post was at 13:10 ----------

Good to know, thanks!
[Samsung Galaxy S 5 Unified Development] thaijunk:
I can confirm that my phone also lags but it's intermittent. There was advice to disable sync for google app which seemed to have worked but eventually lag returned. I'm running latest firmware, modem, and everything with no special kernel. On kltevzw started on August builds. Came from an April build that didn't have this issue.
[Samsung Galaxy S 5 Unified Development] jdrch:
Yeah, performance was really bad on the previous 2 builds and is mostly below par on the current one.

---------- Post added at 13:29 ---------- Previous post was at 13:24 ----------

Same experience here.

Confirmed. It improved somewhat in the most recent build, however, so maybe the issue is being worked on? Like some other users I'm wondering if this is something that can be fixed in LOS or if it's just the device showing its age (too slow to run future builds fast enough?)

---------- Post added at 13:34 ---------- Previous post was at 13:29 ----------

How do we provide feedback to the devs responsible for this? Do we use JIRA as usual? The change is absolutely murdering the S5's performance, with frequent black or white blank screens when switching apps that never occurred before.

---------- Post added at 13:46 ---------- Previous post was at 13:34 ----------

I've filed a regression issue on the LineageOS JIRA. Everyone with this issue please either comment on that thread or upvote it so that it gets the devs' attention. Thanks!

---------- Post added at 13:59 ---------- Previous post was at 13:46 ----------

Since I use adopted storage on LOS, I'm not experiencing this, BUT I do recall a similar misreported storage capacity issue with the S7 when using the Modaco ADB hack to enable adoptable storage (which TouchWiz and Samsung ROMs in general don't support.) Basically, the OS would misreport available storage thereafter. Perhaps this issue is related in some way? Total shot in the dark, I admit.
[Samsung Galaxy S 5 Unified Development] jaholm:
After all it seems to me that sdcardsfs is the bad one in LOS. No problems when disabling this with ro.sys.sdcardfs=false when using exfat on ext sdcard or when ext sdcard is formatted as vfat.
[Samsung Galaxy S 5 Unified Development] fipsy:
I think that's rather unlikely. But who knows... Have you ever tried disabling sdcardfs to see if this solves the problem? Adopted storage uses ext4 as the filesystem instead of exFAT resp. vfat. So normally there should be no issues concerning free space.

---------- Post added at 10:45 PM ---------- Previous post was at 10:28 PM ----------

I can confirm that in its entirety! And the article that fitittome has linked says so too. Therefore, it is recommended to disable sdcardfs until the bugs are fixed.
[Samsung Galaxy S 5 Unified Development] jaholm:
The probability is high, that this sdcardfs bug is introduced with 20170802 from android_kernel_samsung_klte. See lineageos changes.
[Samsung Galaxy S 5 Unified Development] fipsy:
Definitely! 20170726 was the last version with no problems using folders bound to an exFAT formatted SD card via Apps2SD. All subsequent versions are troublesome. They only work with Apps2SD if sdcardfs is disabled.
[Samsung Galaxy S 5 Unified Development] systemcrash:
Edit hmm - sorry, I'm just sowing confusion - it was included in the msm89xx kernel change recently, plus the initial sdcardfs changes were part of the android_kernel_samsung_klte

https://review.lineageos.org/#/q/project:LineageOS/android_kernel_samsung_klte
[Samsung Galaxy S 5 Unified Development] Brasscat82:
Does this ROM also have the 3 beeps at the end of a call if the other party hangs up first? Or has that been fixed in LOS?
[Samsung Galaxy S 5 Unified Development] Saber:
Still a problem AFAIK.
[Samsung Galaxy S 5 Unified Development] eurohunter:
lol i have that too. a very random bug that never really bothered me, but it's there. i thought it was my carrier :)
[Samsung Galaxy S 5 Unified Development] Brasscat82:
I don't know how to link to other threads on here, but You can find the fix apk on ResurrectionRemix's thread by [MENTION=1462294]vd69[/MENTION], page 453. Tested and confirmed on sm-900r4 (klte) and sm-g900p (sprint).
[Samsung Galaxy S 5 Unified Development] Nixda99:
FAT32 on extSD

I record only with 1080p because the picture stabilizer is disabled with 4k. I record a 4k test video with 3min18s length, it needs 1.2Gb space, so I can

record around 10 mins videos with the 4Gb Fat32 limit, enough for me.

I have mostly bigger files on extSDcard, pictures, videos and offline maps. For this case the file system is faster than with a smaller cluster size, also not much lost of space, like for small files. So the bigger cluster size of Fat32 is also no problem for me.

I think the exFAT file system is not 100% working in LOS yet, had also a complete crash of an exFAT extSDCard of a friend with LOS 14.1.

After formatting to FAT32 no problems anymore for him. I had also sometimes problems with exFAT with the July and before versions, Windows

said that it must repair my card and I have some LOST files after that on the card.
[Samsung Galaxy S 5 Unified Development] valinor_7:
Not sure if this is the exact same problem or not, but you could try disabling telephone permissions for Snapchat. I had a similar problem and that fixed it for me.

Source:

https://www.reddit.com/r/Android/comments/6tzup1/psa_if_you_experience_a_loud_beep_through_the/
[Samsung Galaxy S 5 Unified Development] Brasscat82:
I have it fixed. My next post was the fix. I don't use snapchat
[Samsung Galaxy S 5 Unified Development] fipsy:
[MENTION=7978913]fitittome[/MENTION], [MENTION=5665105]iscario[/MENTION] and [MENTION=7405113]shinobusensui[/MENTION]: The NFC bug has been fixed. It was a problem with boeffla kernel. So I suppose iscario and shinobusensui also used boeffla kernel (too bad you didn't get back to us!): https://xdaforums.com/showpost.php?p=73686374&postcount=3602
[Samsung Galaxy S 5 Unified Development] systemcrash:
lineage-14.1-20170906-nightly-klte-signed.zip has landed.

Snap HFR changes do nothing more useful for the KLTE than denying certain unsupported recording modes for media encoding. High-speed 60/90 won't record, SM60 records without audio, SM90 won't record. SDcardFS: still not possible to record video to external SD.

Google maps' most recent update moves it from being a slow sliming snail on startup (10 seconds), to much smoother (almost instant) - I incidentally turned off all of the timeline and other Google cruft 'features', uninstalled maps and reinstalled it. I also successfully calibrated my compass on my KLTE for the first time ... ever. My blob on maps actually points in the direction in which I am moving.

baseband: G900FXXS1CQA3

Security: August 2017
[Samsung Galaxy S 5 Unified Development] fipsy:
I agree that the exFAT support in Lineage OS (and Android in general) is still rather immature. However, I've never had any data loss or file system crashes. It therefore depends very much on the intended purpose and the personal needs, whether exFAT should be used or not.
[Samsung Galaxy S 5 Unified Development] Blackburn119:
September security patch Yes or No?
[Samsung Galaxy S 5 Unified Development] djlooka:
Does anybody else experience "Verification failed. Corrupted or unsecure download" when trying to update? I've seen it for the last 2 releases so far
[Samsung Galaxy S 5 Unified Development] fipsy:
Thank you for the report! In my case, the compass calibration is lost again and again (maybe after a reboot?). Therefore, I have to recalibrate the compass every few days.
[Samsung Galaxy S 5 Unified Development] godofsalt:
Thought my .02 cents might help. Maybe not. Having issues a couple of years back. (Belive I was on Galaxy S3, had the filling installed rooted TW, deoxed, slimmed down) having GPS issuess when traveling so, though XDA, got the app "GPS Status" worked, so went to playstore to give the credit an purchase the PRO KEY.

Anyway I can state for fact the app works rather well. It does give you a ton of info and the best part can truly give your internal GPS the fix it needs. From the actual satellites tooo.

Hope this can help you all. Samsung has had many phones with GPS issues,.
[Samsung Galaxy S 5 Unified Development] fitittome:
Are you saying the OS was patched to the latest sdcardfs but there was no support for it in the kernel? Surely that would have stuck out like a sore thumb in the logcat during boot. All I recall seeing something like Device specifically asked for sdcardfs... Tick.... I am sure I would have seen a 'what the f%^k are you asking for, sdcardfs what's that?'. Maybe this is one of the reasons the new msm8974 kernel was needed?
[Samsung Galaxy S 5 Unified Development] fipsy:
The GPS isn't the problem here. The problem is the saving of the magnetic field sensor data for the compass. It appears to me to be a problem with Google Maps. The GPS works fine for me. I've been using the "GPS Status" App for 6 years now. It's really very good, I can confirm that. :good: