Files
vllm-omni/benchmarks/edge_harness/android_agent/phone_state.py
T
tzhouamandClaude Opus 5 b36a3431bd Package this fork as vllm-embedding: README, docs, roadmap, harness
Turns a branch of accumulated edge/CPU work into something someone else can
read, reproduce and continue.

README.md states what the fork is for (multimodal models on edge CPUs rather
than servers), the headline memory and speed results with their costs, and why
the numbers are worth reading -- five retracted conclusions, all measurement
errors rather than coding errors. Upstream's README is preserved at
docs/README.vllm-omni.md and NOTICE records the Apache-2.0 derivation and the
files this fork changes.

docs/edge/:
  methodology.md  the measurement discipline, which is the most transferable
                  thing here: what each of the five retractions was, and the
                  rule it left behind. Includes the two traps specific to this
                  stack -- vLLM's AOT compile cache keying on config so two
                  arms sharing an artifact load the wrong graph, and allocated
                  not being resident until mincore(2) says so.
  results.md      every measured figure with its spread and baseline, and an
                  explicit note that the four memory levers overlap and must
                  not be added.
  cpu-4bit.md     the two 4-bit paths, the packed layout as measured rather
                  than assumed, why the path choice is a config field, and the
                  GPTQ output-head trap that invalidated a whole round of W4A8
                  numbers.
  harness.md      how to run a comparison, and the two arguments that matter
                  more than they look (--context-len, --prompt-len), each of
                  which has produced a wrong conclusion by being left at its
                  default.

ROADMAP.md orders by whether the verification method is correct rather than by
expected size, lists what is done with results, what is next with expected
gains and how each would be verified, and -- at equal length -- what was
considered and rejected, including the CPU megakernel with the measurements
that rule it out for now.

benchmarks/edge_harness/ brings the tooling into the repo so the numbers are
reproducible: the grid runner, the single-run benchmarks, the memory ledger,
the fidelity metric, the Android agent suite, the quantizers, and the tests
that pin the harness's judgement. 82 tests pass from the new location.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01L1ax5wYLA6XbqEL1i8L9gZ
2026-09-14 13:25:32 +08:00

136 lines
5.6 KiB
Python

"""What the phone is actually in, read the same way for both backends.
The scored suite used to take its predicates over ``SimulatedDevice``'s Python
attributes, so every scored run was a simulator run by construction -- the
real-device path existed for *driving* a phone and not for judging one. That
made "the agent suite" a claim about fixtures.
Success is therefore read two ways, and the order matters:
1. **Out of band, from the setting itself** -- ``device.state`` in the
simulator, ``settings get global wifi_on`` over adb. This is the ground
truth, and it does not depend on where the agent happened to leave the
phone. Scoring from the final screen alone fails an agent that turns Wi-Fi
on correctly and then presses Home, which is not a failure.
2. **From the UI dump**, for anything with no setting behind it -- a saved
alarm appears as a row in the clock app and nowhere else. The simulator
emits real uiautomator XML, so this goes down the same parse, the same
switch lookup and the same text matching a phone would.
Only the facts a phone genuinely cannot report after the fact -- which
switches were flipped on the way, and what was typed into which field -- come
from the simulator object, and any task needing them declares it, so a
real-device run refuses to score rather than scoring wrong.
"""
from __future__ import annotations
from dataclasses import dataclass, field
from ui_tree import parse_ui_dump
def _norm(s: str) -> str:
"""Match labels across the punctuation Android is inconsistent about."""
return "".join(c for c in s.lower() if c.isalnum())
@dataclass
class PhoneState:
source: str
"""``"sim"`` or ``"device"`` -- which facts below are trustworthy."""
settings: dict[str, bool] = field(default_factory=dict)
"""Authoritative setting values, read out of band. Preferred over
:attr:`switches`, which only shows what is currently on screen."""
screen: str | None = None
"""Simulator screen id. ``None`` on a real phone, where there is no such
thing; use :meth:`has_text` against something the screen actually shows."""
switches: dict[str, bool] = field(default_factory=dict)
texts: list[str] = field(default_factory=list)
typed: list[str] = field(default_factory=list)
fields: dict[str, str] = field(default_factory=dict)
records: dict[str, list[dict]] = field(default_factory=dict)
toggled: list[tuple[str, bool, bool]] = field(default_factory=list)
"""(key, before, after) for every switch the agent actually flipped."""
def switch(self, *names: str) -> bool | None:
"""State of the first control matching any of ``names``.
The setting wins over the screen: an agent that turned Wi-Fi on and
then navigated away has still turned Wi-Fi on. ``None`` means neither
source knows the control, which is not the same as off -- an agent that
never found the screen has not turned anything on, and predicates must
not read that as "off".
"""
wanted = {_norm(n) for n in names}
for key, value in self.settings.items():
if _norm(key) in wanted:
return bool(value)
for label, checked in self.switches.items():
if _norm(label) in wanted:
return checked
return None
def has_text(self, *needles: str) -> bool:
joined = " ".join(self.texts).lower()
return any(n.lower() in joined for n in needles)
def times_toggled(self, key: str) -> int:
return sum(1 for k, _, _ in self.toggled if k == key)
def read_state(device) -> PhoneState:
"""Read the phone through its screen, plus the simulator's own records."""
elements = parse_ui_dump(device.dump())
# `checkable` is deliberately not among the flags ui_tree parses, because
# that list is also what the model is shown; adding to it would change the
# agent's prompt. A switch is recognised by its class or by exposing a
# `checked` flag instead.
switches = {e.text: bool(e.flags.get("checked", False))
for e in elements
if "checked" in e.flags
or e.short_class in ("Switch", "CheckBox", "ToggleButton")}
texts = [e.text for e in elements if e.text]
if not hasattr(device, "screens"):
return PhoneState(source="device", switches=switches, texts=texts,
settings=adb_settings(device))
return PhoneState(
source="sim",
screen=device.current,
settings={k: bool(v) for k, v in device.state.items()},
switches=switches,
texts=texts,
typed=list(device.typed),
fields=dict(getattr(device, "fields", {})),
records={k: [dict(r) for r in v]
for k, v in getattr(device, "records", {}).items()},
toggled=list(getattr(device, "toggled", [])),
)
ADB_SETTINGS = {
"wifi": ("global", "wifi_on"),
"airplane": ("global", "airplane_mode_on"),
"bluetooth": ("global", "bluetooth_on"),
}
"""Settings readable out of band, so scoring does not depend on which screen
the agent left the phone on."""
def adb_settings(device) -> dict[str, bool]:
"""Read the authoritative values from a real phone. Missing keys are
omitted rather than defaulted -- an unreadable setting must not be scored
as "off"."""
out: dict[str, bool] = {}
for key, (namespace, name) in ADB_SETTINGS.items():
try:
raw = device._run("shell", "settings", "get", namespace, name)
except Exception:
continue
raw = raw.strip()
if raw in ("0", "1"):
out[key] = raw == "1"
return out