Right AppleInsider. lolAnd yet iOS 9.3 is statistically the most stable iOS in years:
http://appleinsider.com/articles/16...new-release-in-years-app-analytics-firm-finds
Right AppleInsider. lolAnd yet iOS 9.3 is statistically the most stable iOS in years:
http://appleinsider.com/articles/16...new-release-in-years-app-analytics-firm-finds
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.
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.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!
Right AppleInsider. lol
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.
Not surprised. Bluetooth can be flaky from my experience.
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.And yet iOS 9.3 is statistically the most stable iOS in years:
http://appleinsider.com/articles/16...new-release-in-years-app-analytics-firm-finds
I'm still on 9.3 and not having any of these problems.
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.
Not sure what # my car is using will have to check settings later.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?
Interesting. I've definitely run into BT issues with Apple products, but never with the Watch.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.
Turn off WiFi and see if that helps. There are chronic issues with WiFi interfering with BT all over the industry.
Interesting. I've definitely run into BT issues with Apple products, but never with the Watch.
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...
#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.