pippin wrote: > Maybe. I mean, I've only been using the tablet for 15 minutes or so at > the time ;) > And actually it's been that way for a year or so through dozens of > reboots and several OS updates, so no, I don't think it's something like > that. > > And why does it work with the old SqueezeControl App?
Actually I don't think the error is related to the app's inability to find your servers. I think occasionally the networking subsystem gets in a state where the packet can't be sent. I've seen it once in while too, but it's not often. The server discovery problem is probably caused by the fact that the app doesn't use the "255.255.255.255" address to send the broadcast. Instead it iterates through the device's network interfaces and retrieves the broadcast address for each network. Maybe how your particular network is setup is not compatible with this process. The old version worked probably because it also checked if the Wifi subsystem had DHCP info, and if it did it would preferentially figure out the broadcast address from that. I took that out because it only worked if the device had Wifi and it was a bit redundant since the other method is supposed find all the addresses. Also it might have required an extra permission. I think I may just go back to the "255.255.255.255" method. It seems to be the most reliable way. -------------- Squeezebox apps for webOS, Android and Windows Phone, http://www.angrygoatapps.com ------------------------------------------------------------------------ wt0's Profile: http://forums.slimdevices.com/member.php?userid=18760 View this thread: http://forums.slimdevices.com/showthread.php?t=96757 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
