v2.1.2 — phone-as-node + remote chat UI (test build)

Summary

Test build: optional phone as IDE inference node, plus remote chat bubbles that match native LMPlayground UI.

Features

• Settings → Chidori Desktop → paired instance → Offer phone as inference node (needs a loaded model)
• Registers with desktop companion /node/*; serves local OpenAI-compat /v1/models + /v1/chat/completions
• Remote “chat through desktop” uses native message chrome (markdown/share/copy); “via desktop” banner kept

Install

Prefer arm64-v8a on a physical phone.

Pair with desktop

Use a desktop build that includes companion node accept (lclreason commit “Accept chidori-nagasa as a LAN inference node”). On Mac: git pull then make app.

Pairing still uses companion port 8027. Node offer is opt-in and off by default.

v2.1.1 — LAN pairing fix (test build)

Summary

Test build for companion LAN pairing (manual + automatic) against desktop protocol 1.2.0 on port 8027.

Fixes

• Run OkHttp coordinator calls on Dispatchers.IO so begin/confirm no longer fail with NetworkOnMainThreadException on device
• Authenticate DELETE /pairing/{id} with the bearer token
• Surface clearer pairing failure reasons in the UI
• Unit coverage for the wire contract (OkHttpCoordinatorApiTest)

Install

Prefer arm64-v8a on a physical phone. Pair to the desktop companion address ip:8027 (or wait for mDNS discovery). Pairing code appears in desktop Settings → Companion App.

Requires a desktop build that includes the matching lclreason companion listener fixes (listening status, bind-before-mDNS, retry).

v2.1.0 — protocol 1.2.0 companion port (test build)

Test build for protocol 1.2.0 / app 2.1.0-debug.

What's new

• Dedicated companion listen port default 8027 (not IDE 8080); manual port field prefilled and labeled accordingly.
• Client advertises protocol_version 1.2.0.
• mDNS: prefer IPv4 host; when NSD returns empty TXT attributes, probe GET /version instead of silently dropping the instance.
• Docs: CHIDORI_PROTOCOL.md / WIRE_CONTRACT.md / DESKTOP_HANDOFF.md updated for companion port + single-label mDNS names.

How to test

1. Install app-universal-debug.apk (or app-arm64-v8a-debug.apk on arm64 phones).
2. Ensure desktop companion listener is on 8027 and Settings → Companion App can show the pairing code.
3. Try mDNS discovery; if empty, use manual host + port 8027 (not 8080).
4. Complete pairing and confirm status/runs/chat still work.

Debug build, unsigned — allow install from unknown sources / accept the debug signature warning.

v2.0.2 — pairing error surfaced in UI (test build)

Test build. Builds on v2.0.1-mdns-fix-test (cleartext + mDNS service-type
fix). Since that build still showed the same failure, this adds visible
error detail to the pairing-failed dialog instead of a generic message.

What's new

The pairing-failed AlertDialog (shown after "Nearby on this network" or
manual host:port pairing fails) now shows the actual underlying reason
instead of "Could not reach X. Check it's on the same network.":

• If it's a network/platform exception (e.g. cleartext still blocked,
  connection refused, timeout, DNS failure), you'll see the exception
  class + message directly, e.g.
  IOException: Cleartext HTTP traffic to 192.168.1.5 not permitted.
• If the desktop responded but with a non-2xx status, you'll see
  Desktop returned HTTP 404 for /pairing/begin (useful if the endpoint
  doesn't exist yet on the desktop side).
• Also logged via Log.w under tag "CoordinatorApi" if you have logcat
  attached.

How to test

1. Install app-universal-debug.apk (or app-arm64-v8a-debug.apk for a
   smaller download on an arm64 phone).
2. Attempt pairing the same way you did before (mDNS discovery or manual
   host:port).
3. When it fails, tap through and copy/screenshot the exact error text
   in the dialog — that tells us precisely what's still broken.

Debug build, unsigned — allow install from unknown sources / accept the
debug signature warning.

v2.0.1 — desktop pairing fix (test build)

Test build for the desktop-pairing/discovery fix — not a full release.

What's fixed

• Cleartext HTTP was blocked. Android blocks all http:///ws:// traffic by
  default (API 28+, this app targets 35), so every request to the paired
  lclreason desktop was rejected before it ever left the phone. Added a
  network security config that allows cleartext for LAN pairing, per
  DESKTOP_HANDOFF.md's "no TLS in v1" design.
• mDNS discovery service type had a trailing dot (_chidori._tcp.
  instead of _chidori._tcp), which silently broke "Nearby on this
  network" discovery.
• Added a WifiManager.MulticastLock around discovery — some OEM WiFi
  stacks drop mDNS packets without one.

How to test

1. Install app-universal-debug.apk (or app-arm64-v8a-debug.apk if you
   want a smaller download and your phone is arm64, which almost all
   modern phones are).
2. Make sure the phone and desktop are on the same WiFi network.
3. Try both "Nearby on this network" discovery and manual host:port
   pairing.
4. Confirm requests now show up in the desktop's diagnostic log.

Debug build, not signed for release — you may need to allow install from
unknown sources / allow the "debug" signature.

chidori-nagasa 2.0.0

chidori-nagasa 2.0.0 — the Android companion app, built from main (db0c903).

What's in this release

• New app icon — matches the sister chidori desktop app's branding.
• Coordinator monitor (PRD §6.3): tap a paired instance to see live status (idle/running/error) and a recent-runs list (Ask/Agent/Plan/Debug), with a run-detail dialog.
• Remote chat (PRD §6.4): chat through the desktop's attached model from your phone, in a surface clearly distinct from on-device chat.
• Manual host:port pairing (PRD §6.2): pair even when mDNS discovery is blocked (corporate/guest networks).
• Plus everything from the LM Playground base: on-device inference, vision input, tools, system prompts, chat history, and more.

⚠️ Monitor, chat, and pairing all need a running lclreason desktop that speaks the coordinator API to actually connect. See DESKTOP_HANDOFF.md in the repo — that's the next piece of work, on the desktop side.

Which file to download

• app-universal-debug.apk — installs on any device (arm64 + x86_64). Use this if unsure.
• app-arm64-v8a-debug.apk — smaller, for a normal physical phone.

Install

Download → allow "install from unknown sources" → tap to install. Appears as chidori-nagasa (com.druk.lmplayground.debug), coexists with any Play build. Debug-signed for testing only, not for distribution.

chidori-nagasa 1.8.2 (debug — v1 client complete)

Debug test build of chidori-nagasa 1.8.2-debug, built from main (5f8e401).

v1 client-mode is feature-complete

• Coordinator monitor (PRD §6.3): tap a paired instance to see live status (idle/running/error) + a recent-runs list, with a run-detail dialog.
• Remote chat (PRD §6.4): from the monitor, tap "Chat through this desktop" to chat through the desktop's attached model. Distinct from on-device chat, with a persistent "via " banner and graceful disconnect handling.
• Manual host:port pairing (PRD §6.2): the manual-connection fields now have a working Pair button, for networks where mDNS discovery is blocked.

⚠️ All three need a running lclreason desktop that speaks the coordinator API to actually connect — see DESKTOP_HANDOFF.md in the repo for that side's implementation brief. Without a desktop to pair with, the app shows the empty pairing screen (no "Paired" section, nothing to tap).

Which file to download

• app-universal-debug.apk — installs on any device (arm64 + x86_64). Use this if unsure.
• app-arm64-v8a-debug.apk — smaller, for a normal physical phone.

Install

Download → allow "install from unknown sources" → tap to install. Appears as chidori-nagasa (com.druk.lmplayground.debug), coexists with any Play build. Debug-signed for testing only, not for distribution.

---

Note: this repo no longer auto-deploys to Google Play on push to main — that leftover upstream automation was removed since no publishing credentials are configured for this fork.