Re: My top iOS 9 Bugs

[christopher hallsworth]

Seems to be for wired headsets only.
> On 17 Sep 2015, at 21:46, Chris Chaffin <chaffin102...@gmail.com> wrote:
> 
> Does this bug come up when using a bluetooth headset instead of a plug in 
> headset?
> I have only read where people had a plug in headset.
> 
> Thanks,
> 
> Chris
> 
> 
> 
> 
> On Sep 17, 2015, at 3:13 PM, christopher hallsworth <challswor...@icloud.com 
> <mailto:challswor...@icloud.com>> wrote:
> 
>> It shouldn't. It seems to be for headsets only. Even then, they may only 
>> experience a mild form of this or not at all.
>> Chris
>>> On 17 Sep 2015, at 15:23, Russ Kiehne <russ94...@gmail.com 
>>> <mailto:russ94...@gmail.com>> wrote:
>>> 
>>> Let me ask about: 1. Audio routing bug.  My brother has an iphone 6 and 
>>> doesn’t use earbuds or headphones.  Will this bug effect him?
>>>  
>>> From: Jonathan Mosen <mailto:jmo...@mosen.org>
>>> Sent: Wednesday, September 16, 2015 10:15 AM
>>> To: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>>> Subject: My top iOS 9 Bugs
>>>  
>>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>>> might like to be aware of in iOS 9.
>>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>>> minor annoyances to potentially critical, depending on how you use your 
>>> device and whether you find yourself affected. Here are just a few that you 
>>> might like to take into consideration before deciding whether to wait for a 
>>> bug fix release before installing iOS 9. Remember that a few days following 
>>> iOS 9's release, it will not be possible to downgrade again, so you should 
>>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>>> anything below concerns you.
>>> 1. Audio routing bug. This is potentially the most significant 
>>> accessibility bug I can recall ever to slip through an iOS release, due to 
>>> the number of people who may be affected. Not everyone will be, and at 
>>> present, even after extensive testing with a range of people owning 
>>> different devices, I have no information about why it affects some users, 
>>> but not others. It is not device specific, for example it is happening to 
>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem 
>>> isn't so severe. Nor does it seem to be affected by any setting. If you're 
>>> lucky, it won't happen to you, but the only way I am aware of to determine 
>>> this is to upgrade.
>>> This bug may affect you when you have earbuds or headphones connected to 
>>> the headphone socket of your iPhone. The primary way the audio routing bug 
>>> manifests itself is when you receive an incoming phone or FaceTime call. 
>>> You can usually hear if you're going to be affected by the bug because your 
>>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>>> audio to fade in and out when audio ducking is enabled. At this point, if 
>>> you press the power button to silence the ringer and then flick through the 
>>> screen, you will find that not only has VOiceOver become unresponsive, but 
>>> the entire phone has as well.
>>> If you don't press the power button while the phone is ringing, but instead 
>>> opt to flick through the iPHone's screen to locate the Answer button or 
>>> review caller ID information, VoiceOver may not speak at all.
>>> Finally, if you attempt to answer the incoming call with a two-finger 
>>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>>> up.
>>> The bottom line is that if you have earbuds connected, you may not be able 
>>> to answer a call.
>>> Some people have also reported similar problems answering calls when their 
>>> phone is set to silent.
>>> If you rely on your phone for business or safety, this could be a deal 
>>> breaker in terms of upgrading at this point.
>>> What makes this bug so fascinating is that not only is it completely absent 
>>> for some people, but of those who experience it, not all symptoms are 
>>> present for all users. For example, some people experience the issues I 
>>> have described when they press the power button to mute the ringer, but not 
>>> when the phone is ringing. Other

Re: My top iOS 9 Bugs

[christopher hallsworth]

It does, and it may impact those with residual or no hearing at all. If you 
turn Airplane mode on, then turn bluetooth back on, your Braille display will 
not automatically connect. You then need to go into Settings > general > 
accessibility > VoiceOver > Braille and double tap on your display to connect 
again. But the problem doesn't end there. While still in Airplane Mode, if you 
lock your device and unlock it again, the display will once again not connect 
automatically. You will have to do the above to connect again.
Chris
> On 17 Sep 2015, at 04:10, Ron Pelletier <ron.pellet...@sympatico.ca> wrote:
> 
> According to Applevis, it does
> 
> Ron & Danvers
> 
> -Original Message-
> From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf Of 
> Melissa Tucker
> Sent: Wednesday, September 16, 2015 4:07 PM
> To: viphone@googlegroups.com
> Subject: Re: My top iOS 9 Bugs
> 
> does ios9 give any problems for people using a braille display?
> 
> 
> 
> On Sep 16, 2015, at 3:15 PM, Krister Ekstrom <kris...@kristersplace.com> 
> wrote:
> 
> I always religiously update to the latest version of an Os when it comes out, 
> if it works it does, if not… well shrug.
> /Krister
> 
>> 16 sep. 2015 kl. 20:02 skrev Mike Arrigo <n0...@charter.net>:
>> 
>> In general, I think it's always good to wait until at least the first major 
>> update, sometimes the second of any new operating system so the major bugs 
>> can get worked out. Upgrading to a new version of an operating system as 
>> soon as it's released is far too risky.
>> Original message:
>>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>>> might like to be aware of in iOS 9.
>>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>>> minor annoyances to potentially critical, depending on how you use your 
>>> device and whether you find yourself affected. Here are just a few that you 
>>> might like to take into consideration before deciding whether to wait for a 
>>> bug fix release before installing iOS 9. Remember that a few days following 
>>> iOS 9's release, it will not be possible to downgrade again, so you should 
>>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>>> anything below concerns you.
>>> 1. Audio routing bug. This is potentially the most significant 
>>> accessibility bug I can recall ever to slip through an iOS release, due to 
>>> the number of people who may be affected. Not everyone will be, and at 
>>> present, even after extensive testing with a range of people owning 
>>> different devices, I have no information about why it affects some users, 
>>> but not others. It is not device specific, for example it is happening to 
>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem 
>>> isn't so severe. Nor does it seem to be affected by any setting. If you're 
>>> lucky, it won't happen to you, but the only way I am aware of to determine 
>>> this is to upgrade.
>>> This bug may affect you when you have earbuds or headphones connected to 
>>> the headphone socket of your iPhone. The primary way the audio routing bug 
>>> manifests itself is when you receive an incoming phone or FaceTime call. 
>>> You can usually hear if you're going to be affected by the bug because your 
>>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>>> audio to fade in and out when audio ducking is enabled. At this point, if 
>>> you press the power button to silence the ringer and then flick through the 
>>> screen, you will find that not only has VOiceOver become unresponsive, but 
>>> the entire phone has as well.
>>> If you don't press the power button while the phone is ringing, but instead 
>>> opt to flick through the iPHone's screen to locate the Answer button or 
>>> review caller ID information, VoiceOver may not speak at all.
>>> Finally, if you attempt to answer the incoming call with a two-finger 
>>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>>> up.
>>> The bottom line is that if you have earbuds connected, you may not be able 
>>> to answer a call.
>>> Some people have also reported similar problems answering calls when their 
>>> phone is set to silent.
>>> If you rely on your pho

Re: My top iOS 9 Bugs

[christopher hallsworth]

Not here on my iPhone 5s. Doubt it would be on my iPad Mini 2 either, but can't 
say for sure as haven't tried them on there. But since they use the same 
hardware in principle, the Siri voices should work fine on there also.
Chris
> On 17 Sep 2015, at 01:17, Shai <shai...@gmail.com> wrote:
> 
> Hi,
> The setting of the Siri voices for VoiceOver was mentioned on
> AppleVis; however, it was also indicated that the responsiveness is
> quite sluggish while navigating.
> Have you noticed this?
> 
> 
> On 9/16/15, John Diakogeorgiou <jdiakoge2...@gmail.com> wrote:
>> I've been using a VaroUltra and it works fine. Also one thing which no
>> one has mentioned is that you can now use the Siri male and female
>> voices for voice over. Just know that the male voice pronounces some
>> vowels strangely.
>> 
>> On 9/16/15, Jonathan Mosen <jmo...@mosen.org> wrote:
>>> Hi Neal. My understanding is that if you are affected, it will also
>>> happen
>>> if you have your phone on silent. If you just have your phone unmuted and
>>> on
>>> speaker, it appears to be OK as far as I know.
>>> Jonathan Mosen
>>> Mosen Consulting
>>> Blindness technology eBooks, tutorials and training
>>> http://Mosen.org
>>> 
>>>> On 17/09/2015, at 9:38 AM, Neal Ewers <neal.ew...@ravenswood.org> wrote:
>>>> 
>>>> Jonathan. Is this phone problem a problem only when using something
>>>> connected to the phone such as ear buds or a bluetooth device? Or, does
>>>> it
>>>> also effect phone calls if you are using none of these devices and only
>>>> using the microphone and speaker in the phone?
>>>> 
>>>> Thanks.
>>>> 
>>>> Neal
>>>> 
>>>> 
>>>> From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>>>> [mailto:viphone@googlegroups.com <mailto:viphone@googlegroups.com>] On
>>>> Behalf Of Jonathan Mosen
>>>> Sent: Wednesday, September 16, 2015 12:15 PM
>>>> To: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>>>> Subject: My top iOS 9 Bugs
>>>> 
>>>> Hi everyone, now that the NDA is lifted, here are some things I think
>>>> you
>>>> might like to be aware of in iOS 9.
>>>> I am enthusiastic about iOS 9. It is significantly more responsive than
>>>> its predecessor, and there are many new features that I'm sure you'll
>>>> enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 9 that
>>>> range from minor annoyances to potentially critical, depending on how
>>>> you
>>>> use your device and whether you find yourself affected. Here are just a
>>>> few that you might like to take into consideration before deciding
>>>> whether
>>>> to wait for a bug fix release before installing iOS 9. Remember that a
>>>> few
>>>> days following iOS 9's release, it will not be possible to downgrade
>>>> again, so you should consider the upgrade to iOS 9 a one-way trip, and
>>>> proceed with caution if anything below concerns you.
>>>> 1. Audio routing bug. This is potentially the most significant
>>>> accessibility bug I can recall ever to slip through an iOS release, due
>>>> to
>>>> the number of people who may be affected. Not everyone will be, and at
>>>> present, even after extensive testing with a range of people owning
>>>> different devices, I have no information about why it affects some
>>>> users,
>>>> but not others. It is not device specific, for example it is happening
>>>> to
>>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem
>>>> isn't so severe. Nor does it seem to be affected by any setting. If
>>>> you're
>>>> lucky, it won't happen to you, but the only way I am aware of to
>>>> determine
>>>> this is to upgrade.
>>>> This bug may affect you when you have earbuds or headphones connected to
>>>> the headphone socket of your iPhone. The primary way the audio routing
>>>> bug
>>>> manifests itself is when you receive an incoming phone or FaceTime call.
>>>> You can usually hear if you're going to be affected by the bug because
>>>> your ring-tone will fade in and out, rather like the way VOiceOver
>>>> causes
>>>> system audio to fade in and out when audio ducking is enabled. At this
>>>> p

Re: My top iOS 9 Bugs

[christopher hallsworth]

It cannot be duplicated since it is not device specific nor is it situation 
specific.
> On 17 Sep 2015, at 09:28, Jenifer Barr  wrote:
> 
> Has anyone been able to duplicate point 1? That's my whole hesitation of 
> updating because I constantly use earbuds.
> Thanks. 
> 
> Jenifer Barr
> Sent from my iPhone
> 
> On Sep 16, 2015, at 1:15 PM, Jonathan Mosen  > wrote:
> 
>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>> might like to be aware of in iOS 9.
>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>> minor annoyances to potentially critical, depending on how you use your 
>> device and whether you find yourself affected. Here are just a few that you 
>> might like to take into consideration before deciding whether to wait for a 
>> bug fix release before installing iOS 9. Remember that a few days following 
>> iOS 9's release, it will not be possible to downgrade again, so you should 
>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>> anything below concerns you.
>> 1. Audio routing bug. This is potentially the most significant accessibility 
>> bug I can recall ever to slip through an iOS release, due to the number of 
>> people who may be affected. Not everyone will be, and at present, even after 
>> extensive testing with a range of people owning different devices, I have no 
>> information about why it affects some users, but not others. It is not 
>> device specific, for example it is happening to me on my iPhone 6 Plus, but 
>> I know iPhone 6 Plus users where the problem isn't so severe. Nor does it 
>> seem to be affected by any setting. If you're lucky, it won't happen to you, 
>> but the only way I am aware of to determine this is to upgrade.
>> This bug may affect you when you have earbuds or headphones connected to the 
>> headphone socket of your iPhone. The primary way the audio routing bug 
>> manifests itself is when you receive an incoming phone or FaceTime call. You 
>> can usually hear if you're going to be affected by the bug because your 
>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>> audio to fade in and out when audio ducking is enabled. At this point, if 
>> you press the power button to silence the ringer and then flick through the 
>> screen, you will find that not only has VOiceOver become unresponsive, but 
>> the entire phone has as well.
>> If you don't press the power button while the phone is ringing, but instead 
>> opt to flick through the iPHone's screen to locate the Answer button or 
>> review caller ID information, VoiceOver may not speak at all.
>> Finally, if you attempt to answer the incoming call with a two-finger 
>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>> up.
>> The bottom line is that if you have earbuds connected, you may not be able 
>> to answer a call.
>> Some people have also reported similar problems answering calls when their 
>> phone is set to silent.
>> If you rely on your phone for business or safety, this could be a deal 
>> breaker in terms of upgrading at this point.
>> What makes this bug so fascinating is that not only is it completely absent 
>> for some people, but of those who experience it, not all symptoms are 
>> present for all users. For example, some people experience the issues I have 
>> described when they press the power button to mute the ringer, but not when 
>> the phone is ringing. Others can answer a call by pressing the button on 
>> their EarPods, while others cannot.
>> If you upgrade and are affected by this, here are a few things to try.
>> (A) If you have the more moderate version of this bug, avoid pressing the 
>> power button when you receive an incoming call.
>> (B) Turning off audio ducking seems to help a little for some users.
>> (C) If you can't answer a call with a two-finger double-tap, try pressing 
>> the button on your EarPods or similar device if you have such a device 
>> connected.
>> (D) If all else fails, you can disconnect any device from the headphone 
>> jack, answer the call with a two-finger double-tap, then reconnect the 
>> device to the headphone jack.
>> (E) Given the critical nature of this bug, if you've upgraded and now find 
>> yourself afflicted by it, enrol in the iOS beta program so you can receive 
>> early copies of any fixes Apple is working on. But keep in mind that since 
>> you will be running beta software, you may well be swapping one set of bugs 
>> for another.
>> 2. Bluetooth keyboard support unreliable. Sometimes, users may input double 
>> letters when typing. This is a bug that was introduced in the iOS 8 cycle, 
>> and can easily be worked around by toggling VoiceOver off and on.
>> 

Re: My top iOS 9 Bugs

[Jenifer Barr]

Thanks Christopher. (if your name is spelled wrong I appologize... I tried 
coppying it but vo wouldn't let me) 

Jenifer Barr
Sent from my iPhone

> On Sep 17, 2015, at 4:30 AM, christopher hallsworth  
> wrote:
> 
> It cannot be duplicated since it is not device specific nor is it situation 
> specific.
>> On 17 Sep 2015, at 09:28, Jenifer Barr  wrote:
>> 
>> Has anyone been able to duplicate point 1? That's my whole hesitation of 
>> updating because I constantly use earbuds.
>> Thanks. 
>> 
>> Jenifer Barr
>> Sent from my iPhone
>> 
>>> On Sep 16, 2015, at 1:15 PM, Jonathan Mosen  wrote:
>>> 
>>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>>> might like to be aware of in iOS 9.
>>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>>> minor annoyances to potentially critical, depending on how you use your 
>>> device and whether you find yourself affected. Here are just a few that you 
>>> might like to take into consideration before deciding whether to wait for a 
>>> bug fix release before installing iOS 9. Remember that a few days following 
>>> iOS 9's release, it will not be possible to downgrade again, so you should 
>>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>>> anything below concerns you.
>>> 1. Audio routing bug. This is potentially the most significant 
>>> accessibility bug I can recall ever to slip through an iOS release, due to 
>>> the number of people who may be affected. Not everyone will be, and at 
>>> present, even after extensive testing with a range of people owning 
>>> different devices, I have no information about why it affects some users, 
>>> but not others. It is not device specific, for example it is happening to 
>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem 
>>> isn't so severe. Nor does it seem to be affected by any setting. If you're 
>>> lucky, it won't happen to you, but the only way I am aware of to determine 
>>> this is to upgrade.
>>> This bug may affect you when you have earbuds or headphones connected to 
>>> the headphone socket of your iPhone. The primary way the audio routing bug 
>>> manifests itself is when you receive an incoming phone or FaceTime call. 
>>> You can usually hear if you're going to be affected by the bug because your 
>>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>>> audio to fade in and out when audio ducking is enabled. At this point, if 
>>> you press the power button to silence the ringer and then flick through the 
>>> screen, you will find that not only has VOiceOver become unresponsive, but 
>>> the entire phone has as well.
>>> If you don't press the power button while the phone is ringing, but instead 
>>> opt to flick through the iPHone's screen to locate the Answer button or 
>>> review caller ID information, VoiceOver may not speak at all.
>>> Finally, if you attempt to answer the incoming call with a two-finger 
>>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>>> up.
>>> The bottom line is that if you have earbuds connected, you may not be able 
>>> to answer a call.
>>> Some people have also reported similar problems answering calls when their 
>>> phone is set to silent.
>>> If you rely on your phone for business or safety, this could be a deal 
>>> breaker in terms of upgrading at this point.
>>> What makes this bug so fascinating is that not only is it completely absent 
>>> for some people, but of those who experience it, not all symptoms are 
>>> present for all users. For example, some people experience the issues I 
>>> have described when they press the power button to mute the ringer, but not 
>>> when the phone is ringing. Others can answer a call by pressing the button 
>>> on their EarPods, while others cannot.
>>> If you upgrade and are affected by this, here are a few things to try.
>>> (A) If you have the more moderate version of this bug, avoid pressing the 
>>> power button when you receive an incoming call.
>>> (B) Turning off audio ducking seems to help a little for some users.
>>> (C) If you can't answer a call with a two-finger double-tap, try pressing 
>>> the button on your EarPods or similar device if you have such a device 
>>> connected.
>>> (D) If all else fails, you can disconnect any device from the headphone 
>>> jack, answer the call with a two-finger double-tap, then reconnect the 
>>> device to the headphone jack.
>>> (E) Given the critical nature of this bug, if you've upgraded and now find 
>>> yourself afflicted by it, enrol in the iOS beta program so you can receive 
>>> early copies of any fixes Apple is working on. But keep in mind that since 
>>> you will be running beta 

RE: My top iOS 9 Bugs

[Alex Stone]

Sorry, but what do you mean by "the microphone remains open", surely if the 
call has ended this wouldn't make any difference.

-Original Message-
From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf Of 
Lois Butterfield
Sent: 17 September 2015 09:53
To: viphone@googlegroups.com
Subject: Re: My top iOS 9 Bugs

What happens with my iPhone 6 is, when I get a call while earphones are plugged 
in, which is most of the time, everything is fine until I hang up the call.  
That is when something funny happens.  The microphone remains open, and VO is 
dead.  I have to unplug and plug back in to resolve the issue.  Since it 
doesn’t effect the actual calls, I can live with it.
 
Once, I dropped the phone while plugged in, and I had sound both through the 
headphones and the speaker.  That went on until I closed phone in the app 
switcher.  That also had to do with a call ringing while listening to a book.  
Crazy stuff, but I still like the update.
 
Lois
 
From: christopher hallsworth <mailto:challswor...@icloud.com>  
Sent: Thursday, September 17, 2015 4:30 AM
To: Viphone <mailto:viphone@googlegroups.com>  
Subject: Re: My top iOS 9 Bugs
 
It cannot be duplicated since it is not device specific nor is it situation 
specific.


On 17 Sep 2015, at 09:28, Jenifer Barr <claudas...@gmail.com 
<mailto:claudas...@gmail.com> > wrote:
 
Has anyone been able to duplicate point 1? That's my whole hesitation 
of updating because I constantly use earbuds.
Thanks. 

Jenifer Barr 
Sent from my iPhone

On Sep 16, 2015, at 1:15 PM, Jonathan Mosen <jmo...@mosen.org 
<mailto:jmo...@mosen.org> > wrote:



Hi everyone, now that the NDA is lifted, here are some things I 
think you might like to be aware of in iOS 9. 
I am enthusiastic about iOS 9. It is significantly more 
responsive than its predecessor, and there are many new features that I'm sure 
you'll enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 9 that 
range from minor annoyances to potentially critical, depending on how you use 
your device and whether you find yourself affected. Here are just a few that 
you might like to take into consideration before deciding whether to wait for a 
bug fix release before installing iOS 9. Remember that a few days following iOS 
9's release, it will not be possible to downgrade again, so you should consider 
the upgrade to iOS 9 a one-way trip, and proceed with caution if anything below 
concerns you.
1. Audio routing bug. This is potentially the most significant 
accessibility bug I can recall ever to slip through an iOS release, due to the 
number of people who may be affected. Not everyone will be, and at present, 
even after extensive testing with a range of people owning different devices, I 
have no information about why it affects some users, but not others. It is not 
device specific, for example it is happening to me on my iPhone 6 Plus, but I 
know iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to 
be affected by any setting. If you're lucky, it won't happen to you, but the 
only way I am aware of to determine this is to upgrade.
This bug may affect you when you have earbuds or headphones 
connected to the headphone socket of your iPhone. The primary way the audio 
routing bug manifests itself is when you receive an incoming phone or FaceTime 
call. You can usually hear if you're going to be affected by the bug because 
your ring-tone will fade in and out, rather like the way VOiceOver causes 
system audio to fade in and out when audio ducking is enabled. At this point, 
if you press the power button to silence the ringer and then flick through the 
screen, you will find that not only has VOiceOver become unresponsive, but the 
entire phone has as well.
If you don't press the power button while the phone is ringing, 
but instead opt to flick through the iPHone's screen to locate the Answer 
button or review caller ID information, VoiceOver may not speak at all.
Finally, if you attempt to answer the incoming call with a 
two-finger double-tap, you may not be able to, since VoiceOver has effectively 
locked up.
The bottom line is that if you have earbuds connected, you may 
not be able to answer a call.
Some people have also reported similar problems answering calls 
when their phone is set to silent.
If you rely on your phone for business or safety, this could be 
a deal breaker in terms of upgrading at this point.
What makes this bug so fascinating is that not only is it 
completely absent for some people, but of those who experience it, not all 
symptoms are present for all users. For example, some people experience the 
issues I have described when they press the power butt

Re: My top iOS 9 Bugs

['Eleanor Roberts' via VIPhone]

Hi 

Please can folk make sure they report these bugs to Apple, especially the 
bluetooth keyboard one! Whilst I do occasionally use the touch screen, 99.9% of 
the time I use my bluetooth keyboard for everything. I've reported it to Apple 
accessibility, but would strongly encourage everyone else to do the same, 
otherwise it'll never get fixed. 

Eleanor 

Sent from my iPad

> On 17 Sep 2015, at 12:10, Devin Prater <r.d.t.pra...@gmail.com> wrote:
> 
> My biggest bug is the bluetooth keyboard problem. I know, I have, and love, 
> my Varioultra, but I have a friend that exclusively uses a keyboard, and it 
> hit her hard. 
> 
> Sent from my iPhone
> 
>> On Sep 16, 2015, at 4:54 PM, Jonathan Mosen <jmo...@mosen.org> wrote:
>> 
>> Hi Neal. My understanding is that if you are affected, it will also happen 
>> if you have your phone on silent. If you just have your phone unmuted and on 
>> speaker, it appears to be OK as far as I know.
>> Jonathan Mosen
>> Mosen Consulting
>> Blindness technology eBooks, tutorials and training
>> http://Mosen.org
>> 
>>> On 17/09/2015, at 9:38 AM, Neal Ewers <neal.ew...@ravenswood.org> wrote:
>>> 
>>> Jonathan. Is this phone problem a problem only when using something 
>>> connected to the phone such as ear buds or a bluetooth device? Or, does it 
>>> also effect phone calls if you are using none of these devices and only 
>>> using the microphone and speaker in the phone?
>>>  
>>> Thanks.
>>>  
>>> Neal
>>>  
>>>  
>>> From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf 
>>> Of Jonathan Mosen
>>> Sent: Wednesday, September 16, 2015 12:15 PM
>>> To: viphone@googlegroups.com
>>> Subject: My top iOS 9 Bugs
>>>  
>>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>>> might like to be aware of in iOS 9.
>>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>>> minor annoyances to potentially critical, depending on how you use your 
>>> device and whether you find yourself affected. Here are just a few that you 
>>> might like to take into consideration before deciding whether to wait for a 
>>> bug fix release before installing iOS 9. Remember that a few days following 
>>> iOS 9's release, it will not be possible to downgrade again, so you should 
>>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>>> anything below concerns you.
>>> 1. Audio routing bug. This is potentially the most significant 
>>> accessibility bug I can recall ever to slip through an iOS release, due to 
>>> the number of people who may be affected. Not everyone will be, and at 
>>> present, even after extensive testing with a range of people owning 
>>> different devices, I have no information about why it affects some users, 
>>> but not others. It is not device specific, for example it is happening to 
>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem 
>>> isn't so severe. Nor does it seem to be affected by any setting. If you're 
>>> lucky, it won't happen to you, but the only way I am aware of to determine 
>>> this is to upgrade.
>>> This bug may affect you when you have earbuds or headphones connected to 
>>> the headphone socket of your iPhone. The primary way the audio routing bug 
>>> manifests itself is when you receive an incoming phone or FaceTime call. 
>>> You can usually hear if you're going to be affected by the bug because your 
>>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>>> audio to fade in and out when audio ducking is enabled. At this point, if 
>>> you press the power button to silence the ringer and then flick through the 
>>> screen, you will find that not only has VOiceOver become unresponsive, but 
>>> the entire phone has as well.
>>> If you don't press the power button while the phone is ringing, but instead 
>>> opt to flick through the iPHone's screen to locate the Answer button or 
>>> review caller ID information, VoiceOver may not speak at all.
>>> Finally, if you attempt to answer the incoming call with a two-finger 
>>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>>> up.
>>> The bottom line is that if you have earbuds con

Re: My top iOS 9 Bugs

[Devin Prater]

Just slow it down. :) 

Sent from my iPhone

> On Sep 16, 2015, at 1:11 PM, Harry Bell  wrote:
> 
> Also in ios 9 Speak Screen (invoked by two finger swipe down from top of 
> screen) is so fast that it sounds like gibberish. I have reported this to 
> Apple with every beat version but it still hasn't been fixed. Harry
> 
>  
> 
>> On 16 Sep 2015, at 18:15, Jonathan Mosen  wrote:
>> 
>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>> might like to be aware of in iOS 9.
>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>> minor annoyances to potentially critical, depending on how you use your 
>> device and whether you find yourself affected. Here are just a few that you 
>> might like to take into consideration before deciding whether to wait for a 
>> bug fix release before installing iOS 9. Remember that a few days following 
>> iOS 9's release, it will not be possible to downgrade again, so you should 
>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>> anything below concerns you.
>> 1. Audio routing bug. This is potentially the most significant accessibility 
>> bug I can recall ever to slip through an iOS release, due to the number of 
>> people who may be affected. Not everyone will be, and at present, even after 
>> extensive testing with a range of people owning different devices, I have no 
>> information about why it affects some users, but not others. It is not 
>> device specific, for example it is happening to me on my iPhone 6 Plus, but 
>> I know iPhone 6 Plus users where the problem isn't so severe. Nor does it 
>> seem to be affected by any setting. If you're lucky, it won't happen to you, 
>> but the only way I am aware of to determine this is to upgrade.
>> This bug may affect you when you have earbuds or headphones connected to the 
>> headphone socket of your iPhone. The primary way the audio routing bug 
>> manifests itself is when you receive an incoming phone or FaceTime call. You 
>> can usually hear if you're going to be affected by the bug because your 
>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>> audio to fade in and out when audio ducking is enabled. At this point, if 
>> you press the power button to silence the ringer and then flick through the 
>> screen, you will find that not only has VOiceOver become unresponsive, but 
>> the entire phone has as well.
>> If you don't press the power button while the phone is ringing, but instead 
>> opt to flick through the iPHone's screen to locate the Answer button or 
>> review caller ID information, VoiceOver may not speak at all.
>> Finally, if you attempt to answer the incoming call with a two-finger 
>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>> up.
>> The bottom line is that if you have earbuds connected, you may not be able 
>> to answer a call.
>> Some people have also reported similar problems answering calls when their 
>> phone is set to silent.
>> If you rely on your phone for business or safety, this could be a deal 
>> breaker in terms of upgrading at this point.
>> What makes this bug so fascinating is that not only is it completely absent 
>> for some people, but of those who experience it, not all symptoms are 
>> present for all users. For example, some people experience the issues I have 
>> described when they press the power button to mute the ringer, but not when 
>> the phone is ringing. Others can answer a call by pressing the button on 
>> their EarPods, while others cannot.
>> If you upgrade and are affected by this, here are a few things to try.
>> (A) If you have the more moderate version of this bug, avoid pressing the 
>> power button when you receive an incoming call.
>> (B) Turning off audio ducking seems to help a little for some users.
>> (C) If you can't answer a call with a two-finger double-tap, try pressing 
>> the button on your EarPods or similar device if you have such a device 
>> connected.
>> (D) If all else fails, you can disconnect any device from the headphone 
>> jack, answer the call with a two-finger double-tap, then reconnect the 
>> device to the headphone jack.
>> (E) Given the critical nature of this bug, if you've upgraded and now find 
>> yourself afflicted by it, enrol in the iOS beta program so you can receive 
>> early copies of any fixes Apple is working on. But keep in mind that since 
>> you will be running beta software, you may well be swapping one set of bugs 
>> for another.
>> 2. Bluetooth keyboard support unreliable. Sometimes, users may input double 
>> letters when typing. This is a bug that was introduced in the iOS 8 cycle, 
>> and can easily be worked around by toggling VoiceOver off and on.
>> However, a 

