public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Bedot <littletux@zarb.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] PC to phone transfers with obexd 0.6
Date: Thu, 30 Oct 2008 09:10:15 +0100	[thread overview]
Message-ID: <1225354215.14322.8.camel@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 748 bytes --]

Hello,

I have noticed some bug with obexd.
Only the first chunk of data is transfered correctly.
send-files test script says the transfer completed succesfully, but the
image doesn't appear on the pĥone.

Here is send files's output :

./send-files 00:19:63:E3:5B:9A ~/test.jpg
Transfer started
  Filename = /home/ltx/test.jpg
  Name = test.jpg
  Size = 25863
Transfer progress (0 bytes)
Transfer progress (3896 bytes)
Transfer progress (7792 bytes)
Transfer progress (11688 bytes)
Transfer progress (15584 bytes)
Transfer progress (19480 bytes)
Transfer progress (23376 bytes)
Transfer progress (25863 bytes)
Transfer finished

The resulting image is attached.

Any idea of what is wrong ?

Regards,

Guillaume B.

[-- Attachment #2: test.jpg --]
[-- Type: image/jpeg, Size: 25863 bytes --]

[-- Attachment #3: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

                 reply	other threads:[~2008-10-30  8:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1225354215.14322.8.camel@localhost \
    --to=littletux@zarb.org \
    --cc=bluez-devel@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