Skip to main content

scan cloud storage incomplete

Comments

3 comments

  • Official comment
    Dr. Twist

    CloudPlayer extracts metadata and artwork from every single file in your cloud music library. For very large libraries, this process can take a long time, averaging several seconds per file for Google Drive, and a few things can happen:

    1. The import process is sensitive to network conditions such as WiFi dropping for a few seconds and stopping the import process
    2. Google Drive may be temporarily throttling your account
    3. The phone may kill CloudPlayer while it's importing songs in the background. Some OEMs are much more aggressive about killing apps in the background than others. Don't kill my app has a nice list with instructions on how to prevent or minimize this for some of the most popular OEMs
    4. CloudPlayer may have encountered a specific file that may be corrupt and causes the import process to pause

    Looking at the CloudPlayer logs after pressing "Scan Cloud Storage" can provide clues as to the exact problem. The bottom half of the following help page contains instructions on how to access the logs:

    https://support.doubletwist.com/hc/en-us/articles/115002066751-Some-of-my-cloud-files-don-t-show-up-in-CloudPlayer-but-they-appear-on-my-Dropbox-OneDrive-Google-Drive-

  • Harco Rutgers

    Thank you! Quite a few reasons why this process might not go totally smooth I see.

    1. I guess I can rule this one out, because the network conditions are very stable.

    2. Why would Google Drive be throttling my account? What would be reasons for this? Any known ways to prevent this?

    3. It doesn't seem like this is the case, but I could be wrong. The only notification I get from CloudPlayer is 'Getting list of media files from GoogleDrive', but it does not start indexing at all. I don't mind if it takes a long time, but I would like the process to start.

    4. How can I see if this is the case? The log files don't seem to show this, but I'm not sure if I read them correctly.

    When checking the log file, the entries after clicking 'Scan Cloud Storage' are this:

    2019.02.18 11:10:01.503 DEBUG [NGMediaProvider] MediaLibraryService - onStartCommand: startId=0 intent=Intent { act=com.doubleTwist.action.SCAN_LOCAL_STORAGE cmp=com.doubleTwist.cloudPlayer/.MediaLibraryService }
    2019.02.18 11:10:29.503 DEBUG [NGMediaProvider] MediaLibraryService - onStartCommand: startId=0 intent=Intent { act=com.doubleTwist.action.SCAN_LOCAL_STORAGE cmp=com.doubleTwist.cloudPlayer/.MediaLibraryService }
    2019.02.18 11:10:52.550 DEBUG [NGMediaProvider] MediaLibraryService - onStartCommand: startId=0 intent=Intent { act=com.doubleTwist.action.SCAN_LOCAL_STORAGE cmp=com.doubleTwist.cloudPlayer/.MediaLibraryService }

    I'm not sure what to do with this information... 

    0
  • Dr. Twist

    As far as #2 goes, in some cases involving very large music libraries, Google can temporarily throttle Google Drive APIs during the initial import process when thousands of music files are accessed within a short period of time. If it did happen, it would appear in the logs though and I don't see anything pointing to that in the snippet you attached.

    I'll create a ticket from your last reply so we can continue communicating privately. 

    0

Post is closed for comments.