Open GoogleCodeExporter opened 8 years ago
Hello Again,
Additional information to hopefully assist diagnosis of the issue. Bluetooth
options in BTstack at the bottom of iOS "Settings" options will not allow iOS
Bluetooth to be reestablished. iOS Bluetooth attempting to be reestablished
(spinning wheel) but not working, or able to be turned on in "General" under
"Settings"
Thank you
Original comment by stumund...@gmail.com
on 4 Aug 2014 at 4:37
If you reboot your device, can you enable the regular Bluetooth? If not, then
your Bluetooth is most likely be broken. (de-install BTstack to make sure). if
not, start BTstack Keyboard without enabling BTstack in the settings first.
Original comment by matthias.ringwald@gmail.com
on 8 Aug 2014 at 8:58
Thank you for the reply and support Matthias,
I followed your instructions but no change to BTstack. Description follows
- Regular Bluetooth: enabled on Reboot ("now discoverable". Good to know that,
so thank you.
- Started BTstack keyboard from "Keyboard" icon (not from Settings [and I
rebooted again, first, just to be sure]) Same result, as reported - BTstack
Keyboard 1.5; Devices; Activating BTstack… (+ 'working' wheel) "Please make
your Bluetooth HID Keyboard discoverable & select it in the list."
- I have not deinstalled the software. I do not know if I can reinstall it
after deleting it, or whether I would have to buy it again.
It is a pretty standard "Kensington" brand keyboard that works well with a
newer (not jailbroken) 3GS iPhone, as well as a MacBook. The keyboard
frequencies are 2.402GHz - 2.480 GHz. It crossed my mind that the keyboard
might not be compatible with the phone.
I am most appreciative of your getting back to me. I am not knowledgeable
about code. I am user of software, so this is unlikely to be the correct forum
for me to be contacting you through. After posting here, I noticed I could
report through the app and did that there too.
Any additional suggestions and support will be most appreciated.
Original comment by stumund...@gmail.com
on 12 Aug 2014 at 6:11
Original issue reported on code.google.com by
stumund...@gmail.com
on 4 Aug 2014 at 4:18