Comments on: obex-data-server 0.4

By: admin

admin — Sat, 25 Oct 2008 10:54:12 +0000

Just update your bluz-libs to 3.36.
That other issue is a crasher, go to wiki.muiline.com/obex-data-server and read “Reporting bugs” then report it properly in bug tracker, but you should test with ods 0.4, not 0.3.4. I don’t think it is worth maintaining 0.3 series anymore.

By: Ajay

Ajay — Sat, 25 Oct 2008 07:06:55 +0000

Hi Tadas,

Well I am using bluez-utils version 3.32 and am unable the function sdp_extract_seqtype_safe()
but instead has in sdp_lib.h sdp_extract_seqtype() which takes in 3 paramters. So I wonder the if
3.x switch is compatible with 3.32 version.

int sdp_extract_seqtype(const uint8_t *buf, uint8_t *dtdp, int *seqlen);

I am cross compiling the libraries using Montavista toolchain for ARM9.

I had make the A2DP profile working and thought of proceeding with OBEX implementation.

But when using obex-data-server version 0.3.4 I get segmentation fault.

Logs below .. I traced it to something going wrong in cb_data = g_new0 (OdsManagerCreateBluetoothSessionData, 1);
(line 682 in ods-manager.c)

Thanks,
Ajay
——————————————–
root@(none):/opt/gnome/usr/bin# ./obex-data-server –no-daemon &
[1] 803
root@(none):/opt/gnome/usr/bin# INIT doe
** Message: obex-data-server 0.3.4
** Message: Using Session bus

root@(none):/home# ./ods-dbus-test

#./ods-dbus-test 00:18:13:19:62:6E “opp” /root/sample-pictures/Test.jpg
** Message: CreateBluetoothSession (“00:18:13:19:62:6E”, “opp”)

** (process:828): WARNING **: Error: Message did not receive a reply (timeout by message bus)
[1]+ Segmentation fault ./obex-data-server –no-daemon (wd: /opt/gnome/usr/bin)

By: admin

admin — Thu, 23 Oct 2008 06:31:34 +0000

In Bluez 3.x there were sdp_extract_seqtype and sdp_extract_seqtype_safe functions, in Bluez 4.x sdp_extract_seqtype_safe was renamed to sdp_extract_seqtype. So we are effectively calling the same function, just the name is different. As you can see in that code snippet, it’s used just like that and I used ods with Bluez 3.x for quite some time successfully. When running ./configure, it detects if libbluetooth has sdp_extract_seqtype_safe function, if it does, it is Bluez 3.x.

Timeout issue is totally solved, see migration to 0.4 API guide. Basically what you do is listen to SessionConnected and SessionConnectError signals on Manager object prior to calling CreateBluetoothSession()

Cheers,
Tadas

By: Ajay

Ajay — Thu, 23 Oct 2008 04:40:02 +0000

Tadas,

I was using obex-data-server-0.3.4, but always used to get timeout when using CreateBluetoothSession DBUS call. I heard that the timeout issue is fixed in the new release
obex-data-server 0.4 . However I see some issues with the release

1) The ifdef seems to have been reversed.(or the comments at least.
The BlueZ API sdp_extract_seqtype() takes in 3 parameters in rel 3.xx , and since this release uses 4 parameters (bytesleft seems to be extra) it gives linking issues.

#ifdef USE_BLUEZ3FUNCS
/* Using Bluez 3.x */
scanned = sdp_extract_seqtype_safe(rsp, bytesleft, &dataType, &seqlen);
#else
/* Using Bluez 4.x */
scanned = sdp_extract_seqtype(rsp,bytesleft,&dataType, &seqlen);
#endif /* USE_BLUEZ3FUNCS */

Also any help in CreateBluetoothSession() failing for me due to timeout is greatly appreciated.

Thanks
Ajay

By: Heston James

Heston James — Fri, 17 Oct 2008 17:09:21 +0000

Tadas,

Thank you once again for all your work on this release, some really excellent progress made from 0.3.4, really solid release!

Cheers,

Heston