Select to expand quote
sailquik said..Macroscien said..Roo said..Macroscien said..
We need improvent accuracy GPS for our everyday life.
You want to self park your vehicle within cm not meters.
Or hide a stash of money in the jar underground in the garden.
I am reading about newest Mate 70 Chinese smart phone and nobody say how good GPS going to be?! Better cameras or bigger screens that is all they do worry about. For us all the best could be new smartphone with improved GPS not another knock of DIY watch. I am happy even to invest $35 for additional plastic waterproof bag for new smartphone.
New smartphone with Doppler could solve all our problem we worry about for years here.Maybe is all windsurfers and other watersport users send request to Samsung phone manufacturer and ask for Doppler?
Like millions of customers action asking manufacturer to do something they need? Global petition by all GPSTC and others?
You do realise doppler is already on smartphones, in addition to doppler speed accuracy estimates? I have an app that already records the data for post processing.
So do we have the same precision and accuracy on our or any of smartphones as our Motion GPS?
I still have only older Samsung smartphone that hardly can catch up on motorway to find nearest intersection and directions sometimes too late after you just passed in the wrong.
No, we do NOT! Not by a very long way!!
The smartphone have a huge disadvantage because they use a very tiny chip antenna. They are not capable of comparable accuracy from that alone.
Add to that they the GPS chip they use may or may not be in the same class.
The vast majority of smartphones don't give the Doppler error estimate.In fact, I have not found or heard of one that does. If there is one, please inform us. I have not been able to get this out of the Umidigi A7 Pro phone I have, but it does give some more data about the satellites it uses, and it is Multi Constellation so it gets a lot of sats.
Roo, if you have an app that can extract and record the Doppler Error data, why not make it available?

Edit, Sorry Roo, I read your post again and realised you are talking about post processing. I assume that is done on the positional data? I have never heard of post processing to get a better solution on Doppler data.
Daffy,
pretty much most phones with Android 9 and above have the doppler S. Acc in the raw data. It can be saved very easily. I'm having one of our software guys write an app to record and analyse it, essentially an update to GPSLogit. The latest Android 14 phones have an incredible amount of raw data being produced from the current GPS chipsets, quite a few of the higher end ones use the U-Blox.
Roo
Here's what my phone produces:
Raw,utcTimeMillis,TimeNanos,LeapSecond,TimeUncertaintyNanos,FullBiasNanos,BiasNanos,BiasUncertaintyNanos,DriftNanosPerSecond,DriftUncertaintyNanosPerSecond,HardwareClockDiscontinuityCount,Svid,TimeOffsetNanos,State,ReceivedSvTimeNanos,ReceivedSvTimeUncertaintyNanos,Cn0DbHz,PseudorangeRateMetersPerSecond,PseudorangeRateUncertaintyMetersPerSecond,AccumulatedDeltaRangeState,AccumulatedDeltaRangeMeters,AccumulatedDeltaRangeUncertaintyMeters,CarrierFrequencyHz,CarrierCycles,CarrierPhase,CarrierPhaseUncertainty,MultipathIndicator,SnrInDb,ConstellationType,AgcDb,BasebandCn0DbHz,FullInterSignalBiasNanos,FullInterSignalBiasUncertaintyNanos,SatelliteInterSignalBiasNanos,SatelliteInterSignalBiasUncertaintyNanos,CodeType,ChipsetElapsedRealtimeNanos
#
# UncalAccel,utcTimeMillis,elapsedRealtimeNanos,UncalAccelXMps2,UncalAccelYMps2,UncalAccelZMps2,BiasXMps2,BiasYMps2,BiasZMps2
#
# Accel,utcTimeMillis,elapsedRealtimeNanos,AccelXMps2,AccelYMps2,AccelZMps2
#
# UncalGyro,utcTimeMillis,elapsedRealtimeNanos,UncalGyroXRadPerSec,UncalGyroYRadPerSec,UncalGyroZRadPerSec,DriftXRadPerSec,DriftYRadPerSec,DriftZRadPerSec
#
# Gyro,utcTimeMillis,elapsedRealtimeNanos,GyroXRadPerSec,GyroYRadPerSec,GyroZRadPerSec
#
# UncalMag,utcTimeMillis,elapsedRealtimeNanos,UncalMagXMicroT,UncalMagYMicroT,UncalMagZMicroT,BiasXMicroT,BiasYMicroT,BiasZMicroT
#
# Mag,utcTimeMillis,elapsedRealtimeNanos,MagXMicroT,MagYMicroT,MagZMicroT
#
# OrientationDeg,utcTimeMillis,elapsedRealtimeNanos,yawDeg,rollDeg,pitchDeg
#
#
Fix,Provider,LatitudeDegrees,LongitudeDegrees,AltitudeMeters,SpeedMps,AccuracyMeters,BearingDegrees,UnixTimeMillis,SpeedAccuracyMps,BearingAccuracyDegrees,elapsedRealtimeNanos,VerticalAccuracyMeters,MockLocation,NumberOfUsedSignals,VerticalSpeedAccuracyMps,SolutionType#
# Nav,Svid,Type,Status,MessageId,Sub-messageId,Data(Bytes)
#
# Status,UnixTimeMillis,SignalCount,SignalIndex,ConstellationType,Svid,CarrierFrequencyHz,Cn0DbHz,AzimuthDegrees,ElevationDegrees,UsedInFix,HasAlmanacData,HasEphemerisData,BasebandCn0DbHz
#
# Agc,utcTimeMillis,TimeNanos,LeapSecond,TimeUncertaintyNanos,FullBiasNanos,BiasNanos,BiasUncertaintyNanos,DriftNanosPerSecond,DriftUncertaintyNanosPerSecond,HardwareClockDiscontinuityCount,AgcDb,CarrierFrequencyHz,ConstellationType
#