We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I am using Samsung Galaxy S7 edge with Android 6.0.1
Thanks. So it currently gives SIGSEV . Is the the expected behavior?
10-08 05:16:53.787 3158 3158 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
10-08 05:16:53.787 3158 3158 F DEBUG : Build fingerprint: 'samsung/hero2ltelgt/hero2ltelgt:6.0.1/MMB29K/G935LKLU1APH4:user/release-keys'
10-08 05:16:53.787 3158 3158 F DEBUG : Revision: '8'
10-08 05:16:53.787 3158 3158 F DEBUG : ABI: 'arm'
10-08 05:16:53.787 3158 3158 F DEBUG : pid: 22838, tid: 23270, name: GLThread 1860 >>> org.gearvrf.complexsScene <<<
10-08 05:16:53.787 3158 3158 F DEBUG : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xdfe23194
10-08 05:16:53.827 3158 3158 F DEBUG :
10-08 05:16:53.827 3158 3158 F DEBUG : backtrace:
Based on the backtrace the segfault is in the application code, so I'm not sure why we would know if it's the expected behavior or not - it isn't our code ...
HTH, Pete