Closed GoogleCodeExporter closed 9 years ago
Same issue here.
I've opened Wireshark and to see some UDP going out of TUIODroid, I need to go
in settings and press save settings. Then for a short time, I see UDP TUIO
packets and then I see TCP echo packet coming from TUIODroid. Nothing more.
Just a couple of TCP echo packet per second.
Original comment by matjacq...@hotmail.com
on 20 Sep 2011 at 1:08
I'm receiving TUIO after turning off the windows firewall for the local
network. Now the computer is responding to echo request.
I'm not sure why the TUIODroid is sending echo requests though... Is it
necessary?
Original comment by matjacq...@hotmail.com
on 20 Sep 2011 at 1:14
Same issue here turning off Windows firewall allows the communication to
function correctly. However, allowing udp port 3333 and ping request in windows
firewall isn't enough for some reason.
Original comment by eetu.luo...@gmail.com
on 9 Oct 2011 at 10:17
[deleted comment]
Actually "stability fixes" r28 produced this issue. Remove check for
reachability in OSCInterface.java (i.e. every "if (reachable)"), so that server
tries to send data, even if no client listens. Commincation works with UDP, how
I understand, so there is no reason to check for reachability ? Sorry for my
poor english.
Original comment by giesler....@gmail.com
on 20 Oct 2011 at 3:56
I just came across this issue, too. Removing all the reachability checks and
rebuilding, the issue was solved. Comment #5 has the right explanation: UDP is
a connectionless protocol, so there is no reason to check for reachability.
Allowing UDP port 3333 through a firewall should be sufficient. TUIODroid
shouldn't be sending any TCP data.
Original comment by ben...@benizi.com
on 30 May 2012 at 6:19
[deleted comment]
I'm having exactly the same issue and I can confirm that the lack of a TCP
response causes the app to not continue it's touch messages per UDP. I wish I
was more adept at droid app development so I could fix the issue myself :(
Original comment by gazoo...@gmail.com
on 4 Oct 2012 at 2:50
Didn't have the time to try a fix, but i had a closer look at the source, if
you're able to compile just comment the line 73 : checkStatus() in
OSCInterface.java, it should disable the check thread that is apparently not
working.
Original comment by bkuperb...@gmail.com
on 4 Oct 2012 at 7:32
Hey,
I'll try to fix it within the next days...
Tobi
Original comment by tobiassc...@gmail.com
on 12 Oct 2012 at 6:45
Hey,
should be fixed now! New born Version is now 1.1.
The app does still show an message that the client does not respond, but thats
it.
It still sends messages no matter if the client is reachable or not.
I guess we will update the new version in the Play store soon.
Cheers!
Tobi
Original comment by tobiassc...@gmail.com
on 13 Oct 2012 at 4:07
the app has not been updated in the playstore
Original comment by naakol...@gmail.com
on 18 Feb 2014 at 2:18
can some body tell me how to connect the tuiodroid with pc? step? please...
Original comment by shadab...@gmail.com
on 17 Feb 2015 at 5:31
Original issue reported on code.google.com by
bkuperb...@gmail.com
on 4 Sep 2011 at 8:03