Apple Releases iOS 16.5 and iPadOS 16.5, Bringing Sports Tab to News App and Pride Celebration Wallpaper

If you rely on these and are using 16.4 or some such, don't upgrade. If you are playing or stopped and you have your navigation jump set to a time, using that will cause your speech to have a problem when you restart playing. If you have this issue, you'll know because the speech will stop after you've done a swipe up or down while you have that set to a time value like 30 seconds. If you immediately try to start speech, it will mess up again, often stopping even more quickly. Best thing to do is wait a minute before restarting speech and it may well fix itself. Some voices cause more problems than others, Neospeech Paul seems to be one of the worst in Voice Dream.

I've seen a similar problem with bothSpeech Central and Bookshare reader during the beta cycle.

Good luck.

There seems to be no improvement on the voice of a crashing issue, all the other features, I don’t need, and other than the crushing issue iOS, 16.4.1 is perfect over here.

Lol, we're now at IOS 16.5 and they havn't still not resolved the issue when your iPhone is connected to a bluetooth speaker and Voiceover is freaking totally out.
I mean, this bugs is consistent since IOS 14.6, what's the problem to solve it?

Or is focus still spontaneously jumping to the top of the screen one or more times a minute?

I remember on each of the betas I thought it was gone and wrote that in comments only for it to return later. It does seem to be gone but my phone was only restarted an hour ago. I’ll stay cautiously optimistic but update this comment if and when it returns

Yeh, well… Uhm! It returned. So…

I am not having issues that all of you are having. Lucky me. I feel for all of you. I recall with unlucky 13 iOS I had many issues. Using 13 pro that I got last November.

Did you do the following:
1 call apple accessibility?
2 do a screen share?
3 allow them to gather the proper logs?
4 continue to email Apple accessibility about this issue?

They generally want beta feedback through the app, so that's what I do.
If they read the feedback, they know about the problems. Emailing apple accessibility about betas is frowne dupon.

as I write, I feel like I have the hand of trepidation on my shoulder: if I share what I am about to share, will I jinx it? But no, the good of the community must prevail over my own misgivings. If I am right about what I am about to write, others have a right to know so as to make their informed decision. if you are superstitious, don't read the next paragraph:

For me, using an iPhone 13 and good old UK Siri female, the Voiceover crashing and crashing and crashing and crashing bug would appear to have been squashed! it's not happened at all since I updated and during the few hours since that time I have revisited the context in which it used to happen e.g. Facebook, WhatsApp, going home out of certain apps, on several occasions. it's gone, I tell you, gone! Laudamus te, benedicimus te, adoramus tte, glorificamus te!

I don't know whether this is a squashed bug but it's better than where we were: braille display users will be familiar with pressing dot 8 to get enter and instead having the context menu appear. That was how it was in, I think, 16.4 or so. But since going up to 16.4.1A I found that pressing dot 8 would do nothing at all. No, not even a context menu. Others have experienced this, at least with a brailliant, as it features on that Facebook group. Well, as of 16.5 I find that pressing dot 8 once again gets me that context menu. At least that means pressing dots 2-7 to emulate the option key and then pressing dot 8 will, once again, operate as a work-around and get me the enter key. so the bug isn't quite squashed but we're back to the old bug with a work-around rather than the super bug with no work-around whatsoever. I'll take that for now.

Don’t do it you crazy mad dog!!! I made that very mistake earlier and the bug came back. I think VO has been lurking for the last day, just waiting for its time to strike, and strike it did.

This was the comment I was looking for. I'll throw salt over my left shoulder, then update.

Ok guys been thinking about this. The bug is very random. It seems that it affects some and not all users and some but not all phone models. Equally, it then seems to fix itself. I had this issue in 16.4 with most voices on iPhone 13 pro. Since 16.4.1 the bug just went. All voices work fine. So whatever the issue is it maybe a sod to fix for Apple and it isn't uniform to all devices/people. Could be around for a while me thinks.

I found that this version seems to have fixed a bug that had been bothering me for a long time. For quite some time before, I always encountered a bug where the data package used for image description would be automatically deleted. That is to say, even if you found that the switch for image description recognition in VoiceOver was turned on, VoiceOver would tell you that you need a 33.8MB data package when you clicked on it to check. After I updated to 16.5 the day before yesterday and until now, the data package is still there. Hopefully, it has really been fixed and it's not just wishful thinking on my part.

Bugs are not nice to all of you. My series 7 is good so far. I am planning to get the series 9 due to faster chip and new OS. Hope that it will not have bugs since is going to be a new experience with OS.

Bugs that are intermittent, happen for only some users or devices, or that come and go by themselves, are often caused by uninitialized memory. Professional software developers have tools to locate code that references memory that has never been written to. It's a matter of the developer taking the time to use the tools available.

I know this from personal experience. At an employer a long time ago in a city not that far away, we had a single customer who reported an intermittent crash. No one else experienced it. The bug when unfixed for months because our small team of developers was continually developing new features that the sales staff had sold - even though the features didn't exist.

Then, one day, the bug could wait no longer, and guess who drew the short straw? Yours truly. If I remember correctly, it took a solid week of instrumenting code and collecting data to track down and fix. One developer, 40 hours - that's all it took. I know, every bug is different. But I think it's fair to say that, just because a bug is intermittent doesn't mean it's particularly difficult to fix.

iPhone XR iOS 16.5.
VO with Norwegian SIRI male and UK SIRI female and US SIRI #4 in my rotor.
It's crashing all over the place hahaha
F*** LOL

Since ios16.5 the problem is there again where the navigation keys won't work properly, sometimes they do mostly they don't. Please DO report this to accessibility@apple.com I am testing with a smartbeetle and ios16.5 with an iphone XR.
really for me ios16 is the worst and most crab update I have ever experoenced before and I have been using IOS since IOS7.
PLEASE DO COMPLAIN WITH APPLE!

Ok, iOS 16 works fine for me most of the time.
However, I'm very tired of all the bugs and some of these bugs are darn annoying.
I really don't care about useless wallpapers and such.
I care about poor quality TTS voices and VO restarting very often.
Apple, please focus on squashing bugs rather than developing even new VO features.
Please make higher quality voices available and make it easier for third party devs to have their speech engines available on iOS and VO.

I didn't say it quietly enough, clearly. Voiceover still crashes for me, albeit not nearly as often as before. Far more annoying is the bug on the other thread about panning while reading Kindle books. There is now a work-around for that one, but it's still very irksome indeed. I am inclined to agree with those who say that IOS 16 has been one of the buggier releases, though I still haven't forgotten what IOS 13 did to my battery, so IOS 13 remains my least favourite. I've been using an iPhone since 2010, so that's IOS 4 or thereabouts.

For me, the panning issues seem to only exist with the Kindle app, though it doesn't seem to matter which braille display I use. Until Turn Pages While Panning is disabled, I am unable to pan past the bottom of the page. Perhaps It is worse on the Smart Beetle, I do not have one to test with.

Hello, I was just curious if the panning issues reported on the iPhone are also present on iPad 16.5?

I don't use braille so can't say for sure, but as iOS and iPadOS share much of the same code, I'd assume the issues with panning reported on the iPhone are also present on the iPad.

I hadn't heard anyone report it with iPad OS, only iOS, so I was holding out some hope.