Posts by gujal

Quote from Demetris

If you guys are interested i have released new images with updated wifi driver and bluetooth.
If you are brave enough please test and report if issues are gone now.
Link:
not found | AndroidFileHost.com | Download GApps, PA GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers

Tested the S82 build on MX-III 2GB
Both wifi and bluetooth are not working on this build. So I am back to the 29Mar build where wifi works.
Thanks for all the time you are putting on this build
[hr]

Quote from Coto

Hello Gujal,
Can you share with us what you did with the remote control problem after the new release of Demetris and than for the MX III? I have no idee where I can find the remote config.
Where do I create the new folder nocompat? Is that in the update folder or do I create a new folder? Problem now is that everyting is working fine. So the line for me is don't fix it if it aint broken.
tnx

".nocompat" is a file, not a folder. It should be in the same folder as the tar file
The remote.conf is to be taken from your box when it was running Android. You need a root explorer app for this to access the "/etc" directory where you will see this file. You need to copy it from there to an USB drive
Once LE is up, This file needs to be copied in to the Configfiles share

S8X2 build is still not perfect, so for now I am sticking to the S802 build. The only issue I have with that build is getting bluetooth to work. Otherwise, it is a good and stable build thanks to Demetris.

Quote from Coto

Latest version is not compatible with Tronsmart MXIII. After installing I got the messages SX82 not compatible with S802.

It is compatible, looks like you are trying to upgrade from a previously installed Libreelec version. Demetris advised a clean start from Android without any LE version already running.
PS: If you want to upgrade from existing LE, You can always do it by putting a empty file named '.nocompat' along with the tar file in the upgrade directory and it will work. I got it working on my MX-III that way but Bluetooth is not working

Quote from Demetris

Start fresh with android I have merged s802 with s812 and now they are called S8X2

Sent from the Island of Venus

Hi Demetris

I put back the Android OS on my MX-III 2GB and is back to factory defaults and working normally.

Then I downloaded
LibreELEC-S8X2.arm-8.0.1-S82.img.gz and used Etcher to put the image on 8GB microSD

SD content after preparation:
Volume Label : LIBREELEC
Files:
aml_autoscript
kernel
kernel.img.md5
system
system.md5
.LOST.DIR (folder)

Boot from SD is working but it stops as soon as it puts the LibreElec splash screen and shows:

Quote

cp: can´t stat ´/flash/SYSTEM´: No such file or directory
*** Error in prepare_sysroot: mount_common: Could not mount /dev/SYSTEM ***
### Starting debugging shell... type exit to quit ###
sh: can´t access tty: job control turned off
#_

What am I doing wrong. Please advise.

I also tried burning the image using Etcher onto a USB drive and boot. The device has 2 regular USB ports and one Micro USB port. I tried the USB drive on all three ports, go into recovery and reboot, but never boots into LE and always ends up on Android

My box is MXIII S802 Amlogic 2GB RAM/8GB Storage Mali 450.

Quote from Demetris

I found the cause of Bluetooth issue and
Now all is needed is testing. Will release new images soon

Woohoo. Fantastic Bro, that was quick. Thanks for all the support

Quote from Demetris

New images are up, enjoy.

Can now confirm it is back to 8.0.1a behaviour on the MXIII 2GB.
i.e., Remote works fine after copying Beelink S82 remote.conf file. Bluetooth not working (same as 8.0.1a)

The ageing MXIII 2GB is now useable with the Latest Kodi release, Thanks to you!

Thanks, remote is priority so please do that. Bluetooth can wait, it is just nice to have.

Demetris

I am using the S82 build on my MXIII 2GB.
The 8.0.1a build was usable with remote after copying over the remote.conf file. The Bluetooth adapter was not working.
Now with the final 8.0.1 S82 build, the remote does not work even after copying the remote.conf file and the Bluetooth is still not working.

As mentioned before, both Bluetooth and remote were working flawlessly without any additional work to be done on your 7.0.3 S82 build.
Can you please advise what needs to be done to get the two going again.

Quote from RunRunBangBang

I tried to use the 8.0.1 on a MXIII 2G but the image isn't showing in the boot menu so I can install it. Can someone help?

If you are already having 8.0RC4 running, then all you have to do is to copy the 8.0.1a tar file to update directory and reboot

