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

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.

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

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.

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).

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.

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

I just had this issue again today.

MMW in service mode
Started MMA
Selected Sync (wifi)
Sync failed
Back to start page
Selected UPNP, no servers popped up (should have listed MMW, Directv, and 2 windows servers)
Selected second wifi connection (both work on laptop)
UPNP still shows no servers

Log sent: HZBBSTLMZD
MMA 224
MMW 1683


I also tried going to manage apps and force stopping MMA. WiFi sync still fails.

For reference, without changing any settings I can connect to a networked file server via PocketCloud. I can also connect to my RPi using JuiceSSH. This is not a problem with the phone connecting to the network. I reviewed the MediaMonkey Library->Server log and the last item in the list is several days ago (the last time I synced). There is nothing in the MediaMonkey Server->Server log.

I am going to hold off on rebooting the phone which will fix the issue in hopes that there might be some useful info that someone could glean by having me try something and send a log.

MMA is MediaMonkey for Android (this forum) and MMW is MediaMonkey for Windows (main program).

I am having the same problem. Furthermore.... what is MMA and MMW? MediaMonkeyAndroid and Windows????

Please wait until we've posted MMA 222--we've improved the logging. That should be later tonight.

Thanks!

-Rusty

It's possible this is a MMW issue, but I'm not sure. I reset my phone yesterday several hours before attempting to sync (provider forced an update). When I tried to connect to MMW, it did not let me. I then tried to connect to PNP and it listed 3 devices on the network, but not MMW (2 of those were windows media center items on the same machine MMW is located on, the third was the DirecTV receiver). MMW was not loaded, but it was supposed to be running in service mode. I started MMW and tried both sync and PNP worked.

I keep my music collection on a Windows based networked file server running a multi-disk raid. I have been having some issues with that machine that I have just repaired. Turns out that the SAS cable running from the RAID adapter to the drives had a faulty wire. Is it possible that MMW was not happy with network interruptions for some reason? I doubt this is related since these hardware problems have only been an issue for around a month and the failed connections have been an issue for longer.

I will try to generate some debug logs and upload them.

Hi bkenobi69,

As I read through this, it sounds as if restarting MMW isn't relevant--whereas restarting the device is the critical aspect to solving the connectivity problem. Is that correct?

Also, could you generate another MMA log using the latest build, and for that same attempted connection, can you also send a debug log for MMW?

That'll tell us what's happening at both ends, and hopefully give us a clue.

Thanks.

-Rusty

Yes, that's the same solution I posted a few months back but I was hoping there might be a fix on the MMA side. That's still the solution I'm using, but it seems like it must be MMA that is not connecting since my phone can still connect to other network equipment.

Solution by bkenoki69 is posted at: http://www.mediamonkey.com/forum/viewto ... 21&t=74733

-Rusty