Logging in Android 11 leads to app freeze

[secretServant]

Describe the bug In addition to logs in app being empty when enabled, logging in Android 11 leads to the app freezing, disable and re-enabling the app allows the user to boot back into the app to disable logging. Although, the user will be unable to filter/search through applications until storage and cache of Afwall is completely wiped. Something seems to be running amuck in the event logging is enabled on Android 11+.

Smartphone:

• Device: Motorola G
• Android OS: Android 11

Additional Context: This bug seems to be related to #1301

As others have reported dmesg | grep AFL shows blocks, but AFWall log shows "Log is empty." Additionally, iptables seem to still be applied, the frontend just become inoperable, or partially functional until the app data is completely wiped.

[Uj947nXmRqV2nRaWshKtHzTvckUUpD]

switching to nflog breaks it. log doesn't cause freeze but shows no logs

[angela-d]

Seeing crashing behavior on Android 13 / microG Lineage 20 on Oneplus 9.

It works for a bit and anywhere between 5 minutes to an hour it causes the phone to crash and reboot. Such behavior was not exhibited until logging was activated.

I have another device on Android 12 / microG Lineage 19 on a Oneplus 5 - for this device, logging does not crash until you try to look at a log entry; then AF Wall crashes.

Differences between the two, aside from the obvious:

• OP9 is running a VPN constantly: DNS66

[freebrowser1]

This is still pending on AFWall+ 3.5.3 (paid version). Disabling logging keeps AFWall+ from freezing / locking up, so it is a logging issue. Used device : Oneplus 6 + Stock rom 10.