Voyage 20261029 Updates Matrix Messaging

What changed

Voyage 20261029 updates Matrix messaging with scheduled messages, editing gestures, media improvements, and a long list of reliability fixes. The project’s October 29 release record identifies 20261029 as the latest release and lists the changes made since 20261007.

Voyage is an Android Matrix client based on the discontinued Element Classic app. According to F-Droid’s current Voyage listing, the fork adds features and performance work while retaining support for Android 4.0 and newer. The listing describes a client with multiple accounts, homeserver mirrors, encrypted-room search, custom themes, media editing, and extensive support for custom emoji and stickers.

The new release is substantial rather than a single-purpose patch. Its release notes include scheduled messages, swipe to edit, settings search, a persistent audio player, picture-in-picture for video, syntax highlighting, audio extraction from videos, and the ability to reorder attachment previews before uploading them.

Messaging and timeline repairs

Several changes address situations where a conversation could display stale, unstable, or incomplete information. The release notes say Voyage now keeps message jumps stable while the timeline changes, prevents stale refreshes from hiding sent messages, and holds a jumped-to message steady while its timeline loads. Pinned messages can load as their events become available, while historical profiles are shown in mention pills and messages from the same batch.

Other fixes cover specific failure cases:

• An Android 13 crash caused by reading Parcelable intent arguments was fixed.
• Account-switching crashes related to session initialization were repaired.
• A large notification backlog should no longer cause an application-not-responding event.
• Sliding sync should no longer leave an empty room list spinning indefinitely.
• Asynchronous media uploads were corrected so they send the Matrix content URL rather than a local file URI.
• Location sharing, pins, and map previews received fixes.

The release also adds scheduled messages, temporary mutes and bans, and per-room timeline visibility settings. Room and sender presentation received attention too: duplicate display names are disambiguated in reply headers and live sender names, while right-to-left names are prevented from reversing surrounding left-to-right interface sentences, and vice versa.

Privacy context for degoogled phones

Voyage’s F-Droid description says the app has no telemetry, no analytics, and no Google services. It registers for push delivery through a UnifiedPush gateway and normally communicates with the user’s Matrix homeserver. The listing also says Voyage can strip location and other metadata from photos and videos before upload and can block network activity while a configured VPN is disconnected.

Those defaults do not mean every optional feature is self-contained. F-Droid flags the app for optional dependencies on non-free network services. Translation can contact Google, Microsoft, DeepL, DeepSeek, or an OpenAI-compatible service. Telegram sticker imports use the Telegram Bot API, location sharing loads MapTiler maps, and the default integration manager uses scalar.vector.im. On-device translation downloads a large NLLB-200 model from GitHub and a language-detection model associated with Facebook.

That distinction matters on a degoogled phone: the core client does not require Google services, but enabling an optional integration can still create a connection to an external provider. Voyage documents those connections in its store listing so users can decide which features fit their threat model.

What owners should do

1. Open Voyage’s settings or application information and check the installed version. The release discussed here is 20261029.
2. Review the release notes if you have experienced Android 13 crashes, account-switching failures, unstable message jumps, a large notification backlog, or problems with asynchronous media uploads.
3. Examine Voyage’s optional network features before enabling translation, map-based location sharing, Telegram sticker imports, or the integration manager. Each can contact a service beyond your Matrix homeserver.
4. After updating, test account switching, notifications, message editing, media uploads, and any scheduled messages you rely on. The release changes each of those areas.
5. If minimizing network exposure is the priority, leave unused optional integrations disabled and keep photo and video metadata stripping enabled when sharing media.

The result is a broad maintenance and feature release for people using Matrix without Google services. Its most practical changes are the Android 13 crash repair, timeline stabilization, account-switching fixes, scheduled messages, and clearer control over how conversations and media behave.