View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011587 | MMW v4 | Synchronization | public | 2013-12-11 17:35 | 2013-12-21 09:44 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.1 | ||||
| Target Version | 4.1 | Fixed in Version | 4.1 | ||
| Summary | 0011587: Android device can't be browsed if it's unlocked while connected | ||||
| Description | If an android device is locked (with a pin/pattern) and is connected via a USB cable, then it cannot be browsed in Windows Explorer--the device can just be viewed. Then if the user unlocks the device, it can be browsed in Windows Explorer. In contrast, with MMW, if the user unlocks the device while connected, it still can't be browsed! This is confusing to users--it appears as if MMW is broken. The workaround is either restart MM or to unplug the device, and then plug it back in (with it unlocked). This is quite annoying though as well as confusing, evidenced by the number of discussions on the topic. | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=74661 http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=73896 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1682 | ||||
| related to | 0011203 | closed | Ludek | MM 4.1 uses 50% CPU every 30 seconds for some users |
| related to | 0009977 | closed | Ludek | Certain android devices aren't recognized over MTP but are by WMP |
| related to | 0006324 | closed | Ludek | Some devices don't show after connection in MM |
| parent of | 0011640 | new | Ludek | Sync process: Check device Lock State |
| related to | 0011766 | closed | Ludek | Sync MMW->MMA USB sync can fail to transfer advanced metadata on occassion |
| Not all the children of this issue are yet resolved or closed. | ||||
|
|
I've reset the target for this to 4.1--it's going to cause so much confusion. Is it really too risky to fix? |
|
|
The aproach suggested in my last private note is risky, because it involves device enumeration which was causing issues in some enviroments: 0011203:0037281 Trying to find something safer... |
|
|
Per discussion with Jiri, assigned to me to implement it, we can revert in case of problems. |
|
|
Fixed in build 1682. I found that the message is sent several times also during device sync, therefore the device re-enumeration is performed only when there is no active device in MMW, this is only partial fix (won't work if another device is already unlocked and shown in MMW), but it is much more safer solution ATM. |
|
|
Verified 1682 |
|
|
I created new bug 0011640 to track multiple devices usage. |
