View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010485 | MMA | Synchronization | public | 2013-02-05 22:00 | 2013-02-22 23:01 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.0.1 | ||||
| Target Version | 1.0.1 | ||||
| Summary | 0010485: Content is not continually updated in MMA when syncing large number of files over USB in MTP mode (regression) | ||||
| Description | 1. Connect an android device via USB in MTP mode 2. Run MMA 3. Select e.g. 100 files in MMW 4.1 an send to the device => Content is not continually updated in MMA This worked fine in the past, but has stopped working for several tech reasons: - First reason is that MMA no longer use Android's content provider while syncing with MMW 4.1 - Another reason is that mm.store.db.synced.partial (that is uploaded every 30 seconds) almost always fails to upload | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 103 | ||||
|
|
I found that there was also a problem on MMW side, the mm.store.db.synced.partial failed to upload, because it was not properly closed on MMW side. I fixed in in build 1624, but it shown some other hidden problems: 1) MMA started to create duplicates again, i.e. the same track appear two times in library (this is a bug in MMA), I would suggest to fix it together with 0010471 - Couldn't MMA to add the tracks from content provider and then just update them from the uploaded DB? 2) MMW still sometimes fails to upload the mm.store.db.synced.partial , because MMW still "see" the file on the device (can be seen by Windows Explorer too), but the file no longer exists in the device and cannot be deleted from MMW side. It is the known MTP refresh problem :-/ - Because it never happens for the final DB (only for the partial) then I guess it is solvable by refreshing the content on MMA side? Or maybe MMA doesn't copy the partial DB to another location when processing as it does with the final DB? |
|
|
Fixed in build 103 |
|
|
Verified 103 |
