Android head unit - Bluetooth pairing and multi-phone switching
Yes, you can keep two or three phones paired to one Android head unit and let it reconnect on its own - within limits. Most retrofit builds keep a list of the phones you pair to them and come back to the one that connected last. What they won't do is decide for you which phone should win. Pick the order, split the two audio roles, and the switching stops being a daily argument.
Your unit doesn't hold one phone in its head. It holds a list, and so does each handset that paired with it. On the head unit that list sits inside the Bluetooth menu - you reach it through Settings, then Bluetooth, and the row is labelled Paired devices, Saved devices or Bonded phones depending on the build. On your phone, the matching entry hides under Connected devices, behind the little gear icon next to the car's name.
Both ends stay bonded until you unpair on that side. Google's own Android help page for Bluetooth accessories says it plainly: your devices stay paired until you unpair them, and after the first pairing they can connect automatically. A car kit behaves the same way, and that one sentence is the whole mechanism behind automatic switching.
Start by counting rows, because a stale bond is the usual suspect when a phone won't come back. Four saved phones and a two-phone household means two of them are ghosts - an old handset, a rental, somebody's test phone from the shop. Your unit doesn't know nobody carries them any more, so it keeps knocking, and your phone queues behind a door that isn't going to open.
Here's what catches people out. Forgetting the car on your phone doesn't clear the unit's copy, and clearing the unit doesn't touch your phone. Do both, or you'll keep one live pairing and one dead row pointing at the same handset - which is why the same mobile sometimes shows up twice with slightly different names. So which end do you clean up first? Compare the two lists, then start with the unit. It's the end doing the connecting.
Automatic gets used for two different things, and the sales copy cheerfully mixes them. The first is auto-reconnect: the unit remembers a phone and links back to it when you start the car. The second is role switching: call audio going to one handset while music plays from another. The first is normal on anything with a modern Bluetooth stack. The second is a chip and firmware feature, and you can't read it off a product photo.
How many phones can be live at once, then? That's where it goes build-specific. Calls and music travel on separate Bluetooth profiles - HFP carries the call, A2DP carries the audio stream, AVRCP carries the play and pause commands, and PBAP pulls the phonebook across - so a unit can in principle talk to two handsets on different profiles at the same time. Whether yours does is a firmware question, not a standard one.
| What you want | What makes it work | Where it breaks |
|---|---|---|
| Car starts, my phone connects itself | The phone is still in the unit's saved list and both ends are bonded | Another handset is physically nearer the car when it wakes up |
| Calls to my phone, music from my partner's | Two links held at once on different profiles (HFP plus A2DP) | Single-link modules hold one phone and nothing else |
| The unit leaves the other phone alone | No auto-connect on that entry, or the entry removed from the unit | Wireless projection launches on its own and takes the display |
| Correct contact names on an incoming call | Phonebook syncs from the phone you actually want | The unit shows whoever synced most recently, not who's calling |
Each row is a separate condition. Clearing one of them tells you nothing about the other three.
One condition is worth knowing before you plan anything else. Wireless Android Auto is not a Bluetooth feature. Google's Get started with Android Auto page asks for a compatible phone with an active data plan and 5 GHz Wi-Fi support, and it puts wireless projection at Android 11.0 and above, plus a compatible car or stereo. So the Bluetooth pairing you did gets you calls and music - not projection. Where does that confusion start? In a menu that lists a Bluetooth row and a projection row side by side, as if they were alternatives.
The order you pair in matters more than any switch in the menu, and it costs nothing to get right. What you're doing is giving the unit a first choice.
On both sides. In the unit's Bluetooth menu, forget the phones that no longer belong to the car. On each handset, forget the car. Do this parked, and note the unit's Bluetooth name first - you'll be hunting for it in a list of a dozen nearby devices.
The phone that should own calls goes first. Let it connect, then switch the unit off and on once so the link is written down properly. Don't touch anything else until a call works.
Now add the second handset. If your build allows it, open its entry under Connected devices and turn off Phone calls, leaving Media audio on. That's the profile split, and it stops the two of them fighting over the call channel.
Then verify it the way the car will be used. Park, switch off, put both phones where they normally live, and watch which one lands when you start up - then do it twice, because a first connection sometimes goes to whichever phone answered the scan first. If the wrong phone wins twice, redo step two rather than hunting through hidden menus.
I'd spend ten minutes on that order rather than buy an adapter I don't need. Pairing order is free and reversible; a new Bluetooth module isn't.
The common mistake is deciding the unit is locked to one phone, or broken, and reaching for a factory reset. Most of the time your unit is doing exactly what it was told - and the instruction came from a phone.
The usual next suspect is a handset that launches projection by itself. In a mixed household, wireless CarPlay is the one to check first. Apple's own setup steps have you press and hold the voice command button on the steering wheel, put the vehicle into wireless or Bluetooth pairing mode, and then choose the car under Settings, General, CarPlay, Available Cars. Once it's saved, that iPhone reconnects whenever it comes into range - exactly the behaviour you don't want from the phone that isn't driving today. Confirm which handset made that choice before you blame the hardware.
Two more, and both are cheap to rule out. First, the driveway problem: a phone left on the hall table can still sit inside the unit's range, and a car that wakes up and finds it first will hand it the link. Second, an update can leave the saved list carrying two rows for the same handset, so the unit tries both and your phone queues behind its own ghost.
If contact names look wrong, that's PBAP rather than Bluetooth playing up. Phonebook sync belongs to whichever phone connected most recently, so the screen can show last week's caller names while today's handset streams the music. Re-pairing in the right order sorts it.
Work down this list, cheapest first.
This is where the honest answer lives, and it's worth hearing before you spend money. Some modules hold one phone, full stop. If you need two handsets live at once - one for work calls, one for the family's music - find that out from the specification rather than the product picture, because a photo has yet to tell anybody anything useful about a Bluetooth module. On our product pages the Bluetooth line is where to look, and multi-device or multipoint support, where it exists, is listed there rather than in a slogan. What actually breaks in the end is rarely the radio. It's the assumption that the next unit behaves like this one.
And here's what I wouldn't do: swap out a unit that works fine apart from this. Re-pairing in the right order and splitting the call and media roles settles the everyday complaint for most drivers, and neither of those costs you anything.
Two phones that refuse to share are usually a firmware question in disguise. If your Bluetooth page looks different from the one described here, that's useful to know about.
Ask our support deskHave the unit model, the build string, how the phones are paired and a photo of the Bluetooth page ready, and the answer will match your software.
Zhuhai WITSON Industrial Co., Ltd. - Tel: +86-756-8120312, 8120211, 8120212.
No. Add the new one and leave the existing pairings alone. Your unit keeps every row it already holds; the only thing that changes is which handset connected most recently.
Realistically, no. Call audio runs over HFP, and a car kit holds one live call channel at a time, so the second handset is either waiting or parked on media only. That's why splitting the roles is the practical answer: one phone owns the call channel, the other takes the music. It also avoids the annoying version, where a call lands on the phone that isn't in the cabin and the unit hands it to the speaker anyway.
Paired and connected are two different states, and the phone's own list is the half people forget. Forget the car on that handset and pair it again from the unit's side - and check the saved list for a duplicate row for the same phone, because a ghost entry keeps winning the race.
One at a time. Projection is a single session, and starting it from the second phone ends the first one. Bluetooth pairing for calls and music is a separate matter and can stay on both.
Because your unit doesn't know about pockets. It connects to whichever bonded handset answers first, and the one you just walked past the car with is often quicker off the mark. If that bothers you, removing the auto-connect entry for the phone that shouldn't win is a two-minute job in the Bluetooth menu.
