| 7e820c5cfdc8d9fd2f8c34ffe287f2479b6577d2 |
|
18-Apr-2018 |
Andy Hung <hunga@google.com> |
Fix string copy termination
Test: CTS regression
Bug: 78198288
Change-Id: Id433eb3197d4faf530d5f5090ff95e51689e7088
/frameworks/av/services/audioflinger/BufLog.cpp
|
| 49f36ba3b4624ddd3d7efa34c95128a73bda6208 |
|
06-Dec-2017 |
Glenn Kasten <gkasten@google.com> |
Logs use either %#x or 0x%x for flags, channel mask, format, device
Preferred is %#x but 0x%x is also permitted because it is widely used.
The benefit is that it reduces ambiguity and possible confusion,
without needing to read the source code for each log.
Test: builds OK and logs are less ambiguous
Change-Id: Ie2404e071d22278b8bba1e094ad336887844212c
/frameworks/av/services/audioflinger/BufLog.cpp
|
| 3bd1c87ac0d767566f5da387e90b8a3cd86ecc97 |
|
26-Sep-2016 |
rago <rago@google.com> |
Buffer Log functionality for AudioFlinger
Similar to ALOGV, this allows to capture to file audio samples from
within audioservice for debuggin purposes.
Test: manual. Mostly used for debugging
Change-Id: I4d43f573926805a27be910e343476c3f1be51579
/frameworks/av/services/audioflinger/BufLog.cpp
|