Skip to content
AI Box Fix

Apps & launchersReviewed

Launcher or App Doesn't Open When the Box Starts

Box boots to the stock home screen instead of CarCar or Agama? Tap Always to make it default, or use App launch. TBox Ambient, Ultra, ApplePie UX999.

Illustration: Carlinkit TBox Ambient on a car's console at night

Quick answer

When a Carlinkit TBox Ambient boots to its stock home screen instead of CarCar Launcher, make CarCar the permanent default: tap Always in the home-app chooser and take it out of the box's start-up list. Two owners confirmed this. On an ApplePie UX999 Ultra with Android 16, add the launcher to boot-up run in ApplePie settings.

Symptoms

  • The box's stock home screen comes up at every start, and your launcher appears only after you press home or tap its icon
  • Android asks which home app to use every time the box boots
  • Your launcher keeps reloading after start-up instead of settling on its home screen
  • On a TBox Ultra, CarCar starts behind the stock screen, as if in the background
  • After the Android 16 update on an ApplePie UX999 Ultra, Agama no longer opens by itself
  • On an Ottocast Picasou, MultiPlay opens over your launcher at every start

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

When the box finishes booting, Android opens whichever app is set as the default home app. Carlinkit boxes add a second switch on top of that: a start-up slot in the box’s own settings that opens a chosen app after every boot. If the launcher was never saved as the default, Android falls back to the stock home screen; if it sits in both places, the two can compete, and the launcher reloads or the chooser keeps coming back.

A third cause is the firmware itself. Older TBox Ultra builds started the stock shell first whatever you chose, and on an ApplePie UX999 Ultra the Android 16 update made third-party launchers depend on the box’s own boot-up list. Those need the device-specific fixes further down.

If the box gets stuck on a “Loading phone” screen after you install a launcher, that is a different fault with its own fix: see stuck on “Loading phone” after installing a launcher.

Fixes, ranked

Make the launcher the permanent default home app

  • Low risk
  • Time: 5 minutes
  • Worked for 2 of 2 reports
  1. Open Settings → Other parameters → App launch on the box and set it to None if your launcher is listed there.
  2. Press the home button. When Android asks which home app to use, select your launcher and tap Always, not only the launcher’s name.
  3. If no chooser appears and you use CarCar Launcher, open CarCar’s settings, tap its version number, and choose the option to make it the default at the bottom of the menu that opens.
  4. Reboot the box and check that the launcher comes up by itself.

Tapping only the launcher’s name in Android’s chooser uses it once; tapping Always saves it. A TBox Ambient owner whose CarCar kept loading after a factory reset on the latest firmware was told exactly that, and also not to put it in the start-up list. He removed it from autostart, found the option, and the launcher settled. A CarCar 3.0.3 user who wanted it to start with the box used the make-default option under the version number and confirmed it worked.

The same applies to Agama, Nova and other launchers: Android’s default home app setting is under Settings → Apps → Default apps → Home app (Settings → More → Apps on some firmware).

Still the stock screen first: set the launcher in App launch

  • Low risk
  • Time: 2 minutes
  • Worked for 1 of 2 reports
  1. Make sure the launcher is already the default home app (Fix 1).
  2. Open Settings → Other parameters → App launch. Newer firmware calls it Settings → Other → App loading.
  3. Choose your launcher and reboot.
  4. If the launcher now reloads or the chooser pops up at start, set App launch back to None.

A TBox Ambient owner whose box always opened the stock launcher first, with CarCar only after a tap in the corner, was told to update the firmware; he was already on the latest over-the-air build. Setting App launch to CarCar fixed it, and a reply agreed it had been a setting, not the firmware.

It did not help on a TBox Ultra before the 26 Dec 2025 firmware: there the launcher loaded in the start-up slot but stayed behind the stock shell, as if in the background. On current Ultra firmware the community FAQ asks for App loading to be set back to None; the Loading phone guide covers that update. Anything left in this slot opens at every boot, so do not use it for a second app; if Google Play opens at every start, that is the setting to clear, as described in the Loading phone guide.

