Apps & launchersReviewed
CarCar Launcher Player: Wheel Track Buttons Dead Until You Tap
CarCar Launcher's Player panel kills the steering-wheel track buttons until you tap it? Update or roll back the launcher, or stop covering the music app.
MGears Mstick4Carlinkit TBox UHDCarlinkit TBox UltraOttocast OttoAibox NanoCarlinkit TBox AmbientCarlinkit TBox Ultra 2Quick answer
On CarCar Launcher, when the steering-wheel track buttons do nothing under the Player panel until you tap it once, updating the launcher to the current stable build brought them back for 5 of the 8 owners who reported. If an update breaks them again, roll back, switch the widgets engine to legacy, or stop covering the music app.
Symptoms
- The steering-wheel next and previous buttons do nothing after start-up until you tap the CarCar Launcher Player once
- Track buttons work for about 30 seconds, or for one press, after the Player opens, then stop
- Switching tracks works in the music app on its own, but not once the Player panel covers it
- The buttons stopped right after a CarCar Launcher update
- They work with the Player as a pane but die as soon as you open it full screen
Applies to
- Devices
- Connection to the car
- CarPlay and Android Auto
- Head units mentioned in reports
- Chery / Exeed Chery and Exeed head units; Geely GKUI (CarPlay via Carbitlink); Volkswagen MIB 2.5
- Highest risk on this page
- Low risk
- Status
- Workaround confirmed by the community
Why it happens
CarCar Launcher’s Player is an overlay the launcher draws over your music app. The box turns each steering-wheel next or previous press into a media-key press, and when the Player covers the music app that key has to pass through the overlay to reach the player. When the overlay does not hold input focus, the presses go nowhere and the buttons look dead.
Owners traced it to focus. With the music app uncovered the wheel buttons switch tracks fine; cover it with the Player and you have to tap the Player once to wake it, or it works for the first seconds after start-up and then stops. The launcher’s developer said the launcher does not handle the media keys itself and that the stable widgets rendering engine was involved in the fault.
This has been a launcher regression that comes and goes between versions, through the 3.3, 3.4 and 3.5 builds, so a fix tied to one version does not hold for long. The levers that do work are the launcher version, the widgets rendering engine, and whether the Player covers the music app at all.
Fixes, ranked
Update CarCar Launcher to the current stable build
- Low risk
- Time: 10 minutes
- Worked for 5 of 8 reports
- Check the installed CarCar Launcher version in its own settings.
- Update CarCar Launcher to the current stable build, not a beta. See install, update or roll back CarCar Launcher.
- Drive and test the wheel track buttons with the Player panel over your music app.
- If a later update brings the fault back, roll it back instead (next fix).
One MGears Mstick4 owner whose buttons failed in player mode on 3.3.7 updated to 3.3.8 and drove for hours with them working. Another, on a Mstick4 and a TBox UHD 6225, confirmed the problem was gone on 3.3.8. One owner cleared it on 3.4.2, one on a TBox Ultra got it back on 3.3.8 after a bad drive on 3.3.7, and a Chery Tiggo 8 Pro Max owner said everything worked again after the launcher update.
Updating is not a permanent cure. Three owners still had dead buttons after updating: two stayed broken on 3.3.8 and 3.3.9 with both a music app and Spotify under the Player, and one gave up and rolled back. The same Chery owner saw the fault return after a still later update. Treat “the current stable build” as a moving target: update, test, and if a new build breaks it again, drop back.
Roll the launcher back to a build where they worked
- Low risk
- Time: 15 minutes
- Worked for 4 of 4 reports
- Note which CarCar Launcher version you are on and when the buttons last worked.
- Install an earlier CarCar Launcher build from before the fault appeared, following install, update or roll back CarCar Launcher.
- Drive and test the wheel track buttons with the Player as a pane and, if you use it, full screen.
An Ottocast OttoAibox Nano owner rolled back to the previous launcher and everything worked as before. An Mstick4 owner whose buttons died only when the Player was opened full screen rolled back to 3.3.4 and had them working in both the full-screen player and the widget. One owner stays on older builds because every new one breaks the buttons, and a TBox Ultra owner whose buttons failed on a 3.3.0 beta returned to the stable build and had them everywhere.
This is the other direction of the same lever as the update above: you are moving off the broken version. It is the fix owners reached for the full-screen-player case, where switching the widgets engine was not enough.
Use the music app without the Player panel
- Low risk
- Time: 5 minutes
- Worked for 3 of 3 reports
- Open the music app directly rather than through the launcher’s Player panel.
- Close, minimise or turn off the Player overlay in CarCar Launcher.
- Test the wheel track buttons in the uncovered music app.
A TBox owner in a Geely on CarPlay found that minimising or turning off the Player made track switching work in the music app again; re-adding the app to the Player worked only for a while before it dropped out once more. A TBox Ambient owner had the buttons back with the Player turned off, and a TBox Ultra 2 owner confirmed that an uncovered music app switches fine from the wheel while the covered one needs a tap first.
The trade-off is giving up the Player panel, which owners rate as one of the launcher’s best features. If you want to keep it, use one of the version or engine fixes instead.
Switch the widgets rendering engine to legacy
- Low risk
- Time: 5 minutes
- Worked for 2 of 2 reports
- Open CarCar Launcher’s own settings (not the box’s Android settings).
- Find the widgets rendering engine and set it to legacy (the old option).
- Return to the launcher and test the wheel track buttons with the Player panel over your music app.
The launcher’s developer suggested the legacy widgets engine while trying to find what affected the buttons. One owner switched it on and the buttons worked; a TBox Ultra 2 owner in a Geely, whose buttons were dead on the stable engine on 3.4.1 with no amount of tapping helping, had them work at once on the legacy engine, and reported the same cure again on 3.5.13.
This is the fix for the Player used as a pane or widget. For a full-screen player it was not enough: owners there still had to tap the Player or roll the launcher back, which is also what the CarCar Launcher lag and rendering-engine page found. If the engine change does nothing for you in full screen, use the rollback above.
Tap the Player once after each start
- Low risk
- Time: 1 minute each start
- Worked for 2 of 3 reports
- After the box and launcher have loaded, tap the Player panel once anywhere on screen.
- Use the wheel next and previous buttons as normal.
- Repeat the single tap after each start, since the focus is lost when the box restarts.
A Chery Tiggo 8 Pro Max owner found that nothing happened on the player controls until he tapped it once, at every start, and a TBox Ultra owner in a Volkswagen on MIB 2.5 said track switching began only after the first tap on screen. This is the instant workaround while you decide on one of the durable fixes above.
It only revives the focus case. One owner whose buttons had fully dropped found that tapping anywhere switched nothing, and his Mute button half-failed at the same time, so if no tap brings the buttons back the cause is more than lost focus.
Things to try (unverified)
- Re-run the same update in the installer. One owner reinstalled 3.3.8 through the installer and the buttons returned. It reads as a variant of updating rather than a separate fix, and only one owner reported it.
- The same drop-out without the Player at all. The launcher’s developer pointed to reports where the wheel buttons dropped with the Player not involved, and one owner suspected a music-app update rather than the launcher. If rolling back and removing the panel both change nothing, the cause may be a music-app update or the box’s own CarPlay or Android Auto layer, and these launcher fixes will not reach it.
- The Mute button for pause and resume. When the track buttons drop, the car’s Mute button can also stop pausing the player cleanly. That is a sign of the full drop-out, not the focus case, and no setting fixed it in the reports read.
If nothing works
Record the box model and firmware date (Settings → About), the CarCar Launcher version, the car make, model and year, the head unit, the protocol (CarPlay or Android Auto), and one detail that sorts the problem quickly: whether the wheel buttons switch tracks with the music app uncovered but fail once the Player covers it. Write it up with how to report a bug and take it to the launcher’s developer channel.
If the problem is the car’s wheel buttons that die after you remapped them, that is a different fault, covered in CarCar Launcher wheel buttons after remapping. If you want the car’s voice button to open an assistant instead, see assign your assistant to the voice button. If the car never drives the wheel buttons to the box at all, the box or the connection is at fault; contact the seller or start here.
What owners said
“On 3.3.7 the buttons glitched in player mode. This morning I installed 3.3.8 and drove for several hours on the new version: the wheel buttons in player mode now work in [the music app].”
Owner, Jan 2026
“On the Ottocast Nano, same story after the update. I rolled back to the previous version of CarCar and everything worked normally, as it had before.”
Owner, Ottocast OttoAibox Nano, Jan 2026
“If you switch the widgets engine to legacy, the buttons work straight away. No need to tap anywhere. Ultra 2, Tugella.”
Owner, Carlinkit TBox Ultra 2, Jan 2026
Quotes are translated where needed and shortened ([…]); names are removed. Full counts are in the evidence table below.
Questions owners ask
Is this the same as steering-wheel buttons that die after I remap them?
No. That is a separate problem: here nothing was remapped and only track control under the Player panel fails. The remapping fix is on its own page, linked below.
Does the legacy widgets engine fix it in a full-screen player?
Not on its own. The legacy engine restored the buttons with the Player as a pane, but owners with a full-screen player still had to tap it once or roll the launcher back.
Will I lose the Player panel if I stop using it?
Only its overlay. The music app keeps playing and the wheel buttons control it directly. Many owners keep the Player and instead update, roll back, or switch the widgets engine.
Related fixes
- CarCar Launcher Laggy or Glitchy? Change the Rendering EngineLow risk
- CarCar Launcher Wheel Buttons Stop Working After RemappingLow risk
- Install, Update or Roll Back CarCar LauncherLow risk
- Assign the Steering-Wheel Voice Button: 6 Owner ReportsLow risk
- WhatsApp on the AI Box Logs Out Your Phone: Link It InsteadLow 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 16 community reports on MGears Mstick4, Carlinkit TBox UHD, Carlinkit TBox Ultra, Carlinkit TBox Ultra 2, Carlinkit TBox Ambient, Ottocast OttoAibox Nano.
- 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.
| Case | Confirmed on | Result | Source |
|---|---|---|---|
| case-1673 | Model not stated | 5 worked, 3 did not | Owner discussion threads, 5 messages |
| case-1674 | Model not stated | 4 worked | Owner discussion threads, 4 messages |
| case-1675 | Model not stated | 3 worked | Owner discussion threads, 3 messages |
| case-1676 | Model not stated | 2 worked | Owner discussion threads, 2 messages |
| case-1677 | Model not stated | 2 worked, 1 did not | Owner discussion threads, 2 messages |