Re: My top iOS 9 Bugs

[Devin Prater]

I personally think that it should not be the consumer's problem that an update 
contains a bug like bluetooth keyboard problems that impact its usage. I think 
Apple has become too much like clockwork, or at least will be in another few 
years. 

Sent from my iPhone

> On Sep 16, 2015, at 1:02 PM, Mike Arrigo  wrote:
> 
> In general, I think it's always good to wait until at least the first major 
> update, sometimes the second of any new operating system so the major bugs 
> can get worked out. Upgrading to a new version of an operating system as soon 
> as it's released is far too risky.
> Original message:
>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>> might like to be aware of in iOS 9.
>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>> minor annoyances to potentially critical, depending on how you use your 
>> device and whether you find yourself affected. Here are just a few that you 
>> might like to take into consideration before deciding whether to wait for a 
>> bug fix release before installing iOS 9. Remember that a few days following 
>> iOS 9's release, it will not be possible to downgrade again, so you should 
>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>> anything below concerns you.
>> 1. Audio routing bug. This is potentially the most significant accessibility 
>> bug I can recall ever to slip through an iOS release, due to the number of 
>> people who may be affected. Not everyone will be, and at present, even after 
>> extensive testing with a range of people owning different devices, I have no 
>> information about why it affects some users, but not others. It is not 
>> device specific, for example it is happening to me on my iPhone 6 Plus, but 
>> I know iPhone 6 Plus users where the problem isn't so severe. Nor does it 
>> seem to be affected by any setting. If you're lucky, it won't happen to you, 
>> but the only way I am aware of to determine this is to upgrade.
>> This bug may affect you when you have earbuds or headphones connected to the 
>> headphone socket of your iPhone. The primary way the audio routing bug 
>> manifests itself is when you receive an incoming phone or FaceTime call. You 
>> can usually hear if you're going to be affected by the bug because your 
>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>> audio to fade in and out when audio ducking is enabled. At this point, if 
>> you press the power button to silence the ringer and then flick through the 
>> screen, you will find that not only has VOiceOver become unresponsive, but 
>> the entire phone has as well.
>> If you don't press the power button while the phone is ringing, but instead 
>> opt to flick through the iPHone's screen to locate the Answer button or 
>> review caller ID information, VoiceOver may not speak at all.
>> Finally, if you attempt to answer the incoming call with a two-finger 
>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>> up.
>> The bottom line is that if you have earbuds connected, you may not be able 
>> to answer a call.
>> Some people have also reported similar problems answering calls when their 
>> phone is set to silent.
>> If you rely on your phone for business or safety, this could be a deal 
>> breaker in terms of upgrading at this point.
>> What makes this bug so fascinating is that not only is it completely absent 
>> for some people, but of those who experience it, not all symptoms are 
>> present for all users. For example, some people experience the issues I have 
>> described when they press the power button to mute the ringer, but not when 
>> the phone is ringing. Others can answer a call by pressing the button on 
>> their EarPods, while others cannot.
>> If you upgrade and are affected by this, here are a few things to try.
>> (A) If you have the more moderate version of this bug, avoid pressing the 
>> power button when you receive an incoming call.
>> (B) Turning off audio ducking seems to help a little for some users.
>> (C) If you can't answer a call with a two-finger double-tap, try pressing 
>> the button on your EarPods or similar device if you have such a device 
>> connected.
>> (D) If all else fails, you can disconnect any device from the headphone 
>> jack, answer the call with a two-finger double-tap, then reconnect the 
>> device to the headphone jack.
>> (E) Given the critical nature of this bug, if you've upgraded and now find 
>> yourself afflicted by it, enrol in the iOS beta program so you can receive 
>> early copies of any fixes Apple is working on. But keep in mind that since 
>> you will be running beta software, you may well be swapping one set of bugs 
>> for another.
>> 2. Bluetooth keyboard support 

Re: My top iOS 9 Bugs

[Devin Prater]

Yes, Bard has become less useful for me as a braille reader. They say they'll 
make an update, but I'm quite sure they won't.

Sent from my iPhone

> On Sep 16, 2015, at 4:11 PM, Woody Anna Dresner  wrote:
> 
> Hi,
> 
> I've used a Focus 40 Blue Classic and a RefreshaBraille 18 throughout the 
> betas and have had no problems except that BARD Mobile is far less likely to 
> save my reading position than previously.
> 
> Best,
> Anna
> 
> 
> 
>> On Sep 16, 2015, at 3:06 PM, Melissa Tucker  wrote:
>> 
>> does ios9 give any problems for people using a braille display?
>> 
>> 
>> 
>> On Sep 16, 2015, at 3:15 PM, Krister Ekstrom  
>> wrote:
>> 
>> I always religiously update to the latest version of an Os when it comes 
>> out, if it works it does, if not… well shrug.
>> /Krister
>> 
>>> 16 sep. 2015 kl. 20:02 skrev Mike Arrigo :
>>> 
>>> In general, I think it's always good to wait until at least the first major 
>>> update, sometimes the second of any new operating system so the major bugs 
>>> can get worked out. Upgrading to a new version of an operating system as 
>>> soon as it's released is far too risky.
>>> Original message:
 Hi everyone, now that the NDA is lifted, here are some things I think you 
 might like to be aware of in iOS 9.
 I am enthusiastic about iOS 9. It is significantly more responsive than 
 its predecessor, and there are many new features that I'm sure you'll 
 enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 9 that 
 range from minor annoyances to potentially critical, depending on how you 
 use your device and whether you find yourself affected. Here are just a 
 few that you might like to take into consideration before deciding whether 
 to wait for a bug fix release before installing iOS 9. Remember that a few 
 days following iOS 9's release, it will not be possible to downgrade 
 again, so you should consider the upgrade to iOS 9 a one-way trip, and 
 proceed with caution if anything below concerns you.
 1. Audio routing bug. This is potentially the most significant 
 accessibility bug I can recall ever to slip through an iOS release, due to 
 the number of people who may be affected. Not everyone will be, and at 
 present, even after extensive testing with a range of people owning 
 different devices, I have no information about why it affects some users, 
 but not others. It is not device specific, for example it is happening to 
 me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem 
 isn't so severe. Nor does it seem to be affected by any setting. If you're 
 lucky, it won't happen to you, but the only way I am aware of to determine 
 this is to upgrade.
 This bug may affect you when you have earbuds or headphones connected to 
 the headphone socket of your iPhone. The primary way the audio routing bug 
 manifests itself is when you receive an incoming phone or FaceTime call. 
 You can usually hear if you're going to be affected by the bug because 
 your ring-tone will fade in and out, rather like the way VOiceOver causes 
 system audio to fade in and out when audio ducking is enabled. At this 
 point, if you press the power button to silence the ringer and then flick 
 through the screen, you will find that not only has VOiceOver become 
 unresponsive, but the entire phone has as well.
 If you don't press the power button while the phone is ringing, but 
 instead opt to flick through the iPHone's screen to locate the Answer 
 button or review caller ID information, VoiceOver may not speak at all.
 Finally, if you attempt to answer the incoming call with a two-finger 
 double-tap, you may not be able to, since VoiceOver has effectively locked 
 up.
 The bottom line is that if you have earbuds connected, you may not be able 
 to answer a call.
 Some people have also reported similar problems answering calls when their 
 phone is set to silent.
 If you rely on your phone for business or safety, this could be a deal 
 breaker in terms of upgrading at this point.
 What makes this bug so fascinating is that not only is it completely 
 absent for some people, but of those who experience it, not all symptoms 
 are present for all users. For example, some people experience the issues 
 I have described when they press the power button to mute the ringer, but 
 not when the phone is ringing. Others can answer a call by pressing the 
 button on their EarPods, while others cannot.
 If you upgrade and are affected by this, here are a few things to try.
 (A) If you have the more moderate version of this bug, avoid pressing the 
 power button when you receive an incoming call.
 (B) Turning off audio ducking seems to help a little for some users.
 (C) If 

Re: My top iOS 9 Bugs

[Devin Prater]

The only real problem is that when typing, every time you press space the 
display will say "bottom of document" but that only happens sometimes. 

Sent from my iPhone

> On Sep 16, 2015, at 3:06 PM, Melissa Tucker  wrote:
> 
> does ios9 give any problems for people using a braille display?
> 
> 
> 
> On Sep 16, 2015, at 3:15 PM, Krister Ekstrom  
> wrote:
> 
> I always religiously update to the latest version of an Os when it comes out, 
> if it works it does, if not… well shrug.
> /Krister
> 
>> 16 sep. 2015 kl. 20:02 skrev Mike Arrigo :
>> 
>> In general, I think it's always good to wait until at least the first major 
>> update, sometimes the second of any new operating system so the major bugs 
>> can get worked out. Upgrading to a new version of an operating system as 
>> soon as it's released is far too risky.
>> Original message:
>>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>>> might like to be aware of in iOS 9.
>>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>>> minor annoyances to potentially critical, depending on how you use your 
>>> device and whether you find yourself affected. Here are just a few that you 
>>> might like to take into consideration before deciding whether to wait for a 
>>> bug fix release before installing iOS 9. Remember that a few days following 
>>> iOS 9's release, it will not be possible to downgrade again, so you should 
>>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>>> anything below concerns you.
>>> 1. Audio routing bug. This is potentially the most significant 
>>> accessibility bug I can recall ever to slip through an iOS release, due to 
>>> the number of people who may be affected. Not everyone will be, and at 
>>> present, even after extensive testing with a range of people owning 
>>> different devices, I have no information about why it affects some users, 
>>> but not others. It is not device specific, for example it is happening to 
>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem 
>>> isn't so severe. Nor does it seem to be affected by any setting. If you're 
>>> lucky, it won't happen to you, but the only way I am aware of to determine 
>>> this is to upgrade.
>>> This bug may affect you when you have earbuds or headphones connected to 
>>> the headphone socket of your iPhone. The primary way the audio routing bug 
>>> manifests itself is when you receive an incoming phone or FaceTime call. 
>>> You can usually hear if you're going to be affected by the bug because your 
>>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>>> audio to fade in and out when audio ducking is enabled. At this point, if 
>>> you press the power button to silence the ringer and then flick through the 
>>> screen, you will find that not only has VOiceOver become unresponsive, but 
>>> the entire phone has as well.
>>> If you don't press the power button while the phone is ringing, but instead 
>>> opt to flick through the iPHone's screen to locate the Answer button or 
>>> review caller ID information, VoiceOver may not speak at all.
>>> Finally, if you attempt to answer the incoming call with a two-finger 
>>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>>> up.
>>> The bottom line is that if you have earbuds connected, you may not be able 
>>> to answer a call.
>>> Some people have also reported similar problems answering calls when their 
>>> phone is set to silent.
>>> If you rely on your phone for business or safety, this could be a deal 
>>> breaker in terms of upgrading at this point.
>>> What makes this bug so fascinating is that not only is it completely absent 
>>> for some people, but of those who experience it, not all symptoms are 
>>> present for all users. For example, some people experience the issues I 
>>> have described when they press the power button to mute the ringer, but not 
>>> when the phone is ringing. Others can answer a call by pressing the button 
>>> on their EarPods, while others cannot.
>>> If you upgrade and are affected by this, here are a few things to try.
>>> (A) If you have the more moderate version of this bug, avoid pressing the 
>>> power button when you receive an incoming call.
>>> (B) Turning off audio ducking seems to help a little for some users.
>>> (C) If you can't answer a call with a two-finger double-tap, try pressing 
>>> the button on your EarPods or similar device if you have such a device 
>>> connected.
>>> (D) If all else fails, you can disconnect any device from the headphone 
>>> jack, answer the call with a two-finger double-tap, then reconnect the 
>>> device to the headphone jack.
>>> (E) Given the 

Re: My top iOS 9 Bugs

[Christopher Chaltain]

I'm fairly certain there will be an update to the  BARD Mobile app. I'm 
not sure why you're so certain there won't be. They released their 
Android app not too long ago, so I'd be surprised if their resources 
didn't switch to getting an update to the IOS app now. It may be a 
while, but I don't see how the NLS couldn't have planned for some 
updates to their mobile apps.


On 09/17/2015 06:54 AM, Devin Prater wrote:

Yes, Bard has become less useful for me as a braille reader. They say they'll 
make an update, but I'm quite sure they won't.

Sent from my iPhone


On Sep 16, 2015, at 4:11 PM, Woody Anna Dresner  wrote:

Hi,

I've used a Focus 40 Blue Classic and a RefreshaBraille 18 throughout the betas 
and have had no problems except that BARD Mobile is far less likely to save my 
reading position than previously.

Best,
Anna




On Sep 16, 2015, at 3:06 PM, Melissa Tucker  wrote:

does ios9 give any problems for people using a braille display?



On Sep 16, 2015, at 3:15 PM, Krister Ekstrom  wrote:

I always religiously update to the latest version of an Os when it comes out, 
if it works it does, if not… well shrug.
/Krister


16 sep. 2015 kl. 20:02 skrev Mike Arrigo :

In general, I think it's always good to wait until at least the first major 
update, sometimes the second of any new operating system so the major bugs can 
get worked out. Upgrading to a new version of an operating system as soon as 
it's released is far too risky.
Original message:

Hi everyone, now that the NDA is lifted, here are some things I think you might 
like to be aware of in iOS 9.
I am enthusiastic about iOS 9. It is significantly more responsive than its 
predecessor, and there are many new features that I'm sure you'll enjoy. 
Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
minor annoyances to potentially critical, depending on how you use your device 
and whether you find yourself affected. Here are just a few that you might like 
to take into consideration before deciding whether to wait for a bug fix 
release before installing iOS 9. Remember that a few days following iOS 9's 
release, it will not be possible to downgrade again, so you should consider the 
upgrade to iOS 9 a one-way trip, and proceed with caution if anything below 
concerns you.
1. Audio routing bug. This is potentially the most significant accessibility 
bug I can recall ever to slip through an iOS release, due to the number of 
people who may be affected. Not everyone will be, and at present, even after 
extensive testing with a range of people owning different devices, I have no 
information about why it affects some users, but not others. It is not device 
specific, for example it is happening to me on my iPhone 6 Plus, but I know 
iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to be 
affected by any setting. If you're lucky, it won't happen to you, but the only 
way I am aware of to determine this is to upgrade.
This bug may affect you when you have earbuds or headphones connected to the 
headphone socket of your iPhone. The primary way the audio routing bug 
manifests itself is when you receive an incoming phone or FaceTime call. You 
can usually hear if you're going to be affected by the bug because your 
ring-tone will fade in and out, rather like the way VOiceOver causes system 
audio to fade in and out when audio ducking is enabled. At this point, if you 
press the power button to silence the ringer and then flick through the screen, 
you will find that not only has VOiceOver become unresponsive, but the entire 
phone has as well.
If you don't press the power button while the phone is ringing, but instead opt 
to flick through the iPHone's screen to locate the Answer button or review 
caller ID information, VoiceOver may not speak at all.
Finally, if you attempt to answer the incoming call with a two-finger 
double-tap, you may not be able to, since VoiceOver has effectively locked up.
The bottom line is that if you have earbuds connected, you may not be able to 
answer a call.
Some people have also reported similar problems answering calls when their 
phone is set to silent.
If you rely on your phone for business or safety, this could be a deal breaker 
in terms of upgrading at this point.
What makes this bug so fascinating is that not only is it completely absent for 
some people, but of those who experience it, not all symptoms are present for 
all users. For example, some people experience the issues I have described when 
they press the power button to mute the ringer, but not when the phone is 
ringing. Others can answer a call by pressing the button on their EarPods, 
while others cannot.
If you upgrade and are affected by this, here are a few things to try.
(A) If you have the more moderate version of this bug, avoid pressing the power 
button when you receive an incoming call.
(B) Turning off 

Re: My top iOS 9 Bugs

[Devin Prater]

My biggest bug is the bluetooth keyboard problem. I know, I have, and love, my 
Varioultra, but I have a friend that exclusively uses a keyboard, and it hit 
her hard. 

Sent from my iPhone

> On Sep 16, 2015, at 4:54 PM, Jonathan Mosen <jmo...@mosen.org> wrote:
> 
> Hi Neal. My understanding is that if you are affected, it will also happen if 
> you have your phone on silent. If you just have your phone unmuted and on 
> speaker, it appears to be OK as far as I know.
> Jonathan Mosen
> Mosen Consulting
> Blindness technology eBooks, tutorials and training
> http://Mosen.org
> 
>> On 17/09/2015, at 9:38 AM, Neal Ewers <neal.ew...@ravenswood.org> wrote:
>> 
>> Jonathan. Is this phone problem a problem only when using something 
>> connected to the phone such as ear buds or a bluetooth device? Or, does it 
>> also effect phone calls if you are using none of these devices and only 
>> using the microphone and speaker in the phone?
>>  
>> Thanks.
>>  
>> Neal
>>  
>>  
>> From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf 
>> Of Jonathan Mosen
>> Sent: Wednesday, September 16, 2015 12:15 PM
>> To: viphone@googlegroups.com
>> Subject: My top iOS 9 Bugs
>>  
>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>> might like to be aware of in iOS 9.
>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>> minor annoyances to potentially critical, depending on how you use your 
>> device and whether you find yourself affected. Here are just a few that you 
>> might like to take into consideration before deciding whether to wait for a 
>> bug fix release before installing iOS 9. Remember that a few days following 
>> iOS 9's release, it will not be possible to downgrade again, so you should 
>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>> anything below concerns you.
>> 1. Audio routing bug. This is potentially the most significant accessibility 
>> bug I can recall ever to slip through an iOS release, due to the number of 
>> people who may be affected. Not everyone will be, and at present, even after 
>> extensive testing with a range of people owning different devices, I have no 
>> information about why it affects some users, but not others. It is not 
>> device specific, for example it is happening to me on my iPhone 6 Plus, but 
>> I know iPhone 6 Plus users where the problem isn't so severe. Nor does it 
>> seem to be affected by any setting. If you're lucky, it won't happen to you, 
>> but the only way I am aware of to determine this is to upgrade.
>> This bug may affect you when you have earbuds or headphones connected to the 
>> headphone socket of your iPhone. The primary way the audio routing bug 
>> manifests itself is when you receive an incoming phone or FaceTime call. You 
>> can usually hear if you're going to be affected by the bug because your 
>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>> audio to fade in and out when audio ducking is enabled. At this point, if 
>> you press the power button to silence the ringer and then flick through the 
>> screen, you will find that not only has VOiceOver become unresponsive, but 
>> the entire phone has as well.
>> If you don't press the power button while the phone is ringing, but instead 
>> opt to flick through the iPHone's screen to locate the Answer button or 
>> review caller ID information, VoiceOver may not speak at all.
>> Finally, if you attempt to answer the incoming call with a two-finger 
>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>> up.
>> The bottom line is that if you have earbuds connected, you may not be able 
>> to answer a call.
>> Some people have also reported similar problems answering calls when their 
>> phone is set to silent.
>> If you rely on your phone for business or safety, this could be a deal 
>> breaker in terms of upgrading at this point.
>> What makes this bug so fascinating is that not only is it completely absent 
>> for some people, but of those who experience it, not all symptoms are 
>> present for all users. For example, some people experience the issues I have 
>> described when they press the power button to mute the ringer, but not when 
>> the phone is ringing. Others can answer a call by pressing the button on 
>> their EarPods, while oth

Re: My top iOS 9 Bugs

[Lois Butterfield]

What happens with my iPhone 6 is, when I get a call while earphones are plugged 
in, which is most of the time, everything is fine until I hang up the call.  
That is when something funny happens.  The microphone remains open, and VO is 
dead.  I have to unplug and plug back in to resolve the issue.  Since it 
doesn’t effect the actual calls, I can live with it.

Once, I dropped the phone while plugged in, and I had sound both through the 
headphones and the speaker.  That went on until I closed phone in the app 
switcher.  That also had to do with a call ringing while listening to a book.  
Crazy stuff, but I still like the update.

Lois

From: christopher hallsworth 
Sent: Thursday, September 17, 2015 4:30 AM
To: Viphone 
Subject: Re: My top iOS 9 Bugs

It cannot be duplicated since it is not device specific nor is it situation 
specific.

  On 17 Sep 2015, at 09:28, Jenifer Barr <claudas...@gmail.com> wrote:

  Has anyone been able to duplicate point 1? That's my whole hesitation of 
updating because I constantly use earbuds.
  Thanks. 

  Jenifer Barr 
  Sent from my iPhone

  On Sep 16, 2015, at 1:15 PM, Jonathan Mosen <jmo...@mosen.org> wrote:


Hi everyone, now that the NDA is lifted, here are some things I think you 
might like to be aware of in iOS 9. 
I am enthusiastic about iOS 9. It is significantly more responsive than its 
predecessor, and there are many new features that I'm sure you'll enjoy. 
Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
minor annoyances to potentially critical, depending on how you use your device 
and whether you find yourself affected. Here are just a few that you might like 
to take into consideration before deciding whether to wait for a bug fix 
release before installing iOS 9. Remember that a few days following iOS 9's 
release, it will not be possible to downgrade again, so you should consider the 
upgrade to iOS 9 a one-way trip, and proceed with caution if anything below 
concerns you.
1. Audio routing bug. This is potentially the most significant 
accessibility bug I can recall ever to slip through an iOS release, due to the 
number of people who may be affected. Not everyone will be, and at present, 
even after extensive testing with a range of people owning different devices, I 
have no information about why it affects some users, but not others. It is not 
device specific, for example it is happening to me on my iPhone 6 Plus, but I 
know iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to 
be affected by any setting. If you're lucky, it won't happen to you, but the 
only way I am aware of to determine this is to upgrade.
This bug may affect you when you have earbuds or headphones connected to 
the headphone socket of your iPhone. The primary way the audio routing bug 
manifests itself is when you receive an incoming phone or FaceTime call. You 
can usually hear if you're going to be affected by the bug because your 
ring-tone will fade in and out, rather like the way VOiceOver causes system 
audio to fade in and out when audio ducking is enabled. At this point, if you 
press the power button to silence the ringer and then flick through the screen, 
you will find that not only has VOiceOver become unresponsive, but the entire 
phone has as well.
If you don't press the power button while the phone is ringing, but instead 
opt to flick through the iPHone's screen to locate the Answer button or review 
caller ID information, VoiceOver may not speak at all.
Finally, if you attempt to answer the incoming call with a two-finger 
double-tap, you may not be able to, since VoiceOver has effectively locked up.
The bottom line is that if you have earbuds connected, you may not be able 
to answer a call.
Some people have also reported similar problems answering calls when their 
phone is set to silent.
If you rely on your phone for business or safety, this could be a deal 
breaker in terms of upgrading at this point.
What makes this bug so fascinating is that not only is it completely absent 
for some people, but of those who experience it, not all symptoms are present 
for all users. For example, some people experience the issues I have described 
when they press the power button to mute the ringer, but not when the phone is 
ringing. Others can answer a call by pressing the button on their EarPods, 
while others cannot.
If you upgrade and are affected by this, here are a few things to try.
(A) If you have the more moderate version of this bug, avoid pressing the 
power button when you receive an incoming call.
(B) Turning off audio ducking seems to help a little for some users.
(C) If you can't answer a call with a two-finger double-tap, try pressing 
the button on your EarPods or similar device if you have such a device 
connected.
(D) If all else fails, you can disconnect any device from the headphone 
jack, answer the call with a two-finge

Re: My top iOS 9 Bugs

[Lois Butterfield]

Hi Alex,

I mean that, when I move my finger across the mic, I can hear it.  I also 
can't restart my book.  Also VO doesn't work.  That is a problem.


Thanks,
Lois

-Original Message- 
From: Alex Stone

Sent: Thursday, September 17, 2015 5:00 AM
To: viphone@googlegroups.com
Subject: RE: My top iOS 9 Bugs

Sorry, but what do you mean by "the microphone remains open", surely if the 
call has ended this wouldn't make any difference.


-Original Message-
From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf 
Of Lois Butterfield

Sent: 17 September 2015 09:53
To: viphone@googlegroups.com
Subject: Re: My top iOS 9 Bugs

What happens with my iPhone 6 is, when I get a call while earphones are 
plugged in, which is most of the time, everything is fine until I hang up 
the call.  That is when something funny happens.  The microphone remains 
open, and VO is dead.  I have to unplug and plug back in to resolve the 
issue.  Since it doesn’t effect the actual calls, I can live with it.


Once, I dropped the phone while plugged in, and I had sound both through the 
headphones and the speaker.  That went on until I closed phone in the app 
switcher.  That also had to do with a call ringing while listening to a 
book.  Crazy stuff, but I still like the update.


Lois

From: christopher hallsworth <mailto:challswor...@icloud.com>
Sent: Thursday, September 17, 2015 4:30 AM
To: Viphone <mailto:viphone@googlegroups.com>
Subject: Re: My top iOS 9 Bugs

It cannot be duplicated since it is not device specific nor is it situation 
specific.



On 17 Sep 2015, at 09:28, Jenifer Barr <claudas...@gmail.com 
<mailto:claudas...@gmail.com> > wrote:


Has anyone been able to duplicate point 1? That's my whole hesitation of 
updating because I constantly use earbuds.

Thanks.

Jenifer Barr
Sent from my iPhone

On Sep 16, 2015, at 1:15 PM, Jonathan Mosen <jmo...@mosen.org 
<mailto:jmo...@mosen.org> > wrote:




Hi everyone, now that the NDA is lifted, here are some things I think you 
might like to be aware of in iOS 9.
I am enthusiastic about iOS 9. It is significantly more responsive than its 
predecessor, and there are many new features that I'm sure you'll enjoy. 
Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
minor annoyances to potentially critical, depending on how you use your 
device and whether you find yourself affected. Here are just a few that you 
might like to take into consideration before deciding whether to wait for a 
bug fix release before installing iOS 9. Remember that a few days following 
iOS 9's release, it will not be possible to downgrade again, so you should 
consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
anything below concerns you.
1. Audio routing bug. This is potentially the most significant accessibility 
bug I can recall ever to slip through an iOS release, due to the number of 
people who may be affected. Not everyone will be, and at present, even after 
extensive testing with a range of people owning different devices, I have no 
information about why it affects some users, but not others. It is not 
device specific, for example it is happening to me on my iPhone 6 Plus, but 
I know iPhone 6 Plus users where the problem isn't so severe. Nor does it 
seem to be affected by any setting. If you're lucky, it won't happen to you, 
but the only way I am aware of to determine this is to upgrade.
This bug may affect you when you have earbuds or headphones connected to the 
headphone socket of your iPhone. The primary way the audio routing bug 
manifests itself is when you receive an incoming phone or FaceTime call. You 
can usually hear if you're going to be affected by the bug because your 
ring-tone will fade in and out, rather like the way VOiceOver causes system 
audio to fade in and out when audio ducking is enabled. At this point, if 
you press the power button to silence the ringer and then flick through the 
screen, you will find that not only has VOiceOver become unresponsive, but 
the entire phone has as well.
If you don't press the power button while the phone is ringing, but instead 
opt to flick through the iPHone's screen to locate the Answer button or 
review caller ID information, VoiceOver may not speak at all.
Finally, if you attempt to answer the incoming call with a two-finger 
double-tap, you may not be able to, since VoiceOver has effectively locked 
up.
The bottom line is that if you have earbuds connected, you may not be able 
to answer a call.
Some people have also reported similar problems answering calls when their 
phone is set to silent.
If you rely on your phone for business or safety, this could be a deal 
breaker in terms of upgrading at this point.
What makes this bug so fascinating is that not only is it completely absent 
for some people, but of those who experience it, not all symptoms are 
present for all users. For example, some 

RE: My top iOS 9 Bugs

[Alex Stone]

Oh I see, that's a bit odd.

-Original Message-
From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf Of 
Lois Butterfield
Sent: 17 September 2015 10:04
To: viphone@googlegroups.com
Subject: Re: My top iOS 9 Bugs

Hi Alex,

I mean that, when I move my finger across the mic, I can hear it.  I also 
can't restart my book.  Also VO doesn't work.  That is a problem.

Thanks,
Lois

-Original Message- 
From: Alex Stone
Sent: Thursday, September 17, 2015 5:00 AM
To: viphone@googlegroups.com
Subject: RE: My top iOS 9 Bugs

Sorry, but what do you mean by "the microphone remains open", surely if the 
call has ended this wouldn't make any difference.

-Original Message-
From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf 
Of Lois Butterfield
Sent: 17 September 2015 09:53
To: viphone@googlegroups.com
Subject: Re: My top iOS 9 Bugs

What happens with my iPhone 6 is, when I get a call while earphones are 
plugged in, which is most of the time, everything is fine until I hang up 
the call.  That is when something funny happens.  The microphone remains 
open, and VO is dead.  I have to unplug and plug back in to resolve the 
issue.  Since it doesn’t effect the actual calls, I can live with it.

Once, I dropped the phone while plugged in, and I had sound both through the 
headphones and the speaker.  That went on until I closed phone in the app 
switcher.  That also had to do with a call ringing while listening to a 
book.  Crazy stuff, but I still like the update.

Lois

From: christopher hallsworth <mailto:challswor...@icloud.com>
Sent: Thursday, September 17, 2015 4:30 AM
To: Viphone <mailto:viphone@googlegroups.com>
Subject: Re: My top iOS 9 Bugs

It cannot be duplicated since it is not device specific nor is it situation 
specific.


On 17 Sep 2015, at 09:28, Jenifer Barr <claudas...@gmail.com 
<mailto:claudas...@gmail.com> > wrote:

Has anyone been able to duplicate point 1? That's my whole hesitation of 
updating because I constantly use earbuds.
Thanks.

Jenifer Barr
Sent from my iPhone

On Sep 16, 2015, at 1:15 PM, Jonathan Mosen <jmo...@mosen.org 
<mailto:jmo...@mosen.org> > wrote:



