Q: iPhone SE Bluetooth issues

But I don't understand why some says that hardware is involved. For me it is possibly linked to the BT driver, and in this case I don't understand why Apple should setup a workaround to resolve this issue.

I'm not a professor, and I don't know  what causes the problem.

What I do know is, that "so far" the fourth version, works very well for me.

O problems until now, same quality as the 5, 5S and 6 incoming sound BT car.

I'll answer that question with another question:  If in fact Apple has solved the SE bluetooth issue with the 9.3.2 beta, what keep silent about it while many, many SE's are being returned?  Every one I know who got an SE (5 people), except one person, has returned their SE.  Why not say "hold on, we'll fix this for you"?

For Apple dev-team I'm disable (profound hearing loss) so I demand always on BT please fix this bug and contact with us about this issue.

we're loyal apple users and biggest supporters but we need to communicate with us!!

Can understand everyone's frustration that have the issue and also with Apple's lack of communication (not really unusual going from previous experiences is it!) - but comments ref it could be hardware related I find hard to accept, basically because mines been working fine from the off.

Now unless SE's are being produced with different chips why is mine ok (and why if different chip are being employed would not Apple replace returned with the working variety?).

I'm not a Dev but with reports coming out that employing the updates help a lot of people does it not point to software and may be a conflict between the two wireless systems (BT and WiFi) that still requires bottoming out. Had issue on iMac when Bluetooth interfered with any sort of longish download and caused the connect to drop, switching to wired keyboard and mouse resolved until an update was finally released.

It's only my view but think software clash is still the most likely.

matt31500 wrote:

 

But I don't understand why some says that hardware is involved.

Because they don't know what they are talking about, that's why. Since Bluetooth 4.0 came out device makers acquired the ability to update the hardware firmware via a software update. Therefore, regardless if the problem is in the HFP protocol in the Bluetooth stack (likely), or it's in the hardware firmware (unlikely), it can be fixed with software. Unless the BT chip cannot communicate to another BT device at all, which is not the case here, it can't be a hardware problem.

As you are very clearly an expert in this field and I quote ' Since Bluetooth 4.0 came out device makers acquired the ability to update the hardware firmware via a software update'

Could you please explain how this product was shipped with an inability to communicate with the vast majority of Bluetooth devices. Clearly, the SE is not a complete facsimile of the 6s internally, otherwise the product would actually work!

So one can imagine the scenario where the BT chip has been changed or is not the same as the 6s and now, to correct an almighty mess apple issue a software/firmware upgrade to fix the problem.  This still doesn't mean that hardware changes are unlikely and not already in the pipeline.

PS  what do apple do with all the handsets returned that don't work?

Yes, dcpmark fashions himself an expert.  However, and as you allude to, a kindergarten child can conclude that there must be a hardware difference between the SE bluetooth implementation and every other iPhone, or we would't be having this SE bluetooth issue on the very same iOS versions that work perfectly in the other devices.  Whether it is a hardware "problem," a hardware "difference," or a hardware "issue" seems to very important to the self-proclaimed experts here.  But the users have already concluded the obvious, no matter what the ultimate solution.

355f wrote:

 

As you are very clearly an expert in this field and I quote ' Since Bluetooth 4.0 came out device makers acquired the ability to update the hardware firmware via a software update'

 

Could you please explain how this product was shipped with an inability to communicate with the vast majority of Bluetooth devices. Clearly, the SE is not a complete facsimile of the 6s internally, otherwise the product would actually work!

 

So one can imagine the scenario where the BT chip has been changed or is not the same as the 6s and now, to correct an almighty mess apple issue a software/firmware upgrade to fix the problem.  This still doesn't mean that hardware changes are unlikely and not already in the pipeline.

 

PS  what do apple do with all the handsets returned that don't work?

First of all, let's establish that in my experience, Apple has ALWAYS had inferior BT stacks compared to Android. Because BT is not a standard, a BT stack can be built in different ways, and Apple appears to be more interested in other factors such as quality and security at the expense of compatibility. This is not the first time a new iPhone had widespread BT problems, and it probably won't be the last.

BT is supposed to be fully backwards-compatible, but it's not. The older the device the less likely it will work well with the newest BT devices, and many OEM car kits are based on much older versions of Bluetooth. BT 1.0, 2.0, and 3.0 devices are NOT user-upgradeable OTA, and virtually no manufacturers will spend the resources to update them. Many 4.0 and 4.1 are upgradeable, but again the manufacturers are not going to waste resources to do so.

