public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Bluetooth speakers
Date: Mon, 09 May 2022 15:38:30 +0100	[thread overview]
Message-ID: <21461052.EfDdHjke4D@lenovo.localdomain> (raw)
In-Reply-To: <20220509135642.B16A08257288@turkos.aspodata.se>

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

On Monday, 9 May 2022 14:56:42 BST karl@aspodata.se wrote:
> Peter:
> ...
> 
> > What would help is some idea of how the whole BT system works,
> 
> ...
> 
> There are two incompatible types of bluetooth:
>  Bluetooth Low Energy (BLE)
>  Bluetooth Classic
> see:
>  https://www.bluetooth.com/learn-about-bluetooth/tech-overview/
> 
> You must check which generation of bluetooth your speaker uses.
> If your speaker uses the classic type, this might help you:
>  https://wiki.debian.org/Bluetooth/Alsa
> 
> ///
> 
> More info about bluetooth:
>  https://en.wikipedia.org/wiki/Bluetooth
>  https://www.bluetooth.com/specifications/specs/
> 
> ///
> 
> Current linux bluetooth tools (http://www.bluez.org/) doesn't
> handle bluetooth classic, unless you build bluez with
> --enable-deprecated configure option.
>  Also, bluez has dropped direct /dev file access for users, you
> have to set up and go through dbus regardless wether you like it
> or not.
> 
> Regards,
> /Karl Hammar

I've met some success getting BT to work and I tend to follow these basic 
steps:

1. Configure the kernel according to the BT chipset available on the PC.

2. Power the BT chip by using whatever hardware button is available and check 
dmesg identified the device and loaded whatever module and firmware is 
necessary.

3. Use 'rfkill list' to check the device is not blocked and unblock it if 
necessary.

4. Run 'rc-service -v bluetooth start'.

5. Run 'bluetoothctl' to scan, list, pair and trust any peripherals  - 
exchange a PIN to facilitate pairing as necessary.

These steps should be relatively easy to complete and GUI tools are also 
available to assist with the above.  Any problems thereafter are userspace 
related, i.e. whether the applications I use will be able to work with the BT 
peripherals.  Audio has been problematic on a particular use case, where 
neither alsa (bluez-alsa), nor pulseaudio allowed me to output audio via BT.  
Eventually I tried blueman which after a couple of restarts helped pulseaudio 
to recognise the device and output audio through it.

In all cases I prefer cables to temperamental radio connectivity and where 
quality matters, like it can be in some audio applications, I would seek to 
connect with a cable.

HTH

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-05-09 14:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 15:22 [gentoo-user] Bluetooth speakers Peter Humphrey
2022-05-05 16:21 ` Jack
2022-05-05 20:37   ` Michael
2022-05-06  7:59     ` Peter Humphrey
2022-05-06 12:24       ` [gentoo-user] " Grant Edwards
2022-05-06 12:41         ` Peter Humphrey
2022-05-06 14:40         ` Daniel Frey
2022-05-07 17:02       ` [gentoo-user] " Peter Humphrey
2022-05-07 19:32         ` Jack
2022-05-08 18:02           ` Peter Humphrey
2022-05-09 13:56         ` karl
2022-05-09 14:38           ` Michael [this message]
2022-05-10  8:17             ` Peter Humphrey
2022-05-10  9:26               ` Michael
2022-05-10 10:29                 ` 3.5mm jacks (was Re: [gentoo-user] Bluetooth speakers) karl
2022-05-10 10:59                   ` Michael
2022-05-10 12:00                 ` [gentoo-user] Bluetooth speakers Peter Humphrey
2022-05-10 19:06                   ` Michael
2022-05-11 10:54                   ` Peter Humphrey
2022-05-12 10:01               ` Peter Humphrey
2022-05-12 13:49                 ` Neil Bothwick
2022-05-12 14:50                   ` Peter Humphrey
2022-05-12  9:44             ` Peter Humphrey
2022-05-14 16:34 ` [SOLVED]Re: " Peter Humphrey
2022-05-18  8:51   ` Peter Humphrey
2022-05-18 10:02     ` Michael
2022-05-18 14:22       ` Peter Humphrey
2022-05-18 14:47         ` Michael
2022-05-18 21:26         ` Wol
2022-05-19  8:36           ` Peter Humphrey
2022-06-12  7:38 ` FIXED " Peter Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21461052.EfDdHjke4D@lenovo.localdomain \
    --to=confabulate@kintzios.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox