Home > Apple > iPhone

iPhone Black Screen During Call & Voice Record in iOS 16.2 [Fix]

In this guide, we will show you the steps to fix the black screen during calls and voice recordings on iPhone running iOS 16.2. The sixteenth iteration of the OS build has bought in a truckload of new and intriguing features. On the flip side though, it could also be the first OS to be bugged with so many issues, right from Day 1. And this list continues to be growing every other day.

iPhone Black Screen During Call

As of now, numerous users have voiced their concern that they are getting a black screen during calls and voice recordings on iPhones running iOS 16.2. if we talk about calls, then due to this issue, they aren’t able to end their calls or carry out other in-call related activities, such as switching to the speaker. Moreover, during calls with customer care, they usually have to input a number, which unfortunately is no longer possible in the current state.

iPhone Black Screen During Call

Likewise, during voice recordings, they aren’t able to stop the recordings. All these issues aren’t just affecting normal calls and voice recording, carrying out these tasks via third-party apps like WhatsApp, Telegram, and Discord are equally troublesome. A few such issues were first reported during the initial iOS 16 launch but with each bump in the software version, the number of such reports are growing exponentially. If you are also getting bugged by this issue, then this guide will help you out. Follow along.

Fix iPhone Black Screen During Call & Voice Record in iOS 16.2

iPhone Black Screen During Call

  1. Head over to Settings > Accessibility > Touch.
  2. Then go to Touch Accommodations and turn it on.iPhone Black Screen During Call
  3. Now go to Use Initial Touch Location > Swipe Gestures.
  4. Then enable it and choose Standard from the list. That’s it.

This should help you fix the issue of a black screen during calls and voice recordings on iPhone running iOS 16.2. As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly. In the meantime, the aforementioned workaround is your best bet.


Share: