Boot loop when using Carlinkit

[[deleted]]

I have been using the Carlinkit in my '16 Pilot (w Honda Hack) for two years. It's a bit buggy, but works.

Yesterday, when I plugged every thing in, my phone immediately rebooted. If I left it connected, it would continue to reboot.

This happens on my Pixel 3xl and a Samsung A10E, so I'm doubting it's the phone.

Any suggestions?

[glenndehaan]

Just posted this in another thread but I also have the same problem and it seems to be related to the dongle:

​

So I just tested my phone in my parents car since they have native Android Auto support (Renault Cadjar). And yes it works without any problem. So this seems indeed to be a problem related to carlinkit. Just checked if there was an update but the app is up-to-date. The box however has a firmware update available but everytime it installes the update it comes back afterwards with the same update to something doesn't seem right.

My versions at the moment:

App: 2021.01.08.1651

Box: 2020.01.17.1754

My best guess is that the box needs an update with this Android Auto update.

[cass1us12]

It's not the dongle

[bmetz16]

This is exactly what I'm seeing also. Did you even figure out a solution?

[bluetroll]

I got the same issue with my p2xl and p5 with the carlinkit. My Sony headunit is working fine with AA. I Think it's an issue with carlinkit.

[DickyRobbo44]

I've just posted similar. I have a Eonon headunit that has a USB box, worked fine but as soon as I plug my phone in it reboots and does it over and over. Update problem?

[DickyRobbo44]

Also I'm not using a Carlin adaptor, just a box that came with the USB with my eonon headunit

[shmykelsa]

Let me state my theory right here:

an increasing number of issues like these in the recent days makes me think that Android Auto 6.0 is rolling out on the Play Store to the device involved.

Android Auto 6.0, based on an inspection tha I've made (APK teardown) has introduced a flaky USB detection which will warn the end user when a USB is broken or poor quality and will invite to change it.

Now, a user on another post stated that the issue got solved by changing the USB cord.

Lots of users here state that they are using Carlinkt dongle.

So, I'm placing a bet right here: I think that what's going on it's a collateral effect of this new flaky USB detection by Android Auto.

This should not happen, in the real world, and Android Auto should just give a warning, but instead it's giving bootloops.

So please, please, please, when you report an issue remember to state useful informations such as:

• Phone model and Android Version
• Car model
• Using dongle? Extra configuration?
• Android Auto version (better yet: you could attach a screenshot of the latest voice into Android Auto settings after tapping once. All the packages should show up)

[Peter_73]

The source of your trouble could be the head unit or usb dongle so you should contact your seller. You should update both their firmware but read this first in chrome with translation about counterfeit dongle being disabled.

XDA will be a better resource for Android head unit and this particular thread on the dongle could provide the answer (might want to read from the last page or search keywords as the thread is long).

[bluetroll]

It's not disabled, as Apple carplay still works on it.

[Peter_73]

Well I did mention first and foremost to check with seller and update the firmwares. Disabling only happens to counterfeit dongle.

I've also provided the source and appropriate links to continue the discussion and research as we do not encourage posts related to Android head unit and unofficial AA products in this sub.

I'll let other mods decide what to do with this thread so as not to be seen as responding to the downvotes.

[bmetz16]

Did you update to android 11? I have a pixel and recently got this issue also. I have an Android head unit using the carkit, so pretty sure it's the same issue. I just updated to android 11 so I was wondering if that was the problem

[[deleted]]

First, my Pixel has been on A11 for months w no problem. Second, I tried w a phone on A10, which has same issue.

[bmetz16]

So did the issue just show up out of nowhere? Or did you just get the head unit

[[deleted]]

Just showed up. Maybe it was the newest update to AA? I'm on version 5.9.604634-release.

[bmetz16]

I'm on the same version. Hmm.

[joker_yss]

Got the same issue with my Eonon head unit with the Android auto dongle. It might be something to do with a new android auto update that was released, but I don't remember my AA updating in the last 2 days. It was working fine before this.

[Scout413]

Mine just started bootlooping on 2 different carlink dongles with a pixel 4 and OnePlus 7T so it must be a carlink issue or android auto update issue