Android Turn off Debug Logging
#1
I added <loglevel>-1</loglevel> to advancedsettings.xml to turn off logging. But there is a still a log created and it shows

Code:
05:30:01 T:1748520672  NOTICE: Disabled debug logging due to GUI setting. Level -1.
05:30:01 T:1748520672  NOTICE: Log level changed to -1

and continues to show the debug log.

I also checked the guisettings and debugging log is off.

I did the same on my computer and the log stops at
Code:
NOTICE: Log level changed to -1
. Please help identifying how I can turn the log or debug log off.

The log also shows
Code:
05:30:00 T:1748520672  NOTICE: Using Debug XBMC x32 build, compiled Aug 17 2014 by GCC 4.8.0 for ARM Android 32-bit API level 14
, so does that mean that this build has debugging on as default and there is no way to turn it off?

Please help!!
Reply
#2
The normal logfile is always being created by the system. Debug logging shows much more informations than a logfile without debug logging. You can't disabling the creation of a logfile completely. But you already have disabled debug logging. Normal logging is always enabled and can't be disabled. The info you got in the logfile is for the guys who want to read your log if you run into any issues. Therefor a Debug Log is mostly needed.

Hope it helped a bit what the difference between a logfile and a Debug Log is.

Greetings
Reply
#3
(2014-10-26, 00:13)David1977 Wrote: The normal logfile is always being created by the system. Debug logging shows much more informations than a logfile without debug logging. You can't disabling the creation of a logfile completely. But you already have disabled debug logging. Normal logging is always enabled and can't be disabled. The info you got in the logfile is for the guys who want to read your log if you run into any issues. Therefor a Debug Log is mostly needed.

Hope it helped a bit what the difference between a logfile and a Debug Log is.

Greetings

I understand that but even after setting the level to -1, which is actually supposed to turn off the default logging as well, the debug log is still on. I can't find a way to turn it off.
Reply
#4
Do you have any "debug: ........" lines in your logfile? You see the "notice: ...." line? If debug logging is enabled you should see a lot of "debug: ....."lines in your logfile. If you don't see them, then debug logging is disabled.

For being sure just paste a logfile by using pastebin and let us see what the logfile shows completely.

Greetings
Reply
#5
(2014-10-26, 00:30)David1977 Wrote: Do you have any "debug: ........" lines in your logfile? You see the "notice: ...." line? If debug logging is enabled you should see a lot of "debug: ....."lines in your logfile. If you don't see them, then debug logging is disabled.

For being sure just paste a logfile by using pastebin and let us see what the logfile shows completely.

Greetings

Code:
05:30:01 T:1748520672   DEBUG: CPlayerCoreConfig::<ctor>: created player DVDPlayer for core 1
05:30:01 T:1748520672   DEBUG: CPlayerCoreConfig::<ctor>: created player oldmplayercore for core 1
05:30:01 T:1748520672   DEBUG: CPlayerCoreConfig::<ctor>: created player PAPlayer for core 3
05:30:01 T:1748520672   DEBUG: CPlayerSelectionRule::Initialize: creating rule: system rules
05:30:01 T:1748520672   DEBUG: CPlayerSelectionRule::Initialize: creating rule: rtv
05:30:01 T:1748520672   DEBUG: CPlayerSelectionRule::Initialize: creating rule: hdhomerun/myth/mms/udp
05:30:01 T:1748520672   DEBUG: CPlayerSelectionRule::Initialize: creating rule: lastfm/shout
05:30:01 T:1748520672   DEBUG: CPlayerSelectionRule::Initialize: creating rule: rtmp
05:30:01 T:1748520672   DEBUG: CPlayerSelectionRule::Initialize: creating rule: rtsp
05:30:01 T:1748520672   DEBUG: CPlayerSelectionRule::Initialize: creating rule: streams
05:30:01 T:1748520672   DEBUG: CPlayerSelectionRule::Initialize: creating rule: aacp/sdp
05:30:01 T:1748520672   DEBUG: CPlayerSelectionRule::Initialize: creating rule: mp2
05:30:01 T:1748520672   DEBUG: CPlayerSelectionRule::Initialize: creating rule: dvd
05:30:01 T:1748520672   DEBUG: CPlayerSelectionRule::Initialize: creating rule: dvdimage
05:30:01 T:1748520672   DEBUG: CPlayerSelectionRule::Initialize: creating rule: sdp/asf
05:30:01 T:1748520672   DEBUG: CPlayerSelectionRule::Initialize: creating rule: nsv
05:30:01 T:1748520672   DEBUG: CPlayerSelectionRule::Initialize: creating rule: radio
05:30:01 T:1748520672   DEBUG: trying to set locale to en_US.UTF-8
05:30:01 T:1748520672   DEBUG: POParser: loaded 3162 strings from file /data/data/org.xbmc.xbmc/cache/apk/assets/language/English/strings.po
05:30:01 T:1748520672   DEBUG: SECTION:LoadDLL(libavutil-52-arm.so)
05:30:01 T:1748520672   DEBUG: Loading: /data/app-lib/org.xbmc.xbmc-1/libavutil-52-arm.so
05:30:01 T:1748520672   DEBUG: SECTION:LoadDLL(libavcodec-54-arm.so)
05:30:01 T:1748520672   DEBUG: Loading: /data/app-lib/org.xbmc.xbmc-1/libavcodec-54-arm.so
05:30:01 T:1748520672   DEBUG: SECTION:LoadDLL(libavformat-54-arm.so)
05:30:01 T:1748520672   DEBUG: Loading: /data/app-lib/org.xbmc.xbmc-1/libavformat-54-arm.so
any many more from where that came from...
Reply
#6
Could you please paste the full log and please use a pastebin site.
Reply
#7
This will also show your full advancedsettings.xml
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply
#8
This is because you are using a development build, as noted by the log itself:

