I just had to reinstall the team talk app for iOS on my iPhone, and I used to be able to use a 2-finger double-tap to unkey after I finished talking and that isn't working anymore. Where is that option in the app?
Try keeping the Voice-Over focus on the talk key and using a single finger double tap. Or, you can just do what I do, which is to use a Bluetooth keyboard. Use the up and down arrow keys at the same time to operate the toggle to transmit or to stop transmitting.
I do try to keep voiceover focused on the talk key but for some reason the focus often gets moved elsewhere. It's much easier for me to do the 2-finger double-tap when the app is set up for that, but I had to uninstall and reinstall team talk the other day and set it up again, and yesterday while I was chatting with friends the 2-finger double-tap wasn't working.
In preferences under the general heading, there's an option called "Headset TX toggle". Once turned on, your two-finger double-tap should begin working again.
The app creator evidently didn't want anybody to know about that feature, I originally found out about it a few years ago from a friend so I knew about it but it certainly isn't labeled very well.
Comments
thoughts
Try keeping the Voice-Over focus on the talk key and using a single finger double tap. Or, you can just do what I do, which is to use a Bluetooth keyboard. Use the up and down arrow keys at the same time to operate the toggle to transmit or to stop transmitting.
thanks but...
I do try to keep voiceover focused on the talk key but for some reason the focus often gets moved elsewhere. It's much easier for me to do the 2-finger double-tap when the app is set up for that, but I had to uninstall and reinstall team talk the other day and set it up again, and yesterday while I was chatting with friends the 2-finger double-tap wasn't working.
There's a preference for that
In preferences under the general heading, there's an option called "Headset TX toggle". Once turned on, your two-finger double-tap should begin working again.
that worked
Thanks Nico that worked.
The app creator evidently didn't want anybody to know about that feature, I originally found out about it a few years ago from a friend so I knew about it but it certainly isn't labeled very well.