@amarok thank you for your patience and testing this. I have been interested for quite some time, if and how good GPS is working on the L5.
The data you posted doesn’t reveal your location. The part you XXed out at the end is the checksum. In case you are interested, here’s a description about the meaning of the NMEA sentences: https://www.rfwireless-world.com/Terminology/GPS-sentences-or-NMEA-sentences.html
Or if you want to decode the NMEA sentences, you can use an online tool like https://swairlearn.bluecover.pt/nmea_analyser
Now we know that we can query the GPS module via mmcli
on the L5 - that’s cool. In this case, geoclue should be able to pick up the data as soon as you’ve got a GPS fix.
So the next step would be to get an actual GPS fix. You should get back a longer GPGGA NMEA sentence with an actual position from mmcli. This should look similar to that:
$GPGGA,122842.528,5231.277,N,01324.679,E,1,12,1.0,0.0,M,0.0,M,,*65
$GPGSA,A,3,01,02,03,04,05,06,07,08,09,10,11,12,1.0,1.0,1.0*30
$GPRMC,122842.528,A,5231.277,N,01324.679,E,026.8,028.6,121220,000.0,W*73
As soon as you’ve got a GPS fix, you can check again with where-am-i --accuracy-level=8
.
Edit: For reference, here’s some sample output from where-am-i (without GPS fix, location XXed out):
mobian@pinephone:~$ /usr/libexec/geoclue-2.0/demos/where-am-i --accuracy-level=8
Client object: /org/freedesktop/GeoClue2/Client/4
New location:
Latitude: XX.XXXXXX°
Longitude: XX.XXXXXX°
Accuracy: 11.973171 meters
Speed: 0.009006 meters/second
Heading: 0.000000°
Timestamp: 2020年12月12日 14時07分01秒 (1607778421 seconds since the Epoch)
New location:
Latitude: XX.XXXXXX°
Longitude: XX.XXXXXX°
Accuracy: 11.876203 meters
Speed: 0.018885 meters/second
Heading: 0.000000°
Timestamp: 2020年12月12日 14時07分24秒 (1607778444 seconds since the Epoch)