Hi everyone, now that the NDA is lifted, here are some things I think you 
might like to be aware of in iOS 9.
I am enthusiastic about iOS 9. It is significantly more responsive than its 
predecessor, and there are many new features that I'm sure you'll enjoy. 
Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
minor annoyances to potentially critical, depending on how you use your 
device and whether you find yourself affected. Here are just a few that you 
might like to take into consideration before deciding whether to wait for a 
bug fix release before installing iOS 9. Remember that a few days following 
iOS 9's release, it will not be possible to downgrade again, so you should 
consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
anything below concerns you.
1. Audio routing bug. This is potentially the most significant accessibility 
bug I can recall ever to slip through an iOS release, due to the number of 
people who may be affected. Not everyone will be, and at present, even after 
extensive testing with a range of people owning different devices, I have no 
information about why it affects some users, but not others. It is not 
device specific, for example it is happening to me on my iPhone 6 Plus, but 
I know iPhone 6 Plus users where the problem isn't so severe. Nor does it 
seem to be affected by any setting. If you're lucky, it won't happen to you, 
but the only way I am aware of to determine this is to upgrade.
This bug may affect you when you have earbuds or headphones connected to the 
headphone socket of your iPhone. The primary way the audio routing bug 
manifests itself is when you receive an incoming phone or FaceTime call. You 
can usually hear if you're going to be affected by the bug because your 
ring-tone will fade in and out, rather like the way VOiceOver causes system 
audio to fade in and out when audio ducking is enabled. At this point, if 
you press the power button to silence the ringer and then flick through the 
screen, you will find that not only has VOiceOver become unresponsive, but 
the entire phone has as well.
If you don't press the power button while the phone is ringing, but instead 
opt to flick through the iPHone's screen to locate the Answer button or 
review caller ID information, VoiceOver may not speak at all.
Finally, if you attempt to answer the incoming call with a two-finger 
double-tap, you may not be able to, since VoiceOver has effectively locked 
up.
The bottom line is that if you have earbuds connected, you may not be able 
to answer a call.
Some people have also reported similar problems answering calls when their 
phone is set to silent.
If you rely on your phone for business or safety, this could be a deal 
bre

Re: My top iOS 9 Bugs

[Jenifer Barr]

Has anyone been able to duplicate point 1? That's my whole hesitation of 
updating because I constantly use earbuds.
Thanks. 

Jenifer Barr
Sent from my iPhone

> On Sep 16, 2015, at 1:15 PM, Jonathan Mosen  wrote:
> 
> Hi everyone, now that the NDA is lifted, here are some things I think you 
> might like to be aware of in iOS 9.
> I am enthusiastic about iOS 9. It is significantly more responsive than its 
> predecessor, and there are many new features that I'm sure you'll enjoy. 
> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
> minor annoyances to potentially critical, depending on how you use your 
> device and whether you find yourself affected. Here are just a few that you 
> might like to take into consideration before deciding whether to wait for a 
> bug fix release before installing iOS 9. Remember that a few days following 
> iOS 9's release, it will not be possible to downgrade again, so you should 
> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
> anything below concerns you.
> 1. Audio routing bug. This is potentially the most significant accessibility 
> bug I can recall ever to slip through an iOS release, due to the number of 
> people who may be affected. Not everyone will be, and at present, even after 
> extensive testing with a range of people owning different devices, I have no 
> information about why it affects some users, but not others. It is not device 
> specific, for example it is happening to me on my iPhone 6 Plus, but I know 
> iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to be 
> affected by any setting. If you're lucky, it won't happen to you, but the 
> only way I am aware of to determine this is to upgrade.
> This bug may affect you when you have earbuds or headphones connected to the 
> headphone socket of your iPhone. The primary way the audio routing bug 
> manifests itself is when you receive an incoming phone or FaceTime call. You 
> can usually hear if you're going to be affected by the bug because your 
> ring-tone will fade in and out, rather like the way VOiceOver causes system 
> audio to fade in and out when audio ducking is enabled. At this point, if you 
> press the power button to silence the ringer and then flick through the 
> screen, you will find that not only has VOiceOver become unresponsive, but 
> the entire phone has as well.
> If you don't press the power button while the phone is ringing, but instead 
> opt to flick through the iPHone's screen to locate the Answer button or 
> review caller ID information, VoiceOver may not speak at all.
> Finally, if you attempt to answer the incoming call with a two-finger 
> double-tap, you may not be able to, since VoiceOver has effectively locked up.
> The bottom line is that if you have earbuds connected, you may not be able to 
> answer a call.
> Some people have also reported similar problems answering calls when their 
> phone is set to silent.
> If you rely on your phone for business or safety, this could be a deal 
> breaker in terms of upgrading at this point.
> What makes this bug so fascinating is that not only is it completely absent 
> for some people, but of those who experience it, not all symptoms are present 
> for all users. For example, some people experience the issues I have 
> described when they press the power button to mute the ringer, but not when 
> the phone is ringing. Others can answer a call by pressing the button on 
> their EarPods, while others cannot.
> If you upgrade and are affected by this, here are a few things to try.
> (A) If you have the more moderate version of this bug, avoid pressing the 
> power button when you receive an incoming call.
> (B) Turning off audio ducking seems to help a little for some users.
> (C) If you can't answer a call with a two-finger double-tap, try pressing the 
> button on your EarPods or similar device if you have such a device connected.
> (D) If all else fails, you can disconnect any device from the headphone jack, 
> answer the call with a two-finger double-tap, then reconnect the device to 
> the headphone jack.
> (E) Given the critical nature of this bug, if you've upgraded and now find 
> yourself afflicted by it, enrol in the iOS beta program so you can receive 
> early copies of any fixes Apple is working on. But keep in mind that since 
> you will be running beta software, you may well be swapping one set of bugs 
> for another.
> 2. Bluetooth keyboard support unreliable. Sometimes, users may input double 
> letters when typing. This is a bug that was introduced in the iOS 8 cycle, 
> and can easily be worked around by toggling VoiceOver off and on.
> However, a new bug now exists where at times, no text is entered into a field 
> at all when VO is active. Toggling VO doesn't help, nor does switching the 
> keyboard off and on. The only immediate remedy is to turn Vo off, and keep 
> typing without it. If you turn VO back on 

Re: My top iOS 9 Bugs

[Robert Doc Wright]

If you run into problems you might try doing a "reset all".  Do Not 
choose Erase!.


there is another bug with bluetooth keyboards. the find command VO+f 
only rarely works.



On 9/17/2015 2:30 AM, christopher hallsworth wrote:

It cannot be duplicated since it is not device specific nor is it
situation specific.

On 17 Sep 2015, at 09:28, Jenifer Barr > wrote:

Has anyone been able to duplicate point 1? That's my whole hesitation
of updating because I constantly use earbuds.
Thanks.

Jenifer Barr
Sent from my iPhone

On Sep 16, 2015, at 1:15 PM, Jonathan Mosen > wrote:


Hi everyone, now that the NDA is lifted, here are some things I think
you might like to be aware of in iOS 9.
I am enthusiastic about iOS 9. It is significantly more responsive
than its predecessor, and there are many new features that I'm sure
you'll enjoy. Unfortunately, there are also some VoiceOver bugs in
iOS 9 that range from minor annoyances to potentially critical,
depending on how you use your device and whether you find yourself
affected. Here are just a few that you might like to take into
consideration before deciding whether to wait for a bug fix release
before installing iOS 9. Remember that a few days following iOS 9's
release, it will not be possible to downgrade again, so you should
consider the upgrade to iOS 9 a one-way trip, and proceed with
caution if anything below concerns you.
1. Audio routing bug. This is potentially the most significant
accessibility bug I can recall ever to slip through an iOS release,
due to the number of people who may be affected. Not everyone will
be, and at present, even after extensive testing with a range of
people owning different devices, I have no information about why it
affects some users, but not others. It is not device specific, for
example it is happening to me on my iPhone 6 Plus, but I know iPhone
6 Plus users where the problem isn't so severe. Nor does it seem to
be affected by any setting. If you're lucky, it won't happen to you,
but the only way I am aware of to determine this is to upgrade.
This bug may affect you when you have earbuds or headphones connected
to the headphone socket of your iPhone. The primary way the audio
routing bug manifests itself is when you receive an incoming phone or
FaceTime call. You can usually hear if you're going to be affected by
the bug because your ring-tone will fade in and out, rather like the
way VOiceOver causes system audio to fade in and out when audio
ducking is enabled. At this point, if you press the power button to
silence the ringer and then flick through the screen, you will find
that not only has VOiceOver become unresponsive, but the entire phone
has as well.
If you don't press the power button while the phone is ringing, but
instead opt to flick through the iPHone's screen to locate the Answer
button or review caller ID information, VoiceOver may not speak at all.
Finally, if you attempt to answer the incoming call with a two-finger
double-tap, you may not be able to, since VoiceOver has effectively
locked up.
The bottom line is that if you have earbuds connected, you may not be
able to answer a call.
Some people have also reported similar problems answering calls when
their phone is set to silent.
If you rely on your phone for business or safety, this could be a
deal breaker in terms of upgrading at this point.
What makes this bug so fascinating is that not only is it completely
absent for some people, but of those who experience it, not all
symptoms are present for all users. For example, some people
experience the issues I have described when they press the power
button to mute the ringer, but not when the phone is ringing. Others
can answer a call by pressing the button on their EarPods, while
others cannot.
If you upgrade and are affected by this, here are a few things to try.
(A) If you have the more moderate version of this bug, avoid pressing
the power button when you receive an incoming call.
(B) Turning off audio ducking seems to help a little for some users.
(C) If you can't answer a call with a two-finger double-tap, try
pressing the button on your EarPods or similar device if you have
such a device connected.
(D) If all else fails, you can disconnect any device from the
headphone jack, answer the call with a two-finger double-tap, then
reconnect the device to the headphone jack.
(E) Given the critical nature of this bug, if you've upgraded and now
find yourself afflicted by it, enrol in the iOS beta program so you
can receive early copies of any fixes Apple is working on. But keep
in mind that since you will be running beta software, you may well be
swapping one set of bugs for another.
2. Bluetooth keyboard support unreliable. Sometimes, users may input
double letters when typing. This is a bug that was introduced in the
iOS 8 cycle, and can easily be worked around by toggling VoiceOver
off and on.
However, a new bug 

Re: My top iOS 9 Bugs

[Robin]

Hey Jonathan Mosen

I'm wondering if Apple ImProved Siri ToYourSatisfaction

Is its (Siri) now OnParWith Microsoft'sCortana & Google'sGoogleNow 
InYourHumbleOpinion




At 10:15 AM 9/16/2015, you wrote:
Hi everyone, now that the NDA is lifted, here are some things I 
think you might like to be aware of in iOS 9.
I am enthusiastic about iOS 9. It is significantly more responsive 
than its predecessor, and there are many new features that I'm sure 
you'll enjoy. Unfortunately, there are also some VoiceOver bugs in 
iOS 9 that range from minor annoyances to potentially critical, 
depending on how you use your device and whether you find yourself 
affected. Here are just a few that you might like to take into 
consideration before deciding whether to wait for a bug fix release 
before installing iOS 9. Remember that a few days following iOS 9's 
release, it will not be possible to downgrade again, so you should 
consider the upgrade to iOS 9 a one-way trip, and proceed with 
caution if anything below concerns you.
1. Audio routing bug. This is potentially the most significant 
accessibility bug I can recall ever to slip through an iOS release, 
due to the number of people who may be affected. Not everyone will 
be, and at present, even after extensive testing with a range of 
people owning different devices, I have no information about why it 
affects some users, but not others. It is not device specific, for 
example it is happening to me on my iPhone 6 Plus, but I know iPhone 
6 Plus users where the problem isn't so severe. Nor does it seem to 
be affected by any setting. If you're lucky, it won't happen to you, 
but the only way I am aware of to determine this is to upgrade.
This bug may affect you when you have earbuds or headphones 
connected to the headphone socket of your iPhone. The primary way 
the audio routing bug manifests itself is when you receive an 
incoming phone or FaceTime call. You can usually hear if you're 
going to be affected by the bug because your ring-tone will fade in 
and out, rather like the way VOiceOver causes system audio to fade 
in and out when audio ducking is enabled. At this point, if you 
press the power button to silence the ringer and then flick through 
the screen, you will find that not only has VOiceOver become 
unresponsive, but the entire phone has as well.
If you don't press the power button while the phone is ringing, but 
instead opt to flick through the iPHone's screen to locate the 
Answer button or review caller ID information, VoiceOver may not speak at all.
Finally, if you attempt to answer the incoming call with a 
two-finger double-tap, you may not be able to, since VoiceOver has 
effectively locked up.
The bottom line is that if you have earbuds connected, you may not 
be able to answer a call.
Some people have also reported similar problems answering calls when 
their phone is set to silent.
If you rely on your phone for business or safety, this could be a 
deal breaker in terms of upgrading at this point.
What makes this bug so fascinating is that not only is it completely 
absent for some people, but of those who experience it, not all 
symptoms are present for all users. For example, some people 
experience the issues I have described when they press the power 
button to mute the ringer, but not when the phone is ringing. Others 
can answer a call by pressing the button on their EarPods, while others cannot.

If you upgrade and are affected by this, here are a few things to try.
(A) If you have the more moderate version of this bug, avoid 
pressing the power button when you receive an incoming call.

(B) Turning off audio ducking seems to help a little for some users.
(C) If you can't answer a call with a two-finger double-tap, try 
pressing the button on your EarPods or similar device if you have 
such a device connected.
(D) If all else fails, you can disconnect any device from the 
headphone jack, answer the call with a two-finger double-tap, then 
reconnect the device to the headphone jack.
(E) Given the critical nature of this bug, if you've upgraded and 
now find yourself afflicted by it, enrol in the iOS beta program so 
you can receive early copies of any fixes Apple is working on. But 
keep in mind that since you will be running beta software, you may 
well be swapping one set of bugs for another.
2. Bluetooth keyboard support unreliable. Sometimes, users may input 
double letters when typing. This is a bug that was introduced in the 
iOS 8 cycle, and can easily be worked around by toggling VoiceOver off and on.
However, a new bug now exists where at times, no text is entered 
into a field at all when VO is active. Toggling VO doesn't help, nor 
does switching the keyboard off and on. The only immediate remedy is 
to turn Vo off, and keep typing without it. If you turn VO back on 
again, the arrow keys don't work when you're trying to navigate your 
text, and you can't edit it.
3. In the Today view of Notification Center, VO frequently 

Re: My top iOS 9 Bugs

['carol.pearso...@googlemail.com' via VIPhone]

That bluetooth keyboard problem stems back into IOS8.  It drove me mad till I 
discovered you could reload Voice-Over.  Now it's even worse, by sounds of 
things.  ...

Yes, everyone, tell Apple this isn't good enough for those of us not good at 
typing on the phone!

I will do likewise as soon as I experience the problem once I've downloaded.
Carol P

  - Original Message - 
  From: 'Eleanor Roberts' via VIPhone 
  To: viphone@googlegroups.com 
  Sent: Thursday, September 17, 2015 12:44 PM
  Subject: Re: My top iOS 9 Bugs


  Hi 


  Please can folk make sure they report these bugs to Apple, especially the 
bluetooth keyboard one! Whilst I do occasionally use the touch screen, 99.9% of 
the time I use my bluetooth keyboard for everything. I've reported it to Apple 
accessibility, but would strongly encourage everyone else to do the same, 
otherwise it'll never get fixed. 


  Eleanor 

  Sent from my iPad

  On 17 Sep 2015, at 12:10, Devin Prater <r.d.t.pra...@gmail.com> wrote:


My biggest bug is the bluetooth keyboard problem. I know, I have, and love, 
my Varioultra, but I have a friend that exclusively uses a keyboard, and it hit 
her hard. 

Sent from my iPhone

On Sep 16, 2015, at 4:54 PM, Jonathan Mosen <jmo...@mosen.org> wrote:


  Hi Neal. My understanding is that if you are affected, it will also 
happen if you have your phone on silent. If you just have your phone unmuted 
and on speaker, it appears to be OK as far as I know.

  Jonathan Mosen
  Mosen Consulting
  Blindness technology eBooks, tutorials and training
  http://Mosen.org


On 17/09/2015, at 9:38 AM, Neal Ewers <neal.ew...@ravenswood.org> wrote:


Jonathan. Is this phone problem a problem only when using something 
connected to the phone such as ear buds or a bluetooth device? Or, does it also 
effect phone calls if you are using none of these devices and only using the 
microphone and speaker in the phone?

Thanks.

Neal


From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On 
Behalf Of Jonathan Mosen
Sent: Wednesday, September 16, 2015 12:15 PM
To: viphone@googlegroups.com
        Subject: My top iOS 9 Bugs

Hi everyone, now that the NDA is lifted, here are some things I think 
you might like to be aware of in iOS 9.
I am enthusiastic about iOS 9. It is significantly more responsive than 
its predecessor, and there are many new features that I'm sure you'll enjoy. 
Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
minor annoyances to potentially critical, depending on how you use your device 
and whether you find yourself affected. Here are just a few that you might like 
to take into consideration before deciding whether to wait for a bug fix 
release before installing iOS 9. Remember that a few days following iOS 9's 
release, it will not be possible to downgrade again, so you should consider the 
upgrade to iOS 9 a one-way trip, and proceed with caution if anything below 
concerns you.
1. Audio routing bug. This is potentially the most significant 
accessibility bug I can recall ever to slip through an iOS release, due to the 
number of people who may be affected. Not everyone will be, and at present, 
even after extensive testing with a range of people owning different devices, I 
have no information about why it affects some users, but not others. It is not 
device specific, for example it is happening to me on my iPhone 6 Plus, but I 
know iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to 
be affected by any setting. If you're lucky, it won't happen to you, but the 
only way I am aware of to determine this is to upgrade.
This bug may affect you when you have earbuds or headphones connected 
to the headphone socket of your iPhone. The primary way the audio routing bug 
manifests itself is when you receive an incoming phone or FaceTime call. You 
can usually hear if you're going to be affected by the bug because your 
ring-tone will fade in and out, rather like the way VOiceOver causes system 
audio to fade in and out when audio ducking is enabled. At this point, if you 
press the power button to silence the ringer and then flick through the screen, 
you will find that not only has VOiceOver become unresponsive, but the entire 
phone has as well.
If you don't press the power button while the phone is ringing, but 
instead opt to flick through the iPHone's screen to locate the Answer button or 
review caller ID information, VoiceOver may not speak at all.
Finally, if you attempt to answer the incoming call with a two-finger 
double-tap, you may not be able to, since VoiceOver has effectively locked up.
The bottom line is that if you have earbuds connected, you may not be 
able to answer a call.
Some people have also reported similar problems answering calls when 
their phon

Re: My top iOS 9 Bugs

[Russ Kiehne]

Last I heard, there will be a Bard mobile update.  They said the update 
would be released after ios 9 has been released.


-Original Message- 
From: Christopher Chaltain

Sent: Thursday, September 17, 2015 5:02 AM
To: viphone@googlegroups.com
Subject: Re: My top iOS 9 Bugs

I'm fairly certain there will be an update to the  BARD Mobile app. I'm
not sure why you're so certain there won't be. They released their
Android app not too long ago, so I'd be surprised if their resources
didn't switch to getting an update to the IOS app now. It may be a
while, but I don't see how the NLS couldn't have planned for some
updates to their mobile apps.

On 09/17/2015 06:54 AM, Devin Prater wrote:
Yes, Bard has become less useful for me as a braille reader. They say 
they'll make an update, but I'm quite sure they won't.


Sent from my iPhone

On Sep 16, 2015, at 4:11 PM, Woody Anna Dresner <wadres...@att.net> 
wrote:


Hi,

I've used a Focus 40 Blue Classic and a RefreshaBraille 18 throughout the 
betas and have had no problems except that BARD Mobile is far less likely 
to save my reading position than previously.


Best,
Anna



On Sep 16, 2015, at 3:06 PM, Melissa Tucker <melissatuck...@att.net> 
wrote:


does ios9 give any problems for people using a braille display?



On Sep 16, 2015, at 3:15 PM, Krister Ekstrom <kris...@kristersplace.com> 
wrote:


I always religiously update to the latest version of an Os when it comes 
out, if it works it does, if not… well shrug.

/Krister


16 sep. 2015 kl. 20:02 skrev Mike Arrigo <n0...@charter.net>:

In general, I think it's always good to wait until at least the first 
major update, sometimes the second of any new operating system so the 
major bugs can get worked out. Upgrading to a new version of an 
operating system as soon as it's released is far too risky.

Original message:
Hi everyone, now that the NDA is lifted, here are some things I think 
you might like to be aware of in iOS 9.
I am enthusiastic about iOS 9. It is significantly more responsive 
than its predecessor, and there are many new features that I'm sure 
you'll enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 
9 that range from minor annoyances to potentially critical, depending 
on how you use your device and whether you find yourself affected. 
Here are just a few that you might like to take into consideration 
before deciding whether to wait for a bug fix release before 
installing iOS 9. Remember that a few days following iOS 9's release, 
it will not be possible to downgrade again, so you should consider the 
upgrade to iOS 9 a one-way trip, and proceed with caution if anything 
below concerns you.
1. Audio routing bug. This is potentially the most significant 
accessibility bug I can recall ever to slip through an iOS release, 
due to the number of people who may be affected. Not everyone will be, 
and at present, even after extensive testing with a range of people 
owning different devices, I have no information about why it affects 
some users, but not others. It is not device specific, for example it 
is happening to me on my iPhone 6 Plus, but I know iPhone 6 Plus users 
where the problem isn't so severe. Nor does it seem to be affected by 
any setting. If you're lucky, it won't happen to you, but the only way 
I am aware of to determine this is to upgrade.
This bug may affect you when you have earbuds or headphones connected 
to the headphone socket of your iPhone. The primary way the audio 
routing bug manifests itself is when you receive an incoming phone or 
FaceTime call. You can usually hear if you're going to be affected by 
the bug because your ring-tone will fade in and out, rather like the 
way VOiceOver causes system audio to fade in and out when audio 
ducking is enabled. At this point, if you press the power button to 
silence the ringer and then flick through the screen, you will find 
that not only has VOiceOver become unresponsive, but the entire phone 
has as well.
If you don't press the power button while the phone is ringing, but 
instead opt to flick through the iPHone's screen to locate the Answer 
button or review caller ID information, VoiceOver may not speak at 
all.
Finally, if you attempt to answer the incoming call with a two-finger 
double-tap, you may not be able to, since VoiceOver has effectively 
locked up.
The bottom line is that if you have earbuds connected, you may not be 
able to answer a call.
Some people have also reported similar problems answering calls when 
their phone is set to silent.
If you rely on your phone for business or safety, this could be a deal 
breaker in terms of upgrading at this point.
What makes this bug so fascinating is that not only is it completely 
absent for some people, but of those who experience it, not all 
symptoms are present for all users. For example, some people 
experience the issues I have described when they press the power 
button to mute the ringer, but not when the 

Re: My top iOS 9 Bugs

[Russ Kiehne]

Thanks, I’ll pass it along to him and let him decide if he wants to take the 
chance and upgrade.  I’ll probably give ios 9 a try on my 5th generation ipod 
touch.

From: Jonathan Mosen 
Sent: Thursday, September 17, 2015 8:41 AM
To: viphone@googlegroups.com 
Subject: Re: My top iOS 9 Bugs

Russ, the only possibility of it affecting him I'm aware of is if the phone is 
set to silent. Of course, he may be one of the lucky ones and never see it at 
all. 
With the software having been in the wild for 24 hours, and having read a lot 
of email and Twitter traffic, my anecdotal evidence is that 75% to 80% of users 
are not seeing the most serious incarnation of this bug. There just seems to be 
absolutely no way I've found of predicting who's going to be hit by it. While 
it's personally really frustrating to me, there's something fascinating about 
this one as well from an intellectual standpoint.

Jonathan Mosen
Mosen Consulting
Blindness technology eBooks, tutorials and training
http://Mosen.org

  On 18/09/2015, at 2:23 AM, Russ Kiehne <russ94...@gmail.com> wrote:

  Let me ask about: 1. Audio routing bug.  My brother has an iphone 6 and 
doesn’t use earbuds or headphones.  Will this bug effect him?

  From: Jonathan Mosen 
  Sent: Wednesday, September 16, 2015 10:15 AM
  To: viphone@googlegroups.com 
  Subject: My top iOS 9 Bugs

  Hi everyone, now that the NDA is lifted, here are some things I think you 
might like to be aware of in iOS 9. 
  I am enthusiastic about iOS 9. It is significantly more responsive than its 
predecessor, and there are many new features that I'm sure you'll enjoy. 
Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
minor annoyances to potentially critical, depending on how you use your device 
and whether you find yourself affected. Here are just a few that you might like 
to take into consideration before deciding whether to wait for a bug fix 
release before installing iOS 9. Remember that a few days following iOS 9's 
release, it will not be possible to downgrade again, so you should consider the 
upgrade to iOS 9 a one-way trip, and proceed with caution if anything below 
concerns you.
  1. Audio routing bug. This is potentially the most significant accessibility 
bug I can recall ever to slip through an iOS release, due to the number of 
people who may be affected. Not everyone will be, and at present, even after 
extensive testing with a range of people owning different devices, I have no 
information about why it affects some users, but not others. It is not device 
specific, for example it is happening to me on my iPhone 6 Plus, but I know 
iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to be 
affected by any setting. If you're lucky, it won't happen to you, but the only 
way I am aware of to determine this is to upgrade.
  This bug may affect you when you have earbuds or headphones connected to the 
headphone socket of your iPhone. The primary way the audio routing bug 
manifests itself is when you receive an incoming phone or FaceTime call. You 
can usually hear if you're going to be affected by the bug because your 
ring-tone will fade in and out, rather like the way VOiceOver causes system 
audio to fade in and out when audio ducking is enabled. At this point, if you 
press the power button to silence the ringer and then flick through the screen, 
you will find that not only has VOiceOver become unresponsive, but the entire 
phone has as well.
  If you don't press the power button while the phone is ringing, but instead 
opt to flick through the iPHone's screen to locate the Answer button or review 
caller ID information, VoiceOver may not speak at all.
  Finally, if you attempt to answer the incoming call with a two-finger 
double-tap, you may not be able to, since VoiceOver has effectively locked up.
  The bottom line is that if you have earbuds connected, you may not be able to 
answer a call.
  Some people have also reported similar problems answering calls when their 
phone is set to silent.
  If you rely on your phone for business or safety, this could be a deal 
breaker in terms of upgrading at this point.
  What makes this bug so fascinating is that not only is it completely absent 
for some people, but of those who experience it, not all symptoms are present 
for all users. For example, some people experience the issues I have described 
when they press the power button to mute the ringer, but not when the phone is 
ringing. Others can answer a call by pressing the button on their EarPods, 
while others cannot.
  If you upgrade and are affected by this, here are a few things to try.
  (A) If you have the more moderate version of this bug, avoid pressing the 
power button when you receive an incoming call.
  (B) Turning off audio ducking seems to help a little for some users.
  (C) If you can't answer a call with a two-finger double-tap, try pressing the 
button on your EarPods or similar device if yo

Re: My top iOS 9 Bugs

[Jonathan Mosen]

Russ, the only possibility of it affecting him I'm aware of is if the phone is 
set to silent. Of course, he may be one of the lucky ones and never see it at 
all.
With the software having been in the wild for 24 hours, and having read a lot 
of email and Twitter traffic, my anecdotal evidence is that 75% to 80% of users 
are not seeing the most serious incarnation of this bug. There just seems to be 
absolutely no way I've found of predicting who's going to be hit by it. While 
it's personally really frustrating to me, there's something fascinating about 
this one as well from an intellectual standpoint.
Jonathan Mosen
Mosen Consulting
Blindness technology eBooks, tutorials and training
http://Mosen.org

> On 18/09/2015, at 2:23 AM, Russ Kiehne <russ94...@gmail.com> wrote:
> 
> Let me ask about: 1. Audio routing bug.  My brother has an iphone 6 and 
> doesn’t use earbuds or headphones.  Will this bug effect him?
>  
> From: Jonathan Mosen <mailto:jmo...@mosen.org>
> Sent: Wednesday, September 16, 2015 10:15 AM
> To: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
> Subject: My top iOS 9 Bugs
>  
> Hi everyone, now that the NDA is lifted, here are some things I think you 
> might like to be aware of in iOS 9.
> I am enthusiastic about iOS 9. It is significantly more responsive than its 
> predecessor, and there are many new features that I'm sure you'll enjoy. 
> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
> minor annoyances to potentially critical, depending on how you use your 
> device and whether you find yourself affected. Here are just a few that you 
> might like to take into consideration before deciding whether to wait for a 
> bug fix release before installing iOS 9. Remember that a few days following 
> iOS 9's release, it will not be possible to downgrade again, so you should 
> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
> anything below concerns you.
> 1. Audio routing bug. This is potentially the most significant accessibility 
> bug I can recall ever to slip through an iOS release, due to the number of 
> people who may be affected. Not everyone will be, and at present, even after 
> extensive testing with a range of people owning different devices, I have no 
> information about why it affects some users, but not others. It is not device 
> specific, for example it is happening to me on my iPhone 6 Plus, but I know 
> iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to be 
> affected by any setting. If you're lucky, it won't happen to you, but the 
> only way I am aware of to determine this is to upgrade.
> This bug may affect you when you have earbuds or headphones connected to the 
> headphone socket of your iPhone. The primary way the audio routing bug 
> manifests itself is when you receive an incoming phone or FaceTime call. You 
> can usually hear if you're going to be affected by the bug because your 
> ring-tone will fade in and out, rather like the way VOiceOver causes system 
> audio to fade in and out when audio ducking is enabled. At this point, if you 
> press the power button to silence the ringer and then flick through the 
> screen, you will find that not only has VOiceOver become unresponsive, but 
> the entire phone has as well.
> If you don't press the power button while the phone is ringing, but instead 
> opt to flick through the iPHone's screen to locate the Answer button or 
> review caller ID information, VoiceOver may not speak at all.
> Finally, if you attempt to answer the incoming call with a two-finger 
> double-tap, you may not be able to, since VoiceOver has effectively locked up.
> The bottom line is that if you have earbuds connected, you may not be able to 
> answer a call.
> Some people have also reported similar problems answering calls when their 
> phone is set to silent.
> If you rely on your phone for business or safety, this could be a deal 
> breaker in terms of upgrading at this point.
> What makes this bug so fascinating is that not only is it completely absent 
> for some people, but of those who experience it, not all symptoms are present 
> for all users. For example, some people experience the issues I have 
> described when they press the power button to mute the ringer, but not when 
> the phone is ringing. Others can answer a call by pressing the button on 
> their EarPods, while others cannot.
> If you upgrade and are affected by this, here are a few things to try.
> (A) If you have the more moderate version of this bug, avoid pressing the 
> power button when you receive an incoming call.
> (B) Turning off audio ducking seems to help a little for some users.
> (C) If you can't answer a call with a two-finger double-tap, try pressing the 
>

