Start Here: AI Box Families and What Breaks Most

An AI box is a small Android computer that plugs into your car’s USB port. The car’s screen treats it like a phone running CarPlay or Android Auto, but the apps run on the box itself, with its own Wi-Fi, Bluetooth, storage and usually a SIM slot. That is different from a wireless CarPlay or Android Auto adapter, which only cuts the cable between your phone and the car.

This page is an orientation, not a ranking. It groups the boxes this site covers into families, lists what goes wrong most often in each family according to the community reports behind our articles, and points to the hub pages where the fixes live. Terms you do not know are in the glossary.

Does your car support the box at all?

Every AI box needs the car to support wired CarPlay or wired Android Auto; the box pretends to be a phone plugged into that USB port. Check your car before anything else:

• Plug in a phone with a cable. If CarPlay or Android Auto starts, your car speaks that protocol.
• Most boxes can present either protocol and switch between them with a button. If your car supports only one, set the box to that one, or the car will not see it. See switch between CarPlay and Android Auto.
• Some boxes need Android Auto in the car. The MGears Mstick4 works only with Android Auto: in a car that has CarPlay but no Android Auto, it does not work at all.
• Cars with only wireless CarPlay, common on recent BMWs, need a box that can connect to the car wirelessly. Among Carlinkit boxes that means the TBox Ultra 3 or Ultra 4.

Which family is your box?

Family	Models	Chip and Android	Hub
Carlinkit TBox	TBox Plus (EM 668 / EAU 138), TBox Ambient, TBox UHD; older TBox V3 and Mini	QCM6125, SM6225 or SDM660; Android 11 to 13	TBox Plus, TBox Ambient, TBox UHD
Carlinkit TBox Ultra	Ultra (1), Ultra 2, Ultra 3, Ultra 4	SM6350; Android 15	TBox Ultra
Ottocast	Picasou 3, Picasou 3 Lite, Picasou 3 Pro, OttoAibox Nano; older Picasou 2	Picasou 3: Android 12 (QCM6125, per owners); 3 Pro and Nano: SM6225, Android 13	Picasou 3
MGears	Mstick4	Android Auto only	Mstick4
ApplePie (UX999)	UX999 Rocket; also Plus 2.0, Ultra, Ultra 3.0	QCM6490 or QCM4490 on the Rocket	UX999 Rocket

Not sure which Carlinkit you have? Which TBox do I have tells them apart from Settings → About, the case and the lights. Ownice boxes share several menus and fixes with the Carlinkit TBox family; Ownice uses engineering code 1260 where Carlinkit uses 4545.

What breaks most often on each family?

The counts below come from the community cases our articles are built on. They show where owners asked for help most, not how reliable one box is compared with another: popular boxes produce more reports.

Carlinkit TBox Plus, Ambient and UHD

• Firmware updates. The most common category. Updates fail on a corrupt download or the wrong card format, a third-party launcher set as default can reset or brick the box during an update, and 2026 builds made the TBox Ambient forget its SIM card after the first boot. Start with update TBox firmware with FOTA and set the stock launcher before an update.
• Sound. Crackling or muffled audio has the most confirmed reports of any single problem; the fix is usually turning off voice-assistant hot-words. See crackling or muffled sound.
• Apps and launchers. “Loading phone” forever after installing a launcher, split screen, and a YouTube playback error wave in September 2026. See third-party launcher stuck on “Loading phone”.

Carlinkit TBox Ultra 1–4

• Firmware and recovery. Update failures, a black screen after boot on the Ultra 4, and QFIL recovery when a box no longer starts. See “Upgrade failed” on TBox Ultra and the firmware tracker.
• Power and connection. Reboots under load, with a SIM inserted or after app updates, usually because the car’s USB port cannot supply enough current. A Y-cable stopped the reboots for seven of the nine owners who reported back: AI box keeps rebooting. On one Ultra 2, Android Auto mode did not connect to the car until an August 2026 build.
• Heat. The Ultra runs warm, and owners add coolers. See overheating shutdowns.

Ottocast Picasou 3, 3 Lite, 3 Pro and Nano

• Heat. The most reported topic: owners measured high CPU temperatures on the Picasou 3 Pro without extra cooling. See Picasou 3 Pro CPU monitor and cooling.
• Connection drops when the box joins a phone’s hotspot, and reboots when mobile signal drops, are reported but have no confirmed fix yet.
• Hidden developer options. Enabling ADB takes a hotspot-and-port method rather than a menu code; see the ADB cheat sheet.

MGears Mstick4

• Car compatibility. It needs Android Auto in the car; CarPlay-only cars are not supported.
• “Connection interrupted” with some head units, often cleared by another cable or a reset of the car’s Android Auto settings. See Mstick4 connection interrupted.
• Recovery and updates go through MGears’ official Recovery Tool; VW MIB 2.5 cars needed a specific compatible build.

ApplePie UX999

• Reboots with a SIM or weak signal, the same power pattern as other boxes: see AI box keeps rebooting.
• Big firmware jumps. Some UX999 models moved to Android 16 in 2026; that update resets the box to factory settings.

Before you change anything

Three habits prevent most of the problems above:

1. Note your model and firmware date from Settings → About, and photograph your engineering-menu settings (engineering codes).
2. Set the stock launcher as default before any firmware update.
3. Give the box steady power. If it reboots when the car’s USB port is under load, solve that first, because it causes failed updates and corrupt settings too.

When something does break, look up the symptom on the fixes page. If nothing there helps, how to report a bug lists what the manufacturer needs and where to send it.