It seems that the GPS is more inclined to give a fix faster when the trigger defined has type GPS_TRIG_FIX set than if the trigger type is GPS_TRIG_DATA_READY. Is this the case?
It seems that the GPS is more inclined to give a fix faster when the trigger defined has type GPS_TRIG_FIX set than if the trigger type is GPS_TRIG_DATA_READY. Is this the case?
The difference between GPS_TRIG_FIX and GPS_TRIG_DATA_READY is what data from the GPS generates an event. In case of GPS_TRIG_FIX you will only get an event when you have a fix, while with GPS_TRIG_DATA_READY you will also get other data like tracking data. In principle should this not have anything to do with how fast you will get a fix, because it's only has to do with how the data stream from the GPS is filtered.
However testing this can be hard because fix time is not static, every run/setup/configuration will give you different time to fix.
The difference between GPS_TRIG_FIX and GPS_TRIG_DATA_READY is what data from the GPS generates an event. In case of GPS_TRIG_FIX you will only get an event when you have a fix, while with GPS_TRIG_DATA_READY you will also get other data like tracking data. In principle should this not have anything to do with how fast you will get a fix, because it's only has to do with how the data stream from the GPS is filtered.
However testing this can be hard because fix time is not static, every run/setup/configuration will give you different time to fix.