Posts by pheonix

    Voicing an opinion isn't going to and hasn't got anyone banned, but attitude and bitching has. I don't think your last post will get you banned, but I think it is inaccurate to say that voicing your opinion got you banned before, it is ok to have an opinion, but without the attitude.


    well we will just have to agree to disagree on that one, or ask your college who issued the bad after and i quote i said " Tspanel is utter trash and best avoided".

    I know Tspanel is a touchy subject here and it's the reason i was banned from this forum once before, and yes i do know that This forum operates and maintains a server on the Tspanel but if you would allow me to voice my opinion without banning me please ??.


    I really would avoid Tspanel for use with ViX or any other Pli or Pli based image.


    The reason ?.


    Simply that Tspanel overwrites a lot of image critical system files during it's install which directly leads to problems with things like Timeshift it also makes removing it fully from the image at a later date almost impossible. This is a known problem and is the primary reason why We ( ViX ) removed it from our feeds, Pli also have a discussion on the same grounds on their forum with regard to this.


    Now for Cams you can obtain them directly from this forum or via the Openvix image server. and no dont install CrossEPG into the ViX image as it already contains a Highly modified version already and if you overwrite this it will cause you problems.


    My last point. The ViX image has a rather well stocked set of image feeds with lots of the more common plugins already in there ready to install at the click of a button, rendering the Tspanel pretty much useless barring for Cams which i have already mentioned above.

    quote from ansy him self.





    Try to find kernel you mentioned, but only found duo_cfe_cfe.auto ( 280 kb) which seems to be the same as this old one I used when upradeing old BH 1.4 to BH 1.6.6
    Sorry, but I am now confused what s I have to do, shall I repeat same procedure when installing BH 1.6.6 and then after installing old cfe_cfe kernel using USB- instal the newest BH 1.7.9
    Please help me,



    I think your confusing your self a little.


    The file mentioned above is a bootloader ( like a bios update for a PC ), you simply flash this ( only needs doing once so once done it never needs doing again unless there is a updated version released ), then flash the required image.


    All current images are compatible with this bootloader both the older 2.6.18 kernel images and the newer 3.1.1 kernel images ( the kernel is part of the actual image it self ).

    The arivas are very nice boxes i have the e202, but they are not enigma based and as such there a nightmare to get a good working channel list for them and the EPG is now and next only.


    Personally i'd say go for a single tuner Linux based E2 box such as the TM single or the Maxdigital XP1000 both are very nice receivers with a decent amount fo support from various teams in the OE-Alliance such as ViX.


    and both can be bought from the forum sponsor ( you can get your self a £5.00 off voucher for being a member of this forum if you PM him ).

    yes as said above, it's to tell you there are updates available for the image.


    Green are for stable updates and red for unstable, although it is worth noting that even unstable updates are not necessarily unstable, most of the time there for minor bug updates that we have not had sufficient time to test but as there minor were fine to release as is.

    It could be any number of reasons for the update failing, you best bet is to create a set of Debug logs and forward them to the AAF team so they can see whats going wrong and help you either fix it or suggest another solution.

    for example here.


    Code
    https://github.com/oe-alliance/oe-alliance-core/commit/290474dc4728a0830f65ca939f17370960d79357


    we are currently testing Build 578 which may or may not be released to the public as often andy already has fixes and a new build to go before we get through testing the older ones. it's all a long process of test, test and test some more.

    Yes, the images pops out daily (I am sure it is automated robot that does compiling from the git code)


    OK, I see it is WOS then if one wants openvix image


    sebus



    No the build is not automated, it is built as and when we decide to, usually to include fixes or add features to the image. we dont believe it just building a image and palming it off on our users without at least some testing on our part. for example this last week we have held back many builds for inhouse testing due to a lot of changes made to the EPG, we felt these changes were important enough to warrant our testing them as fully as possible before releasing them to the public.


    That said there are also a number of other OE-Alliance teams releasing images for these receivers and a few others not associated with the OE-A such as the italysat team.
    granted the Gigablue may not have the support of say the Vu boxes but they are a relatively young company and the work they have done so far in my opinion has been well worth it.


    as far as the ViX image goes I would far rather support the Gigablue receivers than the Dreambox ones, but thats just my personal opinion and not the opinion of the ViX team as a whole.

    CrossEPG should be fine on the Hard drive m8,


    As it only reads it from the hard drive to begin with,it then keeps it in memory till you either update it or shut down etc



    yes thats exactly rite, EPG data is held in live memory in the same way as Bouquets are. saving a EPG to a hard drive is the preferred method, however i would advise against using the internal flash as the EPG.dat file can very easily become corrupted and grow huge in a very short time, filling the flash to the point where a full reflash is needed.

    appologies, thought it would just be a general issue


    using vix 2.3 with crossepg



    The best thing you can do is to disable overscan on your TV but if thats not possible as a last and only as a last resort you could preposition the OSD ( on screen display ) via the OSD positioning app in the image it self. or better still upgrade to a newer image as ViX 2.3 is now pretty much obsolete and will never be updated or maintained again.


    A lot of work has been done on the EPG in the ViX image lately with a lot more to follow, so give it a try and see if it works any better for you in a newer image.

    Of course you can buddy & by the sound of things you are very close to using all available ram so its going to come in handy.
    @ pheonix other images with built in backup functions and also the backup suite plugin all create a swapfile automatically before the script starts the backup process, is there a reason vix have decided not to in thier own backup script. Personally i never had any problems backing up vix on original solo im just curious.


    Thats something that would have to be brought up with the ViX coder andy blac, he is open to suggestions and will often incorporate them into the image if enough interest is shown. I do know that andy has recently cleaned up a lot of code closing down a lot of the unnecessary running processes when making backups etc but i'm not sure if creating a swap file is the best way to go my self.