OpenVix Custom EPG

[TK4|2|1]

Been using this for a few days now without any issues on the default skin, would love to see these options included in the image by default.

View attachment 48009

Here here.

 

[Partymack711]

Lads,

This GEPG mod is fantastic... But have you made any improvements to the earlier mod from December last year?

The earlier mod conflicted with Powertimers after a timer recording (eg after event go to deep standby) and also general auto standby/auto deep standby.

The "a Powertimer wishes to shut down now, Y/N to allow this" mess would display but box wouldn't time out and go to standby/Deep standby.

If that big is sorted this is the skin mod to beat all skin mods!

 

[bbbuk]

I wasn't aware there was a problem with this.

Can I suggest you make a full image backup and install the plugin and test it out. If any problems then uninstall it (then reboot) and it should restore the main epg files. If all else fails you can go back to your image backup you made.

Let us know how you get on?

 

[Willmoore]

I installed this on my VU Zero using the Confluence skin but when I pressed epg the box crashed.

 

[bbbuk]

I installed this on my VU Zero using the Confluence skin but when I pressed epg the box crashed.

It looks like it's complaining of 6 parameters being passed to IsSelectable when only 5 is needed. I never had this issue on my solo2 and no one else where I got it from has mentioned anything about it.

Maybe remove plugin and this should restore original epg files and restart box and check everything is okay.

If okay, try changing skin to default skin (vix-night) and installing plugin again and see if you have same error again.

 

[Willmoore]

I have un-installed the plugin and put my usual skin back on and all is good. I'll give it a go tomorrow with the default skin just to see what happens (not keen on that skin so it won't be staying).

 

[bbbuk]

Just stay on that skin whilst installing plugin (then restart box after installation) to see if it crashes again. Most features can still be used regardless of skin you prefer.

 

[Willmoore]

Just stay on that skin whilst installing plugin (then restart box after installation) to see if it crashes again. Most features can still be used regardless of skin you prefer.

Tried it with the default skin with the same result.
I also tried it on my Solo2 using You Vix Blue and it also crashed
So, problem with the file ? doubt it, as other users are okay.
Operator error ? likely - but not sure what I am doing wrong.

 

[bbbuk]

@Willmoore, are you using latest version of Vix 4.1 004 ? I have no problems on my solo2 installing this with latest version.

If it's an old version then I can't comment for that personally as I didn't try it but it still shouldn'd be a problem unless a really old version of Vix.

 

[Willmoore]

@Willmoore, are you using latest version of Vix 4.1 004 ? I have no problems on my solo2 installing this with latest version.

If it's an old version then I can't comment for that personally as I didn't try it but it still shouldn'd be a problem unless a really old version of Vix.

Using latest version on both boxes.

 

[bbbuk]

Weird. Can I make a suggestion and you make an image backup of current image and a settings backup on your Solo2 and do a fresh usb flash (with no restore of settings - at least just yet) then FTP a fresh download of this plugin to your tmp folder and from telnet type:

