WilloBuild WilloBuild OpenViX 6.5 Series

Thank you for the pictures.

For the SNPicons, the names of the IPTV ones would need to be gbskywitnessfhdprem, gbailibi (as examples). There are too many iptv providers to cater for those name variations. You could add your own symlinks/picons

For the SRPicons, the picons have to be named to match the service reference. Provided the IPTV service has the correct one, it will work, irrespective of the name.

You have a Service reference picon pack from September 2021. It will not have the references of channels launched in February 2023. The references changes from time to time. Please install the latest version of the SRPicons, then list the picons that are missing. We can then add those references and your picons will show. Not many people use them so the references are not maintained very well.
 
I don't know who maintains/builds those. I will double check the ones on following repository and add links where applicable. Should make it into Sunday's release.
Code:
https://github.com/picons/picons
https://github.com/picons/picons/releases

If where you get them from fork from the other repo, then they should get the changes too.
 
I have built two sets for you . You can download from link below. Please uninstall the previous version otherwise you will get a version clash
Code:
https://www.mediafire.com/folder/ja7r7qq9zc2cc/binaries-srp-full

There was an issue with the upload on Sunday again, not all packages were uploaded . I have also e-mailed the chap on that site you got it from. I think he is using an outdated lamedb file file.
 
I have built two sets for you . You can download from link below. Please uninstall the previous version otherwise you will get a version clash
Code:
https://www.mediafire.com/folder/ja7r7qq9zc2cc/binaries-srp-full

There was an issue with the upload on Sunday again, not all packages were uploaded . I have also e-mailed the chap on that site you got it from. I think he is using an outdated lamedb file file.
Hi Abu, just an update, I have installed the light/transparent version of your build, all those picons are back but IPTV picons are gone, I have also noticed that I think I have more than one Picon folder, one in /media/hdd (Picon location by XE) and one /root/Picon. Is that right?
 
Transfer one to the other and delete one folder. Or check if xe picon location settings can be changedThanksth
Transfer one to the other and delete one folder. Or check if xe picon location settings can be changed
Thanksmate, after a bit of a try and error finally got all the Sats and IPTV Picons back on, although some of the IPTV picons are missing but hey...i am ok with it...
Thank you Abu and all the guys helped me out to resolve the issue I hope this will help the others may have similar problems in the future...
Regards,,
G...
 
Last edited:
Hi guys , just set up a h11s box with willobuild and updated xe downloader plug in. All working great but when i use the willo picon updater it puts the picons on the sat free to air channels but removed the picons from the xe downloader iptv channels. Any ideas how i can have picons for free to air and iptv ? Ive tryed turning off picons in xe plug in then running the picon updater but still nothing . cheers
 
I think picon updater deletes existing picon folders and creates a new one on /media/hdd/.
Have you tried updating XE picons after running picon updater?
 
Picons have not long been updated on vix build.

Run xe picons

Try menu, plugins red to remove plugins and uninstall picons

Then plugins green to install picons and install a picon pack. Choose HDD

If that works disable xe picon update
 
yes fella tryed that just tryed again. its like you can have 1 picon list or the other .
I've just updated the script on my server so that it just appends the date to existing picon folders rather than deleting them and it leaves the internal flash ones alone.
Try running the XE picon updater again and then the picon updater plugin.
 
Have you got a storage drive mounted as /media/hdd

It's working fine here:

--2023-03-08 16:43:45-- https://www.openvix.co.uk/openvix-builds/ax61/openvix-6.3.003.release-ax61_multi.zip
Resolving www.openvix.co.uk... 176.31.181.161
Connecting to www.openvix.co.uk|176.31.181.161|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 107487368 (103M) [application/zip]
Saving to: ‘latestvix.zip’

latestvix.zip 100%[===================>] 102.51M 11.3MB/s in 9.1s

2023-03-08 16:43:54 (11.2 MB/s) - ‘latestvix.zip’ saved [107487368/107487368]

Archive: latestvix.zip
creating: hd61/
inflating: hd61/force_hd61_READ.ME
inflating: hd61/uImage
inflating: hd61/rootfs.tar.bz2
inflating: hd61/imageversion
inflating: unforce_hd61.txt
 
Have you got a storage drive mounted as /media/hdd

It's working fine here:

--2023-03-08 16:43:45-- https://www.openvix.co.uk/openvix-builds/ax61/openvix-6.3.003.release-ax61_multi.zip
Resolving www.openvix.co.uk... 176.31.181.161
Connecting to www.openvix.co.uk|176.31.181.161|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 107487368 (103M) [application/zip]
Saving to: ‘latestvix.zip’

latestvix.zip 100%[===================>] 102.51M 11.3MB/s in 9.1s

2023-03-08 16:43:54 (11.2 MB/s) - ‘latestvix.zip’ saved [107487368/107487368]

Archive: latestvix.zip
creating: hd61/
inflating: hd61/force_hd61_READ.ME
inflating: hd61/uImage
inflating: hd61/rootfs.tar.bz2
inflating: hd61/imageversion
inflating: unforce_hd61.txt
Have you got a storage drive mounted as /media/hdd

It's working fine here:

--2023-03-08 16:43:45-- https://www.openvix.co.uk/openvix-builds/ax61/openvix-6.3.003.release-ax61_multi.zip
Resolving www.openvix.co.uk... 176.31.181.161
Connecting to www.openvix.co.uk|176.31.181.161|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 107487368 (103M) [application/zip]
Saving to: ‘latestvix.zip’

latestvix.zip 100%[===================>] 102.51M 11.3MB/s in 9.1s

2023-03-08 16:43:54 (11.2 MB/s) - ‘latestvix.zip’ saved [107487368/107487368]

Archive: latestvix.zip
creating: hd61/
inflating: hd61/force_hd61_READ.ME
inflating: hd61/uImage
inflating: hd61/rootfs.tar.bz2
inflating: hd61/imageversion
inflating: unforce_hd61.txt
I thought I had but may be not? Is there a way to check?
 
You need to check Mount Manager.

MENU - SETUP - VIX - MOUNT MANAGER on ViX, not sure about ATV.
Managed to mount it correctly but now get this error unfortunately. Apologies
 

Attachments

  • Screenshot_20230308-170433.png
    Screenshot_20230308-170433.png
    393.9 KB · Views: 7
  • Screenshot_20230308-170421.png
    Screenshot_20230308-170421.png
    395.4 KB · Views: 7
Back
Top