Hi,
I’m trying to get the VFD working on my device. Once I add the correct vfd.conf file, the display just shows CE4.
After some digging, I noticed in the /usr/sbin/OpenVFDService/openvfd-start file, the command that starts the openvfd service shows the CoreElec version: /usr/sbin/OpenVFDService $OS_SPLASH_OPT ${clock_12h_format:+-12h}
If I can remove the $OS_SPLASH_OPT parameter, this will work fine, but this file resides in a readonly part of the filesystem. Is there a way I can fix this in order to display the time correctly?
I´m having the exact same problem, I have read somewhere that the CE version is supposed to be displayed for some seconds on boot and then the clock must be displayed, but for some reason it is not working that way.
I have the exact same problem in a S905X box and in a S905X3 box with proven VFD archives.
Also, systemd units in /storage/.config/system.d (maybe wrong folder name, don’t remember correctly) should take priority than those in /usr/lib/systemd/system, so you can copy the service that provides it and edit it in the writable /storage/.config/system.d
Mine is S905X4 with 4.6 Version as this ways can not work , these two files "openvfd.service"and “openvfd-start” just need creat that with notepad++ ? and what is the format it is ? .sh files or .conf files ? thank you so much
Hi, I have registered only to share my hotfix.
You just need to kill OpenVFDService that includes $OS_SPLASH_OPT ${clock_12h_format:+-12h} and launch a new service with only ${clock_12h_format:+-12h}. You can do this through custom_start.sh file located in \emuelec\Configfiles adding the next lines anywhere:
I prefer to add them at the end, just after the line # Any commands that you want to run after the frontend has started goes here so emuelec has time enought to connect to wifi and take the right local time before showing it in the display.
With this solution emuelec 4.6 still boots showing CE4 but once you are in ES you should see the local time in your Vontar x3 display.