Meridian Family · docs
How Meridian works
Five Android apps that turn a phone into an AI workstation: models on the phone, Termux with a co-pilot, performance controls and a knowledge cloud, connected through one hub. Built and run entirely on a phone.
01What it is
Meridian is a family of five apps that work as one system. Core sits in the middle: it starts the family, keeps what the apps share, and holds a helper that can change system settings without root. The four apps around it each do one job well and talk to each other through Core.
A plan written in Chat runs in Parallel. Gaming's controls show up in Chat's Tweaks. What one app learns, the others can use.
02The five apps
03Requirements
- Android 11 or newer (Wireless debugging arrived in Android 11).
- Termux from F-Droid or GitHub, plus the Termux:API app. The Play Store build of Termux is outdated.
- Developer options with Wireless debugging, for Core's helper. No root.
- For local AI: enough free RAM and storage for the model you pick. Small models (about 1 to 2 GB) run on most recent phones.
Built and tested on a Samsung Galaxy S26. Samsung and other makers lock some settings even for the helper, so a few controls need root on those phones.
04Getting started
- Install Core first, then Chat, Gaming, Parallel and NullCloud. Open each once so it joins the family.
- In Core, connect the helper: turn on Wireless debugging, pair once with the code Android shows, and Core starts the helper.
- In Termux, allow external apps so Meridian can send commands, and give storage access.
- Optional: install llama.cpp and a first model for local AI (next section).
One block for Termux that installs llama.cpp, connects Termux to Meridian and downloads a first model into ~/models:
pkg update -y && pkg upgrade -y && pkg install -y llama-cpp curl git termux-api mkdir -p ~/.termux ~/models echo 'allow-external-apps=true' >> ~/.termux/termux.properties && termux-reload-settings termux-setup-storage
05How Core works without root
Android lets a computer control a phone over ADB. Wireless debugging lets the phone do it to itself: Core pairs with the phone once, starts a small helper with ADB shell rights, and the other apps ask Core when they need something only the shell may do.
- The helper is started in its own session, outside the app, the same way Shizuku does it, so it keeps running after the pairing screen closes and when Wi-Fi goes off.
- Changes are read back, so you see what the phone really did. Some phones lock settings even for the shell, for example CPU limits on Samsung; those need root.
- No root is needed for the family to work; root only unlocks the few settings the shell may not touch.
06Local AI with llama.cpp
Chat runs models on the phone through llama.cpp in Termux. Put GGUF models in ~/models; Chat starts llama-server on 127.0.0.1:8080 when you pick one. Nothing leaves the phone.
You can also use an online provider with your own key. Web search works without a key through DuckDuckGo; Brave or Google search use your own key if you add one.
07Diagnose
Paste an error, a command or a piece of code into Parallel's Diagnose. It sorts the problem into one of 17 kinds (missing tools, permissions, storage, memory, network, versions, builds, configuration, git, crashes, local models and more), runs read-only checks in Termux, and explains the likely cause with its evidence and how sure it is. Then it offers fixes, from looking closer to repairing. A fix runs only after you approve it, and a failed check sends it back to the diagnosis. Code is checked with the real tools in Termux: Python, JavaScript, C, C++, shell, JSON, YAML, TOML, .env and SQL.
It was tested on 240 failures collected from GitHub issues, Stack Overflow, documentation and forums. On the 203 with real copied output: 175 right, 18 partly right, none confidently wrong.
- Diagnose: read the facts, no changes.
- Approve: you see the exact command.
- Fix and verify: it runs, then Doctor checks that it worked and remembers what did.
08Privacy
- No accounts, no analytics, no tracking.
- Chats, learned cards, recipes and settings stay in the apps' storage on the phone.
- Data leaves the phone only when you use an online provider or web search you chose, and only to that service.
- API keys stay on the phone and are left out of exports.
- This website keeps only your Motion, Level and Colour settings, in your own browser. Listen uses your device's own voice.
09FAQ
Do I need root?
Can I download the apps?
Which phones does it run on?
Does it work offline?
Why five apps instead of one?
Why do the apps look like this?
Was it really built on a phone?
What happens to my API keys?
10About
Meridian is made by Alen Požun, self-taught, building Android apps and local AI on a phone alone. Before that he worked as an IT technician: custom gaming PCs, servers, repairs and system diagnostics. He designs and directs the apps and builds them with AI coding agents.
11Thanks to
Meridian stands on these open projects. Thank you to everyone who builds and maintains them.
X, GitHub, LinkedIn and XDA are trademarks of their owners and are used only to link to profiles. Full notices ship with the apps.