Cwa-app-android: Exposure logging is not possible / Exposure logging active due to Background Job being killed from Manufacturer Battery Optimisation

[mueslo]

Describe the bug

Status bar below the title bar tells me "EXPOSURE LOGGING ACTIVE". The main content of the app tells me

Exposure logging is not possible. Your exposure logging could not be updated for more than 24 hours. Updated: 16 Jun, 11:30.
ACTIVATE EXPOSURE LOGGING

Pressing on ACTIVATE EXPOSURE LOGGING brings me to a screen which tells me Exposure Logging is already active. (checkbox is set to 'Active', subtext says "Exposure logging has been active for 2 days. [...]". I also tried disabling and re-enabling it.

Going back to the main screen (or killing the app and reopening it) yields the same state.

When initially installing it on Tuesday, 16.06. it seemed to work fine (Unsure about version, possibly 1.0.0?) and on Wednesday gave me a status of "Low Risk", so it seemed to be working. Yesterday afternoon I also updated to 1.0.2 via Google Play Store. However, I cannot tell if it is really due to the updated version or some other cause.

Expected behaviour

Exposure logging works or consistently tells me it doesn't work and for what reason. I'm getting mixed signals here.

Steps to reproduce the issue

Screenshots are disabled in the app.

Technical details

• App version: 1.0.2
• Phone model: Xiaomi Mi 9T (Snapdragon 730)
• Android MIUI 11.0.5.0 (Android 10)

Additional context

Bluetooth and location services are enabled. The phone supports BLE.

---

Internal Tracking ID: EXPOSUREAPP-1592

[mueslo]

Update: seems to work again (after playing around intermittently with the app for 10-20 minutes). Backend server issues?

Leaving this open since backend server issues should be explicitly marked as such. Instead, it looks like something on my device was not working properly, which means it is at the very least a UX bug.

[marcmuschko]

Hi @mueslo,

thank you very much for reporting this! We are currently investigating this issue and will come back to you as soon as possible. If you can provide us with additional details, it might help a lot to identify the root cause for this behavior:
Did you change your phone date & time setting recently, disable background activity for the Corona-Warn-App or change the battery optimization settings for the Corona-Warn-App?

Thank you very much and best,
Marc

[mbw83]

Same problem here with a Xiaomi Mi 9 Lite. Mine is showing "Risk calculation not possible", "Last updated on Monday", but the update should have happened yesterday see also #590

Edit: I didn't change anything on my phone settings since maybe January.

Edit 2: I restarted my phone and now it is again showing "Niedriges Risiko". Seems to work for the moment.

[marcmuschko]

@mbw83 thanks for the reporting this and the follow-up, it's much appreciated and
I am glad to hear that it is now working for you!
Nevertheless we are currently monitoring this and can hopefully provide an update soon.

[gbrehmer]

Have the same issue with Huawei Mate 20 Pro (installed since tuesday, info widget that risk calculation is inactive, please activate, but on second screen is still active (since 2 days)). Probably caused by the battery settings for the app. I have reinstalled the app and deactivated auto settings. I will report tomorrow

[ramsesoriginal]

I have the exact same issue on a Samsung Galaxy S7, Stock Android 8.0.0.
App installed from Google Play.
Last night it was still snowing me "low risk".

Trying to activate or deactivate the power saving mode doesn't affect this issue.

[mueslo]

Hi @mueslo,

thank you very much for reporting this! We are currently investigating this issue and will come back to you as soon as possible. If you can provide us with additional details, it might help a lot to identify the root cause for this behavior:
Did you change your phone date & time setting recently, disable background activity for the Corona-Warn-App or change the battery optimization settings for the Corona-Warn-App?

Thank you very much and best,
Marc

None of the above. However, I do know that MIUI has very strict battery saving behaviour by default (i.e. apps in the background will be killed/put to sleep after a while, e.g. if you want to use a GPS logging app you need to manually set exceptions so your GPS tracing doesn't suddenly stop after 5 minutes). I have currently not set any special behaviour for Corona-Warn. Can you tell me more about what you believe error means? Does the app need to stay on for logging to work? (I was under the impression BLE public key collection is handled in the background by the Android system exposure framework itself) Or does the error mean it could not get the newest list of public keys from the servers?

If you like I can keep my phone with my current settings and see if it reoccurs, and then manually disable "MIUI optimized battery saving" and see if it occurs again. I think I need to wait 24h every time for it to reoccur though. Please let me know if you require any other information.

Edit: These are the standard settings in MIUI: https://i.imgur.com/CDfOCZ4.png https://i.imgur.com/EksCjUY.png
For apps I don't want to be put to sleep (e.g. Strava, Osmand+... I have to manually set it to "No restrictions").

[jaythie]

I have the same issue with a Samsung Galaxy S10,
Android 10. The recording stopped on the 16th at 9:25 am.

I have added the App to the list of apps, that shall not be put into standby. I have been in energy-saving-mode.

If you need any more info, im happy to provide it.

Best regards

--- edit
It works now that i have changed the settings mentioned above and updated to version 1.0.2

[marcmuschko]

@ all
Thank you lots for the detailed reports, we highly value your contributions to find and fix existing errors!
We have identified this issue and are working on a fix that should be rolled out soon. I will keep you posted once this is resolved.

Thanks again to all of you!
Best,
Marc

[the-matzup]

I can also confirm.
Device: Huawei P smart+ with Android 9.1.0.297

My first guess would be that the strict battery manager stops the background functions. But I see you guys are already on the issue.

[tessarakt]

Same issue here on a Huawei Honor 20 Lite.

Installed Tuesday morning, on Wednesday morning it showed me "Low Risk", when I looked this evening, I noticed the problem.

I first thought it was due to the GoPro app yesterday fiddling around with Bluetooth settings.

But then I noticed "RISIKO-ERMITTLUNG AKTIV", "Risiko-Ermittlung nicht möglich" and a button "RISIKO-ERMITTLUNG AKTIVIEREN" on the same screen, which is contradicting itself and thus very bad UX.

Version is still 1.0.0, I will update now.

[avy216]

Same issue here with redmi note 7. I already tried the suggestions you mentioned but I still can't see my infection risk.

[TimAviator]

Same on Xiaomi Mi Note 10 Lite/Pro.

Reboot does not fix the issue.

[Startrek12]

Same here iPhone 7 Plus.

Reboot and changing Corona App "Risko-Ermittlung" off and on, doesnt solve the problem.
Background Update is for the Corona App kind of light green (but the same for all other apps) and is not changeable under settings.

[corneliusroemer]

@ all
Thank you lots for the detailed reports, we highly value your contributions to find and fix existing errors!
We have identified this issue and are working on a fix that should be rolled out soon. I will keep you posted once this is resolved.

Thanks again to all of you!
Best,
Marc

Hi @marcmuschko, would it be possible to say what the problem is in a few words and reference the branch (if public) that you are working on? It's nice for the community to be in the loop and not just get notified once the fix is rolled out.

[mueslo]

Hi @marcmuschko, would it be possible to say what the problem is in a few words and reference the branch (if public) that you are working on? It's nice for the community to be in the loop and not just get notified once the fix is rolled out.

It sounds to me like the background "infected" key lists are not retrieved if the app is put to sleep or killed (which many ROMs do).
Relevant branch: https://github.com/corona-warn-app/cwa-app-android/tree/feature/key-retrieval-on-resume

I really hope key broadcast and collection are still working though... But I believe that is handled by the Android exposure subsystem so hopefully it is fine.

So yeah, I too would appreciate a short outline of what the current working theory is.

[greynoO]

Same Problem with Xiaomi Mi 9 running Android 10.

[Filusi]

I have the same problem with a Xiaomi Redmi Note 8T running Androidversion 9PKQ1.190616.001.
MIUI-Version: MIUI Global 11.0.9 Stable 11.0.9.0 (PCXEUXM)

[Filusi]

Sry, i found my problem.

The App Version was 1.0.0.
I thought, the app will updateing automaticy, but the app wasn't.
Now i updatet the app manually by the Google play store to 1.0.2 and that solved the problem for me. :)

[EMMAOpenSource]

The issue is also found here on a fully updated Huawei Mate 10 Pro (Android 10, EMUI 10.0.0, Play Services 20.18.17) with CWA V1.0.2. It is fully unclear whether the App is actually working or not. Nothing changed. Only thing I remember was acting as usual and turning off Bluetooth some hours ago (but immediately re-enabling it after CWA gave me a warning) and that CWA was (automatically) updated some time yesterday.

Maybe of interest:

• The issue persisted after a re-boot
• turning on/off tracing does not help either

EDIT: The issue appears to be resolved now although I have not altered a thing. Since this happens without interaction with the user (and without a visible warning), it is certainly critical to get that sorted out (also given the number of reported/confirmed cases).

[Kai-Krause]

Same issue with Galaxy S10e (Android 10, One UI Version 2.1, SecurityPatch 1.6.2020)
Solution in 'https://basic-tutorials.de/corona-warn-app-ihre-risiko-ermittlung-konnte-seit-mehr-als-24-stunden-nicht-aktualisiert-werden/' does not work as this menu cannot be found on S10e.

Solution found for Samsung S10e:

• Einstellungen
• Gerätewartung
• Akku
• Energieverwaltung von Apps
• Standby für nicht verwendete Apps: ausschalten

Alternative(in Test): Add 'Corona-Warn' to list 'Nicht in Standby versetzte Apps'

[holgzim]

Same problem with Huawei p20 pro.

The quick solution seems to be:

1) Einstellungen öffnen
2) Unterpunkt „Apps“ auswählen
3)„App-Start“ öffnen
4)Automatisch verwalten für die Corona-Warn-App deaktivieren, stattdessen alle Punkte manuell aktiv lassen
5)Smartphone neustarten
Einige Minuten später aktualisiert sich die App wieder.