Re: My top iOS 9 Bugs

[Russ Kiehne]

Let me ask about: 1. Audio routing bug.  My brother has an iphone 6 and doesn’t 
use earbuds or headphones.  Will this bug effect him?

From: Jonathan Mosen 
Sent: Wednesday, September 16, 2015 10:15 AM
To: viphone@googlegroups.com 
Subject: My top iOS 9 Bugs

Hi everyone, now that the NDA is lifted, here are some things I think you might 
like to be aware of in iOS 9. 
I am enthusiastic about iOS 9. It is significantly more responsive than its 
predecessor, and there are many new features that I'm sure you'll enjoy. 
Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
minor annoyances to potentially critical, depending on how you use your device 
and whether you find yourself affected. Here are just a few that you might like 
to take into consideration before deciding whether to wait for a bug fix 
release before installing iOS 9. Remember that a few days following iOS 9's 
release, it will not be possible to downgrade again, so you should consider the 
upgrade to iOS 9 a one-way trip, and proceed with caution if anything below 
concerns you.
1. Audio routing bug. This is potentially the most significant accessibility 
bug I can recall ever to slip through an iOS release, due to the number of 
people who may be affected. Not everyone will be, and at present, even after 
extensive testing with a range of people owning different devices, I have no 
information about why it affects some users, but not others. It is not device 
specific, for example it is happening to me on my iPhone 6 Plus, but I know 
iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to be 
affected by any setting. If you're lucky, it won't happen to you, but the only 
way I am aware of to determine this is to upgrade.
This bug may affect you when you have earbuds or headphones connected to the 
headphone socket of your iPhone. The primary way the audio routing bug 
manifests itself is when you receive an incoming phone or FaceTime call. You 
can usually hear if you're going to be affected by the bug because your 
ring-tone will fade in and out, rather like the way VOiceOver causes system 
audio to fade in and out when audio ducking is enabled. At this point, if you 
press the power button to silence the ringer and then flick through the screen, 
you will find that not only has VOiceOver become unresponsive, but the entire 
phone has as well.
If you don't press the power button while the phone is ringing, but instead opt 
to flick through the iPHone's screen to locate the Answer button or review 
caller ID information, VoiceOver may not speak at all.
Finally, if you attempt to answer the incoming call with a two-finger 
double-tap, you may not be able to, since VoiceOver has effectively locked up.
The bottom line is that if you have earbuds connected, you may not be able to 
answer a call.
Some people have also reported similar problems answering calls when their 
phone is set to silent.
If you rely on your phone for business or safety, this could be a deal breaker 
in terms of upgrading at this point.
What makes this bug so fascinating is that not only is it completely absent for 
some people, but of those who experience it, not all symptoms are present for 
all users. For example, some people experience the issues I have described when 
they press the power button to mute the ringer, but not when the phone is 
ringing. Others can answer a call by pressing the button on their EarPods, 
while others cannot.
If you upgrade and are affected by this, here are a few things to try.
(A) If you have the more moderate version of this bug, avoid pressing the power 
button when you receive an incoming call.
(B) Turning off audio ducking seems to help a little for some users.
(C) If you can't answer a call with a two-finger double-tap, try pressing the 
button on your EarPods or similar device if you have such a device connected.
(D) If all else fails, you can disconnect any device from the headphone jack, 
answer the call with a two-finger double-tap, then reconnect the device to the 
headphone jack.
(E) Given the critical nature of this bug, if you've upgraded and now find 
yourself afflicted by it, enrol in the iOS beta program so you can receive 
early copies of any fixes Apple is working on. But keep in mind that since you 
will be running beta software, you may well be swapping one set of bugs for 
another.
2. Bluetooth keyboard support unreliable. Sometimes, users may input double 
letters when typing. This is a bug that was introduced in the iOS 8 cycle, and 
can easily be worked around by toggling VoiceOver off and on.
However, a new bug now exists where at times, no text is entered into a field 
at all when VO is active. Toggling VO doesn't help, nor does switching the 
keyboard off and on. The only immediate remedy is to turn Vo off, and keep 
typing without it. If you turn VO back on again, the arrow keys don't work when 
you're trying to navigate your text, and you can't edit it.
3

Re: My top iOS 9 Bugs

[Woody Anna Dresner]

Hi,

I used Airplane mode a couple of days ago, and I had no trouble reconnecting 
with my Focus 40 Blue after I turned it off. So whether you will experience 
this bug probably depends which braille display you are using.

Best,
Anna



> On Sep 17, 2015, at 1:07 AM, christopher hallsworth <challswor...@icloud.com> 
> wrote:
> 
> It does, and it may impact those with residual or no hearing at all. If you 
> turn Airplane mode on, then turn bluetooth back on, your Braille display will 
> not automatically connect. You then need to go into Settings > general > 
> accessibility > VoiceOver > Braille and double tap on your display to connect 
> again. But the problem doesn't end there. While still in Airplane Mode, if 
> you lock your device and unlock it again, the display will once again not 
> connect automatically. You will have to do the above to connect again.
> Chris
>> On 17 Sep 2015, at 04:10, Ron Pelletier <ron.pellet...@sympatico.ca> wrote:
>> 
>> According to Applevis, it does
>> 
>> Ron & Danvers
>> 
>> -Original Message-
>> From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf 
>> Of Melissa Tucker
>> Sent: Wednesday, September 16, 2015 4:07 PM
>> To: viphone@googlegroups.com
>> Subject: Re: My top iOS 9 Bugs
>> 
>> does ios9 give any problems for people using a braille display?
>> 
>> 
>> 
>> On Sep 16, 2015, at 3:15 PM, Krister Ekstrom <kris...@kristersplace.com> 
>> wrote:
>> 
>> I always religiously update to the latest version of an Os when it comes 
>> out, if it works it does, if not… well shrug.
>> /Krister
>> 
>>> 16 sep. 2015 kl. 20:02 skrev Mike Arrigo <n0...@charter.net>:
>>> 
>>> In general, I think it's always good to wait until at least the first major 
>>> update, sometimes the second of any new operating system so the major bugs 
>>> can get worked out. Upgrading to a new version of an operating system as 
>>> soon as it's released is far too risky.
>>> Original message:
>>>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>>>> might like to be aware of in iOS 9.
>>>> I am enthusiastic about iOS 9. It is significantly more responsive than 
>>>> its predecessor, and there are many new features that I'm sure you'll 
>>>> enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 9 that 
>>>> range from minor annoyances to potentially critical, depending on how you 
>>>> use your device and whether you find yourself affected. Here are just a 
>>>> few that you might like to take into consideration before deciding whether 
>>>> to wait for a bug fix release before installing iOS 9. Remember that a few 
>>>> days following iOS 9's release, it will not be possible to downgrade 
>>>> again, so you should consider the upgrade to iOS 9 a one-way trip, and 
>>>> proceed with caution if anything below concerns you.
>>>> 1. Audio routing bug. This is potentially the most significant 
>>>> accessibility bug I can recall ever to slip through an iOS release, due to 
>>>> the number of people who may be affected. Not everyone will be, and at 
>>>> present, even after extensive testing with a range of people owning 
>>>> different devices, I have no information about why it affects some users, 
>>>> but not others. It is not device specific, for example it is happening to 
>>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem 
>>>> isn't so severe. Nor does it seem to be affected by any setting. If you're 
>>>> lucky, it won't happen to you, but the only way I am aware of to determine 
>>>> this is to upgrade.
>>>> This bug may affect you when you have earbuds or headphones connected to 
>>>> the headphone socket of your iPhone. The primary way the audio routing bug 
>>>> manifests itself is when you receive an incoming phone or FaceTime call. 
>>>> You can usually hear if you're going to be affected by the bug because 
>>>> your ring-tone will fade in and out, rather like the way VOiceOver causes 
>>>> system audio to fade in and out when audio ducking is enabled. At this 
>>>> point, if you press the power button to silence the ringer and then flick 
>>>> through the screen, you will find that not only has VOiceOver become 
>>>> unresponsive, but the entire phone has as well.
>>>> If you don't press the power button while the phone is ringing, but 
>&

Re: My top iOS 9 Bugs

[Wayne Merritt]

I have no idea when it will be out, but I have heard from several
sources, including an NLS representative at the NFB convention, that
they are planning on updating the BARD Mobile app. They said soon, but
no idea when that will be. I expect sooner than later since they have
been working on this update for awhile now and have said publically
several times that they were working on an update, which will fix many
of the crashing issues people have been experiencing. We'll see.

Wayne

On 9/17/15, Christopher Chaltain  wrote:
> I'm fairly certain there will be an update to the  BARD Mobile app. I'm
> not sure why you're so certain there won't be. They released their
> Android app not too long ago, so I'd be surprised if their resources
> didn't switch to getting an update to the IOS app now. It may be a
> while, but I don't see how the NLS couldn't have planned for some
> updates to their mobile apps.
>
> On 09/17/2015 06:54 AM, Devin Prater wrote:
>> Yes, Bard has become less useful for me as a braille reader. They say
>> they'll make an update, but I'm quite sure they won't.
>>
>> Sent from my iPhone
>>
>>> On Sep 16, 2015, at 4:11 PM, Woody Anna Dresner 
>>> wrote:
>>>
>>> Hi,
>>>
>>> I've used a Focus 40 Blue Classic and a RefreshaBraille 18 throughout the
>>> betas and have had no problems except that BARD Mobile is far less likely
>>> to save my reading position than previously.
>>>
>>> Best,
>>> Anna
>>>
>>>
>>>
 On Sep 16, 2015, at 3:06 PM, Melissa Tucker 
 wrote:

 does ios9 give any problems for people using a braille display?



 On Sep 16, 2015, at 3:15 PM, Krister Ekstrom 
 wrote:

 I always religiously update to the latest version of an Os when it comes
 out, if it works it does, if not… well shrug.
 /Krister

> 16 sep. 2015 kl. 20:02 skrev Mike Arrigo :
>
> In general, I think it's always good to wait until at least the first
> major update, sometimes the second of any new operating system so the
> major bugs can get worked out. Upgrading to a new version of an
> operating system as soon as it's released is far too risky.
> Original message:
>> Hi everyone, now that the NDA is lifted, here are some things I think
>> you might like to be aware of in iOS 9.
>> I am enthusiastic about iOS 9. It is significantly more responsive
>> than its predecessor, and there are many new features that I'm sure
>> you'll enjoy. Unfortunately, there are also some VoiceOver bugs in iOS
>> 9 that range from minor annoyances to potentially critical, depending
>> on how you use your device and whether you find yourself affected.
>> Here are just a few that you might like to take into consideration
>> before deciding whether to wait for a bug fix release before
>> installing iOS 9. Remember that a few days following iOS 9's release,
>> it will not be possible to downgrade again, so you should consider the
>> upgrade to iOS 9 a one-way trip, and proceed with caution if anything
>> below concerns you.
>> 1. Audio routing bug. This is potentially the most significant
>> accessibility bug I can recall ever to slip through an iOS release,
>> due to the number of people who may be affected. Not everyone will be,
>> and at present, even after extensive testing with a range of people
>> owning different devices, I have no information about why it affects
>> some users, but not others. It is not device specific, for example it
>> is happening to me on my iPhone 6 Plus, but I know iPhone 6 Plus users
>> where the problem isn't so severe. Nor does it seem to be affected by
>> any setting. If you're lucky, it won't happen to you, but the only way
>> I am aware of to determine this is to upgrade.
>> This bug may affect you when you have earbuds or headphones connected
>> to the headphone socket of your iPhone. The primary way the audio
>> routing bug manifests itself is when you receive an incoming phone or
>> FaceTime call. You can usually hear if you're going to be affected by
>> the bug because your ring-tone will fade in and out, rather like the
>> way VOiceOver causes system audio to fade in and out when audio
>> ducking is enabled. At this point, if you press the power button to
>> silence the ringer and then flick through the screen, you will find
>> that not only has VOiceOver become unresponsive, but the entire phone
>> has as well.
>> If you don't press the power button while the phone is ringing, but
>> instead opt to flick through the iPHone's screen to locate the Answer
>> button or review caller ID information, VoiceOver may not speak at
>> all.
>> Finally, if you attempt to answer the incoming call with a two-finger
>> double-tap, you may not be able to, since VoiceOver 

RE: My top iOS 9 Bugs

[Sieghard Weitzel]

Hi Lois,

My 5S was behaving the same way when I ran iOS 9 Beta, I reverted back to iOS 
8.4.1 for the time being since I make and receive a lot of phone calls and that 
is one function I really want to work. As you describe, the phone seems to be 
frozen after I hang up with headphones attached, Voiceover is gone, you can't 
restart playback of a book or music, you can't activate SIRI etc. As soon as I 
unplug my headset it takes about 5 seconds and Voiceover comes back. 
Unfortunately at least in the first version of iOS 9.1 Beta this persists. I 
also had issues with Skype where often Skype displayed a message that something 
was wrong with the audio on my device when I tried to make a Skype call. 
Work-around for that was to reboot the phone and I could make a Skype call, but 
if I tried again a few hours later I received the same message and who wants to 
reboot the phone every time you want to make a Skype call.

If making phone calls with headset is a big part of the usage of your phone, I 
recommend not to upgrade to iOS 9 right away. Hopefully now that iOS 9 is out 
and hopefully now that people in greater numbers report these problems to Apple 
Accessibility something will be done about it sooner rather than later. It will 
be interesting to see if I am going to have these issues when I receive my new 
iPhone 6S. Also, keep in mind that what Lois and I experience is a very mild 
form of this bug, the problem can be much worse to the point where you can't 
even answer an incoming call when a headset is connected. Doing a reset network 
settings or a complete restore will not fix this since Jonathan and other beta 
testers have tried without any success.


Regards,
Sieghard

-Original Message-
From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf Of 
Lois Butterfield
Sent: Thursday, September 17, 2015 2:04 AM
To: viphone@googlegroups.com
Subject: Re: My top iOS 9 Bugs

Hi Alex,

I mean that, when I move my finger across the mic, I can hear it.  I also 
can't restart my book.  Also VO doesn't work.  That is a problem.

Thanks,
Lois

-Original Message- 
From: Alex Stone
Sent: Thursday, September 17, 2015 5:00 AM
To: viphone@googlegroups.com
Subject: RE: My top iOS 9 Bugs

Sorry, but what do you mean by "the microphone remains open", surely if the 
call has ended this wouldn't make any difference.

-Original Message-
From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf 
Of Lois Butterfield
Sent: 17 September 2015 09:53
To: viphone@googlegroups.com
Subject: Re: My top iOS 9 Bugs

What happens with my iPhone 6 is, when I get a call while earphones are 
plugged in, which is most of the time, everything is fine until I hang up 
the call.  That is when something funny happens.  The microphone remains 
open, and VO is dead.  I have to unplug and plug back in to resolve the 
issue.  Since it doesn’t effect the actual calls, I can live with it.

Once, I dropped the phone while plugged in, and I had sound both through the 
headphones and the speaker.  That went on until I closed phone in the app 
switcher.  That also had to do with a call ringing while listening to a 
book.  Crazy stuff, but I still like the update.

Lois

From: christopher hallsworth <mailto:challswor...@icloud.com>
Sent: Thursday, September 17, 2015 4:30 AM
To: Viphone <mailto:viphone@googlegroups.com>
Subject: Re: My top iOS 9 Bugs

It cannot be duplicated since it is not device specific nor is it situation 
specific.


On 17 Sep 2015, at 09:28, Jenifer Barr <claudas...@gmail.com 
<mailto:claudas...@gmail.com> > wrote:

Has anyone been able to duplicate point 1? That's my whole hesitation of 
updating because I constantly use earbuds.
Thanks.

Jenifer Barr
Sent from my iPhone

On Sep 16, 2015, at 1:15 PM, Jonathan Mosen <jmo...@mosen.org 
<mailto:jmo...@mosen.org> > wrote:



Hi everyone, now that the NDA is lifted, here are some things I think you 
might like to be aware of in iOS 9.
I am enthusiastic about iOS 9. It is significantly more responsive than its 
predecessor, and there are many new features that I'm sure you'll enjoy. 
Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
minor annoyances to potentially critical, depending on how you use your 
device and whether you find yourself affected. Here are just a few that you 
might like to take into consideration before deciding whether to wait for a 
bug fix release before installing iOS 9. Remember that a few days following 
iOS 9's release, it will not be possible to downgrade again, so you should 
consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
anything below concerns you.
1. Audio routing bug. This is potentially the most significant accessibility 
bug I can recall ever to slip through an iOS release, due to the number of 
people who may be affected. Not everyone will be, and at present, even after 
extensive testing w

Re: My top iOS 9 Bugs

[Robin]

Jonathan Mosen

I'm curious & I think others ON ThisList are also curious about your 
opinion as it pertains to iOS9


How do the PerceivedBugs and/or PerceivedFlaws CompareTo those that 
were present IN the ReleaseOf iOS8 ... I'm Referrin'To iOS9


Did Apple conduct a MoreEfficientBetaTesting ThisTimeOut
At 10:15 AM 9/16/2015, you wrote:
Hi everyone, now that the NDA is lifted, here are some things I 
think you might like to be aware of in iOS 9.
I am enthusiastic about iOS 9. It is significantly more responsive 
than its predecessor, and there are many new features that I'm sure 
you'll enjoy. Unfortunately, there are also some VoiceOver bugs in 
iOS 9 that range from minor annoyances to potentially critical, 
depending on how you use your device and whether you find yourself 
affected. Here are just a few that you might like to take into 
consideration before deciding whether to wait for a bug fix release 
before installing iOS 9. Remember that a few days following iOS 9's 
release, it will not be possible to downgrade again, so you should 
consider the upgrade to iOS 9 a one-way trip, and proceed with 
caution if anything below concerns you.
1. Audio routing bug. This is potentially the most significant 
accessibility bug I can recall ever to slip through an iOS release, 
due to the number of people who may be affected. Not everyone will 
be, and at present, even after extensive testing with a range of 
people owning different devices, I have no information about why it 
affects some users, but not others. It is not device specific, for 
example it is happening to me on my iPhone 6 Plus, but I know iPhone 
6 Plus users where the problem isn't so severe. Nor does it seem to 
be affected by any setting. If you're lucky, it won't happen to you, 
but the only way I am aware of to determine this is to upgrade.
This bug may affect you when you have earbuds or headphones 
connected to the headphone socket of your iPhone. The primary way 
the audio routing bug manifests itself is when you receive an 
incoming phone or FaceTime call. You can usually hear if you're 
going to be affected by the bug because your ring-tone will fade in 
and out, rather like the way VOiceOver causes system audio to fade 
in and out when audio ducking is enabled. At this point, if you 
press the power button to silence the ringer and then flick through 
the screen, you will find that not only has VOiceOver become 
unresponsive, but the entire phone has as well.
If you don't press the power button while the phone is ringing, but 
instead opt to flick through the iPHone's screen to locate the 
Answer button or review caller ID information, VoiceOver may not speak at all.
Finally, if you attempt to answer the incoming call with a 
two-finger double-tap, you may not be able to, since VoiceOver has 
effectively locked up.
The bottom line is that if you have earbuds connected, you may not 
be able to answer a call.
Some people have also reported similar problems answering calls when 
their phone is set to silent.
If you rely on your phone for business or safety, this could be a 
deal breaker in terms of upgrading at this point.
What makes this bug so fascinating is that not only is it completely 
absent for some people, but of those who experience it, not all 
symptoms are present for all users. For example, some people 
experience the issues I have described when they press the power 
button to mute the ringer, but not when the phone is ringing. Others 
can answer a call by pressing the button on their EarPods, while others cannot.

If you upgrade and are affected by this, here are a few things to try.
(A) If you have the more moderate version of this bug, avoid 
pressing the power button when you receive an incoming call.

(B) Turning off audio ducking seems to help a little for some users.
(C) If you can't answer a call with a two-finger double-tap, try 
pressing the button on your EarPods or similar device if you have 
such a device connected.
(D) If all else fails, you can disconnect any device from the 
headphone jack, answer the call with a two-finger double-tap, then 
reconnect the device to the headphone jack.
(E) Given the critical nature of this bug, if you've upgraded and 
now find yourself afflicted by it, enrol in the iOS beta program so 
you can receive early copies of any fixes Apple is working on. But 
keep in mind that since you will be running beta software, you may 
well be swapping one set of bugs for another.
2. Bluetooth keyboard support unreliable. Sometimes, users may input 
double letters when typing. This is a bug that was introduced in the 
iOS 8 cycle, and can easily be worked around by toggling VoiceOver off and on.
However, a new bug now exists where at times, no text is entered 
into a field at all when VO is active. Toggling VO doesn't help, nor 
does switching the keyboard off and on. The only immediate remedy is 
to turn Vo off, and keep typing without it. If you turn VO back on 
again, the arrow keys 

Re: My top iOS 9 Bugs

[christopher hallsworth]

It shouldn't. It seems to be for headsets only. Even then, they may only 
experience a mild form of this or not at all.
Chris
> On 17 Sep 2015, at 15:23, Russ Kiehne <russ94...@gmail.com> wrote:
> 
> Let me ask about: 1. Audio routing bug.  My brother has an iphone 6 and 
> doesn’t use earbuds or headphones.  Will this bug effect him?
>  
> From: Jonathan Mosen <mailto:jmo...@mosen.org>
> Sent: Wednesday, September 16, 2015 10:15 AM
> To: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
> Subject: My top iOS 9 Bugs
>  
> Hi everyone, now that the NDA is lifted, here are some things I think you 
> might like to be aware of in iOS 9.
> I am enthusiastic about iOS 9. It is significantly more responsive than its 
> predecessor, and there are many new features that I'm sure you'll enjoy. 
> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
> minor annoyances to potentially critical, depending on how you use your 
> device and whether you find yourself affected. Here are just a few that you 
> might like to take into consideration before deciding whether to wait for a 
> bug fix release before installing iOS 9. Remember that a few days following 
> iOS 9's release, it will not be possible to downgrade again, so you should 
> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
> anything below concerns you.
> 1. Audio routing bug. This is potentially the most significant accessibility 
> bug I can recall ever to slip through an iOS release, due to the number of 
> people who may be affected. Not everyone will be, and at present, even after 
> extensive testing with a range of people owning different devices, I have no 
> information about why it affects some users, but not others. It is not device 
> specific, for example it is happening to me on my iPhone 6 Plus, but I know 
> iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to be 
> affected by any setting. If you're lucky, it won't happen to you, but the 
> only way I am aware of to determine this is to upgrade.
> This bug may affect you when you have earbuds or headphones connected to the 
> headphone socket of your iPhone. The primary way the audio routing bug 
> manifests itself is when you receive an incoming phone or FaceTime call. You 
> can usually hear if you're going to be affected by the bug because your 
> ring-tone will fade in and out, rather like the way VOiceOver causes system 
> audio to fade in and out when audio ducking is enabled. At this point, if you 
> press the power button to silence the ringer and then flick through the 
> screen, you will find that not only has VOiceOver become unresponsive, but 
> the entire phone has as well.
> If you don't press the power button while the phone is ringing, but instead 
> opt to flick through the iPHone's screen to locate the Answer button or 
> review caller ID information, VoiceOver may not speak at all.
> Finally, if you attempt to answer the incoming call with a two-finger 
> double-tap, you may not be able to, since VoiceOver has effectively locked up.
> The bottom line is that if you have earbuds connected, you may not be able to 
> answer a call.
> Some people have also reported similar problems answering calls when their 
> phone is set to silent.
> If you rely on your phone for business or safety, this could be a deal 
> breaker in terms of upgrading at this point.
> What makes this bug so fascinating is that not only is it completely absent 
> for some people, but of those who experience it, not all symptoms are present 
> for all users. For example, some people experience the issues I have 
> described when they press the power button to mute the ringer, but not when 
> the phone is ringing. Others can answer a call by pressing the button on 
> their EarPods, while others cannot.
> If you upgrade and are affected by this, here are a few things to try.
> (A) If you have the more moderate version of this bug, avoid pressing the 
> power button when you receive an incoming call.
> (B) Turning off audio ducking seems to help a little for some users.
> (C) If you can't answer a call with a two-finger double-tap, try pressing the 
> button on your EarPods or similar device if you have such a device connected.
> (D) If all else fails, you can disconnect any device from the headphone jack, 
> answer the call with a two-finger double-tap, then reconnect the device to 
> the headphone jack.
> (E) Given the critical nature of this bug, if you've upgraded and now find 
> yourself afflicted by it, enrol in the iOS beta program so you can receive 
> early copies of any fixes Apple is working on. But keep in mind that since 
> you will be running beta software, you may well be swapping one se

Re: My top iOS 9 Bugs

[christopher hallsworth]

I'm not Jonathan, but it really looks that way to me. This is partly thanks to 
Apple making the beta cycle more open than ever before thanks to its public 
beta program.
> On 17 Sep 2015, at 20:46, Robin  wrote:
> 
> Jonathan Mosen
> 
> I'm curious & I think others ON ThisList are also curious about your opinion 
> as it pertains to iOS9
> 
> How do the PerceivedBugs and/or PerceivedFlaws CompareTo those that were 
> present IN the ReleaseOf iOS8 ... I'm Referrin'To iOS9
> 
> Did Apple conduct a MoreEfficientBetaTesting ThisTimeOut 
> At 10:15 AM 9/16/2015, you wrote:
>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>> might like to be aware of in iOS 9.
>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>> minor annoyances to potentially critical, depending on how you use your 
>> device and whether you find yourself affected. Here are just a few that you 
>> might like to take into consideration before deciding whether to wait for a 
>> bug fix release before installing iOS 9. Remember that a few days following 
>> iOS 9's release, it will not be possible to downgrade again, so you should 
>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>> anything below concerns you.
>> 1. Audio routing bug. This is potentially the most significant accessibility 
>> bug I can recall ever to slip through an iOS release, due to the number of 
>> people who may be affected. Not everyone will be, and at present, even after 
>> extensive testing with a range of people owning different devices, I have no 
>> information about why it affects some users, but not others. It is not 
>> device specific, for example it is happening to me on my iPhone 6 Plus, but 
>> I know iPhone 6 Plus users where the problem isn't so severe. Nor does it 
>> seem to be affected by any setting. If you're lucky, it won't happen to you, 
>> but the only way I am aware of to determine this is to upgrade.
>> This bug may affect you when you have earbuds or headphones connected to the 
>> headphone socket of your iPhone. The primary way the audio routing bug 
>> manifests itself is when you receive an incoming phone or FaceTime call. You 
>> can usually hear if you're going to be affected by the bug because your 
>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>> audio to fade in and out when audio ducking is enabled. At this point, if 
>> you press the power button to silence the ringer and then flick through the 
>> screen, you will find that not only has VOiceOver become unresponsive, but 
>> the entire phone has as well.
>> If you don't press the power button while the phone is ringing, but instead 
>> opt to flick through the iPHone's screen to locate the Answer button or 
>> review caller ID information, VoiceOver may not speak at all.
>> Finally, if you attempt to answer the incoming call with a two-finger 
>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>> up.
>> The bottom line is that if you have earbuds connected, you may not be able 
>> to answer a call.
>> Some people have also reported similar problems answering calls when their 
>> phone is set to silent.
>> If you rely on your phone for business or safety, this could be a deal 
>> breaker in terms of upgrading at this point.
>> What makes this bug so fascinating is that not only is it completely absent 
>> for some people, but of those who experience it, not all symptoms are 
>> present for all users. For example, some people experience the issues I have 
>> described when they press the power button to mute the ringer, but not when 
>> the phone is ringing. Others can answer a call by pressing the button on 
>> their EarPods, while others cannot.
>> If you upgrade and are affected by this, here are a few things to try.
>> (A) If you have the more moderate version of this bug, avoid pressing the 
>> power button when you receive an incoming call.
>> (B) Turning off audio ducking seems to help a little for some users.
>> (C) If you can't answer a call with a two-finger double-tap, try pressing 
>> the button on your EarPods or similar device if you have such a device 
>> connected.
>> (D) If all else fails, you can disconnect any device from the headphone 
>> jack, answer the call with a two-finger double-tap, then reconnect the 
>> device to the headphone jack.
>> (E) Given the critical nature of this bug, if you've upgraded and now find 
>> yourself afflicted by it, enrol in the iOS beta program so you can receive 
>> early copies of any fixes Apple is working on. But keep in mind that since 
>> you will be running beta software, you may well be swapping one set of bugs 
>> for another.
>> 2. Bluetooth keyboard support unreliable. Sometimes, users may input 

Re: My top iOS 9 Bugs

[Chris Chaffin]

Does this bug come up when using a bluetooth headset instead of a plug in 
headset?
I have only read where people had a plug in headset.

Thanks,

Chris




