From: Pacho Ramos <pacho@gentoo.org>
To: Bastien Nocera <hadess@hadess.net>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: Cannot send files to PC from phone
Date: Tue, 08 Apr 2014 21:02:33 +0200 [thread overview]
Message-ID: <1396983753.2061.27.camel@belkin5> (raw)
In-Reply-To: <1395487433.1597.60.camel@nuvo>
El sáb, 22-03-2014 a las 12:23 +0100, Bastien Nocera escribió:
[...]
> What are you using as the server (computer) side program? Is it
> gnome-user-share, or the obex test application in bluez?
>
> Simply having obexd installed isn't enough, you need an application to
> control it and handle authorisation, etc.
>
Only one question, even if it works ok with gnome-user-share, how can I
use that obex test application? Or is there any other command line
utility that could allow to send files to PC from phone without needing
gnome-user-share?
Thanks
next prev parent reply other threads:[~2014-04-08 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-22 9:52 Cannot send files to PC from phone Pacho Ramos
2014-03-22 11:23 ` Bastien Nocera
2014-03-22 11:45 ` Pacho Ramos
2014-03-22 11:49 ` Pacho Ramos
2014-04-08 19:02 ` Pacho Ramos [this message]
2014-04-09 10:15 ` Bastien Nocera
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=1396983753.2061.27.camel@belkin5 \
--to=pacho@gentoo.org \
--cc=hadess@hadess.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).