- Home /
Touch stopped working, works in remote
Hey there, I've suddenly had my game not detect touch input on a Samsung Galaxy SII. I can't remember any apparent changes that would cause this.
The touch is working as expected when I test it through the remote, but when I build this and run it, nothing happens. I popped open a logcat and found this printing out whenever I touch the screen:
E/NativeActivity(29852): channel '40557288 com.unity3d.player/com.unity3d.player.UnityPlayerNativeActivity (client)' ~ Failed to receive dispatch signal. status=-11
Using the latest version of Unity.
Anyone seen this before?
The remote is not a very reliable way to test touch. You are most likely handling both touch and mouse-events, and the remote will (by default) convert touch events into mouse events, hiding any problems that may be happening with touch.
Answer by Joyrider · Aug 20, 2013 at 07:06 AM
It seems it is a known issue, but the log only seems to be the manifestation of a temporary workaround for a deadlock in the android input system.
Only one user reported it as interfering with touches. So not sure it is really the source of your problem. You could post in the forum thread linked above. You might get some feedback from the other users that posted a while ago.
I'd try to test if you have this issue on Unity4.0.1f2 (just with a simple touche script and some buttons) and otherwise, maybe change the version of the android distribution installed on your device.
Looks to be some bad scripting on my behalf which caused the touch not being detected. I had a script erroring on start up when testing under mobile. The message is still appearing, but I'll ignore this for the time being, sorry about that!
i have the same issue, when i tap on the $$anonymous$$indle device i found an error in log
NativeActivity: /com.unity3d.player.UnityPlayerNativeActivity Failed to receive dispatch signal status=-11
and when i continuously tap, it is crashing and showing error Activity$$anonymous$$anager Reason: keyDispatchingTimedOut
Answer by emmanuellesmith · Aug 26, 2015 at 09:58 PM
maybe the game update is not suitable for your device.
Your answer
Follow this Question
Related Questions
Android touches wrong after using the application at least once 0 Answers
Why this simple code doesnt work? 0 Answers
OnPointerExit Issue w/ Radial Menu on Android 1 Answer
Problem shadows Android 1 Answer
Swipe and Joystick Together on Mobile 0 Answers