* feat(hud): long press collapses or expands the HUD, locking becomes an option
* fix(hud): keep the collapsing tab at the press point while layout runs
The layout listener could run keepOnScreen during the dock animation and replace the press-centered target with the anchored edge position, which was then saved as the tab position. The dock animation now holds the same guard the other HUD animations use until the dock is committed.
* fix(ci): wait out the API rate limit in build validation
* fix(ci): skip rate-limit sleep retries on status POSTs
* fix(ci): detect status POSTs via --method without changing api() call signature
* feat(agent): OpenCode as a third agent, with free Zen models or a pasted Zen key
* fix(agent): OpenCode's key check reads only its own entry and never overwrites an unreadable auth.json
* Add integer scaling mode
* Fix integer scaling view-space input bounds
* Improve integer scaling tolerance
* Add Fit and Auto scaling toggle to session drawer
* Translate Fit and Integer scaling labels
* Clarify integer scaling cropping hint
* Update integer scaling hint across translations
* Fix integer scaling settings and translations
* Fix controller input for integer scaling
* Complete integer scaling hint translations
* Fix integer scaling hint translations
* Restore XML declaration quote style
* Use double quotes in XML declarations
* Add missing norugeuingz translatisn
* fix: include math.h for roundf integer scaling
* fix: link math library in Vulkan caller tests
* Fix integer scaling translations
* Fix Italian integer scaling string
* Fix Italian scaling hint apostrophe
* fix(proot): ship proot in the APK and run it from the native library directory
* fix(native): start rootfs programs through an APK-shipped exec loader where data files may not be executed
* fix(audio): start PulseAudio through the system linker where data files may not be executed
* feat: target Android 14 (SDK 34) so Play Protect installs DroidDeck without a warning
* fix: ask for all-files access on Android 11+, reject unloadable ELFs before exec, keep checking the proot pack
* fix: hand host scripts to the kernel, skip startup launch while all-files Settings is open
* fix: run proot from its add-on pack through Android's linker, so the APK carries no proot
* fix: declare high sampling rate sensors for controller gyro at target 34
* fix: offer the rootfs proot fallback only where Android lets proot exec its loader
* test: install the runtime's proot pack in GameFileSync fixtures
* feat(display): black frame insertion on 100 Hz and faster screens
* feat(display): black frame insertion lives in Screen effects
* test(compositor): cover black frame insertion in the render-on-commit harness
* fix(display): keep HDR and pacing intact around black frame insertion
* fix(display): gate black frame insertion on the panel's refresh, not the tick rate
BFI checked the 100 Hz minimum against g_refresh_ns, an average of the time
between handled vsync ticks. BFI presents on every tick, so under load the
ticks run late, the average fell to 95-100 Hz on a 120 Hz panel, and BFI
switched off and on again many times a second (3793 times in one session on
a Retroid Pocket Duo). That showed as uneven flicker.
Use the display mode's refresh (g_output_refresh_mhz) instead, which only
changes when the mode does.
* fix(display): offer black frame insertion for the bottom screen and while it is on
* fix(display): capture a picture, not a black refresh, while black frame insertion strobes
* fix(display): hold black frame insertion off until the last capture ends
* fix(display): keep the game composed while a capture holds black frame insertion
* test(display): a picture hold presents only pictures while black frame insertion runs
* fix(preload): Windows games run from noexec shared storage under every Proton
When mprotect(PROT_EXEC) on a private mapping is refused, libblsession
moves the pages into anonymous memory and retries, so Wine can make an
image's code sections executable on noexec mounts. FEX keeps its
existing handling.
* fix(preload): copy noexec image pages without faulting or dropping access
* fix(preload): install copied image pages with final permissions
Nexus moved its Xodus changes from patch files in xodus-nexus into a backend
fork (domsvoboda/nexus-backend, GPL-3.0). prepare.py now fetches that fork at
backend-v0.2.15 (e7884a27, same Xodus base 53ea781d, same Rust 1.99.0) and
applies the DroidDeck patches, rebased onto it:
- droiddeck-credentials, -launch-view, -library-subscriptions: same rebase as
Bannerlator's 0.2.15 update (identical patches before and after).
- droiddeck-credential-fallback, -credential-diagnostics: applied unchanged.
- droiddeck-cloud-token: session::prepare now also returns the account
snapshot; the ticket checks it like upstream's profile/social commands.
- droiddeck-licensing-device-ticket: upstream 0.2.15 already formats
delegation-compact device tickets for Store license tokens (27c335e), so only
the content licensing path is patched. Upstream now writes compact JWE
delegation tickets as t=, so the d= prefix check is replaced by the token
type, the same rule as upstream's store_license.rs.
droiddeck-xbox-ticket.patch is dropped: upstream sends compact JWE delegation
tickets to Xbox Live sign-in in a form it accepts, with tests.
Runtime: domsvoboda/nexus-runtime runtime-11.0-20261102-g76c6dd13 (was
xodus-nexus runtime-11.0-20261018). Same six modules at the same path;
xgameruntime.dll is the C++ implementation (nexus-xgameruntime 455b1ba9).
Archive sha512 from the release's .sha512sum, source sha256 from its
candidate.json, module sha256 from the extracted files. The PlayFab Game Saves
proxy is a newer build at the same path and still passes droiddeck-xbox's
export checks; its license moved to share/doc/nexus-runtime/.
DLC mounting: the C++ runtime mounts downloadable content only inside a
host-managed workspace named by XODUS_MOUNT_ROOT (src/System/Package/Mount.h
returns E_NOTIMPL without it). DroidDeck starts Wine itself
(droiddeck:prepare), so droiddeck-dlc-mount.patch (ported from Bannerlator)
creates the workspace in the launch directory for the prepare session and
reports it as mountRoot; XboxRuntime passes it in the xbox-prepare reply and
droiddeck-xbox sets XODUS_MOUNT_ROOT to its Z: path. XODUS_CONTENT_ROOTS is
unchanged and still read by the runtime.
Upstream fixes since the old pins include sign-in for some accounts, offline
play, cloud-save conflict handling, DLC mounting, duplicate token requests and
per-game fixes (Ori, AoE, MSFS, Forza Motorsport).
The session preload is also built for i386 and preloaded into every 32-bit
x86 program under FEX. There it aliased fstat64, ftruncate64, pwrite64,
fallocate64, posix_fallocate64, open64, openat64 and fcntl64 to their 32-bit
hooks, which on i386 take a different struct layout or argument size. fstat64
returned a size with garbage high bits, so libdbus rejected a valid 33-byte
/etc/machine-id as too large and aborted the program. The aliases now exist
only where off_t is off64_t; on i386 the 64-bit calls reach their own glibc
functions, keeping the open and lock hooks.
* fix(rockstar): ship the launcher service as an add-on pack, not inside the APK
* fix: ship the DiRT ws2_32 stand-in as an add-on pack and reject Windows executables in the APK
* fix(release): reject APK entries under a packed path even when the manifest omits them
* fix(dirt): fetch the ws2_32 stand-in pack once the Linux runtime is installed
* feat: add per-game Steam Input override
* fix(steam-input): keep overrides in Steam's root apps section and keep the panel in step with the session
* fix(steam-input): reload the override after every session
* fix(desktop): serve PipeWire in Desktop mode so screen capture works
* fix(desktop): preserve shared PipeWire lifecycle
* test(desktop): exercise shared PipeWire lifecycle
* fix(desktop): start PipeWire for bottom sessions
* fix(desktop): serialize shared PipeWire bundle preparation
Concurrent Steam and bottom Desktop starts unpacked the bundle into the
same staging directory and rewrote the access settings together. Hold an
exclusive lock around unpacking and access configuration, and cover the
race plus start success and failure environment handling in tests.
* fix(desktop): replace PipeWire access fragments atomically
Write each fragment to a temporary file and rename it so running daemons and clients never read a truncated file.
* fix(desktop): isolate runtime directories in concurrent PipeWire start test
* feat(boot-movie): add a Shuffle switch backed by Steam's startup movie shuffle setting
* test(boot-movie): keep unrelated settings unchanged
* fix(boot-movie): keep the Shuffle choice across reset, unreadable configs and running sessions
* fix(boot-movie): track the Shuffle baseline per Steam home and only for values staging wrote
* fix(boot-movie): adopt a Shuffle change made in the inactive Steam home before staging overwrites it
* fix(boot-movie): keep the 60 fps note under the Installed movies row
* fix: surface Battle.net's own reason when it refuses a game folder
watch() treated any "error": <nonzero> in the Agent's status JSON as fatal. The
install form carries nested errors of its own - language.error 704 when the
requested locale is not offered, game_dir.error when the folder is unusable - so
the loop ended before the install started and agent_job reported "exit 0".
A form with a non-zero game_dir.error now fails with that reason (800 reads as
"the game folder already holds a game"); otherwise the wait continues, and only
a top-level error still ends the loop.
* fix: move the form-failure regression out of the crowded test block
Keep the driver behavior unchanged; this only relocates the new regression case so
the branch can be merged with current main without a test-file conflict.
* fix: sync the agent-error change onto current main
Bring the two touched files up to the current main versions and apply the form
failure handling on top. This keeps the PR limited to the driver and its test
without pulling workflow files into the branch.
---------
Co-authored-by: visail <visail@users.noreply.github.com>
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
* fix(session): record the guest start steps in events.jsonl
* fix(session): keep both start step events in the session where the step began
* fix(session): record the controller and pre-guest start steps in events.jsonl
* fix(audio): restart host after stalled wake recovery
* Serialize audio host restarts and make the stall counter race-free
* fix(audio): an overtaken restart leaves the socket alone and a sink guard only acts on its own host
---------
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
* fix(input): read a USB mouse directly where Android won't capture it, as in REDMAGIC cast mode
REDMAGIC's cast mode shows the session on a virtual display while its own
mirror activity keeps focus on the phone's display. Android only grants
pointer capture on the focused display, so the session got a cursor that
stopped at the screen edge and the camera stopped turning in mouse-look games.
When capture is wanted but not granted within 500 ms, the session claims the
mouse's USB HID boot interface instead, reads its reports with the layout from
its report descriptor (boot protocol if that can't be read), and sends motion,
five buttons and the wheel the way captured motion goes. The mouse goes back
to Android whenever capture is no longer wanted.
* feat(input): hold the middle button still to open the session menu while the mouse is read over USB
While the session reads the mouse over USB, Android has no cursor, so the
mouse can't reach REDMAGIC's cast-mode panel or anything else outside the
session. Holding the middle button for two seconds without moving opens the
session menu, which hands the mouse back to Android until the menu closes.
Quick middle clicks and middle-button drags still reach the game.
Relative motion sent to a locked pointer now hides the session's own cursor,
as pad pointer motion already does. A desktop keeps its grab while the menu
is open, so a click made with Android's cursor on the way back showed the
session cursor, which then stayed where the click was.
* fix(input): give a USB mouse back to Android when the app starts after being killed while reading it
A process killed while it reads the mouse, by a crash or an update, leaves
the mouse's interface with no driver, so Android has no mouse until it is
replugged. At startup, any permitted USB boot mouse that can be claimed
without force has no driver, and releasing it reattaches Android's.
* fix(input): only sessions shown off the phone's screen fall back to reading the USB mouse
Android grants pointer capture on the focused display, which the phone's own
screen is, so a session there never needs the USB mouse. Checking the display
keeps a slow capture grant from ever asking for the mouse's USB access there.
* fix(input): reject out-of-range HID report sizes and counts, and release USB buttons when the mouse is lost
A report descriptor can give any 32-bit report count or size, which drove the
field loop for billions of iterations and could overflow bit offsets into a
negative index on the reader thread. Items outside 32 bits and 4096 fields are
rejected, so such a mouse falls back to the boot protocol.
A mouse that stops responding while it is read over USB now releases the
buttons it held and cancels a pending menu hold, through a separate onLost
callback, since the session's own release path only runs while the grab is
still active.
* test(input): an oversized report count is rejected even when X and Y follow it
The earlier case had no X or Y fields, so it returned null without the count
check too. A 4097-field item before valid X and Y is now rejected, and a
4096-field one still parses.
* fix(input): Auto relative mouse sees a mouse read over USB, and re-checks when it is lost
The Auto relative-mouse decision from #2305 reads mouseAttached() on the
relative-mouse thread, which counts a mouse read over USB, so the grab's
state is now volatile. Losing that mouse re-runs the decision, as removing
an Android mouse does.
* fix(input): set up the USB mouse on its reader thread, select report protocol, and retry a failed permission request
Opening the receiver and its descriptor and protocol transfers now run on the
reader thread, so an unresponsive receiver can't stall the session for up to
two seconds. A release during setup lets the thread clean up as it already
did. A mouse that fails setup isn't tried again until it is replugged, since
releasing it re-adds Android's mouse, which would start another attempt.
A parsed report descriptor now selects report protocol first: HID 1.11
7.2.6 says a host must not assume the protocol a device is in.
A permission request that throws no longer marks the mouse as asked.
* fix(input): a cancelled or overlapping USB reader can't claim the mouse or mark it failed
A new reader waits for the previous one to let go of the interface, so a
quick release and grab, like toggling the session menu, no longer fails the
claim. A reader released before or during setup doesn't claim the interface
or keeps going. Failing to open or claim leaves the mouse with Android without
marking it failed, since nothing re-adds it to start another attempt; only a
failure after claiming, or a lost mouse, marks it, and only for the current
reader.
If SET_PROTOCOL(report) fails, setup tries boot protocol before giving up,
so the decoder always matches the protocol the mouse was set to.
* fix(input): release can't slip between the USB reader's cancellation check and its claim
The reader checked `running` and then claimed the interface, so a release in
between still let it claim and start setup. The check and claim now share a
lock with release, so the reader either never claims or claims first and sees
the release before setup.
* fix(input): hand the mouse back to Android while the WoW chat bar is on top
appUiOwnsPointer() already shows Android's pointer for the on-top chat bar,
but pointer capture, and now the USB mouse, stayed on, so that pointer
couldn't reach the bar. The bar on top now ends capture and USB reading like
the session menus do, and its changes re-run the capture decision.
* fix(game-env): keep DroidDeck's DLL overrides when a game sets its own
* fix(game-env): keep the game row when the merged DLL overrides pass 8192
---------
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
* fix(dual-screen): the bottom-screen terminal keeps its shell when another app covers that screen
* fix(session): sweep the kept terminal shell's process tree when the session ends
* fix(graphics): fall back from unsupported auto display drivers
* refactor(graphics): drop the unused Auto recommendation lookup
* fix(graphics): repair automatic display fallback build
* test(wayland): keep Vulkan caller harness linkable
---------
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
* feat(performance): add idle zram compression toggle
* Gate the idle compression toggle on memory cap support and refresh counters first
* fix(zram): retain launcher reclaim when idle compression is off
* test(memory): verify launcher-only reclaim signals
* fix(performance): keep game reclaim when focus is unknown
* fix(performance): say when to turn idle compression off and that it applies on the next session
---------
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
* fix(fex): the x86 runtime is built from files inside it so FEX finds its libraries
* fix(fex): the x86 runtime keeps the permissions of the directories it is built from
* fix(fex): rebuilding the x86 runtime refreshes the Steam client links and removes read-only trees
* fix(fex): rebuilding the x86 runtime removes old trees that contain unreadable directories
* fix(fex): isolate generated rootfs files
* fix: refresh the session loading tips and drop stale translations
* fix: add tips from common support questions
* fix(session): restore translated loading tips and fix the string that broke resource merging
* fix(tips): list every store the Stores tab signs in to
* fix(shortcuts): move the accessibility service into an optional companion so Play Protect stops blocking the install
* fix(shortcuts): bind only same-signer relays, recheck enablement per call, drop timed-out keys
* fix: Remote Play gets the Steam Deck controller
Steam's Remote Play client reads the controller itself from its own
streaming_client process. The input preload only exposed the virtual
Deck controller (and the DualShock 4 / DualSense pads that share its
code) to the process named steam, so in Steam Deck controller mode
streaming_client was refused /dev/hidraw16 and the stream got no input:
streaming_clien: deck: /dev/hidraw16 refused: not the Steam client
streaming_client now sees the same Deck, DualShock 4 and DualSense pads
as Steam. Each opener gets its own report stream from the read-only
ring, so the two processes do not compete for input. The Steam
Controller paths stay Steam-only: the paired controller's feature and
output slot is serialised only within one process.
Fixes#1860
* fix: Remote Play also gets the Steam Controller and touch controls
streaming_client now opens the Steam Controller pads (the app's
emulated one and a paired controller) and Steam's touch controller,
like the Steam Deck pad.
A paired controller's feature request and output slots, and the touch
controller's state, are shared with the app and written under a
seqlock that expects one writer. Their writers now also take a flock
on a lock file in the hook directory, so Steam and streaming_client
take turns. touch_state() was a template holding its own static mutex,
so each caller had a separate one; it now shares a single mutex.
The pad type and touch plug watchers run in streaming_client too, so
it gets the udev events for mode switches and replugs; those only reach
the process that injects them. Poking /dev watchers and moving event0
on the shared filesystem stay with Steam, so they happen once.
* fix: the shared slot lock fails safe and never waits forever
If the lock file cannot be opened or locked, ProcessSlotLock used to
carry on unlocked. Steam alone is still a single writer then, exactly
as before streaming_client could open these devices, so it carries on;
streaming_client now leaves the paired controller's feature and output
slots and the touch state alone instead (feature reads fail with EIO).
The first failure is logged.
The wait for the lock is now bounded: a session freeze can stop the
process holding it, and writers wait with controller_mutex held, so an
unbounded flock could stall all input in the other process. Feature
reads wait up to their 500 ms reply timeout, outputs 100 ms and touch
state 20 ms. When the deadline passes the lock is held by the other
process, so neither proceeds; the operation is skipped and logged.
* fix: Steam no longer turns motion off under its Remote Play client
Steam and streaming_client both set the Deck pad's IMU mode, and both
wrote the one word Android reads to decide whether to feed the gyro.
Steam keeps toggling its own mode during a stream, so it could switch
motion off while the Remote Play layout needed it, and the client never
re-sent an unchanged mode.
Each process now has its own word. Android reads motion while either
wants it, and ignores the Remote Play word once that process is gone.
* fix: Remote Play decides motion while Steam has set no mode
Until Steam published its IMU mode, Android reported the mode as unknown
without reading the Remote Play client's word, so a Remote Play request
to stop motion had no effect. The word that has been set now decides,
and the mode stays unknown only while neither process has set one.
The rule moves into ImuModes so it can be tested on the JVM.
---------
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
* feat(compositor): pen samples drive the pointer like a mouse
Input record 13 carries the pen's state (in proximity, tip, right and
middle button) and its position in input space as 24.8 fixed point.
Hover moves the pointer, the tip holds the left button, and a record
without the in-proximity bit releases every button. Under a pointer
lock only the buttons pass. A button pressed or released mid-stroke
keeps the implicit grab on the window the stroke started in, unless
that window closed.
* feat(input): a pen moves the pointer while hovering, clicks with its tip and right-clicks with its side button
In Mouse mode (the default) a pen's hover moves the pointer, the tip
holds the left button and the side button right-clicks; Touch keeps it a
finger. The side button can send a middle click or nothing instead, and
a Bluetooth pen key counts as the side button while the pen is near.
With glasses or a program's pointer lock the pen drives the touchpad.
A hover exit followed within 50 ms by more hover or a touch keeps the
pen near, so a pen at the edge of its hover range does not flicker out,
and a hover that sends nothing for 2 s leaves proximity. On the desktop
a pen that comes near releases KWin's grab of a hardware mouse, so the
pen moves KWin's pointer. Whatever cancels touches also ends the pen,
and stylus devices no longer count as hardware mice.
* feat(input): pen mode and side button settings in the Controls tab and the session drawer
A Pen group follows the touch settings once the phone has a stylus
device or a pen event was seen, which is remembered as penSeen and kept
by a settings reset. It holds Pen (Mouse, Touch) and Side button (Right
click, Middle click, Off); Side button is hidden in Touch. Before
Android 14 a touchscreen reports the stylus source without a pen, so
there it counts only with its first pen event. The strings are
translated into all 32 languages.
* docs: describe pen input and its limits
---------
Co-authored-by: alien2003 <11610652+alien2003@users.noreply.github.com>
droiddeckctl input pen hover, tap, stroke and button register a virtual
direct pen with `adb shell uinput -` and play the gesture through it, so
Android's input reader makes the same stylus events a built-in pen does,
with pressure, tilt, distance, the eraser and both side buttons. The app
is not involved, which lets pen handling be tested without a pen.
Positions are fractions of the screen as shown, placed inside the
physical frame of the internal display viewport in dumpsys input: the
frame is smaller than the panel when `wm size` sets another aspect
ratio, and Android drops pen events outside it. The rotation and size
come from the same viewport. The values are checked before anything
runs on the device.
The script waits 1 s after registering, since uinput reads it in one go
and cannot wait for the device, and does not reset uinput's time base
after that, which would drop the first samples. Contact sends a pressure
of at least 1, because Android takes a pen at pressure 0 for a hovering
one, and a lift first moves to where it lifts, because Android's UP
repeats the last contact. A pen held still moves by one unit without
leaving the physical frame so that it keeps reporting, since the kernel
drops frames that change nothing.
Co-authored-by: alien2003 <11610652+alien2003@users.noreply.github.com>
* Head tracking for the XREAL One, One Pro, One Pro+ and Aura
These glasses use the same USB Ethernet link and 128-byte IMU report as the
1S. XrealModel now has one model per product: the 1S keeps its tested
display-mode control, and the others switch 2D and 3D only with GET_INPUT
(0x2821) and SET_INPUT (0x2822). Display-mode set (0x275f), brightness and
the dimmer are never sent to them. The Aura's IMU reads x right, y up, z back
(about +9.8 m/s2 on y at rest), so its axes are not flipped like the rest of
the family. Recovery-mode product ids (one below each) stay excluded.
Signed-off-by: Mike Haye <84657517+mhaye20@users.noreply.github.com>
* Describe the wider XREAL support in the glasses panel and docs
The panel's help text and docs/smart-glasses-support.md named only the 1S.
They now list the One, One Pro, One Pro+ and Aura, say what was tested on
the Aura (head tracking and 2D/3D switching), and note that these models get
2D and SBS only, without brightness, dimming or display-mode set commands.
Translations still describe the 1S only.
Signed-off-by: Mike Haye <84657517+mhaye20@users.noreply.github.com>
* Docs: XREAL support is no longer 1S only
The paragraph under the support matrix still said the One and One Pro were excluded.
Signed-off-by: Mike Haye <84657517+mhaye20@users.noreply.github.com>
---------
Signed-off-by: Mike Haye <84657517+mhaye20@users.noreply.github.com>
* feat(theme): AMOLED black, a theme with a pure black page and panels
* feat(theme): rename to True black and let the user pick its highlight color
* fix(theme): True black leaves the page unlit, with no art wash or corner glow
* feat(xbox): stage the PlayFab Game Saves save-folder proxy from the Nexus runtime
Xbox titles that use PlayFab Game Saves, such as Forza Horizon 6, stop with
"Initialization Failed" E:0-17 right after sign-in. The SDK's default provider
needs Gaming Runtime save APIs that xgameruntime does not have, and its
in-process provider needs a save folder the title never passes on Windows.
xodus-nexus already builds a proxy for this into the runtime archive we pin
(scripts/runtime-compat, MIT): it keeps the title's SDK as
nexus_pgs_native.dll, sets ForceUseInprocGameSaves and passes the
PersistentLocalStorage PlayFabGameSaves folder. runtime.py now takes it and
its license from the archive, checked against runtime.lock.json, and
droiddeck-xbox stages it before each launch when the game's
PlayFabGameSave.dll has exactly the SDK's 40 exports. A game update that
brings a new SDK replaces the kept copy; anything unknown is left alone.
Unlike Nexus, no DLL override is set for the two DLLs: Wine has no builtin of
either, and forcing them native-only made Forza Horizon 6 fail with E:0-0-4.
* fix(xbox): check the whole PlayFab export table and never overwrite an unknown kept SDK
The SDK and proxy checks now also require the export address table to hold
exactly 40 functions, so a DLL with the same names plus an ordinal-only export
is no longer taken for the SDK. Before copying a new SDK to
nexus_pgs_native.dll, an existing file there must itself be a regular file
holding the SDK; an unknown file or a link is left as it is.
* 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