Quelle: https://basic-tutorials.de/corona-warn-app-ihre-risiko-ermittlung-konnte-seit-mehr-als-24-stunden-nicht-aktualisiert-werden/

[Hechendorfer]

Same problem here with my Huawei P30 Pro.
Even the workaround https://basic-tutorials.de/corona-warn-app-ihre-risiko-ermittlung-konnte-seit-mehr-als-24-stunden-nicht-aktualisiert-werden/
didn't solve it.

[pskugit]

Same problem on Mi 9T running Android 9.
Reboot and Blogpost did not fix it.

[FSDKO]

Same problem on Huawei P10 Android 9 (9.0.1.185)

[tessarakt]

The quick solution seems to be:

   3)„App-Start“ öffnen
   4)Automatisch verwalten für die Corona-Warn-App deaktivieren, stattdessen alle Punkte manuell aktiv lassen
   5)Smartphone neustarten
   Einige Minuten später aktualisiert sich die App wieder.

Worked for me (Huawei Honor 20 Lite), but "einige" Minuten was definitely > 15.

[nicouh]

Same issue here on Xiaomi 9T, Andorid 10, MIUI 11.0.5. Only way to get the app to update its status once is a reboot. For the next update I have to reboot another time at least 24h later.
Intuitively without any evidence I assume it has something to do with the energy saving mode of MIUI, maybe disabling some aspects of the app.

