Originally Posted by mkstowegnv
There is a lot of possibly unfamiliar terminology in the video. There are many techniques besides L1L5 multiband for achieving submeter accuracy (summarized by this PowerPoint: https://www.u-blox.com/sites/default..._webinarII.pdf). Two techniques mentioned in the video, RTK and correction services, may be what requires Android P (not clear to me if multiband does as well).
I just finished watching presentation. So while there is some cool stuff in the video (Wi-Fi RTT and ability to do GNSS RTK by turning off duty cycling in Android P), it unfortunately don't shed any more light on the availability of dual-frequency support in devices. L5 signals should be visible in GPSTest if the hardware supports it and the device has Android O or later (same as I originally wrote in https://medium.com/@sjbarbeau/dual-f...es-152b8826e1c
The developer menu option (changed by the device user) to turn off GNSS duty cycling is only available on Android P, but, as described by Frank van Diggelen, this only matters if as a developer you're trying to do RTK positioning - in other words, to do RTK the GPS chipset needs to constantly stay on (which reduces battery life), and when this option is enabled it forces the GPS chipset to stay on. There is a screenshot of this developer option at 31:48, and while the video is a bit grainy the option seems to say "Force full GNSS measurements - Track all GNSS constellations and frequencies with no duty cycling". I do NOT interpret this as meaning that "L5 signals are hidden unless you flip this switch", because a) that's not how Frank described it, b) this same logic doesn't apply to seeing multiple constellations (we know we can already see all GNSS constellations on devices w/ Android O) and c) the GnssStatus object to get carrier frequency is independent of the GNSS measurements callback, and it seems this option specifically targets GNSS measurements as related to doing RTK positioning.
So, the hunt continues...