background activity notice not disappearing #67
Closed
opened 2 years ago by ke352802081770314
·
31 comments
fynngodau
Loading…
Reference in new issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
After upgrading to 1.9.1.4 (I do not have Google stuff nor microG installed, so I am using the embedded microG ENF), I see a notification with a diagonal lines icon saying:
Originating App: Corona Tracing
Headline: Im Hintergrund aktiv
Text: Exposure Notification läuft im Hintergrund weiter. Füge Corona Tracing als Ausnahme zur Batterie-Optimierung hinzu oder verstecke diese Benachrichtigung in den Systemeinstellungen.
It cannot be dismissed by wiping sideways.
I went to settings Apps & Benachrichtigungen / Spezieller App-Zugriff / Akku-Optimierung display all, and switched Corona Tracing to "Nicht optimiert".
Within Corona Tracing this is confirmed: in "Einstellungen", "Priorisierte Hintergrundaktivität" is shown as "An".
Based on the wording of the notification, I would now expect that it disappears, because I have fulfilled one of the two "oder" conditions, I think the preferable one, but it is still displayed.
When will it disappear without me having to additionally suppress it?
Try restarting your device.
Thank you for the hint. Indeed, it does not show up after restart. I rarely restart my phone so this did not occur to me.
While making that notice disappear, now I get "Ihr Risikostatus: Bitte denken Sie daran, Corona Tracing Germany regelmäßig zu öff..." with the message cut off so I am not sure what it is trying to tell me, but it chimes every few minutes, re-issuing this message.
Also after the restart it shows "Aktualisiert: Gestern 01:57" (this was the last update before I installed 1.9.1.4) while before the restart it already updated today and also said so. I open the app and it does not show a more recent update. Before the restart it would have updated at that point. What broke? WLAN-Datenzurgiff and Mobilfunkdatenzugriff and Hintergrunddatenzugriff are permitted, I now also permitted Dtaensparmodus ignorieren, but it made no difference. This was my first reboot after installing the app at all.
Uh... I've not seen that before.
I rebooted again (more specifically, this time I switched off, after closing all foreground apps, and on again), and it stopped doing that.
Does the installation queue some activity to be performed after the next reboot? (I'm only aware of Windows software doing that, and after install usually asking for a reboot, but obviously the user interface of adb install is rather minimal.) In that case, could the strange behaviour be a consequence of the fact that between installing 1.7 and replace-installing 1.9 I didn't reboot at all, and some to-be-performed action prepared by 1.7 interfered with the meanwhile installed new version?
There's no install handling and rebooting isn't special. It just ensures that background services get restarted. On first start they don't necessarily know that background priority is granted.
So .. not sure what's going on. Does everything work correctly now?
I am running both Corona-Warn App (CWA) 1.9.1 from Play Store and Corona Contact Tracing Germany (CCTG) 1.9.1.6 from F-Droid at the same time on Android 9 (security update October 1, 2020) on a Nokia 5.
In both apps the settings are the same: Expose Logging is Active, Notifications are On, Prioritized Background Activity is On.
In Android settings > Battery the Adaptive Battery is Off.
In Android settings > Apps & notifications > Advanced > Special app access > Battery optimization I did set both apps to Not optimized.
When I restart Android then in CCTG's settings the Prioritized Background Activity is Off and in Android's settings the Battery optimization is Optimizing battery use.
I noticed this because the following notification is shown:
Can somebody explain to me why the battery optimization for CCTG is changed without my interaction?
It is never changed for CWA without my interaction.
P.S.: Thank you very much for providing and maintaining this fork of CWA!
For me, the app seems to work now.
Still, on the original topic, for example the "USB debugging is active" notice disappears as soon as I unplug the USB. Since the "im Hintergrund aktiv" notice is similar in nature (cannot be dismissed by wiping sideways) I would have expected that it is controilled by the app and would disappear as soon as the issue has been fixed, without a need to reboot.
I would find it nice if either the wording is changed, adding "this notice will remain until the next reboot", or more preferably, it disappears automatically after a solution has been applied.
Edit: in case you were asking me: OnePlus 3 (A3003), LineageOS 16.0 from 18 May 2019 (Android 9) - I stopped updating to LOS 17/Android 10 because that would have needed a ROM update and I was scared of it.
Pinging @larma here. Maybe the notification text needs to be made more precise. It's not enough to add battery exception inside the app depending on your android version and oem.
What's your phone model?
Nokia 5 "TA-1053"
From my view the notification text is competely correct, but I don't understand why the battery optimization setting changes without my interaction.
This issue has become stale. Is this still reproducible on version 2.18 of CCTG?
The issues I've reported were solved by reboot and the conditions for them appearing no longer apply, so as far as i am concerned you are welcome to close it.
@Ein-Tim
I currently have CWA 2.21.1 and CCTG 2.18.1.0 installed. I updated CCTG yesterday (via F-Droid).
After every reboot CCTG shows in the app a warning named "Prioritized Background Activity" with a blue "Allow" button. Allowing it lasts until the next reboot.
In addition there is a permanent notification (being not "away-swipable") named "Active in background Exposure Notification is running background. Exclude Corona Contact Tracing from battery optimizations or change notification settings to hide this notification." In my Android settings both CWA and CCTG are "Not optimized" regarding "Battery optimization".
And finally: The CCTG app currently crashes a lot when interacting with it for the first time after starting it.
I appreciate your work on this "ungoogled" app and on this issue here in particular. If my problems are special for me and/or my device only I can unterstand if you close this issue.
Thank you for your feedback @ke352802081770314! Nice to hear that the issue has been solved for you.
Hey @TeeTeeHaa
The beahvior you are observing indeed sounds very similar to the one @ke352802081770314 reported in the OP of this issue.
So you click "Allow", then the warning disappears and when you reboot the phone the warning comes back? And the notification is always there, even if you clicked on "Allow" in the app?
Could you please open a new issue for this?
I'd first like to get some more infos, maybe it is something that can easily be fixed, but yes, it is possible that this is an edge case and especially if no one from the CCTG-team can reprodcue the issue, it is hard to fix it.
@Ein-Tim
Correct.
Correct.
As I have no further information than "it crashes" I don't expect creating an issue to be helpful.
I appreciate that. How can I support it? I have very basic developer knowledge of Android and "adb". If you want some log files and tell me how to get those I might be able to post them here.
Maybe you could start the error log in CCTG? This is available by clicking on the 3 dots in the top right corner, then "App information" and then "Error reports". There just activate it and when the app crashes open a new issue and attatch the report together with the approximate time of the crash.
@fynngodau Would have to continue here, as I don't have experience in Android development. I guess a log file would help, but maybe Fynn also asseses the situation different.
I have activated it. So far the app did not crash yet. It might be related to the online update of the data (the stuff in the big, green box) which won't happen again until tomorrow. I'll leave the error reports actived.
...aaand it crashed. What I did today:
The log file is attached. It contains entries from yesterday (23. April) and today (24. April).
...aaand another crash. What I did:
My understanding is that CCTG is intended as a replacement for CWA (which depends on closed source components namely Google Play services, which some people including me see as a contradiction to open source).
I am puzzled why someone might want to install both of them? What benefit do you expect from this?
argh. I meant to abandon my comment without sending it, and definitely not close the issue. apologies for my mistake.
@ke352802081770314 Curiosity. I wanted to see the differences between CWA and CCTG and how fast the updates of CWA are integrated in CCTG. And according to CCTG's website it is possible to run both at the same time:
On my phone (Nokia 5) I unfortunately need Google services and a Google account so using CWA as soon as it was released was possible. CCTG came later.
Thannk you @TeeTeeHaa for the two error reports.
I will assign @Bubu & @fynngodau to this issue now, I hope one of them finds the time to look at the error reports soon. I will also take a first look to see if I can spot anything.
Stay safe and healthy!
Tim
@TeeTeeHaa Please, could you let me know at which time the app crashed ca.?
@Ein-Tim Probably less then a minute before the end of the log files.
Usually there are log entries every couple of seconds. In the first log file there are two 10 second "gaps" (I found by just looking at the log file). Those might eventually be the time of the crash and the restart of the app.
In the second log file there is a 40 second "gap" (maybe I was slower in restarting the app after the second crash).
Both log files even contain the string "Uncaught exception!" twice. Maybe that is related, too.
The logcat indicates that the issue occurs with drawing the cart. I've created a new issue #261 because it seems unrelated to the issue that was originally being discussed here.
I do assume that this is a bug in the Android system. The notification from microG is probably related. What is your Android version?
Sorry that I forgot to open a new issue for the crash (and its log files).
Android version: 9
Android security patch level: October 1, 2020
Kernel version: 3.18.120-perf #1 Tue Oct 6 11:41:08 CST 2020
Build number: 00WW_6_20A_SP01
Device name: Nokia 5 TA-1053
I disabled as many Google related apps as possible. Notable execptions (which still are enabled) are Google Play services, Googe Play Store, Google Play Games, Chrome and Quickstep (the "launcher"/home screen thing).
It is known to me that the Android system sometimes (possibly only on some versions) does not correctly answer the call whether battery optimizations are enabled or not.
However, I am curious why this happens because it happens:
I still do believe that this is rather an Android bug than a CCTG bug and don't know how to proceed here.
My recommendation would be to hide the notification that is permanently shown in the background through the notification settings. If only this notification type is disabled, it will not suppress other notifications like exposure warnings.
I even do not know how to proceed here. I'm fine with closing this issue, accepting this problem being a case of "does not work on my device". Thank you for your efforts.
I'll close this issue if @ke352802081770314 responds here that it is OK to close this issue or there is no feedback from the author in 2 weeks.
you're welcome to close it.