iOS 10.2 was launched the other day by the Apple company for the iPhone, iPad and iPod Touch, and social networks were flooded with complaints from users all over the world. There are many problems that people complain about, but in this article I will focus on battery problems and random shutdowns that happen on iPhone terminals.
You already know that some iPhones were shutting down randomly before iOS 10.2 was released, even if they still had at least 30% of the battery available. Well, in iOS 10.2 things have changed for the worse, so that iPhone terminals randomly close more often, but they also lose battery power out of nowhere during use, something that has not happened until now.
To begin with, those whose iPhone terminals randomly shut down when they still had about 30% of the battery, claim that the problem worsened after the release of iOS 10.2 by Apple. Moreover, it seems that the energy displayed by some iPhone terminals with iOS 10.2 for the battery randomly drops to half without any warning.
iOS 10.2 – battery problems and random shutdowns on iPhone
This problem has never happened before with Apple's iPhone terminals, that is, until now we have not encountered any situation in which the energy in the battery is instantly halved. Of course, it's better than having your iPhone shut down while you're using it, but even so, we're talking about a problem with iOS 10.2 that is extremely annoying.
These problems are reported with the greatest regularity and in increasing numbers by users from all over the world, and the Apple company is certainly aware of them. In general, iOS 10.2 behaved well for many people, even in the beta versions, but the final version brings a lot of unpleasant surprises for other people.
My experience with iOS 10.2 was completely different, without such problems, both on the iPhone 7 Plus and on the iPhone 6S. It is difficult to say why such annoying problems occur with iPhone terminals and if they are not caused by defective batteries, but the Apple company can answer them most clearly.
Having said that, have you encountered problems like this with iOS 10.2?
