04-05-2020, 01:09 AM
So...for the last three days, The Explore App has been crashing on my Go. It forces a hard reset, and I lose progress. Usually it is about 2 hours into my ride..at about 8-9k spins. It always happens just after closing the pause menu and starting to ride. Sometimes it is a brief pause...sometimes a longer pause. In each case I had just written down my GPS coordinates.
When I am able to reset the app, it tells me I only did 4-5k spins and sets me back about a 20-30 minute ride (at Level 1) From where I was before. Today...I was actually riding a total of 6 hours before it crashed...but again...that particular session was about 2 hours in and about 9k spins. It is a bit frustrating because It take 20+ minutes to catch back up where I was at. I've probably lost about 10k spins according to the App. I'm not sure if they are still being counted elsewhere, but the distances have been short enough...I Just decided to re-ride part of the route on level 1 difficulty, rather than starting a new ride at my last recorded GPS end point.
After the crash today I enabled "mono" visual mode on the Go, hoping it would fix the problem. Changing to the new mode is the only thing different over the last several weeks that I can think of. I'm wondering if it is just too much for my GO...or if the problem is somewhere else?
When I am able to reset the app, it tells me I only did 4-5k spins and sets me back about a 20-30 minute ride (at Level 1) From where I was before. Today...I was actually riding a total of 6 hours before it crashed...but again...that particular session was about 2 hours in and about 9k spins. It is a bit frustrating because It take 20+ minutes to catch back up where I was at. I've probably lost about 10k spins according to the App. I'm not sure if they are still being counted elsewhere, but the distances have been short enough...I Just decided to re-ride part of the route on level 1 difficulty, rather than starting a new ride at my last recorded GPS end point.
After the crash today I enabled "mono" visual mode on the Go, hoping it would fix the problem. Changing to the new mode is the only thing different over the last several weeks that I can think of. I'm wondering if it is just too much for my GO...or if the problem is somewhere else?