zombi

Let’s keep things in perspective. It’s not a major system change.

Developer changes are optional. Anyone who prefers the original can still use it, nothing is forced.

What you might see as "bloat" might be very useful to others, and that's the beauty of open development, where everyone can choose what works best for them. No one is forced to use it, as the developer explained, these changes do not affect the system in any harmful way.

From my experience with his modifications, I haven’t encountered any problems, and in fact, I’ve found it more practical and useful than the original.

Constructive feedback is always welcome, but personal preferences shouldn’t be imposed as general rules. Different users have different needs.

It's like trying to fix the door of a haunted house! It's better to put your energy into an active community!

I've switched to openATV 7.6 Beta!

Although it's not as fast as DreamOS, and my DM520 has limited capabilities...

👉 I finally got what I wanted!

✅ Python 3 updated

✅ FFmpeg updated

✅ GStreamer updated

✅ YouTube now works in Full HD with both video and audio, and DASH support! 🚀

Maybe it’s time to add a "Discover More" to open-source images now! 😉

Like I said before, there are no active teams working on DreamOS anymore. That ship sailed a long time ago, there's nothing new. Nothing coming. Period.

It's clear that some of them here don't care about fixes or improvements. They just sit around criticizing without doing anything useful. They don’t even appreciate your efforts!

Even the most disliked guy in the entire Enigma2 community is laughing at your comment He's the same guy known for being toxic and completely out of touch

Why don't you create an image that includes these fixes and improvements?!

Since the DreamOS image is no longer closed source, why not do that along with updating FFmpeg and GstPlayer?!

Quote from dhwz

Actually no they're not, the trailers are from an external plugin and the video source is YouTube.

I'm using IMDb_v0.1-r17, and the trailers play without any external plugins. The trailers shown are those available on IMDb.

alpha

The trailer videos are from IMDb, not YouTube.

Andro1

As you can see, there are currently no active developers. If you would like to continue supporting the plugin in your own way, we would be grateful. Otherwise, it will no longer receive any updates or support.

Hi Andro1

I was wondering if there's a way to improve the quality of the trailer videos, and if a photo browsing section could be added.

Thanks in advance.

You might have to wait for the Dreambox Seven 8K UHD or Dreambox Play More 8K UHD, whatever it's called.

Chipset : Amlogic S928X 5 Core ARM G57 MC2

WIFI : WiFi 6

RAM : DDR4 4GB/8GB

ROM : eMMC 32GB/64GB/128GB

OS : DreamOS/Android 11.0

Ethernet: 1000M Standard RJ-45

Bluetooth: BT 5.4

Andro1

Thanks for sharing this plugin. It works great for me.

This feature should have been in DreamOS settings a long time ago.!

@Andro1

I'm not a developer, but I tested the modified code for a change!

- Channels with out‑of‑sequence EPG timings didn’t show up in the upcoming events list before, after the modification, they now show up correctly.

- Also, the duration was shown only in minutes, now it's shown in both hours and minutes.

Well done!

Quote from dhwz

Thats hardly possible (especially regarding hardware), it was your own fault buying an outdated DM520 instead of newer Amlogic based hardware.

My decision wasn't just about the DM520. Even if I had chosen a newer Dreambox model, the overall ecosystem, software support, and community engagement were key factors in my decision.
Hardware alone doesn't make a device superior if the software development and support are lacking. I prefer to move to a platform that aligns better with my needs.

Andro1

After running the command you mentioned, I got the following result:

Jan 31 20:42:12 dm520 enigma2[150]: OpenGL ES not supported by hw

It looks like the device does not support OpenGL ES after all.

ConfigEnableDisable warning has been resolved.

Skin error has been resolved.

I think my experience with Dreambox has come to an end, and I'll switch to another device with better hardware, more support, and active development.

Thank you for your help!

dhwz
Your responses do not help me understand the results I got.

You're suggesting that I have a problem understanding the meaning of these warnings or errors, and that my interest in understanding the reasons behind these results isn't important to me as a user!!

Could you please explain how you arrived at these conclusions?!

If you could help me understand the reasons behind these results and possible solutions, it would be incredibly helpful.

If your focus is on assessing my understanding or the reason for my interest, it might be more helpful to refrain from further comments on that.

Quote from dre

