iPhone 7 Google maps delay on bluetooth

Another day, another fairly long call with Apple. We're not there yet, tried another Apple suggestion (helpful but didn't work) but I don't think we're regressing either. I'll post again probably by the weekend.

Hang in there, you’re doing great. It certainly is discouraging to see Apple continue to offer ridiculous “fixes” that they must know couldn’t possibly work to overcome the Bluetooth delay that Apple introduced. It’s not Steve Jobs’ Apple, and hasn’t been for quite some time.

HI All! & Apple Just wanted to report another Maps mishap! Last night , driving on I-95, very busy hwy, I was chatting in the car & the direction came over to exit the Hwy. B/C it was such a short command, it was not even announced & I missed the exit. Had to drive 5 miles more to get off, make a U-turn & get off at the unannounced exit. I can count at least 5 dangerous things that occured while Apple Maps.

Thanks for posting. I’ve had similar experiences: last second turns and U-turns, missed exits, all dangerous. Amazing that Apple still refuses to fix this issue that it introduced in the iOS 14 update. Not fixed in 14.5.

Of course I agree with all of the above comments. And if Apple made this change to help with battery life, don’t most of us have our phones charging in the car most of the time anyway? That’s the one place battery % really isn’t an issue.

I have another call with Apple on Monday at 2 PM ET. It looks like they've bumped this up to a more advanced technical level and they're looking at some "logs" from my phone. I'm not sure that will be productive.

I've given them the answer, pause for incoming calls and the directions are treated as calls, but they're not addressing that. Wish I had people given me the answers :)

I'm sticking with this

Thank you for hanging in there. Perhaps they need to go for a ride with someone who has posted here and experience the problem firsthand. After that, they can read all these comments, and then they should be ready to fix it. I feel a bit like they are attempting to reinvent the wheel...with no promise of success.

Wow, Beatrice. They are taking you through the ringer. I'm so sorry!!!

This thread, is monitored by Apple. The program writers who none of us will ever speak to, are the ones who need to do the update to undo what they did.

I hate to be negative, but at the end of the day, with all this documentation, if someone gets hurt due to delayed Instructions & taking their eyes off the road to look at their map, Apple can be held liable.

that is what should make them update and correct the error. They can do it in a matter of minutes.

Beatrice...you are making an impact! I received a phone call from Apple asking about the problem. We discussed what happens, and I offered to take them on a road test to experience it but they declined. We went over a number of things about my phone, and I downloaded 14.5 and will see if it makes any difference over the weekend. They say they are going to call me back on Monday to continue exploring this. We will see, but in the meantime I believe we have Apple’s attention led by Beatrice and supported by all chiming in here. Keep at it!

Good news, though not yet what we are all waiting for. For your information, iOS 14.5 does not solve the problem. Let us know if, based on your conversations with Apple, you think it would help if more of us tried to contact Apple by phone.

That would probably help, especially if it involved you erasing "All Content and Settings" (Apple's common suggestion) then, after the phone came back up did NOT restore from a backup. Instead you installed just Google or Apple Maps tried them out and the problem was still there. Thanks,

APPLE CALLED ME! - Friday afternoon I got a phone call out of the blue from a high up person at Apple, who has been reading this discussion thread and is contacting several of the people on there. I guess through our login information to this board they have our phone numbers which was fine. It was an authentic call coming from an 800 number ending in 2273 so if you see that number pop up on your phone you might want to take the call, because the person indicated he would be calling other people on the thread as well, including over the weekend since his days off are Monday and Tuesday.

The persons name I spoke to was Jacob, who says he is with a very small outreach team that tries to solve and troubleshoot significant problems they see on the discussion board. I asked him if he has some level of tech-support, and he said he is “beyond the levels,“ and he seemed like a very nice guy.

So I went over the problem with him, emphasizing that it is a problem when you are listening to your car radio, using the radio as the source of your music, and using your phone to send driving directions by Bluetooth “playing as a phone call.“ In other words, that the car thinks the driving directions coming from the phone are equivalent to a phone call, which creates a 1.5 or 2 second delay while the phone and car audio systems are establishing the Bluetooth connection, and this results in the first part of driving directions being clipped and not heard. I told Jacobs that if you are using your phone to stream music to your car audio system, and that connection is active via Bluetooth, then when the driving directions come through you get the entire audio from the directions without any clipping because the Bluetooth connection is already active and in use and doesn’t need to handshake or warm up. I also told him that this seems to have been a problem that has come up since iOS 14 started. I did tell him that those who have updated to 14.5 have seen no improvement.

Jacob seemed to totally get the problem, he did understand, and was very empathetic. He said that it sounds like it has something to do with the Bluetooth stack firmware in the iOS system. He is not an engineer, but once he has a good understanding of this from others on the board he talks directly to the engineers and can try to get this fixed.

So I thought I would let everyone know this, because it sounds like at least we have their attention and the outreach team wants to see if anything can be done about it.

I also got a phone call today from Apple. From a Highup technical support person as well. Very similar to GF 760s conversation. Let's hope for making headway.

thank you to everybody who's in this thread and working together.

Sometimes it takes a village of people.

As I write this I’m watching Warren Buffet at the BH annual meeting praising Tim Cook as one of the best managers he’s seen. Warren is probably correct, which suggests that Beatrice’s decision to communicate directly with Tim was spot on. And so far Apple’s response seems to support this. Thank you Beatrice.

Sounds like progress is continuing with folks getting calls from Apple. As I noted on here yesterday, I received my call from Apple yesterday (Friday). I was asked to update to 14.5 and told I would receive a call back on Monday to see if it made any difference. I was willing to give it a try. As anticipated...and as reported here previously... going to 14.5 made no difference with the initial direction info dropped. All it did was make my husband laugh as I tried once again to use a map app in my car. A point of clarification that may help as we proceed in our discussions with Apple. In talking with the Apple rep, he was trying to clarify what happens as on these posts the terminology "delay" is sometime used and that could be interpreted as the directions eventually come through in full. I clarified that is not the case...that I am "missing" the initial words on the directions, and they are never heard. And, for those that have posted here, please know that they are reading these posts, so keep at it!