Since day 1 of using the app it has been a toss up whether or not any given ride will be recorded.
I've tried a variety of techniques with Auto Start on and off (manual Ride start), turn on app before bike and vice versa, and on the Android device have tried different methods of keeping the MC app open in different modes, like on the Ride screen or some other screen, etc.
Throughout this, there has been no consistency with establishing a baseline regarding what causes the problem.
What's the problem? Well, roughly half the rides do not get recorded, drop out during a ride and prompt to Continue the Ride (which I won't see till done riding), and/or draw straight lines on the map (some going to points tens of miles away from the trail I'm on).
When this happens, there is no ride data, which is all I'm interested in.
After spending some time on the phone with a Support tech it was revealed to me how the app will only work if there is cell phone connectivity. I ride mostly in a place where signal is sketchy at best.
There is a perfectly functional GPS in the phone. The data from the rear wheel doesn't require a cell connection, so, it is simply software that was written poorly. It is unable to compensate for a situation where it can't talk to the mothership.
He went on to explain how the coders are located in Switzerland, and that communicating issues by riders in the USA to them is challenging at best. He also hinted at how there is no income stream from a free app it is likely, in his opinion, that they aren't prioritizing improvements to address problems like this.
So, on my high-dollar and state of the art Turbo Levo it is impossible to make use of these bells and whistles, simply because the software engineers have not considered the possibility that a mountain biker might venture outside the reach of cell signal in pursuit of their chosen pastime. I mean, really? People who live a region of the world known for it's mountains (Swiss Alps) are unable to fathom how this cell / data signal requirement might be a little over the top?
Maybe the support tech doesn't really know the answer, though it was made clear that this is something he is asked about often. Even so, his answer would explain why it is an intermittent problem that is hard to narrow down, as RF signal can vary due to a variety of environmental reasons.
I hope Specialized gives this the attention it deserves. There should be a backup plan for when cell signal is lost. It should continue to build the track based on GPS data and continue to record the motor and rear wheel data and associate it with the ride.
Anyone else experience this sort of problem and have found some other fix, or, explanation for it?
I've tried a variety of techniques with Auto Start on and off (manual Ride start), turn on app before bike and vice versa, and on the Android device have tried different methods of keeping the MC app open in different modes, like on the Ride screen or some other screen, etc.
Throughout this, there has been no consistency with establishing a baseline regarding what causes the problem.
What's the problem? Well, roughly half the rides do not get recorded, drop out during a ride and prompt to Continue the Ride (which I won't see till done riding), and/or draw straight lines on the map (some going to points tens of miles away from the trail I'm on).
When this happens, there is no ride data, which is all I'm interested in.
After spending some time on the phone with a Support tech it was revealed to me how the app will only work if there is cell phone connectivity. I ride mostly in a place where signal is sketchy at best.
There is a perfectly functional GPS in the phone. The data from the rear wheel doesn't require a cell connection, so, it is simply software that was written poorly. It is unable to compensate for a situation where it can't talk to the mothership.
He went on to explain how the coders are located in Switzerland, and that communicating issues by riders in the USA to them is challenging at best. He also hinted at how there is no income stream from a free app it is likely, in his opinion, that they aren't prioritizing improvements to address problems like this.
So, on my high-dollar and state of the art Turbo Levo it is impossible to make use of these bells and whistles, simply because the software engineers have not considered the possibility that a mountain biker might venture outside the reach of cell signal in pursuit of their chosen pastime. I mean, really? People who live a region of the world known for it's mountains (Swiss Alps) are unable to fathom how this cell / data signal requirement might be a little over the top?
Maybe the support tech doesn't really know the answer, though it was made clear that this is something he is asked about often. Even so, his answer would explain why it is an intermittent problem that is hard to narrow down, as RF signal can vary due to a variety of environmental reasons.
I hope Specialized gives this the attention it deserves. There should be a backup plan for when cell signal is lost. It should continue to build the track based on GPS data and continue to record the motor and rear wheel data and associate it with the ride.
Anyone else experience this sort of problem and have found some other fix, or, explanation for it?