• Development

  • What features will be missing in GOS' Android 15 version?

I'd like to know if the following features can make it to GrapheneOS or are dependent on Google services:

  • Theft detection (and only the things described below, nothing more)

If Theft Detection Lock detects your device was taken from you, your device’s screen will lock automatically to prevent anyone from accessing your personal data. This feature uses your device’s motion sensors, and WiFi and smart device connections, to try to detect if someone abruptly takes your phone and runs away.
You must be actively using your device while it’s unlocked

  • Adaptive Vibration
  • automatically mute conversations after three is spam
    11 days later

    I assume the expanded satellite messaging is not available in GOS (since AFAIK the emergency messaging wasn't supported either)?

    Some providers, e.g. T-Mobile, now have a satellite messaging option under the SIM settings in the stock OS.

      MarSOnEarth I've not personally seen the option on any device. My friend has a P9P running stock on T-Mobile USA, but her device hasn't gotten the A15 update yet. I'm using T-Mobile on GOS, and I don't have the option, but I'm guessing that's because of GOS and/or my T-Mobile plan. My understanding is that not all plans have the option (at least, not right now).

        Hi, this is my first post.
        I'm not familiar with the feature policy on GrapheneOS and cound't find any concrete info about it.

        I read about the new feature 'Audio Sharing' in Android 15 which got me excited because Samsung had that for a long time as far as I know. But I can't find it in the settings.

        I'm on a Pixel 8. Can we expect some features to emerge later on in the process or what is the overall threshold what to expect from GOS feature-parity-wise?

        Thank you for all the work.

          sir_brickalot My wording came out wrong (language barrier): To clarify my previous message: I didn’t mean to imply specific expectations from the developers. I’m just interested in understanding how the development process usually works and whether new features tend to be added over time to achieve feature parity in GOS or if there is no such thing as feature parity. If not, is there a way to know what features will not be available in GOS.

              sir_brickalot

              If the feature is in AOSP, it will typically be available in GrapheneOS, but I can imagine a scenario where features were deliberately disabled due to being insecure, or they were delayed because they required significant integration effort.

              Two more relevant scenarios to keep in mind:

              • Some features are exclusive to Google's OS, and are not included in AOSP.
              • Some features are announced (by Google), but not rolled out (by Google) in the initial release. They arrive in a QPR update.

                  sir_brickalot I’m just interested in understanding how the development process usually works and whether new features tend to be added over time to achieve feature parity in GOS or if there is no such thing as feature parity.

                  The project is heavily focused on security and privacy. The staffing is very small compared to the staffing of Google's OS. I don't believe "feature parity" is a plausible goal for the foreseeable future. In the other direction, GrapheneOS is often ahead of Google when it comes to security and privacy.

                  sir_brickalot If not, is there a way to know what features will not be available in GOS.

                  So far the GrapheneOS project does not publish a "roadmap", meaning a list of features and projected dates. As Probably9857 indicated, features that Google donates to AOSP tend to be shipped in GrapheneOS. Note that AOSP has many fewer features than the OS that Google ships on Pixels.

                  It is likely that many features of Google's OS (or Samsung's OS, etc.) -- especially features unrelated to security and privacy -- will not show up in GrapheneOS for a very long time.

                        NightSky Any chance of the status icons change happening?

                        My sense is that if Google reverts the status-icon change in a future release of AOSP, or adds a setting, that code will very likely ship in GrapheneOS.

                        But it seems pretty unlikely, given the long list of security and privacy features the GrapheneOS team has expressed an interest in shipping, that the team will themselves revert the status icons or add a preference for that.

                        Please note that I do not speak for the GrapheneOS project.

                          4 days later