From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Unable to transfer big files to Nokia N9
Date: Wed, 1 Dec 2021 18:39:55 +0100 [thread overview]
Message-ID: <eb6d86eb-d156-d7ac-0965-181719023d51@molgen.mpg.de> (raw)
Dear Linux folks,
For the first time, I wanted to transfer a 2 MB PDF file from a Dell
Latitude E7250 with Debian sid/unstable with Linux 5.16-rc1 to a Nokia
N9 (MeeGo/Harmattan). Using the package *bluez-obexd* 5.61-1 and GNOME
41, the device was found, and paired fine. Then I selected to transfer
the 2 MB file, and after starting for a second, it timed out after the
progress bar moves forward ones and failed.
The systemd journal contains:
obexd[21139]: Transfer(0x56243fe4f790) Error: Timed out waiting for
response
Testing with a a 5 byte test text file, worked fine. Also testing with a
Galaly M32, both files were transferred without problems (though slowly
with 32 KB/s.)
Trying to connect to the device with bluetoothctl failed for me, and the
journal contained, it failed.
$ bluetoothctl
Agent registered
[bluetooth]# connect 40:98:4E:5B:CE:XX
Attempting to connect to 40:98:4E:5B:CE:XX
Failed to connect: org.bluez.Error.Failed
bluetoothd[21104]: src/service.c:btd_service_connect() a2dp-source
profile connect failed for 40:98:4E:5B:CE:B3: Protocol not available
As the Nokia N9 was once pretty popular in the Linux community, I am
pretty sure, it used to work fine in the past, and there is some
regression. It’d be great, if you could give me some hints how to
further debug the issue.
Kind regards,
Paul
next reply other threads:[~2021-12-01 17:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 17:39 Paul Menzel [this message]
2021-12-01 18:29 ` Unable to transfer big files to Nokia N9 Luiz Augusto von Dentz
2021-12-01 22:07 ` Paul Menzel
2021-12-20 21:31 ` Paul Menzel
2022-01-16 13:27 ` Paul Menzel
2022-01-28 10:36 ` Thorsten Leemhuis
2022-02-07 13:14 ` Paul Menzel
2022-02-08 7:49 ` Paul Menzel
2022-02-10 10:36 ` Thorsten Leemhuis
2022-02-11 8:29 ` Paul Menzel
2022-02-11 8:59 ` Thorsten Leemhuis
2022-02-11 16:10 ` Paul Menzel
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=eb6d86eb-d156-d7ac-0965-181719023d51@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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.