Re: bt question
My phone has lots of subdevices, I don't know how to connect to any of
them yet either
info F8:CF:C5:00:F0:E2
Device F8:CF:C5:00:F0:E2 (public)
Name: MotoE2(4G-LTE)
Alias: MotoE2(4G-LTE)
Class: 0x005a020c
Icon: phone
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: NAP (00001116-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v001Dp1200d1436
RSSI: -68
I now have installed
dpkg-query -l | grep blue
ii bluealsa 0.13
armhf Bluetooth ALSA Audio backend
ii bluez 5.50-1.2~deb10u1+rpt2
armhf Bluetooth tools and daemons
ii bluez-firmware 1.2-4+rpt4
all Firmware for Bluetooth devices
ii bluez-obexd 5.50-1.2~deb10u1+rpt2
armhf bluez obex daemon
ii bluez-tools 2.0~20170911.0.7cb788c-2
armhf Set of tools to manage Bluetooth devices for
linux
ii libbluetooth3:armhf 5.50-1.2~deb10u1+rpt2
armhf Library to use the BlueZ Linux Bluetooth stack
ii lxplug-bluetooth 0.14
armhf Bluetooth plugin for lxpanel
ii pi-bluetooth 0.1.15
all Raspberry Pi 3 bluetooth
There's more about bluez at https://github.com/Arkq/bluez-alsa
Just occurred to me that with a musical keyboard you may run into
stuff for doing midi (music synthesizer, think moog) over bluetooth.
You probably don't want that although it could be fun, she'd just need
a laptop with software.
On 9/26/20, Alan Corey <alan01346@gmail.com> wrote:
> I moved the base to my earbuds downstairs and connected to this Pi. Some
> notes:
>
> Some of these things get cached, here B1 shows up twice at different
> addresses:
>
> devices
> Device CB:20:07:42:99:64 B1
> Device F3:66:48:29:CA:7D IDTW211R
> Device FE:46:6D:40:FC:43 B1
> [CHG] Controller B8:27:EB:1F:69:7C Discoverable: no
>
> info FE:46:6D:40:FC:43
> Device FE:46:6D:40:FC:43 (public)
> Name: B1
> Alias: B1
> Class: 0x00240404
> Icon: audio-card
> Paired: no
> Trusted: no
> Blocked: no
> Connected: no
> LegacyPairing: no
> ManufacturerData Key: 0x2549
> ManufacturerData Value:
> 96 52 ef 52 40 dc ca da .R.R@...
> RSSI: -57
>
> trust FE:46:6D:40:FC:43
> [CHG] Device FE:46:6D:40:FC:43 Trusted: yes
> Changing FE:46:6D:40:FC:43 trust succeeded
> [bluetooth]# pair FE:46:6D:40:FC:43
> Attempting to pair with FE:46:6D:40:FC:43
> [CHG] Device FE:46:6D:40:FC:43 Connected: yes
> [CHG] Device FE:46:6D:40:FC:43 Modalias: bluetooth:v05D6p000Ad0240
> [CHG] Device FE:46:6D:40:FC:43 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
> [CHG] Device FE:46:6D:40:FC:43 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
> [CHG] Device FE:46:6D:40:FC:43 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
> [CHG] Device FE:46:6D:40:FC:43 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
> [CHG] Device FE:46:6D:40:FC:43 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
> [CHG] Device FE:46:6D:40:FC:43 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
> [CHG] Device FE:46:6D:40:FC:43 ServicesResolved: yes
> [CHG] Device FE:46:6D:40:FC:43 Paired: yes
> Pairing successful
> [CHG] Device FE:46:6D:40:FC:43 ServicesResolved: no
> [CHG] Device FE:46:6D:40:FC:43 Connected: no
>
> connect FE:46:6D:40:FC:43
> Attempting to connect to FE:46:6D:40:FC:43
> [CHG] Device FE:46:6D:40:FC:43 Connected: yes
> Connection successful
> [CHG] Device FE:46:6D:40:FC:43 ServicesResolved: yes
>
> :info FE:46:6D:40:FC:43
> Device FE:46:6D:40:FC:43 (public)
> Name: B1
> Alias: B1
> Class: 0x00240404
> Icon: audio-card
> Paired: yes
> Trusted: yes
> Blocked: no
> Connected: yes
> LegacyPairing: no
> UUID: Audio Sink
> (0000110b-0000-1000-8000-00805f9b34fb)
> UUID: A/V Remote Control Target
> (0000110c-0000-1000-8000-00805f9b34fb)
> UUID: A/V Remote Control
> (0000110e-0000-1000-8000-00805f9b34fb)
> UUID: Handsfree
> (0000111e-0000-1000-8000-00805f9b34fb)
> UUID: Human Interface Device...
> (00001124-0000-1000-8000-00805f9b34fb)
> UUID: PnP Information
> (00001200-0000-1000-8000-00805f9b34fb)
> Modalias: bluetooth:v05D6p000Ad0240
> ManufacturerData Key: 0x2549
> ManufacturerData Value:
> 96 52 ef 52 40 dc ca da .R.R@...
> RSSI: -57
>
> rebooting for alsa to maybe pick it up
>
> Still paired?: [yes]
> info FE:46:6D:40:FC:43
> Device FE:46:6D:40:FC:43 (public)
> Name: B1
> Alias: B1
> Class: 0x00240404
> Icon: audio-card
> Paired: yes
> Trusted: yes
> Blocked: no
> Connected: yes
> LegacyPairing: no
> UUID: Audio Sink
> (0000110b-0000-1000-8000-00805f9b34fb)
> UUID: A/V Remote Control Target
> (0000110c-0000-1000-8000-00805f9b34fb)
> UUID: Advanced Audio Distribu..
> (0000110d-0000-1000-8000-00805f9b34fb)
> UUID: A/V Remote Control
> (0000110e-0000-1000-8000-00805f9b34fb)
> UUID: Handsfree
> (0000111e-0000-1000-8000-00805f9b34fb)
> UUID: Human Interface Device...
> (00001124-0000-1000-8000-00805f9b34fb)
> UUID: PnP Information
> (00001200-0000-1000-8000-00805f9b34fb)
> Modalias: bluetooth:v05D6p000Ad0240
>
> alsa didn't find it yet, probably because it's a HID. More research
> needed.
>
> aplay -l
> **** List of PLAYBACK Hardware Devices ****
> card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
> Subdevices: 4/4
> Subdevice #0: subdevice #0
> Subdevice #1: subdevice #1
> Subdevice #2: subdevice #2
> Subdevice #3: subdevice #3
> card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones
> [bcm2835 Headphones]
> Subdevices: 4/4
> Subdevice #0: subdevice #0
> Subdevice #1: subdevice #1
> Subdevice #2: subdevice #2
> Subdevice #3: subdevice #3
>
> It's only seeing native Pi stuff. But that's an alsa thing, not a
> bluetooth
> one. I knew this was a HID device but my phone didn't care, it just
> connected to the audio sink in it. That's what I want the Pi to do
> too, at least now. But according to the advertising these also have
> microphones in them.
>
> On 9/26/20, Alan Corey <alan01346@gmail.com> wrote:
>> bluetoothctl's info feature can be useful to see what states devices
>> are in even if you're not pairing with them. Especially devices with
>> few buttons.
>>
>> Yes there's a time limit because being discoverable is considered
>> vulnerable.
>>
>> On 9/26/20, Gene Heskett <gheskett@shentel.net> wrote:
>>> On Saturday 26 September 2020 06:48:11 Alan Corey wrote:
>>>
>>>> Bring your devices closer together at least until you get them paired.
>>>> BT doesn't have great range. There are covid tracing schemes which
>>>> figure if you got within BT range you're in danger. 20 feet or so
>>>> should be OK. Also heavy WiFi use disrupts it since they're both in
>>>> the same frequency band.
>>>>
>>>> A device may be discoverable only when it's first turned on but there
>>>> has to be a way. My ear buds have one button each and the LEDs flash
>>>> differently: red and blue instead of just red. It's easiest to start
>>>> with them all within reach until they're set up. Playing sound my ear
>>>> buds aren't 100% reliable 20 feet away. At one job a receptionist had
>>>> a BT headset, they worked within that room, not beyond. A niece had a
>>>> BT headset for hands-free driving on her cell phone, mostly didn't
>>>> work outside her car.
>>>>
>>>> With my ear buds a long press on the one button powers them on and
>>>> makes them discoverable for about 1 minute.
>>>
>>> I wasn't aware there was a time limit. Anyway, the transmitter the phone
>>> will need to pair with is about 3 weeks away, so I'll suggest we shelve
>>> this until that kit arrives.
>>>
>>>> On Sat, Sep 26, 2020, 4:22 AM deloptes <deloptes@gmail.com> wrote:
>>>> > Gene Heskett wrote:
>>>> > > Can anyone else contribute here?
>>>> >
>>>> > for the audio you may need the pulse bluetooth module package.
>>>> > pulseaudio-module-bluetooth
>>>
>>>
>>> Cheers, Gene Heskett
>>> --
>>> "There are four boxes to be used in defense of liberty:
>>> soap, ballot, jury, and ammo. Please use in that order."
>>> -Ed Howdershelt (Author)
>>> If we desire respect for the law, we must first make the law
>>> respectable.
>>> - Louis D. Brandeis
>>> Genes Web page <http://geneslinuxbox.net:6309/gene>
>>>
>>>
>>
>>
>> --
>> -------------
>> No, I won't call it "climate change", do you have a "reality problem"? -
>> AB1JX
>> Cities are cages built to contain excess people and keep them from
>> cluttering up nature.
>> Impeach Impeach Impeach Impeach Impeach Impeach Impeach Impeach
>>
>
>
> --
> -------------
> No, I won't call it "climate change", do you have a "reality problem"? -
> AB1JX
> Cities are cages built to contain excess people and keep them from
> cluttering up nature.
> Impeach Impeach Impeach Impeach Impeach Impeach Impeach Impeach
>
--
-------------
No, I won't call it "climate change", do you have a "reality problem"? - AB1JX
Cities are cages built to contain excess people and keep them from
cluttering up nature.
Impeach Impeach Impeach Impeach Impeach Impeach Impeach Impeach
Reply to: