Posts by chewitt

VIM3:~ # bluetoothctl show
Controller 6C:21:A2:9B:16:AE (public)
    Name: VIM3
    Alias: VIM3
    Class: 0x000c0000
    Powered: yes
    Discoverable: no
    DiscoverableTimeout: 0x000000b4
    Pairable: yes
    UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
    UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
    UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
    UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
    UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
    Modalias: usb:v1D6Bp0246d0536
    Discovering: no
Advertising Features:
    ActiveInstances: 0x00
    SupportedInstances: 0x05
    SupportedIncludes: tx-power
    SupportedIncludes: appearance
    SupportedIncludes: local-name

I've no idea about the Python script, but the "Controller 6C:21:A2:9B:16:AE (public)" line contains the BT device MAC adddress.

You might want to experiment with the audio switcher add-on in our repo.

ping Kwiboo

Which add-ons need it?

Pi DAC boards should be fine (widely used hardware) and I'm not aware of any LE or hardware specific issues with Netflix; it will be as brilliant or sucky as any other non-Android Kodi device (only Android has hardware DRM support).

According to the conversation in RPi Steamlink support [LE9.2] by antonlacon · Pull Request #4319 · LibreELEC/LibreELEC.tv · GitHub the RPi4 requires Xorg (RPi3 does not) which means it's a non-started on LE as we do not use Xorg.

Not technically impossible, but also not as straightforward as you assume as Kodi has a number of dependencies and reverting Python2 > Python3 is more than a simple package bump. I have a suspicion that once you chase down everything for that .. you're basicaally back to our LE 9.2 codebase which is Python2 based.

There is already an MPD add-on in our repo so building derivative audio players should be possible, but it gets complicated when chasing all the extra GUI package dependencies for things like Apache/Nginx. I'd like to see it done though, as all the ARM/Pi audio projects (Volumio/moOde/etc.) are using desktop distros as their base and 400MB images sounds a bit bloated when you're used to something around 120MB. I think LE would be a much better and more focussed base for them.

LE uses connman which stores network setttings using a unique identifier based on the MAC address of the interface. As the network interface does not change between connections, you are forced to manually change the config to change connection.

One way to work around this is using a USB Ethernet adaptor. As this will have a different MAC the settings will be cached and to change connection all you need to do is swap the Ethernet cable between ports. It will also support both being active at the same time; which device becomes eth0 will be dependent on kernel probe order but the on-board NIC should always be faster so this is probably not an issue.

An alternative is (as suggested above) to use WiFi and Ethernet, although here the default behaviour is slightly different. You can have both connections active at the same time, but when Ethernet is connected it always becomes the primary (gateway/routed) connection. This can be changed by copying /etc/connman/main.conf > /storage/.config/connman_main.conf and reordering the PreferredTechnologies line and rebooting.

I'm not familiar with Fritzbox routers and my German is out of practice, but that page looks like it is for port-mapping. Did you put the device in a "DMZ" on the router? If yes, you will probably need to access via the WAN IP address not LAN.

You might be better off using systemd/kernel SMB mounts and pointing Kodi to a "local" file path instead of using the built-in SMB client. I found this was needed with older TimeCapsule devices which also run Apple's own sucky SMB implementation. Have a look in /storage/.config/systemd for the .mount file examples.

Quote from levitsky86

Hi JerneJ!

I still can't play videos through the Apple airplay function, but only music even with this latest version and nightly update. When I turn the switch to play videos in the services menu my phone can't find LibreELEC to stream videos. When I turn that switch off again my phone finds it but only sound is streamed to my Kodi. Is there any solution?

Kodi supports video playback from iOS 8 devices or older. Since then the video protocol changed and Kodi Airplay support became restricted to audio only. If one of the open-source streaming libraries (re)gains support for video Kodi can look at updating things. Until then .. Apple thanks you for funding their locked and proprietary "must pay a $fee to Apple to exist" ecosystem. If you read the help text in the services menu (which I authored) the reason for the toggle switch is clearly described.

To rule out a startup timing issue .. SSH in and run "systemctl restart kodi" .. is the audio hardware now correctly detected?

Kodi automatically doubles the refresh rate of media when appropriate modes are available, so PAL content will use 1080p50 transparently as if it were 1080p25 and YouTube content at 1080p30 will play at 1080p60 (each frame is simply rendered twice). It will make no visible difference to playback, but having the GUI run at higher refresh rates allows transitions to be rendered smoother. I read "I forced the display to 25Hz" as "I forced stuff to look bad" .. and then you're complaining that GUI navigation looks bad.

I have no recollection of anyone on staff or userbase ever atttempting to build Xorg stuff for RPi using our build-system. You will likely run into compile options that are hard-coded to assume x86_64 and missing X11 drivers for the Pi hardware. There is also a high chance that LE drops X11 completely in the near future so the longegivity of whatever you're trying to do might be questionable. You'd be better off with Raspbian.

Unless you enabled "disable password auth" and connect but fail to login (as the setting disabled password auth) .. there is either a firewall active that is blocking traffic or you don't have the right IP address or the device is not on the network correctly. Otherwise SSH works, and has been working in the distro for years without issues.

Linux 5.7-rc1 should be released in the next week and I'll start working on a rebase and update of the patch-set. I ran out of enthusiasm with 5.6 as the patch-set is now 150+ commits and I simply lost track of everything. Kernel bumps normally halve the number..

RPi4 is not perfect, it's had 10-months of development vs. RPi3 which is essentially fettled over 8-years now. In the near future we're about to reinvent the wheel with a move to GBM/V4L2 which will likely add bugs while also moving the Pi codebase forwards and (for RPi4 owners) closer to having 10-bit output and HDR and HD audio things supported. There is a lot of effort being expended on this.

I've been using one for year now (since before launch) as the family daily driver and have zero issues in daily use. I also couldn't care about the lack of USB boot because none of the USB sticks I posess are anywhere near the speed of a decent SD card and I've only had one SD card failure in the last 5-years (completely due to physical abuse) so I don't loose sleep over the inevitable probability that one day one might die. All the media is on an NAS anyway. I also run the GUI at 1080p60 with a BT remove and I don't really notice any artefacts or stutttering during navigation. I can't imaging why anyone would want to run the GUI at 1080@25. I do notice the speed difference on the rare occasions I dig an RPi3 out for testing. I'm not sure that I have done anything unusual or special in setup.

To be clear, the blacklisting on the Kodi forum (and on ours here) is handled via forum plugins that provide the blacklist feeds; it's hands-off, no humans are involved in the listing/unlisting. "StopForumSpam" is usually the source.