I'm thinking of getting a Pixel 7, and I was just wondering about the disadvantages of GrapheneOS.

I am aware that if you want to get the same camera experience as the stock OS, you need to download the Google Camera app.

Are there any special features that are not available on Graphene? Maybe some buttons work differently? What about always-on display? Double-tap the back of the phone to screenshot? Lock-screen auto detecting songs in the environment?

Any other small stuff like that.

Thanks in advance.

    GrapheneOS has differences to the Stock Pixel OS, yes.

    A lot of the same Google services can be used if you use Sandboxed Google Play, but things like "Now Playing" won't work for example, as it requires the app to be embedded into the system with privileged access.

    Another example is Google assistant, whch works, but the "Hey Google" functionality won't, because calling the assistant in that manner requires it to be integrated into the system with privileged access etc.

      matchboxbananasynergy Thank you for your answer. I am planning on having Google Play services and Google Camera installed, so that I'm missing as few things from the stock experience as possible.

      If I have that stuff installed, is there any major feature that I would be missing that comes to mind?

        abcZ This doesn't provide everything needed. It provides the bare minimum functionality to get Google Camera working, but it doesn't allow the servers to download extra features for the camera and Google photos.

        It also means that by using this, you can't install Sandboxed Google Play anywhere else on the device, even other profiles.

        For someone who is asking about Stock OS features and that wants to replicate as much of the Stock OS functionality as possible, this is the wrong recommendation.

        Keep in mind that if you don't want to use Sandboxed Google Play (Play Services/Store), you can also just use Google Services Framework with Google Camera without barring yourself from installing Sandboxed Google Play in other profiles:

        https://grapheneos.org/usage#google-camera

        When making recommendations like that, please caveat them appropriately, because that's how people install things like Gcam Services Provider and then are confused about why they can't install Sandboxed Google Play.

          matchboxbananasynergy
          That's elaborating on what I said. I said GCAM doesn't require .... etc.

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

            stefan10022 Google Pay does not work to my knowledge (correct me if I am wrong)

            It would be nice to have a non exhaustive list of all Stock OS features that do not work on GOS.

            Also has anyone tried turning on the 'Modify System settings' permission?

              5 days later

              An honest list of Pixel OS features that don't work would be a great resource, and transparency makes everyone happy.

              In addition to the ones listed above, I can think of...
              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

              It's getting late and that's all I can think of for now

              *and any app-based script execution. May also affect things like Termux and Tasker, although I don't use them enough to confirm
              **The app TapTap replicates this feature

                hemlockiv Most QS tiles don't work from lockscreen

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

                  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.

                    6 days later

                    Newbie here, we definitely need a list of exclusives that are working or non working. BTW, does text and image extraction from recent menu working?

                      The biggest one for me is android auto. I have a newer vehicle and really enjoy using my cars big entertainment screen for maps

                      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.

                        Raccoon I'm not sure what you want me to test out? For the record, Textbender does work pretty well.

                        I have Google Lens installed (and Assistant, actually) but I do not have any option to select text from the Recent Apps view. I have a feeling that was only possible when those Google apps had high-level system privileges, which Graphene makes a significant effort to undo, and for good reason.