Quote from cbms

I have an MXIII-2G and I recently upgraded to LibreELEC-S802.S82.arm-8.0.RC4.zip through an sdcard. It appears to be frozen on the "KODI" start-up screen. I'm new to this and need help if anyone has experienced this same issue.

Yes, this happened to me too when I went from 7.0.3 to 8.0.1a. Seems to be a generic problem of upgrading from Jarvis to Krypton as it happened to me in windows too when I went from 16.1 to 17.1RC
This can be fixed if you had enabled ssh
1. SSH to the MXIII (use putty, securecrt, or whatever you fancy)
2. run the command without the quotes "mv .kodi .kodi16" (there is a . before kodi and kodi16)

As soon as you run the command you should see Kodi startup correctly and go to the main Estuary welcome screen. If not run a "reboot" command in the ssh window.

You will have to reinstall your addons

Quote from Demetris

That's it thanks

Sent from the Island of Venus

So should I be putting some config file or something to get Bluetooth working. Please advise

Apart from the Amlogic chip under the heatsink, I can see a AP6330, what chip are you after? Please let me know

Quote from Demetris

Tell me your chip please

Sent from the Island of Venus

This is from the working 7.0.2, so I presume it is Broadcomm Bluetooth

[ 7.161686@2] BT_RADIO going: off
[ 7.161699@2] BCM_BT: going OFF
[ 7.207574@2] cur_mode = 0
[ 7.207588@2] [0x0] = 0x1dd0190
[ 7.207592@2] [0x4] = 0xf800ca
[ 7.207595@2] [0x8] = 0x82006e
[ 7.207598@2] [0xc] = 0x3c0030
[ 7.207601@2] [0x10] = 0x30fa0013
[ 7.207604@2] [0x18] = 0x6f19000
[ 7.207606@2] [0x1c] = 0x9f40
[ 7.207609@2] [0x20] = 0x0
[ 7.207611@2] [0x24] = 0x0
[ 7.207614@2] [0x28] = 0x0
[ 7.207618@2] set_remote_mode[69]
[ 7.237199@1] Bluetooth: Core ver 2.16
[ 7.249101@1] NET: Registered protocol family 31
[ 7.249114@1] Bluetooth: HCI device and connection manager initialized
[ 7.249143@1] Bluetooth: HCI socket layer initialized
[ 7.249151@1] Bluetooth: L2CAP socket layer initialized
[ 7.249171@1] Bluetooth: SCO socket layer initialized
[ 7.335947@1] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 7.335959@1] Bluetooth: BNEP filters: protocol multicast
[ 7.335980@1] Bluetooth: BNEP socket layer initialized
[ 7.405444@1] WIFI Disable! 6
[ 7.407544@2] BT_RADIO going: on
[ 7.407554@2] BCM_BT: going ON
[ 7.442824@3] The PHY does not support set_wol, was CONFIG_MICREL_PHY enabled?
[ 7.497696@2] Changing uart_a_ttyS1: baud from 0 to 115200
[ 7.537796@0] Changing uart_a_ttyS1: baud from 115200 to 2000000
[ 7.781367@0] as an end receiver
[ 7.785468@1] ionvideo open
[ 7.785729@1] ionvideo_stop_generating!!!!
[ 7.785748@1] ionvideo release
[ 7.955444@0] Changing uart_a_ttyS1: baud from 2000000 to 115200
[ 8.005442@0] Changing uart_a_ttyS1: baud from 115200 to 2000000
[ 8.035801@0] Bluetooth: HCI UART driver ver 2.2
[ 8.035815@0] Bluetooth: HCI H4 protocol initialized
[ 8.035819@0] Bluetooth: HCI Realtek H5 protocol initialized
[ 8.035822@0] rtk_btcoex: rtk_uart_coex_init, version: 1.1
[ 8.035825@0] rtk_btcoex: create workqueue
[ 8.036339@0] Bluetooth: hci_uart_register_dev
[ 8.047354@3] rtk_btcoex: create udpsocket, connect_port: 30001
[ 8.047400@3] rtk_btcoex: send msg INVITE_REQ with len:11
[ 8.055751@0] rtk_btcoex: uart_coex_info.hci_reversion = 1000
[ 8.055764@0] rtk_btcoex: uart_coex_info.lmp_subversion = 4103

