CTS Verifier Welcome to the CTS Verifier! Continue Pass Info Fail [CTS Verifier %1$s] CTS Verifier %1$s Test Results PASS FAIL NOT_EXECUTED Manual Test List Audio Networking Sensors Security Features Other Clear Test results cleared. Copy Test results copied to clipboard. Share Share Test Results Bluetooth Test The Bluetooth Control tests check whether or not the device can disable and enable Bluetooth properly.\n\nThe Device Communication tests require two devices to pair and exchange messages. The two devices must be: \n\n1. a candidate device implementation running the software build to be tested \n\n2. a separate device implementation already known to be compatible Bluetooth is not available? If your device is supposed to have Bluetooth, your API implementation is not behaving correctly! Bluetooth Control Device Communication Toggle Bluetooth Disable and enable Bluetooth to successfully complete this test. Enable Bluetooth Disable Bluetooth Disabling Bluetooth... Could not disable Bluetooth... Secure Server Start the CTS Verifier on another device, start the Bluetooth test, and choose \"Secure Client\" to complete the test. Insecure Server Start the CTS Verifier on another device, start the Bluetooth test, and choose \"Insecure Client\" to complete the test. Waiting for client... Connecting... Received Messages Sent Messages No messages Make Discoverable Pairing dialog shown? Insecure connections should not show the pairing dialog! Secure Client Insecure Client Device Picker Paired Devices New Devices No devices Scan for Devices Scanning... Device must be unpaired via Bluetooth settings before completing the test.\n\nUnpair the device in settings, make the server discoverable, and rescan to pick this device. Bluetooth Settings Hardware/Software Feature Summary This is a test for... WARNING: device reports a disallowed feature name WARNING: device reports neither WiFi nor telephony No data. standard feature reported by device optional feature not reported by device non-standard feature reported by device required feature not reported, or forbidden feature reported Accelerometer Test This test verifies that the accelerometer is working properly. As you move the device around through space, the triangle should always point down (i.e. in the direction of gravity.) If it does not, the accelerometer is improperly configured. Magnetometer Test This test verifies that the magnetometer (compass) is working properly. As you move the device around through space, the triangle should always point toward the north pole (which may point through the ground.) If it does not, the magnetometer is improperly configured. Be sure not to run this test with the device near any strong magnetic field generators. SUID File Scanner This test will attempt to find unauthorized SUID binaries, but it is not comprehensive due to permission restrictions.\n\nAuthorized SUID binaries will appear green, while unauthorized SUID binaries will appear red.\n\nPress OK to start the scan... Scanning directory... User: %1$s\nGroup: %2$s\nPermissions: %3$s\nPath: %4$s Could not stat file... Congratulations! No unauthorized suid files detected! Audio Quality Verifier 1. Click \"Calibrate\". Position the phone in front of the center of the speaker cone with the microphone facing the speaker, and adjust the volume of the speaker until the status message indicates it is correct. \n\n2. Click on any test in the list to run it, or \"Run All\" to run each test in sequence. \n\nIf the sound level check fails, go back to the calibration step before running any other test. \n\n3. Click \"Results\" to view the outcomes. A correctly functioning device should pass all tests. \n\n4. Click \"Send by email\" from the results page to send the results to an e-mail address of your choice. The recordings made are also attached as raw 16 bit, 16 kHz audio files to help you diagnose any failed tests. Calibrate Run All Stop Results Send by email Clear Audio Quality Results Dismiss Android Audio Quality Verifier Test Results Calibrate Volume Adjust volume to the central point Done Status: unknown Volume too low Volume too high Volume OK Unnamed experiment Sound level check Spectrum shape test Glitch test Gain linearity test Overflow check Bias measurement Cold recording latency Warm recording latency Fail Pass Complete Experiment ran successfully. Mean = %1$.3g, tolerance = +/- %2$.0f\nRMS = %3$.0f, duration = %4$.1fs Overflow check unsuccessful Insufficient tone detected.\nExpected %1$.1fs tone; observed %2$.1fs "Overflow check failed due to discontinuities.\nObserved %1$d bad frames\nTone duration %2$.1fs\nMin peak = %3$.0f, max = %4$.0f "Observed %1$d bad frames\nTone duration %2$.1fs\nMin peak = %3$.0f, max = %4$.0f Experiment failed, error code %1$g Deviation from linearity = %1$.3g dB\nMax allowed = %2$.1f dB Error performing Glitch test. %1$d glitches detected; expected %2$d, duration %3$.1fs %1$d glitches detected; expected %2$d-%3$d, duration %4$.1fs RMS = %1$.0f, target = %2$.0f\nTolerance = %3$.1f%%\nDuration = %4$.1fs Cannot perform test.\nCheck volume is sufficiently high? RMS deviation = %1$.2f\nMax allowed deviation = %2$.1f Latency = %1$dms, maximum allowed = %2$dms RMS = %1$.0f, target = %2$.0f Latency = %1$dms Error getting minimum AudioRecord buffer size: %1$d Error getting minimum AudioTrack buffer size: %1$d Error initializing AudioRecord instance Error initializing AudioTrack instance Error reading data from AudioRecord instance Exception thrown during test: %1$s