Wireless charging on iPhone 11, iOS 13.0 vs.  iOS 13.1

iOS 13.1 is reducing wireless charging to 5W on iPhones with certain chargers

Although it is not a killer-feature, the wireless charging (present on all iPhones from 8 onwards) is a hand on the wheel in some situations – whether to leave your device lying on the nightstand at night or standing on a stand, next to the computer while you work.

Since iOS 11.2, all iPhones that support wireless charging can receive recharges up to 7.5W, as long as your charger is compatible with that rate. However, ChargerLab noticed something strange when he updated his iPhone 11 to iOS 13.1.

The site team had measured the wireless charging capacity of the new device when it was still running iOS 13.0 and did not notice any peculiarities: the charger started to emit power at more than 10W, and the device received this recharge in the traditional 7, 5W. When upgrading the smartphone to iOS 13.1, however, everything changed: the charger started passing power at about 7W to the device, which started receiving it at just 5W.

This implied a difference in the total loading time, as we can see in the graph below. While the iPhone 11 running iOS 13.0 was fully recharged in 3:19, the same device running iOS 13.1 took exactly 4 hours to reach 100% battery life – that is, approximately 30% slower charging.

Wireless charging on iPhone 11, iOS 13.0 vs.  iOS 13.1

The website team found that the behavior was repeated with almost all wireless chargers available in the newsroom, except for some branded devices like Belkin, mophie, NATIVE UNION, Anker and Logitech – all of them sold in Apple stores. All accessories that were able to recharge the device at 7.5W use a voltage regulation at fixed frequency, which is recommended by Apple.

There is still no official statement from Apple on the case, but for now, the most likely hypothesis is that the company has simply turned off faster wireless charging on chargers that do not have fixed frequency voltage regulation. Anyway, we will have to wait and see if this is the case or if we are simply talking about an iOS 13.1 bug – wait.

via iDownloadBlog