Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS 16.1 iPhone volume controls during call not working
- Thread starter RickNY
- Start date
- Sort by reaction score
The volume buttons work fine during a call with the screen dark while holding it to my ear on an iPhone 14 PM running 16.2 RC.
Yes , they fixed it for your model with iOS 16.1.1. iOS 16.1.2 and all the betas of 16.2 did nothing to fix this bug for those who own 12 or 13 series
Volume controls does not work on my iPhone 13 Pro with 16.2 RC. Have to move it away for the ear to light the screen and then it works.
Still not fixed for all models except iphone 14 actually. good job apple. freeform vs basic functionality 1-0
i tried to provide feedback here
Feedback - iPhone
Apple wants to hear from you. Send us your comments and feedback about iPhone.
www.apple.com
and the last ios version they have in their drop menu is 16.0.2
seriously?
I have an iPhone 12, with IOS 16.2 it hasn't been fixed yet. But I noticed one thing: when I DISABLE the silent, the volume controller on call works. It never works with voice notes (e.g.: whatsapp)
Interesting. I’ve tried the silent mode on my iPhone 12 and it is still not working
It works for me when silent mode is turned off. But only for the volume on call not for the voice notes.
Not fixed on my iPhone 13 Pro after installing 16.3 B1. I’ve no words.
Obviously Apple doesn’t think their phones should support changing volume of phone calls. What has Apple become?
I would also report that when in call, if you go to home or another app like Maps as said by Stephan55, the screen goes off and the volume works "as usual". The volume controls are broken only on main Phone screen (or Whatsapp or Telegram when triggering earpiece audio), not if you change app.
Can't reproduce this. I tried starting a phone call, switched to another app, and held the phone up to my ear. I was still unable to change volume of the phone call. iPhone 13, IOS 16.2.
Just registered to confirm that on 16.2 this still persists, at least on a 13 Pro Max, and that is perfectly reproducible. Whoever let this bug make its way into multiple releases should be fired without severance and change careers.