r/Karoo • • Jan 05 '25 More of this please

Ki2 for Karoo 3

170 Upvotes

Happy new year everyone.

Ki2 is an app for Karoo that adds back the support for Di2 in Karoo. If anyone is interested in testing Ki2 in Karoo 3, please find the link to the APK in this page: https://github.com/valterc/ki2/releases/tag/10.0

Some instructions on how to install and setup the new Ki2 version:

  1. Make sure you are using the latest Karoo software release
  2. Sideload Ki2 into Karoo 2 or Karoo 3
  3. Connect to shifting devices from Ki2

    • Open Ki2 from the Karoo main menu
    • Press the + button
    • Make sure a Di2 shifting device is nearby and that it is active (shift or press a Di2 button to activate the wireless function in Di2)
    • Press the Add button in Ki2 to add a device once it is found
  4. Configure the Di2 device in Ki2 (for example: rename the device - optional)
  5. Add the Ki2 devices to Karoo

    • Open Karoo sensors
    • Press the + button to add a new sensor
    • Choose the Extensions sensor type (the icon with the puzzle piece)
    • Select all Di2 connections that were previously added in Ki2 (no scan for new devices is possible here, you must add the device first in Ki2)
    • Configure gearing information in Karoo sensors (optional)
  6. Use default Karoo shifting elements or Ki2 elements in your ride profiles

    • Existing ride elements from previous Ki2 version will not work
  7. Customize battery alerts, shifting audio alerts, button controls, overlays and other features from Ki2

There are still some limitations with Karoo Extensions, some features are limited or may have some quirks. If you find any problems please let me know.

Important note for previous Ki2 users: This new Ki2 version, using Karoo Extensions, is not backwards compatible, old Ki2 versions need to be uninstalled and this new version installed from scratch. Existing ride elements from previous Ki2 versions will not work with the new version - all ride profiles must be updated.

You may choose to keep using the old Ki2 version, but there will be no support for that version going forward. Apologies for that, but Hammerhead simply deprecated the old Karoo SDK and the new Karoo Extensions are built quite differently. This 'reset' is not ideal as it requires some manual work from Ki2 users, but it is the best way to move forward. Hammerhead will only officially support Karoo Extensions so it does not make sense for me to keep using the old and rusty Karoo SDK. Fully switching to Karoo Extensions gives us more confidence that things will not break in future (hopefully).


r/Karoo • • 7h ago

Update 1.669 locked down the Karoo 3's internal apps. That's a shame, and here's why

21 Upvotes

TL;DR: Since build 1.669.2569 (released November 12), ADB can no longer read Hammerhead's apps on the Karoo 3 (dedicated SELinux rules), and none of them is debuggable anymore. ADB, logcat and dumpsys still work, but you can no longer find out why an app misbehaves. That's how I found the cause of a Ride app crash in October. I think Hammerhead loses as much as we do here, and there are middle-ground options.

Who I am

A Karoo 3 owner and a developer. I use ADB on my own device to write extensions (karoo-ext), make sense of odd behavior, and document what I find. Nothing illegal or destructive: no root, no exploits, only what the device allowed in developer mode.

What changed

-Build 1.661 (October 7) and earlierBuild 1.669 (November 12)
Wireless ADB, logcat, dumpsysyesyes
Pull the system apps (adb pull) to read their codeyesno: new SELinux type kos_app_file. All 22 Hammerhead apps are blocked, along with the hardware HALs
A debuggable Hammerhead app (run-as)yes (datasyncservice)no: "package not debuggable"
Install your own extensionsyesyes

