Trigger application on incoming bluetooth connection

[123mahaveer]

I have a bluetooth device which once paired with mobile connects automatically to my phone (similar to a bluetooth headset).
I want my application to be triggered when the connection request arrives.


Currently using my application I manually trigger a bluetooth connection to the device to read/write data from the device.

I tried out push registry but i could not figure out what should be specified in the Connection Url . I tried out btspp://localhost:device_bt_address and btspp://device_bt_address.But it did not work.

Please let me know if there is a way to trigger my application when the auto connection request is received on my phone.

[traud]

Does this help? To which service (profile) does your remote device connects to? That is the UUID you have to specify in the URL, instead of a BD_ADDR.

[123mahaveer]

Hi Traud,
Thanks for your response , I am not sure to which profile my remote device connects to , it is a health monitoring device .

Before my application gets hit, the device gets connected to my phone automatically.

Once paired it auto connects to my phone when it is switched on.

I had tried the connection for the following profiles but none of them worked.

SDP 0x0001
RFCOMM 0x0003
OBEX 0x0008
HTTP 0x000C
L2CAP 0x0100
BNEP 0x000F 16-bit
Serial Port 0x1101
ServiceDiscoveryServerServiceClassID 0x1000
BrowseGroupDescriptorServiceClassID 0x1001
PublicBrowseGroup 0x1002
OBEX Object Push Profile 0x1105
OBEX File Transfer Profile 0x1106
Personal Area Networking User 0x1115
Network Access Point 0x1116
Group Network 0x1117


As specified in the thread pointed by you , i tried out the 128 bit Profile UUID's

I had used the following format (Eg. for Serial Port Profile)

btspp://localhost:0000110100001000800000805F9B34FB

Let me know if there is anything else i could try.

OR is it impossible to trigger my application unless i know to which service my device connects to .

[traud]

Currently, your remote device connects to a well-known UUID. There is no way to override that profile from within J2ME. Specifying that UUID in J2ME, you end up with two profiles with the same UUID. Which one is taken, gets pure luck – if you do not know for what your remote device is looking for.

You have to know for which UUID your remote device is searching for. Period. You should not ‘try’. Period. You have to ‘know’. Period. If you really, really want to debug this, connect it to a computer and log that UUID with a protocol analyser.

You should use a 128 byte UUID for private UUIDs, only.