Test: Cts Verifier > Device Administration > Device Admin Tapjacking Test
The test is open to interpretation if it behaves as expected or not. Buttons can be tapped through the overlay but maybe produce an unclear description.
The button to activate the admin should be disabled and should not register any taps.
It isn't possible to activate the device admin app but a toast is shown Because another app is displaying on top of these options, Settings can't respond to your action. Hence, the tap is registered and it is still possible to tap cancel and press Uninstall app.
Below are the expected results for Step 3.
|3. Tap [ENABLE DEVICE ADMIN]||3.1. [Active this device admin app] is enabled.||3.2. [Active this device admin app] is disabled.|
Companion Device Test
The companion device test is
It may be unclear if the test has finished correctly after selecting the device in the list and pressing OK.
See below for the expected results.
|1. Tap [GO]||2. Tap a BT device||3. Tap [Pass]|
Voicemail Broadcast Test
The voicemail broadcast test is
To send a voicemail to the phone, call the device, decline the call on the device, and leave a voicemail.
A visual voicemail is a way to send the device audio data and detailed information for incoming voicemails, instead of just sending the Message Waiting Indicator** (MWI) SMS.
The test is testing behavior regarding receiving the MWI, and if visual voicemail is being used, the carrier might not send the MWI and interfere with the test, thus it must be disabled.
USB Accessory/Device Test
Specific instructions to avoid flaky behavior:
- Install the CtsVerifier.apk on the DUT
- Install the CtsVerifierUSBCompanion.apk on the Pixel
- Make sure all USB cables are disconnected
- Start the CtsVerifierUSBCompanion on the Pixel and select the accessory test companion
- Start the CtsVerifier on the DUT and select the USB Accessory test
- Connect the OTG-Adapter to the Pixel and then connect the DUT via a USB-A(male)-C cable
- Approve the connection dialogs in the following order:
- Wait until test completes
Dynamic Sensor Discovery Test
Each device maker can decide whether or not to support the API
If a device supports the API, the device maker needs to source an external sensor that can be used to pass the test. The device maker will need to locate a device to connect to their device to test dynamic sensors.
If the device maker isn't able to locate a device, the following setup can be used.
- Purchase TI EK-TM4C123GXL development board.
Download and install lm4tools.
For linux/mac execute:
cd /tmp git clone https://github.com/utzig/lm4tools.git cd lm4tools make sudo PREFIX=/usr make install
For windows, you can use LMFlash directly from TI which allows you to flash from a GUI.
Retrieve a Google provided binary called
Flip the switch present on the board to the DEBUG mode and plug a USB micro cable into the port labeled DBG.
Run the following command:
lm4flash -v -E usb_accel_dummy.bin
NOTE: If there's a permission issue, please run with
After flashing completes, unplug the USB micro cable from the DBG port, flip the switch used earlier back to DEVICE, and then plug one end of the USB micro cable into the USB slot labeled DEVICE. The other end of the cable should be plugged directly into your device.
Now you can execute this CTS-V test which should be able to discover and use the device you just plugged in as a fake accelerometer.
Device Admin Uninstall Test
This test may require manual install of
CtsEmptyDeviceAdmin.apk on the device
first from a host via
adb install CtsEmptyDeviceAdmin.apk.
Use CTS Verifier > Device Administration > Device Admin Uninstall Test.
It should detect that the app is installed and go through other steps.