mirror of
https://github.com/seemoo-lab/AirGuard.git
synced 2026-04-25 23:45:50 +03:00
[GH-ISSUE #63] [Bug] Automatic background scan is not working #42
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AirGuard#42
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Sorunome on GitHub (Apr 18, 2022).
Original GitHub issue: https://github.com/seemoo-lab/AirGuard/issues/63
Despite having the app excempted from battery optimization, the background scan is not working. Every time when opening it the "Last scan" field is from I have last opened the app.
I use LineageOS 18.1 (Android 11) and would be happy to provide any debugging information (adb logcat, whatnot) as needed
@lenhart commented on GitHub (Apr 20, 2022):
Issue #54 seems to be related.
I have the same problem with an old Android 9 Phone (Moto X4). The last scan is some old date 14 days past (even when I just did a manual scan) and it definitely did not detect an Airtag on a borrowed bike which I used for a couple of hours..
@aramova commented on GitHub (Apr 25, 2022):
Also running into this as of the latest version 1.3.3 on Android 12
@Sn0wfreezeDev commented on GitHub (Apr 28, 2022):
Hi,
We believe that this issue might be related to Android updates. We have delivered several updates in the recent past, and it looks like an update might stop the Android background worker. According to the documentation, this should not happen, but we will add several changes that will reschedule the background scans after the app was updated.
@Sn0wfreezeDev commented on GitHub (May 2, 2022):
Should be fixed by version 1.3.4:
https://github.com/seemoo-lab/AirGuard/releases/tag/1.3.4
It'll be available on Google Play a bit later, since we use a phased rollout
@Sorunome commented on GitHub (May 9, 2022):
Yes, seems to be fixed now, thanks a lot!