I just stumbled across something while trying to connect my Samsung Galaxy S2 (the TMobile version) to an old iGo Stowaway Think Outside XTBT01 bluetooth keyboard and thought I'd share.
When I went to scan for Bluetooth devices on my S2 and chose connect to keyboard, it prompted me for a pin but didn't give me an input box or onscreen keyboard. The message on my S2 screen when I tried to connect read: "Enter PIN Think Outside Keyboard to pair with "605655". So I guessed that it might be all done from the keyboard. After trial and error, I discovered that the number in the on-screen message worked as the PIN to type in on the keyboard! It seems that the S2 kind of "auto-generates" a PIN for this keyboard (and possibly other similar Bluetooth devices where you can input a PIN from the device?)
Here's the specific steps that worked for me:
- On the Droid, with Bluetooth turned on, go to Settings > Wireless & Networks > Bluetooth Settings.
- Now, go back to the Think Outside keyboard. Hit CTRL, blue FN and green FN all simultaneously for a second or two to initiate pairing. The green LED above the "T" will start blinking.
- Back to the Droid. Hit "Scan for devices" and when the "Think Outside Keyboard" shows up tap it. The pairing process will begin and you will get a message like "Enter PIN Think Outside Keyboard to pair with "605655"
- Immediately, go to the Think Outside keyboard, click and HOLD the blue FN key and hit "605655" (or whatever number appears in the message on the Droid) then, with the blue FN key still being held down, hit the "Enter" key. The Blue FN key turns the "Enter" key into the "Ok" key.
Boom - you should be connected. When you close the keyboard, or it times out, it will say "Paired but not connected". All you have to do is reopen the keyboard or hit the space bar and the status goes back to "Connected". Any where you would have to use the screen keyboard, you can now use the Think Outside keyboard.
I'm still trying to figure out why caps lock appears to be stuck on. Not sure yet if it occurs in all apps, but it's on by default. I seem to be able to cancel it by hitting backspace, but it reengages the next time I hit the Shift key. So something isn't quite perfect with the driver. Still...
When I went to scan for Bluetooth devices on my S2 and chose connect to keyboard, it prompted me for a pin but didn't give me an input box or onscreen keyboard. The message on my S2 screen when I tried to connect read: "Enter PIN Think Outside Keyboard to pair with "605655". So I guessed that it might be all done from the keyboard. After trial and error, I discovered that the number in the on-screen message worked as the PIN to type in on the keyboard! It seems that the S2 kind of "auto-generates" a PIN for this keyboard (and possibly other similar Bluetooth devices where you can input a PIN from the device?)
Here's the specific steps that worked for me:
- On the Droid, with Bluetooth turned on, go to Settings > Wireless & Networks > Bluetooth Settings.
- Now, go back to the Think Outside keyboard. Hit CTRL, blue FN and green FN all simultaneously for a second or two to initiate pairing. The green LED above the "T" will start blinking.
- Back to the Droid. Hit "Scan for devices" and when the "Think Outside Keyboard" shows up tap it. The pairing process will begin and you will get a message like "Enter PIN Think Outside Keyboard to pair with "605655"
- Immediately, go to the Think Outside keyboard, click and HOLD the blue FN key and hit "605655" (or whatever number appears in the message on the Droid) then, with the blue FN key still being held down, hit the "Enter" key. The Blue FN key turns the "Enter" key into the "Ok" key.
Boom - you should be connected. When you close the keyboard, or it times out, it will say "Paired but not connected". All you have to do is reopen the keyboard or hit the space bar and the status goes back to "Connected". Any where you would have to use the screen keyboard, you can now use the Think Outside keyboard.
I'm still trying to figure out why caps lock appears to be stuck on. Not sure yet if it occurs in all apps, but it's on by default. I seem to be able to cancel it by hitting backspace, but it reengages the next time I hit the Shift key. So something isn't quite perfect with the driver. Still...
