Hi. Maybe someone found solution for FD6551 chip?
Since latest update I have a lot of issue between the n5 and my harmony hub using bluetooth.
Am I the only one with this?
@2small @ffimon @supermegazord
Can someone post the DTB from Android on the boxes where the VFD isn’t working?
1 Like
Thank you.I looked at it and the config is fine. I will do some more investigation over the weekend and see if we can get it to work.
1 Like
Following this message 9.0.2 Discussion I have updated to latest nightly and bluetooth is back.
1 Like
FD655 works fine, it’s the FD6551 that don’t work.
1 Like
i have FD6551 chip, ill try port some android firmware, and recipe to work display is copy this FD655_Demo to /system/bin write lines at init.amlogic.rc and it work. so i think this service start my fd6551 chip
This is not the source code, I can’t do anything with it.
2 Likes
Disclaimer: This post is intended only for those, whose VFD isn’t working with the existing vdf.conf file and driver.
@2small @akella130986 @ffimon @supermegazord
After some digging around, I think I got the VFD problem with FD6551 chips figured out.
You’ll need the attached vfd conf before proceeding.
magicsee-n5-vfd.conf (1.5 KB) - rename to vfd.conf and place in /storage/.config
To run the test driver, SSH to box and run the following commands:
Get the driver (perform once):
cd /storage/downloads
mkdir openvfd
cd openvfd
wget https://test.coreelec.org/arthur/openvfd.zip
unzip openvfd
Run the driver (perform after a reboot to start the test driver again):
cd /storage/downloads/openvfd
systemctl stop openvfd
sh stop_service.sh
sh test_led.sh
Please report back whether it fixes the problem.
2 Likes
Great! Now you need to install the OpenVFD service addon to get the icons working 
1 Like
finally, all finished! here photo and repacked image for magicsee n5 (fixed bluetooth and new openvfd)
https://yadi.sk/d/Upb7p682hr6EvQ
copy SYSTEM to \CoreELEC\Downloads then ssh
mount -ro remount,rw /flash
cp /storage/downloads/SYSTEM /flash
1 Like
@TheCoolest I also confirm the display shows the time with your (detailed) information (but shows an hour behind).
I don’t think I understand completely how to make it work permanently… is this going to be included in future updates?
The driver displays the system clock, so it’s the system clock that is wrong.
I’m not sure exactly why this is, but it’s something to do with Kodi time and maybe region settings.
Great. The fix should be in the next nightly.
2 Likes
My Kodi shows the correct time. Maybe system has GMT and KODI is GMT+1 (Portugal).
That’s strange and to be tracked down.
Thanks.
I’m using portuguese regional settings and the time is correct. I remember that initially in Kodi I had to choose manually the correct timezone. When I switched the region initially it wasn’t correct (the time).
1 Like