Strange log in android platform!

FMOD Engine
1

Hi:
Since I imported the fmod libary in my android project, I found my app output many logs as follow:
05-28 15:36:55.846: D/AudioTrack(24851): write: 0x7f5a03b080, frames = 512, written = 2048
05-28 15:36:55.846: D/AudioTrack(24851): write: 0x7f5a03b080, userSize = 2048, blocking = 1
05-28 15:36:55.846: D/AudioTrack(24851): write: 0x7f5a03b080, frames = 512, written = 2048
05-28 15:36:55.846: D/AudioTrack(24851): write: 0x7f5a03b080, userSize = 2048, blocking = 1
05-28 15:36:55.846: D/AudioTrack(24851): write: 0x7f5a03b080, frames = 512, written = 2048
05-28 15:36:55.846: D/AudioTrack(24851): write: 0x7f5a03b080, userSize = 2048, blocking = 1
05-28 15:36:55.846: D/AudioTrack(24851): write: 0x7f5a03b080, frames = 512, written = 2048
05-28 15:36:55.846: D/AudioTrack(24851): write: 0x7f5a03b080, userSize = 2048, blocking = 1
05-28 15:36:55.915: D/AudioTrack(24851): write: 0x7f5a03b080, frames = 512, written = 2048
05-28 15:36:55.915: D/AudioTrack(24851): write: 0x7f5a03b080, userSize = 2048, blocking = 1
05-28 15:36:55.916: D/AudioTrack(24851): write: 0x7f5a03b080, frames = 512, written = 2048
05-28 15:36:55.916: D/AudioTrack(24851): write: 0x7f5a03b080, userSize = 2048, blocking = 1
05-28 15:36:55.916: D/AudioTrack(24851): write: 0x7f5a03b080, frames = 512, written = 2048
05-28 15:36:55.916: D/AudioTrack(24851): write: 0x7f5a03b080, userSize = 2048, blocking = 1
05-28 15:36:55.985: D/AudioTrack(24851): write: 0x7f5a03b080, frames = 512, written = 2048
05-28 15:36:55.985: D/AudioTrack(24851): write: 0x7f5a03b080, userSize = 2048, blocking = 1
05-28 15:36:55.985: D/AudioTrack(24851): write: 0x7f5a03b080, frames = 512, written = 2048
ps: I use the non-log version library in my project.
I check the android source code and I don’t find log pattern like that. Does it output by fmod? Anyone who can tell me how it happens? Thanks!

2

Android

3

log

4

It looks like this logging is coming directly from the OS, we will have a ‘fmod’ prefix on our logs.

You could try with our logging libs to see if that may expose some more information.