In my organization, GrapheneOS would be welcomed but the lack of voice recording is a no-go for now:

  • some users do need it for legal purpose.
  • many use it to ease the process of taking notes and/or to write meeting summaries or verbatims (sometimes using voice recognition afterwards).
  • de0u replied to this.

    Carbon14 In my organization, GrapheneOS would be welcomed but the lack of voice recording is a no-go for now.

    Depending on the size of your organization, it might have an IT person who could do custom builds of GrapheneOS including BCR (or something else). The build directions are clear enough that even I was able to do it, despite never having written any Android code at all. Arguably the build directions could be improved by adding an explicit list of the steps necessary to re-badge the resulting OS (i.e., so it doesn't advertise itself as "GrapheneOS", uses a different boot logo, etc.). A "private label" OS for your organization could probably be deployed in a week or two (including an update server).

    At the other end of the timeline spectrum, contributing call recording to Google's AOSP project, if successful, would likely result in it showing up downstream in GrapheneOS. That could easily take more than a year -- again, if successful: Google might just not be interested in adding call recording to AOSP. I suspect they would not at all want to incorporate GPLv3 code such as BCR or any derived work (which would also be GPLv3).

    Please note that I don't in any way speak for the GrapheneOS project (and certainly not for Google!).

      aguttfx This would kill any potential implementation as it would violate states that have two-party consent laws to recording phone calls.

          BalooRJ GrapheneOS is not going to be responsible for how call recording is used, we're not going to artificially restrict or add tones indicating call recording. We will have a warning upon first use and in the call recording settings that will explicitly tell you that you're responsible for your usage of it. It's going to be extremely cumbersome to maintain and keep a list of allowed countries and bringing in a lawyer to help us determine these kinds of things is a waste of project funding.

              matchboxbananasynergy Wow! Fantastic guys! Thanks for this. A great gift.

              I'll be sending a donation.

              r3g_5z GrapheneOS is not going to be responsible for how call recording is used

              Exactly right. How I use a knife is on me not the knife maker. End of story.

                  BalooRJ

                  This would kill any potential implementation as it would violate states that have two-party consent laws to recording phone calls.

                  No, it would not!
                  It's not the responsibility of the OS to preemtively not offer APIs because an app could do something illegal with it in some jurisdictions. Some states allow it, some don't? Maybe I don't even live in the US?!
                  Let the app and the user worry about that, instead of forcing something against the owner's will.
                  Big 👎It actually shocked me that the Graphite account liked your post.

                  I am happy that there is some integration in the dialer now. Evidently it didn't kill implementations after all!

                  It would still be great to bring the old APIs back.

                      aguttfx

                      I 👍 the comment because I agree it could cause devs to kill any implementation if they're worried about litigation. Google killed the API for this reason. And the US is a litigious country.
                      You and I agree that it "should" be on the user. But state laws are finicky, anyone can sue anyone for anything. I'm sure they consulted lawyers before implementing this.

                        timyysoo There are others way to donate. Crypto. You can also buy a prepaid card and use that on GitHub.

                        IF there is a will, there is a way

                          aguttfx Technology and IP law is thorny. App devs do not want to get sued for developing an app whose main use could be for illegal purposes. Check out the MGM Studios, Inc. v. Grokster, Ltd., 545 U.S. 913 (2005) for a prime example of this.