Posts by lrusak

Quote from anthontex

Thank you just tried and now the problem that I had regarding the black screen is disappeared. I've test game boy and PlayStation emulator: the first works good but I can't save. The second works but is painful slow (on raspberry 2) and also it doesn't auto remap keys like the game boy emulator so with a ps3 controller I can only "control" kodi and not the game itself, while in the GB everything is fine controller too . Thanks for you update another strange thing is that i can't install the game repo provided it's not listed .

Even if you cannot save you should be able to use "save states" however this may require a keyboard to be plugged in to access the menu by hitting "enter" then going the the "save states" manager icon.

The psx controller issues I am aware of and will try and fix it.

On RPi you should make sure to use pcsx-rearmed as the emulator instead of beetle-psx if you aren't already.

Quote from ronbaby

That's still a "pull" solution, and thus less convenient, because I'd still have to be looking at it on a regular and/or frequent basis... even though most of the time there will ne no new news or announcements.

A "push" solution, like an announcement mailing list would be more conenient for those who want to know about new developments, but can't spare the time to check the web site every day until something new actually is announced.

Like I said, use ifttt then

The best thing to do would be to follow our rss feed. Perhaps there is a recipe using ifttt that will email you when a new rss post is made.

RSS link: feed

Honestly to me it just seems like it depends on the device. I have a bluetooth speaker that auto connects fine when I turn the speaker on yet my iPhone does not auto connect.

Perhaps it is something in bluez that I can look into.

Quote from Hans Gruber

Thanks, will the Transmission service automatically start up at each boot with that method?

Yes it will.

Quote from nickrob84

Has their been any movement on the 64bit side of things?

Yes, as far as I am aware the aarch64 kernel will boot, but there are problems with the VPU.

maybe popcornmix can shed some more light on it or can point you in the right direction regarding kernel sources.

Post a proper debug log after trying to play a file with a DTS-HD track.

No, because currently the RPi3 uses the RPi2 build, this is because aarch64 kernel support isn't ready yet for the RPi3.

But make sure it's using that exact device name in the kodi audio settings. There should be 3 HDMI devices listed, you need to select the correct one.

Quote from selector34

Hi - Here's my kodi.log

404 File Not Found - Jumpshare

Hope it provides info

Please use pastebin, I don't like having to download random files off the internet. Also, please enable debugging!

It looks like you need to use the audio device and passthrough device labled as "PIO AV Receiver on HDMI #1" or "PIO AV Receiver on DisplayPort #1"

I have this available for my retroplayer builds however it just crashes. No idea how it works with plain retroarch though.

post a kodi debug log please.

Also, make sure you enable advanced settings mode and have passthtough, DTS-HD and True HD enabled.
Settings - Official Kodi Wiki

Quote from V10lator

So I thought maybe I need dtparam=audio=on

just put it in config.txt

mount -o remount,rw /flash
nano /flash/config.txt

Quote from V10lator

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

You have filesystem corruption.

no idea really

LibreELEC:~ # pactl load-module module-udev-detect
16

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        
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        
16    module-udev-detect        
17    module-alsa-card    device_id="0" name="platform-audio" card_name="alsa_card.platform-audio" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1"    
18    module-bluez5-device    path=/org/bluez/hci0/dev_28_E1_4C_6A_9F_D5    
19    module-loopback    source="bluez_source.28_E1_4C_6A_9F_D5" source_dont_move="true" sink_input_properties="media.role=music"  
1    alsa_output.platform-audio.analog-stereo    module-alsa-card.c    s16le 2ch 44100Hz    SUSPENDED
1    alsa_output.platform-audio.analog-stereo.monitor    module-alsa-card.c    s16le 2ch 44100Hz    SUSPENDED
2    bluez_source.28_E1_4C_6A_9F_D5    module-bluez5-device.c    s16le 2ch 44100Hz    SUSPENDED
0    1    -    module-loopback.c    s16le 2ch 44100Hz
0    2    -    module-loopback.c    s16le 2ch 44100Hz
7    protocol-native.c    pactl
0    alsa_card.platform-audio    module-alsa-card.c
1    bluez_card.28_E1_4C_6A_9F_D5    module-bluez5-device.c

LibreELEC:~ # pactl set-default-sink alsa_output.platform-audio.analog-stereo
LibreELEC:~ # pactl set-default-source bluez_source.28_E1_4C_6A_9F_D5

LibreELEC:~ # pactl info
Server String: /var/run/pulse/native
Library Protocol Version: 30
Server Protocol Version: 30
Is Local: yes
Client Index: 9
Tile Size: 65496
User Name: root
Host Name: LibreELEC
Server Name: pulseaudio
Server Version: 8.0
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.platform-audio.analog-stereo
Default Source: bluez_source.28_E1_4C_6A_9F_D5
Cookie: 6bfa:6fb3

Note that "alsa_output.platform-audio.analog-stereo" is actually my HDMI output

Nope

Quote from V10lator

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:

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).

It's all been covered before
LibreELEC

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.