<commit_before>---
title: Manifest compatibility
metadesc: As you prepare your Android app to run on Chromebooks, you should consider the device features that your app uses.
date: 2020-05-01
weight: -1
tags:
  - touchscreen support
---

As you prepare your Android app to run on Chromebooks, you should consider the device features that your app uses. Chromebooks don't support all of the hardware and software features that are available on other devices running Android. If your app requires specific features that aren't supported on Chromebooks, it won't be available for installation on Chromebooks.

You declare your app's requirements for hardware features and certain software features in the [manifest file](https://developer.android.com//guide/topics/manifest/manifest-intro). This document describes the app manifest feature declarations that aren't compatible with Chromebooks.

## Incompatible manifest entries

The manifest entries listed in this section aren't currently compatible with Chromebooks. If your app uses any of these entries, consider removing them or including the `required="false"` attribute value with them so that your app can be installed on Chromebooks. For more information about declaring feature use without requiring that the feature be available on the device, see the guide for the [`<uses-feature>`](https://developer.android.com//guide/topics/manifest/uses-feature-element.html#market-feature-filtering) manifest element. For a complete list of app manifest features and descriptions, see the [Features reference](https://developer.android.com//guide/topics/manifest/uses-feature-element#features-reference).

!!! aside.message--note
**Note:** Android Studio 2.3 and above has built-in lint checks to automatically validate the manifest file. In Android Studio select **File > Settings > Editor > Inspections > Android > Lint > Correctness > Chrome OS**.
!!!

### Hardware features

Support for hardware features varies on Chromebooks. Some features aren't supported on any Chromebooks while others are supported on some Chromebooks.

### Special features

The following list includes features which got added for better hardware support on Chromebooks:

- `android.hardware.type.pc` - Disabling input emulation for mouse and touchpad. Note that you must indicate `required="false"` to prevent that you can only run on Chromebooks.

#### Unsupported hardware features

The following list includes the hardware features that aren't currently supported on Chromebooks:

- `android.hardware.camera` – Back-facing camera
- `android.hardware.camera.autofocus` – Camera that uses autofocus
- `android.hardware.camera.capability.manual_post_processing`  – Camera that uses the `MANUAL_POST_PROCESSING` feature, including functionality for overriding auto white balance
- `android.hardware.camera.capability.manual_sensor` – Camera that uses the `MANUAL_SENSOR` feature, including auto-exposure locking support
- `android.hardware.camera.capability.raw` – Camera that uses the `RAW` feature, including the ability to save DNG (raw) files and provide DNG-related metadata
- `android.hardware.camera.flash` – Camera that uses flash
- `android.hardware.camera.level.full` – Camera that uses `FULL`-level image-capturing support
- `android.hardware.consumerir` – Infrared (IR)
- `android.hardware.location.gps` – GPS<commit_msg>:recycle: (code) Update special features wording<commit_after>---
title: Manifest compatibility
metadesc: As you prepare your Android app to run on Chromebooks, you should consider the device features that your app uses.
date: 2020-05-01
weight: -1
tags:
  - touchscreen support
---

As you prepare your Android app to run on Chromebooks, you should consider the device features that your app uses. Chromebooks don't support all of the hardware and software features that are available on other devices running Android. If your app requires specific features that aren't supported on Chromebooks, it won't be available for installation on Chromebooks.

You declare your app's requirements for hardware features and certain software features in the [manifest file](https://developer.android.com//guide/topics/manifest/manifest-intro). This document describes the app manifest feature declarations that aren't compatible with Chromebooks.

## Incompatible manifest entries

The manifest entries listed in this section aren't currently compatible with Chromebooks. If your app uses any of these entries, consider removing them or including the `required="false"` attribute value with them so that your app can be installed on Chromebooks. For more information about declaring feature use without requiring that the feature be available on the device, see the guide for the [`<uses-feature>`](https://developer.android.com//guide/topics/manifest/uses-feature-element.html#market-feature-filtering) manifest element. For a complete list of app manifest features and descriptions, see the [Features reference](https://developer.android.com//guide/topics/manifest/uses-feature-element#features-reference).

!!! aside.message--note
**Note:** Android Studio 2.3 and above has built-in lint checks to automatically validate the manifest file. In Android Studio select **File > Settings > Editor > Inspections > Android > Lint > Correctness > Chrome OS**.
!!!

### Hardware features

Support for hardware features varies on Chromebooks. Some features aren't supported on any Chromebooks while others are supported on some Chromebooks.

### Special features

The following list includes features that were implemented to better support Chromebook hardware:

- `android.hardware.type.pc` - This disables the input emulation and allows you to develop custom behavior for mouse and touchpad. Note that you must indicate `required="false"` to prevent that you can only run on Chromebooks.

#### Unsupported hardware features

The following list includes the hardware features that aren't currently supported on Chromebooks:

- `android.hardware.camera` – Back-facing camera
- `android.hardware.camera.autofocus` – Camera that uses autofocus
- `android.hardware.camera.capability.manual_post_processing`  – Camera that uses the `MANUAL_POST_PROCESSING` feature, including functionality for overriding auto white balance
- `android.hardware.camera.capability.manual_sensor` – Camera that uses the `MANUAL_SENSOR` feature, including auto-exposure locking support
- `android.hardware.camera.capability.raw` – Camera that uses the `RAW` feature, including the ability to save DNG (raw) files and provide DNG-related metadata
- `android.hardware.camera.flash` – Camera that uses flash
- `android.hardware.camera.level.full` – Camera that uses `FULL`-level image-capturing support
- `android.hardware.consumerir` – Infrared (IR)
- `android.hardware.location.gps` – GPS
{'fraction_non_alphanumeric': 0.0737801293356849, 'fraction_numerical': 0.003233392122281011, 'mean_word_length': 5.1863636363636365, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 19, 'https://': 6, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '748217', 'n_tokens_mistral': 1734, 'n_tokens_neox': 1618, 'n_words': 784}