Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I think Apple software quality has gone downhill due to mediocre testing. Whomever it is running QA department should be fired. All those bugs (like this, the link from mail) are just too common, no excuse for not catching them early.

Let's propose to Apple that they sack all their staff at software testing/QA, and hire you instead, so you can fix all the bugs by sitting various models on the test bench and moaning at the screens.
 
In my current vehicle (Acura MDX) the hand's-free BT calling is very quiet over the speaker, to the point where I need to blast the volume and quickly turn it back down when a call ends or drops to avoid rupturing an ear-drum when the radio kicks back on!
Not sure if this is it but adjust the volume on your phone during the call as well as the radio volume. If BT is turned down the radio volume will not help much. I am one click below full blast and radio on about half way.
 
Again, a few dozen people does not quantify a "widespread issue" when millions upon millions of the SE's have been sold into active circulation.

Also, this is not confined to the iPhone SE, as users with other model iPhone's and even Android phones are reporting this.

Quit trying to follow the OP and sensationalizing this, when no such sensationalization is warranted.

Out of interest, what will you say if Apple release a patch for this in the near future? Will you admit that it was a bug affecting the SE?

You do realise that small samples can be used to estimate an occurance in the wider population to some degree of confidence? I mean its the basis of statistics. Right now none of us know the whole picture based on the information given in the original article.
 
  • Like
Reactions: Fyxxxr and r3dflame
Apple has had wireless protocol issues for years. Heck, I can't use Bluetooth while simultaneously using AT&T wifi calling. My headsets (multiple) disconnect and reconnect frequently, or voices start to come in garbled after some minutes on the phone.

That, despite being connected to 5ghz wifi. Just bizarre. If wifi calling is off, no issues. If I use FaceTime over wifi, no issues.

This is on s 6s Plus.
 
  • Like
Reactions: motulist
Hey Apple, you are a rich company. Go and rent all the popular vehicles and test your damn products. You spend millions on stupid wooden tables and celebrity endorsements, yet you always have these annoying bugs that should have been identified in testing.
 
Out of interest, what will you say if Apple release a patch for this in the near future? Will you admit that it was a bug affecting the SE?

You do realise that small samples can be used to estimate an occurance in the wider population to some degree of confidence? I mean its the basis of statistics. Right now none of us know the whole picture based on the information given in the original article.

I won't say anything other than, "Good job Apple", because I have no doubt this could be a bug in iOS, or perhaps a broader issue with the Bluetooth protocol, or issues with interoperating with older Bluetooth hardware protocols.

But my point stands, a few dozen people complaining about this cannot be used as a basis for declaring something "widespread", especially the people that frequent the Apple Discussion forums... Hell, people there will complain it's Apple's fault if they sneeze and a booger get's stuck to their screen and they can't clean it off themselves!
 
  • Like
Reactions: MrGuder
Not surprised. Bluetooth can be flaky from my experience.

Bad excuse. Maybe instead, Apple should just hire for once someone who knows something about BLUETOOTH?!?

I mean think about it. They've had nothing but problems with Yosemite & El Capitan regarding bluetooth El Capitan STILL has unresolved bluetooth issues I keep reporting to no avail.

Get your BLUETOOTH in order Apple!
 
It's funny because I have been avoiding updating to 9.3.1 but not because of this, just because 9.3 has been working so great and I don't want to ruin a good thing right now. I connected to wifi the other day and the update started downloading so I had to go into iCloud storage and delete the download and set it back to manual updates.
 
The old saying of, "There are lies, damn lies, and then statistics" holds true here. That report is about crashes only. System crashes aren't the only measurement for OS stability. There's a world of variety in OS issues that wouldn't trigger a crash; this BT issue being an example of one. If you're going to use sweeping generalities you should, at a minimum, understand what your supporting evidence actually means. As it relates to your posts in this thread, 'most stable release' doesn't mean what you think it does.
 
I'm still on 9.3 and not having any of these problems.

Are your Bluetooth devices using the 4.x protocol? Mine are all 2.x and I've had the issue on two SE's.
Wonder if it's isolated to an older version of Bluetooth?
 
Hey Apple, you are a rich company. Go and rent all the popular vehicles and test your damn products. You spend millions on stupid wooden tables and celebrity endorsements, yet you always have these annoying bugs that should have been identified in testing.

Wow, could you possibly be any more obnoxious in your commentary?