> On Sep 17, 2015, at 3:13 PM, christopher hallsworth <challswor...@icloud.com> 
> wrote:
> 
> It shouldn't. It seems to be for headsets only. Even then, they may only 
> experience a mild form of this or not at all.
> Chris
>> On 17 Sep 2015, at 15:23, Russ Kiehne <russ94...@gmail.com> wrote:
>> 
>> Let me ask about: 1. Audio routing bug.  My brother has an iphone 6 and 
>> doesn’t use earbuds or headphones.  Will this bug effect him?
>>  
>> From: Jonathan Mosen
>> Sent: Wednesday, September 16, 2015 10:15 AM
>> To: viphone@googlegroups.com
>> Subject: My top iOS 9 Bugs
>>  
>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>> might like to be aware of in iOS 9.
>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>> minor annoyances to potentially critical, depending on how you use your 
>> device and whether you find yourself affected. Here are just a few that you 
>> might like to take into consideration before deciding whether to wait for a 
>> bug fix release before installing iOS 9. Remember that a few days following 
>> iOS 9's release, it will not be possible to downgrade again, so you should 
>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>> anything below concerns you.
>> 1. Audio routing bug. This is potentially the most significant accessibility 
>> bug I can recall ever to slip through an iOS release, due to the number of 
>> people who may be affected. Not everyone will be, and at present, even after 
>> extensive testing with a range of people owning different devices, I have no 
>> information about why it affects some users, but not others. It is not 
>> device specific, for example it is happening to me on my iPhone 6 Plus, but 
>> I know iPhone 6 Plus users where the problem isn't so severe. Nor does it 
>> seem to be affected by any setting. If you're lucky, it won't happen to you, 
>> but the only way I am aware of to determine this is to upgrade.
>> This bug may affect you when you have earbuds or headphones connected to the 
>> headphone socket of your iPhone. The primary way the audio routing bug 
>> manifests itself is when you receive an incoming phone or FaceTime call. You 
>> can usually hear if you're going to be affected by the bug because your 
>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>> audio to fade in and out when audio ducking is enabled. At this point, if 
>> you press the power button to silence the ringer and then flick through the 
>> screen, you will find that not only has VOiceOver become unresponsive, but 
>> the entire phone has as well.
>> If you don't press the power button while the phone is ringing, but instead 
>> opt to flick through the iPHone's screen to locate the Answer button or 
>> review caller ID information, VoiceOver may not speak at all.
>> Finally, if you attempt to answer the incoming call with a two-finger 
>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>> up.
>> The bottom line is that if you have earbuds connected, you may not be able 
>> to answer a call.
>> Some people have also reported similar problems answering calls when their 
>> phone is set to silent.
>> If you rely on your phone for business or safety, this could be a deal 
>> breaker in terms of upgrading at this point.
>> What makes this bug so fascinating is that not only is it completely absent 
>> for some people, but of those who experience it, not all symptoms are 
>> present for all users. For example, some people experience the issues I have 
>> described when they press the power button to mute the ringer, but not when 
>> the phone is ringing. Others can answer a call by pressing the button on 
>> their EarPods, while others cannot.
>> If you upgrade and are affected by this, here are a few things to try.
>> (A) If you have the more moderate version of this bug, avoid pressing the 
>> power button when you receive an incoming call.
>> (B) Turning off audio ducking seems to help a little for some users.
>> (C) If you can't answer a call with a two-finger double-tap, try pressing 
>> the button on your EarPods or similar device if you have such a device 
>> connected.
>> (D) If all else fai

Re: My top iOS 9 Bugs

[Mike Arrigo]

In general, I think it's always good to wait until at least the first 
major update, sometimes the second of any new operating system so the 
major bugs can get worked out. Upgrading to a new version of an 
operating system as soon as it's released is far too risky.

Original message:
Hi everyone, now that the NDA is lifted, here are some things I think 
you might like to be aware of in iOS 9.
I am enthusiastic about iOS 9. It is significantly more responsive than 
its predecessor, and there are many new features that I'm sure you'll 
enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 9 that 
range from minor annoyances to potentially critical, depending on how 
you use your device and whether you find yourself affected. Here are 
just a few that you might like to take into consideration before 
deciding whether to wait for a bug fix release before installing iOS 9. 
Remember that a few days following iOS 9's release, it will not be 
possible to downgrade again, so you should consider the upgrade to iOS 
9 a one-way trip, and proceed with caution if anything below concerns you.
1. Audio routing bug. This is potentially the most significant 
accessibility bug I can recall ever to slip through an iOS release, due 
to the number of people who may be affected. Not everyone will be, and 
at present, even after extensive testing with a range of people owning 
different devices, I have no information about why it affects some 
users, but not others. It is not device specific, for example it is 
happening to me on my iPhone 6 Plus, but I know iPhone 6 Plus users 
where the problem isn't so severe. Nor does it seem to be affected by 
any setting. If you're lucky, it won't happen to you, but the only way 
I am aware of to determine this is to upgrade.
This bug may affect you when you have earbuds or headphones connected 
to the headphone socket of your iPhone. The primary way the audio 
routing bug manifests itself is when you receive an incoming phone or 
FaceTime call. You can usually hear if you're going to be affected by 
the bug because your ring-tone will fade in and out, rather like the 
way VOiceOver causes system audio to fade in and out when audio ducking 
is enabled. At this point, if you press the power button to silence the 
ringer and then flick through the screen, you will find that not only 
has VOiceOver become unresponsive, but the entire phone has as well.
If you don't press the power button while the phone is ringing, but 
instead opt to flick through the iPHone's screen to locate the Answer 
button or review caller ID information, VoiceOver may not speak at all.
Finally, if you attempt to answer the incoming call with a two-finger 
double-tap, you may not be able to, since VoiceOver has effectively locked up.
The bottom line is that if you have earbuds connected, you may not be 
able to answer a call.
Some people have also reported similar problems answering calls when 
their phone is set to silent.
If you rely on your phone for business or safety, this could be a deal 
breaker in terms of upgrading at this point.
What makes this bug so fascinating is that not only is it completely 
absent for some people, but of those who experience it, not all 
symptoms are present for all users. For example, some people experience 
the issues I have described when they press the power button to mute 
the ringer, but not when the phone is ringing. Others can answer a call 
by pressing the button on their EarPods, while others cannot.

If you upgrade and are affected by this, here are a few things to try.
(A) If you have the more moderate version of this bug, avoid pressing 
the power button when you receive an incoming call.

(B) Turning off audio ducking seems to help a little for some users.
(C) If you can't answer a call with a two-finger double-tap, try 
pressing the button on your EarPods or similar device if you have such 
a device connected.
(D) If all else fails, you can disconnect any device from the headphone 
jack, answer the call with a two-finger double-tap, then reconnect the 
device to the headphone jack.
(E) Given the critical nature of this bug, if you've upgraded and now 
find yourself afflicted by it, enrol in the iOS beta program so you can 
receive early copies of any fixes Apple is working on. But keep in mind 
that since you will be running beta software, you may well be swapping 
one set of bugs for another.
2. Bluetooth keyboard support unreliable. Sometimes, users may input 
double letters when typing. This is a bug that was introduced in the 
iOS 8 cycle, and can easily be worked around by toggling VoiceOver off and on.
However, a new bug now exists where at times, no text is entered into a 
field at all when VO is active. Toggling VO doesn't help, nor does 
switching the keyboard off and on. The only immediate remedy is to turn 
Vo off, and keep typing without it. If you turn VO back on again, the 
arrow keys don't work when you're trying to navigate your text, and you 

Re: My top iOS 9 Bugs

[Harry Bell]

Also in ios 9 Speak Screen (invoked by two finger swipe down from top of 
screen) is so fast that it sounds like gibberish. I have reported this to Apple 
with every beat version but it still hasn't been fixed. Harry

 

> On 16 Sep 2015, at 18:15, Jonathan Mosen  wrote:
> 
> Hi everyone, now that the NDA is lifted, here are some things I think you 
> might like to be aware of in iOS 9.
> I am enthusiastic about iOS 9. It is significantly more responsive than its 
> predecessor, and there are many new features that I'm sure you'll enjoy. 
> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
> minor annoyances to potentially critical, depending on how you use your 
> device and whether you find yourself affected. Here are just a few that you 
> might like to take into consideration before deciding whether to wait for a 
> bug fix release before installing iOS 9. Remember that a few days following 
> iOS 9's release, it will not be possible to downgrade again, so you should 
> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
> anything below concerns you.
> 1. Audio routing bug. This is potentially the most significant accessibility 
> bug I can recall ever to slip through an iOS release, due to the number of 
> people who may be affected. Not everyone will be, and at present, even after 
> extensive testing with a range of people owning different devices, I have no 
> information about why it affects some users, but not others. It is not device 
> specific, for example it is happening to me on my iPhone 6 Plus, but I know 
> iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to be 
> affected by any setting. If you're lucky, it won't happen to you, but the 
> only way I am aware of to determine this is to upgrade.
> This bug may affect you when you have earbuds or headphones connected to the 
> headphone socket of your iPhone. The primary way the audio routing bug 
> manifests itself is when you receive an incoming phone or FaceTime call. You 
> can usually hear if you're going to be affected by the bug because your 
> ring-tone will fade in and out, rather like the way VOiceOver causes system 
> audio to fade in and out when audio ducking is enabled. At this point, if you 
> press the power button to silence the ringer and then flick through the 
> screen, you will find that not only has VOiceOver become unresponsive, but 
> the entire phone has as well.
> If you don't press the power button while the phone is ringing, but instead 
> opt to flick through the iPHone's screen to locate the Answer button or 
> review caller ID information, VoiceOver may not speak at all.
> Finally, if you attempt to answer the incoming call with a two-finger 
> double-tap, you may not be able to, since VoiceOver has effectively locked up.
> The bottom line is that if you have earbuds connected, you may not be able to 
> answer a call.
> Some people have also reported similar problems answering calls when their 
> phone is set to silent.
> If you rely on your phone for business or safety, this could be a deal 
> breaker in terms of upgrading at this point.
> What makes this bug so fascinating is that not only is it completely absent 
> for some people, but of those who experience it, not all symptoms are present 
> for all users. For example, some people experience the issues I have 
> described when they press the power button to mute the ringer, but not when 
> the phone is ringing. Others can answer a call by pressing the button on 
> their EarPods, while others cannot.
> If you upgrade and are affected by this, here are a few things to try.
> (A) If you have the more moderate version of this bug, avoid pressing the 
> power button when you receive an incoming call.
> (B) Turning off audio ducking seems to help a little for some users.
> (C) If you can't answer a call with a two-finger double-tap, try pressing the 
> button on your EarPods or similar device if you have such a device connected.
> (D) If all else fails, you can disconnect any device from the headphone jack, 
> answer the call with a two-finger double-tap, then reconnect the device to 
> the headphone jack.
> (E) Given the critical nature of this bug, if you've upgraded and now find 
> yourself afflicted by it, enrol in the iOS beta program so you can receive 
> early copies of any fixes Apple is working on. But keep in mind that since 
> you will be running beta software, you may well be swapping one set of bugs 
> for another.
> 2. Bluetooth keyboard support unreliable. Sometimes, users may input double 
> letters when typing. This is a bug that was introduced in the iOS 8 cycle, 
> and can easily be worked around by toggling VoiceOver off and on.
> However, a new bug now exists where at times, no text is entered into a field 
> at all when VO is active. Toggling VO doesn't help, nor does switching the 
> keyboard off and on. The only immediate remedy is to turn Vo 

Re: My top iOS 9 Bugs

[John Diakogeorgiou]

Jonathan thanks for the bug report. I can confirm point 4. It is very
frustrating when I am trying to make a call and it always goes to the
top of my contact list. I have not tried using ear buds. I will say
though that I haven't had any problems using a Bluetooth ear piece. I
am able to answer calls just fine.
In general the new software is much better than version 8.

On 9/16/15, Nancy Feldman <lorav...@gmail.com> wrote:
> For what it's worth, I've successfully upgraded and received three phone
> calls. None of them has resulted in unusual or unstable behavior from the
> phone and I was able to answer it from the earbuds and from the screen.
>
> I appreciate being made aware of the possibility, but I opted to take my
> chances, and have no concerns so far.
>
>> On Sep 16, 2015, at 11:52, Jenifer Barr <claudas...@gmail.com> wrote:
>>
>> Wow Jonathan!!! Thanks for the list. While I gladly bought your book...
>> I'll wait for the next version hopefully in a week or so!!
>>
>> Jenifer Barr
>> Sent from my iPhone
>>
>> On Sep 16, 2015, at 1:33 PM, Cristóbal <crismuno...@gmail.com
>> <mailto:crismuno...@gmail.com>> wrote:
>>
>>> Geez. So I think I’m going to wait for the first 9.x update. Significatn
>>> bugs for sure.
>>>
>>> From: viphone@googlegroups.com
>>> <mailto:viphone@googlegroups.com>[mailto:viphone@googlegroups.com
>>> <mailto:viphone@googlegroups.com>] On Behalf Of Jonathan Mosen
>>> Sent: Wednesday, September 16, 2015 10:15 AM
>>> To: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>>> Subject: My top iOS 9 Bugs
>>>
>>> Hi everyone, now that the NDA is lifted, here are some things I think you
>>> might like to be aware of in iOS 9.
>>> I am enthusiastic about iOS 9. It is significantly more responsive than
>>> its predecessor, and there are many new features that I'm sure you'll
>>> enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 9 that
>>> range from minor annoyances to potentially critical, depending on how you
>>> use your device and whether you find yourself affected. Here are just a
>>> few that you might like to take into consideration before deciding
>>> whether to wait for a bug fix release before installing iOS 9. Remember
>>> that a few days following iOS 9's release, it will not be possible to
>>> downgrade again, so you should consider the upgrade to iOS 9 a one-way
>>> trip, and proceed with caution if anything below concerns you.
>>> 1. Audio routing bug. This is potentially the most significant
>>> accessibility bug I can recall ever to slip through an iOS release, due
>>> to the number of people who may be affected. Not everyone will be, and at
>>> present, even after extensive testing with a range of people owning
>>> different devices, I have no information about why it affects some users,
>>> but not others. It is not device specific, for example it is happening to
>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem
>>> isn't so severe. Nor does it seem to be affected by any setting. If
>>> you're lucky, it won't happen to you, but the only way I am aware of to
>>> determine this is to upgrade.
>>> This bug may affect you when you have earbuds or headphones connected to
>>> the headphone socket of your iPhone. The primary way the audio routing
>>> bug manifests itself is when you receive an incoming phone or FaceTime
>>> call. You can usually hear if you're going to be affected by the bug
>>> because your ring-tone will fade in and out, rather like the way
>>> VOiceOver causes system audio to fade in and out when audio ducking is
>>> enabled. At this point, if you press the power button to silence the
>>> ringer and then flick through the screen, you will find that not only has
>>> VOiceOver become unresponsive, but the entire phone has as well.
>>> If you don't press the power button while the phone is ringing, but
>>> instead opt to flick through the iPHone's screen to locate the Answer
>>> button or review caller ID information, VoiceOver may not speak at all.
>>> Finally, if you attempt to answer the incoming call with a two-finger
>>> double-tap, you may not be able to, since VoiceOver has effectively
>>> locked up.
>>> The bottom line is that if you have earbuds connected, you may not be
>>> able to answer a call.
>>> Some people have also reported similar problems answering calls when
>>> their phone is set to silent.
>>> If y

Re: My top iOS 9 Bugs

[Harry Bell]

Speak Screen has the chipmunks for sure in ios 9! Harry

 

> On 16 Sep 2015, at 19:55, Brent Harding <br...@hostany.net> wrote:
> 
> I tested the beta on the old 4S that I don't have active service on. Did they 
> fix the bug that would sometimes make streaming audio sound like the 
> chipmunks? I was playing Tunein radio on it at the time of that first public 
> beta, and VO and everything started playing fast with the high pitch and so 
> did the airplay from Tunein. I thought I read on Twitter awhile ago that 
> someone said that phone calls would get the chipmunks too.
>  
>  
> - Original Message -
> From: Cristóbal
> To: viphone@googlegroups.com
> Sent: Wednesday, September 16, 2015 12:33 PM
> Subject: RE: My top iOS 9 Bugs
> 
> Geez. So I think I’m going to wait for the first 9.x update. Significatn bugs 
> for sure. 
>  
> From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf Of 
> Jonathan Mosen
> Sent: Wednesday, September 16, 2015 10:15 AM
> To: viphone@googlegroups.com
> Subject: My top iOS 9 Bugs
>  
> Hi everyone, now that the NDA is lifted, here are some things I think you 
> might like to be aware of in iOS 9.
> I am enthusiastic about iOS 9. It is significantly more responsive than its 
> predecessor, and there are many new features that I'm sure you'll enjoy. 
> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
> minor annoyances to potentially critical, depending on how you use your 
> device and whether you find yourself affected. Here are just a few that you 
> might like to take into consideration before deciding whether to wait for a 
> bug fix release before installing iOS 9. Remember that a few days following 
> iOS 9's release, it will not be possible to downgrade again, so you should 
> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
> anything below concerns you.
> 1. Audio routing bug. This is potentially the most significant accessibility 
> bug I can recall ever to slip through an iOS release, due to the number of 
> people who may be affected. Not everyone will be, and at present, even after 
> extensive testing with a range of people owning different devices, I have no 
> information about why it affects some users, but not others. It is not device 
> specific, for example it is happening to me on my iPhone 6 Plus, but I know 
> iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to be 
> affected by any setting. If you're lucky, it won't happen to you, but the 
> only way I am aware of to determine this is to upgrade.
> This bug may affect you when you have earbuds or headphones connected to the 
> headphone socket of your iPhone. The primary way the audio routing bug 
> manifests itself is when you receive an incoming phone or FaceTime call. You 
> can usually hear if you're going to be affected by the bug because your 
> ring-tone will fade in and out, rather like the way VOiceOver causes system 
> audio to fade in and out when audio ducking is enabled. At this point, if you 
> press the power button to silence the ringer and then flick through the 
> screen, you will find that not only has VOiceOver become unresponsive, but 
> the entire phone has as well.
> If you don't press the power button while the phone is ringing, but instead 
> opt to flick through the iPHone's screen to locate the Answer button or 
> review caller ID information, VoiceOver may not speak at all.
> Finally, if you attempt to answer the incoming call with a two-finger 
> double-tap, you may not be able to, since VoiceOver has effectively locked up.
> The bottom line is that if you have earbuds connected, you may not be able to 
> answer a call.
> Some people have also reported similar problems answering calls when their 
> phone is set to silent.
> If you rely on your phone for business or safety, this could be a deal 
> breaker in terms of upgrading at this point.
> What makes this bug so fascinating is that not only is it completely absent 
> for some people, but of those who experience it, not all symptoms are present 
> for all users. For example, some people experience the issues I have 
> described when they press the power button to mute the ringer, but not when 
> the phone is ringing. Others can answer a call by pressing the button on 
> their EarPods, while others cannot.
> If you upgrade and are affected by this, here are a few things to try.
> (A) If you have the more moderate version of this bug, avoid pressing the 
> power button when you receive an incoming call.
> (B) Turning off audio ducking seems to help a little for some users.
> (C) If you can't answer a call with a two-finger double-tap, try pressing the 
> button on your EarPods or simi

Re: My top iOS 9 Bugs

[Jenifer Barr]

Wow Jonathan!!! Thanks for the list. While I gladly bought your book... I'll 
wait for the next version hopefully in a week or so!! 

Jenifer Barr
Sent from my iPhone

> On Sep 16, 2015, at 1:33 PM, Cristóbal <crismuno...@gmail.com> wrote:
> 
> Geez. So I think I’m going to wait for the first 9.x update. Significatn bugs 
> for sure.
>  
> From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf Of 
> Jonathan Mosen
> Sent: Wednesday, September 16, 2015 10:15 AM
> To: viphone@googlegroups.com
> Subject: My top iOS 9 Bugs
>  
> Hi everyone, now that the NDA is lifted, here are some things I think you 
> might like to be aware of in iOS 9.
> I am enthusiastic about iOS 9. It is significantly more responsive than its 
> predecessor, and there are many new features that I'm sure you'll enjoy. 
> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
> minor annoyances to potentially critical, depending on how you use your 
> device and whether you find yourself affected. Here are just a few that you 
> might like to take into consideration before deciding whether to wait for a 
> bug fix release before installing iOS 9. Remember that a few days following 
> iOS 9's release, it will not be possible to downgrade again, so you should 
> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
> anything below concerns you.
> 1. Audio routing bug. This is potentially the most significant accessibility 
> bug I can recall ever to slip through an iOS release, due to the number of 
> people who may be affected. Not everyone will be, and at present, even after 
> extensive testing with a range of people owning different devices, I have no 
> information about why it affects some users, but not others. It is not device 
> specific, for example it is happening to me on my iPhone 6 Plus, but I know 
> iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to be 
> affected by any setting. If you're lucky, it won't happen to you, but the 
> only way I am aware of to determine this is to upgrade.
> This bug may affect you when you have earbuds or headphones connected to the 
> headphone socket of your iPhone. The primary way the audio routing bug 
> manifests itself is when you receive an incoming phone or FaceTime call. You 
> can usually hear if you're going to be affected by the bug because your 
> ring-tone will fade in and out, rather like the way VOiceOver causes system 
> audio to fade in and out when audio ducking is enabled. At this point, if you 
> press the power button to silence the ringer and then flick through the 
> screen, you will find that not only has VOiceOver become unresponsive, but 
> the entire phone has as well.
> If you don't press the power button while the phone is ringing, but instead 
> opt to flick through the iPHone's screen to locate the Answer button or 
> review caller ID information, VoiceOver may not speak at all.
> Finally, if you attempt to answer the incoming call with a two-finger 
> double-tap, you may not be able to, since VoiceOver has effectively locked up.
> The bottom line is that if you have earbuds connected, you may not be able to 
> answer a call.
> Some people have also reported similar problems answering calls when their 
> phone is set to silent.
> If you rely on your phone for business or safety, this could be a deal 
> breaker in terms of upgrading at this point.
> What makes this bug so fascinating is that not only is it completely absent 
> for some people, but of those who experience it, not all symptoms are present 
> for all users. For example, some people experience the issues I have 
> described when they press the power button to mute the ringer, but not when 
> the phone is ringing. Others can answer a call by pressing the button on 
> their EarPods, while others cannot.
> If you upgrade and are affected by this, here are a few things to try.
> (A) If you have the more moderate version of this bug, avoid pressing the 
> power button when you receive an incoming call.
> (B) Turning off audio ducking seems to help a little for some users.
> (C) If you can't answer a call with a two-finger double-tap, try pressing the 
> button on your EarPods or similar device if you have such a device connected.
> (D) If all else fails, you can disconnect any device from the headphone jack, 
> answer the call with a two-finger double-tap, then reconnect the device to 
> the headphone jack.
> (E) Given the critical nature of this bug, if you've upgraded and now find 
> yourself afflicted by it, enrol in the iOS beta program so you can receive 
> early copies of any fixes Apple is working on. But keep in mind that since 
> you will be running beta software, you may well be swapping one

Re: My top iOS 9 Bugs

[Melissa Tucker]

does ios9 give any problems for people using a braille display?



On Sep 16, 2015, at 3:15 PM, Krister Ekstrom  wrote:

I always religiously update to the latest version of an Os when it comes out, 
if it works it does, if not… well shrug.
/Krister

> 16 sep. 2015 kl. 20:02 skrev Mike Arrigo :
> 
> In general, I think it's always good to wait until at least the first major 
> update, sometimes the second of any new operating system so the major bugs 
> can get worked out. Upgrading to a new version of an operating system as soon 
> as it's released is far too risky.
> Original message:
>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>> might like to be aware of in iOS 9.
>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>> minor annoyances to potentially critical, depending on how you use your 
>> device and whether you find yourself affected. Here are just a few that you 
>> might like to take into consideration before deciding whether to wait for a 
>> bug fix release before installing iOS 9. Remember that a few days following 
>> iOS 9's release, it will not be possible to downgrade again, so you should 
>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>> anything below concerns you.
>> 1. Audio routing bug. This is potentially the most significant accessibility 
>> bug I can recall ever to slip through an iOS release, due to the number of 
>> people who may be affected. Not everyone will be, and at present, even after 
>> extensive testing with a range of people owning different devices, I have no 
>> information about why it affects some users, but not others. It is not 
>> device specific, for example it is happening to me on my iPhone 6 Plus, but 
>> I know iPhone 6 Plus users where the problem isn't so severe. Nor does it 
>> seem to be affected by any setting. If you're lucky, it won't happen to you, 
>> but the only way I am aware of to determine this is to upgrade.
>> This bug may affect you when you have earbuds or headphones connected to the 
>> headphone socket of your iPhone. The primary way the audio routing bug 
>> manifests itself is when you receive an incoming phone or FaceTime call. You 
>> can usually hear if you're going to be affected by the bug because your 
>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>> audio to fade in and out when audio ducking is enabled. At this point, if 
>> you press the power button to silence the ringer and then flick through the 
>> screen, you will find that not only has VOiceOver become unresponsive, but 
>> the entire phone has as well.
>> If you don't press the power button while the phone is ringing, but instead 
>> opt to flick through the iPHone's screen to locate the Answer button or 
>> review caller ID information, VoiceOver may not speak at all.
>> Finally, if you attempt to answer the incoming call with a two-finger 
>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>> up.
>> The bottom line is that if you have earbuds connected, you may not be able 
>> to answer a call.
>> Some people have also reported similar problems answering calls when their 
>> phone is set to silent.
>> If you rely on your phone for business or safety, this could be a deal 
>> breaker in terms of upgrading at this point.
>> What makes this bug so fascinating is that not only is it completely absent 
>> for some people, but of those who experience it, not all symptoms are 
>> present for all users. For example, some people experience the issues I have 
>> described when they press the power button to mute the ringer, but not when 
>> the phone is ringing. Others can answer a call by pressing the button on 
>> their EarPods, while others cannot.
>> If you upgrade and are affected by this, here are a few things to try.
>> (A) If you have the more moderate version of this bug, avoid pressing the 
>> power button when you receive an incoming call.
>> (B) Turning off audio ducking seems to help a little for some users.
>> (C) If you can't answer a call with a two-finger double-tap, try pressing 
>> the button on your EarPods or similar device if you have such a device 
>> connected.
>> (D) If all else fails, you can disconnect any device from the headphone 
>> jack, answer the call with a two-finger double-tap, then reconnect the 
>> device to the headphone jack.
>> (E) Given the critical nature of this bug, if you've upgraded and now find 
>> yourself afflicted by it, enrol in the iOS beta program so you can receive 
>> early copies of any fixes Apple is working on. But keep in mind that since 
>> you will be running beta software, you may well be swapping one set of bugs 
>> for another.
>> 2. Bluetooth keyboard support 

Re: My top iOS 9 Bugs

[Krister Ekstrom]

I always religiously update to the latest version of an Os when it comes out, 
if it works it does, if not… well shrug.
/Krister

> 16 sep. 2015 kl. 20:02 skrev Mike Arrigo :
> 
> In general, I think it's always good to wait until at least the first major 
> update, sometimes the second of any new operating system so the major bugs 
> can get worked out. Upgrading to a new version of an operating system as soon 
> as it's released is far too risky.
> Original message:
>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>> might like to be aware of in iOS 9.
>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>> minor annoyances to potentially critical, depending on how you use your 
>> device and whether you find yourself affected. Here are just a few that you 
>> might like to take into consideration before deciding whether to wait for a 
>> bug fix release before installing iOS 9. Remember that a few days following 
>> iOS 9's release, it will not be possible to downgrade again, so you should 
>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>> anything below concerns you.
>> 1. Audio routing bug. This is potentially the most significant accessibility 
>> bug I can recall ever to slip through an iOS release, due to the number of 
>> people who may be affected. Not everyone will be, and at present, even after 
>> extensive testing with a range of people owning different devices, I have no 
>> information about why it affects some users, but not others. It is not 
>> device specific, for example it is happening to me on my iPhone 6 Plus, but 
>> I know iPhone 6 Plus users where the problem isn't so severe. Nor does it 
>> seem to be affected by any setting. If you're lucky, it won't happen to you, 
>> but the only way I am aware of to determine this is to upgrade.
>> This bug may affect you when you have earbuds or headphones connected to the 
>> headphone socket of your iPhone. The primary way the audio routing bug 
>> manifests itself is when you receive an incoming phone or FaceTime call. You 
>> can usually hear if you're going to be affected by the bug because your 
>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>> audio to fade in and out when audio ducking is enabled. At this point, if 
>> you press the power button to silence the ringer and then flick through the 
>> screen, you will find that not only has VOiceOver become unresponsive, but 
>> the entire phone has as well.
>> If you don't press the power button while the phone is ringing, but instead 
>> opt to flick through the iPHone's screen to locate the Answer button or 
>> review caller ID information, VoiceOver may not speak at all.
>> Finally, if you attempt to answer the incoming call with a two-finger 
>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>> up.
>> The bottom line is that if you have earbuds connected, you may not be able 
>> to answer a call.
>> Some people have also reported similar problems answering calls when their 
>> phone is set to silent.
>> If you rely on your phone for business or safety, this could be a deal 
>> breaker in terms of upgrading at this point.
>> What makes this bug so fascinating is that not only is it completely absent 
>> for some people, but of those who experience it, not all symptoms are 
>> present for all users. For example, some people experience the issues I have 
>> described when they press the power button to mute the ringer, but not when 
>> the phone is ringing. Others can answer a call by pressing the button on 
>> their EarPods, while others cannot.
>> If you upgrade and are affected by this, here are a few things to try.
>> (A) If you have the more moderate version of this bug, avoid pressing the 
>> power button when you receive an incoming call.
>> (B) Turning off audio ducking seems to help a little for some users.
>> (C) If you can't answer a call with a two-finger double-tap, try pressing 
>> the button on your EarPods or similar device if you have such a device 
>> connected.
>> (D) If all else fails, you can disconnect any device from the headphone 
>> jack, answer the call with a two-finger double-tap, then reconnect the 
>> device to the headphone jack.
>> (E) Given the critical nature of this bug, if you've upgraded and now find 
>> yourself afflicted by it, enrol in the iOS beta program so you can receive 
>> early copies of any fixes Apple is working on. But keep in mind that since 
>> you will be running beta software, you may well be swapping one set of bugs 
>> for another.
>> 2. Bluetooth keyboard support unreliable. Sometimes, users may input double 
>> letters when typing. This is a bug that was introduced in the iOS 8 cycle, 
>> and can easily be 

Re: My top iOS 9 Bugs

[Brent Harding]