[doktormerlin]

P30 Pro here, having the same issue. It worked fine on the first day, but it didnt refresh yesterday and today it said "Risikoermittlung nicht möglich"

[KathrinIG]

Same issue here on a Huawei Honor 7. First day no issues. Now the error message everyone has already reported despite logging being shown as active.

[NeverUsedID]

Same here. Xiaomi Note 7. Also i can't make Screenshots of the app.

Edit: looks like you need to enable "autostart" and disable MIUI Energy savingmode.

[egeu5]

Same here on Xiaomi Mi 9.

[FrankSJB]

Same on Huawei Mate 9 Pro, latest OS patch level

[Matt6233]

Solved the issue on Xiaomi Mi9, MIUI 11, Android 10, by turning off all energy savings for the Corona App.

[Skyhawk1328]

Gleiches Problem bei
Mi 9t(MIUI Global 11.0.5)
Redmi note 6
Redmi note 7

[gbtec-michaelhoppe]

Hey,

same problem on Honor 20 with Android 10.
Risk couldnt be determined since June 17, 2020.

Btw: Thanks for your work 👍

[BPKLN]

Same with my Huawei Mate 10 pro, Android 9 including newest Patches.

[Freche17]

Same here on Xiaomi Redmi Note 8

[birgit-xy]

thanks Freche17 - same with my Xiaomi Redmi Note 8 - Android 9 !!!! A call with a member of the hp of coronawarn.app: pls delete app and new download - haha!!! no result. SAP hotline gives me the same number so no-one could help!!! 3 days app on the phone, no green block. till now: Ungekanntes Risiko Da Sie die Risiko-Ermittlung noch nicht lange genug aktiv... blabla!!! F...k - no trial bevore release?!

[Freche17]

Huhu! Sprichst Du deutsch?

birgit-xy [e-mail] schrieb am Fr., 19. Juni 2020, 17:31:

thanks Freche17 - same with my Xiaomi Redmi Note 8 - Android 9 !!!! A call
with a member of the hp of coronawarn.app: pls delete app and new download

• haha!!! no result. SAP hotline gives me the same number so no-one could
  help!!! 3 days app on the phone, no green block. till now: Ungekanntes
  Risiko Da Sie die Risiko-Ermittlung noch nicht lange genug aktiv...
  blabla!!! F...k - no trial bevore release?!

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-android/issues/637#issuecomment-646699353,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQAL4XXRCZRTCNBTXT3LKZTRXOAGFANCNFSM4OBP5J5A
.

[Freche17]

Ich glaube ich hab die Lösung: Ihr müsst in den App Einstellungen für die Corona App den Autostart anschalten, dann funktioniert es zumindest beim Xiaomi Redmi Note 8. Hier noch einmal zum Nachlesen die Anleitung
https://www.androidpit.de/corona-warn-app-probleme-loesungen-fehler-bugs?amp=true

[Freche17]

I think I have the solution: You have to turn on the autostart in the app settings for the Corona app, then it works at least for the Xiaomi Redmi Note 8. Here you can read the instructions again
https://www.androidpit.de/corona-warn-app-probleme-loesungen-fehler-bugs?amp=true

[birgit-xy]

