Moved to assets repo available at https://codeberg.org/corona-contact-tracing-germany/assets
|29 minutes ago|
|.circleci||2 months ago|
|.idea/codeStyles||5 months ago|
|.pipeline||6 months ago|
|.reuse||3 months ago|
|Corona-Warn-App||2 days ago|
|LICENSES||3 months ago|
|Server-Protocol-Buffer||1 month ago|
|docs||4 weeks ago|
|fastlane||2 months ago|
|fdroidrepo||2 weeks ago|
|gradle/wrapper||3 months ago|
|metadata||2 weeks ago|
|protobuf/build||10 months ago|
|.editorconfig||8 months ago|
|.gitignore||1 month ago|
|.gitlab-ci.yml||4 months ago|
|CHANGELOG.md||2 weeks ago|
|CODEOWNERS||4 months ago|
|CODE_OF_CONDUCT.md||11 months ago|
|FAQ_de.md||2 days ago|
|Gemfile||3 months ago|
|Gemfile.lock||2 months ago|
|LICENSE||3 months ago|
|README.md||2 days ago|
|build.gradle||2 months ago|
|gradle.properties||3 weeks ago|
|gradlew||3 months ago|
|gradlew.bat||3 months ago|
|prod_environments.json||1 month ago|
|screenshot.sh||3 months ago|
|settings.gradle||11 months ago|
|sonar-project.properties||10 months ago|
|translation_v2.json||3 months ago|
Our F-Droid repository contains beta versions and is updated with new releases immediately. After a few days, stable releases will also be available in the standard f-droid.org repo. You can also verify the builds yourself, see Reproducible Builds.
This is a fork of CWA without proprietary dependencies. While the German Corona Warn App itself is Free Software, it depends on Google's proprietary Exposure Notification Framework. This fork instead uses the drop-in compatible microg implementation.
While we've had many reports of users successfully running the app on various Android versions it's by far not as well tested as the official Corona-Warn-App. Use at your own risk! It should work on any Android 5+ device regardless of installed play-services or microg versions.
If there's microg already installed on the system it will use the exposure notification framework from there. Otherwise it will use the bundled implementation. It will never connect to the play services exposure notification framework.
There's currently no translation system in place as most translation are taken directly from CWA. There's some small bits left to translate/fix for Romanian, Bulgarian and Turkish. Please contact us!
The FAQ is also available in German.
If you see such a notice, your device is capable of collecting IDs from other devices, but not able to send any itself. In case you are infected and you decide to notify others, nobody will be able to receive your warning, unfortunately.
This is caused by a restriction in the combination of hardware and software that doesn't allow CCTG to make use of Bluetooth LE periphial mode. In some cases, a different operating system or newer OS version may bring a Bluetooth driver that has support for this advertising mode, which can fix the issue. In other cases, we don't know of anything you can do to resolve the issue.
Specifically, some operating systems on Fairphone 2 are affected by this, but it has also been reported that LineageOS contains a compatible driver.
This usually means that the scanner service is getting stopped in the background.
The scanner service should restart whenever you manually disable Exposure Logging and enable it again.
If you notice that scanning stops again eventually and you would like to contact us regarding this, it's best if you include details about your operating system and device vendor, as well as an indication that you followed the instructions above.
Yes! You can be warned about contacts in each of the countries that are included in this list: https://www.coronawarn.app/en/faq/#interoperability_countries
You can not receive test results from these countries. In case you are infected, however, you may call the TAN hotline to receive a code that allows you to warn others.
The official Corona-Warn-App build contains a proprietary component to interact with the Exposure Notifications API, even if microg is installed instead of Google Play Services.
Corona Contact Tracing Germany replaces this proprietary component with a different library provided by the microg project, meaning that it is built as fully free software (in contrast to Corona-Warn-App).
Our app also ships with the relevant components to also function as a standalone app if microg is not installed.
Additionally, we have the following "exclusive" features, though we are always willing to contribute our improvements back to CWA:
Due to an upstream decision, CWA's data donation (privacy preserving analytics, PPA) and survey features are not available in CCTG, as they require Google SafteyNet attestation. (cwa-wishlist/#356)
Both apps are periodically scanning for encounters in the background, but not exactly at the same time. Therefore, both apps can collect slightly different data and reach different conclusions about your risk status.
Starting with version 1.9.1 this is expected, see the official blog post:
In simplified terms: Under Exposure Notification Version 2.0, the operating system also logs encounters with a risk lower than "low risk" (green). However, since these encounters are not relevant from the current epidemiological perspective, the Corona-Warn-App filters them out.
This may be correct for iOS; for Android, the platform is supposed to allow you to grant exceptions from battery optimization procedures.
No, this app bundles a standalone version of the microG implementation that will get used when there's no microG system installation found.
The app doesn't access GPS or Network location but Android considers bluetooth scanning a form of location access (because you could derive location information from the info you could get there), see here for details: https://stackoverflow.com/a/44291991/1634837. CCTG doesn't do any location tracking though.
On Android 11 Google allowed the play services ENF implementation to do bluetooth scanning in the background without special location permission. CCTG isn't whitelisted of course and thus needs to still ask for full location permission in Android 11.
On Android 11, it is necessary to explicitly set location access to Always enabled through the settings menu in order to enable Exposure logging. This video demonstrates how to do that.
Shortly after an update to CWA is released, we will release a new version of CCTG. New versions are immediately available on our repo.
In the first stage of our "transparent staged rollout", the app is not marked as "suggested" yet, meaning that your F-Droid client won't recommend it as an update, though you can install it manually. We do this to be informed about crashes and other issues by users who knowingly choose to try out a version that might not be stable yet.
Once we feel that all issues are sorted out, we will mark the most recent version as "suggested", causing users of our repository to receive the update immediately (once their F-Droid client refreshes the repository).
After some time, the latest version also appears in the official F-Droid repository, though as usual for F-Droid, this can take a while. Therefore, please be patient. F-Droid will serve exactly the APK that we also have in our repo, because our app builds reproducibly.
You might want to follow our mastodon account, where we will announce new versions.
If you have been running CWA with google's exposure notification framework before, you'll have to use both apps in parallel for two weeks. After two weeks all past exposure data will have been deleted and all new data is also recorded by the CCTG app. If you have a positive test result, you'll have to report this through CWA until the two weeks are over. You can uninstall CWA after those two weeks. As far as we know there's no downsides to running both apps in parallel.
If you have been using CWA on a phone with microG migration is super simple instead: Just uninstall CWA and install CCTG, no exposure data will be lost in the process. The app will say that it has only been active for 0 days again, but this is purely cosmetic and does not have an effect on the exposure notification and reporting functionality.
Some ROMs come with a version of microG that is signed with a different key from the one the microG project distributes, in this case you need to wait for your ROM to update their built-in microG version before you can use the new CCTG version.
CCTG version 1.9.1.X needs microG at least version 0.215 to work. The previous version (1.7.1) needed at least version 0.2.14 but this wasn't enforced.
If you already updated you can try following this comment to see how to downgrade to 1.7.1 again. You can also uninstall CCTG and reinstall the older version. Your exposure data (but not pending or received test results) will be kept intact inside the microG installation. The app will start counting from day 0 again but this makes no functional difference.
Since version 184.108.40.206, there is a bottom tab for the encounters graph from microg. If you however want to access the other microg Exposure Notification settings screens, you can still follow these steps:
Open the exposure logging settings by clicking on the "Exposure logging active" (or "Exposure logging stopped", etc.) section above your risk status on the main screen. From there, select "Open advanced settings". It'll magically take to to the correct (integrated or external) microG EN settings page. If you're still unsure what to do, the video attached to this post may help you.
Alternatively, go to App Information (via the three-dot/kebab menu) and then tap on the
ENF Version XYZ field. This will bring you to the same screen. This used to be the only option in earlier versions.
See also here:
See docs/rebuilding.md on how to reproduce the official builds.