Holy shiznit.
For X10III Android 11, this just worked to instantly restore AppSupport start ability:
$ systemctl –-user stop apkd-bridge-hw
(Not sure where apk-bridged exists, maybe newer A13 AAS devices?)
Couple days ago, I ran # systemctl edit appsupport@defaultuser for [Service] Restart=no, so when it crashes, it wouldn’t kill my battery in a restart loop. (PS Sorely disappointed @jolla has left this AAS crash loop debacle [yet another] papercut linger this long.)
Seemingly innocent change, but now AAS would not start after a crash, not even from Settings panel Start button. No idea (yet) what the connection is.
But stopping apkd-bridge-hw instantly made everything work just now.
When did they discover this, how long have they been sitting on this info? 