Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dosen't work on deGoogled Android #59

Open
thereallinusrg opened this issue May 26, 2020 · 10 comments
Open

Dosen't work on deGoogled Android #59

thereallinusrg opened this issue May 26, 2020 · 10 comments
Labels
No-PlayServices Issues regarding a version not requiring Google PlayServices.

Comments

@thereallinusrg
Copy link

I run LineageOS without Google Services. The application reports, that it needs updated Google Play Sevices to run, which I will not install, since they are closed source and proprietary software.

@zukunft
Copy link

zukunft commented May 26, 2020

Several others have a similar issue: #51

@dbrgn
Copy link

dbrgn commented May 27, 2020

The Google Exposure Notification API (https://www.google.com/covid19/exposurenotifications/) is being distributed through Google Play Services. A device without Play Services will not have this API.

The alternative would mean that the app would constantly need to send BLE advertisement frames and listen for incoming BLE advertisement frames. This would be a big battery drain. Furthermore, since apps only have access to a high-level API, it's not possible to have the same level of control over the beacons being sent and received.

I am not involved in DP-3T (but I do work as an Android developer and have some BLE experience), but I do not see how this could be reliably implemented on application level (as opposed to OS level).

@zukunft
Copy link

zukunft commented May 27, 2020

@dbrgn I had installed a previous version of the App without Google Exposure Notification API and the battery drain was around 6%. This would be acceptable for me, but I guess the bigger issue is the contact key synchronization on the backend server.

@zukunft
Copy link

zukunft commented Jun 5, 2020

For the German App an alternative Backend synchronization has been requested: corona-warn-app/cwa-documentation#169 . Probably a similar setup could be used for Swiss App.

@zukunft
Copy link

zukunft commented Sep 3, 2020

Looks like Google has published the code of the API: https://github.com/google/exposure-notifications-internals

@simonroesch
Copy link
Contributor

simonroesch commented Sep 3, 2020

This repository contains snippets of code that show how the Exposure Notifications API works inside the Google Play services layer.

Unfortunately, this is not a complete solution that you can use as alternative on devices without PlayServices. But it helps very much in understanding what is done by the PlayServices and helps a lot for building an independent solution on app level as discussed in DP-3T/dp3t-sdk-android#10

@zukunft
Copy link

zukunft commented Oct 20, 2020

Maybe coralibre.de / https://github.com/CoraLibre/CoraLibre-android-sdk can be used as a base.

@lbort
Copy link

lbort commented Nov 12, 2020

Micro-G released a open implementation of the google Exposure notification framework. I used this with a de-googled version of lineage. It looked as it works, swisscovid as well as the german CoronaWarnApp were happy, and gave some statistical info, saying IDs are collected. I cannot confirm the notification process worked, since I was not shown any dangerous contacts, neither was I tested positive, so I couldn't publish my keys.

However, since the last update of swisscovid (version 1.2.0, released 28.10.2020), this setup with microG's framework stopped to work. Now it displays error "keine aktuellen Daten", RTSENLOST.

What exactely was changed from the previous version to 1.2.0? It seems not to be a problem with the Bluetooth stuff, but rather with the download of infected keys... Is it possible to make this work again? Many people with de-googled phones run microG, and this would be a fix for this issue.

@tobru
Copy link

tobru commented Nov 12, 2020

Please have a look at #249 and therefore also at microg/GmsCore#1258 (comment) which will explain what happened and what can be done.

@v3DJG6GL
Copy link

With the fix 4c2ef04 and the release of microG GmsCore v0.2.14.204215, SwissCovid version 1.2.0 should work again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
No-PlayServices Issues regarding a version not requiring Google PlayServices.
Projects
None yet
Development

No branches or pull requests

7 participants