From the SD/USB, enabling the network card did not work either, from Android honestly if I did not get to try
I leave some screenshots of the error that it gives me, I have investigated a bit but I have not finished carrying out the tests
in case something occurs to you
I found how to put android back but I think it’s not worth the risk as long as it works for me over wifi
For now put Android back on internal.
Test all functions on Android
Sometimes you need data from Android to configure CoreELEC
Like VFD config
Make a clean install SD/USB CoreELEC
Leave CoreELEC on external SD/USB
Depending on Media the read write speeds are not that much slower…
Continue to test CoreELEC on external
Once you have working CoreELEC with correct dtb
Remote config
VFD config
All functions etc…
Then maybe send to internal
This is what i would do.
Good luck
Happy Testing
JUST TO LET YOU KNOW, IT DOES WORK:
GPU- Mali-G31
Soc Amlogic Meson SC2 S905x4/C2
Board Ohm
USB stick Kingston DTSE9 8Gb
sysOS 20.0 Nexus
Linux v. 5.4.125
1.First i used balenaETCHER for Mac to make an image.
2. * Terminal Emulator: boot into Android, insert the CoreELEC prepared SD / USB, install Terminal Emulator app (either from Google Play or APKMirror), run it and type reboot update. Your device should reboot into CoreELEC.
First time come to a screen:
filesystem corruption has been detected
to prevent an automatic repair attempt continuing,
press any key … 120 sec.
Not knowing what to do, took electricity cable out.
Second try come to the same screen.
This time by accident, after 120seconds IT DID boot into Coreelec.
After that, any given time did boot it directly into CE-Kodi.
I was positive suprised by welcome screen od selecting wifi spot, but i have choosen for UTP.
So i did not tested.
SMB-CIFS works wel. Finding miniDLNA as wel. Only problem, dlna from OpenMediaVault does not in some case`s wana to use .srt files. In case of smb, there is no problem.
But i prefer NFS protocol for watching media from OMV as on another mediaplayer M8s-II who passed away.
In Kodi, when i press on NFS button to make a contact with OMV, it`s just get jammed.
A bug or whatever, do not know.
BUT, there is another way:
+add videos-browse-> zeroconf browser= NFS acc. is vissible.
Remote control was not useble according tree file i have used.
But mouse with a reciver helped for time beaning.
In posts above, have used remote.conf(remote.vontarx4_hk1x4) wich works great. There is only one button that gives no option as before, but still reachable via “OK”.
Forgot to mention, front LED panel is not working. But in my case, even beter.Its allredy annoing having living led collors arround.
About movies and transfer, nothing to complain(speaking about NFS). Allready tested a broad kind of formats. No hitch at all. A specialy UHD.According to router 3000kb/s +/-
However there is a small complain if any. If is a movie or episode on pause for a longer time(my kiddo loves to do that) after pressing a play, video stutters. After pressing stop and play again, no problem at all.
About treefile, i have used that NOT on the pic. is.
U have made a great job!!!
Congratulations!!!
Ps. Still to ask, if i change a tree file, do i get remote useable?
the highlighted key (@) seems not working. Normally this button works to show Player Info during video playback. Also tried with keymap editor, this key cannot be programmed as it is not detecting it.
Is it due to remote.conf?? Any better conf file for this remote??
Found out 3 buttons not working with attached remote.conf (attached)
remote_2.conf (2.6 KB)
Later I try SSH to see the system behaviour while pressing those button.
dmesg return are below:
@ button
[ 576.161004@2] meson-ir fe084040.meson-remote: scancode 82 undefined
[ 576.161017@2] meson-ir fe084040.meson-remote: no valid key to handle
<< Previous button
[ 666.320341@2] meson-ir fe084040.meson-remote: scancode 85 undefined
[ 666.320356@2] meson-ir fe084040.meson-remote: no valid key to handle
>> Next button
[ 709.289212@2] meson-ir fe084040.meson-remote: scancode 84 undefined
[ 709.289228@2] meson-ir fe084040.meson-remote: no valid key to handle
How I can alter my remote.conf to make this 3 buttons work? Please teach
Hi is there some solution for fix Bluetooth on this box ?
All works good but Bluetooth “No adapter found” probably bad driver for this X96X4 Box
If the WiFi+BT chip used in the box is from Amlogic, then BT will not work as there is no linux driver released by Amlogic
Atleast the WiFi works because of the great work done by CE team in developing the aml-w1 driver GitHub - CoreELEC/w1-aml: Amlogic W150S1
No solution until Amlogic releases the linux driver, and usually with Amlogic, this may never happen
My remote has same problem.
It is this one:
The buttons in first row (APP,KD,Mouse) also doesn’t work, but maybe can be remapped in CoreELEC for other use, plus one other button.
Scancodes:
meson-remote fe084040.meson-remote: scancode 65 undefined
also scancode 0, 15, 68 undefined
@Fliacik
My X96x4 rev 1.3 has realtek WLAN/BT chip and works.
It is kind of a lottery which chips are in this box for WLAN/BT and LAN.
About | FAQ | Terms of Service | Privacy Policy | Legal Notice
