I'm got a Harmony Ultimate (Working on Cubox-i and RPi) and the only profile I have got to work with "most" commands is
Microsoft : Media Center SE with rc6 and I've tried most of them as well as BT without much success.
I didn't disable CEC so not to sure if you need to.
Worth reading Wiki if you still have problems.
On my Harmony One, used on a Cubox-i, I use "Microsoft : Media Server SE" which has most of the keys working. This of course is assumed that the Neo uses rc6 protocol for the IR.
If you need to test, see Wiki
Looking around, this seems to work on Ubuntu 16.04 - not too sure if possible on LE. From Here
A year isn't too long to wait on the Linux route. It always takes a while for the drivers to become available (and working). Even Ubuntu 18.04 is "just" a possibility for coffee lake. So 2019 isn't that far away.
I was going down the i3-8100 or J4105 route also, so I can understand the frustration.
At least the website wasn't seized by ICE - Homeland Security Investigations as in 2017!
I got one of these and it worked out of the box on my RPi3. However, the antenna is a bit small unless you are close to the transmitter, or willing to modify it to connect to a proper external antenna.
Neptune Rising and Exodus are banned addons. See Here
Under LE's (In line with Kodi's) policy on piracy - no further support is offered until all banned addons are removed.
I have a similar setup to you albeit a RPi3 and LE 8.2.3 with DVB-T via Xbox TV Tuner and I haven't had any issues with locking. I do however have Kodi shutdown and HDMI + LEDs turned off (If that makes any difference).
If you don't really need Kodi running (Not needed for TVH) then shut it down - it may solve your issue.
Also I reduced GPU memory to 112 and used nmon (In the LE system repository) to monitor my box periodically, which leaves around 600M free.
There is also a Raspbian GPIO switch shutdown available (Which I have tested in Raspbian Stretch - and works well) but haven't tested on LE which might allow a clean shutdown/Reboot if you need it.
There is also the Raspbian watchdog service that does work under Raspbian, but I believe this has caused issues with LE and is no longer implemented because of problems.
I use a Logitech F710 which is similar to an XBOX360 controller.
Firstly you will also need a keyboard to SET the controller.
In the Input-> Controller menu select "Kodi" from the left hand side with the keyboard. Then when the countdown timer starts on the "A" button, select that button on the controller. If all goes well it will move to "B", "X", "Y" etc. If one of the buttons fails, just select it again with the keyboard and try again.
If nothing happens, check cat .kodi/temp/kodi.log for something like inpiut/jr0 not found. If that is the case restart Kodi with systemctl restart kodi.
Also I have found that if a button is not pressed on the controller during boot, LE will fail to recognise the controller, so if rebooting hit a button a number of times.
All you questions are probably answered in the Wiki
Partial fix is to push a button or two whilst LE is booting.
Duplicate of Thread
The easiest way is to use a disk manager like gparted to expand the partition to fill the unused space.
Otherwise you can follow this Thread
I have a Logitech F710 game pad that used to work, flawlessly, on 8.1.xx systems but has started causing issues on boot/reboot. This is only on IMX6 as I have tested on RPi2 without issue.
The F710 is a “clone” of the XBOX controller and works with the standard Kodi controller configuration.
The Logitech Keyboard K400 works without issue which uses a similar USB transmitter.
On boot or reboot Game Pad fails to work
dmesg
After Kodi restart
“systemctl restart kodi” the Game Pad works
I’ve tried redoing the controller configuration without success. Ditto swapping cables, position of the transmitter etc. I’m using 2 USB hubs so putting the USB transmitter directly into the Cubox-i USB port is not really an option.
Any ideas?
Use
~/.config/samba.confIf it doesn't exist, copy samba.config.sample as a template.
Please read Thread
I'm assuming "Radio" by Tristan Fischer as there are many other"radio" addons.
I've tested on a RPi2 and yes there is a burst of cpu activity at first start, but this settles down once the buffer has filled. Leaving it on the selection screen increases the cpu to > 50%. <Tab> brings this down to 25%.
Are you using a visualization and if so which one?
Shadertoy didn't cause any unwanted increases in usage..
However, my temperature doesn't go above 55 degrees, so there is something else wrong with your machine or setup.
Use "top" to see what is causing the high cpu usage and try disabling spotify/tvheadend and other addons, to see if they reduce the CPU.
Is the watchdog service enabled? I've tried it on raspbian and it worked fine.
I can see on my RPi3
Libreelec:~ # ps -ef|grep watchdog
11 root 0:03 [watchdog/0]
14 root 0:02 [watchdog/1]
20 root 0:02 [watchdog/2]
26 root 0:02 [watchdog/3]
39 root 0:00 [watchdogd]
31253 root 0:00 grep watchdog
So something is running, and they have a priority of RT.They can also not be killed with kill -9 39
However, trying the normal fork bomb :(){ :|:& };: fails with -sh: syntax error: bad function name.
Whereas
bomb() { bomb | bomb &
}; bomb
Works, but the system just stalls and nothing happens - even though ping still works.
I tried adding
dtparam=watchdog=onTo config.txt but without any success.
So it seems that something is almost there but not actually working.
As @Klojum mentioned it caused problems but with the addition of the dtparm option users could enable/disable the watchdog if they feel the need