Install Android Auto / Waze on R-Link 1

Last update: August 19th, 2018

 

The handling below may irreparably damage your vehicle, if you are not sure what you are doing do not do the handling. The site can not be held responsible.
This manipulation is a hack, it is not official, you can not get help from Renault if it goes wrong. Moreover on the R-Link 1, the USB socket does not deliver enough power, it can cause bugs.
Why the first R-Link 1 are not compatible with Android Auto? R-Link 1 was introduced in 2012, at that time neither Android Auto nor Carplay existed since they were presented in June 2013 and 2014. But whether it’s Google or Apple, there are hardware requirements that are imposed on car manufacturers. It was therefore not possible for Renault to integrate and deploy them on the first versions. It was therefore necessary that Renault slightly change its hardware on the R-Link 1 released in 2017 knowing that the validation of the evolutions is a process much heavier in the automobile than in the world of the smartphone for example in particular because there is security issues. . This explains that even if it’s frustrating I grant you





Internet is incredible, smart guys have found a way to install Android Auto on all Renault R-Link 1 marketed even the first. As it’s a little mess on the web, so I compiled all the info. No need to ask your garage Renault to do so, its computer equipment is not able to activate the function.

Interested? follow the guide!

To enable smartphone replication (Android Auto / Apple Carplay) on R-Link 1 there are some prerequisites:

  • Own the latest software version of R-Link 1 ( see this page )
  • Have an ELM interface (all are not compatible, those are recommended) with the 25k80 chip.





The very first thing to do is to modify the ODB extension. Why? The interface is made to work on the classic CAN of the vehicle so pins 6 and 14. But the calculator of R-Link 1 is on a secondary CAN (12 and 13).

So you have to change the extension to get the following situation:

  • pin 6 ELM side to pin 13 OBD side
  • pin 14 ELM side to pin 12 OBD side

Once all this is done let’s start.

Install the DDT4all application on your computer.

Download and install the drivers for the interface ( see this page ). On Windows 8 and 10, you may use this method to install the drivers.




Copy the DDT2000 database to the C: \ Program Files (x86) \ ddt4all directory.

Start DDT4all and check that the interface (connected) is detected by appearing on the first window.

If the interface appears well, you can go to the vehicle and connect the probe to the ODB socket of the vehicle using the extension . To find out where your ODB socket is, you can visit this site.

Select your interface, check the box as you are aware that you should not do anything and select “connected mode”.

Activate the Expert mode (Einstein icon at the top), then select the after sales mode from the drop-down menu.

  • Select your vehicle.
  • Choose MFD 4.6
  • Choose from Screens: 13 – ECU configuration ADAS. ..
  • Choose the Screen tab at the top.




On the main screen choose the following options:

  • SPVR for iPhone: Present (to use SIRI with a long press on the voice command button just in Bluetooth even if you do not have Carplay)
  • Android Auto feature: Present
  • Mirror Link feature: Not Present
  • MW activation: Not Present (if you want to disable these radio bands so that they do not appear anymore)
  • LW activation: Not Present (if you want to disable these radio bands so that they do not appear anymore)
  • SPVR for others Phones: Present (to get the Google Voice Assistant just in Bluetooth even without plugging in and running Android Auto).

Then you just have to click on WRITE ECU Config (the big yellow button) at the end of the modified lines.

On the lower part you will see the frames of writing scroll. Once that’s good you can restart the R-Link 1 by pressing the Home button 5 times.




The feature is now activated! You can benefit from Google Maps, Waze directly on R-Link 1.

Here’s what it makes in a Megane 3.

Note that the Joystick is perfectly taken into account just as shortcuts Maps / Audio / Phone …

However, USB plugs do not provide enough power to charge the phone, so some phones may discharge slightly. The discharge is more pronounced when using Android Auto in the foreground than in the background. For example using Deezer via Android Auto and the classic navigation of the R-Link I noticed that it worked well!




To use the voice command of Android Auto, it will be necessary to make a long press on the button. She is damn good.

This is a manipulation that offers new possibilities to R-Link 1! I adopted it on my Mégane 3, and use it daily for Deezer!

Enjoy! 😉😎

