Seems you were on the right track @abcZ
in this issue the problem is also very well explained about SELinux and a special sepolicy which is missing.

One GrapheneDev answered with "Won't Fix" because it can be an attack vector for them ;( ;(
https://github.com/GrapheneOS/os-issue-tracker/issues/1841

They think Google will fix it but I would not bet on that (they don't have sepolicy problems on their firmware).
For me this is unfortunately a dealbreaker against GrapheneOS on my new Pixel 7 Pro (that device was too expensive to not use the camera AND THE DSP to its fullest)

    therealmarv Hmm, well unfortunately, "thestinger" is David Micay, who is in charge of GrapheneOS, therefore his position is absolutely authoritative.

    I don't believe that it is likely to be fixed by google, their history suggests virtually no chance that they'll fix it.

        therealmarv

        Totally agree with your point. GOS is an amazing OS but one of the strongest points of Pixel 7 is its camera. Not having a proper camera means we are loosing a lot.

        I already highlighted this above and will repeat that if its the case then it should be at least mentioned in official GOS FAQ that Google Camera will not work as expected. The FAQ currently says that Google Camera works fine but this is not the case for Pixel 7 devices and is misleading. Ultimately, someone will buy the phone thinking the camera will work as per FAQ and then will find out it doesn't and this will negatively affect GOS as people might try posting here and there on the web that there is a misleading promise the camera will work.

        I think its necessary to update the FAQ to include this important information so that prospective users will be aware. Obliviously, the choice is ultimately up to GOS team but its my 2 cents.

        abcZ

        Agree too - I don't believe Google will fix it as they have no reason to. It seems we are pretty much stuck with an inferior camera... which is really a big shame!

              Do you think it's possible that this can be solved by a gcam mod?

                snowdonia

                I am not an expert in this but don't believe so as gcam still requires that sepolicy to communicate with hardware properly.

                I've tried a few gcam mods, all are suffering from the same issue.

                Not sure what the risks are to allow the sepolicy in question or at least provide that option to users so that they could enable it if they want to (accepting the possible risk factor).

                I was doing a photo session yesterday and the camera was so slow, especially when taking multiple pictures. My old Notes 10 Ultra blows it out of the water which is a huge shame.

                  I also suffer from the same problem - really frustrating, as GrapheneoOS experience is really good otherwise...
                  As GrapheneoOS developers probably won't solve that issue, like we have read on the GitHub issue - is there a way we can give this issue priority at Google?

                    kruton

                    This is N1 issue for me on Graphene now.

                    I think contacting Google is a good idea but its probably should be done by someone who is far more knowledgeable as they could explain the exact issue to Google?

                      Damn, I noticed this issue some days ago and thought it's just an exception..

                      I always take portrait photos of people, as it looks incredibly good, especially on this phone. I don't mind waiting (Even though it's very awkward when you say "this phone takes good pictures, but we'll wait a minute for each"), but after like three photos, the camera app won't allow me to take another, and I'll have to wait until at least one is processed.

                      Waiting is one thing, but not being able to take another shot before it's processed is very very annoying.

                      I also noticed that Google photos generally has very slow processing, it feels way slower than my old P6P and even the P5. Maybe the new Tensor chip isn't used fully, even if that's the whole reason for Tensor to exist.

                        BTW, there is one manual workaround for faster processing: Snap a normal picture of the person, and then add portrait blur via google photos. It takes some steps, but that way you're much faster in making portrait shots.

                        Make sure to zoom in 1.3x to have the same frame, too.

                          May be isolated to the P7P. I have the Google Camera on my P7 and don't seem to have this issue.

                          18 days later

                          spl4tt
                          This is also the reason I find it annoying - I wouldn't mind waiting done time for it to finish processing, but having the camera "lock up" after (just tested) 4 portrait shots is frustrating.
                          Still looking for a way to help resolve this issue!

                            Not sure if it will help but maybe we can also post in Android's Issue Tracker thread so that Google support team will prioritize this?

                            Looking at the ticket in question: https://issuetracker.google.com/issues/227166806#comment8 Google assigned P4 priority to this issue and P4 is basically the lowest priority they have, described as "An issue that should be addressed eventually. Such an issue is not relevant to core organizational functions or the work of other teams, or else it relates only to the attractiveness or pleasantness of the system".

                            In other words, they don't seem to care about this as we can see they didn't do anything in the last 8 months.

                            Camera is the only thing I missed so dearly from Samsung.

                              spl4tt Snap a normal picture of the person, and then add portrait blur via google photos

                              Does google photos communicate in any way with google? Or is it only on-camera processing?

                                  Volen Looking at the ticket in question: https://issuetracker.google.com/issues/227166806#comment8 Google assigned P4 priority to this issue and P4 is basically the lowest priority they have, described as "An issue that should be addressed eventually. Such an issue is not relevant to core organizational functions or the work of other teams, or else it relates only to the attractiveness or pleasantness of the system".

                                  Thanks for looking this up and sharing it.

                                  I would go further than this: enabling full functionality of Google's Pixel hardware and related software so it can fully work in an OS that is used by people who do NOT want to interact with Google is NOT in their business interests. A P4 response should be entirely expected, not only on this issue but others.

                                  There can be and likely will be more impediments like this in the future. It is simply not in Google's business interest for GrapheneOS and the alternate, google-free ROMs which allow people to not be tracked by Google to grow.

                                  I contend that future progress in degoogling depends not only in the software area but equally in the legal area (e.g. privacy and anti-competition).

                                    16 days later
                                    11 days later

                                    Right now I'm just taking normal photos as a workaround and adding the bokeh effect afterwards in Google Photos....

                                    spl4tt Good call not trusting gphotos, since its primary purpose seems to be to steal your pictures and upload them to a google account.

                                      Volen I think its necessary to update the FAQ to include this important information so that prospective users will be aware.

                                      It seems as if this thread has enough supporting info that somebody could submit a pull request against the GOS web site repo.