Could someone please implement this feature?
Hello, there’s one feature that’s sorely missing for all long-distance cyclists: the ability to track cumulative totals across multiple stages. When we do a race of over 600 km, most of us break the route down into sections of 150 or 200 km. For the PBP, the vast majority split the route based on checkpoints, resulting in about fifteen recording tracks. So Karoo is sorely lacking the ability to display cumulative distance, riding and rest times, average speed, and cumulative elevation gain. Would it be possible for a developer to implement this feature and create a page with these different fields?
A huge thank you to whoever can develop this feature, which will be widely used by all ultra-cyclists.
Marc PONTIF
-
Are you suggesting you want cumulative stats across mulitple different activities? I'm not sure any bike computer can do that aside from simply resetting the "odometer" that some bike computers have. But as far as I know that data is typically only displayed on the home screen and not in data fields.
Otherwise I think the solution would be to load and discard routes as needed while keeping the activity live, and using the lap button at checkpoints.
On the other hand, as much as I love the Karoo, I don't think ultras are a great use-case for it. For that I'd probably go with the Coros Dura.
-
Hi Marc,
Great use case. I think a live in-ride data field would need Karoo to hold state across recordings, which brings back the same reliability risks splitting the route was meant to avoid.
More realistic: a post-ride rollup in the companion app. Tag activities as one event ("PBP 2027"), and the app computes total distance, moving time, rest time, elevation, and avg speed across the whole series — similar to Strava's training blocks, just for a multi-day event. Easier to review, and much less work for Hammerhead than new firmware/data fields.
Given how many ultra-cyclists hit this exact wall (PBP, LEL, Tour Divide), framing it as a companion-app feature rather than a live data field might get more traction with the dev team. Worth reposting with that spin if you want more votes—so that the Hammerhead Companion DevTeam takes a look at the case and perhaps implements it.
Please sign in to leave a comment.
Comments
2 comments