Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
this update has been great for me so far, I was having the bad "Swipe Up" stuttering again, lag everywhere, horrible battery life. All the lag, stuttering and frame drops are gone. It's only been 1 day so I can't comment yet on battery life.
 
  • Like
Reactions: Pearsey
I just uninstalled the mail app.
It was doing a lot of background stuff through the afternoon and the morning, but it seems like it's stabilizing now. I'll keep an eye on it over the next few days. If not I might just jump ship to Gmail.
 
Last edited:
Let’s hope they fixed the reboots and freezing on the 14 pros when charging at night. They fixed it months ago and it was rock solid until about 16.2 then it would happen again but far less frequent. Maybe once a week vs every day. A few of my friends noticed the same thing.
 
HomePod 2nd gen shows up as No response 24/7 here now (it‘s updated to 16.3.2 and iPhone etc on latest release also).

Where is it showing as no response? In the Home app? If so, since this &*^% update including 16.3.2 on HomePods and Apple TV, all mine are doing the same (mixture of original and mini). Have to keep restarting my iPad and iPhones to (temporarily) correct it.
 
Perhaps Las Vegas, NM?
It may have gotten confused but I have my location set. So I don’t know where NM came from 🫤🤥

3BAE0E62-9E64-49E5-8271-75811967D88A.jpeg
 
  • Like
Reactions: SFjohn
I just got off the phone with Apple. IOS16 removed the ability to adjust the volume while on a phone call and holding the phone to your ear!! And there is no option to change that behavior. I wonder who came up with that feature?
 
Yes and no.

There’s virtually always more than one way to logically implement any particular algorithm / function / whatever. Some are more obvious to the typical human; some use fewer CPU cycles but more RAM; and so on. Some are more energy-efficient one one hardware architecture but not some other.

At the heart of a software engineer’s job is finding a good balance between performance, maintainability, time to implement, and so on.

So it’s not at all hard to imagine something being initially released that works just fine but isn’t the most optimal solution for battery performance — and then a revision later focussed on optimizing battery performance.

All that writ, these are pretty well-trod paths, and all the low-hanging fruit is gone. So, while I wouldn’t rule out a software update improving battery performance, I wouldn’t exactly expect it, either.

b&
It's certainly possible that Apple could make these kinds of optimizations mid-cycle (and you certainly wouldn't get any complaints from me if they did), but given the realities of the annual major release cycle and the pressure to get new features out the door, I would be exceptionally surprised to see this kind of focus from the company as it is today — the litany of longstanding user-facing bugs, UI glitches, and performance issues are evidence of that.
 
Tap to wake that lag that’s there sometimes when the phones been left for a while seems to be fixed.

The restore probably helped that.
Oh man, I didn't know that was a bug. I noticed when I'd touch the screen or press the power button to wake it up, there was a moment of waiting and then an abrupt pop up of the lock screen. The transition wasn't "smooth" like it usually was. I figured my iPhone was processing something in the background.

hopefully it fixes that and battery life
 
STILL constantly getting the "Trust this computer?" Pprompts any time you connect to a computer.

Trust this computer?
Trust this computer?
Please enter your passcode to backup.
Please enter your passcode to update.
Could not update because you did not enter your password for the 5th time in the 10 seconds we gave you to respond. Try again.
This is new behavior since iOS 16n not a bug. iMazing has an article discussing it. Its due to enhanced security.
I just got off the phone with Apple. IOS16 removed the ability to adjust the volume while on a phone call and holding the phone to your ear!! And there is no option to change that behavior. I wonder who came up with that feature?
Not true. This was a bug early on and was resolved in 16.3. (one of the betas). Still working fine in 16.3.1.
 
  • Like
Reactions: blueeyes2die4
Oh man, I didn't know that was a bug. I noticed when I'd touch the screen or press the power button to wake it up, there was a moment of waiting and then an abrupt pop up of the lock screen. The transition wasn't "smooth" like it usually was. I figured my iPhone was processing something in the background.

hopefully it fixes that and battery life

Yeah I found when the phone had been snoozing for a while, especially in the morning, it took a couple of taps.

