04-08-2020, 08:35 PM
(04-08-2020, 03:58 PM)emalafeew Wrote: 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?
Thanks for looking into this issue.
Yes, I remembered your prediction, which is why I suspected it might be the issue.
The Go has been stable since I locked back into Mono mode, but it has only been a couple of rides, and they haven't been as long. I will keep it on Mono and let you know if I see any further performance issues.
In terms of heat...I've only noticed the GO getting warm in situations where I have already discharged the battery and I am continuing to use it while recharging it. Using it plugged in while already at 100% charge does not generate a noticeable heat issue. I say noticeable, because I realize something might still be going on...even if I am not noticing it. When I am riding, I always have a fan or two blowing on my face and the Go as well. I have not received any overheating warnings.
I suppose in the "Crash" situations there may have been times I temporarily unplugged the Go, to get some water or run an errand. Perhaps plugging it back in, and then restarting a ride triggered something? Maybe the combination of attempting to recharge even a few percent of battery, and Stereo Mode is the straw that breaks the camel's back?