Compare results using the performance map

Use the data provided in the performance tables to populate the performance map of the ecosystem. Follow the recommended data visualization how-to guide when populating the performance map. Align the data acquired from the DUT to the performance map for comparison.

Visualize the data in the performance map

The performance map for Effect 1 and Effect 2 is drawn with peak duration, peak amplitude, and figure of merit for sharpness (FOMS = PRR / peak duration). When aligning your data to the performance map, carefully follow the data in the x axis (peak duration), y axis (peak amplitude), and the bubble size (FOMS). The performance map is presented with several categories, including price tier (low, medium, high) and actuator type (X-LRA, Z-LRA, ERM). Use different colors to represent different categories.

The performance map assists with the evaluation of the target device using a contextually relative comparison (rather than a pass or fail judgement). When interpreting the comparison results between the performance map and your DUT measurement, build your expectations based on the categories that the phone belongs to, then consider these questions:

• Where on the map are your device's performance characteristics located?
• Considering many conditions (for example, price tier or actuator type), is your device outperforming, equal to, or underperforming your competitors?
• Do the results meet your expectations? If not, which factor underperformed?

For example, if the performance from your budget phone with ERM is equivalent to that of premium X-LRA phones, the budget phone has outstanding quality haptics compared to similar budget phones with ERM.

In EFFECT_CLICK (Effect 1) and createOneShot (Effect 2), the x axis and y axis refer to the peak duration and peak amplitude, respectively. The size of the bubble indicates the figure of merit for sharpness (FOMS = PRR / peak duration), and the color codes in the legend represent categories for further segmentation (price tier or actuator types). For example, in the performance map segmented by the price tier (for example, low/medium/high), the color of each bubble represents the price tier. By matching the bubble's color with your phone's price tier, you can compare your phone with competitors in the same price tier.

The green bubble in Figure 1 shows high-quality haptics for EFFECT_CLICK (Effect 1). Effects are typically crisp and strong when the duration is short, the amplitude is high, and bubble size is large.

The red bubble in Figure 1 shows the low-quality haptics from EFFECT_CLICK (Effect 1). Effects are typically buzzy, mushy, and weak when the duration is long, the amplitude is low, and the bubble size is small.

The dotted red line indicates the minimum amplitude threshold. If the amplitude is weaker than 0.1 g, the haptic isn't perceivable by users (failure case F03-2).

Figure 1. Performance map for Effect 1 how-to guides

Figure 2. Performance map for Effect 2 how-to guides

Reading data from createOneShot (Effect 2) is an almost identical process to Effect 1 data, with one exception. Because the target duration of Effect 2 is 20 ms, the peak duration close to 20 ms represents the output with good braking.

Data from createWaveform (Effect 3) focuses on amplitude control capabilities. The target ratio between the first acceleration (Acceleration 1 = 50% amplitude = left bar in the group bar chart) and the second acceleration (Acceleration 2 = 100% amplitude = right bar in the grouped bar chart) is 2.

Figure 3. Performance map for Effect 3 how-to guides

Performance map data and illustrations

This data applies to the performance maps:

• Test date: April 12, 2020
• Number of device models tested: 28
• Number of device manufacturers tested: 10
• Device release period: Up to 18 months prior to the test date

• Haptic effects observed in the performance map:

  • VibrationEffect.EFFECT_CLICK (Effect 1)
  • VibrationEffect.createOneShot (Effect 2)
  • VibrationEffect.createWaveform (Effect 3)

• Price tier segmentation

  • High (600 USD or higher)
  • Medium (from 300 USD to 600 USD)
  • Low (up to 300 USD)

• Failure cases

  • F01: Haptic constant isn't implemented. No signal to analyze.
  • F02: Signal amplitude is too weak to be analyzed or to be perceived by humans. MATLAB error.
  • F03-1: Signal amplitude is too weak to be analyzed or to be perceived by humans. PRR value is smaller than zero (< 0).
  • F03-2: Signal amplitude is too weak to be analyzed or to be perceived by humans. Amplitude value is smaller than 0.1 (< 0.1).
  • F04: The first acceleration phase is missing. No signal for the first half.
  • F05: No increased acceleration between two phases. The max amplitude of acceleration 1 and acceleration 2 is almost identical.

• Android version required for the hardware assessment: Android 10.0 (API level 29) or higher.

• Android version used to populate the performance map: Android 8.0 (API level 26) or higher. For Effect 1, HapticFeedbackConstants.KEYBOARD_PRESS was used instead of VibrationEffect.EFFECT_CLICK because the data acquisition was performed prior to the introduction of the Haptics implementation checklist.

Performance map for EFFECT_CLICK (Effect 1)

Vibrator vibrator = getSystemService(Vibrator.class);
vibrator.vibrate(VibrationEffect.createPredefined(EFFECT_CLICK));

val vibrator = getSystemService(Vibrator::class.java)
vibrator.vibrate(VibrationEffect.createPredefined(EFFECT_CLICK))

Figure 4. Performance map for Effect 1 (by price tier)

Figure 5. Performance map for Effect 1 (by actuator type)

Performance map for createOneShot (Effect 2)

private static final long oneShotTiming = 20;
private static final int oneShotAmplitude = 255;


Vibrator vibrator = getSystemService(Vibrator.class);
vibrator.vibrate(VibrationEffect.createOneShot(oneShotTiming, oneShotAmplitude));

private val oneShotTiming: Long = 20
private val oneShotAmplitude = 255


val vibrator = getSystemService(Vibrator::class.java)
vibrator.vibrate(VibrationEffect.createOneShot(oneShotTiming, oneShotAmplitude))

Figure 6. Performance map for Effect 2 (by price tier)

Figure 7. Performance map for Effect 2 (by actuator type)

Performance map for createWaveform (Effect 3)

private static final long[] waveformTimings = {500, 500};
private static final int[] waveformAmplitudes = {128, 255};


Vibrator vibrator = getSystemService(Vibrator.class);
vibrator.vibrate(VibrationEffect.createWaveform(waveformTimings, waveformAmplitudes, -1));

private val waveformTimings = longArrayOf(500, 500)
private val waveformAmplitudes = intArrayOf(128, 255)


val vibrator = getSystemService(Vibrator::class.java)
vibrator.vibrate(VibrationEffect.createWaveform(waveformTimings, waveformAmplitudes, -1))

Figure 8. Performance map for Effect 3 (by pass/fail)