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)

                                            GrapheneOS it's very strange. I had tried a restart yesterday and it didn't help. but this morning, a restart helped? I didn't do a full power off.

                                            The difference this morning is that I set USB-C to On (no restrictions), then restarted, and after that it just kind of works. I can switch it back off and back on, no problem. Usually I only use the Charging-only when locked setting, when I need to use USB, before setting it back to Charging-only.

                                              Michiel 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.

                                              other8026 just tried that as well, but it worked for me.

                                              Michiel I tried to repeat it, but it works now. Maybe a reboot in between did the trick.

                                              For what it is worth, I also tried to create a private space, but when two secondary users where already logged in so there shouldn't be any free spots. But it worked just fine. The private space was created just fine, it didn't even log out any of the secondary user profiles.

                                                    GrapheneOS
                                                    I am not sure if it is the same issue, but it happens to me on both Android 14 and 15, therefore I think it is not a Android 15-specific bug, but it did persist on Android 15 as well.
                                                    I tested this on a Pixel Tablet and a Pixel 7 both with the same results.

                                                    The issue is as follows:

                                                    1: I set the USB profile to "charging-only"
                                                    2: I reboot the device completely.
                                                    3: After restarting the device I set the USB profile to "charging only when unlocked".
                                                    4: I put in a USB drive, the Samsung FIT Plus 256 to be precise, but this bug also happens on other USB drives.
                                                    5: It does not recognize the USB drive. (It is not being mounted at all)

                                                    I resolve it as follows:

                                                    6: I take out the USB drive from the USB port.
                                                    7: I put my device at the lockscreen twice, both for a few seconds.
                                                    8: I unlock my device.
                                                    9: I mount the USB drive, it will get recognized.
                                                    10: After cycling through USB profiles a second time around this problem does not occur anymore until I do a fresh reboot again.

                                                    I use the official Google OTG adapter that was included with the device.