yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] fbs:
Try setting virtual memory like this on Kernel Adiutor, using BFQ as i/o scheduler.

Just transfered 22GB back and forth via MTP/USB to my PC without any problems. But my SD is original and tested.

I saw many roms using "swapiness" with 100%.

BOY, that is the same to say "compress everything you can in this 420mb space of zram"
[Samsung Galaxy S 5 Unified Development] fipsy:
Thanks for your answer! Of course I know that free software is without warranty. But it should have no errors in basic functionality.

The problem is, that this issue doesn't cause any noticeable entries in the logcat. Everything seems to be normal but it isn't. But this error can be reproduced on any device: Just copy 2 GB to your internal or external sd-card. And delete these 2 GB afterwards. You will see that the device has 2 GB less free memory. Copy these 2 GB again and delete it afterwards. Now 4 GB are missing. And so on until the device runs out of memory. Then perform a warm boot. After this warm boot all the files you copied and deleted can be found in lost+found or LOST.DIR. If you perform a cold boot everything is okay again without any files in LOST.DIR.

I tried it with bfq, cfq and sio. Always the same problem. And I tried it with the Samsung stock kernel as well as with Boeffla kernel. Always the same. It occurs on the external sdcard as well as on the internal sdcard. So it has nothing to do with the scheduler or kind of sdcard. It's not a problem with data errors while copying files but with free memory after deleting files! Try to perfom a copy-and-delete operation to your internal sdcard as described above while watching free memory. You will notice the problem.
[Samsung Galaxy S 5 Unified Development] fbs:
I think this happened to me before tweaking those "virtual memory" values on adiutor. Did you give it a try? I attached a screenshot on the last message
[Samsung Galaxy S 5 Unified Development] fipsy:
Okay, I installed Kernel Adiutor and set all the values you recommended and then rebooted. Same problems. It had no effect... :(

Additionally since I installed the last Lineage 14.1 nightly and the last Boeffla kernel, the phone freezes every 10 to 20 minutes and restarts from itself. I don't use this phone until now. I bought it in march for use with Lineage 14.1, but it only lies on the table because there are too many problems. I still use Cyanogenmod 11 on my Galaxy S3 which runs without any problems since 2 years. I thought it would be the same with Lineage 14.1 but that was far wrong...
[Samsung Galaxy S 5 Unified Development] fbs:
It seems a caching/MTP bug that won't happen if you don't try to warm boot. So, just don't do it.

The stuff you do with your PC showing the contents of your phone aren't really happening that way. It isn't "physically" doing things like a Pendrive would do. It's MTP, it's not "USB MASS STORAGE" as before. It just simulates files and simulates file operations.

Also, you must be having some hardware problems there, because I have zero restarts/crashes with ANY rom/kernel here.. Aren't you using those bad-ported cpu governos in these custom kernels out there?
[Samsung Galaxy S 5 Unified Development] fipsy:
I never do warm boots as they don't work anyway and always result in a cold boot after a few seconds of freezing. If you read back in this thread I'm not the only one having this file and memory problems. After posting this issue in march there have been some others users that confirmed it.

I didn't use MTP when copying. I just copied files from the external sdcard to the internal card or vice versa using android filemanager or ES File Manager.

Mhhh. It never happened before. Only after flashing the latest ROM and Kernel. I tried different governors with Boeffla Kernel. E.g. pegasusq or zzmove. Never had problems with zzmove. Now I'm trying pegasusq. It perhaps avoids these freezes. For my experience the Boeffla Kernel is really good. Much better than stock kernel. And these file problems also occured when I was first using stock kernel with Lineage 14.1.

Edit: Very interesting: If I copy and delete the file to a Folder in /data/data the free memory values are always accurate! But if I copy and delete the same file to /sdcard the values are wrong. Can anyone explain this to himself? May this be due to wrong mounting parameters? I noticed that /data is mounted with a lot of parameters different from the ones /sdcard is mounted with. I'm not sure if there maybe a problem. :eek:
[Samsung Galaxy S 5 Unified Development] OmarPepe:
Does the latest version have expanded screenshot
[Samsung Galaxy S 5 Unified Development] fitittome:
SD-Cards and 2Gb files

[MENTION=1160716]bilbonotry[/MENTION] [MENTION=5110154]fipsy[/MENTION]

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

Extras: addonsu

Notes: Root Enabled

Method:

Copied 1.84Gb in three subdirectories from sd-card to internal storage.

Verified OK

Formatted external sd-card with 'Files'

Rebooted. Checked external sd-card in TWRP (verified that it formated the filesystem as vfat Mount Point: /external_sd)

Rebooted

Moved 1.84Gb from internal storage to external sd-card with 'Files'.

Verified files OK

Note:VFAT has a file size limit of 2Gb without LFS, I am not sure that LFS is supported on Android, if it were the file size limit would increase to 4Gb. So I was dubious to test that configuration. Also, there maybe some logic in 'Files' to perform a different type of format based on the size of the sd-card, this might be worth checking. Also, Filer may prefer to re-format using the existing type of filesystem. So a few variables remain.
[Samsung Galaxy S 5 Unified Development] fbs:
Someone correct me if I'm wrong, but a crash in "installd" shouldn't crash the Kernel itself, it isn't part of it. And this crash may be caused by too many factors, including: corrupted memory caused by buggy kernel(are you on LOS original?), corrupted processing caused by overclock or undervolt, failing sdcard/internal memory, failing cpu, failing ram, failing motherboard...

---------- Post added at 04:45 PM ---------- Previous post was at 04:32 PM ----------

I have the paid Boeffla version and I don't use it because it just degrades overall phone performance, even when using "performance" governor. Crazykernel and SmartPack too. Boeffla himself says the only trustable governor is "interactive" or "performance".. so, don't mess with many things simultaenously, or else you won't never know what hit you
[Samsung Galaxy S 5 Unified Development] 10goto10:
Try formatting the card to ExFAT (and perhaps using a bigger memory card.) I also had hard reboots while downloading many files (not simultaneously) to the external SD card and losing the files in the process.

The suggestion to tweak swappiness value is interesting, I'll do that when doing heavy operations with my microSD card next time.

By the way, is anyone having issues with Google Maps navigation hard-rebooting the phone after a few mins? G900F, stock kernel, CQB2 modem, 20170621/28 build, addonsu rooted with adaway.
[Samsung Galaxy S 5 Unified Development] fitittome:
Thanks for feedback. I was trying to get something reproducible with stock/standard configuration. I thought it odd that my sd-card was vfat. But I am not sure about exFat, its a bit proprietary. There are so many variables, the original problem doesn't mention, at all, what filesystem was used, there are many! It also doesn't mention if the problem is just with individual 2gb files or just copying 2gb of files. I think what is needed, as logcats are not being provided, is a definitive, step by step, guide to reproduce the problem on a basic stock/standard configured device.

PS. Google maps is fine for me, but I don't use Adaway.

Edit: Ummm. If I scroll down on maps I am seeing a sort of flashing panel where ads would normally appear!
[Samsung Galaxy S 5 Unified Development] cal002:
In one of my older posts I wrote about framework restart causing hard reboot. I never use "warm reboot" but

I guess it is the same a framework restart (i.e. "restart" or "stop; start" in adb shell). I tracked down the

root cause is related to the fingerprint trustzone app, which triggers a hardware reset (probably it

just crashes and a watchdog timer causes the reset). It's proprietary Samsung code, so it's unlikely

anyone can fix it. Maybe someone who cares could find a workaround by trial and error.
[Samsung Galaxy S 5 Unified Development] mclad:
Sorry for not getting back sooner guys! The issue with the device detection was because I was using "twrp-3.1.0-20170331_1146-kfh-klte.img" as I saw that recommended, either on xda or a lineage site. Flashing the latest official TWRP allowed me to update lineage and wireless came back.

I'm not sure why wireless wasn't working it could have other things I flashed at the same time as the lineage + gapps, namely "addonsu-arm-signed.zip" (which I got from same source as the twrp above) or maybe smartpack kernel but pretty sure not as it was a recent version and I just tested it with no problems.
[Samsung Galaxy S 5 Unified Development] romyg:
07-07 23:22:51.001 E/LightSensor(721): RED : 0, GREEN : 0, BLUE : 0, CLEAR : 0, CALCULATED LUX : 0.000000, CCT : 1596.000000, REAL LUX : 0.000000 a_time = 238, gain = 64, ir=0, rp1=1, gp1=0, bp1=0, cp1=0, cpl=3202560
[CODE]

I have this same issue, and it seems to be causing most of my battery drain. Searched the thread and didn't find any solution, although there are multiple people reporting similar issues. The error pops up multiple times a second. Does anyone know if this has been addressed? G900V.
[Samsung Galaxy S 5 Unified Development] romyg:
I've messed with that, sometimes it stops the errors in the log, sometimes it doesn't. But either way, why is this throwing errors in low light, seems like that is a bug? I'm wondering if it's the error handling/logging that might be causing the battery use, not necessarily the sensor...

Edit: I found that it depends on either the adaptive brightness settings or the live display display mode set to automatic. Either one turned on keeps the sensor on and generates massive errors in low light.
[Samsung Galaxy S 5 Unified Development] fitittome:
Amazing, I never could reproduce it! Being reliably reproducible will really, really help the dev. The general procedure around here seems to be to submit it onto JIRA, but only on the weekends, so its open now! https://jira.lineageos.org/projects/BUGBASH

BTW. For obvious reasons they are strict!
[Samsung Galaxy S 5 Unified Development] eurohunter:
I have G900P (Virgin Mobile), and I have the same issue. I also do the same steps (besides reboot) to get signal back. The problem can be replicated by simply turning airplane mode on and off, as mentioned by Efraim. I am assuming the issue is only related to the sprint variant G900P.

[MENTION=2693412]haggertk[/MENTION], I captured a log of this issue. The log includes about 2 minutes of data. During those 2 minutes I rebooted phone, let phone get connected to LTE, I turned on Airplane mode, waited about 5 seconds, then turn it off again. The phone tries every 5 seconds to connect, and I can see it showing Sprint or Virgin Mobile for a fraction of the second, then it goes back to "No Service". So I went to Settings -> More Wireless and Networks ->Cellular Networks -> Carrier Settings, I get an error, and signal comes back.

Should this issue be on Bugbash? If you need more details, let us know!
[Samsung Galaxy S 5 Unified Development] fitittome:
I would have thought so. It looks like there are a number of devs that work on klte (and zillions of other things too, probably) Status-open klte

They use JIRA to capture the bug information and track it. I guess the bugs get allocated to a dev with appropriate time and resources to deal with it.

So as its a weekend, I think BUGBASH would be a good place to report it. More info here https://wiki.lineageos.org/bugreport-howto.html
[Samsung Galaxy S 5 Unified Development] chainzy:
Just done a clean flash of the newest nightly for kltedv. My mms messages are still coming through rotated the wrong way
[Samsung Galaxy S 5 Unified Development] k2828:
does anyone else havin problem with cellular data? it jus does not connect to the internet(no connection sign)

i have the verizon s5(usa). and my carrier is vodafone(in germany).

vodafone bands:

http://www.lte-anbieter.info/ratgeber/frequenzen-lte.php

verizon s5 bands:

http://www.gsmarena.com/samsung_galaxy_s5_(usa)-6338.php

so this shouldnt be the problem, right?
[Samsung Galaxy S 5 Unified Development] Paul_Lunardi:
Hi all just a quick question.

Should Google assistant now appear by default with lineage?

I say this because I was experiencing show performance. Very laggy. I then proceeded to remove cache from settings>storage then I decided to delete Google Play data this seems to have reverted my Google assistant to Google now.

In the past I have downloaded an app from Google Play to assist me to set up Google assistant and am considering to do this again. Though I'm willing to wait if this will be installed with next week's weekly update. I'm using the latest rom 5th July. On my Samsung sm-g900i.

Thank you.
[Samsung Galaxy S 5 Unified Development] FurFur_:
Hm.. I use Beans Gapps and after setting up my device I get to set up my google assistant.

But in case it doesnt works I use Magisk and the Magisk module :)

