[woppa]

We've developed an application for controlling a project we've designed with our mobile phones. We make a bluetooth connection to one of our pc's and we send xml from and to te phone to control our application. Everything has worked well so far and the application is getting bigger and bigger, we only have one problem:

There is one phone, my N95 8GB, which doesn't find any services on my notebook. All other phones using the same j2me midlet can connect to my notebook just fine. We're using RFCOMM as protocol and Serial Port (0x1101) as UUID.

What could we be overlooking here? I've been searching the internet for a few hours now and i've discovered some people with the same problem but nowhere a real solution.

Our server application runs on linux and when I search the local pc for public services I see my service:

Service Name: RC
Service Description: A bluetooth remote control
Service Provider: RC
Service RecHandle: 0x10005
Service Class ID List:
  "Serial Port" (0x1101)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 11
Profile Descriptor List:
  "Serial Port" (0x1101)
    Version: 0x0100

Nothing wrong there, the problem seems to be at the clientside ... My phone (the N95) CAN find alle devices surrounding me but when I start a servicesearch it fails with the SERVICE_SEARCH_NO_RECORDS error indicating that no service records were returned.

Does the N95 handle things different? When I don't use our application but sample code from specialised websites I get the same error. If anyone has some bright ideas about this I'd be very happy!

[Pada]

I'm using a N95 to test my BT application (using Serial Port) too and it works fine so far. The reason why my application might be working and yours not, can be due to the fact that I'm not checking the ResponseCode in the "serviceSearchCompleted" method.

The Sample BluetoothDemo that comes with NetBeans 6.5 (with Mobility Pack) doesn't check for the ResponseCode either,
nor does the Example provided in Chapter 5.4 of the JSR-82 Specifications document (Final Release 3, 28 Aug 2008), which can be download from http://jcp.org/en/jsr/detail?id=82

I changed the UUID array from "L2CAP" to "Serial Port" ofcourse:

UUID[] searchList = new UUID[1];
searchList[0] = new UUID(0x1101);

And also change the "deviceDiscovered" method to check for other classes.

I'm still a beginner with this BT programming, so please correct me if I'm wrong...

Regards
Chris

[traud]

woppa, I recommend a Bluetooth packet analyzer which should tell which data is requested and which is sent. However, I do not have one at hand for Linux right now.

[Pada]

traud, can you maybe give a URL to a BT packet analyzer which you're using or know of?

[woppa]

I've tried the examples from netbeans 6.5 and they also don't work. Today I installed a new firmware on my N95 and that also doesn't make any difference... I've made a log (with hcidump) which shows my N95 connecting, looking for services and then disconnecting again... Where does it go wrong?!

device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
> HCI Event: Connect Request (0x04) plen 10
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connect Complete (0x03) plen 11
< ACL data: handle 11 flags 0x02 dlen 10
    L2CAP(s): Info req: type 2
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Command Status (0x0f) plen 4
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> HCI Event: Read Remote Supported Features (0x0b) plen 11
> HCI Event: Command Complete (0x0e) plen 6
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
> HCI Event: Command Status (0x0f) plen 4
> ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 1 scid 0x0040
< ACL data: handle 11 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
      Connection successful
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
> HCI Event: Connection Packet Type Changed (0x1d) plen 5
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 11 flags 0x02 dlen 16
    L2CAP(s): Info rsp: type 2 result 0
      Extended feature mask 0x0003
> ACL data: handle 11 flags 0x02 dlen 10
    L2CAP(s): Info req: type 2
< ACL data: handle 11 flags 0x02 dlen 16
    L2CAP(s): Info rsp: type 2 result 0
      Extended feature mask 0x0000
> HCI Event: Remote Name Req Complete (0x07) plen 255
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 11 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 65535 
< ACL data: handle 11 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      Success
      MTU 65535 
< ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 11 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      Success
      MTU 672 
> ACL data: handle 11 flags 0x02 dlen 17
    L2CAP(d): cid 0x0040 len 13 [psm 1]
        SDP SS Req: tid 0x1 len 0x8
          pat uuid-16 0x1002 (PubBrwsGrp)
          max 65535
          cont 00
< ACL data: handle 11 flags 0x02 dlen 14
    L2CAP(d): cid 0x0040 len 10 [psm 1]
        SDP SS Rsp: tid 0x1 len 0x5
          count 0
          cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
< HCI Command: Disconnect (0x01|0x0006) plen 3
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Disconn Complete (0x05) plen 4

I think the interesting bit is here:

> ACL data: handle 11 flags 0x02 dlen 17
    L2CAP(d): cid 0x0040 len 13 [psm 1]
        SDP SS Req: tid 0x1 len 0x8
          pat uuid-16 0x1002 (PubBrwsGrp)
          max 65535
          cont 00
< ACL data: handle 11 flags 0x02 dlen 14
    L2CAP(d): cid 0x0040 len 10 [psm 1]
        SDP SS Rsp: tid 0x1 len 0x5
          count 0
          cont 00

[woppa]

The problem is solved... It appears as if the bluez-utils library (3.25) is faulty. Phones running on Symbian S60 cannot find any services... Upgrading bluez to a higher version solves the problem!

[ash9999]

Hello woppa. I am having the same problem and came across this post.. Can you please tell me exactly which bluez package you installed. I tried the latest one which is actually bluez-4.30. I suppose you are using bluecove as a jsr82 implementation for j2se.. Did you have to install any other package in linux for using bluecove(apart from the bluecove-gpl one). thanks mate..