leafnose With the GOS Camera, there are too many what seem to be noise reduction artifacts for my taste.

I often see a purplish, static-like effect on the corners of my pictures when I reduce the aperture on the GrapheneOS Camera. Is that it?

I also hope CameraX extensions advance enough to add support for adjusting focus manually like with Google Camera. Hope it happens sooner than later.

    yore the photos get saved to the same place as usual. Turning on storage scopes just makes the app think it can access all of storage, but it storage will appear to be empty except for files the app itself created. Even without storage scopes, Google Camera can still save files to the DCIM/Camera folder.

    The way android does storage stuff is a little different. You can read through storage access section of the website to see how all that works.

      When an app asks for access to storage, whether it's all files access or just certain media types, I always just enable storage scopes for that app so it stops asking for access.

      The only times I can think of where I add a file or folder to storage scopes for an app to access are:

      • I need to send a file using a messenger app and the app doesn't support using the system file picker
      • Editing specific photos (I either add the photo file or move the photo to a folder that's added in storage scopes)
      • For gallery apps, I add regular media folders, like the Pictures, Movies, and DCIM folders.

        other8026 I wouldn't add the DCIM folder

        Also

        other8026 For gallery apps, I add regular media folders, like the Pictures, Movies, and DCIM folders.

        Cool Schrödinger's cat.

          23Sha-ger he said he would only add DCIM access for gallery apps, not to pixel camera or anything else. Not sure what that has to do with Schrödinger's cat? O.o

          other8026 Thanks for explaining!

          other8026 Even without storage scopes, Google Camera can still save files to the DCIM/Camera folder.

          So if I understand this correctly, it won't matter whether or not I enable Storage Scopes as the media will save to the DCIM/Camera folder regardless?

          And if I reinstall Google Camera, would I need to grant Storage Scopes and select the folder for the app to see the previous media? Would that mean permitting access to the DCIM/Camera folder?

            yore

            I often see a purplish, static-like effect on the corners of my pictures when I reduce the aperture on the GrapheneOS Camera. Is that it?

            That would be something else.
            Do you mean directly reducing the aperture? How do you do that?

            yore
            To answer your first question: my experience is that you have to enable Storage Scopes, otherwise you’ll always see the prompt asking you to choose the permission and you won’t be able to use the camera app.

            • yore replied to this.

              yore So if I understand this correctly, it won't matter whether or not I enable Storage Scopes as the media will save to the DCIM/Camera folder regardless?

              Yes.

              And if I reinstall Google Camera, would I need to grant Storage Scopes and select the folder for the app to see the previous media? Would that mean permitting access to the DCIM/Camera folder?

              Correct, see this from the Storage Scopes section:

              The most significant limitation of Storage Scopes is the fact that the app will lose access to files that it created if it's uninstalled and then installed again, same as any other app that doesn't have a storage access permission. As a workaround, users can manually grant access to these files/directories via SAF picker.

              Can Google Camera change its save location? If yes, you could also consider making a "Google Photos" folder, setting it as the location for images taken, and then adding the folder in Storage Scopes for the Google Camera.

                Dumdum Correct, see this from the Storage Scopes section:

                Would that open up the possibility of Play Services seeing my media?

                Dumdum
                The media won’t save to the DCIM folder because the Camera app won’t be useable.
                For Google Camera to work, the Photos and videos permission has to have something selected, the most conservative choice being Don’t allow (+ Storage Scopes).

                leafnose That would be something else.

                I don't follow what you mean by noise?

                leafnose Do you mean directly reducing the aperture? How do you do that?

                Before capturing the picture, reducing the brightness slider.

                  GCam doesnt need any additional play services on GrapheneOS

                  • yore replied to this.

                    missing-root I know. But I sometimes enable Play Services for other apps that need it. And from this thread, it seems like Play Services can communicate with Google Camera even if Google Camera is disabled.

                      yore

                      Before capturing the picture, reducing the brightness slider.

                      That’s what I thought.

                      I don’t follow what you mean by noise?

                      https://en.wikipedia.org/wiki/Image_noise

                      yore
                      No, if an app is disabled, it won’t be able to communicate through IPC with another one.

                      Do you refer to this message of mine? leafnose Second point?
                      I only said that if you gave Google Play Services the explicit access to the save folder of Google Camera, it would have the permission to ‘see your photos’. It’s hypothetical, but that would be allowed with this kind of permission.

                      • yore replied to this.