Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Suppressing the AW MPP library logging
#1
Photo 
Hello,

When I run the examples the console is printing a lot of information. Is there a way to disable this? As I don't want to spam the console with debug messages.

[Image: sMojHS0.png]
Reply
#2
http://priorestate.ru
ремонт квартир ключ новостройка|

http://ecoenergograd.ru
купить 1 новостройку|

http://azestate.ru
сайт новостройки|


Attached Files Thumbnail(s)
           
Справочник недвижимости России - http://scifinews.ru/
Reply
#3
(09-05-2019, 02:33 PM)itzandroidtab Wrote: Hello,

When I run the examples the console is printing a lot of information. Is there a way to disable this? As I don't want to spam the console with debug messages.

[Image: sMojHS0.png]

I was wondering so myself, but didn't find the answer.
I guess your best bet is to redirect all output of the program to /dev/null...

P.S. From my view, Allwinner did a very bad job with software. The fact that they compiled libraries as armel instead of armhf is driving me nuts...
Reply
#4
I found a way to change the log level of awplayer. The only thing is that there are no header files for it and the awplayer sets the log level to 3 on its own.

I looked in the binary and it looks like the log level is 5 by default. Something in libcdx_common changes the log level to 3 and that is where the debugging messages start. I changed the libcdx_common binary to not call the log_set_level function. This means the log level wont be changed at the start anymore. This disables the DEBUG and the INFO prints of awplayer. The warnings are still going through (errors probably as well (not tested)). This removes some of the messages when the program starts.

[Image: 502Zk2c.png]

So I think they accidentally left in the log_set_level() call and just shipped it.

To remove the logs you need to change the libcdx_common.so in /usr/lib to the one in the attachment.

If you want to change the log level you can create a declaration:

Code:
void log_set_level(uint32_t);

The log level is stored in this variable:

Code:
extern uint32_t GLOBAL_LOG_LEVEL;

You should be able to read from it. Not sure if writing works as it looks like the set_log_level function does more than just changing the value.

And you need to link against "-lcdx_base"

modified libcdx_common.so:
https://github.com/itzandroidtab/device/..._common.so


I removed some more prints especially the ">>>> something <<<<" messages.

As these prints are hardcoded and there is no check for a debug level. I changed the subroutines to return directly instead of printing something. I forked the device repo of lindenis and changed all the binary's there:

https://github.com/itzandroidtab/device/
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)