信驿 Relay

Xinyi Relay is an adaptive Android relay and verification-code autofill project. It uses Enhanced mode when a live Xposed/LSPosed runtime is available and otherwise falls back to Standard Android APIs, with unified handling for SMS, app notifications, and incoming call events.

The project now ships in three major parts:

Android App: local event capture, verification parsing, autofill, and Xposed hooks

Backend: device binding, per-device config mirrors and command queues, record upload, and cloud Web console

Desktop App: cross-platform management tool with a built-in local SQLite database, supporting standalone offline execution and cloud sync

The old embedded WebUI has been retired from the Android runtime path. The current official architecture is Android Agent + Backend / Desktop working collectively.

Android App

The Android app is a runtime-adaptive agent. Enhanced and Standard use the same APK, app identity, database, and settings; Xposed is optional unless hook-only capabilities are required.

Install & Use

Install Xinyi Relay:

GitLab Releases: APK downloads

Google Play: Store distribution

In Standard mode, grant only the SMS, MMS, call, or notification-listener capabilities declared by the installed distribution. Denying one permission disables only that capability.

If you need hook interception, system-level SMS blocking, or hook keep-alive features, optionally root the device and enable the same app in LSPosed/Xposed; no separate lite APK is required.

Configure sender channels, routing rules, filters, and verification-code policies.

Compatibility

Minimum Android 8.0 (API 26).

Designed for AOSP-like systems; heavily customized ROMs may have compatibility issues.

Core Features

SMS relay: relay verification SMS and plain SMS with rules

App notification relay: bind apps to sender channels

Call-event relay: capture and relay incoming-call metadata

Global and app-level filtering: keywords, sources, priorities, and forward filters

Verification code parsing, copy, and autofill

Verification-code rules: bundled official read-only rules, refreshable cache, and user custom rules are merged in layers

Records and backup: export/import config and history

Work-mode Boundary

Enhanced/Standard are runtime states, not Play/GitHub/E2EE distribution flavors.

Xposed service bind/death immediately re-resolves the mode and reconciles the Standard foreground service and call monitor.

Post-install phone-process restart is requested only after a successful Xposed service bind; ordinary Standard startup never probes root or restarts telephony/MMS processes.

The Standard keep-alive service uses the remoteMessaging foreground-service type, so boot recovery does not inherit Android 15's dataSync start restriction or cumulative timeout.

Standard MMS metadata is decoded by a bounded Notification.ind parser shipped in the APK, while ended-call enrichment uses finite, cancellable CallLog retries only when the number is missing.

Google Play keeps a policy-compliant Standard subset centered on notification forwarding, while GitHub distributions can enable broader SMS/MMS/call capabilities when the user grants them.

Backend

The Backend is the self-hosted remote control plane for Xinyi Relay, with a local-first deployment model and optional public access.

Stack

Go API

PostgreSQL

Caddy

Web console

Default Deployment

Docker Compose pulls docker.io/alpha317/xinyi-relay-backend:beta by default

Android Agent, Web, and Desktop share the same backend API

Local HTTPS uses Caddy tls internal, with user CA installation available for Android Agent

Entry Docs

Backend Guide

Backend API Overview

Desktop parity and capability inventory

Log Locations

Both Backend and Desktop support log file output for troubleshooting:

Backend Docker: backend/logs/backend.log (configure RELAY_LOG_FILE in .env)

Desktop:

macOS: ~/Library/Logs/io.github.magisk317.relay.desktop/

Windows: %APPDATA%\io.github.magisk317.relay.desktop\logs\

Linux: ~/.local/share/io.github.magisk317.relay.desktop/logs/

See each component's README for details.

Desktop

The desktop app is built with Kotlin Multiplatform + Compose Multiplatform (currently shipping Linux x64 / arm64 packages). It has been upgraded to a fully-featured client, supporting three distinct modes:

Local Mode: Runs completely offline, using its built-in SQLite database to manage devices, configs, and history records for maximum privacy.

Remote Mode: Acts as a traditional thin client, connecting directly to your self-hosted Backend instance.

Hybrid Mode: Prioritizes ultra-fast local response times, seamlessly syncing bidirectionally with the Backend instance when needed.

Desktop Release Notes

Desktop releases currently ship Linux x64 and arm64 deb packages, plus an uber jar for the same architecture (a no-install form, assets prefixed kmp-).

There is no automatic updater; upgrading means downloading the new package manually.

Desktop credentials live in the system keychain (secret-tool on Linux), never in a plaintext config file.

Feedback and suggestions are welcome.

Documentation

Release Logs

Custom Broadcast Interface

System Architecture & Runtime Refactoring Codebase Architecture

Backend Guide

Backend API Overview

Privacy Policy

Donations

Shared CI logic is pinned to one immutable magisk-ci-toolkit commit across GitLab includes, job variables, and the local/GitHub resolver. The resolver uses exact fetch and must not default back to a floating main ref.

Thanks To

XposedSmsCode

LSPosed API

SmsForwarder

NekoSMS

Material Dialogs

EventBus

Room

Kotlin Serialization

Kotlin Coroutines

Material Design 3

Jetpack Compose

License

All code is licensed under GPLv3.