Q: iOS 8.1 still has  Bluetooth issue with mazda

I appreciate the suggestion and I'm glad it worked for you.  However, I found the same solution and I've done it multiple times -  it didn't change anything for my iPhone 6 under iOS 8.0.1 or 8.1.

Reset all settings is a pain too - so annoying to have to customize them all again.

Just wanted to chime in here and say I'm having the same issue with my iPhone 6 and bluetooth on 2010 Mazda3. It's pretty annoying when I place a call and I can't hear the phone ringing and the bluetooth only kicks on my car stereo when someone picks up on the phone call.  Never had this issue with my iPhone 5 on iOS 7.

Yes, still exactly the same problem with my 2013 Mitusubishi Outlander Aspire!  Have tried all the suggested solutions. Very annoying!

Confirm this EXACT issue on another Outlander 2013.  Have even taken it to Mitsubishi and got a shrug and statement that it worked perfectly on ios 7.x.  Which to their credit it did.

Well my "fix" stopped working after a week or two. So I guess it only temporarily works. I'm not going to reset my settings every week or two. Way too much of a pain.

I'm having a similar problem too with the phone side of the car's bluetooth not switching over properly. More annoyingly for me, on my iPhone 6 it won't accept the AVRCP commands (play, rewind, FF, stop, etc...). I really wish they would fix this since I use my phone as my music player in the car.

iOS 8.1.1 is out and it supposedly addresses Bluetooth issues!

However, after my first tests this morning, it made no changes to my situation.  Same problem as before - outgoing calls simply WILL NOT route through the car until the other end has picked up.  I have yet to test to see if 8.1.1 broke other functionality that worked under 8.1, namely incoming calls and music.  I also should note that I have not unpaired and repaired under 8.1.1, so I'll try that later today, but I'm guessing that's a long shot.

Same.  Issue persists on 8.1.1 exactly as before.  2013 Outlander.  Such a huge problem for me being on the road a lot that I am thinking about returning the phone.

You could buy an external in-car Bluetooth speaker that clips on your sun visor. I've heard these work pretty well.

That's no good but you have saved me the trouble of me trying it in my Outlander.  Does Apple read these blogs????

They do not read these forums.  It's in the terms and conditions somewhere.  It's just us humble users trying to help each other out.

The best thing you can do is bombard them with product feedback here: https://www.apple.com/feedback/

They don't respond, but at least they read.  I've sent them several messages detailing this bluetooth issue as well as a few others that showed up in iOS8, such as the occasional double email tones, which still aren't fixed either sadly.

Same problem for me... Apple please help us

If you are still having trouble connecting your phone, pair it through the voice prompts instead of the radio screen.  That worked for me.

I've never had trouble pairing - the issue I have is only with outgoing calls being routed through the car.

In other news, iOS 8.1.2 dropped today.  The release notes say they've fix a problem with purchased ringtones disappearing (the horror!) while I continue to take my life in my hands every time I need to make a phone call from the car.  As expected, iOS 8.1.2 did not address this bluetooth issue.  Nice job on the bug fix priorities there Apple... I've also done further testing and found that the problem is not limited to Mazda - my 2013 Honda has the exact same problem.  The phone pairs normally, music works normally, incoming calls work normally.  Outgoing calls cannot be routed to the car until after the other end has answered, at which time the call must be manually routed to the car.  This happens on my iPhone 6 and iPhone 5, both running every iteration of iOS 8.x there has ever been.  The only common thread is iOS 8.

We are also having the same issue with our 2013 Mazda 6.  Even got our phone replaced and it still will not make outgoing calls.  This is ridiculous that Apple wont address this