Skip to content
AI Box Fix

Renault R-Link 1 / R-Link 2 / EasyLink / S-Link / reviewed 17 Oct 2026

AI Box on Renault R-Link and EasyLink: Fixes and Quirks

AI box in a Renault with R-Link 2, EasyLink or S-Link: which protocol fills the portrait screen, the R-Link reset, calls, GPS and lag fixes owners found.

What works

On a Renault the first thing to settle is which head unit you have, because they do not all offer the same projection, and the box behaves very differently on each.

  • R-Link 2 (Megane 4, Scenic 4, Talisman, Kadjar, and the Koleos II sold as the Samsung QM6) takes wired CarPlay and wired Android Auto, so an ordinary wired box works. Run it in CarPlay mode. On these portrait screens CarPlay fills the display and is the faster of the two; Android Auto mode gives a shortened picture and lags, which owners describe below.
  • EasyLink (Duster II, Kaptur, Arkana, and the Megane 4 facelift) takes wired projection too. One owner runs an MGears Mstick4 on a single stock cable with the steering-wheel buttons, the steering voice button and calls through the head unit all working.
  • R-Link 1 (Megane 3, Clio 4, Zoe) offers only Android Auto, no CarPlay, it is slow, and owners often cannot get a box to hold the connection at all; see the R-Link 1 section below.
  • S-Link, the Korean head unit in the QM6 / Koleos II, behaves like a fussier R-Link and is covered in its own section.

Owners report working set-ups with the Carlinkit TBox Ambient, TBox Plus and TBox Ultra, the Ottocast Picasou 2 and Picasou 3, the ApplePie UX999 Max and the MGears Mstick4. One Megane 4 owner moved from an Mstick4 to a TBox Ultra 2 in CarPlay mode because it ran at a higher resolution and rebooted cleanly after he reflashed it. A Duster owner’s head unit saw a TBox Ultra at once in both CarPlay and Android Auto.

Known quirks

What owners saw: a TBox Ambient that had worked for four months stopped coming up. The R-Link head unit no longer listed it as a TBox but as an “iPhone”, asked once whether to enable CarPlay, and then never showed the CarPlay button to select the box. Removing and re-adding the device changed nothing, and the box behaved the same in another car.

What fixed it: a full factory reset of the R-Link head unit itself, not the box. One owner reported the CarPlay icon came back and the box has started by itself at every ignition since. He had first wasted half a day resetting, recovering and reflashing the box, none of which helped; a QFIL recovery of the box reported “Download Succeed” and changed nothing, because the fault was in the head unit, not the box.

Reset an R-Link only if you accept the brick risk in the warning above and you use Renault’s own procedure for your car. The general, lower-risk route for a box the car stops seeing is on car doesn’t detect the AI box; if the box lights up but the screen stays blank on an Android-Auto-only R-Link, the case is Carlinkit TBox shows nothing on Renault R-Link instead.

R-Link 2’s screen is portrait, and what fills it depends on the protocol and on the R-Link software version.

On most R-Link 2 cars (owners report it on the Megane 4 and Scenic 4), CarPlay fills the screen and Android Auto does not — the Android Auto picture is shortened. Several owners say there is no need to change protocols on R-Link 2: CarPlay works best, and the box only starts to lag once it is switched to Android Auto. If you do need to switch for some other reason, the button-and-file procedure is on switch the box’s protocol.

One owner on R-Link 2 software 3.3.16 had the opposite trouble: CarPlay filled only half his screen, so he ran the box in Android Auto, and the best result he reached was “a square”. He was told full screen on that build needs a newer R-Link software version flashed with Renault’s dealer tools, which he had not been able to arrange. On a small-screen R-Link the picture always fills, so this is a large-screen problem. The same portrait-screen fight on another make is on AI box stuck in a small window on the F-150.

What owners saw: with the box switched to Android Auto, owners report it crawls — a Scenic 4 owner measured a 10-to-20-second response to taps, a Megane owner found CarPlay about three times faster, and an S-Link (QM6) owner saw the box work badly in Android Auto while CarPlay was fine. No owner reported a fix.

This is the reverse of the usual complaint, where CarPlay mode is the slow one; see AI box slow in CarPlay mode for that case and the general causes. On Renault the practical answer is to stay in CarPlay mode — unless you need Android Auto for calls, which is the next quirk.

What owners saw: R-Link will not keep the phone’s own Bluetooth connection to the head unit while the box is in CarPlay mode, so calls are forced through the box, and owners report being heard poorly on them. R-Link’s own hands-free, by contrast, is good.

What some owners do: switch the box to Android Auto mode, which on some head units lets the box (over the cable) and the phone (over Bluetooth) coexist, so you keep the car’s dialer and microphone. It is not a sure thing — whether the box and the phone’s Bluetooth run at once depends on the head unit — and Android Auto is the slow mode on R-Link, so it is a trade-off, not a clean fix. Keeping calls on the car’s Bluetooth with any box is covered in car Bluetooth calls with an AI box, and poor call audio through the box in caller can’t hear you on calls.

What owners saw: on a Duster II with EasyLink (the same unit fitted to the Kaptur and Arkana), one owner’s head-unit microphone stopped working whenever the box was connected. It worked again as soon as he unplugged the box, and the head unit refused to let him use the microphone while “Android Auto” was connected. No fix was reported.