The SE Bluetooth does in fact pair and communicate with every other BT device.....in fact, it likely works well with every BT device Apple sells in their store. And some people reported they did not have trouble with their particular car kits and headsets. My SE didn't work in my 2014 Acadia Denali, but worked perfectly out of the box in a 2016 model. But there are tens of thousands of BT devices, and it's simply not possible to check every one, or even a majority. The problem is Bluetooth itself.....every one of those devices is certified by Bluetooth, which is supposed mean they should work together.....but because Bluetooth has become a money grab they don't, and no one seems to care.

Apple doesn't give a rat's arse about how many are returned......there is nothing wrong that 9.3.2 won't fix, and they will update them and give them out as AppleCare replacements. Remember that by nature message boards attract those who are having problems......you don't usually hear from the masses that have no problems, and believe it or not, MOST people in this world don't even know about or bother coming to message boards to complain or praise.

Compatibility is based on the vehicle?  If there any users here, or anywhere, who reported that the SE worked with their vehicle out of the box please list them.  I don't recall seeing any, anywhere.

Thank you for your information- very interesting, I fully understand about  reticent theoretical backwards compatibility.

I quote 'And some people reported they did not have trouble with their particular car kits and headsets'

I have a Mercedes, the SE doesn't work with my vehicle or ANY Mercedes in the new car showroom. My associate has a Porsche, the SE doesn't work with that or ANY new models in the showroom, my sales team have Audis, the SE doesn't work with ANY of those 9 vehicles or any models in the showroom.

Perhaps you could tell me which vehicle manufacturer the SE actually works with and it would seem an easier route to buy the car rather than bother with this debacle !!

mreg376 wrote:

 

Compatibility is based on the vehicle?  If there any users here, or anywhere, who reported that the SE worked with their vehicle out of the box please list them.  I don't recall seeing any, anywhere.

Posters reported clear BT audio during phone calls prior to Beta 2 being released for the following (MR = MacRumors, TT = this thread):

2016 GMC Acadia (MR)

2015 Audi TT Mk3 (TT)

2013 Toyota RAV4  (MR)

2015 Ford Focus (MR)

2015 Ford F150 (MR)

2015 Acura SH-AWD (TT)

2013 Dodge Journey (MR)

2016 VW Tiguan (MR)

Plantronics M25 headset (TT)

Skull Candy headset (MR)

Bose headset (model unknown) (TT)

Uniden BT Cordless phone (TT)

Unnamed headset with BT 4.1 (TT)

Unnamed BT headset purchased at a Verizon store, (MR)

Sony SRX-X33 BT speaker (TT)

Finally, prior to Beta 2 being released, the poster "elzale" reported in this thread that by resetting his network settings his SE was now working fine on both his car kit and his headset, but he didn't identify the makes and models of either.

355f wrote:

 

Thank you for your information- very interesting, I fully understand about  reticent theoretical backwards compatibility.

 

I quote 'And some people reported they did not have trouble with their particular car kits and headsets'

 

I have a Mercedes, the SE doesn't work with my vehicle or ANY Mercedes in the new car showroom. My associate has a Porsche, the SE doesn't work with that or ANY new models in the showroom, my sales team have Audis, the SE doesn't work with ANY of those 9 vehicles or any models in the showroom.

 

Perhaps you could tell me which vehicle manufacturer the SE actually works with and it would seem an easier route to buy the car rather than bother with this debacle !!

Ha! You do not need to buy another car. Very soon (perhaps as soon as tomorrow), you will be able to update your SE to work as it should with your Mercedes.

HI

I did reported my car brand on my original post.

It's a Seat Altea Freetrack 2009.

After resetting my network settings BT became ok and still is.

I have not upgraded to any beta or done anything else.

I don have nearby my BT headset to check the brand, I'm on a trip these days. But I'll do when back home.

I returned my handset, that of my business associate and six purchased for our sales team last week.

I do not intend to be a beta tester for Apple, I need a product that works out of the box.

I will wait six months, then look at the situation again- when they update the internals!

Apple have put my company to a lot of trouble, being economical with the truth over the problem and insisting one goes through ridiculous procedures that don't fix the issue.