@pparent i know its a longer shot, but for calling using signal (or any other app) you have had an active forground connection, so it could just not stop the permission when the active call is already in place (which you authorised during your online time).

So i dont think it needs background permission if the system in place recognises the difference between a call being made in background, or if it is going inside the background.
Even when you are being called, you will get an active screen where you want to decide if you accept the call or not.

for network access i dont think we can do without with all the missing services for a wide range of applications?

the only real issue is, how to prefend the wrong services to have access in background if you kinda authorised it.

@donieck i had it like a week ago, i dont think it is just "device based" they did something to distrobute the load on server capacity. not sure what though

@pparent other then that i totally agree, it might also be a good idea to add like only permission when you need it, why give whatsnew permission to access my microphone all the time? i could also just give it permission when i access a microphone requiered token? even if it is in the forground i barely need it to use my microphone at all.

so that could look like app development:
Forground permission,
Background permission, which i would only need during rare phone calls? and i suposse not even then since it will activate to the forground?

and user side:
once or trusted.