Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[ViX_Misc] panic button

Rob - is there any easy way to populate the channel 1 slot even though the ZZL build seems to start it at 101? I've tried looking for a file called *101* and a sym link but cant find it
 
text

Rob + Rossi and ABU - sorry I got it now after Rob's post earlier. Just needed to vi the sat_282_sky_uk_zzl.xml file to introduce a working channel #001 for my region.

I swapped 1:64: BLANK ..... for 1:00:19:1b1f:802: etc and all working as previously. Do we need an ABM update that something populates Channel 001 despite other ABM selections?


All OK now - 1080 HD skin tomorrow
 
Last edited:
It is working with ABM as it has always done before.
The only issue is: when your ABM settings are such that if no channel #1 exists (e.g. because your lists starts at #101), the box can't zap to channel1 either. So panic button doesn't zap in that case, although the rest of the functionality (i.e. delete history and move to bouquet #1) remains functional.

If you want to overcome this 'issue', make sure your ABM settings generate the main bouquet as well.
I will try this feature on 099 once FTP site is updated but if panic button doesn't automatically zap to first channel of first bouquet because numbering of channels follows $ky numbering instead then could this feature not be added to by specifically mentioning in the menu settings for it which specific channel it should zap to rather than it trying to zap to channel #1 which wont exist under $ky numbering system.
 
good suggestion mate - with regionalisation it might not be possible to have same one and we already have default startup channel selectable so should be possible. All OK on my Box now - only thing left to test is adding 1080 skin (already downloaded) after fresh -098 and -099 upgrade and solution to Panic button. I'm still on Graphical EPG and all OK to me I get 2.59 secs when timing it (EPG startup) and 2.3 secs when chaning from BBC first page down to S** Atl*****
 
I will try this feature on 099 once FTP site is updated but if panic button doesn't automatically zap to first channel of first bouquet because numbering of channels follows $ky numbering instead then could this feature not be added to by specifically mentioning in the menu settings for it which specific channel it should zap to rather than it trying to zap to channel #1 which wont exist under $ky numbering system.

In openvix Apollo.095 when you hit the panic Button it would automatically zap to first channel of first bouquet Channel 101 BBC One HD

Something has changed Post Apollo.095
 
I'm still on Graphical EPG and all OK to me I get 2.59 secs when timing it (EPG startup) and 2.3 secs when chaning from BBC first page down to S** Atl*****
The EPG lag will be corrected in next build as 099 was already built by time Rossi/Andy corrected it. You could do it manually (see other thread if you want to).
 
Rob + Rossi and ABU - sorry I got it now after Rob's post earlier. Just needed to vi the sat_282_sky_uk_zzl.xml file to introduce a working channel #001 for my region.

I swapped 1:64: BLANK ..... for 1:00:19:1b1f:802: etc and all working as previously. Do we need an ABM update that something populates Channel 001 despite other ABM selections
All OK now - 1080 HD skin tomorrow

UPDATE
Sorry - that file edited was /etc/e*2/autoboquet.sat_282_sky_uk_zzl.main.tv
 
I too confirm that panic button doesn't entirely work as it's meant to.

I found it cleared the history but didn't actually zap to first channel of first bouquet.

Background: Viewing Channel 5 (105) and if I pressed the channel up/down button it would go either to 104 or 106 as expected.

However, whilst viewing Channel 5 (105), if I press the 0 (panic) button, and then pressed the channel up (as if to move to 106) it actually zaps to 102 as if I was viewing BBC 1 (101) but I wasn't, I'm still viewing 105.

So it's clears the history and kind of zaps to 101 but actually doesn't but by pressing channel up/down after pressing the panic button, it zaps to very last channel (ie one before 101) or 102 depending on whether channel up/down was pressed.

I've a Solo2, with ZZL ABM (with no HD swap) and CrossEPG OpenTV for 28.2.

I've attached debug log.

View attachment Enigma2-01-01-1970_01-00-12.log
 
Last edited:
Hi again bbbuk - I hadn't tested it that much but following one of the team's posts I had updated my *.zzl.main.tv file to include a channel 001 at the top and hide the description so I don't have 2 BBC1 HD's in EPG. Zap cleared stored channels and went back to BBC1 HD. HOWEVER - I just realised of course it went to 001 and not 101 so when I watch say 503 then 402 etc etc etc then zap back to "0" thinking I'm at start of my list. I actually am there but at 001 and not 101! So subsequently pressing up arrow to go thru 102 to 103 104 etc takes me to 002 003 004 etc - with no channels. I could swear this used to work with channel clear and zap back to channel 101 (BBC1 HD) with no channels config-ed in the lower 100.
 
Panic Button not working on my Solo2 either. It worked perfectly on build 95 but not on 97 and not on build 100 which I am now on. I have not changed any settings, simply updated the software online. I use the Lraizers Autobouquet-e2 Plugin. I have tried reinstall and rebooting. So what has changed in build 96 or 97 onwards that has stopped this working and please can I request a fix be looked at. Thanks.
 
If it helps I have repeated bbbuk's test (using the down channel button which I hadn't thought of) and I concur - it goes to channel 4098 - last one) - so it does think it is at 101 - just does not change display. (Solo2 at build 100 with ZZL and no tweaks to *.main.tv in place). I'll test when you've had time to look at it. THanks.
 
Stop panicking!

The issue has been acknowledged and should be looked at in due course. Do we need a daily confirmation that it is not working? A post will be made when work has been done on it.
 
Yes Rob that would be best but a new thread for each box and build would be best and maybe an hourly confirmation would be more useful than daily :D
 
Just done a clean install on 113 Apollo and this is now working again on my solo2

regards
 

OpenViX Feeds Status

Back
Top