MERIDIAN

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

CoreThe hub. Shared data, the activity log, and the ADB helper that lets the family change settings without root.
ChatAI on the phone: local models through llama.cpp in Termux, or a provider you choose. Learned cards, recipes, and plans Parallel can run.
GamingLive CPU cluster and GPU clocks, clock profiles, heat guard and RAM release. Every value is read back, so you see what the phone really did.
ParallelTermux with a co-pilot: one-tap plans, a console that fixes known errors, file tools, and Meridian Doctor.
NullCloudShare a link or paste text: a summary, the steps or answers to your question, kept for the rest of the family.

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

  1. Install Core first, then Chat, Gaming, Parallel and NullCloud. Open each once so it joins the family.
  2. In Core, connect the helper: turn on Wireless debugging, pair once with the code Android shows, and Core starts the helper.
  3. In Termux, allow external apps so Meridian can send commands, and give storage access.
  4. 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
The apps are not publicly released yet. This page explains how Meridian works; there are no downloads here.

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.

Small instruct models in Q4 or Q8 are the best start on a phone. Bigger models answer better but need more RAM and get slower.

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.

  1. Diagnose: read the facts, no changes.
  2. Approve: you see the exact command.
  3. 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?
No. Core's helper uses Wireless debugging. A few settings that phone makers lock, such as CPU limits on Samsung, still need root.
Can I download the apps?
Not yet. Meridian is not publicly released. If you want to know more, use the contact on the main page.
Which phones does it run on?
Android 11 or newer. It is built and tested on a Galaxy S26; other phones should work, but makers lock different settings.
Does it work offline?
Yes, with local models in Termux. Online providers and web search need internet.
Why five apps instead of one?
Each app does one job with only the permissions it needs, and they can update separately. Core joins them into one system.
Why do the apps look like this?
Every app draws its picture live with WebGL2: depth, light running along the lines, particles and the gyroscope. The same engine draws this website and the Showcase.
Was it really built on a phone?
Yes. No PC: Termux on the phone, AI coding agents for the code, GitHub Actions for the builds, and every build is signed and tested on the phone itself.
What happens to my API keys?
They stay on the phone, are sent only to the provider they belong to, and are never included in exports.

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.

libadb-androidApache-2.0Muntashir Al-Islam and contributors. ADB pairing and connection inside Core's helper (used under its Apache-2.0 option).
BoringSSLOpenSSL · ISC · Apache-2.0Pairing cryptography (SPAKE2), packaged for Android by vvb2060.
ConscryptApache-2.0TLS for the helper connection.
Bouncy CastleMITCertificates and keys for pairing.
AndroidX · Jetpack Compose · KotlinApache-2.0Core's app and interface.
TermuxGPL-3.0The Linux environment the family works with. Meridian talks to Termux; it does not include it.
llama.cppMITLocal models on the phone, installed in Termux.
ApktoolApache-2.0Rebuilds Chat, Gaming, Parallel and NullCloud.
Eleven MusicCommercial licenceThe source tracks of the official Meridian track, generated by Alen Požun on a paid plan, then cut and mixed for this website.
Rajdhani · ManropeSIL OFL 1.1The typefaces on this website, served by Google Fonts.
Simple IconsCC0The X, GitHub and XDA logos.
Font Awesome FreeCC BY 4.0The LinkedIn logo.

X, GitHub, LinkedIn and XDA are trademarks of their owners and are used only to link to profiles. Full notices ship with the apps.