will try the second devel release.
EDIT
Bluetooth still not working, however RAM is better. With 006 after a few minutes i was able to use up about 49%, with the second devel I'm currently at 34% which is much better. I'm trying to keep my test conistant as possible. So w/e changes you made you are for sure on the right track.
if we want to go back to official 006 after these test builds do we just put the zip/tar in the upgrade folder?
The fix is included in this build so it looks like the reason is elsewhere.
This is the only flaw I can see with getting these cheap boxes. Any idea what the cause is? Seems like its kernel since people have been reporting this on Android as well. Which i guess AML does not want to fix.
Since i opened my box i checked what chips where on it.
RTL872JBS
RTL8212F or RTL8211F really hard to read.
Can't help you since I don't have a s905x box.
Sadly RAM still fills up quickly after using addons and browsing the library. Video playback is actually much better on this build, skipping chapters works now.
Will keep my cron job active to reboot the box
Delete the dtb.img file from the sdcard, that what it says for s905x boxes in OP
It looks like there isn't one listed yet.
LibreELEC
nah its there Kszaq must have missed it or still working on it.
Bluetooth still not working on build 006
##############################################
# LibreELEC #
# http://libreelec.tv #
##############################################
LibreELEC (community) Version: 7.0.2.006
LibreELEC:~ # /usr/bin/rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5 &
LibreELEC:~ # Realtek Bluetooth init uart with init speed:115200, final_speed:115200, type:HCI UART H5
Realtek Bluetooth :Realtek hciattach version 2.5
Realtek Bluetooth :3-wire sync pattern resend : 1, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 2, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 3, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 4, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 5, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 6, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 7, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 8, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 9, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 10, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 11, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 12, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 13, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 14, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 15, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 16, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 17, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 18, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 19, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 20, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 21, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 22, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 23, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 24, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 25, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 26, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 27, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 28, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 29, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 30, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 31, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 32, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 33, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 34, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 35, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 36, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 37, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 38, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 39, len: 8
Realtek Bluetooth :3-wire sync pattern resend : 40, len: 8
Realtek Bluetooth ERROR: H5 sync timed outfew things i noticed on minimxiii
internal bluetooth still not working
in system info cpu temp is no longer displayed.
cant boot into recovery even with recovery.img and dtb.img on sd card using 'reboot recovery' over ssh
Any ram management improvements with the new kernel?
EDIT:
Turns out recovery does work on the Mini MXIII using toothpick. I cracked it open to see if it had a functional button and it does, its just the hole was tiny and a wooden toothpick was to big to reach the button. I took a small phlips screw driver and made the hole larger and can now reboot into recovery with the two files on SD.
Thanks Kszaq
perfect upgraded my Beelink Mini MXIII NAND without issue. As expected recovery no longer works, will we need to update future NAND builds the same way or just a one time thing?
great, normally dont watch anime or 10bit on kodi but great to know one less bug to worry about.
Works great on 006
is this the case for both 720p/1080p h.264? What about 10bit h.265? since 10bit HVEC plays fine.
hes not finished, the build is ready but updating instructions are different because of device trees. So just wait he will update eveything on the s905 image thread.
[hr]
Hi there,it seems my box is resetting date/time to 01.01.1970 01:00 am on every cold boot and after some time (betweet 30 secs and a minute) it gets the correct date/time when it has an established network connection. This also happens on Android. Problem with this is that Kodi tries to connect to my Mysql-Server with that incorrect time/date and cannot get through, and so i have no database on Kodi startup. I'll have to wait until the correct time/date are displayed in Kodi and then do a warm reboot to get my Mysql-connection working.
Is there anything i could add to autostart.sh to set/read the correct time/date before Kodi reads my advancedsettings.xml ? Or a pause setting? I want to make sure my wife can use Kodi without rebooting several times
(Wait for network setting doesn't do the trick as the network is available right from the start, it must be the time/date setting and i can reproduce that problem)
i had this issue, just enable 'Wait for network before starting Kodi". This can be found under Network in the libreelec settings, this is different from Kodi network settings. I set my max wait time to 120 seconds which is the amount of seconds my network needs to come online after a power outage. This has no effect on boot time if my network is already online, Kodi still boots within 30 seconds.
I plan to release the build this week.
Here my week is over tomorrow :D, Cant wait to see all the improvements.
Thank you for finding this! I will add the patch for the next build, backporting should be trivial.A new build is almost ready, I only need to prepare device trees for your devices as the new kernel needs some changes and we can't use device tree from internal memory.
I can also see that Amlogic uploaded new sources to their Openlinux site, I will see if we can use the latest drivers. [emoji56]
If you ever need a tester 
Gpu memory fix from popcornmix, which might help with the memory leak. Trying to find his github changes.
Wrxtasy added the patch to his c2 LE7 port.
How is this relevant to the topic? Create a new thread and if you can post logs.
Here what i did after adding the remote.conf of a different remote.
Install keymap editor addon, launch the addon and start assiging kodi commands to each button. It does not matter what you add as long as you know the kodi command, i just used the navigation buttons and pressed keys from in order. I know i could have just used the addon to configure but i wanted to used my old keyboard.xml file.
It will create a new xml file in the keymap folder which you can then open to get the button ID and assign it to whatever kodi command you want.
