docs(phantom): how Android counts guest processes and why detaching cannot escape it (#2584)

* docs(phantom): how Android counts guest processes and why detaching cannot escape it

* docs(phantom): clarify probe permissions and batch capture

* docs(phantom): qualify probe precondition by SDK and size the limit device-wide

* docs(phantom): keep phantom discovery on for the 12L probe and raise the limit instead

* docs(phantom): warn about the CPU kill, raise the limit before the flag and restore both after the probe

* docs(phantom): restore the monitor flag before the phantom limit after the probe

* docs(phantom): restore the flag before the limit whether each is put or deleted
This commit is contained in:
MaxsTechReview authored and GitHub committed 2026-11-15 09:37:34 -05:00
1 parent 56fabbdbf0
commit 4527e93118
2 files changed
+211

No files matched your search

@@ -58,6 +58,24 @@ class PhantomProcessLimitTest {
assertFalse(PhantomProcessLimit.verified("null", enabled = false, sdk = 33))
}
@Test
fun android12LKeepsTheFlagAndNotTheCountLimit() {
assertFalse(PhantomProcessLimit.usesDeviceConfig(32))
assertEquals(
listOf("settings put global settings_enable_monitor_phantom_procs false"),
PhantomProcessLimit.shellCommands(enabled = false, sdk = 32),
)
}
@Test
fun android12KeepsTheCountLimitBecauseItHasNoFlag() {
assertTrue(PhantomProcessLimit.usesDeviceConfig(31))
assertTrue(
PhantomProcessLimit.shellCommands(enabled = false, sdk = 31)
.any { it.startsWith("device_config put activity_manager max_phantom_processes") }
)
}
@Test
fun developerToggleStartsAtAndroid14() {
assertFalse(PhantomProcessLimit.hasDeveloperToggle(33))