Re: Bluetooth

[David Wright]

On Thu 20 Feb 2025 at 00:22:14 (+0500), Alexander V. Makartsev wrote:
> I suggest you to check out this link:
> https://wiki.batocera.org/hardware:compatible_dongle_list#tested_on_pc_x86_64
> Personally, I have Asus BT500 USB adapter, which is based on a
> controller chip from Realtek and it works fine on Bookworm.

> In my experience Bluetooth technology became barely usable with
> version 5.0+ (for many reasons, like stability, effective range, wifi
> interference, etc),

I'm not sure whether you meant what you wrote there. In idiomatic
English, something is becoming barely usable when it's very nearly
unusable. IOW, it's getting progressively worse.

> so my advice for you to avoid any Bluetooth ver4.0
> and lower devices, both adapters and clients.

Cheers,
David.

Re: Bluetooth

[Alexander V. Makartsev]

On 11.02.2025 09:17, Gregory Forster wrote:
I've been looking on Amazon.  Is there a bluetooth dongle I can plug 
into my desktop PC USB port that will work with Debian GNU/Linux 
12.8?  Everything I find specify s for Windows.


I suggest you to check out this link: 
https://wiki.batocera.org/hardware:compatible_dongle_list#tested_on_pc_x86_64
Personally, I have Asus BT500 USB adapter, which is based on a 
controller chip from Realtek and it works fine on Bookworm.
In my experience Bluetooth technology became barely usable with version 
5.0+ (for many reasons, like stability, effective range, wifi 
interference, etc), so my advice for you to avoid any Bluetooth ver4.0 
and lower devices, both adapters and clients.



--

 With kindest regards, Alexander.

 Debian - The universal operating system
 https://www.debian.org

Re: Bluetooth

[fxkl47BF]

On Wed, 12 Feb 2025, Hans wrote:

>
> I am very happy with this one:
>
>
> https://de.aliexpress.com/item/1005006848427195.html?spm=a2g0o.order_list.order_list_main.20.4ef95c5fLm9VN0&gatewayAdapt=glo2deu
>
>
> But maybe you get it also somewhere else, too.


does this work with regular bluetooth, bluetooth le, or both

Re: Bluetooth

[Hans]

I am very happy with this one:

https://de.aliexpress.com/item/1005006848427195.html?
spm=a2g0o.order_list.order_list_main.
20.4ef95c5fLm9VN0&gatewayAdapt=glo2deu[1]

But maybe you get it also somewhere else, too.

Best

Hans


[1] https://de.aliexpress.com/item/1005006848427195.html?
spm=a2g0o.order_list.order_list_main.
20.4ef95c5fLm9VN0&gatewayAdapt=glo2deu

Re: Bluetooth

[Russell S.]

Gregory Forster  writes:

> I've been looking on Amazon.  Is there a bluetooth dongle I can plug
> into my desktop PC USB port that will work with Debian GNU/Linux
> 12.8?  Everything I find specify s for Windows.

I'm currently using this one in Debian 12, KDE Plasma 5. Works great.

TP-Link USB Bluetooth Adapter
https://www.amazon.com/gp/product/B07V1SZCY6/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

-- 
this is my clever sig.

Re: Bluetooth

[eben]

On 2/10/25 23:17, Gregory Forster wrote:
> I've been looking on Amazon.  Is there a bluetooth dongle I can plug into my
> desktop PC USB port that will work with Debian GNU/Linux 12.8?  Everything I
> find specify s for Windows.

I have one of these:

Bus 001 Device 025: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
Dongle (HCI mode)


It has "ZEXMTE" printed on the spine, so I think that's the brand name.
Anyhow it worked great, until suddenly it didn't. Good thing my headset
connects via USB.  I don't remember changing anything, but I guess I did.
Anyhow YMMV.

Re: Bluetooth

[debian-user]

Gregory Forster  wrote:
> I've been looking on Amazon.  Is there a bluetooth dongle I can plug 
> into my desktop PC USB port that will work with Debian GNU/Linux
> 12.8? Everything I find specify s for Windows.

There's a useful page at
https://www.home-assistant.io/integrations/bluetooth/#known-working-high-performance-adapters

Re: Bluetooth

[Ceppo]

On Mon, Feb 10, 2025 at 10:17:37PM -0600, Gregory Forster wrote:
> Is there a bluetooth dongle I can plug into my desktop PC USB port 
> that will work with Debian GNU/Linux 12.8?

I don't know about Amazon, but the one from Technoethical [1] is 
advertised as fully compatible. I didn't try it, but I do use some of 
their other hardware and it works well.
Their stuff can be expensive, but my experience is that it keeps its 
promises.


[1]: https://tehnoetic.com/TET-BT4


-- 
Ceppo
https://wiki.debian.org/Ceppo
Please, encrypt our messages with the key at the link above and send me yours.


signature.asc
Description: PGP signature

Re: Bluetooth

[Charles Curley]

On Mon, 10 Feb 2025 22:17:37 -0600
Gregory Forster  wrote:

> I've been looking on Amazon.  Is there a bluetooth dongle I can plug 
> into my desktop PC USB port that will work with Debian GNU/Linux
> 12.8? Everything I find specify s for Windows.
> 

I've found these work well with Bluetooth mice:
https://www.newegg.com/plugable-technologies-usb-bt5/p/1GK-00A3-4?Item=9SIA2XBJPY8352

root@tsalmoth:~# lsusb -s 2:3
Bus 002 Device 003: ID 2230:0016 Plugable Plugable Bluetooth 5.0 Adapter
root@tsalmoth:~#

There is a note in the documentation that one should use a USB 2 port
for these if at all possible. I have been told that they are not
shielded well enough to live in a USB 3 port.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Bluetooth/SSH issue

[Jeffrey Walton]

On Sun, Jun 16, 2024 at 10:33 PM George at Clug  wrote:
>
> Rayan,
>
> On Monday, 17-06-2024 at 09:18 Ryan Nowakowski wrote:
> > On Sun, Jun 16, 2024 at 02:30:32PM -0600, Charles Curley wrote:
> > > On one of my machines, I have some interesting interference. Bluetooth
> > > works just fine, and so does networking. Bluetooth is normally disabled.
> > > However, when I have Bluetooth turned on (and after I turn it off), SSH
> > > is *slow*.
> > > Is there some sort of cross-talk issue?
> >
> > Sometimes Bluetooth and Wi-Fi share the same radio.  Are you running ssh 
> > over Wi-Fi?  Try running ssh over Ethernet while using Bluetooth.  Is ssh 
> > still slow?
>
> What do you mean by "Bluetooth and Wi-Fi share the same radio" ?
>
> In the early days of Windows 8 Tablet and laptop devices, I noticed that the 
> bluetooth mouse would move jerkily while a large download was happening over 
> Wi-Fi. Many people had this issue, and it was so annoying it lead me to tell 
> people not to use bluetooth mice.
>
> You comment might explain why this problem existed, though I am still not 
> sure what "share the same radio" actually means?

Both Wifi and Bluetooth use the globally unlicensed Industrial,
Scientific and Medical (ISM) 2.4 GHz short-range radio frequency band.

You can buy combo chips for the application. See, for example,
Qualcomm's QCA9377,
.

Jeff

Re: Bluetooth/SSH issue

[eben]

On 6/16/24 19:27, George at Clug wrote:

Rayan,

On Monday, 17-06-2024 at 09:18 Ryan Nowakowski wrote:

On Sun, Jun 16, 2024 at 02:30:32PM -0600, Charles Curley wrote:

On one of my machines, I have some interesting interference. Bluetooth
works just fine, and so does networking. Bluetooth is normally disabled.
However, when I have Bluetooth turned on (and after I turn it off), SSH
is *slow*.
Is there some sort of cross-talk issue?


Sometimes Bluetooth and Wi-Fi share the same radio.  Are you running ssh over 
Wi-Fi?  Try running ssh over Ethernet while using Bluetooth.  Is ssh still slow?


What do you mean by "Bluetooth and Wi-Fi share the same radio" ?


There is some circuitry in the computer (the radio) that does both BT and
wifi (at least 2.4GHz wifi) in some cases, probably by toggling from one to
the other.  They share the same frequency, or are close enough that the same
electronics works.

--
O freddled gruntbuggly
Thy micturations are to me
As plurdled gabbleblotchits on a lurgid bee.  -- P. V. Jeltz

Re: Bluetooth/SSH issue

[George at Clug]

Rayan,

On Monday, 17-06-2024 at 09:18 Ryan Nowakowski wrote:
> On Sun, Jun 16, 2024 at 02:30:32PM -0600, Charles Curley wrote:
> > On one of my machines, I have some interesting interference. Bluetooth
> > works just fine, and so does networking. Bluetooth is normally disabled.
> > However, when I have Bluetooth turned on (and after I turn it off), SSH
> > is *slow*.
> > Is there some sort of cross-talk issue?
> 
> Sometimes Bluetooth and Wi-Fi share the same radio.  Are you running ssh over 
> Wi-Fi?  Try running ssh over Ethernet while using Bluetooth.  Is ssh still 
> slow?

What do you mean by "Bluetooth and Wi-Fi share the same radio" ?

In the early days of Windows 8 Tablet and laptop devices, I noticed that the 
bluetooth mouse would move jerkily while a large download was happening over 
Wi-Fi. Many people had this issue, and it was so annoying it lead me to tell 
people not to use bluetooth mice.

You comment might explain why this problem existed, though I am still not sure 
what "share the same radio" actually means?

Thanks for your comment,

George.


> 
> 

Re: Bluetooth/SSH issue

[Ryan Nowakowski]

On Sun, Jun 16, 2024 at 02:30:32PM -0600, Charles Curley wrote:
> On one of my machines, I have some interesting interference. Bluetooth
> works just fine, and so does networking. Bluetooth is normally disabled.
> However, when I have Bluetooth turned on (and after I turn it off), SSH
> is *slow*.
> Is there some sort of cross-talk issue?

Sometimes Bluetooth and Wi-Fi share the same radio.  Are you running ssh over 
Wi-Fi?  Try running ssh over Ethernet while using Bluetooth.  Is ssh still slow?

Re: Bluetooth sound problems playing from a web browser

[Richmond]

Thanks, I tried it but it turns out to be a wifi/usb problem I think.

Jan Krapivin  writes:

> Have you tried a LIVE-version of another Linux distribution? It will
> be interesting to compare.
>
> вс, 7 апр. 2024 г. в 22:30, Richmond :
>
> Richmond  writes:
>
> > Richmond  writes:
> >
> >> When playing videos in a web browser, and sending the sound to
> a
> >> bluetooth speaker (amazon echo) I get playback problems;
> stuttering,
> >> sound quality reduction to AM radio level or lower). These
> things can
> >> clear up after a minute or two, or be reduced.
> >>
> >> When playing from nvlc however I get no such problems. (I
> haven't
> >> tried vlc so I am not sure if it is just that it is a command
> line).
> >>
> >> I have tried google-chrome and firefox-esr.
> >>
> >> Perhaps there is some other browser which will work? Maybe I
> need to
> >> isolate the process from the browser? I tried pop-out picture
> on you
> >> tube and it improved but there was still stuttering.
> >
> > I installed Falkon and Konqueror. I tried Falkon and it worked
> fine, no
> > sound problems. But then I tried Google-chrome again and that
> was
> > working fine too, and so was Firefox-esr. The problems have
> gone away
> > and even rebooting doesn't bring them back. Maybe one of those
> browsers
> > brought a better library with it.
>
> These problems have come back again. I have tried rebooting. I
> tried
> sending the same audio from an android phone and it works fine.
> How do I
> find out what the problems is? I cannot see errors in journalctl
>

Re: Bluetooth sound problems playing from a web browser

[Richmond]

Lee  writes:

> On Sun, Apr 7, 2024 at 3:30 PM Richmond wrote:
>>
>> Richmond writes:
>>
>> > Richmond writes:
>> >
>> >> When playing videos in a web browser, and sending the sound to a
>> >> bluetooth speaker (amazon echo) I get playback problems;
>> >> stuttering, sound quality reduction to AM radio level or
>> >> lower). These things can clear up after a minute or two, or be
>> >> reduced.
>> >>
>> >> When playing from nvlc however I get no such problems. (I haven't
>> >> tried vlc so I am not sure if it is just that it is a command
>> >> line).
>> >>
>> >> I have tried google-chrome and firefox-esr.
>> >>
>> >> Perhaps there is some other browser which will work? Maybe I need
>> >> to isolate the process from the browser? I tried pop-out picture
>> >> on you tube and it improved but there was still stuttering.
>> >
>> > I installed Falkon and Konqueror. I tried Falkon and it worked
>> > fine, no sound problems. But then I tried Google-chrome again and
>> > that was working fine too, and so was Firefox-esr. The problems
>> > have gone away and even rebooting doesn't bring them back. Maybe
>> > one of those browsers brought a better library with it.
>>
>> These problems have come back again.
>
> So unless you've updated or installed new hardware or software it's
> probably not a firmware/software issue.
>
>> I have tried rebooting. I tried sending the same audio from an
>> android phone and it works fine. How do I find out what the problems
>> is? I cannot see errors in journalctl
>
> It's possible that wifi or usb 3.0 could be interfering with your
> bluetooth speakers - eg
> https://www.zdnet.com/article/usb-3-and-usb-c-devices-can-cause-problems-with-wi-fi-and-bluetooth-connections-but-theres-a-solution/

Thanks, I think this is the answer! I was having no problems today but
noticed that the PC was connected to 5Ghz. Sometimes it connects at
2.4Ghz. When I disabled 5Ghz and forced the PC to use 2.4Ghz the problem
came back. So now all I need to do is seperate those services and/or tie
the PC to 5Ghz.

The PC is a laptop but I never move it from the desktop. I am using a
USB mouse and USB keyboard adapter to an old IBM keyboard.

> https://sortatechy.com/spot-and-fix-bluetooth-interference-with-wifi/
>
> If your PC is using wireless and can use a 5Ghz channel, try moving
> your PC wireless to a 5Ghz channel first.  If you PC only supports
> 2.4Gh wireless you can install linssid
> https://packages.debian.org/bookworm/linssid and pick a relatively
> unused channel for your PC wireless.  Or just try channels 1, 6 and 11
> and see if any of those makes a difference..
>
> If you're using a USB 3.0 device on your PC try turning it off or
> moving it to a USB 2.0 port and see if that fixes the bluetooth
> interference.
>
> Regards, Lee

Re: Bluetooth sound problems playing from a web browser

[Lee]

On Sun, Apr 7, 2024 at 3:30 PM Richmond wrote:
>
> Richmond writes:
>
> > Richmond writes:
> >
> >> When playing videos in a web browser, and sending the sound to a
> >> bluetooth speaker (amazon echo) I get playback problems; stuttering,
> >> sound quality reduction to AM radio level or lower). These things can
> >> clear up after a minute or two, or be reduced.
> >>
> >> When playing from nvlc however I get no such problems. (I haven't
> >> tried vlc so I am not sure if it is just that it is a command line).
> >>
> >> I have tried google-chrome and firefox-esr.
> >>
> >> Perhaps there is some other browser which will work? Maybe I need to
> >> isolate the process from the browser? I tried pop-out picture on you
> >> tube and it improved but there was still stuttering.
> >
> > I installed Falkon and Konqueror. I tried Falkon and it worked fine, no
> > sound problems. But then I tried Google-chrome again and that was
> > working fine too, and so was Firefox-esr. The problems have gone away
> > and even rebooting doesn't bring them back. Maybe one of those browsers
> > brought a better library with it.
>
> These problems have come back again.

So unless you've updated or installed new hardware or software it's
probably not a firmware/software issue.

> I have tried rebooting. I tried
> sending the same audio from an android phone and it works fine. How do I
> find out what the problems is? I cannot see errors in journalctl

It's possible that wifi or usb 3.0 could be interfering with your
bluetooth speakers - eg
https://www.zdnet.com/article/usb-3-and-usb-c-devices-can-cause-problems-with-wi-fi-and-bluetooth-connections-but-theres-a-solution/
https://sortatechy.com/spot-and-fix-bluetooth-interference-with-wifi/

