Heat & throttlingReviewed
Still 60–80 °C With a Cooler: Find What Loads the CPU
Box still runs 60–80 °C with a cooler? An app or launcher setting is pinning the CPU. Change the launcher engine, swap the app. TBox Ultra, Mstick4.
Carlinkit TBox UltraMGears Mstick4Carlinkit TBox Ultra 2
Quick answer
Change what the box is rendering: in CarCar Launcher, switch the widget rendering engine and let the launcher's built-in player cover your music app, which lowered temperatures for three of four owners. If one CPU core still sits at 100%, the navigation app is the culprit; another app or app version brought one box from 82 °C to 38 °C. Six owner reports in total.
Symptoms
- You fitted a cooler or heatsink, but the box still reads 60–80 °C
- Another owner with the same box and car reports 40 °C
- The Mstick4 fan runs loud whenever navigation and music share the screen
- Temperature jumped after a navigation app or launcher update
- Apps you never open keep showing up as running
Applies to
- Connection to the car
- CarPlay and Android Auto
- Highest risk on this page
- Low risk
- Status
- Workaround confirmed by the community
Why it happens
A cooler removes heat; it does not reduce how much heat is made. When one app keeps a processor core at 100%, the box makes more heat than any stick-on cooler can carry through the case, and the temperature climbs back to 60–80 °C or higher. Owners traced this to three sources: the launcher’s way of drawing widgets, a particular navigation app or version, and apps running in the background without being opened.
This is why two identical boxes in identical cars can read 40 °C and 75 °C. One TBox Ultra 1 owner fitted a cooler, then a better one, and the heat shutdowns still came back; most replies pointed to load rather than cooling. Once you find the load, the cooler you already have starts working again.
Rule out power first if the box shuts down rather than slows down, especially at moderate temperatures: AI box keeps rebooting covers that.
Fixes, ranked
Lighten the launcher: switch its rendering engine and use the built-in player
- Low risk
- Time: 15 minutes plus a test drive
- Worked for 3 of 4 reports
- Open CarCar Launcher’s settings and find the rendering engine options (in the version and widget sections). Note what is selected now.
- Switch the widget rendering engine to the other option (legacy or stable) and drive the same route as before.
- Cover your music app with the launcher’s built-in player instead of showing the music app’s own full window.
- Keep whichever combination gives the lower reading.
An Mstick4 owner whose box ran hot with a loud fan when navigation and music shared the screen switched the rendering engine and reported less heat and less fan noise. A second Mstick4 owner found the legacy widget engine noticeably cooler; after more careful testing the gap was about 5–7 °C, and only when the music player was expanded. A TBox Ultra 2 owner held about 35 °C with the launcher’s built-in player over the music app, though active route guidance still pushed it up.
It did not help everyone. A fourth owner saw little difference from the engine change, because the newest version of his navigation app was running the box at 80–85 °C on its own. If that sounds like you, go to Fix 2.
Find the app that pins a CPU core and swap it or its version
- Low risk
- Time: One drive
- Worked for 2 of 2 reports
- Open a system-monitor app that shows per-core load and watch it while navigating.
- If one core sits at 100% with the navigation app open, try another navigation app on the same route.
- If the problem started with an app update, stay on the version that ran cool and turn off auto-update for that app in Google Play.
- Also turn off 3D buildings and similar 3D map features in the navigation app (suggested in a reply, not tested on its own).
An Mstick4 owner hit 82 °C with throttling and freezes, with one core permanently at 100% under his navigation app, and the box strapped to a cooler that could only blow on plastic. Switching to Google Maps brought it to 38 °C; a third navigation app settled at 62 °C. Another owner saw one version of a navigation app push the box past 80 °C, and the problem went away with a later version; he then stopped updating.
The catch is that a later version can bring it back, as one owner found with the newest release at 80–85 °C. Note the version that runs cool before you update.
Uninstall the background apps you do not use
- Low risk
- Time: 20 minutes
- Worked for 1 of 1 report
- Open Settings → Apps and list every app that is not part of the system.
- Uninstall the ones you do not need in the car.
- For the apps you keep, restrict background activity, then check after a few minutes whether they started again on their own.
- Drive with the temperature display on and compare.
A TBox Ultra 1 owner found about 15 apps starting by themselves: a radar-detector app, alternative app stores, the stock APK installers, video apps. The box lagged at 89 °C. Extra heatsinks got it to 78 °C; removing half of those apps from the background brought it to a little over 60 °C.
Restriction alone did not hold for him. Apps restarted within minutes after background restriction in their settings and after being disabled in the factory menu, and a task killer only lowered the temperature until they reloaded. Uninstalling worked. Avoid modified or pirated app builds: one of the removed apps was a cracked navigation app.
Things to try (unverified)
- Factory reset and add apps one at a time. Suggested to the Ultra 1 owner whose box went from 60–80 °C with a cheap cooler to shutting down again: back up your app list, reset, install only navigation and music, drive with the temperature display on, then add one app per drive. He had not reported back.
- Connect the Y-cable’s second power lead. If the box shuts down rather than slows down, power may be the real cause; see AI box keeps rebooting.
- Consider the screen. A very large or high-resolution head-unit display keeps the processor busy on its own; see big screens overload the box.
One reply suggested opening the case and re-applying thermal paste. Some owners have done it, but it voids the warranty; exhaust the steps above first.
If nothing works
Record the box model and firmware date (Settings → About), the apps that are running (a screenshot of the running-apps list helps), which cooler you use, and the temperature with only navigation and music open. Note whether the box slows down or shuts down.
If it still runs hot after a reset with only two apps and a cooler, ask the seller or manufacturer (Carlinkit: [email protected]) about a warranty check. How hot is too hot explains how to read the temperature reliably, and start here compares box families if you decide to replace it.
What owners said
“It starts lagging, no reboots. […] A 50×50×11 heatsink underneath helped bring the temperature down to 78. After removing half of the 15 apps from the background, 60+.”
Owner, Dec 2025
“On the stable widget engine the temperature is as before. […] On the legacy widget engine the temperature is noticeably lower. For now I've gone back to legacy.”
Owner, Dec 2025
“Hit 82 degrees today, throttling with freezes and everything. One core was permanently at 100% and heating the box. […] First I switched [my maps app] to Google Maps and got 38 degrees instead of 82.”
Owner, Oct 2025
Quotes are translated where needed and shortened ([…]); names are removed. Full counts are in the evidence table below.
Questions owners ask
My friend's identical box runs at 40 °C. Is mine faulty?
Usually not. Owners of the same box report anything from 20–40 °C to 60–80 °C, and in the threads the difference came from apps and launcher settings. Rule those out before a warranty claim.
Does restricting background activity in app settings stop an app?
Not reliably. One owner found apps restarted within minutes after background restriction and after disabling them in the factory menu; only uninstalling them lowered the temperature for good.
Will a bigger cooler fix it?
Not if one app keeps a core at full load. A cooler on a plastic case cannot keep up with that, as one Mstick4 owner found with the box strapped to a cooler at 82 °C.
Parts the fixes above need

