Hi Scott,
I'm using a different display than you, so I don't know if this matters. I have
found that I have to do the pairing as you described if I have connected my
display to another device, such as my iPhone. If, however, I forget the iPhone
pairing and only pair with the fire, I can turn the display off and back on and
the pairing is fine. Even with the iPhone turned totally off, as long as my
display has been paired with that device, I can't get it to reconnect with the
fire unless I totally forget the other pairing. I don't think I have the new
braille commands. I only have the sort of reading support that was introduced
early last summer. What version of fire OS do you have? I wonder if there is a
way to turn off auto correct. That might stop the jumping problem.I would be
tempted to send bug reports directly to Peter corn, rather than to the device
Accessibility address, just because the responses I have gotten from that
address have been less than wonderful. If you sent it directly to Peter, you
know it would be going to a good place. Do you have his address or do you need
it? Maybe somebody else has more information on bug reporting channels.
Mary
Sent from my iPhone
On Oct 6, 2017, at 6:19 AM, Scott Davert <kc8pnl@xxxxxxxxx> wrote:
Hello all.
It's possible that some of you may already be familiar with me from
AppleVis or Blindbargains. I currently live in Charlotte NC and work
for the state of NC.
Anyway, I'm now on the Kindle bandwagon and am finding some good and
bad with braille.
First, at least with my VarioConnect 32, each time I reboot the
Kindle, I need to have the VarioConnect pairing forgotten under
wireless>bluetooth and then repair it through VoiceView each time. Is
anyone finding this with other displays? Is there some sort of place
we can file bug reports?
The other issue I'm having, which I know isn't unituqe to me from what
I've read, is that each time I type something, either with the
BrailleBack for Kindle app or the native support with VoiceView,
autocorrect keeps coming up and taking me out of the text field. I'm
also finding that some of the navigation commands appear not to be
working. Over all, though, I find this to be a much better braille
experience than BrailleBack on Android, but not quite up to par with
iOS. Then again, Apple have been developing braille support since
2009, whereas, Amazon has been doing this since the spring, so I'm
quite optomistic in its ftuture!
Scott
