Database Info

Microsoft Bluetooth Keyboard 6000 Works!

I just received my MS Bluetooth Keyboard 6000 and got it working on cyanogenmod6 (CM6), connected using Bluetooth Keyboard Easy Connect. I ran into some problems getting it to work initially, so I figured I'd outline how I got it working and explain the functionality of the keys on the keyboard to help out anyone wishing to use this keyboard with the Viewsonic Gtablet.
Here's what I did:
(1) Installed Bluetooth Keyboard Easy Connect and got it running. Turned on bluetooth (but left it as non discoverable) on the gtablet.
(2) Rebooted Gtablet.
(3) Bluetooth automatically stays on upon reboot because I turned it on previously. Under Settings > Wireless, I went to bluetooth and let it scan for devices. I had previously turned my keyboard on and its LED was already flashing (to signal that the keyboard was discoverable).
(4) Once the gtab detected the keyboard, I selected the keyboard to make it pair. The gtab will prompt for a PIN. **HERE'S WHERE THE MICROSOFT INSTRUCTIONS DON'T EXPLAIN WHAT TO DO VERY WELL**
(5) Enter "0000" or any pin you want into the gtab and select OK. Immediately after doing this (without any further prompts), type the SAME pin (i.e. "0000") into your bluetooth keyboard and hit "Enter".
(6) Assuming that you had properly installed Easy Connect earlier and that it is already running in the background, your bluetooth keyboard should magically work!
(7) If the bluetooth keyboard stops working after a minute (mine stopped working, and everything I typed out in an email got deleted...weird), it might be because you didn't grant superuser permissions to Easy Connect. Do that, and it should work again.
That's all to make it work! Now, here's what works on the keyboard:
- volume control keys: up and down work, mute does not
- arrow keys work for typing; on home screen, arrow keys can be used to select app across multiple home screens (and pressing enter when an app is highlighted launches it)
- shift key works just like the android soft kb shift key (one press is shift, two presses is caps lock); but it seems like press and hold works too, including for the symbol keys on for shift+number
- windows key: doesn't work
F1 = settings
F2 = nothing
F3 = call log
F4 = sleep and wake the device (cool that it wakes up, but only after sleeping for less than a short time)
F5 and above = nothing
- CTRL and DEL don't do anything either
- ESC key: nothing
- tilde key (squiggly key under ESC): nothing
- FN Home: home (and wake when asleep)
- FN End : same as F4 (sleep and wake)
- FN Insert: nothing, it seems
- FN Print Screen: probably nothing
- Alt+Tab and Win+Tab: search
Also the keyboard is fairly responsive and wakes up quite quickly after non-use. So far so good, but I haven't tried rebooting or re-pairing yet.

ok... so I spoke too soon. The initial pairing was flawless, even after it went to sleep. Now, after rebooting, it doesn't pair properly and interferes with my wifi. I'm going to run some more tests and then probably report my findings of bugs in the Bluetooth Keyboard Connect thread.

Any updates? Did you get this to work reliably?

Mankey Magic said:
Any updates? Did you get this to work reliably?
Click to expand...
Click to collapse
I've got the same keyboard. I got it to work with Blueinput. The only issue is that if you're using the free version, {Blueinput Demo} shows up in the middle of your typing an awful lot. I use it a lot, so I sprang for it.

