January 3, 2017 at 4:11 pm #148237
In prior versions of the IOS system I was able to make and receive calls on my iPhone through the system with new issues.
However, after installing IOS10 I have had difficulties: I can still make calls on the bluetooth system, however, when I receive a call I have issues. The incoming call rings through the system and I am able to answer the phone via the answering icon on my steering wheel. For some reason the call gets forwarded from there back to my iPhone forcing me to select audio settings and press the Chevy Malibu bluetooth link, at which point I am able to have a call through the bluetooth system. Unfortunately this operation is not hands free and causes me frustration and potential driving issues.
I have spoken to the dealer and there is no update they can find for the bluetooth system for my vehicle. I have spoken to Apple and they claim it is an issue with the bluetooth firmware. I have confirmed at a very high percentage rate it is in fact with the firmware for my vehicle. I recently bought a new iPhone 7, upgraded from an iPhone 6, and I get the same result.
Has anyone experienced this issue and does anyone know if I need to change phone settings or if someone from GM sees this has this issue been reported and is GM working on it?
I plan to go to my dealer this week and try this on a new vehicle’s bluetooth system to isolate if the problem is my radio and not firmware.
In the meantime, replies with helpful suggestions or the same issue would be helpful.
May 5, 2017 at 7:37 am #161795
I am having the same issue with my 2013 Malibu 2LT! Outgoing calls – no issues. Incoming calls – come through and can be answered, but transfers directly back to my phone after hitting the answer button/clicking answer on the screen. Sometimes I have to click transfer back to Bluetooth a few times before it connects.
I see that your post is over a few months old – did you ever get any kind of fix or knowledge of what is going on with this problem? I thought it was my iPhone as well because the issue started directly after the iOS 10 update. This small problem is starting to really bug me, so I hope there has been a fix for this!
You must be logged in to reply to this topic.