Android Question Samsung S5 crash reports - Native crash at /system/lib/libinput.so

[Wembly]

Hi

In the last 24 hours I've had 3 different users with Samsung Galaxy S5 reporting similar issues where app crashes. One user submitted a crash report please see below.

The app was compiled with B4A 3.80

Any ideas how I can troubleshoot this?

Please do not suggest the BACK KEY workaround I have seen elsewhere as my app does not make use of it.

Thanks.

Build fingerprint: 'Verizon/kltevzw/kltevzw:4.4.2/KOT49H/G900VVRU1ANCG:user/release-keys'
Revision: '14'
pid: 10879, tid: 10879, name: u.ShiftCalendar >>> uk.co.androidapps4u.ShiftCalendar <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000000c
r0 00000000 r1 78d486a0 r2 00000000 r3 00000040
r4 78d486a0 r5 00000000 r6 78d486a0 r7 78d48d40
r8 be9370c0 r9 78d48cfc sl 402681b1 fp 00000001
ip 40280efc sp be937058 lr 4044601d pc 40444fac cpsr 200f0030
d0 c4618000c3de0000 d1 c45b800041c00000
d2 0000000000000000 d3 0000000000000000
d4 fe8000003f000001 d5 000122e800000000
d6 0000000000000000 d7 c3ea000041c00000
d8 0000000000000000 d9 0000000000000000
d10 0000000000000000 d11 0000000000000000
d12 0000000000000000 d13 0000000000000000
d14 0000000000000000 d15 0000000000000000
d16 0077006f0064006e d17 0073007300650053
d18 002e006900750067 d19 0061007200470049
d20 0063006900680070 d21 0066006600750042
d22 0072005000720065 d23 006300750064006f
d24 3fd1b10853a79915 d25 3fd554fa9ca0567a
d26 3fdb6db71408e660 d27 3fe33333332d4313
d28 3ff0000000000000 d29 0000000000000001
d30 408f400000000000 d31 4024000000000000
scr 28000013

backtrace:
#00 pc 0000efac /system/lib/libinput.so (android::InputChannel::receiveMessage(android::InputMessage*)+9)
#01 pc 00010019 /system/lib/libinput.so (android::InputConsumer::consume(android::InputEventFactoryInterface*, bool, long long, unsigned int*, android::InputEvent**)+56)
#02 pc 0006cbd1 /system/lib/libandroid_runtime.so (android::NativeInputEventReceiver::consumeEvents(_JNIEnv*, bool, long long, bool*)+80)
#03 pc 0006cdd5 /system/lib/libandroid_runtime.so (android::NativeInputEventReceiver::handleEvent(int, int, void*)+52)
#04 pc 000107bb /system/lib/libutils.so (android::Looper::pollInner(int)+478)
#05 pc 00010869 /system/lib/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+92)
#06 pc 00074125 /system/lib/libandroid_runtime.so (android::NativeMessageQueue::pollOnce(_JNIEnv*, int)+22)
#07 pc 00020e4c /system/lib/libdvm.so (dvmPlatformInvoke+112)
#08 pc 00051aef /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
#09 pc 0002a2e0 /system/lib/libdvm.so
#10 pc 00031790 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
#11 pc 0002ee28 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
#12 pc 00064239 /system/lib/libdvm.so (dvmInvokeMethod(Object*, Method const*, ArrayObject*, ArrayObject*, ClassObject*, bool)+392)
#13 pc 0006c50f /system/lib/libdvm.so
#14 pc 0002a2e0 /system/lib/libdvm.so
#15 pc 00031790 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
#16 pc 0002ee28 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
#17 pc 00063f55 /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+336)
#18 pc 0004d6d7 /system/lib/libdvm.so
#19 pc 00055fa7 /system/lib/libandroid_runtime.so
#20 pc 0005753b /system/lib/libandroid_runtime.so (android::AndroidRuntime::start(char const*, char const*)+354)
#21 pc 0000105b /system/bin/app_process
#22 pc 0000e513 /system/lib/libc.so (__libc_init+50)
#23 pc 00000d7c /system/bin/app_process

 

[Erel]

Can you post the link to this app in Google Play?

 

[Wembly]

Sure here you go...

https://play.google.com/store/apps/details?id=uk.co.androidapps4u.ShiftCalendar

 

[Erel]

I've asked someone who is working with me to test it on a Galaxy S5 device and he wasn't able to reproduce this issue.

 

[Wembly]

Well that's reassuring it's not necessarily all S5 devices. I will keep pushing end users for more details if they contact me directly and report back.

Is there anything else I can do to diagnose the error from the crash report?

Thanks.

 

[Erel]

It is hard to say. Do you know when exactly did this error happen?