Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fail to list folder with 600+ files on SAF R/W mode on external storage. [workaround found] #178

Open
GDXN opened this issue Aug 4, 2019 · 1 comment · May be fixed by #376
Open

Fail to list folder with 600+ files on SAF R/W mode on external storage. [workaround found] #178

GDXN opened this issue Aug 4, 2019 · 1 comment · May be fixed by #376

Comments

@GDXN
Copy link

GDXN commented Aug 4, 2019

System Huawei P9lite (Android 7) + 128GB Samsung Evo+
PC client Filezilla (300s tiemout)

when trying to list a folder with 640 files it fails, I found that with 600s timeout it works but is painfully slow. Possible solution is to send the client some message every 150sec for example a code 211 or 214 indicating slow operation preventing timeout with the most common default value of 300seg.

PD. Why don't use 2 methods to access the media, SAF slow for writing and another faster for listing and if possibly also reading.

@GDXN GDXN changed the title Fail to list folder with 600+ files on SAF R/W mode on external storage. Fail to list folder with 600+ files on SAF R/W mode on external storage. [workaround found] Aug 4, 2019
@wolpi
Copy link
Owner

wolpi commented Aug 6, 2019

Well, that SAF is slow is known. That is the reason why I created read-only SAF. The root cause is Googles approach to prevent SD Card from beeing accessible by Filesystem API.

Sending Codes 211/214 would be interesting but in this case hard to do as this app does currently not implement protocols in its own but uses libraries from Apache Mina.

Mixing SAF APIs for reading and writing would be interesting, too. But that would be a Major Code Change and Takes time.

By the way: contibutions are Welcome ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants