You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
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.
The text was updated successfully, but these errors were encountered: