UnityPlayerNativeActivity Failed to receive dispatch signal

Unity Engine
1

There is error message keep displayed when I touch the screen of nexus one.
The error message is:
E/NativeActivity(10892): channel ‘41f90ff0 com.abc.abc/com.unity3d.player.UnityPlayerNativeActivity
(client)’ ~ Failed to receive dispatch signal. status=-11

I have updated Unity from 4.1.2 to 4.1.5. The error message was not appeared in 4.1.2.
The error message appears in Nexus One (Android 2.3.6) and Galaxy Tab 8.9 (Android 4.0.4), but it is not appearing in Nexus 4 (Android 4.2.2)

part of my AndroidManifest file on UnityPlayerNativeActivity:



Is there a solution to fix that? thanks

2

Seeing the same thing on a Kindle here. Just updated to 4.1.5.

3

I am also getting that issue. It used to be only during a release build and on a Tab 8.9 on the pause-quit to main menu or end game-quit to main menu. Yet only after the second time consistently. Yet it has transferred to also in Development mode. This was just yesterday I was told about this.

4

bump

5

anybody care to address this issue, I reported it to unity. Yet this is stalling the release of the game or at the very least excluding a whole swath of potential users.

6

Is this breaking anything for you? We are seeing it as well but haven’t noticed any negative results in the app. But it’s still clearly an issue.

7

Hi, unfortunately there is little we can do to avoid that message in the log. The reason the log gets spammed is because of a workaround for a deadlock in the android input system. Once google has released a fix we can also remove our workaround, but as of JB MR1 the issue is still present.

8

Seeing the same thing with Google Glass when using the touch pad. No touches are being delivered as far as i can tell.

9

on a Kindle 100 percent reproduction!
tried Unity 4.1.3, 4.1.5, 4.2. Unity developers seem to have reconciled ((
on a Unity3D_4.0.1f2 all works

10

Seeing this here too. ANY idea on a fix?

11

When I’m trying to run even an empty Unity project on Kindle Fire HD 7", I get the same error on tap or swipe.

E/NativeActivity(11561): channel ‘41a24ba8 com.unity3d.player/com.unity3d.player.UnityPlayerNativeActivity (client)’ ~ Failed to receive dispatch signal. status=-11

I’m using Unity ver4.2.0f4.

Can any of the Unity Devs tell us if this is a Unity issue or a device specific issue?
Is there any other way to fix this error?

12

I’ve started getting the same thing on my end in the logcat on a Samsung Galaxy SII, not getting any touch response at all on the device.
I can’t replicate what it was that caused it to happen, its as if it started happening for no reason at all.

13

Up!
Asus TF101 and Unity 4.2.0f4 (4.1.5f1, 4.1.2f1 also…)
How i can fix it? What version Unity good for production?

14

well this bug slowing down “mid end” devices because of bunch of pushed logs, how to fix it or maybe disable logs? i don’t know

15

Been getting this on a variety of Android devices, preventing me from receiving touch input. It seems to be related to the EZGUI package for me, but I’m not sure.

16

It has nothing to do with EZGUI. As soon as you put a finger on the screen you get this message. Seems to be slowing some devices down, but it’s hard to tell, since i don’t know how to get rid of the msg. With slowing down i mean not registering presses as readily as it should.

17

Yeah, I tried working with EZGUI and it wasn’t the fix. It prevents me from receiving touch input at all, though.

18

I solved this problem. My Unity version is 4.2.

In AndroidManifest.xml,
the property “unityplayer.ForwardNativeEventsToDalvik” of UnityPlayerNativeActivity,

You should change value “false” to “true”.

19

Hello, I have the same issue with my Asus Transformer TF101.

I tested my game on Galaxy S4 and others devices and it run at 60 FPS but on my Asus Transformer TF101 my game is still running with 15-20 FPS.
When I touch the screen ‘Android Debug Monitor’ shows me:

And I tried to set ‘unityplayer.ForwardNativeEventsToDalvik’ to ‘true’ but nothing change.
This only happen on my Transformer TF101…

Is there any other solution to fixe that ?

Thanks

20

bump