Also den Bluetooth vom Hisilicon mali habe ich nie zum laufen gebracht, also habe ich jetzt einen Stick ASUS BT500 dran gehängt, funktionieren tut das nur teilweise eigentlich wollte ich Kopfhörer dranhängen - das ist für mich jetzt einfach zur Doku
# Firmware manuell installieren
wget https://git.kernel.org/pub/scm/linux/ke ... 1bu_fw.bin -O /lib/firmware/rtl_bt/rtl8761bu_fw.bin
wget https://git.kernel.org/pub/scm/linux/ke ... config.bin -O /lib/firmware/rtl_bt/rtl8761bu_config.bin
# Treiber neu laden
modprobe -r btusb
modprobe btusb reset=1
# Für alle USB-Ports (als root)
find /sys/bus/usb/devices/ -name power/control -exec sh -c 'echo on > {}' \;
find /sys/bus/usb/devices/ -name power/autosuspend -exec sh -c 'echo -1 > {}' \;
hcitool cmd 0x03 0x0003 # Hardware-Reset
hciconfig hci0 up
A2DP hast du mir für bluetootd ein main.conf das ich möglichst Kompatibel mit Soundcore2 Kopfhörern bin, die beiden wollen nicht wirklich miteinander sprechen. [CHG] Controller CC:28:AA:68:C9:0C Discovering: yes
[NEW] Device AC:12:2F:D3:EC:9B AC-12-2F-D3-EC-9B
[CHG] Device AC:12:2F:D3:EC:9B LegacyPairing: no
[CHG] Device AC:12:2F:D3:EC:9B RSSI: 127
[CHG] Device AC:12:2F:D3:EC:9B Name: Soundcore Life P2
[CHG] Device AC:12:2F:D3:EC:9B Alias: Soundcore Life P2
[CHG] Device AC:12:2F:D3:EC:9B LegacyPairing: yes
[CHG] Device AC:12:2F:D3:EC:9B RSSI is nil
[bluetooth]# connect AC:12:2F:D3:EC:9B
Attempting to connect to AC:12:2F:D3:EC:9B
[CHG] Device AC:12:2F:D3:EC:9B Connected: yes
[CHG] Device AC:12:2F:D3:EC:9B UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device AC:12:2F:D3:EC:9B UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device AC:12:2F:D3:EC:9B UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device AC:12:2F:D3:EC:9B UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device AC:12:2F:D3:EC:9B UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device AC:12:2F:D3:EC:9B UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device AC:12:2F:D3:EC:9B UUIDs: 0000eb03-d102-11e1-9b23-00025b00a5a5
[CHG] Device AC:12:2F:D3:EC:9B ServicesResolved: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device AC:12:2F:D3:EC:9B ServicesResolved: no
[CHG] Device AC:12:2F:D3:EC:9B Connected: no
Soundcore Life P2 Bluetooth - mit einem ASUS BT500 Stick an einer maxytecmultise das ist so eine TV Box mit einem hisilicon mali arm und dem Betriebssystem openatv nachdem es unter 7.5.1 nicht ging habe ich jetzt auf die Beta von 24.05.2025 7.6 openatv upgedated neuer geht kaum.
cat /etc/bluetooth/main.conf
[General]
Name = MaxytecBox
Class = 0x20041C
MultiProfile = true
ControllerMode = dual
FastConnectable = true
[Policy]
AutoEnable=true
Beim Rumexperementieren um es zum laufen zu bringen hatte ich mir zuviel oder die falschen Kernelmodule installiert, der bnep-Fehler beim /etc/init.d/bluetooth start war die Ursache
Das script räumte danach auf und es bleiben die Module übrig, die ich wirklich brauche
#####################################
#!/bin/sh
KEEP_MODULES="
kernel-module-bluetooth-4.4.35
kernel-module-bnep-4.4.35
kernel-module-btusb-4.4.35
kernel-module-btrtl-4.4.35
kernel-module-btbcm-4.4.35
kernel-module-btintel-4.4.35
kernel-module-hidp-4.4.35
kernel-module-rfcomm-4.4.35
kernel-module-hci-uart-4.4.35
kernel-module-hci-vhci-4.4.35
kernel-module-rtk-btusb-4.4.35
kernel-module-r8188eu-4.4.35
kernel-module-cfg80211-4.4.35
kernel-module-xfs-4.4.35
kernel-module-libcrc32c-4.4.35
kernel-module-tntfs-4.4.35
kernel-module-mali-4.4.35
kernel-module-multiboxse_1-4.4.35
kernel-module-multiboxse_2-4.4.35
kernel-module-multiboxse_3-4.4.35
kernel-module-multiboxse_4-4.4.35
"
INSTALLED_LIST="/tmp/installed-kmods.txt"
REMOVE_LIST="/tmp/remove-kmods.txt"
# Alle installierten Kernel-Module holen
opkg list-installed | grep ^kernel-module > "$INSTALLED_LIST"
# Entfernen-Liste leeren
> "$REMOVE_LIST"
# Durch alle installierten Module iterieren
while read pkg; do
echo "$KEEP_MODULES" | grep -q "^$pkg$"
if [ $? -ne 0 ]; then
echo "$pkg" >> "$REMOVE_LIST"
fi
done < "$INSTALLED_LIST"
echo "
cat "$REMOVE_LIST"
echo ""
read -p "Sicher? [j/N] " confirm
if [ "$confirm" != "j" ]; then
echo "
exit 1
fi
while read pkg; do
echo "Entferne $pkg ..."
opkg remove "$pkg"
done < "$REMOVE_LIST"
echo "
################################
Keine Ahnung warum bluealsa habe ich nicht zum laufen gebracht und damit geht dann auch Sink
cat /etc/init.d/pulseaudio
#!/bin/sh
# /etc/pulse/client.conf may have been changed if ran pw.
# note that user and group 'pulse' is only when start pulseaudio with --system.
# so code below about 'pulse' group not required. however, see /etc/pulse/default.pa
# -- users must belong to group 'audio'.
# keine Ahnung wie das Enigmadisplay heisst
export DISPLAY=:0
if [ "$1" == "restart" ];then
pulseaudio -k
sleep 0.1
/usr/bin/pulseaudio --start --log-target=syslog --disallow-exit --exit-idle-time=-1
exec start-pulseaudio-x11
fi
if [ "$1" == "stop" ];then #20221026
pulseaudio -k
exit
fi
# bluetoothd
# don't hang around here very long waiting for it...
#wait for bluetoothd...
if [ -x /etc/init.d/bluetooth ];then
for CNT in 0 1 2 #3 4 5 6 7 8 9 10 11 12 13 14
do
pidof bluetoothd >/dev/null
[ $? -eq 0 ] && break
sleep 1
done
echo "/etc/init.d/pulseaudio: waited ${CNT} seconds for bluetoothd"
fi
# this used to be done in /etc/init.d/10alsa
# for pa, 1st bootup, level setting and store is in /usr/sbin/delayedrun
if [ -f /etc/asound.state ];then
alsactl -f /etc/asound.state restore
fi
echo "/etc/init.d/pulseaudio: pulseaudio daemon running"
#i have configured /etc/pulse/daemon.conf so that it doesn't exit.
# (so probably don't need respawning enabled)
#note, --system mode, daemon changes user and group to 'pulse', and users have to
# be in that group to use audio. The pulse user needs to be in the audio and
# bluetooth groups in order to be able to use ALSA and bluetooth devices.
# All users that need access to PulseAudio have to be in the pulse-access group, even root.
# /usr/bin/pulseaudio --start --log-target=syslog --system --disallow-exit
# no, run as user root,
# see ref: http://billauer.co.il/blog/2014/01/pa-multiple-users/
# ...unix socket, changes to /etc/pulse/default.pa and for non-root users ~/.config/pulse/defaut.pa
# see also /usr/local/clients/setup-client, /etc/pulse/daemon.conf,
# /etc/pulse/default.pa, /etc/pulse/client.conf
#note, --start also implies --daemonize
#note, --disallow-exit --exit-idle-time=-1 are already specified in /etc/pulse/daemon.conf
/usr/bin/pulseaudio --start --log-target=syslog --disallow-exit --exit-idle-time=-1
####### Ende /etc/init.d/pulseaudio
pulseaudio habe ich mir alles installiert was in der 7.6-BETA verfügbar war. Viel zu viel.
pactl list | grep bluez
Name: module-bluez5-discover
Vermutlich hätten die gereicht
pulseaudio-module-bluetooth-discover - 17.0-r0 - PulseAudio module for bluetooth-discover
pulseaudio-module-bluetooth-policy - 17.0-r0 - PulseAudio module for bluetooth-policy
pulseaudio-module-bluez5-device - 17.0-r0 - PulseAudio module for bluez5-device
pulseaudio-module-bluez5-discover - 17.0-r0 - PulseAudio module for bluez5-discover
Nach dem das geschehen war gelang zum ersten Mal ein connect und him Headset bekam ich auch den Bestätigungston, das die maxytecmultise über den Bluetoothstick händlich auch mit den Kopfhörern spricht --- ach ja das Bluetooth-Keyboard ging vorher schon unter der openatv 7.5.1
Card #1
Name: bluez_card.AC_12_2F_D3_EC_9B
Driver: module-bluez5-device.c
Owner Module: 21
Properties:
device.description = "Soundcore Life P2"
device.string = "AC:12:2F:D3:EC:9B"
device.api = "bluez"
device.class = "sound"
device.bus = "bluetooth"
device.form_factor = "headset"
bluez.path = "/org/bluez/hci0/dev_AC_12_2F_D3_EC_9B"
bluez.class = "0x240404"
bluez.alias = "Soundcore Life P2"
bluetooth.battery = "100%"
device.icon_name = "audio-headset-bluetooth"
device.intended_roles = "phone"
bluetooth.codec = "mSBC"
Profiles:
a2dp_source: High Fidelity Capture (A2DP Source) (sinks: 0, sources: 1, priority: 20, available: no)
a2dp_sink: High Fidelity Playback (A2DP Sink) (sinks: 1, sources: 0, priority: 40, available: no)
handsfree_head_unit: Handsfree Head Unit (HFP) (sinks: 1, sources: 1, priority: 30, available: yes)
off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
Active Profile: handsfree_head_unit
Ports:
headset-output: Headset (type: Headset, priority: 0, latency offset: 0 usec, availability unknown)
Part of profile(s): a2dp_sink, handsfree_head_unit
headset-input: Headset (type: Headset, priority: 0, latency offset: 0 usec, availability unknown)
Part of prCard #1
Name: bluez_card.AC_12_2F_D3_EC_9B
Driver: module-bluez5-device.c
Owner Module: 21
Properties:
device.description = "Soundcore Life P2"
device.string = "AC:12:2F:D3:EC:9B"
device.api = "bluez"
device.class = "sound"
device.bus = "bluetooth"
device.form_factor = "headset"
bluez.path = "/org/bluez/hci0/dev_AC_12_2F_D3_EC_9B"
bluez.class = "0x240404"
bluez.alias = "Soundcore Life P2"
bluetooth.battery = "100%"
device.icon_name = "audio-headset-bluetooth"
device.intended_roles = "phone"
bluetooth.codec = "mSBC"
Profiles:
a2dp_source: High Fidelity Capture (A2DP Source) (sinks: 0, sources: 1, priority: 20, available: no)
a2dp_sink: High Fidelity Playback (A2DP Sink) (sinks: 1, sources: 0, priority: 40, available: no)
handsfree_head_unit: Handsfree Head Unit (HFP) (sinks: 1, sources: 1, priority: 30, available: yes)
off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
Active Profile: handsfree_head_unit
Ports:
headset-output: Headset (type: Headset, priority: 0, latency offset: 0 usec, availability unknown)
Part of profile(s): a2dp_sink, handsfree_head_unit
headset-input: Headset (type: Headset, priority: 0, latency offset: 0 usec, availability unknown)
Part of profile(s): a2dp_source, handsfree_head_unitofile(s): a2dp_source, handsfree_head_unit
Aber als handsfree unit .....
root@maxytecmultise:/usr/share/sounds/alsa# aplay -D bluealsa:HCI=hci0,DEV=AC:12:2F:D3:EC:9B,PROFILE=a2dp *.wav
Playing WAVE 'Front_Center.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
Playing WAVE 'Front_Left.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
Playing WAVE 'Front_Right.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
Playing WAVE 'Noise.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
Playing WAVE 'Rear_Center.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
Playing WAVE 'Rear_Left.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
Playing WAVE 'Rear_Right.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
Playing WAVE 'Side_Left.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
Playing WAVE 'Side_Right.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
das ist dann die Macadresse vom Master und der Beweis erbracht, das die Hardware läuft.
Das die läuft nutzt mir nur mit enigma2 gar nix.
root@maxytecmultise:/usr/share/sounds/alsa# cat /etc/asound.conf
pcm.!default {
type plug
slave.pcm "bluep2"
}
ctl.!default {
type bluealsa
}
pcm.bluep2 {
type plug
slave.pcm {
type bluealsa
interface "hci0"
device "AC:12:2F:D3:EC:9B"
profile "a2dp"
hint {
show on
description "Soundcore Life P2 Bluetooth Headset"
}
}
}
ctl.bluep2 {
type bluealsa
}
hilft nicht, nach einem Neustart ist alles weg
aplay -D bluealsa:HCI=hci0,DEV=AC:12:2F:D3:EC:9B,PROFILE=a2dp *.wav
ALSA lib ../../../git/src/asound/bluealsa-pcm.c:702:(_snd_pcm_bluealsa_open) BlueALSA connection failed: Connection refused
aplay: main:857: audio open error: Connection refused
Nein nicht alles nachdem sie dem System bekannt sind verbinden sie ich jetzt automatisch nach messagelog
Bluetooth: hci0 urb dc1f2780 failed to resubmit (2)
usbcore: registered new interface driver btusb
input: AC:12:2F:D3:EC:9B as /devices/virtual/input/input5