Skip to content

Commit

Permalink
Merge pull request #203 from ajanon/fix_aaos_features
Browse files Browse the repository at this point in the history
Add more features to the unsupported list for AAOS
  • Loading branch information
keirthana authored Oct 29, 2024
2 parents 395f726 + 82be7f4 commit c6dc9e6
Showing 1 changed file with 10 additions and 3 deletions.
13 changes: 10 additions & 3 deletions reference/anbox-features.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,9 @@ The following table lists some Anbox features and whether they are supported for
| boot-package and boot-activity in {ref}`ref-application-manifest` || - |
| {ref}`howto-install-apk-system-app` || - |
| [Custom Android ID](#custom-android-id) || - |
| [System UI](#system-ui) || - |
| [Virtual Keyboard](#virtual-keyboard) || - |
| [Client-Side Virtual Keyboard](#client-side-virtual-keyboard) || - |
| {ref}`VHAL HTTP API <sec-anbox-https-api-vhal>` | - ||
| [VhalConnector](https://canonical.github.io/anbox-cloud.github.com/latest/anbox-platform-sdk/classanbox_1_1VhalConnector.html) in Platform SDK API | - ||
| {ref}`exp-custom-images` | - ||
Expand All @@ -33,23 +36,27 @@ To configure a feature for one application in the manifest, use a syntax similar

### System UI

*since 1.10.2*
*since 1.10.2, supported on AOSP images only*

By default, Anbox hides the Android system UI when an application is running in foreground mode. In some use cases, however, it's required to have the system UI available for navigation purposes. This can be enabled with the `enable_system_ui` feature flag.

The feature flag will be considered by all new launched instances once set.

On AAOS, the Android Car system UI is always enabled and cannot be disabled.

### Virtual Keyboard

*since 1.9.0*
*since 1.9.0, supported on AOSP images only*

The Android virtual keyboard is disabled by default but can be enabled with the `enable_virtual_keyboard` feature flag.

For the feature to be considered, applications must be manually updated, because changes to allow the feature to work are only applied during the application {ref}`bootstrap process <sec-application-bootstrap>`.

On AAOS, the Android virtual keyboard is always enabled and cannot be disabled.

### Client-Side Virtual Keyboard

*since 1.11.0*
*since 1.11.0, supported on AOSP images only*

The client-side virtual keyboard is disabled by default but can be enabled with the `enable_anbox_ime` feature flag. It requires the client application to embed {ref}`Anbox WebView <sec-application-bootstrap>` which interacts with the client-side virtual keyboard for text editing and sends the text to the Android container.

Expand Down

0 comments on commit c6dc9e6

Please sign in to comment.