One more question: do you have passthrough turned on or audio decoded to PCM?
It will be a bit hard for me to reproduce your issue since I do not have DVB TV access.
Edit: Can you try with this build: LibreELEC-S905.aarch64-7.0-devel-20160910230431-r23333-gacc409d.img.gz
locki Most of the times MAC address should be passed by uboot - check your command line by cat /proc/cmdline and you should see your address there. If not, try upgrading Android to latest version from manufacturer.
Can you tell if there were any drops in .006 version?
Do you have any idea about that? Does any default option changed in the last version?
2 audio-related changes from 006 to 007: audio output configuration has changed to enable multichannel PCM and I dropped one Kodi patch. I reverted the revert for a trial: can you test this version (download that file to Update folder and reboot): LibreELEC-S905.aarch64-7.0-devel-20160910193005-r23332-g19a3d56.img.gz
[hr]
I have kerber's libre elec installed on nand, will it work if I use the toothpick method to boot from sd? Or I absolutely need android on the nand for this?
You don't need Android on internal memory, except that you need to manually provide remote.conf: put it either in root folder of your SD card or copy it to Configuration folder after first boot.
kostaman Thank you for a complete report. Can you tell whether WiFi used to work on any pre-006 version - i.e. before kernel update?
Try a different HDMI cable. Some boxes have broken EDID/physical port detection and they will only work when connected to HDMI 1 directly to your TV (not via AVR).
S905X reportedly cannot play 4K H.264 @ 60fps.
kszaq I am not sure if this issue should be moved to a new thread or bug thread ?
Just asking as i am not sure doing that is correct or is it double posting ?
Thanks again.
You can create a new thread so that we can have all information on that bug in one place. Meanwhile can you try WiFi with gxbb_p201 device tree? I'm not sure if it'll boot and if it does, it will show only 1GB RAM. Don't worry about that, I only need to know if p201 device tree fixes WiFi issues so that I can port changes to other trees.
I can't find p201 dtb image in devices_tree.
Could you put it again please?
Re-uploaded.
so my known bugs are:
- Volumne up + back button not workin on mxq pro 4k. image is not usable with no volume up buttom
- suspend mode not workin. i know that is well known bug. but any plan to make it work properly ? the mxq pro 4k have no power on button andturn on with remote control dont work
To look at remote.conf I will need both your remote.conf from Android - if you're running from SD card you should find it on your SD card as LE copies it automatically - and some debugging info. Please create a new thread so that we can fight issues there - sometimes it's hard to find issues when threads get tens of pages long.
I am aware that suspend mode is not working - that's why it's a known issue. I would like to fix it but it's not that easy - otherwise it would have been solved long time ago.
Wrxtasy has this notice in his LE thread for Wetek Play 2: Interlaced DVD Rips (480/576i) will use high quality YADIFx2 Software deinterlacing. Is something similar possible in your builds, Kszaq? Mpeg2 files playback is not as good as the other formats. But that is my only con. Thank you for your hard work.
I know, best results are with no hw for mpeg2, but still not as smooth as the old OE 5.0.8.7 build from Alex on Minix X-8H Plus.
Like envagyok said, you need to disable HW acceleration of mpeg2 playback. My builds also use YADIF deinterlacing by default for software-decoded interlaced videos. Alex's build did not have YADIF deinterlacing - maybe you want BOB deinterlacing? This can be selected in playback menu.
kszaq thanks for the new dtb for both MXIII and MXQ. Updated MXIII using dd with no system corruption YAY, everything seems to work.On the MXQ installed from stock p201 firmware and it booted with the new MXQ dtb however LAN is not functional, wifi and remote including power off & reboot are functional. If you can fix the LAN i can finally give it to a family member.
EDIT: I also created a usb with gxbb_p200_1G_100M.dtb and that seem to have booted from usb but fails on nand install with the p201 firmware. Right now i have 007 with gxbb_p200_mxq_pro_4k.dtb on NAND with no LAN and gxbb_p200_1G_100M.dtb on usb with working LAN.
EDIT2: Booting LE from usb and running installtointernal using gxbb_p200_1G_100M.dtb = brick.
EDIT3: Booting LE from usb and running installtointernal using gxbb_p200_mxq_pro_4k.dtb = working, again no LAN
I forgot that this box has 100Mbit LAN and not 1Gbit... Device tree updated. Please re-download.
Only thing I notice is that I am seeing this message every few seconds in dmesg:
RTL871X: IsBtDisabled=0, IsBtControlLps=0Not sure what it means. Bluetooth seems to be working.
If it works, why do you worry? 
This is a driver debug message, source from Amlogic has debugging enabled by default. I will change this behaviour in the next build for your peace of mind (and less cluttered dmesg). 
I don't have a WeTek Play 2 (yet) so it's not supported in my builds. I think I can add it to a next one, unofficially.
I think you can try running one of my builds off an SD card without changing a device tree and it should work, but no promises on remote control and internal tuner will not work for sure.
For a working LE build have a look at WeTek forum: LibreELEC (WP2) - WeTek Community Forum
Not good. 
I guess I will have to gather some funds and get a S905X to debug on.
Sorry if i wasn't clear, i was able to boot LE using the p200_1GB_100M with p200 android firmware, but that is an old 2015 firmware which has issues with the remote.I was looking for a p201 dtb instead, the p201 android firmware has a working remote and is newer. The p201 in the device tree folder causes a brick.
LE is independent from Android you have installed, except for remote.conf it copies from Android. You can have p201 firmware and run LE with p200_mxq_pro_4k dtb from SD, p200 and p201 device tree differences are very minor.
Can you (S905X guys) test this build: LibreELEC-S905.aarch64-7.0-devel-20160909192321-r23330-g284fbb8.img.gz (diff included in folder)
This is 7.0.2.007 with console changed from tty0 to tty1. I am wondering if it can make an impact in any way. Thank you in advance for sharing your results.
You need to get ZIP file with Android firmware from your manufacturer/seller. I can't provide these files as they are different for every box. I will reword that point to make it more clear.
Is the new mxq dtb for p200 or p201?
p200_mxq_pro_4k
Hi kszaq,Yes - renamed to dtb.img and rebooted. The only thing I can find for the MX64 is the following .dtd file from another user on freaktab. I have no zip files for the MX64 but I do have the firmware on my device. However, I can't find the dtb.img file in Android.
Pls find attached the .dtd file for MX64:-
Please test an updated tree: gxbb_p200_2G_1Gbit_OTG_Port.dtb
@all I updated device trees directory, the only additional/changed device trees are for MiniMXIII (1st rev) and "MXQ Pro 4K". They both have a corrected system partition size to hopefully prevent filesystem errors when installed to NAND.
gxbb_p200_2G_1Gbit_OTG.dtb bricked my Beelink Mini MXIII internal install. Systemfile corruption error using dd command in OP for dtb upgrades AND install from stock Android. Flashed 007 using minimxiii dtb from 006 so back up and running.gxbb_p201.dtb also bricks the MXQ PRO 4K using p201 firmware.
I can now confirm that partition table for these boxes is different than standard Amlogic one. I think we can drop device-tree-defined partition table and let kernel read it directly from eMMC/u-boot (not sure which one is used). I will do some tests later today to see if we can make it work this way.
Edit: I will need to provide alternative partition tables in device trees.
Currently only build:LibreELEC-S905.aarch64-7.0-devel-20160826224219-r23299-g6fd2ccc.img
is booting every time on S905X device from SD card.
Do you need some logs from that build or something else that I may test to help narrow down what cause the problems on current build.
Last night I tested 007 build with dtb.img from android also without any dtb.iimg and with s905_autoscript from built that woks , but did not succeded to find combination that works for every boot.
If I remove dtb.img from SD card, successfully boot rate increases.
Thanks for all efforts for porting LibreELEC to S905X devices.
That build also did not have a proper framebuffer console support.
Tried the new dtb.img file but still same result - no activity from the micro-OTG port. All works fine when running from Android.
I assume that you renamed the file to dtb.img and rebooted, right? Can you provide me with device tree from Andoid in a dedicated thread?
Hi kszaq and others......please can someone help. Just tried to flash LE to nand on brand new Beelink Mini MXiii.....it has 2GB and 1Gbite Ethernet. I put the following files on a USB - aml_autoscript, factory_update_param.aml, a zip file with an update, and tried both gxbb_p200_1Gbit.dtb and gxbb_p200_2G_1Gbit_OTG.dtb as the dtb.img, obviously on different upload attempts. I have tried to upload going into android recovery via the toothpick method and then updateing from USB and whilst it goes through the motions of uploading and saying at the end of the process that 'Libreelec has successfully been installed'.....when i reboot it it just sticks on the Beelink splash screen and does not load as Libreelec. Please can someone help as I am going nuts with this.Many thanks.
Please try running from SD card first with different devie trees to find a one that works for you. Then you can use a recommended method to flash - please see OP.
Is it a case of just replacing the dtb.img file and rebooting or do I need to anything else?
Replace and reboot. That's it.
