DF218
Since you haven't used your old iPhone in weeks, you should be fine.
The actual problem is that Google stopped supporting their Pixels in AOSP. They're not AOSP reference devices anymore.
That means the GrapheneOS Devs have to take care of that Pixel Device specific code themselves now, which takes time away from developing GrapheneOS exclusive features.
According to the Devs future releases will be pushed out much faster, since there will be more automation in place by then.
The real question is: What cost cutting measures will Google take next? They will surely remove the ability to use a different OS with all security features intact, now that Pixels are not AOSP reference devices anymore.
Any current Pixel will most likely receive support without issues. But what about the upcoming Pixel 10, 11, 12?
When Qualcomm releases a new Gen of their Flagship SoCs with MTE support, the GrapheneOS Devs stated they could crowdfund a GrapheneOS branded device and get them built by a trustworthy OEM. If that happens and those devices are of good quality, who knows? Maybe everything will turn out just fine and barely anyone will end up missing Pixel Devices all that much. After all, Tensor SoCs are lagging years behind Apple or Qualcomm in terms of performance and battery life right now.
Another question to ask: Wouldn't working with an well established OEM and selling devices mean that GrapheneOS can get certified by Google and the Devs finally obtaining Partner Access?
- The lack of Google Pay support
- Play Integrity woes for users
- Unnecessarily stressful porting due to not having early access to AOSP Code, like all certified Android Partners do
Could finally be a thing of the past as well, one would think.