Posts by chewitt

Debug log files that demonstrate the problem will provide more info that your "wonky" description. I'm not doing any development specific the the Slice these days (as none is required) but next Alpha release will be out imminently.

btw, the S905D2 based VIM2 "lite" board has never been released, only the S912 using VIM2 basic/pro boards.

Look in /storage/.cache/connman for the ethernet service and "cat /path/to/file | paste" the settings file so we can see what NTP config is used.

create a udev rule that matches against the USB vendor/device ID and executes a script to do whatever it is you need to do

It's software decoding and 8726MX is (by todays standards) a pretty weak CPU, so no great surprise.

I had an eventful weekend, busy start to the week, and will be travelling for the rest of the week. There's a slim window this evening to test and then PR something, but no promises (sorry).

You can probably discover that something is playing via the JSON API but I don't think there's a method to distinguish whether it's playing a TVH stream or some other stream or something from the Library. You'd be better off asking that Q in Kodi forums.

That's generally the best option anyway.

It's not possible to kill streams within Kodi so you have to restart Kodi with "systemctl restart kodi" (nicer than killing processes)

You can use "scp" or "rsync" to securely move addon and media files to the remote Pi (use SSH key authentication and disable password auth) but you cannot install the addon without restarting Kodi and then manually enabling the automatically-disabled addon.

Once you fix the MAC address and then set connection properties for that MAC in connman (via any method) things will persist normally. There is no need for any extra logic.

Two comments:

You are free to use our project logo to indicate compatibility with our distro (fair use) but we are not your "partner" so please remove our logo and the Kodi Logo from that section of the website - or simply remove the whole section since I'm confident the Raspberry Pi Foundation and WeTek are not your partners either. I'll leave this thread for 24h to allow for changes. If no change, it will be trashed.

Also, in the world of Kodi "Wizards" are frequently associated with Piracy so it would be a good idea to provide links to sources for your addon under a FOSS license so the code can be openly inspected for security and privacy issues.

Thanks.

Connman persists connection data against the interface MAC address and you probably have a cheap USB dongle (or Android box) where the MAC address isn't preset in the factory (as the manufacturer was too cheap to buy an address range) and when there is no preset MAC most kernel drivers assign a random MAC, thus on each boot the persisted connection data doesn't match the current MAC and you need to create a "new" config again. You must also configure connman via the settings addon GUI or the connmanctl command line client. Manual edits to those files have to be made with connman stopped (in which case you will have no network) else connman can update/overwrite the files at any time.

(
sleep 10
/usr/sbin/ip link set dev wlan0 down
/usr/sbin/ip link set dev wlan0 address aa:bb:cc:dd:ee:ff  <= set a MAC address
/usr/sbin/ip link set dev wlan0 up
)&

If my hunch is correct, adding ^ that to /storage/.config/autostart.sh will overwrite the random MAC with a persistent one of your choosing on each boot. You may need to delay Kodi start in LE settings to allow for the network going down/up during startup.

It's an S905X device with Realtek Ethernet. You can grab the device-tree file from the original OS.

If the TV supports CEC you can use the TV remote (CEC is active by default) to navigate and turn SSH on; it's off by default for good reasons. If CEC isn't an option you'll need to borrow a USB keyboard from someone.

If the TV supports CEC you can use the TV remote (CEC is active by default) to navigate and turn SSH on; it's off by default for good reasons. If CEC isn't an option you'll need to borrow a USB keyboard from someone.

It's not a problem specific to RPi devices. The H.264 standard specifies 8-bit content so while it's technically possible to rip media into a 10-bit version of the format, nobody makes GPU/SoC chips that support it and all devices CPU decode it. Most Anime fans end up migrating to Intel NUC's (or similar x86_64 boxes) because lots of CPU grunt is needed to decode with all the fancy GPU based video post-processing that the Anime scene seems to like.

You know the settings addon is available under Addons > Program addons from the Home screen?