![]() |
BT Keyboard problem
I bought a iGo stowaway ultra-slim keyboard recently (Think Outside Keyboard). It worked GREAT when I first got it, was typing in no time after pairing through the control panel and pairing through the BT keyboard option. however, recently even though the pair is successful, no text appears when I type using the keyboard. I have tried multiple power cycles, I have tried deleting the profile for the BT keyboard and then re installing it, all yield the same result! Please help! I am about to try a reflash though I would really rather not. =[
|
Re: BT Keyboard problem
Battery low? :)
|
Re: BT Keyboard problem
The "JKL" keys stopped working on my Think Outstide Model xtbt01 BT keyboard. It makes me so mad. I have removed it, changed batteries, sprayed air in to it, etc.. That's all I can really think of to do.
I still can't get them to work. It makes it really inconvenient to type with. I'll be picking up the Nokia Keyboard soon, if I can't figure this out. EDIT: OP, have you tried pairing it to another device? Like your smartphone, or someone else's? |
Re: BT Keyboard problem
No, i dont have another device I could pair it to. And its not batteries since I have changed them out. =\
|
Re: BT Keyboard problem
Quote:
|
Re: BT Keyboard problem
Am I being fair with Nokia? I have this concern that they included (or allowed) this bug because Stowaway T O was outselling their keyboard. This would be a good way for them to catch up. But dropping more bucks for another expensive keyboard is not in my vocabulary at the moment. By the time that it would be it would be time for another device.
I upgraded to OS2008 somewhere around the sixteenth of May. I was very excited over the new OS; very, until a few days later when I realized that I didn't have a keyboard. What happens is that I go through the motions to pair with the keyboard, but when the four digit code number is assigned for me to enter from the keyboard, the keyboard shuts off - every time. So, I Ctrl-Fn-Fn to restart the keyboard and enter the code, but immediately the Nate responds that pairing failed. No other keys activate the keyboard. To make it even stranger, the keyboard comes on automatically when I unfold it. I cannot turn it off either. It doesn't respond to the key combination. |
Re: BT Keyboard problem
I highly doubt they're being that clever, and more importantly, communicative; think about which parts of a gigantic corporation would be able to notice sales shortfalls on one product (the keyboard) and would be able to introduce bugs on another one. It's just not feasible.
Maybe iGo keyboards are just junk? (I don't actually think so; I think they're just so much more popular, that you see a lot more problems with them.) My Palm 3245WW works with no trouble, and always has... |
Re: BT Keyboard problem
I know you're right. But you know how one feels when something like this goes wrong! Still, I have to wonder why my keyboard acts differently now, immediately after reflashing my OS. It is strangely different - not just different. This justifies (in my mind) the suspicion which I related!
One wonders, can the keyboard firmware be tampered with? Let me reiterate: The keyboard comes on when I open it up. I do not have to press Ctrl-Fn-Fn to get the green led to bounce. The keyboard goes off when the Nate delivers the four digit access code, and rejects the process as soon as I repower. I have been following other threads in which the BT Keyboard owner has this problem. They, however did not specify that the keyboard shuts off. Is it ok to use the Nate while it is charging? Does anybody know? I do not want to assume, though I normally would, historically..... |
Re: BT Keyboard problem
well ill tell ya it took me 20 minutes to get mine paired...and mine did all those odd things works fine using it now
|
Re: BT Keyboard problem
It's just fine to use it while charging; note that exceptionally heavy use can result in discharging faster than it can charge, especially if you're using one of the lower-current chargers.
|
All times are GMT. The time now is 13:19. |
vBulletin® Version 3.8.8