View Issue Details

IDProjectCategoryView StatusLast Update
0009959MMW v4Synchronizationpublic2012-12-24 00:50
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilitysometimes
Status closedResolutionfixed 
Product Version4.0.7 
Target Version4.0.7Fixed in Version4.0.7 
Summary0009959: Android devices aren't recognized in some cases (regression)
DescriptionSome Android devices that were recognized in mmw 4.0.6 are no longer recognized with MM 4.0.7.

User reported issue + log with Xperia S:
http://www.mediamonkey.com/forum/viewtopic.php?p=351105

Peke provided logs re. similar problem with Xperia Tipo and LG e610 (in his case, the failed detection only occurred if the device was connected after MM was running--if it was connected beforehand, then it was detected correctly).
TagsNo tags attached.
Attached Files
1511.LOG (6,968 bytes)
Fixed in build1511

Relationships

related to 0009977 closedLudek Certain android devices aren't recognized over MTP but are by WMP 

Activities

Ludek

2012-11-11 21:18

developer   ~0033100

Fixed in build 1511.

peke

2012-11-12 00:41

developer   ~0033101

Last edited: 2012-11-12 00:52

Still no change in 1511, logs uploaded. I filtered only WMDM to make logs easier to use.
1511 LOGs contains:
- MM startup till 1303 no device
- Connected Device 3102-3125
- closed MM 3792-3816 (device still connected)
- open MM again 3792-5395
- closing MM 6266-6296

As per Rusty remark I tested again with 1501 and behavior was same.

NOTE: Both Explorer and Zentimo Detects Device connection correctly.

rusty

2012-11-12 03:39

administrator   ~0033102

Last edited: 2012-11-12 03:40

Peke, if I understand correctly, the issue you're experiencing is different than the issue that the user is experiencing. You're experiencing a bug, but it's not a regression.

The user, on the other hand, is experiencing a regression (build 1501 worked).

Note: I experience a similar problem with Xperia Pro (GB 2.3.4) in MTP mode: in 1501 and in 1510 MM fails to recognize the device. BUT, WMP also fails to recognize the device, so I don't really consider this to be a bug in MM, but rather a bug in the device's MTP implementation. Can you confirm whether your devices can be synced using WMP?

Ludek

2012-11-12 09:36

developer   ~0033103

Last edited: 2012-11-12 15:55

Peke, the first insertion that I see in the log is
5307 311.52288818 [8420] WMDM: Is Inserted: LG-E610 - SD Card
so it corresponds to
- open MM again 3792-5395

It looks that Rusty's conclusion in his note above is right.

i.e. It can be seen from the log that MM was looking for the device on each connect, but the failure was that IWMDeviceManager2::EnumDevices2 ( http://msdn.microsoft.com/en-us/library/windows/desktop/ff801384(v=vs.85).aspx ) did not enumerate the device, so I guess that WMP also doesn't enumerate it as it uses the same method.

rusty

2012-11-12 15:56

administrator   ~0033110

Note: user at http://www.mediamonkey.com/forum/viewtopic.php?p=351105 confirmed that build 1511 resolve the regression that he experienced.

Waiting for confirmation from Peke...

peke

2012-11-12 23:33

developer   ~0033116

Looks like you two are both right.

WMP do not initially detect device due IWMDeviceManager2 ludek pointed, but after I left WMP oppened for few minutes It adds device and be able to sync.

Open new bug if needed.

Ludek

2012-11-13 00:09

developer   ~0033117

There is no need for new bug, it is bug outside of MM as confirmed.

peke

2012-11-13 00:27

developer   ~0033119

Are you sure as MMW do not detext connected device even I left it for several hours.

It updates as soon as I connect another device.

Ludek

2012-11-13 09:14

developer   ~0033121

Last edited: 2012-11-13 09:23

OK, probably WMP is looking for new devices more often, MM does it just on MM start or when a device is plugged-in as you pointed.
We could implement something similar and looks for new devices every minute or so.

Lowering priority and removed 4.0.7 target...

Ludek

2012-11-14 17:04

developer   ~0033147

Last edited: 2012-11-14 17:04

I see that Rusty entered new issue to cover this: 0009977

peke

2012-12-24 00:50

developer   ~0034166

Verified 1615 During 0009977 verification