starred/AirGuard
1
0
Fork 0
mirror of https://github.com/seemoo-lab/AirGuard.git synced 2026-04-25 15:35:49 +03:00
Code Issues 30 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #211] Frequent background ANR crashes #131

New issue
Closed
opened 2026-02-26 21:32:13 +03:00 by kerem · 6 comments
kerem commented 2026-02-26 21:32:13 +03:00
Owner
Copy link

Originally created by @ghost on GitHub (Sep 16, 2025).
Original GitHub issue: https://github.com/seemoo-lab/AirGuard/issues/211

I have LogFox running in the background and it tells me constantly that AirGuard crashed.

OS: Android v15, OneUI v7.0, Kernel 5.15.153, SE=enforcing, Knox v3.11, patch level: 2025-07-01
Hardware: Samsung Galaxy A16 5G (EU)

AirGuard:

  • Version: 2.6.0 (f-droid) (2025-09-13)
  • Battery: Unrestricted
  • Permissions: Location, Nearby devices, Notifications (nothing "Not Allowed")
  • Settings:
    • Expert Mode: yes
    • Deactivate Background scan: no
    • Permanent scanning: no
    • Participate in study: yes
    • Use Location: yes
    • Low Power Scan Mode: yes
    • Detection Sensitivity: Medium
    • Filter out device types: none
    • High Priority Notifications: yes

Crash Frequency

(today)

  • 19:44:34
  • 19:29:33
  • 19:14:33
  • 18:59:33
  • 18:44:33
  • ... (over 170 since yesterday, all ANR)

Example error:

ANR in de.seemoo.at_tracking_detection
PID: 17551
Reason: Broadcast of Intent { act=AlarmManagerWakeUp_Perform_BackgroundScan flg=0x14 cmp=de.seemoo.at_tracking_detection/.worker.ScheduleWorkersReceiver (has extras) }
ErrorId: f96d0051-c050-42a5-89cf-0e869a550296
Frozen: s[false] g[false]
Load: 0.0 / 0.0 / 0.0
------ Current CPU Core Info ------
- offline :
- online : 0-7
- AP Temp = 261
                             0           1           2           3           4           5           6           7
------------------------------------------------------------------------------------------------------------------
scaling_cur_freq        533000      533000      533000      533000      533000      533000      864000      864000
scaling_governor  energy_awareenergy_awareenergy_awareenergy_awareenergy_awareenergy_awareenergy_awareenergy_aware
scaling_max_freq       2002000     2002000     2002000     2002000     2002000     2002000     1728000     1728000
------------------------------------------------------------------------------------------------------------------
----- Output from /proc/pressure/memory -----
some avg10=0.00 avg60=0.14 avg300=0.13 total=2835326627
full avg10=0.00 avg60=0.10 avg300=0.09 total=2380044824
----- End output from /proc/pressure/memory -----
----- Output from /proc/pressure/cpu -----
some avg10=11.87 avg60=11.81 avg300=11.90 total=182260383118
full avg10=0.00 avg60=0.00 avg300=0.00 total=0
----- End output from /proc/pressure/cpu -----
----- Output from /proc/pressure/io -----
some avg10=0.00 avg60=0.01 avg300=0.01 total=2541450827
full avg10=0.00 avg60=0.00 avg300=0.00 total=1509254145
----- End output from /proc/pressure/io -----
CPU usage from 29936ms to -1ms ago (2025-09-16 19:44:02.983 to 2025-09-16 19:44:32.920):
  49% 26031/com.android.bluetooth: 29% user + 20% kernel / faults: 6 minor
  41% 15181/com.unicornsonlsd.finamp: 23% user + 18% kernel / faults: 1677 minor 28 major
  23% 1039/android.hardware.audio.service: 6.1% user + 17% kernel / faults: 1 minor
  19% 19380/media.swcodec: 12% user + 7% kernel / faults: 1547 minor 29 major
  14% 1078/audioserver: 11% user + 3.3% kernel
  9% 30183/InfinityLoop1309.NewPipeEnhanced: 4.8% user + 4.1% kernel / faults: 142 minor
  8.6% 1040/android.hardware.bluetooth@1.1-service: 1.7% user + 6.9% kernel / faults: 2 minor
  7% 1093/surfaceflinger: 2.9% user + 4.1% kernel
  6.4% 13609/com.f0x1d.logfox: 3.3% user + 3.1% kernel / faults: 3469 minor
  3.6% 1283/system_server: 1.5% user + 2.1% kernel / faults: 935 minor 12 major