18 Responses to “Install Android Auto / Waze on R-Link 1

  • Sergiu Miclea
    7 months ago

    Thank you so much for this article. Do you have a picture of modified OBD extension or a more detailed explanation on the whole process for doing that?

  • I’m curious if you’ve tried the SPVR for iPhone option. I’ve enabled it but the voice button doesn’t activate Siri, but if I press and hold the button on the iPhone it does activate as if expect.

  • Hey Sergiu,
    I’m yet to do it, but have just bought on ebay:
    16 Pin OBD2 Male To Female extension cable – 30cm length

    I plan on just splicing the 2 wires that need changing – seems like the easiest option to me.

  • Richard ten Velde
    4 months ago

    would it not be an option to use an Y-cable for usb power (just like you would use for a portable hard drive) to add power from a 12 v charger?

  • Hi I have followed the guide step by step, I have rewired an extention cable (soldering etc) and did pin by pin continuity testing to ensure that the cables are connected correctly and I cannot enable android auto on my head unit….

    I can see the settings and change them and write them on DDT4all but the settings will not get written…. Not sure what I am doing wrong…. I have tried with the RLINK unit on & off – no difference and I cannot think of anything else to do…

    Any ideas?

  • All I am getting back is:

    ECU uses SDS 10C0
    Sending request :StartAfterSalesSession
    Delay 50 ms
    Switching to session mode 10 C0
    Sending request :DataWrite.ECU
    Delay 250 ms
    Sending ELM request:2E 6C 1C E4
    ELM response :
    Sending request :StartDiagnosticSession
    Delay 250 ms
    Switching to session mode 10 81

    And nothing happens… Could you please let me know if anyone has seen similar behaviour from the RLINK1 head unit? Any ideas….

    • I have the exact same problem. Also, the DDT4All tool shows NO DATA in the right purple column so maybe it cannot read the RLink? Did you manage to get it fixed?

  • Hello,

    I was wondering if this ‘hack’ fully enables CarPlay for iPhone or does it only support the Siri voice control?

    Regards,

    JeePee

  • bonjour pouvez vous me dire quelle est la derniere version du R Link1
    je possede actuellement la version 11.336.2194669-7053

  • hello can you tell me which is the last version of the R Link1 I currently have version 11.336.2194669-7053

  • Hi, I tried it with the advertised obd usb connector (ordered over amazon.de). I also rewired the extension (tested the connections with a line tester). When trying to run the Write ECU Config I get the following error messages:

    Sending request :DataWrite.ECU
    Delay 250 ms
    Sending ELM request:2E 6C 1C E4
    Bad ELM response : WRONG RESPONSE CFC0 Unknown
    ELM response : WRONG RESPONSE CFC0 Unknown
    Sending request :StartDiagnosticSession
    Delay 250 ms
    Switching to session mode 10 81
    Bad ELM response : WRONG RESPONSE CFC0 Unknown

    It keeps repeating the Bad ELM response line.

    Also tried the ELM benchmark from the ddt4all launch window which resulted in the all tests failing.

    Incompatible adapter on ARM core
    Result: 0 succeeded from 95
    ELM Max version:

    Did I maybe just get a bad OBD to USB connector or am I doing something wrong?

    • Ivo Tavares
      2 months ago

      hello,

      I have the same problem.

      Do you have a fix?

      Please anyone can help?

      Thank you.

  • barbieru Petrica
    2 months ago

    Same problem i encounter. Do you found a fix?

  • Hi guys! Recently I succesfully activated Android Auto on Rlink1. If you have android phone, download app ELM327 identifier, connect phone to OBD (you have to plug it into car socket) and run app. It will show you which commands are supported. I was able to succesfully operate within ddt4all with module, which supports all commands from v1.0 to 1.4 of ELM327. I had also several others which I was not succesful with. They supported only few of commands (usually acceptable for classic dashboard screen).

  • Followed the procedure, and… THA DHAAA! worked, thanks for sharing. The challenge i have is that i can only connect via MirrorLink but not on Android Car! tried different phones (different android versions) all are sporting the same behaviour. Any idea?
    Thanks,
    Serban

  • THEOFILOS KIRKMALIS
    3 weeks ago

    I own a Renault Clio IV 2018 model but it came with Media Nav Evolution 9.1.3. Can the procedure described above been applyed on Media Nav or is it only for R-Link cars? Thanks a lot.

Leave a Reply Text

Your email address will not be published. Required fields are marked *