Bluetooth problem with the iPhone 15 about 6 months after its release

Bluetooth problem with the iPhone 15 about 6 months after its release

With the iPhone 15 having been on the market for a few months, you would think that the major post-launch issues would have been resolved by now Apparently not so for some users, who have complained of ongoing Bluetooth connectivity issues since its launch

These users have expressed their frustration on Apple's Support Community and MacRumors forums Apparently they are having problems keeping their iPhone 15s connected to older Bluetooth systems, including cars and headphones Some have experienced problems with more recent systems, such as Apple's own AirPods

One user stated that he regularly experiences Bluetooth issues with his new iPhone and 2014 BMW, but that a software update often solves the problem not so with the iPhone 15, which regularly disconnects from the car's Bluetooth disconnects, forcing drivers to use the phone's speaker

They noted that this does not happen with another iPhone 12, and other drivers have responded to confirm that it happens in their cars as well Including BMW in 2011 and Audi in 2013

Another Apple Support Community user claims that the iPhone 15 Pro Max works with in-car Bluetooth, but struggles with the AirPods Max and Beats Studio Buds Apparently, calls disconnect after 5-10 minutes while music is repeatedly interrupted or disconnected They are not alone, with one respondent joking that it "just keeps getting worse" Another stated that his older iPhone 12 Pro did not have this problem and that it started after he upgraded to an iPhone 15 Pro

Obviously, these are not the kind of problems one would want to experience with a high-end device costing several hundred dollars However, given that new products always have problems in the beginning or within a few weeks, it is forgivable

The fact that users still seem to be plagued with these problems almost six months later is another story altogether In particular, some users were told that the problem would be fixed in a future iOS 17 update iOS 174, the fourth major release, is about to be released, and apparently it has not yet been fixed Hopefully Apple will get its act together and fix the problem soon

Categories