CGarces I don't have a task list to be done. Anything you think should be fixed you can work on and submit a PR either to my repo or to LE master.
I don't have issues enabled on Github as they were mostly useless and people were asking the same things on forum and on Github.
Was able to boot from USB and LE seemed to work. I then copied the appropriate dtb to boot partition and rebooted. Then SSH in and installtointernal. Now I am receiving ...automatic repair attempt continuingbad magic number in super=block
fsck failed. Your sysmte is broken beyond repair
reinstall LibreELEC
This means your box has a different partition layout and installtointernal needs to be run twice, second time after a reboot.
I noticed that the system makes a backup of device tree. But it's 8 times the size of the 212-2g one. What does this mean? Did it write the correct one?
A backup will always be 256kB in size because it will include the whole partition - if you view the file in hex editor you will see that it has lots of zeros at the end. So don't worry about the bigger size.
Gábor you can force RGB output by using echo 1 > /sys/class/amhdmitx/amhdmitx0/output_rgb in SSH. You can also add this command to autostart.sh. This command works fully only in 7.0.2.008 build and latest dev builds.
Most if not all S905 devices don't have a working RTC and will forget date and time and have to get it from a time server at every boot.
There was a devel from 25th, not available anymore, that broke my systemGlad I did a backup yesterday...
Please don't update to versions uploaded but not posted as they are not tested at all. Sorry for that. 
If you run LE from SD card, you can downgrade by replacing kernel.img and SYSTEM files with files from an older image. Your data will stay unaffected.
With latest devel from 24th the system is up again, but the volume buttons on top of remote (t95x) aren't working anymore!? They do now a page up & page down!?
You need to remap these buttons using keymap editor. The keycodes used in your box' remote.conf are indeed for Page Up/Down buttons and after many complaints I figured out that I shouldn't remap them as with most other remotes these are assigned to P+/- buttons.
There are 2 more buttons on the top (setup & apps) that aren't assigned to any function, correct?
Any extra buttons that you have on your remote that don't work have to be assigned manually using keymap editor.
You have to understand how it works: my builds grab remote.conf from Android that is installed in internal memory (either in runtime when you run from SD card or during installation for internal memory) and try to remap keycodes that I figured that can be remapped universally. Some remote controls have extra buttons that I don't know about and they have to be assigned manually.
If you don't want to play with keymap editor and are running LE from SD card, you can take the card out and use your computer to edit remote.conf that is present on SD card - that's the one copied from Android. Edit it and replace numbers in second column: 104 -> 115, 109 -> 114.
Updated to 1023 devl and ram usage was still increasing after watching videos and browsing after 2 days it had used 37% ram.Tring the new 1024 devl, just browsing my library a few times and the ram jumps to about 60% then slowly decreases. On fresh boot the ram is abot 16% after library browsing it now at 18% which is better than before which used about 7% just browsing
There is still a memory leak issue when using software decoding - related to EGL or FFMPEG, I still don't know. It's also present in Krypton and it will be worked on.
wkchick There is an explanation why internal tuner driver is not included in afl1's build. Also official LE builds with Kodi Krypton beta 4 haven't been released yet.
logicheart Please update to the latest development version (link in my post above) - simply drop that file into Update folder and reboot: HOW TO:Update LibreELEC - LibreELEC
There is one memory leak fix that might help you.
For any next bug report please generate log according to point 8 here: LibreELEC
This - apart from Kodi log - includes system logs that may include additional helpful information. Thanks.
Edit: I also prefer NFS over SMB. 
New development version (with focus on a/v sync): LibreELEC-S905.aarch64-7.0-devel-20161024175728-r23406-g57856b7.img.gz
mmpp Your sample doesn't play properly with that build, I guess it'll need some further tweaking...
I also can hear the clicks from time to time, mostly when using multichannel audio. I'm afraid it has something to do with buggy audio driver for I2S audio interface, not my area of expertise. I will see if there's anything I can tweak to make the clicks go away.
logicheart Your Kodi has full amount of Banned addons which we don't support here. Official:Forum rules - Official Kodi Wiki
When Kodi freeze/crash there is a lot of free memory, my test install is minimal : only one add-on (artetv from kodi repo), no lib and nothing else...
The same stream works perfectly on kodi+android.
I can use kodi on android it is not so bad on my NexBox but I prefer LE (at least on i86/64 until now).
I have found that using GUI in browsing add-on files and library files in the home network etc, causes available memory to get down to under 180mb available and then a freeze.
It is no big deal for me just an observation on when it happens.
Can you please test a new development build I've just uploaded? I have added a patch for EGL rendering that supposedly fixes some GL-related leak. I'm not able to reproduce it and I'd be greatful if you can tell me whether things are improved or not. This is the build: LibreELEC-S905.aarch64-7.0-devel-20161023234951-r23404-g0b27f28.img.gz (when upgrading from .008 you don't need to include a device tree in your update process)
This build also has the same approach to a/v sync as 2016-10-18 devel as this was so far the best one. VQ drops to ~0% but I don't notice any stuttering because of this.
for the remote mapping i recommend to use priority 1.remote.conf on root of boot partition 2. remote.conf internal nand, 3. remote.conf amlogic universal
The current priority is as follows:
1. remote.conf in Configfiles folder
2. remote.conf on root boot partition
3. remote.conf in SYSTEM partition (if present) - there is no "universal" one, unfortunately.
@kszaq....thought it polite to give you an update on my saga with my beelink min mxiii. Thanks to your help I managed to get it to work again using the (fresh install) 2.0.8 fix.img via sd card and then installtointernal........works a treat except the issue with the back button not working but fixed that with keymap editor. i then did exactly the same with my new A95X Nexbox 1gb/8gb and it again works great except for the back button issue but that is now sorted. I just wanted to ask if anyone else has noticed that the wifi with the original device tree on the A95X Nexbox is very very poor. Has anyone tried it with one of kszaq's device trees and if so does the wifi work well?
Thank you for an update. Back button has been fixed in development version, it will also be available in next "official" build. For your Nexbox you should try "Realtek" device tree - if you have S905 and not S905X inside. You should also test WiFi close to your router first. Some of the boxes have poor antennas - I'm not calling Nexbox here, I don't know how they are built. An example: in the same spot I'm getting 150Mb/s negotiated rate with my WeTek Hub (good external antenna), while a box with poor quality internal antenna is only 12Mb/s.
2ami .008 build includes a script that adds labels to partitions so as long as you update using recommended way (and not simply replacing files on SD card), the box will boot correctly.
All builds have a script to remap some buttons from Android to make them work and as I don't have all remotes possible, not all may be remapped correctly. I welcome all suggestions to improve the remapping script.
I suppose returning to 007 build is the best option for me at this time but I would like to confirm the best way to downgrade. Any help would be appreciated.
Simply put .007 in Update folder and reboot.
[hr]
Is there any chance that You would add support for rtl8723bs integrated bluetooth?
It is supported.
kszaq ...sorry for being a pain on this but when i do the dev build on SD card it works, I then do the internaltointernal and it reboots, but when it comes back on it has the error in the top left corner say 'do not press any key for the next 120 secs' and then it gives me some more text about 'your system is broken beyond repair' ...or I get the 'error tty job control'........do you think my box is goosed? happy to send you an image but need instructions as to how to upload on here?? Thanks
After you get this message, power off your box, plug it again and it will boot LE from SD card. Run installtointernal again and it it should boot from internal memory fine.
Most of the changes in the latest build are Kodi related. One of them took some work off the CPU and that's where you might see a performance gain from. Unfortunately most of Video Player tweaks we are using in Jarvis don't apply to Krypton and tweaking will have to be started over.
At this point I think there will be one more Jarvis build for both S805 and S905 - then Krypton starts.
I want to ask if it will be possible to add CEC and suspend features to the builds. I know that are in the changelog put they are not working.
CEC works, suspend is experimental.
Sorry, maybe I'm a real noob, but is it correct to put the device tree file in the update folder together with the latest build? This is my method, should I do something else? I also tried both gxbb_p200_1G_100M_RealtekWiFi.dtb and gxbb_p200_1G_100M.dtb. I'm running from SD card. Maybe I'm doing something wrong...
You need to rename the device tree to dtb.img after downloading.
are you advising that I pull the power cord after the initial reboot and then do the sd card toothpick boot again and then do installtointernal and let it reboot automatically?
Yes. Actually you don't need a toothpick to boot from SD card again.
Same here... latest dev build and strange results. Movie with DTS-HD MA 7.1 plays OK with an occasional (approx. 10 times per movie) stutter in sound, while playing a movie with regular DTS results in no sound at all and stuttering image. Furthermore, with passthrough disabled, loud popping sounds and stuttering image...
Have you read updating notes carefully and updated your device tree?
@kszag - please can you offer some guidance mate. I am having major issues with my Beelink Mini MXiii 2gb/1gb box. I was running 2.0.7 build from nand absolutely fine and then did the 2.0.8 update via 'update', but on reboot the box just locked up with the message 'your system is broken beyon repair'. After reflashing the stock ROM I was able to run LE in both 2.0.7 and 2.0.8 from SD, but as soon as i did 'installtointernal' the box locked up again. Can you advise if it is me doing something wrong or is the internal memory just shot? Happy to send you a photo but when I try and upload the image on here it asks for my url instead of the image file....how do I sort that???? Thanks
MiniMX III has a different partition layout than standard Amlogic. It doesn't matter when you run LE from SD card but if you want to install .008 to internal memory, you have to do a fresh install twice, e.g. boot from SD card, run installtointernal, reboot, boot again from SD card, run installtointernal again. After that your box should run LE from internal just fine. That procedure will not be necessary for future releases, i.e. you will be able to do a simple upgrade from .008 to .009.
