Are you losing any features from stock os?

nid This one is a feature actually, although they could have made it toggleable.

OP asked what abilities they will be losing by switching from stock Pixel OS to Graphene. If a user capability is restricted, that is losing something. (Whether the QS restriction is a "feature" or not is simply opinion. I agree that it, like all other instances where user capabilities were restricted, should be toggleable. Add a big 'ol "Enabling this will create a security vulnerability!" warning if need be. Personally, I don't like when programmers take away user choice. If I wanted to baby-proof my phone, there are apps for that.)

For me the one feature that is not present on GOS that I really wish it can be included is call recording :(
Like yea Pattern unlock, voice assistant are cool features but I'm totally fine without them don't really care that much comparing to the benefits GOS provides.
But calling recording to me personally at least is quite important.
Have been dealing it for days trying to find a practical method that works without defeating the purpose of installing GOS in the first place.

hemlockiv Call Screen
Hold For Me
Shizuku*
Pattern unlock
Face-recognition unlock
Double-tap on back of phone**
Weather info on lock screen
Trusted Device unlock
Most QS tiles don't work from lockscreen
Select text via screenshot/Recent Apps view
Voice typing
Pixel Stand fast charging
Audio captioning

• Shizuku - Not an unavailable Pixel OS specific feature. It is ill advised to use ADB on a production device as it opens up massive attack surface that can be exploited. Doing so on GrapheneOS is antithetical to the projects stated aims. Any persistent state such as the package manager data files, persistent settings, permissions, special access grants, etc. is attack surface for verified boot and attestation. That includes non-user-facing settings including development permissions intended for use via ADB, etc https://nitter.net/GrapheneOS/status/1618069440280817664
  Termux and Tasker work fine within the scope.
• Pattern Unlock - provides a false sense of security. You should use a randomly generated 6 digit PIN so you have working encryption based on the secure element throttling. Pattern unlock doesn't have nearly enough choices at each step and encourages an even narrower set than that. Not an unavailable Pixel OS specific feature but a conscious decision by the development team within the scope of the project as an enhancement to security.
• Facial Recognition Unlock - This does work but ONLY on Pixel 4. Pixel 4 had dual infrared cameras + dot projector + flood illuminator which provided a more secure approach than a fingerprint scanner. Pixel 7 approach is far worse.
• Weather Info on Lockscreen - Could be worked around if an app with a persistent notification was used and enabled on the lockscreen.
• Most QS Tiles don't work on Lockscreen - Not an unavailable Pixel OS specific feature but a conscious decision by the development team within the scope of the project as an enhancement to security.
• Voice Typing - works so long as you're using GBoard and have Faster Voice Typing enabled for Offline dictation with Network Permission revoked after the language pack has downloaded (3 mins should be enough to download with network enabled and maybe language and IME dependent). Or you could also use an app like Sayboard.

hemlockiv OP asked what abilities they will be losing by switching from stock Pixel OS to Graphene.

Raccoon BTW, does text and image extraction from recent menu working?

No, it doesn't (or at least, I haven't found a way to make it work). That's what I meant by:

• Select text via screenshot/Recent Apps view

I think that functionality involves Google Lens and/or Assistant, so it would be pretty privacy-violating to let it extract text from any screen at any time. I'm currently trying out Textbender as a FOSS alternative; it uses an Accessibility overlay to let you select any on-screen text. Main limitation, I think, is that it has to be rendered text, not text that's OCR'd from an image.

We all have to distinguish and choose between what we “enjoy” and what we “need”.

For some, it is a struggle.

hemlockiv Have you ever gotten a 2FA code via SMS? Do you know how Android has a button in that SMS notification that allows you to copy the code to clipboard without opening the notification?

Yes, I use that to copy codes to clipboard for my accounts which use SMS 2FA. However, my workflow means that my phone is always unlocked when I need to copy the code.

I have the contents of sensitive notifications hidden altogether on the lock screen, so I am not able to see the code at all normally. I temporarily enabled showing all notification content, which shows the code, and I can confirm that to copy the code, I need to unlock the phone.

In my opinion, that seems like a sensible security feature. I am not aware whether this functionality changed recently, or not. I am not aware of GrapheneOS making any changes to the way that the clipboard works from upstream AOSP, at least not since Android 10.

abcZ True for privacy, but not necessarily for security. Yubikeys require play services.

abcZ If avoidable, its always better to have less of that google crap installed.