Posts by chewitt

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.

Kodi filemanager cannot see hidden folders (with a . prefix) unless you enable "hidden files and folders" in Kodi options. Even if you do enable them there isn't much you'll be able to do from filemanager itself so best to learn how to SSH into the box and edit that way.

Re-reading the original screenshot: You ran emmctool without actually having the AMLGX file to write on the /storage partition so it's errored and written no data to the device. Hence boot has still worked. If the box boots; that's where advice stops because I have no interest in wading into the shitfest of atetmpting support for internal installs on hardware I don't have. I've deleted the GT1 image from my test share.

In LE11 Kodi settings can set defaults for subtitle preferences (language choice etc.). Now bring up video settings during playback and enable subtitles and 'set as default' for media.

Quote from WarpLover

CEC?

Probably. You can turn it off in Kodi settings.

I deleted the other random post that bumped a thread from 2019. Install the System-Tools add-on and you have 7-zip as an alternative to normal zip.

And you have a low-spec ARM board with an older Mali 450 GPU. It uses exactly the same mesa/lima graphics as LE10 so I would not expect any significant change to GUI behaviour. IMHO scrolling and navigation performance is more dependent on the remote device being used than anything else.

VNC is VNC .. and works with the legacy Pi codebase in LE 9.2.8. However VNC stopped working on RPi and all platforms using V4L2/GBM from LE10 onwards. It's an inherent problem with how zero-copy graphics pipelines work and a "fix" will be non-trivial to engineer; and we're not aware of anyone working on something.