Posts by chewitt

Please update to the current LE 11 beta; there are lots of fixes and enhancements for various RPi related screen issues. There will be no fixes for anything found under LE 10 now so best to start fom the current/active codebase.

If you locally mount remote drives the OS is frequently doing something in the background which generates activity and the drives will rarely spin down (and this is not controllable). If you use the SMB/NFS client built into Kodi you might run into client timeout issues (something that can be fine-tuned in advancedsettings.xml) but Kodi shouldn't be accessing the NAS unless scraping or playing and the drives should spin down more frequently. In short; from your description you're doing the former, so it's an expected behaviour.

If you installed add-on's with graphics dependencies under GBM and then swapped to X11 you will need to remove the add-ons, clear the add-on package cache, then reinstall the add-ons; else you will have add-ons with GLES dependencies on a GL platform. The same is true if you go in the other direction.

The main thing I was looking for was SDIO WiFi support (there are some fixes added since 10.95.1) and that looks good now.

I need to find the name of the manufacturer for Vorke to create a vendor binding, then I'll create a proper device-tree file for next test.

Ethernet looks to be working this time. It has 100Base-T speed, but that could be due to cables or switch ports? - WiFi shows more output this time, but still has errors so we might need to reduce the speed of the SDIO bus.

Please update to https://chewitt.libreelec.tv/testing/LibreE….arm-11.0.0.tar and share "dmesg | paste" URL again.

Thanks for the Android dts. It confirms a couple of things that I'll need to prepare a proper dts file.

Quote from Capper

How can I get the Seekbar to stay visible for a few seconds again? Thanks very much

Post a request to the Confluence skin maintainers in the Kodi forum to implement the same feature/setting that Estuary has.

If it works great until turning off .. he must be since GBM won't show any output ever.

2469 Are you running "getedid create" or trying to do things manually from the guide?

Google claims the Vorke Z6 plus is the same as some Tanix box which had board pictures showing QCA9377 as the SDIO module. SDIO WiFi should probe and load automagically regardless of device-tree content, so not sure why it doesn't, but BT is serial UART based and needs the correct content in device-tree to probe and load drivers. VFD also needs content in device-tree and some detective work.

If it's a Gbit Ethernet box the Q200 device-tree should work (not Q201 which is for 10/100 boxes). I'd guess Ethernet not-working correctly is the reason for adding the USB Ethernet adaptor?

I'll think about creating something, but start with logs from Q200 dtb please. If you have the original dts or dtb file from Android that would also be useful to have.

For other boxes; start individual threads else I easily lose track of things.

Quote from chewitt

You will obviously need to modify the /path/to/brightness for whatever LEDs are on the board

^^^^

Quote from excalibur

Which LE11 image is best to test : nightly or beta ?

LE 11.0.0 should be out within 24h so doesn't really matter which.

WP2:~ # find / -name brightness
/sys/devices/platform/leds/leds/wetek-play:wifi-status/brightness
/sys/devices/platform/leds/leds/wetek-play:ethernet-status/brightness
/sys/devices/platform/leds/leds/blue:power/brightness

Let's say the blue:power LED is the annoying one:

echo 0 > /sys/devices/platform/leds/leds/blue:power/brightness

Should make it turn off.. and we can script this to run after startup:

echo "(sleep 10 && echo 0 > /sys/devices/platform/leds/leds/blue:power/brightness)&" > /storage/.config/autostart.sh

Should result in the LED being turned off 10 seconds after boot starts. You will obviously need to modify the /path/to/brightness for whatever LEDs are on the board. NB: this only works if the LEDs are GPIO controllable; some LEDs are hardwired.

No debug log = No problem to investigate.

You can power the board off from flirc, but not power on as the USB device is not awake/listening once off. It may be possible to configure a power on event from the IR sensor, but that normally depends on the low-level boot firmware and the device being suspended rather than powered off (so the sensor can receive the power-on code). jernej would need to comment on that possibility.

It makes no difference because we will overwrite the partition table on the card. As long as the OS can see the card, all is good.

The Cubox keymap is probably for an older Linux kernel and will need to be transcribed into the 'toml' format used now. There is a section in the wiki on creating custom keymaps. It needs to be updated to reference the toml format but the files you need to create and their locations are still correctly described. There are lots of existing keymaps in /usr/lib/udev/rc_keymaps/ to crib the toml format from.

Or the whole point of flirc is that you can program it to respond to any remote. If you install the config app on a PC it should take no more than 2 mins to map all the core Kodi functions to remote buttons.

The Generic x86_64 image switched to GBM/V4L2 graphics which means we use OpenGLES rendering not OpenGL required for ProjectM. The Generic-Legacy image still uses older X11 and OpenGL approach, and ProjectM should be available there, but then you lose HDR support. The Goom visualiser is OpenGLES compatible and similar to Project M.

Delete the second half of the file. If it works, the issue is in the second half of the file. If it doesn't, the issue is in the first half. Keep following the same add/remove methodology until you find the problem entry in the list.

There is a prometheus agent add-on for LE users that want to monitor stats on their HTPC (everyone else prefers to just watch movies). If you are trying to develop an application; LE is the wrong codebase to work from as our distro packaging will be rather restrictive.