Cling UPnP library for Android. Not seeing devices after shutdown and restart

Question

I am using the cling library for android to locate and control other mobile devices in my WiFi network. I have downloaded and imported (in Eclipse) the Cling Browser and Cling Switch Power Examples and they work fine until I exit the Switch power app from my remote device and start it again.

Afterwards, it is never again visible inside the Cling Browser App. The only way to make the device appear again inside the browser, is to force stop the Power Switch App from inside the apps menu of android settings and start it again.

Is there a possibility that the AndroidUpnpServiceImpl isn't shutting down correctly? I have tried to first unbind and then also stop the service using stopService() but still nothing.
I have tested on several devices, all using Android 4.1 and 4.4. and I have noticed the same behavior. Am I doing something wrong?

Thank you in advance

I forgot to mention that I can see the logs of UPnPServiceImpl:
>>> Shutting down UPnP service...
<<< UPnP service shutdown completed
which indicates that the service must have properly shut down.

Unfortunately no! I have so far used a workaround to kill the App when exiting so everytime I start it everything works. But this is not good programming practice. I would like a proper solution. — dzografi, Jul 14 '15 at 08:58

cV2 · Answer 1 · 2015-07-17T15:59:38.833

I've found some solution, but it was unfortunately some problem inside the cling library. some colluegue of mine did the fix, I'm not able to share the "patches library" and it's not clear what changes were affected. We used a patched version of: cling-distribution-2.0.1

So possibly with latest lib it's also already fixed? Good luck! Did u test it already with 2.0.1?

So problem was: successful run from library code:

07-17 17:53:23.205  14826-14826/ I/DatagramIO﹕ Creating bound socket (for datagram input/output) on: 192.168.1.110/192.168.1.110
    07-17 17:53:23.205  14826-14826/ I/StreamServer﹕ Setting executor service on servlet container adapter
    07-17 17:53:23.205  14826-14826/ I/StreamServer﹕ Adding connector: 109.46.235.174/109.46.235.174:0
    07-17 17:53:23.205  14826-14826/ D/libc-netbsd﹕ [getaddrinfo]: hostname=xxxxx; servname=(null); cache_mode=(null), netid=0; mark=0
    07-17 17:53:23.205  14826-14826/ D/libc-netbsd﹕ [getaddrinfo]: ai_addrlen=0; ai_canonname=xxxxx; ai_flags=4; ai_family=0
    07-17 17:53:23.205  14826-14826/ I/pnpServiceConfiguration﹕ Thread pool rejected execution of class org.eclipse.jetty.server.AbstractConnector$Acceptor
    07-17 17:53:23.205  14826-14826/ W/System.err﹕ 2015-07-17 17:53:23.215:INFO:oejs.AbstractConnector:Started SocketConnector@109.46.235.174:60087
    07-17 17:53:23.205  14826-14826/ I/DatagramIO﹕ Creating bound socket (for datagram input/output) on: 109.46.235.174/109.46.235.174
    07-17 17:53:23.205  14826-14826/ I/StreamClient﹕ Starting Jetty HttpClient...
    07-17 17:53:23.205  14826-14826/ I/Router﹕ WiFi multicast lock acquired
    07-17 17:53:23.205  14826-14826/ I/Router﹕ Created WiFi lock, mode: 3
    07-17 17:53:23.205  14826-14826/ I/Router﹕ WiFi lock acquired
    07-17 17:53:23.215  14826-14826/ I/UpnpServiceImpl﹕ <<< UPnP service started successfully

error run was something like this:

07-17 17:53:23.205  14826-14826/ I/StreamClient﹕ Starting Jetty HttpClient...
07-17 17:53:23.205  14826-14826/ I/Router﹕ WiFi multicast lock acquired
07-17 17:53:23.205  14826-14826/ I/Router﹕ Created WiFi lock, mode: 3
07-17 17:53:23.205  14826-14826/ I/Router﹕ WiFi lock acquired
07-17 17:53:23.205  14826-14826/ I/DatagramIO﹕ Creating bound socket (for datagram input/output) on: 192.168.1.110/192.168.1.110
    07-17 17:53:23.205  14826-14826/ I/StreamServer﹕ Setting executor service on servlet container adapter
    07-17 17:53:23.205  14826-14826/ I/StreamServer﹕ Adding connector: 109.46.235.174/109.46.235.174:0
    07-17 17:53:23.205  14826-14826/ D/libc-netbsd﹕ [getaddrinfo]: hostname=xxxxx; servname=(null); cache_mode=(null), netid=0; mark=0
    07-17 17:53:23.205  14826-14826/ D/libc-netbsd﹕ [getaddrinfo]: ai_addrlen=0; ai_canonname=xxxxx; ai_flags=4; ai_family=0
    07-17 17:53:23.205  14826-14826/ I/pnpServiceConfiguration﹕ Thread pool rejected execution of class org.eclipse.jetty.server.AbstractConnector$Acceptor
    07-17 17:53:23.205  14826-14826/ W/System.err﹕ 2015-07-17 17:53:23.215:INFO:oejs.AbstractConnector:Started SocketConnector@109.46.235.174:60087
    07-17 17:53:23.205  14826-14826/ I/DatagramIO﹕ Creating bound socket (for datagram input/output) on: 109.46.235.174/109.46.235.174
    07-17 17:53:23.215  14826-14826/ I/UpnpServiceImpl﹕ <<< UPnP service started successfully

Yes, I have been using version 2.0.1 from the beginning. Downloaded from the 4thline.org website. Maybe if you could share what causes the problem then probably I could figure out a solution. Maybe I should build the source code and debug it. Thank you for your response anyway! — dzografi, Jul 15 '15 at 15:27
Okay, Ill search some log, and pin down the solution here. give me a littlebit. — cV2, Jul 16 '15 at 09:58
The logs are not perfect, but definitly at first starting jetty, then setting up some socket completely. — cV2, Jul 17 '15 at 15:59
Thanks a lot for your time and answers. I'll compare it to my logs and hopefully find a solution. — dzografi, Jul 20 '15 at 09:49

Cling UPnP library for Android. Not seeing devices after shutdown and restart

1 Answers1