View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009977 | MMW v4 | Synchronization | public | 2012-11-14 16:20 | 2016-05-09 21:13 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.0.7 | ||||
| Target Version | 4.1 | Fixed in Version | 4.1.12 | ||
| Summary | 0009977: Certain android devices aren't recognized over MTP but are by WMP | ||||
| Description | In 0009959 a regression was discovered re. the fact that certain Android devices that worked in MM 4.0.6 were no longer being recognized. However, it was also discovered that certain Android devices weren't being discovered at all in any version of MMW: - Xperia Pro (GB 2.3.4) - LG-E610 (ICS 4.0.3) - Xperia Tipo (ICS 4.0.4) It appears that MM searches for the device on each connect, but the failure is that IWMDeviceManager2::EnumDevices2 ( http://msdn.microsoft.com/en-us/library/windows/desktop/ff801384(v=vs.85).aspx [^] ) did not enumerate the device. However, WMP if left running for a few minutes, eventually recognizes the device. Ludek suggested that this is because MM only enumerates devices on MM start or when a device is plugged-in. But we could implement periodic checks subsequent to an initial connection, in cases where the initial connection fails to recognize a device. | ||||
| Additional Information | Logs posted at 0009959 | ||||
| Tags | todoc-help | ||||
| Fixed in build | 1791 | ||||
| related to | 0009959 | closed | Ludek | Android devices aren't recognized in some cases (regression) |
| related to | 0006324 | closed | Ludek | Some devices don't show after connection in MM |
| parent of | 0011203 | closed | Ludek | MM 4.1 uses 50% CPU every 30 seconds for some users |
| related to | 0011587 | closed | Ludek | Android device can't be browsed if it's unlocked while connected |
| related to | 0013267 | assigned | Ludek | Some Marshmallow devices are not seen by WMP and MM |
|
|
Fixed in build 1606. It is now periodically checked every 30 seconds as part of the UpdateDriveLetters thread. |
|
|
Verified 1615 |
|
|
Note that this change was reverted in 0011203. The workaround is to restart MM to trigger device enumeration. |
|
|
Re-opened, user from ticket MDE-626-20085 experinces this issue too and indicated that restarting MM workarounds the issue. I guess that we could add the check back, but run it only once after 30 seconds from the "DEVICE CHANGE" message (that is coming in his case). i.e. to enumerate the devices on device connect ("DEVICE CHANGE" message) and then later _once_ after 30 seconds re-enumerate the devices. Fixed in 4.1.12.1791 |
|
|
Verified 1791 |
|
|
Verified 1791 |
