View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0013420 | MMW v4 | Synchronization | public | 2016-07-21 22:07 | 2016-10-09 01:19 |
Reporter | peke | Assigned To | |||
Priority | urgent | Severity | major | Reproducibility | unable to reproduce |
Status | closed | Resolution | unable to reproduce | ||
Target Version | 4.1.14 | ||||
Summary | 0013420: USB: Synchronization reports Can't Access device MTP Connection fail | ||||
Description | Based on user description as soon as it connects his S7 MMW throw an error of not being able to connect to device. | ||||
Additional Information | QGH-350-53271 | ||||
Tags | No tags attached. | ||||
Fixed in build | |||||
|
I've done remote session and we installed Clean Portable MMW. Phone is not connected thru HUB but using Direct USB 3.0 connection. There is three external HDDs connected which were detected normally. Log file from remote session is supplied in Ticket. |
|
Based on LOG and additional IM talk with user it looks like MTP Freeze as Windows explorer access also locks. |
|
Reminder sent to: rusty @Rusty You have S7 device I wonder if you have installed additional drivers so that S7 became available? |
|
In the log I see that 'Big Worm S7 - Phone' and 'Big Worm S7 - Card' were detected correctly, but for both 'Big Worm S7 - Card' and 'Big Worm S7 - Phone' the error from 0013283 was applied because it failed to enumerate storage when accessing storageInfo.xml \Android\data\com.ventismedia.android.mediamonkey\files\files\storageInfo.xml \MediaMonkey\files\StorageInfo.xml with MTP error 8007001F I wonder: a) does phone reboot solve it? b) I guess that storageInfo.xml was created by MMA, but is not accessible from PC (via explorer or MMW), i.e. instance of 0013283. Could you verify that the storageInfo.xml is there when accessing via ES Explorer in Android? |
|
MMW Throw error immediately apron connection and profile is not created. NOTE: It is desired behavior and MMW acts as designed but maybe we should correct message so that it states MMW Can't access device at all and profile is not created. |
|
The message is 'The USB media transfer process is having trouble connecting to [DEVICE NAME]. Please disconnect your device and reboot it. If the problem recurs, please use Wi-Fi Sync instead.' Which I guess is true, because it cannot access storageInfo.xml to match the device profile. Try to verify that the storageInfo.xml is there (in android) and somehow force refresh of the MTP, if the reboot does not help then maybe clearing media storage cache ? i.e. Android -> Apps -> Media Storage -> [Clear Data] or some tips from 0012961:0043503 Note that the [Help] button goes to http://www.mediamonkey.com/mediamonkey-usb-sync -- so we could upgrade the info there if we have some other tips how to force the MTP refresh (Android's media provider refresh) |
|
After uninstall of MMA phone is finally recognized but there was sync errors. Unfortunately log was incomplete and I asked for new one. |
|
As suggested making clean MMA install mede things work with errors, I still suspect MTP issues but ne wlogs are supplied for analyze. |
|
Yes, I see many MTP errors (when enumerating Music subfolders, creating folders and file uploadings) in the last log from #QGH-350-53271 Couldn't it be by a corrupted SD card? Maybe replacing SD card could help? |
|
fyi, works fine on my S7 device. |
|
Resolving no more reports from user |