Hallo Freche17, klar spreche ich Deutsch. Bei mir funktioniert es leider so nicht.... aber vielleicht habe ich etwas übersehen... danke dir!

[birgit-xy]

@Freche17 ... bei mir steht trotz aller mehrfachen Versuche (Auto start ein, wieder aus, jedesmal Handy neu gestartet) immer noch, dass die App aktiv ist - aber darunterdass sie seit 0 Tagen aktiv sei! Widerspricht sich. In einem anderen Blog heißt es, dass man extra den Auto Start ausschalten soll, dann würde es funktionieren. https://basic-tutorials.de/forum/threads/corona-warn-app-ihre-risiko-ermittlung-konnte-seit-mehr-als-24-stunden-nicht-aktualisiert-werden.4149/ -Wie auch immer - es geht einfach nicht

[EMMAOpenSource]

@birgit-xy
Achtung! Hier ist evtl. etwas mehr Geduld gefragt. Nachdem die Energiesparfunktionen manuell geändert werden kann es schon mal eine halbe h dauern, bis sich hier etwas tut (eigene Erfahrung bei zwei völlig verschiedenen Huawei Geräten - beide Male schlussendlich erfolgreich). Nur neu starten reichte jedenfalls nicht aus.

Insgesamt ist dieser Fehler trotzdem völlig überflüssig und v.a. schädigt er der Akzeptanz der App. Die Anmerkung "Google Play Services" noch neuerer Bauart zu installieren ist ein Witz, denn die aktuell installierte Version ist weniger als drei Wochen alt und externe Pakete einzubinden ist dem Sicherheitsstandard nicht zuträglich.

[Matt6233]

Ich hatte auf meinem Mi9 erst Autostart für die App aktiviert. Das hat nichts gebracht. Dann Energiesparen ausgeschaltet, Neustart, und dann ging's.

[FraumitKlasse]

Same problem with my huawei p20 pro. Bugfix hasn't worked yet.

[Freche17]

Have you tried it with setting the app on autostart?

FraumitKlasse [e-mail] schrieb am Fr., 19. Juni 2020,
23:08:

Same problem with my huawei p20 pro. Bugfix haevn't worked yet.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-android/issues/637#issuecomment-646861125,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQAL4XSN3WIAAIWAJJC5IX3RXPHVLANCNFSM4OBP5J5A
.

[panoptiku]

Same problem here on a Oneplus 3T, OygenOS 9.06.
Workarounds like restart of the phone and disabling energy saving did not work.

[mfgchen]

Same here with Asus zenfone 6, Android 10

[aeneasr]

Bug appears on current iOS as well (iPhone X).

[mbw83]

Mine is again not updating. It still says that it was updated the day before yesterday, but it think this afternoon it will turn again to "Risk calculation not possible". I think this bug is also related to #621.

Hi @marcmuschko, would it be possible to say what the problem is in a few words and reference the branch (if public) that you are working on? It's nice for the community to be in the loop and not just get notified once the fix is rolled out.

@marcmuschko would it be possible to give a small update? For me it must not be the branch, just a short status update would be good. This would also prevent, these weird things going on here in this thread. As far as I understand, the big advantage of using the Google/Apple API is, that the app doesn't have to be running the whole day, just because the logging is made by the API. The only thing the app has to do is to download the infected keys from a server every 24 hours. So why setting some settings in regard to autostart or battery saving?
Nevertheless, even my instant messaging and email apps are able to work without setting these options.

[FraumitKlasse]

I've been successfully by using Einstellungen (settings) --> Akku (battery?) --> App-Start --> Corona-Warn --> Manuell verwalten (manage manually?) --> turned of every button manually --> turned on every button manually --> restarted my mobile --> repeated a fiew times
Today in the morning the app looks like working.

I't would be fine to fix the bug, some people I know would have given up yet.

Thanks!

Have you tried it with setting the app on autostart? FraumitKlasse [e-mail] schrieb am Fr., 19. Juni 2020, 23:08:
…
Same problem with my huawei p20 pro. Bugfix haevn't worked yet. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#637 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQAL4XSN3WIAAIWAJJC5IX3RXPHVLANCNFSM4OBP5J5A .

[Aim23]

Having the same issue on a honor 9 (SFT-L09) smartphone.
None of the "Tipps and Tricks" above worked so far.

[towo]

I've got a case here with a HUAWEI P smart (2018) that's showing the same problems; I've just deactivated the startup management, but it at least didn't lead to an immediate update. Software versions are current.

Maybe have a (rate limited) force update button, to circumvent that the app is only doing an update every 24h or so?

[casore735]

Same issue with Galaxy A3 (2017) and Android version 8.

[florianj1]

At first, my risk level was not updated as described in #621, thus I turned off energy saving (Switch "Energiesparmodus" to "Keine Beschränkungen"). 48 hours after last update I received a new one, but a few hours later my risk level changed to unknown and the situation became as described by @mueslo in this issue. After restarting my phone for approximately 5 times the risk level is back again.

