From e0963298071290284331f85e237ab4bc4cbf4291 Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Sat, 6 Mar 2021 17:43:13 -0500 Subject: [PATCH] GNSS + carrier-based A-GPS is hard to improve The available data providers for supplementary location information do not appear to have much to offer. There's also the issue of reliability and trustworthiness of user generated content. https://github.com/GrapheneOS/os_issue_tracker/issues/24#issuecomment-792069571 --- static/index.html | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/static/index.html b/static/index.html index 60b6e40f..859756ba 100644 --- a/static/index.html +++ b/static/index.html @@ -93,12 +93,11 @@

AOSP APIs not tied to Google but that are typically provided via Play services will continue to be implemented using open source providers like the Seedvault - backup app. Text-to-speech, speech-to-text, non-GPS-based location services, - geocoding, accessibility services, etc. are examples of other open Android APIs - where we need to develop/bundle an implementation based on existing open source - projects. GrapheneOS is not going to be implementing these via a Google service - compatibility layer because these APIs are in no way inherently tied to Google - services.

+ backup app. Text-to-speech, speech-to-text, geocoding, accessibility services, + etc. are examples of other open Android APIs where we need to develop/bundle an + implementation based on existing open source projects. GrapheneOS is not going to + be implementing these via a Google service compatibility layer because these APIs + are in no way inherently tied to Google services.

We're developing a minimal Play services compatibility layer as a regular app without any special privileges. The app will provide a stub implementation of the