Generate them yourself? If warnings that do have zero impact on any functionality of your dreambox are an issue for you, then it's a simple two liner (and one import) to get rid of most of them. E.g. the icons for reception type have been added that skinners who would like to show them in channellist can do that easily but they have never been included by default.

This is a warning that is very helpful and tells devs that they should no longer use ConfigEnableDisable. This is not a but but a very important information.

Well, regarding the messages about the missing UI files, they can be added easily. However, what I meant is that as long as these files are defined in the system, they should be included with the image. Or if the developer doesn’t want to add them, they could be referenced as an informational message or a warning, not as a failed message as if they are critical and required by the system!

As for other messages like 'VIDEO0 got pts failed,' 'RFKILL,' 'Harddisk.py,' 'eStaticServiceDVBBouquetInformation,' 'eglGetError,' 'eglGetDisplay,' etc., are they related to issues with the drivers, kernel, or something else?

This is not my problem, it's an issue with the image and the default skin.

The developer added 9 "wait" files to the spinner folder, and now the system is telling me that the file wait10.png is missing. How can I get it?!

The developer did not add the file notification_mail.png. How can I get it?!

The developer did not add the files (ico_dvb_s-fs8, ico_dvb_c-fs8, ico_dvb_t-fs8, ico_service_group-fs8). How can I get them?!

The developer did not add RassLogo and state. How can I get them?!

This is the developer's issue; they defined the files but didn't add them.

Recently, I installed the Zombi-Shadow-FHD skin, and the system is telling me that the extvolumeText render is missing, but when I searched inside the skin, I found it in its correct place! How could this happen?!

The problems are related to the mistakes of the previous developers who are now gone, leaving us with these annoying issues.

I used commands to check whether the DM520 has any errors, and the results are as follows:

journalctl | grep -i "failed" >> /media/hdd/failed.log &

Jan 01 02:00:15 dm520 kernel[145]: [    9.587000] VIDEO0 got pts failed !!!! (ret 0)
Jan 01 02:00:16 dm520 connmand.real[144]: Failed to open RFKILL control device
Jan 26 15:42:50 dm520 enigma2[150]: gPixmap: Failed to access '/usr/share/enigma2/skin_default/spinner/wait10.png': No such file or directory
Jan 26 15:42:57 dm520 enigma2[150]: gPixmap: Failed to access '/usr/share/enigma2/skin_default/icons/notification_mail.png': No such file or directory
Jan 26 15:43:07 dm520 enigma2[150]: gPixmap: Failed to access '': No such file or directory
Jan 26 15:43:10 dm520 enigma2[150]: gPixmap: Failed to access '/usr/share/enigma2/ico_dvb_s-fs8.png': No such file or directory
Jan 26 15:43:10 dm520 enigma2[150]: gPixmap: Failed to access '/usr/share/enigma2/ico_dvb_c-fs8.png': No such file or directory
Jan 26 15:43:10 dm520 enigma2[150]: gPixmap: Failed to access '/usr/share/enigma2/ico_dvb_t-fs8.png': No such file or directory
Jan 26 15:43:10 dm520 enigma2[150]: gPixmap: Failed to access '/usr/share/enigma2/ico_service_group-fs8.png': No such file or directory
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/platform/brcmnand.0/mtd/mtd1/mtdblock1/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/platform/spi_brcmstb.0/spi_master/spi0/spi0.0/mtd/mtd3/mtdblock3/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/platform/brcmnand.0/mtd/mtd0/mtdblock0/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/platform/brcmnand.0/mtd/mtd2/mtdblock2/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop1/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop2/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop0/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop4/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop3/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop5/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop6/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/mtd/mtd4/mtdblock4/partition
Jan 26 15:43:14 dm520 enigma2[150]: Harddisk.py: failed to read /sys/devices/virtual/block/loop7/partition
Jan 26 15:51:57 dm520 enigma2[150]: getting program info failed.
Jan 26 15:52:20 dm520 enigma2[150]: getting program info failed.
Jan 26 15:52:24 dm520 enigma2[150]: getting program info failed.
Jan 26 15:52:40 dm520 enigma2[150]: getting program info failed.
Jan 26 15:53:42 dm520 enigma2[150]: getting program info failed.
Jan 26 15:54:19 dm520 enigma2[150]: eStaticServiceDVBBouquetInformation::getName failed.. getBouquet failed!
Jan 26 15:54:20 dm520 enigma2[150]: eStaticServiceDVBBouquetInformation::getName failed.. getBouquet failed!
Jan 26 15:55:57 dm520 enigma2[150]: eStaticServiceDVBBouquetInformation::getName failed.. getBouquet failed!
Jan 26 15:55:58 dm520 enigma2[150]: eStaticServiceDVBBouquetInformation::getName failed.. getBouquet failed!
Jan 26 15:59:07 dm520 systemd-tmpfiles[2076]: Failed to open directory /var/tmp: Too many levels of symbolic links

