mobos what is your threat model here? Being open source and from the GOS developers, I hardly think the camera app is one of your problems or that removing it would solve your problem with it. Maybe disabling camera access system-wide is what you need. For more critical threat models that include threat actors getting access to your OS, you'd need to tape or physically remove the camera modules.

If you simply prefer another camera app for taking photos, you might just ignore the system camera app, hide it from your custom launcher and restrict battery usage. But like @collector said, it's a system app that you don't want removed because it can cause issues.

    brn Any app relying on system capture intents is broken. It just sounds like you're using no app that uses that. It is definitely a broken setup, though.

        matchboxbananasynergy I don't doubt it, that's why I said YMMV! I don't use many apps, but popular ones like Signal and WhatsApp have the camera working without issues.

            a year later

            • pfr

              • Post #8
              • Edited

              Same here. It was possible to disable the Grahene camera in previous builds because I had disabled it. I recently saw that the camera app had been updated so I enabled it to see what marvelous updates awaited me, then found I could no longer disable it again. I use lawnchair launcher so I've just hidden the app, but I find odd that the GOS camera is required by other apps. And in many cases, other apps simply look for any app named "camera" so they will happily use the Pixel camera if installed. I generally don't give other apps camera access anyway. If I want to send a picture on Signal, I'll take a photo with my camera app and then just add it to a chat as an attachment.

                Sounds like "Hide app" options will solve all problems!

                brn Any app launching the media capture intents will fail to launch them and potentially crash.

                  brn These apps are requesting the camera and microphone permissions instead of allowing you to capture images and video without them. Apps using the media capture intents don't require those.

                    pfr There's nothing odd about it being required by other apps. That's how Android works. Apps are meant to use the media capture intents to use the system camera app to have the user capture images and videos for them instead of unnecessarily requesting invasive camera and microphone access while the app is in use.

                    And in many cases, other apps simply look for any app named "camera" so they will happily use the Pixel camera if installed.

                    No, this is completely wrong. The media capture intents can only be provided by system camera apps. Apps are not looking for camera apps to capture images and videos this way.

                    I generally don't give other apps camera access anyway. If I want to send a picture on Signal, I'll take a photo with my camera app and then just add it to a chat as an attachment.

                    The whole point of the media capture intents is not needing to give apps camera and microphone access. The whole point is that the app launches the system camera app on top of itself and you can take a picture or video with that if you want based on the app requesting it instead of granting it access. This is a very privacy friendly standard Android design that's used for the file picker, photo/video picker, contact picker and media capture intents (photo and video capture) among other things. It's not a good thing when apps require permissions instead of these things. We had to make our Contact Scopes and Storage Scopes features to work around apps not doing things in the privacy friendly way via intents. We plan to make similar features for Camera and Microphone but we'd barely need it if apps just used the media capture intents when possible.

                        • pfr

                          • Post #14
                          • Edited

                          GrapheneOS Thanks for the info!

                          I'm curious though, if the ability to disable the system camera was removed in recent updates? As I stated in my previous comment, I had the system camera disabled up until recently. In any case, I'm not bothered by it :)