Aglare FHD by MNASR

Thanks for your quick response.

The issue seems to be with the image, as it also appears in the default skin.

3.jpg

Quote from giorbak

Thanks for your quick response.

The issue seems to be with the image, as it also appears in the default skin.

It looks like you used some script to create additional slots.

It is possible that they are not mounted correctly in the device manager.Therefore they are out of order.

All partitions are correctly mounted in the fstab file. I have 50 slots on Octagon sf8008 and 30 slots on Edision osmio4kplus.

I didn't use a script to create the slots, but did them manually with the program "Partition Wizard"; also manually the STARTUP files.

The order of images in the "Image Backup" window is: 1, 10-19, 2, 20-29, 3, 30-39, 4, 40-49, 5, 50, 6-9 (they are not mixed up).

As you can see, the problem is due to OpenATV that not numbering the slots correctly.

If I remember correctly, in the old OpenATV versions, there was the same issue with "Multiboot Manager" and was fixed some time ago.

To verify what I wrote in my previous post, I installed an old OpenATV file (version 7.2) on the Edision osmio+, and here are the results.

1.jpg  2.jpg  3.jpg

Quote from giorbak

To verify what I wrote in my previous post, I installed an old OpenATV file (version 7.2) on the Edision osmio+, and here are the results.

1.jpg  2.jpg  3.jpg

I think the point is not related to the skin or image itself, it is related to your methodology.

I am following another road

1. Using plugin called Multiboot flashonline 7.2, which format and generate partitions.

2. Use device manager or direct edit my fstab file to make organized and visible.

Regards

IMG_20250518_091125.jpg

I think I was misunderstood. I said that the problem with the "Multiboot Manager" existed in the old versions of OpenATV.

It has been fixed a couple of years now. However, it still remains in the "Image Backup".

I'm uploading the fstab files for sf8008 and osmio4kplus:

1.jpg

Quote from giorbak

I think I was misunderstood. I said that the problem with the "Multiboot Manager" existed in the old versions of OpenATV.

It has been fixed a couple of years now. However, it still remains in the "Image Backup".

I'm uploading the fstab files for sf8008 and osmio4kplus:

1.jpg

Display More

Your fstab is not correct and will not give your the correct order

Please have a look on the post below

Quote from Mahmoud Hussein

Mount System with Fstab

What does "mount" mean in the Enigma2 system?

It’s a word that means connecting or linking your memory storage, referring to the process of attaching storage media used to install various systems. In other words, if you have an operating system like Enigma2 and want to add a hard disk (HDD) or USB drive to it, you must define the HDD or USB to the system so that it recognizes it, displays it among its contents, and can interact with it.

90% of the problems with Multiboot plugins like Barry Allen, Neutrino, and MultiBoot are caused by issues in the mounting process with storage media (such as HDDs or USBs) and the primary system through which the mount is performed.

One of the most annoying issues I’ve encountered is why the current system doesn’t recognize other systems when using a multiboot setup. For example, if you have 12 images (system installations) on your device, why don’t the files stored on the storage media appear in the currently running image?

1.png

2.png

Well, why would you want to see the files from other images? The truth is, the reason is simple: laziness. For instance, when an update is released for a plugin like AJPanel, instead of reinstalling it on each image separately, I just copy the updated file and paste it into the corresponding path in the other images. Then, when I switch to another image, the plugin is already updated, and the issue is resolved.

The idea isn’t just limited to plugin updates—you can transfer plugins, boot logos, skins, settings, and anything else, as long as you know what you’re doing.

Note

Any Enigma2 image requires two partitions—one with a size of 16 MB and another with 2024 MB. The main image files are installed on the larger partition.

Once you finish adjusting all your mount points, restart the device. After the boot process completes, go to a file called fstab, located in the following path:

<span style="font-size: 12pt;"><em><span style="color:#00FF00;">/etc/fstab</span></em></span><span style="color:#FF0000;"><span style="font-size: 12pt;"><em></em></span></span>

But what if the current image doesn’t see the other images? There are two ways to fix this:

1. Using a tool like Mount Manager or Device Manager: Through these tools, you set up the mount points and assign a specific name to each available storage device on your system. This helps the image recognize them.