USB Y-cable (second power lead)
Moves the box's power draw onto a second USB port or a 12 V adapter so the car's data port only carries data. The thick lead goes in the car's data port, the thin one in a charger.
Some links above are affiliate links: if you buy through them we may earn a commission at no extra cost to you. It never changes which fix we rank first. Product photos are the sellers' own, from the AliExpress listing. Disclosure.
If none of these fixes work
Try every free fix above first. Each of these needs a car whose screen already runs wired CarPlay or Android Auto. We have not tested them: check the seller's compatibility list for your car and head unit, and that the listing shows the exact model named here, before you buy.
Wireless CarPlay / Android Auto adapter (Carlinkit Mini Ultra 3)
If you only use the box to get CarPlay or Android Auto without a cable, a plain wireless adapter has no Android system to update, overheat or crash.
Replacement AI box (Carlinkit, Android 13, SM6225)
If the box is out of warranty and still fails after the fixes above, another Carlinkit box keeps your apps on the car screen. It needs wired CarPlay or Android Auto in the car. Pick the NA variant for North American cars, EAU elsewhere.
Replacement from another maker (Ottocast P3 Pro)
If you would rather switch brands, Ottocast's P3 Pro runs Android 13 and has HDMI out. It needs the connection protocol Ottocast lists for your car. The listing opens on a cheaper Mini adapter: select the P3 Pro option and check the picture and name before you pay.
Affiliate links: we may earn a commission at no extra cost to you. Disclosure.
Related fixes
- AI Box Overheating Shutdowns: Heatsink, Cooler or Fan?Low risk
- How Hot Is Too Hot? AI Box Temperatures and How to See ThemAdvanced
- AI Box Lags on a Big High-Resolution Screen? Raise Smallest WidthLow risk
- AI Box Keeps Rebooting or Disconnecting? Start With PowerLow risk
- AI Box Reboots When Mobile Signal Drops: Hotspot or LTE ModeLow 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 MGears Mstick4, Carlinkit TBox Ultra 2, Carlinkit TBox Ultra.
- 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 (4 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-0017 | Model not stated | 0 worked | Owner discussion threads, 3 messages |
| case-2007 | Carlinkit TBox Ultra | 1 worked | Owner discussion threads, 5 messages |
| case-2008 | MGears Mstick4; Carlinkit TBox Ultra 2 | 3 worked, 1 did not | Owner discussion threads, 11 messages |
| case-2009 | MGears Mstick4 | 2 worked | Owner discussion threads, 5 messages |