[GiGaBlue UHD UE 4K] Content not accessible

[avalon65]

Yes I appreciate that , but as the error message has been appearing every day for the last few weeks, there is no debug log any other times. But I'll check again tomorrow morning.

 

[Huevos]

If you set up the debug logs they should run permanently. Use a pen drive and make sure you have set them up to write to /media/usb.

 

[avalon65]

The logs are now set to write to an 8Gb USB stick, after a reboot.

 

[avalon65]

After the said error message appeared again earlier, I went to check the debug logs and there wasn't one for today

 

[Huevos]

After the said error message appeared again earlier, I went to check the debug logs and there wasn't one for today

The date of the debug log filename is when it was created which would have been yesterday.

 

[avalon65]

Ok but there i only this one which was created after a reboot yesterday afternoon: Ever since the error message has appeared there has not been any debug file as I know of

 

[avalon65]

The receiver is now showing this screen, and there is no log for or about it.
It's like the receiver has a mind of its' own! The previous error message is now. not showing When I turned off the tv last night, the screen was normal, but now it is like someone has pressed a button on the remote to bring up this screen???

 

[avalon65]

20 minutes after I put the screen back to normal, it went to this now::

 

[cactikid]

Did you press the radio button? press tv button to revert to tv channels as sometimes i like some music instead.

 

[avalon65]

No I didn't press any buttons on the remote as I went to OW and clicked on the TV button for the remote. Anyway, I have since flashed the receiver with the latest image 6.4.003, and the problem seems to have gone away now, with no error messages nor any other strange things happening.

Thanks

 

[Huevos]

The ABM run is happening because you programmed it that way and lately one of the transponders it is searching is a bit weak. Are you searching terrestrial? Maybe a tree is blocking a bit of signal.

This other problem is something different. Either:

1. The dog stepped on the remote, or
2. Something in the room is sending commands that conflict with this equipment, or
3. Your remote control is knackered, maybe a stuck button, or
4. Your receiver is knackered.

Whatever it is it is not a software problem.

 

[avalon65]

Ok, but how do I program the ABM, like what settings should I change. I just left it at the default setting AFAIK

I don't have a dog.
Whatever was sending commands which conflict with the equipment, it iis not doing it now
The remote is only 5 months old
And the receiver is almost 1 year old

As I said earlier, I flashed the receiver with the latest image 6.4.003, and noting untoward has happened since I did it.

Thanks

 

[Huevos]

Ok, but how do I program the ABM, like what settings should I change. I just left it at the default setting AFAIK

You obviously didn't leave it as default because those aren't the default settings... but as you are not able to provide a log it is not possible to help.

As I said earlier, I flashed the receiver with the latest image 6.4.003, and noting untoward has happened since I did it.

It is not a software problem.

 

[avalon65]

No, you are right, I was not thinking properly, I didn't leave ABM as default, but set it up for my providers etc and the epg is set to download at 01.00am now

I cannot provide a log because as I have said before, no logs were generated for the initial error message. it is beyond me why this is so.

I have never said it was a software problem, just that the error message seemed to have only started since I flashed the receiver with the 6.4.002 image. Coincidence or what?
Now it is flashed with 6.4.003 image there are no error messages, nor anything else wrong ,m so I don't need any help now.

 

[Huevos]

Please provide a screen grab of your logs settings.

 

[avalon65]

Log settings as requested:

 

[Huevos]

Then there should be logs in /media/usb/logs.

 

[avalon65]

Yes there are 2 debug logs. 1 is for when I did the upgrade and the other is for an earlier reboot.