Re: Unable to transfer big files to Nokia N9

From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	linux-bluetooth@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Unable to transfer big files to Nokia N9
Date: Wed, 1 Dec 2021 23:07:46 +0100	[thread overview]
Message-ID: <cf71bdea-ec22-e4c9-016c-69e94a130607@molgen.mpg.de> (raw)
In-Reply-To: <CABBYNZLENxvXMCh6XbBSnu0jasV1F0QestEK5v2mnNUpJdw3Vw@mail.gmail.com>

Dear Luiz,

Thank you for your quick reply.

Am 01.12.21 um 19:29 schrieb Luiz Augusto von Dentz:

> On Wed, Dec 1, 2021 at 9:39 AM Paul Menzel <pmenzel@molgen.mpg.de> wrote:

>> 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.
> 
> We will need some logs, obexd and btmon, if possible.

I only managed to get the btmon trace [1]. I did `sudo modprobe -r 
btusb` and `sudo btmon -w /dev/shm/trace.log`.

Linux messages:

     [29880.100381] calling  btusb_driver_init+0x0/0x1000 [btusb] @ 28716
     [29880.239603] usbcore: registered new interface driver btusb
     [29880.239608] initcall btusb_driver_init+0x0/0x1000 [btusb] 
returned 0 after 135952 usecs
     [29880.240706] Bluetooth: hci0: unexpected event for opcode 0x0500
     [29880.241598] Bluetooth: hci0: Legacy ROM 2.5 revision 1.0 build 3 
week 17 2014
     [29880.241605] Bluetooth: hci0: Intel device is already patched. 
patch num: 32

 From the system journal:

     Dez 01 22:52:19 ersatz obexd[21139]: Transfer(0x56243fe53dd0) 
Error: Timed out waiting for response

Kind regards,

Paul

[1]: https://owww.molgen.mpg.de/~pmenzel/trace.log.7z