kszaq Which images have been re-built. I see no difference (result wise, they are different sizes) in any re-downloaded from the update folder. I'll try the SD method
I have re-built entire 7.0.2.1 release. File names are the same. You can update using tar files, there is no need for a clean install.
Will do
Build complete, now uploading. 
On the downside, at least using the update method, these new builds cause my v2.0 box to adopt a new random MAC address each boot. I'll check if the full install makes any difference . . . same
Thank you for reporting. I am re-building 7.0.2.1 to fix this. Please check the download site in 2-3 hours and re-download.
New release:
7.0.2.1 7.0.2.1
Commits from 7.0.1.4 to 7.0.2.1: Comparing 7.0.1.4...7.0.2.1 · kszaq/LibreELEC.tv · GitHub
Kernel commits from 7.0.1.4 to 7.0.2.1: Comparing 543ae83...5df008c · kszaq/linux · GitHub
Changelog:
Known issues:
@dreischel The only time I saw this issue was on a S905 box when u-boot supplied wrong command line arguments to recovery. Have you tried flashing factory ROM via USB Burning Tool? Also remove aml_autoscript from SD card as it may corrupt the boot process somehow.
Have you tried performance? I doubt I'll try it as stability is more important.
I haven't, I'm happy with how interactive performs and and I don't like my box getting hot. If you don't modify trip points, performance should be safe to run although your box will throttle at some point for sure.
I thought the latest build used interactive according to the changelog: https://forum.libreelec.tv/thread-200-po...ml#pid3408
That's correct and my mistake. I was a bit confused about it. I am thinking that we may want to go back to ondemand for stability. I am not experiencing issues with interactive yet after discussing it with a few people I think we'll have ondemand as default for the next build.
Any update on the progress of your S905 build?
It's ready but not public. You can PM me for the details.
OK, thought it might need special permissions/chmod. Do you know if this is the correct syntax:Code( echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ) &
This should work.
And while I'm on the subject has anybody tried performance mode? Maybe there's reason not to use this as I read somewhere that the cpu frequency is cut whem temp goes over 70 degrees.
Performance will turn off frequency scaling and keep CPU at max available speed. CPU will throttle in accordance to trip points defined in device tree: LibreELEC.tv/meson8b_hd18q_dtd.patch at 7.0.1.4 · kszaq/LibreELEC.tv · GitHub
This translates to 1.5GHz up to 60°C, 1.4GHz up to 65°C and so on. If the temperature goes over 90°C the box will shut down immediately.
Where do I find 'autostart.sh' and if I need to create it where do I put it? Thinking of trying 'hotplug' or 'ondemand' as my box often sticks for a few seconds or more!
You can read about autostart.sh here (it's the same in LE): Autostart.sh - OpenELEC
In the most recent builds ondemand is the default CPU governor and I recommend trying hotplug only if you experience system freezes, not hiccups.
I tried what you had and it made no difference. I have tried my stock remote.conf on several different builds lf LE and another for OE, been looking for the LCD information with no luck, i have talked to the manufacture and they are sayings its a standard 7 segment digital screen. Last two things to try and figure out, seem easy but have not been lol
For the remote control, you may want to see if there's any other *.conf file in Android firmware. The one you posted in other thread looks incomplete.
what about dificult solution? maybe i can fix this by myself ?
This is what my script is doing and you can execute this over SSH:
sed -i 's/ 97/ 28/
s/ 102/ 172/
s/ 125/ 46/
s/ 142/ 116/
s/ 143/ 116/
s/ 158/ 1/
s/ 183/ 398/
s/ 184/ 399/
s/ 185/ 400/
s/ 186/ 401/
s/ 232/ 38/
s/ 240/ 164/
s/ 241/ 128/
s/ 242/ 163/
s/ 243/ 165/
s/ 244/ 208/
s/ 245/ 168/
s/ 264/ 63/
s/ 704/ 116/' /storage/.config/remote.conf
Remember to reboot afterwards.
the only problem that i have is that OK button is not working,is there any solutions for this ?
Easiest solution: wait for the next build - this week I think - which will remap the button automatically.
Thanks kszaq for the reminder in your pm. Unless YOU tell me there are benefits in the s905 that will wow me, I'll be sticking with beelink S805.
The advantages of S905 over S805 are:
Additionaly, with WeTek Hub you get full DRM support in Android, i.e. Netflix, Amazon Prime Video in full resolution.
If you don't need any of those, S805 is completely fine.
1. Each box will usually lockup a 3 or 4 times a week on me. I have to unplugg it and then press the power button to power it back on. I'm not sure if this is only happening with MXV or if it also happening with the MXQ with red stripe as well. Im guessing it probably just the MXV since its not really supported by you. I haven't grabbed a error log file from it afterwards but I will the next time it happens. Can I post it or send the log to you when it does?
A few things you can try doing to resolve this:
2. The remote arrow keys have a tendency to stop responding whenever you double click the up or down arrow key very quickly. I'm not sure if this is just becuase of the double click or a physical flaw the remote design itself and it acuatlly hits the mouse pointer button because of the board is bowing inside the remote case. However it may be a combination of both or could it be the remote config file causing the problem. The workaround for whenever the remote arrow keys stop responding is to just press the mouse pointer button once and the arrow keys will start working again. Does anyone else have this same issue with the MXV remote?
You can disable switching to "mouse pointer" mode by commenting line with fn_key_scancode in remote.conf - simply put # in front of the line.
3. The home button doesn't work. I tried using the Keymap editor addon to fix this issue but it will not fix the problem. So I am wondering if I can manually edit the remot.config file to fix this issue? If so do you have a link on configuring and editing the remote config files? Or does someone already have a remote config file for the MXV that has the Home button working?
To resolve this you should replace keycode for Menu button in your remote.conf (look at kmsg to tell which one) or wait for a next build where I'll include a script that remaps remote buttons in custom remote.conf. 
4. I can not reboot the MXV from the homescreen but I can shutdown the MXV from the homescreen. Before I upgraded to Librelec I believe you had gotten it to not only shutdown but to also reboot. You of course fixed the usb male to male cable in port 1 and 4 issue..... Which was Awesome BTW!
Reboot works just like before (i.e. in OE builds), it must be something else that changed. For now you can work this around by choosing "Power off" and powering the box back on.
ok but where exactly is the "Configuration folder?"
/storage/.config over SSH or \\[i]your_box_IP[/i]\Configuration using Windows shares.
So is the Hub out for sale? I can't see it anywhere in the UK and with the state of the pound after Brexit I doubt I'll be buying it from America!
You can preorder it from WeTek Website.
How can I put these 2 lines into my autostart.sh? What should the syntax be?
You can simply add these 2 without anything extra around - these are simple commands that don't start any process that would need to be put to the background.
kszaq - Thanks for your hard work, I have Libreelec 7 running on a MXV but I still have to have the USB cable going from port 1 to 4 or else the box powers down. I think its because I originally flashed an MXQ image (I get an MXQ logo when booting up) which contained bootloader and recovery. Do you know how I would go about fixing this? should I re-flash an Android image with the burning tool, then flash libreelec?Thanks.
Please try doing that. Use MXQ build as this one is reported to work on MXV. I don't have MXV box and can't help much.
Thanks for taking the time to enlighten me on this. Do you know if the same problem exists with the S905 boards?
No idea, actually. I have only 2 S905 boxes and they don't have such an issue. There are so many S905 boxes on the market right now that I can't say for every single one. I think we will have reports when my builds go public. All things considered, I will always advise against buying cheap S905 boxes and get a quality one instead (WeTek Hub).
@kszaq Why is it that the Android builds of the v3_1 boxes can wake using the power button, but the LE builds cannot?
I know that you have mentioned it is a u-boot.bin bug, so are the Android builds not using u-boot.bin? or is it really complex and not easily explained to the layman?
Android on V3_1 boards do not turn off the box, it only turns off the screen. It's a bit similar to what smartphones do: they keep working when you press the power button. When you press the power button again, screen is turned back on.
My LibreELEC builds use a proper way to sleep - "deep sleep" or "u-boot sleep". In that mode kernel puts system components to sleep and tells u-boot to suspend. From that point only u-boot is able to bring the box back to life. This is a standard feature of Amlogic u-boot which has been somehow turned off or not compiled in by V3_1/V3_2 boards manufacturer. I cannot change that behaviour without having their u-boot source code as u-boot compiled from Amlogic source does not boot.
To make "V3_1 Android way" work on these boards I would have to do 2 things: enable WAKELOCK in kernel config and write code to make Kodi aware of "suspend" with wakelock. Unfortunately enabling WAKELOCK breaks kernel for some other boards so this is a no-go.
I have sent multiple requests to the board manufacturer to either share u-boot source code or compile it to be able to wake from u-boot and all I got in response is silence.
dataghost There is no key definition in your remote.conf. Is this the whole file?
Kszaq can you make a "ludicrous" build where you remove the thermal profiles and go full 1.5Ghz without throttle? I want to test something...I have an extra stick that I put some heatsinks on and I want to run some load tests on it ...stess it for a few days ect.
You can try this (at your own risk!):
echo disabled > /sys/devices/virtual/thermal/thermal_zone0/mode
echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Ahh, did I hear S905 build happening ?I have the mini-MX
PM me for details.
Hey people,i have MXQ S805 Android tv box,and i would like to boot LibreELEC from a SD card,i've followed the instructions,flashed my 4gb sd card with LibreELEC and all that kind of stuff.. the problem is that device is not booting from the sd card..i've tried different versions of LibreELEC but the problem is still the same...I'm using toothpick and turning device ON at the same time and all i get is Amlogic S805 logo and that's all,no actions anymore.also i've tried to wait for about 15 minutes and still the same thing )
Have you tried the m201d build?
Sleep/wake up unther Android 4.4 works fine. Ping me if you need something from the stock ROM
I need u-boot source code so that it can be compiled correctly. 
A note to everyone: Please don't post links to eBay/e-shops. Let's not advertise and discuss the builds instead.
But now I have to think what to do with it..
I don't think I can wake the stick up once it turned off?
I think I will make this button suspend the box, that is work like "Power" key. I don't think you will be able to wake it with the remote as that a task for u-boot - something out of my control.
I have good news to report: The NEXBOX A85 boots the HD18Q 7.0.1.4 build. internal board MXQ_S805 V3_2 build date 20160229. You must put remote.conf from m201d build via SAMBA to ConfigFiles folder to use remote. These are the cheapest boxes I have found on Amazon at around $25 and run the build great.
What is the build date for Android firmware? Can you wake the box with IR remote after you put it to sleep in LE?
I tried with remote.conf but didn't work...
Isn't remote.conf just for IR-codes?
my "remote" is a wireless keyboard/mouse
I missed the part when you pointed out that this is a USB remote... yes, I can add that keycode to Kodi for the next release.
It's possible to pass this command when system start : hdmi force edid audio=1
This allow passthrough of DTS/AC3 even when not reported as supported.
There is no such parameter for Amlogic and there is no need to set it - simply enable passthrough in Kodi settings.