Strange characters in EPG info of some channels

**s3n0** · 02.03.2021, 19:52

When EPG event in your case is simply read(y) in memory, so it's fine.

However, as soon as the data is saved to disk and reloaded, it is corrupted.

This has yet to be verified. So, try this:

switch to the channel on which the EPG events are corrupted to correct the EPG recording for that channel
switch to a different channel, but it must not be a channel on the same satellite transponder
- you can also switch to the previous channel, for example, because this previous channel did not correct all the EPG data while you were on this previous channel before
perform a full reboot of the set-top box
now open the list of channels and check if the EPG data is corrupted (I mean verify the EPG event for the channel that has already been "fixed" before restarting the set top box)

**GH_162** · 02.03.2021, 23:22

Some of those channels are stubborn, EPG doesn't get corrected even after switching several times to them. :-)
I found one that became readable after switching, so I could try the routine above, but sadly it was the same after the reboot.

It's a pity that this is only happening in my favourite image, tried two more multiboot images and all EPG data was normal in both.
Well, it would be nice if it could be fixed in some simple way, but I guess I can live with garbage EPG data of a few channels, instead of reinstalling or switching to another image just for this.

Thanks anyway for trying to help with alternate solutions, much appreciated.

**s3n0** · 03.03.2021, 00:04

And have you tried another version of the oATV ? For example 6.3 version or a new 6.5 test version ? They should also work in Open Multiboot.

You need to check your "epg.dat" file. Also write your channel data - satellite provider name, channel name, satellite position, channel frequency, and so on. But I don't know if there will be anyone who will help you.

The problem requires a system programmer (reading and checking EPG events in Linux system) and at the same time an experienced DVB technology expert

. The Enigma2 / Python programmer is not enough to solve this problem. Must also to be a master in C language and DVB technology (epg event reading). Unfortunately, I only know Enigma / Python. I don't know DVB technology very well.

Maybe someone from the oATV development team will find and fix this BUG.

**GH_162** · 03.03.2021, 18:47

It's very interesting, I tried with 6.3 version in multiboot and EPG was okay there.
I copied the epg.dat of 6.3 to the 6.4 in flash in this way:

init 4 (phutty)
replace epg.dat with filezilla
init 3 (phutty)

All was good at first, but as soon as I zapped to one of problematic channels, its EPG changed and garbage appeared again!
I'm sure there's something wrong with the 6.4 in flash, so I decided to do a flash online with settings backed up.
Don't wanna lose the images in multiboot, so I asked in Octagon SF8008 section if it's possible to do it.
Let's see what other Octagon users will suggest to do.

**tiopedro1958** · 03.03.2021, 19:20

What about the idea to start a Channel Scan and later remove all n/a entries?
And initializing a new epg scan.

**s3n0** · 03.03.2021, 19:26

Well, that's clear

. OpenATV 6.4 has some problem processing or storing EPG events in its own EPG cache.

Will the EPG event start time be corrupted as well? Or are only the letters in the EPG event damaged?

Apparently the correct character set recognition does not work in OpenATV 6.4. I really have no idea.

I don't know if sending a debug-log from the OpenATV + epg.dat file with corrupted letters would help. But you can try

. The debuging must first be enabled in the "system" settings via the GUI MENU and then the device must to be rebooted. After rebooting, an debug-log file will be automatically created in the "/home/root/logs" folder.

**tiopedro1958** · 03.03.2021, 19:34

Just read in another Thread there are 5 different Images in use (Multiboot).
Do they all manage the same epg.dat on its stored place in the same manner?

**GH_162** · 04.03.2021, 15:40

Zitat von s3n0

Will the EPG event start time be corrupted as well? Or are only the letters in the EPG event damaged?

Apparently the correct character set recognition does not work in OpenATV 6.4. I really have no idea.

Yes, sometimes start time and even the content change as well, there's definitely something wrong in EPG system of 6.4, you're right.
I decided to stick with 6.3 for now, it works very well and as an average user, I see no difference at all from 6.4 except the bootlogo. :-)

Zitat von tiopedro1958

Just read in another Thread there are 5 different Images in use (Multiboot).
Do they all manage the same epg.dat on its stored place in the same manner?

No, they all have their own epg.dat file at their own /etc/enigma2 folder.

**GH_162** · 11.03.2021, 16:55

Update:
Today I flashed online the main image 6.4 with the latest available (11.03.2021) with settings backup.
For some reason the hdd (where the settings were stored) was not recognised at first, so I ended up with a fresh image.
Later, I mounted it manually at device manager, but before doing that I wanted to see if garbage EPG would appear on a fresh 6.4, and it did!
I hope someone from the team can find some time to look into this, because there's definitely something wrong with EPG system of 6.4
Back to 6.3 now.

**GH_162** · 16.03.2021, 14:20

Update 2:

It's the same with freshly installed 6.5:

Strange characters in EPG info of some channels-6_5.jpg

And this is how the same screen looks in 6.3:

Strange characters in EPG info of some channels-6_3.jpg

Could it be a font update for both 6.4 and 6.5, but not for 6.3 ?
I can't think of any other reason why this is happening, other images are fine too.
Desperately waiting for a fix in the next updates.

Thema: Strange characters in EPG info of some channels

Themen-Optionen

Anzeige

Stichworte

Lesezeichen

Lesezeichen

Berechtigungen