You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Complete the setting in the android device.
2. Connected to mobile device with computer.
3. Trying to give input from mobile.
What is the expected output? What do you see instead?
Client no reachable.
Source : TUIOdroid@fe80::d2b3:3fff:fe6e:7cd1%wlan0
What version of the product are you using? On what operating system?
Android 4.0.1
Please provide any additional information below.
Original issue reported on code.google.com by [email protected] on 24 Jan 2014 at 11:22
The text was updated successfully, but these errors were encountered:
Should all work with the latest version. See comment from play store:
Known Issues and Fixes TUIOdroid does not use IPV6, only IPV4. The address for the OSC receiver that you define in the app, has to be IPV4. There are two typical problems until now: 1) There was a functionality in the software that did check if the OSC client is reachable. If there was no reply it said "client not reachable" and also did not send any OSC data. Usually it worked although this message came up as this reply was blocked by the client firewall but still it could be possible that the firewall completely blocks the OSC data. With the latest version this is fixed, OSC data are sent always even though the client might not respond. 2) Some confusion came up as the app sometimes displays an IPV6 address as source address. This is a small bug in the software but only related to the GUI, the data should still be send from IPV4 network adaptor to IPV4 address. This issue is also fixed with the latest version For latest updates check also: https://github.com/TobiasSchwirten/tuiodroid (Project was moved from here: https://code.google.com/p/tuiodroid/)
Original issue reported on code.google.com by
[email protected]
on 24 Jan 2014 at 11:22The text was updated successfully, but these errors were encountered: