View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008926 | MMW v4 | Synchronization | public | 2012-01-05 15:27 | 2012-12-22 23:48 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.1 | ||||
| Target Version | 4.1 | Fixed in Version | 4.1 | ||
| Summary | 0008926: Ability to pair USB and Wireless key of Android device | ||||
| Description | Currently there are several situations in which we should ensure the correct detection of Android device profile: 1. User that already uses MM4 with an Android phone syncing via USB upgrades to MM4.1 and connect his phone wirelessly => MM should detect the wireless device as the same that was synced via USB previously 2. User installed MM4.1 and has never connected the phone via USB, but he tries to connect wirelessly => New device profile should be created and on subsequent USB connect the profile should be used. 3. User installed MM4.1 and connect the phone via USB with the MM for Android installed => MM should get the wireless key from the android install folder so that subsequent wireless connection uses that profile. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1608 | ||||
| related to | 0008610 | closed | Ludek | Wireless sync with android devices |
| related to | 0008923 | closed | Ludek | Write/Read metadata from/to the database of 'MediaMonkey for Android' (when syncing via USB) |
| related to | 0009013 | closed | Ludek | Option to use media server as sync server |
| related to | 0010092 | closed | Ludek | MMW Crashes when deleting Device Profile |
| related to | 0010104 | closed | Ludek | Issues with device profiles created over WiFi subsequently connected via USB |
| related to | 0009877 | closed | Ludek | Initial sync sometimes fails to trigger accept connection dialog on MMW |
|
|
Re: 1) We would need the ability of the Android app to get USB VID (Vendor ID) and PID (Product ID) and send these values on the first wireless connect Re: 2&3) We would need the Android app to store its wireless key in the android install folder so that the desktop MediaMonkey can get it when connecting via USB. |
|
|
Re 1) Instead of USB VID/PID we are using SN. Technically: Since API level 9, android.os.Build.SERIAL is offered. This serial number is however part of many USB IDs - specifically, if the device has already been connected to a PC over USB, it's stored in registry in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_04E8&PID_6860\{serial_number_here} key! I.e., if we browse the whole HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB key, we can find the correct VID and PID. It works well for my Galaxy S2 and also Asus Transformer, i.e. it looks like a method that could be useful for a lot of devices. |
|
|
Implemented pairing based on Serial Number, works fine with my Galaxy Nexus |
|
|
This can be resolved, all have been implemented. a) MM4.1 stores the pairing key into the StorageInfo.xml for MMA b) MMA also stores the pairing key into the StorageInfo.xml for MM4.1 c) in case of WiFi sync MMA uses Serial Number as key so that existing profiles are properly matched as described in the above note. |
|
|
Per offline discussion, if an unpaired device that has connected over USB with pre-4.1 versions of MM, attempts to connect to MM wirelessly, MMW won't be able to automatically match the device to an existing profile. Consequently, the following approach is proposed: "An unknown device is attempting to access the MediaMonkey library. Since you already have numerous device profiles, it's recommended that you physically connect your device for the first time over USB. Grant remote sync / access rights to the MediaMonkey library ? [Yes] [No] [I'm not sure. I'll connect the device via USB instead.] |
|
|
What is the difference between [No] and [I'm not sure. I'll connect the device via USB instead.] ? I would suggest something like this (note that we know the device name as MMA sends it over WiFi): "Samsung Galaxy Nexus - Internal Storage is attempting to access the MediaMonkey Library, but corresponding device profile was not found. It's recommended that you physically connect your device for the first time over USB. Would you like to create new profile and grant remote sync / access rights anyway? [Create new] [I'll connect the device via USB instead] |
|
|
Upon further discussion: 1) For cases where the device exists but hasn't been granted access: "Samsung Galaxy Nexus - Internal Storage" is attempting to sync with the MediaMonkey Library over WiFi. Do you want to allow it to proceed? [Yes] [No] 2) For cases where the device doesn't exist OR can't be found: "Samsung Galaxy Nexus - Internal Storage" is attempting to sync with the MediaMonkey Library for the first time. Do you want to allow it to proceed? Note: If you've previously synced this device with earlier versions of MediaMonkey, it's recommended that you initially sync over USB to preserve your existing sync configuration. [Yes] [No / I'll sync over USB instead] |
|
|
Added to 1604 |
|
|
Verified 1605 |
|
|
Small wording changes to make it consistent with 0009013: 1) For cases where the device exists but hasn't been granted access: "Samsung Galaxy Nexus - Internal Storage" is attempting to sync with the MediaMonkey Library over WiFi. Details: MAC address: xx-xx-xx-xx-xx-xx IP address: xxx.yyy.zzz.aaa [This is an external IP address!] Do you want to grant it access? [Yes] [No] 2) For cases where the device doesn't exist OR can't be found: "Samsung Galaxy Nexus - Internal Storage" is attempting to sync with the MediaMonkey Library for the first time. Details: MAC address: xx-xx-xx-xx-xx-xx IP address: xxx.yyy.zzz.aaa [This is an external IP address!] Do you want to grant it access? Note: If you've previously synced this device with earlier versions of MediaMonkey, it's recommended that you initially sync over USB to preserve your existing sync configuration. [Yes] [No / I'll sync over USB instead] |
|
|
Added in 1608. |
|
|
Verified 75 |
