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.

                        GrapheneOS Interesting, I thought device name was always sent and the setting introduced in Android 15 is to control that. I've seen my device's name appear on DHCP servers. I will play around with my phone tomorrow and see if I can get it working again. Thanks.

                            My First post on this forum → pretty nervous.
                            First of all a huge "Thank you!!" to the developers. Finally a mobile operating system I can trust. Porting a new major version this quick is impressive! Please keep up the good work. I Will surely donate a some money.

                            Ammako
                            GrapheneOS

                            Something very similar regarding USB happened to me yesterday (still on Android 14) waiting for a release to hit the stable branch. My Pixel 8a is normally set to "Charging Only" but I wanted to temporarily enable USB to use MTP. Whatever cables and computers I tried → no reaction but charge. Even after a direct reboot into fastboot absolutely nothing happened on USB.
                            I was already in panic (reseller will(!!) deny hardware warranty because of custom OS an no way to flash back without USB).

                            After turning it off for a while all functions where back (adb for sideload recovery, fastoot, main OS working exactly like it should according to the USB-C settings.
                            Set it back to charge only. Next morning: Same problem. Off → On → fine again.

                            It is not a big deal for me since I'm planning to use USB more or less never.

                                AlphaElwedritsch However, in the current beta 2024101801 it is shown as "Pixel-7a".
                                I think that is what is being fixed for the next beta (already in alpha).

                                  USB is wobbly for me. I don't care much since I have the phone on USB-c Charging only normaly.
                                  Pixel 6 / Debian Trixie/Sid.

                                  GrapheneOS

                                  USB is wobbly for me also. Will try the power off trick next time.

                                  Regards

                                    whambam Btw, anyone know how to access Private Space files from PC via USB?

                                    fid02 As far as I can tell, you can't get access to the home folder of Private Space through MTP. I attempted this on stock PixelOS as well

                                    This is totally a blocker for me from starting to use private space. I really hope MTP support for Private Space gets added later on, by either Google or GrapheneOS developers. I guess the easiest would be to extend the popup dialog that appears when inserting the USB cable to have one option to enable MTP for main profile and one to enable it for private space, instead of only one enable MTP option that in practice enable it for main profile. But if we get support for this, it will likely be after stable release.

                                    Until then, I have to keep using separate user profiles. Because I need to be able to transfer in and transfer out files in my use case, without touching network, and without storing things unencrypted on USB sticks, and without using third-party solutions.

                                    Homerstar Got an error with the Hotspot Feature.

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

                                    The crash log I have seen indicates MTE (memory tagging) is killing the Wifi subsystem because of some memory safety violation. This sounds serious. I have tried reproducing, but I have a Pixel 7a, and it does not support MTE.

                                    Are there anyone at all with a Pixel 8 or later phone, that has enabled MTE, that do not experience this crash when last connected device leave the hotspot?

                                    paweljott When trying to change the privacy settings for saved wifi networks (in particular "send device name"), the dialog repeatedly crashes if the network SSID includes a "/" character. I will try to test more when I get home.

                                    Issue fixed in 2024101900, that is now in alpha.

                                                ryrona Are there anyone at all with a Pixel 8 or later phone, that has enabled MTE, that do not experience this crash when last connected device leave the hotspot?

                                                I have a Pixel 8 but can't reproduce this with the steps given ("last connected device leaves the hotspot"). Would need clearer instructions, and an overview of the hotspot settings at the time of the crash.

                                                    ryrona MTE is enabled by default for the system except for third-party apps. No toggle to disable it.

                                                        Thank you for all the fantastic work! I really appreciate it alot!
                                                        Android 15 seems to work fine on my Pixel 7 and Pixel Tablet. (I have no Google Services installed)