If you dont have Magisk maybe try this : Google Assistant Launcher .

I hope I could help you :)

( :good: ?)
[Samsung Galaxy S 5 Unified Development] chainzy:
I've also noticed since installing the newest nightly for kltedv, nfc is broken again and greyed out
[Samsung Galaxy S 5 Unified Development] fitittome:
A fresh install of LineageOS will install Trebuchet

A fresh install of LineageOS & OpenGapps Pico will also install Trebuchet by default.

I am not sure what other versions of OpenGapps may do.
[Samsung Galaxy S 5 Unified Development] Amirk365:
Once play services are updated it should work. I'm running stock MM TouchWiz and I have Assistant
[Samsung Galaxy S 5 Unified Development] fitittome:
TL;DR OpenGapps 7.1 arm Pico seems to be broken.

Geez. I avoid logging into Google if I can help it.

The moment I logged onto a Google Account it downloaded and installed Instant Apps.

Once in Google Play it started checking for updates and it's hung there ever since.

So, I quit and cleared the cache and data for Play Services etc. Reboot and go back in, it still hangs at checking for updates. :(

Wiped the phone and clean installed lineage-14.1-20170705-nightly-klte and open_gapps-arm-7.1-pico-20170709, immediately after the install setup, same thing in Play Store. "checking for updates". :(

Wiped the phone and clean installed lineage-14.1-20170705-nightly-klte and the earlier open_gapps-arm-7.1-pico-20170627 , same thing in Play Store. "checking for updates". :(

Wiped the phone and clean installed lineage-14.1-20170705-nightly-klte and the latest nano package open_gapps-arm-7.1-nano-20170709

Trebruchet still the default home app. :) But inflicted with the Google Search Bar on the Home Page (The app is called Google)

The moment I went into Play Store "Instant Apps" was downloaded and installed, but checking Updates was instant. :)

So it looks like OpenGapps Pico is broken at the moment.
[Samsung Galaxy S 5 Unified Development] jeremywh7:
Google Now gets installed starting with Gapps Micro. It replaces the stock launcher starting with Stock. The Google Assistant gets enabled via popup request, but can be declined.
[Samsung Galaxy S 5 Unified Development] fipsy:
File copying itself doesn't produce any problems. It's just the free space after copying and deleting the file that's wrong! Did you watch the free space on the internal or external sdcard after deleting any files? It doesn't change!

I'm not sure anymore if the problem with installd caused the reboots. Becaue meanwhile I often had this installd error without any reboot afterwards.

I don't use LOS but Boeffla kernel. I did not overclock but light undervolt the device as it has an ASV/PVS value of 5 which should make this possible. But seems it doesn't. Since I don't undervolt anymore I did not have a spontaneous reboot again. I didn't notice degrades in performance using Boeffla. Also the governor does not seem to have influence on this issue. But after the next Update I will give LOS kernel a try. ;) I love the nice Boeffla Config App which really makes administering easy and offers a lot of other nice features.

