ADB does not work. adbd UID is not the expected 1011, it's running as shell (UID 2000)

[CapitalF]

EDIT: I corrected some major confusion from my original post and clarified what I believe the actual case of the problem is.

AFWall+ v3.6.0. I am in Allow-Selected mode. I am an advanced long-time user with multiple devices running AFW+. The device is a new Pixel 8 running LineageOS 21/Android 14.

I was not able to use ADB over network, even though I had adb allow-listed in AFW+, so I began investigating.

Disabling AFWall+ immediately results in ADB over network working properly. tcpdump also shows packets coming in to port 5555 without any problem.

I found the the process ID for adbd is running as UID shell/2000 instead of the expected adb/1011. This is confirmed from a shell via the ps and netstat tools, and reviewing iptables-save output.

A simple workaround is to allow the special UID/app Shell access, but this obviously leads to confusion for users.

Maybe a simple pop-up is in order if someone selects an adb item. Something like: "Hey user, I know you just selected adb, but the adbd on modern Android runs as the shell user, so select that instead to allow ADB Over Network" or something.