Please I dont need flagship mobile CPU specs. Something reasonably priced with a decent OLED screen and decent speakers is enough for me. I dont game on the phone anymore (I got Steam Deck for that). I still consume content in my phone.
I also dont need a fancy back camera (I have a dedicated mirrorless camera now lol) but I will need at least decent selfie camera for video calls.
A 3.5mm jack would be nice to completely remove the need for bluetooth (at least for my use case - I know some people will want bluetooth).
Hardware switches for toggling wireless, Bluetooth, and WiFi is a more reasonable ask from a privacy respecting device. Also, choice of atleast two - reasonably priced and specâd smartphone and one flagship for power users.
From a product POV, those are going to be better ways to go about it if at all they want to properly differentiate between a Graphene hardware and the hoi polloi of enshittified tech. Iâm afraid 3.5mm is gone the way of the Dodo my friend (on smartphones atleast).
I want those too but IP rating will significantly suffer the more âaccessibleâ it.
I agree with you but the question is, will it be the low end phone with the toggleable switch (and maybe 3.5mm jack) or will it be the flagship one?
I dont mind having a cheap-ass phone with no official IPxx rating for as long as it has the toggle switches (might as well add a replaceable battery for that). For the flagship one, maybe it should be the one with glue seal for the proper IPxx rating because of course you donât want the expensive phone to die from water immersion.
That is the ideal setting but realistically, I think Graphene will roll out only one model, at least for now. It will probably be an entry level one because making a high end phone with an âunproven track recordâ is sort of a risk that companies are averse to.
The question right now is that are sealed/glued units cheaper to produce or the ones with accessible internals.
Didnât see it mentioned here, but they said a release with GrapheneOS support in 2026 (not guaranteed) or 2027. My guess is 2027.
This is also pretty old news â they have been working with this partner since June 2025, which is how they have been able to get the patches early for the security preview releases and might also use the partner to make the Android 16 QPR1 release if they are allowed to before Google eventually pushes Android 16 QPR1.
The devices from the OEM partner will be priced similarly to Pixels. They are still not sure if the Snapdragon flagship will meet the requirements or be secure enough to support.
Actually, I think itâs because the new flagship Qualcomm processor (the supposed Snapdragon 8 Elite Gen 5) is expected to implement Memory Tagging Extension (MTE), a feature previously only supported by the SoCs in Pixel and iPhone devices.
That is one of the reason but also because âAt least 5 years of updates from launch for device support code with phones (Pixels now have 7) and 7 years with tabletsâ is a requirement to be supported.
Itâs more that since it seems like we already know what the basic specs and price (pixel range) will be, there just isnât that much to be excited about. I hadnât considered form factor and things like headphone jack and microsd though. So I can see why thats exciting.
Yeah I think GOS is making the right calls right now and do the best thing they can do. But itâs still a âtrust me broâ. Doesnât really matter if it is a valid reason or not. Youâre still adding a new layer of trust.
Iâm also skeptical of the of GOS+OEM phone because if GrapheneOS becoming a OEM/Getting a small time OEM because youâre making it alot easier for governments and 3 letters to make a focus attack on GOS. Unless the OEM make fully open-source phone I wouldnât trust it and I will still use pixels as long as I can. There are to many new layer of trust with a GOS+OEM phone to my liking.
A hidden perk of pixels phones, it is a lot harder to do a supply-chain attacks or a focus attack on GOS because you need to attack millions of phones just to hit the 1% of GOS users. We can say alot of bad things about Google but attacking one of the most secure companyâs with a supply-chain attack is more unlikely then other OEMâs. And Google is probably one of the few companyâs that are powerful enough to fight governments if they wanted to.
Ah yes do a uncle Teddy. Lucky for me Iâm not that paranoid nor need that level of privacy.
I was mainly thinking of countrys like Spain would like to have a way to attack the OEM with laws. And spyware companyâs in Israel would like to have a way to crack GOS and hardware would probably the easiest way to do it.
If those are what youâre thinking about, it leads me to believe you have that high a threat model. And if so, give up smartphone and only use Tails OS or Whonix or whatever youâre comfortable with on the desktop.
I donât know what else to tell you but thatâs what comes to mind. If GOS is not going to be enough for you, now sure what other computer will be either though.
My understanding is that the new OEM will not deliver a phone with GrapheneOS, they will just meet all the hardware requirements that GOS has and make it possible to manually install it (i.e. unlockable bootloader). So itâs going to be the same as with Pixels: you have to buy the device with stock Android and then install GOS yourself, and the majority of the buyers of this phone will stay on stock Android.
Lucky for me Iâm not that paranoid nor need that level of privacy. 