It's okay, no issues with normal use. Not sure about gaming, since I never game anyway. The only issue is that pixel 6 is nearing eol for grapheneos. Still gonna use it after, but might be good to know.
I recommend getting a 6a or 7a instead, maybe even the 8a if you're ready to pay the higher price. But at least get the 6a, it's cheaper than the normal Pixel 6, and gets updates for 10 more months than the Pixel 6. The Pixel 6 has less than 2 years of life time left, I don't think it's a good option nowadays. You can always check on this site: https://pixel-pricing.netlify.app/ (it's in German, but you can either use the website translation in Firefox or on Google Translate)
GrapheneOS with a Pixel 6 Pro. It works perfectly for me. Most Google apps don't work, but that's only because I've chosen not to install their spyware "services".
I've jumped through a couple on my Redmi Note 10 Pro.
Needless to say, Xiaomi's recent hostility towards Bootloader unlocking has soured my desire to buy another
Yes, I have an old Xiaomi 11T I'm not sure what to do with, unfortunately the custom ROMs support seems subpar. Interesting to see that vast the majority of the people here use LineageOS.
Looks like that model has a MediaTek CPU, so that explains it: MediaTek doesn't release their sources so it's very hard top get a custom ROM working.
Snapdragon is the way to go (though it isn't a guarantee so always check if community support is good before buying)
LineageOS 20 on the Nokia 4.2. The only option for this phone besides LineageOS 19 and it's one of these cases where the dev just stopped updating anything and deleted their XDA profile. Might go back to vanilla but the problem is that's a downgrade in Android version too.
This whole phone is a regret. My previous phone had just died unexpectedly and it was a spur of the moment purchase with a low budget, based on nostalgia for a 'Nokia' that doesn't actually exist anymore. Should've just gone for a cheap Samsung and I probably would've at least had more choice in custom firmwares.
Calyxos pixel 4a 5g. Works pretty well phones old but does what I need of a phone, replaced the screen last year and actually down graded from my pixel 6a as I like how wide the 4a is.
GrapheneOS on a Pixel 9 Pro. It's nice to have better control over what data is leaving my device.
Updates / patches from upstream AOSP are usually offered in GOS in the same timeframe it takes to hit regular Pixels.
GrapheneOS on Pixel 7 I got used for $200. I've been running this for a year and its the most satisfying setup I've ever ran. I have multiple user profiles to segregate Google Play Services, banking apps, consumption apps, and a very restricted profile for my kid to use. I can't recommend it enough.
GrapheneOS on Pixel 9 Pro XL. it's a very refreshing experience having nearly no preinstalled apps, and having to install anything you want yourself, not the other way around. I don't need Play Services/FCM notifications either, I use Molly to talk with people, a fork of Signal that allows for UnifiedPush support, which I self host ntfy for.
LineageOS 22.1 (Android 15) on a OnePlus 5T. I'm a little surprised the latest released LineageOS supports this phone, but I'm glad I don't have to replace my phone yet. There are several apps I can't use on this phone, but I don't need any of them that much, so I'll keep using a custom ROM as long as I can.
It works on some devices; they do sign the builds as far as I can tell. But the bootloader itself needs to be convinceable to trust the LOS signatures, and needs to understand the secure boot implementation used in the Android that the current LOS is built from (since Android has re-done it all a few times). Nobody knows anything about bootloaders to figure out which of them can do this or how they would be induced to do it.
This is not true at all. We know plenty of things about Android boot loaders since they are all mostly the same. The thing about relocking is that you need a boot loader that will allow adding custom keys. The common wisdom is that this is only possible on Pixel.
However, I think that wisdom is wrong. The reason I say that is that Calyx OS supports boot loader relocking on devices such as the G52. I think Motorola devices in particular are good candidates since Motorola generally one of the better ones for boot loader unlocking. Locked Moto devices don't restrict the able to flash via fast boot but they do check signatures. If you could add a custom signature it would work.
Lineage OS is build in debug mode with no signing keys. I think the main reason for this is user freedom but I find it annoying. To do boot loader locking with Lineage OS you need to build from source with custom keys that are used for signing.