No Siri audio over bluetooth

Hello

I am using an iPhone 10R and have Bluetooth issues as well with iOS13. If I attempt to initiate Siri by holding down the button on the steering wheel I hear the Siri "beep" but then the connection is ended right away. Before upgrading iOS13 this worked flawlessly. I can still stream music, get directions, and answer phone calls just fine in the car over Bluetooth. For me the issue is only with initiating Siri.

I called tonight5, was told this is a seldom reported issue and they made me an appointment to go to the Apple Store tomorrow! How silly is that? It happens on both my phone and my husbands... two different models, so why should I go to the Apple store?

Updated to 13.3 but nothing is fixed. Hey siri does not work, still no feedback through car stereo. If i use the power button to call siri it works, i get feedback through car speakers. So thanks Apple...

I have the same issue except the power button makes no difference. Tried three cars so far all with same result.

Upgrading to 13.3 made no difference. Works fine with bluetooth headsets - only not working in car bluetooth head units.

Hi , I’m in Australia and here Apple have acknowledged the problem and have done all sorts of testing including me uploading videos to them of the problems in action and remoting into my phone. They’re calling back Saturday with the results of the testing but I can’t see the problems being fixed before the release a new bug fix iOS . All I say is report it to Apple care , the more people who do it , the faster the fix will be released

Yeah, erased everything, set iphone as new but nothing. Sometimes i can hear siri if i long press the power button, sometimes not, sometimes i get bt disconnected in the middle of the call sometimes not. Streaming music with spotify works flawless though through bluetooth. This just shows how much apple cares about their customers.

I wonder if it's something strange like being dependant on the version your phone was on when first paired with the head-unit? I think I upgraded my phone to 13.x very soon and potentially hadn't paired it to the car before then.

danglesdoo wrote:

I wonder if it's something strange like being dependant on the version your phone was on when first paired with the head-unit? I think I upgraded my phone to 13.x very soon and potentially hadn't paired it to the car before then.

Above you mentioned having an 11 Pro, that would have come with iOS 13 pre-installed.

My wife got her 11 Pro before I did, and she noticed this problem in her Jeep Wrangler right away. At the time I still had my Xs Max and did not have this problem in her Jeep, but I was on iOS 12 at the time. Once I updated my Xs Max to iOS 13 then I had the problem, so seems to be an iOS 13 issue and nothing to do with "first pairing". Of course, once my 11 Pro came in I had the problem as well.

Perhaps there is a hardware link too, e.g. does an iPhone 6s on iOS 13 have this problem? Different Bluetooth hardware may act differently with iOS 13, but so far it seems that "lucky 13" is the culprit.

I'm beginning to think that this issue has something to do with how iOS 13 handles phone calls vs. A2DP (audio) Bluetooth profiles -- they're different, and in some vehicles they are managed and set up independently, though most modern vehicles require only one pairing for both protocols. There used to be a way in iOS Bluetooth settings for navigation on which channel to use, but I don't see that anymore (not sure where it was though, LOL!) If Apple removed this capability to switch navigation audio between the Bluetooth "phone call channel" and the "audio (music) channel" then perhaps that is at the root of where things have gone sideways. The double-appearance of the Bluetooth device leads me to suspect this.

For now, keep providing feedback to Apple.

That's true - I'd forgotten that they come with 13. My wife and I both have the same phone - 11 Pro and the symptoms are identical, and have been for every update so far. We have our old models - 6S and SE that i'll test as well.

Your theory about A2DP seems possible - there is definitely some mis-communication happening as the head-units all behave as if there is a phone call during the Siri conversation. What I don't understand is the differences between a Bluetooth head-unit and a Bluetooth head-set - perhaps Bluetooth has particular roles even if they're similar - since the head-sets have a 2-way audio mode where the signal is used for both (and hence has lower quality audio) vs the headphone mode where the full bandwidth is devoted to audio and gets a better quality. Every head-set I have tried so far works fine with Siri.

[edit] this explained the differences to me: https://en.wikipedia.org/wiki/List_of_Bluetooth_profiles#Hands-Free_Profile_(HFP)

Ultimately I just want Apple to stop wasting our time and acknowledge the bug so we can wait for the fix.

FWIW, in my truck I use a Griffin BlueTrip device for Bluetooth audio (my truck's Bluetooth only supports phone calls). The BlueTrip is essentially a "head set" since it handles phone calls and audio, and it has this same issue. What I have not tried is to pair my iPhone with my truck's Bluetooth (for phone calls) and the BlueTrip (for audio) ... curious what that will do, if anything.\

Agreed, Apple needs to fix this ... I'm shocked that there is so little mentioned about this across the internet.

That’s pretty much the setup i have. My bmw e90’s bluetooth only supports phone calls, so i have a bt reciever connected to the aux port for music. I have tried connecting the phone to the adapter (which also supports phone calls btw) but nothing changed... music works, maps work, hey siri doesn’t.

my facts:

All phones worked with all Bluetooth (BT) prior to iOS 13

As of today my husbands SE on 13.2 will not work w/Siri in any car (2011 BMW, 2019 BMW, 2018 Nissan)

It does work if Google Maps is talking thru BT

My phone is an 11 Pro on 13.3. As of today and upgrade to 13.3 my phone now works with Siri paired to a $25 Jumbo BT speaker, it will not work w/Siri in any car. It does work if Google Maps is talking thru BT.

My phone came with 13.0 - I bought it early after release. Siri BT feedback worked; in fact everything worked perfectly - better than BT ever worked; It actually seemed that my phone was ignoring the car's crappy microphone, and was using its own mic when siri was activated (transcribed text messages were as accurate as without BT). Then things started to go downhill after some updates. At some point making calls was unbearable because of crackling, during the call (fixed in 13.3), but Siri audio feedback still worked with "hey siri". Then (for me) with 13.3, siri audio feedback stopped working. I have noticed (one of the posters mentions this) that if you hold down the side button to activate Siri, audio feedback works.

I've tried doing a master clear in my car's phone setup, so it completely resets all BT/phone settings from previous pairings.

This doesn't make a difference.

Your assumption about a2dp sounds quite plausible, and yes, I remember you could set these options, although I think it may be application specific? I remember you could set it both in google maps and waze.

Hi all, Apple care just rang and me to upgrade to iOS 13.3 but it didn’t make any difference. They are aware of this thread and others like it. Hopefully 13.4 will fix it but it’s getting beyond a joke. $1000 fine for touching your phone in car in Brisbane, Australia and now they have cameras that can detect usage. Appalling!