Well spoken :D

So on stock OS this issue just didn't catch anyones eye because there is no warm boot option? Very interesting! Perhaps it would be more constructive to simply remove the warm boot option in LOS!? :p

Same here. It just occurs if the ambient light is very low. If it's bright there are no problems. I also think that error logging causes the battery drain. I deactivated the kernel logger on my boeffla kernel and the drain disappears. But this of course is not really a solution!
[Samsung Galaxy S 5 Unified Development] fitittome:
I spent a fair bit of time on that and didn't notice anything, but it would have been easy to check. Please would you confirm the filesystem type you are having problems with (your baseband version would help to eliminate differences too). My SD-Card was vfat, as it came out of the box. If you are certain these problems show up on a vanilla install, I'll run through it again on a freshly flashed latest nightly and see if we can nail down the problem.
[Samsung Galaxy S 5 Unified Development] Molinari:
So am I to understand for safety net to work I need to put a stock boot image back on first ?
[Samsung Galaxy S 5 Unified Development] fitittome:
I think just removing the addonsu (zip to flash on the LineageOS site) and clearing the data on Google Play Services etc. will make Safetynet pass again.

Safetynet will be OK with a fresh install. Adding the Lineage addonsu will break it. Most people seem to use just Magisk if they need root. But it is a game of cat and mouse for Magisk to keep root hidden from the Google developers.
[Samsung Galaxy S 5 Unified Development] fitittome:
Ah, got it. It doesn't write the changes to the filesystem until you reboot OR manually eject the SD-Card. I guess if was done in real time you wouldn't need to eject the card to flush the changes. So I guess this is 'by design'.

