Our XT1762 (dual SIM) has a bug with Bluetooth connectivity to an in-car head unit/stereo system
The bug occurs with phone book/contact sharing. Here is the problem:-
i) When the device is initially paired or subsequently connected to the head unit, the address book/contacts are not automatically transferred even though this has been set in the phone.
ii) It becomes necessary to initiate the sync/transfer from the car head unit. When this happens, the whole process takes in excess of four minutes with the connection being lost several times during the process.
iii) When the sync/transfer is complete, the head unit shows every contact twice i.e. they are duplicated.
Also, when the head unit and phone reconnect e.g. when starting the car up, there is no sync/updated initiated. This has to be done again, but always from the car head unit.
This issue was not present when the device was new - it has only occurred in subsequent system updates.
The device has been reset to factory and rebooted several times but is 100% persistent.
Head unit is a CD450 in a Vauxhall Mokka.
Does anybody else have this issue? Thanks.
Related
I have noticed that my phone (OP 5) sometimes (quite often, but not always) requires a new pair process with my car head unit. My head unit is VW RCD330.
For example: two hours ago I came to my office. I listen to my music and use Android Auto on my way. Now I'm looking on my phone and my head unit isn't listed. So I expected that I will be asked again to pair.
Good Day all. Hoping I could get some help with my new Android 9.1 inch head unit, version 10.1 (Model YJ9213AJ). I just installed the unit and have an issue with the CarPlay (usb dongle) which stops playing almost instantly when connected to Spotify and/or my songs on the iPhone. If I click play again it stops within a second. It also stops playing media files on my USB (local music) when it switches to the home screen, which it does on its own after playing music for approx a minute or two. I reset the system and unfortunately still have the same issue. Also on the bluetooth I get "please connect HFP first" too, maybe related IDK?.
Anyone have any suggestion on how I can try and fix these issues. Thank you in advance.
I had problems with android auto if bt was also trying to connect to the phone as an audio device. Disabled bt audio fixed it.
Then I just dumped android auto and went back to bt
Fixed it. Reset the unit and added apps one by one until the culprit was found. It was the CarPlay dongle app that caused the entire issue. Strange.
I installed an Atoto S8 (2nd generation) head unit in my car, and I'm noticing that it only reconnects to whoever drove the car last.
For example, I usually drive the car. But when my wife drives, we need to manually go into settings to find the list of paired devices on the unit and then click on her phone to connect. After that, it will auto-connect whenever she drives until I take the car. My phone won't connect anymore unless I go into the list of paired devices and do that same thing. Silly and annoying because we share the car sometimes and have to keep track of who drove last if we want our phones connected.
I reached out to Atoto because their linux-based F7 didn't do this (I owned one previously), it would reconnect to any previously paired device automatically like any head unit should (obviously most recent first, but then if not found move on to another previously paired). They said the Android based units don't work like that, then gave me a silly reason for it that didn't make sense (something about security unlocking which the F7 doesn't have to worry about).
I'm wondering, do all Android head units have this issue or is it unique to this brand?
Head unit is this one from Idoing.
I have the BT1 ODB2 Dongle from Ecutek, and downloaded the ECU Connect App.
I confirmed that this works from my Phone (Galaxy S21). It successfully finds the dongle and the app works from there.
When I try from the head unit - it tries to find BT devices, but every device is listed as "noName". It finds anywhere from 4-10 devices (depending on how long I let it scan). A couple of devices actually pair, but they do not work for ECU Connect. So I assume they are not the correct devices. I think at this point I've gone through every 'noName' device. Most do not pair at all. The ones that do pair, I've renamed so I can keep track of which ones they are.
Now, when I try using the native BT connection on the head unit - it can actually find and correctly identify the Ecutek dongle. However, connecting from here does nothing - I must connect from within the ECU Connect App which of course fails.
I tried some random BT scanning apps - they all show similar behavior with devices being displayed as "noName". Googling this "noName" BT issue doesn't come up with anything useful.
Any ideas for what I can try or at least try to diagnose the issue? I have a friend who says he ran into something similar with a similar head unit, but he cannot remember how he fixed it...
I figured it out. Figured I'd write it up here since I couldn't find this anywhere else on the internet.
Sparing all the middle troubleshooting steps, here's a summary:
First, these Chinese Android head units all seem to struggle to pair with certain BT devices. This 'noName' issue is merely a symptom of other problems.
The Ecutek BT dongle has a passcode. The head unit is trying to use a passcode of '0000' when negotiating with the dongle. If this is not the passcode, it will fail silently most of the time. Sometimes you get a failure indication.
Steps to fix:
Connect to the Ecutek BT dongle via your phone. Your phone has a better time negotiating this connection. Once successful, it will ask you to enter the passcode (if one was set up previously). For me, my car had a previous owner/tuner - so I imagine they set it up already.
At this point, you can reset the pre-existing passcode (i.e. if you do not know it). Follow the prompts in the ECU Connect app to reset the passcode.
After resetting, change the passcode to '0000'
If you already have the passcode set to something else, you can reset the passcode within the ECU Connect app. Simply reset to '0000'
Back in ECU Connect when looking up new BT devices, you will still have the 'noName' issue. I simply tried every 'noName' device until one worked. It appears that both successes and failures can be silent when in the head unit's BT screen... You can tell that it worked by pressing 'back' from the BT screen. If successful, ECU Connect will recognize the device and show a success message. If it doesn't, then this 'noName' device is not the right device.
I recently installed a Fellostar Android head unit/radio in the car, and we have a problem getting the unit reliably to connect to the phone. This usually happens automatically, via whatever app (can't recall the name) that came installed on the unit for that purpose. *But* sometimes it is flaky, and doesn't want to connect (endlessly "verifying"), even when the cable is plugged into the phone. *And* the problem is much worse if there are multiple phones/users in the car who have connected previously - the head unit just randomly connects to one of the phones, again regardless of which one is plugged in.
Is there a fix for this? Is there some way to choose, from the head unit, WHICH phone it should connect to?? The factory installed linking app offers no such choice. Are better apps available? what and where?? Thanks in advance...