@neil I've been very careful with the port on my Pixel 9, as my Pixel 6 had similar "tired port" issues when I replaced it.
I've switched to wireless pads for most of the charging. I've found Warpinator (FOSS/GPL3) to be a far faster way to send files around than USB cables.
@neil After reviewing /e/OS earlier this year I was pretty much set on buying a Pixel when I needed a new phone, with the idea of putting /e/OS or Lineage on it. Not really feeling that now.
@neil You strike me as a Fairphone guy tbh. It also comes with /e/OS is you want: https://shop.fairphone.com/fairphone-5-e-operating-system
@batist3 @neil A few months ago Google essentially stopped developing AOSP in the open, and now throw code over the wall to the open repo on occassion, early access only provided to industry partners.
More recently they decided not to release the Pixel hardware specific changes alongside Android 16 pre-releases which they have always done. Meaning you can't build Android 16 for Pixels at the moment.
@batist3 @neil Coincidentally they are posting about it again: https://grapheneos.social/@GrapheneOS/114670995130379882
@neil See if your preferred device is supported by sailfish? (Either officially or via a community port). I've been using it since way back when Jolla launched their first phone and feel no reason to swap to android/ios.