View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011016 | MMW v4 | Synchronization | public | 2013-06-27 21:25 | 2013-10-18 20:44 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0011016: USB Sync: Renaming playlist yields strange confirmations | ||||
| Description | 1 Create a playlist 'Playlist1' 2 Add 'Playlist1' to the auto-sync list 3 Auto-sync over USB --> sync proceeds as expected 4 Change tracks in 'Playlist1' and Rename 'Playlist1' to 'Playlist2' in MMW 5 Autosync over USB -->'Playlist1' appears checked in 'Files and playlists to delete from the device' (as expected), but 'Playlist: Playlist1' appears unchecked in 'New Files and playlists to copy from the device to the PC'. I don't know why it appears there, considering that the most recent edits were done on the PC. -->Side note: After sync is completed, the playlist does not appear on the device after the first scan is completed (it takes several minutes and a couple of scans before it shows up). | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1665 | ||||
|
|
Assigned to me as USB sync is controlled by MMW |
|
|
I added MMW.playlists.GUID field and fixed necessary stuff on MMW side in build 1654. Nevertheless it still doesn't work, because MMA doesn't seem to use the MMA.playlists.GUID written by MMW, but creates new one when transfering playlist from mmstore.db.synced to mmstore.db This needs to be fixed on MMA side. |
|
|
Insert of correct GUID was fixed but there are still some issues on MMW side. When playlist is renamed and USB sync proceed on MMW side, MMW stores /storage/.../Playlist2.m3u file BUT MMA obtain instruction to INSERT (should be UPDATE) Playlist1 (should be Playlist2) with path /storage/.../Playlist1.m3u. Guid is ok, but MMA inserts new playlist (Playlist1) with duplicate GUID. I think that old file (/storage/.../Playlist1.m3u) should be deleted by MMW too. The result is that MediaStore scans newly created Playlist2.m3u and in MMA exist 3 playlists: Playlist1 - old, origin playlist from first sync Playlist1 - inserted in second sync according to MMW's instructions Playlist2 - scanned by MediaStore |
|
|
I fixed this in MMW build 1658, - MMA now correctly updates the playlist path to /storage/emulated/0/Playlists/Playlist2.m3u and correctly shows only one playlist, but the playlist name remains still Playlist1 in MMA! I would also need so that MMA could delete the old path (../Playlist1.m3u) when updating the path/name, because otherwise MMW would need to remember naming history for each playlist. |
|
|
I have added deleting of playlist when path is changed to build 172. But I cannot test it because there are some issues on MMW side, these issues occur also without changes in build 172: 1. After playlist is renamed to Playlist2, sync confirmation occurs with confirmation of Playlist1 deletion. This shouldn't occur, it should only update. 2. After sync, there are both playlists in MMW, Playlist1 and Playlist2 - both checked for autosync. |
|
|
Fixed in MMW build 1665. This issue still remains: - MMA now correctly updates the playlist path to /storage/emulated/0/Playlists/Playlist2.m3u and correctly shows only one playlist, but the playlist name remains still Playlist1 in MMA! |
|
|
This issue is on MMW side. MMA takes the name from mmstore.db.synced where I found the old name, i.e. Playlist1. |
|
|
Fixed in MMW build 1665. |
|
|
Verified MMW 1665 / MMA 172 This now works correctly when doing a wi-fi sync (the user is prompted to delete the old playlist, and the new one is uploaded). However, when syncing via USB, Google's music app shows the updated playlist, but MMW doesn't. I suspect that this issue is related to a failure of MMA to scan for updated playlists, so will track this separately. |
