How to Report an AI Box Bug to Carlinkit, Ottocast or MGears

A bug report that names the box, the firmware date, the car and the exact moment things go wrong gets an answer; “it doesn’t work” gets a form reply. Owners in the community put it plainly: the more people send the same detailed report, the sooner the manufacturer fixes it. This page lists what to collect, how to capture it, and where each brand takes reports.

What should I collect before writing?

Five details make a report usable. Carlinkit, Ottocast and MGears all ask for some version of this list.

1. Box model and variant. For example “Carlinkit TBox Ultra 3” or “TBox Plus EM (668)”. If you are unsure, use which TBox do I have.
2. Firmware date from Settings → About, written out (“26 Dec 2025”). Say whether the problem started after an update, and from which build to which.
3. Car make, model and year, and the head unit if you know it (for example BMW iDrive 6, VW MIB 2.5).
4. Protocol and phone. CarPlay or Android Auto, wired or wireless to the car, and your phone model if a phone connects to the box. MGears and Carlinkit both ask for the phone model.
5. What happens, and how often. The exact steps, what you see, and whether it happens every time, every drive or once a week. MGears’ form asks for the frequency explicitly.

Add what you already tried. Fixes on this site are a good list to work through first, especially AI box keeps rebooting for power and crackling or muffled sound for audio. Saying “a factory reset did not help” saves a round of email.

How do I capture the problem?

Photo or video. Film the car screen and, if relevant, the box’s lights, from power-on until the fault. Keep it short (under a minute) and say in the email at which second the problem appears. Screenshots from the box are fine for menus and error messages.

Settings → About. Take one photo of the whole About screen. It holds the model string, Android version and firmware date in one place.

Logs, if support asks or the fault is intermittent:

• On Carlinkit boxes, turn on the setting that copies logs to the memory card, reproduce the problem, and send the newest files from the logbak folder on the microSD card. Turn the setting off afterwards.
• With ADB, save a log right after the fault happens. The commands are in the ADB cheat sheet:

adb logcat -d -v time > box-log.txt

Logs can include account names and Wi-Fi network names. Skim them before you send, and never post them publicly.

Your modifications. List anything you changed beyond normal settings: engineering-menu options (4545, 166888), third-party firmware, root, multitouch edits, disabled apps, disabled verity. If you can undo them, do so and check the problem is still there. Undo steps are on engineering codes and the ADB cheat sheet.

Where do I send it?

Write to the manufacturer for firmware bugs and warranty, and to the shop you bought from for returns. Use one email per problem.

Brand	Where to report	What they ask for	Notes
Carlinkit (TBox Plus, Ambient, UHD, Ultra)	[email protected]	Product model, firmware version, car model, phone model, description	Monday to Friday, 9:00 to 18:00 (UTC+8). Amazon orders: [email protected]. The same address sends firmware files on request.
Ottocast (Picasou, OttoAibox Nano)	[email protected]	Pre-sales or after-sales questions	Amazon orders: [email protected]. A request form is linked from the contact page; Ottocast aims to answer within 24 hours.
MGears (Mstick4)	The CS Center board on en.mgears.co.kr, or [email protected]	Vehicle brand and model, phone brand and model, the issue, how often it happens	You can attach files to a board post.
ApplePie (UX999), Ownice, Wizcar	The seller you bought from	Same five details	We have not verified an official support address for these brands yet.

Contact addresses checked against the manufacturers’ own pages on 5 Oct 2026. Do not send a box back, or flash recovery files, before support has replied: some repairs depend on the exact variant, and Carlinkit warns that a box flashed with the wrong version may have to be returned for repair.

A report template you can copy

The details below are an example; replace every line with your own.

Subject: [Model] [firmware date] - [one-line problem]

Box: Carlinkit TBox Ultra 3, firmware 14 Sep 2026 (Settings > About photo attached)
Car: 2021 Example Motors Model X, head unit: [system name if known]
Connection: Android Auto, wired to the car
Phone: [brand and model], connected to the box over Wi-Fi
Problem: When a call comes in, I cannot hear the caller. Outgoing calls work.
How often: Every incoming call since updating from 21 Aug 2026 to 14 Sep 2026.
Steps to reproduce: 1. Start the car. 2. Wait for the box to connect. 3. Call the phone from another number.
Already tried: reboot, factory reset, switching protocol. No change.
Modifications: none (or: ADB used to disable the floating button, now re-enabled).
Attachments: 40-second video (problem at 0:25), About screen photo, log file.

Fill in your own details. Keep the subject line specific so it can be matched with other owners’ reports of the same fault.

Will anyone else see my report?

Your email to the manufacturer is private. If you also want to help other owners, send the same details to this site: reports are how fixes get confirmed and ranked here. Use the form at the end of any fix article or the contact page. We do not publish names or contact details. For the overall picture of which problems are most common on each box, see start here, and for builds that already fixed your problem, the firmware tracker.