iyanmv

There's no change since what we wrote on the releases page. Most of the supported devices are on the 2023-09-05 patch level. As explained on the site, AOSP had the patch level string set to 2023-09-01 for all devices and we didn't delay the release to make an aesthetic change for the devices with all the 2023-09-05 patches.

Our current stable release for the Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel Tablet and Pixel Fold has the 2023-09-05 patch level already and there will be an early update to the 2023-10-01 patch level today.

Pixel 4a is end-of-life and is receiving extended support. The patch level is permanently frozen going forward since it won't ever get the required firmware patches.

5th generation Pixels are on 2023-09-01 because there hasn't been a 2023-09-05 release of the Android Open Source Project or stock Pixel OS with Qualcomm firmware/driver updates.

Pixel 7a is the only device with standalone Qualcomm Wi-Fi and is in the same situation as 5th generation Pixels.

My device is in stable channel and auto updates enabled. However i recieved this update yesterday which is beta as i see in the releases page..does it happen to you too?

    Goseur7 The releases page hadn't been regenerated yet. It's usually done right after moving an update to the beta or stable channel, but there was a connection failure.

      JayJay Also, I have noticed when I switch from a secondary profile (Google shit) to the main (owner) profile, sometimes my Pixel 7a freezes, all the apps start crashing on launch and swiping down on the homescreen force closes the launcher instead of bringing the QS panel down. I need to restart my device in order to get out of this weird situation. This behavior happens every now and then and this makes the whole experience so annoying.

        Something is happening with the notifications in this release? I am getting late or no notifications after the upgrade (Pixel7).

          • [deleted]

          gonzalo 7 Pro here and notifications are working fine for me.

          SoulKeeper I've had this same issue and the way to fix it is a reboot. Its not from this release though and has been happening for about the last 5 updates. I'm not sure what's causing it but I know it happens when using a profile and then switching back to another. It might not be a Graphene issue and could be an upstream issue, hopefully it gets fixed though.

          Settings: remove Private DNS setting for secondary users since it's not currently per-profile like VPN configuration but rather is global like Wi-Fi configuration

          This hurts my experience a little not being able to toggle it on and off in the profile I am in.

            Mickeybrad
            I think the changelog suggests that the setting is not per profile and the toggle will be pointless or misleading. No?

              Either the updates are getting faster, or I got lucky

              Both 01 and 03 arrived the next day for me.

              Panda-na well no luck, somehow notifications are working very erratically since the last upgrade, it works fine then with delay, I got whatsapp notifications 10 min late for example, reboot doesn't fix it.

              Oggyo its like if we had to go the main profile to change WiFi connection.

                After latest update, cannot make wifi calls or sms?

                Mickeybrad
                I guess - yes, because it's a global setting. Honestly, I'm not sure how it was before. I mean if the toggle had any local profile meaning and allowed Private DNS per profile.

                  Oggyo before it worked globally. If you turned it off in a secondary profile it would turn off as a whole. Was good in use cases where a WiFi connection doesn't allow private DNS like some work places. I also use it as my primary source of adblock but sometimes need to disable it if a site or captcha is not working. I can still do these things but its a little longer now.

                    Mickeybrad
                    I see. Looks like it always was a global setting, but was accessible from a user profile. The user profiles were always more restricted compared to the Owner and I agree for people who use the user profiles exclusively (or as a main profile) this can be a hiccup.