Karoo 2 crashed / restarted itself mid ride, data lost
Completed
Towards the end of my ride today, the Karoo 2 restarted itself out of nowhere - the Hammerhead logo appeared, followed by the rest of the startup sequence. I think I'm the 4th user with this issue since the last software update. Climber functionality was active and on the screen while the crash happened - maybe it's related to that, since this was changed in the last update.
The Karoo did not enter any sort of ride recovery procedure, and the ride up to that point (~40 miles) seems lost, it does not show up on the device. I started recording a ride again after the crash, for the remaining 1.6 miles. That one does show up in the device's ride list.
I tried recovering the lost ride via USB on my Mac, but it does not show up in the FitFiles folder, and the temp folders are empty. What's interesting is that the 1.6 mile ride after the crash, which does appear on the device, does not show up in the FitFiles folder either...
-
"Not happy" was looking forward to my 100mile ride on Sunday to Folkstone 8miles in a reboot on its own
I lost the route from the headset as well it said resume ride so I pressed that and it restarted from 0 miles
and no route so had to rely on my mate's Garmin for the route then it crashed again at 32miles and 50 miles
so it only recorded the last 50 miles gutted not happy what's going on??????????
I have a 110-mile event on the 8 of July and do i use the the Karoo2 please help.
-
@Lee - it is a high-severity issue and a very frustrating one. I know, I lost most of my 150k ride too. But let's be fair here - some issues are very difficult to debug. I wouldn't suspect HH are not doing all they can to get it fixed as soon as possible. In the end it's their reputation suffering here, and I expect quite a few people might have decided to switch to the new Edge 1040 - although I'm afraid they might not have much better time with it as new Garmin products are well known for facing teething firmware issues too, and from DCR's review the 1040 probably won't be any different...
-
If you really want to be certain to record your whole ride, you need a second or back-up recording unit.
My primary is a Karoo 2 and I use an old Garmin 1000 as a backup.
I have had my Karoo 2 crash recently and I lost the record of my ride, but had it fully recorded on my Garmin 1000.
-
I have never lost a ride on my Garmin 1000, but like you I did not like the navigation, so I used Komoot on my Iphone for navigation (eats battery life). I then bought the Karoo 2, as it has excellent battery life and I think the navigation is excellent.
But I still carry the Garmin 1000 as a backup, mainly to record my ride.
-
Hi Lee - We have got actual customers testing the fix. All ATG riders are paid customers.
As per my comment and Andy's comment before that, we are hopeful to get the fix out in the next release. There are no planned release this Thursday as we need more testing time. We want to commit that no one loses rides! -
My Karoo 2 also crashed mid ride on Sunday. When it rebooted itself, it picked the ride back up, like it never crashed. But when I finished my ride and looked at the route afterwards, it basically made a straight line from two points of my ride, approximately 1/3 of the 45 mile-ish ride. Not a huge deal, but still disappointing. I also had an issue with the .fit file when the ride uploaded to strava. For some reason the date changed to the year 1989. I'm not sure how to fix that....
-
I experienced this issue and moved over to Wahoo however amidst the frustrations of current people I want to say I appreciate that they are currently working to resolve it, and have provided test firmware to people who have experienced it, which will ultimately allow me to evaluate moving back to the Karoo 2. They can't go back in time and fix the issue, but they appear to be committed to doing so now and I hope they also use this as a chance to see if there's process or testing improvements they can make to reduce the chance of similar issues in the future.
-
Hi all,
It is frustrating, I know, I lost rides also. Not acceptable, but Hammerhead also know this isn’t right.
I’ve been using the potential new firmware for a while now and despite my best efforts to trip it up and prompt a system crash, I’ve yet been unable to make it fail.
Hopefully the others using the firmware have the same experience as I and we’re a little closer to banishing this bug for good.
-
I did t have speed sensor as that bike isn’t used indoors. I had heart rate, cadence, Varia all connected. Phone also connected with alerts for everything enabled. Have tested with and without routing. Forced re-routing, turning unit off and on mid ride. Changing profiles mid ride, stopping one route then starting another
all had no ill effect this far
-
@Andy Watson: did you try the following or can try this too: route active, climber active, everything else also active. And then do a stop and PAUSE RECORDING, do a long coffe break while karoo is in pause mode AND WAIT UNTIL IT TURNED OFF/WENT TO STANDBY. Then push the power button to wake it up again. Mine crashed twice after that workflow. It never does without the pause/standby.
-
Ok. Little ride with the Mrs this evening. Started unit and route in the house and left it to go to standby, woke up, all good, rode with all alerts from phone on, Varia radar on, climber on, cadence and HR connected. Close to end of ride I paused. Let go to standby again. Woke unit up, got to end of route, saved ride, all good!
-
Nevermind, looks like update is rolling out now! Excited to have a fix. After this update, will be disabling auto-updates. The two week update cadence needs to be rethought, as I do not see this as a positive feature. It's simply not sufficient time to properly QA your software package and prevent bugs like this from happening in the future.
-
Does the fix include doing a flush to storage more frequently?
I got bit by this during a PR up Mt. Constitution. The entire way up, the unit was responsive, reporting power, climbr, etc. After a pause at the top, the device presumably crashed and rebooted. When I scraped the data off, almost the ENTIRE ride was lost -- including about 30-60 minutes of time while the unit was still on and working.
If your system only flushes to storage 1x/hr, and is storing ride state in process memory the entire time, that is not engineering that I will use. This is like reliable engineering 101. Losing data is near-unforgivable. I planned a whole weekend around beating my PR and you guys messed it up.
You need to tell us exactly what the problem was, what steps you have taken to fix this, and what steps you will take to never have it happen again -- a public RCA -- or my device is going to PC Recycle -- I don't even care about the price.
Please sign in to leave a comment.
Comments
159 comments