I'm pretty confident this is a software bug in the new ios release; at least that's the issues I'm having. An order / priority of execution problem. I'm having to reboot multiple times a day since going to version 16. versions 16.1 (e.g. 16.1.1 and 16.1.2) were a big issue with the typical reboot sequence struggling to work. There would be long pauses where I would have to practically sit on the buttons before I'd get a response from the op system. Going to 16.2 has now avoided the freezes trying to reboot, but I'm still having to reboot multiple times a day because when dialing out the phone is saying I'm calling, but doesn't provide the normal ring tone when going to connect, eventually starts counting as if connected; sometimes, sometimes not... still saying connecting and not counting. At that point it really is connected and the user at the other end can hear me, but I can't hear them. At other times it does connect and count quickly, but the user can't hear me nor can I hear them. They hang up on me, of course. I reboot the phone and voila, it immediately gives me the ring tone on dialing out and immediately connects. I do not know what issue has been created but others are experiencing it. I ran into a guy who just bought a brand new iPhone 14 and is having the same problem. I suspect it is certain functionality or software use that is creating the issue, as it is only sporadic with certain users. Additionally, there is a huge detail that has occurred with Apples own navigation app. I can't use it anymore. It delays and hangs. I've used it routinely and now I've had to go to Google's map navigation, which works fine. Also there is a large magnitude of delay when searching in contacts. I took programming and while I don't program, I've designed systems and have had them custom coded and have troubleshot with programmers and trained users and have managed IT. Apples doesn't have their act together on this one. I've spent hours on the phone and have gone into the Apple store and they've run diagnostics. It's definitely a code issue in the new release. Unfortunately, it's not affecting enough people they've bothered to figure it out yet.
