TCH

When i play a wav with aplay, then the first ~1 second of it is being cut. I've checked what could it be and the only things i've found were the wifi (which did not caused this as disabling it did nothing) and the A2DP trigger delay. How can i disable the A2DP trigger delay?

I see, so it's not necessary to have multiple PCM entries, i can select with MAC address. Thank you again! (For the '80s radio link too. :) )

Oh, thank you for this detailed howto! I think i'll redo the entire setup with this as i already messed up the system a bit with experimenting. A theoretical question (as i has no means to try it out) what if i will attach multiple BT speakers to the system, how i'm gonna controll them via aplay? Do i need to add a separate pcm for each of them in asound.conf?

Okay, solved it. Ohel was kind enough to share his script (https://github.com/ohel/dotfiles/blob/master/scripts/bluealsa_dev_select.sh) with me which created the PCM device bluetooth, so now it works.

Okay, i tried it with bluealsa-aplay, but still no avail. bluealsa-aplay -L bluealsa:SRV=org.bluealsa,DEV=09:10:67:34:24:40,PROFILE=a2dp BT-SPEAKER, trusted audio-card, playback A2DP (SBC): S16_LE 2 channels 48000 Hz bluealsa-aplay -D bluealsa:SRV=org.bluealsa,DEV=09:10:67:34:24:40,PROFILE=a2dp fancy2.wav bluealsa-aplay: E: Couldn't parse BT addresses: Invalid argument Same happens if i try to do it with an empty MAC address, or nothing. If i do bluealsa-aplay -vv 09:10:67:34:24:40 the test song is begun playing but no sound. I found this page: https://gist.github.com/mill1000/74c7473ee3b4a5b13f6325e9994ff84c And installed a2dp-agent ran it manually, but still not works.

Hello guidol, Thank you for this great tutorial. I can confirm that this is works also on Devuan 2 (based on Debian 9). I only had to install one additional package: libdbus-1-dev. The autoconnect did not worked, but manually connecting in /etc/rc.local did: export LIBASOUND_THREAD_SAFE=0 bluealsa & sleep 1 && /bin/echo -e 'connect 09:10:67:34:24:40\nquit\n' | bluetoothctl However, even if i created ~/.asoundrc as you've suggested, defaults.bluealsa.interface "hci0" defaults.bluealsa.device "09:10:67:34:24:40" defaults.bluealsa.profile "a2dp" defaults.bluealsa.delay 10000 ALSA does not list the BT speaker. The system does recognize it, i hear it playing the connect/disconnect signals, but aplay cannot play through it. If i run aplay -D bluealsa:HCI=hci0,DEV=09:10:67:34:24:40,PROFILE=a2dp fancy2.wav The result is: ALSA lib conf.c:4858:(parse_args) Unknown parameter HCI ALSA lib conf.c:4991:(snd_config_expand) Parse arguments error: No such file or directory ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM bluealsa:HCI=hci0,DEV=09:10:67:34:24:40,PROFILE=a2dp aplay: main:788: audio open error: No such file or directory aplay -L also does not list anything aside the RPi3's own devices. I know, that there is a known problem about RPi3 that it's WiFi conflicts with the BT dongle, but i use no WiFi, it's connected with ethernet cable. I've blocked blacklist modules brcmfmac and brcmutil and also disabled both WiFi and the onboard BT in /boot/config.txt, but to no avail. Can you please advise me, what could i miss?

Okay, found the solution: http://trustfarm.net/index.php/2016/08/17/orangepi-plus-2e-with-5inchlcd/

Hello. I have an Orange Pi PC+. I've just dd-ed Armbian 5.30 to an SD card and booted it up. Whenever i try to set the resolution to anything aside from the default 1280x720, then i only get a black screen. (I did not tried all possibilites.) How can i set my resolution to 800x480? It's connected via HDMI to a small LCD screen panel with this board. The output of h3disp: Usage: h3disp [-h/-H] -m [video mode] [-d] [-c [0-2]] ############################################################################ This is a tool to set the display resolution of your Orange Pi by patching script.bin. In case you use an HDMI-to-DVI converter please use the -d switch. The resolution can be set using the -m switch. The following resolutions are currently supported: 480i use "-m 480i" or "-m 0" 576i use "-m 576i" or "-m 1" 480p use "-m 480p" or "-m 2" 576p use "-m 576p" or "-m 3" 720p50 use "-m 720p50" or "-m 4" 720p60 use "-m 720p60" or "-m 5" 1080i50 use "-m 1080i50" or "-m 6" 1080i60 use "-m 1080i60" or "-m 7" 1080p24 use "-m 1080p24" or "-m 8" 1080p50 use "-m 1080p50" or "-m 9" 1080p60 use "-m 1080p60" or "-m 10" 1080p25 use "-m 1080p25" or "-m 11" 1080p30 use "-m 1080p30" or "-m 12" 1080p24_3d use "-m 1080p24_3d" or "-m 13" 720p50_3d use "-m 720p50_3d" or "-m 14" 720p60_3d use "-m 720p60_3d" or "-m 15" 1080p24_3d use "-m 1080p24_3d" or "-m 23" 720p50_3d use "-m 720p50_3d" or "-m 24" 720p60_3d use "-m 720p60_3d" or "-m 25" 1080p25 use "-m 1080p25" or "-m 26" 1080p30 use "-m 1080p30" or "-m 27" 4kp30 use "-m 4kp30" or "-m 28" 4kp25 use "-m 4kp25" or "-m 29" 800x480 use "-m 800x480" or "-m 31" 1024x768 use "-m 1024x768" or "-m 32" 1280x1024 use "-m 1280x1024" or "-m 33" 1360x768 use "-m 1360x768" or "-m 34" 1440x900 use "-m 1440x900" or "-m 35" 1680x1050 use "-m 1680x1050" or "-m 36" 2048x1536 use "-m 2048x1536" or "-m 37" Two examples: 'h3disp -m 1080p60 -d' (1920x1080@60Hz DVI) 'h3disp -m 720i' (1280x720@30Hz HDMI) You can also specify the colour-range for your HDMI-display with the -c switch. The following values for -c are currently supported: 0 -- RGB range 16-255 (Default, use "-c 0") 1 -- RGB range 0-255 (Full range, use "-c 1") 2 -- RGB range 16-235 (Limited video, "-c 2") ############################################################################