View Issue Details

IDProjectCategoryView StatusLast Update
0011628MMW v4Synchronizationpublic2013-12-19 21:31
Reporterlowlander Assigned To 
PriorityurgentSeverityminorReproducibilitysometimes
Status resolvedResolutionnot fixable 
Product Version4.1 
Target Version4.1 
Summary0011628: USB Sync Problems (Samsung Galaxy Note)
DescriptionSome problems during USB sync on 1681 (Samsung Galaxy Note):

1) Files are set to be synced to a folder with the Playlist name. Using right click Send To on a Playlist in MMW had some files synced to the Unknown folder.

2) MMW Device Profile is set to remove Artwork over 1KB (all other options deselected). On one USB sync .alb files were created on device, on other sync (that failed on device hang) this wasn't the case.

3) Playlists were not created (neither in Playlist folder nor in MMA) on sync despite being set to do so.

4) Right click Playlist > Send To fails without warning if Playlist hasn't loaded yet.

5) Sync get's stuck on initializing. [Stuck on Initializing.zip on FTP]
TagsNo tags attached.
Fixed in build

Relationships

related to 0009821 closedLudek Samsung Galaxy Note: Tracks show unknown Album Artist / Album (failed device detection) 
parent of 0011636 newLudek Right-click files in filelisting -> Send to -> Device may result in improper structure 
parent of 0011637 newLudek Right click Playlist > Send To > device fails without warning if the playlist hasn't loaded yet 
Not all the children of this issue are yet resolved or closed.

Activities

Ludek

2013-12-19 12:15

developer   ~0038848

Last edited: 2013-12-19 12:31

1) Can you please attach export of your device profile (MMDC file) so that I could import your exact settings and try to reproduce it?

2) I remember that the .alb files caused MTP freezes for you in the past (I guess it was issue 0009821 ). I will try to see how this could happen.

3) Could you attach debug log of that? Probably related to 5) ?

4) I see, this can happen for your complex auto-playlists for which loading takes some time, right? I would suggest to track this as a lower priority issue.

5) It seems that MTP is totaly broken for your device, MMW failed to download MMA's DB with MTP Error Code 8007001E and subsequently MTP has frozen totally. I guess you couldn't access it using Windows Explorer too and unpluging the device unfreezed it, right?
I guess if it could be caused by the .alb files as it was in the past, could you try to delete them to see if it helps?
When these problems started with your Galaxy Note?
Which MMA version you used to test? Maybe could be related to the recent changes made on MMA side re. MTP handling: 0011458:0038809

Ludek

2013-12-19 12:51

developer   ~0038850

Last edited: 2013-12-19 12:53

Re the .alb files, I found that MMW still creates them if your device advice it as supported. Previously in 0009821 we removed creating only the abstract artworks when creating .alb (as .alb has not been the issue before).
On the FTP is attached new d_WMDM.dll where creating .alb is disabled entirelly, please give a try with that DLL to see whether it helps.

lowlander

2013-12-19 17:14

developer   ~0038859

I will test, but yes, once MMW fails Windows Explorer is frozen too. Removing device resolves this. However it seems that from then on the device no longer works until a PC restart. This has been an ongoing issue for the Galaxy Note (got WMP to freeze the same way). The only reason I was doing USB sync was due to wifi sync no longer syncing to external (0011399).

1) Profiles on FTP

2) Not sure what causes it, but it happens on larger syncs. Smaller syncs seem to run successfully (other than the missing Playlists).

3) Unfortunately DBGView was closed prior to realizing problem. Will attempt new sync later to see if it re-occurs.

4) This is a fairly complex Auto-Playlist, however MMW should handle the fact that the node hasn't loaded. It should either A) disable options that won't work on unloaded node, B) tell user that nothing was synced, C) hold off processing the user action till node has loaded. I don't think this scenario only happens in complex auto-playlists, it would also affect users of slow PCs and large database (as this could happen on any node, not just Playlists).

5) MMA 203 was loaded when testing. However I disconnected, then connected again and sync did start (got stuck on track 1). I suggest going through log anyway to see if anything can be improved in MMW.

lowlander

2013-12-19 20:23

developer   ~0038873

I restarted the PC and attempted a Send To > Device sync with a small Playlist and the sync hung. This was done with the new d_WMDM.dll from FTP [USB Note hang.zip]

Ludek

2013-12-19 20:50

developer   ~0038875

Last edited: 2013-12-19 21:06

Hmm, it has frozen when copying G:\MediaMonkey_Temp\Temp\EB3C.mp3 -> \MMAMusic\Radio\Stef Bos - Papa.mp3

Could you try whether:
1) Device reboot helps ?
2) Return to default '[x] Sync all artwork to file folders' helps ? (As there have been some artworks copied there before copying the track, although I don't believe this is the issue)
3) Was MMA running while syncing? Try to close it to see if it could have an infuence.

lowlander

2013-12-19 21:05

developer   ~0038877

1 & 3) Note that I rebooted both device and PC prior to this sync. MMA hadn't been started yet.
2) This could be problematic as all files are synced to single folder.

Ludek

2013-12-19 21:06

developer   ~0038878

You wrote: "This has been an ongoing issue for the Galaxy Note (got WMP to freeze the same way)"
this makes me feel that it could be the same problem as I had with my Nexus after update to JB 4.2 in the past, there only restoring the device helped: 0010552:0035413 :-(

lowlander

2013-12-19 21:10

developer   ~0038880

This has been an ongoing issue since purchasing device. Device has been wiped several times since. Current Android version is 4.1.2.

Ludek

2013-12-19 21:25

developer   ~0038886

Last edited: 2013-12-19 21:31

The issue 1) is being tracked as 0011636
The issue 4) is being tracked as 0011637

The rest (2,3,5) is related to the MTP freeze. As you indicated that this has been an ongoing issue since purchasing device and observing it with WMP too, I am closing it as "not fixable".