Perhaps here: https://issues.chromium.org/issues?q=status:open as xtradeb ppa is packaking service only. I don't think they do anything else that that.

I've seen this same issue with Discord, since March/April this year. Just going to https://discord.com/app (no login necessary) is enough to trigger it. From what I gather, this seems to be some sort of problem with the Chromium build Armbian uses (it appears to be the same build from the xtradeb ppa). This seems to happen on: 1. Raspberry Pi 4 on Armbian Ubuntu Noble 2. Some random Ubuntu VM ARM64 on Apple Silicon using Chromium from xtradeb/apps PPA 3. Dragon Q6A w/ Armbian Ubuntu Noble No workarounds seem to work. Turning off GPU acceleration, disabling sandboxing, etc. all make no difference. But it does not occur on: 1. Google Chrome 2. Chromium 145 or earlier ARM64 from Armbian or Xtradeb PPA, on all devices. Only 146 or later is affected for some reason 3. Linux Mint's Chromium x64 build 4. x64 Chromium snap package on Ubuntu I have not tested xtradeb PPA (or Armbian)'s x64 build of Chromium. Based on the above, I do not think this is an Armbian specific issue. Anyone have any ideas on where to report this?

Where can I find the image?

Update: the ready-to-flash Debian 13 + KDE Plasma image is now available: https://github.com/ut-slayer/orangepi-4a-mainline/releases/tag/v0.1 Boots straight to an accelerated Plasma desktop. Feedback welcome!

So you try routed AP instead of bridged. Trixie might handle 'iptables' in a different way, depends also what alternatives you have for that and/or if it is netfilter underneath. This kind of manual setup (routed, hostapd) I did before Bookworm only a few times, rest is always bridged and basically using only NM. It seems to me that something on IP layer is not accepted by your phone, so it disconnects. You need to dig more and deeper and also still take in to account what is said about that brcmf_psm_watchdog_notify issue. But it seems yest another issues.