Skip to content
AI Box Fix

Audio & callsReviewed

Noise After Switching the Box to Android Auto: Factory Reset

Stutter, crackle or thin sound after moving your AI box from CarPlay to Android Auto? Factory reset the box. Carlinkit TBox Ambient, Plus, UHD and Ultra.

Quick answer

Factory reset the box after you switch it from CarPlay to Android Auto, then set it up again in Android Auto mode. That cleared the stutter, crackle or thin sound in five of the six owner reports, and the community FAQ recommends it; if you do not need Android Auto, switching back to CarPlay brought clean sound back for two owners.

Symptoms

  • Music stutters, crackles or skips in Android Auto mode, while it was clean in CarPlay mode
  • Sound turns thin, quiet or loses its bass right after you switch protocol
  • The sound breaks only after you switched to CarPlay and back
  • Sometimes the box starts very quiet, and the volume control shows Navigation instead of Media

Applies to

Connection to the car
CarPlay and Android Auto
Head units mentioned in reports
Haval / GWM GWM head units; Tank / GWM Tank head units
Highest risk on this page
Advanced
Status
Workaround confirmed by the community

Why it happens

Carlinkit boxes ship in CarPlay mode. When you switch to Android Auto, the box keeps audio settings and app state that were made for the CarPlay connection. Some of those no longer match the new audio path, and the result is stutter, crackle or a thin, quiet sound. A factory reset rebuilds them for the protocol the box is now in.

It does not happen to everyone. One owner switches between protocols regularly and hears no difference; others got stutter on two different boxes after the same switch. The community FAQ and the moderators advise a reset whenever sound changes after a switch, and the reports below show why.

To change protocol, press the pin-hole button on the box for no more than 2 seconds, or on newer TBox Ambient firmware use Factory settings → 4545 → Other. Switching between CarPlay and Android Auto covers both methods.

Fixes, ranked

Factory reset the box after switching to Android Auto

  • Safe
  • Time: 30–60 minutes including setup
  • Worked for 5 of 6 reports
  • Recommended in the community FAQ
  1. Write down your apps, logins and launcher layout. A reset erases them.
  2. Check that the box is already in Android Auto mode. The protocol survives the reset.
  3. Open Settings → System → Reset options → Erase all data (factory reset).
  4. Set the box up again, install your music app first and test playback before adding anything else.
  5. Turn off assistant wake phrases as you reinstall (see crackling or muffled sound).

An owner whose music crackled in Android Auto but was clean in CarPlay, even with the 44.1 kHz switch on, reset and reinstalled everything and the crackle was gone. Another owner had quiet sound with missing bass after moving to Android Auto, tried everything else, and only the reset fixed it. A Haval F7 owner switched to Android Auto, did a full reset, and lost both the lag and the distortion.

One owner who moved a TBox Ambient and later a TBox Ultra to Android Auto saw music stutter on both; restarts and reinstalling the music app did nothing, and only a reset helped. Another said stutter after a protocol change always cleared with a reset.

The one report that did not end well: a TBox Ambient owner in a Tank 500 reset right after switching, and still gets random starts where the sound is very quiet and the volume control shows Navigation instead of Media. A restart clears it each time. Several owners have the same quiet-start problem, and nobody has found the cause.

If you do not need Android Auto, switch back to CarPlay

  • Safe
  • Time: 5 minutes
  • Worked for 2 of 2 reports
  1. Press the pin-hole button on the box for up to 2 seconds.
  2. Let the box restart in CarPlay mode.
  3. Play the same music and listen for a full drive.

On newer TBox Ambient firmware the protocol switch also sits in the engineering menu (code 4545); that route is an advanced change, so use the button if your box has one.

A Tank owner got stutter on Android Auto, switched back to CarPlay and the sound was normal again, with the 44.1 kHz switch still on. A TBox Ambient owner heard interference on Android Auto and clean sound again after switching back. Weigh what you lose: some head units only allow your phone on the car’s Bluetooth in Android Auto mode, and some cars start the box more reliably in Android Auto.

Restart the box after every protocol switch

  • Safe
  • Time: 2 minutes
  • Worked for 1 of 1 report
  1. After switching protocol, restart the box from its power menu, or unplug it for 10 seconds.
  2. Wait for the launcher to load completely, then play music.

A TBox Ultra owner who switched from CarPlay to Android Auto and back lost all sound. The restart that followed a settings change brought it back, and the owner concluded the restart was what helped. Try this before a reset; it costs nothing.

Set the box's media volume one or two steps below maximum

  • Safe
  • Time: 2 minutes
  • Worked for 1 of 1 report
  1. On the box, open Settings → Sound (on some boxes Settings → More → Sound).
  2. Lower the media volume one or two steps from maximum, about 75–85%.
  3. Turn up the volume on the car’s knob instead.

An owner whose music crackled in Android Auto mode replied that lowering the box’s overall volume helped them, and that it worked even per app. Digital audio at full scale can clip in some head units, so this is worth trying alongside the reset.

Turn the 44.1 kHz switch off in CarPlay mode, then return to Android Auto

  • Advanced
  • Time: 15 minutes
  • Worked for 1 of 2 reports

Warranty warning: this uses developer or engineering access. Follow the undo steps afterwards; some sellers refuse warranty claims on units with debugging left enabled.

  1. Switch the box to CarPlay and restart it.
  2. Open Settings → Other → Factory settings, enter 166888, turn Force 44K audio off and tap Save. The box reboots.
  3. Switch the box back to Android Auto and restart it again.
  4. Test the sound. Turn the 44K switch back on only if you had it on and want to compare.

An owner who hit stutter after a brief switch to CarPlay found this sequence by experiment and recommended it to avoid a full reset. The TBox Ambient owner who tried it next still had stutter and went on to a reset; the advice afterwards was to restart after every single step. 44.1 kHz in code 166888 explains why that switch causes trouble on some boxes.

Things to try (unverified)

  • Remove assistant apps you do not use. One owner with the quiet-start problem removed a forgotten voice-assistant app and the box seemed to start at normal volume afterwards; they were not sure it was the cause.
  • Clear the music app’s cache before resetting. Suggested several times as a lighter step; nobody reported that it alone fixed post-switch stutter, and one owner said reinstalling the app did not.
  • Equaliser preamp. One owner lowered the preamp by 2.5 dB in an equaliser app to stop crackle, but in CarPlay mode, so it is not clear it helps after a protocol switch.
  • Ottocast Picasou 3 Pro. An owner found music very quiet after switching to Android Auto. Ottocast boxes use different firmware, and no fix was reported.

If nothing works

Write down the box model and firmware date (Settings → About), the protocol you switched from and to, whether the 44.1 kHz switch is on, the car and head unit, and whether the sound was clean before the switch. Record a short clip of the stutter.

Send that to the seller or to Carlinkit at [email protected]. If the sound is clean only in CarPlay and you need Android Auto for your car, ask support whether a newer build fixes Android Auto audio on your model; start here if you are choosing between boxes.

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 report

Changelog

  • Last reviewed against new community reports:
  • Confirmed by 10 community reports on Carlinkit TBox Ambient.
  • 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.