It’s only as good as you make it. 
Posts by Andro1
-
-
Thanks for the great idea!
However, I no longer use the plugin, as the system I’m currently working on already integrates this feature into the Channel Selection and Radio Selection menus.
I only made the necessary fixes and adjustments to ensure better compatibility with DreamOS.
If you or anyone else has any fixes, improvements, or other suggestions, feel free to share them with the users.
Enjoy!
-
Since I’m moving to Python 3, I’ll focus on the important fixes and a few useful additions that can actually help users.
I understand the concern about changing buttons and how that can affect different skins, especially system skins. That’s why I decided to go back to using Label instead of StaticText
(that is, Button_Small_name instead of Button_Small_source)
to keep things consistent with the version currently available in the feed and avoid confusing beginner users.
Note:
If you’re using the default skin (Default-FHD), you’ll notice a difference in the (ZapHistoryConfigurator) screen’s skin.
You can keep the current screen’s skin without issues. However, if you want to switch to the updated skin, you’ll need to remove the (ZapHistoryConfigurator) screen’s skin from the (skin_default_1080.xml) file.
The intention is not to break anything in system skins. All changes are optional, safe, and aimed at helping users who want them.
Hope this clarifies things and keeps everyone happy
Download the updated file from the #1 post.
Cheers!
-
You’re right, I didn't notice that. Thanks for pointing it out.
Perhaps superadmin could move the topic to the appropriate section or delete it if he finds it unhelpful!
-
Just to clarify, these changes are intentional, they’re my own personal improvements that I think work best.
I’m not forcing anyone to use them; it’s completely optional. If you like them, feel free to use them as is. If not, you can always stick with the original version on the feed.
These changes don’t affect the system in any way. You’re free to use or ignore them as you prefer — it’s completely up to the dreamers.
-
The default skin file needs to be updated.
Go to /usr/share/enigma2 and open the skin_default_1080.xml file.
Search for Zap-History, then within the corresponding <layout name=...> block, change Button_Small_name to Button_Small_source, and save the changes.
Alternatively:
You can completely remove the Zap-History Browser plugin skins (ZapHistoryBrowser and ZapHistoryConfigurator) so that the updated default skin will be used instead.
-
New Update (6)
- Added a setting to show/hide the event progress bar.
- Minor fixes and improvements.
Download the updated file from the #1 post.
-
New Update (5)
- A new option to display Picons has been added. You can enable or disable it from the plugin setup.
- A progress bar has also been added to show the current event progress
You can customize the list appearance through the skin file, including:
- Adjusting Picon sizes.
- Changing the colors of the event name text and progress bar.
Example skin component configuration:
Code
Display More<component type="ZapHistoryBrowserList" itemHeight="72" itemWidth="1160" lineSpacing="1" serviceNameHeight="35" eventNameHeight="30" piconWidth="100" piconHeight="50" piconYOffset="4" progressWidth="100" progressHeight="16" progressYOffset="3" eventNameColor="#aaaaaa" progressColor="#aaaaaa" progressBackColor="#ffffff" /> -
Important: If you are using the scan_tp_valid_check.py file located in /etc/enigma2, make sure to use the updated version of the ServiceScan.py file.
This update prevents crashing during manual search for incorrect frequencies via Satfinder plugin, making the search process more stable.
Replace the ServiceScan.py file in the following directory:
Code/usr/lib/enigma2/python/Components -
Hi,
I’ve made a few simple enhancements to the Satfinder plugin:
-
Added Scan Functionality
Pressing OK now launches the ServiceScan screen to start scanning the selected transponders.
-
Blue Button Action
The Blue Button triggers an immediate retune to quickly check the signal before running a full scan.
🔧 Installation Note
Replace the plugin.py file in the following directory:
Code/usr/lib/enigma2/python/Plugins/SystemPlugins/SatfinderBest regards.
-
-
New Update (3)
- Modified the channelSelected function in the ChannelSelectionRadio class to include service validity checks using if ref and ref.valid().
Download the updated file from the #1 post.
-
New Update (4)
- Additional fixes and performance improvements.
Download the updated file from the #1 post.
🔧 Note: The plugin still needs further improvements, such as:
-
Displaying orbital position
-
Bouquet name
-
Event start and end times
-
Remaining time & progress bar
-
Picons
-
And more...
I’ve implemented some important fixes, and I hope it’s now working more reliably for everyone.
Best regards.
-
New Update (3)
- Additional fixes and performance improvements.
Download the updated file from the #1 post.
-
The plugin location has not changed, it is the same as in the Extensions menu.
-
New Update (2)
- Added a setting to show/hide the service number.
-
Hi,
I’ve made several improvements and fixes to the Zap-History Browser plugin to enhance performance and user experience.
🔹 Key Updates Include:
Flexible History Sorting
-
Most Recent: Displays recently viewed services first.
-
Alphabetical (A–Z): Sorts services by name.
-
Numeric: Orders services by their bouquet/service number.
Quick Access to Event Information
-
Event View Mode: Press the "Info" button to view details of the current event.
-
EPG Selection Mode: Access the full Electronic Program Guide (EPG) for the selected service.
Enhanced Skin Support
-
Added support for multiple screen resolutions: 2560, 1920, and standard.
🔧 Installation Note:
If you’re already using the plugin, replace the plugin.py file in the following directory:
Code/usr/lib/enigma2/python/Plugins/Extensions/ZapHistoryBrowserBest regards.
-
-
Hi,
I’ve improved the StartUpService plugin to provide a more stable and reliable experience when selecting a startup service.
An extra validation step has been added to the channel context menu to ensure that the selected service (such as a TV or radio channel) is both present and valid before it can be added to the "set as startup service" or "reset startup service" options.
What Does This Mean?
- Improved User Experience: The menu options will only appear for valid services, reducing confusion and enhancing the plugin’s reliability.
- Compatibility: The plugin’s functionality remains unchanged, but it is now more reliable in handling unexpected scenarios.
Best regards.
-
-
I agree that pressing "OK" or "Info" in an empty directory may be uncommon for experienced users who typically avoid such actions. However, this doesn’t mean the issue is nonexistent or unworthy of a fix.
Addressing this issue improves system reliability, especially for new users who might accidentally press these buttons, preventing the current service from stopping (when pressing "OK") or displaying an empty EPG Selection screen for invalid services, directories, or markers (when pressing "Info").
The modifications to showEPGList and channelSelected are simple checks (e.g., ref.valid() and excluding directories/markers) that leverage standard Enigma2 functions. These checks do not alter core system behavior; they only prevent actions for invalid cases, ensuring stability.
-
Creating custom images for each available device requires a lot of time, effort, and unfortunately, I just don’t have the time for that at the moment.
I recommend reaching out to teams that still support DreamOS images, like Gemini Project or Dream-Elite. They have experienced developers who are better equipped to handle these kinds of tasks.
Regarding the FFmpeg and GstPlayer updates, unfortunately, the protection mechanisms aren't what they used to be. Some plugins that were originally made exclusively for DreamOS images have been cracked and later used in open-source images.
While the process isn’t overly complicated, it’s still in the testing phase and hasn’t become widely adopted yet. A few hobbyist developers have managed to get some initial results. Some even tried to contribute and interact with the Enigma2 forums, but they were pushed back.!
For now, I can't help with this, and these updates definitely won’t be released from my side.!