If those servers you are connecting to, are crap, I guess there´s nothing we can do
It is not server - it is addon or kodi. My opinion is that Krypton just sucks in this regards. That's why I stayed with Jarvis where channel switching is much, much faster. At least for me.
Have you any idea, why?
Maybe because it is Progressive type? Try different options to encode. But I'm afraid there is nothing to fix (imx6 player just doesn't like something).
If reason would be known then issue would be resolved 
It is some thing with kernel (hw is fine).
The reason for using 4.4 version was for docker requirements which was interesting thing for some users. Maybe it was mistake to switch but now it is what it is. And I will build images with 3.14 kernel in the future too.
Do you know of anyone else with a cubox-i4pro 2gb that got kernel 4.4 working?
It works for most users including me. Others has black screen (which is the main problem).
thefoofighter, I don't know which image exactly did you use but official images are using Linux kernel 4.4. But I also provide with 3.14 which works better for some users.
Looks like it's working ok with imx6-solidrun-kernel-3.14.
On the other hand CEC isn't working good with this kernel.
I think it depends on a TV in use. For most users it is working fine.
Seems kodi krypton has issues with some video files which worked in jarvis. Nothing much can be done.
here it is.
Thanks. I can reproduce the issue but don't know how to solve it (seems kodi issue and not only libreelec is affected).
WhyTea, upload a sample somewhere.
AndrewZ, let me check BT with a speaker I requested back from a friend. BT keyboard I don't have.
In Windows I think 7-zip can open .img.gz file and show the files.
Just to inform, updated to 8.0.1, no cec connection, ...
I blame your TV.
In ssh console try to stop kodi and then check what cec-client do:
systemctl stop kodi
cec-clientimx6q-cubox-i.dtb: means old revision of cubox-i. BT should work fine with it. What exactly is the problem?
You could also use kodi's build-in touchscreen calibration functionality if you had so much problems with mine addon. And yes, now that there is available I don't build it anymore.
daniel, remote should been fixed in v8.0.1. It is working for me and others.
Kodi repository problem: maybe related to this? 
How can I check the revision? Can I see it on a running system or I need to catch it during the boot?
I have problems with pairing my BT keyboard, last time it was working on some OpenELEC version
Probably you need to open the device and see chips 
But if you see this Loaded imx6q-cubox-i-som-v15.dtb from u-boot then you have revision 1.5. And it is very newer (only few months). But seems there are some bugs in u-boot identifying correct one. Can you type u-boot commands I posted above?
Here's the list of test cases on a Cubox-i4 Pro rev 1.2:
Can you stop u-boot and type this commands (one line at a time) in it's prompt and post the result? Seems strange that your box needs som-v15 dtb.
gpio input 105
gpio input 68
gpio input 40
gpio input 160
gpio input 164This is what I got
CuBox-i U-Boot > gpio input 105
gpio: pin 105 (gpio 105) value is 0
CuBox-i U-Boot > gpio input 68
gpio: pin 68 (gpio 68) value is 1
CuBox-i U-Boot > gpio input 40
gpio: pin 40 (gpio 40) value is 1
CuBox-i U-Boot > gpio input 160
gpio: pin 160 (gpio 160) value is 0
CuBox-i U-Boot > gpio input 164
gpio: pin 164 (gpio 164) value is 0Maybe nvme support is missing here?