okay. The issue ive been having is the box constantly reboots with my setup installed. untill it boots so much it boots to safe mode. I just wanted to try a pre 20 build
Is there a kodi 19 build for a S912 box I can try?
Both? .. there are at least 8x device-trees for GXM boxes and they are all mostly identical. If none of those work .. unless you attach a UART cable and share the u-boot serial console output so we can see where it gets stuck. Note the device-tree process is different in mainline images: You need to use the "box" image and edit the dtb name in uEnv.ini. if you start renamng files like legacy images do that's one reason none will boot.
Ah helps if you edit the uEnv.ini Booted first time with meson-gxm-q200.dtb for a S912 Vorke Z6 if anyone is asking. Thanks
I have a Vorke Z6 with a S912 and 3G ram. Ive tried both of the gxm device trees but cant get it to boot.
Any ideas if I can get a matrix build on this box?
My question was merely about the location of the kodi install, not kodi itself, I though my question would be better here because people are talking about eMMC and how to use the android partition to store the data. I am using the LibreELEC OS not Android.
Ive installed kodi so that it boots from eMMC. As I understand it all the data is stored on the android disk. If I use HD File Manager in Android, where can I find these files?
Hi all does anyone have a working link to Tanix TX7 android firmware please
Hi hopefully somebody can help me.. I’ve been using wrxtasy build for a long time without any problems and for some reason I decided I would try out the coreelec build, it installed ok but playback was terrible so I copied over the wrxtasy image and dtb to the upgrade folder and restarted and it went through the process but I am now stuck on the mecool logo. I’ve tried creating a sd cars with the image creator tool and it is still stuck on the mecool logo. (My original install was installed to internal) I’ve looked and I can’t find any hard reset button. The device is a mecool m8s pro 3gb s912
Anyone have any ideas?
Use the USB burning tool to get it back to android then install LE on eMMC
I found my answer
I have an ABOX S905W 2GB box that I want to run LE from sd card then do the [HOWTO] Boot from SD card, use internal memory for data trick.
I saw that @kszaq said to "S905W: You should use one of device trees for S905X devices"
So my question is if I want to install Index of /s905/8.2/188.8.131.52 does any one know what device tree works already?
Im going to try gxl_p212_2g.dtb first and go from there.
Does anyone have LE on this model if so please could you let me know which newest firmware and device tree you are using please.
It still something with your time settings.
Android is irrelevant, LibreELEC doesn't get time from Android.
Set it to auto in Kodi, pick the correct time zone, should work just fine.
Thanks that was a simple fix. What i had to do though was change to a different time zone then change it back again.
Android has nothing to do with the OpenVFD/FD628 driver in LE.
If you change a config file, the driver needs to be restarted, yes - you can reinstall it or just restart the box.
I don't understand what you mean by "can't change the clock". The time displayed is the system time, you shouldn't have to change anything in the driver, just make sure that the system time is set correctly on your box (in Kodi).
The current time here is 15:45 MST
The time on my Kodi is 15:45
The time on my Android side says 3:45PM
The time on my display says 21:45
I tried restarting the box after changing the vfd.conf file and nothing changed. Only when I uninstalled and reinstalled the command via ssh did it change.
I found the issue it was this:
IF YOU CHANGE VFD.CONF FILES YOU HAVE TO RUN THE "sh uninstall.sh" THEN "sh install.sh" WITH THE NEW VFD.CONF FILE.
I do actually now have another problem. I can't change the clock in the display. I changed it in android AFTER i ran the sh install.sh command.
Do you have to set the clock in android first then run the command??
They are not the same...Diff
diff --git a/vorke-z6-vfd.conf b/tanix-tx9-pro-vfd.conf index 3769853..fb6f36e 100644 --- a/vorke-z6-vfd.conf +++ b/tanix-tx9-pro-vfd.conf @@ -1,6 +1,6 @@ # This file must be renamed to vfd.conf and placed in the /storage/.config/ folder. # -# Vorke Z6/TX92 configuration +# Tanix TX9 Pro configuration #-------------------- #gpio_xxx: #  0 = &gpio, 1 = &gpio_ao. @@ -14,7 +14,7 @@ vfd_gpio_stb='0,53,0' #chars: # < DHHMM > Order of display chars (D=dots, represented by a single char) -vfd_chars='4,3,2,1,0' +vfd_chars='4,0,1,2,3' #dot_bits: # Order of dot bits. Typical configurations: @@ -33,4 +33,4 @@ vfd_dot_bits='0,1,2,3,4,5,6' #  - Flags. (bit 0 = '1' - Common Anode display) #  - Controller. -vfd_display_type='0x01,0x00,0x00,0x00' +vfd_display_type='0x00,0x00,0x00,0x00'
Ahh I see they are actually different, my mistake.
I have tried both many times and no matter which one i try my display is always upside down.
Any ideas what the heck could be going on?
I even deleted my FD addon settings file.
Ive just noticed that the Z6 and the TX9 vfd.conf files are the same apart from the box name