summaryrefslogtreecommitdiff
path: root/libs/WindowManager/Shell
diff options
context:
space:
mode:
author Wenhui Yang <wenhuiy@google.com> 2024-07-03 07:21:04 +0000
committer Wenhui Yang <wenhuiy@google.com> 2024-07-10 06:30:35 +0000
commit8c86d3e8da25dcb25a9e9f103435e9d647a3d281 (patch)
tree8110faaf346aae3a6dfaa02d658e0377ebce2dde /libs/WindowManager/Shell
parent09672b7cc14d717288a09cfc169a64a5f1da8b86 (diff)
Allow SurfaceControlRegistry to be able to update at runtime
Fixes: 346397738 Test: adb shell setprop persist.wm.debug.sc.tx.log_match_call setAlpha,setPosition Flag: TEST_ONLY Change-Id: Ie5dd4f800a31732a2dcca69ae0dd265dada4004b
Diffstat (limited to 'libs/WindowManager/Shell')
-rw-r--r--libs/WindowManager/Shell/src/com/android/wm/shell/docs/debugging.md6
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.