search

corona-warn-app / cwa-app-android

Native Android app using the Apple/Google exposure notification API. The CWA development ends on May 31, 2023. You still can warn other users until April 30, 2023. More information:
https://coronawarn.app/en/faq/#ramp_down
Apache License 2.0
2.44k stars 496 forks source link

Exposure logging is not possible / Exposure logging active due to Background Job being killed from Manufacturer Battery Optimisation #637

Closed mueslo closed 4 years ago

mueslo commented 4 years ago

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

Additional context

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

Internal Tracking ID: EXPOSUREAPP-1592

mueslo commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

@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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

@ 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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

TimAviator commented 4 years ago

Same on Xiaomi Mi Note 10 Lite/Pro.

Reboot does not fix the issue.

Startrek12 commented 4 years ago

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 commented 4 years ago

@ 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 commented 4 years ago

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 commented 4 years ago

Same Problem with Xiaomi Mi 9 running Android 10.

Filusi commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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:

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 commented 4 years ago

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:

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

holgzim commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

FSDKO commented 4 years ago

Same problem on Huawei P10 Android 9 (9.0.1.185)

tessarakt commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

Same here on Xiaomi Mi 9.

FrankSJB commented 4 years ago

Same on Huawei Mate 9 Pro, latest OS patch level

Matt6233 commented 4 years ago

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

Skyhawk1328 commented 4 years ago

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

gbtec-michaelhoppe commented 4 years ago

Hey,

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

Btw: Thanks for your work 👍

BPKLN commented 4 years ago

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

Freche17 commented 4 years ago

Same here on Xiaomi Redmi Note 8

birgit-xy commented 4 years ago

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 commented 4 years ago

Huhu! Sprichst Du deutsch?

birgit-xy notifications@github.com 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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

birgit-xy commented 4 years ago

@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 commented 4 years ago

@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 commented 4 years ago

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 commented 4 years ago

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

Freche17 commented 4 years ago

Have you tried it with setting the app on autostart?

FraumitKlasse notifications@github.com 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 commented 4 years ago

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

mfgchen commented 4 years ago

Same here with Asus zenfone 6, Android 10

aeneasr commented 4 years ago

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