Activating the keyboard vibration that iOS 16 offers you could use more battery on your iPhone
iOS 16 brought a lot of changes to the iPhone and a level of customization for the lock screen that allows you to give it a very special touch. One of these changes was the haptic keyboard vibration, which is nothing more than a small vibration when pressing a key. Despite being one of the added functions that users liked the most, the reality is that if you activate the keyboard vibration of iOS 16, you could use more battery.
When this function is activated, the iPhone emits a slight vibration just after each keystroke, confirming that you pressed that key. Although this new function is something that was already in other mobiles from the competition, the reality is that it has caught on very well with Apple users, as it is one of the things that iOS 16 added that has more positive reviews.
Activating the vibration of the iPhone keyboard could consume more battery
Nevertheless, Apple has issued a document where he warns -or rather announces- that enabling keyboard haptic vibration may result in increased battery drain. In other words, if you activate the keyboard vibration your phone will download faster. If you don’t have this feature activated yet and want to try it, here’s how to activate the haptic vibration of the iPhone keyboard with iOS 16.
But not to worry, while any such addition reflects more battery usage, the truth is that impact on battery life should be minimal. Although if after trying this new feature you have seen that there is a noticeable change in the battery life of your iPhone, we recommend that you disable haptic vibration:
- Go into Setting.
- Click on sounds and vibration.
- Click on keyboard vibration.
- deactivate Vibration.
The new function of haptic vibration is only available on iPhones 8 and later running iOS 16. Although it can be negative that the vibration of the keyboard consumes more battery, it is important that Apple is already aware of what happened. So it is very likely that in future updates of iOS 16 the problem will be solved.