New beta release - GPSTest v3.9.13

[Sean Barbeau]

Hi all,

I pushed a new beta release to Google Play beta testing group (v3.9.13):

https://play.google.com/apps/testing/com.android.gpstest  

It should be available over the next 24 hours or so.

This release introduces Android 12 (S) support and specifically two features available on Android 12 and higher:

• "Force full GNSS measurements" setting (Android 12 and up) - No more digging into the Android system developer mode. See https://bit.ly/gnss-force-full-measurements for details.

• Better capture of device GNSS capabilities (Android 12 and up) - Uses GnssCapabilities API for GPSTest Database. See https://bit.ly/gpstest-database-article for details.

If you have a device with the Android 12 beta on it, please give it a try and let me know if it works! Specifically, submitting data to the GPSTest Database (2nd bullet point) would be helpful. And let me know if you see anything strange on Android 12.

Full release notes are at:

https://github.com/barbeau/gpstest/releases/tag/v3.9.13

Thanks,

Sean

[lodrog...@gmail.com]

today, i download and install the apk file from github
i have one old  device from 2017 with snapdragon 835 and android 10. I made all the well known tests that with older versions has issues and all is working well so far.

i need to ask about the new feature of "Force full GNSS measurements" setting
- if we have manually enabled this option into developer option, will gpstest app disable it, if we disable this, into gpstest settings. When ? during we run this app or and after the exit

[Sean Barbeau]

Thanks for testing!

"Force full GNSS measurements" setting in the app only affects Android 12 and higher - it has no effect on Android 11 and lower.

But that's a good question for Android 12. I don't have an Android 12 device to test on, so I don't know if the "Force full GNSS measurements" setting still exists in the system Developer Options, and if it does, which wins if there are conflicts between the app setting and system Developer Options setting. I assume the app setting would probably win, but I'd love feedback from anyone who could test this.

Sean

--
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/d3493c73-ceb8-4078-93fa-6950fcec670en%40googlegroups.com.

[lodrog...@gmail.com]

if we have a new feature "Force full GNSS measurements" and the programmer don't know the real behavior, i think it is better ...

- to add a master switch to disable this option for android 12 and newer
the power users knows very well about "developer options". They know very well that from android 9 we have the option "Force full GNSS measurements" and it is very easy to enable this. Please remove this option from gpstest or add a master switch to fully disable this setting. The automatic "AI" behaviors can be very problematic.

[Sean Barbeau]

I've gotten confirmation back from Google.

On Android 12, the Android system Developer Options setting and setting within GPSTest are logically OR'd together at the Android platform level. So if at least one of them is true (set to active), then "Force full GNSS measurements" is true (i.e., duty cycling is disabled). If both of them are false, then "Force full GNSS measurements" is false (i.e., duty cycling is active, which is the default device setting).

Sean

[lodrog...@gmail.com]

thank Sean for the info. So, it works like the "screen always on" setting you have.

[Sean Barbeau]

v3.9.14 is rolling out now with some accessibility improvements that won't obvious unless you have TalkBack enabled:

https://github.com/barbeau/gpstest/releases/tag/v3.9.14

Sean