1.24.0
These release notes cover new features and changes in Anbox Cloud 1.24.0.
Anbox Cloud 1.24.0 is a minor release. To understand minor and patch releases, see Release notes.
Please see Component versions for a list of updated components.
Requirements
See the Requirements for details on general and deployment specific requirements to run Anbox Cloud.
New features & improvements
Updates to components
- Anbox Cloud includes and uses the following latest versions for components it uses:
- LXC version 6.0.2
- Mesa driver version 24.2.4
- VirGL renderer version 1.9.0.
Security
- We have enhanced security with a minimum version of TLS 1.3 as a requirement for all services working with Anbox Cloud. TLS 1.3 is also enabled by default for the Anbox Stream Agent and Gateway.
Anbox Management Service (AMS)
- We have increased the maximum number of queued operations in AMS to allow better performance.
- AMS supports querying the image variant (
android
oraaos
) for Anbox Cloud images. - The web client, for example, the Anbox Cloud dashboard can communicate with multiple AMS instances.
Android
- This release includes Android 14 based AOSP and AAOS images.
- We now support using the lock screen in Anbox Cloud(LP 1983426).
- For the Android 14 image, the out of band v2 feature in Anbox Cloud requires the Android app to be running to receive broadcasts. If the app is in the cached state, the system places context-registered broadcasts in a queue and hence the app may not receive broadcasts immediately as it would when it is running.
Charms
- For the NFS Operator charm for Anbox Cloud,
Cachefilesd
is now optional and is used only whenfsc
is provided as a mount option.
Dashboard
- You can now debug a session with the new developer tools on the stream page. Terminal and logs are available in parallel when streaming an instance.
- For mobile streams, a location selector is now available.
- For increased security, HTTPS is mandatory for all connections.
- Image type is auto-detected once application is selected.
- Improved accessibility with a Skip to content button.
Streaming
- Anbox Cloud now provides an option to allow the use of custom fragment shader-based upscaling algorithms for video streaming. This helps you to apply multiple shaders sequentially to perform multi-pass upscaling and replaces the default AMD FidelityFX Super Resolution 1.0 shader. See {ref}
sec-custom-fragment-shader
for more information. - The Anbox Streaming SDK now includes two additional examples that demonstrate shader-based upscaling algorithms integrated with the JS SDK:
Other
- Android security updates for November 2024 (see Android Security Bulletin - November 2024 for more information).
- The Android WebView has been updated to 130.0.6723.73.
Removed functionality
Following deprecation in earlier releases, these functionalities have been removed from Anbox Cloud with the 1.24.0 release:
- Support for Ubuntu 20.04 (Focal Fossa)
Deprecations
There are no new deprecations announced for 1.24.0. For the list of features or components that were deprecated before 1.24.0 and are planned to be removed in future releases, see deprecation notices.
Known issues
-
The following features can be enabled for AAOS images based on Android 14. However, this is not supported and may result in unexpected behaviour. This will be removed in the next patch release:
enable_virtual_keyboard
enable_system_ui
enable_anbox_ime
- Custom Android ID
- Custom system apps
- Boot package support
-
When using the Android 14 image, displaying an activity from a boot package using the
foregroundActivity
option in the Anbox Streaming SDK may not work. This issue occurs due to a native crash occurring in the Android container.
Bug fixes
The following bugs have been fixed as part of the Anbox Cloud 1.24.0 release.
- LP 2064900 If an instance fails and ends up with Error status, the session for the instance is set to Error status as well. When the instance is restarted, the session status remains in Error and it is not possible to stream from the instance again.
- LP 2084897 Null pointer exception when opening Anbox IME.
- LP 2072496 Setting user data while creating an instance with streaming enabled creates an instance but does not allow you to join the session.
- LP 2085098 The dashboard fails to connect to the stream gateway because the value of the
ASG_API_URL
configuration is used to limit the dashboard’s communication. So when the CORS header is set to, for example, the private address of the gateway, the dashboard cannot connect to the gateway. - LP 2084800 The
no_wait
query parameter for thePOST /1.0/instances
endpoint is not documented. - LP 2084120 Anbox WebRTC Data Proxy service takes too long to get started.
- LP 2083795 When reconnecting to the ADB server, the connection is refused.
- LP 2077638 After initialising the Anbox Cloud Appliance, the output of
amc image list
remains empty. This shows that the Anbox Management Service (AMS) has not loaded the image list immediately after the initialisation. - LP 2084253 64-bit only detection on ARM systems does not work and causes a boot failure.
Upgrade instructions
See How to upgrade Anbox Cloud and How to upgrade the Anbox Cloud Appliance for instructions on how to update your Anbox Cloud deployment to the 1.24.0 release.