From: Marcel Holtmann <marcel@holtmann.org>
To: Marco Milanesi <marco.milanesi@iaki.it>
Cc: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] pin less obex file transfer
Date: Thu, 06 Sep 2007 11:53:37 +0200 [thread overview]
Message-ID: <1189072417.7318.36.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <20070906113357.be276256.marco.milanesi@iaki.it>
Hi Marco,
> > wild guess is that you used the wrong RFCOMM channel number. Make sure
> > you use the Object Push channel retrieved via SDP and not some static
> > magic. If the phone requires a PIN you can't do anything about it.
>
> that was it! at least... partially. now operating on obex push channel (I didn't knew that there was a specific channel for PUSH) I can approve the file receving from the mobile, but obex prints this strange error:
> root@myhost:/home/kpanic# obexftp -b 00:02:EE:46:5F:32 -B 9 -p image.jpg
> Browsing 00:02:EE:46:5F:32 ...
> Channel: 10
> Connecting...failed: FBS UUID
> Still trying to connect
> Connecting...failed: FBS UUID
> Still trying to connect
> Connecting...failed: FBS UUID
> Still trying to connect
>
> I'm noticing that also that I use -B 9 but Channel 10 is used, weird
use the OpenOBEX mailing list for any OBEX questions.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-09-06 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 8:57 [Bluez-users] pin less obex file transfer Marco Milanesi
2007-09-06 9:20 ` Marcel Holtmann
2007-09-06 9:33 ` Marco Milanesi
2007-09-06 9:53 ` Marcel Holtmann [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=1189072417.7318.36.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=marco.milanesi@iaki.it \
/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