Skip to content
More languages

Translate automatically from English. Screenshots and search terms remain English.

Google Translate loads after you choose a language.

English original

Logs Settings

This reference contains the help text provided by OpenATV. The open dialog and selected options determine which entries are visible.

Main Menu → Setup → System → Logs Settings

Search also matches technical keys. Back to the directory

Logs location

Choose the location for crash and debug logs.

Reference & notes

config.crash.debug_path

Setup level: Expert.

Handle Python crashes

Try to prevent reboots for software errors and maintain of the availability for the receiver.

Reference & notes

config.crash.bsodpython

Setup level: Expert.

Show crash info on screen and write crash log for x times

If 'never', will write crash log despite that for the first crash.

Reference & notes

config.crash.bsodhide

Setup level: Expert.

Visibility depends on other options or the dialog.

Restart GUI after x crashes

If 'never', will force restart despite that after 100 crashes.

Reference & notes

config.crash.bsodmax

Setup level: Expert.

Visibility depends on other options or the dialog.

Enable debug log *

Allows you to enable the debug log. They contain very detailed information of everything the system does.

Reference & notes

config.crash.debugLevel

Setup level: Expert.

Include international data *

Enable this option to add international language and country load information detected during system boot to the debug log file.

Reference & notes

config.crash.debugInternational

Setup level: Expert.

Include MultiBoot data *

Enable this option to add MultiBoot information detected during system boot to the debug log file.

Reference & notes

config.crash.debugMultiBoot

Setup level: Expert.

Include keyboard data

Enable this option to add keyboard key map data to the debug log file.

Reference & notes

config.crash.debugKeyboards

Setup level: Expert.

Include remote control data

Enable this option to add remote control data to the debug log file.

Reference & notes

config.crash.debugRemoteControls

Setup level: Expert.

Include action map data

Enable this option to add action map / remote control mapping data to the debug log file.

Reference & notes

config.crash.debugActionMaps

Setup level: Expert.

Include screen load data

Enable this option to add screen names and resolution data to the debug log file.

Reference & notes

config.crash.debugScreens

Setup level: Expert.

Include opkg output data

Enable this option to add opkg output data to the debug log file.

Reference & notes

config.crash.debugOpkg

Setup level: Expert.

Include timer data

Enable this option to add timer debugging data to the debug log file.

Reference & notes

config.crash.debugTimers

Setup level: Expert.

Include seek data

Enable this option to add seek/time shift debugging data to the debug log file.

Reference & notes

config.crash.debugSeek

Setup level: Expert.

Include EPG data

Enable this option to add extra EPG data to the debug log file.

Reference & notes

config.crash.debugEPG

Setup level: Expert.

Include DAB+ data

Enable this option to add detailed DAB+ receiver, packet, MOT and SPI information to the debug log file.

After changing: GUI restart required.

Reference & notes

config.crash.debugDAB

Setup level: Expert.

Include DVB scan data

Enable this option to add extra DVB scan data to the debug log file.

After changing: GUI restart required.

Reference & notes

config.crash.debugDVBScan

Setup level: Expert.

Include DVB timesync data

Enable this option to add extra DVB time sync data to the debug log file.

After changing: GUI restart required.

Reference & notes

config.crash.debugDVBTime

Setup level: Expert.

Include DVB details

Enable this option to add extra DVB details to the debug log file.

After changing: GUI restart required.

Reference & notes

config.crash.debugDVB

Setup level: Expert.

Include teletext details

Enable this option to add extra teletext details to the debug log file.

After changing: GUI restart required.

Reference & notes

config.crash.debugTeletext

Setup level: Expert.

Include storage device data

Enable this option to add storage device information detected during system boot and hot plug events to the debug log file.

Reference & notes

config.crash.debugStorage

Setup level: Expert.

Include bouquet DB data

Enable this option to add bouquet database information to the debug log file.

After changing: GUI restart required.

Reference & notes

config.crash.debugDVBDB

Setup level: Expert.

Include text encoding data

Enable this option to add text encoding information to the debug log file.

After changing: GUI restart required.

Reference & notes

config.crash.debugTextEncoding

Setup level: Expert.

Include network data

Enable this option to add network information to the debug log file.

After changing: GUI restart required.

Reference & notes

config.crash.debugNetwork

Setup level: Expert.

Include SEC/DiSEqC data

Enable this option to add verbose SEC/DiSEqC debug data to the debug log file.

Reference & notes

config.crash.debugSec

Setup level: Expert.

Limit debug log size (MB)

Allows you to set the maximum size of the Debug log size (MB). When that size is reached, a new file will be created.

Reference & notes

config.crash.debugloglimit

Setup level: Expert.

Show Log Manager in Extension Menu

Allows you to show/hide Log Manager in the Extension Menu screen (BLUE button).

Reference & notes

config.logmanager.showinextensions

Setup level: Expert.

Maximum no of days

Logs older then the set no of days will be deleted.

Reference & notes

config.crash.daysloglimit

Setup level: Expert.

Maximum space used (MB)

If logs are using the set maximum space used the eldest will be deleted.

Reference & notes

config.crash.sizeloglimit

Setup level: Expert.

Crash at skin error for debug reasons

Select 'No' to only write a log message to the debug log file.

Reference & notes

config.crash.skin_error_crash

Setup level: Expert.

Log python stack trace on spinner

Set to yes for debugging the root cause of a spinner.

Reference & notes

config.crash.pystackonspinner

Setup level: Expert.

Debug log time format *

This sets the prefix for each line in the debug log. The 'Boot time' is the number of seconds since your OpenATV was last booted.

Reference & notes

config.crash.debugTimeFormat

Setup level: Expert.

Enable GStreamer debug log *

Allows you to enable the GStreamer debug log. They contain very detailed information of everything the GStreamer system does.

Reference & notes

config.crash.gstdebug

Setup level: Expert.

GStreamer debug log category *

Only log debug information of GStreamer category. * means all categories.

Reference & notes

config.crash.gstdebugcategory

Setup level: Expert.

Visibility depends on other options or the dialog.

GStreamer debug log level *

Detail of GStreamer log.

Reference & notes

config.crash.gstdebuglevel

Setup level: Expert.

Visibility depends on other options or the dialog.

Enable GStreamer pipeline graphs *

Allows you to enable the GStreamer pipeline graphs. These are .dot files that describe the topology of your pipeline, along with the caps negotiated in each link.

Reference & notes

config.crash.gstdot

Setup level: Expert.

Enable core dumps *

Core dumps are helpful for developers in case of a FATAL SIGNAL crash in the C++ code. Typical core dump size is 110 MB so adjust maximum space used and choose proper location.

Reference & notes

config.crash.coredump

Setup level: Expert.


Source: OpenATV setup.xml · fdc9347241.