Quote:NOTICE: Using Debug XBMC x32 build

For development builds (nightlies, monthlies, testing builds, etc), some debugging information can't be turned off completely. When formal/stable releases are made, this debug mode is turned off when the program is compiled.
Reply
#9
(2014-10-26, 01:39)Ned Scott Wrote: This is because you are using a development build, as noted by the log itself:

Quote:NOTICE: Using Debug XBMC x32 build

For development builds (nightlies, monthlies, testing builds, etc), some debugging information can't be turned off completely. When formal/stable releases are made, this debug mode is turned off when the program is compiled.

I am using the release 13.2 version. I will post the log file.

(2014-10-26, 01:33)David1977 Wrote: Could you please paste the full log and please use a pastebin site.

(2014-10-26, 01:38)nickr Wrote: This will also show your full advancedsettings.xml

http://pastebin.com/hq23CiC3
Reply
#10
Ah, my bad, I understood that incorrectly about the debugging mode.
Reply
#11
(2014-10-26, 02:19)Ned Scott Wrote: Ah, my bad, I understood that incorrectly about the debugging mode.

I am only having this trouble on Android. All other platforms work fine with the log level set to -1
Reply
#12
Help would be appreciated!!!
Reply
#13
Don't bump your thread without waiting 24 hours please.

Why not switch to the standard logging? Is there some particular reason you want to turn off debugging entirely?
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply
#14
Nickr I suppose he wants to use the "standard" logging (I think with "standard" you mean logging without debug enabled). That´s why he set his loglevel to -1. The problem is, that the system allways does a debug logging indifferent what he has set in the GUI or in advancedsettings.xml. He doesn´t want to switch logging of entirely. That´s what I thought too in the first and the reason why I explained the differrence between normal and debug logging.

The problem might be, that this line

Quote:17:01:39 T:1729542368 NOTICE: Using Debug XBMC x32 build, compiled Aug 17 2014 by GCC 4.8.0 for ARM Android 32-bit API level 14

is still present even if he uses the release build. So it could be a "bug" on XBMC for android. I set "bug" in quotes because I wouldn´t complain to allways have debug logging enabled...this kind of logging is needed in nearly all cases. But I understand the question why it can´t be turned off.

So...ericlak...I´m as curious as you, why this can´t be turned off. Unfortunately I can´ t help for this. I looked into other 13.2 android log files (http://forum.xbmc.org/showthread.php?tid=207200 in the first posting for example) and the line from above is allways there, too.

Greetings
Reply
#15
No, -1 implies he wants no logging at all - why that is not working I do not know.

I can understand that on a constrained platform like a typical android box, debug logging might swamp your system, however XBMC's standard debugging shouldn't (or if it does get a less constrained system, or work out where the excessive logging is coming from).

So my suggestion is to set standard logging level and see where that gets you.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply

Logout Mark Read Team Forum Stats Members Help
Turn off Debug Logging1