No tool exists to test SNR &TTFF on a handset

Bug #1408984 reported by John McAleely
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
Critical
Unassigned
location-service (Ubuntu)
Fix Released
High
Thomas Voß
location-service (Ubuntu RTM)
Fix Released
Undecided
Unassigned

Bug Description

OEMs wishing to confirm that GPS is working correctly need to be able to observe TTFF and SNR data from a handset under test. They will repeat these tests in multiple locations.

They expect to find a tool somewhere in this projects deliverables that they can use to do this.

For manual verification purposes:

* sudo apt-get update && sudo apt-get install ubuntu-location-service-tests
* /usr/bin/uls-tests/gps_provider_test --gtest_filter=HardwareAbstractionLayerFixture.time_to_first_fix_cold_start_without_supl_benchmark_requires_hardware
* Three trials will be run, measuring TTFF from cold start without any sort of assistance data, reporting details about visible space vehicles to the terminal.

The timeout per trial is chosen as 15 minutes, as the theoretical cold start time of GPS is 12.5 minutes (see http://en.wikipedia.org/wiki/Time_to_first_fix).

Related branches

Revision history for this message
John McAleely (john.mcaleely) wrote :

It seems reasonable for that tool to be command line based, and therefore accessed after installing the terminal app to the phone.

Revision history for this message
John McAleely (john.mcaleely) wrote :

It should, however, be delivered in the image, so that it is easy to distribute among geographically dispersed teams.

Changed in location-service (Ubuntu):
assignee: nobody → Thomas Voß (thomas-voss)
importance: Undecided → High
status: New → Confirmed
Changed in location-service (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Thomas Voß (thomas-voss) wrote :

@part of the image: Would it be sufficient if the executable is part of ubuntu-location-service-tests, installable via apt-get install?

description: updated
Revision history for this message
John McAleely (john.mcaleely) wrote :

@tvoss - that would be a big step away from the ideal. I'm sure we both know that the tests don't alter the image and screw up updating, but the general line is 'use apt-get install, and you're on your own'.

So I'd rather see it in the default image.

Revision history for this message
Thomas Voß (thomas-voss) wrote :

Fair point, adjusted the MP, adding an option --test to the cli executable, available in: usr/bin/ubuntu-location-serviced-cli

Revision history for this message
John McAleely (john.mcaleely) wrote :

Sounds good!

Revision history for this message
Thomas Voß (thomas-voss) wrote :

Adjusted the CLI, please call with:

  sudo ubuntu-location-serviced-cli --bus system --test

or for the verbose variant:

  sudo GLOG_logtostderr=1 GLOG_v=1000 ubuntu-location-serviced-cli --bus system --test

Revision history for this message
John McAleely (john.mcaleely) wrote :

second command line gives:

phablet@ubuntu-phablet:~$ sudo GLOG_logtostderr=1 GLOG_v=1000 ubuntu-location-serviced-cli --bus system --test
stop: Unknown instance:
I0113 18:08:18.707639 10498 android_hardware_abstraction_layer.cpp:481] virtual bool com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::start_positioning(): 0x1a0f2d8, 0x1a13d38
I0113 18:08:18.709936 10498 android_hardware_abstraction_layer.cpp:231] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_status_update(uint16_t, void*): status=3, context=0x1a0f2d8
I0113 18:08:18.710777 10498 android_hardware_abstraction_layer.cpp:231] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_status_update(uint16_t, void*): status=1, context=0x1a0f2d8
I0113 18:08:18.706547 10509 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1421172498000 nmea=$GPGGA,180818.086,8960.0000,N,00000.0000,E,0,0,,137.0,M,13.0,M,,*45
 length=69 context=0x1a0f2d8
I0113 18:08:18.713310 10509 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1421172498000 nmea=$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
0,,137.0,M,13.0,M,,*45
 length=45 context=0x1a0f2d8
I0113 18:08:18.715703 10509 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1421172498000 nmea=$GPGSV,1,1,1,30,,,25*4C
.99,99.99,99.99*30
0,,137.0,M,13.0,M,,*45
 length=25 context=0x1a0f2d8
I0113 18:08:18.718250 10509 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1421172498000 nmea=$GPRMC,180818.086,V,8960.0000,N,00000.0000,E,0.000,0.00,130115,,,N*40
 length=71 context=0x1a0f2d8

Revision history for this message
John McAleely (john.mcaleely) wrote :

First gives:

phablet@ubuntu-phablet:~$ sudo ubuntu-location-serviced-cli --bus system --test
[sudo] password for phablet:
ubuntu-location-service stop/waiting
key snr has_almanac_data has_ephimeris_data used_in_fix azimuth elevation
30 3.000000e+01 0 0 0 0.000000e+00 0.000000e+00
key snr has_almanac_data has_ephimeris_data used_in_fix azimuth elevation
30 3.000000e+01 0 0 0 0.000000e+00 0.000000e+00

(repeats)

There was a long wait - several minutes? - (at my desk near a window) for the first data point.

Revision history for this message
John McAleely (john.mcaleely) wrote :

@pmcgowan, @olli what's the process for getting this into this week's milestone? It seems it has sat in canonical-devices-system-image for 4 days without triage?

Changed in canonical-devices-system-image:
status: New → Confirmed
importance: Undecided → High
importance: High → Critical
milestone: none → ww03-2015
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package location-service - 2.1+15.04.20150113~rtm-0ubuntu1

---------------
location-service (2.1+15.04.20150113~rtm-0ubuntu1) 14.09; urgency=low

  [ thomas-voss ]
  * Print details about visible space vehicles to the gps provider test
    case. (LP: #1408984)
 -- Ubuntu daily release <email address hidden> Tue, 13 Jan 2015 13:01:58 +0000

Changed in location-service (Ubuntu RTM):
status: New → Fix Released
Changed in canonical-devices-system-image:
status: Confirmed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package location-service - 2.1+15.04.20150126.1-0ubuntu1

---------------
location-service (2.1+15.04.20150126.1-0ubuntu1) vivid; urgency=low

  [ thomas-voss ]
  * Make the remote::Provider::Stub fail loudly on construction if the
    other side is not reachable. Relax the exception in
    location::Daemon::main and do not exit if instantiating a provider
    fails. (LP: #1414591)

location-service (2.1+15.04.20150125~rtm-0ubuntu1) 14.09; urgency=low

  [ CI Train Bot ]
  * Resync trunk

  [ thomas-voss ]
  * Add an interface for querying settings by key. Add an implementation
    leveraging boost::property_tree to provide settings. (LP: #1362765)
  * Allow for enabling/disabling providers. Wire up engine state changes
    to enabling/disabling of providers. (LP: #1392399)

location-service (2.1+15.04.20150113~rtm-0ubuntu1) 14.09; urgency=low

  [ thomas-voss ]
  * Print details about visible space vehicles to the gps provider test
    case. (LP: #1408984)

location-service (2.1+15.04.20150106~rtm-0ubuntu1) 14.09; urgency=low

  [ thomas-voss ]
  * Fix #1394204 by: (LP: #1394204)

  [ Ubuntu daily release ]
  * New rebuild forced
 -- Ubuntu daily release <email address hidden> Mon, 26 Jan 2015 20:16:32 +0000

Changed in location-service (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.