Currently Being ModeratedJan 21, 2013 7:33 AM (in response to SirIra)
I purchased a 2013 Equinox last week and have had the same issues with the MyLink bluetooth disconnecting and the inbound call going back to the cell phone.
GM advised me on Friday night that the fix would be released within the next 21 days. So that's all I know as of now - GM says the fix is coming from Apple, not GM, but will resolve the issue.
Currently Being ModeratedJan 21, 2013 10:39 AM (in response to MCW1953)
I have 2012 Lexus is250 and have the same problem with not being able to receive incoming calls. My dealership advised me that Apple is supposed to have a release by end of month to correct. I sure hope so! If anyone with Lexus and same issue with resolution, please let me know!!!
Currently Being ModeratedJan 21, 2013 10:57 AM (in response to sandyjean123)
It's interesting that I see "Apple will release a fix by the end of the month" mentioned in more than one thread. I'm not an iOS developer but I see in other threads that the latest Apple Beta version expires on 1/28. If that's true, then another beta will be released or the actual version will be released before then. This second or third or fourth hand information so if I'm wrong please correct me and remember I quailified it as not having firsthand knowledge.
Currently Being ModeratedJan 21, 2013 11:05 AM (in response to PNutts)
What is interesting to me is that there is indisputable proof of at least one head unit manufacturer (Pioneer) and one automaker (Nissan/Infiniti) having acknowledged a compatibility problem and released a fix from their side, yet there apparently are still some auto dealers (and maybe THAT is where the lack of knowledge resides) telling customers that this is a problem that awaits a fix from Apple.
The former belies the latter, no?
Currently Being ModeratedJan 21, 2013 11:15 AM (in response to Katchman)
No. The former does not bely the latter. You are making the leap of assumption that the fact that two manufacturers have made their products work actually means that it was their problem. I don't see any basis for that conclusion. Those manufacturers were able to make it work -- that's the only thing that we know. It may be that they found what Apple fouled up and were able, with some effort, to work around it, and wanting their customers to be happy, they did it.
Whoever may be at fault, there is evidence that these two manufacturers want their customers to be happy, and they have put in the effort to fix the problem -- whoever's problem it is. There is NO such evidence, regarding the situation that we are discussing in this thread, that Apple cares whether their customers are happy, and no evidence that they are doing anything about it.
Currently Being ModeratedJan 21, 2013 11:29 AM (in response to ahoutzer)
It is a given that BlueTooth is a published standard for close-distance wireless communication and control. To entertain your "on the other hand" point-of-view, one would have to assume that the iPhone 5 in some way "broke" this standard-- causing existing systems that once worked to no longer operate correctly-- and that some manufacturers took it upon themselves to make changes on their side to work around the Apple problem. It stands to reason under this theory that these manufacturers had previously done everything right, but now, out of a desire to keep their customers happy, have diverted from the standard and in essence committed a second wrong to make a right.
I don't buy it. This would mean that the manufacturers issuing a fix have also diverted from the standard which would not be done by any responsible software developer.
Currently Being ModeratedJan 21, 2013 11:40 AM (in response to Katchman)
So you're submitting that for all these years, Apple wasn't complying with Bluetooth standards. Somehow so many of the manufacturers of hands-free phone devices in their cars, GPSs, and others also got it wrong.
In a strange twist, everyone made the same mistake in the Bluetooth standards such that everyone's hands-free devices worked.
Worked, that is, until Apple discovered that it has been in error since day one and "fixed" their problem.
Doing so made the other devices lose functionality; presumably because they were all wrong in the first place.
Does that really make sense? It's just a little hard for me to accept . . . that Apple is getting it right and all the Bluetooth-compatible manufacturers are wrong.
My Garmin worked with my very first iPHone, second iPhone, and third iPHone. But it doesn't now with the "fixed" Bluetooth in my iPhone 5. Garmin insists that they're complying with the standard and that their devices work with other smart-phone's Bluetooth. My motorcycle-traveling friend confirms that his identical Garmin 665 does indeed work with a non-Apple smart phone. (I forget which smartphone)
Currently Being ModeratedJan 21, 2013 11:39 AM (in response to Katchman)
Nonsense. It's done all the time. Right at this moment, you are probably using a web browser that is written with loads of IF statements that work around scenarios where the servers that your browser is communicating with do not correctly implement standards, or where the standards themselves were not well written, so that compatibility is poor unless third parties work around the shortcomings. We do not live in the standards-perfect world that you suggest. That must be some other planet.
Currently Being ModeratedJan 21, 2013 11:47 AM (in response to DFWKen)
Actually, Apple implemented the new Bluetooth 4.0 standard and some older devices aren't forward compatible. This KB article demonstrates that Apple is aware and cares about these issues.
Currently Being ModeratedJan 21, 2013 11:55 AM (in response to DFWKen)
No-- that is not what I am saying at all. The iPhone 5 uses a new Bluetooth chip that implements Bluetooth 4.0. BT 4.0 is supposed to be backward compatible, but this presumes the headunit manufacturers were 100% compliant in their respective implementations. This appears to not be the case with certain (but not all) head unit manufacturers.
Currently Being ModeratedJan 21, 2013 1:31 PM (in response to Katchman)
This is a complicated issue. To try to understand it go to http://en.wikipedia.org/wiki/Bluetooth_low_energy and note under history that the 4S used Bluetooth 4.0. Then look at http://techtips.salon.com/iphone-bluetooth-compatibility-4988.html . There are a lot of standards. A standard is not code. Each device may program a standard themselves or may use a common routine that is the industry standard for that function. Each device has only so much room for the firmware hence some corners may get cut or they may drop a section of code that is not relevant to that device at that time. Once this is done full compatibility with a standard is lost.
Now in this case Apple introduced some issue if the 4S was fully compatible and the 5 is not. However if you look at the Nissan site you see that the last iphone to be mentioned as compatible was 3.0. This does not mean that Apple is at fault only that the devices are not compatible.
The bottom line is that both manufacturers recognize there is a serious problem that needs to be addressed and neither has let it stand. Kudos to both, shame it had to happen at all, but thanks for the fix.