Skip to content
AI Box Fix

Heat & throttlingReviewed

AI Box Lags on a Big High-Resolution Screen? Raise Smallest Width

Box lags, overheats or loses touch on a huge car screen (Geely Atlas)? Set Smallest width to 800 or switch to Android Auto. TBox Ambient, Plus, Picasou 3.

Quick answer

Open Developer options and set Smallest width to 800, so the box draws its interface at a lower density for the large display; on a Geely Atlas that stopped the touch dropouts and lowered the heat for two of three owners. If your head unit supports Android Auto, switching the box from CarPlay to Android Auto made it smoother for two more owners on large screens.

Symptoms

  • Your car has a very large or very high-resolution screen and the box lags on it
  • Touch stops responding for a few seconds and comes back
  • Sound stutters or warbles even though few apps are running
  • The box runs at 70–80 °C on this car but was fine in a car with a smaller screen
  • CarPlay mode feels slow, with a delay on every tap

Applies to

Connection to the car
CarPlay and Android Auto
Head units mentioned in reports
Geely GKUI (CarPlay via Carbitlink); Haval / GWM GWM head units
Highest risk on this page
Safe
Status
Workaround confirmed by the community

Why it happens

The box draws its whole interface at the head unit’s resolution and streams it to the car as video. A large display such as the Geely Atlas screen (about 1441 by 1768 pixels in one owner’s report) has roughly twice the pixels of a typical car screen, so the processor works harder on every frame. On a modest chip that leaves little room for navigation and music: the box lags, touch input drops out, sound stutters, and the temperature climbs.

One owner who moved the same TBox from an Exeed with half the resolution to a Geely Atlas found it struggled only in the Atlas. Another, on the same car, reported that a TBox Plus lagged badly while a TBox Ambient did not lag but kept losing touch. A third gave up on a TBox Plus in an Atlas, saying the screen size made everything lag and the sound croak.

AI box caseSoCheatsink / cooler on the heat-spreader sideNeeds airflow:not a closed armrest~80–85 °C: throttlingbeyond: reboots
A bigger, sharper screen means more work per frame for the same chip; more work means more heat and earlier throttling.

Fixes, ranked

Set Smallest width to 800 in Developer options

  • Safe
  • Time: 5 minutes
  • Worked for 2 of 3 reports
  1. Enable Developer options: Settings → More → About, then tap Build number repeatedly until it says you are a developer.
  2. Open Settings → More → System → Developer options → Smallest width.
  3. Enter 800 and confirm.
  4. Reboot, then check touch response, the temperature and that your widgets still fit.

Write down the value shown before you change it (484 is common on Carlinkit boxes). If widgets no longer fit or text becomes too small to read while driving, enter the old value again and reboot; nothing else changes.

Labels vary between firmware versions. Reconstructed screen, labels may differ by firmware.

A Geely Atlas owner who changed Smallest width to 800 reported that touch stopped dropping out, the box ran stably and cooler, and it held 40–50 °C with an extra heatsink. A TBox Ambient owner on the same car set the same value and his touchscreen stopped freezing. The asker who started that thread had been seeing 70–80 °C on July 2024 firmware.

It did not work for one owner: whatever he typed, the value stayed at 484. On some Carlinkit firmware the value follows the split-screen ratio set in the factory menu and resets when the output resolution changes, so if it will not stick, check those settings in the engineering codes reference first.

Switch the box from CarPlay to Android Auto

  • Safe
  • Time: 10 minutes
  • Worked for 2 of 2 reports
  1. Check that your head unit supports Android Auto: a phone connected by cable shows it.
  2. Switch the box’s protocol from CarPlay to Android Auto, as described in switching the box protocol.
  3. Reconnect and test touch response and smoothness.
  4. If callers hear an echo afterwards, pair your phone to the head unit directly for calls.

A TBox Plus owner in a Haval F7x found CarPlay mode laggy at times. After switching to Android Auto, updating the firmware and setting the box’s resolution option to its maximum, touch responded instantly; those three changes happened together, so this counts as one report. A Picasou 3 owner with a large display said Android Auto felt livelier: the resolution dropped slightly, but the picture refreshed faster.

Two caveats from the same threads. The Haval owner’s callers began to hear an echo, which the forum advice was to fix by connecting the phone to the car directly for calls. And a head unit without Android Auto cannot use this at all; one Picasou 3 owner was stuck on CarPlay for that reason.

Things to try (unverified)

  • Use the car’s own system for the heavy work. The Atlas owner who gave up on a TBox Plus improved the car’s native head unit instead and added a separate GPS receiver and a mobile router. It is an honest option when the box cannot keep up, but it is a project, not a setting.
  • Choose a faster box for a very large screen. One owner with a 30-inch 6K display in an Exlantix ET8 was advised that a TBox Ultra 3 or 4 should work, but had not tested it. If you are buying for such a car, ask for a return option.
  • Cut the app load. Fewer apps running at once leaves more of the processor for the display. Still hot with a cooler shows how owners found the app that was pinning the processor.

If nothing works

Note the head unit’s screen size and resolution, the box model and firmware date (Settings → About), the protocol you use, and record a short video of the lag or touch dropout with the temperature readout visible (how to show it).

Send that to the seller or the manufacturer (Carlinkit: [email protected]; Ottocast: [email protected]) and ask whether the model supports your display’s resolution. If it does not, a faster box or the car’s own system is the honest answer; start here explains how the families compare.

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 4 community reports on Carlinkit TBox Ambient, Carlinkit TBox Plus, Ottocast Picasou 3.
  • 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.