Skip to content
AI Box Fix

Audio & callsReviewed

Mstick4 Hands-Free Calls: Pair Through the Car, Not the Stick

Calls on the MGears Mstick4 ring on the phone or have no sound in the car? Clear old pairings, keep the phone on the car, register the stick in MGears Go.

Illustration: MGears Mstick4 on a dashboard on a rainy evening

Quick answer

On the MGears Mstick4, calls with no sound in the car came back for all four owners who cleared the old Bluetooth pairings, kept the phone paired with the car and registered the stick in the MGears Go phone app. MGears recommends the app for Android: it stops the phone sending calls to the stick, which has no call audio.

Symptoms

  • An incoming call rings on the phone, and when you answer there is no sound in the car
  • The call shows on the stick's screen, but the audio goes to the phone's own speaker
  • The stick keeps saying hands-free is not connected and offers to reconnect
  • The car refuses the phone, or asks you to unplug Android Auto first, once the stick has started
  • You call a contact from the stick and the sound stays on the phone

Applies to

Connection to the car
Android Auto
Head units mentioned in reports
Chery / Exeed Chery and Exeed head units
Highest risk on this page
Low risk
Status
Workaround confirmed by the community

Why it happens

The MGears Mstick4 has no phone function of its own. Calls always travel from your phone to the car’s own hands-free over Bluetooth; the stick only shows who is calling and gives you a button to hang up. The trouble starts when the phone is also connected to the stick as a hands-free device. It then has two hands-free targets and can send the call to the stick, where there is no audio path, so you hear nothing or the call jumps back to the phone’s speaker.

MGears support explained it in those terms to one owner: the phone is connected to two Bluetooth hands-free devices. On Android, the MGears Go app switches off the hands-free profile between phone and stick once the stick is registered, so the phone keeps calls on the car. A second problem is timing: on some head units, whichever device claims the connection first wins, and if the stick starts before the phone has reached the car, the car refuses the phone.

Fixes, ranked

Clear old pairings and register the stick in MGears Go

  • Low risk
  • Time: 15 minutes
  • Worked for 4 of 4 reports
  1. On the phone, open Bluetooth settings and forget the Mstick4.
  2. On the stick, remove the phone from its Bluetooth hands-free settings.
  3. In the MGears Go app on the phone, delete the registered stick if one is listed.
  4. Check that the phone is paired with the car’s own Bluetooth, and pair it if not.
  5. Accept the pairing request the stick sends, and register the stick again in MGears Go.
  6. Make a test call. The sound should come through the car while the caller’s name shows on the stick.

Four owners got calls working this way. One installed the phone app, which reported his hands-free setup as wrong; he unpaired everything, paired again through the app, and calls worked over the car’s Bluetooth. An Android owner whose call audio went to the stick and was silent registered in the app on MGears’ advice: call controls appeared on the stick and the conversation ran through the head unit. A third owner wrote up the clean-slate version above and found the stick’s Bluetooth entry stayed on the phone but no longer connected, while calls showed on the stick and were heard in the car. A fourth followed his write-up and no longer had to connect the phone by hand on every other drive.

Some owners talk normally without registering, so if your calls already work, leave them be. Owners with iPhones could not complete the registration; for them the fix below that keeps the phone off the stick is the route.

Let the phone reach the car before the stick starts

  • Low risk
  • Time: 2 minutes per drive
  • Worked for 3 of 4 reports
  1. When the stick shows that hands-free is not connected, tap its reconnect (Retry) prompt. The stick steps aside for a few seconds.
  2. Let the phone connect to the car’s Bluetooth in that gap.
  3. If no prompt appears, unplug the stick, let the phone connect to the car, then plug the stick back in.
  4. Once the phone is on the car, let it connect to the stick as well, if you use the stick’s call display.

An owner who changed phones found the stick kept saying hands-free was not connected; with the stick unplugged, the phone connected to the car, and after plugging the stick back in everything worked. Another owner needs the same order every time on his head unit: phone to the car first, stick second, or the car drops the phone. A third taps the stick’s reconnect prompt: the stick restarts, the phone joins the car and then the stick. One owner tapped Retry and the phone still did not connect, and a VW MIB 2.5 owner never sees the prompt at all.

Calling from the stick? Send the sound to the car's Bluetooth

  • Low risk
  • Time: 1 minute
  • Worked for 3 of 3 reports
  1. Find the contact on the stick and start the call.
  2. On the call screen, open the audio output choice.
  3. Choose the car’s Bluetooth connection.
  4. Check on the next call; if the phone does not remember the choice, repeat it.

Three owners fixed outgoing calls this way. One chooses the car’s Bluetooth connection each time after the contact is found, and a second owner replied that it worked for him too, although he would rather the car were the default. A Chery Tiggo 7 owner with the phone connected to both the car and the stick found the Google dialer on the stick placed the call through his phone, but the sound went to the stick until he switched it to the head unit.

Keep the phone off the stick's Bluetooth entirely

  • Low risk
  • Time: 5 minutes
  • Worked for 2 of 3 reports
  1. On the phone, forget the Mstick4 in Bluetooth settings.
  2. Keep the phone paired with the car’s own Bluetooth.
  3. Start the car and let the phone connect to the head unit while the stick boots.
  4. Take and place calls with the car’s phone screen and the steering-wheel buttons.

