View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012439 | MMW 5 | General | public | 2014-12-16 21:49 | 2023-10-05 04:10 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | feedback | Resolution | open | ||
| Target Version | 5.2 | ||||
| Summary | 0012439: Import/Export: Ability to migrate whole Sync Settings to another device profile | ||||
| Description | Currently when user export Options (Device profile) it only exports Options TAB Where if User wants to Export also Sync Settings so that he can copy sync settings from example Samsung S4 to LG L3. To avoid miss imports when MMDS is moved to Different MMW installation with different MM.DB where Sync Settings (tracks, artists, Playlists, ...) are different and importing sync settings would make things worse. As Device profile contain Device ID MMW should Automatically check if there is Local Profile for that Device ID and if it exist than import sync settings otherwise do not import sync option (eg. it will act as current) Solution: Add COPY/PASTE buttons in Portable Device Sync which will copy all Settings from selected profile except Device ID which can be pasted to different device | ||||
| Additional Information | 2023-01-26 https://www.mediamonkey.com/forum/viewtopic.php?t=103604 http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=78673 http://www.mediamonkey.com/forum/viewtopic.php?f=12&t=80831 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
To give a bit more context: the issue that precipitated this is that when some users upgrade their devices (e.g. kitkat --> lollipop) , MMW stops recognising their devices, and the sync profile is lost. Peke is proposing a solution to manually allow users to port sync settings from one device to another, but my preference would be to have MMA always recognize devices going through such an upgrade (the idea of manually porting sync settings could be a neat new feature, but I think it's a low priority item), and/or automatically prompt the user whether an existing profile from e.g. DeviceA-Kitkat should be used if DeviceA-Lollipop has been detected. |
|
|
MMDC profile includes only the settings from the [Options] tab. The logic is that these settings are related to particular device type/model so once the profile is imported by another user (having the same device model) then the user settings (e.g. sync-list) is preserved, but the the device options are loaded from MMDC. If we want to import/export also user specific settings then we should probably introduce another profile file (in addition to MMDC), but I would see this as low priority (same as Rusty). Rusty, what is the kitkat --> lollipop issue? Is there a corresponding issue in mantis or info about that? |
|
|
The kitkat-->lollipop issue is the problem that the user raised in the forum at http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=78673 . After his device was upgraded to lollipop, MMW no longer recognized the device, and instead created a new profile. That's the issue that Peke was trying to solve. I don't think a new bug is really needed--I think that that is the only issue that really needs to be looked into. |
|
|
I'm closing this bug as it doesn't directly address the problem that was reported. Hopefully we'll get more information so that we can actually address the issue. Resolving for now...until we get more info or can replicate. |
|
|
Note that the addressed issue (KK -> Lollipop update) is resolved together with 0012205 in build 4.1.6.1720 , more details about the solution is here 0012205:0041044 |
|
|
Reopen and documented for inclusion in MM5 |
|
|
User request simply Copy Settings from one device to new one in https://www.mediamonkey.com/forum/viewtopic.php?p=505812#p505812 |
