Welcome, Guest. Please login or register.

Login with username, password and session length
February 07, 2012, 07:16:59 AM
Pages: [1]
  Print  
Topic: Devices undiscoverable after a first discovery  (Read 873 times)
« on: May 08, 2009, 05:24:45 AM »
Mat
Newbie

View Profile
*
Karma: +0/-0
Posts: 1



Hi,

I'm writing a Java-Bluetooth app (with Bluecove), in which two devices have to send/receive text messages from each other. I'm testing it with two computers (desktop + laptop) both running Ubuntu Linux (8.10 for the desktop, 9.04 for the laptop) and both having a bluetooth USB dongle.

On both computers, Bluetooth works, I can send/receive files with my phone, I can use my Bluetooth mouse, etc.

With the application I'm writing, I have to look for other devices, which works fine. The computers can find each other, they can find the service they are offering, and they can open a connection.

BUT

This only works once. If I close the application, then restart it, a computer can not find the other one (but both still can find my cellphone), sometimes it's the laptop that can't find the desktop anymore, sometimes it's the opposite.

In any case, service discovery never works. If the laptop can find the desktop, it will try to find the right service, but will always fail.

If I then restart the laptop, the desktop will be able to find it back. It will even be able to find the service and open a connection. But the laptop won't find the desktop.



So I'm wondering: is there a kind of «you tried to discover me several times, are-you a spammer?»-system that is built into the dongles/Bluetooth protocol/Bluecove/Linux Bluetooth stack? If so, is there a way to disable it?

Or is there something else I'm doing wrong?



Many thanks if you can help me!
Logged
 
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.2 | SMF © 2006-2007, Simple Machines LLC