Xieohp For the past 3 days, after about two system updates, my battery has started to work horribly, practically lasting 3 hours from the moment I turn it on.

During those three hours, is the phone noticeably warm? If yes, maybe some apps are running too much. If no, maybe the battery is failing.

What is the battery's cycle count? Settings, About phone, Battery information?

      de0u No, the phone has the usual temperature and, as I described in the first post, the phone and battery are not stressed at all. After almost a year of life, the battery has 120 charge cycles.

        I had exact the same problem with my Pixel 7a after updating to 2025.03.08.00.
        I've installed 2025.02.11.00 again and everything is fine since then.

        I also have this problem after the same update. By 2025031300 the issue is still present. Pixel 8A

        4 days later

        I have a similar battery problem starting in early March. It's a pixel7a with a cycle count of 300.

        The specific thing I saw is towards the end of the day, my battery's percentage would drop really fast, like 2 percentage points per second. Shortly after, it would turn off.

        • de0u replied to this.

          aaronm04 Towards the end of the day, my battery's percentage would drop really fast, like 2 percentage points per second. Shortly after, it would turn off.

          That really sounds like a battery that is starting to fail. I suspect that if you provide that description to somebody at a repair shop my hunch will be confirmed.

            Thanks @de0u . I'll find a shop that'll replace it this weekend. In the meantime, it's still usable with Battery Saver mode.

              Hello, the same problem here since last update. My both Pixel 7a and Pixel 8a are affected. The battery of the Pixel 8a has only 102 cycles.

              I think there is generally something wrong with the update, which leads to high battery consumption.

              Additionally, after the calibration charging till 100% I got that shield, but after approx. 80 minutes (according to AccuBattery log) the phone began discharge from 100% down, as if it was no bypass anymore, however the shield icon was still present. So the shield icon was there, the charger was connected to the phone, but actually no bypass and no charge at that time.

                Grapi

                Grapi I think there is generally something wrong with the update, which leads to high battery consumption.

                I have a feeling you're right. In my case, the problems happened all at once earlier this month. If the only problem was my battery getting older, I think the onset would be more gradual.

                I didn't understand your last paragraph though.

                      Grapi

                      I think there is generally something wrong with the update, which leads to high battery consumption.

                      You have an issue with your apps, network or configuration which you're attributing to OS updates without evidence for it. Battery life is not negatively impacted by recent updates for our overall userbase.

                        aaronm04

                        In the meantime, it's still usable with Battery Saver mode.

                        This is a near certain indication that it's caused by apps.

                          Xieohp

                          What could have happened? Is there any information about power problems with the new updates?

                          You're using buggy apps not compatible with Android 15 QPR2 which are now draining the battery or they had updates which caused it. Our users all use a small set of well supported devices so we're confident there's nothing severely wrong that's not impacting only a tiny number of users, which would be caused by their specific apps, networks or configuration even if they were OS bugs. Whether or not the battery drain is from bugs in your apps, in the OS or something else, it is one of those areas causing it because it's not occurring for everyone else. It is something you will need to narrow down regardless of the cause. No one else can narrow down which app, network, etc. it causing it without access to it.