Detect if setFullTracking() is honoured

[samodadela]

Is your feature request related to a problem? Please describe. It seems that setFullTracking() is not honored on all devices. It would be nice to know which devices honor it and add it to the Crowdsourcing GNSS data.

I am trying to get the location as precisely as possible so I though that keeping the GPS chip always on would give me better results.

What I'm seeing is that when FLP returns positions at 2 seconds intervals (that's the interval I requested with the API), the data is very precise... but sometimes it start reporting at 4 second intervals and the positions are way worse (they even backtrack). This happens outside (no buildings) and seems quite random. Looks like some power saving kicking in.

So the idea is to enable setFullTracking() which should also force FLP to receive updates more frequently.

Describe the solution you'd like Add a 'duty-cycling' test in GPSTest that enables setFullTracking(), records the data and then checks for gaps. Add the info to the Crowdsourcing GNSS data.

Describe alternatives you've considered Use GPSTest or GNSSLogger to capture the data and analyze it myself. Problem is this is slow and I would have to test a lot of devices. I though that if GPSTest already crowdsources the data, it could add this information to the table. This information would be used to recommend devices that could return better data.

Additional context Add any other context or screenshots about the feature request here.