Obviously this sucks but I can see the comment hitting me like a fright train. "Jira is not a feature request platform, so don't treat it as such. It's an issue tracking platform, meant to report bugs, and this is not a bug."

Grrr... maybe I'm getting cynical in my old age?
[Samsung Galaxy S 5 Unified Development] 10goto10:
I wish this was just about free space. I'm guessing sdcardfs is the culprit here. I just corrupted my microSD card three times today just from (re)downloading my Spotify library. Phone either reboots or the SD card stops getting detected by Android. By the time you reboot, your data is corrupted. Even older data can get clobbered. Thank $deity I had backups...

Seems like it doesn't matter whether the SD card is formatted as exFAT / vfat (FAT32), this problem still occurs.

Oh yeah, by the way, my SD cards is not fake or broken, all of them passed full checksummed random data write/read tests on my PC with flying colors.

Steps to reproduce (for me):

SM-G900F, FXXUCQB2, LOS14.1 2017(05-7), Stock kernel, no tweaks

- Use a 32GB+ SD card.

- Format it, and then fill it with data you don't mind losing.

- Do a huge Spotify / YouTube offline download to the mSD Card. 1.5GB+ will do.

- Let the automatic screen lock occur. << important! Using caffeine to keep the screen awake can be seen as a workaround.

