Menu

Two Phones, One Dongle, One Car: Building a Phone Switcher for Android Auto (and Knowing When to Stop Reverse Engineering)
📰

Two Phones, One Dongle, One Car: Building a Phone Switcher for Android Auto (and Knowing When to Stop Reverse Engineering)

DEV Community: android·Duvan Jamid Vargas·1 day ago
#WftSCZXd
#devtoandroid#devto#dev#dongle#phone
Reading 0:00
15s threshold

It started with a small question: what can we improve on our wireless Android Auto dongle?

Two people, one car, one Carlinkit CPC200-2Air dongle (5.0 / U2AC, AutoKit firmware), and every time we swapped phones it was a manual, slightly miserable dance: turn Bluetooth off on one phone, wait, hope the other one connects first. A lot of poking later we had a full Android app with its own screen inside Android Auto , a BLE presence protocol between phones, a live dongle monitor, a CI pipeline that ships signed releases, and a pile of research notes about what the dongle does inside, including the exact point where we decided to stop.

This is the whole story, dead ends included. The code is MIT-licensed and public: muvatec/switch-phone-aa .

Disclaimer. This is an independent project, not affiliated with Carlinkit, HeWei, Google or Android Auto. It uses the web API the dongle itself exposes for its own settings page, and it contains no manufacturer binaries or code.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.