OpenPhone
Releases

OpenPhone 0.0.1 Release Notes

Status: draft.

0.0.1 is the first OpenPhone developer preview target. It is intended for ROM developers and early collaborators, not daily-driver consumer use.

Supported Devices

  • Google Pixel 9a (tegu) - development target.

Highlights

  • Source-available OpenPhone project repository.
  • LineageOS-based build workflow.
  • Pixel 9a product target documentation.
  • Privileged OpenPhone Assistant app.
  • Chat-style assistant home screen with text/voice task entry and stateful mic/send/stop composer control.
  • Hidden Android framework manager API.
  • system_server OpenPhone agent manager service.
  • Task, screen, action, policy, confirmation, pointer-event, and audit plumbing.
  • Assistant-owned active-agent indicator and cursor overlay.
  • Assistant-side dynamic island state model for compact, transcript, reply, and approval states.
  • Assistant-side trajectory logging for agent runs.
  • Agent Runtime V1 background jobs for scheduled/deferred agent turns, with notification delivery and state-changing background tools blocked until foreground review exists.
  • Agent eval report contract and validator for packaging trajectory/audit evidence from physical runs.
  • Host-side agent eval collector for pulling the latest phone-exported trajectory/audit files and generating the eval report.
  • Host-side device connection diagnostic for USB/ADB/fastboot bringup states.
  • Assistant-side accessibility UI-tree capture for development screen understanding.
  • Development OpenAI text/vision model adapter path.
  • OpenPhone broker/proxy transport option for development cloud model calls.
  • Dependency-free reference model broker with admin-authenticated signed development-token minting, request-size/request-count/byte-volume controls, provider/model registry-backed allowlisting, device-subject registry checks, optional development HMAC device-proof checks, and body-free JSONL audit events.
  • Model broker privacy gate for OpenPhone task metadata, sensitive-screen flags, and maximum screenshot/image count.
  • Model broker bounded retry for transient upstream provider failures.
  • First-pass model broker Linux deployment artifacts, including systemd and nginx TLS reverse-proxy templates.
  • Model broker helper for rotating broker token/admin secrets and provider keys.
  • Model broker helper for rendering nginx/certbot TLS setup.
  • Assistant-owned task grant controls and approval surface.
  • Settings/About phone OpenPhone version and support rows.
  • Settings homepage OpenPhone dashboard with assistant, task-grant, audit-evidence, and support entry points.
  • Settings-hosted durable task-grant defaults and audit status pages.
  • First per-app capability policy seed for sensitive app surfaces, enforced by assistant model-tool preflight using foreground package context.
  • Durable Settings.Secure app-policy override contract for future per-app/per-capability Settings UI.
  • Development helper for generating/installing app-policy override JSON.
  • SystemUI-owned OpenPhone Quick Settings tile for launching the assistant, showing framework task status, and stopping active framework tasks.
  • Pixel 9a DTB preparation and generated vendor_kernel_boot.img verification in the build script.
  • Lightweight GitHub CI for repository checks.
  • Release artifact checksum, validation, and draft-preparation scripts.

Known Issues

  • Not a consumer-ready ROM.
  • Production signing is not used for the preview artifact; private release-signing workspace preparation and signing wrapper are documented.
  • On-device OTA installation is not implemented. The first assistant-owned preview client can check the OTA feed and download a size/SHA-256 verified ZIP to Downloads/OpenPhone, but installing it remains manual.
  • Full autonomous multi-step agent loop is still in progress. Agent Runtime V1 adds durable background jobs, but the post-turn review worker and resumable background approvals are still future work.
  • Framework-owned UI hierarchy extraction and OCR are not implemented.
  • The first UI-tree path is assistant-side and depends on accessibility service enablement.
  • The first SystemUI OpenPhone surface is a Quick Settings tile. The assistant-owned island/cursor overlay exists for active development feedback, but richer production status-bar or dynamic-island-style SystemUI presence is not implemented.
  • Settings has OpenPhone audit and task-grant pages, and task-grant defaults are durable. The first per-app policy seed exists, but the full editable per-app/per-capability Settings manager is not implemented yet.
  • The assistant-side accessibility UI tree now has first-pass sensitive-screen handling: password-field labels are redacted, and screenshot tools are blocked on password/payment/account-like screens.
  • Assistant fallback policy covers every capability in the product registry, including high-risk share.content; repo checks validate registry/policy risk alignment.
  • The first model-tool registry maps model-visible tools to product capabilities, and repo checks validate executor/adapter coverage.
  • Model web-link launches use a framework-mediated network.use action path instead of direct assistant intent launching.
  • Action-contract checks validate that assistant-emitted framework action types are represented in the public action-request schema and patch stack.
  • Reason-required model tools now fail closed in the executor when the model omits a non-empty reason.
  • Audit-event schema coverage is checked against framework recordAudit(...) event names.
  • Trajectory events.jsonl exports include a schema marker and have a public trajectory-event schema.
  • Screen-context schema covers the assistant accessibility UI-tree snapshot fields used for visible text, windows, interactive elements, sensitivity, and risk hints.
  • Assistant trajectory exports can be validated with scripts/validate-trajectory-export.sh before using them as release evidence.
  • Framework audit evidence exports can be validated with scripts/validate-audit-evidence-export.sh.
  • Pixel 9a target-files/OTA builds use automated DTB preparation and generated vendor_kernel_boot.img verification in scripts/build.sh.
  • Hardware validation is incomplete.
  • Current Pixel 9a can run assistant-only APK updates through the privileged /system_ext push flow. Full OTA validation is still required for framework, sepolicy, Settings/SystemUI, boot-chain, and release-signing changes.

Artifacts

  • Source archive: GitHub generated.
  • Development OTA ZIP: pending release staging.
  • Development OTA SHA-256: pending release staging.
  • On-device assistant package metadata: record from scripts/verify-tegu-device.sh for the exact release artifact.
  • On-device assistant APK SHA-256: record for the exact release artifact.
  • Release OTA ZIP: pending physical sideload/runtime validation.
  • Release OTA SHA-256: pending physical sideload/runtime validation.

Flashing Notes

See:

  • docs/BUILD.md
  • docs/TEGU_BOOTCHAIN.md
  • docs/devices/tegu.md

On this page