- Wait a few mins, depending on your connection speed.

Outcomes:

- Download stalls / stops, and you can't write to the SD card anymore. If you're lucky, you're only going to lose the stuff you just downloaded. Using Windows' CHKDSK on the mSD card will show corruptions galore. Your files could be randomly corrupted and truncated, even ones you haven't touched for a while.

- Phone hangs, automatically reboot, shows 'corrupted SD card' and asks to format the thing. If you try to fix it using CHKDSK, it'll be a similar story as above, maybe even worse. If you use FAT32, you could even lose whole _folders_.

- You got lucky, or my device is showing its age :)

EDIT: bonus bug: try copying files to the microSD card using a file manager that shows transfer speeds. It will sometimes stall for seconds copying at a rate of '1B/s'. If you are patient, the copy will finish fine. This doesn't happen on stock, and is a little concerning.

By the way, anyone care to share their experience with adoptable storage? What is the risk of losing your data if you dirty-flash / clean flash your ROM? Ext4 / F2FS should be more robust than this, right?
[Samsung Galaxy S 5 Unified Development] fitittome:
Good work. Yep, I think this is a bug. It needs to be posted onto JIRA on the weekend. I'll do the same with my testing too. I cannot understand why I haven't noticed this before, I think it maybe because the contents remain fairly static for me.
[Samsung Galaxy S 5 Unified Development] shkedov:
I wonder if this is considered a bug:

Assuming the fingerprint screen unlock is activated; when I wake my phone with the home key, screen will stay off until I raise my finger from touching the home key, and then the screen turns on.

Anybody confirm? And I'm not familiar with posting on JIRA...
[Samsung Galaxy S 5 Unified Development] jdrch:
- Create an account.

- Log in.

- Click Issues -> Create.

- Fill in all the fields. Make sure you know the last working date (only regressions are accepted.)

- Attach a logcat file for the issue or be prepared to attach one if asked.

- Make sure you make a nandroid backup before attempting anything drastic such as flashing/reflashing/(non cache) wiping, etc.

Generally I've found that even if JIRA responders ridicule the bug, it does get fixed eventually.
[Samsung Galaxy S 5 Unified Development] Caduebla:
Hey guy, thanks for the work.

I'd like to report a bug.

My WiFi is not working since the latest actualization.

It keeps activating the WiFi and never change.

Anyone knows something to do for fixing?

Using a S5(SM-G900M)
[Samsung Galaxy S 5 Unified Development] 10goto10:
Excellent write-up [MENTION=5909804]jdrch[/MENTION]. Much thanks! To clarify, to avoid recovery mode screwing up the adopted SD card somehow, I just need to put flashable zips in the phone internal memory and remove the mSD before entering recovery, right?

And I believe you can use TWRP to nandroid straight to a PC via an USB cable. Is this correct? I don't foresee myself switching to another ROM in the foreseeable future, so I might need to brush up my ADB-fu and take the plunge :)

As for transferring files wirelessly, I found Resilio Sync to be too heavy / battery-intensive for a phone, so I just use good-old FTP to transfer files wirelessly. I'm also going to try Syncthing to see if that works better.

First, what is your device model? Try updating your baseband. Here's a link to haggertk's baseband files folder: https://www.androidfilehost.com/?w=files&flid=102820

Flash that with Odin. Don't forget to pull and reinsert the battery for a few seconds before entering download mode and flashing -- the baseband update won't get applied otherwise.

If that still doesn't work, try using the network settings reset function (Settings > (under network) More.) This will also reset your saved WiFi passwords and device BT name and pairings.