ADB, root & tinkeringReviewed
Control the AI Box Remotely With AnyDesk Without Constant Prompts
Set up AnyDesk on a Carlinkit TBox for unattended access: stop the screen-recording prompt over ADB or USB debugging, and make the picture appear.
Carlinkit TBox PlusCarlinkit TBox Ambient
Quick answer
On a Carlinkit TBox, Android's screen-recording prompt on every AnyDesk session stops once you grant AnyDesk the PROJECT_MEDIA permission over ADB; two owners confirmed it, and it must be re-run after any reflash. Granting AnyDesk 'display over other apps' then makes the picture appear without touching the box.
Before you start
- AnyDesk installed on the box, with an unattended-access password set
- A way to reach the box over ADB (a wired connection, or Wireless debugging)
- Developer options available on the box (Settings → About, tap the build number)
- The computer or phone you will connect from, on a network the box can reach
Time: about 30 minutes. Tools: AnyDesk (on the box and on your computer or phone), Android SDK Platform Tools (adb), AnyDesk control plugin.
Applies to
- Connection to the car
- CarPlay and Android Auto
- Highest risk on this page
- Advanced
What unattended AnyDesk needs on an AI box
AnyDesk can show and control these boxes from a computer or phone, but Android gets in the way of leaving it unattended. Two things break a hands-off connection: Android asks you to allow screen recording at the start of every session, and the picture does not come up on its own until AnyDesk is opened on the box. Both are permission problems, and owners solved both.
A third problem comes first for some boxes: you connect, you see the screen, but taps and swipes do nothing. That is AnyDesk missing its control add-on, not a permission. Install that before you worry about the prompts. The steps below go in the order you would set the box up: app and plugin, then the screen-recording prompt, then the picture.
If you have never opened ADB on one of these boxes, enable ADB on an AI box covers the wired and Wireless debugging routes, and the ADB cheat sheet lists the commands. For getting around the box day to day without the touchscreen, see control the AI box without the touchscreen.
Steps
Install AnyDesk and its control plugin so taps work
- Low risk
- Time: 10 minutes
- Worked for 1 of 1 report
- Install the AnyDesk app on the box. Sideloading apps onto a box is covered in install an APK on an AI box.
- When AnyDesk says a plugin is needed for remote control, install the control add-on it offers for your device and enable it. AnyDesk publishes these control plugins itself; use the one AnyDesk points you to, not a repackaged file from elsewhere.
- Open AnyDesk’s settings on the box and set an unattended-access password, so a remote session can start without someone pressing Accept on the box.
Without the control plugin the session is view-only. One owner on an ApplePie UX999 running Android 13 could see the screen over both AnyDesk and TeamViewer but could not click or move anything; once the right control plugin was installed, control worked for him. If you only ever need to watch the screen, you can skip the plugin, but then you cannot operate the box.
Stop Android asking to record the screen every session
- Advanced
- Time: 15 minutes
- Worked for 2 of 2 reports
Warranty warning: this uses developer or engineering access. Follow the undo steps afterwards; some sellers refuse warranty claims on units with debugging left enabled.
- Connect to the box over ADB, wired or through Wireless debugging.
- Grant AnyDesk the screen-capture permission:
adb shell appops set com.anydesk.anydeskandroid PROJECT_MEDIA allow- Start an AnyDesk session and confirm the “allow screen recording” prompt no longer appears.
- Run the same command again after any firmware reflash: a reflash clears the grant.
Two owners on the Carlinkit TBox confirmed this. One ran it over a wired ADB connection and reported it working perfectly; he noted the command has to be entered again after every reflash and keeps it written down. The other also added his home Wi-Fi network to the box afterwards, so now the box connects on USB power at home and he reaches it over AnyDesk, while CarPlay still starts normally in the car with no switching back. The command can be run from a computer in ADB mode or from an ADB shell on a phone over Wireless debugging; the box does not need root.
Or stop the prompt by turning on USB debugging
- Advanced
- Time: 5 minutes
- Worked for 1 of 1 report
Warranty warning: this uses developer or engineering access. Follow the undo steps afterwards; some sellers refuse warranty claims on units with debugging left enabled.
- Open Developer options on the box. If they are hidden, open Settings → About and tap the build number until the box says you are a developer.
- Turn on USB debugging.
- Start an AnyDesk session and confirm the screen-recording prompt no longer appears.
One owner on a TBox running Android 13 could not get the PROJECT_MEDIA command to run (his ADB shell returned an error), and the wireless-ADB apps he tried wanted root. Turning on USB debugging on the box stopped the screen-recording prompt on its own, with no root and no command. Try this first if you are on Android 13 and the command route is giving you trouble.
Make the picture appear without tapping the box
- Low risk
- Time: 5 minutes
- Worked for 1 of 1 report
- On the box, open Settings and find AnyDesk’s permissions.
- Turn on Display over other apps (also shown as “Appear on top”) for AnyDesk.
- Start a remote AnyDesk session and confirm the picture comes up without anyone touching the box.
Until this permission is granted, the box stays blank on the remote side until AnyDesk is opened on the box itself, which defeats unattended access. The same Android 13 owner above found that granting AnyDesk permission to display over other apps was the last step: after that, everything worked.
Verify it worked
From the computer or phone, disconnect any open session and start a fresh AnyDesk connection to the box without touching the box:
- The session connects using your unattended-access password, with no Accept prompt on the box.
- No “allow screen recording” dialog appears.
- The box’s screen shows on its own, before anyone opens AnyDesk on the box.
- Taps and swipes from your side move things on the box.
If all four hold, the box is reachable unattended. In the car, connect in your usual protocol and confirm the head unit still shows the box; none of these changes take the USB port out of car mode.
Undo / rollback
To return the box to asking for consent each session and to close remote access:
- Reset the screen-capture permission with
adb shell appops set com.anydesk.anydeskandroid PROJECT_MEDIA default, or turn USB debugging back off if that was the route you used. - Turn Display over other apps off for AnyDesk if you no longer want it starting on its own.
- Remove the unattended-access password in AnyDesk, or uninstall AnyDesk and its control plugin.
- Switch Wireless debugging off in Developer options if you turned it on.
Troubleshooting this guide
The command returns an error. Running adb shell appops … from a phone’s ADB shell app has failed for owners where the same command worked from a computer in ADB mode. Connect a computer over ADB and run it there, or use the USB-debugging route above instead.
You can see the screen but cannot tap anything. The control plugin is missing or disabled. Install the control add-on AnyDesk offers for the box and enable it, as in the first step.
The picture is still blank until you open AnyDesk on the box. The “display over other apps” permission is not on. Grant it to AnyDesk, not only to its plugin.
There is no sound over AnyDesk. Owners reported AnyDesk’s audio did not come through on these boxes: in the AnyDesk profile, with Full Access set, the sound permission stayed inactive. Treat AnyDesk here as screen-and-control only.
The car says “device not supported” after you worked over ADB. If you used a wired ADB connection and the box will not talk to the car afterwards, it is still in ADB mode. The device not supported after ADB fix walks you back. The Wireless-debugging and USB-debugging routes leave the USB port in car mode, so they avoid this.
Nothing connects and you need the box set up today. You can configure the box on your desk with Android’s Desktop Head Unit instead, which needs neither AnyDesk nor ADB.
What owners said
“I just took the test! It worked 100%, I appreciate your help.”
Owner, May 2024
“It worked. I also added my home network manually. Now I come home, plug it into USB power and connect over AnyDesk.”
Owner, Feb 2024
“I turned on USB debugging on the box and it did the trick: no more screen-recording prompt.”
Owner, Oct 2023
Quotes are translated where needed and shortened ([…]); names are removed. Full counts are in the evidence table below.
Questions owners ask
Do I have to run the PROJECT_MEDIA command again after a firmware update?
Yes. A reflash clears the permission, so run adb shell appops set com.anydesk.anydeskandroid PROJECT_MEDIA allow again afterwards. One owner keeps a note of the command for exactly this reason.
Why can I see the box over AnyDesk but not tap anything?
AnyDesk cannot send taps on Android without its control add-on. Install the control plugin AnyDesk offers for the box and enable it; one ApplePie UX999 owner had control working only after that.
Does AnyDesk sound work on these boxes?
Owners reported it did not. In the AnyDesk profile, with Full Access set, the audio permission stayed inactive, so treat AnyDesk on these boxes as screen-and-control only.
Can I leave the box reachable at home while CarPlay still works in the car?
Yes. One owner added his home Wi-Fi to the box, so it connects on USB power at home for AnyDesk, and CarPlay still starts in the car with no switching back.
Related fixes
- Enable ADB on an AI Box (Ottocast Port 65535): 25 Owner ReportsAdvanced
- Control an AI Box Without a Touchscreen: 28 Owner ReportsLow risk
- Install an APK on the Box: Transfer, File Manager, InstallerLow risk
- Set Up an AI Box on the Desktop Head Unit: 11 Owner ReportsAdvanced
- Enable Multitouch Pinch-Zoom on TBox Ultra, Plus and AmbientBrick 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 5 community reports.
- 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-1228 | Model not stated | 1 worked | Owner discussion threads, 1 message |
| case-1229 | Model not stated | 2 worked | Owner discussion threads, 2 messages |
| case-1230 | Model not stated | 1 worked | Owner discussion threads, 1 message |
| case-1231 | Model not stated | 1 worked | Owner discussion threads, 1 message |