I tested the beta on the old 4S that I don't have active service on. Did they 
fix the bug that would sometimes make streaming audio sound like the chipmunks? 
I was playing Tunein radio on it at the time of that first public beta, and VO 
and everything started playing fast with the high pitch and so did the airplay 
from Tunein. I thought I read on Twitter awhile ago that someone said that 
phone calls would get the chipmunks too.


  - Original Message - 
  From: Cristóbal 
  To: viphone@googlegroups.com 
  Sent: Wednesday, September 16, 2015 12:33 PM
  Subject: RE: My top iOS 9 Bugs


  Geez. So I think I’m going to wait for the first 9.x update. Significatn bugs 
for sure. 

   

  From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf Of 
Jonathan Mosen
  Sent: Wednesday, September 16, 2015 10:15 AM
  To: viphone@googlegroups.com
  Subject: My top iOS 9 Bugs

   

  Hi everyone, now that the NDA is lifted, here are some things I think you 
might like to be aware of in iOS 9.

  I am enthusiastic about iOS 9. It is significantly more responsive than its 
predecessor, and there are many new features that I'm sure you'll enjoy. 
Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
minor annoyances to potentially critical, depending on how you use your device 
and whether you find yourself affected. Here are just a few that you might like 
to take into consideration before deciding whether to wait for a bug fix 
release before installing iOS 9. Remember that a few days following iOS 9's 
release, it will not be possible to downgrade again, so you should consider the 
upgrade to iOS 9 a one-way trip, and proceed with caution if anything below 
concerns you.

  1. Audio routing bug. This is potentially the most significant accessibility 
bug I can recall ever to slip through an iOS release, due to the number of 
people who may be affected. Not everyone will be, and at present, even after 
extensive testing with a range of people owning different devices, I have no 
information about why it affects some users, but not others. It is not device 
specific, for example it is happening to me on my iPhone 6 Plus, but I know 
iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to be 
affected by any setting. If you're lucky, it won't happen to you, but the only 
way I am aware of to determine this is to upgrade.

  This bug may affect you when you have earbuds or headphones connected to the 
headphone socket of your iPhone. The primary way the audio routing bug 
manifests itself is when you receive an incoming phone or FaceTime call. You 
can usually hear if you're going to be affected by the bug because your 
ring-tone will fade in and out, rather like the way VOiceOver causes system 
audio to fade in and out when audio ducking is enabled. At this point, if you 
press the power button to silence the ringer and then flick through the screen, 
you will find that not only has VOiceOver become unresponsive, but the entire 
phone has as well.

  If you don't press the power button while the phone is ringing, but instead 
opt to flick through the iPHone's screen to locate the Answer button or review 
caller ID information, VoiceOver may not speak at all.

  Finally, if you attempt to answer the incoming call with a two-finger 
double-tap, you may not be able to, since VoiceOver has effectively locked up.

  The bottom line is that if you have earbuds connected, you may not be able to 
answer a call.

  Some people have also reported similar problems answering calls when their 
phone is set to silent.

  If you rely on your phone for business or safety, this could be a deal 
breaker in terms of upgrading at this point.

  What makes this bug so fascinating is that not only is it completely absent 
for some people, but of those who experience it, not all symptoms are present 
for all users. For example, some people experience the issues I have described 
when they press the power button to mute the ringer, but not when the phone is 
ringing. Others can answer a call by pressing the button on their EarPods, 
while others cannot.

  If you upgrade and are affected by this, here are a few things to try.

  (A) If you have the more moderate version of this bug, avoid pressing the 
power button when you receive an incoming call.

  (B) Turning off audio ducking seems to help a little for some users.

  (C) If you can't answer a call with a two-finger double-tap, try pressing the 
button on your EarPods or similar device if you have such a device connected.

  (D) If all else fails, you can disconnect any device from the headphone jack, 
answer the call with a two-finger double-tap, then reconnect the device to the 
headphone jack.

  (E) Given the critical nature of this bug, if you've upgraded and now find 
yourself afflicted by it, enrol in the iOS beta program so you can receive 
early copies of any fixes Apple is working on. But keep in mind

Re: My top iOS 9 Bugs

[Ioana Gandrabur]

∫there's a good post on applevis about all the bugs and the only one posted 
about Braille if I'm not mistaken, is that the display disconnects and has to 
be repaired when in airplain mode, every time you unlock the phone. 
I have not checked this and have also not noticed any other bugs during my beta 
testing. 

Best,  

Ioana 



Sent from my iPhone

> On Sep 16, 2015, at 4:06 PM, Melissa Tucker  wrote:
> 
> does ios9 give any problems for people using a braille display?
> 
> 
> 
> On Sep 16, 2015, at 3:15 PM, Krister Ekstrom  
> wrote:
> 
> I always religiously update to the latest version of an Os when it comes out, 
> if it works it does, if not… well shrug.
> /Krister
> 
>> 16 sep. 2015 kl. 20:02 skrev Mike Arrigo :
>> 
>> In general, I think it's always good to wait until at least the first major 
>> update, sometimes the second of any new operating system so the major bugs 
>> can get worked out. Upgrading to a new version of an operating system as 
>> soon as it's released is far too risky.
>> Original message:
>>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>>> might like to be aware of in iOS 9.
>>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>>> minor annoyances to potentially critical, depending on how you use your 
>>> device and whether you find yourself affected. Here are just a few that you 
>>> might like to take into consideration before deciding whether to wait for a 
>>> bug fix release before installing iOS 9. Remember that a few days following 
>>> iOS 9's release, it will not be possible to downgrade again, so you should 
>>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>>> anything below concerns you.
>>> 1. Audio routing bug. This is potentially the most significant 
>>> accessibility bug I can recall ever to slip through an iOS release, due to 
>>> the number of people who may be affected. Not everyone will be, and at 
>>> present, even after extensive testing with a range of people owning 
>>> different devices, I have no information about why it affects some users, 
>>> but not others. It is not device specific, for example it is happening to 
>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem 
>>> isn't so severe. Nor does it seem to be affected by any setting. If you're 
>>> lucky, it won't happen to you, but the only way I am aware of to determine 
>>> this is to upgrade.
>>> This bug may affect you when you have earbuds or headphones connected to 
>>> the headphone socket of your iPhone. The primary way the audio routing bug 
>>> manifests itself is when you receive an incoming phone or FaceTime call. 
>>> You can usually hear if you're going to be affected by the bug because your 
>>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>>> audio to fade in and out when audio ducking is enabled. At this point, if 
>>> you press the power button to silence the ringer and then flick through the 
>>> screen, you will find that not only has VOiceOver become unresponsive, but 
>>> the entire phone has as well.
>>> If you don't press the power button while the phone is ringing, but instead 
>>> opt to flick through the iPHone's screen to locate the Answer button or 
>>> review caller ID information, VoiceOver may not speak at all.
>>> Finally, if you attempt to answer the incoming call with a two-finger 
>>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>>> up.
>>> The bottom line is that if you have earbuds connected, you may not be able 
>>> to answer a call.
>>> Some people have also reported similar problems answering calls when their 
>>> phone is set to silent.
>>> If you rely on your phone for business or safety, this could be a deal 
>>> breaker in terms of upgrading at this point.
>>> What makes this bug so fascinating is that not only is it completely absent 
>>> for some people, but of those who experience it, not all symptoms are 
>>> present for all users. For example, some people experience the issues I 
>>> have described when they press the power button to mute the ringer, but not 
>>> when the phone is ringing. Others can answer a call by pressing the button 
>>> on their EarPods, while others cannot.
>>> If you upgrade and are affected by this, here are a few things to try.
>>> (A) If you have the more moderate version of this bug, avoid pressing the 
>>> power button when you receive an incoming call.
>>> (B) Turning off audio ducking seems to help a little for some users.
>>> (C) If you can't answer a call with a two-finger double-tap, try pressing 
>>> the button on your EarPods or similar device if you have such a device 
>>> connected.
>>> (D) If all else 

Re: My top iOS 9 Bugs

[John Diakogeorgiou]

I've been using a VaroUltra and it works fine. Also one thing which no
one has mentioned is that you can now use the Siri male and female
voices for voice over. Just know that the male voice pronounces some
vowels strangely.

On 9/16/15, Jonathan Mosen <jmo...@mosen.org> wrote:
> Hi Neal. My understanding is that if you are affected, it will also happen
> if you have your phone on silent. If you just have your phone unmuted and on
> speaker, it appears to be OK as far as I know.
> Jonathan Mosen
> Mosen Consulting
> Blindness technology eBooks, tutorials and training
> http://Mosen.org
>
>> On 17/09/2015, at 9:38 AM, Neal Ewers <neal.ew...@ravenswood.org> wrote:
>>
>> Jonathan. Is this phone problem a problem only when using something
>> connected to the phone such as ear buds or a bluetooth device? Or, does it
>> also effect phone calls if you are using none of these devices and only
>> using the microphone and speaker in the phone?
>>
>> Thanks.
>>
>> Neal
>>
>>
>> From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>> [mailto:viphone@googlegroups.com <mailto:viphone@googlegroups.com>] On
>> Behalf Of Jonathan Mosen
>> Sent: Wednesday, September 16, 2015 12:15 PM
>> To: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>> Subject: My top iOS 9 Bugs
>>
>> Hi everyone, now that the NDA is lifted, here are some things I think you
>> might like to be aware of in iOS 9.
>> I am enthusiastic about iOS 9. It is significantly more responsive than
>> its predecessor, and there are many new features that I'm sure you'll
>> enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 9 that
>> range from minor annoyances to potentially critical, depending on how you
>> use your device and whether you find yourself affected. Here are just a
>> few that you might like to take into consideration before deciding whether
>> to wait for a bug fix release before installing iOS 9. Remember that a few
>> days following iOS 9's release, it will not be possible to downgrade
>> again, so you should consider the upgrade to iOS 9 a one-way trip, and
>> proceed with caution if anything below concerns you.
>> 1. Audio routing bug. This is potentially the most significant
>> accessibility bug I can recall ever to slip through an iOS release, due to
>> the number of people who may be affected. Not everyone will be, and at
>> present, even after extensive testing with a range of people owning
>> different devices, I have no information about why it affects some users,
>> but not others. It is not device specific, for example it is happening to
>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem
>> isn't so severe. Nor does it seem to be affected by any setting. If you're
>> lucky, it won't happen to you, but the only way I am aware of to determine
>> this is to upgrade.
>> This bug may affect you when you have earbuds or headphones connected to
>> the headphone socket of your iPhone. The primary way the audio routing bug
>> manifests itself is when you receive an incoming phone or FaceTime call.
>> You can usually hear if you're going to be affected by the bug because
>> your ring-tone will fade in and out, rather like the way VOiceOver causes
>> system audio to fade in and out when audio ducking is enabled. At this
>> point, if you press the power button to silence the ringer and then flick
>> through the screen, you will find that not only has VOiceOver become
>> unresponsive, but the entire phone has as well.
>> If you don't press the power button while the phone is ringing, but
>> instead opt to flick through the iPHone's screen to locate the Answer
>> button or review caller ID information, VoiceOver may not speak at all.
>> Finally, if you attempt to answer the incoming call with a two-finger
>> double-tap, you may not be able to, since VoiceOver has effectively locked
>> up.
>> The bottom line is that if you have earbuds connected, you may not be able
>> to answer a call.
>> Some people have also reported similar problems answering calls when their
>> phone is set to silent.
>> If you rely on your phone for business or safety, this could be a deal
>> breaker in terms of upgrading at this point.
>> What makes this bug so fascinating is that not only is it completely
>> absent for some people, but of those who experience it, not all symptoms
>> are present for all users. For example, some people experience the issues
>> I have described when they press the power button to mute the ringer, but
>> not when the phone is ringing. Others

Re: My top iOS 9 Bugs

[Alex Stone]

I also always update Asaph, even though I'm also a beta tester.

Sent from my iPhone

> On 16 Sep 2015, at 21:16, Ioana Gandrabur  wrote:
> 
> ∫there's a good post on applevis about all the bugs and the only one posted 
> about Braille if I'm not mistaken, is that the display disconnects and has to 
> be repaired when in airplain mode, every time you unlock the phone. 
> I have not checked this and have also not noticed any other bugs during my 
> beta testing. 
> 
> Best,  
> 
> Ioana 
> 
> 
> 
> Sent from my iPhone
> 
>> On Sep 16, 2015, at 4:06 PM, Melissa Tucker  wrote:
>> 
>> does ios9 give any problems for people using a braille display?
>> 
>> 
>> 
>> On Sep 16, 2015, at 3:15 PM, Krister Ekstrom  
>> wrote:
>> 
>> I always religiously update to the latest version of an Os when it comes 
>> out, if it works it does, if not… well shrug.
>> /Krister
>> 
>>> 16 sep. 2015 kl. 20:02 skrev Mike Arrigo :
>>> 
>>> In general, I think it's always good to wait until at least the first major 
>>> update, sometimes the second of any new operating system so the major bugs 
>>> can get worked out. Upgrading to a new version of an operating system as 
>>> soon as it's released is far too risky.
>>> Original message:
 Hi everyone, now that the NDA is lifted, here are some things I think you 
 might like to be aware of in iOS 9.
 I am enthusiastic about iOS 9. It is significantly more responsive than 
 its predecessor, and there are many new features that I'm sure you'll 
 enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 9 that 
 range from minor annoyances to potentially critical, depending on how you 
 use your device and whether you find yourself affected. Here are just a 
 few that you might like to take into consideration before deciding whether 
 to wait for a bug fix release before installing iOS 9. Remember that a few 
 days following iOS 9's release, it will not be possible to downgrade 
 again, so you should consider the upgrade to iOS 9 a one-way trip, and 
 proceed with caution if anything below concerns you.
 1. Audio routing bug. This is potentially the most significant 
 accessibility bug I can recall ever to slip through an iOS release, due to 
 the number of people who may be affected. Not everyone will be, and at 
 present, even after extensive testing with a range of people owning 
 different devices, I have no information about why it affects some users, 
 but not others. It is not device specific, for example it is happening to 
 me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem 
 isn't so severe. Nor does it seem to be affected by any setting. If you're 
 lucky, it won't happen to you, but the only way I am aware of to determine 
 this is to upgrade.
 This bug may affect you when you have earbuds or headphones connected to 
 the headphone socket of your iPhone. The primary way the audio routing bug 
 manifests itself is when you receive an incoming phone or FaceTime call. 
 You can usually hear if you're going to be affected by the bug because 
 your ring-tone will fade in and out, rather like the way VOiceOver causes 
 system audio to fade in and out when audio ducking is enabled. At this 
 point, if you press the power button to silence the ringer and then flick 
 through the screen, you will find that not only has VOiceOver become 
 unresponsive, but the entire phone has as well.
 If you don't press the power button while the phone is ringing, but 
 instead opt to flick through the iPHone's screen to locate the Answer 
 button or review caller ID information, VoiceOver may not speak at all.
 Finally, if you attempt to answer the incoming call with a two-finger 
 double-tap, you may not be able to, since VoiceOver has effectively locked 
 up.
 The bottom line is that if you have earbuds connected, you may not be able 
 to answer a call.
 Some people have also reported similar problems answering calls when their 
 phone is set to silent.
 If you rely on your phone for business or safety, this could be a deal 
 breaker in terms of upgrading at this point.
 What makes this bug so fascinating is that not only is it completely 
 absent for some people, but of those who experience it, not all symptoms 
 are present for all users. For example, some people experience the issues 
 I have described when they press the power button to mute the ringer, but 
 not when the phone is ringing. Others can answer a call by pressing the 
 button on their EarPods, while others cannot.
 If you upgrade and are affected by this, here are a few things to try.
 (A) If you have the more moderate version of this bug, avoid pressing the 
 power button when you receive an incoming call.

Re: My top iOS 9 Bugs

[christopher hallsworth]

Not really, but there is one bug that has been mentioned in this thread.
> On 16 Sep 2015, at 21:06, Melissa Tucker  wrote:
> 
> does ios9 give any problems for people using a braille display?
> 
> 
> 
> On Sep 16, 2015, at 3:15 PM, Krister Ekstrom  
> wrote:
> 
> I always religiously update to the latest version of an Os when it comes out, 
> if it works it does, if not… well shrug.
> /Krister
> 
>> 16 sep. 2015 kl. 20:02 skrev Mike Arrigo :
>> 
>> In general, I think it's always good to wait until at least the first major 
>> update, sometimes the second of any new operating system so the major bugs 
>> can get worked out. Upgrading to a new version of an operating system as 
>> soon as it's released is far too risky.
>> Original message:
>>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>>> might like to be aware of in iOS 9.
>>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>>> minor annoyances to potentially critical, depending on how you use your 
>>> device and whether you find yourself affected. Here are just a few that you 
>>> might like to take into consideration before deciding whether to wait for a 
>>> bug fix release before installing iOS 9. Remember that a few days following 
>>> iOS 9's release, it will not be possible to downgrade again, so you should 
>>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>>> anything below concerns you.
>>> 1. Audio routing bug. This is potentially the most significant 
>>> accessibility bug I can recall ever to slip through an iOS release, due to 
>>> the number of people who may be affected. Not everyone will be, and at 
>>> present, even after extensive testing with a range of people owning 
>>> different devices, I have no information about why it affects some users, 
>>> but not others. It is not device specific, for example it is happening to 
>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem 
>>> isn't so severe. Nor does it seem to be affected by any setting. If you're 
>>> lucky, it won't happen to you, but the only way I am aware of to determine 
>>> this is to upgrade.
>>> This bug may affect you when you have earbuds or headphones connected to 
>>> the headphone socket of your iPhone. The primary way the audio routing bug 
>>> manifests itself is when you receive an incoming phone or FaceTime call. 
>>> You can usually hear if you're going to be affected by the bug because your 
>>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>>> audio to fade in and out when audio ducking is enabled. At this point, if 
>>> you press the power button to silence the ringer and then flick through the 
>>> screen, you will find that not only has VOiceOver become unresponsive, but 
>>> the entire phone has as well.
>>> If you don't press the power button while the phone is ringing, but instead 
>>> opt to flick through the iPHone's screen to locate the Answer button or 
>>> review caller ID information, VoiceOver may not speak at all.
>>> Finally, if you attempt to answer the incoming call with a two-finger 
>>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>>> up.
>>> The bottom line is that if you have earbuds connected, you may not be able 
>>> to answer a call.
>>> Some people have also reported similar problems answering calls when their 
>>> phone is set to silent.
>>> If you rely on your phone for business or safety, this could be a deal 
>>> breaker in terms of upgrading at this point.
>>> What makes this bug so fascinating is that not only is it completely absent 
>>> for some people, but of those who experience it, not all symptoms are 
>>> present for all users. For example, some people experience the issues I 
>>> have described when they press the power button to mute the ringer, but not 
>>> when the phone is ringing. Others can answer a call by pressing the button 
>>> on their EarPods, while others cannot.
>>> If you upgrade and are affected by this, here are a few things to try.
>>> (A) If you have the more moderate version of this bug, avoid pressing the 
>>> power button when you receive an incoming call.
>>> (B) Turning off audio ducking seems to help a little for some users.
>>> (C) If you can't answer a call with a two-finger double-tap, try pressing 
>>> the button on your EarPods or similar device if you have such a device 
>>> connected.
>>> (D) If all else fails, you can disconnect any device from the headphone 
>>> jack, answer the call with a two-finger double-tap, then reconnect the 
>>> device to the headphone jack.
>>> (E) Given the critical nature of this bug, if you've upgraded and now find 
>>> yourself afflicted by it, enrol in the 

Re: My top iOS 9 Bugs

[Jonathan Mosen]

Hi Neal. My understanding is that if you are affected, it will also happen if 
you have your phone on silent. If you just have your phone unmuted and on 
speaker, it appears to be OK as far as I know.
Jonathan Mosen
Mosen Consulting
Blindness technology eBooks, tutorials and training
http://Mosen.org

> On 17/09/2015, at 9:38 AM, Neal Ewers <neal.ew...@ravenswood.org> wrote:
> 
> Jonathan. Is this phone problem a problem only when using something connected 
> to the phone such as ear buds or a bluetooth device? Or, does it also effect 
> phone calls if you are using none of these devices and only using the 
> microphone and speaker in the phone?
>  
> Thanks.
>  
> Neal
>  
>  
> From: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
> [mailto:viphone@googlegroups.com <mailto:viphone@googlegroups.com>] On Behalf 
> Of Jonathan Mosen
> Sent: Wednesday, September 16, 2015 12:15 PM
> To: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
> Subject: My top iOS 9 Bugs
>  
> Hi everyone, now that the NDA is lifted, here are some things I think you 
> might like to be aware of in iOS 9.
> I am enthusiastic about iOS 9. It is significantly more responsive than its 
> predecessor, and there are many new features that I'm sure you'll enjoy. 
> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
> minor annoyances to potentially critical, depending on how you use your 
> device and whether you find yourself affected. Here are just a few that you 
> might like to take into consideration before deciding whether to wait for a 
> bug fix release before installing iOS 9. Remember that a few days following 
> iOS 9's release, it will not be possible to downgrade again, so you should 
> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
> anything below concerns you.
> 1. Audio routing bug. This is potentially the most significant accessibility 
> bug I can recall ever to slip through an iOS release, due to the number of 
> people who may be affected. Not everyone will be, and at present, even after 
> extensive testing with a range of people owning different devices, I have no 
> information about why it affects some users, but not others. It is not device 
> specific, for example it is happening to me on my iPhone 6 Plus, but I know 
> iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to be 
> affected by any setting. If you're lucky, it won't happen to you, but the 
> only way I am aware of to determine this is to upgrade.
> This bug may affect you when you have earbuds or headphones connected to the 
> headphone socket of your iPhone. The primary way the audio routing bug 
> manifests itself is when you receive an incoming phone or FaceTime call. You 
> can usually hear if you're going to be affected by the bug because your 
> ring-tone will fade in and out, rather like the way VOiceOver causes system 
> audio to fade in and out when audio ducking is enabled. At this point, if you 
> press the power button to silence the ringer and then flick through the 
> screen, you will find that not only has VOiceOver become unresponsive, but 
> the entire phone has as well.
> If you don't press the power button while the phone is ringing, but instead 
> opt to flick through the iPHone's screen to locate the Answer button or 
> review caller ID information, VoiceOver may not speak at all.
> Finally, if you attempt to answer the incoming call with a two-finger 
> double-tap, you may not be able to, since VoiceOver has effectively locked up.
> The bottom line is that if you have earbuds connected, you may not be able to 
> answer a call.
> Some people have also reported similar problems answering calls when their 
> phone is set to silent.
> If you rely on your phone for business or safety, this could be a deal 
> breaker in terms of upgrading at this point.
> What makes this bug so fascinating is that not only is it completely absent 
> for some people, but of those who experience it, not all symptoms are present 
> for all users. For example, some people experience the issues I have 
> described when they press the power button to mute the ringer, but not when 
> the phone is ringing. Others can answer a call by pressing the button on 
> their EarPods, while others cannot.
> If you upgrade and are affected by this, here are a few things to try.
> (A) If you have the more moderate version of this bug, avoid pressing the 
> power button when you receive an incoming call.
> (B) Turning off audio ducking seems to help a little for some users.
> (C) If you can't answer a call with a two-finger double-tap, try pressing the 
> button on your EarPods or similar device if you have such a device connected.
>

Re: My top iOS 9 Bugs

[Kerri G]

I always update to the latest since though I do not have a paid job in the 
technology field, I find it better so I may assist where possible.



> On Sep 16, 2015, at 12:15 PM, Krister Ekstrom  
> wrote:
> 
> I always religiously update to the latest version of an Os when it comes out, 
> if it works it does, if not… well shrug.
> /Krister
> 
>> 16 sep. 2015 kl. 20:02 skrev Mike Arrigo :
>> 
>> In general, I think it's always good to wait until at least the first major 
>> update, sometimes the second of any new operating system so the major bugs 
>> can get worked out. Upgrading to a new version of an operating system as 
>> soon as it's released is far too risky.
>> Original message:
>>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>>> might like to be aware of in iOS 9.
>>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>>> minor annoyances to potentially critical, depending on how you use your 
>>> device and whether you find yourself affected. Here are just a few that you 
>>> might like to take into consideration before deciding whether to wait for a 
>>> bug fix release before installing iOS 9. Remember that a few days following 
>>> iOS 9's release, it will not be possible to downgrade again, so you should 
>>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>>> anything below concerns you.
>>> 1. Audio routing bug. This is potentially the most significant 
>>> accessibility bug I can recall ever to slip through an iOS release, due to 
>>> the number of people who may be affected. Not everyone will be, and at 
>>> present, even after extensive testing with a range of people owning 
>>> different devices, I have no information about why it affects some users, 
>>> but not others. It is not device specific, for example it is happening to 
>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem 
>>> isn't so severe. Nor does it seem to be affected by any setting. If you're 
>>> lucky, it won't happen to you, but the only way I am aware of to determine 
>>> this is to upgrade.
>>> This bug may affect you when you have earbuds or headphones connected to 
>>> the headphone socket of your iPhone. The primary way the audio routing bug 
>>> manifests itself is when you receive an incoming phone or FaceTime call. 
>>> You can usually hear if you're going to be affected by the bug because your 
>>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>>> audio to fade in and out when audio ducking is enabled. At this point, if 
>>> you press the power button to silence the ringer and then flick through the 
>>> screen, you will find that not only has VOiceOver become unresponsive, but 
>>> the entire phone has as well.
>>> If you don't press the power button while the phone is ringing, but instead 
>>> opt to flick through the iPHone's screen to locate the Answer button or 
>>> review caller ID information, VoiceOver may not speak at all.
>>> Finally, if you attempt to answer the incoming call with a two-finger 
>>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>>> up.
>>> The bottom line is that if you have earbuds connected, you may not be able 
>>> to answer a call.
>>> Some people have also reported similar problems answering calls when their 
>>> phone is set to silent.
>>> If you rely on your phone for business or safety, this could be a deal 
>>> breaker in terms of upgrading at this point.
>>> What makes this bug so fascinating is that not only is it completely absent 
>>> for some people, but of those who experience it, not all symptoms are 
>>> present for all users. For example, some people experience the issues I 
>>> have described when they press the power button to mute the ringer, but not 
>>> when the phone is ringing. Others can answer a call by pressing the button 
>>> on their EarPods, while others cannot.
>>> If you upgrade and are affected by this, here are a few things to try.
>>> (A) If you have the more moderate version of this bug, avoid pressing the 
>>> power button when you receive an incoming call.
>>> (B) Turning off audio ducking seems to help a little for some users.
>>> (C) If you can't answer a call with a two-finger double-tap, try pressing 
>>> the button on your EarPods or similar device if you have such a device 
>>> connected.
>>> (D) If all else fails, you can disconnect any device from the headphone 
>>> jack, answer the call with a two-finger double-tap, then reconnect the 
>>> device to the headphone jack.
>>> (E) Given the critical nature of this bug, if you've upgraded and now find 
>>> yourself afflicted by it, enrol in the iOS beta program so you can receive 
>>> early copies of any fixes Apple is 

Re: My top iOS 9 Bugs

[Woody Anna Dresner]

Hi,

I've used a Focus 40 Blue Classic and a RefreshaBraille 18 throughout the betas 
and have had no problems except that BARD Mobile is far less likely to save my 
reading position than previously.

Best,
Anna



> On Sep 16, 2015, at 3:06 PM, Melissa Tucker  wrote:
> 
> does ios9 give any problems for people using a braille display?
> 
> 
> 
> On Sep 16, 2015, at 3:15 PM, Krister Ekstrom  
> wrote:
> 
> I always religiously update to the latest version of an Os when it comes out, 
> if it works it does, if not… well shrug.
> /Krister
> 
>> 16 sep. 2015 kl. 20:02 skrev Mike Arrigo :
>> 
>> In general, I think it's always good to wait until at least the first major 
>> update, sometimes the second of any new operating system so the major bugs 
>> can get worked out. Upgrading to a new version of an operating system as 
>> soon as it's released is far too risky.
>> Original message:
>>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>>> might like to be aware of in iOS 9.
>>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>>> minor annoyances to potentially critical, depending on how you use your 
>>> device and whether you find yourself affected. Here are just a few that you 
>>> might like to take into consideration before deciding whether to wait for a 
>>> bug fix release before installing iOS 9. Remember that a few days following 
>>> iOS 9's release, it will not be possible to downgrade again, so you should 
>>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>>> anything below concerns you.
>>> 1. Audio routing bug. This is potentially the most significant 
>>> accessibility bug I can recall ever to slip through an iOS release, due to 
>>> the number of people who may be affected. Not everyone will be, and at 
>>> present, even after extensive testing with a range of people owning 
>>> different devices, I have no information about why it affects some users, 
>>> but not others. It is not device specific, for example it is happening to 
>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem 
>>> isn't so severe. Nor does it seem to be affected by any setting. If you're 
>>> lucky, it won't happen to you, but the only way I am aware of to determine 
>>> this is to upgrade.
>>> This bug may affect you when you have earbuds or headphones connected to 
>>> the headphone socket of your iPhone. The primary way the audio routing bug 
>>> manifests itself is when you receive an incoming phone or FaceTime call. 
>>> You can usually hear if you're going to be affected by the bug because your 
>>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>>> audio to fade in and out when audio ducking is enabled. At this point, if 
>>> you press the power button to silence the ringer and then flick through the 
>>> screen, you will find that not only has VOiceOver become unresponsive, but 
>>> the entire phone has as well.
>>> If you don't press the power button while the phone is ringing, but instead 
>>> opt to flick through the iPHone's screen to locate the Answer button or 
>>> review caller ID information, VoiceOver may not speak at all.
>>> Finally, if you attempt to answer the incoming call with a two-finger 
>>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>>> up.
>>> The bottom line is that if you have earbuds connected, you may not be able 
>>> to answer a call.
>>> Some people have also reported similar problems answering calls when their 
>>> phone is set to silent.
>>> If you rely on your phone for business or safety, this could be a deal 
>>> breaker in terms of upgrading at this point.
>>> What makes this bug so fascinating is that not only is it completely absent 
>>> for some people, but of those who experience it, not all symptoms are 
>>> present for all users. For example, some people experience the issues I 
>>> have described when they press the power button to mute the ringer, but not 
>>> when the phone is ringing. Others can answer a call by pressing the button 
>>> on their EarPods, while others cannot.
>>> If you upgrade and are affected by this, here are a few things to try.
>>> (A) If you have the more moderate version of this bug, avoid pressing the 
>>> power button when you receive an incoming call.
>>> (B) Turning off audio ducking seems to help a little for some users.
>>> (C) If you can't answer a call with a two-finger double-tap, try pressing 
>>> the button on your EarPods or similar device if you have such a device 
>>> connected.
>>> (D) If all else fails, you can disconnect any device from the headphone 
>>> jack, answer the call with a two-finger double-tap, then reconnect the 
>>> device 

