would you please investigate this?
Nope. I have absolutely no interest in reopening the firmly-closed pandora's box that is AppleTV support. I haven't touched that codebase in 3.5 years, so if it works for you that's great, but if it doesn't, sorry..
I think Oleg bumped mesa to HEAD which means he picked up lima/ppir: more tex rework and optimization (!4975) · Merge Requests · Mesa / mesa · GitLab which causes the problem, and is resolved in lima/ppir: use a ready list in node_to_instr (!5092) · Merge Requests · Mesa / mesa · GitLab which has been acked but not merged into mesa yet.
No, and due to a complete lack of cross-platform "casting" solutions that Kodi could implement, that's unlikely to change.
I've been told the AllowedIP setting is for internal WireGuard logic and WireGuard is not controlling the routing table. However, the WG connection is higher in the list of connman services (as it was created most recently) which means it becomes the primary service and default route. To change this we can change the service order via connmanctl, e.g.
connmanctrl move-after vpn_138_116_14_12_wg_domain_tld ethernet_1cf05e0b93f0_cable
Moved vpn_138_116_14_12_wg_domain_tld after ethernet_1cf05e0b93f0_cableSo syntax is: connmanctl move-after <service_to_move> <service_to_move_it_after>
So for scenarios where you want to connect via WireGuard to access content on a remote server, but otherwise still want/need the Internet connection to be as-normal from the local network, we can add another ExecStart in the connman.service file, e.g.
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/connmanctl connect vpn_138_116_14_12_wg_domain_tld
ExecStart=/usr/bin/connmanctl move-after vpn_138_116_14_12_wg_domain_tld ethernet_1cf05e0b93f0_cable
ExecStop=/usr/bin/connmanctl disconnect vpn_138_116_14_12_wg_domain_tldNB: I haven't tested this, but it makes sense to me, so please have a play and report back.
NOTE: I have subsequently been told that the move-after changes are persistent, so would only need to be done once.
If using deinterlaced media make sure the 1080p@25/29.97/30 modes are NOT enabled in the whitelist so that Kodi will default to 50/59.94/60; as Kodi only outputs progressive and needs to render each interlaced half-frame as a full frame, requiring double the frame rate. Also set "Adjust refresh" to start/stop not always.
The one upgrade you can do that would make a difference is to replace the ATA drive with an SSD, as the stock drive is 5400rpm (and likely around a decade old - the fact it hasn't failed is a miracle) and although RAM is an unresolvable issue, swapping on an SSD is greatly improved. I've used SATA SSDs via an adapter in the past, but Amazon/eBay show mSATA to IDE/ATA drive converters now which would be easier to fit inside the case.
Which LE release?
Do you have "WireGuard.PersistentKeepalive" in your config?
I don't see issues with the connection dropping from LE, but I sometimes see issues from macOS to the same WG server.
The OE 6.0.1 image is the best-performing release for the AppleTV that I created as it has hacks like nVidia shader caching and a startup sequence in Kodi designed to force things into swap to create free RAM headroom that helps subsequent playback. However it's all a fudge/compromse and both OE and OSMC have the same fundamental issue: the CHD drivers are not perfect and 256MB RAM is not enough for good Kodi operation.
NB: An RPi Zero (€15 new, prob. cheaper used) with 512MB RAM would be a huge improvement over a mk1 AppleTV.
Setttings > System > Display > Whitelist .. add the specific resolution/refresh rates that you want Kodi to use, e.g. [email protected]/24/50/59.95/60 (skip 25/29.97 if you have interlaced media) and in Settings > Player enable "Adjust display refresh rate to" start/stop.
The Android box market moved onto newer/shinier things so S912 is long-forgotten as the top device in Amlogic's line-up, but there is still commercial interest in S912 from industrial users. LibreComputer is about to release a new board (tartiflette) and because GXM is only a minor evolution from GXL it's a solid/stable platform, which is key for that audience. I've been passed some S912 devices recently and even without an Android dtb or schematics it's been fairly trivial to get all the core hardware working.
However, the tricky bit is always the boot firmware. You either need to self-compile a recent mainline u-boot and experiment with fip sources. The only public ones are for VIM2 and Tartiflette so that shouldn't be a lengthy exercise. Or you extract something from an Android image. Until you solve that piece of the puzzle building higher-level distro's (meta-meson, LE, Armbian, etc.) isn't going to be fruitful.
Setting the wireless regulatory domain may also help to ensure the correct spread of radio channels is available. This becomes a GUI setting in LE 9.2.3 .. before then it has to be done manually from a conf file.
The only way to force a connection to 5GHz only networks is to set the router so it has a dedicated SSID for 5GHz and then only authentticate the LE device to that SSID. Otherwise the WiFi card is doing what it's supposed to do .. find the best connection and use it. The problem with all WiFi networks is that connectivity and performance are variables that are largely outside your control.
RPi4 does not support any decoder licenses as the CPU is capable of software decoding the formats that historically required them.
You have banned repo's installed. No futher support. Official:Forum rules/Banned add-ons - Official Kodi Wiki
It is banned pirate crapware. End of conversation.
If you're using the .img.gz files that I linked, it's the first and only Amlogic device I've encountered which is not looking for boot firmware in the normal and known locations, and there isn't much I can do to help. The last dice-roll is writing them to a USB stick instead of an SD card.