diff options
| author | 2024-07-11 18:02:22 +0000 | |
|---|---|---|
| committer | 2024-07-11 18:02:22 +0000 | |
| commit | b450cf1a75427c75e07439eb5c2c2fdbe86c93d8 (patch) | |
| tree | 4e7a835ae403564b680d1449ba0b068cdad8efa5 /libs/WindowManager/Shell | |
| parent | 03d4729847ff69109a0c6a392e3308752d42f505 (diff) | |
| parent | 8c86d3e8da25dcb25a9e9f103435e9d647a3d281 (diff) | |
Merge "Allow SurfaceControlRegistry to be able to update at runtime" into main
Diffstat (limited to 'libs/WindowManager/Shell')
| -rw-r--r-- | libs/WindowManager/Shell/src/com/android/wm/shell/docs/debugging.md | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/libs/WindowManager/Shell/src/com/android/wm/shell/docs/debugging.md b/libs/WindowManager/Shell/src/com/android/wm/shell/docs/debugging.md index 3572d161f5b9..84f6af4125b8 100644 --- a/libs/WindowManager/Shell/src/com/android/wm/shell/docs/debugging.md +++ b/libs/WindowManager/Shell/src/com/android/wm/shell/docs/debugging.md @@ -68,7 +68,7 @@ adb shell dumpsys SurfaceFlinger ## Tracing global SurfaceControl transaction updates While Winscope traces are very useful, it sometimes doesn't give you enough information about which -part of the code is initiating the transaction updates. In such cases, it can be helpful to get +part of the code is initiating the transaction updates. In such cases, it can be helpful to get stack traces when specific surface transaction calls are made, which is possible by enabling the following system properties for example: ```shell @@ -81,9 +81,11 @@ adb logcat -s "SurfaceControlRegistry" # Disabling logging adb shell setprop persist.wm.debug.sc.tx.log_match_call \"\" adb shell setprop persist.wm.debug.sc.tx.log_match_name \"\" -adb reboot ``` +A reboot is required to enable the logging. Once enabled, reboot is not needed to update the +properties. + It is not necessary to set both `log_match_call` and `log_match_name`, but note logs can be quite noisy if unfiltered. |