goonie4life9
macrumors 6502a
So much for the “rapid security response” approach, I guess?
Nor is everyone upgrading to the .0 release
I remember that requirement was lowered on a previous update, iOS 16.5. Now it only requires a minimum of 20 or 30%14 Pro Max updated with 40% battery left. It has always been a requirement of 50% or more. Maybe security updates don’t need that now….
I guess I’ll wait for iOS 16.7
Well, iOS 15.7 didn’t have betas either a year ago. It was released as a RC few days before iOS 16iOS 16.7 might not happen, as we have not had any betas for it and iOS 17 should be out in less than two weeks.
Might not be a bad idea.Wisdom says to wait a day or two just to see if there's any bricking going on.![]()
If your magsafe charger is a Belkin device, you may want to search for those articles. There was a problem, but I don't know if/when it might have been resolved.I hope this fixes a MagSafe bug that I've encountered on the 12 Pro. Every once in a while, MagSafe charging would stop and until I restart the phone, charging via MagSafe is uncertain. The typical case I've seen is when you put the phone on the MagSafe charger, it would start charging but at some point it would stop (not related to optimized charging or charge only using green energy period). From that point on, further use of the phone would continue to discharge the battery. Only a restart of the phone has solved the problem.
Sometimes I get that alert, but I've noticed that at least some of my devices will update as long as they're charging. Maybe that rule is different now for newer Apple devices?14 Pro Max updated with 40% battery left. It has always been a requirement of 50% or more. Maybe security updates don’t need that now….
If your magsafe charger is a Belkin device, you may want to search for those articles. There was a problem, but I don't know if/when it might have been resolved.
Happy to hear!iOS 17 is pretty much a fine-tuned iOS 16, with very few actual changes. An average user might not even notice a difference between the two.
The latest iOS 17 beta is quite stable and works very well.
That was so funny I forgot to laugh.Im not upgrading to 17
I was wondering that too.I wonder why this was not an RSR.
Not if they’re smart.Nor is everyone upgrading to the .0 release
That’s my ride.I can't wait for 17.1.
Anyone else update and lose their Reminders/ Completed Reminders in the Reminders app? Lose all on iPad/iPhone and MacBook Pro? And if so have any solution as to how to get 'Completed Reminders ' back???/
Apple today released iOS 16.6.1, iPadOS 16.6.1, and watchOS 9.6.2, minor updates for the iOS, iPadOS, and watchOS operating systems that came out last September. The launch of iOS 16.6.1 comes over a month after the release of iOS 16.6, an update that brought bug fixes.
![]()
iOS 16.6.1 and iPadOS 16.6.1 can be downloaded on eligible iPhones and iPads over-the-air by going to Settings > General > Software Update. It can take a few minutes for the updates to propagate to all users because of demand.
watchOS 9.6.2 can be downloaded for free through the Apple Watch app on the iPhone by opening it up and going to General > Software Update. To install the new software, the Apple Watch needs to have at least 50 percent battery, it needs to be placed on a charger, and it needs to be in range of the iPhone.
According to Apple's release notes for the updates, they includes unspecified bug fixes and security improvements.
Article Link: Apple Releases iOS 16.6.1, iPadOS 16.6.1, and watchOS 9.6.2 With Bug Fixes
Read mine above….Guess I'll update. No bad results posted.
I checked mine and they seem to be fine but I'm not a heavy user of reminders.Read mine above….
iOS 17 is pretty much a fine-tuned iOS 16, with very few actual changes. An average user might not even notice a difference between the two.
The latest iOS 17 beta is quite stable and works very well.
Yes there are 300+ reported new features and changes. There are video posts in the 17 beta thread. Have a look.I thought a lot of new features and some device support were being added to iOS 17. Is this not the case?