One owner tested every combination: with the phone on the car alone, all calls worked; with the phone on the stick, or on both, calls switched to the phone’s speaker. Another, answering a VW MIB 2.5 owner, removed the stick’s pairing completely and answers calls and picks contacts on the instrument cluster with the wheel buttons.

You lose a little. The stick no longer shows the caller, and an owner noticed its music then does not pause for a call. The owner on MIB 2.5 found the navigation voice talks over the caller in this mode. A stick setting labelled “disable smartphone connection” gives a similar result: no call info on the stick, and music is muted rather than paused. On a Hyundai Santa Fe 4 with a Samsung phone this did not help: after the engine had been off for a minute the phone still would not reconnect to the car.

Dial from the stick's Contacts icon

  • Low risk
  • Time: 5 minutes
  • Worked for 2 of 2 reports
  1. Open Contacts on the stick and call from there.
  2. Put Contacts, and cards for the people you call most, on the stick’s home screen.
  3. Answer incoming calls with the call button on the steering wheel. The conversation runs through the car’s speakers and microphone, even though the phone in your pocket rings.

One owner, after three trips out to the car to test it, found calls placed through the stick’s Contacts icon went through and everyone heard well; another owner replied that it worked for him. He adds that every car behaves a little differently, so test it on yours. If the wheel’s call button does nothing or leaves the stick, see steering-wheel call buttons not working.

Things to try (unverified)

  • Update the stick and drop root. One owner found the order of connection stopped mattering after he installed firmware 1.9.4 without root, but he also changed the cable at the same time, on a VW MIB3 car. A poor cable causes its own drops: see Mstick4 connection interrupted.
  • Do not block MGears Go notifications. One owner who turned off the app’s notifications on the phone got a flood of old calls and notifications and the stick disconnecting from the car. Another owner with notifications off saw nothing of the kind.
  • Code the head unit for two phones (VW MIB 2.5). A MIB 2.5 owner reported that, with his head unit coded to allow two Bluetooth phones, the box and the phone both connect to the car and calls work. It was described for a box in general, not confirmed on the Mstick4, and changing the head unit coding needs a VW coding tool.
  • Use the phone’s own voice assistant for calls. Since the stick’s Google Assistant cannot place calls while MGears Go runs, owners say “Hey Google, call…” to the phone lying on the charger, and the call goes out through the car.

For Carlinkit boxes the pairing advice is different, because those boxes switch protocol and can carry calls themselves; that is in keep your phone on the car’s Bluetooth while the AI box runs.

If nothing works

Note the stick’s firmware version from MGears settings and whether it is rooted, the phone model and its Android or iOS version, the car and head unit, and exactly what is paired with what: phone to car, phone to stick, and whether the stick is registered in MGears Go. Record a short video of a call from ringing to hanging up.

Write to MGears at [email protected]; owners who contacted them got replies within about a day, and it was MGears that pointed owners to the MGears Go registration. The Mstick4 page lists the stick’s settings and firmware history. If your car refuses the phone whenever any Android Auto device is plugged in, the limit is in the head unit, and start here explains what the other box families do differently with calls.

What owners said

“At that moment the stick offers to reconnect. I tap it, the stick restarts, the phone connects to the car's head unit, then to the stick, and everything is great.”
Worked: Tap reconnect so the car connects first
Owner, Feb 2026
“I removed the stick's pairing with the phone completely. […] The phone connects to the head unit, the stick boots […]. An incoming call shows on the instrument cluster and I answer with the steering-wheel button.”
Worked: Phone paired with the car only
Owner, Feb 2026
“I put the app on my phone and it told me itself that my hands-free was set up wrong. I unpaired everything everywhere and paired through the app, and it worked: the link goes through the car's Bluetooth.”
Worked: Re-pair through the MGears Go app
Owner, Jun 2025

Quotes are translated where needed and shortened ([…]); names are removed. Full counts are in the evidence table below.

Questions owners ask

Can the Mstick4 make calls with its own SIM card?

No, not properly. Owners report that calls from the stick's SIM are disabled. With a third-party dialer installed, the other person hears you but you cannot hear them, which is only good for opening gates and barriers.

Should the phone be paired with the stick or with the car?

With the car, always: the car carries the call. On Android, also register the stick in MGears Go, so the stick can show the caller without taking the call audio. If you skip the app, keep the phone off the stick's Bluetooth entirely.

Does MGears Go registration work with an iPhone?

MGears support gave the app fix for Android phones. Owners with iPhones could not complete the registration and use the stick without it, with the phone paired to the car.

Can I call with Google Assistant on the stick?

MGears support told one owner that Google Assistant cannot place calls while MGears Go is in use. Owners who call by voice use the assistant on the phone itself instead.

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 14 community reports on MGears Mstick4.
  • 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 (5 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.

CaseConfirmed onResultSource
case-8220MGears Mstick44 workedOwner discussion threads, 4 messages
case-8221MGears Mstick43 worked, 1 did notOwner discussion threads, 4 messages
case-8222MGears Mstick42 worked, 1 did notOwner discussion threads, 3 messages
case-8223MGears Mstick43 workedOwner discussion threads, 3 messages
case-8224MGears Mstick42 workedOwner discussion threads, 2 messages