From: redondos <redondos@gmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Problem transferring file to a Sony T630 cellular phone
Date: Tue, 15 Aug 2006 19:17:19 -0300 [thread overview]
Message-ID: <20060815221719.GH15576@refinery.twat.com.ar> (raw)
In-Reply-To: <44E237D5.50202@zubrowka.org>
[-- Attachment #1.1: Type: text/plain, Size: 1932 bytes --]
On Tue, Aug 15 23:08, Emmanuel Lesouef wrote:
> Hello bluez-users list,
>
> I'm currently trying to setup the communication between my laptop and my
> cell phone (Sony Ericsson T630)
>
> elesouef@lothlorien:~$ hcitool scan
> Scanning ...
> 00:0F:DE:CB:D4:04 Manu-T630
> elesouef@lothlorien:~$ sdptool browse 00:0F:DE:CB:D4:04 |grep "Service Name"
> Service Name: Dial-up Networking
> Service Name: Voice gateway
> Service Name: Serial Port 1
> Service Name: Serial Port 2
> Service Name: OBEX Object Push
> Service Name: IrMC Synchronization
> Service Name: HF Voice gateway
> Service Name: OBEX Basic Imaging
> Service Name: OBEX File Transfer
>
> Everything seems to be OK for now.
>
> I tried the simple way (gnome-bluetooth, "Send file to..." etc...) but
> that didn't work and I didn't saw any messages on the cellular.
>
> I then tried obexftp :
>
> elesouef@lothlorien:~$ obexftp -b -l
> Scanning ...
> Using 00:0F:DE:CB:D4:04 Manu-T630
> Failed to connect to SDP server: Operation already in progress
Maybe the error message was exactly the answer to your question. Give it
a few seconds and try again. If it doesn't work, try restarting the sdp
daemon, as well.
But maybe not, maybe you need to specify the channel number in which
your phone listens for OBEX-push transfers. sdptool should tell you that,
without the grepping, of course. :)
Once you find that out, try:
$ obexftp -b 00:0F:DE:CB:D4:04 -B <channel> -l
I think that'll work.
> I suppose there's something wrong in my setup.
I don't think so. I have been experiencies more or less the same
problems. Most of them can be worked around by knowing (with a little
experience) when/what to do when something fails. Usually, waiting until
my phone's Bluetooth icon "idles" is enough, but sometimes a little more
fiddling is required.
> Anyone got an idea ?
--
redondos
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 373 bytes --]
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-08-15 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 21:08 [Bluez-users] Problem transferring file to a Sony T630 cellular phone Emmanuel Lesouef
2006-08-15 21:42 ` digitalfredy
2006-08-15 22:17 ` redondos [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=20060815221719.GH15576@refinery.twat.com.ar \
--to=redondos@gmail.com \
--cc=bluez-users@lists.sourceforge.net \
/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