25% TOTAL: 12% user + 10% kernel + 2.6% irq + 0.3% softirq
CPU usage from 2069145064ms to 2069145064ms ago (1970-01-01 01:00:00.000 to 1970-01-01 01:00:00.000) with 0% awake:
0% TOTAL: 0% user + 0% kernel
Killing 17551:de.seemoo.at_tracking_detection/u0a314 (adj 905): bg anr
Completed ANR of de.seemoo.at_tracking_detection in 1260ms, latency 3ms
Originally created by @ghost on GitHub (Sep 16, 2025). Original GitHub issue: https://github.com/seemoo-lab/AirGuard/issues/211 I have [LogFox](https://github.com/F0x1d/LogFox) running in the background and it tells me constantly that AirGuard crashed. OS: Android v15, OneUI v7.0, Kernel 5.15.153, SE=enforcing, Knox v3.11, patch level: 2025-07-01 Hardware: [Samsung Galaxy A16 5G](https://en.wikipedia.org/wiki/Samsung_Galaxy_A16) (EU) AirGuard: * Version: 2.6.0 (f-droid) (2025-09-13) * Battery: Unrestricted * Permissions: Location, Nearby devices, Notifications (nothing "Not Allowed") * Settings: * Expert Mode: yes * Deactivate Background scan: no * Permanent scanning: no * Participate in study: yes * Use Location: yes * Low Power Scan Mode: yes * Detection Sensitivity: Medium * Filter out device types: none * High Priority Notifications: yes ### Crash Frequency (today) * 19:44:34 * 19:29:33 * 19:14:33 * 18:59:33 * 18:44:33 * ... (over 170 since yesterday, all ANR) ### Example error: ``` ANR in de.seemoo.at_tracking_detection PID: 17551 Reason: Broadcast of Intent { act=AlarmManagerWakeUp_Perform_BackgroundScan flg=0x14 cmp=de.seemoo.at_tracking_detection/.worker.ScheduleWorkersReceiver (has extras) } ErrorId: f96d0051-c050-42a5-89cf-0e869a550296 Frozen: s[false] g[false] Load: 0.0 / 0.0 / 0.0 ------ Current CPU Core Info ------ - offline : - online : 0-7 - AP Temp = 261 0 1 2 3 4 5 6 7 ------------------------------------------------------------------------------------------------------------------ scaling_cur_freq 533000 533000 533000 533000 533000 533000 864000 864000 scaling_governor energy_awareenergy_awareenergy_awareenergy_awareenergy_awareenergy_awareenergy_awareenergy_aware scaling_max_freq 2002000 2002000 2002000 2002000 2002000 2002000 1728000 1728000 ------------------------------------------------------------------------------------------------------------------ ----- Output from /proc/pressure/memory ----- some avg10=0.00 avg60=0.14 avg300=0.13 total=2835326627 full avg10=0.00 avg60=0.10 avg300=0.09 total=2380044824 ----- End output from /proc/pressure/memory ----- ----- Output from /proc/pressure/cpu ----- some avg10=11.87 avg60=11.81 avg300=11.90 total=182260383118 full avg10=0.00 avg60=0.00 avg300=0.00 total=0 ----- End output from /proc/pressure/cpu ----- ----- Output from /proc/pressure/io ----- some avg10=0.00 avg60=0.01 avg300=0.01 total=2541450827 full avg10=0.00 avg60=0.00 avg300=0.00 total=1509254145 ----- End output from /proc/pressure/io ----- CPU usage from 29936ms to -1ms ago (2025-09-16 19:44:02.983 to 2025-09-16 19:44:32.920): 49% 26031/com.android.bluetooth: 29% user + 20% kernel / faults: 6 minor 41% 15181/com.unicornsonlsd.finamp: 23% user + 18% kernel / faults: 1677 minor 28 major 23% 1039/android.hardware.audio.service: 6.1% user + 17% kernel / faults: 1 minor 19% 19380/media.swcodec: 12% user + 7% kernel / faults: 1547 minor 29 major 14% 1078/audioserver: 11% user + 3.3% kernel 9% 30183/InfinityLoop1309.NewPipeEnhanced: 4.8% user + 4.1% kernel / faults: 142 minor 8.6% 1040/android.hardware.bluetooth@1.1-service: 1.7% user + 6.9% kernel / faults: 2 minor 7% 1093/surfaceflinger: 2.9% user + 4.1% kernel 6.4% 13609/com.f0x1d.logfox: 3.3% user + 3.1% kernel / faults: 3469 minor 3.6% 1283/system_server: 1.5% user + 2.1% kernel / faults: 935 minor 12 major 25% TOTAL: 12% user + 10% kernel + 2.6% irq + 0.3% softirq CPU usage from 2069145064ms to 2069145064ms ago (1970-01-01 01:00:00.000 to 1970-01-01 01:00:00.000) with 0% awake: 0% TOTAL: 0% user + 0% kernel Killing 17551:de.seemoo.at_tracking_detection/u0a314 (adj 905): bg anr Completed ANR of de.seemoo.at_tracking_detection in 1260ms, latency 3ms ```
kerem 2026-02-26 21:32:13 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-02-26 21:32:14 +03:00
Author
Owner
Copy link

@jay commented on GitHub (Sep 29, 2025):

