From: "Prabhu nath" <gprabhunath@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Obex File Transfers between Nokia and BlueZ
Date: Fri, 26 Jan 2007 12:51:17 +0530 [thread overview]
Message-ID: <2e9fc96f0701252321k59b0320cld9eef725a6cc06ac@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1387 bytes --]
Dear All,
This is the 2nd time I am posting the question with more
experiments and more logs.
Has anyone tried obex file transfers between Nokia and BlueZ.
I tried with following Nokia series. In all of these I was not able to Push
a file from the Cell Phone to my Computer with BlueZ. I can push/pull a file
from BlueZ to Cell Phone
Nokia 6260
Nokia 6681
Nokia N80
Nokia E61
Nokia N93.
On the contrary, Object Push works well with MotoQ.
Here is the configuration of BlueZ :
http://brochevarevarura.googlepages.com/bluezconf
Logs of Obj. Push from Nokia to BlueZ :
http://brochevarevarura.googlepages.com/N93_to_BlueZ.htm
Logs of Obj. Push from MotoQ to BlueZ :
http://brochevarevarura.googlepages.com/MotoQ_to_BlueZ.htm
Observation :
In case of MotoQ, L2CAP is connection is getting disconnected
after SDP
negotiation and again reconnecting for the Obex file
transfer.
whereas In case of Nokia, L2CAP connection is not getting
disconnected after SDP
Negotiation.
This comparision is based on Observation, but I am not aware of rationale
behind this behaviour.
If anyone has successfully tried out Object Push from Nokia, can you please
get me the configuration and the operation.
Appreciate your help in fishing out the problem.
Thanks,
Prabhu
[-- Attachment #1.2: Type: text/html, Size: 2433 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
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
[-- 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
next reply other threads:[~2007-01-26 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 7:21 Prabhu nath [this message]
2007-01-27 11:58 ` [Bluez-users] Obex File Transfers between Nokia and BlueZ Andres Vargas - zodman
2007-01-27 11:26 ` Prabhu nath
2007-01-28 2:24 ` Albert Huang
2007-01-29 16:48 ` Prabhu nath
2007-01-30 22:04 ` Albert Huang
2007-02-01 9:55 ` 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=2e9fc96f0701252321k59b0320cld9eef725a6cc06ac@mail.gmail.com \
--to=gprabhunath@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