Separately, an Arkana owner’s hands-free through a TBox Plus stopped after a box firmware update and nobody answered him. If your microphone fails on calls, caller can’t hear you on calls lists the box-side settings to check first.

What owners saw: on a Megane 4 / Scenic 4 with R-Link 2, an Mstick4 rebooted at random on firmware 1.8. Earlier builds had been fine.

What fixed it: updating the stick to firmware 1.9.4. One owner reported no reboots over several days afterward, on the stock cable. A second owner noted he saw no reboots on either 1.8.2 or 1.9.4 using a two-metre cable with a SIM fitted, so a good cable may matter as well. A different Megane 4 Mstick4 fault — the stick not connecting until the head unit’s clock is set by hand — is covered on Mstick4 connection interrupted, and random reboots in general on AI box keeps rebooting.

The box’s screen does not always come up by itself

Several Renault owners find the box does not reappear on its own at every start, and there is no single fix.

  • On a Megane 4, one owner’s box loads from cold but does not restart if the head unit is switched off and on again.
  • On an Ottocast Picasou 2, the owner found whether the box auto-starts depends on the box firmware version.
  • On the Korean S-Link (QM6), one owner gets only a black screen saying the device is connected until he opens and closes the climate menu, after which the box’s interface appears.
  • On the Mstick4, if you unlock the car but do not start the engine straight away, the stick boots before R-Link; when R-Link comes up you tap its Android Auto tile once and the stick is already running, with no reboot or wait.

The start-up options to try — a plug-in delay, plugging in after the head unit has booted — are in car doesn’t detect the AI box after ignition.

Koleos II / Samsung QM6: most boxes connect only every other time

What owners saw: the Koleos II (sold as the Renault Samsung QM6) with R-Link / S-Link is hard to satisfy. One owner tried a TBox Plus 8/128, a TBox Ultra, an Ownice and a UX999 Ultra, all of which connected only every other time, and found that only the ApplePie UX999 Max on Android 10 ran “more or less normally”, with CarCar Launcher as its home screen.

A second QM6 owner with a UX999 Max reported that only the February and April 2023 box firmware builds were stable on his R-Link; newer builds dropped until he restarted the head unit. If a box keeps dropping on a QM6, note which firmware build was stable and hold off on updates until owners confirm a newer one behaves.

What owners saw: R-Link 1 offers only Android Auto, never CarPlay. Owners report the box tries to start, sometimes flashes an Android logo for a moment, and then shows “Android Auto connection error”, or shows nothing at all. One Zoe owner’s box worked perfectly in another car; an ordinary wireless CarPlay dongle works in the same Renault, but the box does not.

The two things worth trying — switching the box to Android Auto mode and adding power to R-Link’s weak USB port — are on Carlinkit TBox shows nothing on Renault R-Link, where these reports are counted. Be honest with yourself about the odds: on R-Link 1 extra power often does not help, and some of these units never ran a box at all.

Other things Renault owners ran into

  • Megane 4, TBox Plus: a box that had worked for a year suddenly only blinked green and was no longer seen; the same owner’s box stopped again after a workshop disconnected the battery terminal. No outcome was reported.
  • Kaptur, UX999: after a box update the DPI jumped, everything shrank, the box kept dropping, the sound was gone and the external buttons died; changing the display mode did nothing, and nobody answered.
  • Kadjar: the volume drops after you select reverse. Owners note this happens with no box fitted, so it is the car, not the box.
  • Navigation-prompt volume: one owner with a TBox Lite S in CarPlay mode cannot set the navigation-prompt volume separately from the music with the car’s volume control — the control moves both at once.
  • Car GPS wrong: an EasyLink owner found the position from the car’s antenna was far off, so he used the stick’s own GPS instead; the box’s own receiver settings are in inaccurate GPS on the AI box.

Before you connect a box

  • Find out which head unit you have. Plug a phone in by cable: if the screen offers CarPlay, you have R-Link 2 or EasyLink and a wired box can work; if it offers only Android Auto, you have R-Link 1 (or an Android-Auto-only EasyLink) and should read the R-Link 1 section first.
  • On R-Link 2, start in CarPlay mode. It fills the portrait screen and is faster. Switch to Android Auto only if you need the phone on the car’s Bluetooth for calls, knowing it will be slower and the picture shorter.
  • Use the cable that came with the box for the first connection, and on R-Link 1 plan on a Y-cable or USB booster for extra power.
  • Do not reach for a full R-Link factory reset lightly. It can brick the unit.
  • Know your box. Which TBox do I have shows how to read the model and chip in Settings → About.

If something breaks

Write down the box model and firmware date (Settings → About), the car model and year, the head unit (R-Link 1, R-Link 2, EasyLink or S-Link) and its software version, the box’s mode (CarPlay or Android Auto), and whether a phone works on the same USB port in the same mode. Note when it fails: every start, only after the head unit was switched off and on, or after an update. A short video of the screen helps.

Send that to the box maker’s support (Carlinkit: [email protected]; Ottocast: [email protected]); how to report a bug has a template. If a phone is also refused on the same port, the head unit is the problem, and on an R-Link 1 that refuses every box the honest answer may be the car’s own projection or a different set-up; start here covers whether a car supports a box at all.

Public sources

Owner reports behind this page that are public and can be opened. Reports from owner forums and chats are kept on file but not linked, to protect owners' privacy.

  1. Reddit thread, Jun 2026: an owner confirms a fix
  2. Reddit thread, Mar 2025: an owner confirms a fix