[wende60]

Same here, Huawei P10, Android 9, active since 4 days but no status update. Already did set permissions in App-Start to manual management, but did not know that i should restart. Will see if restart will fix the issue now...
UPDATE: restart after settings-change does the job, so for now it is working. Took some additional time after restart though... So again (German menu) Akku - App-Start: set Corona-app to 'manuell verwalten' (all options on) and restart.

[potofcoffee]

Same here Huawei P20 lite, all automatic energy-management settings disabled for CWA. Sayys "Risiko-Ermittlung aktiv" and then "Risiko-Ermittlung nicht möglich: Ihre Risiko-Ermittlung konnte seit mehr als 24 Stunden nicht aktualisiert werden."

[tombied]

das selbe Problem seit heute auf mein Huawei P30 Pro.. keine Aktualisierung möglich trotz eingeschalteter Risikoüberwachung..

[Claudi801]

Same Problem with Huawei P20

[martinhd]

Same on my Honor 10 with Android 9 (Kernel 4.9.148)
Was working initially, but not any longer.....

[birgit-xy]

Von: martinhd [mailto:[email protected]]
Gesendet: Samstag, 20. Juni 2020 18:13
An: corona-warn-app/cwa-app-android
Cc: birgit-xy; Mention
Betreff: Re: [corona-warn-app/cwa-app-android] Exposure logging is not possible / Exposure logging active (#637)

Same on my Honor 10 with Android 9 (Kernel 4.9.148)
Was working initially, but not any longer.....

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/corona-warn-app/cwa-app-android/issues/637#issuecomment-647014986 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AQAMM7FTMWZ5A2GFOKHLQZTRXTNZ5ANCNFSM4OBP5J5A . https://github.com/notifications/beacon/AQAMM7A543JXCXT557SOTW3RXTNZ5A5CNFSM4OBP5J5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE2IKUSQ.gif

[cant-think-of-aname]

Same issue here with an Honor 8x with Android 10 and latest SW and security patches installed. Installed the app right after it was released on Tuesday, it worked as intented first and showed me a green status on Wednesday, on Thursday it said exposure logging was not working. Restart of the app or phone did not work, updating the app in the play store neither. I ended up uninstalling and reinstalling the app. It worked on Friday, but today on Saturday it was the same again. Seems it works for 2 days (48 hours?) and then stops. Will try to change battery saving settings for the app and see if that makes a difference, but the issue should be solved for non tech savvy users.

[mueslo]

I have now had battery saver disabled and autostart enabled for around a
day, and the bug remains.

Edit: Disabling battery savings and autostart was not enough, but after a restart, it seems it updates properly every day now.

[aWeinzierl]

Same problem:

Exposure Logging is not possible
Your exposure logging could not be udpated for more than 24 hours.
Last exposure logging: Low Risk
Updated 17 Jun, xx:xx

Click on:

Activate Exposure Logging

Exposure Logging Active( *)
Exposure logging has been active for 4 days. An exposure check can only be reliable if exposure logging is permanently activated.

When I go back, I see the same.
Disabling battery saver did not help.
Reactivating GPS, Bluetooth, and settings in the app did not help.

Version 1.0.2
Releasd on 12 Jun 2020
Android 7.1.2 N2G47H
MIUI version MIUI Global 11.0.2 | Stable 11.0.2.0(NAMMIXM)
Xiaomi Redmi 4X

[gbrehmer]

Have the same issue with Huawei Mate 20 Pro (installed since tuesday, info widget that risk calculation is inactive, please activate, but on second screen is still active (since 2 days)). Probably caused by the battery settings for the app. I have reinstalled the app and deactivated auto settings. I will report tomorrow

fixed by changing app battery settings (disable auto mode and leave the sub-settings unchanged = all active). But after that it takes up to 24 hours for the error to go away

[matheis]

fixed by changing app battery settings (disable auto mode and leave the sub-settings unchanged = all active). But after that it takes up to 24 hours for the error to go away

Yes, I can confirm this. Disable auto and keep the then shown settings does the trick. I use an Honor 8X with Android 10.
Just to mention it: It seems to me that Honor (and most likely Huawei, i.e. their EMUI) have these strict battery saving settings. Does anyone know if this feature of rigid battery saving options is EMUI specific? Reading the thread here one could get this impression.
BTW: I needed to do set manual battery settings also for Threema and Podcast Addict. Unfortunately I don't remember exactly, what kind of problem exactly I had with these apps. For Threema I can remeber, that I was not notified about newly received messages correctly/in time.

[schnodda]

To whom it may concern. I have the same issue. Opened the app and the "Exposure Logging not possible" screen is displayed. When I click on "Activate Exposure Logging" I get send to the activation menu in which the exposure Logging toggle is activated. Setting it off then on does not solve the issue.

Device: Xiaomi Mi 9T Pro
No battery optimization setting enabled.

edit: what I now see is that I did not toggle on the "autostart" feature in Xiaomi miui which prevents apps to start during system startup and run in background. I will now switch the feature on and report back if the error persists.

[gbhajda]

Gleiches Problem mit Samsung Galaxy M20, Android 10

[Benwick91]

Same issue on Xiaomi Redmi Note 7. None of the fixes with Autostart or Akku - App-Energiesparen work for me.

[mmlea]

Huawei PSmart FIG - LX 1 (Google Services enabled Auto start Change from Automatic to manual and back, restart made ,no battery saving enabled)....what may be interesting that from from 17.6. to 19.6. it worked and showed low risk and now ( letzte Aktualisierung 18.6. 18:06) since I assume yesterday it went back to Risikoermittlung nicht möglich and none of the suggested changes in settings ( Autostart enabled manually and back to automatic / Google Services running, no Accu saving ) gets Risikoermittlung back to work.How can sb know when the problem is solved ...will the app work again by itself or will updates / restart s be necessary ....and if yes where will this info be available.
Edit 22.6. 12;00 it is working again and tells me aktualisiert heute 11.18 h ( which is 2,5 days after the last actualization)Thank you VG

[doganoo]

having the same issue with an iPhone XR. The app showed me a "low risk" notification the first day. Since then it is showing "exposure logging is not possible". Tried app and phone restarting as well as revoking and granting exposure logging permissions

[schnodda]

To whom it may concern. I have the same issue. Opened the app and the "Exposure Logging not possible" screen is displayed. When I click on "Activate Exposure Logging" I get send to the activation menu in which the exposure Logging toggle is activated. Setting it off then on does not solve the issue.

Device: Xiaomi Mi 9T Pro
No battery optimization setting enabled.

edit: what I now see is that I did not toggle on the "autostart" feature in Xiaomi miui which prevents apps to start during system startup and run in background. I will now switch the feature on and report back if the error persists.

My error has now gone and my state returned to the nominal state "Low Risk".I will continue monitor, if the error reappears.

My working assumption is that my xiaomis "autostart" feature closed the app on system start (restart) so that the Bluetooth connections weren't monitored. After I enabled "Autostart" and the app, the app required some more logging time to return to the default "Low Risk" state.

2nd possiblility: Maybe the error is connected with the recent update closing the application and interrupting the logging (together with disabled "autostart")

[Kimtinki]

Same in Samsung Galaxy A3 (2017)

[tkowark]

In the meantime, the team identified a workaround that solved the problem at least for some users: https://www.coronawarn.app/de/faq/#no_risk_update. Would be great if you can let us know whether it worked for you as well.

Of course, the team is nevertheless still working on a proper solution for the issue.

[alxy]

Unfortunatly, the generic workaround has not worked for me. After restarting my phone (Huawei P30) and opening the CWA the problem still persists.

[EACourts]

The workaround hasn't worked for me either
Xiaomi Mi 9/MIUI 11.0.9

[schnodda]

@alxy Just to be sure. if you disable the battery saver mode after receiving the error. Make sure to wait a day until the logging has received enough data to trigger the low risk status. Disableing batter saver mode doesn't instantly triggers the low risk status.

That confused me initially when I applied the error fix. But it makes sense given how the functionality works.

I guess most people know that. But just to be safe.

[mbw83]

In the meantime, the team identified a workaround that solved the problem at least for some users: https://www.coronawarn.app/de/faq/#no_risk_update. Would be great if you can let us know whether it worked for you as well.

Of course, the team is nevertheless still working on a proper solution for the issue.

I still can not see the point, why setting this (weird) options should help solving the problem. As pointed out by @mh- in this thread of the cwa-documentation#236 three attemps within 1 minute are done to get the data from the server. If this fails (this can also be because the internet is not available), the next attempt will be done 24 hours later.
And as I also said before, my messaging (Signal, Telegram, WhatsApp, ...) and eMail (K-9 Mail, GMail, ...) apps are also able to retrieve the data on my phone without adjusting any energy options.

I do not want to offend anybody, I'm just trying to understand why this should help.

[alxy]

@alxy Just to be sure. if you disable the battery saver mode after receiving the error. Make sure to wait a day until the logging has received enough data to trigger the low risk status. Disableing batter saver mode doesn't instantly triggers the low risk status.

That confused me initially when I applied the error fix. But it makes sense given how the functionality works.

I guess most people know that. But just to be safe.

I indeed wasn't aware of this. I will see if the problem is gone tomorrow then and report if that is the case. For the FAQ I thnik it would make sense to clearly mention that it takes some time for the app to go back to green status again. As said, I expected it to work immediatly, as the last step in the FAQ workaround is to open the CWA.

Edit: I just reopened the app and can confirm it is working now! So the workaround worked for me.

[schnodda]

@alxy Just to be sure. if you disable the battery saver mode after receiving the error. Make sure to wait a day until the logging has received enough data to trigger the low risk status. Disableing batter saver mode doesn't instantly triggers the low risk status.
That confused me initially when I applied the error fix. But it makes sense given how the functionality works.
I guess most people know that. But just to be safe.

I indeed wasn't aware of this. I will see if the problem is gone tomorrow then and report if that is the case. For the FAQ I thnik it would make sense to clearly mention that it takes some time for the app to go back to green status again. As said, I expected it to work immediatly, as the last step in the FAQ workaround is to open the CWA.

Edit: I just reopened the app and can confirm it is working now! So the workaround worked for me.

Ok great to here. I am obviously not 100% sure how all the functions work. So not 100% sure about the 24hrs . :) But what I think is definitely reasonable for people is to wait at least a while after applying the bug fix. If it didnt't work immediately after applying the bug fix, one can't assume the bug fix didn't work. :)