If your PC is using wireless and can use a 5Ghz channel, try moving
your PC wireless to a 5Ghz channel first.
If you PC only supports 2.4Gh wireless you can install linssid
  https://packages.debian.org/bookworm/linssid
and pick a relatively unused channel for your PC wireless.  Or just
try channels 1, 6 and 11 and see if any of those makes a difference..

If you're using a USB 3.0 device on your PC try turning it off or
moving it to a USB 2.0 port and see if that fixes the bluetooth
interference.

Regards,
Lee

Re: Bluetooth sound problems playing from a web browser

[Jan Krapivin]

Have you tried a LIVE-version of another Linux distribution? It will be
interesting to compare.

вс, 7 апр. 2024 г. в 22:30, Richmond :

> Richmond  writes:
>
> > Richmond  writes:
> >
> >> When playing videos in a web browser, and sending the sound to a
> >> bluetooth speaker (amazon echo) I get playback problems; stuttering,
> >> sound quality reduction to AM radio level or lower). These things can
> >> clear up after a minute or two, or be reduced.
> >>
> >> When playing from nvlc however I get no such problems. (I haven't
> >> tried vlc so I am not sure if it is just that it is a command line).
> >>
> >> I have tried google-chrome and firefox-esr.
> >>
> >> Perhaps there is some other browser which will work? Maybe I need to
> >> isolate the process from the browser? I tried pop-out picture on you
> >> tube and it improved but there was still stuttering.
> >
> > I installed Falkon and Konqueror. I tried Falkon and it worked fine, no
> > sound problems. But then I tried Google-chrome again and that was
> > working fine too, and so was Firefox-esr. The problems have gone away
> > and even rebooting doesn't bring them back. Maybe one of those browsers
> > brought a better library with it.
>
> These problems have come back again. I have tried rebooting. I tried
> sending the same audio from an android phone and it works fine. How do I
> find out what the problems is? I cannot see errors in journalctl
>
>

Re: Bluetooth sound problems playing from a web browser

[Richmond]

Richmond  writes:

> Richmond  writes:
>
>> When playing videos in a web browser, and sending the sound to a
>> bluetooth speaker (amazon echo) I get playback problems; stuttering,
>> sound quality reduction to AM radio level or lower). These things can
>> clear up after a minute or two, or be reduced.
>>
>> When playing from nvlc however I get no such problems. (I haven't
>> tried vlc so I am not sure if it is just that it is a command line).
>>
>> I have tried google-chrome and firefox-esr.
>>
>> Perhaps there is some other browser which will work? Maybe I need to
>> isolate the process from the browser? I tried pop-out picture on you
>> tube and it improved but there was still stuttering.
>
> I installed Falkon and Konqueror. I tried Falkon and it worked fine, no
> sound problems. But then I tried Google-chrome again and that was
> working fine too, and so was Firefox-esr. The problems have gone away
> and even rebooting doesn't bring them back. Maybe one of those browsers
> brought a better library with it.

These problems have come back again. I have tried rebooting. I tried
sending the same audio from an android phone and it works fine. How do I
find out what the problems is? I cannot see errors in journalctl

Re: Bluetooth sound problems playing from a web browser

[Richmond]

Richmond  writes:

> When playing videos in a web browser, and sending the sound to a
> bluetooth speaker (amazon echo) I get playback problems; stuttering,
> sound quality reduction to AM radio level or lower). These things can
> clear up after a minute or two, or be reduced.
>
> When playing from nvlc however I get no such problems. (I haven't
> tried vlc so I am not sure if it is just that it is a command line).
>
> I have tried google-chrome and firefox-esr.
>
> Perhaps there is some other browser which will work? Maybe I need to
> isolate the process from the browser? I tried pop-out picture on you
> tube and it improved but there was still stuttering.

I installed Falkon and Konqueror. I tried Falkon and it worked fine, no
sound problems. But then I tried Google-chrome again and that was
working fine too, and so was Firefox-esr. The problems have gone away
and even rebooting doesn't bring them back. Maybe one of those browsers
brought a better library with it.

Re: Bluetooth sound problems Debian 12 GNOME

[Charles Curley]

On Mon, 18 Mar 2024 13:32:18 +0300
Jan Krapivin  wrote:

> Small problem is that LTS Kernel 6.1 doesn’t support this device, so
> I have used Liquorix kernel, which I have installed earlier. Though,
> I don’t need this kernel, as it haven’t helped me with sound
> interrupts, which was my hope at first.

I'm glad you reached a solution. You might also check the backports
kernel, which is currently linux-image-6.6.13+bpo-amd64
6.6.13-1~bpo12+1.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

Good news. Looks like I have solved the problem. As a last resort I have
bought another one wi-fi receiver, third one. It has *Realtek RTL8763BW*
chip

and *two antennas*. And finally all works fine. I have spent some hours,
using Bluetooth headphones, waiting for problems, but they hadn’t occur.
Small problem is that LTS Kernel 6.1 doesn’t support this device, so I have
used Liquorix kernel, which I have installed earlier. Though, I don’t need
this kernel, as it haven’t helped me with sound interrupts, which was my
hope at first. So… I bought more old Wi-fi receiver with *Realtek
RTL8761BUV* chip with antenna and it also works fine, and also works with
stable 6.1 kernel.

I am glad that situation found its resolution, though it is strange for me
that USB-dongle Bluetooth receiver (I don’t know the exact model) and
receiver on an internal wi-fi adapter (AX 210) have worked so poorly both.
Though I was in the distance not more than 2 meters from receiver.

Thanks for help

пт, 15 мар. 2024 г. в 05:21, Max Nikulin :

