[PROBLEM] Issue with Blutooth in 4.1

[Tim Curtis]

BINGO!!!!

In the latest commits they changed the default enabled plugins:

Code:

Available BT profiles:
 - a2dp-source Advanced Audio Source
 - a2dp-sink   Advanced Audio Sink
 - hsp-hs      Headset
 - hsp-ag      Headset Audio Gateway
 - hfp-hf      Hands-Free
 - hfp-ag      Hands-Free Audio Gateway

By default only output profiles are enabled, which includes A2DP Source and
HSP/HFP Audio Gateways. If one wants to enable other set of profiles, it is
required to explicitly specify all of them using `-p NAME` options.

So I changed the /etc/systemd/system/bluealsa.service adding -p a2dp-sink .

Code:

#
# 2018-01-26 TC moOde 4.0
#

[Unit]
Description=BluezAlsa proxy
Requires=bluetooth.service
After=bluetooth.service

[Service]
Type=simple
#User=pi
#Group=audio
ExecStart=/usr/bin/bluealsa -p a2dp-sink

[Install]
WantedBy=multi-user.target

And everything resurrected  .
Again now I have the problem that once I connect a device the volume goes to 100%, awaking my son   and make me fight with my wife...
I want to test all input profiles, now but this is the right way!!!

Hi,

- What type of audio device?
- What is MPD volume (Software, Hardware, Disabled)?

I've added volume management to Bluetooth for the MPD volume disabled (0dB) case.

-TIm

Hi Tim,
- The audio device is an HiFiBerryAMP with
- HW Volume enabled.

So the in version 4.0 the volume was managed by MPD?

4.0 had no volume coordination between MPD and Bluetooth.
4.1 added volume management and "Resume after MPD" but not implemented for the 0dB case
4.2 covers the 0dB case and fixes a bug in volume mgt :-)

-Tim