Re: My top iOS 9 Bugs

[Sherrie]

I was just wondering if the audio ducking bug also affected blue tooth ear 
pieces? I have had difficulties with wired earphones for more than a year with 
my iPhone 5 so I use a Plantronics Voyager Edge most of the time.
I am planning to purchase the 6S in a month or so and I will have IOS 9 on it 
so will need to deal with it..
Thanks,
Sherrie Gosling


From: Jonathan Mosen 
Sent: Wednesday, September 16, 2015 1:15 PM
To: viphone@googlegroups.com 
Subject: My top iOS 9 Bugs

Hi everyone, now that the NDA is lifted, here are some things I think you might 
like to be aware of in iOS 9. 
I am enthusiastic about iOS 9. It is significantly more responsive than its 
predecessor, and there are many new features that I'm sure you'll enjoy. 
Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
minor annoyances to potentially critical, depending on how you use your device 
and whether you find yourself affected. Here are just a few that you might like 
to take into consideration before deciding whether to wait for a bug fix 
release before installing iOS 9. Remember that a few days following iOS 9's 
release, it will not be possible to downgrade again, so you should consider the 
upgrade to iOS 9 a one-way trip, and proceed with caution if anything below 
concerns you.
1. Audio routing bug. This is potentially the most significant accessibility 
bug I can recall ever to slip through an iOS release, due to the number of 
people who may be affected. Not everyone will be, and at present, even after 
extensive testing with a range of people owning different devices, I have no 
information about why it affects some users, but not others. It is not device 
specific, for example it is happening to me on my iPhone 6 Plus, but I know 
iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to be 
affected by any setting. If you're lucky, it won't happen to you, but the only 
way I am aware of to determine this is to upgrade.
This bug may affect you when you have earbuds or headphones connected to the 
headphone socket of your iPhone. The primary way the audio routing bug 
manifests itself is when you receive an incoming phone or FaceTime call. You 
can usually hear if you're going to be affected by the bug because your 
ring-tone will fade in and out, rather like the way VOiceOver causes system 
audio to fade in and out when audio ducking is enabled. At this point, if you 
press the power button to silence the ringer and then flick through the screen, 
you will find that not only has VOiceOver become unresponsive, but the entire 
phone has as well.
If you don't press the power button while the phone is ringing, but instead opt 
to flick through the iPHone's screen to locate the Answer button or review 
caller ID information, VoiceOver may not speak at all.
Finally, if you attempt to answer the incoming call with a two-finger 
double-tap, you may not be able to, since VoiceOver has effectively locked up.
The bottom line is that if you have earbuds connected, you may not be able to 
answer a call.
Some people have also reported similar problems answering calls when their 
phone is set to silent.
If you rely on your phone for business or safety, this could be a deal breaker 
in terms of upgrading at this point.
What makes this bug so fascinating is that not only is it completely absent for 
some people, but of those who experience it, not all symptoms are present for 
all users. For example, some people experience the issues I have described when 
they press the power button to mute the ringer, but not when the phone is 
ringing. Others can answer a call by pressing the button on their EarPods, 
while others cannot.
If you upgrade and are affected by this, here are a few things to try.
(A) If you have the more moderate version of this bug, avoid pressing the power 
button when you receive an incoming call.
(B) Turning off audio ducking seems to help a little for some users.
(C) If you can't answer a call with a two-finger double-tap, try pressing the 
button on your EarPods or similar device if you have such a device connected.
(D) If all else fails, you can disconnect any device from the headphone jack, 
answer the call with a two-finger double-tap, then reconnect the device to the 
headphone jack.
(E) Given the critical nature of this bug, if you've upgraded and now find 
yourself afflicted by it, enrol in the iOS beta program so you can receive 
early copies of any fixes Apple is working on. But keep in mind that since you 
will be running beta software, you may well be swapping one set of bugs for 
another.
2. Bluetooth keyboard support unreliable. Sometimes, users may input double 
letters when typing. This is a bug that was introduced in the iOS 8 cycle, and 
can easily be worked around by toggling VoiceOver off and on.
However, a new bug now exists where at times, no text is entered into a field 
at all when VO is active. Toggling VO doesn't help, nor does switching the 
keyboard

RE: My top iOS 9 Bugs

[Neal Ewers]

Jonathan. Is this phone problem a problem only when using something connected 
to the phone such as ear buds or a bluetooth device? Or, does it also effect 
phone calls if you are using none of these devices and only using the 
microphone and speaker in the phone?
 
Thanks.
 
Neal
 
 
From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf Of 
Jonathan Mosen
Sent: Wednesday, September 16, 2015 12:15 PM
To: viphone@googlegroups.com
Subject: My top iOS 9 Bugs
 
Hi everyone, now that the NDA is lifted, here are some things I think you might 
like to be aware of in iOS 9.
I am enthusiastic about iOS 9. It is significantly more responsive than its 
predecessor, and there are many new features that I'm sure you'll enjoy. 
Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
minor annoyances to potentially critical, depending on how you use your device 
and whether you find yourself affected. Here are just a few that you might like 
to take into consideration before deciding whether to wait for a bug fix 
release before installing iOS 9. Remember that a few days following iOS 9's 
release, it will not be possible to downgrade again, so you should consider the 
upgrade to iOS 9 a one-way trip, and proceed with caution if anything below 
concerns you.
1. Audio routing bug. This is potentially the most significant accessibility 
bug I can recall ever to slip through an iOS release, due to the number of 
people who may be affected. Not everyone will be, and at present, even after 
extensive testing with a range of people owning different devices, I have no 
information about why it affects some users, but not others. It is not device 
specific, for example it is happening to me on my iPhone 6 Plus, but I know 
iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to be 
affected by any setting. If you're lucky, it won't happen to you, but the only 
way I am aware of to determine this is to upgrade.
This bug may affect you when you have earbuds or headphones connected to the 
headphone socket of your iPhone. The primary way the audio routing bug 
manifests itself is when you receive an incoming phone or FaceTime call. You 
can usually hear if you're going to be affected by the bug because your 
ring-tone will fade in and out, rather like the way VOiceOver causes system 
audio to fade in and out when audio ducking is enabled. At this point, if you 
press the power button to silence the ringer and then flick through the screen, 
you will find that not only has VOiceOver become unresponsive, but the entire 
phone has as well.
If you don't press the power button while the phone is ringing, but instead opt 
to flick through the iPHone's screen to locate the Answer button or review 
caller ID information, VoiceOver may not speak at all.
Finally, if you attempt to answer the incoming call with a two-finger 
double-tap, you may not be able to, since VoiceOver has effectively locked up.
The bottom line is that if you have earbuds connected, you may not be able to 
answer a call.
Some people have also reported similar problems answering calls when their 
phone is set to silent.
If you rely on your phone for business or safety, this could be a deal breaker 
in terms of upgrading at this point.
What makes this bug so fascinating is that not only is it completely absent for 
some people, but of those who experience it, not all symptoms are present for 
all users. For example, some people experience the issues I have described when 
they press the power button to mute the ringer, but not when the phone is 
ringing. Others can answer a call by pressing the button on their EarPods, 
while others cannot.
If you upgrade and are affected by this, here are a few things to try.
(A) If you have the more moderate version of this bug, avoid pressing the power 
button when you receive an incoming call.
(B) Turning off audio ducking seems to help a little for some users.
(C) If you can't answer a call with a two-finger double-tap, try pressing the 
button on your EarPods or similar device if you have such a device connected.
(D) If all else fails, you can disconnect any device from the headphone jack, 
answer the call with a two-finger double-tap, then reconnect the device to the 
headphone jack.
(E) Given the critical nature of this bug, if you've upgraded and now find 
yourself afflicted by it, enrol in the iOS beta program so you can receive 
early copies of any fixes Apple is working on. But keep in mind that since you 
will be running beta software, you may well be swapping one set of bugs for 
another.
2. Bluetooth keyboard support unreliable. Sometimes, users may input double 
letters when typing. This is a bug that was introduced in the iOS 8 cycle, and 
can easily be worked around by toggling VoiceOver off and on.
However, a new bug now exists where at times, no text is entered into a field 
at all when VO is active. Toggling VO doesn't help, nor does switching the 
keyboard

Re: My top iOS 9 Bugs

[Shai]

Hi,
The setting of the Siri voices for VoiceOver was mentioned on
AppleVis; however, it was also indicated that the responsiveness is
quite sluggish while navigating.
Have you noticed this?


On 9/16/15, John Diakogeorgiou <jdiakoge2...@gmail.com> wrote:
> I've been using a VaroUltra and it works fine. Also one thing which no
> one has mentioned is that you can now use the Siri male and female
> voices for voice over. Just know that the male voice pronounces some
> vowels strangely.
>
> On 9/16/15, Jonathan Mosen <jmo...@mosen.org> wrote:
>> Hi Neal. My understanding is that if you are affected, it will also
>> happen
>> if you have your phone on silent. If you just have your phone unmuted and
>> on
>> speaker, it appears to be OK as far as I know.
>> Jonathan Mosen
>> Mosen Consulting
>> Blindness technology eBooks, tutorials and training
>> http://Mosen.org
>>
>>> On 17/09/2015, at 9:38 AM, Neal Ewers <neal.ew...@ravenswood.org> wrote:
>>>
>>> Jonathan. Is this phone problem a problem only when using something
>>> connected to the phone such as ear buds or a bluetooth device? Or, does
>>> it
>>> also effect phone calls if you are using none of these devices and only
>>> using the microphone and speaker in the phone?
>>>
>>> Thanks.
>>>
>>> Neal
>>>
>>>
>>> From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>>> [mailto:viphone@googlegroups.com <mailto:viphone@googlegroups.com>] On
>>> Behalf Of Jonathan Mosen
>>> Sent: Wednesday, September 16, 2015 12:15 PM
>>> To: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>>> Subject: My top iOS 9 Bugs
>>>
>>> Hi everyone, now that the NDA is lifted, here are some things I think
>>> you
>>> might like to be aware of in iOS 9.
>>> I am enthusiastic about iOS 9. It is significantly more responsive than
>>> its predecessor, and there are many new features that I'm sure you'll
>>> enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 9 that
>>> range from minor annoyances to potentially critical, depending on how
>>> you
>>> use your device and whether you find yourself affected. Here are just a
>>> few that you might like to take into consideration before deciding
>>> whether
>>> to wait for a bug fix release before installing iOS 9. Remember that a
>>> few
>>> days following iOS 9's release, it will not be possible to downgrade
>>> again, so you should consider the upgrade to iOS 9 a one-way trip, and
>>> proceed with caution if anything below concerns you.
>>> 1. Audio routing bug. This is potentially the most significant
>>> accessibility bug I can recall ever to slip through an iOS release, due
>>> to
>>> the number of people who may be affected. Not everyone will be, and at
>>> present, even after extensive testing with a range of people owning
>>> different devices, I have no information about why it affects some
>>> users,
>>> but not others. It is not device specific, for example it is happening
>>> to
>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem
>>> isn't so severe. Nor does it seem to be affected by any setting. If
>>> you're
>>> lucky, it won't happen to you, but the only way I am aware of to
>>> determine
>>> this is to upgrade.
>>> This bug may affect you when you have earbuds or headphones connected to
>>> the headphone socket of your iPhone. The primary way the audio routing
>>> bug
>>> manifests itself is when you receive an incoming phone or FaceTime call.
>>> You can usually hear if you're going to be affected by the bug because
>>> your ring-tone will fade in and out, rather like the way VOiceOver
>>> causes
>>> system audio to fade in and out when audio ducking is enabled. At this
>>> point, if you press the power button to silence the ringer and then
>>> flick
>>> through the screen, you will find that not only has VOiceOver become
>>> unresponsive, but the entire phone has as well.
>>> If you don't press the power button while the phone is ringing, but
>>> instead opt to flick through the iPHone's screen to locate the Answer
>>> button or review caller ID information, VoiceOver may not speak at all.
>>> Finally, if you attempt to answer the incoming call with a two-finger
>>> double-tap, you may not be able to, since VoiceOver has effectively
>>> locke

Re: My top iOS 9 Bugs

[John Diakogeorgiou]

I find it works well but will try another voice to see if I am wrong.

On 9/16/15, Shai <shai...@gmail.com> wrote:
> Hi,
> The setting of the Siri voices for VoiceOver was mentioned on
> AppleVis; however, it was also indicated that the responsiveness is
> quite sluggish while navigating.
> Have you noticed this?
>
>
> On 9/16/15, John Diakogeorgiou <jdiakoge2...@gmail.com> wrote:
>> I've been using a VaroUltra and it works fine. Also one thing which no
>> one has mentioned is that you can now use the Siri male and female
>> voices for voice over. Just know that the male voice pronounces some
>> vowels strangely.
>>
>> On 9/16/15, Jonathan Mosen <jmo...@mosen.org> wrote:
>>> Hi Neal. My understanding is that if you are affected, it will also
>>> happen
>>> if you have your phone on silent. If you just have your phone unmuted
>>> and
>>> on
>>> speaker, it appears to be OK as far as I know.
>>> Jonathan Mosen
>>> Mosen Consulting
>>> Blindness technology eBooks, tutorials and training
>>> http://Mosen.org
>>>
>>>> On 17/09/2015, at 9:38 AM, Neal Ewers <neal.ew...@ravenswood.org>
>>>> wrote:
>>>>
>>>> Jonathan. Is this phone problem a problem only when using something
>>>> connected to the phone such as ear buds or a bluetooth device? Or, does
>>>> it
>>>> also effect phone calls if you are using none of these devices and only
>>>> using the microphone and speaker in the phone?
>>>>
>>>> Thanks.
>>>>
>>>> Neal
>>>>
>>>>
>>>> From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>>>> [mailto:viphone@googlegroups.com <mailto:viphone@googlegroups.com>] On
>>>> Behalf Of Jonathan Mosen
>>>> Sent: Wednesday, September 16, 2015 12:15 PM
>>>> To: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>>>> Subject: My top iOS 9 Bugs
>>>>
>>>> Hi everyone, now that the NDA is lifted, here are some things I think
>>>> you
>>>> might like to be aware of in iOS 9.
>>>> I am enthusiastic about iOS 9. It is significantly more responsive than
>>>> its predecessor, and there are many new features that I'm sure you'll
>>>> enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 9 that
>>>> range from minor annoyances to potentially critical, depending on how
>>>> you
>>>> use your device and whether you find yourself affected. Here are just a
>>>> few that you might like to take into consideration before deciding
>>>> whether
>>>> to wait for a bug fix release before installing iOS 9. Remember that a
>>>> few
>>>> days following iOS 9's release, it will not be possible to downgrade
>>>> again, so you should consider the upgrade to iOS 9 a one-way trip, and
>>>> proceed with caution if anything below concerns you.
>>>> 1. Audio routing bug. This is potentially the most significant
>>>> accessibility bug I can recall ever to slip through an iOS release, due
>>>> to
>>>> the number of people who may be affected. Not everyone will be, and at
>>>> present, even after extensive testing with a range of people owning
>>>> different devices, I have no information about why it affects some
>>>> users,
>>>> but not others. It is not device specific, for example it is happening
>>>> to
>>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the
>>>> problem
>>>> isn't so severe. Nor does it seem to be affected by any setting. If
>>>> you're
>>>> lucky, it won't happen to you, but the only way I am aware of to
>>>> determine
>>>> this is to upgrade.
>>>> This bug may affect you when you have earbuds or headphones connected
>>>> to
>>>> the headphone socket of your iPhone. The primary way the audio routing
>>>> bug
>>>> manifests itself is when you receive an incoming phone or FaceTime
>>>> call.
>>>> You can usually hear if you're going to be affected by the bug because
>>>> your ring-tone will fade in and out, rather like the way VOiceOver
>>>> causes
>>>> system audio to fade in and out when audio ducking is enabled. At this
>>>> point, if you press the power button to silence the ringer and then
>>>> flick
>>>> through the s

Re: My top iOS 9 Bugs

[Terry-Ann Saurmann]

Great explanation!  Thank you.  Terry

- Original Message - 
From: "Christopher Chaltain" <chalt...@gmail.com>

To: <viphone@googlegroups.com>
Sent: Wednesday, September 16, 2015 11:11 PM
Subject: Re: My top iOS 9 Bugs


Although the ecosystem is much simpler for Apple then it is say for
Microsoft or Google, it's still a huge task to test every possible
combination of hardware, software, applications and settings. I think
there are 7 iPhone models right now, and I'm not sure how many iPads and
iPods there are running IOS. There are different screen sizes now across
all of the Apple product lines.

The components in each iDevice come from multiple vendors and change
from year to year. I remember that not long after the iPhone 5's came
out, there was an update just for the iPhone 5's that caused a lot of
confusion since everyone was running the latest IOS but not everyone was
running the same version of IOS. This was because Apple fixed a bug in
code written to support a particular component that was only present in
the iPhone 5 at the time.

iDevices can also have different amounts of memory, multiplying the size
of the test matrix. iPhones are also on different carriers, some being
GSM and some being CDMA.

You then have all of the different settings users can change. Users can
also use very different amounts of memory. Someone could have a 64G
iPhone with almost no available memory while someone else might run a
very lean 16G iPhone. Of course, there's all of the combinations of apps
a user can have, whether they clear out the App Switcher regulraly or
not, how frequently they power off their phone, whether they keep all of
their radios on or whether they turn off bluetooth, whether they run
their batteries down frequently or just top it off and so on.

There will also be some bad hardware out there. It may look like an
upgrade breaks the system when really it's just exposing some defective
hardware that wasn't being exercised before the upgrade.

It's very likely that you'll see a bug on one model and not another or
even on one device and not another device of the same model.

I haven't looked at the numbers, but it very well might be the case that
the dozen or so bugs we're seeing in IOS 9 are still much smaller
proportionally then you saw with a new release of Windows or Android.
Note, I'm not saying Apple is higher quality or less buggy. I just think
they're different ecosystems, and it's hard to compare them, especially
when you're just looking at anecdotal data of the individual bugs we're
seeing right after an initial release of IOS.

On 09/16/2015 02:23 PM, Mary Otten wrote:
OK, here is the question. Perhaps really it is a rhetorical one. One of 
the things they used to say with justification, about windows, was that 
part of the problem was that there was such a proliferation of hardware 
and software. Microsoft had to worry about all these various 
configurations. No wonder it wasn't stable, and bugs were hard to 
reproduce. So here is Apple. Relatively few types of iOS device are 
present. Yet we are seeing reports of bugs that show up here and not there 
and I have a question. Why? Apple controls the hardware and they control 
the OS. If there is a bug, shouldn't it at least show up on all of a given 
device say an iPhone 6 Plus? Or an iPad mini? I wonder what happens if you 
take your device that is exhibiting a bug, and to strip it back down to 
where it only has the things that Apple offers. Does the bug go away? Is 
there some sort of interaction between certain software and voiceover or 
the OS or whatever that cause is bugs to appear on some peoples device

s and not others? This really does not seem to make very much sense.

Mary

Sent from my iPhone

On Sep 16, 2015, at 11:38 AM, John Diakogeorgiou <jdiakoge2...@gmail.com> 
wrote:


I have not seen Harry's problem either.


On 9/16/15, John Diakogeorgiou <jdiakoge2...@gmail.com> wrote:
Jonathan thanks for the bug report. I can confirm point 4. It is very
frustrating when I am trying to make a call and it always goes to the
top of my contact list. I have not tried using ear buds. I will say
though that I haven't had any problems using a Bluetooth ear piece. I
am able to answer calls just fine.
In general the new software is much better than version 8.


On 9/16/15, Nancy Feldman <lorav...@gmail.com> wrote:
For what it's worth, I've successfully upgraded and received three 
phone
calls. None of them has resulted in unusual or unstable behavior from 
the

phone and I was able to answer it from the earbuds and from the screen.

I appreciate being made aware of the possibility, but I opted to take 
my

chances, and have no concerns so far.


On Sep 16, 2015, at 11:52, Jenifer Barr <claudas...@gmail.com> wrote:

Wow Jonathan!!! Thanks for the list. While I gladly bought your 
book...

I'll wait for the next version hopefully in a week or so!!

Jenifer Barr
Sent from my iPhone

On

Re: My top iOS 9 Bugs

[Chris Smart]

Hi Jonathan. Thanks for listing the Bluetooth keyboard issue, #2 below.

Hopefully they'lll get a fix out soon!

At 01:15 PM 9/16/2015, you wrote:
Hi everyone, now that the NDA is
lifted, here are some things I think you might like to be aware of in iOS
9.
I am enthusiastic about iOS 9. It is significantly more responsive than
its predecessor, and there are many new features that I'm sure you'll
enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 9 that
range from minor annoyances to potentially critical, depending on how you
use your device and whether you find yourself affected. Here are just a
few that you might like to take into consideration before deciding
whether to wait for a bug fix release before installing iOS 9. Remember
that a few days following iOS 9's release, it will not be possible to
downgrade again, so you should consider the upgrade to iOS 9 a one-way
trip, and proceed with caution if anything below concerns you.
1. Audio routing bug. This is potentially the most significant
accessibility bug I can recall ever to slip through an iOS release, due
to the number of people who may be affected. Not everyone will be, and at
present, even after extensive testing with a range of people owning
different devices, I have no information about why it affects some users,
but not others. It is not device specific, for example it is happening to
me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem
isn't so severe. Nor does it seem to be affected by any setting. If
you're lucky, it won't happen to you, but the only way I am aware of to
determine this is to upgrade.
This bug may affect you when you have earbuds or headphones connected to
the headphone socket of your iPhone. The primary way the audio routing
bug manifests itself is when you receive an incoming phone or FaceTime
call. You can usually hear if you're going to be affected by the bug
because your ring-tone will fade in and out, rather like the way
VOiceOver causes system audio to fade in and out when audio ducking is
enabled. At this point, if you press the power button to silence the
ringer and then flick through the screen, you will find that not only has
VOiceOver become unresponsive, but the entire phone has as well.
If you don't press the power button while the phone is ringing, but
instead opt to flick through the iPHone's screen to locate the Answer
button or review caller ID information, VoiceOver may not speak at
all.
Finally, if you attempt to answer the incoming call with a two-finger
double-tap, you may not be able to, since VoiceOver has effectively
locked up.
The bottom line is that if you have earbuds connected, you may not be
able to answer a call.
Some people have also reported similar problems answering calls when
their phone is set to silent.
If you rely on your phone for business or safety, this could be a deal
breaker in terms of upgrading at this point.
What makes this bug so fascinating is that not only is it completely
absent for some people, but of those who experience it, not all symptoms
are present for all users. For example, some people experience the issues
I have described when they press the power button to mute the ringer, but
not when the phone is ringing. Others can answer a call by pressing the
button on their EarPods, while others cannot.
If you upgrade and are affected by this, here are a few things to
try.
(A) If you have the more moderate version of this bug, avoid pressing the
power button when you receive an incoming call.
(B) Turning off audio ducking seems to help a little for some users.
(C) If you can't answer a call with a two-finger double-tap, try pressing
the button on your EarPods or similar device if you have such a device
connected.
(D) If all else fails, you can disconnect any device from the headphone
jack, answer the call with a two-finger double-tap, then reconnect the
device to the headphone jack.
(E) Given the critical nature of this bug, if you've upgraded and now
find yourself afflicted by it, enrol in the iOS beta program so you can
receive early copies of any fixes Apple is working on. But keep in mind
that since you will be running beta software, you may well be swapping
one set of bugs for another.
2. Bluetooth keyboard support unreliable. Sometimes, users may input
double letters when typing. This is a bug that was introduced in the iOS
8 cycle, and can easily be worked around by toggling VoiceOver off and
on.
However, a new bug now exists where at times, no text is entered into a
field at all when VO is active. Toggling VO doesn't help, nor does
switching the keyboard off and on. The only immediate remedy is to turn
Vo off, and keep typing without it. If you turn VO back on again, the
arrow keys don't work when you're trying to navigate your text, and you
can't edit it.
3. In the Today view of Notification Center, VO frequently restarts
itself when flicking through your widgets, and sometimes the phone locks
up entirely.
4. It's much less 

RE: My top iOS 9 Bugs

[Ron Pelletier]

According to Applevis, it does

Ron & Danvers

-Original Message-
From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf Of 
Melissa Tucker
Sent: Wednesday, September 16, 2015 4:07 PM
To: viphone@googlegroups.com
Subject: Re: My top iOS 9 Bugs

does ios9 give any problems for people using a braille display?



On Sep 16, 2015, at 3:15 PM, Krister Ekstrom <kris...@kristersplace.com> wrote:

I always religiously update to the latest version of an Os when it comes out, 
if it works it does, if not… well shrug.
/Krister

> 16 sep. 2015 kl. 20:02 skrev Mike Arrigo <n0...@charter.net>:
> 
> In general, I think it's always good to wait until at least the first major 
> update, sometimes the second of any new operating system so the major bugs 
> can get worked out. Upgrading to a new version of an operating system as soon 
> as it's released is far too risky.
> Original message:
>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>> might like to be aware of in iOS 9.
>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>> minor annoyances to potentially critical, depending on how you use your 
>> device and whether you find yourself affected. Here are just a few that you 
>> might like to take into consideration before deciding whether to wait for a 
>> bug fix release before installing iOS 9. Remember that a few days following 
>> iOS 9's release, it will not be possible to downgrade again, so you should 
>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>> anything below concerns you.
>> 1. Audio routing bug. This is potentially the most significant accessibility 
>> bug I can recall ever to slip through an iOS release, due to the number of 
>> people who may be affected. Not everyone will be, and at present, even after 
>> extensive testing with a range of people owning different devices, I have no 
>> information about why it affects some users, but not others. It is not 
>> device specific, for example it is happening to me on my iPhone 6 Plus, but 
>> I know iPhone 6 Plus users where the problem isn't so severe. Nor does it 
>> seem to be affected by any setting. If you're lucky, it won't happen to you, 
>> but the only way I am aware of to determine this is to upgrade.
>> This bug may affect you when you have earbuds or headphones connected to the 
>> headphone socket of your iPhone. The primary way the audio routing bug 
>> manifests itself is when you receive an incoming phone or FaceTime call. You 
>> can usually hear if you're going to be affected by the bug because your 
>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>> audio to fade in and out when audio ducking is enabled. At this point, if 
>> you press the power button to silence the ringer and then flick through the 
>> screen, you will find that not only has VOiceOver become unresponsive, but 
>> the entire phone has as well.
>> If you don't press the power button while the phone is ringing, but instead 
>> opt to flick through the iPHone's screen to locate the Answer button or 
>> review caller ID information, VoiceOver may not speak at all.
>> Finally, if you attempt to answer the incoming call with a two-finger 
>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>> up.
>> The bottom line is that if you have earbuds connected, you may not be able 
>> to answer a call.
>> Some people have also reported similar problems answering calls when their 
>> phone is set to silent.
>> If you rely on your phone for business or safety, this could be a deal 
>> breaker in terms of upgrading at this point.
>> What makes this bug so fascinating is that not only is it completely absent 
>> for some people, but of those who experience it, not all symptoms are 
>> present for all users. For example, some people experience the issues I have 
>> described when they press the power button to mute the ringer, but not when 
>> the phone is ringing. Others can answer a call by pressing the button on 
>> their EarPods, while others cannot.
>> If you upgrade and are affected by this, here are a few things to try.
>> (A) If you have the more moderate version of this bug, avoid pressing the 
>> power button when you receive an incoming call.
>> (B) Turning off audio ducking seems to help a little for some users.
>> (C) If you can't answer a call with a two-finger double-tap, try pressing 
>>

Re: My top iOS 9 Bugs

[Nancy Feldman]

I haven't noticed any sluggishness with the male Siri voice when I'm using it 
for Voiceover. It seems fine.