> On 14/03/2024 19:06, Jan Krapivin wrote:
> >
> > What do you think about QUANT parameter in */pw-top/*? Can it influence
> > sound quality? I wasn't able to change it with
> >
> > pw-metadata -n settings 0 clock.force-quantum 2048
>
> Sorry, my experience with tuning PipeWire is limited to switching audio
> profiles (A2DP codecs, HSF) from UI.
>
> I think in you case it would be more productive to enable debug logs
> either in bluetoothd or PipeWire to find either the host or the device
> drops or lost connections causing pauses till reconnect.
>
>
>

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

On 14/03/2024 19:06, Jan Krapivin wrote:


What do you think about QUANT parameter in */pw-top/*? Can it influence 
sound quality? I wasn't able to change it with


pw-metadata -n settings 0 clock.force-quantum 2048


Sorry, my experience with tuning PipeWire is limited to switching audio 
profiles (A2DP codecs, HSF) from UI.


I think in you case it would be more productive to enable debug logs 
either in bluetoothd or PipeWire to find either the host or the device 
drops or lost connections causing pauses till reconnect.

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

> You may try to discriminate hardware/software issues when you comparing
> different laptops by booting various live images (GNOME, xfce, etc.).
>

 I will try... Thank you.

What do you think about QUANT parameter in *pw-top*? Can it influence sound
quality? I wasn't able to change it with

*pw-metadata -n settings 0 clock.force-quantum 2048*

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

On 13/03/2024 17:43, Jan Krapivin wrote:
While watching */pactl subscribe /*command output, i have noticed that 
there was a change from sink 414 to sink 213 when sound interrupt occurred


"Event 'change' on sink-input #414

Can this information be of any help?


It is expected due to


Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) event25 - Haylou W1 
(AVRCP): device removed
Mar 11 23:14:11 deb pipewire-pulse[1359]: mod.protocol-pulse: client 
0x58b39dbbea40 [GNOME Settings]: ERROR command:-1 (invalid) tag:358 error:25 
(Input/output error)
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) config/udev: 
removing device Haylou W1 (AVRCP)


journalctl running with root privileges may provide more details.

You may try to discriminate hardware/software issues when you comparing 
different laptops by booting various live images (GNOME, xfce, etc.). I 
admit that it is inconvenient since it may require at least a half of an 
hour to test each variant and regular working environment is unavailable.

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

> Run the command as root, but you already have enough keywords to search
> in bug reports and discussions related to PipeWire and pulseaudio. The
> latter may have some workarounds for specific models of headphones.


Thanks, i will try to research this topic.


> PipeWire mailing list or forum may be a better place to discuss the issue.
>

OK

While watching *pactl subscribe *command output, i have noticed that there
was a change from sink 414 to sink 213 when sound interrupt occurred

"Event 'change' on sink-input #414
Event 'change' on sink-input #414
Event 'change' on sink-input #414
Event 'change' on sink-input #213
Event 'change' on sink-input #213
Event 'change' on sink-input #213"

Can this information be of any help?

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

On 12/03/2024 03:48, Jan Krapivin wrote:


"Mar 11 22:20:13 deb wireplumber[1357]: RFCOMM receive command but modem 
not available: AT+XIAOMI=1,1,102,85,88,27,174"


Just a wild guess, unlikely it is true. Headphones might report battery 
charge level using a vendor protocol extension. 85 and 88 are decreasing 
in later messages.


Sound stream may be interrupted when headphones decide to balance 
battery discharge by switching device that communicates with laptop.


Perhaps messages related to input devices are different because it is 
Wayland session while I use KDE with X11 session, so in my case 
messages are "Watching system buttons" instead of "KEYBOARD...".


You may use --since and --until journalctl options to get system logs 
for the same time intervals you posted.

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

On 12/03/2024 03:48, Jan Krapivin wrote:


As for journald i have a lot of such errors, but they don't influence 
the audio quality:


"Mar 11 22:20:13 deb wireplumber[1357]: RFCOMM receive command but modem 
not available: AT+XIAOMI=1,1,102,85,88,27,174"


Headphones might expect some response to some of these command and might 
drop connection otherwise.



journalctl -f
Hint: You are currently not seeing messages from other users and the system.
  Users in groups 'adm', 'systemd-journal' can see all messages.


Run the command as root, but you already have enough keywords to search 
in bug reports and discussions related to PipeWire and pulseaudio. The 
latter may have some workarounds for specific models of headphones.



Mar 11 23:14:11 deb gsd-media-keys[1744]: Unable to get default sink
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) event25 - Haylou W1 
(AVRCP): device removed
Mar 11 23:14:11 deb gsd-media-keys[1744]: Unable to get default sink
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) event25 - Haylou W1 
(AVRCP): device removed
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (**) Option "fd" "78"
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) UnloadModule: 
"libinput"
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) systemd-logind: 
releasing fd for 13:89
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (EE) systemd-logind: 
failed to release device: Device not taken
Mar 11 23:14:12 deb wireplumber[1357]: set volume 74 failed for transport 
/org/bluez/hci0/dev_9C_19_C2_1B_A7_25/sep4/fd1 (No such property 'Volume')
Mar 11 23:14:14 deb /usr/libexec/gdm-x-session[1449]: (II) config/udev: Adding 
input device Haylou W1 (AVRCP) (/dev/input/event25)
Mar 11 23:14:14 deb /usr/libexec/gdm-x-session[1449]: (**) Haylou W1 (AVRCP): Applying 
InputClass "libinput keyboard catchall"
Mar 11 23:14:14 deb /usr/libexec/gdm-x-session[1449]: (II) Using input driver 
'libinput' for 'Haylou W1 (AVRCP)'


So device disappears for some reason. Perhaps driver receives something 
unexpected, perhaps headphone do not receive something they expect.



Mar 11 23:24:28 deb /usr/libexec/gdm-x-session[1449]: (II) XINPUT: Adding extended input 
device "Haylou W1 (AVRCP)" (type: KEYBOARD, id 20)


Check if similar lines are logged on Mint. KEYBOARD looks a bit strange, 
but perhaps it is normal for GNOME.


PipeWire mailing list or forum may be a better place to discuss the issue.

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

It is strange. I can see in a Debian mailing list an answer

- *From*: Ottavio Caruso 
- *Date*: Mon, 11 Mar 2024 16:50:45 +

"Not sure if this is your case, I had the same problem but I upgraded from
11 to 12. The transition from pulse to pipewire was not smooth. So I nuked
anything *pulse* and *bluetooth* and reinstalled from scratch using the
Debian guide:

https://wiki.debian.org/PipeWire

Is this a brand new installation or an upgrade?"

But i can't see it in my mailbox


*ANSWER*


No, this is a clean new installation. And it looks like i have the
same problem on another laptop with Debian 12 XFCE (Pulseaudio).

But the problem is with *TWO* headsets, so i am in question whats
happening with Debian, because Linux Mint and Android works fine...





пн, 11 мар. 2024 г. в 23:48, Jan Krapivin :

> Hello again. I have used *pactl subscribe *command and i think that in
> the moment of sound interrupt there are the corresponding lines:
>
> "Event 'remove' on sink-input #353
> Event 'new' on sink-input #358
> Event 'change' on sink-input #358"
>
> As for journald i have a lot of such errors, but they don't influence the
> audio quality:
>
> "Mar 11 22:20:13 deb wireplumber[1357]: RFCOMM receive command but modem
> not available: AT+XIAOMI=1,1,102,85,88,27,174"
>
> There are some other mentions of the bluetooth/headphones, but they don't
> meet the moment of sound issues. Full journald -f log is in an attachment.
>
> I must say that i had an opportunity today to test a laptop with Debian 12
> XFCE laptop with Pulseaudio and the problem is the same there. But, as i
> said, on a laptop with Linux Mint XFCE everything is fine. That's strange.
> What is the main difference between Linux Mint and Debian here..?
>
> I also tried Liquorix 6.7 kernel but it didn't help.
>
> Thanks.
>

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

Hello again. I have used *pactl subscribe *command and i think that in the
moment of sound interrupt there are the corresponding lines:

"Event 'remove' on sink-input #353
Event 'new' on sink-input #358
Event 'change' on sink-input #358"

As for journald i have a lot of such errors, but they don't influence the
audio quality:

"Mar 11 22:20:13 deb wireplumber[1357]: RFCOMM receive command but modem
not available: AT+XIAOMI=1,1,102,85,88,27,174"

There are some other mentions of the bluetooth/headphones, but they don't
meet the moment of sound issues. Full journald -f log is in an attachment.

I must say that i had an opportunity today to test a laptop with Debian 12
XFCE laptop with Pulseaudio and the problem is the same there. But, as i
said, on a laptop with Linux Mint XFCE everything is fine. That's strange.
What is the main difference between Linux Mint and Debian here..?

I also tried Liquorix 6.7 kernel but it didn't help.

Thanks.
journalctl -f
Hint: You are currently not seeing messages from other users and the system.
  Users in groups 'adm', 'systemd-journal' can see all messages.
  Pass -q to turn off this notice.
Mar 11 21:28:16 deb wireplumber[1357]: RFCOMM receive command but modem not 
available: AT+BTRH?
Mar 11 21:28:16 deb wireplumber[1357]: RFCOMM receive command but modem not 
available: AT+XIAOMI=1,1,102,100,100,27,174
Mar 11 21:29:21 deb systemd[1331]: Started 
app-gnome-gnome\x2dterminal-6829.scope - Application launched by gsd-media-keys.
Mar 11 21:29:21 deb dbus-daemon[1367]: [session uid=1000 pid=1367] Activating 
via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.131' (uid=1000 pid=6829 
comm="gnome-terminal")
Mar 11 21:29:21 deb systemd[1331]: Starting gnome-terminal-server.service - 
GNOME Terminal Server...
Mar 11 21:29:22 deb dbus-daemon[1367]: [session uid=1000 pid=1367] Successfully 
activated service 'org.gnome.Terminal'
Mar 11 21:29:22 deb systemd[1331]: Started gnome-terminal-server.service - 
GNOME Terminal Server.
Mar 11 21:29:22 deb systemd[1331]: Started 
vte-spawn-82cf01f4-467e-44e1-b0e3-19af9cb02a2a.scope - VTE child process 6864 
launched by gnome-terminal-server process 6834.
Mar 11 21:30:27 deb systemd[1331]: Started 
app-gnome-gnome\x2dterminal-7042.scope - Application launched by gsd-media-keys.
Mar 11 21:30:27 deb systemd[1331]: Started 
vte-spawn-6e59a663-467e-40c5-9553-ad6b513aeecb.scope - VTE child process 7048 
launched by gnome-terminal-server process 6834.
Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Changing 
wallpaper...
Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Current wallpaper 
"a2.jpg"
Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Wallpapers in 
queue: 8
Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Next slide in 600 
seconds.
Mar 11 21:41:51 deb gnome-shell[1624]: JS ERROR: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such property 
“IconAccessibleDesc”
   
_promisify/proto[asyncFunc]/

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

пн, 11 мар. 2024 г. в 07:50, Max Nikulin :

>
> Are there anything in journalctl output (executed as root) around these
> events?
>

I guess that no, but i will recheck.


> Is XFCE configured to use pulseaudio or PipeWire as GNOME?
>

Pulseaudio


> Another option might be LC3 codec from Bluetooth LE (5.2 Basic Audio
> Profile) if it is supported by the headphones.
>

Unfortunately it's not supported.


> Either a software/hardware bug or some piece of software disables power
> saving for handsfree/headset profiles to achieve low latency, but for
> A2DP device tries to sleep after some period of time.
>

 Hm, i will try to research that, thank you.

Arch Linux wiki pages have long troubleshooting sections.
>

Yes, I saw but found nothing relatable to my view.

Last resort might be dumping bluetooth traffic, but perhaps it is better
> to ask in some mailing list or forum more close to Bluetooth stack
> developers.
>

I have installed Wireshark, but somehow i can't find bluetooth connection
to capture
(https://forums.debian.net/viewtopic.php?p=795020#p795020)

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

Please, respond to the mailing list.

On 11/03/2024 11:50, Max Nikulin wrote:

https://wiki.debian.org/BluetoothUser/a2dp

Last resort might be dumping bluetooth traffic


The link above has an example

dumpcap -i bluetooth0

Another tool is

hcidump -w /tmp/bt.pcap

However at first I would check logs using journalctl. Maybe debug should 
be enabled for bluez and PipeWire.

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

On 10/03/2024 21:07, Jan Krapivin wrote:
Hello! I have a problem with sound quality when using bluetooth 
headphones on Debian 12 GNOME.


Every ~20 minutes, sometimes less, sometimes more, sound interrupts for 
a 1-5 seconds with complete silence.


Are there anything in journalctl output (executed as root) around these 
events?


At first I thought that problem can be in the headphones, though it have 
worked fine with Android phone and Linux Mint XFCE on a other laptop.


Is XFCE configured to use pulseaudio or PipeWire as GNOME?

So I bought another headphones with support of different codecs: SBC, 
AAC, and AptX.


Another option might be LC3 codec from Bluetooth LE (5.2 Basic Audio 
Profile) if it is supported by the headphones.


Though in mSBC there are no interruptions. I wonder why mSBC works fine 
and SBC no..?


Either a software/hardware bug or some piece of software disables power 
saving for handsfree/headset profiles to achieve low latency, but for 
A2DP device tries to sleep after some period of time. At least SBC 
allows to decrease bitrate if connection is unreliable. I have read 
somewhere that current drivers can not increase bitrate without 
reconnection. It is just speculations, do not take it too serious.


Arch Linux wiki pages have long troubleshooting sections. Debian ones 
are partially outdated:

https://wiki.debian.org/BluetoothUser
https://wiki.debian.org/BluetoothUser/a2dp

Last resort might be dumping bluetooth traffic, but perhaps it is better 
to ask in some mailing list or forum more close to Bluetooth stack 
developers.

Re: Bluetooth driver error on boot after upgrade to bookworm

[The Wanderer]

On 2023-06-16 at 11:00, Unni wrote:

> Hello,
> 
> I am getting Bluetooth firmware error after upgrade. I've tried 
> reinstalling firmware-iwlwifi. But no luck. I've added non-free-firmware 
> in apt source, so thats not the issue. Help me to fix the error on booth.

From that last, I'm presuming that you've rebooted since the upgrade,
and that it's at boot time that the error appears.

> ~# dmesg | egrep -i 'bluetooth'
> [6.051557] Bluetooth: Core ver 2.22
> [6.051579] NET: Registered PF_BLUETOOTH protocol family
> [6.051580] Bluetooth: HCI device and connection manager initialized
> [6.051587] Bluetooth: HCI socket layer initialized
> [6.051589] Bluetooth: L2CAP socket layer initialized
> [6.051593] Bluetooth: SCO socket layer initialized
> [6.093212] bluetooth hci0: firmware: failed to load 
> intel/ibt-20-0-0.sfi (-2)
> [6.093358] bluetooth hci0: firmware: failed to load 
> intel/ibt-20-0-0.sfi (-2)

I see some things online that seem to suggest that this may be a
misleading message, and that the stack may already be using the
available firmware, but is also attempting to load this lower version
and is reporting that that attempt failed. However, those mentions are
somewhat older (2021-ish?), and the messages aren't quite the same, and
it looks like they should have been fixed by now, so I'm not assuming
that they're talking about this same thing.

Can you confirm whether you're seeing any actual functionality issues
along with this change, or whether it's just the fact that the message
is appearing that has you concerned?

FWIW, I get all of the above messages except the two about firmware (I
get two about a command timeout and a "Reading Intel version command
failed" instead)...

> [7.622442] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [7.622446] Bluetooth: BNEP filters: protocol multicast
> [7.622450] Bluetooth: BNEP socket layer initialized

...and also get these three...

> [7.623488] Bluetooth: MGMT ver 1.22
> [9.011767] Bluetooth: RFCOMM TTY layer initialized
> [9.011779] Bluetooth: RFCOMM socket layer initialized
> [9.011784] Bluetooth: RFCOMM ver 1.11
> [   32.748460] Bluetooth: hci0: Opcode 0x 401 failed: -16

...but not these. I don't actually know whether Bluetooth functionality
is available on my system, because I don't think I have any hardware
suitable to pair to it. Presumably, however, the lines we have in common
should not be relevant to what you're seeing.


$ apt-file search ibt-20-0-
firmware-iwlwifi: /lib/firmware/intel/ibt-20-0-3.ddc
firmware-iwlwifi: /lib/firmware/intel/ibt-20-0-3.sfi

(This is with the same package version you referenced; it's in both
stable and testing, at the moment.)

So ibt-20-0-3.sfi exists, but not the 20-0-0 version. The question would
then seem to be why the Bluetooth stack is attempting to load that
lower-numbered version.

Given that we're talking about firmware, it may be necessary to
reinitialize the relevant modules (et possibly cetera) after the
upgrade; that can almost certainly be done by rebooting, but should also
be possible to do manually in many cases by removing and reinserting
modules. If (as suggested above) you've rebooted, then presumably this
approach has already been tried.

(In my case, I'm fairly sure I haven't rebooted since the release, but I
was also tracking testing right up to the release so I'm already running
the same kernel etc. that you mentioned.)

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Bluetooth sound problems

[Peter von Kaehne]

> On 9 Nov 2022, at 15:12, Charles Curley  
> wrote:
> 
> On Wed, 9 Nov 2022 09:52:15 +
> Peter von Kaehne  wrote:
> 
>> My laptop (Thinkpad Yoga11e first gen) on Debian Sid is showing for
>> last few months diverse and variable sound problems.l, particularly
>> with using Bluetooth speakers, but also with Airplay. 
> 
> You might see what tips or tricks you can find at
> https://www.thinkwiki.org/wiki/ThinkWiki and at
> https://linux-hardware.org.
> 

Thank you. Both of these have no relevant information. Also, things _did_ work, 
they do not now, but drivers are present and working, 

My question is how to approach debugging the nexus of Bluetooth, Pipewire, 
Pulseaudio and whatever controls permissions to access here. 

Peter
> 
> -- 
> Does anybody read signatures any more?
> 
> https://charlescurley.com
> https://charlescurley.com/blog/
> 

Re: Bluetooth sound problems

[Charles Curley]

On Wed, 9 Nov 2022 09:52:15 +
Peter von Kaehne  wrote:

> My laptop (Thinkpad Yoga11e first gen) on Debian Sid is showing for
> last few months diverse and variable sound problems.l, particularly
> with using Bluetooth speakers, but also with Airplay. 

You might see what tips or tricks you can find at
https://www.thinkwiki.org/wiki/ThinkWiki and at
https://linux-hardware.org.



-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: BlueTooth - Acer - Qualcomm Atheros

[Alexander V. Makartsev]

On 26.08.2022 21:24, Amn wrote:


Hey there!!

As the subject suggests, this combo [BlueTooth - Acer - Qualcomm 
Atheros] is my problem.
But before going any further I'd like to leave clear that I am not, by 
any means, a Linux Power User [LPU], I just installed Debian 11 in my 
laptop and are now discovering the pros and cons of this OS, that's it!


After installing Debian 11 from an USB, I found out that the 
blue-tooth wasn't working, so searching the net I found this web pages 
that attempt to fix the issue, among them are



There is pretty good ArchWiki page about Bluetooth setup. [1]
Basically, first you need to install bluetooth stack provided by BlueZ 
and install firmware for your hardware, before you will proceed to the 
other things, like changing PulseAudio config.

To install bluetooth stack:
$ sudo apt install bluetooth bluez bluez-tools bluez-firmware blueman
And to install firmware (from non-free section [2] ):
  $ sudo apt install firmware-atheros

To check if there is a Bluetooth adapter:
    $ hciconfig -a

If there is an adapter, you can use GUI application "Bluetooth Manager" 
for an additional setup and BT device pairing.



You can also install additional packages that will help to gather 
information about your hardware:

  $ sudo apt install lshw pciutils usbutils inxi

They will provide "lshw", "lspci", "lsusb", "inxi" console utilities.


[1] https://wiki.archlinux.org/title/bluetooth
[2] https://wiki.debian.org/SourcesList

--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: Re: bluetooth audio

[Luis Mochan]

Thanks!

-- 
WLM

Re: bluetooth audio

[deloptes]

Luis Mochan wrote:

> After a recent update/upgrade in debian/bookworm my bluetooth
> earphones and my bluetooth earphones stopped working.
> I found a solution in the discussion of at
> 
>
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997862&archived=no&mbox=no&mboxmaint=no
> 
> related to bug #997862 which seemed to work for me, that is,
> installing a package libspa-0.2-bluetooth.

FYI: Same is up on the pulseaudio devel list
Bug#993011: pulseaudio-module-bluetooth: no longer detects bluetooth
headphones

Re: bluetooth keyboard

[mick crane]

On 2021-08-09 02:47, Polyna-Maude Racicot-Summerside wrote:


Does this help ?

OK, it is no great hardship to wait a second or two.
mick
--
Key ID4BFEBB31

Re: bluetooth keyboard

[deloptes]

Klaus Singvogel wrote:

> This means, that I can't change nor access my BIOS / UEFI settings by a BT
> keyboard?

It depends on the hardware and BIOS. Some newer especially with integrated
BT would implement a HID driver, so that you could, but if it would work
with each keyboard etc. no idea.
It is risky ... keep one with USB cable around for the case.

-- 
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0

Re: bluetooth keyboard

[Klaus Singvogel]

Polyna-Maude Racicot-Summerside wrote:
> On 2021-08-08 6:14 p.m., mick crane wrote:
> > I like the little generic bluetooth keyboards but it is annoying that
> > when they go to sleep it takes a few seconds for everything to wake up
> > so you can commence typing.
[...]
> It's also one of the
> reason that make it impossible to use a Bluetooth keyboard to
> communicate with GRUB or another bootloader or simply access the system
> configuration of your PC.

This means, that I can't change nor access my BIOS / UEFI settings by a BT 
keyboard?

Thanks in advance.

Best regards,
Klaus.
-- 
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D  1994-06-27

Re: bluetooth keyboard

[Polyna-Maude Racicot-Summerside]

Hi,

On 2021-08-08 6:14 p.m., mick crane wrote:
> Debian 11
> I like the little generic bluetooth keyboards but it is annoying that
> when they go to sleep it takes a few seconds for everything to wake up
> so you can commence typing.
> Is it perhaps to do with the PC polling the keyboard for activity and
> can that be made quicker ?
No, this is related to the way the bluetooth stack work.
When you use a hardware keyboard (USB or PS/2 for example), the
interface is purely thru the use of a driver in the kernel (USB driver
or PS/2 driver).
When you use a Bluetooth keyboard, the driver in the kernel or as a
module is only responsible for the dongle itself. There's a software
stack that manage authentication, connection to devices and more. This
software stack has to be launched so the keyboard can communicate with
the PC (or the PC get info from the keyboard).
This take much more time than a simple USB driver. It's also one of the
reason that make it impossible to use a Bluetooth keyboard to
communicate with GRUB or another bootloader or simply access the system
configuration of your PC.

Does this help ?
> mick
Sincerely, with solidarity,

-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development



OpenPGP_signature
Description: OpenPGP digital signature

Re: Bluetooth: Disabling ertm via sysfsutils

[Christian Britz]

Reco wrote:

1) First, if all you need is modify a kernel module option - you do not
need to tinker with /sys. Just create a file like this:

cat /etc/modprobe.d/bluetooth-ertm.conf << EOF
options bluetooth disable_ertm=1
EOF
update-initramfs -k all -u


Great, straight forward and works, thanks! :-)

Re: Bluetooth: Disabling ertm via sysfsutils

[Reco]

Hi.

On Wed, Jul 28, 2021 at 02:30:20PM +0200, Christian Britz wrote:
> If I manually restart sysfsconf.service it works!

systemd manages to start sysfsconf before starting systemd-modules-load,
so that sysfs entry does not exist at the time of boot.

This is expected from systemd SYSV unit generator, it likes to write
just about every dependency to unit, but somehow manages to miss that
one you actually need.

>  Any Idea?

Two ideas.

1) First, if all you need is modify a kernel module option - you do not
need to tinker with /sys. Just create a file like this:

cat /etc/modprobe.d/bluetooth-ertm.conf << EOF
options bluetooth disable_ertm=1
EOF
update-initramfs -k all -u


2) Second, if you absolutely need that /sys-modifying kludge - you'll
need to invoke a usual systemd trick to modify sysfsutils dependencies:

mkdir /etc/systemd/system/sysfsutils.service.d/
cat /etc/systemd/system/sysfsutils.service.d/override.conf << EOF
[Unit]
After=systemd-modules-load.service
EOF
systemctl daemon-reload

Reco

Re: Bluetooth connection problem

[deloptes]

Thomas George wrote:

> Failure to pair and connect android cellphone and Debian pc. The
> cellphone scans and finds the pc but cannot maintain the connection.
> 
> bt-device -l responds added devices moto g(7) play (04:D3:95:43:1D:43)
> 
> hciconfig -a responds hci0: Type: Primary Bus: USB BD Address
> F8:AC:65:85:BF:91 and further details including UP RUNNING PSCAN, Slave
> Accept and Device Class: Computer, Desktop workstation.
> 
> How can I establish a firm connection and stream music between the two
> devices?

bluetoothctl to pair
pulseaudio-module-bluetooth
pavucontrol to setup the preferred profile (I don't know what is the KDE
equivalent)

if issues remove ~/.config/pulse/ and reboot or login/logout, pair and setup
again as described above

you do not need hciconfig -a

Re: bluetooth problems Cambridge Silicon Radio

[deloptes]

Jeremy Ardley wrote:

> I have seen several references to the Cambridge Radio bug, with at least
> some patches being generated back in 2013 and in 2020, none of which
> seem to have made it to the kernel.
> 
> Given how hard it is to compile packages on debian without going down
> never ending rabbit holes of dependencies, it may be easier for me to
> just get a USB dongle that is known to work in the current distro.
> 
> Any suggestions on USB dongles that are known to work? Preferably V5.

1. this is the kernel - you do not have many dependencies and it is not hard
to compile.
2. I have one that reports the same ID but could be V3 or V4 - I bought it
many many years ago.
3. it could be this is a new generation (V5) that does not work.
4. Look forward to buy genuine one - there is a lot of crap made in China
out there.

Some other options pop up in my mind. Are you using it on USB3 port?
Is it a LE device?

there are rumors that both were causing problems?

Re: bluetooth problems Cambridge Silicon Radio

[Jeremy Ardley]

On 26/3/21 8:33 am, deloptes wrote:

Jeremy Ardley wrote:


Mar 25 15:30:46 client.bronzemail.com kernel: usb 1-3.2: new full-speed
USB device number 7 using xhci_hcd
Mar 25 15:30:47 client.bronzemail.com kernel: usb 1-3.2: New USB device
found, idVendor=0a12, idProduct=0001, bcdDevice=88.91
Mar 25 15:30:47 client.bronzemail.com kernel: usb 1-3.2: New USB device
strings: Mfr=0, Product=2, SerialNumber=0

Did you by chance read this?
I wonder if it is something with the stock kernel

https://askubuntu.com/questions/1098165/bluetoothctl-cant-find-default-device-but-hciconfig-hcitool-can-see-my-device
https://askubuntu.com/questions/1205962/bluetooth-dongle-problem


I have seen several references to the Cambridge Radio bug, with at least 
some patches being generated back in 2013 and in 2020, none of which 
seem to have made it to the kernel.


Given how hard it is to compile packages on debian without going down 
never ending rabbit holes of dependencies, it may be easier for me to 
just get a USB dongle that is known to work in the current distro.


Any suggestions on USB dongles that are known to work? Preferably V5.


Jeremy



OpenPGP_signature
Description: OpenPGP digital signature

Re: bluetooth problems Cambridge Silicon Radio

[deloptes]

Jeremy Ardley wrote:

> Mar 25 15:30:46 client.bronzemail.com kernel: usb 1-3.2: new full-speed
> USB device number 7 using xhci_hcd
> Mar 25 15:30:47 client.bronzemail.com kernel: usb 1-3.2: New USB device
> found, idVendor=0a12, idProduct=0001, bcdDevice=88.91
> Mar 25 15:30:47 client.bronzemail.com kernel: usb 1-3.2: New USB device
> strings: Mfr=0, Product=2, SerialNumber=0

Did you by chance read this?
I wonder if it is something with the stock kernel

https://askubuntu.com/questions/1098165/bluetoothctl-cant-find-default-device-but-hciconfig-hcitool-can-see-my-device
https://askubuntu.com/questions/1205962/bluetooth-dongle-problem

Re: bluetooth problems Cambridge Silicon Radio

[Jeremy Ardley]

On 25/3/21 3:18 pm, deloptes wrote:

Jeremy Ardley wrote:


sudo rfkill
ID TYPE  DEVICE  SOFT  HARD
2 bluetooth hci0   unblocked unblocked

what says dmesg -T when you plugin the dongle?
what says syslog (journalctl)?


sudo dmesg -T

[Thu Mar 25 15:30:43 2021] usb 1-3.2: USB disconnect, device number 6
[Thu Mar 25 15:30:46 2021] usb 1-3.2: new full-speed USB device number 7 
using xhci_hcd
[Thu Mar 25 15:30:47 2021] usb 1-3.2: New USB device found, 
idVendor=0a12, idProduct=0001, bcdDevice=88.91
[Thu Mar 25 15:30:47 2021] usb 1-3.2: New USB device strings: Mfr=0, 
Product=2, SerialNumber=0

[Thu Mar 25 15:30:47 2021] usb 1-3.2: Product: BT DONGLE10

(unplug and replug dongle)

sudo journalctl -xe

Mar 25 15:30:43 client.bronzemail.com systemd[1]: Stopped target Bluetooth.
-- Subject: A stop job for unit bluetooth.target has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit bluetooth.target has finished.
--
-- The job identifier is 7697 and the job result is done.
Mar 25 15:30:43 client.bronzemail.com systemd[1]: Started Load/Save RF 
Kill Switch Status.
-- Subject: A start job for unit systemd-rfkill.service has finished 
successfully

-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit systemd-rfkill.service has finished successfully.
--
-- The job identifier is 7689.
Mar 25 15:30:46 client.bronzemail.com kernel: usb 1-3.2: new full-speed 
USB device number 7 using xhci_hcd
Mar 25 15:30:47 client.bronzemail.com kernel: usb 1-3.2: New USB device 
found, idVendor=0a12, idProduct=0001, bcdDevice=88.91
Mar 25 15:30:47 client.bronzemail.com kernel: usb 1-3.2: New USB device 
strings: Mfr=0, Product=2, SerialNumber=0
Mar 25 15:30:47 client.bronzemail.com kernel: usb 1-3.2: Product: BT 
DONGLE10
Mar 25 15:30:47 client.bronzemail.com systemd-udevd[8630]: Process 
'/usr/lib/virtualbox/VBoxCreateUSBNode.sh 189 6 e0' failed with exit code 1.

Mar 25 15:30:47 client.bronzemail.com systemd[1]: Reached target Bluetooth.
-- Subject: A start job for unit bluetooth.target has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit bluetooth.target has finished successfully.
--
-- The job identifier is 7698.
Mar 25 15:30:52 client.bronzemail.com systemd[1]: 
systemd-rfkill.service: Succeeded.

-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit systemd-rfkill.service has successfully entered the 'dead' 
state.


--
Jeremy



OpenPGP_signature
Description: OpenPGP digital signature

Re: bluetooth problems Cambridge Silicon Radio

[deloptes]

Jeremy Ardley wrote:

> sudo rfkill
> ID TYPE  DEVICE  SOFT  HARD
> 2 bluetooth hci0   unblocked unblocked

what says dmesg -T when you plugin the dongle?
what says syslog (journalctl)?

Re: bluetooth problems Cambridge Silicon Radio

[Jeremy Ardley]

On 25/3/21 2:45 pm, deloptes wrote:

Jeremy Ardley wrote:


Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
Dongle (HCI mode)

these are widely spread I have the same (at least from the usb id)

Bus 002 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
Dongle (HCI mode)

what says rfkill list ???



sudo rfkill
ID TYPE  DEVICE  SOFT  HARD
 2 bluetooth hci0   unblocked unblocked

--
Jeremy



OpenPGP_signature
Description: OpenPGP digital signature

Re: bluetooth problems Cambridge Silicon Radio

[deloptes]

Jeremy Ardley wrote:

> Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
> Dongle (HCI mode)

these are widely spread I have the same (at least from the usb id)

Bus 002 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
Dongle (HCI mode)

what says rfkill list ???

Re: bluetooth problems Cambridge Silicon Radio

[Charles Curley]

On Thu, 25 Mar 2021 12:05:19 +0800
Jeremy Ardley  wrote:

> lsusb
...
> Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd
> Bluetooth Dongle (HCI mode)

It doesn't hurt to search on the word Linux and the USB ID:

https://duckduckgo.com/?q=linux+0a12:0001

That should give you some reading to do.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/


pgpIiq3KBRStw.pgp
Description: OpenPGP digital signature

Re: Bluetooth audio periodic disconnect

[deloptes]

Bhasker C V wrote:

> Hi all,
>   I am on bullseye.
>   I have tried and tested this with many headphones
> 
>  When on bluetooth the audio gets periodically disconnected and
>  re-connects
> to audio after 5 seconds.
>  During the time the bluetooth per-say does not get disconnected but just
> the audio stops and then starts again in 5 seconds.
>  I have already set laptop-mode tools to blacklist usb power management
>  for
> my usb adapter.
>  There are no issues with bluetooth lag or connection issues. My
>  headphones
> connect fine and work fine except for the intermittent disconnects.
> 
>  Please could someone help me fix this ?
> 

One option would be to get debian stable somehow and try if it is
reproducible there.
Another option would be to look at what the underlaying systems are doing
there. For example start pulse audio with -vvv to get more output or
inspect the data flow. Use dbus-monitor --system and --session or other to
inspect dbus event. All components in the chain could cause the issue -
kernel/driver, systemd, dbus, pulse and bluez. You have to find out which
system is causing the connection drop.
I am on buster and I play recently more with bluetooth and the phone. I
noticed that when I connect two profiles (A2DP and HFP) the audio is
lagging. When A2DP or HFP is connected only, audio is fine. When I make a
call via HFP and I finish the call, connection to phone drops.

>From what you write, I assume you use A2DP and may be it is pulse not able
to process or too sensitive, but this suggestion is just fortune telling.

I am personally disappointed by the move to bluez5 in the whole linux
world - not that bluez4 was OK, but after a lot of effort things were
working. Now bluez5 is better, but other systems are still improving to
match the new design - we pay the price.

regards 

Re: bluetooth keyboard

[mick crane]

On 2020-07-18 20:08, deloptes wrote:


When I looked in the Google glass it told me this

https://forum.manjaro.org/t/bluetooth-usb-adapter-not-being-recognized/142636/12
which lead to this
https://www.reddit.com/r/AnnePro/comments/e76ij8/csr_40_bluetooth_dongle_on_linux/



yup looks exactly the same, can't be bothered to take it to bits to look 
at chip or start patching modules.

Still, got more of a clue about bluetooth now.
cheers
mick
--
Key ID4BFEBB31

Re: bluetooth keyboard

[deloptes]

mick crane wrote:

> On 2020-07-18 01:11, deloptes wrote:
>> mick crane wrote:
>> 
>>> added myself to input group but no joy.
>>> keyboard has sticker "Generic Bluetooth Apple keyboard".
>>> I use wireless mouse which Just Works.
>>> Bluetooth Dongle I think was described as for Apple.
>>> keyboard and dongle worked on macmini.
>>> I'd have thought that Blueman would see the adapter.
>> 
>> [bluetooth]# show
>> 
>> gives the controller (the dongle)
>> 
>> [bluetooth]# discoverable on
>> 
>> enables visibility
>> 
>> [bluetooth]# scan on
>> 
>> searches for devices
>> 
>> when (and if) found do the pairing and trust the device.
> 
> root@slinky:~$ lsusb
> 
> Bus 004 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
> Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
> Dongle (HCI mode)
> 
> root@slinky:~$ hciconfig
> hci0:   Type: Primary  Bus: USB
>  BD Address: 00:1A:7D:DA:71:11  ACL MTU: 679:9  SCO MTU: 48:16
>  DOWN
>  RX bytes:2296 acl:0 sco:0 events:120 errors:0
>  TX bytes:1472 acl:0 sco:0 commands:120 errors:0
> 
> root@slinky:~$ hciconfig -a hci0 up
> Can't init device hci0: Operation not supported (95)
> 
> root@slinky:~$ systemctl start bluetooth
> root@slinky:~$ bluetoothctl
> Agent registered
> [bluetooth]# show
> No default controller available
> 
> seems a lot have people have trouble with this cheap bluetooth dongle
> Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
> Dongle (HCI mode)
> 
> As I don't really know what I'm doing I give up, I'll move the PC.
> 
> mick

Seems that I have this too

$ lsusb
Bus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
Dongle (HCI mode)

I've been using this since 2007 - all rocks

When I looked in the Google glass it told me this

https://forum.manjaro.org/t/bluetooth-usb-adapter-not-being-recognized/142636/12
which lead to this
https://www.reddit.com/r/AnnePro/comments/e76ij8/csr_40_bluetooth_dongle_on_linux/

Are you sure it is not one of those described in the articles. If so - it's
bad luck. Meanwhile I am rethinking my position on dead penalty for
producers of fakes. It is really really bad out there. An the price is not
always a guarantee for good quality, but cheep is usually a sign for bad
quality.

In case it is not one of those reported not working, when enabled, below is
some output to compare. I also never had to use hciconfig to configure it -
it is systemd doing it via I don't know what - probably udev.

I was also thinking of some details:
- Does it work on other machines - different kernel or OS?
- Here ATM it is running on 4.19.
- I'm just not sure if it needs firmware. I have not rebooted the PC for
months and I can't find anything in the logs.
- What about groups (are you in bluetooth)?
- What about dbus?

regards

# hciconfig
hci0:   Type: Primary  Bus: USB
BD Address: 00:10:60:xx:xx:xx ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:126491975 acl:406135 sco:3168 events:4620 errors:0
TX bytes:707462 acl:3276 sco:3173 commands:1463 errors:0

# systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
   Active: active (running) since Sat 2020-07-18 20:53:04 CEST; 2s ago
 Docs: man:bluetoothd(8)
 Main PID: 7509 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 4915)
   Memory: 2.1M
   CGroup: /system.slice/bluetooth.service
   └─7509 /usr/lib/bluetooth/bluetoothd

Jul 18 20:53:04 fujitsu systemd[1]: Starting Bluetooth service...
Jul 18 20:53:04 fujitsu bluetoothd[7509]: Bluetooth daemon 5.50
Jul 18 20:53:04 fujitsu bluetoothd[7509]: Starting SDP server
Jul 18 20:53:04 fujitsu systemd[1]: Started Bluetooth service.
Jul 18 20:53:04 fujitsu bluetoothd[7509]: Bluetooth management interface
1.14 initialized
Jul 18 20:53:04 fujitsu bluetoothd[7509]: Sap driver initialization failed.
Jul 18 20:53:04 fujitsu bluetoothd[7509]: sap-server: Operation not
permitted (1)
Jul 18 20:53:04 fujitsu bluetoothd[7509]: Endpoint registered: sender=:1.35
path=/MediaEndpoint/A2DPSource
Jul 18 20:53:04 fujitsu bluetoothd[7509]: Endpoint registered: sender=:1.35
path=/MediaEndpoint/A2DPSink


# hciconfig -a version hci0
Warning: unknown command - "hci0"
hci0:   Type: Primary  Bus: USB
BD Address: 00:10:60:xx:xx:xx  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:126493351 acl:406135 sco:3168 events:4725 errors:0
TX bytes:718970 acl:3276 sco:3173 commands:1568 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'fujitsu'
Class: 0x3c0104
Service Classes: Rendering, Capturing, Object Transfer, Audio
Device Class: Computer, Desktop workstation
HCI Version: 2.1 (0x4)  Revisi

Re: bluetooth keyboard

[mick crane]

On 2020-07-18 01:11, deloptes wrote:

mick crane wrote:


added myself to input group but no joy.
keyboard has sticker "Generic Bluetooth Apple keyboard".
I use wireless mouse which Just Works.
Bluetooth Dongle I think was described as for Apple.
keyboard and dongle worked on macmini.
I'd have thought that Blueman would see the adapter.


[bluetooth]# show

gives the controller (the dongle)

[bluetooth]# discoverable on

enables visibility

[bluetooth]# scan on

searches for devices

when (and if) found do the pairing and trust the device.


root@slinky:~$ lsusb

Bus 004 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)


root@slinky:~$ hciconfig
hci0:   Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:11  ACL MTU: 679:9  SCO MTU: 48:16
DOWN
RX bytes:2296 acl:0 sco:0 events:120 errors:0
TX bytes:1472 acl:0 sco:0 commands:120 errors:0

root@slinky:~$ hciconfig -a hci0 up
Can't init device hci0: Operation not supported (95)

root@slinky:~$ systemctl start bluetooth
root@slinky:~$ bluetoothctl
Agent registered
[bluetooth]# show
No default controller available

seems a lot have people have trouble with this cheap bluetooth dongle
Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)


As I don't really know what I'm doing I give up, I'll move the PC.

mick
--
Key ID4BFEBB31

Re: bluetooth keyboard

[deloptes]

mick crane wrote:

> added myself to input group but no joy.
> keyboard has sticker "Generic Bluetooth Apple keyboard".
> I use wireless mouse which Just Works.
> Bluetooth Dongle I think was described as for Apple.
> keyboard and dongle worked on macmini.
> I'd have thought that Blueman would see the adapter.

[bluetooth]# show

gives the controller (the dongle)

[bluetooth]# discoverable on

enables visibility

[bluetooth]# scan on

searches for devices

when (and if) found do the pairing and trust the device.

Re: bluetooth keyboard

[riveravaldez]

> added myself to input group but no joy.
> keyboard has sticker "Generic Bluetooth Apple keyboard".
> I use wireless mouse which Just Works.
> Bluetooth Dongle I think was described as for Apple.
> keyboard and dongle worked on macmini.
> I'd have thought that Blueman would see the adapter.

Just in case?

«make sure you have bluetoothctl and hcitool installed.»[1]

[1] 
https://wiki.archlinux.org/index.php/Apple_Keyboard#Magic_Keyboard_does_not_connect

Re: bluetooth keyboard

[mick crane]

On 2020-07-17 21:16, Dan Ritter wrote:

mick crane wrote:

hello,
somebody gave me an old macmini and a bluetooth keyboard.
I don't know anything about bluetooth.
I'd like to use the keyboard with buster because the wired keyboard 
wire is

not long enough.
I got a usb bluetooth dongle (whatever they are called)
The kernel seems to see it from dmesg

[   84.976912] usb 3-2: new low-speed USB device number 3 using 
uhci_hcd
[   85.173975] usb 3-2: New USB device found, idVendor=046d, 
idProduct=c31c,

bcdDevice=64.00
[   85.173979] usb 3-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[   85.173982] usb 3-2: Product: USB Keyboard
[   85.173984] usb 3-2: Manufacturer: Logitech
[   85.210624] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.1/usb3/3-2/3-2:1.0/0003:046D:C31C.0002/input/input20
[   85.269388] hid-generic 0003:046D:C31C.0002: input,hidraw1: USB HID 
v1.10

Keyboard [Logitech USB Keyboard] on usb-:00:1a.1-2/input0
[   85.303712] input: Logitech USB Keyboard Consumer Control as 
/devices/pci:00/:00:1a.1/usb3/3-2/3-2:1.1/0003:046D:C31C.0003/input/input21
[   85.361073] input: Logitech USB Keyboard System Control as 
/devices/pci:00/:00:1a.1/usb3/3-2/3-2:1.1/0003:046D:C31C.0003/input/input22
[   85.361251] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID 
v1.10

Device [Logitech USB Keyboard] on usb-:00:1a.1-2/input1


That's not a bluetooth keyboard. That's a Logitech proprietary
dongle wireless keyboard. Nothing wrong with that.

Since the kernel sees it as a HID (human interface device), it
should be a keyboard already.


what to do to enable the adapter and get keyboard working ?


It should be working. If you're in X, maybe you don't have
permissions to use /dev/input/* ? Put yourself in the input
group.

-dsr-


added myself to input group but no joy.
keyboard has sticker "Generic Bluetooth Apple keyboard".
I use wireless mouse which Just Works.
Bluetooth Dongle I think was described as for Apple.
keyboard and dongle worked on macmini.
I'd have thought that Blueman would see the adapter.

mick
--
Key ID4BFEBB31

Re: bluetooth keyboard

[Dan Ritter]

mick crane wrote: 
> hello,
> somebody gave me an old macmini and a bluetooth keyboard.
> I don't know anything about bluetooth.
> I'd like to use the keyboard with buster because the wired keyboard wire is
> not long enough.
> I got a usb bluetooth dongle (whatever they are called)
> The kernel seems to see it from dmesg
> 
> [   84.976912] usb 3-2: new low-speed USB device number 3 using uhci_hcd
> [   85.173975] usb 3-2: New USB device found, idVendor=046d, idProduct=c31c,
> bcdDevice=64.00
> [   85.173979] usb 3-2: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [   85.173982] usb 3-2: Product: USB Keyboard
> [   85.173984] usb 3-2: Manufacturer: Logitech
> [   85.210624] input: Logitech USB Keyboard as 
> /devices/pci:00/:00:1a.1/usb3/3-2/3-2:1.0/0003:046D:C31C.0002/input/input20
> [   85.269388] hid-generic 0003:046D:C31C.0002: input,hidraw1: USB HID v1.10
> Keyboard [Logitech USB Keyboard] on usb-:00:1a.1-2/input0
> [   85.303712] input: Logitech USB Keyboard Consumer Control as 
> /devices/pci:00/:00:1a.1/usb3/3-2/3-2:1.1/0003:046D:C31C.0003/input/input21
> [   85.361073] input: Logitech USB Keyboard System Control as 
> /devices/pci:00/:00:1a.1/usb3/3-2/3-2:1.1/0003:046D:C31C.0003/input/input22
> [   85.361251] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10
> Device [Logitech USB Keyboard] on usb-:00:1a.1-2/input1

That's not a bluetooth keyboard. That's a Logitech proprietary
dongle wireless keyboard. Nothing wrong with that.

Since the kernel sees it as a HID (human interface device), it
should be a keyboard already.

> what to do to enable the adapter and get keyboard working ?

It should be working. If you're in X, maybe you don't have
permissions to use /dev/input/* ? Put yourself in the input
group.

-dsr-

Re: bluetooth mouse and keyboard stop working after some time

[Federico Beffa]

Thanks for the suggestions.

After some more experiments I think that it's not a timeout/power
problem, but it's probably a bug related to suspend/resume.

Re: bluetooth mouse and keyboard stop working after some time

[Jonas Smedegaard]

Hi Federico,

Quoting Federico Beffa (2019-11-18 20:54:37)
> I recently purchased bluetooth mouse and keyboard to use with a Debian 
> 9 machine.  I could pair the devices without problems and they do work 
> for some time. However, after some time they stop working.  I suspect 
> that some timeout triggers. (After a reboot they start working again 
> for some time.)
> 
> I'm using kernel linux-image-4.19.0-0.bpo.6-amd6.
> 
> Below is an excerpt from /var/log/syslog showing that the Bluetooth 
> module is shutting down.
> 
> Any suggestions?

Try disable power management for the bluetooth device driver.

Easiest to play with that is probably to install and use powertop, which 
hints at what it changes so that (if succesful) you can transfer those 
changes to e.g. lines in a new file /etc/sysctl.d/local-powersave.conf

NB! You may need to disable power management not only from device driver 
but also drivers of underlying bus.  You can get a topological view of 
the USB bus with this command:

  lsusb --tree

...and a topological view of your whole machine with this:

  lshw | less


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Re: bluetooth and Debian 10

[deloptes]

Bruce Byfield wrote:

> Can anyone suggest a solution? I'm sure I'm missing something obvious,
> but I'm at a loss to suggest what. Any suggestions?

it was asked recently already.

reported that removing the pairing and ~/.pulse or ~/.config/pulse after
which reboot and repair worked. 

Try first removing ~/.pulse and/or ~/.config/pulse before you login with
your user. if it does not help try unpair, remove  ~/.pulse and/or
~/.config/pulse and pair again.

Re: Bluetooth audio problem

[Mark Fletcher]

On Sat, Mar 23, 2019 at 08:24:30AM -0500, Nicholas Geovanis wrote:
> On Fri, Mar 22, 2019 at 9:29 AM Mark Fletcher  wrote:
> 
> >
> > So this turned out to be a weirdie -- if I dropped the "sudo" my
> > original command worked.
> > So now, suddenly from that update that started this thread, if I run the
> > pactl command as an unprivileged user, it works fine.
> 
> 
> Is it possible that you had previously started pulseaudio as root, and
> could no longer communicate with it as an unprivileged user?
> I ask this having been a pulseaudio victim myself sometimes.
> 
> 

Hmm, interesting idea, but the situation I was previously in pertained 
over a period since Stretch became Stable until shortly before my 
original mail in this thread (sometime in February if I recall 
correctly). Over, naturally, multiple reboots.

For that period, I had to use sudo when issuing the pactl command (in 
Jessie and previously, the pactl command wasn't necessary at all).

So I guess I could have had some sort of configuration which repeatedly 
put me in that situation on every reboot, and the update that "created 
the problem" actually fixed whatever *that* problem was... otherwise, no 
I don't think so.

Thanks for the suggestion though

Mark

Re: Bluetooth audio problem

[Nicholas Geovanis]

On Fri, Mar 22, 2019 at 9:29 AM Mark Fletcher  wrote:

>
> So this turned out to be a weirdie -- if I dropped the "sudo" my
> original command worked.
> So now, suddenly from that update that started this thread, if I run the
> pactl command as an unprivileged user, it works fine.


Is it possible that you had previously started pulseaudio as root, and
could no longer communicate with it as an unprivileged user?
I ask this having been a pulseaudio victim myself sometimes.


> Mark
>
>

Re: Bluetooth audio problem

[Mark Fletcher]

On Fri, Mar 22, 2019 at 08:44:46PM +0100, deloptes wrote:
> Mark Fletcher wrote:
> 
> > So this turned out to be a weirdie -- if I dropped the "sudo" my
> > original command worked.
> > 
> > So now, suddenly from that update that started this thread, if I run the
> > pactl command as an unprivileged user, it works fine. I have no idea why
> > it changed but I'm just happy I have it working again.
> 
> you can mark also as solved, if solved
> 

True, I could have. But I don't think it will kill interested people who 
follow after to read a 3-mail thread to see the resolution.

Re: Bluetooth audio problem

[deloptes]

Mark Fletcher wrote:

> So this turned out to be a weirdie -- if I dropped the "sudo" my
> original command worked.
> 
> So now, suddenly from that update that started this thread, if I run the
> pactl command as an unprivileged user, it works fine. I have no idea why
> it changed but I'm just happy I have it working again.

you can mark also as solved, if solved

Re: Bluetooth audio problem

[Mark Fletcher]

On Sun, Mar 03, 2019 at 06:04:05PM +0100, deloptes wrote:
> Mark Fletcher wrote:
> 
> > Hello
> > 
> > Since upgrading to Stretch shortly after it became stable, I have had to
> > execute the following after a reboot before being able to connect to
> > bluetooth devices using the Gnome bluetooth applet:
> > 
> > $ sudo pactl load-module module-bluetooth-discover
> > 



> > Now, when I run the above command it is erroring out with:
> > 
> > xcb_connection_has_error() returned true
> > Connection failure: Connection refused
> > pa_context_connect() failed: Connection refused
> > 
> 
> 
> When I want to debug pulse I do
> 
> echo "autospawn = no" > ~/.pulse/client.conf
> 
> kill PA and run it from command line with -v option you can also
> use --log-level (man pulseaudio)
> 
> perhaps you can see what is the problem there. If not it might be dbus issue
> with permissions - check the dbus settings
> 
> Also some times it helps to remove the ~/.pulse directory and restart
> pulseaudio.
> 

So this turned out to be a weirdie -- if I dropped the "sudo" my 
original command worked.

So now, suddenly from that update that started this thread, if I run the 
pactl command as an unprivileged user, it works fine. I have no idea why 
it changed but I'm just happy I have it working again.

Mark

Re: Bluetooth audio problem

[deloptes]

Mark Fletcher wrote:

> Hello
> 
> Since upgrading to Stretch shortly after it became stable, I have had to
> execute the following after a reboot before being able to connect to
> bluetooth devices using the Gnome bluetooth applet:
> 
> $ sudo pactl load-module module-bluetooth-discover
> 
> Without that command, needed once only after each reboot, the Gnome
> applet is unable to connect to any bluetooth audio devices, eg my
> headphones to be used as an audio sink, or my iPhone to be used as an
> audio source. Once that command has been issued once, everything works
> as it should, and continues to do so until the next reboot.
> 
> I've been away for a couple of weeks and so hadn't installed updates to
> my stretch installation for something like 3 weeks, until Saturday this
> week when I installed updates. Unfortunately I didn't pay enough
> attention to exactly what was upgraded but I _believe_ I saw udev in the
> list of things getting upgraded.
> 
> Now, when I run the above command it is erroring out with:
> 
> xcb_connection_has_error() returned true
> Connection failure: Connection refused
> pa_context_connect() failed: Connection refused
> 
> Googling for this has only turned up old information which does not seem
> to relate to the problem I am facing. In most cases the context is audio
> not working; in my case audio output through speakers plugged into the
> sound card is working fine, USB mic connected by a wire is working
> fine, the only problem is anything bluetooth.
> 
> Bluetooth on this machine is provided by a USB bluetooth dongle which I
> have been using for ages.
> 
> Can anyone suggest steps to diagnose?
> 


When I want to debug pulse I do

echo "autospawn = no" > ~/.pulse/client.conf

kill PA and run it from command line with -v option you can also
use --log-level (man pulseaudio)

perhaps you can see what is the problem there. If not it might be dbus issue
with permissions - check the dbus settings

Also some times it helps to remove the ~/.pulse directory and restart
pulseaudio.

regards

Re: bluetooth not working

[deloptes]

Pierre Frenkiel wrote:

> 
> this gives:
> --> pactl list short
> 0   module-alsa-sinkdevice=default
> 1   module-alsa-source  device=default
> 2   module-native-protocol-unix
> 0   alsa_output.default module-alsa-sink.c  s16le 2ch
> 44100Hz   IDLE
> 0   alsa_output.default.monitor module-alsa-sink.c  s16le
> 2ch 44100Hz   IDLE
> 1   alsa_input.default  module-alsa-source.cs16le 2ch
> 44100Hz   IDLE
> 0   protocol-native.c   pactl
> 
> but I have before to check whether pulseaudio is still alive, as it exits
> very often, as if there was a timeout, which is not the case.
> 

if it exits, it might be crashing. 

I don't see in the output above some other device except your pc

25  module-bluez5-devicepath=/org/bluez/hci0/dev_40_98_4E_90_56_E3
autodetect_mtu=0

3   alsa_output.pci-_00_1b.0.analog-stereo.monitor 
module-alsa-card.c  s16le 2ch 44100Hz   SUSPENDED
4   alsa_input.pci-_00_1b.0.analog-stereo   module-alsa-card.c 
s16le 2ch 44100Hz   RUNNING

5   bluez_source.40_98_4E_90_56_E3.a2dp_source 
module-bluez5-device.c  s16le 2ch 44100Hz   RUNNING

Where I usually have to manually do

pactl load-module module-loopback
source=bluez_source.40_98_4E_90_56_E3.a2dp_source
sink=alsa_output.pci-_00_1b.0.analog-stereo


> 
>>> I also tried "pactl load-module module-bluetooth-discover" with the
>>> following result
>>>
>>> Connection failure: Connection refused
>>> pa_context_connect() failed: Connection refused
>>>
>>
>> Are you trying to do this from root?
> 
>no, but same remark as above for pulseaudio.

If it crashes I noted that restarting PA does not repair everything, but I
have to logout and login (it starts in user session). Either find out what
needs to be done after restarting PA, to fully recover or logout and login.

In any case crashing PA is not normal. I found out for debugging you could
kill PA and start it from the command line, but better disable autostart
and logout/login and start manually from command line.

echo "autospawn = no" > ~/.pulse/client.conf

> 
>it gives:
>-->pactl load-module module-bluetooth-discover
>3
> 
> I tried again bluetoothctl:
> 
> bluetooth]# scan on
> Discovery started
> [CHG] Controller 3C:95:09:46:D6:74 Discovering: yes
> [CHG] Device B0:34:95:41:6A:43 RSSI: -89
> [CHG] Device 57:88:14:78:8A:48 RSSI: -43
> 
> [bluetooth]# devices
> Device B0:34:95:41:6A:43 B0-34-95-41-6A-43
> Device 57:88:14:78:8A:48 SLBB  4 A1
> [bluetooth]# connect 57:88:14:78:8A:48
> Attempting to connect to 57:88:14:78:8A:48
> Failed to connect: org.bluez.Error.Failed
> 

I think it never paired properly - did you try blueman?
You may need to clean up ~/.pulse directory and start over. There PA writes
information about devices already used and configured.

> As I don't need to use the speaker far from the laptop, I solved
> the problem by ordering a small wired speaker ...
> But it's a pity that this basic facility is so difficult to setup on
> Linux, and so easy on Windows( 30 seconds)

well - in Windows they don't use bluez5 yet I guess - not sure about windows
10. In linux it is work in progress and I also suffer a lot as it is not
mature enough to be used easily, but was already adopted by the most
distros and causes a lot of headache.

Here are some links if you are interested

https://wiki.archlinux.org/index.php/Bluetooth_headset
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting
https://fedoraproject.org/wiki/How_to_debug_PulseAudio_problems

Re: bluetooth not working

[Pierre Frenkiel]

On Sun, 25 Mar 2018, deloptes wrote:


Have you paired and trusted the device already?


  yes, and it seemed to work.


you could list all connected devices in pulseaudio with
$ pactl list short


this gives:
   --> pactl list short
   0   module-alsa-sinkdevice=default
   1   module-alsa-source  device=default
   2   module-native-protocol-unix
   0   alsa_output.default module-alsa-sink.c  s16le 2ch 44100Hz
   IDLE
   0   alsa_output.default.monitor module-alsa-sink.c  s16le 2ch 
44100Hz   IDLE
   1   alsa_input.default  module-alsa-source.cs16le 2ch 44100Hz
   IDLE
   0   protocol-native.c   pactl

but I have before to check whether pulseaudio is still alive, as it exits very 
often, as if there was a timeout,
which is not the case.



I also tried "pactl load-module module-bluetooth-discover" with the
following result

Connection failure: Connection refused
pa_context_connect() failed: Connection refused



Are you trying to do this from root?


  no, but same remark as above for pulseaudio.

  it gives:
  -->pactl load-module module-bluetooth-discover
  3

I tried again bluetoothctl:

   bluetooth]# scan on
   Discovery started
   [CHG] Controller 3C:95:09:46:D6:74 Discovering: yes
   [CHG] Device B0:34:95:41:6A:43 RSSI: -89
   [CHG] Device 57:88:14:78:8A:48 RSSI: -43

   [bluetooth]# devices
   Device B0:34:95:41:6A:43 B0-34-95-41-6A-43
   Device 57:88:14:78:8A:48 SLBB  4 A1
   [bluetooth]# connect 57:88:14:78:8A:48
   Attempting to connect to 57:88:14:78:8A:48
   Failed to connect: org.bluez.Error.Failed

As I don't need to use the speaker far from the laptop, I solved
the problem by ordering a small wired speaker ...
But it's a pity that this basic facility is so difficult to setup on Linux, 
and so easy on Windows( 30 seconds)


best regards,
--
Pierre Frenkiel

Re: bluetooth not working

[deloptes]

Pierre Frenkiel wrote:

> hi,
> I'm unable to output sound to my bluetooth loud speaker.
> It's not a hardware problem, as it works perfectly on Windows 10.
> here is the ouput of bluetoothctl (the LS device is 57:88:14:78:8A:48)
> 
> Discovery started
> [CHG] Controller 3C:95:09:46:D6:74 Discovering: yes
> [CHG] Device 57:88:14:78:8A:48 RSSI: -52
> [CHG] Device 57:88:14:78:8A:48 RSSI: -37
> [bluetooth]# connect 57:88:14:78:8A:48
> Attempting to connect to 57:88:14:78:8A:48
> Failed to connect: org.bluez.Error.Failed
> [CHG] Device B0:34:95:41:6A:43 RSSI: -88
> [CHG] Device 57:88:14:78:8A:48 RSSI: -49

Have you paired and trusted the device already?
I usually do

[bluetooth]# agent on
[bluetooth]# default-agent

pair 
trust
connect

but  it would be easier if you would use blueman-applet (or equivalent) to
do so.

you could list all connected devices in pulseaudio with
$ pactl list short

and if needed  modify the setup.


> 
> I also tried "pactl load-module module-bluetooth-discover" with the
> following result
> 
> Connection failure: Connection refused
> pa_context_connect() failed: Connection refused
> 

Are you trying to do this from root?
This all should be done by the user as PA is started in the user session.

regards

regards

Re: bluetooth keyboard prevents suspend

[Pétùr]

On 28/01/18 10:32, Karol Augustin wrote:


I know that id doesn't fix the problem but as you won't be able to use
usb wakup functionality with bluetooth keyboard anyway maybe just
disable it in BIOS and it should fix the problem for now.


My idea is to rely on another usb device to wake up the computer. For
now, my logitech (wireless) mouse doesn't do that but I think it is
possible. I will look into it.

So disable the BT keyboard, wake up with the mouse.

Pétùr

Re: bluetooth keyboard prevents suspend

[Pétùr]

On 28/01/18 14:28, tv.deb...@googlemail.com wrote:

Hello, I am not very familiar with Bluetooth which I tend to disable 
entirely on my computers, but in case of such problems with buggy 
hardware I use the TLP package. The configuration allows to precisely 
choose what hardware (pointing devices, gpu...) or service (wifi, 
bluetooth...) to enable/disable during sleep and wake-ups. Maybe it 
can handle your keyboard too.


Thanks, it's help!

TLP allows indeed to disable specificly one USB device:

# Set to 0 to disable, 1 to enable USB autosuspend feature.
USB_AUTOSUSPEND=1

# Exclude listed devices from USB autosuspend (separate with spaces).
# Use lsusb to get the ids.
# Note: input devices (usbhid) are excluded automatically
USB_BLACKLIST="0a12:0001"

I disabled my usb connected bluetooth dongle (so my usb keyboard
doesn't wake up my system).

Thanks again!
Pétùr

Re: bluetooth keyboard prevents suspend

[Karol Augustin]

On 2018-01-28 8:02, Pétùr wrote:
> I have set my BIOS configuration to allow usb devices to wake up the
> computer. I used my mouse or my usb keyboard to wake up the system.
> 
> But I just replaced my usb keyboard with a bluetooth one. My bluetooth
> adapter is a dongle connected to a usb port.
> 
> Everytime I suspend (no matter which method), the computer wake up
> immediately (because it detects some connecting activity from the
> bluetooth keyboard).
> 
> I have to disconnect the bluetooth keyboard with the hardware button
> before suspending. Then I can suspend and wakeup with the mouse.
> 
> Is there a way to suspend without turning off the buetooth keyboard first?
> 
> Cheers,
> Pétùr

I know that id doesn't fix the problem but as you won't be able to use
usb wakup functionality with bluetooth keyboard anyway maybe just
disable it in BIOS and it should fix the problem for now.


-- 
Karol Augustin
ka...@augustin.pl
http://karolaugustin.pl/
+353 85 775 5312

Re: bluetooth keyboard prevents suspend

[tv.deb...@googlemail.com]

On 28/01/2018 13:32, Pétùr wrote:

I have set my BIOS configuration to allow usb devices to wake up the
computer. I used my mouse or my usb keyboard to wake up the system.

But I just replaced my usb keyboard with a bluetooth one. My bluetooth
adapter is a dongle connected to a usb port.

Everytime I suspend (no matter which method), the computer wake up
immediately (because it detects some connecting activity from the
bluetooth keyboard).

I have to disconnect the bluetooth keyboard with the hardware button
before suspending. Then I can suspend and wakeup with the mouse.

Is there a way to suspend without turning off the buetooth keyboard first?

Cheers,
Pétùr



Hello, I am not very familiar with Bluetooth which I tend to disable 
entirely on my computers, but in case of such problems with buggy 
hardware I use the TLP package. The configuration allows to precisely 
choose what hardware (pointing devices, gpu...) or service (wifi, 
bluetooth...) to enable/disable during sleep and wake-ups. Maybe it can 
handle your keyboard too.


Hope it helps.

Re: Bluetooth devices get disconnected.

[Jiri Kanicky]

Hi,

So the issue was most likely related to iwlwifi modue (Network 
controller: Intel Corporation Wireless 8260 (rev 3a)). After adding the 
following options for iwlwifi the issue disappeared and the mouse is 
working fine.


$ cat /etc/modprobe.d/iwlwifi.conf
options iwlwifi bt_coex_active=0 swcrypto=1 11n_disable=8 led_mode=3

-Jiri


On 12/12/17 23:44, Jiri Kanicky wrote:

Hi.

I am running Debian Sid with KDE. I have Logitech MX 2 and Bose 
Bluetooth headphones. I experience disconnects very often.


I tried to use different configuration, but nothing seems to work.

After running the following the mouse gets connected again, and I can 
reconnect BT headphones also. However the devices get disconnected 
again in 1, 5 or 10 minutes again:

hciconfig hci0 sspmode 1
hciconfig hci0 down
hciconfig hci0 up

I also noticed that when the mouse is working I see the following:

$ hciconfig -a
hci0:   Type: Primary  Bus: USB
    BD Address: 28:16:AD:B6:2A:0A  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING
    RX bytes:21923293 acl:792631 sco:0 events:111597 errors:0
    TX bytes:10619740 acl:18458 sco:0 commands:1832 errors:0
    Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
    Link policy: RSWITCH SNIFF
    Link mode: SLAVE ACCEPT
    Name: 'supermanbt'
    Class: 0x1c010c
    Service Classes: Rendering, Capturing, Object Transfer
    Device Class: Computer, Laptop
    HCI Version: 4.2 (0x8)  Revision: 0x100
    LMP Version: 4.2 (0x8)  Subversion: 0x100
    Manufacturer: Intel Corp. (2)


After disconnect I can see the following:

$ hciconfig -a
hci0:   Type: Primary  Bus: USB
    BD Address: 28:16:AD:B6:2A:0A  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN
    RX bytes:22096318 acl:800070 sco:0 events:113012 errors:0
    TX bytes:11042199 acl:19322 sco:0 commands:2053 errors:0
    Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
    Link policy: RSWITCH SNIFF
    Link mode: SLAVE ACCEPT
    Name: 'Bluemoon Universal Bluetooth Host Controller'
    Class: 0x00
    Service Classes: Unspecified
    Device Class: Miscellaneous,
    HCI Version: 4.2 (0x8)  Revision: 0x100
    LMP Version: 4.2 (0x8)  Subversion: 0x100
    Manufacturer: Intel Corp. (2)

I also configured blutoothd with -d option, but I don't see any 
specific messages when the devices disconnect.


Any thoughts how to fix it or debug it? Is this general bluetooth 
issue or KDE bluedevil problem?


Thanks Jiri

Re: Bluetooth mouse disconnect while laptop runs with cell

[deloptes]

wg...@china.com wrote:

> I think the reason is the function of bluetooth power save while the cell
> is used. So I want to turn off the function of bluetooth power save, but I
> can not find where to define it. Would you please tell me how to turn off
> the function of bluetooth power save?

I don't know exactly, but you might look at the bt kernel module - perhaps
there is an option

Re: bluetooth hci0: firmware: failed to load brcm/BCM20702A1-0a5c-21e6.hcd

[inkbottle]

It might be that the heart of the problem could be:
# hciconfig hci0 up
Can't init device hci0: Invalid request code (56)
And that consequently, at some point, "btusb" could be unloaded, with the 
consequence that
hciconfig --all
wouldn't show anything anymore.

If I put that point aside... Some things are working:

# systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Wed 2017-05-31 01:45:22 CEST; 7min ago
 Docs: man:bluetoothd(8)
 Main PID: 12520 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
   └─12520 /usr/lib/bluetooth/bluetoothd

May 31 01:45:22 pluto systemd[1]: Stopping Bluetooth service...
May 31 01:45:22 pluto systemd[1]: Stopped Bluetooth service.
May 31 01:45:22 pluto systemd[1]: Starting Bluetooth service...
May 31 01:45:22 pluto bluetoothd[12520]: Bluetooth daemon 5.43
May 31 01:45:22 pluto systemd[1]: Started Bluetooth service.
May 31 01:45:22 pluto bluetoothd[12520]: Starting SDP server
May 31 01:45:22 pluto bluetoothd[12520]: Bluetooth management interface 1.14 
initialized

# hciconfig --all
hci0:   Type: Primary  Bus: USB
BD Address: 9C:2A:70:82:50:FB  ACL MTU: 1021:8  SCO MTU: 64:1
DOWN 
RX bytes:10122 acl:0 sco:0 events:1227 errors:0
TX bytes:108651 acl:0 sco:0 commands:1224 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH SNIFF 
Link mode: SLAVE ACCEPT 

But hci0 can't be brought up, and therefore nobody can see it,
starting with bluetoothctl.

I might have gathered sufficient information to take that issue to bluez-devel 
mailing list.

On Tuesday, May 30, 2017 7:15:18 PM CEST you wrote:
> (note: that chipset is probably used by all recent thinkpad, which probably
> show that when iphones have no jack anymore, BT might not be so much used by
> Linux users)
> 
> If I do a "modprobe" (https://ubuntuforums.org/showthread.php?t=2346879)
> modprobe -r btusb
> modprobe btusb
> 
> I get that:
> 
> May 30 18:53:06 pluto kernel: usbcore: deregistering interface driver btusb
> May 30 18:53:06 pluto kernel: Bluetooth: hci0 urb 8de95167e600 failed to
> resubmit (2)
> May 30 18:53:06 pluto systemd[1]: Starting Load/Save RF Kill Switch
> Status... May 30 18:53:06 pluto bluetoothd[457]: Endpoint unregistered:
> sender=:1.33 path=/MediaEndpoint/A2DPSource
> May 30 18:53:06 pluto systemd[1]: bluetooth.target: Unit not needed anymore.
> Stopping.
> May 30 18:53:06 pluto bluetoothd[457]: Endpoint unregistered: sender=:1.33
> path=/MediaEndpoint/A2DPSink
> May 30 18:53:06 pluto systemd[1]: Stopped target Bluetooth.
> May 30 18:53:06 pluto dbus[458]: [system] Rejected send message, 3 matched
> rules; type="error", sender=":1.33" (uid=1000 pid=1859 comm="/usr/bin/
> pulseaudio --start --log-target=syslog ") in
> May 30 18:53:06 pluto systemd[1]: Started Load/Save RF Kill Switch Status.
> May 30 18:53:06 pluto dbus[458]: [system] Rejected send message, 3 matched
> rules; type="error", sender=":1.33" (uid=1000 pid=1859 comm="/usr/bin/
> pulseaudio --start --log-target=syslog ") in
> May 30 18:53:06 pluto dbus[458]: [system] Rejected send message, 3 matched
> rules; type="error", sender=":1.33" (uid=1000 pid=1859 comm="/usr/bin/
> pulseaudio --start --log-target=syslog ") in
> May 30 18:53:06 pluto dbus[458]: [system] Rejected send message, 3 matched
> rules; type="error", sender=":1.33" (uid=1000 pid=1859 comm="/usr/bin/
> pulseaudio --start --log-target=syslog ") in
> May 30 18:53:11 pluto systemd[1]: Reached target Bluetooth.
> May 30 18:53:11 pluto kernel: usbcore: registered new interface driver btusb
> May 30 18:53:11 pluto kernel: Bluetooth: hci0: BCM: chip id 63
> May 30 18:53:11 pluto kernel: Bluetooth: hci0: ChromeLinux_8A81
> May 30 18:53:11 pluto kernel: Bluetooth: hci0: BCM20702A1 (001.002.014)
> build 
> May 30 18:53:11 pluto kernel: bluetooth hci0: firmware: direct-loading
> firmware brcm/BCM20702A1-0a5c-21e6.hcd
> May 30 18:53:12 pluto kernel: Bluetooth: hci0: BCM20702A1 (001.002.014)
> build 1757
> May 30 18:53:12 pluto kernel: Bluetooth: hci0: Broadcom Bluetooth Device
> 
> 
> root@pluto:/lib/firmware/brcm# hciconfig -a
> hci0:   Type: Primary  Bus: USB
> BD Address: 9C:2A:70:82:50:FB  ACL MTU: 1021:8  SCO MTU: 64:1
> DOWN
> RX bytes:3374 acl:0 sco:0 events:409 errors:0
> TX bytes:36217 acl:0 sco:0 commands:408 errors:0
> Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH SNIFF
> Link mode: SLAVE ACCEPT
> 
> Seems nice, but actually, I do not have any adapter anymore:
> 
> root@pluto:/lib/firmware/brcm# bluetoothctl
> [bluetooth]# list
> [bluetooth]#
> 
> 
> You can see that here too:
> https://bugs.

Re: bluetooth hci0: firmware: failed to load brcm/BCM20702A1-0a5c-21e6.hcd

[inkbottle]

(note: that chipset is probably used by all recent thinkpad, which probably 
show that when iphones have no jack anymore, BT might not be so much used by 
Linux users)

If I do a "modprobe" (https://ubuntuforums.org/showthread.php?t=2346879)
modprobe -r btusb
modprobe btusb

I get that:

May 30 18:53:06 pluto kernel: usbcore: deregistering interface driver btusb
May 30 18:53:06 pluto kernel: Bluetooth: hci0 urb 8de95167e600 failed to 
resubmit (2)
May 30 18:53:06 pluto systemd[1]: Starting Load/Save RF Kill Switch Status...
May 30 18:53:06 pluto bluetoothd[457]: Endpoint unregistered: sender=:1.33 
path=/MediaEndpoint/A2DPSource
May 30 18:53:06 pluto systemd[1]: bluetooth.target: Unit not needed anymore. 
Stopping.
May 30 18:53:06 pluto bluetoothd[457]: Endpoint unregistered: sender=:1.33 
path=/MediaEndpoint/A2DPSink
May 30 18:53:06 pluto systemd[1]: Stopped target Bluetooth.
May 30 18:53:06 pluto dbus[458]: [system] Rejected send message, 3 matched 
rules; type="error", sender=":1.33" (uid=1000 pid=1859 comm="/usr/bin/
pulseaudio --start --log-target=syslog ") in
May 30 18:53:06 pluto systemd[1]: Started Load/Save RF Kill Switch Status.
May 30 18:53:06 pluto dbus[458]: [system] Rejected send message, 3 matched 
rules; type="error", sender=":1.33" (uid=1000 pid=1859 comm="/usr/bin/
pulseaudio --start --log-target=syslog ") in
May 30 18:53:06 pluto dbus[458]: [system] Rejected send message, 3 matched 
rules; type="error", sender=":1.33" (uid=1000 pid=1859 comm="/usr/bin/
pulseaudio --start --log-target=syslog ") in
May 30 18:53:06 pluto dbus[458]: [system] Rejected send message, 3 matched 
rules; type="error", sender=":1.33" (uid=1000 pid=1859 comm="/usr/bin/
pulseaudio --start --log-target=syslog ") in
May 30 18:53:11 pluto systemd[1]: Reached target Bluetooth.
May 30 18:53:11 pluto kernel: usbcore: registered new interface driver btusb
May 30 18:53:11 pluto kernel: Bluetooth: hci0: BCM: chip id 63
May 30 18:53:11 pluto kernel: Bluetooth: hci0: ChromeLinux_8A81
May 30 18:53:11 pluto kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) build 

May 30 18:53:11 pluto kernel: bluetooth hci0: firmware: direct-loading 
firmware brcm/BCM20702A1-0a5c-21e6.hcd
May 30 18:53:12 pluto kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) build 
1757
May 30 18:53:12 pluto kernel: Bluetooth: hci0: Broadcom Bluetooth Device


root@pluto:/lib/firmware/brcm# hciconfig -a
hci0:   Type: Primary  Bus: USB
BD Address: 9C:2A:70:82:50:FB  ACL MTU: 1021:8  SCO MTU: 64:1
DOWN 
RX bytes:3374 acl:0 sco:0 events:409 errors:0
TX bytes:36217 acl:0 sco:0 commands:408 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH SNIFF 
Link mode: SLAVE ACCEPT 

Seems nice, but actually, I do not have any adapter anymore:

root@pluto:/lib/firmware/brcm# bluetoothctl
[bluetooth]# list
[bluetooth]# 


You can see that here too:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801084



I also did that:
sudo cp /lib/firmware/brcm/BCM43142A0-0a5c-21e6.hcd /lib/firmware/brcm/BCM.hcd

Then modprobe -r and modprobe btusb 

And then the result: "bluetooth.target: Unit not needed anymore. Stopping"

May 30 18:53:06 pluto kernel: usbcore: deregistering interface driver btusb
May 30 18:53:06 pluto kernel: Bluetooth: hci0 urb 8de95167e600 failed to 
resubmit (2)
May 30 18:53:06 pluto systemd[1]: Starting Load/Save RF Kill Switch Status...
May 30 18:53:06 pluto bluetoothd[457]: Endpoint unregistered: sender=:1.33 
path=/MediaEndpoint/A2DPSource
May 30 18:53:06 pluto systemd[1]: bluetooth.target: Unit not needed anymore. 
Stopping.
May 30 18:53:06 pluto bluetoothd[457]: Endpoint unregistered: sender=:1.33 
path=/MediaEndpoint/A2DPSink
May 30 18:53:06 pluto systemd[1]: Stopped target Bluetooth.
May 30 18:53:06 pluto dbus[458]: [system] Rejected send message, 3 matched 
rules; type="error", sender=":1.33" (uid=1000 pid=1859 comm="/usr/bin/
pulseaudio --start --log-target=syslog ") in
May 30 18:53:06 pluto systemd[1]: Started Load/Save RF Kill Switch Status.
May 30 18:53:06 pluto dbus[458]: [system] Rejected send message, 3 matched 
rules; type="error", sender=":1.33" (uid=1000 pid=1859 comm="/usr/bin/
pulseaudio --start --log-target=syslog ") in
May 30 18:53:06 pluto dbus[458]: [system] Rejected send message, 3 matched 
rules; type="error", sender=":1.33" (uid=1000 pid=1859 comm="/usr/bin/
pulseaudio --start --log-target=syslog ") in
May 30 18:53:06 pluto dbus[458]: [system] Rejected send message, 3 matched 
rules; type="error", sender=":1.33" (uid=1000 pid=1859 comm="/usr/bin/
pulseaudio --start --log-target=syslog ") in
May 30 18:53:11 pluto systemd[1]: Reached target Bluetooth.
May 30 18:53:11 pluto kernel: usbcore: registered new interface driver btusb
May 30 18:53:11 pluto kernel: Bluetooth: hci0: BCM: chip id 63
May 30 18:53:11 pluto kernel: Bluetooth: hci0: ChromeLinux_8A81
May 30 18:53:11 pluto kernel: Blu

Re: Bluetooth Connection Issue

[Ennio-Sr]

* Michael Milliman  [040417, 08:00]:
> [...] 
 
> Given this information the following questions present themselves:
>   1) Is there a setting somewhere that will cause this issue?
>   2) Is this a known issue with Testing or Blueman?
>   3) Is there a solution which will allow use of Blueman for pairing?
> 
> Clearly, the kernel and drivers on the system are working correctly, or
> I would not be able to accomplish the pairing with bt-device.  I suspect
> the problem is with notifications, either in general, or with Blueman
> specifically, that is causing the problem, and that were I to be getting
> the notification I expect, I would be able to accept the pass code and
> proceed normally.
> 

Hi Michael,

I had a problem with bluetooth too, although it was of a different type.
However, why not have a look at posts dated 'Feb 02' c,y. and
subject:'Bluetooth: unable to pair Apple Wireless keyboard Mod. A1016'.
You might find some useful info, particularly as far as 'agent' is
concerned.

Regards,
   Ennio

-- 
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo.   \\?//
 Fa' qualche cosa di cui non sei capace!"  (diceva Henry Miller) ](°|°)
[Why use Win$ozz (I say) if ... "even a fool can do that.  )=(
 Do something you aren't good at!" (as Henry Miller used to say) ]

[SOLVED] Re: Bluetooth: unable to pair Apple Wireless Keyboard Mod. A1016

[Ennio-Sr]

* Ennio-Sr  [030217, 00:46]:
> * deloptes  [020217, 23:34]:
> > Ennio-Sr wrote:
> > 
> > did you have a look here?
> > http://askubuntu.com/questions/730316/apple-wireless-keyboard-wont-connect-in-15-10
> > 
> > and here they say to "trust", but well, this is after successfull pairing
> > http://askubuntu.com/questions/701978/how-can-a-bluetooth-keyboard-that-requires-a-code-entry-be-paired-in-the-termina
> > 

Sorry! I was so excited to forget to add 'Solved' to the subject

-- 
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo.   \\?//
 Fa' qualche cosa di cui non sei capace!"  (diceva Henry Miller) ](°|°)
[Why use Win$ozz (I say) if ... "even a fool can do that.  )=(
 Do something you aren't good at!" (as Henry Miller used to say) ]

Re: Bluetooth: unable to pair Apple Wireless Keyboard Mod. A1016

[Ennio-Sr]

* deloptes  [020217, 23:34]:
> Ennio-Sr wrote:
> 
> > No, I can assure all commands were in order, including 'agent'.
> > ...
> 
> Wait you say squeeze. The thing is bluetooth changed significantly since
> squeeze. If I am not mistaken wheezy to jessie. So jessie has the new
> version of bluez. You can read there what changed if interested.
> did you have a look here?
> http://askubuntu.com/questions/730316/apple-wireless-keyboard-wont-connect-in-15-10
> 
> and here they say to "trust", but well, this is after successfull pairing
> http://askubuntu.com/questions/701978/how-can-a-bluetooth-keyboard-that-requires-a-code-entry-be-paired-in-the-termina
> 
> I am not familiar with bt keybards, but if it was working it should work in
> stretch too. I spent time dealing with bt and my mobile phones. Now I use
> blueman to manage the adapter, however I used also bluetoothctl several
> times in the past. What happens if you try to connect and then pair?
> 
> FYI I have on jessie
> 
> blueman 1.99~alpha1-1+deb8u1
> bluemon 1.4-6
> bluetooth   5.23-2
> bluez   5.23-2+b1
> bluez-dbg   5.23-2+b1
> bluez-firmware  1.2-3
> bluez-hcidump   5.23-2+b1
> bluez-obexd 5.23-2+b1
> bluez-test-scripts  5.23-2
> btscanner   2.1-5.1
> libbluetooth-dev5.23-2+b1
> libbluetooth3:amd64 5.23-2+b1
> libbluetooth3-dbg   5.23-2+b1
> libgnome-bluetooth133.14.0-2
> pulseaudio-module-bluetooth 5.0-13
> 

Let me say it in one single word: 'GREAT!!!'

Following instructions reported in the first link solved the problem
(and I'm right now using the Wireless Keyboard :-)

My thanks are not enough to express my gratitude. Thank you so much
indeed. All the best for you and Heaven bless you!

Ennio

-- 
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo.   \\?//
 Fa' qualche cosa di cui non sei capace!"  (diceva Henry Miller) ](°|°)
[Why use Win$ozz (I say) if ... "even a fool can do that.  )=(
 Do something you aren't good at!" (as Henry Miller used to say) ]

Re: Bluetooth: unable to pair Apple Wireless Keyboard Mod. A1016

[deloptes]

Ennio-Sr wrote:

> No, I can assure all commands were in order, including 'agent'.
> In the meantime a look given to 'lsmod' in the older mcmini (the one
> with squeeze ppc that paired with the kb) showed that there the
> bluetooth mod was used, among others, by 'l2cap' and 'sco', which are
> missing both in Jessie and Stretch kernel's modules.
> OTAH I have no idea what those modules helped doing...
> 
> BTW, I red the suggested url, and so many others up to now and have no
> hope left

Wait you say squeeze. The thing is bluetooth changed significantly since
squeeze. If I am not mistaken wheezy to jessie. So jessie has the new
version of bluez. You can read there what changed if interested.
did you have a look here?
http://askubuntu.com/questions/730316/apple-wireless-keyboard-wont-connect-in-15-10

and here they say to "trust", but well, this is after successfull pairing
http://askubuntu.com/questions/701978/how-can-a-bluetooth-keyboard-that-requires-a-code-entry-be-paired-in-the-termina

I am not familiar with bt keybards, but if it was working it should work in
stretch too. I spent time dealing with bt and my mobile phones. Now I use
blueman to manage the adapter, however I used also bluetoothctl several
times in the past. What happens if you try to connect and then pair?

FYI I have on jessie

blueman 1.99~alpha1-1+deb8u1
bluemon 1.4-6
bluetooth   5.23-2
bluez   5.23-2+b1
bluez-dbg   5.23-2+b1
bluez-firmware  1.2-3
bluez-hcidump   5.23-2+b1
bluez-obexd 5.23-2+b1
bluez-test-scripts  5.23-2
btscanner   2.1-5.1
libbluetooth-dev5.23-2+b1
libbluetooth3:amd64 5.23-2+b1
libbluetooth3-dbg   5.23-2+b1
libgnome-bluetooth133.14.0-2
pulseaudio-module-bluetooth 5.0-13

Re: Bluetooth: unable to pair Apple Wireless Keyboard Mod. A1016

[Ennio-Sr]

* deloptes  [020217, 20:26]:
> Ennio-Sr wrote:
> 
> > Thanks for your attention. Regards, Ennio
> 
> http://ubuntuforums.org/showthread.php?t=2276551
> 
> I think you missed agent on and so on

No, I can assure all commands were in order, including 'agent'.
In the meantime a look given to 'lsmod' in the older mcmini (the one
with squeeze ppc that paired with the kb) showed that there the
bluetooth mod was used, among others, by 'l2cap' and 'sco', which are
missing both in Jessie and Stretch kernel's modules.
OTAH I have no idea what those modules helped doing...

BTW, I red the suggested url, and so many others up to now and have no hope 
left ;-(

Thanks, Ennio


-- 
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo.   \\?//
 Fa' qualche cosa di cui non sei capace!"  (diceva Henry Miller) ](°|°)
[Why use Win$ozz (I say) if ... "even a fool can do that.  )=(
 Do something you aren't good at!" (as Henry Miller used to say) ]

Re: Bluetooth: unable to pair Apple Wireless Keyboard Mod. A1016

[deloptes]

Ennio-Sr wrote:

> Thanks for your attention. Regards, Ennio

http://ubuntuforums.org/showthread.php?t=2276551
#!/bin/bash
bluetoothctl << EOF
power on
discoverable on
agent on
default-agent
pairable on
EOF

I think you missed agent on and so on

Re: Bluetooth: unable to pair Apple Wireless Keyboard Mod. A1016

[Ennio-Sr]

* Ennio-Sr  [010217, 19:33]:
> 
> OK, I did it, but nothing changed: getting more or less the same errors
> as before,may be some more. But I'll come back with some consistent data...
> Regards, Ennio
>  

And here we are!
The bluetooth Stretch version is bugged so I tried again with Jessie;
This is a screen dump of the commands used:


root@mcmini-4_1-deb:~# hciconfig hc10 sspmode 0 ->>> # same result not 
runnning this one #


root@mcmini-4_1-deb:~# bluetoothctl
[NEW] Device 00:0A:95:3F:A8:DF Apple Wireless Keyboard
[bluetooth]# show  
Controller C8:BC:C8:E9:DA:AA  
Name: mcmini-4_1-deb 
Alias: mcmini-4_1-deb 
Class: 0x0c0104
Powered: yes
Discoverable: no 
Pairable: yes 
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb) 
Modalias: usb:v1D6Bp0246d052B
Discovering: no  <<<-
[bluetooth]# discoverable on  <<< -
Changing discoverable on succeeded
[CHG] Controller C8:BC:C8:E9:DA:AA Discoverable: yes
[bluetooth]# scan on
Discovery started 
[CHG] Controller C8:BC:C8:E9:DA:AA Discovering: yes  
[CHG] Device 00:0A:95:3F:A8:DF RSSI: -74

[bluetooth]# pair 00:0A:95:3F:A8:DF
Attempting to pair with 00:0A:95:3F:A8:DF   ->>> # not touching kb
Failed to pair: org.bluez.Error.AuthenticationTimeout
[CHG] Device 00:0A:95:3F:A8:DF RSSI: -55 

[bluetooth]# pair 00:0A:95:3F:A8:DF  
Attempting to pair with 00:0A:95:3F:A8:DF   ->>> # input 1234
Failed to pair: org.bluez.Error.AuthenticationTimeout  

[bluetooth]# pair 00:0A:95:3F:A8:DF
Attempting to pair with 00:0A:95:3F:A8:DF   ->>> # input 
Failed to pair: org.bluez.Error.AuthenticationTimeout

[bluetooth]# pair 00:0A:95:3F:A8:DF
Attempting to pair with 00:0A:95:3F:A8:DF   ->>> # input 00
Failed to pair: org.bluez.Error.AuthenticationTimeout 

[bluetooth]# exit
[DEL] Controller C8:BC:C8:E9:DA:AA mcmini-4_1-deb [default]


root@mcmini-4_1-deb:~# hidd --search
Searching ...
Connecting to device 00:0A:95:3F:A8:DF 
Can't get device information: Function not implemented

root@mcmini-4_1-deb:~# dpkg -l | grep -i blue  
ii  bluez  5.43-1amd64   Bluetooth tools and 
daemons
ii  bluez-compat   4.99-2amd64   BlueZ 3.x 
compatibility binaries
ii  bluez-firmware 1.2-3 all Firmware for Bluetooth 
devices 
ii  bluez-hcidump  5.43-1amd64   Analyses Bluetooth HCI 
packets  ->>> (1)
ii  gir1.2-gnomebluetooth-1.0:amd643.20.0-1  amd64   Introspection data for 
GnomeBluetooth 
ii  libbluetooth3:amd645.43-1amd64   Library to use the 
BlueZ Linux Bluetooth stack 
ii  libgnome-bluetooth13:amd64 3.20.0-1  amd64   GNOME Bluetooth tools 
- support library 

->>> (1) Bluetooth gave the same errors before installing this (Jessie) pckg
root@mcmini-4_1-deb:~#  


# And this is part of journalctl -xb
...
Feb 02 18:03:58 mcmini-4_1-deb bluetoothd[4414]: vendor 0x0 product: 0x0
Feb 02 18:03:58 mcmini-4_1-deb bluetoothd[4414]: No agent available for request 
type 4
Feb 02 18:03:58 mcmini-4_1-deb bluetoothd[4414]: device_notify_pin: Operation 
not permitted
Feb 02 18:04:42 mcmini-4_1-deb bluetoothd[4414]: vendor 0x0 product: 0x0
Feb 02 18:04:42 mcmini-4_1-deb bluetoothd[4414]: No agent available for request 
type 4
Feb 02 18:04:42 mcmini-4_1-deb bluetoothd[4414]: device_notify_pin: Operation 
not permitted
...
Feb 02 18:05:38 mcmini-4_1-deb bluetoothd[4414]: vendor 0x0 product: 0x0
Feb 02 18:05:38 mcmini-4_1-deb bluetoothd[4414]: No agent available for request 
type 4
Feb 02 18:05:38 mcmini-4_1-deb bluetoothd[4414]: device_notify_pin: Operation 
not permitted
Feb 02 18:06:52 mcmini-4_1-deb bluetoothd[4414]: No agent available for request 
type 0
Feb 02 18:06:52 mcmini-4_1-deb bluetoothd[4414]: device_request_pin: Operation 
not permitted
...

Re: Bluetooth: unable to pair Apple Wireless Keyboard Mod. A1016

[Ennio-Sr]

* deloptes  [010217, 00:46]:
> ennio wrote:
> 
> > I'm waiting for 'stretch' to be officially the new 'stable' debian
> > version on 5th February so as to fully upgrade my system (now it is
> > partially Jessie, partially Stretch) and check again whether or not
> > bluetooth works with this quite old keyboard.
> 
> You could use stretch in apt/sources.list and upgrade already. No need to
> wait until 5th. Have some balls, show some character!
> 
> regards

OK, I did it, but nothing changed: getting more or less the same errors
as before,may be some more. But I'll come back with some consistent data...
Regards, Ennio
-- 
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo.   \\?//
 Fa' qualche cosa di cui non sei capace!"  (diceva Henry Miller) ](°|°)
[Why use Win$ozz (I say) if ... "even a fool can do that.  )=(
 Do something you aren't good at!" (as Henry Miller used to say) ]

Re: Bluetooth: unable to pair Apple Wireless Keyboard Mod. A1016

[deloptes]

ennio wrote:

> I'm waiting for 'stretch' to be officially the new 'stable' debian
> version on 5th February so as to fully upgrade my system (now it is
> partially Jessie, partially Stretch) and check again whether or not
> bluetooth works with this quite old keyboard.

You could use stretch in apt/sources.list and upgrade already. No need to
wait until 5th. Have some balls, show some character!

regards

Re: Bluetooth: unable to pair Apple Wireless Keyboard Mod. A1016

[ennio]

This is just to thank deloptes, solitone, Leandro for their suggestions.
Unluckily, none of them helped solve the problem.
I'm waiting for 'stretch' to be officially the new 'stable' debian
version on 5th February so as to fully upgrade my system (now it is
partially Jessie, partially Stretch) and check again whether or not
bluetooth works with this quite old keyboard.

At present I only get a large variety of errors, depending on the
commands used to attempt pairing and may be I'm missing something:
The link suggested by Deolptes brought me to a
'pin-code-database.xml' file that should be in gnome-bluetooth
directory, not present in my system (broken dependencies).

Yes, I have the latest 'bluez-firmware' version.

AAMOF, prior to installing stretch bluetooth applications to the base
Jessie version, I got the same errors when I tried bluetooth in Jessie.

What upsets me most is that the keyboard worked nicely under
Squeeze/bluetooth running on a debian ppc on a macmini older than the
one I'm using with Jessie (intel amd64).

Thanks again to you all. Regards,
Ennio



-- 
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo.   \\?//
 Fa' qualche cosa di cui non sei capace!"  (diceva Henry Miller) ](°|°)
[Why use Win$ozz (I say) if ... "even a fool can do that.  )=(
 Do something you aren't good at!" (as Henry Miller used to say) ]

Re: Bluetooth: unable to pair Apple Wireless Keyboard Mod. A1016

[solitone]

On Monday, January 30, 2017 9:10:59 PM CET Leandro Noferini wrote:
> I have a bluetooth keyboard different model (the model without numeric
> keys) and to pair in a debian stable I needed to install also the
> bluez-firmware package: after this I paired with standard gnome tools.

I also believe you could give bluez-firmware a try. I had a pairing issue with 
a different device (a speaker), and I could only solved it with that package.

Re: Bluetooth: unable to pair Apple Wireless Keyboard Mod. A1016

[Leandro Noferini]

Ennio-Sr  writes:

> Has any of you benn able to pair the subject keyboard with bluetooth
> under linux debian/jessie or stretch?

[...]

I have a bluetooth keyboard different model (the model without numeric
keys) and to pair in a debian stable I needed to install also the
bluez-firmware package: after this I paired with standard gnome tools.

-- 
leandro
1A0B 125B 2E4D 2DAE 4E26  4551 88FB BBCC 7A29 640B
https://bbs.cybervalley.org/ChiaveLeandro/gpg.html
http://6xukrlqedfabdjrb.onion


signature.asc
Description: PGP signature

Re: Bluetooth: unable to pair Apple Wireless Keyboard Mod. A1016

[deloptes]

Ennio-Sr wrote:

> Could not load pin-code-database.xml
this might help
http://askubuntu.com/questions/486347/bluetooth-mouse-not-auto-reconnecting-to-laptop

regards

Re: bluetooth error

[Manoel Pedro de Araújo]

Thanks for your answers.

2016-10-22 20:52 GMT-02:00 deloptes :

> Manoel Pedro de Araújo wrote:
>
> > Hi,
> >
> > I have installed debian jessie on a  Samsung X40 notebook, when the
> > bluetooth is working, but it shows an error as shown bellow
> >
> > Out 22 16:56:18 debian bluetoothd[824]: Sap driver initialization failed.
> > Out 22 16:56:18 debian bluetoothd[824]: sap-server: Operation not
> > permitted (1)
> > Out 22 16:56:18 debian bluetoothd[824]: hci0 Load Connection Parameters
> > failed: Unk...1)
> >
> > Maybe is this a problem? Please, help me
>
> look in /var/log/syslog for the initialization of the driver, if this is
> fine and bluetooth is working, ignore the messages. I get the same here
> (see attached).
>
> You can check also this bug
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803265
>
> regards
>
>
>
>
>


-- 
Manoel

Re: bluetooth error

[deloptes]

Manoel Pedro de Araújo wrote:

> Hi,
> 
> I have installed debian jessie on a  Samsung X40 notebook, when the
> bluetooth is working, but it shows an error as shown bellow
> 
> Out 22 16:56:18 debian bluetoothd[824]: Sap driver initialization failed.
> Out 22 16:56:18 debian bluetoothd[824]: sap-server: Operation not
> permitted (1)
> Out 22 16:56:18 debian bluetoothd[824]: hci0 Load Connection Parameters
> failed: Unk...1)
> 
> Maybe is this a problem? Please, help me

look in /var/log/syslog for the initialization of the driver, if this is
fine and bluetooth is working, ignore the messages. I get the same here
(see attached).

You can check also this bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803265

regards




Oct 21 10:14:43 hostname kernel: [   15.314677] Bluetooth: Core ver 2.21
Oct 21 10:14:43 hostname kernel: [   15.314688] NET: Registered protocol family 
31
Oct 21 10:14:43 hostname kernel: [   15.314689] Bluetooth: HCI device and 
connection manager initialized
Oct 21 10:14:43 hostname kernel: [   15.314692] Bluetooth: HCI socket layer 
initialized
Oct 21 10:14:43 hostname kernel: [   15.314694] Bluetooth: L2CAP socket layer 
initialized
Oct 21 10:14:43 hostname kernel: [   15.314698] Bluetooth: SCO socket layer 
initialized
Oct 21 10:14:43 hostname kernel: [   15.522624] mousedev: PS/2 mouse device 
common for all mice
Oct 21 10:14:43 hostname kernel: [   15.656894] usbcore: registered new 
interface driver btusb
Oct 21 10:14:43 hostname kernel: [   15.670211] Bluetooth: hci0: read Intel 
version: 370710018002030d00
Oct 21 10:14:43 hostname kernel: [   15.678811] Bluetooth: hci0: Intel 
Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Oct 21 10:14:43 hostname kernel: [   15.688616] iwlwifi :02:00.0: loaded 
firmware version 17.352738.0 op_mode iwlmvm
Oct 21 10:14:43 hostname kernel: [   15.861172] Bluetooth: hci0: Intel 
Bluetooth firmware patch completed and activated

Oct 23 00:31:33 hostname systemd[1]: Reached target Bluetooth.
Oct 23 00:31:33 hostname systemd[1]: Started Load/Save RF Kill Switch Status of 
rfkill7.
Oct 23 00:31:33 hostname bluetoothd[4513]: Sap driver initialization failed.
Oct 23 00:31:33 hostname bluetoothd[4513]: sap-server: Operation not permitted 
(1)
Oct 23 00:31:33 hostname bluetoothd[4513]: Failed to set mode: Busy (0x0a)
Oct 23 00:32:02 hostname org.blueman.Mechanism[2041]: Exception AttributeError: 
"'NoneType' object has no attribute 'stdout'" in > ignored
Oct 23 00:32:02 hostname org.blueman.Mechanism[2041]: Starting blueman-mechanism
Oct 23 00:32:02 hostname org.blueman.Mechanism[2041]: loading Network
Oct 23 00:32:02 hostname org.blueman.Mechanism[2041]: loading Config
Oct 23 00:32:02 hostname org.blueman.Mechanism[2041]: loading RfKill
Oct 23 00:32:02 hostname org.blueman.Mechanism[2041]: loading Ppp
Oct 23 00:35:01 hostname CRON[982]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
Oct 23 00:35:02 hostname dbus[2041]: [system] Activating service 
name='org.blueman.Mechanism' (using servicehelper)
Oct 23 00:35:02 hostname blueman-mechanism: Starting blueman-mechanism
Oct 23 00:35:02 hostname dbus[2041]: [system] Successfully activated service 
'org.blueman.Mechanism'
Oct 23 00:35:02 hostname blueman-mechanism: loading Network
Oct 23 00:35:02 hostname blueman-mechanism: loading Config
Oct 23 00:35:02 hostname blueman-mechanism: loading RfKill
Oct 23 00:35:02 hostname blueman-mechanism: loading Ppp
Oct 23 00:35:02 hostname org.blueman.Mechanism[2041]: Unable to init server: 
Could not connect: Connection refused
Oct 23 00:35:02 hostname org.blueman.Mechanism[2041]: Unable to init server: 
Could not connect: Connection refused
Oct 23 00:35:02 hostname kernel: [112537.592093] usb 1-1.8.2: USB disconnect, 
device number 7
Oct 23 00:35:02 hostname kernel: [112537.594352] Bluetooth: hci0: turning off 
Intel device LED failed (-19)
Oct 23 00:35:02 hostname systemd[1]: Service bluetooth.target is not needed 
anymore. Stopping.
Oct 23 00:35:02 hostname systemd[1]: Stopping Bluetooth.
Oct 23 00:35:02 hostname systemd[1]: Stopped target Bluetooth.
Oct 23 00:35:32 hostname org.blueman.Mechanism[2041]: Exception AttributeError: 
"'NoneType' object has no attribute 'stdout'" in > ignored
Oct 23 00:35:32 hostname org.blueman.Mechanism[2041]: Starting blueman-mechanism
Oct 23 00:35:32 hostname org.blueman.Mechanism[2041]: loading Network
Oct 23 00:35:32 hostname org.blueman.Mechanism[2041]: loading Config
Oct 23 00:35:32 hostname org.blueman.Mechanism[2041]: loading RfKill
Oct 23 00:35:32 hostname org.blueman.Mechanism[2041]: loading Ppp

SOLVED: Re: Bluetooth: impossible to send files from phone to computer

[Lisi Reisz]

On Sunday 18 September 2016 17:05:41 Frédéric Mesplède wrote:
> 2016-09-13 23:21 GMT+02:00 deloptes :
> > Frédéric Mesplède wrote:
> >> I do not know how I am supposed to connect the phone to my computer...
> >> When I use gnome tool [ http://i66.tinypic.com/2912n89.png ] the
> >> switch instantly comes back to off position and I cannot turn it on...
> >
> > Use bluetoothctl to test these. I spent some time before I was able to
> > use bluetooth.
> > The problem with the transfer from phone to computer might be the way
> > your computer configuration looks like. The easy way to customize it is
> > bluetoothctl
> >
> > For transfering files you need obex ftp. I've never transferred from
> > phone to pc.
> >
> > regards
>
> Ok, so for some unexplained reason bluetooth works fine again... I
> installed obex ftp but I am not even sure that it solved my problem...
> I explored the parameters through bluetoothctl and suddenly bluetooth
> was working again. Thank you guys!
>
> By the way, I am new at mailing lists, how do you mark a thread as
> solved (just like in the forums)?

As above!  I have taken the liberty of doing it for you.

Lisi 

Re: Bluetooth: impossible to send files from phone to computer

[Frédéric Mesplède]

2016-09-13 23:21 GMT+02:00 deloptes :
> Frédéric Mesplède wrote:
>
>> I do not know how I am supposed to connect the phone to my computer...
>> When I use gnome tool [ http://i66.tinypic.com/2912n89.png ] the
>> switch instantly comes back to off position and I cannot turn it on...
>
> Use bluetoothctl to test these. I spent some time before I was able to use
> bluetooth.
> The problem with the transfer from phone to computer might be the way your
> computer configuration looks like. The easy way to customize it is
> bluetoothctl
>
> For transfering files you need obex ftp. I've never transferred from phone
> to pc.
>
> regards
>

Ok, so for some unexplained reason bluetooth works fine again... I
installed obex ftp but I am not even sure that it solved my problem...
I explored the parameters through bluetoothctl and suddenly bluetooth
was working again. Thank you guys!

By the way, I am new at mailing lists, how do you mark a thread as
solved (just like in the forums)?

Re: Bluetooth: impossible to send files from phone to computer

[deloptes]

Frédéric Mesplède wrote:

> I do not know how I am supposed to connect the phone to my computer...
> When I use gnome tool [ http://i66.tinypic.com/2912n89.png ] the
> switch instantly comes back to off position and I cannot turn it on...

Use bluetoothctl to test these. I spent some time before I was able to use
bluetooth. 
The problem with the transfer from phone to computer might be the way your
computer configuration looks like. The easy way to customize it is
bluetoothctl

For transfering files you need obex ftp. I've never transferred from phone
to pc.

regards

Re: Bluetooth: impossible to send files from phone to computer

[Frédéric Mesplède]

I do not know how I am supposed to connect the phone to my computer...
When I use gnome tool [ http://i66.tinypic.com/2912n89.png ] the
switch instantly comes back to off position and I cannot turn it on...