Telegram Amiga alpha 0.0.94 is available from September 25, 2026 and takes the native MTProto client to six platforms. The most visible change is the new AROS ARM64 package for Raspberry Pi 4, Pi 400 and Pi 5 running the native AROS image; the work that matters most to daily use is the hardening of persistence, file loading and GUI behaviour.
The project remains a C-based native Telegram client, with an Intuition/GadTools GUI and a TUI sharing the same engine. Version 0.0.94 is not a collection of decorative features: it widens the hardware base, fixes real field failures and prepares the next speed-focused 0.0.95 release.
AROS ARM64 becomes an official distribution lane
With 0.0.94, AROS aarch64 becomes the sixth project lane. The package is built from the same commit as the other five targets and uses the native AROS image for Raspberry Pi 4, Raspberry Pi 400 and Raspberry Pi 5. The first complete round was checked on a Raspberry Pi 400: login, chats, history, photos, documents and a download.
ARM validation did not stop at launching the binary. The chat list, random seed and window geometry must survive a restart, including when the drawer lives on a FAT card. This is the difference between a port that compiles and a target that can actually be used.
The most important fix is in the FAT filesystem path
On AROS FAT, rewriting an existing file in place could leave an empty file while the C library still reported success. The consequences were concrete: a saved login disappeared, the chat list could no longer find its conversations, the seed became zero bytes and the GUI geometry was forgotten.
Version 0.0.94 replaces the fragile path with one common door: files are deleted and recreated, then flushed while still open. The same treatment covers the chat list, seed, avatars, recent emoji, window geometry, downloads to existing names and temporary files before rename. The fix came from a Raspberry Pi report, but the shared code protects every target.
Downloads no longer make the GUI flash
Every progress percentage used to repaint the whole window. With inline photos, that also meant copying the chat content again: on Vampire, photos disappeared and returned during a transfer, while the window became difficult to use.
Progress now repaints only the status strip, copied from the off-screen buffer; if a menu is open, the full-paint fallback remains available. The change gives Vampire about 260 milliseconds back for every 32 KiB part and, more importantly, removes the visible flashing.
ARM loading, self-tests and stack usage
The AROS ARM build enforces -fno-common, because the AROS relocatable ELF loader rejects the COMMON symbols produced by GCC 6.5 defaults. The shared emoji geometry value is explicitly initialized, and the executable now loads directly after make without a manual relink.
The same release reduces GUI test stack usage. A window model larger than half a megabyte is no longer copied into the main routine’s frame, and each test uses one scratch copy per file. The runner drops from roughly 584 KiB to 25 KiB of frames, the tests stay below 10 KiB and both GUI self-tests pass on AROS ARM.
Native icons, previews and international text
Every package now receives Carlo Spadoni’s icons: a coherent set for the platform and an icon for the drawer, which previously had none. AmigaOS 4, MorphOS and AROS keep their native formats; AmigaOS 3.x receives Workbench-compatible colour icons. The credit appears in the About box, README and manuals.
If Telegram already has a link’s metadata in its own cache, the preview now returns directly in the send response. The release also adds a fallback for characters outside Latin-1: Latin Extended-A letters are folded to a readable base letter without changing the UTF-8 text sent over the wire.
Official downloads: Aminet, GitHub and AROS Archives
Alpha 0.0.94 is published for six targets. The first five remain available on Aminet and GitHub; the AROS ARM64 package is distributed on GitHub and The AROS Archives, now served by the operational AROS Archives mirror at OS4Depot.
- Aminet AmigaOS 3.x and the GitHub AmigaOS 3.x release;
- Aminet AmigaOS 4.x and the GitHub AmigaOS 4.x release;
- Aminet MorphOS and the GitHub MorphOS release;
- Aminet AROS i386 and the GitHub AROS i386 release;
- Aminet AROS x86_64 and the GitHub AROS x86_64 release;
- The AROS Archives / OS4Depot AROS ARM64 and the GitHub AROS aarch64 release.
The official repository contains source, documentation and build material. The CHANGELOG and roadmap are the references for technical details. The complete path is collected in the Telegram Amiga development diary; the Italian article is available here, while the previous milestone is covered in the 0.0.93 article.
A concrete portability release
Version 0.0.94 genuinely widens the scene: six platforms, an ARM64 port checked on Raspberry Pi 400, native package icons and fixes born from real hardware and filesystems. The main branch now targets 0.0.95, a transfer-speed release still subject to validation on all six systems. Before the 0.1 beta, the project keeps choosing the less spectacular and more useful path: measure, fix and document.
Sources and materials
- Official Telegram Amiga repository
- All GitHub releases
- 0.0.94 CHANGELOG
- Official roadmap
- The AROS Archives ARM64 package page
- Telegram Amiga development diary
Primary source (checked 2026-09-26): https://github.com/kaffeine1/telegram-amiga/blob/main/CHANGELOG.md
Repository and release metadata: https://github.com/kaffeine1/telegram-amiga
AROS ARM64 package: https://arosarchives.os4depot.net/download.php?file=network/chat/telegramamiga.aarch64-aros.lha