opkg update
opkg install /tmp/*.ipk

and once plugin installed, and full reboot of box (telnet command "init 6").

See if that works which I hope it does. You could then re-install your plugins from feeds again and restore your settings (if that's your preference).

 

[twol]

Running my own "ViX" builds and with the ability to switch images easily through a simple restart (due to the dual image capability of the ET8500), I have this code implemented into the standard ViX code.
Although I initially thought I would be in debug mode for a few images, I have been surprised at how solid the image has been with no issues during the last week.

I also find the changes immensely productive and the use of the Epg much easier with the keys set up the way I like them.

As a keen user of OpenVix image, for the reasons that (in my view) OpenViX offers the most complete image available, and one that has a track record of being innovative, I feel that the ViX team should look at offering these changes in the base code.
It really adds value to the "average" use of the OpenViX image

Obviously a weeks testing by one user doesn't prove the code is 100% solid, but having run several image builds with the recent Xtrend kernel changes, and had no issues when re-flashing and restoring the settings between images, I feel the code is pretty transparent.

Note: I also have a copy of the ViX skins on my system with the epg changes implemented.

Would be interested in comments from the ViX team

 

[Partymack711]

Twol,

Mod is great but have you found it interrupting your Powertimers?

If I do a timed record, which the box needs to wake up from deep standby, record , then go back to deep standby. it will wake up, record but won't go to deep standby. It gets caught in a loop thinking there are recordings coming up.

Also I have my box set to auto standby after 90 mins, then auto deep standby (from standby) after 30. It never gets to deep standby.

Same happening for you?

 

[twol]

Twol,

Mod is great but have you found it interrupting your Powertimers?

If I do a timed record, which the box needs to wake up from deep standby, record , then go back to deep standby. it will wake up, record but won't go to deep standby. It gets caught in a loop thinking there are recordings coming up.

Also I have my box set to auto standby after 90 mins, then auto deep standby (from standby) after 30. It never gets to deep standby.

Same happening for you?

No - but I don't ever use a lot of timers - so obviously needs more testing to sort this ... but don't remember anything in the code that would cause this, so does this happen with Vanilla ViX or not???

 

[birdman]

If I do a timed record, which the box needs to wake up from deep standby, record , then go back to deep standby. it will wake up, record but won't go to deep standby. It gets caught in a loop thinking there are recordings coming up.

The first part of that sounds like an issue I partly looked into 5 months ago. Not sure whether it would cause the other part, though.

Take a look at this thread (just one post) and follow the link in it for a solution....if that is your problem.

 

[bbbuk]

The only thing I have noticed is that in epglist.py, 2 lines of code go where the namefont is reset ... haven,t followed through to see what impact this has but sticking to the OpenViX code hasn,t caused any obvious issues

Could you provide more info on this and it will be looked at

@Partymack711, as mentioned by twol there is nothing obvious in the code of the modded epg files that could cause this but obviously I can't confirm this as I too don't use power timers. More testing would need to be done to determine if it was the mod files and what offending code that is/isn't their that can cause this.

 

[dfox]

@Ford1, here is the latest blue-hd skin but modded with just the two lines of code needed. Can you see if this solves your bold issue?

Extract the .xml file from the archive and FTP it to:

/usr/share/enigma2/Blue-HD/

and over-write the existing file. You will need to restart box.

@Twol, I vaguely remember GEPG being bit more bold after installing this mod for blue-hd (nothing seems to change for the skin I use).

Yes, this worked and changed the font back from bold. Thanks

 

[abu baniaz]

Are the following possible?
1. Remove enigma2 from depends in control file. It is not required for install and I can't imagine anyone using this on an image that does not have enigma2.
2. Add Blue HD skin as a depends. This means that you will always install the current one from plugins server
3. Try using Use epg_custom.png, else epg.png. This removes the need for one of the backing up processes.
4. Is there a possibility that the debug print comments can state that a modified version is being used. Makes it easier to diagnose issues.
5. As far as I can see, the removal process only deals with the .pyo files, not .py files. So removal is not complete. Workaround is to use .pyo files in ipk or to add the .py files in removal process

 

[bbbuk]

Are the following possible?

I'll answer the questions in turn...

1. Remove enigma2 from depends in control file. It is not required for install and I can't imagine anyone using this on an image that does not have enigma2

I have removed this.

2. Add Blue HD skin as a depends. This means that you will always install the current one from plugins server

The problem with this is user may not actually want Blue HD skin installed. The plugin only replaces a modded skin .xml file.

It would be easier if admin/mods were to allow these skin .xml changes to github and included in future Vix releases!?! I can confirm that using these modded skin .xml files without the plugin installed (or any other modded epg files) doesn't result in any errors/crashes or anything. It appears the skin just ignores widget names if it can't find them within the modded epg files. I'm happy to submit these few changes if okay with admin/mods?

3. Try using Use epg_custom.png, else epg.png. This removes the need for one of the backing up processes

See my proposal for question 2. This is better/easier option.

4. Is there a possibility that the debug print comments can state that a modified version is being used. Makes it easier to diagnose issues.

Good idea. I could only see one debug print statement which i've amended. I've also added the following debug statement to all plugin .py files:

[OpenVix Custom EPG] OpenVix Custom EPG is installed.....

This then mentions the name of the file that is modded. Hopefully, this will aid with diagnosing issues as you can just search for "Custom EPG" in debug logs to see if/what modded epg file is being used, if any.

5. As far as I can see, the removal process only deals with the .pyo files, not .py files. So removal is not complete. Workaround is to use .pyo files in ipk or to add the .py files in removal process

The package provider, opkg, in this case handles removal of additional files installed when removed using opkg. I can confirm .py files are actually removed by opkg package.

 

[abu baniaz]

Thanks for the clarification/s.

Best not to submit any pull requests until the existing one is merged. You saw how the primary bouquet thing caused confusion and gave credence to rejection to other items.

There was mention that there would be possible slow down in the EPG menu. How this is going to be tested/confirmed/found not to be the case is going to be difficult if it is not merged. The whole point of the Developer image is to test things before adding to the public image. I'll leave that discussion to others.

The plugin only replaces a modded skin .xml file.

I found an epg.png in the following folder
/media/hdd/ipkg-tools/enigma2-plugin-extensions-openvixcustomepg_1.0_all/usr/share/enigma2/Blue-HD/infobar
This is what prompted the question/suggestion. Maybe this is/was an oversight?