Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

I've collected some information about the crash via ADB and logcat below, perhaps some of it will help you debug.
It is practically a new headset so I have some suspicions there just hasn't been anyone else to try it on the 3S yet. It is updated and there is far more than enough free storage. If nothing comes of it, I'm not worried about the money -  consider it a donation :)

https://paste.sh/ggy0E8Ow#2rpGTKBbgw9g6DYS2Q5amX_I

(5 edits)

After a little bit of investigating, I found this which is likely the culprit:

05-24 16:41:33.341 23919 23984 F ltisekai.VRHand: java_vm_ext.cc:591] JNI DETECTED ERROR IN APPLICATION: GetStringUTFChars received NULL jstring

05-24 16:41:33.341 23919 23984 F ltisekai.VRHand: java_vm_ext.cc:591]     in call to GetStringUTFChars

05-24 16:41:33.623 23919 23984 F ltisekai.VRHand: runtime.cc:691] Runtime aborting...

05-24 16:41:33.623 23919 23984 F ltisekai.VRHand: runtime.cc:691] Dumping all threads without mutator lock held

Also noticed this:

VrRuntimeCompatHelper: DevicesSupported : 4 devices, quest2|cambria|eureka|quest2|

This would indicate support for the Quest 2, Pro (Cambria), and 3 (Eureka).

This may be a version of OVRPlugin / Oculus XR plugin which doesnt support the 3S?

I'm extremely amateur when it comes to the technical side of Android so this may be totally incorrect, but maybe it gives you some leads at least

Thanks for the logs. If you have purchased it, you can request a refund.