There is no debian packaging for this — just an autogen.sh
It should work on other distributions, but I haven't tried it. The main
requirement is bluez-utils 3.7, and that -x is passed to hcid to
enable the org.bluez.RFCOMM interface.
Still to do is cleaning up the obex:/// listing of bonded devices, so
that it serves desktop
rather than symlinks, so that it is usable in Nautilus. This would also
make it easier to show the device names to the user and get nice icons.
This is seriously wonderfull!
Now I'll have to install edgy on a machine this weekend :)
Johan Hedberg -
I took a look at the code and it looks good. One thing however:
About the "NFTP" service identifier, that's actually something that
btcond supported but hcid doesn't. You'll have to give the exact
UUID-128 to hcid instead as
"00005005-0000-1000-8000-0002ee000001" (I hope that's correct).
What it's about: some Nokia Symbian phones have two OBEX FTP services:
one identified with the normal UUID and another with a Nokia specific
128 bit UUID. The service found behind the normal identifier is very
limited in features on these phones while the other one supports full
OBEX FTP (don't ask me why).
Thank you man. You're awsome.… I've installed the software
succesfully and everything works. Great.….
B.t.w. mine gives me the full name after a while... and it's fully
useable in nautilus. (Pretty stable...)
I'f you wan't some testers just let me know.…(just say so on your
GReat great great.…
Thanks! This is awesome. I've been thinking for some time now, though,
that OBEX != bluetooth.
There are at least four other media commonly (or less commonly) used for
OBEX: USB, IrDA, Serial, and TCP/IP. All of these are supported by
I've been told that IrDA is somewhat harder to deal with but USB should
be pretty easy. Serial might not be worth implementing. TCP/IP, if
supported at all, probably doesn't need to be discoverable (unless of
course it's advertised through mDNS).
USB should use a different approach: mount it as a filesystem through
FUSE/obexfs. I'll check out how it all works
James Henstridge -
Wout: yeah. I implemented that a bit after posting this article.
Andrew/Alex: Matthew Garrett has plans to add bluetooth device support
to HAL, which would help here. If I can look up IrDA OBEX and Bluetooth
OBEX devices in the HAL hardware database by some property, then it
should be possible to support both: the only bluetooth specific code is
for listing the paired devices and creating RFCOMM connections.
clp: I had the same problem at first. Trouble was that by default things
get installed in /usr/local. Try the following:
./configure --sysconfdir=/etc --prefix=/usr
A lot of thanks, Andrew!
> ./configure --sysconfdir=/etc --prefix=/usr
It's a great job!
In amd64 architecture I get this problem in oss-gwobex compilation:
autoreconf2.50: running: /usr/bin/autoconf
configure.ac:11: error: possibly undefined macro: AC_PROG_LIBTOOL
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf2.50: /usr/bin/autoconf failed with exit status: 1
Salu2 clp ;)
Onkar Shinde -
Works really well. I could see name of my phone and a pretty icon. Did
file transfers in both directions without problem.
I have just one question. The autogen script in the vfs module code says
it requires automake1.9. Is this strict dependency?
Also is opebobex > 1.2. a strict dependency.
Please note that I have not even looked into code. So pardon if my
questions are redundant.
I followed the instructions above. And obex method works fine until i
try to transfer a file to the bluetooth device (sony ericsson K750i).
The error messages tells me that theres not enough free space on the
receiver (I know theres about 1Gb free, Nautilus says 0byes free).