Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit e8a8b29c authored by Wyatt Riley's avatar Wyatt Riley
Browse files

Clarifying broadcast vs. predicted orbits 

Clarifying comment changes only, no functional
changes.

Bug: 30955615
Test: Builds and GPS still works on device
Change-Id: I073527c11d095651d712b41fc5b301ac478e4082
parent 27c2f822

gnss/1.0/IGnssDebug.hal

+8 −4
Original line number Diff line number Diff line
@@ -71,8 +71,8 @@ interface IGnssDebug { 
        /** Represents heading in degrees. */

        float bearingDegrees;

        /**

         * Estimated horizontal accuracy of position expressed in meters, radial,

         * 68% confidence.

         * Estimated horizontal accuracy of position expressed in meters,

         * radial, 68% confidence.

         */

        double horizontalAccuracyMeters;

        /**
@@ -126,7 +126,11 @@ interface IGnssDebug { 
        /** Defines the constellation type of the given SV. */

        GnssConstellationType constellation;



        /** Defines the ephemeris type of the satellite. */

        /**

         * Defines the standard broadcast ephemeris or almanac availability for

         * the satellite.  To report status of predicted orbit and clock

         * information, see the serverPrediction fields below.

         */

        SatelliteEphemerisType ephemerisType;

        /** Defines the ephemeris source of the satellite. */

        SatelliteEphemerisSource ephemerisSource;
@@ -143,7 +147,7 @@ interface IGnssDebug { 
        float ephemerisAgeSeconds;



        /**

         * True if a server has provided a predicted orbit (& clock) for

         * True if a server has provided a predicted orbit and clock model for

         * this satellite.

         */

        bool serverPredictionIsAvailable;