⚠️Important Beta Relase Information⚠️
This is a beta release. Please expand this drop-down to read more about what this means before installing.
As a beta release, this build is not yet considered a stable release, but is instead a build which exists to allow users to test new features and help us discover bugs before a stable release is published.
If you are unwilling to tolerate potential minor issues, you may be better off waiting until the beta release is promoted to a full release.
It is advised to back up your Azahar user data directory before using a pre-release build.
Azahar 2123.4 is an unscheduled minor release which primarily targets several critical issues which were discovered since the last release, some of which were caused by upstream changes.
Please read the change log for further details.
Work continues on the 2124 major release, and you can track its progress here.
New download options:
Android
- The Android build has been split into two new download options, those being the
vanillaandgoogleplaybuilds.- The
vanillaversion uses a new method of filesystem access which is significantly faster and more simple, but isn't permitted by the Google Play store due to its use of theMANAGE_EXTERNAL_STORAGEpermission.- This new system is in its infancy, and is mostly the same as the
googleplayvariant, so the performance improvements won't yet be apparent. Filesystem performance should noticeably improve in the next few major releases as more functionality is migrated to the new system.
- This new system is in its infancy, and is mostly the same as the
- The
googleplayversion is compliant with Google Play Store regulations, and uses the old SAF-based method. This build will not see the performance improvements present in thevanillabuild. - Unless you have a particular reason to use the
googleplaybuild or you are downloading the app from the Google Play Store, thevanillaversion is recommended.
- The
Linux
- The AppImage build has been split into two new download options, those being
azahar.AppImageandazahar-wayland.AppImage- The default
azahar.AppImagenow has native Wayland support disabled, instead opting to use XWayland when run in a Wayland session. This is due to some severe upstream issues that have been discovered when using native Wayland with Azahar (e.g. #1191) - Users are advised to use the default AppImage unless they have a specific reason to have native Wayland support enabled, for example if they are running a system with no xwayland support.
- The default
Azahar 2123.4-beta2 Changelog
Desktop
- Fixed an issue where the emulator could instantly crash when starting an application due to a race condition. | @OpenSauce04 #1448
Android
- Fixed an issue where, if an application attempted to rename a file to a different location, the file wouldn't be moved, and the file would just be renamed in the same directory it was previously in. | @OpenSauce04 #1545
- This notably fixes an issue where Nimbus 2.x wouldn't install its files correctly.
- Implement new build variant which uses raw filesystem access for file I/O. | @OpenSauce04 #1511 #1542
MacOS
- Fixed an issue where attempting to use a real camera for camera emulation would result in solid green video output from the camera. | @OpenSauce04 #1515
Linux
- Disabled native Wayland support in default AppImage, Create new AppImage download option with native Wayland support enabled. | @OpenSauce04 #1499
Technical
- Fixed a build failure in the AppImage build caused by an upstream change to linuxdeploy. | @OpenSauce04 #1486
- Added
relWithDebInfoLitebuild profile. | @OpenSauce04 #1498 - Upgraded AGP to 8.13.1. | @OpenSauce04 #1500
- Updated Boost to v1.89.0 | @PabloMK7 #1502
Note: The version number above is correct: 2123.4-beta1 was tagged but never published.