Genghis

You can always connect a USB stick or card reader with an SD card via USB-OTG

I will recommend you do use a phone that still receives security updates (Not EoL) because I don't want you to lose out on security just to deGoogle.

If you are strict on having an SD card slot and your phone is still receiving support, you should use StockOS to receive firmware updates as soon as possible. If the phone you decide to get is EoL, the least bad option would be DivestOS (fork of LineageOS)

Again, I would advise not using an EoL phone.

microG runs Google Play code just like Aurora Store. It is not fully open source. Here's more information.. It is still connecting to Googles propriety servers.

microG requires Signature Spoofing and alternative OSes usually ship with microG as a privileged system app. This increases the attack surface as it is not confined by the regular sandbox rules.

Now you're using a privileged component, which downloads and executes Google code in that privileged unprotected context, and which talks to Google servers because otherwise, how would FCM work for example?

Despite doing both of those things, MicroG doesn't have the same app compatibility as Sandboxed Google Play despite the extra access it has on your device. Even in some magical universe MicroG worked without talking to Google servers or running Google code (again, in a privileged context), the apps you're actually using it with (the apps depending on Google Play) have Google code in them.

I recommend you purchase a Google Pixel 6a or above (minimum security support ends July 2027) and flash GrapheneOS. (Pixel 8/pro preferred)

Aurora Store doesn't avoid Google since a lot of the apps from the play store include Google's SDK and libraries. microG also doesn't avoid Google as it is still running proprietary Google code and has more privacy/security weaknesses

Sandboxed Google Mobile Services is a much better implementation which is featured in GrapheneOS. The services are not privileged and is treated like any other app. They don't downgrade privacy or security unlike the other alternatives.

There are much more privacy and security benefits using GOS. Here is a 3rd party comparison between different mobile OS.

I would use Firefox on Android but I'm waiting until the security is on par with Chromium such as having internal sandboxing and site isolation.

Also since Firefox doesn't have a WebView implementation, it has to be used with the Chromium based one so it doesn't make sense for me to use two browser engines.

security theater

AOSP does get security updates first because GrapheneOS is based on unmodified AOSP. They are quick to port over updates though and they have extra features like hardened malloc and better user profile support.

Non pixel phones aren't secure because GrapheneOS doesn't support them. They aren't secure because they either don't have secure elements, broken verified boot, or don't properly support alternative operating systems. This makes phones like OnePlus, Fairphone, etc not secure enough for GrapheneOS.

DivestOS I would say is the least worst option when it comes to supporting EoL phones. They're at least honest about what they do and don't provide unlike what other OSes do. On their website, they tell you they aren't a secure OS and they can only try their best to reduce harm on an EoL device. DivestOS Security.

The only secure phone operating systems are either grapheneOS or stock. All the others usually are behind security updates.

For migration, I would just use a USB C drive and transfer files.

Please do not tell me you use Mull over Vanadium

Have you tried enabling the Exploit protection compatibility mode on the PF app setting info page?

Passkeys are replacing MFA and passwords.

Element for matrix is actually cheeks

I just use the AOSP messenger. If I used google play services, I would switch to Google messages because of RCS and it looks much nicer.