Instant now. IP14
 
This is new behavior since iOS 16n not a bug. iMazing has an article discussing it. Its due to enhanced security.

Pretty sure it’s a bug. Apple’s support article was updated last month and still says trusted devices are remembered.


These computers remain trusted unless you change which computers you trust or erase your device.
 
  • Like
Reactions: sbailey4
I just got off the phone with Apple. IOS16 removed the ability to adjust the volume while on a phone call and holding the phone to your ear!! And there is no option to change that behavior. I wonder who came up with that feature?
Are you talking about the volume of the person you are on phone with? If so I can still adjust it with buttons while holding it to the ear on 16.3.1
 
I’m on the beta and received this update yesterday. My main complaint of the beta build is data drops. Was wondering if I should put this on and see if it helps. Those of you that had the beta installed already and then went to the public release. Have you noticed any improvements at all? Did any of your bugs get fixed?
 
Where is it showing as no response? In the Home app? If so, since this &*^% update including 16.3.2 on HomePods and Apple TV, all mine are doing the same (mixture of original and mini). Have to keep restarting my iPad and iPhones to (temporarily) correct it.
Yep it shows the HomePod as no response in the Home app. I can, as of a few hours ago, select them in AirPlay again but all the Home app accessory settings are inaccessible due to the no response.

The TV app library on my iPhone has long been missing loads of cover photos, now they slowly load in but are from the wrong movie every time (I e.g. scroll to Ghostbusters After Life but it shows a cover from Gladiator)… what a gigantic mess.

tvOS is beyond broken too… the TV app library shows no owned content anymore (movies and shows still work when I search for them but I can no longer browse my library on the Apple TV anymore… jikes).

One of the buggiest releases I‘ve ever jumped on… and I went through every major beta period since iOS 5.
 
I'm an idiot. Everything was going swimmingly with 16.3.1 on my 13 mini until I just had the wise idea to do an IPSW "update" which ended up soft-bricking my device. Attempting to restore software + backup via iCloud now. Lesson learned: IPSW is not always better 😆
 
  • Wow
  • Like
Reactions: addamas and Macx69
I'm an idiot. Everything was going swimmingly with 16.3.1 on my 13 mini until I just had the wise idea to do an IPSW "update" which ended up soft-bricking my device. Attempting to restore software + backup via iCloud now. Lesson learned: IPSW is not always better 😆

Ugh.. and I've been doing nothing but full IPSW updates and nothing OTA.

Sounds to me that right now the only thing safe to update is WatchOS. after that, I'm staying where I'm at until the issues are fixed.

BL.
 
  • Sad
Reactions: sorgo †
Ugh.. and I've been doing nothing but full IPSW updates and nothing OTA.

Sounds to me that right now the only thing safe to update is WatchOS. after that, I'm staying where I'm at until the issues are fixed.

BL.
At first I (perhaps like everyone else) just thought—or hoped—I was being dramatic, but no. My phone seemed pretty thoroughly bricked was throwing a 2015 error in Finder whenever I'd try to initiate a restore or update with the IPSW. Funny thing is, when I Googled that error, it said something about iTunes and/or macOS needing to be updated. My MacBook was updated to 13.2.1 yesterday. I really thought I was going to have to make the trek down to the Apple Store for a minute there but after restarting the computer I finally got it to work.

Frankly the worst **** I've had to deal with in a long time as far as any of my Apple kit goes :)
 
...And now I can't get my iMessage conversations to properly restore from iCloud. Nice one, Apple. Pretty ironic how a public release this late in the game of iOS 16/macOS 13 development can be the most unstable yet for me. :rolleyes:

Anyone have any advice? :confused:
 
...And now I can't get my iMessage conversations to properly restore from iCloud. Nice one, Apple. Pretty ironic how a public release this late in the game of iOS 16/macOS 13 development can be the most unstable yet for me. :rolleyes:

Anyone have any advice? :confused:

The signing window for iOS 16.3 should still be open. Could you revert back to that using your last backup, or download the 16.3 IPSW, and restore as new against that, then restore your backup?

BL.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.