journalctl | grep -i "error" >> /media/hdd/error.log &

Jan 26 15:42:49 dm520 enigma2[150]: EGL Error: 0 ((null))
Jan 26 15:42:49 dm520 enigma2[150]: WARNING: eglGetError not implemented!
Jan 26 15:51:57 dm520 kernel[145]: [  565.637000] audio ch0: pts error 0 PTS 0x78cf7e9e, STC 0x78cf600c, type 0
Jan 26 15:54:14 dm520 kernel[145]: [  692.228000] audio ch0: pts error 0 PTS 0x1c4a1776, STC 0x1c4a15c8, type 0
Jan 26 15:54:14 dm520 kernel[145]: [  692.440000] audio ch0: pts error 1 PTS 0xd89e995e, STC 0xd89e9502, type 0
Jan 26 15:54:15 dm520 kernel[145]: [  693.232000] audio ch0: reset pts error counter

journalctl | grep -i "warning" >> /media/hdd/warning.log &

Jan 26 15:42:49 dm520 enigma2[150]: WARNING: eglGetDisplay not implemented!
Jan 26 15:42:49 dm520 enigma2[150]: WARNING: eglGetError not implemented!
Jan 26 15:43:08 dm520 enigma2[150]: WARNING! ConfigEnableDisable is deprecated, please use ConfigOnOff instead!
Jan 26 15:43:11 dm520 enigma2[150]: warning, skin is missing element RassLogo in <class 'Screens.RdsDisplay.RdsInfoDisplay'>
Jan 26 15:43:11 dm520 enigma2[150]: warning, skin is missing element state in <class 'Screens.PVRState.TimeshiftState'>
Jan 26 15:43:13 dm520 enigma2[150]: warning, skin is missing renderer <Components.Renderer.extvolumeText.extvolumeText object at 0x6afd1cb0> in <class 'Screens.Volume.Volume'>
Jan 26 15:52:51 dm520 enigma2[150]: libpng warning: iCCP: known incorrect sRGB profile
Jan 26 15:54:05 dm520 enigma2[150]: libpng warning: iCCP: known incorrect sRGB profile

It kept giving me error messages in /var/log/samba.

Since I don’t use it, I disabled it using the following commands:

systemctl disable nmb
systemctl disable smb

I noticed that there is an issue with the samba file at the path /etc/init.d/samba for the DM520.

The file path is incorrectly written inside the file.

if [ ! -d /usr/bin ]
then                    # /usr not mounted
        exit
fi

killproc() {            # kill the named process(es)
        pid=`/usr/bin/ps -e |
             /usr/bin/grep -w $1 |
             /usr/bin/sed -e 's/^  *//' -e 's/ .*//'`
        [ "$pid" != "" ] && kill $pid
}

When trying to stop the service, I get the following result:

root@dm520:
/etc/init.d/samba stop

/etc/init.d/samba: line 15: /usr/bin/ps: No such file or directory
/etc/init.d/samba: line 16: /usr/bin/grep: No such file or directory
/etc/init.d/samba: line 17: /usr/bin/sed: No such file or directory
root@dm520:

But it seems that this issue has been resolved in DM ONE and DM TWO (Unstable & AIO):

if [ ! -d /bin ]
then                    # /usr not mounted
        exit
fi

killproc() {            # kill the named process(es)
        pid=`/bin/ps -e |
             /bin/grep -w $1 |
             /bin/sed -e 's/^  *//' -e 's/ .*//'`
        [ "$pid" != "" ] && kill $pid
}

I installed Media Portal and entered my API key, but unfortunately, the videos are not working.
It seems that the plugins currently available and working for me are the ones suggested by Andro1. The video quality is 360p when DASH MP4 is not enabled, while some live streams are in high quality.!!