Google restricts the number of Google API searches that can be made per-day with applications. Developers of registered Google API using apps can purchase access to higher numbers of searches, or they can request a free bump to higher tiers and then it's up to Google to grant the request. The net result is .. both the YouTube and Tubed add-ons are wildly more popular than the current tier of requests allowed, and when the free quota is used you see the warning. Neither add-on is going to pay for searches, so the workaround is for you to register with Google for a personal developer account, and then you can have your own API keys with their own quota. You will find instructions for this online. Once you get YouTube add-on working Tubed can/will use the same API key files. It sucks, but unless Google decides to grant Tubed a larger quota, there is nothing the developers (or LE, or Kodi) can do.
Posts by chewitt
-
-
You can create a new SD card from https://chewitt.libreelec.tv/testing/LibreE…85.0-box.img.gz and as a starting point, set the dtb name to "meson-gxl-s905w-p281.dtb" in uEnv.ini. You may need to force recovery boot again for the SD card to be read. The SSV6051 WiFi chip is not supported in the upstream codebase that LE uses (and no hope of that changing) but Ethernet should work. The IR remote will need a keymap creating, but once you get the box booting the LE image it's not hard to capture the IR codes and then I can add that. If you do not have a USB keyboard to complete the first-run wizard with you, can always force SSH on by adding "ssh" to boot params in uEnv.ini.
NB: This is an LE11/Nexus (pre-Alpha) image. There are no LE10/Matrix images .. and this is LE not CE. The upstream codebase is still a little experimental, but works quite well on older GXL hardware.
-
I updated the wiki page, but the root issue is that the files are hosted on third party mirror servers that don't always support https, so we need to downgrade the links to http at some point.
-
Seems like an ideal device for our requirements, for it's performance & high quality DAC RCA outputs
I have a BPI-W2 with the same RTD1296 SoC from experiments a couple of years ago. It wasn't bad hardware in its day, but the challenge is software. There is almost zero support in the upstream kernel and the vendor sources are both ancient and horrificly ugly. That means no chance of an LE image. There was an effort to upstream things https://github.com/afaerber/linux/tree/rtd1295-next but it appears to have fizzled out, and since the hardware is now ageing I doubt it will resume.
-
Most Kodi repo provided add-ons are either available in Nexus specific versions or are Matrix compatible. For non-Kodi add-ons
but most Matrix add-ons will probably work fine. You can install Greek under Kodi settings > Interface > Regional > Language. -
It sounds like the issue with expired CA details in the TLS certificate chain. Have a read here RE: Cannot Install/Update Addons
-
Just got the box and after few hours i read your post again and now i have it working but wifi is not working at all?
jernej and MartinB are in the process of writing support for the SDIO version of RTL8822CS in the rtw88 driver. Once some patches hit the mailing list I will backport them into images. Until then the WiFi is not supported on those boxes.
-
-
LE10 uses Linux 5.10 kernel and support for the latest Intel chips/GPUs was still WIP at the time 5.10 shipped. If you update to a current LE11 nightly image from: https://test.libreelec.net the latest kernels (5.15, and we bumped to 5.16 last night) should have support. Nightlies are running pre-Alpha Kodi Nexus but should be fairly stable to use.
-
LE 9.2.8 exists for Slice3 users with some changes that were needed for widevine support. If you don't use Netflix/Amazon or similar there's no need to update. There are no dedicated Slice3 images for LE10/LE11 but you should be able to cross-grade to RPi2 .. although we have not formally made an RPi2 image yet (maybe soon, for 10.0.2). LE10/LE11 images will be missing support for 3D and software optimised HEVC playback so if you need either of those it'll be best to remain on LE 9.2.x. Anyone with an original CM(1) board will want to remain on the legacy images as those run better on the older/lower spec.
NB: I shipped my Slice3 box to HiassofT last year. I'm not expecting him to do much/anything with it, but at least our primary RPi image maintainer has a sample box. If someone reports breakage at least he'll be able to test it.
-
Is 4K60 enabled? .. If yes, disable it and try again.
-
You can try a current nightly to see if improvements fix anything. Plan B would be to re-rip from your original media.
-
the mainline kernel works thanks to the work of volunteers
Google also bankrolls a lot of effort around the Graphics stack in support of ChromeOS (Chromebooks). Most of the work done by Collabora has its roots in ChromeOS needs. Rockchip staff are also upstreaming a lot of the core drivers and board support. There is still a lot of work done by volunteers, but as vendors go, Rockchip aren't bad (better than most, worse than others).
-
andrkac if the changes were packaged into a custom LE image; commit the changes and push to a public repo like GitHub and share the link so anyone following in your footsteps can see them.
-
Right-click, save-as.
-
I believe the following link is very relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377
If you believe it's relevant have you tried the workarounds it contains? e.g. "ethtool -K eth0 gso off gro off tso off" .. If you shared logs (as asked multiple times) we'd be able to confirm your box produces the same hang messages. No logs = No problem.
NB: LE11 nightlies are here: https://test.libreelec.net/ .. If you want to test safely, stop Kodi, rename /storage/.kodi to .kodi-old and then drop the udpate .tar file in /storage/.update and reboot. You will start with a clean Kodi install - which means we don't "upgrade" all your existing config to LE11 and the downgrade is simply the reverse process; stop Kodi, move folders around so the old folder so the active one and drop the older 'update' file in /storage/.update and reboot again. It's messing .. but low drama.
-
Any suggestions please?
Share logs else we can only make blind guesses at the problem. We suck at guessing, and it's tiresome.
-
intelmorino I think you need to trigger "recovery" mode on the box again. This will trigger the factory u-boot to search for boot scripts and read them, and the important bit - store/overwrite the file-search routines. If you've simply switched the SD card the stored config will be set to look for CE/Legacy files, hence LE bootscripts are not automatically found and read. It's also interesting to see the file rename approach, I wouldn't have thought it would work (but then I don't test with Legacy images or CE at all). Also good to hear the A95XF3 dtb is okay.. I've submitted it upstream and it should be merged for Linux 5.18.