TBox Ultra on older firmware: press Home automatically at boot

  • Low risk
  • Time: 15 minutes
  • Worked for 1 of 1 report
  1. Set CarCar (or your launcher) as the default home app as in Fix 1.
  2. Install the automation app MacroDroid from the app store on the box.
  3. Create a macro with the trigger Device boot and an action that presses the Home button or opens the home screen.
  4. Save it, reboot, and check that your launcher comes to the front.

On Ultra builds older than 26 Dec 2025 the stock shell always starts first, and pressing Home then brings up the default launcher. One Ultra owner automated that press with a macro and reported that it works. If your Ultra can take the 26 Dec 2025 firmware or later, updating removes the cause; the firmware update guide explains how, and setting the stock launcher before an update avoids trouble during it.

If the macro fires before the stock screen has finished loading, add a short delay to it. Nobody has reported which value works best.

ApplePie UX999 Ultra on Android 16: add the launcher to boot-up run

  • Low risk
  • Time: 5 minutes
  • Worked for 1 of 1 report
  1. Open the ApplePie settings app on the box.
  2. Find the start-at-boot option; owners describe it as Bootup run or similar.
  3. Add your launcher (for example Agama) to it.
  4. Reboot and check the launcher opens by itself.

After updating a UX999 Ultra to Android 16 and Agama to 5.0.4, one owner found the launcher no longer started at boot although everything was set. A reply explained that on Android 16 third-party launchers do not start without being added to the box’s autostart; after adding it under the boot-up option, it worked. Another Ultra owner on Android 16 has a third-party launcher that starts without this step, so not every unit needs it.

Two launchers installed: remove the one you do not use

  • Low risk
  • Time: 5 minutes
  • Worked for 1 of 1 report
  1. Open Settings → More → Apps → Default apps → Home screen and note which launcher is selected.
  2. Uninstall the other launcher app you no longer use.
  3. Reboot and check that the launcher you chose comes up.

A TBox owner who could not find the home-screen choice in either settings menu was given that path, then uninstalled a second launcher app he had, and the chosen one worked at once. Note that the paid app called Car Launcher is a different product from CarCar Launcher, as the CarCar team pointed out in the same thread; if you have both, they compete for the home screen.

Ottocast Picasou: MultiPlay pops up over CarCar at every start

  • Low risk
  • Time: 5 minutes
  • Worked for 1 of 1 report
  1. Disconnect your phone from the box completely.
  2. Open the MultiPlay app.
  3. In its settings, untick automatic connection.
  4. Reboot and check that CarCar stays in front.

When the phone connects by itself at start-up, MultiPlay opens its CarPlay screen over whatever launcher you set. One Picasou owner with CarCar in the start-up slot unticked auto-connect as a reply described and reported that MultiPlay no longer popped up. You then start the phone connection from MultiPlay when you want it.

CarCar stopped opening by itself: reinstall it

  • Low risk
  • Time: 10 minutes
  • Worked for 1 of 1 report
  1. Uninstall CarCar Launcher.
  2. Install it again with its official installer from Google Play.
  3. Set it up again: default home app (Fix 1) and its own start options.
  4. Reboot and check that it opens by itself.

A TBox UHD owner using Android Auto mode found that neither CarCar nor its preset opened at start any more. Reinstalling CarCar 3.0.3 and setting it up again brought the autostart back. Reinstalling resets the launcher, so check its licence afterwards as described in CarCar Launcher licence after a reset.

