[GH-ISSUE #63] [Bug] Automatic background scan is not working #42

Closed
opened 2026-02-26 21:31:25 +03:00 by kerem · 5 comments
Owner

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

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
kerem closed this issue 2026-02-26 21:31:25 +03:00
Author
Owner

@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..

<!-- gh-comment-id:1104392437 --> @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..
Author
Owner

@aramova commented on GitHub (Apr 25, 2022):

Also running into this as of the latest version 1.3.3 on Android 12

<!-- gh-comment-id:1109010815 --> @aramova commented on GitHub (Apr 25, 2022): Also running into this as of the latest version 1.3.3 on Android 12
Author
Owner

@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.

<!-- gh-comment-id:1112167703 --> @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.
Author
Owner

@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

<!-- gh-comment-id:1114819656 --> @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
Author
Owner

@Sorunome commented on GitHub (May 9, 2022):

Yes, seems to be fixed now, thanks a lot!

<!-- gh-comment-id:1120731476 --> @Sorunome commented on GitHub (May 9, 2022): Yes, seems to be fixed now, thanks a lot!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/AirGuard#42
No description provided.