Posts by chewitt

The proxy in the Kodi GUI does work, but it will only proxy communications made by Kodi itself, not by Kodi add-ons which make independent connections. It's not working as you expected, but it works as designed, so there is no bug to be fixed.

The description sounds [sic] like the high-pitched pops that I heard on Amlogic until I ditched the experimental HDMI pass-through patches.

It's rare (mostly seen with older HDMI-dongle devices that need 32-bit boot firmware) but some BIOS are funny about syslinux on HDD (but fine with it on removable media) and you might need to use a different bootloader, e.g. GRUB. The syslinux and GRUB boot config file formats are quite similar so it's normally fairly obvious how/where to copy-paste the kernel boot params we use. You can also experiment to see if GPT partitions (not MSDOS) show up.

GitHub - librespot-org/librespot: Open Source Spotify client library <= there's some references to installing librespot via cargo here. The LE add-on is packaged to work only on LE so isn't going to work on OSMC or other Kodi using general distros.

It depends on what you use Kodi for. The main driver for upgrades is often the add-on ecosystem; at some point add-on devs stop supporting Javis with updates and then you're forced to bump. If you're not motivated by add-ons the old saying "if it works, don't fix it" always applies

Set desktop to 1080p, it will be much faster to navigate in the Kodi GUI and the TV will do a better job of upscaling 1080p to the TV panel native 4K resolution than Kodi can achieve. Use the whitelist so Kodi switches to 4K when needed for playback.

May 04 13:25:57 N2PLUS connmand[524]: ntp: adjust (slew): +0.000828 sec
May 04 13:43:02 N2PLUS connmand[524]: ntp: adjust (slew): -0.001210 sec
May 04 14:00:06 N2PLUS connmand[524]: ntp: adjust (slew): +0.050135 sec
May 04 14:17:41 N2PLUS connmand[524]: ntp: adjust (slew): -0.078711 sec
May 04 14:34:45 N2PLUS connmand[524]: ntp: adjust (slew): +0.023562 sec
May 04 14:51:50 N2PLUS connmand[524]: ntp: adjust (slew): -0.000587 sec
May 04 15:08:55 N2PLUS connmand[524]: ntp: adjust (slew): +0.002952 sec
May 04 15:25:59 N2PLUS connmand[524]: ntp: adjust (slew): +0.000830 sec
May 04 15:43:03 N2PLUS connmand[524]: ntp: adjust (slew): +0.000999 sec
May 04 16:00:07 N2PLUS connmand[524]: ntp: adjust (slew): +0.001539 sec
May 04 16:17:11 N2PLUS connmand[524]: ntp: adjust (slew): +0.000139 sec
May 04 16:34:16 N2PLUS connmand[524]: ntp: adjust (slew): +0.000668 sec

^ running "journalctl | grep ntp" on an idle Amlogic device in the network here shows a check every 17 mins; more frequent than I would have expected but also nothing too extreme. It's not 20/minute though. Can you corroborate that frequency with journal entries?

Quote from derlinus

Hey Chewitt, no chance to get my trusty Wetek play1 back on a supported version ?

Nope. It's a struggle to get people to work on mainline Linux support for the latest Amlogic chips, let alone a chip from 2014 that was slow at the time it was released. There is nobody doing any work on mainline Linux Meson 6 support, so this unlikely to change, so LE 9.0 is (and will remain) the last release for 8726MX devices like WP1.

It's not the first time we see "Amlogic" MX boxes sold with Rockchip SoCs inside. The chip rotated 45º confirms it's not an S905 chip, this is only seen with RK and Allwinner chips.

From the LE repo, under Inputstream Add-ons

Quote from NickMihai

@chewitt - can you please tell me if the dtb are the same from (LibreELEC-S905.arm-7.0.3.012l.img) where my box it's running perfectly with gxbb_p200_1G_100M_RealtekWiFi.dtb to be put on this release as well? 9.95.2? I think not but worth a try to ask you before. Thanks!

No. LE 7.x-9.x is using Linux 3.14 kernel and LE10 images are using 5.10+ .. everything is different.

LE runs 64-bit kernel and 32-bit userspace (so widevine DRM libs work), so the =arm in the build command is correct, and the aarch64 kernel conf is also correct. The original problem is probably solved by using "boot=LABEL=LIBREELEC disk=LABEL=STORAGE" in extlinux.conf instead of the GUIDs; assuming LIBREELEC/STORAGE are the partition labels.

Someone needs to write a V4L2 demux driver before any work can be done on supporting internal DVB cards (and then there's reworking the demod driver, and the pile of individual tuner drivers). I'm not expecting that work to happen anytime soon.

I've told you where the files are. You have full permission to use some initiative and see what happens.

Quote from jimmyneutron

There’s a reason why we all use VPN’s on Kodi.

^ pirates always (wrongly) assume that everyone else is like them

Quote from jimmyneutron

FYI. I’m here for support and help out anybody who is having or experiencing this issue.

^ the forum staff are here to support people who aren't pirates.

LE 9.2 reached a point where it worked for the majority of use-cases, and then the focus moved away from legacy MMAL/OMX decoding onto the all-new GBM/V4L2 codebase. The older methods still have rough edges that will never be fixed, so if you have problem media I'd suggest you retest under LE10, because bugs/issues found there are of interest to the developers.

LE 9.2.6 from the downloads page on the website

Quote from eisenb11

Will in-place upgrades be allowed on the final release? Understand it's not recommended, but I have a massive DB and would rather not rescan everything again.

No, because add-ons frequently cause problems in any Kodi major version upgrade and the Py2 > Py3 move from K18 > K19 throws up some extra challenges. Nothing impossible for knowledgeable users to figure out, but the other 98% of our userbase will panic and use lots of bad words. We aren't going to stop people from doing it, but the warnings will stay and if people ignore them; users should expect low sympathy when things go wrong.

That said. I would stop Kodi, move /storage/.kodi to /storage/.kodi-old, download the LE10 image file to /storage/.update/ and then reboot. It will upgrade to an empty Kodi install which sidesteps 99% the issues with outdated Py2 add-ons. Then stop Kodi, and move /storage/.kodi-old/userdata to /storage/.kodi/userdata and restart again. DB files should now auto-upgrade and you have all the existing settings etc. for add-ons (once you reinstall them) and thumb caches. Kodi settings may need to be tweaked if stuff changed. Always take a backup and move it off-box first so if something does go tits-up you can always reinstall LE-old and recover.