- removed issue_status
"show transponder info" shows defined information and not live data
When ever you see a service list you are permitted to press MENU and can select the option "show transponder info" to display information about the channel. This information is based on the configuration data as defined in files like /etc/enigma2/terretrial.xml and not the live / actual values.
This display could / should also list the name and LCN of the channel as broadcast. This data can be changed in the UI so this could be the place to display the original, unedited, data.
As has been mentioned in
issue #56
the "Frequency:" display is set to no decimal places.
Side bug note: The "Transmission mo" and "Hierarchy informa" labels in the information pop up have their text cut short!
Reproduction steps
From live TV press FAV then RED (All) to display a list of channels. Select any channel and press MENU and select "show transponder info" to display the transponder's information.
The pop up contains entries "Inversion:", "Transmission mo", "Guard interval:", "Coderate LP:", Hierarchy informa", Constellation:" and "Coderate HP:" that have the value "Auto" and not the actual values learnt during the scan of the service.
Comments (6)
-
-
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Confirmed to Testing.
-
reporter - removed issue_status
No changes in behaviour noted.
The issue was updated with the following change(s):
- The status has been updated, from Testing to Not Fixed.
-
- removed issue_severity
The issue was updated with the following change(s):
- The severity has been updated, from Normal to Minor.
-
- removed issue_category
The issue was updated with the following change(s):
- The category has been updated, from Not determined to Application / User Interface.
-
There is also the same problem in MENU>Information>Service, YELLOW Tuner status and in the PliExtraInfo/TransponderInfo2line information at the bottom right of the Infobar.
- Log in to comment
The issue was updated with the following change(s):