From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: James Pattinson <jamesp@hisser.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Obex / Palm TT
Date: Tue, 09 Mar 2004 22:22:36 +0100 [thread overview]
Message-ID: <1078867356.10671.70.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.58.0403092101240.24697@greebo>
Hi James,
> Do you have any more info about this application? I have just revisted bluetooth
> now I have a bt enabled handheld again. (This time it's Tungsten T3).
>
> Everything works great - would just like a way of using obex push.
>
> I tried opexftp over rfcomm, the connection got established however the file
> didn't transfer:
>
> greebo root # obexftp -d /dev/bluetooth/rfcomm/0 -p /tmp/trace.out
> Custom transport set to 'Siemens'
> Connecting...failed: connect
> Still trying to connect
why to you think you can use a Siemens custom transport to connect to a
Palm Tungsten? Actually using the RFCOMM TTY emulation should not be
necessary. Try to make a direct connection over the RFCOMM socket. I
think obexftp supports it.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-03-09 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0303121553230.9558-100000@greebo.hisser.org>
[not found] ` <1047488348.28415.117.camel@pegasus.local>
2004-03-09 21:02 ` [Bluez-users] Obex / Palm TT James Pattinson
2004-03-09 21:22 ` Marcel Holtmann [this message]
2004-03-09 21:30 ` James Pattinson
2004-03-09 22:44 ` Marcel Holtmann
2004-03-10 10:47 ` Thomas Arendsen Hein
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=1078867356.10671.70.camel@pegasus \
--to=marcel@rvs.uni-bielefeld.de \
--cc=bluez-users@lists.sourceforge.net \
--cc=jamesp@hisser.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.