View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012206 | MMA | Synchronization | public | 2014-10-01 18:11 | 2014-12-12 19:30 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 1.0.7 | ||||
| Target Version | 1.1.0 | Fixed in Version | 1.1.0 | ||
| Summary | 0012206: Tracks on GS3/GS5 external storage are inacessible in some cases | ||||
| Description | There are a couple of recent reports in the store feedback that: 1) GS4 / 3.0.6: ... my library won't load so the only way I have my play my music is navigating through folders or using a different app. 2) GS5 / 3.0.4: Can't keep play list open the app by mistake once and it copied every song in every Playlist twice... I tried to replicate this with a new S5 mini + SD card, and was able to trigger the bugs as follows: 1 Run MMA in S5 mini, and configure Options > Sync > External SD Card 2 Select a single playlist to be synced, and enable 'delete tracks not in the sync list' 3 Initiate Wi-Fi sync --> Tracks sync to the SD card, and the playlist appears in the MMA library, but the playlist indicates 0 tracks, and none of the tracks appear in the MMA library! The only way to see/play the content is via Folders > External Storage (/storage/etSdCard) > Android > data > com.ventismedia.android.mediamonkey > files > Music , in which case the tracks all appear, but without their artwork. --> In addition the Playlist appears in Google Play, however, it is listed as having 0 tracks! 4 In MMW, edit the auto-conversion rules and then initiate Wi-Fi sync again via MMA --> the tracks are resynced/converted (i.e. duplicates of every track were created in the case of tracks that matched the auto-conversion rules), but this time, tracks appeared in the database correctly!! It seems that just by modifying the device profile in MMW, something has changed that causes synchronization to work correctly. --> the playlist still appears in Google Play with 0 tracks. Note: when the same set of tests is performed by syncing to internal memory, synchronization works as expected (with the exception that some tracks are missing artwork--but that is tracked elsewhere). | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 352 | ||||
|
|
I've been testing this for the past day trying to replicate it and am unable to. Tagging as resolved -- unable to reproduce. |
|
|
I was able to replicate a variant of this issue on a Galaxy S3. Tracks that had been synced to MMA 1.0.7.xxx and were previously accessible, could not be seen in the DB when viewed in MMA 1.0.7.306 (I'm not sure at what point they disappeared). However, they are still loaded in the Now Playing list and can be played, even though they don't appear in the library! fyi, there appear to be 2 sets of content on the device: - ~ 1000 tracks that are at ?? .../Playlists/Goodstuff/... ?? - ~ 100 tracks that are at extSDCard/Music/ Neither displays in MM, but the tracks synced to extSDCard/Music/ display in Google Play Music / Samsung Music. Debug log of them playing after previous unsuccessful attempts to browse: 0VW0OZH073 The really strange thing is that MMA indicates that the playing files are in a directory /Playlists/Goodstuff, but I can't find any of the tracks there using ES Exporer?! |
|
|
Unfortunately the log starts when DB is already empty. But I have some questions: 1) I can see that only /storage/emulated/0/Movies dir is selected in MMA for scanning. Other dirs (/storage/emulated/0/Music, /storage/emulated/0/Video) are scanned automatically because they are checked in MMW. But there are no dirs from external SD card. Actually it looks like no sync of external sd card was done because there are no settings. 2) Did you do some uninstall previously ? Beta and release version of MMA have different paths. But uninstall would probably delete all trakcs. 3) I don't know certainly why the settings profile dissappeared. But I think that the following happend: Due to fixes in USB sync and looking for storageInfo on storages with limited access the GUID of external storage has been corrected, i.e. it changed. The settings is paired by GUID so that is why the settings was not found and why these storage is not scanned. Sync with MMW should fix it or manual adding of these folders can help too. Usually, new storages that are READWRITE_LIMITED have the path /Android/data/com...mediamonkey/files automatically added. But the storage most proabably changed it's type from READWRITE_HACKED (hacked storage that was working before samsung's update) to READWRITE_LIMITED...but in this case dirs with path /Android/data/com...mediamonkey/files are not automatically added for scanning. But there might be still scanned when checked in MMW profile. But this was not the case because the sync was not done. I will create new build 307 that contains logging of settings files of unused GUIDs....this will reveal the old settings and confirm that it is really this way as I think. Please install it and you can send the logs immediately after startup. |
|
|
1/2) It's possible that an uninstall was done at some point--I'm not sure. I can tell you for certain that an OS upgrade _was_ done. debug uploaded: Y6L1ZDC6H9 |
|
|
Yes, it was certainly caused by 0012168 . It's side effect was that it caused to create profile duplicates ( 0012196 ) too. I have found unused settings with different GUID that belonged to SD card. I have no workaround for it because it is caused by bug that was fixed and next sync will fix it. But I will add some functionality to add /Android/data/... path to default scanned paths for every type of storage. |
|
|
Fixed in build 308 |
|
|
Tested build 308 and found that: 1) Manually enabling the extSDCard/Music folder in 'Choose library folder' caused the tracks to appear. Disabling it caused them to disappear. i.e. this is the root cause of the issue. 2) Syncing the device did _not_ solve the problem, even with the newly created profiles. The problem is that although the sync operation resulted in force-selection of the extSDCard/Music folder in 'Choose library folder', because the sync operation didn't sync any tracks, a scan wasn't triggered. This is consistent with the bug as it was originally reported--repeated sync operations had no effect in terms of getting the tracks to appear. They only appeared after a sync in which the auto-conversion rules had been edited, because that triggered a sync operation that actually modified content--resulting, which triggered a scan. Could a solution to this be that sync operations that trigger a configuration change re. selected folders in 'Choose library folder' should trigger a scan (even if no tracks are synced)? |
|
|
Marek fixed this in 309. MMA now starts new mediastore sync when change in remote dirs from MMW occurs. |
|
|
Apparently, this isn't completely fixed or a regression was introduced--users are again reporting this issue in build 341: http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=78456 (GS3, Galaxy Note 10, Galaxy Note 3) http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=78469 (Galaxy S3) + more symptoms at http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=78478 Possibly related: http://www.mediamonkey.com/support/staff/index.php?/Tickets/Ticket/View/25877 (playlists becoming empty) |
|
|
I have to study it more. This is regresion from 12196 but: 1. we are receiving notifications about mounting and unmounting of storage 2. in logs from these devices I see a lot of mounting and unmounting events 3. This is why the storages are removed and readded. There are probably some invalid notifications...storage cannot be unmounted so many times. But I don't know how to solve it now. Recently we were not removing unmounted storages automatically. We were doing tests, whether they are writable. BUT I tested it with Asus Transformer with SD card slot and when unmount intent was received, the storage was still writable !! This caused incorrect state and sometimes duplicates of profiles and crashes. So I have to remove storage that is indicated as unmounted but we have to figure out why these devices are sending these events. |
|
|
Fixed in build 347 There was a bug that unmounted storage wasn't sometimes recognized when re-mounted. |
|
|
Seems to work on Samsung S5 mini. Will close on user feedback. |
|
|
Marek, this may be fixed, but I've re-opened in case there's a file path issue that you might have overlooked. See the user's comment at: http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=78469#p399247 If this isn't an issue or if it's a separate issue, please re-resolve (I can open another bug if needed). |
|
|
This path issue is strange. I have requested log. |
|
|
Fixed in build 352 |
|
|
No observable regressions. Waiting for user confirmation. |
|
|
Based on the following, it appears that this issue may not be resolved: http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=72060&start=45#p399597 http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=74407&start=30#p399548 THD-424-11093 Waiting for additional feedback before re-opening. |
