View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0014790 | MMA | Synchronization | public | 2018-04-28 19:56 | 2018-06-01 08:13 |
| Reporter | peke | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | unable to reproduce |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.3.2 | ||||
| Target Version | 1.3.2 | ||||
| Summary | 0014790: Sync: Constant fail for number of tracks | ||||
| Description | Sync constantly fail for 67 tracks if synced over Wifi. MMA LOGIDs: D1WTDANR8S -> MMA809 + MMW LOG supplied on FTP IB5EFDF8R6 -> MMA810 | ||||
| Additional Information | NDM-327-97004 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Same issue with 811 LOG ID is sent 4HVC5UGE5T |
|
|
Yes, the issue is that MMA can't create a downloaded file on sd-card. I really don't know why, because permission is granted for all sd-card. I will add more logs to another build. |
|
|
MMA 812 LogID after same error: 9QJ6GTW791 Will update after user tries to fill the card full, again it is 128GB SDCard :( I also Asked user to do a Fake SDCard test as he have Around 70GB free when it started to fail |
|
|
As Requested from user he created copies existing Music over and over in File manager till SDcard reserved 5% of Free Space and File manager refused to copy any more tracks. Random tracks are selected to be played in MMA and then MMA is used to Delete files where Circle would not stop spinning . At that moment C9RKRBD47L MMA 812 LOG is sent. |
|
|
Re deletion files: I can see in log C9RKRBD47L "No space left on device", this causes that MMA test of writing file fails and sdcard is evaluated as "ReadOnly" To summarize the issue. MMA is not able to create a new file. So when MMA receive a new file from MMW, then MMA is not able to store it to sdcard. MMA used API is Storage Access Framework (SAF). Also, I have tried old API wih java.io.File. Both don't work although all permissions are granted. Really is he able write files from another android app like ES File Explorer https://play.google.com/store/apps/details?id=com.estrongs.android.pop Can he try to create a file on sdcard from this app? (SD card - > Options -> new -> File if ESFile is freshly installed, it should ask for permission) I saw that OnePlus X was originally distributed with Android Lollipop 5.1.1, but he has now android 6.0.1. Does he get it from an official distributed update or he installed custom ROM? |
|
|
His firmware OxygenOS 3.1.4 is last official OTA Update OnePlus X ES File explorer works fine for him after he accepts permissions for accessing SDcard. |
|
|
Today we did an experiment with mma. We deleted one of the tracks which fail to sync to mma from mmw library, then moved it using windows explorer (To somewhere else within my mp3 folder), then changed some tags from windows explorer, then searched for new tracks in MMW. Track was rediscovered. Then renamed file from within MMW and then did a WIFI sync. It downloaded that track OK (its still the same MP3 file, but in a different place with different tags). It now only fails on 66 tracks. We send log ID 1WTLL3FBGA. The track plays fine in MMA. We also ripped a new CD, added to MMW and wifi synced it OK to MMA. Reporting back the results of 815 |
|
|
815 Failed. Log ID DDMABV99C4 and MMA didn't asked for permission |
|
|
Permission is already granted for all(root) sd-card, so MMA won't ask again for permission. Unfortunately, the last Log DDMABV99C4 contains media store sync only. New debug log would be useful. I have changed tags of my mp3 track to be same as user's track to try create same file sdcard-id:Music/Various/Bits and Bobs1/49 kubb - Mother.mp3 no issue on my deviece. Default template for wifi sync is \Music\<Album Artist>\<Album>\<Track#:2> $Left(<Artist>,20) - <Title> I can see in older log that folder \Music\<Album Artist>\<Album>\ exists, can user confirm? So I guess that track name somehow matters, but also folder can by corrupted in some weird way. What differences had new synced track in path/filename (I can't see it in 1WTLL3FBGA)? I suggest try to remove <Track#:2> from filename or at first try to sync to different folder eg. <Album>Test, so template will look like \Music\<Album Artist>\<Album>Test\<Track#:2> $Left(<Artist>,20) - <Title> or if it will fail, then \Music\<Album Artist>\<Album>Test\$Left(<Artist>,20) - <Title> |
|
|
Another idea, if folder \Music\<Album Artist>\<Album>\ exists, but empty, the user can delete it before sync. It could help, if the folder is corrupted and user doesn't have to change anything in MMW. |
|
|
From user: "Not sure if you know this already but I found the following weird behaviour. I went into ES File Explorer (ESFE) and found the "missing/failed" tracks exist but with zero bytes. 1) I deleted 2 of the tracks (in bits and bobs 1 folder) Broken Bells, Holding on for life, and Rhianna, California King Bed. 2) I closed ESFE, re-opened and checked the files are gone. 3) I Browsed by folder in MMA - the files are still showing in there. 4) I tried to delete the files in MMA but they do not delete. 5) I reopened ESFE and the tracks have re-appeared with zero bytes. 6) I sent log ZC1W6HAIAA. I hope this is new information and it can help you find the answer !" |
|
|
So definitely it seems on OS side issue with SAF API. "Re-appearing" is OS side issue. MMA saw over SAF already deleted files but was not able to get more info due to getting FileNotFoundException (inconsistency on OS side) Unfortunately, this issue does not be fixable on MMA side. Anyway, I guess a similar issue is with unsynchronized files (inconsistency on OS side). As I said before the user should try to change the path template to sync to completely new location. |
|
|
Along with 0014790:0050284 observations when we tested on Friday user also pointed out that he would like to evade resync of 50gb+ Tracks and loosing them. Disabling force path should evade that? |
|
|
I didn't know that he already synced 50 Gb tracks. In this case, the user has right that changing the path template is not the good idea. 1) Maybe he should try: A) delete folders with zero bytes tracks from ESFE again, B) or delete files/folders from sdcard mounted as storage from PC 2) restart the phone 3) check it from ESFE 4) and if files/folders don't exist, try synchronization. |
|
|
Based on offline debug in remotes session with user it is found that SDCard was corrupted during MTP Freeze that resulted in creation of 9 byte track files named by tracks MMW tried to sync. Result was that not any file manager on Android or using SDcard in PC Card Reader can delete those files. Apron using Windows partition Properties -> Tols -> Check and fix Errors SDcard was fixed and Windows explorer could delete affected folders and files. Then after reinsertattion of SDcard in phone and init of WiFi Sync incorrect tracks were re-synced and inaccessible (incorrect) tracks are removed (MMA prompted for deletion), resulting in complete sync. LOGS supplied with testing (in order of submit): EMSTZ2ZTU1 1KMDBTLWVZ f7vgxekrx5 6MPWZ81DFB 75AVU6N4GW During each Sync same 15 tracks got updated and Martin Log analyze showed that MMA try to download album art for some tracks, but gets HTTP response code: 404 from MMW tracked as 0014824 |
|
|
MMA log ID after sync results showing 15 files updated is G9BJMJKCFC Accompanied MMW log files are on FTP under "/!TempFiles/bugs_14790and14824and14709.rar" |
|
|
Remaining issue fixed on MMW side. |
|
|
Reopen to get feedback from user on his return in a week and then we will be able to do another remote session. |
|
|
User confirmed fix |
