Samsung devices have basically everything except hardware memory tagging, afair (which is allegedly being added now?), and it looks like it's possible to both OEM unlock and relock the bootloader?
> We have talks with a large Android OEM ongoing and they're doing initial work towards supporting GrapheneOS. We hope there will be another device we can support in 2026 or 2027 based on this. Qualcomm releasing MTE support this year is key and appears to be happening.
> The initial devices built for us by an OEM are going to be their regular devices improved to meet our security and support time requirements. We aren't going to have much influence over the initial hardware. If GrapheneOS on these devices is highly successful, then we can make the business case that it makes sense to have custom hardware and firmware beyond meeting our minimum requirements. Our minimum requirements cannot require more than what we have on current devices.
A.K.A: the minimum requirements are current requirements (currenly only met by Pixels)
You can't OEM unlock Snapdragons/North American models.
I just have a hard time believing that Samsung is working to improve GrapheneOS compatability with their devices when they don't even allow you to unlock the bootloader in certain regions, and they're chasing a very Apple-like ecosystem approach where many device features require you to go all in on Samsung products (ex. their earbuds and watches are both hamstrung if you don't use them with a Samsung phone).
Verizon pixels also can't be OEM unlocked. That doesn't make them unsuitable for GOS.
(I've seen both watch an buds used with Motorola phones just fine, not sure what are the issues? Genuinely curious, one of the users is eyeing phone upgrade, I might steer them the galaxy way if that improves their experience)
(oh, and I know their trackers work really good only with Samsung phones, but that's the consequences of Samsung making good choices and Google making bad choices)
> Verizon pixels also can't be OEM unlocked. That doesn't make them unsuitable for GOS
Everything I'm seeing says that Verizon Pixels can't install Graphene, since Verizon doesn't let you unlock the bootloader. [1]
Galaxy Buds come with 3 Bluetooth codecs: SBC, AAC, and Samsung's proprietary codec. SBC and AAC are low-quality, low bandwidth codecs. Samsung's proprietary codec supports high bit rates, but only Samsung phones support their codec.
Competing non-Samsung & non-Apple earbuds will typically also support other codecs, like aptx-HD, aptx-Adaptive, and LDAC. These are all high-quality codecs, that are supported on every new Android phone except for Samsungs.
The Galaxy Watch situation has improved. I think all that's currently missing is a couple of health features like the ECG when not using a Samsung phone. Last time I checked, there was a modded apk out there that you could install to get the full functionality.
tl;dr galaxy buds will have subpar audio quality when connected to a non-Samsung phone, galaxy watch requires sideloaded apk for certain health features.
Thank you so much for your responses, this is extremely useful (especially the ECG part since my olderly relative is considering getting the latest Galaxy Watch for ECG)
And with your first paragraph, 100% correct. Verizon Pixels cannot be oem unlocked which means they cannot have the bootloader unlocked, which means GOS cannot be installed.
I think there's a typo in my response which you rightly corrected.
The claim I was responding to:
> You can't OEM unlock Snapdragons/North American models
The response was supposed to mean that you can unlock North American Pixels, except for these from Verizon.
