'Unfortunately the Samsung Keyboard has stopped' annoying dialog keeps popping up during gameplay

Unity Engine
,
1

Since I updated my Samsung Galaxy Tab A to Android 6.0.1, my game has touch input and I now get severe pauses every few seconds, and then a native dialog '‘Unfortunately the Samsung Keyboard has stopped’ pops up in the middle of gameplay.

This is only during gameplay when I am holding down buttons while racing. Perhaps the constant touch is overloading the keyboard somehow?

I’ve rebooted the device, reset Samsung keyboard etc but no difference.
It pops up every 20 seconds or so during gameplay, which is highly annoying.

Any ideas?

2

It does sound like an issue in the new Samsung Keyboard for me. Did you check logcat for the error messages? Did you try resetting the device?

3

I did a factory reset today, no difference :frowning:

I’ve attached the log file from logcat just containing errors from the start of a race in my game. I didn’t really see much activity in logcat when the error occurred unfortunately.

But looking through the log I found this interesting…

08-14 20:00:43.537: E/AndroidRuntime(17364): FATAL EXCEPTION: main
08-14 20:00:43.537: E/AndroidRuntime(17364): Process: com.sec.android.inputmethod, PID: 17364
08-14 20:00:43.537: E/AndroidRuntime(17364): java.lang.NullPointerException: Attempt to invoke virtual method 'void com.sec.android.inputmethod.base.common.SamsungIMEInputConnection.clear()' on a null object reference
08-14 20:00:43.537: E/AndroidRuntime(17364):     at com.sec.android.inputmethod.base.input.ComposingTextManager.clear(ComposingTextManager.java:35)
08-14 20:00:43.537: E/AndroidRuntime(17364):     at com.sec.android.inputmethod.base.input.AbstractInputModule.initComposingBuffer(AbstractInputModule.java:253)
08-14 20:00:43.537: E/AndroidRuntime(17364):     at com.sec.android.inputmethod.base.input.AbstractInputModule.finishComposing(AbstractInputModule.java:310)
08-14 20:00:43.537: E/AndroidRuntime(17364):     at com.sec.android.inputmethod.base.input.AbstractInputController.updateInputModule(AbstractInputController.java:266)
08-14 20:00:43.537: E/AndroidRuntime(17364):     at com.sec.android.inputmethod.base.common.InputManagerImpl.startInput(InputManagerImpl.java:4907)
08-14 20:00:43.537: E/AndroidRuntime(17364):     at com.sec.android.inputmethod.SamsungKeypad.onStartInput(SamsungKeypad.java:474)
08-14 20:00:43.537: E/AndroidRuntime(17364):     at android.inputmethodservice.InputMethodService.doStartInput(InputMethodService.java:2442)
08-14 20:00:43.537: E/AndroidRuntime(17364):     at android.inputmethodservice.InputMethodService$InputMethodImpl.startInput(InputMethodService.java:564)
08-14 20:00:43.537: E/AndroidRuntime(17364):     at android.inputmethodservice.IInputMethodWrapper.executeMessage(IInputMethodWrapper.java:185)
08-14 20:00:43.537: E/AndroidRuntime(17364):     at com.android.internal.os.HandlerCaller$MyHandler.handleMessage(HandlerCaller.java:37)
08-14 20:00:43.537: E/AndroidRuntime(17364):     at android.os.Handler.dispatchMessage(Handler.java:102)
08-14 20:00:43.537: E/AndroidRuntime(17364):     at android.os.Looper.loop(Looper.java:148)
08-14 20:00:43.537: E/AndroidRuntime(17364):     at android.app.ActivityThread.main(ActivityThread.java:7325)
08-14 20:00:43.537: E/AndroidRuntime(17364):     at java.lang.reflect.Method.invoke(Native Method)
08-14 20:00:43.537: E/AndroidRuntime(17364):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
08-14 20:00:43.537: E/AndroidRuntime(17364):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
08-14 20:00:43.607: E/android.os.Debug(1786): ro.product_ship = true
08-14 20:00:43.607: E/android.os.Debug(1786): ro.debug_level = 0x4f4c
08-14 20:00:43.607: E/android.os.Debug(1786): sys.mobilecare.preload = false

Any other ideas?

3182851–242851–log.txt (14.3 KB)

4

There’s no single mention of Unity in your logs. Sorry - can’t suggest anything other than the keyboard issue.