1.22.0¶
The Anbox Cloud team is pleased to announce the release of Anbox Cloud 1.22.0.
Please see Component versions for a list of updated components.
New features & improvements¶
The 1.22.0 release of Anbox Cloud brings the following features and improvements:
Core stack improvements¶
Support for 64-bit only systems for all supported Android versions.
Support for installing relevant 32-bit NVIDIA userspace binaries on AMD64 systems.
To allow easier identification and use of instances, you can now explicitly name an instance when creating it. See How to create an instance.
VHAL enhancements:
Configuration returned by the APIs have a new field containing a name and a list of area names for the standard VHAL properties.
Property values returned by the APIs have a new field containing a list of area names for the standard VHAL properties.
You can replace the Anbox Cloud VHAL implementation with your custom implementation for AAOS images. See How to use a custom VHAL implementation.
Streaming stack improvements¶
Streaming can now be enabled when launching an instance using the
--enable-streaming
option. Existing installations will require the charm deployment for Anbox Cloud to be manually upgraded to use the new relation between the AMS and the stream agent.See How to stream applications and How to create an instance for details on launching stream-enabled instances. See How to upgrade Anbox Cloud for instructions on manually upgrading the relation between the AMS and the stream agent charms.
VirGL is the default renderer for NVIDIA GPUs with driver version 545 and later. For driver versions earlier than 545 or old NVIDIA GPU architecture such as Turing, Ampere or Ada, EmuGL is used as the default renderer. See Rendering architecture.
Experimental support for pointer lock is available with this release. This helps in locking the pointer to a particular browser element, for example, your game window, and limits movement outside the game until the lock is disabled. The pointer lock property must be explicitly enabled on the stream object via the streaming SDK.
All components of Anbox Cloud upgrade to NVIDIA 550 driver series by default on Ubuntu 22.04 images. For Ubuntu 20.04 images, 535 driver series will be used.
Dashboard improvements¶
The following improvements are available in the Anbox Cloud dashboard for this release:
Page level guided tours are now available for help in navigating through the dashboard.
Support for using custom authentication server instead of Ubuntu SSO.
Custom instance name field in Create instance form.
User experience enhancements to the AAOS control panel:
Extending VHAL support to allow setting the geographic location and to be able to provide and revoke consent for enabling APIs in the browser when using maps.
Enhancements to forms to support AOSP vs AAOS applications.
Other¶
Support for building custom images of Anbox Cloud based on AAOS. See Custom images.
Android security updates for May 2024 (see Android Security Bulletin - May 2024 for more information).
The Android WebView has been updated to 124.0.6367.82.
Deprecations¶
See Deprecation notices for a list of deprecations in this release.
Removed functionality¶
Documentation on how to enable VirGL manually is removed because with this release, VirGL is the default renderer for NVIDIA GPUs.
Known issues¶
The following known issues exist in the 1.22.0 release and are planned to be fixed in future releases:
Video playback does not work on 64-bit only systems where the NVIDIA GPU is installed.
For existing charmed deployments, creating instances with streaming enabled using the
enable-streaming
option requires manually adding the new relation between the AMS and the stream agent charms. See How to upgrade Anbox Cloud.To work around issue 13420 in LXD, run the following command after deploying a new unit of the LXD for Anbox Cloud charm:
juju ssh lxd/n -- lxc storage set ams0 volume.zfs.block_mode=false
This workaround needs to be applied to every LXD node deployed using the LXD for Anbox Cloud charm. Otherwise, instances launched via AMS fail with an error similar to the following:
Error: Failed creating instance from image: Failed to run: zfs set volsize=3000000512 ams0/containers/ams-cp1pjd7lra53mbq42mug: exit status 255 (cannot set property for 'ams0/containers/ams-cp1pjd7lra53mbq42mug': 'volsize' must be a multiple of volume block size (16K))
Bugs fixed¶
LP 2061700 When streaming from an instance that is based on an AAOS image, the following error is displayed on the right panel:
VHAL error, could not get fan positions
LP 2060110 Keyboard is not displayed in the Honkai: Star Rail.
LP 2045823 Keyboard display flickers in Monopoly Go.
LP 2059887 Sluggish performance when playing Honkai: Star Rail.
LP 2058423 Compatibility issues with Monopoly Go and Marvel Strike in Vulkan mode causing the games to end abruptly.
LP 2056707 Android system unable to boot due to the error:
Extension not supported: VK_KHR_swapchain
.LP 2056527 Android stops working with the error
MESA-VIRTIO: failed to create nv_mem from dma_buf
.LP 2046249 Deleted applications leave behind base instances in Error state.
LP 2060023 Missing
min
values for VHAL properties.LP 2060605 The post-stop hook fails to be called when terminating a session via the gateway DELETE endpoint API.
LP 2061741 VHAL panel displays empty values for VHAL properties.
Compilation errors when building Anbox kernel modules on kernel 6.8
When using the web dashboard, occasionally the VHAL panel does not appear due to timing issues between the stream client, the stream gateway, the stream agent and the server.
When running Anbox Cloud with VirGL enabled on NVIDIA L4 GPUs, Android stops abruptly on startup with the following error:
vtest_resource_create_blob called virgl_renderer_resource_create_blob which failed (-1)
Upgrade instructions¶
See How to upgrade Anbox Cloud or How to upgrade the Anbox Cloud Appliance for instructions on how to update your Anbox Cloud deployment to the 1.22.0 release.