View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010175 | MMA | Synchronization | public | 2012-12-07 23:17 | 2013-02-22 22:40 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 1.0.1 | Fixed in Version | 1.0.1 | ||
| Summary | 0010175: Track Deletion: Windows Explorer (connected over MTP) doesn't update | ||||
| Description | MMW Music Sync Profile: \Music\<Album Artist>\<Album>\<Track#:2> <Title> Steps: 1. Sync One track that will create Folder structure 2. Navigate Artist 3. Select Artist for deletion 4. Answer Yes on Dialog that Files will be permanently deleted 5. Use Windows Explorer and see if Track/Folder Structure is deleted NOTE: use USB Connection for easier tracking Edit by Rusty: Title: MTP Browsing: Tracks showing not removed from Device --> Windows Explorer doesn't update on Track deletion in MMA Clarification re. the bug: If the user deletes a track in MMA, Windows Explorer fails to recognize the fact that it's been deleted. e.g. 1 Connect device running MMA to windows machine 2 Delete a track in MMA --> Track is deleted (as verified by ES Explorer) but Windows Explorer (or MMW) still shows the track | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 103 | ||||
|
|
2. Removing Track From MMA Still Show Tracks Existence in Windows Explorer and MMW Browsing device. I guess that Media Re Scan is not triggered with MMA action |
|
|
Peke, what exactly do you tested? Do you tested WiFi sync or USB sync? i.e. you deleted the tracks by using MMW or MMA? I suppose that you deleted the tracks using MMA, but MMW/Windows see the tracks still there, is this what you think? And you are testing in MTP mode, right? |
|
|
Checking Local file system using ES File Explorer, it looks that files are physically removed but folder.jpg is not |
|
|
You are right Ludek, here are steps: 1. Connected Nexus 7 (JB 4.2.1 in MTP) with USB as Wi-Fi is not seen by Windows Explorer as device 2. Navigate Folder structure to one song in windows explorer and play it to ensure that file is accessible (playback player not important) and closed Windows Explorer 3. Delete that Song from Nexus 7 using MMA 4. Repeat step 2 and track is shown but not playable 5. Repeat same step using MMW and track is Shown but not playable 6. Started ES Explorer on Nexus to ensure that track is there, track was not there but Folder.jpg still existed |
|
|
This doesn't seem to be fixable, since it's how MTP caching is implemented - it doesn't necessarily always show the very latest state of device filesystem (particularly for Android phones). |
|
|
Per IM discussion with Marek, it is possible to do on MMA side. i.e. MMA has a possibility to refresh the content |
|
|
It seems to be solvable: http://androidforums.com/samsung-galaxy-nexus/493534-why-do-some-files-not-show-up-over-mtp.html I downloaded the app SDrescan ( https://play.google.com/store/apps/details?id=com.bero.sdrescan&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5iZXJvLnNkcmVzY2FuIl0 ) and it does the job for me. i.e. content is updated in windows explorer by using that app |
|
|
This issue is particularly unpleasant while testing USB sync. 1. Copy some tracks MMW->MMA 2. Delete them in MMA 3. Copy the same tracks again using MMW (MMW still see the tracks there thus it doesn't copy the tracks, MMW doesn't replace them because of 0009431:0031388 ) => deadlinks are created in MMA Workaround is to run the SDrescan app between steps 2. and 3. |
|
|
Fixed in build 87 |
|
|
Verified in 87 |
|
|
Verified 88 |
|
|
Re-opened, as discussed with Marek, the refresh was reverted, because it is causing some problems in MSC UMS mode. To be resolved by calling the refresh in MTP mode only (if there is a way for MMA to find this info) |
|
|
What about to call the refresh just on sync start? i.e. Once MMW uploads the sync-started file then MMA could update the content. This approach should work if there is no way for MMA to find which mode (MTP/UMS) is configured. But it seems that android.intent.action.ums_connected can be used to detect UMS connection |
|
|
Fixed in build 103 |
|
|
Verified 103 |
