Audio & callsReviewed
Call Delay and Bluetooth Music Quality: What's Normal
A 1–2 second call delay through an AI box is normal; echo for the caller is not. Take calls on the head unit's Bluetooth. Carlinkit TBox, Ottocast Nano.
Carlinkit TBox (V3 / CPC-200 / S450)Carlinkit TBox AmbientCarlinkit TBox UltraCarlinkit TBox Ultra 2Carlinkit TBox Ultra 3Ottocast OttoAibox Nano
Quick answer
Pair your phone with the car's own Bluetooth instead of the box, so calls skip the box altogether; that removed the echo for both owners who reported it, and calls through the head unit have none of the box's delay. A delay of 1–2 seconds on calls routed through the box is normal and cannot be tuned away, and music through the box will not match the phone's own CarPlay.
Symptoms
- The other person's voice arrives a second or two late, so you talk over each other
- The caller hears an echo of their own voice, while you hear them fine
- The echo appeared after you switched the box to Android Auto
- Music through the box sounds flatter than from your phone's own CarPlay or Bluetooth
Applies to
- Devices
- Carlinkit TBox (V3 / CPC-200 / S450)
- Carlinkit TBox Ambient
- Carlinkit TBox Ultra
- Carlinkit TBox Ultra 2
- Carlinkit TBox Ultra 3
- Ottocast OttoAibox Nano
- Connection to the car
- CarPlay and Android Auto
- Highest risk on this page
- Advanced
- Status
- Workaround confirmed by the community
Why it happens
A call through the box takes a long road. The caller’s voice travels from your phone to the box over Bluetooth, through the box’s Android audio system, and over the CarPlay or Android Auto cable to the head unit. Your voice goes back the same way from the car’s microphone. Each step buffers a little audio, and the community FAQ for Carlinkit boxes says the resulting 1–2 seconds is normal and cannot be removed.
Echo is the side effect. The caller’s voice comes out of your speakers, the car’s microphone picks some of it up, and it goes back to them a second or two late. Phones and head units cancel that echo; one TBox Ultra 2 owner who examined the firmware reported that echo cancellation is switched off in it. Owners also noticed echo getting worse in poor mobile coverage, and in Android Auto mode compared with CarPlay.
Music quality has a similar cause. Everything you play is mixed and resampled by the box’s Android system before it reaches the head unit, so it will not match a phone playing straight into the car. 44.1 kHz in code 166888 covers the one audio switch the box offers and where it helps.
Fixes, ranked
Take calls on the head unit's own Bluetooth
- Low risk
- Time: 15 minutes
- Worked for 2 of 2 reports
- On your phone, forget the box’s Bluetooth pairing.
- Pair the phone with the car’s own Bluetooth, as you would without the box.
- Leave the box connected for navigation and music.
- Make a test call and ask whether the other person hears an echo.
A TBox Ultra owner’s callers heard their own voice; the echo went away once the phone was paired only with the head unit and no longer with the box. The owner’s explanation was that three microphones (car, box path and phone) were involved during a call. Calls on the head unit’s own Bluetooth also skip the box’s audio path, so they do not carry its delay.
A second owner was told to put the box in Android Auto mode and pair the phone straight to the head unit, and the echo was gone. Pairing did not work at first: with the box connected, the head unit refused the phone with a wrong-password error and offered to forget the device. After he restarted the phone it paired. If you see that error, restart the phone, or pair the phone first and connect the box afterwards.
Many head units turn their own Bluetooth off while the box is connected in CarPlay mode. In that case, route calls through the head unit explains the Android Auto variant, including turning off media audio on that link.
Echo only in Android Auto mode: switch the box to CarPlay
- Low risk
- Time: 5 minutes
- Worked for 2 of 2 reports
- Switch the box to CarPlay with the pin-hole button (press for up to 2 seconds).
- Restart the box and make a test call.
A TBox Ultra owner had echo on calls in Android Auto mode, and the box also read speed-camera warnings into the call, so the caller heard them. Back in CarPlay mode both problems were gone. An owner of an original Carlinkit TBox (CPC200, 4 GB + 64 GB) had set it to Android Auto because he uses an Android phone; his callers heard an echo until he switched the box to CarPlay, and then calls worked both ways. Two more owners described the same pattern, clean in CarPlay and echo in Android Auto, without saying what they did next. See switching between CarPlay and Android Auto for the methods.
iPhone on a TBox Ambient: make calls through AutoKit
- Low risk
- Time: 15 minutes
- Worked for 1 of 1 report
- With the box in CarPlay mode, connect the iPhone to the box through the AutoKit app (CarPlay from the phone into the box).
- In the box’s hands-free settings, choose AutoKit as the app for calls.
- Answer with the steering-wheel button and test a call.
A TBox Ambient owner who found the box’s own Bluetooth dialer unusable because of echo set it up this way. The phone’s CarPlay screen then appears inside the box, calls go through it, and the phone can stay on a wireless charger. The owner had not tried the Android Auto equivalent.
Ottocast Nano: turn off A2DP in the engineering menu
- Advanced
- Time: 10 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.
- Open the box’s engineering (factory) menu. Ottocast support can tell you the access path for your firmware.
- Turn off A2DP (Bluetooth media audio from the phone).
- Restart the box and make a test call.
An Ottocast Nano owner whose callers heard an echo turned off A2DP after another owner suggested it, and reported louder call audio with no echo. The trade-off is that music from your phone can no longer play to the box over Bluetooth; apps on the box are unaffected. Ottocast support had earlier suggested a different sound setting that did not help.
Things to try (unverified)
- Turn off assistant wake phrases. A TBox Ambient owner said echo and poor audibility on Bluetooth calls mostly go away with assistants off, but that echo still appears where mobile signal is weak. See microphone not working on calls.
- TBox Ultra 2 Sound settings. The 21 July 2026 Ultra 2 build added a Sound settings page with Noise suppression (0–8) and audio/video sync (0–20). The owner who tried noise suppression during a call heard no change, and there is no Save button, so it is unclear whether the value sticks.
- A delay of 3 seconds or more. One owner (box model not stated) had about 3 seconds of delay on Bluetooth calls and on calls from the box’s own SIM. That is longer than the FAQ’s normal range; nobody found the cause.
- For music: play from apps on the box. If you stream from your phone to the box over Bluetooth, the audio is compressed twice. A TBox Ultra owner found the iPhone’s own CarPlay and Bluetooth ALAC sounded far better than the box. Nobody has reported a setting that closes that gap.
If nothing works
Write down the box model and firmware date (Settings → About), your phone, the protocol, the car and head unit, and how you route calls (phone to box, phone to head unit, or the box’s SIM). Ask the person you called to describe the delay or echo, and record a short clip from your side.
Send that to the seller or to the manufacturer (Carlinkit: [email protected]; Ottocast: [email protected]). If calls through the box stay poor in your car, keeping the phone on the car’s own Bluetooth is the practical answer, and start here explains how the box families differ if call quality is a deciding factor.
What owners said
“The echo went away when I removed the Bluetooth link between the phone and the Ultra and kept the phone paired over Bluetooth only with the head unit.”
Owner, Aug 2026
“Yes, it made a difference: after turning off A2DP on the Nano through the engineering menu, call sound from the phone got better, with no echo and louder. I checked today.”
Owner, Ottocast OttoAibox Nano, Oct 2025
“Since I have a Pixel 7, I had originally set the Carlinkit to Android Auto mode, but I switched it to CarPlay mode, and now phone calls work perfectly in both directions!”
Owner, Carlinkit TBox (V3 / CPC-200 / S450), Apr 2025
Quotes are translated where needed and shortened ([…]); names are removed. Full counts are in the evidence table below.
Questions owners ask
Is a 1–2 second delay on calls a fault?
No. The community FAQ for Carlinkit boxes calls it normal and not fixable, because call audio passes from the phone over Bluetooth into the box and then over the cable to the head unit. A delay of 3 seconds or more, or an echo, is worth working on.
Why does the caller hear their own voice?
Their voice comes out of your car speakers, reaches the car's microphone and goes back to them, delayed by the box. Owners found this worse in Android Auto mode and with poor mobile signal.
Will a better Bluetooth codec fix music quality?
Not on its own. One owner compared a phone and a TBox Ambient over Bluetooth to the same head unit with the same codec and the box still sounded clearly worse.
Related fixes
- Can't Hear the Caller on Incoming Calls Through the AI BoxAdvanced
- Microphone Not Working on Calls? Clear Every Bluetooth PairingAdvanced
- AI Box Sound Quality: When 44.1 kHz (Code 166888) Helps or HurtsAdvanced
- Make Calls With the SIM Card Inside the AI BoxAdvanced
- All Audio on the AI Box Plays Sped Up: Try a Factory ResetLow risk
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 6 community reports on Carlinkit TBox Ambient, Ottocast OttoAibox Nano, Carlinkit TBox (V3 / CPC-200 / S450).
- 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-0030 | Model not stated | Recommended in the FAQ (not counted) | Community FAQ, 1 message |
| case-0031 | Model not stated | 0 worked | Owner discussion threads, 1 message |
| case-3050 | Model not stated | 1 worked | Owner discussion threads, 2 messages |
| case-3051 | Model not stated | 1 worked | Owner discussion threads, 4 messages |
| case-3052 | Ottocast OttoAibox Nano | 1 worked | Owner discussion threads, 4 messages |
| case-3053 | Carlinkit TBox Ambient | 1 worked | Owner discussion threads, 1 message |
| case-3054 | Model not stated | 0 worked | Owner discussion threads, 4 messages |
| case-9320 | Carlinkit TBox (V3 / CPC-200 / S450) | 1 worked | Owner discussion threads, 3 messages |
| case-9321 | Model not stated | 1 worked | Owner discussion threads, 4 messages |