public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Iain Hibbert <plunky@rya-online.net>
To: Lorenzo Brito Morales <lorenzo.brito@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Help
Date: Fri, 18 Sep 2009 14:18:03 +0100 (BST)	[thread overview]
Message-ID: <1253279884.019277.17552.nullmailer@galant.ukfsn.org> (raw)
In-Reply-To: <c1d79cc40909180419t45198d46h91b06ca20383fc12@mail.gmail.com>

On Fri, 18 Sep 2009, Lorenzo Brito Morales wrote:

> Hi, im a beggineer in bluez and also in programming stuff, i have read
> a coupble of things about bluez and programming,  what i want to do is
> a progran that send files to the phone is near by,,im trying to get
> work these code, its compile, and conect to the phone , but in the
> phone ask for a number security, ahta later i have to type in the
> computer...... how can i send a file whitout asking a number? just
> asking in the phone about aceptting the file

Well, in this case the phone requires authentication to connect to the
service on RFCOMM channel #1 so you are out of luck unless you can provide
the same PIN at both ends (or other pairing)

You need to investiage "OBEX Object Push". Sometimes you can send a text
file without authentication, but the person who owns the phone will
usually be required to authorise the connection (ie a message will appear,
asking if they wish to receive the file and they will need to approve)

It is a long way to do it yourself, look for "obexd" at www.bluez.org

iain



  reply	other threads:[~2009-09-18 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18 11:19 Help Lorenzo Brito Morales
2009-09-18 13:18 ` Iain Hibbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-03 23:04 help Thomas Green

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=1253279884.019277.17552.nullmailer@galant.ukfsn.org \
    --to=plunky@rya-online.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=lorenzo.brito@gmail.com \
    /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