3.png

Press the OK) key on any partition with 2.15 GB to mount it and ignore the 16.78 MB Partitions

4.png

Congratulation

Now all your partitions are saved successfully in fstab file located in /etc/

This file is the registry where all mount points are recorded. If the entries in this file are correctly written, you can easily take a copy of it and paste it into the same path in all the images you want.

2. Direct Edit for your Fstab file.

Using any text editor like notpad++ open your fstab file located in (/etc/), just add same sequence and note sda = SDcard, sdb = HDD, sdc= Flash disk)

5.png

Sorry for the long post, and I hope you find it useful!

Best regards.

Display More

Also have a look on the attached fstab for my sf8008

Regards

My fstab files are 100% correct. You can verify that in the following images.

You're using UUID for mounting, which is the recommended method, but using the partition name (e.g., sda1) works perfectly fine.

I have no issues with the Multiboot Manager in any image. All of them display the correct order for the images.

There is only a problem with the Image Backup in OpenATV.

I see that you have OpenATV-7.6. Did you try to do a Full Backup with it? If so, what does it show? Share a screenshot.

1.jpg  2.jpg  3.jpg

4.jpg  5.jpg  6.jpg

Hi odem2014

Could you fix the information window that resizes based on the content?

If the information is too long, it exceeds the screen limits, making it unreadable.

Can you restrict it within the screen boundaries and enable text wrapping if it is too long?

Thanks

7.jpg     8.jpg

9.jpg     10.jpg

Mahmoud Hussein