And here is the one from your build, where it fails

[ 3.422746@3] Error: Driver 'bt-dev' is already registered, aborting...[ 27.628177@0] Changing uart_a_ttyS1: baud from 115200 to 2000000
[ 27.656115@3] Bluetooth: Core ver 2.16
[ 27.656226@3] NET: Registered protocol family 31
[ 27.656231@3] Bluetooth: HCI device and connection manager initialized
[ 27.656250@3] Bluetooth: HCI socket layer initialized
[ 27.656258@3] Bluetooth: L2CAP socket layer initialized
[ 27.656274@3] Bluetooth: SCO socket layer initialized
[ 27.659328@3] Bluetooth: HCI UART driver ver 2.2
[ 27.659338@3] Bluetooth: HCI H4 protocol initialized
[ 27.659341@3] Bluetooth: HCI Realtek H5 protocol initialized
[ 27.659345@3] rtk_btcoex: rtk_uart_coex_init, version: 1.1
[ 27.659348@3] rtk_btcoex: create workqueue
[ 27.659948@0] Bluetooth: hci_uart_register_dev
[ 27.661321@0] rtk_btcoex: create udpsocket, connect_port: 30001
[ 27.661352@0] rtk_btcoex: send msg INVITE_REQ with len:11
[ 27.668970@0] rtk_btcoex: uart_coex_info.hci_reversion = 1000
[ 27.668982@0] rtk_btcoex: uart_coex_info.lmp_subversion = 4103
[ 27.698200@1] Changing uart_a_ttyS1: baud from 2000000 to 115200
[ 27.713090@3] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 27.713100@3] Bluetooth: BNEP filters: protocol multicast
[ 27.713121@3] Bluetooth: BNEP socket layer initialized
[ 29.718190@0] Bluetooth: hci0 command 0x1004 tx timeout
[ 37.668210@0] rtk_btcoex: release udp socket

And I also think you should include the remote.conf linked earlier as it is specific to Beelink S82 which is the model you are building for.

Thanks for all your help

Quote from nikosgrgr

i have MXII 2G...put it remote.conf in config folder via filezila client...and reboot
remote.conf - Google Drive

Perfect, the remote.conf file fixed the issue with the infrared remote. Thanks for that
Now if Demetris can take a look at the Bluetooth issue then it will be 100%

Quote from Demetris

LE-8.0.1 release is out enjoy!

Fantastic, Thanks a lot Demetris for your work towards keeping Amlogic S802 still relevant

I had been using 7.0.2 S82 build from Drieschel on a MX-III 2GB and everything was working fine including wifi, Bluetooth and IR Remote

I updated the MX-III with LibreELEC-S802.arm-8.0.1a-S82 from your release and have run into issues
Everything but two devices seem to be working fine
The things not working are
1. Bluetooth
2. IR Remote
As both input devices are not working, I can't use the device without plugging in a USB mouse/keyboard.

Here is the dmesg output from 7.0.2 which shows the BT recognized correctly, don't know where IR is recognized but it sure works nicely.
zmK92jW8

And here is the dmesg output from your 8.0.1 build
bFwQptpq

Can you please take a look and advise what I am doing wrong. Thanks

Quote from lrusak

Yea it didn't create a new input device, so maybe it's just not possible with this card

Thanks for your help. Atleast these modules show up in dmesg so that is something, at least we are on the right track
I will try installing ubuntu server and experiment to see if I can get ir receciver detected and report back.

Thanks for the new build. Here is the output for the three commands as before
# lsmod | pastebinit
QaiW

# dmesg | pastebinit
HIWA

# udevadm info -q all -a /dev/lirc0 | pastebinit
Unknown device, absolute path in /dev/ or /sys expected.
IOAI

Thanks for that, let me know when you have a build, and I will report back with the results.
I am currently using LibreELEC-Generic.x86_64-7.0.2.img.gz

lrusak

Here is the output as per your specification above. As you mentioned, the last file is empty. Thanks for your time.

# lsmod | pastebinit
http://sprunge.us/ANNd


# dmesg | pastebinit
http://sprunge.us/RHVG


# udevadm info -q all -a /dev/lirc0 | pastebinit
Unknown device, absolute path in /dev/ or /sys expected.
http://sprunge.us/ELcY