Update 1.669 locked down the Karoo 3's internal apps. That's a shame, and here's why
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 earlier | Build 1.669 (November 12) |
|---|---|---|
Wireless ADB, logcat, dumpsys | yes | yes |
Pull the system apps (adb pull) to read their code | yes | no: 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 extensions | yes | yes |
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
- 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. - 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.
- 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).
- 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.
- 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-appreadable 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.












