Apps & launchersReviewed
Assign the Steering-Wheel Voice Button: 6 Owner Reports
Make the car's voice button open Gemini, Alexa or another assistant on your AI box: set it as Digital assistant app. Carlinkit TBox Ambient, Plus, Ultra.
Carlinkit TBox AmbientCarlinkit TBox PlusCarlinkit TBox UltraCarlinkit TBox Ultra 2Carlinkit TBox Ultra 3Carlinkit TBox Ultra 4Carlinkit TBox UHDMGears Mstick4
Quick answer
Install your assistant app, set the box's own Voice assistant setting to None, then choose that app under Settings → Apps → Default apps → Digital assistant app; the car's voice button now opens it. Four owners confirmed this on TBox Ambient and Ultra boxes, with Gemini and with a regional assistant. It cannot work on cars whose head unit keeps the voice button for its own voice control.
Owner reports at a glance
- Owner reports of a fix that worked
- 6
- Reports with a result
- 9
- 6 worked, 3 did not help
- Most-confirmed fix
- Set your assistant as the Digital assistant app: worked in 4 of 7 reports; all fixes, ranked
- Boxes owners confirmed it on
- Carlinkit TBox Ambient, MGears Mstick4
One owner counts once per fix; reports with no result yet are not counted. Counts reviewed . How we count.
Symptoms
- Pressing the voice button on the steering wheel does nothing on the AI box, or opens the wrong assistant
- The button opens a full app instead of a listening assistant
- The wheel's answer button hangs up incoming calls instead of answering them
- The assistant setting resets after you close the assistant app (TBox Plus)
Applies to
- Devices
- Connection to the car
- CarPlay and Android Auto
- Firmware in confirmed reports
- Carlinkit TBox Ambient: 2024-03; Carlinkit TBox Ambient: 2024-06; Carlinkit TBox Ambient: 2023-12
- Highest risk on this page
- Low risk
- Status
- Workaround confirmed by the community
Why it happens
When your car passes its steering-wheel voice button through CarPlay or Android Auto, the AI box treats the press like the assist gesture on an Android phone. Android then opens whatever app is set as the Digital assistant app. Out of the box that is Google’s assistant, or the box’s own Voice assistant setting, so a different assistant only answers the button once you point that setting at it.
Two things get in the way. Some head units never send the button to the box: they keep it for their own voice control, and the car’s assistant starts instead. And the box’s separate Voice assistant setting can compete with the Digital assistant choice, which is why the FAQ sets it to None first.
Fixes, ranked
Set your assistant as the Digital assistant app
- Low risk
- Time: 10 minutes
- Worked for 4 of 7 reports
- Recommended in the community FAQ
- Install your assistant app from Google Play: Gemini, Alexa, or a regional assistant if you use one. It has to be an app that registers as a digital assistant, not a navigation app with a voice icon.
- In the box’s settings, set Voice assistant to None.
- Open Settings → Apps → Default apps → Digital assistant app (on some builds Settings → More → Apps; the settings search finds it) and select your assistant app.
- Open the assistant app and turn off its voice activation (wake word). The button now does that job.
- Press the voice button on the steering wheel and speak a command.
- If sound turns distorted after using the assistant, go back to the home screen or switch to another app once.
The community FAQ links to this setup, written by an owner who checked it on a TBox Ambient with late-March 2024 firmware. An Ambient owner with a Kia in CarPlay mode followed it exactly on the June 2024 firmware and reported the assistant starting from the wheel. An Ultra owner confirmed it on the Ultra too: the button brought up the assistant, which could plan a route and start music. Another Ultra owner set up Gemini the same way and uses the car’s own voice button for calls and smart-home commands.
Three owners said it did not work for them. Two drove Chery models, where the head unit’s own assistant answered the button (one on a TBox UHD) or nothing happened at all (one on an Ambient); the third said only that the instructions did not work for them. Those failures fit head units that keep the button, covered under “Things to try” below.
Two caveats from owners. On the TBox Plus the Digital assistant choice was kept only until the assistant app was closed, then reset; the Ambient did not do this. And the Ultra owner noticed music sounding distorted after the assistant ran, until they left for the home screen. If you hear crackling generally, the wake word is the usual cause; see crackling or muffled sound.
One owner found their regional assistant responded only with its own voice activation switched on. If the button opens the app but it does not listen, try that switch, and turn it off again if the sound degrades.
Wheel answer button hangs up calls: change the Digital assistant app
- Low risk
- Time: 5 minutes
- Worked for 1 of 1 report
- Open Settings → Apps → Default apps → Digital assistant app.
- If Google’s assistant is selected, choose another installed assistant app instead.
- Ask someone to call you and press the answer button on the wheel.
A TBox Ambient owner with a Kia Sportage on the December 2023 firmware found that the wheel’s answer button rejected incoming calls while Google was the digital assistant. After switching the Digital assistant app to another assistant, the answer button worked. The owner could not explain the link, and nobody else has tested it, but the Ambient owner in Fix 1 also noticed that answering from the wheel started working after the same change.
If callers cannot hear you once you answer, that is a separate problem; see microphone not working on calls.
MGears Mstick4: launch an app from the voice button with Tasker
- Low risk
- Time: 20 minutes
- Worked for 1 of 1 report
- Install Tasker (an automation app) on the stick. It does not need root.
- Create a task that launches the app you want on the button, for example your navigation app.
- Create a profile with the event Secondary app opened, not Assistant action, and link it to that task.
- Press the voice button on the steering wheel.
An Mstick4 owner without root wanted the wheel’s voice button to bring up his navigation app, which on his Carlinkit boxes he set through the system assistant setting. On the stick, a Tasker profile on the assistant event never fired; the press showed up as “secondary app opened”. With the profile on that event instead, the button launched the app. He later had Tasker call an automation macro so the button does something else when the navigation app is already on screen.
Button-mapping apps are not an alternative here: the same owner found KeyMapper does not see the wheel buttons on the Mstick4 at all, while on Carlinkit boxes it does. More on the stick on the MGears Mstick4 page.
Things to try (unverified)
- Assistant opens from the button but waits for a tap on the screen. A TBox Ambient owner whose assistant opened from the wheel and then waited for a tap on the on-screen microphone said one-press worked when the box was new, and a factory reset had restored it once before. He had not reset again when he reported it, and another Ambient owner with the same symptom found no fix.
- Hold the button for five seconds. Suggested to a Chery Tiggo 8 Pro Max owner whose short press did nothing for the box. Nobody reported back. Some head units only pass a long press to CarPlay or Android Auto.
- Head units that keep the button. On a Chery Tiggo 4 Pro the car’s own assistant opened; another owner explained that their head unit gives its own voice input priority and cuts the box’s audio channel. A Chevrolet Equinox owner saw a “language not supported for your region” message from the press. In these cases the box never receives the press; check the head unit’s voice settings or the protocol you run.
- Stop Google’s assistant from answering the button. Owners whose car assistant clashed with the box’s were told to deny microphone permission to the assistant apps. A Haval owner who switched the assistant off still got a prompt offering to turn it back on at every press. Unresolved.
- TBox Plus: keep the setting. One owner kept settings changes on a TBox Plus by unplugging the box right after changing them, so the change was written before the next restart. Untested by others.
If nothing works
Write down the box model and firmware date (Settings → About), the car’s make, model, year and head unit, the protocol (CarPlay or Android Auto), the assistant app and its version, and what a short and a long press do. Test the button with your phone connected directly to the car: if the phone’s assistant does not answer the button either, the head unit is keeping it and no box setting will change that.
Send box-side faults to Carlinkit support ([email protected]). For other engineering-menu settings that affect audio, see the engineering codes reference. If steering-wheel voice control is essential, check how your car hands the button to CarPlay or Android Auto before choosing a box; start here.
What owners said
“I set up Google's Gemini: it works from the car's own voice-assistant button on the steering wheel. I mostly use it for phone calls and smart-home controls (gate, parking lights). Works great.”
Owner, Sep 2026
“Huge thanks again, it all worked! Now I need to dig a little deeper and set it so that when the maps app is running, pressing this button does something else.”
Owner, MGears Mstick4, Jul 2026
“I switched it to [another assistant] and now answering calls from the wheel works! […] December firmware, Kia Sportage, Ambient 6225. […] Before that I had Google set.”
Owner, Carlinkit TBox Ambient, Jul 2024
Quotes are translated where needed and shortened ([…]); names are removed. Full counts are in the evidence table below.
Questions owners ask
Which assistant apps work?
Any app Android lists under Digital assistant app. Owners confirmed Gemini and a regional assistant app. Alexa and other apps that register as a digital assistant use the same setting, but no owner has reported on them yet.
Should the assistant's wake word stay on?
Turn it off. The button replaces the wake word, and an always-listening assistant is the most common cause of crackling or muffled sound on these boxes.
My car's own assistant opens instead. Can I change that?
Usually not from the box. Some head units keep the voice button for their own voice control and never send it over CarPlay or Android Auto. A long press is worth one try.
Related fixes
- Crackling or Muffled Sound? Turn Off Voice-Assistant Hot-WordLow risk
- Microphone Not Working on Calls? Clear Every Bluetooth PairingAdvanced
- Head Unit Shows Only CarPlay? Switch the Box's ProtocolAdvanced
- Voice Assistant Doesn't Hear You: 13 Owner ReportsLow risk
- CarCar Launcher Player: Wheel Track Buttons Dead Until You TapLow risk
- Telegram Login Code Never Arrives on the AI Box: How to Sign InLow 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, 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 (8 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-0032 | Model not stated | Recommended in the FAQ (not counted) | Community FAQ, 2 messages |
| case-6014 | Carlinkit TBox Ambient (2024-06) | 1 worked | Owner discussion threads, 3 messages |
| case-6015 | Model not stated | 1 worked | Owner discussion threads, 3 messages |
| case-6016 | Model not stated | 1 worked | Owner discussion threads, 3 messages |
| case-6017 | Carlinkit TBox Ambient (2023-12) | 1 worked | Owner discussion threads, 5 messages |
| case-6018 | Model not stated | 0 worked, 3 did not | Owner discussion threads, 9 messages |
| case-6019 | Model not stated | 0 worked | Owner discussion threads, 5 messages |
| case-7180 | MGears Mstick4 | 1 worked | Owner discussion threads, 8 messages |