--
You received this message because you are subscribed to the Google Groups "GPSTest" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gpstest_andro...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gpstest_android/e79695ad-1d10-497f-86d7-0843117bbf66n%40googlegroups.com.
Okay, I tested it further. It is apparently impossible to get lower value than 3.8/2.5, and that number you get in 30 seconds or so. So that says me it should be a bug. Values decrease fast until you get 3.8/2.5. But I would imagine snapdragon on 4nm is superiour to mediatek with its 1 m. Tested on September patch of Android 12 I installed yesterday. After installing armv8 GnssLogger I was shocked to see it has 4 sources of geoposition: GNSS, WLS, NLP, FLP. Maybe Gpstest takes some wrong number? Or Qualcomm private blob has a bug.
--
You received this message because you are subscribed to the Google Groups "GPSTest" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gpstest_andro...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gpstest_android/59840157-5f99-43dc-99af-5ad08fb5e869n%40googlegroups.com.
The biggest problem with "If you're benchmarking GNSS chipset accuracy in GPSTest using the "Accuracy" feature, please see this article I wrote for details," is that ground truth Google map will not use G2139 WGS 84 or even any WGS 84 or even same ITRF in all places, like in France or Australia. So I would not be able to check 30 cm anyway. Unless I go to some known location with G2139 coordinates known. Or ITRF2014 or ITRF2020. I wrote the whole new topic on it. https://groups.google.com/g/gpstest_android/c/vSyqMYUL504I think I have two places in my city... So may go there.
--
You received this message because you are subscribed to the Google Groups "GPSTest" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gpstest_andro...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gpstest_android/8fb79ef6-158f-4899-b76e-141468066aafn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gpstest_android/CAEkVq%2BgoFS%2B670%2Buh6fnYX8xMYgOOupYT2QwSE7pnSSk-tsrNw%40mail.gmail.com.
I realize that most of the discussion in here concerns the location accuracy and accessibility of GNSS chipsets, but mymain interest is in accessing the GPS timestamps! Why do vendors not use the GPS time to set the phone device time,or at least allow API access to the GPS clock?This would allow smartphone clocks to be synchronized to within 1ms easily, enabling many applications.Without GPS clock access, apps have to rely on services like NTP, which can be off by 30ms and typically more.Is there any particular reason why phone clocks don't use the nanosecond clocks within their GPS chips?
To view this discussion on the web visit https://groups.google.com/d/msgid/gpstest_android/59840157-5f99-43dc-99af-5ad08fb5e869n%40googlegroups.com.b