Frequently Asked Questions

You can download it from the Apple App Store or Google Play Store.

Last updated: 28 10 2020

It's not foreseeable at the moment if and when the app will be available in other app stores except Google or Apple. The app will use the Apple and Google Exposure Notification APIs.

Last updated: 28 10 2020

We don’t plan to implement the app for tablets, smart watches, and other wearables. Our focus is on smart phones, for example because of the availability of the required APIs.

Last updated: 28 10 2020

Persons aged 16 and older may use the app, which is targeted at users in Lithuania. The age restriction of 16 years and older is necessary, because the app processes data that is particularly worthy of protection under the General Data Protection Regulation (GDPR) of the European Union. According to the GDPR, minors can only give their effective consent to the processing of data after the age of 16. In principle, this applies to both app stores.

However, the level of strictness is different in both app stores:

  • Apple applies stricter criteria in its store, including data protection and GDPR age restrictions. This results in the specification '17+' in the App Store. Apple may require you to verify your age.
  • Google Play Store, on the other hand, only applies USK specifications. According to the USK, the app is approved for all age groups, which is why the minimum age in Google Play Store is 0.
Last updated: 28 10 2020

The app is currently available in the following languages:

  • Lithuanian
  • English
  • Russian
  • Polish

The telephone hotline (+370 619 54870) and email support service ([email protected]) answers in Lithuanian only.

The language of the app is derived from the language that is configured in the smartphone's language settings. To display the app in other languageplease change the language in your phone settings.

Please note that many countries release their own Corona tracking apps. Corona tracking is also available in the app stores and play stores of these countries, the Corona tracking apps could be mixed up. Therefore, make sure that you download the app for your country.

Last updated: 28 10 2020

Google delivers the required Exposure Notification API for contact tracing apps with Google Play Services. The API is supported starting with Android API level 23. This version is available starting with Android version 6.0. This was decided solely by Google. In addition, older devices sometimes don’t support Bluetooth Low Energy. We as app developers, unfortunately, cannot influence this.

Last updated: 28 10 2020

Apple introduced the required Exposure Notification API with iOS 13.5, see About iOS 13 Updates. You can find the supported devices here: Supported iPhone Models. Unfortunately, Apple no longer supports devices that are older than 4-5 years. We as app developers, unfortunately, cannot influence this.

Last updated: 28 10 2020

Apple/iOS: Korona Stop LT runs on the iPhone 6s or higher. The Exposure Notification API was introduced with iOS 13.5, so your operating system needs to be iOS 13.5 or higher.

Google/Android: Korona Stop LT runs on phones with Android 6 ('Marshmallow') or higher. Google Play services install the Exposure Notification API automatically.

For other operating system-related questions, please contact Apple or Google.

Last updated: 28 10 2020

Since I installed the app, my phone sometimes behaves oddly. Example: There are occasional problems with other apps and devices that use Bluetooth. What can I do?

Some users report that their phones behave differently since they installed Korona Stop LT app. Example: Sometimes the communication between their phones and Bluetooth devices via other apps is interrupted. This affects, for example, smart watches or Bluetooth earphones. We’re investigating these problems, but this is likely a problem with the basic operating system functions, over which we have no control.

Please try the following:

  • Restart your phone.
  • Unpair the other Bluetooth-connected devices and recouple them.

If the above does not help, contact your device manufacturer:

  • Apple/iOS phones: Apple Support
  • Android phones: Get help from your device’s manufacturer
Last updated: 28 10 2020

If, when opening Korona Stop LT app, the current keys of positively tested users are to be downloaded from the server (because automatic data synchronization was not yet carried out on that day) and no internet connection can be established, you may receive the following error message: 'Cause: 9002, Something went wrong. timeout'. There are two different known causes that can lead to this error:

  1. The internet connection is still being established. If you have just switched on previously deactivated data connections (Wi-Fi or mobile) or restarted your phone and immediately open Korona Stop LT app, the internet connection may not have been fully established yet. There are also special apps that only enable data connections when the screen is switched on. In these cases the error message can occur. Solution: If the internet connection was deactivated or interrupted, wait a few seconds after switching on the internet connection before opening Korona Stop LT app. If you use an app to control data connections, set it up so that data connections in the background are enabled for Korona Stop LT app.
  2. The internet connection is blocked. This can be the case if you have either manually restricted data connections in your phone’s settings or if data connections for Korona Stop LT app have been automatically deactivated by your antivirus app and/or firewall. Solution: Enable data usage in general as well as background data and unrestricted data usage in the settings of your phone for Korona Stop LT app. If you use an antivirus app and/or firewall on your phone, set it up so that there are no data usage restrictions for Korona Stop LT app.
Last updated: 28 10 2020

This is a general notification, which does not mean that risk encounters have been identified. It is not a message or function of the Korona Stop LT. Apple's Exposure Notification Framework (ENF) sends this notification and displays the icon. Apple's ENF provides information about any encounters with app users who were approved for Covid-19 infection without making a statement as to whether or not it was a critical encounter according to the apps algorithm. For example, encounters are also displayed in case the distance was more than 8 meters or in case it only lasted a few minutes. This means that the 'Weekly Update' only provides information about technical procedures of the ENF that are insufficient for an actual risk calculation. A reliable risk calculation takes place exclusively in the Korona Stop LT app under the scientific framework. You can view your current risk status directly in the Korona Stop LT app.

