Building the datasheet manually

This page assumes that ADB is installed, on your search path and that you are familiar with using a command line.

Please note that DummyDroid does not use the methods described on this page, but extracts the data programmatically. There might be differences between your results and DummyDroid’s probes.

ABI Tab

The ABI tab lists the native platforms (one per line), supported by the device. The following values can be listed (arm and x86 are mutually exclusive architectures):

• armeabi
• armeabi-v7a
• arm64-v8a
• x86
• x86_64

The following ADB commands can be used to probe the supported ABIs of a given device:

adb shell getprop ro.product.cpu.abi

adb shell getprop ro.product.cpu.abi2

adb shell getprop ro.product.cpu.abilist

Which one applies is SDK level dependent. If in doubt, list all that you can find.

Build Tab

The Build tab is populated from the 🗋 /system/build.prop file. You can either view the file as a whole:

adb shell cat /system/build.prop

or each key individually:

adb shell getprop KEYNAME

The form maps to the following keys (some keys may be named differently on some devices):

Unless you have a specific reason not to, leave the OTA checkbox unchecked.

Features tab

The features tab lists device supported features (one per line). To probe a device, use the following command:

adb shell pm list features

Note that the output must be edited before entering into the form:

• remove the line containing reqGlEsVersion (usually the first one).
• remove the feature: prefix from every line.

The features tab plays a major role in determining app compatibility. If no apps are compatible with a profile, it’s likely because the android.hardware.touchscreen feature is missing.

Graphics Tab

The graphics tab specifies the supported 3D capabilities of your device. Valid values for the version are:

• 1.0
• 1.1
• 2.0 (since Android 2.2)
• 3.0 (since Android 4.3)
• 3.1 (since Android 5.0)

The text area lists the supported OpenGL ES extensions (one per line). Both, version and extensions can be probed using ADB:

adb shell dumpsys SurfaceFlinger

Note that the output format of the dumpsys command is not specified and can change between Android versions. There is no way of automatically parsing it. Values must be copied manually.

Languages Tab

This tab lists system supported locales (one per line). There doesn’t seem to be a way to probe this. Simply list two letter, lowercase ISO 3166 of your choice.

Libraries Tab

Lists OS supplied software libraries, one per line. To probe a device, use the following command:

adb shell pm list libraries

Note that the output must be edited before submitting to DummyDroid (remove the library: prefix).

Userinterface Tab

The user interface tab may seem to be a bit of a misnomer, but keep in mind that Android runs on a lot of devices (Wear, TV, Car…) besides smartphones and tablets.

The screen dimensions can be probed using the following command:

adb shell dumpsys display

Note that the output format of the dumpsys command is not specified. It cannot be parsed automatically, all values have to be copied manually.

The screen density can be probed using the following command:

adb shell getprop ro.sf.lcd_density

Always leave the screen layout at 2 if unsure. Valid values are:

• 1 (small)
• 2 (normal)
• 3 (large)
• 4 (extra large)

If your device has a touchscreen (smartphones and tablets, not Wear, TV or Car), set the Touchscreen to FINGER . Navigation should be NO_NAV and keyboard NO_KEYS (the latter two refer to hardware features that were only present in early Android devices).

Versions Tab

The SDK version can be probed using the following command:

adb shell getprop ro.build.version.sdk

The versions of the software packages can be probed using the following command:

adb shell dumpsys package com.android.vending | grep version

Note that the output format of the dumpsys command is not specified. It cannot be parsed automatically, all values have to be copied manually.

Only the version information of the com.android.vending package is relevant for determining device compatibility.