Amiberry 8.2.0 improves Amiga emulation on Raspberry Pi, ARM64, Android and desktop systems

Amiberry 8.2.0 arrives as a focused update for one of the most practical Amiga emulator projects available today, bringing performance diagnostics, platform fixes and deeper compatibility work across ARM, x86, macOS, Windows, Linux, Android and other supported systems. For users running classic Amiga games, WHDLoad setups, productivity software or more demanding PowerPC-era configurations, this release is less about headline spectacle and more about making the emulator behave better under real-world conditions.

A serious maintenance release with visible gains

The new version continues Amiberry’s role as a WinUAE-derived Amiga emulator tuned for contemporary devices, including single-board computers, desktops and handheld-style systems. That mix matters. Amiga emulation is no longer limited to one kind of user or one kind of machine. Some users want a clean Workbench setup on a laptop, others want a Raspberry Pi connected to a television, and many rely on front-end environments where Libretro integration is part of the daily experience.

Amiberry 8.2.0 targets that broad audience with a set of changes that should be noticeable in different ways depending on the hardware. The update adds a new performance monitor, improves behaviour on slower ARM hosts, refines first-run defaults for Raspberry Pi 4, fixes several JIT-related issues and tightens PPC/QEMU-UAE support. It also brings improvements to Android input handling, Libretro operation, packaging, networking, configuration saving and dependency updates.

Performance monitor puts timing problems in view

One of the most useful additions is the new performance monitor. Emulation problems are often felt before they are understood: a game stutters, audio crackles, input feels late or screen presentation becomes uneven. Without proper diagnostics, users can spend too much time guessing whether the issue comes from CPU load, video timing, rendering, presentation or configuration choices.

The new monitor adds frame timing, render and present timing, and line-rendering diagnostics. That gives users and testers a clearer look at where performance problems occur. For a project supporting so many platforms, this is especially valuable because the same Amiga configuration can behave very differently on a Raspberry Pi, an ARM64 Linux build, a Windows desktop or an Android device.

This is also useful for community support. Instead of describing performance issues only in subjective terms, users can now provide more precise information. That should help narrow down problems faster and make future fixes easier to validate.

Raspberry Pi 4 and slower ARM systems get attention

Amiberry has long been associated with ARM-based systems, and version 8.2.0 keeps that focus intact. Slow ARM hosts now receive a warning and one-click recovery behaviour when the system is overloaded. That is a practical improvement for users who may not understand why their chosen settings are too demanding for their device.

Raspberry Pi 4 users also get a changed first-run approach. The default setup now favours resolution autoswitching rather than immediately lowering accuracy. That is an important distinction. Instead of sacrificing emulation accuracy too quickly, the emulator first tries to manage display demands in a way that may preserve a better overall Amiga experience.

Linux ARM64 builds have also been tuned for Cortex-A72 scheduling while retaining a generic ARMv8-A baseline. In plain terms, the release tries to make better use of common ARM64 hardware without narrowing support too aggressively. For retro computing fans who rely on affordable boards and compact machines, that kind of balance is exactly what keeps an emulator useful beyond high-end desktops.

JIT fixes improve confidence on ARM64 and x86-64

A large part of Amiberry 8.2.0 concerns JIT reliability. Just-in-time compilation is central to high-performance emulation, but it is also one of the areas where small edge cases can cause difficult bugs. This release addresses a broad set of ARM64 JIT problems, including MOVEM predecrement base stores, branch target PC state, LINK A7 fallback, trap PC preservation, indirect rtarea translation and instruction flag regressions.

The x86-64 JIT also receives important corrections, including fixes for pointer-width memory operands, RIP range checking, REX prefix handling and x87/FPU control-word code generation crashes. These are not flashy feature-list items for casual users, but they are exactly the kind of fixes that improve trust in the emulator over time.

For people running more complex Amiga software, demos, operating system setups or edge-case configurations, JIT correctness matters as much as raw speed. A faster emulator is only useful if it remains predictable, and Amiberry 8.2.0 clearly puts effort into both sides of that equation.

PPC and QEMU-UAE support becomes more robust

PowerPC support remains one of the more demanding parts of Amiga emulation, and version 8.2.0 includes several hardening measures around PPC/QEMU-UAE. Fixes target OS4 CyberStorm boot stalls, macOS QEMU thread event handling, executable-state issues on macOS, non-Windows PPC lock creation and disabled or unsupported PPC board states.

This is significant for users experimenting with later Amiga environments and AmigaOS 4-style configurations. These setups are more complex than standard classic gaming profiles, and they place heavier demands on emulation infrastructure. Better PPC handling does not make every configuration effortless, but it does make Amiberry more dependable for advanced users who need this layer to behave consistently.

The release also improves QEMU-UAE PPC plugin packaging and signing support, which should help reduce friction around distribution and deployment.

Libretro, WHDLoad and audio fixes strengthen daily use

For many users, Amiberry is part of a broader retro gaming setup. That makes Libretro support a major practical area, and version 8.2.0 includes several fixes here. The update addresses startup input crashes, WHDLoad booting, lifecycle callback edge cases, input polling, path handling, qemuvga SCSI backend coverage, audio crackle and vblank AV-info churn.

Those changes are likely to matter most to users who want Amiga games to launch cleanly from a front end with minimal manual intervention. WHDLoad reliability is particularly important because it remains one of the most convenient ways to run classic Amiga titles from hard disk-style installations rather than relying on floppy workflows.

Libretro also gains direct 7z disk loading and improved ROM key handling. These are quality-of-life improvements that help Amiberry fit more naturally into organised retro libraries, where compressed media and clean automated launching are often expected.

Android input and interface fixes widen the appeal

Android support also receives attention, with improvements to app launch behaviour, controls, SDL input handling, mouse lifecycle fallback and settings UI constraints. Mobile and Android-based devices can be awkward for systems originally designed around keyboards, mice, joysticks and floppy drives, so input handling is a key part of making Amiga emulation feel usable.

The wider GUI and input layer also benefits from fixes for input capture regressions, uncaptured hotkey modifier remapping, keyboard LED mapping, ROM-dependent list refreshes, WHDBooter cache refreshes and dark-theme startup behaviour. These improvements may sound small individually, but together they reduce the number of rough edges users encounter before they even start running software.

A cleaner base for the next stage

Amiberry 8.2.0 also refreshes SDL3, SDL_image, ImGui, AGP, Gradle, cputester and WinUAE-derived code. CMake configuration and dependency linking have been modernised, while packaging fixes cover Debian builds, PortMidi dependency detection, CPack metadata, macOS app bundles, Windows Libretro stub builds and Android builds after the SDL3 update.

The result is a release that feels carefully engineered rather than cosmetically updated. It improves the emulator’s ability to diagnose problems, recover from overload, handle demanding JIT and PPC cases, and integrate with common retro computing workflows. For Amiga emulator users, Amiberry 8.2.0 is a strong update because it focuses on the details that make emulation dependable: timing, input, packaging, compatibility and platform-specific polish.

For anyone running Amiga software on modern hardware, especially ARM-based systems, Raspberry Pi 4 setups, Libretro environments or advanced PPC configurations, Amiberry 8.2.0 is worth installing. It is not a reinvention of Amiga emulation. It is something more useful: a broad, technical clean-up that should make the experience smoother, easier to diagnose and more reliable across the machines people actually use.