But happy to be corrected by the developers.

[r5r3]

Auf dem Samsung A3 2017 funktioniert für mich folgendes:

Einstellungen => Apps => Corona-Warn => Akku => Akkuverbrauch optimieren => Alle Apps => Corona-Warn deaktivieren.

Nach dem Ändern dieser Einstellung wurde direkt wieder ein Risiko angezeigt. Davor ging es zwei Tage lang nicht.

[Alistro178]

The same Problem with Honor 8x.

[leholz]

Same problem here with Huawei Mate 10 Pro (device already mentioned). Also thought deactivating battery save functions for corona warn might help but this doesnt resolved the issue for me. Some days ago my phone was updatet to Android 10. I'm unsure if the update to EMUI 10 was installed right before i first had the issue described above.

Is the function of receiving and sending tokens affected by this issue?

Thanks

[Discostu36]

And as I also said before, my messaging (Signal, Telegram, WhatsApp, ...) and eMail (K-9 Mail, GMail, ...) apps are also able to retrieve the data on my phone without adjusting any energy options.

These apps are most likely using push notification services while CWA is not. The server is not pushing the list, the app is asking for it (at least that's how it was explained in UKW podcast).

Like others before me I'd like to ask the developers for more information about this issue:

• Is only the retrieval of the positives list affected or also the logging?
• Is it already sure that energy management is the (only) reason for this issue?
• Was the topic of possible energy management issues discussed in development?
• Is the fix you are working on only the in-app configuration of energy options or are there other things you are doing about this?

[drillabit]

Similar problem on Samsung A3 2017 Android 9. No Risk-Update since 18.6.2020 7:48. Shows button to enable Risk-Assessment, but when clicked, shows the enable switch in on position.
Today i had the app open around update time, did not fix it. Have no power saving enabled, excempted CWA from data-volume or power limitations. I am almost always in a Wifi at update time.

[cschoenle]

I had the same problem on Samsung Galaxy S10+. However, found that an update was available in Google Play store (from 20 June, had apparently not updated automatically), and now the issue is gone and everything working again.

[janfreymann]

Related to https://www.coronawarn.app/en/faq/#no_risk_update

Afaik it is possible to show a dialog to the user to disable battery optimization: https://developer.android.com/reference/android/provider/Settings.html#ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS

However, the setting does not "help" with vendor-specific battery optimizers.

[gbhajda]

Auf Basis der bisherigen Tipps habe ich es jetzt auch für mein Samsung M20 die Möglichkeit gefunden, die Corona App wieder zum Laufen zu bringen: Einstellungen => Gerätewartung => Akku =>Energieverwaltung von Apps Dort gibt es einen pauschal wirkenden Schalter „Standby für nicht verwendete Apps“, der bei mir gesetzt war; darunter gibt es dann eine Auflistung von Apps im Standby, und nachdem ich die Corona Warn App explizit auf „Nicht in Standby versetzen“ gestellt hatte und das Gerät neu gestartet habe läuft jetzt alles problemlos und aktualisiert auch.

Von: Robert Redl [mailto:[email protected]]
Gesendet: Sonntag, 21. Juni 2020 18:08
An: corona-warn-app/cwa-app-android
Cc: gbhajda; Comment
Betreff: Re: [corona-warn-app/cwa-app-android] Exposure logging is not possible / Exposure logging active (#637)

Auf dem Samsung A3 2017 funktioniert für mich folgendes:

Einstellungen => Apps => Corona-Warn => Akku => Akkuverbrauch optimieren => Alle Apps => Corona-Warn deaktivieren.

Nach dem Ändern dieser Einstellung wurde direkt wieder ein Risiko angezeigt. Davor ging es zwei Tage lang nicht.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/corona-warn-app/cwa-app-android/issues/637#issuecomment-647147439 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AQA3WLI53EGTQ3HUQNCSOELRXYV6DANCNFSM4OBP5J5A . https://github.com/notifications/beacon/AQA3WLIBM3PUONIDHWWCNZTRXYV6DA5CNFSM4OBP5J5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE2JK7LY.gif

[m6100]

It exists an unresolved Android bug for this issue that is being ignored by Google for more than 1.5 Years now: https://issuetracker.google.com/issues/122098785
Please see also: https://dontkillmyapp.com/

[jheinitz]

Hi,

I'm facing the same issue. I'm using a Huawei P30 Pro. Please let me know if you need more details.

Kind regards
Jens

[drillabit]

cschoenle wrote:

I had the same problem on Samsung Galaxy S10+. However, found that an update was available in Google Play store (from 20 June, had apparently not updated automatically), and now the issue is gone and everything working again.

Found this update today, didn't install automatically on my phone, but did the trick after installing it manually!
Thanks to cschoenle!
Thanks to all the other people, but the app was already exempted from Standby! That did not help in my case, but may be its needed... who knows...

[casore735]

Samsung Galaxy A3 (2017) with android 8: I tried all the workarounds with the battery standby mode and disabling the optimization, update to version 1.0.2, none of this worked. I now manually updated the app to the latest version 1.0.4 (the app did not update automtically), and now it's working again.

[gbrehmer]

I now manually updated the app to the latest version 1.0.4 (the app did not update automatically), and now it's working again.

Probably because with 1.0.3+ the app is getting updates also on app start (https://github.com/corona-warn-app/cwa-app-android/pull/660). It's possible that the problem still exists, if the app is not opened manually. Does anyone know which downsides this approach has?

[Kimtinki]

In the meantime, the team identified a workaround that solved the problem at least for some users: https://www.coronawarn.app/de/faq/#no_risk_update. Would be great if you can let us know whether it worked for you as well.
Of course, the team is nevertheless still working on a proper solution for the issue.

to Change the battery Settings didn't work for me. Today I had the Chance to update the app to the newest Version, it was not possible before, now the app works again

[holgerman]

Same on Samsung Galaxy Note 9
Workaround not relevant for Note 9 Android 10, as settings have different names, tried to adapt the workflow as shown below, but this did not work either...bug remains
Öffne die Geräte-Einstellungen.
Wähle 'Apps' bzw. 'Apps & Benachrichtigungen'.
Wähle 'Corona-Warn'.
Wähle 'Akkuverbrauch optimieren'.
Wahle alle
Wähle 'Corona-Warn'. --> umstellen, dass optimieren NICHT mehr gewaehlt ist
Neustart

[Jo-Achim]

[Info:] „Risiko-Ermittlung nicht möglich“ und „Risiko-Ermittlung einschalten“ bei „Risiko-Ermittlung Aktiv“…
"Android one - Nokia 7.1", Android 10 mit Sicherheitspatch vom 01. Mai 2020, CWA 1.0.4.

Scheinbar verhindert die eingeschaltete Option „Datensparer“ die korrekte Risiko-Ermittlung. Nach Ausschalten der Option „Datensparer“ und erneutem Aufruf der CWA funktioniert die Risikoermittlung wieder; d.h. das ermittelte Risiko wird angezeigt.

---

[Info:] "Risk determination not possible" and "Activate risk determination" when "Risk determination active" ...
"Android one - Nokia 7.1", Android 10 with security patch from May 1st 2020, CWA 1.0.4.

Apparently the activated option "Data saver" („Datensparer“) prevents the correct risk determination. After switching off the "Data saver" („Datensparer“) option and opening the CWA again, the risk determination works again; i.e. the determined risk is displayed.

[svengabr]

Fix for iPhone users (I am using iPhone XS Max)

1. Go to "Settings"
2. Go to "General"
3. Go to "Background App Refresh"
4. Turn "Background App Refresh" on
5. Find the Corona-Warn App in the list and enable Background App Refresh
6. Restart Corona-Warn App
7. It will work now

[FabianFalck]

I confirm that @svengabr 's comment fixes the issue for iPhone users. I had this issue since day one when the app was released; it rendered the app useless for me and it wasn't fixed until now (I have the latest version of the app). The average user would not attempt to find a solution for this issue here on Github. This requires an immediate fix with a warning message that redirects to the correct settings menu (as detailed above), if background app refresh is disabled. Currently, the warning message redirects to the general app settings, where background app refresh is enabled, but greyed out, since the global background app refresh was turned off. This is misleading.

[daimpi]

@FabianFalck agreed. I see quite a few users still experiencing this issue. It seems to get tracked here currently btw 🙂.

[yannicgraeser]

I have the same problem. I am not able to use the app. After deleting and reinstalling the app works for some time. I assume this has to do with disabling and enabling bluetooth/air plane mode.

[GPclips]

Hello community,

This issue has been fixed (Release 1.3) and will be closed now.

Thanks,
LMM

Corona-Warn-App Open Source Team