CH- and LEFT do not work correctly in Terrestrial LCN bouquet
Issue #111
resolved
Using CH- and LEFT to change services does not select all available services in the Terrestrial LCN bouquet, it only appears to visit alternate services.
In Canberra my Terrestrial LCN bouquet is (in order): ABC1, SBS ONE, SC10, PRIME7, WIN, ABC1, ABC2 / ABC4, ABC3, ABC News 24, SBS HD, SBS TWO, SBS 3, NITV, ONE, TVSN, ELEVEN, Aspire, PRIME7, PRIME7, 7TWO, 7mate, 4ME, ishoptv, GEM, GOLD 2, GOLD, GO!
If I start at ABC1, and use CH- or LEFT to sequence through the service list, I should visit the services in this order: ABC1, GO!, GOLD, GOLD 2, GEM, ishoptv, 4ME, 7mate, 7TWO, PRIME7, PRIME7, Aspire, ELEVEN, TVSN, ONE, NITV, SBS 3, SBS TWO, SBS HD, ABC News 24, ABC3, ABC2/ABC4, ABC1, WIN, PRIME7, SC10, SBS ONE, ABC1
The order that I actually visit the services is: ABC1, GO!, GOLD 2, ishoptv, 7mate, PRIME7, Aspire, TVSN, NITV, SBS TWO, ABC News 24, ABC2/ABC4, WIN, SC10, ABC1
If I highlight the services I actually visit in the list that I should visit, there's a clear pattern: ABC1, GO!, GOLD, GOLD 2, GEM, ishoptv, 4ME, 7mate, 7TWO, PRIME7, PRIME7, Aspire, ELEVEN, TVSN, ONE, NITV, SBS 3, SBS TWO, SBS HD, ABC News 24, ABC3, ABC2/ABC4, ABC1, WIN, PRIME7, SC10, SBS ONE, ABC1
If I start with a service that's not on that list of services visited starting from ABC1, a few presses of CH- will get back to that list, and then cycle through just the services on it.
As with bug 110, removing the
#SERVICE 1:832:d:0:0:0:0:0:0:0:
entries from /etc/enigma2/userbouquet.terrestrial_lcn.tv works around this problem.
Also as with bug 110, the problem only appears in the Terrestrial LCN bouquet, not in any other bouquet, nor in FAV, All.
Reproduction steps
For Canberra scan data, I can reproduce this by selecting Terrestrial LCN in FAV, and then selecting ABC1, OK to go to ABC1 in live TV. Then pressing CH- or LEFT will go through the data in that order.
I've asked twice on the T3 forum for people to try to reproduce this problem, but I haven't had any definite responses, so I don't know whether this is Canberra-specific or not.
If it's not possible to reproduce the problem using scans from other locations, I've attached the lcndb, lamedb, userbouquet.terrestrial_lcn.tv, userbouquet.LastScanned.tv from my Canberra scan. It may be possible to reproduce this problem by copying them into /etc/enigma2 on another T3, restart the GUI and then attempt to reproduce the problem.
I've marked the bug as Always in Reproducability, because it is reproducible for me. I don't know if it's reproducible for scans at other locations.
Comments (11)
-
reporter
-
reporter
A file was uploaded. reference to attachment lamedb (lamedb from Canberra scan)
-
reporter
A file was uploaded. reference to attachment userbouquet.terrestrial_lcn.tv (userbouquet.terrestrial_lcn.tv from Canberra scan)
-
reporter
A file was uploaded. reference to attachment userbouquet.LastScanned.tv (thumb)
-
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from New to Delegated.
-
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Delegated to Testing.
-
reporter
A file was uploaded. reference to attachment 20140318_prl_Canberra_settings.zip (/etc/enigma2 from a scan of Canberra Black Mountain) This comment was attached:
Scan and other settings from a scan of Canberra Black Mountain (upgrade firmware, scan in setup wizard, Restart GUI).
I hope that using these settings will help the developers replicate the problem.
-
reporter
- removed issue_status
Still the same problem for me in 20140316 and 20140317, though the order the services are visited has changed. CH+ still does not take me through all services in the Terrestrial LCN bouquet. I have attached a copy of the contents of my /etc/enigma2 folder. I hope this makes finding the problem easier for the Beyonwiz engineers.
The issue was updated with the following change(s):
- The status has been updated, from Testing to Not Fixed.
-
reporter
-
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Not Fixed to Testing.
-
- removed issue_resolution
- removed issue_percent
- removed issue_close
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Testing to Closed.
- This issue has been closed
- This issue's progression has been updated to 100 percent completed.
- The resolution has been updated, from Not determined to Fixed.
- Log in to comment
A file was uploaded. reference to attachment lcndb (lcndb from Canberra scan)