Posts by chewitt

cat /storage/.kodi/temp/kodi.log | paste

^ our in-build paste function to ix.io has a 1mb limit

Quote from Ernestopheles

but it does not work on restart, just on start.

If restart = cold start then autostart.sh will be run. If restart = wake from suspend it will not be run, because autostart is a boot script and waking a suspended system is not boot. Your current script forces the entire boot process to stall for 5 secs. It would be better to (background)& the mount task so that boot can continue normally. You can look at using systemd .power functions in /storage/.config/system.d/ to schedule actions around system suspend and wake events.

We expect behaviour in the latest S912 image to be slightly different as we switched from the ARM mali_kbase driver to the new (meaning new bugs) panfrost DRM in-kernel driver which has now reached broad parity with the ARM driver. Memory behaviour seems to be better. Overall stability seems to be about the same, i.e. there is still crashing but the crashes are different.

kodi.log .. I want to see the output of the python add-on when it fails

Connman stores connection information against a service name which includes the wireless interface MAC address. I have a hunch the WiFi chip does not have a fixed MAC address (i.e. MAC changes with each reboot) which means the previously configured connman service is no longer valid and a "new" configuration (for the new MAC) must be created .. and if you reboot again it will be lost again (rinse/repeat ad infinitum).

To confirm the hunch .. check the MAC address between reboots.

LE people are experts at installing LE .. not ChromeOS. Perhaps read here: MrChromebox.tech

echo "options cfg80211 ieee80211_regdom=DE” > /storage/.config/modprobe.d/cfg80211.conf

Connect ethernet, enable SSH, login, run ^ this command, reboot.

You need to share a debug logfile for us to see what the issue with decompressing widevine is (hopefully something is logged). The resolution switch is normal. It can be changed if you remove the 1080p modes from the whitelist. Kodi will then remain at 4K and will scale lower resolution media to 4K at matching refresh rates. This takes some compute power and most TV's do a better job of scaling 1080p to 4K than Kodi can, so the default behaviour of playing media at its native resolution usually gives the best result.

You need to change the path to the ffmpegx location. Just (re)read this thread.

Quote from snazmeister

My internet speed is more than sufficient to accommodate downloading 4k movies in a hour so title updates etc. are a walk in the park.

I use Sonarr and Radarr for my movies and this takes care of the titles and renaming. Previously it has worked. but stopped somewhere in 8.x I forget which. So, for 9.x I simply made a clean install hoping that the problem was software related and would go away... sadly, it didn't.

There are significant scraper differences between Kodi v17 and v18 - the main one being the default scrapers use a different DB site. And just because you've got a super-fast connection doesn't mean the DB websites don't throttle their responses to ensure manageable load on their web tiers (and they do this). The scraping experience in v18 is quite a bit slower than v17 but there is nothing you or we (or Kodi) can do about that. The main goal was to continue have a scraping experience (instead of no scraping).

video=HDMI-A-1:1920x1080@60

^ can be useful for forcing output instead of the edid.bin file approach.

Amlogic 'GX' SoC's support two video output planes; the Video (primary) plane and OSD (secondary) plane in a fixed z-order where the OSD plane used for the GUI sits behind (not in-front) the Video plane. Only the Video plane supports 4K resolution so in a multi-plane configuration the OSD (GUI) is always rendered at up-to-1080p even if the screen resolution is set to 4K ~ Kodi scales the up-to-1080p OSD plane to 4K and the HDMI driver blends the planes together for output. The kernel DRM driver is missing 10-bit output support at the moment, and since most 4K media is 10-bit HEVC it's rather hard to conduct meaningful 4K testing and there are bugs. Until 4K support moves forwards (current priorities are elsewhere in the codebase) it's best to set 1080p and leave 4K media alone.

LE will always prefer to route over Ethernet if Ethernet + WiFi are available but I don't think that's relevant. if your phone connected to the WiFi network cannot access the GUI of an app which is on the LE/HTPC device with a valid IP in the WiFi network; the issue is with the app on the LE/HTPC device not "listening" for traffic on that interface. Apps are "bound" to IP/port combinations (and IP's belong to interfaces). I'd guess the app is bound solely to the Ethernet IP/port and thus does not listen for traffic on the second (valid) WiFi IP/interface on the host system. That's an app issue, not an LE issue.

"netstat -a" will show you all the open ports and assocaited interfaces. Start there.

Ansible is normally used to describe software packages as part of continuous integration workflows. It's not used (or needed) in LE.

Developers use a variety of text editors to update code/config files and "git" provides version management/control of the changes. Same for Kodi and most open-source software these days.

Quote from Shoog

As far as I am aware this feature is no longer provided in any official versions of LE and there is no interest in bringing it back because of the number of people who end up bricking their boxes using it.

^ as the man said. It will reappear in the future, but not in its current forum, and probably with a restricted set of hardware targets

balbes150 has some mainline kernel test images that run on VIM2 boards using panfrost instead of the missing mali blob. Things run "okay" but panfrost has some OOM stability issues that probably won't be resolved until we switch over to a proper kernel driver. I think we're a couple of months away from something stable enough for regular use. I'd stick in the stoneage for a little while longer until there's a clear option