[Bug 214750] Re: browse device should not try to connect non-OBEX devices

[Mike Dalrymple]

I was having similar problems with a Logitech v470 bluetooth mouse.
After reading Onkar Shinde's post, I realized that I was using the UI
incorrectly.  When you right click on the Bluetooth icon there is the
"Browse Device..." option.   I was incorrectly reading this as "Browse
FOR Devices..."  To actually connect my mouse I had to do the following:

1. Right click the Bluetooth Icon
2. Select "Preferences..."
3. In the device's tab (mine was called "fourtytwo-0", yours will be different) there is a pane for "Bonded devices" that was empty.
4. I put my mouse in discovery mode and it appeared in the bonded devices screen.
5. While it was in discovery mode I clicked the "Add Trust" button (actual name may be slightly different.

So now I had a trusted device but it still didn't work and when I went
to Services, it didn't show up.  It turns out that the discovery mode is
short lived and your device needs to be in discovery mode even if it is
trusted for it to appear in the services window.  So...

6. Click the Services tab.
7. Make sure the service you want is running.
8. Select the service you want to add your device to.
9. Cick the "Add" button.
10. Put your device (in my case my mouse) in discovery mode again and it should appear.

Bob's your uncle.  I hope this helps.

As far as the bug report goes, maybe a more helpful message like "No
devices found that support browsing."  Unfortunately the term "Browse"
is incredibly overloaded in this business.

-- 
browse device should not try to connect non-OBEX devices
https://bugs.launchpad.net/bugs/214750
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez-gnome in ubuntu.