Re: Bluetooth connection failure

Marc Chamberlin <[email protected]> Fri, 6 Mar 2020 11:34:00 -0800
Newsgroups gmane.linux.suse.kde
Message-ID <[email protected]>
On 3/6/20 5:56 AM, Patrick Shanahan wrote:
> * gumb <[email protected]> [03-06-20 04:16]:
>> On 06/03/2020 05:23, Marc Chamberlin wrote:
>>> Hello -  I am running OpenSuSE Leap 15.0 with version 5.12.5 of the
>>> Bluetooth applet on my ASUS laptop. I am trying to make a Bluetooth
>>> connection to a gadget I have (a TinyTrack4 with the Bluetooth adapter)
>>> and it is not succeeding. I have no problems with making a Bluetooth
>>> connection to my Android phone so I don't think I have done anything
>>> wrong in setting up this Bluetooth device and indeed the Bluetooth
>>> applet shows the TinyTrack4 as an available device I can connect to. But
>>> when I try to connect, it appears that I get a momentary successful
>>> connection but then it almost immediately disconnects. The messages log
>>> file shows the following error message -
>>>
>>> 2020-03-05T19:50:15.949381-08:00 marcslaptop plasmashell[2455]:
>>> org.kde.bluez: PendingCall Error: "In Progress"
>>>
>>> I have no idea what that means and Google was of no help either... And
>>> FWIW when I dual boot my laptop over to Windows 10, I have no problems
>>> connecting to my TinyTrack4 with the Bluetooth connection.
>>>
>>> So any and all help will be much appreciated, and thanks in advance... I
>>> hope some kind guru can guide me and my laptop to a joyful Bluetooth
>>> union with my TinyTrak4 gizmo...
>>>
>>>       Marc...
>>>
>> Whilst I can't offer any specific help, I've stumbled on a few quirks
>> and foibles with bluetooth recently. With one device I found that when
>> trying to pair the device using a PIN, or sending a file to the PC,
>> although the device sends the PIN / file, in Plasma the notification
>> doesn't pop up (this is on Leap 15.1) so it always fails. In that case I
>> was able to go into the Advanced Settings tab of Bluetooth Settings on
>> the PC, and check Accept automatically Trusted devices.
>>
>> With another device - a very very old feature phone, I've found the
>> connection drops after a few seconds. I've had to reboot the PC and
>> sometimes that gets it to make a stable connection. But using Wammu to
>> connect to the phone and transfer files, I can only succeed using a Leap
>> 42.3 installation on an old PC, not with Leap 15.1.
> instead of "reboot", 
>   bluetoothctl power off
>   bluetoothctl power on
> ???
>
> or 
>   bluetoothctl
> and use "help"
>   
>   

Hi Patrick,     I tried using bluetoothctl at you suggested (nice tool
BTW) and still no joy connecting to my TinyTrak4 gizmo. Here is a view
of what I tried and the results I got -

> [bluetooth]# power off
> Changing power off succeeded
> [CHG] Controller E4:A7:A0:46:83:E4 Powered: no
> [CHG] Controller E4:A7:A0:46:83:E4 Discovering: no
> [CHG] Controller E4:A7:A0:46:83:E4 Class: 0x00000000
> [bluetooth]# power on
> [CHG] Controller E4:A7:A0:46:83:E4 Class: 0x001c010c
> Changing power on succeeded
> [CHG] Controller E4:A7:A0:46:83:E4 Powered: yes
> [CHG] Controller E4:A7:A0:46:83:E4 Discovering: yes
> [CHG] Device FC:A8:9A:00:26:C0 RSSI: -54
> [NEW] Device 47:6A:53:32:EC:64 47-6A-53-32-EC-64
> [bluetooth]# devices
> Device FC:A8:9A:00:26:C0 TT4BT
> Device C0:17:4D:08:3B:2F Galaxy S8
> Device 47:6A:53:32:EC:64 47-6A-53-32-EC-64
> [bluetooth]# info FC:A8:9A:00:26:C0
> Device FC:A8:9A:00:26:C0 (public)
>         Name: TT4BT
>         Alias: TT4BT
>         Class: 0x00001f00
>         Paired: yes
>         Trusted: yes
>         Blocked: no
>         Connected: no
>         LegacyPairing: yes
>         UUID: Serial Port              
> (00001101-0000-1000-8000-00805f9b34fb)
>         RSSI: -54
> [bluetooth]# connect FC:A8:9A:00:26:C0
> Attempting to connect to FC:A8:9A:00:26:C0
> [CHG] Device FC:A8:9A:00:26:C0 Connected: yes
> [CHG] Device FC:A8:9A:00:26:C0 ServicesResolved: yes
> Failed to connect: org.bluez.Error.InProgress
> [CHG] Device FC:A8:9A:00:26:C0 ServicesResolved: no
> [CHG] Device FC:A8:9A:00:26:C0 Connected: no
> [CHG] Device FC:A8:9A:00:26:C0 RSSI: -66
> [CHG] Device FC:A8:9A:00:26:C0 RSSI: -54
> [DEL] Device 47:6A:53:32:EC:64 47-6A-53-32-EC-64
> [bluetooth]# 

Gumb -  Thanks for the insights on the other issues you have found with
Bluetooth.

Stakanov -  I don't understand what you meant by - "If laptop: try to
take off the battery and line and press for 30 seconds the interrupter."

Thanks guys for taking the time to try and help!    Marc...

-- 

  --...  ...--  .----.  ...    -..  .    .--  .-  --...  .--.  -..-  .--     --  .-  .-.  -.-. 


*Computers: the final frontier. These are the voyages of the user Marc.
His mission: to explore strange new hardware. To seek out new software
and new applications.
To boldly go where no Marc has gone before!
*
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]