Testers required for OpenViX Python 3 images

[ccs]

Here is the nfs issue dealt with: https://github.com/oe-alliance/oe-alliance-core/commit/27bda873a5ca600dcb9d28d4b7df0f50eaf05acb

Back working again now on 5.5.014.005

 

[BrokenUnusableAccount]

Minor cosmetic difference between Py3 and Py2:



In Py2 it says 28.2°E.

(Skin is Simple 1080)

 

[ccs]

.... same on freeview, P2 545.833 MHz rounded down to 545.0 MHz in P3.

 

[twol]

.... same on freeview, P2 545.833 MHz rounded down to 545.0 MHz in P3.

can you post a picture!

 

[ccs]

Here we go....

 

[Huevos]

Minor cosmetic difference between Py3 and Py2:

View attachment 62400

In Py2 it says 28.2°E.

(Skin is Simple 1080)

Please try this: https://github.com/OpenViX/enigma2/commit/a5b3eeb6fe3a783c9dc278121e43b5328b1bb52c

 

[Huevos]

Here we go....

Can you try the attached file. Goes in Python.Tools

 

[BrokenUnusableAccount]

Please try this: https://github.com/OpenViX/enigma2/commit/a5b3eeb6fe3a783c9dc278121e43b5328b1bb52c

Thanks. That's fixed 28.2°E.

I don't seem to have any Freeview on nnn.833MHz to test that.

But I noticed:



that QAM256 shows up as QPSK.

This was the same in Py2, I have no idea if it's a hardware or API limitation or a bug.

 

[birdman]

that QAM256 shows up as QPSK.

Given that QAM256 is Mode6 and QPSK is Mode7, is this an off-by-one error?

 

[BrokenUnusableAccount]

Can you try the attached [Transponder.py] file. Goes in Python.Tools

That doesn't seem to work at all.

I think you accidentally removed a # from the beginning of line 248.

 

[ccs]

Can you try the attached file. Goes in Python.Tools

Yes, that's now ok. (I didn't add the PliExtraInfo.py commit, but did add the # mentioned by @BefuddledBrian).

 

[BrokenUnusableAccount]

That doesn't seem to work at all.

I think you accidentally removed a # from the beginning of line 248 [of Transponder.py].

Further thoughts:

Without the # it made my box hang or loop so that it never finished booting up.

Is that a sign that there is some kind of untrapped error condition or something during the phase of bootup where new .py files are compiled to .pyc?

 

[Huevos]

@CCS, @Brian, can you investigate this DVB-T modulation problem. Does it also show the wrong type in Py2. Does it just show wrong on the zgemma?

 

[ccs]

@CCS, @Brian, can you investigate this DVB-T modulation problem. Does it also show the wrong type in Py2. Does it just show wrong on the zgemma?

I'm seeing the same on all HD muxes (QPSK) for both P2 and P3, SD muxes as in post #431 (QAM64). Ultimo4k.P3, ET10K.P2

P2

 

[BrokenUnusableAccount]

Further thoughts:

Without the # it made my box hang or loop so that it never finished booting up.

Is that a sign that there is some kind of untrapped error condition or something during the phase of bootup where new .py files are compiled to .pyc?

I think maybe it was looping retrying over and over:
View attachment logs.zip

I guess there's no easy way round it.
You usually want to start again after a crash.

 

[ccs]

It certainly doesn't like line 248

18:11:51.3953   File "/usr/lib/enigma2/python/Tools/Transponder.py", line 248
18:11:51.3954     print 'frequency:',tp.get("frequency")
18:11:51.3954           ^
18:11:51.3955 SyntaxError: invalid syntax

 

[thecaretaker]

On my VUUltimo4K with release 5.5.14.005 it won't go into standby. It dims the boxes screen for a few moments (with the Picon still showing not the standby screen) and then turns back on. I have my soundbar and TV linked using the ARC HDMI so it also turns the soundbar and TV back on. I've double checked the HDMI CEC settings and they are exactly the same as I had on the 5.4.013, 5.5.013, 5.5.14 004 which works fine.

 

[ccs]

.... there were recent changes in HdmiCeC relating to standby, maybe you can post debug logs?

 

[twol]

On my VUUltimo4K with release 5.5.14.005 it won't go into standby. It dims the boxes screen for a few moments (with the Picon still showing not the standby screen) and then turns back on. I have my soundbar and TV linked using the ARC HDMI so it also turns the soundbar and TV back on. I've double checked the HDMI CEC settings and they are exactly the same as I had on the 5.4.013, 5.5.013, 5.5.14 004 which works fine.

@Caretaker .. Sounds like you have a crash - so look for crash log and also current & last debug log - post all !

Also try this version (which runs fine for me both direct to TV an also through a Onkyo amp)
Putty: init 4 (space between)
Filezilla: copy attachment to /usr/lib/enigma2/python/Components
Putty: init 6 (space between)

#########Note - attachment changed##### 16.39 19/7/2021

 

[twol]

It certainly doesn't like line 248

18:11:51.3953   File "/usr/lib/enigma2/python/Tools/Transponder.py", line 248
18:11:51.3954     print 'frequency:',tp.get("frequency")
18:11:51.3954           ^
18:11:51.3955 SyntaxError: invalid syntax

Either put a # in front or print('frequency:', tp.get("frequency"))