by captainmcl » Thu Mar 07, 2013 10:26 pm
This is the same problem I was having, but I am not any more. Of course it's always hard to say why something changes, but I think that part of my problem was the introduction of WiFi synching. It appears (and someone with more behind-the-scenes knowledge can correct me here) that MMW creates a new profile for the WiFi connection, separate from the USB sync profile. It may also have created a separate one for MMA via USB since I already had a non-MMA USB profile for my device. This would make sense because (it would seem) that synching to its own db on the device would be a different protocol than synching to an Android device for use with a non-MM player.
Anyway, I went through my device profiles and cleaned out a bunch of extras. Once the WiFi sync profile is created, it appears that MMW uses that every time going forward. I think that solved at least a portion of my struggles.
This is the same problem I was having, but I am not any more. Of course it's always hard to say why something changes, but I think that part of my problem was the introduction of WiFi synching. It appears (and someone with more behind-the-scenes knowledge can correct me here) that MMW creates a new profile for the WiFi connection, separate from the USB sync profile. It may also have created a separate one for MMA via USB since I already had a non-MMA USB profile for my device. This would make sense because (it would seem) that synching to its own db on the device would be a different protocol than synching to an Android device for use with a non-MM player.
Anyway, I went through my device profiles and cleaned out a bunch of extras. Once the WiFi sync profile is created, it appears that MMW uses that every time going forward. I think that solved at least a portion of my struggles.