08-10-2018, 05:17 PM
(This post was last modified: 08-10-2018, 05:20 PM by Tim Curtis.
Edit Reason: eta
)
Ok, bluealsa-aplay not starting would explain the "no audio" symptom.
bluealsa-aplay is started by a UDEV rule set. It uses /etc/bluealsaaplay.conf file to determine the audio output device.
/etc/udev/rules.d/10-a2dp-autoconnect.rules
------>/usr/local/bin/a2dp-autoconnect
Try monitoring UDEV during a connection from the Echo.
udevadm monitor -p
If in fact a connection is happening then the monitor will dump out a bunch of properties similar to below. A good connection will have properties that contain the 'NAME' attribute with a mac address as the value.
-Tim
bluealsa-aplay is started by a UDEV rule set. It uses /etc/bluealsaaplay.conf file to determine the audio output device.
/etc/udev/rules.d/10-a2dp-autoconnect.rules
------>/usr/local/bin/a2dp-autoconnect
Try monitoring UDEV during a connection from the Echo.
udevadm monitor -p
If in fact a connection is happening then the monitor will dump out a bunch of properties similar to below. A good connection will have properties that contain the 'NAME' attribute with a mac address as the value.
Code:
KERNEL[6804.792571] add /devices/virtual/input/input2 (input)
ACTION=add
DEVPATH=/devices/virtual/input/input2
EV=100007
KEY=2fc800 1452 0 0 0 0 10300 49e8 c00 e1680 f f8100000 10000ffc
MODALIAS=input:b0005v0000p0000e0000-e0,1,2,14,k71,72,73,8A,8B,A3,A5,A6,A7,A8,AB,AE,C8,C9,D0,161,164,166,16A,16C,18B,18E,18F,190,191,192,193,195,ramlsfw
NAME="5C:8D:4E:91:48:AE"
PRODUCT=5/0/0/0
PROP=0
REL=0
SEQNUM=1240
SUBSYSTEM=input-Tim