> On Sep 16, 2015, at 19:48, John Diakogeorgiou <jdiakoge2...@gmail.com> wrote:
> 
> I find it works well but will try another voice to see if I am wrong.
> 
> On 9/16/15, Shai <shai...@gmail.com> wrote:
>> Hi,
>> The setting of the Siri voices for VoiceOver was mentioned on
>> AppleVis; however, it was also indicated that the responsiveness is
>> quite sluggish while navigating.
>> Have you noticed this?
>> 
>> 
>> On 9/16/15, John Diakogeorgiou <jdiakoge2...@gmail.com> wrote:
>>> I've been using a VaroUltra and it works fine. Also one thing which no
>>> one has mentioned is that you can now use the Siri male and female
>>> voices for voice over. Just know that the male voice pronounces some
>>> vowels strangely.
>>> 
>>> On 9/16/15, Jonathan Mosen <jmo...@mosen.org> wrote:
>>>> Hi Neal. My understanding is that if you are affected, it will also
>>>> happen
>>>> if you have your phone on silent. If you just have your phone unmuted
>>>> and
>>>> on
>>>> speaker, it appears to be OK as far as I know.
>>>> Jonathan Mosen
>>>> Mosen Consulting
>>>> Blindness technology eBooks, tutorials and training
>>>> http://Mosen.org
>>>> 
>>>>> On 17/09/2015, at 9:38 AM, Neal Ewers <neal.ew...@ravenswood.org>
>>>>> wrote:
>>>>> 
>>>>> Jonathan. Is this phone problem a problem only when using something
>>>>> connected to the phone such as ear buds or a bluetooth device? Or, does
>>>>> it
>>>>> also effect phone calls if you are using none of these devices and only
>>>>> using the microphone and speaker in the phone?
>>>>> 
>>>>> Thanks.
>>>>> 
>>>>> Neal
>>>>> 
>>>>> 
>>>>> From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>>>>> [mailto:viphone@googlegroups.com <mailto:viphone@googlegroups.com>] On
>>>>> Behalf Of Jonathan Mosen
>>>>> Sent: Wednesday, September 16, 2015 12:15 PM
>>>>> To: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>>>>> Subject: My top iOS 9 Bugs
>>>>> 
>>>>> Hi everyone, now that the NDA is lifted, here are some things I think
>>>>> you
>>>>> might like to be aware of in iOS 9.
>>>>> I am enthusiastic about iOS 9. It is significantly more responsive than
>>>>> its predecessor, and there are many new features that I'm sure you'll
>>>>> enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 9 that
>>>>> range from minor annoyances to potentially critical, depending on how
>>>>> you
>>>>> use your device and whether you find yourself affected. Here are just a
>>>>> few that you might like to take into consideration before deciding
>>>>> whether
>>>>> to wait for a bug fix release before installing iOS 9. Remember that a
>>>>> few
>>>>> days following iOS 9's release, it will not be possible to downgrade
>>>>> again, so you should consider the upgrade to iOS 9 a one-way trip, and
>>>>> proceed with caution if anything below concerns you.
>>>>> 1. Audio routing bug. This is potentially the most significant
>>>>> accessibility bug I can recall ever to slip through an iOS release, due
>>>>> to
>>>>> the number of people who may be affected. Not everyone will be, and at
>>>>> present, even after extensive testing with a range of people owning
>>>>> different devices, I have no information about why it affects some
>>>>> users,
>>>>> but not others. It is not device specific, for example it is happening
>>>>> to
>>>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the
>>>>> problem
>>>>> isn't so severe. Nor does it seem to be affected by any setting. If
>>>>> you're
>>>>> lucky, it won't happen to you, but the only way I am aware of to
>>>>> determine
>>>>> this is to upgrade.
>>>>> This bug may affect you when you have earbuds or headphones connected
>>>>> to
>>>>> the headphone socket of your iPhone. The primary way the audio routing

Re: My top iOS 9 Bugs

[Christopher Chaltain]

com
<mailto:viphone@googlegroups.com>[mailto:viphone@googlegroups.com
<mailto:viphone@googlegroups.com>] On Behalf Of Jonathan Mosen
Sent: Wednesday, September 16, 2015 10:15 AM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
Subject: My top iOS 9 Bugs

Hi everyone, now that the NDA is lifted, here are some things I think
you
might like to be aware of in iOS 9.
I am enthusiastic about iOS 9. It is significantly more responsive than
its predecessor, and there are many new features that I'm sure you'll
enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 9 that
range from minor annoyances to potentially critical, depending on how
you
use your device and whether you find yourself affected. Here are just a
few that you might like to take into consideration before deciding
whether to wait for a bug fix release before installing iOS 9. Remember
that a few days following iOS 9's release, it will not be possible to
downgrade again, so you should consider the upgrade to iOS 9 a one-way
trip, and proceed with caution if anything below concerns you.
1. Audio routing bug. This is potentially the most significant
accessibility bug I can recall ever to slip through an iOS release, due
to the number of people who may be affected. Not everyone will be, and
at
present, even after extensive testing with a range of people owning
different devices, I have no information about why it affects some
users,
but not others. It is not device specific, for example it is happening
to
me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the
problem
isn't so severe. Nor does it seem to be affected by any setting. If
you're lucky, it won't happen to you, but the only way I am aware of to
determine this is to upgrade.
This bug may affect you when you have earbuds or headphones connected
to
the headphone socket of your iPhone. The primary way the audio routing
bug manifests itself is when you receive an incoming phone or FaceTime
call. You can usually hear if you're going to be affected by the bug
because your ring-tone will fade in and out, rather like the way
VOiceOver causes system audio to fade in and out when audio ducking is
enabled. At this point, if you press the power button to silence the
ringer and then flick through the screen, you will find that not only
has
VOiceOver become unresponsive, but the entire phone has as well.
If you don't press the power button while the phone is ringing, but
instead opt to flick through the iPHone's screen to locate the Answer
button or review caller ID information, VoiceOver may not speak at all.
Finally, if you attempt to answer the incoming call with a two-finger
double-tap, you may not be able to, since VoiceOver has effectively
locked up.
The bottom line is that if you have earbuds connected, you may not be
able to answer a call.
Some people have also reported similar problems answering calls when
their phone is set to silent.
If you rely on your phone for business or safety, this could be a deal
breaker in terms of upgrading at this point.
What makes this bug so fascinating is that not only is it completely
absent for some people, but of those who experience it, not all
symptoms
are present for all users. For example, some people experience the
issues
I have described when they press the power button to mute the ringer,
but
not when the phone is ringing. Others can answer a call by pressing the
button on their EarPods, while others cannot.
If you upgrade and are affected by this, here are a few things to try.
(A) If you have the more moderate version of this bug, avoid pressing
the
power button when you receive an incoming call.
(B) Turning off audio ducking seems to help a little for some users.
(C) If you can't answer a call with a two-finger double-tap, try
pressing
the button on your EarPods or similar device if you have such a device
connected.
(D) If all else fails, you can disconnect any device from the headphone
jack, answer the call with a two-finger double-tap, then reconnect the
device to the headphone jack.
(E) Given the critical nature of this bug, if you've upgraded and now
find yourself afflicted by it, enrol in the iOS beta program so you can
receive early copies of any fixes Apple is working on. But keep in mind
that since you will be running beta software, you may well be swapping
one set of bugs for another.
2. Bluetooth keyboard support unreliable. Sometimes, users may input
double letters when typing. This is a bug that was introduced in the
iOS
8 cycle, and can easily be worked around by toggling VoiceOver off and
on.
However, a new bug now exists where at times, no text is entered into a
field at all when VO is active. Toggling VO doesn't help, nor does
switching the keyboard off and on. The only immediate remedy is to turn
Vo off, and keep typing without it. If you turn VO back on again, the
arrow keys don't work when you're trying to navigate your text, and you
can't edit it.
3. In the Today view of Notification Cente

Re: My top iOS 9 Bugs

[Nancy Feldman]

For what it's worth, I've successfully upgraded and received three phone calls. 
None of them has resulted in unusual or unstable behavior from the phone and I 
was able to answer it from the earbuds and from the screen.

I appreciate being made aware of the possibility, but I opted to take my 
chances, and have no concerns so far.

> On Sep 16, 2015, at 11:52, Jenifer Barr <claudas...@gmail.com> wrote:
> 
> Wow Jonathan!!! Thanks for the list. While I gladly bought your book... I'll 
> wait for the next version hopefully in a week or so!! 
> 
> Jenifer Barr
> Sent from my iPhone
> 
> On Sep 16, 2015, at 1:33 PM, Cristóbal <crismuno...@gmail.com 
> <mailto:crismuno...@gmail.com>> wrote:
> 
>> Geez. So I think I’m going to wait for the first 9.x update. Significatn 
>> bugs for sure. 
>>  
>> From: viphone@googlegroups.com 
>> <mailto:viphone@googlegroups.com>[mailto:viphone@googlegroups.com 
>> <mailto:viphone@googlegroups.com>] On Behalf Of Jonathan Mosen
>> Sent: Wednesday, September 16, 2015 10:15 AM
>> To: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>> Subject: My top iOS 9 Bugs
>>  
>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>> might like to be aware of in iOS 9.
>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>> minor annoyances to potentially critical, depending on how you use your 
>> device and whether you find yourself affected. Here are just a few that you 
>> might like to take into consideration before deciding whether to wait for a 
>> bug fix release before installing iOS 9. Remember that a few days following 
>> iOS 9's release, it will not be possible to downgrade again, so you should 
>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>> anything below concerns you.
>> 1. Audio routing bug. This is potentially the most significant accessibility 
>> bug I can recall ever to slip through an iOS release, due to the number of 
>> people who may be affected. Not everyone will be, and at present, even after 
>> extensive testing with a range of people owning different devices, I have no 
>> information about why it affects some users, but not others. It is not 
>> device specific, for example it is happening to me on my iPhone 6 Plus, but 
>> I know iPhone 6 Plus users where the problem isn't so severe. Nor does it 
>> seem to be affected by any setting. If you're lucky, it won't happen to you, 
>> but the only way I am aware of to determine this is to upgrade.
>> This bug may affect you when you have earbuds or headphones connected to the 
>> headphone socket of your iPhone. The primary way the audio routing bug 
>> manifests itself is when you receive an incoming phone or FaceTime call. You 
>> can usually hear if you're going to be affected by the bug because your 
>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>> audio to fade in and out when audio ducking is enabled. At this point, if 
>> you press the power button to silence the ringer and then flick through the 
>> screen, you will find that not only has VOiceOver become unresponsive, but 
>> the entire phone has as well.
>> If you don't press the power button while the phone is ringing, but instead 
>> opt to flick through the iPHone's screen to locate the Answer button or 
>> review caller ID information, VoiceOver may not speak at all.
>> Finally, if you attempt to answer the incoming call with a two-finger 
>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>> up.
>> The bottom line is that if you have earbuds connected, you may not be able 
>> to answer a call.
>> Some people have also reported similar problems answering calls when their 
>> phone is set to silent.
>> If you rely on your phone for business or safety, this could be a deal 
>> breaker in terms of upgrading at this point.
>> What makes this bug so fascinating is that not only is it completely absent 
>> for some people, but of those who experience it, not all symptoms are 
>> present for all users. For example, some people experience the issues I have 
>> described when they press the power button to mute the ringer, but not when 
>> the phone is ringing. Others can answer a call by pressing the button on 
>> their EarPods, while others cannot.
>> If you upgrade and are affected by this, here are a few things to try.
>&

Re: My top iOS 9 Bugs

[John Diakogeorgiou]

I have not seen Harry's problem either.

On 9/16/15, John Diakogeorgiou <jdiakoge2...@gmail.com> wrote:
> Jonathan thanks for the bug report. I can confirm point 4. It is very
> frustrating when I am trying to make a call and it always goes to the
> top of my contact list. I have not tried using ear buds. I will say
> though that I haven't had any problems using a Bluetooth ear piece. I
> am able to answer calls just fine.
> In general the new software is much better than version 8.
>
> On 9/16/15, Nancy Feldman <lorav...@gmail.com> wrote:
>> For what it's worth, I've successfully upgraded and received three phone
>> calls. None of them has resulted in unusual or unstable behavior from the
>> phone and I was able to answer it from the earbuds and from the screen.
>>
>> I appreciate being made aware of the possibility, but I opted to take my
>> chances, and have no concerns so far.
>>
>>> On Sep 16, 2015, at 11:52, Jenifer Barr <claudas...@gmail.com> wrote:
>>>
>>> Wow Jonathan!!! Thanks for the list. While I gladly bought your book...
>>> I'll wait for the next version hopefully in a week or so!!
>>>
>>> Jenifer Barr
>>> Sent from my iPhone
>>>
>>> On Sep 16, 2015, at 1:33 PM, Cristóbal <crismuno...@gmail.com
>>> <mailto:crismuno...@gmail.com>> wrote:
>>>
>>>> Geez. So I think I’m going to wait for the first 9.x update.
>>>> Significatn
>>>> bugs for sure.
>>>>
>>>> From: viphone@googlegroups.com
>>>> <mailto:viphone@googlegroups.com>[mailto:viphone@googlegroups.com
>>>> <mailto:viphone@googlegroups.com>] On Behalf Of Jonathan Mosen
>>>> Sent: Wednesday, September 16, 2015 10:15 AM
>>>> To: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>>>> Subject: My top iOS 9 Bugs
>>>>
>>>> Hi everyone, now that the NDA is lifted, here are some things I think
>>>> you
>>>> might like to be aware of in iOS 9.
>>>> I am enthusiastic about iOS 9. It is significantly more responsive than
>>>> its predecessor, and there are many new features that I'm sure you'll
>>>> enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 9 that
>>>> range from minor annoyances to potentially critical, depending on how
>>>> you
>>>> use your device and whether you find yourself affected. Here are just a
>>>> few that you might like to take into consideration before deciding
>>>> whether to wait for a bug fix release before installing iOS 9. Remember
>>>> that a few days following iOS 9's release, it will not be possible to
>>>> downgrade again, so you should consider the upgrade to iOS 9 a one-way
>>>> trip, and proceed with caution if anything below concerns you.
>>>> 1. Audio routing bug. This is potentially the most significant
>>>> accessibility bug I can recall ever to slip through an iOS release, due
>>>> to the number of people who may be affected. Not everyone will be, and
>>>> at
>>>> present, even after extensive testing with a range of people owning
>>>> different devices, I have no information about why it affects some
>>>> users,
>>>> but not others. It is not device specific, for example it is happening
>>>> to
>>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the
>>>> problem
>>>> isn't so severe. Nor does it seem to be affected by any setting. If
>>>> you're lucky, it won't happen to you, but the only way I am aware of to
>>>> determine this is to upgrade.
>>>> This bug may affect you when you have earbuds or headphones connected
>>>> to
>>>> the headphone socket of your iPhone. The primary way the audio routing
>>>> bug manifests itself is when you receive an incoming phone or FaceTime
>>>> call. You can usually hear if you're going to be affected by the bug
>>>> because your ring-tone will fade in and out, rather like the way
>>>> VOiceOver causes system audio to fade in and out when audio ducking is
>>>> enabled. At this point, if you press the power button to silence the
>>>> ringer and then flick through the screen, you will find that not only
>>>> has
>>>> VOiceOver become unresponsive, but the entire phone has as well.
>>>> If you don't press the power button while the phone is ringing, but
>>>> instead opt to flick through the iPHone's screen to locate the A

Re: My top iOS 9 Bugs

[christopher hallsworth]

I believe this bug is not device specific nor is it situation specific. It will 
only rear its ugly head if the ringtone fades in and out as if VoiceOver is 
ducking system or other audio.
> On 16 Sep 2015, at 19:11, Nancy Feldman <lorav...@gmail.com> wrote:
> 
> For what it's worth, I've successfully upgraded and received three phone 
> calls. None of them has resulted in unusual or unstable behavior from the 
> phone and I was able to answer it from the earbuds and from the screen.
> 
> I appreciate being made aware of the possibility, but I opted to take my 
> chances, and have no concerns so far.
> 
>> On Sep 16, 2015, at 11:52, Jenifer Barr <claudas...@gmail.com 
>> <mailto:claudas...@gmail.com>> wrote:
>> 
>> Wow Jonathan!!! Thanks for the list. While I gladly bought your book... I'll 
>> wait for the next version hopefully in a week or so!! 
>> 
>> Jenifer Barr
>> Sent from my iPhone
>> 
>> On Sep 16, 2015, at 1:33 PM, Cristóbal <crismuno...@gmail.com 
>> <mailto:crismuno...@gmail.com>> wrote:
>> 
>>> Geez. So I think I’m going to wait for the first 9.x update. Significatn 
>>> bugs for sure. 
>>>  
>>> From: viphone@googlegroups.com 
>>> <mailto:viphone@googlegroups.com>[mailto:viphone@googlegroups.com 
>>> <mailto:viphone@googlegroups.com>] On Behalf Of Jonathan Mosen
>>> Sent: Wednesday, September 16, 2015 10:15 AM
>>> To: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>>> Subject: My top iOS 9 Bugs
>>>  
>>> Hi everyone, now that the NDA is lifted, here are some things I think you 
>>> might like to be aware of in iOS 9.
>>> I am enthusiastic about iOS 9. It is significantly more responsive than its 
>>> predecessor, and there are many new features that I'm sure you'll enjoy. 
>>> Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
>>> minor annoyances to potentially critical, depending on how you use your 
>>> device and whether you find yourself affected. Here are just a few that you 
>>> might like to take into consideration before deciding whether to wait for a 
>>> bug fix release before installing iOS 9. Remember that a few days following 
>>> iOS 9's release, it will not be possible to downgrade again, so you should 
>>> consider the upgrade to iOS 9 a one-way trip, and proceed with caution if 
>>> anything below concerns you.
>>> 1. Audio routing bug. This is potentially the most significant 
>>> accessibility bug I can recall ever to slip through an iOS release, due to 
>>> the number of people who may be affected. Not everyone will be, and at 
>>> present, even after extensive testing with a range of people owning 
>>> different devices, I have no information about why it affects some users, 
>>> but not others. It is not device specific, for example it is happening to 
>>> me on my iPhone 6 Plus, but I know iPhone 6 Plus users where the problem 
>>> isn't so severe. Nor does it seem to be affected by any setting. If you're 
>>> lucky, it won't happen to you, but the only way I am aware of to determine 
>>> this is to upgrade.
>>> This bug may affect you when you have earbuds or headphones connected to 
>>> the headphone socket of your iPhone. The primary way the audio routing bug 
>>> manifests itself is when you receive an incoming phone or FaceTime call. 
>>> You can usually hear if you're going to be affected by the bug because your 
>>> ring-tone will fade in and out, rather like the way VOiceOver causes system 
>>> audio to fade in and out when audio ducking is enabled. At this point, if 
>>> you press the power button to silence the ringer and then flick through the 
>>> screen, you will find that not only has VOiceOver become unresponsive, but 
>>> the entire phone has as well.
>>> If you don't press the power button while the phone is ringing, but instead 
>>> opt to flick through the iPHone's screen to locate the Answer button or 
>>> review caller ID information, VoiceOver may not speak at all.
>>> Finally, if you attempt to answer the incoming call with a two-finger 
>>> double-tap, you may not be able to, since VoiceOver has effectively locked 
>>> up.
>>> The bottom line is that if you have earbuds connected, you may not be able 
>>> to answer a call.
>>> Some people have also reported similar problems answering calls when their 
>>> phone is set to silent.
>>> If you rely on your phone for business or safety, this could be

Re: My top iOS 9 Bugs

[Mary Otten]

OK, here is the question. Perhaps really it is a rhetorical one. One of the 
things they used to say with justification, about windows, was that part of the 
problem was that there was such a proliferation of hardware and software. 
Microsoft had to worry about all these various configurations. No wonder it 
wasn't stable, and bugs were hard to reproduce. So here is Apple. Relatively 
few types of iOS device are present. Yet we are seeing reports of bugs that 
show up here and not there and I have a question. Why? Apple controls the 
hardware and they control the OS. If there is a bug, shouldn't it at least show 
up on all of a given device say an iPhone 6 Plus? Or an iPad mini? I wonder 
what happens if you take your device that is exhibiting a bug, and to strip it 
back down to where it only has the things that Apple offers. Does the bug go 
away? Is there some sort of interaction between certain software and voiceover 
or the OS or whatever that cause is bugs to appear on some peoples devices and 
not others? This really does not seem to make very much sense.
Mary

Sent from my iPhone

> On Sep 16, 2015, at 11:38 AM, John Diakogeorgiou <jdiakoge2...@gmail.com> 
> wrote:
> 
> I have not seen Harry's problem either.
> 
>> On 9/16/15, John Diakogeorgiou <jdiakoge2...@gmail.com> wrote:
>> Jonathan thanks for the bug report. I can confirm point 4. It is very
>> frustrating when I am trying to make a call and it always goes to the
>> top of my contact list. I have not tried using ear buds. I will say
>> though that I haven't had any problems using a Bluetooth ear piece. I
>> am able to answer calls just fine.
>> In general the new software is much better than version 8.
>> 
>>> On 9/16/15, Nancy Feldman <lorav...@gmail.com> wrote:
>>> For what it's worth, I've successfully upgraded and received three phone
>>> calls. None of them has resulted in unusual or unstable behavior from the
>>> phone and I was able to answer it from the earbuds and from the screen.
>>> 
>>> I appreciate being made aware of the possibility, but I opted to take my
>>> chances, and have no concerns so far.
>>> 
>>>> On Sep 16, 2015, at 11:52, Jenifer Barr <claudas...@gmail.com> wrote:
>>>> 
>>>> Wow Jonathan!!! Thanks for the list. While I gladly bought your book...
>>>> I'll wait for the next version hopefully in a week or so!!
>>>> 
>>>> Jenifer Barr
>>>> Sent from my iPhone
>>>> 
>>>> On Sep 16, 2015, at 1:33 PM, Cristóbal <crismuno...@gmail.com
>>>> <mailto:crismuno...@gmail.com>> wrote:
>>>> 
>>>>> Geez. So I think I’m going to wait for the first 9.x update.
>>>>> Significatn
>>>>> bugs for sure.
>>>>> 
>>>>> From: viphone@googlegroups.com
>>>>> <mailto:viphone@googlegroups.com>[mailto:viphone@googlegroups.com
>>>>> <mailto:viphone@googlegroups.com>] On Behalf Of Jonathan Mosen
>>>>> Sent: Wednesday, September 16, 2015 10:15 AM
>>>>> To: viphone@googlegroups.com <mailto:viphone@googlegroups.com>
>>>>> Subject: My top iOS 9 Bugs
>>>>> 
>>>>> Hi everyone, now that the NDA is lifted, here are some things I think
>>>>> you
>>>>> might like to be aware of in iOS 9.
>>>>> I am enthusiastic about iOS 9. It is significantly more responsive than
>>>>> its predecessor, and there are many new features that I'm sure you'll
>>>>> enjoy. Unfortunately, there are also some VoiceOver bugs in iOS 9 that
>>>>> range from minor annoyances to potentially critical, depending on how
>>>>> you
>>>>> use your device and whether you find yourself affected. Here are just a
>>>>> few that you might like to take into consideration before deciding
>>>>> whether to wait for a bug fix release before installing iOS 9. Remember
>>>>> that a few days following iOS 9's release, it will not be possible to
>>>>> downgrade again, so you should consider the upgrade to iOS 9 a one-way
>>>>> trip, and proceed with caution if anything below concerns you.
>>>>> 1. Audio routing bug. This is potentially the most significant
>>>>> accessibility bug I can recall ever to slip through an iOS release, due
>>>>> to the number of people who may be affected. Not everyone will be, and
>>>>> at
>>>>> present, even after extensive testing with a range of people owning
>>>>> different devices, I have no informat

My top iOS 9 Bugs

[Jonathan Mosen]

Hi everyone, now that the NDA is lifted, here are some things I think you might 
like to be aware of in iOS 9.
I am enthusiastic about iOS 9. It is significantly more responsive than its 
predecessor, and there are many new features that I'm sure you'll enjoy. 
Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
minor annoyances to potentially critical, depending on how you use your device 
and whether you find yourself affected. Here are just a few that you might like 
to take into consideration before deciding whether to wait for a bug fix 
release before installing iOS 9. Remember that a few days following iOS 9's 
release, it will not be possible to downgrade again, so you should consider the 
upgrade to iOS 9 a one-way trip, and proceed with caution if anything below 
concerns you.
1. Audio routing bug. This is potentially the most significant accessibility 
bug I can recall ever to slip through an iOS release, due to the number of 
people who may be affected. Not everyone will be, and at present, even after 
extensive testing with a range of people owning different devices, I have no 
information about why it affects some users, but not others. It is not device 
specific, for example it is happening to me on my iPhone 6 Plus, but I know 
iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to be 
affected by any setting. If you're lucky, it won't happen to you, but the only 
way I am aware of to determine this is to upgrade.
This bug may affect you when you have earbuds or headphones connected to the 
headphone socket of your iPhone. The primary way the audio routing bug 
manifests itself is when you receive an incoming phone or FaceTime call. You 
can usually hear if you're going to be affected by the bug because your 
ring-tone will fade in and out, rather like the way VOiceOver causes system 
audio to fade in and out when audio ducking is enabled. At this point, if you 
press the power button to silence the ringer and then flick through the screen, 
you will find that not only has VOiceOver become unresponsive, but the entire 
phone has as well.
If you don't press the power button while the phone is ringing, but instead opt 
to flick through the iPHone's screen to locate the Answer button or review 
caller ID information, VoiceOver may not speak at all.
Finally, if you attempt to answer the incoming call with a two-finger 
double-tap, you may not be able to, since VoiceOver has effectively locked up.
The bottom line is that if you have earbuds connected, you may not be able to 
answer a call.
Some people have also reported similar problems answering calls when their 
phone is set to silent.
If you rely on your phone for business or safety, this could be a deal breaker 
in terms of upgrading at this point.
What makes this bug so fascinating is that not only is it completely absent for 
some people, but of those who experience it, not all symptoms are present for 
all users. For example, some people experience the issues I have described when 
they press the power button to mute the ringer, but not when the phone is 
ringing. Others can answer a call by pressing the button on their EarPods, 
while others cannot.
If you upgrade and are affected by this, here are a few things to try.
(A) If you have the more moderate version of this bug, avoid pressing the power 
button when you receive an incoming call.
(B) Turning off audio ducking seems to help a little for some users.
(C) If you can't answer a call with a two-finger double-tap, try pressing the 
button on your EarPods or similar device if you have such a device connected.
(D) If all else fails, you can disconnect any device from the headphone jack, 
answer the call with a two-finger double-tap, then reconnect the device to the 
headphone jack.
(E) Given the critical nature of this bug, if you've upgraded and now find 
yourself afflicted by it, enrol in the iOS beta program so you can receive 
early copies of any fixes Apple is working on. But keep in mind that since you 
will be running beta software, you may well be swapping one set of bugs for 
another.
2. Bluetooth keyboard support unreliable. Sometimes, users may input double 
letters when typing. This is a bug that was introduced in the iOS 8 cycle, and 
can easily be worked around by toggling VoiceOver off and on.
However, a new bug now exists where at times, no text is entered into a field 
at all when VO is active. Toggling VO doesn't help, nor does switching the 
keyboard off and on. The only immediate remedy is to turn Vo off, and keep 
typing without it. If you turn VO back on again, the arrow keys don't work when 
you're trying to navigate your text, and you can't edit it.
3. In the Today view of Notification Center, VO frequently restarts itself when 
flicking through your widgets, and sometimes the phone locks up entirely.
4. It's much less likely you can return to your previous position on screen 
after taking an action. For example, flick 

RE: My top iOS 9 Bugs

[Cristóbal]

Geez. So I think I’m going to wait for the first 9.x update. Significatn bugs 
for sure. 

 

From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf Of 
Jonathan Mosen
Sent: Wednesday, September 16, 2015 10:15 AM
To: viphone@googlegroups.com
Subject: My top iOS 9 Bugs

 

Hi everyone, now that the NDA is lifted, here are some things I think you might 
like to be aware of in iOS 9.

I am enthusiastic about iOS 9. It is significantly more responsive than its 
predecessor, and there are many new features that I'm sure you'll enjoy. 
Unfortunately, there are also some VoiceOver bugs in iOS 9 that range from 
minor annoyances to potentially critical, depending on how you use your device 
and whether you find yourself affected. Here are just a few that you might like 
to take into consideration before deciding whether to wait for a bug fix 
release before installing iOS 9. Remember that a few days following iOS 9's 
release, it will not be possible to downgrade again, so you should consider the 
upgrade to iOS 9 a one-way trip, and proceed with caution if anything below 
concerns you.

1. Audio routing bug. This is potentially the most significant accessibility 
bug I can recall ever to slip through an iOS release, due to the number of 
people who may be affected. Not everyone will be, and at present, even after 
extensive testing with a range of people owning different devices, I have no 
information about why it affects some users, but not others. It is not device 
specific, for example it is happening to me on my iPhone 6 Plus, but I know 
iPhone 6 Plus users where the problem isn't so severe. Nor does it seem to be 
affected by any setting. If you're lucky, it won't happen to you, but the only 
way I am aware of to determine this is to upgrade.

This bug may affect you when you have earbuds or headphones connected to the 
headphone socket of your iPhone. The primary way the audio routing bug 
manifests itself is when you receive an incoming phone or FaceTime call. You 
can usually hear if you're going to be affected by the bug because your 
ring-tone will fade in and out, rather like the way VOiceOver causes system 
audio to fade in and out when audio ducking is enabled. At this point, if you 
press the power button to silence the ringer and then flick through the screen, 
you will find that not only has VOiceOver become unresponsive, but the entire 
phone has as well.

If you don't press the power button while the phone is ringing, but instead opt 
to flick through the iPHone's screen to locate the Answer button or review 
caller ID information, VoiceOver may not speak at all.

Finally, if you attempt to answer the incoming call with a two-finger 
double-tap, you may not be able to, since VoiceOver has effectively locked up.

The bottom line is that if you have earbuds connected, you may not be able to 
answer a call.

Some people have also reported similar problems answering calls when their 
phone is set to silent.

If you rely on your phone for business or safety, this could be a deal breaker 
in terms of upgrading at this point.

What makes this bug so fascinating is that not only is it completely absent for 
some people, but of those who experience it, not all symptoms are present for 
all users. For example, some people experience the issues I have described when 
they press the power button to mute the ringer, but not when the phone is 
ringing. Others can answer a call by pressing the button on their EarPods, 
while others cannot.

If you upgrade and are affected by this, here are a few things to try.

(A) If you have the more moderate version of this bug, avoid pressing the power 
button when you receive an incoming call.

(B) Turning off audio ducking seems to help a little for some users.

(C) If you can't answer a call with a two-finger double-tap, try pressing the 
button on your EarPods or similar device if you have such a device connected.

(D) If all else fails, you can disconnect any device from the headphone jack, 
answer the call with a two-finger double-tap, then reconnect the device to the 
headphone jack.

(E) Given the critical nature of this bug, if you've upgraded and now find 
yourself afflicted by it, enrol in the iOS beta program so you can receive 
early copies of any fixes Apple is working on. But keep in mind that since you 
will be running beta software, you may well be swapping one set of bugs for 
another.

2. Bluetooth keyboard support unreliable. Sometimes, users may input double 
letters when typing. This is a bug that was introduced in the iOS 8 cycle, and 
can easily be worked around by toggling VoiceOver off and on.

However, a new bug now exists where at times, no text is entered into a field 
at all when VO is active. Toggling VO doesn't help, nor does switching the 
keyboard off and on. The only immediate remedy is to turn Vo off, and keep 
typing without it. If you turn VO back on again, the arrow keys don't work when 
you're trying