On my Google Pixel 3a, I can download AOSP to my own computer, modify it how I wish, scrape the vendor dependencies I need[1], compile it myself, sign it myself, and use my own key to control what OS gets installed, then relock the bootloader so it only trusts updates using my key! I can choose not to use Google Play and then install whatever App I want on it.
I wish I could not have to use any proprietaryy binaries, but this is as close to an open device that you can get today [2].
[1] This is where the quasi defense comes in. AOSP has no official process to install all of the vendor binaries needed to support carriers. If you don't include this process you get broken SMS, Calling, WiFi Calling. This script helps you do it: https://github.com/GrapheneOS/android-prepare-vendor
[2] Yes I know of the Librem 5. I am a day one backer and have yet to get a shipping notification despite shipping starting in Sept. I also know of the Pinephone, it is not publically available. I await the day those types of products are viable.
Moving forward, my biggest purchasing decision as a consumer is going to be based on how much ties a company has to The CCP. I feel like my freedom is under direct threat from The CCP more than anything else, and I'll treat it accordingly when making purchasing decisions moving forward.
It tried to and would have gotten away with it too, if it weren't for you meddling kids.
Did you not read the memo?
As you have noticed, neither one really have consumer and citizen interests at heart.
I'm planning on taking the step of opting out completely. I plan to build my own "phone". I recently purchased a low-cost Mini-PCIe 4G module, antennas, and a USB adapter. I should be able to tether it to a RasPi.
My "phone" won't actually look like a phone; it's going to be more of a "data terminal" - something to hack on, send/receive data, and have SMS texting capabilities. I pretty much never use voice calling anyway.
Everything I plan on doing, others have already done in various forms. You can find Raspberry Pi based homebrew "cell phones". People have also made similar phones using the Arduino and the ESP microcontrollers (8266, 12, 32, etc), among others (there are probably PIC and Propellor based phones, too - heck, I wouldn't be surprised if someone repurposed a modern 8051 or 52, or Z80 core controller for such a device). Some of these phones are purely basic - make and take calls, maybe some stored phone numbers. Other run entire operating systems under-the-hood.
I guess what I am saying here is that if you have electronics hacking skills, consider a homebrew phone an option. It may not be pretty, it may not be svelte, it may not even be 4G (2 and 3G modules are cheaper and more common) - but it will be (mostly - unless you have your own mad skills at FPGA design and more) yours.
Bonus points if you make it run on TempleOS!
If you don't have those skills? Well - it wouldn't be a bad project to work towards. Don't take it on as your "first project" though - instead, build up to it, then when you think you have enough experience to take it on, go thru your idea, break it down into manageable parts, and work on those individually for small successes, and later, start merging them together - just like any large project, success is more a matter of "divide and conquer", as looking at it as a whole can lead to feeling inadequate, or being demoralized at finishing, etc...
I'd like to do that, honestly, but I need navigation or I'm completely helpless in the city.
https://www.youtube.com/watch?v=wqWVH38jtQo
Apple is responding to a threat from China, whereas Google is actively assisting the Chinese. Just thought you'd like to know that.