MMA wifi sync (sometimes) failing

[rusty]

Hi,

Thanks--we'll have a look.

A couple of questions though:
1) When you say 'sync failed' can you elaborate? e.g. did MMA fail to connect as in reports earlier in the thread? What was the exact error message?
2) It might not be relevant, but can you upgrade MMW to build 1691 just to ensure that the problem still exists in the latest builds?
3) EDIT: is there any difference if you're running UPnP normally (not as a service)?


Thanks.

-Rusty

[bkenobi69]

1) The message said "Error" in the background (grayed out). I don't have the exact text since I'm at work but I think it said something like "connection failed!". I'll update with exact text later.
2) I didn't know that there was an updated MMW, so yes I will update later.
3) I tried connecting to UPNP before launching MMW (running as service) and with MMW running interactively. Both failed to show any servers.

[bkenobi69]

1) The message says:

Error (grayed out in background)

Synchronization failed!
Connection failed!
OK

2) Upgraded to MMW 1691
3) MMW running interactively (not as service)

Just to be clear...I am running MMW on a Windows 7 machine that has 2 accounts. When MMA syncs correctly, I can go to uPNP and it will list MMW, 2 Windows accounts, and my Directv receiver (not connected to this machine, just on the network). At the moment, uPNP shows zero available servers. Either this is MMA or it is somehow not accessing that type of data due to the router. I don't think that could be related though since restarting the phone corrects the problem (not touching the router).

[bkenobi69]

I just followed the directions of:

http://www.mediamonkey.com/forum/viewto ... an#p376274

I do NOT see port 5000 available. If I go into MMW in Media Sharing (UPnP/DLNA) I see both MediaMonkey Library and MediaMonkey Server claim to be running. But, the port listed is not 5000. MM Library is 51952 and Server is 40930. Neither of those ports show up in the list in Fing either.

[rusty]

OK, based on the most recent set of logs, it appears that the failure is due to a bug in Android versions prior to 4.2. It occurs after the network connection has gone up and down numerous times raising the "network interface index" to use 3 digits.
So the solution is to upgrade, and the workaround if you can't upgrade, is to restart the device (which restarts the network inteface index at a low number).

More info at:
http://www.ventismedia.com/mantis/view.php?id=11774

-Rusty

[bkenobi69]

Disappointing really. I'm on ICS at the moment because the standard OTA update did not work to go up to JB (I'd have to unroot and I'm not sure I care about the update anyway). Motorola/Verizon decided not to go beyond 4.1.2 on this handset, so I can't get up to 4.2 without going to a custom rom. I guess I'll just have to reboot if sync fails.

Since other apps work when MMA refuses to sync/UPNP, is this something that can be worked around another way? If you have a reference to the error in the OS I could read up on, that might help.

[rusty]

See the link at http://www.ventismedia.com/mantis/view.php?id=11774 for more info about the bug in Android.

The problem is that MMA uses the Cling UPnP library, and it depends on the buggy Android function. We'll get in touch with the main authors of that library to see if a fix is in the works.

-Rusty