-
Notifications
You must be signed in to change notification settings - Fork 495
Enhance the visibility of the tracking status if location service is deactivated. #2301
Comments
@Nebkaa Location (Standortdienste) is needed for CWA under Android, except for the latest version, Android 11 (see https://www.coronawarn.app/de/faq/#android_location for German language FAQ) so it is important that location is enabled. If a CWA user disables location, then the Google Exposure Notification System immediately fires a notification which warns the user and instructs what to do: This notification can be dismissed by the user without taking any other action, in which case there would be no new recording of Random IDs from other mobile devices. Your screen shots show that the status in CWA changes from "RISIKO-ERMITTLUNG AKTIV" to "STANDORTDIENSTE DEAKTIVIERT". If you tap on the status, a detailed screen is shown with Risiko-Ermittlung Gestoppt showing: Problems with current display A. The display is misleading, because it says "Risiko-Ermittlung dauerhaft aktiv" even though it is not collecting new Random IDs if location is disabled. This is related to the hot topic "'Risiko-Ermittlung dauerhaft aktiv' despite BlueTooth being disabled" #920. B. The status information "STANDORTDIENSTE DEAKTIVIERT" is a correct description, however it does not inform the user on the main screen of the consequences of this status in clear words. C. Only the notification from COVID-19-Benachrichtigungen tells the user what to do. If this notification is dismissed without taking action to enable location then there is no further reminder or instruction to the user. Possible improvements
(Missing Internet is already covered by the app and it is not necessary to have a device permanently connected to Internet via WiFi or a mobile data connection. If no risk evaluation has been possible for more than 36 hours then a deadman notification is shown which alerts the user to the problem.) |
@MikeMcC399 As i said before I was shocked to see nurses and doctors not understand this fact, telling me that the app is green and the "Risiko-Ermittlung" is active, and therefore ID recording was running in their minds. |
I think there are a number of misunderstandings..., see: corona-warn-app/cwa-wishlist#352 (comment). |
Hello everyone, Thank you for your input. We have brought this topic to the attention of the development team. They will now investigate if the information in the UI is precise enough and how it could be adjusted. We will make a comment with updates here, if we hear anything new from the developer's side. Regards, Corona-Warn-App Open Source Team |
I have another related question about the Exposure Logging status If Bluetooth is disabled Exposure Logging is Restricted I don't understand why there is a difference between Bluetooth disabled and location disabled. Both location and Bluetooth are only needed by CWA to enable Bluetooth Low Energy. If either one or both are disabled then no Rolling Proximity Identifiers (RPI) can be exchanged. CWA continues to carry out exposure checks by pulling the keys from the server and comparing them to the ones stored on the device at regular intervals, however it can't collect any new ones.
|
@MikeMcC399 I forwarded your comment and questions to the developers. |
No planned |
Requested enhancement
Hello everybody, I would like to recommend that the layout of the main screen gets changed to enhance the visibility of the tracking status to make it easier for normal people to see that the app is not registering meetings with other people.
Expected Benefits
I met many people who did not realise and knew that the location services always needs to be active. I bet we have low numbers of active users due to this fact. With this change the numbers should increase and our overall tracking of this virus will enhance rapidly.
Example pictures with this very easy to oversee change in the status area on top of this huge green square of the status report that looks like everything is good and working fine.
Internal tracking ID: EXPOSUREAPP-5116
The text was updated successfully, but these errors were encountered: