开各模块log前,建议先关闭selinux权限,并确定camera logD是已经有打印的,如果没有打印可以用如下命令开启:
adb shell setenforce 0
adb shell setprop persist.vendor.mtk.camera.log_level 3
adb shell pkill camera*
再按以下方法开对应模块的 log:
1. 开MTK Camera2 APP log
adb root
adb shell setprop vendor.debug.mtkcam.loglevel 3
2. 开camera device hal3 log
log tag: mtkcam-dev3
adb root
adb shell setprop debug.camera.log.CameraDevice3 2
⇒\Rightarrow⇒ dump session param in configure stage
⇒\Rightarrow⇒ log requests from framework
⇒\Rightarrow⇒ log results from pipeline
3. 开 AppStreamMgr 的 log
log tag: mtkcam-AppStreamMgr
adb root
adb shell setprop vendor.debug.camera.log.AppStreamMgr X
⇒\Rightarrow⇒ X >= 1, dump per-frame callback image/meta/shutter/error message
⇒\Rightarrow⇒ X >= 2, dump per-frame control metadata
⇒\Rightarrow⇒ X >= 3, dump per-frame result metadata
打开后,会有关键 log: mtkcam - AppStreamMgr: [x - CallbackHandler::performCallback]
4. 开Pipeline log
log tag: mtkcam-PipelineFrameBuilder
adb root
adb shell setprop persist.vendor.debug.camera.log X
adb reboot
⇒\Rightarrow⇒ X >= 2, Log every IPipelineFrame settings
⇒\Rightarrow⇒ X >= 3, Log every IPipelineFrame settings and its PipelineContext
打开后,会有关键 log: mtkcam-PipelineFrameBuilder: App image stream buffers=

本文档详细介绍了如何开启MTK Camera2应用、设备HAL3、AppStreamMgr、Pipeline等模块的日志,以及如何进行P1Node、P2S、Capture、MFNR和FD的log和dump操作。涉及的关键日志标签包括mtkcam-dev3、mtkcam-AppStreamMgr、mtkcam-PipelineFrameBuilder等,同时提供了相应的adb命令和dump路径。
953

被折叠的 条评论
为什么被折叠?



