Test using the configurable emulator
Stay organized with collections
Save and categorize content based on your preferences.
To help emulate some of the configurations seen across OEMs, certain hardware
profiles support runtime
configurability.
These configurations are implemented using Runtime Resource
Overlays (RROs)
and can be managed using the adb shell cmd overlay command.
Use the following commands to enable or disable a RRO:
adb shell cmd overlay enable NAME
adb shell cmd overlay disable NAME
Modify system bar position
By default, the configurable emulator has two system bars – a status bar on the
top of the screen and a navigation bar at the bottom of the screen. Though many
cars share this layout, some don't. Of particular note is that some cars have
their system bar(s) on the horizontal sides of the screen and not the vertical
sides, which may break assumptions made when developing apps for mobile form
factors. See System bars, immersive mode, and
edge-to-edge rendering
for more details and technical guidance.
The following RROs can be used to modify the system bars:
com.android.systemui.rro.bottomcom.android.systemui.rro.bottom.roundedcom.android.systemui.rro.leftcom.android.systemui.rro.right
Emulate display cutouts
Some cars have screens with display cutouts that are very different when
compared to those seen on mobile devices. Instead of the notches or pinhole
camera cutouts, some Android Automotive OS vehicles have curved screens that
make the screen non-rectangular. See Adapt to irregularly shaped displays
for more details and technical guidance.
The following RROs can be used to emulate display cutouts:
com.android.internal.display.cutout.emulation.top_and_rightcom.android.internal.display.cutout.emulation.free_formcom.android.internal.emulation.automotive_ultrawide_cutout
Recommended testing configurations
Since the total number of configurations that can be created by combining these
RROs is quite large, we recommend testing your app using the following
combinations of hardware profiles
and RROs, which are similar to some vehicles on the road today.
- Automotive (1080p landscape) with
com.android.systemui.rro.left
or com.android.systemui.rro.right
- Automotive Ultrawide with
com.android.systemui.rro.left and
com.android.internal.emulation.automotive_ultrawide_cutout
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2025-05-22 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-05-22 UTC."],[],[],null,["# Test using the configurable emulator\n\nTo help emulate some of the configurations seen across OEMs, certain [hardware\nprofiles](/training/cars/testing/emulator#bundled-profiles) support runtime\nconfigurability.\n\nThese configurations are implemented using [Runtime Resource\nOverlays](https://source.android.com/docs/core/runtime/rros) (RROs)\nand can be managed using the `adb shell cmd overlay` command.\n\nUse the following commands to enable or disable a RRO: \n\n adb shell cmd overlay enable \u003cvar translate=\"no\"\u003eNAME\u003c/var\u003e\n adb shell cmd overlay disable \u003cvar translate=\"no\"\u003eNAME\u003c/var\u003e\n\nModify system bar position\n--------------------------\n\nBy default, the configurable emulator has two system bars -- a status bar on the\ntop of the screen and a navigation bar at the bottom of the screen. Though many\ncars share this layout, some don't. Of particular note is that some cars have\ntheir system bar(s) on the horizontal sides of the screen and not the vertical\nsides, which may break assumptions made when developing apps for mobile form\nfactors. See [System bars, immersive mode, and\nedge-to-edge rendering](/training/cars/parked/automotive-os#bars-immersive-edge)\nfor more details and technical guidance.\n\nThe following RROs can be used to modify the system bars:\n\n- `com.android.systemui.rro.bottom`\n- `com.android.systemui.rro.bottom.rounded`\n- `com.android.systemui.rro.left`\n- `com.android.systemui.rro.right`\n\nEmulate display cutouts\n-----------------------\n\nSome cars have screens with display cutouts that are very different when\ncompared to those seen on mobile devices. Instead of the notches or pinhole\ncamera cutouts, some Android Automotive OS vehicles have curved screens that\nmake the screen non-rectangular. See [Adapt to irregularly shaped displays](/training/cars/parked/automotive-os#irregular-displays)\nfor more details and technical guidance.\n\nThe following RROs can be used to emulate display cutouts:\n\n- `com.android.internal.display.cutout.emulation.top_and_right`\n- `com.android.internal.display.cutout.emulation.free_form`\n- `com.android.internal.emulation.automotive_ultrawide_cutout`\n\nRecommended testing configurations\n----------------------------------\n\nSince the total number of configurations that can be created by combining these\nRROs is quite large, we recommend testing your app using the following\ncombinations of [hardware profiles](/training/cars/testing/emulator#bundled-profiles)\nand RROs, which are similar to some vehicles on the road today.\n\n- *Automotive (1080p landscape)* with `com.android.systemui.rro.left` or `com.android.systemui.rro.right`\n- *Automotive Ultrawide* with `com.android.systemui.rro.left` and `com.android.internal.emulation.automotive_ultrawide_cutout`"]]
