Import and export exposure notification data
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Use case
I have used Google Play Services before.
Now I want to switch to microG.
Because of the Corona/COVID-19-situation I do not want to loose my data of encounters in the last 14 days.
How to
What I can currently do:
Go to the COVID screen:

Export the data:

Problem: After you press that menu entry, you get literally no feedback. I have no idea where that data is saved. (checking the usual internal storage I could not find anything.)
Intended solution
Anyway, what we need in microG's implementation is just an import feature for those.
For whatever reason, Google Play Services do not offer any import feature though – maybe so one cannot abuse it and generate fake results. (though AFAIK this is already cryptographically assured, as you cannot easily generate those hashes or respectively only random ones hmm)
Anyway, would be great if we could switch to microG but keeping the 14days history, so one does not loose data that could result in a missed COVID notification.
For completeness you may of course also implement an export feature – I guess if you have an import feature that will be easy. So you'd have feature parity with Google's implementation in this regard then.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the COVID screen and its export menu entry to determine how exposure notification data is currently handled in microG. Define the import and export behavior for preserving the last 14 days of encounter history, then verify that switching from Google Play Services does not lose usable notification data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100