Audio & callsReviewed
Keep the Phone on the Car's Bluetooth: 21 Owner Reports
Head unit drops your phone when the AI box connects? Switch the box to Android Auto and pair the phone first. Carlinkit TBox Ambient, UHD, Plus, Ultra.
Carlinkit TBox AmbientCarlinkit TBox UHDCarlinkit TBox PlusCarlinkit TBox UltraCarlinkit TBox Ultra 2Carlinkit TBox Ultra 3Carlinkit TBox Ultra 4Ottocast Picasou 2Ottocast Picasou 3
Quick answer
If your head unit drops the phone's Bluetooth when a Carlinkit TBox connects, switch the box to Android Auto mode and pair the phone with the car, not the box; six of nine owners kept calls on the head unit this way. If the phone still drops, pair it before plugging in the box (seven of nine).
Owner reports at a glance
- Owner reports of a fix that worked
- 21
- Reports with a result
- 28
- 21 worked, 7 did not help
- Most-confirmed fix
- Pair the phone first, then plug in the box: worked in 7 of 9 reports
- Boxes owners confirmed it on
- Carlinkit TBox Ambient, Carlinkit TBox UHD, Carlinkit TBox Ultra, Carlinkit TBox Ultra 3, Ottocast Picasou 2, Ottocast Picasou 3
One owner counts once per fix; reports with no result yet are not counted. Counts reviewed . How we count.
Before you start
- A head unit that offers wired Android Auto as well as CarPlay (check its connection menu or manual)
- Access to your phone's Bluetooth settings and the head unit's phone or Bluetooth menu
- A paper clip for the box's recessed mode button
- The car parked with the engine running for about half an hour
Time: about 30 minutes. Tools: paper clip.
Applies to
- Devices
- Connection to the car
- Android Auto
- Head units mentioned in reports
- Haval / GWM GWM head units; Chery / Exeed Chery and Exeed head units; Omoda / Jaecoo Omoda / Jaecoo head units; Volkswagen MIB 2.5; Škoda Columbus (MIB3); Changan Changan head units; Audi MMI; Various Generic Android head units; Toyota Entune / Toyota Audio Multimedia
- Firmware in confirmed reports
- Carlinkit TBox Ambient: 2024-04-25
- Highest risk on this page
- Advanced
Why your head unit drops the phone
Your head unit has one hands-free system. When a device connects over wired CarPlay, CarPlay itself carries calls, and many head units then switch their own Bluetooth phone link off or refuse a new one. The AI box presents itself to the car as a CarPlay phone, so the head unit treats it exactly like that. Owners see a message such as “CarPlay will stop working” when they try to pair the phone, or the phone drops silently the moment the box finishes booting.
In Android Auto mode a lot of the same head units behave differently: they let the box stream its screen over the cable and keep a separate Bluetooth phone pairing for calls. That is the setup this guide builds. Calls then go straight from your phone to the car, with the car’s own call screen, and skip the box’s audio path, which removes the box’s call delay and the echo described in call delay and echo.
Whether it works is decided by the car, not by the box. Owners report it working in Android Auto mode on a Haval Dargo and a Haval F7, a Chery Tiggo 7 Pro Max, a VW Tiguan with MIB 2.5 and a Skoda Kodiaq with MIB3 (the Kodiaq even in CarPlay mode). It needed the pairing order in Step 2 on an Omoda C5 and a 2025 Haval H7. It did not work at all for owners of a Changan Uni-T, a 2019 VW Teramont and an Audi Q7 with MIB3, and one Haval owner found that his wife’s Jolion refuses the phone in both modes.
What changes when the box runs in Android Auto
Read this before you switch. Owners who keep the phone on the head unit accept these trade-offs:
- No car GPS for the box. On Carlinkit boxes the car’s own GPS receiver is used only in CarPlay mode, so navigation on the box falls back to the box’s own location. See inaccurate GPS if that matters where you drive.
- Calls move to the car’s own phone screen. The Haval F7 owner noticed he now has to open the head unit’s menu to see who is calling. Two other owners, one with a Haval F7, saw no caller name over the box, and one of them could answer only from the phone. If your wheel buttons stop answering calls, see steering-wheel call buttons.
- Less information on the dashboard. Owners of a Haval Dargo and a Chery Tiggo 7 Pro Max lost song titles or cover art on the instrument cluster in Android Auto mode.
- The box may not open by itself. On some cars you tap the Android Auto tile once after every start. A VW Tiguan owner also found the box took much longer to connect in Android Auto, and went back to CarPlay because of it.
- Sound after the switch. If music crackles after you change protocol, the fix owners used is a factory reset; see noise after switching to Android Auto.
If you are not sure which box you have, which TBox do I have explains how to tell. The steps below apply to the TBox Plus, Ambient, UHD and Ultra; owners’ reports came from all four.
Steps
Switch the box to Android Auto, then pair the phone with the car
- Low risk
- Time: 15 minutes
- Worked for 6 of 9 reports
- With the car on and the box fully booted, press the recessed mode button next to the box’s LED with a paper clip for 2–3 seconds, then release. The box restarts in the other protocol. Never hold it for 10 seconds or more.
- On the head unit, open the Android Auto tile and check that the box’s home screen appears.
- On your phone, open Settings → Bluetooth and forget the box (it may be listed as TBox, AutoKit or the box’s model name).
- On the box, open Settings → Bluetooth and forget your phone.
- Pair the phone with the car’s own Bluetooth from the head unit’s phone menu, as you would without the box.
- Ask someone to call you. The call should ring on the head unit’s own phone screen while the box keeps navigation and music.
The other ways to change protocol, including the menu option on 2025 and later firmware, are in switching between CarPlay and Android Auto.
Six owners reported this setup working. A TBox Ambient owner on the 25 Apr 2024 firmware in a Haval F7, whose callers had heard themselves loudly, moved the phone to the head unit and the echo was gone. A Haval Dargo owner’s head unit answered “CarPlay” and refused the phone until he switched the box to Android Auto. A VW owner fixed it with the same change, and an owner who set up a TBox UHD in a friend’s Chery Tiggo 7 Pro Max confirmed the phone stays on the head unit in Android Auto mode. A TBox Ambient owner with a Tiguan on MIB 2.5 could pair directly in Android Auto, and a TBox Ultra owner summed it up: CarPlay switches the head unit’s Bluetooth off, Android Auto works.
Three owners switched and still could not keep the phone. A Changan Uni-T with a TBox Plus kept warning that CarPlay would stop, a 2019 VW Teramont cut the connection in Android Auto too, and on an Audi Q7 with MIB3 the TBox Plus would not connect in Android Auto at all. If the phone pairs but drops again a few seconds later, go on to Step 2 before giving up.
Pair the phone first, then plug in the box
- Low risk
- Time: 15 minutes
- Worked for 7 of 9 reports
- Unplug the box from the car’s USB port.
- On the phone, forget the car and the box. In the head unit’s phone menu, delete your phone.
- If your phone has wireless Android Auto, turn it off in the phone’s Android Auto settings. Otherwise the phone tries to take over the car’s screen itself.
- Pair the phone with the head unit as a plain hands-free device, and wait until the head unit shows it connected.
- Plug the box in and let it boot fully, until its LED is steady.
- If the head unit or the phone asks whether to switch the phone’s connection, decline. The phone stays on Bluetooth only.
- Make a test call. If the first call still rings through the box, choose the car as the audio device on the phone’s call screen; the phone usually remembers.
- On later drives, keep the order: let the phone connect to the head unit first, then let the box start.
The order matters on head units where the first device to claim the connection wins. An Omoda C5 owner with a TBox Ambient had first found the head unit told him to turn Android Auto off when he tried to pair. After he unplugged the box, deleted the pairings, turned off wireless Android Auto on the phone, paired the phone and only then plugged the box back in, calls ran without problems for the two weeks he reported on; before that, the box had sometimes rebooted after a call.
A Haval H7 (2025) owner with a TBox Ultra 1 and a Samsung phone wrote up the same idea: pair the phone with the head unit while the box is unplugged, plug in the box, wait for it to boot, turn the phone on and reject the request to change its connection. Every day after that he opens the driver’s door, waits for the box’s LED to go steady, starts the car and rejects the prompt. The wheel’s phone buttons work and calls go through the head unit. The owner who passed that write-up on said it did not work in his own car.
On VW and Skoda MIB2 and MIB 2.5 units the order has two more moves: phone to head unit, plug in the box, pair the phone with the box as well, then restart. A VW MIB2 owner with a TBox Ultra described that last move twice, once as restarting the head unit and once as restarting the box; either way his phone ends up on the head unit for calls.
Two MIB 2.5 owners restart the head unit. A Columbus MIB 2.5 owner, who had spent a year on coding changes and head-unit firmware without result, holds the head unit’s power button until it restarts by force, and the phone then connects to the head unit. A 2018 Kodiaq owner with a Bolero MIB 2.5 unit tried exactly that and reported calls through the head unit with the box in Android Auto. He left calls and contacts enabled on the phone’s link to the car and only contacts on its link to the box, and was still watching it; a reply in the same discussion calls the workaround not fully stable on a Bolero. So if restarting the box does not bring the phone back on MIB2 or MIB 2.5, force-restart the head unit.
A Skoda Kodiaq owner with MIB3 found the phone connects as long as it starts connecting before the box has booted. An iPhone owner saw the same pattern: start the head unit without the box and the iPhone connects, start it with the box plugged in and it does not.
One TBox Ultra owner lost a working setup after switching the box to CarPlay and back, and the order did not bring it back; see “Troubleshooting this guide” below.
Reconnect the phone automatically when the box boots first
- Low risk
- Time: 10 minutes
- Worked for 2 of 2 reports
- Open your phone’s automation app: Modes and Routines on Samsung phones, or an automation app such as MacroDroid on other Android phones.
- Create a routine with the trigger wireless charging starts.
- Add the condition not connected to the car’s Bluetooth, so it does not run on every charge.
- Add the action connect Bluetooth to your car’s head unit.
- Get in, start the car, put the phone on the wireless charger, and check that the head unit shows the phone.
This is for cars where the order in Step 2 works but the box often wins the race: remote start, or the box booting before you are in the car. One owner explained, in a thread about a Haval Jolion, that once the box is connected the head unit stops searching for the phone, so the phone has to start the reconnection. He set up the routine above for himself and said it works perfectly; the Jolion owner who asked set up the same routine on his Samsung and reported everything connected.
A trigger on “car detected” does not work for this, because the head unit is not advertising itself at that point. The wireless charger works as a trigger because you use it on every drive. Owners mentioned iPhone automations too, but nobody reported a working iPhone version of this routine.
Android head units: keep only calls on the phone's link
- Advanced
- Time: 15 minutes
- Worked for 1 of 1 report
Warranty warning: this uses developer or engineering access. Follow the undo steps afterwards; some sellers refuse warranty claims on units with debugging left enabled.
- Photograph the head unit’s current Bluetooth settings for your phone, so you can restore them.
- Open the head unit’s engineering menu and go to its standard Android settings. The way in differs per car; this is the head unit’s menu, not the box’s.
- Open Bluetooth, tap the gear next to your paired phone, and untick every profile except phone calls and contact sharing. Media audio must be off.
- Reconnect the phone and make a test call with the box running in Android Auto.
A TBox Ultra 3 owner with an Android 11 head unit had the phone pair with the head unit in Android Auto mode and then disconnect after about ten seconds, over and over. Turning off every profile except calls and contacts stopped it. He suspected the media profile and could not say how long the fix would hold.
If your head unit has no engineering menu, the phone-side version is less invasive: in the phone’s Bluetooth settings for the car, turn off Media audio and leave Phone calls on. Can’t hear the caller describes it; it also stops music jumping between the box and the phone after a call.
If the car will not cooperate: pair the phone with the box only
- Low risk
- Time: 10 minutes
- Worked for 3 of 3 reports
- On the phone, open Settings → Bluetooth and forget the head unit. On the head unit, delete the phone.
- On the box, open Settings → Bluetooth and pair the phone with the box.
- Make a test call, and check that music on the box pauses for the call and comes back afterwards.
This is the reverse of the steps above, for cars where the phone on the head unit makes calls worse rather than better. Three owners reported calls working this way. A TBox Ambient owner with CarCar Launcher had the phone on the head unit: a call paused the box’s music, never resumed it, and showed no caller over the box, so he had to pick up the phone to see who was calling. Paired with the box only, he got a call window over the box’s screen and the music came back after the call.
A second owner could not pair his phone with the head unit at all while the box held it; with the box’s Bluetooth off, the head unit showed his contacts but would not place a call. Once he deleted the head unit pairing and paired only the box, calls worked and he reported good sound on both ends. On a Picasou 2 in CarPlay mode, whose car refused the phone while the box ran, pairing the phone with the box gave answer and hang-up, but the box showed no contacts and the wheel’s dial button did nothing.
Expect the box’s own call screen, which owners call basic, and the call delay described in call delay and echo. If you cannot hear the caller, can’t hear the caller sets this route up cleanly.
Verify it worked
Check four things on your next two or three drives, not only once in the driveway:
- The phone connects on its own. Start the car the way you normally do and look at the head unit’s phone screen before touching anything. If it connects only when you pair by hand, use the order in Step 2 or the routine in Step 3.
- Incoming and outgoing calls both work. Have someone call you, then call them back from the head unit or by voice. Ask whether they hear an echo.
- The box keeps running during the call. Navigation should stay on screen or come back after the call, and music should pause and resume.
- The phone is not paired with the box. Open Settings → Bluetooth on the box. If your phone appears there and connects, calls can land on the box instead of the car; forget it, unless you chose Step 5 on purpose.
Undo / rollback
To go back to calls through the box:
- On the head unit, delete your phone from its phone menu. On the phone, forget the car.
- Press the box’s mode button for 2–3 seconds to return it to CarPlay, if you changed protocol for this guide.
- Pair the phone with the box from the box’s Bluetooth settings.
- Delete the routine from Step 3 if you made one.
- If you changed Bluetooth profiles in the head unit’s engineering menu, restore them as in the undo steps of Step 4.
Calls through the box carry a delay of a second or two, which owners treat as normal; call delay and echo explains why.
Troubleshooting this guide
The head unit says CarPlay or Android Auto will be disconnected when you pair the phone. The head unit is refusing a parallel phone in that mode. Try the other protocol, then the order in Step 2. If both fail, your car does not allow it: pair the phone with the box (Step 5) and follow can’t hear the caller to set that up cleanly.
The box does not connect at all in Android Auto mode. Some head units reject the box in Android Auto even when they accept a phone. See car doesn’t detect the AI box and the protocol guide’s troubleshooting before going back to CarPlay.
It worked for months, then the phone started dropping when the box connects. Two owners hit this in Android Auto mode with nothing changed. A TBox Ambient owner on the March 2025 firmware got it back with a factory reset of the box, but it dropped again while he was reinstalling his apps. A TBox UHD owner in a Toyota tried the latest firmware, a factory reset and disconnecting the car battery, without success. Neither found the cause, so clear every pairing and redo Step 2 before resetting anything.
Music and video on the box keep pausing. On a Picasou 3 already in Android Auto mode, playback kept pausing with a pop-up window after a firmware update; the box itself had been paired with the head unit over Bluetooth. Removing that pairing seems to have fixed it, the owner reported. On a Picasou 3 in a Tenet T7, music paused when the indicator came on, in CarPlay mode only; switching the box to Android Auto cured it for that owner, though he finds call sound poor in that mode.
It stopped after you switched protocol and back. One TBox Ultra owner lost the parallel connection that way and could not restore it with the order, fresh pairings or clearing the head unit’s Android Auto app. He had not tried a factory reset of the box; another owner suggested it, since a reset after a protocol change is also what fixes bad sound.
VW, Skoda and Audi head units. Some MIB 2.5 and MIB3 units allow the parallel phone from the factory, others only after the second-phone option is enabled in the head unit’s coding. Owners had that done with a coding tool. It changes the car’s configuration, so leave it to a dealer or a coding specialist. One MIB 2.5 owner who enabled it that way has voice calls on the car but cannot play messages back through it.
Three more single reports come from MIB 2.5 owners and are not counted in the steps above. A 2019 Kodiaq owner with a Bolero unit and a TBox Ambient could not get the phone onto the car until he turned on Disable Bluetooth A2DP hardware offload in the box’s developer options, an advanced setting; his car has no official support for two devices. A 2017 Kodiaq owner with MIB 2.5 and a TBox Ambient in Android Auto, whose head unit refused the phone because one was already connected over Android Auto, reversed the order: delete every phone in the head unit, plug in the box, pair the phone with the box, and only then pair it with the head unit. He keeps both links, and notes that calls can be switched off on the phone’s link to the box. An Ottocast Nano owner reports that on its latest firmware, in Android Auto on MIB 2.5, the phone can be used directly through the head unit.
Ideas nobody has confirmed yet:
- Turn off “Phone calls” on the phone’s link to the box and leave it on for the car. Suggested to an owner who could not find the switch on an iPhone; a VW MIB2 owner who tried it on Android found the box then kept connecting and dropping. A 2018 Kodiaq owner with a Bolero MIB 2.5 unit does run this way, with only contacts on the box’s link, after the head-unit restart order in Step 2; it had held so far when he reported.
- Keep the box’s own Bluetooth switched off. A Skoda Kodiaq owner drives this way with the phone on the head unit. Another owner tried it in his car and the head unit showed his contacts but refused to place calls, so he went back to calls through the box.
- Add a start-up delay to the box, so the phone reaches the head unit first. One owner planned to try it; nobody reported back. The setting is in the factory settings, which are an advanced change; see the engineering codes reference.
If none of this works, write down the box model and firmware date (Settings → About), the car’s make, model, year and head unit, your phone, the protocol, and exactly what the head unit says when you pair. Send it to the seller or to Carlinkit at [email protected]. If your car blocks a second phone in every mode and calls through the box are not good enough, start here to compare boxes and setups.
If your head unit is an Android unit (TEYES and similar), its own Bluetooth and microphone settings come first: the TEYES hub lists what owners of those units fixed, counted separately from the AI box reports in this guide.
What owners said
“Found it by chance and tried it on my 2018 Kodiaq with the Bolero MIB 2.5. It works! Now I can make phone calls through the head unit and use the box in Android Auto.”
Owner, Sep 2026
“Thank you, kind person! It works. I deleted the head unit from Bluetooth connections, paired only the box, and now calls go through. The interface is awful, but it does the main job. Sound is good; everyone hears everyone.”
Owner, May 2025
“I unplugged the box, deleted the pairing on the head unit and the phone, turned off wireless AA on the phone, re-paired the head unit over Bluetooth, then plugged the box back in. Two weeks of driving, no problems.”
Owner, Mar 2025
Quotes are translated where needed and shortened ([…]); names are removed. Full counts are in the evidence table below.
Questions owners ask
Why does the head unit refuse my phone only while the box is in CarPlay mode?
CarPlay carries calls itself, so many head units switch their own hands-free Bluetooth off as soon as a wired CarPlay device is attached, and the box counts as one. In Android Auto mode a lot of the same head units keep a separate phone pairing. It depends on the car, not on the box.
What do I give up by running the box in Android Auto mode?
On Carlinkit boxes the car's own GPS receiver is used only in CarPlay mode. Owners also lost song titles on the instrument cluster, and on some cars the box's screen no longer opens by itself. Calls show in the head unit's own phone screen instead of over the box.
Does this work with an iPhone?
Yes. The protocol and the pairing order only concern the car's Bluetooth. One owner with an iPhone found it connects to the head unit whenever the head unit starts before the box. The automation in Step 3 was reported on Android phones only.
My car refuses the phone in both modes. What now?
Pair the phone with the box instead and take calls through it; three owners reported calls working that way (Step 5). Clean up old pairings first, as in the incoming-calls guide, and expect a delay of a second or two on calls.
Related fixes
- Can't Hear the Caller on Incoming Calls Through the AI BoxAdvanced
- Call Delay and Bluetooth Music Quality: What's NormalAdvanced
- Head Unit Shows Only CarPlay? Switch the Box's ProtocolAdvanced
- Phone Won't Pair With the Box: Bluetooth Connection ErrorLow risk
- Connect an OBD2 (ELM327) Adapter to Your AI BoxLow risk
- Picasou Sound Cuts Out Mid-Drive Until You RebootAdvanced
Did this work for you?
Tell us which fix worked (or didn't), with your box, firmware date and car. Reports are how fixes get confirmed and re-ranked.
Send a reportChangelog
- Last reviewed against new community reports:
- Confirmed by 21 community reports on Carlinkit TBox Ambient, Carlinkit TBox UHD, Carlinkit TBox Ultra, Carlinkit TBox Ultra 3, Ottocast Picasou 2, Ottocast Picasou 3.
- Page updated:
"Confirmed" means a community member reported that the fix worked on their unit. We have not tested it on our own hardware. How we verify.
Evidence behind these counts (9 cases)
One row per case: a device, a symptom and a fix, merged from owner reports. An owner counts once per fix. Reports with no outcome yet are not counted. Forum and chat message references are kept on file but not published, to protect owners' privacy; public Reddit and YouTube sources are linked.
| Case | Confirmed on | Result | Source |
|---|---|---|---|
| case-8010 | Carlinkit TBox Ambient (2024-04-25); Carlinkit TBox UHD | 6 worked, 3 did not | Owner discussion threads, 11 messages |
| case-8011 | Carlinkit TBox Ambient; Carlinkit TBox Ultra | 5 worked, 2 did not | Owner discussion threads, 11 messages |
| case-8012 | Model not stated | 2 worked | Owner discussion threads, 7 messages |
| case-8013 | Carlinkit TBox Ultra 3 | 1 worked | Owner discussion threads, 3 messages |
| case-8014 | Model not stated | 0 worked, 2 did not | Owner discussion threads, 6 messages |
| case-9360 | Carlinkit TBox Ambient; Ottocast Picasou 2 | 3 worked | Owner discussion threads, 9 messages |
| case-9361 | Ottocast Picasou 3 | 1 worked | Owner discussion threads, 3 messages |
| case-9362 | Ottocast Picasou 3 | 1 worked | Owner discussion threads, 1 message |
| case-1834 | Model not stated | 2 worked | Owner discussion threads, 3 messages |