tree a8fc12fea2391efc119bf38803b4b60598effc6a
parent 32257fdc92016ed2f76e62af8425937284e0d61b
author weijiaxu <weijiaxu@google.com> 1508980901 -0700
committer Eric Erfanian <erfanian@google.com> 1509035962 +0000

App latency test migration.
Migrate the existing app latency test to a new solution from Project Fi team.
The main change on this new solution is that the data collection part is done by Primes now.

Also, a few changes has been made on DialerPrimes class and a new Dialer variant dialer_release_test has been created.

The benefits of using primes to collect data are:
1. latency tests dont need to insert lines of code to track latency in dialer codebase
2. be able to collect data on any variants with or without Proguard
3. latency tests now only contain ui interaction to trigger scenarios on which we want add measurements
4. share the same logic with primes on production so that data from testbeds and normal users are comparable.
5. easier for anyone to add interesting data entries.

----------Mobile Harness Below-----------------------------------
RELNOTES[INC]:Add entries for dialer to use mobileharness plugin.

Test: No
PiperOrigin-RevId: 173481741
Change-Id: Ia6812794141382898bea4b34bca90278c5663464