The chat list and message notifications now say "Video call" or
"Voice call" for a call's ring (org.matrix.msc4075.rtc.notification)
and "Call declined" for its decline, as the web client does.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The display name an admin sets was only on the admin API, so the app
could not show it. /capabilities now carries it as io.warp.server
({"display_name": ...}, left out while there is none), and the About
row's title is that name, falling back to "Homeserver".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An App lock switch in Settings asks to confirm it's the user at start and
after more than a minute in the background, and covers the app in the
app switcher. local_auth needs a FlutterFragmentActivity, USE_BIOMETRIC
and AppCompat themes on Android, and a Face ID usage string on iOS.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
encryption.enabled / WARP_ENCRYPTION_ENABLED (default true) joins the
runtime switches, with allow_runtime_toggle. Off, the homeserver refuses
m.room.encryption from its users, in createRoom's initial_state or sent
as state, and tells clients not to offer it: io.warp.e2ee in
/capabilities and Element's io.element.e2ee in the client well-known,
now cached for five minutes. Rooms already encrypted stay so.
The admin panel gets an Encryption page, a dashboard badge and the audit
action; the web and mobile apps stop encrypting new rooms while the
server says no. Every .env example, warp.yaml.example and the docs
describe it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Calls keep going with the app in the background: a foreground service
(CallService.kt, driven from lib/matrix/call_service.dart) declares the
microphone, the camera while it's on and the screen while it's shared.
Its notification (CallStyle) shows the call's length, opens the call
and hangs up. Swiping the app away ends the call.
- Screen sharing on Android: consent, then media projection on the
service, then LiveKit publishes a screen-share track. A shared screen
replaces the sharer's camera on their tile, shown whole and unmirrored;
stopping it from Android's controls stops the share.
- Read receipts per thread (MSC3771): an open thread sends receipts with
thread_id, "Read" under replies comes from receipts in the thread, and
threads with unread replies get a dot on "N replies" and in the list.
Not tested on a device yet. README updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Found testing calls between two phones on the Compose call stack:
- The famedly SDK keeps only "important" state in memory for a room that
hasn't been opened, so call memberships of other rooms were invisible:
no ring (it was cleared at once, the call looking empty), no room-list
marker. org.matrix.msc3401.call.member is now important state.
- The incoming-call card closed itself with Navigator.pop when the ring
cleared, which popped the call screen pushed above it on Answer. The
buttons now close the card first, and it closes itself only while it
is the top route.
Tested: a voice call in a room of two (ring, answer, both connected
through LiveKit), and a video call in an encrypted room (to-device media
keys, frame cryptors OK on both sides, each phone showing the other's
video). The web client sees a phone's membership and rings for its
notification.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Calls the way the web client and Element Call do them, with the same
events, so the three can share a call. The famedly SDK's own group calls
use com.famedly.call.member events, which the others don't read, so this
is written against the matrix-js-sdk wire format instead (lib/matrix/
calls.dart):
- Membership: org.matrix.msc3401.call.member state, key
_@user:server_DEVICE_m.call, with the legacy session fields the js-sdk
sends (application m.call, call_id "", membershipID, expires,
focus_active, foci_preferred). An empty delayed copy (MSC4140) is
scheduled first and pushed back every 5 s; leaving sends the empty
state and cancels it.
- Media: a LiveKit token from the JWT service (the call's, else the
homeserver's rtc/transports or .well-known rtc_foci) for an OpenID
token; livekit_client connects.
- Encrypted rooms: a random 16-byte key per device, sent to every other
device in the call over encrypted to-device
io.element.call.encryption_keys, keys from others applied per LiveKit
identity (@user:server:DEVICE); per-participant keys, no ratcheting,
HKDF, like the web client's livekit-client.
- Ringing: a call started in a room of two sends a ring notification
(MSC4075); the other side gets an incoming-call card and an insistent
ringtone notification (full screen on a locked phone), declines with
MSC4310 or answers by joining. The caller gives up after a minute or on
a decline.
- UI: voice and video buttons in the room header, a call screen (the
other person large and you in the corner, or a grid; mute, camera, flip,
leave), a Join banner and a room-list marker for calls going on.
Not tested end to end yet: it needs a LiveKit SFU and JWT service.
README: replies, reactions, threads, spaces, QR verification, sliding
sync and calls.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Mobile:
- The room list's title picks a space: All chats, or one space, which
narrows the list to its rooms (and its subspaces' rooms).
- A space browser over /hierarchy: the rooms of a space and of its
subspaces, joined or joinable, with Join; for those who may, adding an
existing room or a new one to the space.
- New space in the new-chat sheet; invites to spaces show with the other
invites and open the space when joined.
- Fixes several setState calls that were handed a Future (reloading the
members, sessions, push distributor, threads), which Flutter rejects.
Server: /hierarchy left out children_state for a room without children.
The spec requires it on every room (an empty list), and SpaceRoom's
omitempty dropped empty lists too, despite its comment. The famedly Dart
SDK fails to parse such a response. The client API now wraps each room so
the field is always written; the federation response, which wants it left
out of the children it lists, is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Replies: Reply on a message's long press puts it above the composer;
sent replies quote the message they answer (sender and first line),
with the reply fallback left out of the body.
- Reactions: six quick ones and any other on long press, chips under the
message with counts, the user's own highlighted; tapping a chip adds or
takes back a reaction, a long press lists who reacted.
- Threads: Reply in thread opens a thread view (the root, then its
replies, older ones fetched from /relations, new ones live from the room
timeline) with a composer that sends into the thread. Thread replies
are hidden from the main timeline; the root shows "N replies". Room info
lists the room's threads (/threads).
The composer moved out of the room screen into widgets/composer.dart so
the room and thread views share it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
apps/mobile is a Matrix client for Android on the famedly Matrix Dart SDK,
with vodozemac (compiled from Rust during the build) for end-to-end
encryption. It speaks the plain Client-Server API and uses the web
client's design tokens, fonts and symbol.
- Sign in by server name (.well-known), homeserver address or full user ID;
sign up with the dummy and registration token stages. Sessions survive
restarts: SQLite in private storage, credentials also in the Keystore,
both excluded from backups and device transfers.
- Room list with unread and mention counts, invites, search and filters.
Timeline with grouping, day separators, notices, history on scroll,
links, images and files (authenticated media). Sending text, photos,
camera shots and files, with Sending/Sent/Read/Not sent and Retry.
Typing, receipts, deleting. New rooms and DMs, encrypted by default;
joining by address; room info with members, invite, rename, topic,
notification level, leave.
- Encryption: one-step setup behind a recovery key, verifying a new session
with the recovery key (restoring the backup) or another session, emoji
verification of people and sessions, reset. Undecryptable messages say
why. Session list with verify and sign out.
- Notifications while running, and push through UnifiedPush (no Firebase):
the distributor's endpoint becomes an event_id_only pusher, the gateway
is discovered, and a push starts the app headless to fetch, decrypt and
show the event.
Make targets: mobile (release APKs per ABI into bin/), mobile-run,
mobile-test. Kotlin incremental compilation is off (Windows, project and
pub cache on different drives), and Tink's JVM artifact is excluded in
favour of tink-android.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
