Karoo 2 dies at 5% and refuses to upload restored ride to Strava
Adding another small but annoying mark against the Karoo 2. Tonight while wrapping up a ride my computer decided to die at 5%. I get that I ran it down, but I average 10-12 minutes of ride time per 1%. I should have been well within the margin of error when I had 6 minutes left in my ride.
Then when I got home to charge the device it went through the ride recovery phase and now refuses to upload to Strava or the dashboard.
Honestly these are the little issues that make me question if I'm just testing a very expensive beta unit. These are features that should be firm without failure.
-
These are likely two separate issues: the 5% shut down is just a bad gas gauge algorithm, the ride upload (I assume to Strava has been an issue recently (I still cannot upload to Strava)
If the ride shows up in the Karoo Dashboard online, you can try and push it to Strava from there, or download the fit file and upload it manually to Strava.
Honestly these are the little issues that make me question if I'm just testing a very expensive beta unit.
Let me clear all your doubts, this is exactly what is happening, as Hammerhead has not grown to the point of understanding the customer value of Software QA. I would expect better from them, but people have been putting up with a decade of crappy Garmin SW, so why not...
-
This just happened to me. The battery ran out during my ride and now it won't upload the recovered ride to the dashboard, Strava or Training Peaks. I'm pretty disappointed in the battery life and even more disappointed that I need to faff around with cables to upload my ride.
Edit: It was even more of a faff than I expected. First of all to even access the files I had to meddle with Android's developer settings - then the ride didn't appear as a single .fit file. There was a temp folder with 3 files in and I had to use https://www.fitfiletools.com/ to combine them all to get a file I could upload to Strava and Training Peaks.
-
Me too. Even Adrian Wells' painstaking fix is not the whole story. In my case, of the 3 files in the FileFiles/temp folder, the most recent, according to its modification date, was part of the lost ride data and the other two were older files that would successfully combine with the third into an uploadable .fit file, but it had the wrong ride date. So I needed another fitfiletools step to change the activity date within the two older files before combining and uploading. Then it all looked right.
Please sign in to leave a comment.
Comments
4 comments