You might object to the fact that I am not using UUID for mounting partitions (I repeat, that's the correct way). The reason is simply that I don't need it.

As you can see, I'm using only one drive for slots, and the HDD is part of the card, so I get the same results as with UUID since the system reads it as sda.

If I had 2-3 storage drives connected at the box's startup, I would have to use UUID for the system to know which is which.

If I want to connect some extra USB sticks, I do it after the image boots, so they get mounted as sdb, sdc, etc.

Hello odem2014

Can I get in the queue and ask for bigger blindscan screens, like in the default skin?

aglare_bs1.jpg     metrix_bs1.jpg

aglare_bs2.jpg     metrix_bs2.jpg

Thanks in advance!

crash when playing a recorded movie

openatv 7.5.1

i think it is skin related..

13:15:59.9636 [Enigma] Python path is '/usr/lib/enigma2/python'.
13:15:59.9641 [Enigma] DVB API version 5, DVB API version minor 12.
13:15:59.9642 [Enigma] Enigma debug level 3.
13:15:59.9643 [Enigma] sourcedate 2025-03-15 / master 34081+a3f8b1a.
13:16:40.1029 [eDVBPESReader] Created. Opening demux
13:16:40.1033 [eDVBPESReader] Created. Opening demux
14:08:51.0476 eServiceApp::enableSubtitles - track is not in the map!
14:09:07.3011 eServiceApp::enableSubtitles - track is not in the map!
14:09:09.4020 [eDVBPESReader] Created. Opening demux
14:09:09.4027 [eDVBPESReader] Created. Opening demux
14:58:19.7351 Traceback (most recent call last):
14:58:19.7357   File "/usr/lib/enigma2/python/skin.py", line 2172, in processWidget
14:58:19.7364 KeyError: 'chapterLabel'
14:58:19.7375 
During handling of the above exception, another exception occurred:

14:58:19.7379 Traceback (most recent call last):
14:58:19.7383   File "/usr/lib/enigma2/python/skin.py", line 2309, in processScreen
14:58:19.7385   File "/usr/lib/enigma2/python/skin.py", line 2174, in processWidget
14:58:19.7392 skin.SkinError: [Skin] Error: Component with name 'chapterLabel' was not found in skin of screen 'MoviePlayer'!
14:58:19.7520 Traceback (most recent call last):
14:58:19.7524   File "/usr/lib/enigma2/python/skin.py", line 2172, in processWidget
14:58:19.7526 KeyError: 'subtitleLabel'
14:58:19.7529 
During handling of the above exception, another exception occurred:

14:58:19.7531 Traceback (most recent call last):
14:58:19.7534   File "/usr/lib/enigma2/python/skin.py", line 2309, in processScreen
14:58:19.7535   File "/usr/lib/enigma2/python/skin.py", line 2174, in processWidget
14:58:19.7538 skin.SkinError: [Skin] Error: Component with name 'subtitleLabel' was not found in skin of screen 'MoviePlayer'!
14:58:19.7635 Traceback (most recent call last):
14:58:19.7638   File "/usr/lib/enigma2/python/skin.py", line 2172, in processWidget
14:58:19.7640 KeyError: 'audioLabel'
14:58:19.7642 
During handling of the above exception, another exception occurred:

14:58:19.7643 Traceback (most recent call last):
14:58:19.7645   File "/usr/lib/enigma2/python/skin.py", line 2309, in processScreen
14:58:19.7647   File "/usr/lib/enigma2/python/skin.py", line 2174, in processWidget
14:58:19.7649 skin.SkinError: [Skin] Error: Component with name 'audioLabel' was not found in skin of screen 'MoviePlayer'!
14:58:19.7739 Traceback (most recent call last):
14:58:19.7742   File "/usr/lib/enigma2/python/skin.py", line 2172, in processWidget
14:58:19.7745 KeyError: 'Cover'
14:58:19.7749 
During handling of the above exception, another exception occurred:

14:58:19.7750 Traceback (most recent call last):
14:58:19.7753   File "/usr/lib/enigma2/python/skin.py", line 2309, in processScreen
14:58:19.7754   File "/usr/lib/enigma2/python/skin.py", line 2174, in processWidget
14:58:19.7756 skin.SkinError: [Skin] Error: Component with name 'Cover' was not found in skin of screen 'MoviePlayer'!
14:59:00.4876 Traceback (most recent call last):
14:59:00.4881   File "/usr/lib/enigma2/python/skin.py", line 2359, in readSkin
14:59:00.4883   File "/usr/lib/enigma2/python/skin.py", line 2309, in processScreen
14:59:00.4886   File "/usr/lib/enigma2/python/skin.py", line 2242, in processWidget
14:59:00.4889   File "/usr/lib/enigma2/python/Components/Converter/ServicePosition.py", line 60, in __init__
14:59:00.4892 Components.Element.ElementError: type must be {Length|Position|Remaining|Gauge|Summary} with optional arguments {Negate|Detailed|ShowHours|ShowNoSeconds|ShowNoSeconds2} for ServicePosition converter
15:02:51.9618 Traceback (most recent call last):
15:02:51.9623   File "/usr/lib/enigma2/python/skin.py", line 2359, in readSkin
15:02:51.9625   File "/usr/lib/enigma2/python/skin.py", line 2309, in processScreen
15:02:51.9628   File "/usr/lib/enigma2/python/skin.py", line 2242, in processWidget
15:02:51.9630   File "/usr/lib/enigma2/python/Components/Converter/ServicePosition.py", line 60, in __init__
15:02:51.9633 Components.Element.ElementError: type must be {Length|Position|Remaining|Gauge|Summary} with optional arguments {Negate|Detailed|ShowHours|ShowNoSeconds|ShowNoSeconds2} for ServicePosition converter
15:02:52.1264 Traceback (most recent call last):
15:02:52.1266   File "/usr/lib/enigma2/python/Screens/MovieSelection.py", line 734, in LivePlay
15:02:52.1350   File "/usr/lib/enigma2/python/Navigation.py", line 321, in playService
15:02:52.1361   File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 228, in streamrelayChecker
15:02:52.1391 AttributeError: 'NoneType' object has no attribute 'toCompareString'
15:02:52.1393 [ePyObject] (PyObject_CallObject(<bound method MovieSelection.LivePlay of <class 'Screens.MovieSelection.MovieSelection'>>,()) failed)

In the latest version, the primary infobar does not display the correct audio carrier. The audio codec is displayed, but not the audio carrier.

After trying the latest version Aglare-FHD v5.7.

The device has become heavy in the channel list, unlike the previous version, which was light and smooth.

The device is: Novaler Pro 4K

Egami 10.6-R10

5.7 with the next update on the open ATV feed

thx @ odem2014