Now it doesn't work again since many Milhouse builds 
Actually LibreELEC 9.1-Milhouse #0507 is installed on my RPi3.
Any hint?
Autochange audio output
-
anthontex -
October 8, 2016 at 10:46 AM -
Thread is Unresolved
-
-
I've just tried a fresh install on my pi3 - Millhouse #0512 (12th May'19 build).
Scripts work fine for me still - maybe try a fresh install?
-
Mhh, my is a fresh LibreElec 9.0.1 with updates from Milhouse builds.
-
All I can suggest is to go through the same troubleshooting steps as in this thread.
I started with a fresh libreelec 9.0, added my usual stuff, checked the headphones script worked and updated to Millhouse.
Nothing broke that I've come across yet, and headphones script is still fine.
,
FWIW what I did to get headphones working...
Add the following files:
/storage/.config/system.d/systemd-udevd.service.d/override.conf
/storage/.config/udev.rules.d/99-btautoconnect.rules
/storage/wherever/switchtobluetoothprofile.sh
/storage/wherever/switchtohdmiprofile.sh
Then install the audio profiles addon and set my profiles.
Pair headphones and test.
Update to Millhouse build
re-test
-
-- obsolete -- -
Hi guys,
I have the same issue with my Samsung soudbar. I need to go to settings and connect it manually on every start up. I've tried to do as you recommanded in your different posts:
bluetoothHandler.sh
99-btautoconnect.rules
I didn't find the part about "switchtobluetoothprofile.sh"
I'm pretty new to this and might have missed something obvisous
Thanks in advance.
-
Updated clean to LE 10 on my RPi4 and now Bluetooth autoconnect per udev rule didn't work anymore, again!
Doesn't matter if i set localhost in the override.conf or not.
Permissions for scripts and 99-btautoconnect.rules seems ok for me.
Any hint?
-
No one with a hint here?
-
Seems ok. My udev 99-btautoconnect.rules is there, the two scripts starting from shell are working also, MAC adress from BT headphones didn't changed. Only the udev didn't trigger if my Bluetooth headphones are automatically connected by LE.
Code
Display MoreMorty:~ # udevadm test -a add $(udevadm info -q path -n /dev/input/event1) This program is for debugging only, it does not run any program specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. Load module index Created link configuration context. Reading rules file: /usr/lib/udev/rules.d/30-disable-wakeup.rules Reading rules file: /usr/lib/udev/rules.d/40-modeswitch.rules Reading rules file: /usr/lib/udev/rules.d/50-udev-default.rules Reading rules file: /usr/lib/udev/rules.d/60-autosuspend.rules Reading rules file: /usr/lib/udev/rules.d/60-block.rules Reading rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules Reading rules file: /usr/lib/udev/rules.d/60-drm.rules Reading rules file: /usr/lib/udev/rules.d/60-evdev.rules Reading rules file: /usr/lib/udev/rules.d/60-fido-id.rules Reading rules file: /usr/lib/udev/rules.d/60-input-id.rules Reading rules file: /usr/lib/udev/rules.d/60-iw-regdomain.rules Reading rules file: /usr/lib/udev/rules.d/60-not-joysticks.rules Reading rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules Reading rules file: /usr/lib/udev/rules.d/60-persistent-input.rules Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules Reading rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules Reading rules file: /usr/lib/udev/rules.d/60-sensor.rules Reading rules file: /usr/lib/udev/rules.d/60-serial.rules Reading rules file: /usr/lib/udev/rules.d/61-cdrom.rules Reading rules file: /usr/lib/udev/rules.d/64-btrfs.rules Reading rules file: /usr/lib/udev/rules.d/70-infrared.rules Reading rules file: /usr/lib/udev/rules.d/70-input-repeat.rules Reading rules file: /usr/lib/udev/rules.d/70-joystick.rules Reading rules file: /usr/lib/udev/rules.d/70-mouse.rules Reading rules file: /usr/lib/udev/rules.d/70-power-switch.rules Reading rules file: /usr/lib/udev/rules.d/70-touchpad.rules Reading rules file: /usr/lib/udev/rules.d/75-net-description.rules Reading rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules Reading rules file: /usr/lib/udev/rules.d/78-sound-card.rules Reading rules file: /usr/lib/udev/rules.d/80-alsa-preallocsize.rules Reading rules file: /usr/lib/udev/rules.d/80-clock.rules Reading rules file: /usr/lib/udev/rules.d/80-drivers.rules Reading rules file: /usr/lib/udev/rules.d/80-libinput-device-groups.rules Reading rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules Reading rules file: /usr/lib/udev/rules.d/90-libinput-fuzz-override.rules Reading rules file: /usr/lib/udev/rules.d/90-pulseaudio.rules Reading rules file: /usr/lib/udev/rules.d/90-rpi-add-serial.rules Reading rules file: /usr/lib/udev/rules.d/95-udevil-mount.rules Reading rules file: /usr/lib/udev/rules.d/98-eventlircd.rules Reading rules file: /storage/.config/udev.rules.d/99-btautoconnect.rules Reading rules file: /usr/lib/udev/rules.d/99-systemd.rules Reading rules file: /usr/lib/udev/rules.d/99-wakeup-eth.rules DEVPATH=/devices/virtual/input/input1/event1 DEVNAME=/dev/input/event1 MAJOR=13 MINOR=65 ACTION=add SUBSYSTEM=input TAGS=:power-switch: ID_INPUT=1 ID_INPUT_KEY=1 ID_BUS=bluetooth CURRENT_TAGS=:power-switch: LIBINPUT_DEVICE_GROUP=5/0/0:dc:a6:32:07:c9:9d USEC_INITIALIZED=220026145 run: '/usr/bin/evrepeat -d 500 /dev/input/event1' Unload module index Unloaded link configuration context.99-btautoconnect.rules
CodeACTION=="add", SUBSYSTEMS=="input", ATTRS{name}=="00:22:37:1B:F7:2F", RUN+="/storage/.kodi/userdata/scripts/switchtobluetoothprofile.sh" ACTION=="remove", SUBSYSTEMS=="input", ATTRS{name}=="00:22:37:1B:F7:2F", RUN+="/storage/.kodi/userdata/scripts/switchtoHDMIprofile.sh"Any way to log this to find the problem?