search

nextcloud / android

📱 Nextcloud Android app
https://play.google.com/store/apps/details?id=com.nextcloud.client
GNU General Public License v2.0
4.17k stars 1.75k forks source link

No response when downloading large folder to local storage #4668

Open guoyunhe opened 4 years ago

guoyunhe commented 4 years ago

Actual behaviour

Android says "Nextcloud no response. Wait or Stop?".

Expected behaviour

Nextcloud should download files quietly in background.

Steps to reproduce

  1. Create a folder in server, upload a large amount of audio or videos. (I have 3GB *.flac music, average size 60MB)
  2. In Android app, choose the folder to synchronize.
  3. Leave the app and continue using the phone for other tasks.

Environment data

Android version: Android Pie, MIUI 11

Device model: Mi Max 3

Stock or customized system: Custom

Nextcloud app version: 3.8.0

Nextcloud server version: 16.0.5

KrisZane commented 4 years ago

I am getting the exact same issue with many smaller files, I have about 66000 files in one folder and it freezes and then crashes with the close or wait popup.

ghost commented 4 years ago

I often see this. The solution is to dismiss this and simply wait.

It feels like the whole app is single threaded and this bottlenecks.

AndyScherzinger commented 4 years ago

The issue is rather that it is a synchronous foreground action which is limited by Android regarding its duration and if it hits a threshold Android will ask the users of they want to wait or terminate.

The correct way would be to do this asynchronously in the background but that implies a complete rewrite which is very time consuming.

KrisZane commented 4 years ago

I would like to point out that when it crashes it permanently disables synchronisation, so I am effectively not able to sync files to my phone because there is one larger file in my directory.

stale[bot] commented 4 years ago

This request did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

guoyunhe commented 4 years ago

Keep open.

stale[bot] commented 4 years ago

This request did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

guoyunhe commented 4 years ago

Keep open.

stale[bot] commented 4 years ago

This request did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

guoyunhe commented 4 years ago

Keep open.

stale[bot] commented 4 years ago

This request did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

ghost commented 4 years ago

The correct way would be to do this asynchronously in the background but that implies a complete rewrite which is very time consuming.

Hi. Has there been any more thoughts about this? Possibly this would give users a great deal better experience with the app.

AndyScherzinger commented 4 years ago

Has there been any more thoughts about this? Possibly this would give users a great deal better experience with the app.

It would but no, no efforts have been taken to tackle this yet and I am not aware of anybody planning to take care of this in the near future.