Same problem here with Skoda Superb.

I had no issues with Android Auto with all other Android phones that I possessed. Nothing phone is the first case where the car system doesn’t recognize the connected phone.

Please fix this issue!

Related discussions

Hello all i found a solution that works with my Opel Corsa.

First in the android auto app on your phone go to recently connecter cars and remove you car from that list.

After that my car would connect again.

Then in the setting of android auto on your screen go to start android auto automatically and switch the option to always.

This worked for my car so i hope it does for you guys too

Now tried with latest update of NOS 2.5.1 - no success. Same problem, same CAPE-QRD… error. Maybe there is some ETA when the fix could be done or it’s already in progress? Or probably there will not be fix on this? Asking as don’t want to rush on buying AAWireless or similar solutions.

Really hope that Nothing team will find that unlucky part of code that causes this problem.

I drive a Skoda Scala from 2021. I have the ‘Bolero’ infotainment system (MEN3/MIB3, as it’s known). This infotainment can be found in many VAG (VW, Audi, Seat, Skoda) cars.

I also have the CAPE-QRD_SN:XXXXXXX problem. This is the first phone with this problem in this car. I’ve connected the phone to a coworkers infotainment (he has the 10″ version instead of my 8″ version). It connects, but still gives CAPE-QRD_SN:XXXXXXXX as the device name. It should be ‘Nothing Phone (2)’, like the Bluetooth name is.

Nothing Support wants a video of the problem, even after giving them photo’s and a full description of my troubleshooting steps :

- Tried different phones (OnePlus, Samsung etc), they ALL work flawlessy.
- Tried different cables, CAPE-QRD error, no connection.
- Tried resettting the infotainment, CAPE-QRD error, no connection.
- Tried factory resetting the phone, CAPE-QRD error, no connection.
- Went to the car dealer for a software update of the infotainment, CAPE-QRD error, no connection.
- Problem happens on 2.04 and 2.51. No difference after manually updating to 2.51.

This clearly is a problem with the ID the phone sends trough wired Android Auto.

Nothing needs to fix this issue, as more people seem to be getting this problem.

EDIT 02-01-2024 (Happy New Year!) : Installed update 2.51a through OTA. Problem persists.

4 days later

Even I am facing the same issue CAPE-QRD, I am using nothing phone 2 with 2.0.4 version and my vehicle is Skoda Kushaq.

Hope we get a resolution early as this is very important feature.

  • vpS likes this.

Hi Same problem, with my skoda kushaq. Connected Bluetooth but not Android Auto. Although in phone it shows “android auto connected”, but on car’s screen it says CAPE-QRD …. error

Hello! Any progress with fix on this? Any reasonable ETA for this?

    7 days later

    Hi everyone,

    I have the same problem connecting my NP2 with android auto on my Dacia Duster (2022). Every other phone that I own work just fine.

    Any news on softwares update to solve this issue?

    It’s very frustrating no been able to use Android Auto.

      5 days later

      EM (1) huntsmarinho

      Hi, thanks for raising this issue, the team is looking into it - we’d appreciate you sharing device logs if possible to help us identify the cause.

      The process for capturing logs is below, but please choose the method that reflects your usage, for a wired connection, use the ‘General Log’ and for wireless choose ‘Bluetooth Log’:

      Guide to capturing a General log:

      1. Dial *#*#569#*#*>>general problem

      2. Turn on “Screenshot” & “Record screen”&“Bug report”

      3. Select “NO REBOOT”

      4. Reproduce the issue (keep the log kit running in the background)

      5. When the issue appears, please help save a screenshot (Press the Volume- & Power buttons)

      6. Dial *#*#569#*#* to go back to the log kit (or tap the one in the notification bar) and tap “Stop capture" and wait for “Log saved”

      7. Tap “OK” when the log is generated

      8. Turn back to the “Log tool” interface and tap the top right corner>>Log list>>long-press the log file we need>>copy>>ok

      9. Open File Manager and find it under the folder internal storage-NtShareLog Choose the log captured just now

      10. Upload the log file on Google Drive and share the link.

      PS: Please set the “General access” to “Anyone with the link”
      ‎

      Guide to capturing a Bluetooth log:

      1. Dial *#*#569#*#*>>Bluetooth

      2. Turn on “Screenshot” & “Record screen” &“Bug report”

      3. Select “NO REBOOT”

      4. Turn off & on the Bluetooth once

      5. Reproduce the issue (keep the log kit running in the background)

      6. When the issue appears, please help save a screenshot (press the Volume- & Power buttons)

      7. Dial *#*#569#*#* to go back to the log kit (or tap the one in the notification bar) and tap “Stop capture" and wait for “Log saved”

      8. Tap “OK” when the log is generated

      9. Turn back to the “Log tool” interface and tap the top right corner>>Log list>>long-press the log file we need>>copy>>ok

      10. Open File Manager and find it under the folder internal storage-NtShareLog Choose the log captured just now

      11. Upload the log file on Google Drive and share the link.

      PS: Please set the “General access” to “Anyone with the link”

            I have a similar but slightly different issue with Android Auto, the phone shows up as Nothing Cape QRD on the cars infotainment system and is able to launch Android Auto, however on the phone the message says continue Android Auto Auto setup on your car screen but the cars infotainment system stays on a black screen, unsure if this is a related issue but feels similar. Hoping for a quick resolution from the devs if it is an issue due to the way the phone appears in the car.
            Car is a Skoda Fabia with a Swing/Swing Plus infotainment system.
            Phone is a Nothing Phone 2

            ErikV_NL

            I’ve updated my phone to 2.5.2; the problem persists.

            I hope this will be fixed soon in a future update. I’ve read a AAWireless dongle works. A shame you have to dish out 70 bucks to ‘fix’ this problem right now.

              I am using Nothing phone 2 with OS version 2.5.2. Trying to connect Android auto using nothing cable in my Jeep compass 2017 model but Android auto does not connect.

              Tried with other phones and it works fine. Nothing please do help with this issue. I personally know many who are going through this issue

              Merged 1 post from Android Auto failing nothing phone 2.

              Had this problem with my last phone and honda jazz. Solution that worked for me was only use a usb type 2 cable and make sure you get the positive connection in the usb c port (i.e. make sure there is no pocket lint trapped in the port, unlikely if you have only had the Nothing phone a few months). Hope this works for you.

              Hope that this means - good news.

              UPDATE

              Yeah, it looks like progress and good news

              UPDATE 2 (Support on X)

              Or not-so-good ones.

              5 days later

              Hey,

              So I had this same problem a year ago with a OnePlus 10T. The answer from OnePlus is that it is not a supported phone on the infotainment system. So a 2020 Skoda with a more modern phone may fall into issues.

              OnePlus said they would do a fix (like the above) but a brief search of Reddit shows that 4 days ago (well over a year since I tried) nothing has changed for the 10T fix.

              My theory is the infotainment system is outdated with no more updates and that the newer phone will become less compatible over time. Nothing Tech may create a patch but I am unsure whether your infotainment will get an update to be able to pair. (Don’t shoot me and I may end up eating my words if I’m wrong).

              This is just a theory but lines up based on OnePlus doing exactly the same thing. Was looking for this issue today for the Nothing Phone (2) because I may have dropped my NP(1) a bit too hard.

                Hey, Dominic! Of course, it’s possible that the entertainment system does not support this, but I doubt this is the case.
                I just tried the OnePlus Nord 3 (released 1 year after 10T and 6 days before my NP2) - Works like a charm!

                So it’s more on the management’s willingness to prioritize this as a reasonable problem and fix it.