X10II 18.104.22.168 (III is still sitting on shelf, waiting for 4.5)
Wow, so this was all along why my phone has been intermittently struggling to play A2DP audio on car head unit.
Fairly certain I’ve been struggling with this over a year now, ever since I swapped head units in my car (order date reads Oct '21), and got BT A2DP capability to it.
Fresh off Sailfish reboot, BT would connect and play A2DP music fine on Spotify.
It always felt like with all the OOMs Sailfish app suffers through a session, somehow phone’s Bluetooth capability deteriorated, but I could never figure out the details. Next ride, BT connects fine, but head unit audio player fails to play audio or display track info, and no on-screen controls work.
Turns out I was always looking in the wrong place, trying to
journalctl through bluetooth unit.
systemctl --user status mpris-proxy had crashed with SIGABRT, just like [4.4.0] mpris-proxy service crashing and not restarting - #6 by direc85 shows.
systemctl --user restart mpris-proxy immediately restored all functionality (I also edited service unit for auto-restart), and ended this year-long frustration that made me want to test other head units and go through all that rebuild trouble.
Got a couple of long drives coming up, couldn’t be happier about getting ths figured out. You the man @direc85.
PS phone doesn’t seem to have
coredumpctl so we can’t really get details on why mpris-proxy crashes?
PPS History for tools/mpris-proxy.c - bluez/bluez · GitHub for History, hopefully it becomes hardened upstream.