iPhone 7 Google maps delay on bluetooth

Indeed, Apple did change something; namely it now imposes a delay before an incoming phone call connects to an automobile’s Bluetooth. And for older cars such as mine that do not support a direct Bluetooth connection for driving directions, the workaround has always been to treat each direction as an incoming call. Thus Apple’s change now imposes a delay for each direction. Apple’s refusal to correct this must mean that Apple believes the problem will be reduced over time as newer cars replace older ones, and therefore it isn’t worth the effort for Apple to fix the problem it created. So much for Apple’s concern for its customers. Bear that in mind the next time you need to replace your iPhone.

Thanks and that makes sense. When you say an older car that doesn't support a direct Bluetooth connection do you mean that's why I have to, in my 2019 Infiniti, set the Google Maps navigation settings to treat the directions as a Bluetooth call and with Apple Maps I have to enable Hands Free Prompt?

Thanks,

Don't know much about a 2019 Infiniti. My 2014 BMW does not allow map driving directions from Google or Apple maps to bluetooth directly to the car's audio, but it does allow phone calls to do this. So driving directions masquerade as incoming phone calls and that way are bluetoothed to the car's speakers. But when Apple screwed up by inserting a delay before incoming phone calls are bluetoothed (they did this ostensibly to save iPhone battery drain)the delay affected map directions. In 2019 models BMW provided for direct bluetooth connection from iPhones for all purposes, so the delay is eliminated. I don't know about Infiniti.

This is not only absurd this is DANGEROUS!! This just started happening to me. Google maps, Waze, and Apple Maps, none of them will play properly. As everyone else I only hear the very tail end of the voice command.

seems seems like it's been almost a year and they can't fix it. I've been chasing my tail to the car dealer, T-Mobile, Lexus, and the Apple Store,,, just found this, thought I was going crazy.

what can we do?

Well, one thing that ought to work (I haven't tried it)... since people report that it works if you have an existing blue tooth connection running, if your phone has the ability to play music over blue tooth to your car speakers, you should be able to get that going before you begin navigation. As long as you are rocking your tunes over blue tooth, the navigation should be able to break in with directions without any problems.

Simple. Just turn off Bluetooth and listen to driving directions through your iPhone’s speaker. It won’t be as loud as through the car’s speakers but you should be able to hear and you won’t miss anything.

Of course Apple should fix this. But it seems obvious by now that they’re not going to. The problem was identified months ago and there have been numerous updates to iOS since then, but no fix. What does this say about Apple?

Your advice, which is undoubtedly correct, raises a separate serious issue. That is, not only has Apple created a significant problem, one with a potential impact on driving safety; not only has Apple refused to fix that problem; but Apple has provided misinformation regarding what should be done to fix the problem. The problem itself was apparently created in the interest of saving battery life by disabling Bluetooth reception of a phone call until a call (or in the case of map driving directions, something made to look like a call) actually arrives; the refusal to fix is apparently justified within Apple by how it thinks its resources may best be applied; but the providing of misinformation to its customers cannot possibly be justified. What does this say about Apple?

I tried to reply to your question but Apple deleted my response as "not constructive". At least that shows that someone at Apple reads these comments, or perhaps it is done by AI. Bottom line is that there is not much we can do except to hope that Apple will some day decide to fix the problem it caused.

I’ve been following this thread, as well as several related threads. I have seen no indication of an Apple rep acknowledging, or even understanding, the problem. All responses have been basic tier 1 support answers of “try this”, when the user community here has already confirmed that the problem is a software bug.

Apple's non responsiveness is incredibly frustrating. Just like when they told me to take my Mac (after 3+_ hours on the phone with 3 different techs) to the Genius Bar for an appointment. It is a 2 hour trip. When I arrived they wouldn't even talk to me. Told me I had to leave the Mac for 24 hours and they would get back to me. Said they don't read what went on with the phone reps as they don't have time to do that. Worthless time wasters. Now they are putting us in danger with their break to maps, and non-responsiveness to the issue.

I sent an e-mail to Tim Cook today. I know there is absolutely no chance he ever sees it but I'm hoping that whoever is tasked with reviewing e-mails sent to him will at least get something going on this. I'm not holding my breath but I'll repost if I hear anything.

My e-mail to Tim Cook drew a response from Apple. Got a phone call from them today and have a call with a "product specialist" about the issue on Monday and will post back with the results. While on the phone call the Apple rep mentioned they were aware of the issue and thought some fix(es) were implemented. I told him I've had the problem non stop for months. I'll see how Monday's call goes.