Agreed, Android 13 was expected though given the SoC platform and launch timing.
I'm already on Bluesky, but I stopped posting there because it seemed dead in comparison to Mastodon and Threads.
...I already post on Mastodon though 😅
https://androiddev.social/@MishaalRahman
I'm also on Threads: https://www.threads.net/@Mishaal_Rahman
Yeah, this is the right approach. It's true that ASUS dropped the ball when it comes to getting their bootloader unlock tool server back online as well as in keeping users updated on their progress. It's also true that you should never really take what support staff says at face value, and that a response from a PR rep is always preferable over support staff.
However, there are times when even the PR reps aren't aware of an internal policy change, or they aren't allowed to communicate as such yet. I don't think that's the case here, though. The PR rep I'm in touch with is the same one who has been running the Zenfone developer program for years, so I trust them!
Most OEMs aren't willing to preload Google's AVB keys for their GSIs. DSU is only really supposed to be used by app developers (and even then most app devs don't know it even exists or use it) which is why most OEMs don't bother with it.
I don't see why not, so long as you install an app on the watch that's capable of playing those audiobook files!