Last updated: 28 10 2020

Your phone settings display the exposure checks for the last 14 days: Apple: 'COVID-19 Exposure Logging', Android: 'Exposure checks'. When the app was running constantly during the last two weeks, you should see 14 checks within the last 24 hours.

Please note: The log is just the history. The exposures of the last 14 days are checked and the risk status calculated each and every day. The important thing is that the exposure logging for within the last 24 hours is shown.

It might be that entries are displayed for less than 14 days, although exposure was checked correctly. There are several reasons:

  1. The log has a fixed limit of 100 entries on iOS devices. If there are more entries, only the latest are kept. We're in contact with Apple so that the complete log will be displayed. The log limit of 100 entries on Android devices has been recently removed by Google at the end of August 2020.
  2. Sometimes, only 13 logs display for a day. The 14th entry was deleted only after risk calculation. This can happen when the time of downloading the keys from the server intersects with the time of deleting the keys that are older than 14 days from your phone. The same applies here: the exposure was checked properly.
  3. If you use the app only recently (let's say for 5 days), less checks for the last 24 hours are displayed (here: 5 checks), one for every day that the Korona Stop LT app was running constantly.
Last updated: 28 10 2020

When the app downloads the current diagnosis keys from the server, a check of the exposure log is performed. During that process, a separate check is performed for each of the last 14 days, for which diagnosis keys are available. It is therefore not an error that multiple, seemingly simultaneous entry are visible in the exposure check history. You can further click on the details of each check to see that different amounts of keys were provided for each of them.

Last updated: 28 10 2020

The Korona Stop LT uses the latest Bluetooth technology: Thanks to the Exposure Notification API from Apple and Google, the app can use the energy-efficient BLE (Bluetooth Low Energy) technology.

The battery consumption of the Korona Stop LT is made up of two factors: the consumption of the app itself and the consumption due to the recording of the encounters via the Exposure Notification Framework. The latter can be optimized by using the currently available operating systems for iOS and Android.

While interpreting your battery consumption, please note that the percentage refers to the full use of your phone in the last 24 hours. This means that a frequently and intensively used phone has a very low percentage of battery consumption per app. On the contrary, if you use your phone mainly to make phone calls and only occasionally stream music or use social media, the percentage per app will be relatively high.

Note for Android phones: Bluetooth devices near your device can only be detected if 'Use location' is activated on your phone. For details, see Android: When activating exposure logging or Bluetooth I'm asked to activate my location. Do I have to do this?. This means that other apps on your device could also use your location, which might be the reason for higher power consumption. To avoid this, you should check which apps use your location. Go to your device settings and choose 'Security & Location' > 'Location' > 'App level permissions'. Here you can deny other apps permission to use your location if you don't think they need it. Since Korona Stop LT doesn't need this permission, it doesn't appear in the list.

Last updated: 28 10 2020

Korona Stop LT does not track your location and does not have permission to do this. The reason for this message is an Android requirement: Bluetooth devices in close proximity to your device can only be detected if 'Use location' is activated on your phone. However, this doesn't mean that apps that use Bluetooth can automatically track your location.

Since Korona Stop LT must be able to detect devices in close proximity, you must activate the general system setting 'Use location'. However: The app will never record your location and will never use GPS. You can verify this yourself:

  • Open 'Settings' on your phone (not the settings of the app).
  • Choose 'Security & Location' > 'Location' > 'App level permissions'.
  • You see a list of apps that can use your location if you give them permission. Korona Stop LT is not listed here.

Here you can allow or deny other apps to use your location, but since Korona Stop LT doesn't need this permission, it doesn't even appear in the list.

Again, as described above: You should not deactivate 'Use location' under 'Settings' > 'Security & Location' > 'Location', because this is a prerequisite for exchanging the encrypted random IDs.


Last updated: 28 10 2020

All active Korona Stop LT aps once a day download the diagnosis keys released on the Korona Stop LT server and pass them on to the operating system in batches through an interface. The app checks whether any of these received, recorded rolling proximity identifiers match any of the diagnosis keys. If there is a match, this means the following: The user’s smartphone encountered the smartphone of a person who has subsequently uploaded their diagnosis keys.

In the next step, the app analyzes all the matching rolling proximity identifiers for each diagnosis key, to estimate how long the exposure lasted in total on the day in question and how close the smartphones were to each other on average during the exposure. The distance is calculated from the measured reduction in strength of the Bluetooth signal, which is specified in dB (decibel). All exposures for a diagnosis key that lasted less than 10 minutes in total (regardless of how close the smartphones came during that time) or during which the smartphones were more than 8 meters (73 dB attenuation) apart on average (regardless of how long the exposure lasted) are rated as harmless.

The remaining encounters are rated collectively according to their distance and duration as well as the presumed infectiousness of the other person(s). This rating doesn't always yield an increased risk in which case those encounters - together with the harmless encounters from above - will be shown in the Korona Stop LT app but the risk status will stay the same.

Last updated: 28 10 2020