Q: iOS 8.1.1 bluetooth problem in Mazda persists

The beta is 8.2

The beta is 8.2, but this release is 8.1.2. You can try updating it to see if it fixes anything, but I wouldn't hold my breath. This is a minor update, the bluetooth and other issue update would likely be larger than 28 mb.

Looks like we will have to wait until next year, and even then no guarantee it will fix things.

http://www.forbes.com/sites/gordonkelly/2014/12/09/apple-releases-ios-8-1-2/

I have this exact same problem. It is incredibly frustrating.

2011 Mazdaspeed3 - Bluetooth worked perfectly until iOS 8. Now I can still play music, answer and hang up calls via steering controls. Dial out via Mazda's version of Siri. But if i dial via my phone or Siri while connected to car the bluetooth drops you then have to use the phone. As soon as someone picks up the phone you can then switch back to bluetooth and all is well. If someone calls me and I answer with the car all is well. I've tried changing the Bluetooth name - Removing Mazda from device - reset all settings - None has improved the situation. I'm currently on 8.1.2 and this did not make any changes. Hopefully there will be some fix soon as I spend a ton of time driving for my job and i'm on the phone 50% of that time making lots of different calls this is dangerous. The phone is a 5s on 8.1.2(12B440)

What I am reading and hearing from programmers is that there is a very high probability Apple has produced a program update that does not apply equally to all the variations of hardware they have produced.  There seems to be a decision by Apple to just let those affected hang out to suffer and finally give up and "upgrade" to a new iPhone if their phone is past warranty.  Well, my new LG works fine and I, and I hope many others, have left Apple! 

I had similar problems with iOS 8.1.1 with my Jabra Drive bluetooth device.  I could connect to the device for any purpose except making a call.  I could dial the number, and hear the touchtones from the device, but when the call started, it would kick back to the phone with no option to send the call to the Jabra.  iOS 8.1.2 fixed the issue for me, I'm happy to say.

In response to TJBUSMC1973's repeated assertions that the fault lies in the hardware developers for not updating their hardware to keep up with Apple's changes, I would submit that there are two explanations for why my Jabra now works:

(1) Apple realized that many hardware manufacturers were lazy and unable or unwilling to update their device firmware to keep up with new developments, and magnanimously released an update to  mitigate the manufacturers' shortcomings.

(2) Apple screwed up and finally started fixing the problem with 8.1.2.

Occam's razor suggests explanation #2.

Eyeballer001 wrote:

 

I had similar problems with iOS 8.1.1 with my Jabra Drive bluetooth device.  I could connect to the device for any purpose except making a call.  I could dial the number, and hear the touchtones from the device, but when the call started, it would kick back to the phone with no option to send the call to the Jabra.  iOS 8.1.2 fixed the issue for me, I'm happy to say.

 

In response to TJBUSMC1973's repeated assertions that the fault lies in the hardware developers for not updating their hardware to keep up with Apple's changes, I would submit that there are two explanations for why my Jabra now works:

(1) Apple realized that many hardware manufacturers were lazy and unable or unwilling to update their device firmware to keep up with new developments, and magnanimously released an update to  mitigate the manufacturer's shortcomings.

(2) Apple screwed up and finally fixed the problem with 8.1.2.

 

Occam's razor suggests explanation #2.

Actually, you're misapplying Ockham's Razor. 

If the iPhone's Bluetooth works on other accessories, but not in a specific vehicle, then the most logical conclusion is that there is an issue with the specific vehicle. 

And if the Bluetooth in other identical iPhones works in most every other vehicle's Bluetooth, but not with one specific one, then the most logical conclusion is, again, that one specific vehicle.

Every version of iOS 8 worked in all of my vehicle's Bluetooth systems.  If the iOS was at fault, then it would not have worked in any of them.

Yes, it is entirely possible that instead of waiting for the Bluetooth accessory manufacturers to fix it on their end, Apple made modifications to the newest version to provide a workaround.  If Apple had 'screwed up the Bluetooth', then the problem would be much more widespread.

This is a proper application of Ockham's Razor.

breezymcgz wrote:

 

