The error shown in the screenshot in the article is just one test on a particular device in a challenging environment. This particular test wasn’t at a geodetic marker.
I’ve seen a number of NTRIP client apps floating around but I’ve never used them and can’t recommend any. That’s ultimately something I’d like to support in GPSTest too. Let me know if you find one you like.
I haven’t yet seen evidence of decimeter accuracy from any Android phone with integrated dual-frequency support.
That’s great! Both good questions — you can use the new “Accuracy” feature in GPSTest to measure the actual horizontal and vertical accuracy values and see what the average error is. See https://medium.com/@sjbarbeau/measuring-gnss-accuracy-on-android-devices-6824492a1389.
Can you please post the data and questions to the GPSTest Google Group?
Others may be able to help there too.
You can get a position calculated by the device via the Location API even if the device doesn’t provide the delta range. Checkout the KML export from GPS Benchmark to see example of how to display information in Google Earth.
You only need accumulated delta range if you’re planning on calculating your own positions. If you just want to compare accuracy, visible sats, SNR and position error you can use any Android device that shows dual-frequency info in GPSTest. You might want to check out the new accuracy feature in GPSTest v3.3, as well as an older app I created, GPS Benchmark.