From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Object Push from Nokia N93 to BlueZ fails
Date: Tue, 16 Jan 2007 15:30:00 +0100 [thread overview]
Message-ID: <1168957800.8918.20.camel@violet> (raw)
In-Reply-To: <2e9fc96f0701160623i44199950u8005dc70a9176975@mail.gmail.com>
Hi Parbhu,
> I started the rfcomm to listen on channel 9. Now, when I
> transfer file from Nokia N93 to my
> PC.
> It hangs. hcidump will give a segmentation fault.
> My configuration :
> http://gprabhunath.googlepages.com/bluez_conf
>
> hcidump : http://gprabhunath.googlepages.com/home
>
> I did the following.
> * Edited rfcomm.conf and hcid.conf (Ref: My configuration)
> * started hcid and sdpd (service bluetooth start)
> * started rfcomm to listen on channel 9 (rfcomm -i hci0
> listen 2 9)
> * started obexftpd (obexftpd -b -c /tmp/inbox)
you should only use obexftpd and not "rfcommm listen". The rfcomm
command will only create a TTY on successful connect, but then don't do
the needed OBEX connection for the push.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-01-16 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 6:16 [Bluez-users] Object Push from Nokia N93 to BlueZ fails Prabhunath G
2007-01-15 13:27 ` Marcel Holtmann
2007-01-16 14:23 ` Prabhu nath
2007-01-16 14:30 ` Marcel Holtmann [this message]
2007-01-17 16:03 ` Prabhu nath
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=1168957800.8918.20.camel@violet \
--to=marcel@holtmann.org \
--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 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.