Wi-Fi Sync doesn’t work

Wi-Fi Sync has a few prerequisites to work correctly:

  • The client (MediaMonkey for Android (MMA)) must be able to browse content on MediaMonkey for Windows (MMW) via Wi-Fi using UPnP.
  • The client must be able to initiate a Wi-Fi Sync operation over UPnP.
  • The client must be able to write files to the chosen storage on the device

If you’re having problems syncing verify that you’re running the latest version of MediaMonkey for Windows and MediaMonkey for Android, and:

  1. Test whether MMA can connect to and access content on the MediaMonkey for Windows UPnP Server:
    1. Click UPnP/DLNA
    2. Click the MediaMonkey Server
    3. Browse and play content

      If you’re able to access the content, but periodically lose the connection, it’s likely that your Wi-Fi connection is unstable. Try rebooting your device & router. er which connectivity will work again (for awhile until the number of wifi on/off cycles re-triggers the issue)

      If you’re unable to access the content at all, then it implies a network or access control problem.
      See:?Failure to connect to the UPnP/DLNA server
  2. If MMA can access content from the MMW UPnP server but can’t initiate a sync, it implies a problem with the sync settings for the MMA device:
    1. Verify that the Sync Profile exists, and is active. Restart MediaMonkey for Windows, navigate to ‘Devices & Services’ (Options > Portable Device Sync in MM4) and verify that:
      • your device is listed
      • your device appears only once for each storage location (e.g. once for Internal memory and a second time for SD storage). If there are duplicates, determine which is the correct profile by comparing which profile has sync settings that match those in MMA, and then delete the duplicates.
      • synchronization with the device’s storage is enabled (and disabled for other devices/locations). This is shown in the list of devices/storage locations in MMW5 (in MMW4 this is shown with a checkbox). For example if you only plan to sync to ‘Galaxy’s SD card’, make sure that profile is enabled, and disable the profile for ‘Galaxy-internal memory’.
      • that MMW allows incoming Wi-Fi Sync connections from the device. In MM5 ‘Allow [DeviceName] to remotely sync with the [ServerName]’ must be enabled (in MM4 the setting is ‘Grant remote sync / access rights to the [Server Name]’)
      • that the [ServerName] in the step above is the same UPnP server that was tested in Step 1. Disable any other DLNA/UPnP servers that are running.
    2. In MediaMonkey for Android, confirm that the sync profile is?active. Restart MMA, and verify that Options > Sync Settings > Storage location settings > Sync to this location is enabled.

      When you’re ready to initiate a Wi-Fi sync, in MMA, click Options > ‘Select sync server’ (instead of clicking Sync), and make certain that MMA is configured to sync with the [ServerName] that you configured above. If MMA is still unable to connect to a sync server:
    3. If this fails to solve the problem, please generate a debug log, and submit a support ticket.
  3. If MMA initiates a sync, but doesn’t write any content, it generally means that either:
    1. No content has been added to the sync list. Choose which Playlists/conent to sync via either:
      • MMA > Options > Sync Settings [DeviceName] > Auto-sync server content
      • MMW Device settings > Sync list (Library –> Device)
    2. Content cannot be written to the device due to a problem with writing to the device/storage location. See:

Online Help: Sync MediaMonkey with an Android device

Applies to: , , ,

Was this article helpful?