I've got a Microsoft Wireless Entertainment Keyboard 7000 that worked fine under Ubuntu 9. The GUI discovers my mouse fine, and also appears to connect to the keyboard, but the keyboard does not type when paired through the GUI. When I pair using hidd (either --search or --connect), the keyboard pairs and works fine, however when I cycle power on the keyboard, it will not auto-reconnect, and I get the following error message associated with it (see attached image):
Grant access to '00001124-0000-1000-8000-00805f9b34fb'Device 'Microsoft Wireless Entertainment Keyboard 7000' (00:12:5A:A1:5A:8D) wants access to the service '00001124-0000-1000-8000-00805f9b34fb'. If i grant access, it does nothing, and will simply request it again when a key is typed. how to make the bluetooth service automatically pair (either through config files, or better yet, through the GUI?)
I have a simple Bluetooth device I would like to pair with my computer. I detect it in the BlueTooth New Device Setup (from the GNOME pannel), detected as "Unknown", I enter its pairing code (1234) and click on "forward". But then it asks me to enter a code on the BlueTooth device... I don't have anything to enter any code on this device. I would like to simply connect to it! From other OS, I manage to connect to the device as it's not asking to write any pair code in the bluetooth device. The PIN code 1234 is enough to make the connection.
I have a bluetooth headset that I hope I can get to work with Ubuntu 10.10 so that I can use it with Skype.I am using these instructions to get it to work. However, there are some differences between my experience and what I expect from the instructions, ultimately leading to some errors.First, I should mention that according to Blueman device manager, it would seem I have successfully paired my device. It has a MAC address. I have attached a screen shot of the interface:It sure looks like the device is recognized by my system. However, when I get to step 5, the MAC address of the one device I see is not the same as the one in the interface above:
I'm struggling for pairing my laptop with my phone to dial up internet. On slack 13 I configured hcid.conf but on the new 13.1 with the new demon bluetoothd I don't know how to pair on command line.Documentation is not a lot, or I'm not able to find it.
I am developing an application which communicates with a bluetooth device.I do not want the user to pair or unpair the device using the Bluetooth applet or command line, but I want to automate the pairing process through my application. The application will scan and find the bluetooth devices in the proximity of the computer, and automatically pair the required device without any user input.Where should I look for the relevant APIs?
The PIN validation screen is giving me some trouble. I am trying to pair an LG Rumor Touch and the PIN pops up and matches and the phone is happy to accept the pairing so when I click the PIN matches button on the Bluetooth Remote Device Wizard it will not close. It shows a spinny clocky but just sits there until I cancel. The device manager shows a greyed out light but it lists the device. The tray icon shows device, but gives No supported services found on the menu entry. Dolphin shows device but when I click it to browse it loads to an empty folder. The Device Wizard behaves this way for other phones also, but I was able to get some services running if I ignored it and let it sit there. If I canceled the process it messed up the services.
I can't configure Bluetooth in Slackware 13.1. It basically works. I can scan my mobile phone: Code: $ hcitool scan Scanning ... BA:BE:DE:AD:AB:ED Nokia 6300
But when I try other commands, mobile phone asks me about passcode. Because I don't know it pairing fails: Code: $ gammu 6300 --identify Error opening device. Unknown, busy or no permissions.
On the other hand when I try to pair computer using mobile phone it doesn't find any device. Code: Pair new device Searching for devices No devices found
In Slackware 13.0 to configure Bluetooth it was enough to edit /etc/bluetooth/hcid.conf file. In Slackware 13.1 there is no such file. I tried to use blueman but it offers first and foremost a lot of error messages. In despair I even started KDE and tried Bluetooth Manager. It attempts to run for a dozen or so of second and finally fails. I did full installation of Slackware 13.1 and I use generic SMP kernel.
pairing bluetooth devices on Centos? I'm trying to pair a phone (Nokia 6086) with a bluetooth dongle. I've been able to do it on Ubuntu (using the bluetooth applet), but so far no luck connecting it to a Centos machine. Steps I have taken so far:
Just picked up a Microsoft Designer Bluetooth Mouse.Whenever I try to pair it, my system hangs and I have to hard power it down. The mouse is Bluetooth 4.0, but my Bluetooth connectivity is provided by my Intel Wireless 3160 card which does support Bluetooth 4.0.I'm using Blueman as a front end, and one other thing of note is that it shows as "Unknown" after a scan.If I need to return it, I need to return it, but it seems like a good mouse and I'd like to keep it if I can make it work.
I've took this out of syslog: Code: Select allAug 1 14:58:04 Noah-LEMUR kernel: [ 317.772054] BUG: unable to handle kernel NULL pointer dereference at 0000000000000398 Aug 1 14:58:04 Noah-LEMUR kernel: [ 317.772090] IP: [<ffffffff81569f7e>] mutex_lock+0xe/0x30 Aug 1 14:58:04 Noah-LEMUR kernel: [ 317.772113] PGD 0 Aug 1 14:58:04 Noah-LEMUR kernel: [ 317.772123] Oops: 0002 [#1] SMP
bluetooth-applet is not auto-starting on one of the 2 users of a system. In the user's environment where auto-start does not work it can be started from a shell without any error and bluetooth otherwise works fine. There is an entry in the start up applications preferences for both users. We are running 9.10.
Im using a Samsung R420/R470 laptop with Broadcom bluetooth and a Prolink PMO624B mouse.My mouse works when I add it as a new device, but if I off the mouse and on it again, the mouse does not auto connect. I have to press and hold the connection button under the mouse and reconnect to the mouse.The mouse says that it is linux compatible, so I guess its a problem with my bluetooth drivers.
I have bluetoothd,hidd,and bluez-simple-agent running. I can manually connect my if I use
"hidd --connect XX:XX:XX:XX:XX:XX"
However, I cannot get bluetoothd to make any sort of connection automatically. I have hidd running as a server, I see link_key_request(sba=XXXXX,dba=XXXXX) in dmesg when I click the mouse, but I get no connection.
I have a nifty new headset (a JawBone icon�the noise cancellation is incredible) and I've successfully connected it to my Karmic laptop (64 bit, for the off chance it makes a difference). The trouble is, I only occasionally want to connect it to my laptop; I mostly use it with my mobile 'phone.
The two devices fight over my new toy a lot, and invariably the laptop wins, contrary to what I want. It seems a pain to have to rediscover the headset every time I want to use VIOP or whatever, so is there a way to add a device to Karmic's Bluetooth list, but not have it connect whenever it sees it?
I am trying to use an Apple BT keyboard with a new installation of 10.04.Using Bluetooth Preferences, I discovered the keyboard, and paired with it. No problem with pairing. If I click on the BT icon in the top panel, it indicates that the keyboard is connected. But any text typed on on keyboard does not appear on screen. I opened Keyboard Settings, thinking that I might have to select the connected BT keyboard as the input device. Nothing there. Is there another preference somewhere that has to be set for the BT keyboard to actually work as an input device (as opposed to simply being paired)? My USB keyboard is still connected (and is working). Perhap Ubuntu only tolerates one keyboard device at a time?
I have two machines one Ubuntu Lucid and one Kubuntu Lucid. They share a bluetooth keyboard through a KVM switch. As of last week both were working. At this point my KDE machine disconnects from the keyboard on the first keystroke. The Ubuntu machine is still okay. What I've tried/checked so far without success
I can connect my keyboard through Kbluetooth but it disconnects when I start typing. The timeout time is set to none. I tried rebooting and then reinstalling the software to no avail. I replaced the batteries in the keyboard. Plugging the bluetooth usb adapter directly into the KDE box. Removing and then adding the trust I find this in the syslog:
2010-09-18 12:09:42 godel bluetoothd link_key_request (sba=00:1BC:0F:F1:E7, dba=00:22:48:87:B3:49) 2010-09-18 12:09:42 godel bluetoothd Encryption failed: Permission denied(0x5) Here's the kbluetoothrc from my home folder [KBlueLock]
I have a Rocketfish bluetooth keyboard and mouse combo and am running Ubuntu 10.04. The mouse was easy to set up. I just went to the bluetooth icon and clicked add new device and it connected. The same wasn't true for the keyboard. It gives me the code to type so I typed it and pressed enter and... nothing. So I found a little tutorial and I had to install bluez and type in the terminal, "sudo hidd --search" then enter my password (which I needed to grab my other keyboard to do) and it connected. If I don't use it for a while or reboot, the keyboard will not connect. I have to do the hidd search again which means I need to keep my extra keyboard handy. I had it set up before where it would connect on a reboot, but I got a new hard drive and reinstalled Ubuntu, now I can't remember how I set it up. Could I have set up bluez wrong?
I have a laptop. . .Dell 1150. Ubuntu installed, bluetooth device installed and my bluetooth keyboard and mouse works like a charm. I decided to load up my same exact Ibuntu on my desktop, use the same keyboard on it, and the mouse too. I tested it on the laptop, just in case it would not work in Ibuntu, and I didn't want to wipe out my Windows XP on my desktop and find out Ibuntu would not work on it with a wireless keyboard. Since it worked very well with my laptop, I figured it would work just as good with my desktop. I wiped my desktop out, and installed Ibuntu. Everything worked fantastic. Until I tried to install the bluetooth.
When I plug in my Bluetooth device, Ibuntu finds it and asks to set up your device. I attempt to set up my keyboard/mouse combo and it asks for a 6 digit code (like it is supposed to). I enter the code and press enter. From here, the problem starts. Ubuntu "claims" to connect to the keyboard, shows it connected, but my keyboard does not work at all. Neither does the mouse that is built into the keyboard. I type and nothing happens. This also brings up (sometimes) another message that says my keyboard is trying to connect to the bluetooth device please enter keyboard PIN. Well.
I can't enter anything, because the keyboard does not work! The mouse does not work! I can (without any problems) disconnect and connect to my laptop, but I can't do this to my desktop. Both are dell units. Desktop is about 3 years old, laptop is about 8 years old. Both running Ubuntu, the latest version. Both recognize the bluetooth transceiver. I have tried different USB ports on the desktop with no avail. I would really like to use my desktop as a unit to my TV with a wireless keyboard, not my laptop. It is much faster, more memory, and I can use the TV as a monitor.
I'm trying to use an Apple wireless keyboard with Ubuntu 9.10 (Karmic) but the fn key is not working at all. If I start up xev and hit the fn key it generates no event. What do I need to do for it to work. It seems as if it should work when viewing pages like URL...
I tried to do a clean install of Ubuntu 10.04, but when I get to the screen if I want to test or install Ubuntu, the keyboard and mouse (bluetooth) don't work. I tried to resync the peripherals, I disconnected usb connector base of the tower and putting it back but nothing works for me. I have a Logitech Desktop MX 5000 (Bluetooth).
I'm using an Apple bluetooth keyboard, model A1016 the one with a white bottom inside clear plastic. The machine is a Mac Mini (2,1) and I also have an Apple bluetooth mouse. The mouse works fine on Ubuntu 10.04. The keyboard has issues.
When I add the keyboard using the bluetooth applet, I find that I can't assign a specified PIN. I have to use automatic PIN, and then type the random number presented. That works until I reboot the machine.
After reboot the bluetooth applet menu shows both the mouse (connected) and the keyboard (not connected). If I tell it to connect the keyboard, nothing happens. The only thing I can do is delete the keyboard, re-add it, with a new random PIN.
I think my computer must be haunted, as I've so far failed at 3 different ways of installing Maverick on my 2007 aluminium imac! I've written off using a VM, and I'm currently stuck trying to make a dual boot setup.
So I've followed the guide at [URL].. and got as far as rebooting with the CD in, and selecting Ubuntu, but then when everything loads I'm left at the screen where I can select try or install, with no way of selecting either as my mouse (apple bluetooth mighty mouse) and keyboard (apple bluetooth wireless aluminium keyboard) don't seem to be connected. I've got past this point by hitting random keys after booting and selecting the CD - this takes me into a more basic looking menu where the keyboard does still work and I can select install, try etc.
So I can get as far as selecting try, and get a working Ubuntu desktop. However, when the desktop loads, my keyboard and mouse are again not working. By connecting a USB keyboard and mouse, I'm able to get my mouse to pair, using the bluetooth menu and going through the setup. However, I'm stuck trying to get my keyboard to pair.
Going into set up new device and searching initially shows up my keyboard, then it disappears. If I wait it randomly comes back and disappears again. If I click on next whilst it is available, I can get as far as putting in a pin, but when I press enter it says Failed..
Sorry for the rambling post - I basically have 2 questions: 1- Is it expected that bluetooth keyboards and mice won't work during the installation menus? Half my problem is that I don't know what should be working and when (should I have to boot into the trial installation and setup the keyboard and mouse, or should it be set up automatically?).
2- Has anyone else seen the same problem with the apple wireless keyboard failing to pair? I've searched the forums and google, and found lots of people with problems with bluetooth keyboards, but none which seem to match what I'm seeing. I don't know if there's any point in pressing on with the installation using the USB keyboard and mouse in the hope that things will work in the full install, or if they don't work in the trial install then thats my lot.
I've paired a bluetooth keyboard and mouse with my machine using the Gnome bluetooth wizard and the keyboard and mouse work fine. Then, if I let the computer sit for a few hours and then try to use the keyboard or mouse, nothing happens. When paired with my windows machine, and I start using the keyboard and mouse after a hour or two, the keyboard takes a second or two to start working again. I suspect that it turns itself off, and then has to reconnect, and that in Linux, the reconnection isn't working properly. I've found other instances on the forums of people with the same symptoms, but never any clear answers. Does anyone know what's going on?
On my Raspberry (I know but I could not get any response in raspberry-forums) running raspian I have a problem with a bluetooth-keyboard.
It has bluez 4.99-2 installed and I was able to pair the keyboard and make it trusted and when I run "bluez-test-input connect <address>" I can use it as an input device, but the problem is that when the keyboard goes into a standby-mode after some inactivity the connection is lost and not reestablished. To make it work again I have to run the bluez-test-input command again.
Now when I use the keyboard on my Android-device it also goes into standby but as soon as I start to type again it automatically reestablishes the connection - this is what I would like to achieve on the Rasperry.
My fundamental problem is that I don't know anything about bluetooth really...
I assume that on Android the keyboard initiates a connection when it comes back from sleep but on Raspbian the connection is initiated from the Pi and when the connection is lost the keyboard may try to reconnect but maybe there is no "bluetooth-server" on the Pi to accept the connection but that is just guesswork from someone that really has no clue...