View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008680 | MMW v4 | Synchronization | public | 2011-11-10 04:00 | 2012-04-23 23:38 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.0.1 | ||||
| Target Version | 4.0.1 | Fixed in Version | 4.0.3 | ||
| Summary | 0008680: Automatic device configuration based on profiles | ||||
| Description | In MM 4.0, profiles for a phone must be loaded manually. For MM 4.0.1, MediaMonkey will include various profiles, and they will automatically be assigned to a device that's pluged in, however, we may need to deal with the situation in which a device matches multiple profiles. e.g. - user plugs in new device - the device matches 2 profiles - user is given the option to choose which device - all profile settings are automatically applied, so the only thing required of the user is to configure auto-sync rules | ||||
| Additional Information | Required for Mambo project as well. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1464 | ||||
|
|
Note that this has been already implemented in 4.0: When a device previously unconnected to MM is found by MM, it tries to find the correct profile in the Plugins\Profiles folder (based on VID_xxxx&PID_yyyy). So the only remaining issue is handling the situation if more than one corresponding profile is found in the Plugins\Profiles folder (more than one profile matches VID_xxxx&PID_yyyy). Currently the first one is automatically assigned, which is not necessarily bad and I presonally would prefer the current workflow. i.e. Are we sure that we want to give users the choice? And what should be included in the choice so that user would have enough info which profile to select? Would be enough to show just device name and profile MMDC filename when showing the choices? |
|
|
From what I see, this looks like it'll mainly be a problem for Blackberry devices which seem to not have unique USB device IDs. Jiri, was there an alternative mechanism implemented for blackberry devices? |
|
|
Now, we haven't found any alternative for blackberry, they all look like the same devices. I.e. the selection made by user would be the only choice to distinguish among them. That said, it doesn't seem to be _that_ important, since this is probably the only common case and also it doesn't make much difference when a common Blackberry profile is used. |
|
|
Fixed failure (detection miss) for some specific profiles in build 4.0.1.1461, mambo build 4.0.1.1507 |
|
|
Verified 1462 |
|
|
This needs to be reverified--MM doesn't presently include any hw profiles so it's impossible to test (and in fact didn't work in build 1464 due to bug 0008938). It can be tested either: a) on a Mambo build, using any of the pre-installed profiles b) in MM build, by exporting an device profile, unplugging the device, deleting the profile from Options, ensuring that the profile is in Plugins/Profiles folder or any of its subfolders, restarting MM, replugging device. If all is well, MM should automatically detect the device and use the configured profile. |
|
|
Verified 1483 |
