SSH in and run:
connmanctl
agent on
scan wifi
services
connect wpa_blah_blah_psk
Enter the password when prompted. If this works (using connman's own dbus agent) the issue is in LE settings code. If it barfs here, the issue is somewhere else.
SSH in and run:
connmanctl
agent on
scan wifi
services
connect wpa_blah_blah_psk
Enter the password when prompted. If this works (using connman's own dbus agent) the issue is in LE settings code. If it barfs here, the issue is somewhere else.
UTC time is set using NTP over the network. Display time is then offset from UTC according to whatever timezone you set in Kodi.
You already have SSH access. You have a console.
Time for a PSU with a higher current rating.
pastebin a Kodi debug log
"systemctl restart kodi" is much nicer than kill commands
Our long term technical direction will be to use the in-kernel framework and we are actively collaborating with Hans Verkuil who maintains that part of the Linux kernel. At the moment the kernel parts hook into the libCEC support within Kodi, but at some point code needs to be reworked to drop that dependency. I'm not directly involved or sure whether this will happen in v18 as GBM/DRM and V4L2 graphics support has a higher priority, but it's a firm item on our long-range to-do list.
Connect via Ethernet (temporarily) and run:
connmanctl
agent on
scan wifi
services
connect <name of service>
Copy/paste the password string when required.
WPS could technically be supported, but there is currently no support in our settings add-on for it, and that's unlikely to change.
"journalctl -b 0" <= current boot
"journalctl -b 1" <= previous boot
The journal has limited buffer though, so logs often rotate before anything useful is captured. Add "debug" to kernel boot params to make things more persistent.
Make sure you have an HDMI cable that supports 2.0 specs.
I am keen to see a public URL to the sources of this so-called LibreELEC image? .. or are Tanix just another cheap GPL violating manufacturer?
People in our forum have exorcised Android from their devices so won't be much use for detailed comparisons with a specific custom ROM image they are not using. Go experiment and make your own decision.
Or use the manual update function in the settings GUI (no need to use the console). The update mechanism works fine so there is some kind of local issue for your device or network (including ISP).
I'm confident there is a bug in the LE settings agent error handling code for a long time now, but as none of the staff appear to have hardware or USB dongles that exhibit the issue it remains unresolved. The LE settings add-on has its own dbus agent so the connmanctl console agent being off or on is irrelevant to the problem.
Current C2 releases are aarch64, future C2 releases and kszaq current release are 'arm' so the update process aborts. Instructions on how to override that are shown on-screen under the error/abort message.