Skip to contentSkip to conversation

Pocket PC 2003 and Linux

Bluez-users Detlef Grittner 2 participants 6 messages Aug 25, 2004 2 messages not in the archive Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

I have a working connection between a Linux box with SuSE 9.1 (Sitecom Bluetooth dongle) and a Pocket PC 2003 HP 5550. Ping and so on is no problem.

But I found no way to transfer files from the Pocket PC to the Linux box.
The other way round works: I can send any file from my Linux box to the Pocket PC via OBEX push.
I have tried to start the obex demon with:
opd --mode OBEX --channel 10 --daemonize --path /tmp --sdp
Although the Pocket PC finds the Linux box, it says there are no known services on it.
I have tried kbluetoothd as well and now the Pocket PC claims there is a kbtserialchat service on my Linux box. But I have no idea what I can do with it on my Pocket PC. I was able to establish a PAN network. But again, although the Pocket PC claims it is working, I have no idea how to use it.

What I want to do is a obex push from the Pocket PC to the Linux box. Any ideas what am I missing?

Detlef

-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

#1 lore raw
Quoted 17 lines · Detlef Grittner

I have a working connection between a Linux box with SuSE 9.1 (Sitecom Bluetooth dongle) and a Pocket PC 2003 HP 5550.
Ping and so on is no problem.

But I found no way to transfer files from the Pocket PC to the Linux box. The other way round works: I can send any file from my Linux box to the Pocket PC via OBEX push.
I have tried to start the obex demon with:
opd --mode OBEX --channel 10 --daemonize --path /tmp --sdp Although the Pocket PC finds the Linux box, it says there are no known services on it.
I have tried kbluetoothd as well and now the Pocket PC claims there is a kbtserialchat service on my Linux box. But I have no idea what I can do with it on my Pocket PC.
I was able to establish a PAN network. But again, although the Pocket PC claims it is working, I have no idea how to use it.

Quoted 2 lines

What I want to do is a obex push from the Pocket PC to the Linux box. Any ideas what am I missing?

I can answer you for the kde-bluetooth's kbluetoothd