Do you know how complex of an operating system iOS (or any modern OS for that matter) is? Do you know how many millions of lines of code it contains?

How about you go try debugging and testing something that complex, and then come and talk to us...
 
  • Like
Reactions: uid15
Are your Bluetooth devices using the 4.x protocol? Mine are all 2.x and I've had the issue on two SE's.
Wonder if it's isolated to an older version of Bluetooth?
Not sure what # my car is using will have to check settings later.
 
Pssht, welcome to my world. I've been having bluetooth issues since forever. Apple watch loses connectivity to my phone every day or two and have been accustomed to reseting bluetooth like i'm checking my email.
Interesting. I've definitely run into BT issues with Apple products, but never with the Watch.
 
Turn off WiFi and see if that helps. There are chronic issues with WiFi interfering with BT all over the industry.

LOL yeah no. While Wi-Fi and BT share the same 2.4 GHz band (same as microwave ovens), the only "chronic issues" most people are experiencing in that regard is the WLAN crapping out when you're nuking a cup of coffee or that Pandora stops playing music once I'm a block away from my Wi-Fi access point because it doesn't jump to LTE by itself.
 
Interesting. I've definitely run into BT issues with Apple products, but never with the Watch.

Well I know the watch isn't the problem. I'll usually see the issue in the morning when I use TouchID to unlock my phone, but the watch (already on my wrist) stays locked. I've reset the watch and tried unlocking TouchID on my phone again and it still stays locked on the watch. I turned off/on BT on my phone and then did an unlock and the watch unlocks as it should. I've also seen issues where my phone won't connect (until BT is reset) to my home phone (essentially a landline phone that pairs to my phone via bluetooth so that i can answer/make calls throughout my house without having my phone on me)..
 
Wow, could you possibly be any more obnoxious in your commentary?

Do you know how complex of an operating system iOS (or any modern OS for that matter) is? Do you know how many millions of lines of code it contains?

How about you go try debugging and testing something that complex, and then come and talk to us...

Yeah, sounds good. Give him Apple's resources (billions of dollars, and every and any engineering specialist they could desire), then see how he does.
"millions of lines of code"...? What? you think that's a lot? EVERYTHING has millions of lines of code. So what?
 
#bluegate

It is a real issue.

Actually we shall see. If there is a software fix, then it isn't an issue. It will get fixed. Too soon to say.

But if it is a hardware issue, there may need to be some retooling, replacements, or refunds (like if the phone just doesn't work with your car.)

Someday Apple is going to release an iPhone that needs to be recalled. Or at least some large portion of the build needs to get recalled. That is going to be a very bad day for Apple. I know they work really really hard to avoid that outcome. But it is going to happen. And assuming Apple has its contracts set up right, that moment is going to be very bad for the component producer who made the component that causes the recall. But it will be worse for Apple. And it will be a bad day for me as a shareholder.
 
  • Like
Reactions: KPandian1
My mom and I just got ourselves our first bluetooth headphones for our SE's. We just returned them because the call quality was crap but the music was great. It's unfortunate we just returned them, now that I know our issue is the phones, not our reception or anything.
 
I'm quite shocked that Apple haven't yet hired most of you, since you seem to know what Apple need to be doing in almost every single facet of their business, and seem to have the answer to all problems, 365 days a year. With such insight, each of you would surely already have been snapped up by another company, being put to work so hard that you'd not have had time to spend more than ten mins on a forum before dropping off to sleep with exhaustion.

Your multiple visionary skills are extremely valuable, so what are you doing loitering on forums, handing out your valuable advice free of charge?
[doublepost=1460397847][/doublepost]
#bluegate

It is a real issue.

Actually we shall see. If there is a software fix, then it isn't an issue. It will get fixed. Too soon to say.

But if it is a hardware issue, there may need to be some retooling, replacements, or refunds (like if the phone just doesn't work with your car.)

Someday Apple is going to release an iPhone that needs to be recalled. Or at least some large portion of the build needs to get recalled. That is going to be a very bad day for Apple. I know they work really really hard to avoid that outcome. But it is going to happen. And assuming Apple has its contracts set up right, that moment is going to be very bad for the component producer who made the component that causes the recall. But it will be worse for Apple. And it will be a bad day for me as a shareholder.

I don't know how you do it, being so cheery and uplifting, but thank you - you're a real inspiration and a fresh breath of oxygen. :)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.