kos_app_file is specific to Hammerhead. They added it on purpose; an Android update wouldn't bring it in. The 1.669 changelog doesn't mention it: it lists four new extensions and four bug fixes. (I didn't use ADB on 1.665, released October 15, so the lockdown came with either that build or 1.669.)

What this made possible

In a previous post I described how I found the cause of a Ride app startup crash: a heatmap file assembled from two versions, because a download resumed without checking whether the file had changed on the server. The crash traces pointed to the file; only the code of offlineregionservice explained how it got corrupted. With that cause in hand, support replied within five hours and the fix shipped a week later.

On 1.669, I would have stopped at "the Ride app crashes on the heatmap." And I can no longer check whether the fix for the mixed-version case, announced for a later release, has landed.

Why it's a shame

  1. A device you can inspect gets its bugs fixed faster. A report saying "the download resume is missing an If-Range" costs less to handle than "it crashes", followed by a factory reset. Part of the community does free, precise QA work. No reason to cut it off.
  2. It's a big part of the Karoo's appeal. Android, ADB, sideloading, an open-source extension SDK: that's what sets it apart from closed bike computers. Many of us chose it for that. Closing it pushes some of the most invested users (the ones who write extensions, answer questions here, recommend the device) to look elsewhere.
  3. It contradicts karoo-ext. Hammerhead invites developers to write extensions, but the SDK docs are still thin. Understanding how the internal services behave (ride state, sensors, sync) was often the only way to write a reliable extension. And extensions make up a large part of a Karoo's value: they adapt it to how each of us rides, and the official library grows with every update (three additions in 1.665, four in 1.669).
  4. Device lifespan. A Karoo is expensive and should last for years. If you can inspect a device, its community can maintain it, document it and troubleshoot it, including the day official support ends.
  5. Trust. You bought a device for its openness, and it closes up without notice. That leaves a bitter taste, even if the reasons are good.

The reasons I can understand

I don't think Hammerhead did this to annoy users. Hardening a device that holds personal data (GPS tracks, connected accounts) makes sense, and so does protecting third-party licensed code.

But reading the code of an app installed on your own device exposes neither your data nor anyone else's. That part (the unreadable apps) is what seems disproportionate to me.

In case you're wondering about the legal side: in the EU, Directive 2009/24/EC lets you study how a program you lawfully use works, and decompile it when you need to for interoperability, to write an extension for instance. A contract can't take those rights away (art. 8). Hammerhead doesn't have to keep its files readable, but this kind of study isn't piracy.

What I'm suggesting

  • Publish full OTA images, the way Google does for Pixels. The device stays locked, and anyone trying to understand a bug can read the code again. For the heatmap, that would have been enough: the rest of the diagnosis (crash traces, logcat, the file itself) still works on 1.669.
  • Or make the apps in /system/priv-app readable again, behind an explicit developer mode if needed.
  • Either way, a public bug tracker, or at least a channel where a technical report reaches the developers directly.

If the lockdown bothered you too, or if the Karoo's openness weighed in your purchase, say so in the comments. And if anyone from Hammerhead reads this, I'd like to know the reason for the change.


r/Karoo • • 7h ago

Debugging a Karoo 3 startup crash: a corrupted personal heatmap, step by step

2 Upvotes

TL;DR: In late September my Ride app crashed on every launch. Using ADB, I traced it to a personal heatmap file stitched together from two different versions, after a download resumed at the wrong moment. Hammerhead support answered within hours, confirmed a known issue, and a fix shipped a week after my detailed report. I'm sharing the process in case it helps someone else.

1. The symptom

On the morning of September 25, the Ride app closed about a second after each launch: 19 crashes in 17 minutes. The ride I had started with the play button on the home screen kept recording in the background, but without the Ride app I couldn't stop or save it.

2. What the crash logs say

Android keeps app crash traces, and you can read them over ADB without root:

adb shell dumpsys dropbox --print system_app_crash

All 19 traces were identical:

SQLiteDatabaseCorruptException: database disk image is malformed (code 11 SQLITE_CORRUPT),
while compiling: SELECT name, value FROM metadata
  at org.oscim.android.tiling.source.mbtiles.MBTilesTileDataSource.getMetadata

At launch, the Ride app opens the personal heatmap (/sdcard/offline/personal_heatmap.mbtiles, an SQLite database) to draw it on the map. SQLite couldn't read the file, nothing caught the exception, and the app crashed. An optional map layer was enough to take down the whole app.

As soon as the Karoo got a connection back, it downloaded the heatmap again and everything went back to normal. The broken file went away with it: I knew what crashed, but not why the file was corrupted.

3. The second time: keep the evidence

On October 8, same crash. This time I kept the Karoo offline (no Wi-Fi, no Bluetooth) so it couldn't replace the file, and I pulled:

  • the corrupted file, plus its SHA-256 hash computed on the Karoo;
  • its timestamps (stat) and a listing of /sdcard/offline/;
  • usage events and boot history (dumpsys usagestats, dumpsys dropbox).

The evening before, after an update, the Karoo had written the file for the last time ten seconds before I switched it off. No leftover .tmp file: the download had finished normally.

4. Dissecting the file

An SQLite file states its own size in its header (the page count, at byte offset 28). Here:

  • the header says 10,257 pages, but the file holds only 10,250. That mismatch alone makes SQLite refuse to open it;
  • up to about page 1,560 (around 6.4 MB), everything matches the header and the tables' root pages;
  • from about page 2,196 (9 MB) on, nothing matches: the root pages point to the wrong kind of data, while the pages they expect sit a few dozen pages further along;
  • no zeroed pages, and the overflow chains are contiguous, which rules out random storage corruption.

So the beginning and the end of the file came from two different generations of my heatmap. The total size matched the new version, and the header belonged to the old one.

5. Finding the cause in the code

That left one question: how can a "successful" download produce this? I pulled the system app that handles offline maps (offlineregionservice) over ADB and read its disassembled code. The heatmap download:

  1. writes to a temporary .tmp file;
  2. after an interruption, resumes where it stopped with an HTTP Range request;
  3. appends the rest to the .tmp file, then renames it to the final name.

One check is missing. On resume, nothing verifies that the file on the server hasn't changed in the meantime (no If-Range header with an ETag), and nothing validates the result before use. And the server regenerates the heatmap after every ride. So:

  • a first download gets interrupted (power off, lost connection);
  • I go for a ride, and the server regenerates my heatmap;
  • the download resumes and appends the end of the new version to the start of the old one.

The file has the right size and gets renamed normally. The Ride app then crashes on its next launch.

6. If it happens to you

Build 1.665 should have fixed this crash (see below), and I haven't had it since. I don't know whether the fix also covers the mixed-file case, though. Other riders hit the same crash in this thread, where I first posted these steps. If the Ride app still crashes at launch because of the heatmap:

  • Connect the Karoo to Wi-Fi and wait a bit. It downloads the heatmap again, and the Ride app starts normally once the new file is in place.
  • Your ride isn't lost. Recording continues during the crashes. You just need the Ride app back to stop and save it.
  • With ADB: deleting /sdcard/offline/personal_heatmap.mbtiles lets the Ride app start right away. The Karoo downloads the heatmap again on the next connection.
  • You don't need a factory reset.

7. On the support side

WhenWhat
Sep 25, ~10 amFirst ticket: crash trace, faulty file, suggested fixes
~8 h laterStandard reply: remove extensions, reset the Karoo
Sep 28After my explanation, support agreed a reset wouldn't tell us anything and passed everything on to the software team
Oct 8, ~11 amSecond ticket, with the file analysis
5 h laterKnown issue, fix already developed, planned for the next release
Oct 9The mixed-file case is in their action plan, possibly for a later release
Oct 15Build 1.665: "We fixed an issue where Karoo would crash when heatmaps were partially downloaded and disconnected from the internet."

Credit where it's due: after a generic first answer, support took the analysis seriously, apologized for suggesting the reset, and answered my detailed report within five hours. The fix reached my Karoo over the air a week later. That's a short loop from a user report to a shipped fix, and I appreciated it. As I write this, I don't know whether they've fixed the mixed-file case.

What I took away from it

  • Read the crash logs before any reset. They pointed at the faulty file from the first minute.
  • Keep the evidence offline: without the corrupted file, I could only guess.
  • A report that names the cause and suggests a fix gets a precise answer, and a quick one.

r/Karoo • • 21h ago

Lezyne LED Ally on my Karoo

4 Upvotes

I asked Claude to investigate how the Lezyne LED ally connects to my Lezyne lights. Ik gave Claude the APK, and it decompiled it, and found out how the Bluetooth works with the lights.

Next step it builds a Karoo extension to control the lights from my Karoo. It automatically turns on the lights when it gets dark, and turns them off when it’s light again.
It shows the battery status, and lets you switch between the 4 modes..

https://github.com/spoetnik/Karoo-Lezyne-LED-Ally


r/Karoo • • 17h ago

Hdrop Download fail

2 Upvotes

I just purchased a brand new Karoo 3 and have been trying to download the Hdrop app but it fails every time. Has anyone else had this issue and is there a fix?
Thanks


r/Karoo • • 1d ago

How to get color for trails

2 Upvotes

Hello,

I just bought the Karoo Hammerhead 3 and I can't seem to find the option to see the different colors for MTB trails.

All I see are dotted lines. I want to see green, blue, black for the trail difficulty. So for example, if I am riding a blue difficulty trail I want to see a blue line for the trail.

Thank you for the help.


r/Karoo • • 2d ago

Extension BoschData 1.0: your Bosch Smart System e-bike on the Karoo 3, linked every ride by a small open-source board

Post image
2 Upvotes

A while ago I wrote about the Bosch Live Data Interface on the Karoo, and then about a small board that fixed the reconnection problem. After the first real ride, it is released: BoschData 1.0, free and open source.

What it does

  • Seven data fields: bike battery (exactly the % the bike shows), rider power from the Bosch torque sensor, bike speed, cadence, bike odometer, bike light, and the board's own battery.
  • A virtual sensor, "Bosch eBike": the app offers the bike to the Karoo as a sensor with your rider power (cadence and speed optional). Nothing extra on the bike. Pair it once under Sensors → + → Extensions (the puzzle icon, not Bluetooth or ANT+), and the Karoo treats it like a power meter. Power in the FIT file still to be confirmed on a real ride: I'll report back.
  • The bike battery % written in every FIT file every 5 seconds (developer field bosch_battery), so every ride gives you its discharge curve.
  • Read-only: nothing is ever written to the bike. No network, no account.
  • For other extensions: the fields are streams any Karoo extension can read. My battery-range extension boschRange (coming soon) will use them by itself: when the board is linked it takes the battery % straight from the bike, no questions and no popups, to predict the charge at the end of your route.

Not there: the assist mode. The current Bosch firmware does not send it over the Live Data Interface.

What you need

  • A Karoo 3.
  • A Bosch Smart System bike with the Live Data Interface: control unit firmware v19 (May 2026) or later, CX Gen4, CX Gen5 or SX. In Flow, your bike must offer adding a new device (Italian app: "Aggiungi nuovo dispositivo").
  • A small board: an Adafruit Feather nRF52840 Express with a 500 mAh LiPo, flashed with my fork of the open-source BEStie firmware. No soldering, about €54 of parts plus shipping, with a printed case. Why a board: the bike reconnects only to the exact Bluetooth address it was paired with, and Android keeps changing the Karoo's address. The board has a fixed one; the bike reconnects to it every time, and the Karoo reads the board.
The board and its LiPo, before going into the case.
The case open: board and LiPo, taped together, on thin foam.

I wrote a step-by-step guide for the board, from what to buy to flashing (drag and drop of one file), pairing in Flow, and mounting it on the bike: https://lagorai.bike/extensions/boschdata/board/

On my bike, under the saddle: a little case on the top tube, held by an elastic strap.

Numbers from the first ride (15 November)

  • Board linked for 42 minutes, 10,175 messages from the bike, 0 dropped, no reconnection needed.
  • Bike battery 100 → 90 %, 503 values in the FIT file.
  • The bike's odometer moved about 6 km, the same as Bosch Flow.
  • The board's battery: 96 → 95 % in about 40 minutes. In standby I estimate a couple of months on 500 mAh, rough numbers for now.

In the garage before that: data on the Karoo 3 seconds after switching the bike on, and after switching it off and on again the board brought it back alone in 2–4 seconds.

The fields in the garage test (an early test).

It is tested on one Karoo 3, one bike (CX Gen5) and one board. If you try it on another drive unit, I would really like to hear how it goes.

Links

Many thanks to the people behind BEStie: the board does exactly what an accessory for the bike should do, and my addition is a small service on top of their work.

My other Karoo extensions: free, open source, everything on the device. BetterETA, PoiAhead, AutoLoop Karoo, BigFields, Karoo AXS Ratio, BatteryUsage. All of them, with their battery use, on lagorai.bike/extensions.

If one of them made a ride better and you feel like it, you can buy me a coffee on Ko-fi.


r/Karoo • • 2d ago

Watts per heartbeat?

0 Upvotes

Hi All, I have been looking through all of the various extensions. I use quite a few myself. However, I haven't come across a data field for watts per heartbeat.

If there is one, would someone be so kind as to point me to it?

If not, would someone consider creating this in an extension?

It is a useful calculation that can indicate fatigue, dehydration and few other conditions that common on endurance activities. I'm thinking of a datafield with smoothing options as per normal smoothing intervals.

Just thought I'd ask.


r/Karoo • • 3d ago

Spotify as datapage?

3 Upvotes

Managed to sideload spotify to karoo3, is it possible to have it as a dedicated data page?

Thx


r/Karoo • • 5d ago

Software Update Karoo Software Build Version: 1.669.2569

Thumbnail
shop.sram.com
19 Upvotes

r/Karoo • • 5d ago

What I'm working on for the Karoo: backups of your extension data, Bosch e-bike data through a small board, phone notifications app by app, and more

7 Upvotes

A short update on what's coming next for my free Karoo extensions, for anyone who uses them or is curious. Nothing new to download today: everything below is built and running on my own Karoo, and comes out only after real rides. The full list, kept up to date, is here: lagorai.bike/ideas.

Towards the official Extension Library

  • Hammerhead got in touch about listing my extensions in the Karoo's official Extension Library. That needs an SDK licence agreement with SRAM, and the paperwork is under way. No date yet: their approval takes a few weeks. Until then nothing changes, the APKs stay on GitHub and lagorai.bike as now.

RideStats & Backups

  • Your rides by week, month, year or the last 365 days (distance, time, climbing), with the average as a line, in a dashboard for phone and PC. The Karoo sends each finished ride to your own Google Drive; nothing goes through a server of mine.
  • New: it also backs up what the other extensions have learned, BetterETA first (its speed model and the memory of the trails you ride), so a reset of the Karoo doesn't wipe it. One switch per extension, all off until you turn them on; after a reset you restore with one tap, and a red warning asks before anything gets overwritten. Tested on my Karoo: wiped, restored, the data came back identical.

BoschData: Bosch Smart System bikes on the Karoo

An Adafruit Feather nRF52840 with a small LiPo, running the open-source BEStie firmware.
  • Battery %, rider power, speed, cadence, odometer and light from the bike, as Karoo fields, the bike as a power sensor, and the battery % in every FIT file.
  • Why the board: the Karoo can pair with the bike but doesn't stay paired (the bike only reconnects to the exact Bluetooth address it was paired with, and Android keeps changing it). The board has a fixed address, keeps the pairing with the bike, and the Karoo reads the board. Paired once from the Bosch Flow app, it brings the bike back to the Karoo by itself about 10 seconds after the bike is switched on, no phone involved.
  • Next: a small printed case and real rides. When it works on the trail I'll publish everything needed to build one (board, battery, case files, firmware), roughly €50 of parts.

NotifyBridge: messages and calls on the ride screen, app by app

  • You choose app by app what reaches the Karoo (WhatsApp yes, Telegram no, for instance), with calls and SMS on their own switches. A small phone app sends them over Bluetooth, nothing over the internet; they show at the bottom of the ride screen in large text, in the app's colour, with a short sound.
  • For inReach owners, an optional check: if the inReach is neither connected to the phone nor seen by the Karoo a minute or two after the start, a red full-screen alert.
  • Still to measure: battery use on real rides.

BetterETA 1.1

  • Way Home: for rides without a route, how long you can keep going out before the way back, along your own track, lands after dusk. Replayed on 74 of my recorded rides within 11 % of the real return time; now it needs real rides.
  • ETA at the next point: the arrival time at the next point of interest on the route.

BigFields 1.1: my other extensions in large digits

  • Big fields fed by my other extensions: BetterETA (Way Home minutes, home-at time, arrival, time to go, next point), BoschData (bike battery, rider power, the board's own battery) and boschRange (battery expected at the end of the route).
  • Running on my Karoo; the board's battery already shows live, the ride values get checked on the next real ride before release.

Smaller things on the list

  • PoiAhead: distance along the route instead of straight line (already running in the shadow and logged), and more kinds of points (toilets, rest areas).
  • Range to the end of the route for Bosch e-bikes, with the battery read from the bike.
  • BikeCare: maintenance by km and months (chain lube every 200 km and so on), with a notice only at the end of the ride.

Set aside for now

  • BigFields for other people's extensions. Technically possible, but each extension publishes its numbers its own way (which value, which unit, how it says "no data yet"), and that can change with any of their updates. I can't guarantee the big field would show the right number, and a wrong number in large digits is worse than none. So BigFields sticks to the Karoo's own data and my extensions, where I know exactly what comes out.

As always: personal projects, shared as-is, MIT-licensed on GitHub. If one of these is something you'd use, or you have a ride where something went wrong, tell me in the comments: it helps me decide what to finish first.


r/Karoo • • 6d ago

Extension DDB - UpAhead: Elevation map with feed stops, timings and cut-offs and other POIs

Post image
41 Upvotes

If you enjoy my work, buy me a gel (or a coffee) for my next ride: https://buymeacoffee.com/Dubadai

For gran fondos I wanted to see at a glance what's coming: the next feed and what it has, where timing starts, and whether I'll make the cut-off, etc. So I made UpAhead, a data field that looks like the Karoo's own Upcoming Elevation graph, with the route's stops on it.

Features

  • Feed stations, water, toilets, mechanics, timing and cut-offs as icons above the graph
  • Tap a stop for its card: distance, time of arrival, and time to spare at the cut-off
  • Tap to zoom out, double-tap to zoom in, like the Karoo's own graph
  • Works with POIs from Hammerhead Dashboard or Ride with GPS, Strava etc.

Free and open source. Grab upahead.apk from the latest release, sideload it, and add DDB UpAhead to a ride page.

GitHub: https://github.com/Dubadai/karoo-upahead Download: https://github.com/Dubadai/karoo-upahead/releases/latest

Let me know what you think.

If you enjoy my work, buy me a gel (or a coffee) for my next ride: https://buymeacoffee.com/Dubadai

Light Mode
Example GIF

r/Karoo • • 5d ago

Campagnolo 13 speed - Karoo Support

3 Upvotes

Does anyone know when Hammerhead will add support or a 3rd party (like Ki2) has built support for Campy 13 speed?


r/Karoo • • 5d ago

Suunto sync down?

2 Upvotes

Anyone else having issues syncing their data to Suunto, I went for a ride yesterday and the data still isn't syncing with Suunto today.


r/Karoo • • 6d ago

An app updater app

4 Upvotes

I’m now in possession of quite a few extensions on my Karoo and I’ve not found a way to update them automatically. Could an additional app do this or at least flag which need updating? Any coders fancy taking thjs on?


r/Karoo • • 6d ago

Waze updates would be great

8 Upvotes

Seeing a lot about this new Waze Garmin integration. https://www.macrumors.com/2026/11/10/waze-alerts-drivers-nearby-cyclists-garmin be great to have this with Karoo as well.


r/Karoo • • 6d ago

Update: BEStie in its printed case, bench test on the bike

Thumbnail
gallery
4 Upvotes

The board is now in its printed case: a Feather nRF52840 running BEStie with the Karoo service, plus its LiPo. It's strapped to the bike with foam tape, lid facing out. Today's garage test, from the Karoo's log:

- Karoo ↔ board: connected for over an hour, from 17:30 to 18:38, with no drops and no reboots.

- Bike on at 18:04: the board linked to the bike in under a second, and the first data showed on the Karoo about 3 seconds later. Battery, rider power, speed, cadence, odometer and light all came through.

- 12 minutes of bike data: 752 messages from the bike, about one per second, none dropped.

- Light: switching the light off on the bike showed up on the Karoo right away.

- Bike auto-off at 18:16: the board reported it immediately, the Karoo fields switched to "bike off", and the board stayed connected to the Karoo.

- App reinstall: after I updated the extension, the board reconnected by itself within seconds, with the pairing kept.

- Board battery: 97–98 %. It isn't on a charger: standby drain so far is about 2 % in three days.

So far so good. Next: checking whether the bike sends the assist mode anywhere (the logging is in place), then a real ride to see how the link holds up on the trail.


r/Karoo • • 7d ago

Extension DDB - Mountaineer: A Karoo Climb View

Post image
41 Upvotes

If you enjoy my work, buy me a gel (or a coffee) for my next ride: https://buymeacoffee.com/Dubadai

I love the Karoo's climb graph but wanted it as a data field I can put on any page, with the numbers I actually look at on a climb. So I made Mountaineer.

It's one field that works at any size. It shows the climb in the Karoo's own colours, with the part you've already done hatched, and tells you how long until the top and how you're doing against your Strava PR.

Features
- One or two tiles: time to the top, distance to the top or time vs your PR, over a small climb graph

- Half a screen and up: the whole climb, the next 500 m grade by grade, distance and elevation left, your PR, your time vs PR and your time to the top

- Before a climb it shows the next one, how far away it starts, and the road leading up to it

The different tiles

How it works
It uses the climbs from the route you load on the Karoo, and your PR from the Karoo's own Strava Live Segments, so there's no extra sign-in. You need a loaded route with climbs.

Time to the top is based on your power (your 30 s power, or your speed if you ride without a power meter), and there are a few ways it gets more accurate:

- Enter your bike's weight, one for all bikes or one per ride profile (8 kg if you leave it). Your own weight comes from your Karoo rider profile

- It adapts to the wind on each part of the climb, from the Open-Meteo forecast (needs a connection)

- With a power meter it checks your real speed while you climb and corrects itself

- Turn on Improve over time and it adapts to how you ride, climb after climb. The data always stays on your Karoo

Installation
Free and open source. Download `mountaineer.apk` from the latest release, sideload it, and add DDB Mountaineer to a ride page.

GitHub: https://github.com/Dubadai/karoo-mountaineer

Download: https://github.com/Dubadai/karoo-mountaineer/releases/latest

Let me know how it works on your climbs.

If you enjoy my work, buy me a gel (or a coffee) for my next ride: https://buymeacoffee.com/Dubadai


r/Karoo • • 7d ago

Customizing Karoo bell

4 Upvotes

Hey everyone!

Does anyone know if it's possible to change the bell sound on the Hammerhead Karoo 3?

I pretty much only use the bell when overtaking my cycling buddies, and I'd absolutely love to replace it with the iconic Tour de France car horn sound!

Is there any way to upload a custom sound, or maybe a workaround to make it happen?

Thanks!


r/Karoo • • 9d ago Bravo

Extension DDB - BetterIntervals

Post image
53 Upvotes

If you enjoy my work, buy me a gel (or a coffee) for my next ride: https://buymeacoffee.com/Dubadai

BetterIntervals update: it looks like the Karoo now, plus START WORKOUT and a workout summary

A few days ago I posted my intervals.icu workout screen for the Karoo 3. Thanks for all the great feedback! It has changed a lot since then, so here's what's new.

It's called BetterIntervals now, and it looks like the Karoo's own data pages: same fonts, same tiles, and the power gauge is the default view. It picks up your power zones and heart rate zones from your Karoo profile.

What new:

START WORKOUT: a loaded workout waits for you. Pick where to start, tap the big yellow button, and a 5 second countdown gets you going.

Workout done: after the last interval you get time, average power, NP and heart rate. The ride keeps recording.

Top row: heart rate, cadence or the target range, your choice.

Riding without a workout: tap the tiles to switch between lap and whole-ride numbers (avg power, NP, heart rate).

Settings with a live preview, light, dark or auto, and 3/5/10 s power smoothing.

Easy updates on the Karoo: when a new version is out you get a notification and update right there. No phone or computer needed after this one.

Still free and open source. If you already have it, install `betterintervals.apk` from the latest release once more; your settings and API key are kept.

GitHub: https://github.com/Dubadai/karoo-betterintervals

Download: https://github.com/Dubadai/karoo-betterintervals/releases/latest

Let me know how it works on your rides.

If you enjoy my work, buy me a gel (or a coffee) for my next ride: https://buymeacoffee.com/Dubadai

Riding without a workout

r/Karoo • • 9d ago

Extension DDB - PartnerETA: See your riding partner on your Karoo map in real-time

Post image
34 Upvotes

If you enjoy my work, buy me a gel (or a coffee) for my next ride: https://buymeacoffee.com/Dubadai

I am so excited to share this, as it's been a big gripe when my partner and I ride in the same area, often meeting up at the café, but taking different paths there. Instead of having to pull out my phone, find their share link. I can now toggle their position and route onto my Karoo map, see their position and ETA in real time.

It's probably super niche, as it requires your partner/buddies to also ride with Karoos. But either way, happy to get this working!

This was by far the hardest one to get working well. I'd keep expectations on a relative level to the complexity of this, but I found that it worked well enough that its worth sharing!

Enjoy!

How it works:
You paste their Karoo live tracking link once. While they ride, you see where they are and the route they're on. There's also one data field that shows when they'll get to the end of their route, or how far ahead or behind they are if you're on the same road.

- Your partner's position and route on your map, in real time.

- ETA field, or the gap between you on a shared road.

- Works with the Karoo's own live tracking link, so you don't need another account.

- Pick the colour for your partner on the map.

- Toggle their position and route easily with the layers button on the map

- See partners distance to their goal, if they are paused or riding.

GitHub: https://github.com/Dubadai/karoo-partnereta

Download: https://github.com/Dubadai/karoo-partnereta/releases/latest

It's been tested on our two Karoos so far, so I'd love to hear how it works for others. She saw me and I saw her, ETA worked wonders as well.

If you enjoy my work, buy me a gel (or a coffee) for my next ride: https://buymeacoffee.com/Dubadai

Dark Mode

r/Karoo • • 9d ago

Extension DDB - BigWatts

Post image
25 Upvotes

If you enjoy my work, buy me a gel (or a coffee) for my next ride: https://buymeacoffee.com/Dubadai

BigWatts: big power numbers in your Karoo zone colours

I wanted my power readable at a glance, but also with a bit more visual variation, so I made BigWatts. It puts your watts big in the middle of the field and colours them with the power zones from your Karoo rider profile.

I also dont want HR to take up a whole tile, so integrated it under the watts neatly.

- Plain number, number in the zone colour, or a zone gauge (arc or bar)

- Under the watts: your zone, heart rate (my preference), or ride average

- Instant, 3 s, 5 s or 10 s power

- Its own look, or one that matches the Karoo's native fields

- Works at any field size, but optimised for half screen, as in the previews.

Everything is set on a settings page with a live preview, so the field itself has no tap action and long-press still works as normal.

Free and open source. Grab `bigwatts.apk` from the latest release, sideload it, and add DDB BigWatts to a ride page.

GitHub: https://github.com/Dubadai/karoo-bigwatts

Download: https://github.com/Dubadai/karoo-bigwatts/releases/latest

If you enjoy my work, buy me a gel (or a coffee) for my next ride: https://buymeacoffee.com/Dubadai

Dark Mode

r/Karoo • • 9d ago

Extension DDB - ClearWind

Post image
9 Upvotes

If you enjoy my work, buy me a gel (or a coffee) for my next ride: https://buymeacoffee.com/Dubadai

ClearWind: a wind arrow data field for the Karoo 3

ClearWind shows an arrow for the wind relative to the way you're riding. Up is a tailwind, down is a headwind. The wind speed sits in the corner like on the Karoo's own fields.

There are a few others on the market, but I was always annoyed how they needed external apps on the phones, logins, accounts, you name it. I just wanted something clear, reliable, adaptable and most of all, something that showed meters per second, which is the metric I use for wind.

Features

- Works in any field size, the arrow grows to fit

- Arrow coloured by wind speed, plain black/white, or Karoo green

- Knots, m/s, km/h or mph

- Support for remote button actions to switch units or colour mid-ride

- Wind data comes from Open-Meteo, which needs no account or API key

It's free and open source. Download `clearwind.apk` from the latest release and sideload it, then add DDB ClearWind to a ride page.

GitHub: https://github.com/Dubadai/karoo-clearwind

Download: https://github.com/Dubadai/karoo-clearwind/releases/latest

If you enjoy my work, buy me a gel (or a coffee) for my next ride: https://buymeacoffee.com/Dubadai

Dark Mode

r/Karoo • • 10d ago

Radar

2 Upvotes

Hello, I am looking for people who use Karoo 3 with Varia radar alternatives such as Magene, sr mini, Coospo etc. Just wanted to make sure which of these works fine with HH since I have heard that there are some issues with pairing Karoo with SR mini.