other8026 I noticed that I couldn't start a private space while I had a session in another user profile open. After closing the session I could start the private space and see it on the app drawer with the default launcher.

      Michiel I noticed that I couldn't start a private space while I had a session in another user profile open.

      I'm not sure if I'm understanding this correctly... Are you saying that if you have another active secondary profile (not owner), you can't unlock the private space? If not, what do you mean by "session"?

      I just tried myself on my old phone and it worked for me, but I haven't updated to the latest release.

          other8026 I tried to install a private space for the first time from settings, but it did not work (instead it did the privacy check) when I had a user profile running in the background. But it was able to install it after this user profile session was closed.

              Michiel just tried that as well, but it worked for me. This is what I did:

              • factory reset my phone
              • set up owner
              • set up a secondary profile that can run in the background
              • set up private space in the owner profile
              • unlock private space

              Michiel instead it did the privacy check

              Sorry, I'm not sure what you mean by this.

                    other8026 I tried to repeat it, but it works now. Maybe a reboot in between did the trick. The privacy check (or scan) is the top option in the Security and Privacy menu in Settings.

                        Michiel okay, so it sounds like maybe it was a one time thing. Thanks for letting us know, though!

                          I nad problem with enabling hotspot. Did not work
                          I had to reboot phone

                            I'm not able to use USB anymore. No problems on 2024101200, but on 2024101801, even if I disable the USB-C exploit protection like usual, connecting to my PC does not work anymore. Pixel 7a.

                            The cable should be good, it works fine with my 4a and worked fine on the 7a before the Android 15 upgrade. When I plug it in, it takes like 4 seconds before the phone finally reacts to the cable being plugged in, but PC doesn't recognize it, and I don't have the options to choose USB File Transfer, for instance.

                            Can't use USB OTG either. SD card reader doesn't react to being plugged in, while headphone jack adapter sort of recognizes it's being plugged in (I hear a faint crackling noise in the headphones after plugging it in), but audio doesn't get passed through USB.

                              I appear to be unable to connect to my car using Android Auto since 2024101801. I am 99% sure it worked fine on 2024101701, so I wonder if it's something to do with 'stop enabling the new Android 15 "Send device name" toggle for Wi-Fi networks by default' since 2024101800.

                              Has anyone else experienced this? Can I downgrade to 2024101701 without losing my data to test that it definitely worked on 2024101701?

                                abdullah Can I downgrade to 2024101701 without losing my data to test that it definitely worked on 2024101701?

                                Unfortunately not. The current upgrade mechanisms all block downgrades. This is because otherwise an adversary with physical possession of your device could install an old version of GrapheneOS chosen to contain a bug that the adversary knew how to exploit. More information: https://grapheneos.org/usage#updates-sideloading

                                    abdullah There should be no changes rleevant to Android Auto usage. Sending the device name to DHCP wasn't something that was done in Android 14 QPR3. It was a new addition in Android 15. We were only restoring how things already worked before on GrapheneOS.

                                        de0u In addition to both the over-the-air update client and sideloading blocking downgrades, update_engine also blocks it at a lower level. Verified boot also enforces a downgrade check too although the granularity can be different. An update package downgrading the device to an older release would require building the older release again with a newer build date. If the security patch level is lower, it's not possible since that's enforced.

                                            Ammako You're the only person who has reported having any issue with USB. It's probably not caused by the update. You could try turning off the device to make sure the USB controller gets rebooted. A regular reboot may not do it.

                                                GrapheneOS Thanks for the clarification! Especially at a time when the team is busy with Android 15.