Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Android app

The Android app is a remote control device for your phone. It scans the QR code a Fontaine host shows, pairs through the confirmation in the host terminal, and then drives the live session: it shows the transcript, sends prompts and slash lines, answers approvals and questions, and interrupts a turn. It is a sideloaded APK; there is no store listing.

Install

Download fontaine-android.apk and fontaine-android.apk.minisig from a tagged release, or the latest dev build of main from https://github.com/madesroches/fontaine/releases/download/dev/fontaine-android.apk, verify the signature as described in Verifying releases, then open the APK on the phone and allow your browser or file manager to install apps from unknown sources when Android asks. The app needs Android 8 (API 26) or newer, an arm64 phone and OpenGL ES 3.

Android’s own install signature only lets the system install and update the package. The minisign signature is what proves who made the file.

Dev and release APKs are signed with different Android keys, so Android refuses to install one over the other; uninstall the app first to switch. Dev builds are signed with one stable key and each has a higher version code, so they update in place.

Pair

  1. On the host, run fontaine --remote, or /remote-control or /remote on in a session. A QR code appears in the ticket dialog.
  2. Open the app and point the camera at the code, or scan it with the system camera: Android offers to open Fontaine and lands on the same screen. The system camera only works when the app is not already running; a link opened while it runs is ignored, so use the in-app scanner or paste instead.
  3. The app shows “Pair with <host id>?”. Nothing connects until you agree.
  4. The host terminal asks you to confirm the device. Press y there. The app moves on to the session when the host says the pairing is done.

The code carries a fontaine://pair/… link. A link only asks to pair: any app or web page can open it, and the ticket inside is a secret. Only the confirmation in the host terminal authorizes the phone, so decline a pairing prompt you did not start. The app does not keep the link after reading it. The phone’s name on the confirmation line is its model name.

The scan screen keeps clear of the status bar, the display cutout and the keyboard. It shows a card with the live camera image behind a “Scanning” label while the camera is live, and “Camera access is off” with an “Allow camera” button when it is not, then a paste field and, when the phone is already paired, the list of paired hosts. The image is grayscale, taken from the same frames the QR decoder reads, kept upright when the phone rotates, and cropped to fill the square. Frames are held in memory only until the next one replaces them; nothing is stored.

If the camera is off or denied, copy the link, the prefixed ticket or the bare ticket text, hold the field on the scan screen and tap Paste, then “Use this”. The camera permission is requested when you tap “Allow camera” on the scan screen.

Reattach

Paired hosts are listed on the scan screen. Tap one to connect without scanning again, while the host has remote control on. A host that revoked the phone, or no longer knows it, shows the reason (this device was revoked and must pair again); pair again with a new ticket.

Editing the message field

The paste field on the scan screen and the message field in a session are edited in place:

  • Tap the text to put the cursor there; typing and Backspace act at the cursor, and the left and right D-pad keys of a hardware keyboard move it, and Delete deletes forward.
  • Hold a word to select it, or hold and then drag to select a range; the selection follows your finger across wrapped lines. Typing replaces the selection.
  • Releasing a hold opens a menu: Cut and Copy when something is selected, Paste and Select all always. Paste in a session inserts the clipboard text at the cursor, over the selection; in the scan screen’s paste field it replaces the whole field with the trimmed text. Cut and Copy put the selection on the system clipboard.

Swipe typing and dragging the spacebar to move the cursor are not supported: the app has no Java input-method connection, so the keyboard delivers key presses only.

In a session

  • The transcript follows the host, and the status line shows the model, mode and branch.
  • The message field sends a prompt. A message that starts with / is sent as a slash line and runs only if the command is on the device list. A message is at most 8 KiB.
  • Interrupt stops the main turn when one is running.
  • An approval shows the tool, the reason and any diff, with the choices the host offered: allow once, allow for the session, deny. “Always allow” is never offered, because it writes a permanent rule on the host. A question takes one option; a multi-select question is answered at the host.
  • Elicitations, the pairing confirmation and other host-only dialogs show “the host is waiting on …”.
  • While the connection is down the app shows that it is reconnecting and resumes without a new pairing. A dropped connection never answers a dialog.

The app sends the same messages as fontaine attach, so the host’s floor, guardian, device command list and attribution by node id apply unchanged, and the ledger records the phone’s node id.

Limits

  • The app has no TalkBack or other accessibility support.
  • The device key lives in the app’s private storage, readable only by the app. It is not wrapped by the Android Keystore.
  • One session at a time; there is no session list, push notification or LAN-only mode.
  • Questions allow one option each; typed answers and multi-select answers happen at the host.
  • The app reads what the host publishes leniently: an entry kind the app does not know is skipped.