I have been seeing AirGuard background "not responding" popups sporadically since I upgraded to Android 15. Some days it doesn't happen at all and some days it happens like 20 times.

<!-- gh-comment-id:3347317023 --> @jay commented on GitHub (Sep 29, 2025): I have been seeing AirGuard background "not responding" popups sporadically since I upgraded to Android 15. Some days it doesn't happen at all and some days it happens like 20 times.
kerem commented 2026-02-26 21:32:14 +03:00
Author
Owner
Copy link

@imbissbudenaesthetik commented on GitHub (Sep 30, 2025):

Hello,

thank you for reporting this. There have been some issues regarding ANR in version 2.5.0 on Android 15 which should be fixed now.

@Jan9103 Could you please try this again with the new 2.6.1 release? If the ANR should still persist after the update, please try to activate and then deactivate the permanent scanner toggle and then restart the app?

It would be very helpful to diagnose the issue. We do not have a Galaxy A16 in our array of devices on which we test.

<!-- gh-comment-id:3351045338 --> @imbissbudenaesthetik commented on GitHub (Sep 30, 2025): Hello, thank you for reporting this. There have been some issues regarding ANR in version 2.5.0 on Android 15 which should be fixed now. @Jan9103 Could you please try this again with the new 2.6.1 release? If the ANR should still persist after the update, please try to activate and then deactivate the permanent scanner toggle and then restart the app? It would be very helpful to diagnose the issue. We do not have a Galaxy A16 in our array of devices on which we test.
kerem commented 2026-02-26 21:32:15 +03:00
Author
Owner
Copy link

@imbissbudenaesthetik commented on GitHub (Oct 8, 2025):

Hello again, we have uploaded a new release with ANR and crash fixes. Github and Google Play Store are available right now, F-Droid will probably take a few days. I will mark this issue as closed now, but if there is any further issues or if this issue should still persist, please contact us again. Thank you for your help.

<!-- gh-comment-id:3381244782 --> @imbissbudenaesthetik commented on GitHub (Oct 8, 2025): Hello again, we have uploaded a new release with ANR and crash fixes. Github and Google Play Store are available right now, F-Droid will probably take a few days. I will mark this issue as closed now, but if there is any further issues or if this issue should still persist, please contact us again. Thank you for your help.
kerem commented 2026-02-26 21:32:15 +03:00
Author
Owner
Copy link

@ghost commented on GitHub (Oct 8, 2025):

Ok - i am still waiting for f-droid (don't want to deal with signing keys).
Ill come back when it finally updates.

<!-- gh-comment-id:3381731413 --> @ghost commented on GitHub (Oct 8, 2025): Ok - i am still waiting for f-droid (don't want to deal with signing keys). Ill come back when it finally updates.
kerem commented 2026-02-26 21:32:15 +03:00
Author
Owner
Copy link

@ghost commented on GitHub (Nov 26, 2025):

Fdroid finally updated it 2025-11-13 and i haven't had any reported crashes since.

tho the fdroid update frequency feels very slow considering this is a security related app (which was broken for me).

<!-- gh-comment-id:3582190244 --> @ghost commented on GitHub (Nov 26, 2025): Fdroid finally updated it 2025-11-13 and i haven't had any reported crashes since. tho the fdroid update frequency feels very slow considering this is a security related app (which was broken for me).
kerem commented 2026-02-26 21:32:15 +03:00
Author
Owner
Copy link

@imbissbudenaesthetik commented on GitHub (Nov 26, 2025):

Hi,

F-Droid had issues with their build server (compatibility issues with dependencies, see the last 3 messages in #215 ). Apparently this has been fixed as of last week. We submitted a version with older dependencies which took some time to publish. This was outside of our control.

Thank You for your feedback regarding the crashes. This confirms our internal testing.

<!-- gh-comment-id:3582263490 --> @imbissbudenaesthetik commented on GitHub (Nov 26, 2025): Hi, F-Droid had issues with their build server (compatibility issues with dependencies, see the last 3 messages in #215 ). Apparently this has been fixed as of last week. We submitted a version with older dependencies which took some time to publish. This was outside of our control. Thank You for your feedback regarding the crashes. This confirms our internal testing.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
developmentNext
development
googlePlayRelease
dependabot/bundler/webrick-1.8.2
superTrackerProtection
PassiveLocationListener
serviceless
v2.0
3.0.2
3.0.1
2.7.1
2.7.0
2.6.2
2.6.1
2.6.0
2.4.1
2.4.0
2.3.1
2.3.0
2.1.1
2.1.0
2.0.1
2.0.0
1.4.0
1.3.4
1.3.2
1.2.0
1.1.1
1.1.0
1.0.6
1.0.5
1.0.4
1.0.3
1.0.2
1.0.1
v1.0.0
Labels
Clear labels   
bug

   
enhancement

   
good first issue

   
minor-bug

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
wontfix
No labels
bug
enhancement
good first issue
minor-bug
pull-request
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#131
No description provided.