Happy Friday guys! Let's begin today with my iPhone having a meltdown. I had a report because I wasn't gonna go sitting there log diving and analyzing and trying to explain what happened. But this is how I spend my morning. Let's hope whatever happened was the cause of me leaving my iPhone, not rebooted for about a few days or weeks? No.
Well, my iPhone decided to have a spectacular meltdown this morning. (1/4)
0 Boosts
0 Likes
Turns out, Apple’s audio system had experienced a serious communication timeout, possibly involving a deadlock. Basically, parts of iOS were waiting on each other and getting nowhere. VoiceOver was caught up in the mess. The logs also revealed that VoiceOver had crashed the previous night.
Here’s the bizarre part: connecting my AirPods brought speech back, but the vibrations were still acting strange. Eventually, I rebooted. (3/4)
The logs don’t prove exactly what triggered the disaster, but they confirm something genuinely went wrong.
Apparently, my iPhone decided that accessibility was an optional feature this morning.
#Apple #Technology #Voiceover #Today #MorningSilliness (4/4)
Around 8:35, I was trying to send a WhatsApp message when VoiceOver, the screen reader I rely on, suddenly stopped talking. Completely. The phone was barely responding, vibrations were working only sometimes, and restarting VoiceOver accomplished absolutely nothing.
Naturally, I pulled a 356 MB diagnostic report to investigate. (2/4)