04-08-2020, 03:58 PM
Hi Shon sorry for the delay!
I suspect your Go is being overloaded between your ride times and keeping it plugged in, which also generates some heat. I also predicted we'd have this trouble when allowing Go users to not be locked to Mono, because stereo rendering takes more computing. Our games do have a hook that Android calls before it runs out of batteries to store progress (ACTION_REQUEST_SHUTDOWN), but seems it isn't being called in the case of your crashes.
Can you confirm it's been stable as long as you have Mono enabled?
I suspect your Go is being overloaded between your ride times and keeping it plugged in, which also generates some heat. I also predicted we'd have this trouble when allowing Go users to not be locked to Mono, because stereo rendering takes more computing. Our games do have a hook that Android calls before it runs out of batteries to store progress (ACTION_REQUEST_SHUTDOWN), but seems it isn't being called in the case of your crashes.
Can you confirm it's been stable as long as you have Mono enabled?