To look if it has registered the OBEX PUSH sdp entry you can use the graphical interface (right click on the kbluetoothd tray icon -> configuration details -> configure services and look if the kbtobexsrv is registered and active.

You can do the same thing typing in a shell:
sdptool browse FF:FF:FF:00:00:00

If the Obex Push is registered you'll get something like this:

Service Name: Obex Push Server
Service Description: KDE OBEX Object Push Service
Service RecHandle: 0x804f9a8
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
"OBEX" (0x0008)
Profile Descriptor List:
"OBEX Object Push" (0x1105)

    Version: 0x0100

Bye!

Signature · 14 lines
Simone Gotti
<[email protected]>
http://kde-bluetooth.sf.net


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
#2 lore raw

Yes, I have kbtobexsrv registered and the sdptool command output is as expected.

The problem is I can send data from the Linux client to the Pocket PC via Obex Push using the KDE tools. But I can't send data from the Pocket PC to the Linux client.

Quoted 53 lines · Simone Gotti
Quoted 17 lines · Detlef Grittner

I have a working connection between a Linux box with SuSE 9.1 (Sitecom Bluetooth dongle) and a Pocket PC 2003 HP 5550.
Ping and so on is no problem.

But I found no way to transfer files from the Pocket PC to the Linux box. The other way round works: I can send any file from my Linux box to the Pocket PC via OBEX push.
I have tried to start the obex demon with:
opd --mode OBEX --channel 10 --daemonize --path /tmp --sdp Although the Pocket PC finds the Linux box, it says there are no known services on it.
I have tried kbluetoothd as well and now the Pocket PC claims there is a kbtserialchat service on my Linux box. But I have no idea what I can do with it on my Pocket PC.
I was able to establish a PAN network. But again, although the Pocket PC claims it is working, I have no idea how to use it.

Quoted 4 lines

What I want to do is a obex push from the Pocket PC to the Linux box. Any ideas what am I missing?

I can answer you for the kde-bluetooth's kbluetoothd

To look if it has registered the OBEX PUSH sdp entry you can use the graphical interface (right click on the kbluetoothd tray icon -> configuration details -> configure services and look if the kbtobexsrv is registered and active.

You can do the same thing typing in a shell:
sdptool browse FF:FF:FF:00:00:00

If the Obex Push is registered you'll get something like this:

Service Name: Obex Push Server
Service Description: KDE OBEX Object Push Service
Service RecHandle: 0x804f9a8
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
"OBEX" (0x0008)
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100

Bye!

#3 lore raw
Quoted 6 lines · Detlef Grittner

Yes, I have kbtobexsrv registered and the sdptool command output is as expected.

The problem is I can send data from the Linux client to the Pocket PC via Obex Push using the KDE tools.
But I can't send data from the Pocket PC to the Linux client.

So the Obex Push service is right registered but the Pocket PC can't find it? you said that it can find only the kbtserialchat, can you confirm this? I can only think that probably there are registered more than one obexservice. Can you post the full output of "sdptool browse local"?

P.S. I don't know if this is the right place to talk about kdebluetooth. Probably we should move our thread to the kdebluetooth mailing list (avoiding any crossposting).

Bye!

Signature · 14 lines
Simone Gotti
<[email protected]>
http://kde-bluetooth.sf.net


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
#4 lore raw
Quoted 9 lines · Simone Gotti

So the Obex Push service is right registered but the Pocket PC can't find it?
you said that it can find only the kbtserialchat, can you confirm this?
I can only think that probably there are registered more than one obexservice. Can you post the full output of "sdptool browse local"?

P.S. I don't know if this is the right place to talk about kdebluetooth. Probably we should move our thread to the kdebluetooth mailing list (avoiding any crossposting).

Bye!

It's not only kdebluetooth that isn't working, but opd as well. And yes, kserialchat is detected by the Pocket PC.

Here is the output, which looks alright:
Browsing FF:FF:FF:00:00:00 ...
Service Name: SDP Server
Service Description: Bluetooth service discovery server Service Provider: BlueZ
Service RecHandle: 0x0
Service Class ID List:
"SDP Server" (0x1000)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 1
Version: 0x0001
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100

Service Name: Public Browse Group Root Service Description: Root of public browse hierarchy Service Provider: BlueZ
Service RecHandle: 0x804d008
Service Class ID List:
"Browse Group Descriptor" (0x1001)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100

Service Name: Obex Push Server
Service Description: KDE OBEX Object Push Service
Service RecHandle: 0x8050770
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
"OBEX" (0x0008)
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100

Service Name: KBtHandsfree
Service Description: KDE Bluetooth Phone Client
Service RecHandle: 0x8050b58
Service Class ID List:
"" (0x111e)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4
Profile Descriptor List:
"" (0x111e)
Version: 0x0101

Service Name: KBtSerialChat
Service Description: KDE Bluetooth Serial Chat Service Service RecHandle: 0x8050eb0
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 5

-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#7 lore raw
Quoted 8 lines · Detlef Grittner
Quoted 1 line

ACL data: handle 0x0029 flags 0x02 dlen 23

    L2CAP(d): cid 0x40 len 19 [psm 1]
        SDP SA Req: tid 0x3 len 0xe
          hndl 0x8051328
          max 0x1f0
          aid(s) 0x0000 - 0xffff
          cont 00

Here the pocket PC sent a SDP_ServiceAttributeRequest for every attribute in the PC sdp record.

Quoted 20 lines

< ACL data: handle 0x0029 flags 0x02 dlen 113

    L2CAP(d): cid 0x40 len 109 [psm 1]
        SDP SA Rsp: tid 0x3 len 0x68
          cnt 0x65
          aid 0x0000 (SrvRecHndl)
             uint 0x8051328
          aid 0x0001 (SrvClassIDList)
             < uuid-16 0x1105 (OBEXObjPush) >
          aid 0x0004 (ProtocolDescList)
             < < uuid-16 0x0100 (L2CAP) > <
             uuid-16 0x0003 (RFCOMM) uint 0xa > <
             uuid-16 0x0008 (OBEX) > >
          aid 0x0005 (BrwGrpList)
             < uuid-16 0x1002 (PubBrwsGrp) >
          aid 0x0009 (BTProfileDescList)
             < < uuid-16 0x1105 (OBEXObjPush) uint 0x100 > >
          aid 0x0100 (SrvName)
             str "OBEX Object Push"
          aid 0x0303 (SuppFormatsList)
             < uint 0x1 uint 0x2 uint 0x3 uint 0x4 uint 0x5 uint 0x6
Quoted 7 lines

uint 0xff >

          cont 00
Quoted 1 line

HCI Event: Number of Completed Packets(0x13) plen 5

01 29 00 01 00

This is the answer. The service can be located on the rfcomm chennale n.10 (0xa), it looks right for me.

Quoted 28 lines
Quoted 1 line

ACL data: handle 0x0029 flags 0x02 dlen 23

    L2CAP(d): cid 0x40 len 19 [psm 1]
        SDP SA Req: tid 0x4 len 0xe
          hndl 0x80516b0
          max 0x1f0
          aid(s) 0x0000 - 0xffff
          cont 00
< ACL data: handle 0x0029 flags 0x02 dlen 113
    L2CAP(d): cid 0x40 len 109 [psm 1]
        SDP SA Rsp: tid 0x4 len 0x68
          cnt 0x65
          aid 0x0000 (SrvRecHndl)
             uint 0x80516b0
          aid 0x0001 (SrvClassIDList)
             < uuid-16 0x1105 (OBEXObjPush) >
          aid 0x0004 (ProtocolDescList)
             < < uuid-16 0x0100 (L2CAP) > <
             uuid-16 0x0003 (RFCOMM) uint 0xa > <
             uuid-16 0x0008 (OBEX) > >
          aid 0x0005 (BrwGrpList)
             < uuid-16 0x1002 (PubBrwsGrp) >
          aid 0x0009 (BTProfileDescList)
             < < uuid-16 0x1105 (OBEXObjPush) uint 0x100 > >
          aid 0x0100 (SrvName)
             str "OBEX Object Push"
          aid 0x0303 (SuppFormatsList)
             < uint 0x1 uint 0x2 uint 0x3 uint 0x4 uint 0x5 uint 0x6
Quoted 2 lines

uint 0xff >

this is the same but for a different handle.
this is caused because the request for SDP_ServiceSearchRequest reported 4 handlers and 2 of this are reffered to object push. So it looks like there are 2 records for the same object push service. I Don't know if this is right and/or will be the cause of the problem.

did you have a similare behavior using kbluetoothd instead of opd ?

I hope that someone more expert than me (like Marcel) can find the source of the problem.

Bye!

Signature · 14 lines
Simone Gotti
<[email protected]>
http://kde-bluetooth.sf.net


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users