It seems to interfere with my wifi... When I have bluetooth and Easy Connect running in the background on boot, it causes my wifi to cut out, especially when I open the Amazon app store and marketplace. Not sure why--maybe those use more bandwidth than just opening email?
My solution thus far has been to only turn on bluetooth (and Easy Connect, which runs automatically upon bluetooth being turned on) when I need it. Surprisingly though, the wifi problem doesn't seem to occur when bluetooth is connected to something--anything at all--like when it's connected to my bluetooth GPS module but not the bluetooth keyboard. Of course, when the bluetooth keyboard is connected, there aren't problems at all.
So the solution so far seems to be to re-pair it each time I want to use it. Not sure if anyone else has encountered the same problem (seems like it's a problem with Easy Connect) or has any suggestions.
I might try Blueinput to see if that fixes things.

Well, it sounds like it's a bit of a hassle but still definitely usable.
Do you know if the G Tablet works with any bluetooth keyboard? I'm thinking about buying a smaller one. Why's this tablet got to be so temperamental sometimes? Haha.

Yep... definitely usable. After fiddling with it some more, it seems (but I can't confirm) that I don't get problems so long as bluetooth isn't on when I boot it up (i.e. I turn off bluetooth before turning the tablet off). Looks like, once the tablet is on, things work out if I do the following:
(1) I can turn on the keyboard
(2) toggle bluetooth on the tablet
(3) watch as the pop up tells me that easy connect is running (it runs automatically when you turn on bluetooth)
(4) type in pairing code "0000 + enter" on the keyboard (not sure if this is necessary, but the 2 times I've tried it, it works, and I haven't tried going without).
Using these steps, and most importantly not having bluetooth on when booting up (that seems to interfere with wifi), seems to make things fairly smooth.
I haven't filed a bug report based on the wifi-interference issue yet because I haven't tried out all the permutations of what's on and running in the background on boot and what I'm pressing on the keyboard. It seems that things are working better after I fiddled with my bluetooth GPS external module and uninstalled/reinstalled Airport Mode (forgot the name of the app), so I'm not sure if either the GPS or the airport app did something.
Mankey: as for whether the gtab works with any bluetooth keyboard, it has the potential to, but it depends on what ROM you're running. I'm using CM6 and my results are based on that ROM. Good luck!

Thanks Kungfu and Judo. (lol)
Will probably jump on the 6000.

You're welcome. And I just noticed that judo has been replying too....
Do let us know how it works out for you on whatever ROM you're using and if you're able to get around some of the kinks I've discovered. I'll experiment with Blueinput when I have more time next week and see what I can figure out.

Hey so I just got my 6000 in the mail and downloaded blueinput demo but there seems to be a lot of missed keystrokes and some lag. Lag is fine to me as long as all my keystrokes go through. Haven't tried easy connect yet. But was just wondering if this was a symptom of me having the demo.
Tried easy connect but it doesn't seem to like me. Will connect and work for a while but soon it says that it disconnected.

Generally no lag at all using Easy Connect, although the first 3-4 keystrokes after a standby might be slow.
For Easy Connect, did you make sure that it had superuser privileges? That solved the disconnection problem for me. Also try what I did in terms of ensuring that bluetooth is off before rebooting, then turning on BT, then connecting the device.
What ROM are you running?

I actually tried doing exactly what you posted. No dice. It will always connect well, then after a couple minutes just crap out, followed by a message that says that it's disconnecting. Gave it superuser privileges, restarted with BT off. :/
I'm running Vegan 5.1.1 with pershoot at 1400. I was going to flash to Vegan 7 sometime soon (probably next week since I'm not in dire need of the keyboard right now) to see if it would help at all.
I'm not sure if the 6000 is HID or SPP bluetooth but I have a feeling it's HID. Maybe gingerbread can handle HID better. Once I flash ginger, I'll post my findings here.

Logitech Bluetooth Keyboard+Tf300T problem

Hello, so I recently installed cynaogenmod 10.1 on my device, and everything went smoothly. I bought a Logitech Bluetooth Keyboard(it comes with a pocket-like leather piece/stand). However, I'm able to connect it and the tablet asks for a series of numbers, i input them and then it says connected! I go to any app or even try the home/back keys on the keyboard and nothing responds. The keyboard works because I tried it with the iPhone and my laptop to make sure. Batteries are brand new, is this a cynaogenmod problem? Also, at times when I'm trying to turn on the bluetooth it'll go on and then immediately off no matter what. I have to reboot and then it works again.
Thanks!

Amirocassar said:
I'm able to connect it and the tablet asks for a series of numbers, i input them and then it says connected! I go to any app or even try the home/back keys on the keyboard and nothing responds. The keyboard works because I tried it with the iPhone and my laptop to make sure. Batteries are brand new, is this a cynaogenmod problem? Also, at times when I'm trying to turn on the bluetooth it'll go on and then immediately off no matter what. I have to reboot and then it works again.
Click to expand...
Click to collapse
I believe this is a known issue with CM10.1.
Sent from my Transformer Pad TF300T using Tapatalk HD

bluetooth is disconnecting by itself

my tablet is samsung galaxy tab s2 and it has android 6.0.1 on it. i am using belkin yourtype bluetooth keyboard with the tablet
if i am using the keyboard then things are fine. however if leave keyboard idle for some time then it will disconnect from the tablet and i have to type on the keyboard so it will reconnect again. i didnt have this problem when i was using my old tablet which is samsung galaxy tab pro
i did some research and i found out fault is with the android 6.0.1 and it causes bluetooth devices to disconnect automatically. i read it here:-
http://forums.androidcentral.com/samsung-galaxy-s6/540579-bluetooth-keeps-disconnecting.html
what do i do to stop it from disconnecting?
the link said tiles app is doing it. what is the tiles app? i couldnt find it

Gear S3 Frontier and Nexus 6p connection problems

Hi all,
I'm growing increasingly frustrated with this watch because of connection issues.
When I received this watch in January, I was able to set it up no problem. Everything worked great. I just had two issues-
1. The Bluetooth car system would no longer work because the phone would use the watch as the default headset.
2. Google duo would go bonkers when I was getting a call if the watch was connected.
Both of these issues were solved with a solution found here in the forums-by unchecking the option to use the watch for phone connection.
I noticed immediately after doing that that the connection became unstable. I would disconnect randomly then reconnect. As the weeks went on the disconnections became more frequent i.e. Every 2-3 minutes. Then the watch wouldn't connect anymore. Once the watch wouldn't connect anymore neither would my car. Nothing related to Bluetooth would work on my phone. My Tiles wouldn't connect anymore either.
So I went through and deleted all data and cache related to the three Samsung apps and uninstalled the apps. I deleted all Bluetooth connections. Then reinstalled the apps and connected the watch. Within an hour I was still in the same situation. (With no other things connected to Bluetooth.)
I figured out that if I restart my phone everything works again for about 20-30 minutes.
I'm at the point where I don't feel like it is worth keeping anymore. I can't have anything else connected to Bluetooth and I have to restart the phone so often that it just doesn't make sense.
After reading through the forums here it doesn't sound like this is a common problem. Is there something I am missing? Is the watch defective? Any suggestions is greatly appreciated.
Thank you.

You could well find the issue is with your phone and not the watch. I initially used my S3 with a Samsung phone that went bust. I went back to my Nexus 5 and found I had some issues and one app had disappeared from the app store. I contacted the app firm who told me that they were aware of it but it was Samsung that was blocking the app. On going back to a Samsung phone the app was available again and works fine. Can you check your S3 with a different phone?

I also have a S3 and a 6P. Disconnect the S3 Bluetooth from your phone Bluetooth settings and it should connect to your car. You should still see the "Gear S Plugin" notification if you swipe down on the the phone. You should still receive notifications on your phone but the Bluetooth will connect to your car. Connect the S3 to your phones Bluetooth again if you want to answer calls via your watch. Hope this helps.

I have the Mate 9 and the Frontier... when i enter my truck i just press airplan mode on the watch turning off all connection. bluetooth from phone to truck connects 1-2-3....

Clarification
Hi all,
Thanks for the responses. Probably because of my long rambling post there is a little misunderstanding of where I'm at now.
Right now my problem is that my phone can't stay connected to my watch. I have nothing else connected via Bluetooth to my phone. Once it can't connect anymore, I have to restart my phone in order for it to connect again. And then it only stay connected for a couple of minutes before disconnecting.
It is like the Bluetooth gets locked up on my phone by the Samsung gear apps.
Maybe it's my phone. Maybe time to get a Pixel.
Any suggestions are greatly appreciated.

Try this. I do it when I lose notifications. Go to Bluetooth on your phone. "forget your watch" it will disconnect. Reboot phone. Then re pair watch and phone after reboot using your phone and the watch (not the gear app). That usually fixes most problems for me.
Sent from my ONEPLUS A3000 using Tapatalk

[Q] Gear S3 and Samsung S8 connection problems

Hi.
Just got my S8 and tried to pair it to my Gear S3. All goes fine and both stay connected until I disable the watch audio function in the S8 bluetooth options (to not conflict with my car handsfree system).
After that, they just disconnect and don't connect anymore.
Any help out there?
Thanks!

Similar issue over here: I lose BT connection of my Gear S3 to my One+ 3T phone after a day or so. Factory reset of th ewatch does not help, in combination with ROM falsh of the phone it connects just fine but loses connection again in a day or so. Any hints what can cause this are most welcome.

I've had the same issues since getting my S3 Frontier with my S8. It "seems" that when my phone connects to some other BlueTooth source like my car and then I leave my car it doesn't want to reconnect to the Gear. I've also set my phone down, walked away (out of BT range) and its switch to connected remotely. Then when I get closer it just disconnects and sits at stand alone even through my phone is next to me.
It's driving me crazy and makes the Gear very unreliable. If I go into the Gear app and turn off "Gear Connection" then back on it connects no problem.
I've checked the battery settings, they are fine. Also the Gear and S8 are fully up to date but the problem has been there between software versions, no changes between updates.
-Allan

I am having the same problem with Gear S3 and S8. Toggle airplane mode on the phone fixes it. The problem is I don't like to do this every time they refuses to automatically connect.

I'm going to put in a support request with Samsung, this is getting ridiculous. That or I'm gonna sell it. New thing it's doing:
I put my phone on its charger.
I walk outside to let out the dog.
BlueTooth disconnects (fine). It switches to my house wireless. Its now "connected remotely".
It never switches back to bluetooth, stays connected remotely.
I leave the house the next day.
My wireless network is out of range
Gear is now "Stand Alone" with the phone 3 feet away.
Stays stand alone until I either turn off and on airplane mode (effectively turning off and on Bluetooth) or go into the gear app and turn off and on its connection.
-Allan

vseven said:
I'm going to put in a support request with Samsung, this is getting ridiculous. That or I'm gonna sell it. New thing it's doing:
I put my phone on its charger.
I walk outside to let out the dog.
BlueTooth disconnects (fine). It switches to my house wireless. Its now "connected remotely".
It never switches back to bluetooth, stays connected remotely.
I leave the house the next day.
My wireless network is out of range
Gear is now "Stand Alone" with the phone 3 feet away.
Stays stand alone until I either turn off and on airplane mode (effectively turning off and on Bluetooth) or go into the gear app and turn off and on its connection.
-Allan
Click to expand...
Click to collapse
I have this exact issue! I just purchased Gear S3 Frontier non-LTE model and have it paired to my Galaxy S8. It seems like sometimes it goes into standalone mode when I leave the bluetooth range and does not want to reconnect to bluetooth once I'm back in range until I force it to connect within the Gear app on the Phone... this is very frustration. Coming from an Android wear, I never had connectivity issues...

nitewolfgtr said:
I have this exact issue! I just purchased Gear S3 Frontier non-LTE model and have it paired to my Galaxy S8. It seems like sometimes it goes into standalone mode when I leave the bluetooth range and does not want to reconnect to bluetooth once I'm back in range until I force it to connect within the Gear app on the Phone... this is very frustration. Coming from an Android wear, I never had connectivity issues...
Click to expand...
Click to collapse
Talked to support. They said reset the S3 and if it keeps happening it's a hardware issue and I need to send it in. I highly doubt it's a hardware issue....really seems like faulty software. But I reset it, again, and I'll see what happens.
I suggest everyone having this issue does the same: http://www.samsung.com/us/support/#contact_us_for_support Maybe they don't even know it's a issue.

vseven said:
Talked to support. They said reset the S3 and if it keeps happening it's a hardware issue and I need to send it in. I highly doubt it's a hardware issue....really seems like faulty software. But I reset it, again, and I'll see what happens.
I suggest everyone having this issue does the same: http://www.samsung.com/us/support/#contact_us_for_support Maybe they don't even know it's a issue.
Click to expand...
Click to collapse
I just did the reset as well... i'll let you know if it fixes mine. If not, it's going back to Amazon... lol!

So resetting mine worked for about 3 days then I started having the same issue. Reset again, another 2 - 3 days then more problems. However my S8 just got a system update and in the release notes:
- Prevents unintended Bluetooth® disconnections with a companion Gear S3 smartwatch.
So far since the update yesterday mine has been better.....we'll see.

Same issue with my Oneplus 3 and Gear S3 Frontier.
Combination of Turning off everything on Connections on Gear s3 settings than turning on bluetooth and rebooting phone and gear s3 ussualy solves this.
But there is no logic to the steps. I coulnt pinpoint what of the above fixes it. Because its always different.

Having this problem on my OnePlus 5T. Going to phone's bluetooth settings and unpairing then pairing again seems to do the trick.

My S3 Frontier ran out of battery and shutdown, from there on, after getting charged again of course, the parring just stalled.
Normally I can slide down the top buttons and "Gear S3" is displayed under the BT icon, but not now
First I tried to turn off BT and turn on again on my S8, no success.
The I deleting the parring and pairing the watch again, no success.
Then I booted the phone, no success.
Going to BT settings on the S8 showed the gear, details showed nothing is turned on, i tried to turn on the input device, now the gear was connected on the top button BT icon... but still Samsung health says no gear device is connected.
I was just about to reset the watch, thinking "oh, now I have to setup the watch again with height, weight, etc... lovely!" then I thought I wanna try one last thing, disable BT on the watch and turn it on again. That did the trick for me!