In this situation, Apple put out an update that caused the phones to lose functionality.  That's on Apple.

 

No, they didn't.  My iPhone didn't lose Bluetooth functionality after any of the updates, so the updates didn't cause the problem.

The Bluetooth accessory manufacturer didn't keep up like they are supposed to.

Imagine that Blockbuster was still in business all over the country.  And imagine that the DVD player industry changed over to making only Blu-Ray versions of DVD players.  But Blockbuster decided not to invest in purchasing the Blu-Ray versions for rental.  They fall behind the times... and it's no one's fault but their own.

TJBUSMC1973 wrote:

 

No, they didn't.  My iPhone didn't lose Bluetooth functionality after any of the updates, so the updates didn't cause the problem.

The Bluetooth accessory manufacturer didn't keep up like they are supposed to.

 

Imagine that Blockbuster was still in business all over the country.  And imagine that the DVD player industry changed over to making only Blu-Ray versions of DVD players.  But Blockbuster decided not to invest in purchasing the Blu-Ray versions for rental.  They fall behind the times... and it's no one's fault but their own.

it ***** that Tim Cook makes you work on weekends. 

breezymcgz wrote:

it ***** that Tim Cook makes you work on weekends.

It might if TJBUSMC1973 worked for Tim Cook/Apple and if he actually worked on weekends...

breezymcgz wrote:

 

TJBUSMC1973 wrote:

 

No, they didn't.  My iPhone didn't lose Bluetooth functionality after any of the updates, so the updates didn't cause the problem.

The Bluetooth accessory manufacturer didn't keep up like they are supposed to.

 

Imagine that Blockbuster was still in business all over the country.  And imagine that the DVD player industry changed over to making only Blu-Ray versions of DVD players.  But Blockbuster decided not to invest in purchasing the Blu-Ray versions for rental.  They fall behind the times... and it's no one's fault but their own.

it ***** that Tim Cook makes you work on weekends.

You've actually got that backwards.  Tim Cook works for me.

TJBUSMC1973 wrote:

 

breezymcgz wrote:

 

it ***** that Tim Cook makes you work on weekends.

 

You've actually got that backwards.  Tim Cook works for me.

I knew you weren't dead Steve!  Long live the king!

I’m afraid you haven’t convinced me with your arguments.  As I see it, modern operating systems are so complicated that it’s not realistic for any individual or even group of individuals to anticipate *every* possible scenario the OS will deal with.  It is not rare for even small, seemingly innocuous updates to have unexpected consequences and dysfunctions.

The crux of your argument seems to be that since Bluetooth device pairing with iPhone OS 8.1.1 works for most people in general, and for you in  particular, then it is inconceivable that iOS 8.1.1 is at fault for those few outliers having problems.

I think a relevant analogy is the WiFi problem which previously surfaced with OS X Yosemite.  Most people had no problems with WiFi after updating.  Applying your reasoning would suggest that the WiFi hardware manufacturers were at fault for those few individuals who did have problems.  However, in some posted cases, people were having problems connecting Apple computers with Apple Airport stations, both of which had the latest software/firmware updates.   Apple finally released a software update which fixed the problem for most affected people.  The problem, in a simple sense, was that Apple developers hadn’t accounted for some less common, particular system configurations, and those particular configurations “broke” the WiFi component of Yosemite.

For the other posters in this thread, their devices worked with previous versions of iOS as well as other devices’ implementation of Bluetooth (e.g. Android).  That would suggest that the devices had properly implemented some version of Bluetooth.  Bluetooth is a common standard, like 802.11n for WiFi,  and is maintained by the Bluetooth Special Interest Group.  All licensed Bluetooth devices are required to be backwards compatible with older versions of Bluetooth, and so your assertion that users needed to update their device firmware is flawed.  Even if Apple had implemented a “new and improved” version of Bluetooth, they would have been required to have it compatible with older devices.  (Out of curiosity, how would you suggest I update the Jabra Drive firmware…the device has no mechanism for doing so, nor should it need one given the backwards compatibility requirement for Bluetooth).

If you cannot concede the possibility the Apple messed up, then we’ll just have to agree to disagree.

Cheers