From: Tadas Dailyda <tadas@dailyda.com>
To: David Sainty <david.sainty@dtsp.co.nz>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: Sending files via bluez-gnome
Date: Sat, 18 Oct 2008 14:49:50 +0300 [thread overview]
Message-ID: <48F9CD5E.3010902@dailyda.com> (raw)
In-Reply-To: <48F9A964.2030107@dtsp.co.nz>
Hi everyone,
As of newest bluez-gnome git, bluetooth-sendto is still not updated to
obex-data-server 0.4 API (patch was already sent to this list in mail
called "Make bluetooth-sendto functional with ODS SVN head"). I also
wrote a wiki page to make migration easier:
http://wiki.muiline.com/obex-data-server/migrating_to_0.4
I installed newest bluez-gnome just recently and I was pretty much blown
away :) Why is OBEX server stuff disabled? The old code will work with
Bluez 4.x and requires no changes.
And good luck with obexd, BTW :) If you are going for a full blown
client API, you are up for a good waste of time.
Cheers,
Tadas
David Sainty wrote:
> Hi people,
>
> I notice that the "Send files to device" menu item off
> bluetooth-applet is only available if "obex-data-server" is in the
> $PATH. But I get the impression that "obexd" is trying to provide the
> DBus service that the applet is actually after (point being that
> searching the $PATH for "obex-data-server" isn't a very good test for
> "obexd" presence :)
>
> Sadly, either way (running either server) I can't seem to transfer
> files to my Blackberry. But that could be a Blackberry problem, its
> Bluetooth support is pretty dismal...
>
> Cheers,
>
> Dave
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-10-18 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 9:16 Sending files via bluez-gnome David Sainty
2008-10-18 11:49 ` Tadas Dailyda [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48F9CD5E.3010902@dailyda.com \
--to=tadas@dailyda.com \
--cc=david.sainty@dtsp.co.nz \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.