Hi!
As some of you have reported, since upgrading to Ios 27.2, the voice started glitching like crazy, to the point of being unable to type fast or navigate through the screen.
How the bug was replicated? It was extremely inconsistent. Some people had it when recording whatsapp messages, others including me had it while watching videos, others thought it was a specific voice issue, some said it was out of the blue, and the lucky ones never experienced this problem.
I managed to fix it for good, if anyone wants to try my solution, here it goes:
1) Reset voiceover settings. Head to Settings -> Accessibility -> Voiceover -> Reset voiceover settings.
All my custom gestures, voice and feedback settings went away. I had to set up everything again, but I initially thought it was worth it, since the glitches reduced substantially.
For most of you, the second step is unnecessary, after a reset and reconfiguration, it will be good. But not for me, so in case it doesn't solve for you, there is the extra step.
2) Be careful of the "voice" setting. I use Eloquence, so I changed the main voice to him. But Voiceover has an annoying thing on certain apps, even with my settings to auto change voice and language turned off, it will read text in English with the default american vocalizer voice. So the way I found to force Voiceover to stay in Eloquence, was to put him both as the default and additional voice, and change the "voice" rotor to Eloquence.
I even thought Eloquence was the problem, and changed the voice to Vocalizer. But since the problem didn't go away, i found out it was not.
The actual bug is, for some reason, if I maintain any voice forced through the rotor, it will glitch. But if I keep it as the "default voice", it's good and won't glitch.
In case I have an app that insists on using the american voice, I just use the rotor to switch back to Eloquence temporarily. After what I need to do is done, I revert to "default voice" in rotor and no problem happens. No glitches and Eloquence running smoothly.
If Voiceover was glitching, you try this solution, post your results here. Let's find evidence that this is the bug so we can report how to replicate it to Apple.
In summary: Try a voiceover reset, then make sure you choose the voice you like as the main voice. This should be good already, but if you encounter the same problem as me - need to force voice to not change - configure the same main voice as an additional one in the rotor.
Comments
Nope
Tried this a few weeks ago, and again last week, didn't work at all. I only use my default voice as I never have any in the rotor, and its still as glitchy as it was before. Have submitted multiple reports to Apple, but at this point, who knows
doing what apple couldn't/wouldn't do
all of us having to do apples work for them and we arn't even getting ;payed for it. we all need a rase bruh
Re: doing what apple couldn't/wouldn't do
Apple can’t do the same work as us. They are not and users. They need our help. And I’m for one and willing to give it. I know not everybody can or has time or wants to. But I will help them as much as I can.
Re: doing what apple couldn't/wouldn't do
i understand that, and i'm not wanting to be a broken record here, because for about 10 years probs more here, the question is, who tests stuff outside of us?
Need to be caught up
I haven't upgraded to 27, and discussions of voice glitches are scattered through several threads. When everybody talks about voice glitches, is all of that about the 20-30 second hang? That and mention of a problem with external audio devices are my reasons for still holding back.
Is the voice hang tied to rapid swipes or other actions that send a lot of rapid-fire utterances to the speech engine? If so, has anybody clocked it?
There aren’t enough people Accessibility testing during beta.
There aren’t a lot of people test during the beta cycles so we have to help Apple during the regular year. It’s not a problem. You just do a little bit of it at a time. You don’t have to do it all at once. They’re more than willing to help you work with you. I’ve thought I’m going cases with them for like sometimes a couple of weeks or months even when how bad it was and then we’re willing to help with it. Hey they’re not gonna know what’s wrong if we don’t tell them and they always tell you that so they’re not doing their job. They don’t know what the jobs are to do and then when we tell them they work on it. And for somebody who was gonna come on here and tell me oh we tell them for years nothing happens. You try programming the code to make these work and then you can talk to me about it. It’s gonna be a whole lot more complicated than that plus we’re not the old Accessibility features they have. I bet you anything if you went onto regular sided peoples iOS forms on Facebook cause I have we’ve been having all kinds of crazy bugs with their stuff too. People that regret updating all kinds of stuff. I’m done here. I’ve said enough to get the idea if you’re willing to work with Apple, they’re willing to work with you if you have time to do it go ahead and help them troubleshoot. If not, then I’ll try to do what I can to help all of you. I’m not gonna lie, I actually enjoy helping all of you OK so if there’s something you genuinely feel like the Apple isn’t doing that you need them to do and I happen to be able to reproduce it. I’ll do what I can. It’s kind of a passion of mine to make sure that everything is working OK for all of you and Maine and I know how frustrated it can be for us so I try to do what I can. As I said, I know people do not always have time or ability to do this so I wanna do what I can.
There aren't enough people testing during betas
Singer Girl
You hit the nail on the head.
RE:
How do you go about reporting issues to apple?
Because the voice glitch isn't the only one that came recently, don't wanna go off topic.
Comment
Hi, if you’re on the beta, you can use the feedback app. I also recommend attaching a screen recording to the feedback—it really helps a lot.
re. singer girl
hav you conciderd that most people on this site would probs only hav one device. that device is there one and only device. if i didn't hav belief that this mac would work with thees betas just fine there would be no way i touch them with a berning mettle stick.
not everyone would get a second device just to beta test. not everyone is technicly savvy as well or anything like that. i'm just saying it's not as easy as you might think it is
They might get more testers if:
They actually told people what they should be testing, and responded to feedback. I have another device, but I send enough comments into black holes already.
Seems it came back
Seems the glitches came back since the last update 27.2.1, even though it's now more on specific scenarios than out of the blue.
Noticed it while using Youtube, both on the web browser and in the app, and Instagram reels.
In the Youtube the glitches are more moderate, occurring when you exit a video to browse the next one, on Instagram even the audio of the video will cut from time to time, and Youtube on the browser is the worst, making voiceover get silent for some minutes.
Discouraging, I was thinking to get a new Iphone to enjoy the Apple Intelligence features, especially since what was working since the beginning - rudimentary descriptions - was worsened since these last updates. But now I don't quite know what to do.
If people report it I'm sure it will get fixed
I would still get a new phone. Things will only get better. Things unfortunately aren't fixed in a day. They need good feedback. For those that expect Apple to respond to every report and give you a "list" of what to test that isn't realistic. That is the entire point of testing. Everyone uses their phone computer or devices differently with different apps ETC. There is no way apple can test with every configuration.
Not a beta tester
I'm not a beta tester, seems this is the only way to report bugs?
Re: Not a beta tester
I'll explain why I think it is the best way.
1 they get your logs automatically.
2 You can and should do this. You are able to do a screen recording. If screen recording isn't there in the control center I put it there. I also turn the microphone on.
I find screen recording in the control center. swipe up to open controls.
I find microphone by default it is off.
I turn it on.
Then when I start the screen recording they can hear my TTS and If I want to talk they will hear me.
So I would demonstrate where the speech skips.
example: Applevis.
I would make it skip. and say something like as you can hear when I'm on applevis the audio is crackly.
If I go to google.com as you can see and hear it isn't.
If you could please fix this as it makes it difficult to understand the screen reader I'd truly appreciate it.
Remember you always get farther with a company with honey then vinegar.