Posts by V10lator

V10lator · RPi - dtoverlay V10lator May 30, 2016 at 8:58 PM

With 7.0.1 it's even worse:

Code

LibreELEC:~ # dtoverlay dtparam audio=on
* Failed to find overlays directory

and indeed there's no such directory:

Code

LibreELEC:~ # ls /flash/
FSCK0000.REC         FSCK0017.REC         FSCK0034.REC         FSCK0051.REC         FSCK0068.REC
FSCK0001.REC         FSCK0018.REC         FSCK0035.REC         FSCK0052.REC         FSCK0069.REC
FSCK0002.REC         FSCK0019.REC         FSCK0036.REC         FSCK0053.REC         FSCK0070.REC
FSCK0003.REC         FSCK0020.REC         FSCK0037.REC         FSCK0054.REC         FSCK0071.REC
FSCK0004.REC         FSCK0021.REC         FSCK0038.REC         FSCK0055.REC         SYSTEM
FSCK0005.REC         FSCK0022.REC         FSCK0039.REC         FSCK0056.REC         SYSTEM.md5
FSCK0006.REC         FSCK0023.REC         FSCK0040.REC         FSCK0057.REC         bcm2709-rpi-2-b.dtb                                                                                                   
FSCK0007.REC         FSCK0024.REC         FSCK0041.REC         FSCK0058.REC         bcm2710-rpi-3-b.dtb                                                                                                   
FSCK0008.REC         FSCK0025.REC         FSCK0042.REC         FSCK0059.REC         bootcode.bin
FSCK0009.REC         FSCK0026.REC         FSCK0043.REC         FSCK0060.REC         cmdline.txt
FSCK0010.REC         FSCK0027.REC         FSCK0044.REC         FSCK0061.REC         config.txt
FSCK0011.REC         FSCK0028.REC         FSCK0045.REC         FSCK0062.REC         fixup.dat
FSCK0012.REC         FSCK0029.REC         FSCK0046.REC         FSCK0063.REC         kernel.img
FSCK0013.REC         FSCK0030.REC         FSCK0047.REC         FSCK0064.REC         kernel.img.md5
FSCK0014.REC         FSCK0031.REC         FSCK0048.REC         FSCK0065.REC         start.elf
FSCK0015.REC         FSCK0032.REC         FSCK0049.REC         FSCK0066.REC
FSCK0016.REC         FSCK0033.REC         FSCK0050.REC         FSCK0067.REC

Display More

V10lator

Quote from lrusak

It's all been covered before
LibreELEC

Thanks, I tried that but stuck at pactl list short, there are no usable sources/sinks:

Code

LibreELEC:~ # pactl list short
0       module-native-protocol-unix
1       module-stream-restore
2       module-device-restore
3       module-default-device-restore
4       module-rescue-streams
5       module-always-sink
6       module-null-sink        sink_name=auto_null sink_properties='device.description="Dummy Output"'
7       module-suspend-on-idle
8       module-position-event-sounds
9       module-dbus-protocol
10      module-bluetooth-policy
11      module-bluetooth-discover
12      module-bluez5-discover
13      module-zeroconf-publish
14      module-native-protocol-tcp      auth-anonymous=1
15      module-switch-on-connect
17      module-udev-detect
0       auto_null       module-null-sink.c      s16le 2ch 44100Hz       SUSPENDED
0       auto_null.monitor       module-null-sink.c      s16le 2ch 44100Hz       SUSPENDED
9       protocol-native.c       pactl

Display More

I guess I did everything correctly:

Code

LibreELEC:~ # lsmod
Module                  Size  Used by
snd_bcm2835            22554  0
snd_pcm                66018  1 snd_bcm2835
snd_timer              17428  1 snd_pcm
snd                    40540  3 snd_bcm2835,snd_timer,snd_pcm
hci_uart               14478  1
btbcm                   5379  1 hci_uart
bluetooth             282086  21 btbcm,hci_uart
brcmfmac              172683  0
brcmutil                4893  1 brcmfmac
cfg80211              229385  1 brcmfmac
bcm2835_gpiomem         2652  0
bcm2835_wdt             2777  0
LibreELEC:~ # ls /lib/modules/4.4.7/kernel/sound/arm/
snd-bcm2835.ko

Display More

V10lator

Quote from lrusak

We only support audio the other way by default, so RPi --> Bluetooth audio speaker, not the other way around. It is possible to make it work manually but we cannot make it the default for all devices.

Any hint on how to do that? I see you're using bluetoothd but can't even find it's config files.

Also then the question still stands:

Quote from V10lator

I wonder why does LibreELEC advertise A2DP when it doesn't work?

It might be a really good idea to not advertise what you can't handle (a user making it work manually will re-add the advertising, too).

V10lator

Today I tried to pair my Raspberry Pi 3 with my Jolla smartphone (running SailfishOS). As soon as the devices are connected SailfishOS routes all audio to the RPi but LibreELEC just seems to route it to trash. So the result is a completely muted phone and the only way to get audio back is to close the bluetooth connection.

Now I wonder why does LibreELEC advertise A2DP when it doesn't work? Or is this maybe just related to the RPi 3 and if so: Anything I could test?

V10lator · Chromium? V10lator May 30, 2016 at 3:50 AM

Quote from lrusak

Which requires wayland which we also don't use

I guess you're also not using Mir? Sorry if that's off-topic but what are you using (any documentation available) ?

V10lator · Chromium? V10lator May 30, 2016 at 12:29 AM

Quote from chewitt

Chromium requires Xorg so it's only available on Generic.

Arch has an Xorg-free Chromium: AUR (en) - chromium-wayland

Posts by V10lator

RPi - dtoverlay

[Bluetooth] LibreELEC "mutes" SailfishOS devices

[Bluetooth] LibreELEC "mutes" SailfishOS devices

[Bluetooth] LibreELEC "mutes" SailfishOS devices

Chromium?

Chromium?