Login
You're viewing the mstdn.degu.cl public feed.
  • GrapheneOSGrapheneOS@grapheneos.social
    Aug 1, 2025, 1:48 PM

    @leeloo @Life_is @CoMaps Our opt-in network location service provides support for location detection without satellite reception, similarly to the Apple and Google services. Our implementation is currently based on Apple's service with the choice of using it directly or the recommended option of using it through our proxy. Similarly to Apple's approach, we do local position estimation rather than on a server like Google's implementation. It works semi-offline and will have full offline support.

    💬 1🔄 0⭐ 0

Replies

  • GrapheneOSGrapheneOS@grapheneos.social
    Aug 1, 2025, 1:49 PM

    @leeloo @Life_is @CoMaps It provides the same OS API as the Google implementation does on a Google Mobile Services OS. Apps using the OS APIs for network or fused location will use our network location service when the user has opted into enabling it. Apps using the Google Play services fused location API directly rather than via the OS get redirected to the OS API by our sandboxed Google Play compatibility layer. However, that's not present when sandboxed Google Play isn't present.

    💬 1🔄 0⭐ 0
  • GrapheneOSGrapheneOS@grapheneos.social
    Aug 1, 2025, 1:50 PM

    @leeloo @Life_is @CoMaps It's best if apps add a version check for Android 15 and use the Fused location provider from the OS for Android 15 and above where it should always be present and properly functioning. This way, they avoid an unnecessary dependency on Play services for fused location with Android 15 or above. It's possible to implement this for older Android versions reliably by adding an equivalent to fused location within the app querying for the GNSS and network providers.

    💬 1🔄 0⭐ 0
  • Leelooleeloo@chaosfem.tw
    Aug 1, 2025, 1:58 PM

    @GrapheneOS @Life_is @CoMaps
    That's confusing. I have an Android 14 phone with CoMaps installed from F-droid, and no "Google service" anti-feature, so if I understood correctly, neither method should work. Yet I can enable the feature without any errors.

    💬 1🔄 0⭐ 0
  • GrapheneOSGrapheneOS@grapheneos.social
    Aug 1, 2025, 2:00 PM

    @leeloo @Life_is @CoMaps Fused location has been an OS API on Android for years. All we were saying is that for Android 15 and later it should always be available and reliable. There were issues with fused location availability in the past along with both OEM forks of Android on non-Pixel devices and aftermarket operating systems causing issues for it due to introducing bugs. It's entirely possible for apps to use the OS APIs for network location and fused location including before Android 15.

    💬 1🔄 0⭐ 0
  • GrapheneOSGrapheneOS@grapheneos.social
    Aug 1, 2025, 2:02 PM

    @leeloo @Life_is @CoMaps All we were saying is they should phase out using Google's Play services fused location API for Android 15 and later. There's only a reason to use it on older devices for compatibility. There's no reason to keep using it.

    In their non-Google variant of the app, the relevant option may simply be a no-op if it hasn't been removed as a toggle. You'll need to check the code or ask them about it. We were explaining how the OS APIs and Play service API work, not their app.

    💬 0🔄 0⭐ 0