If you have been following this thread, you might be interested to know that
the issue which sparked it off seems to have for the moment resolved itself. I
have been happily reading books and magazines with the Kindle app without the
Right Pan button skipping. I am hoping it doesn't rear its ugly head again.
My sympathies go out to Ibrahim unable to use his Braille display. Having so
recently purchased mine, I am sure I now wouldn't like to be without it.
Iain
On 10 Jan 2017, at 7:35 pm, Ian Macrae (Redacted sender "ian.macrae1" for
DMARC) <dmarc-noreply@xxxxxxxxxxxxx> wrote:
And of course it’s worth making the point that those of us with Braillenote
Touch 18 cell models cannot and never have been able to connect our device to
our IOS products having been expressly told by Humanware that we would be able
to do so following an upgrade to their proprietory OS in the autumn of last
year. Deeply frustrating and highly annoying.
Ian Macrae
ian.macrae1@xxxxxxx
On 10 Jan 2017, at 19:30, Ibrahim § <ibrahim_gucukoglu@xxxxxxxx> wrote:
Hi Ian.
No, there hasn't been any update from Apple or Freedom Scientific to my
knowledge regarding this. I am in the unfortunate position of having a Focus
braille display but cannot pair it to my iPhone 7 because I am running iOS
10.2 and have not paired my braille display to my phone in some time, having
previously deleted the pairing. This means I cant use my nearly 2000 pound
braille display with my iPhone which I am pissed off about, to put it very
mildly. Of course its easy to blame apple, however Freedom Scientific could
offer a firmware update to resolve this problem, just as apple could issue a
software patch. We'll have to see who plays first but until then, my Braille
display is sitting pretty in a bag.
All the best, Ibrahim.
-----Original Message----- From: Iain Lackie
Sent: Tuesday, January 10, 2017 11:16 AM
To: access-uk@xxxxxxxxxxxxx
Subject: [access-uk] Re: Focus Blue
From what I read, there are no problems with iOS10.2 if you update and your
device was already paired. I have found this to be the case. It seemed the
issue was with pairing a new Focus or pairing a focus after it had been
unpaired. There was a post from Freedom about this but I don't know if there
have been any updates to it.
Iain
On 10 Jan 2017, at 11:02 am, Jackie Brown <jackieannbrown62@xxxxxxxxx> wrote:
No problem Terry, thanks for clarification.
Kind regards,
Jackie Brown
Email: Jackieannbrown62@xxxxxxxxx
Check out my website: www.thebrownsplace.info
Follow me on Twitter: @thebrownsplace
Skype name: thejackmate
-----Original Message-----
From: access-uk@xxxxxxxxxxxxx [mailto:access-uk@xxxxxxxxxxxxx] On Behalf Of ;
Terry clasper (Redacted sender "terry.clasper" for DMARC)
Sent: 10 January 2017 10:49
