OpenCyvis

The open-source AI phone.
Commercial AI phones are black boxes. This one isn't.

_{Open Cyber Jarvis}

Docs • 中文 • Getting Started • Roadmap • Contributing

---

What It Does

OpenCyvis turns Android into an AI phone. Give it a task in natural language — it sees your screen, understands the UI, and operates apps just like you would.

"Reply 'let's go eat sushi' in WeChat" — opens WeChat, finds the conversation, types and sends:

"Find the best-rated coffee shop nearby and get directions" — opens Maps, searches, sorts by rating, taps navigate.

"Set a 7am alarm, turn on Do Not Disturb, and switch to dark mode" — chains Clock, Settings, and Display in one go.

It works in the background

Most AI tools lock your screen while they work. OpenCyvis operates on a virtual display — an isolated background screen. The AI books your flight while you scroll Twitter.

┌─────────────────────┐    ┌─────────────────────┐
│   Your screen        │    │   Virtual display    │
│                      │    │   (AI works here)    │
│   Browse, chat,      │    │                      │
│   watch videos —     │    │   Booking flights,   │
│   phone is yours     │    │   sending messages,  │
│                      │    │   placing orders     │
└─────────────────────┘    └─────────────────────┘
      You use this              AI uses this

Watch the AI work anytime. Take over if something looks wrong. Hand it back when you're done.

---

Why

When a company ships an "AI phone," they get full access to your screen, your apps, your messages — and you can't see what model is running, can't verify what data leaves your device, can't choose an alternative.

You should at least have the choice.

OpenCyvis is the open-source alternative: you see every line of code, you pick the AI model, you decide where your data goes. With a local model, nothing ever leaves your device.

---

Two Install Modes

Standard Mode

For most users. No custom ROM, no root, no computer.

1. Download and install the APK
2. Open the app and choose ADB wireless pairing or Shizuku as the privilege backend
3. Choose your LLM backend (cloud or local), start using

The built-in ADB wireless pairing flow completes entirely on-device. Alternatively, if Shizuku is already running, grant OpenCyvis access once and no wireless debugging or pairing is needed. Supports Android 11+.

ADB wireless pairing tips

• The wizard sends you to Wireless debugging → Pair device with pairing code. Once you see the 6-digit code, pull down the notification shade and type the code straight into the OpenCyvis notification — no need to switch back to the app.
• Some vendor ROMs (ColorOS / OnePlus, MIUI, …) freeze apps once they go to the background. If the system asks you to allow background activity / ignore battery optimization during pairing, choose Allow for a smoother experience.
• If you don't see the notification with the input field, just pull down the shade once to find it.

System App Mode

For developers and power users.

Flash an AOSP system image. The app runs as a system application with full platform signing privileges. Screenshots use SurfaceControl directly — fastest possible. Full virtual display task management via system APIs.

How they relate

Same AI engine, same LLM backends, same UI, same capabilities. The only difference is how the app obtains system permissions. Standard mode uses ADB shell or Shizuku privileges; System App mode uses platform signing. For everyday tasks, you won't notice the difference.

---

v2.0 New Features

Remote Control via IM

Send messages to a bot in your IM app to control the phone's AI remotely. Currently supports Feishu and Telegram.

Use case: Install OpenCyvis on a parent's phone. Mom says "the text is too small" — you send "set font size to largest" in IM. The AI does it and sends back a confirmation screenshot. No need for both parties to watch the screen simultaneously.

Supports: sending commands, receiving progress, viewing screenshots, answering the AI's questions, stopping tasks. Pairing uses a 6-digit code.

Routines

Save frequent operations and run them on a schedule or with one tap.

Example: "Check calendar, weather, and unread emails every morning at 8am" — the AI runs automatically and pushes a summary to chat. Also supports geofencing — auto clock-in when arriving at the office.

Provider Profiles

Save multiple AI configurations (e.g., cloud Qwen, local Gemma 4, Claude) and switch between them with one tap. No need to re-enter API URLs and keys each time.

Dark Mode

Full day/night theme. Follows system settings or set manually. All screens — home, chat, settings, watch mode — have matching dark variants.

Multi-ROM Support

Standard mode now supports MIUI, ColorOS, OriginOS, and other vendor ROMs. Different manufacturers have vastly different wireless debugging entry points — OemHelper handles the differences.

---

How It Compares

---

Supported Models

OpenCyvis is model-agnostic. Bring your own AI account, connect a private service, or run a local model.

Cloud Models

Local Models (via Ollama)

Recommended: Gemma 4 26B-A4B — best balance of speed, quality, and memory.
Minimal: Gemma 4 E2B — just 1.8 GB, still passes all 4 tests.

---

Architecture

Both install modes share all upper-layer code. The difference is only in the privilege layer, isolated behind a PrivilegeBackend interface:

The backend is selected automatically at runtime.

---

Privacy & Security

An AI agent with full phone access is one of the most privileged pieces of software you can run. This is not a place for "trust us."

• You choose the AI service — hosted, private, or local
• No telemetry, no analytics, no phone-home — zero tracking code
• Open source — anyone can audit
• Local model option — nothing leaves your device

---

Getting Started

Download

Two APKs are available on the Releases page:

Standard Mode (recommended)

1. Download opencyvis-standard-release.apk and install
2. Open the app and choose ADB wireless pairing or Shizuku
3. Configure your LLM provider in Settings
4. Start sending tasks

Use the built-in ADB wireless pairing flow by entering the 6-digit code in the OpenCyvis notification and allowing background activity if your ROM prompts for it. Alternatively, if Shizuku is already running, simply grant OpenCyvis access—no wireless pairing is required.

System App Mode

For developers building a custom AOSP image:

git clone https://github.com/opencyvis/opencyvis-phone.git
cd opencyvis-phone/android
./gradlew assembleSystemRelease

See android/README-AOSP.md for AOSP deployment and platform key signing.

Configure LLM

Set your provider in-app, or via deeplink:

# Local Ollama (fully private)
adb shell am start -a android.intent.action.VIEW \
  -d "opencyvis://config?provider=ollama&base_url=http://localhost:11434&model=gemma4:26b"

# Cloud API
adb shell am start -a android.intent.action.VIEW \
  -d "opencyvis://config?provider=openai&base_url=https://api.example.com/v1&api_key=YOUR_KEY&model=qwen-vl-max"

---

Roadmap

• Explore more convenient privilege acquisition methods
• Further optimize local model support
• Cross-device coordination (phone + desktop)

---

Contributing

See CONTRIBUTING.md. We welcome code, bug reports, security audits, translations, and documentation.

License

Apache 2.0

Acknowledgments

• Sherpa-ONNX — on-device speech recognition (Apache 2.0)

OpenCyvis v2.0.1

Downloads

Changes since v2.0.0

• ADB wireless pairing — split-screen OTP entry + on-device number pad, no need to leave Settings to type the code
• ColorOS / OnePlus fix — discover pairing port at submit-time so aggressive OEM freezers (HansManager) no longer kill the pairing service
• Privileged permissions — added INTERACT_ACROSS_USERS_FULL (ShizukuProvider multi-user) and SCHEDULE_EXACT_ALARM (scheduled routines / BootReceiver) to AOSP allowlist
• AOSP integration — updated Android.bp optional libs, renamed prebuilt APK to OpenCyvis.apk
• Battery optimization prompt — user can exempt the app from OEM battery savers that suspend the pairing service

Signing

• standard APK: signed with opencyvis-release key (RSA 4096)
• system APK: unsigned — sign with your platform key before pushing to /system/priv-app/