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.

Installing ffmpeg with encoders and decoders: ffmpeg-rockchip-armhf.zip On rv1126 armbian device: cd /media/usb/esp32-rv1126-ffmpeg-rockchip ./install-on-target.sh Verify: /opt/ffmpeg-rockchip/bin/ffmpeg -hide_banner -encoders | grep -Ei 'rkmpp|mpp' /opt/ffmpeg-rockchip/bin/ffmpeg -hide_banner -filters | grep -Ei 'rkrga|rga'

maybe an entry in the file: /boot/armbianEnv.txt entry / edition: overlays=meson-sm1-jethome-jethub-j200-spi reboot If this doesn't work, you have to ask e.g. AI / Gemini if you are not a programmer... That's what he suggested to me, but will it work? ................... sudo apt update && sudo apt install -y device-tree-compiler nano bpi-spidev.dts Edit and add entry: ............... /dts-v1/; /plugin/; / { compatible = "amlogic,sm1"; fragment@0 { target = <&spifc>; __ some_status__ { status = "okay"; }; }; fragment@1 { target-path = "/soc/spi@14000"; __overlay__ { status = "okay"; #address-cells = <1>; #size-cells = <0>; spidev@0 { compatible = "rohm,dh2228fv"; reg = <0>; spi-max-frequency = <10000000>; status = "okay"; }; }; }; }; ................. save Ctrl+X ...enter compile: sudo dtc -@ -I dts -O dtb -o /boot/dtb/amlogic/overlay/meson-bpi-spidev.dtbo bpi-spidev.dts edit: sudo nano /boot/armbianEnv.txt entry: overlays=meson-bpi-spidev sudo reboot Check: ls /dev/spi* but these are just suggestions, I don't know if it will work for you?

I'm facing the same issue and haven't found a way to enable USB 3.0. There doesn't seem to be an overlay like the one in Radxa OS for enabling it. If anyone knows how to get USB 3.0 working, I'd really appreciate the help.

Now I have tried to bring my non-working Trixie setup as near as possible to my working Bookworm setup (both BananaPi Pro boards) (and: no bridging stuff here!): -I replaced systemd-networkd with NetworkManager on Trixie -I restricted NM to handling of end0 (wlan0 as "unmanaged"), set up everything "the old way" as it is working on Bookworm (manual hostapd, dnsmasq, iptables) And now I try to connect from my mobile phone to both APs: Bookworm is okay as always, Trixie says "connect w/o internet" (although the very first time before rebooting it connected w/ Internet). In the extended dnsmasq log I see in both cases lots of connection names, but anyway the Trixie AP claims to have "no internet". The only visible difference is the log output for hostapd (both v2.10): in the failing case the following lines are printed for every connection, whereas in the working case these are not there: 2026-07-14T19:15:41.505822+02:00 bananapipro hostapd: wlan0: STA 22:50:7b:ac:e3:2e IEEE 802.11: associated 2026-07-14T19:15:41.541156+02:00 bananapipro hostapd: wlan0: STA 22:50:7b:ac:e3:2e RADIUS: starting accounting session 0F32AA180BFF0C2C 2026-07-14T19:15:41.542161+02:00 bananapipro hostapd: wlan0: STA 22:50:7b:ac:e3:2e WPA: pairwise key handshake completed (RSN) ....(many lines of log output from dnsmasq) 2026-07-14T19:15:58.724493+02:00 bananapipro hostapd: wlan0: STA 22:50:7b:ac:e3:2e IEEE 802.11: disassociated I have no clue what activates this RADIUS stuff and why there is this associated / disassociated pair (or why it is not there in the Bookworm case).