Things to try (unverified)

  • Update the firmware on a TBox Plus with Android 13. The CarCar Launcher FAQ says the stock launcher can start first on some older Plus builds even when CarCar is the default, and that the latest firmware fixes it. No owner reported the result; the details are in the Loading phone guide.
  • Clear the launcher’s cache and data and set it up again. Suggested to a TBox Ultra 2 owner whose stock screen seemed to appear first; he did not report back. If you use CarCar, check its licence afterwards: see CarCar Launcher licence after a reset.
  • An app other than the launcher should start at boot. Navigation, music or speed-camera apps have their own start-at-boot options, which often need Android’s background permission for the app as well. Set them one at a time and reboot between changes: a misbehaving app set to start with the device can stop the box from booting.

If your launcher does open but signs you out of apps as it starts, that is a timing problem with its own fix: see apps log out when the launcher starts.

If nothing works

Record a short video from power-on to the first screen, and note the box model and firmware date (Settings → About), the launcher’s name and version, what App launch is set to, and which home app Android lists as default. If you recently changed the protocol, note that too, because in Android Auto mode some head units wait for you to open the tile; AI box slow in CarPlay mode lists what else changes between the two modes.

For launcher-specific problems, the launcher’s developers are the right contact; for a box that ignores the default home app on current firmware, write to the manufacturer (Carlinkit: [email protected]) with the video. If you are weighing a box whose stock interface you like better, start here.

What owners said

“I did it with MacroDroid. The problem was that the stock shell (QuickStep) starts, but when you press Home, CarCar loads automatically. So I made MacroDroid emulate a Home press when the device boots. It works.”
Worked: Automation app presses Home at boot
Owner, Dec 2025
“Reinstalled CarCar 3.0.3 (on a Carlinkit TBox HDMI, the box connects to the car through Android Auto). […] Set up a Neutron Player + clock preset. And the autostart of CarCar and the preset WORKED. That problem was solved.”
Worked: Reinstall CarCar Launcher
Owner, Carlinkit TBox UHD, Oct 2025
“I have the latest firmware, which came straight over the air to the Ambient. […] I've just beaten it: I had to go into 'Other parameters' and change 'App launch' there to CarCar.”
Worked: App launch set to CarCar
Owner, Carlinkit TBox Ambient, Nov 2023

Quotes are translated where needed and shortened ([…]); names are removed. Full counts are in the evidence table below.

Questions owners ask

Should my launcher be the default home app and in App launch at the same time?

Usually not. One owner whose CarCar kept reloading at start-up fixed it by taking it out of the start-up list and tapping Always. Use App launch only when the default is set and the stock screen still comes first.

Why is the make-default button greyed out in CarCar?

A reply in the launcher's community explained that it is greyed out because CarCar already is the default. If the stock screen still appears first, look at the box's start-up setting or its firmware instead.

Can an app set to start at boot stop the box from starting?

It can. One TBox UHD owner set a speed-camera app to start with the device and the box then rebooted before he could reach Settings. He needed a reset method that does not go through the menu; ask the manufacturer's support for it.

The box shows nothing until I tap the Android Auto tile. Is that the launcher?

No, that is the protocol. In Android Auto mode many head units wait for you to open the tile, while in CarPlay mode the box usually comes up by itself. Owners in an Exeed and a Citroen reported exactly that.

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 8 community reports on Carlinkit TBox Ambient, ApplePie UX999 Ultra, Carlinkit TBox UHD.
  • 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 (8 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.

CaseConfirmed onResultSource
case-8130Carlinkit TBox Ambient1 worked, 1 did notOwner discussion threads, 9 messages
case-8131Model not stated1 workedOwner discussion threads, 6 messages
case-8132Carlinkit TBox Ambient1 workedOwner discussion threads, 6 messages
case-8133Model not stated1 workedOwner discussion threads, 2 messages
case-8134ApplePie UX999 Ultra1 workedOwner discussion threads, 7 messages
case-9760Model not stated1 workedOwner discussion threads, 5 messages
case-9761Model not stated1 workedOwner discussion threads, 3 messages
case-9763Carlinkit TBox UHD1 workedOwner discussion threads, 2 messages