This changes nothing. Only starting/stopping a vid gets it to correct after any reboot.
Calm down glitch, rel-a-a-ax.
I can't give you the definite answer you're looking for but, if starting/stopping a video corrects it after reboot, have you tried enabling the kodi start-up animation to give you a start/stop of a video after every reboot?
However, on booting the sdcard it is unable to mount LABEL=DISK (unlike kszaq's builds).
I believe the partition labels should be LIBREELEC (boot) & LIBREELEC_DISK (storage) 
(Or, perhaps it hasn't changed for the 7.0.3.x builds :s )
I also did a quick test with beta 3 on my MiniMXIII II. Audio bluetooth works!
Thank you very much for your effort!
Ditto!
kszaq, with the temp-sensor-disabled builds there does seem to be a bug (maybe not a bug, but different to the normal build) when using the kodi start-up animation, whereby a 'ghost image' of the last frame of the animation is displayed momentarily before the animation starts. I have not seen this issue with the normal build, is there some cache that is not being cleared in the crippled builds?
nvm: I've now seen it on the normal builds as well. (Maybe more to do with the animation itself)
I think there is Typo in the add 2 files ?
I believe the instructions regarding file names are eg: MiniMxs905_uboot_mini_mx.zip
aml_autoscript
No, doesn't matter which zip is used, 2 errors - footer is wrong and fails signature verification.
If I re-sign the zip files, the two errors disappear but the Installation still aborts.
Merziyas Which box did you have success with this on?
Is there another file that is supposed to be on the SD card, along with aml_autoscript & aml_autoscript.zip?
Temp Sensor Disabled is for the S905 Chip boxes that freeze on bootup.
You have a S905x so no need to use that version.
S905X is also affected #102, so not quite as 'black and white' as that
Just install the normal build and if you get any issues with boot freezes, then try the temp-sensor-disabled version
How to apply uboot (dual boot) : Add the 2 files (aml_autoscript.zip and aml_autoscript) in a FAT formatted USB or SD card (max partition space 2GB). Then use the Update&Backup app in android, select the "aml_autoscript.zip" file and click on update. Your device will boot to recovery and apply the uboot script.
Sounded interesting - but doesn't work at all with MiniMX (footer error and signature error).
There's no actual new uboot file, so what is aml_autoscript actually doing? (On the boxes it does work with)
I'm running a LE from microSD, mostly works superb in Mini M8S II. I'm going to install to NAND soon.
Is it possible to run LE from microSD again in the future, for testing purposes, if LE already installed to NAND? Is three such thing as which booting is priority in this case if there is both LE on microSD and NAND?
The external version will boot if it is detected on SD / USB
Meanwhile you can temporarily fix it by running systemctl stop eventlircd.
Good on ya Champ! Man, you're good! 
'HOME' and 'INFO' key using Android Yatse App are working with the Krypton beta build
The Home button is detected with builds 7.0.x.x and LibreELEC-S905.arm-8.0-7.90.beta1 but is actioned as previous menu, but with LibreELEC-S905.arm-8.0-devel-20161223194610-r25062-g308adcf build, although the log shows OnKey: home (0xf088) pressed, action is FirstPage nothing happens 
The Yatse App does not send IR codes, so I'm not sure that it's relevant that the App can send these commands.
EDIT: 'STOP' button not working either
[Moved from 7.0.3.012c build for S905/S905X]
kszaq
I am now testing the 7.90beta1 build. I seem to have lost some functionality with my remote (a few keys which have been working fine, are no longer acknowledged by kodi). Any ideas why?
The 7.90b1 build is not dealing with key presses the same as the previous builds.
In the new build, LIRC seems to be detecting the key presses but kodi no longer actions the event whereas, in the earlier builds, there is no LIRC entries in the logs
Three logs attached 7.0.3.012, Krypton dev and 7.90b1
In each build, using the same remote.conf in /storage/.config and gen.xml in /storage/.kodi/userdata/keymaps, I was repeatedly pressing the 'info' key on my remote, which is mapped to the i key /key ID 61513
No LIRC for generic S905 builds yet.
That's a shame, as it looks like there is a big LIRC presence in the 7.90b1 build, which seems to be causing, once functional, keys mapped in remote.conf to be ignored. Any suggestion for a workaround?
(This is a pretty old thread, maybe there is LIRC support now)
Where can I find a dummy.zip?
Create a new file, (dummy.txt for example). No need to write anything to it, just rename it 'dummy.zip', and copy it to your SD/USB - done!
You can call it anything you want.zip, I just use dummy zip to save confusion since update.zip is a commonly used, valid source file
. . .video crashes the wetek hub. . .
Please excuse my ignorance, but I thought Wetek had it's own forum? Oh, maybe that's for Android FW.
kszaq
I am now testing the 7.90beta1 build. I seem to have lost some functionality with my remote (a few keys which have been working fine, are no longer acknowledged by kodi). Any ideas why?
gbate Don't forget to let us know if you've got this sorted
There seems to be a lot of MXQ Pro's showing up with more different issues than any other box.
The whole boot freeze issue is not, completely, resolved. It's not only MXQ Pro's that still have issues, I have a MiniMX that occasionally stalls at boot using the disabled build while, on the other hand, I have another MiniMX (same specs) that rarely freezes using the normal build.
Disabling the Temp sensor has dramatically improved the issue, but not resolved it.
[hr]Thanks for the reply. I've seen one of the LE boxes on a 4k tv, and it seems a bit tricky to be able to view/access the kodi>>settings>>system menu
You can navigate to Video Calibration 'blind'.
What LE version and skin is being used?
eg. with 7.90.Beta1 using default skin, Estuary, go up, right, OK, right, right, right, down, OK, right, up, up, OK and you will be in the Calibration screen and able to adjust the overscan
