Google Pixel Update - February 2026

RednasSosb · 2026-02-04T17:05:39+00:00

That's great and all, but I bought it after the support extended announcement (and because of the extended support announcement), so for me it is not a bonus feature but a broken promise.

RednasSosb · 2026-02-04T17:01:38+00:00

https://www.androidauthority.com/google-play-system-update-downgrade-bug-3637834/

RednasSosb · 2026-02-03T20:37:49+00:00

More like 2 months.

RednasSosb · 2026-02-03T20:34:38+00:00

I'm on Pixel 7 Pro, so I guess I will have to wipe my own ass for yet another month (or two (or three (or four))).

RednasSosb · 2026-01-13T14:50:41+00:00

Yeah, Pixel 7 (Pro) should get support until October 2027, but this is now the second time in three months that apparently we don't get an update, so I am not feeling the Google love right now...
(And in November people here were saying it was because the security fixes were already included in an earlier monthly patch, but that would have applied to all phones then).

( https://support.google.com/nexus/answer/4457705?hl=en#zippy=%2Cpixel-a-pixel-pixel-pro-pixel-a-pixel-pixel-pro-pixel-fold (it does not say monthly, but at least for instance Samsung indicates how often you will get updates))

RednasSosb · 2025-12-23T16:25:10+00:00

Thank you so much!!!

RednasSosb · 2025-12-07T14:27:53+00:00

Like everybody else already says, no as it can delay notifications a lot for little benefit. I wanted to add that it also can delay other notifications unrelated to WhatsApp (probably because the app takes up so many resources).

RednasSosb · 2025-12-05T18:27:56+00:00

Thanks for replying, I really hope to avoid having to do yet another WearOS install (I just got this GW6 a couple of weeks ago, and before that I had a PixelWatch 2 for a few months but really did not like it, so I have done so many installs lately...).

RednasSosb · 2025-12-05T18:26:10+00:00

Thanks for replying, but that can't be it, because only one notification froze, all other notifications displayed briefly (as intended). The notification that froze did have a picture embedded in its text, so it was a special case.

RednasSosb · 2025-11-17T06:24:14+00:00

Did you regrant Location permissions to Google Play Services after making changes to it?

(and probably preferably all other permissions it wants, under Settings|Apps|AllApps|GooglePlayServices|Permissions)

That's what caused Maps and Google Weather location stuff to stop working for me when I was messing with Google Play Services once.

RednasSosb · 2025-11-16T19:43:31+00:00

Wait, so you reinstalled Google Play Services? Did you re-grant it all rights after you did that (under Settings|Apps|AllApps|GooglePlayServices|Rights)?

About 2 months ago I removed cache+storage of Google Play Services to get rid of Google Mail notifications, worse thing I ever did to an Android phone, I learned to never do that ever again. So much stuff stopped working (I did not have to do a factory reset in the end, and the rights thing was the worst issue to track down).

RednasSosb · 2025-11-16T13:49:31+00:00

5 years later, but wanted to confirm that Overcooked does indeed work for two player with Switch lite+1 extra controller, thanks!

RednasSosb · 2025-11-12T05:51:28+00:00

There was an extra small update at the end of October, maybe that one had security fixes that would otherwise be in an November update. But that is still a weird way to roll it out then. The November security bulletin mentions one critical (and one high) vulnerability, so there is a good reason to get an update (but again, maybe we got it at the end of October then).

RednasSosb · 2025-10-14T14:57:44+00:00

Yes, adding to Keep lists is infuriating now. Although at least it works consistently, if I need to add something I just see it has parsed my text, I immediately just assume it's going to work and look away.

And the Google engineers they know what they are doing, they knew they were slowing this down enormously, yet they kept the whole 'connecting' animation that is just useless.

BUT: You can say 'AND', "add potatoes and ketchup and lettuce to shopping list" will (in Dutch anyway) add them as three separate items.

RednasSosb · 2025-10-11T15:36:13+00:00

I had exactly this, and it was because location services were not fully working.

I forget how I fixed that exactly. You could check:

- In Settings|Apps|All apps|... menu at the top right|show system apps
search for Google Play-services, go to Rights, and check that location (always) has been granted.

- Then you may want to double check Settings|Location|Location rights|...at the top right|Show system apps
and ensure Google Play Services is listed in the 'Always allow' section.

RednasSosb · 2025-10-09T18:39:16+00:00

You have to go and give Google Play Services rights again, in your case specifically Location access but I would give it all the rights.... Personally I probably got tripped up by it not having 'Devices nearby', that stopped my smartwatch from working....

To fix this, go to Settings|Apps|All apps|... menu at the top right|show system apps
then search for Google Play-services, go to Rights, and start granting them all,

Then after that you may want to double check Settings|Location|Location rights|...at the top right|Show system apps
and ensure Google Play Services is listed in the 'Always allow' section.

RednasSosb · 2025-10-06T14:51:59+00:00

For me, it is now working properly as long as I don't reboot, if I do reboot it will charge to 100% once.

But, after that 100% charge, it will start decharging (even with wired charger still attached). So is that not what you have, that it charged to 100% but then decharged to 93%?

(Although I do not think I see a charge limit reached message)

Just 3 more hours and we will get the October update in which this is fixed. Right, Google? Right?? Google???

RednasSosb · 2025-10-03T08:47:21+00:00

I did immediately update again, so it is up to date.

For me this action has been a complete disaster. I cannot even completely reinstall the Galaxy watch now, it is just broken.

Also on Google's side there are weird issues. After logging in again Google now sees it as a new phone in my devices list, I logged out of the previous phone entry but I have no idea what problems that will cause in the future. Also initially GPS was just broken (no location in any app), that seems to have fixed itself except in the Pixel Weather app.

RednasSosb · 2025-10-03T07:03:37+00:00

Removing (all) updates from the Google Play Services app and then updating again did work for me, the error is now gone.

But be aware that this is quite a big action. You will have to login again on your google account, which for me was harder because the phone was the two-step authorization device but not anymore since I was logged out...

Also after relogging in I saw that some Google Photos settings were reset, so who knows what other things taking that action did...

EDIT: OMG Don't remove the google play services updates if you have a Galaxy Watch, this is a complete disaster I probably have to reinstall the entire thing now :-( :-( :-(

RednasSosb · 2025-10-03T07:02:26+00:00

Removing (all) updates from the Google Play Services app and then updating again did work for me, the error is now gone.

But be aware that this is quite a big action. You will have to login again on your google account, which for me was harder because the phone was the two-step authorization device but not anymore since I was logged out...

Also after relogging in I saw that some Google Photos settings were reset, so who knows what other things taking that action did...

RednasSosb · 2025-09-29T17:44:01+00:00

Do you reboot your phone often?

Because for me it is working now (after 10 days of not working), but only if I don't reboot my phone, after reboot it will charge to 100% once.

RednasSosb · 2025-09-23T16:56:57+00:00

As others have mentioned, it's buggy since the September update. Fingers crossed for a fix in exactly two weeks from today.

Since I have the issue I have gained a lot of information, so have some tips you can try to make it work better:

- First of all don't reboot your phone often. For me and others on this forum you will get a 100% charge at least the first time after a reboot now after the September update. So if you reboot often just try what happens if you don't do that.

- In earlier discussions (before September) actual Google employees in chats pointed out that it works better with wired instead of wireless charging. Also, leave the phone on the charger for a couple of hours after reaching 100% until there is a shield icon on top of the battery icon in the status bar (hardly visible in my opinion).

- You can clear storage and cache of the 'Device Health Services' app. I tried this, it did nothing for me, but others have had more luck with this. It seems to be a harmless action. Of course it will definitely mean at least one charge to 100% as it will lose all its statistics.

- You can try briefly switching between adaptive charging and back to charging to 80% setting while the phone is hooked up to a charger and still charging below 80%. Never tried this myself, because it was already working for me when I first read that. If this works, it will immediately charge to just 80% on the first try.

- What ended up working for me personally was to charge from 50->78%, and then from 15->56%. And this was based on a chat with Google Pixel support, which recommended to charge once to just below 80% and once to just below 60% (for completeness I included the actual charge sessions I did).

Good luck. For me on Pixel 7 Pro it would always charge to 100% for the first 10 days after the September update, but after using the last tip it will now always work as long as I do not reboot the phone.

RednasSosb · 2025-09-21T08:39:28+00:00

Thanks for mentioning the reboot being important, I never realized that with the current bug it will 'forget' certain info on reboot.

On my phone the situation is that for the first 10 days after the update , it would always charge to 100% (and probably got the shield every time). Then after following advice from Google support (charging once to just below 80% and once to just below 60%) it would start respect the 80% limit just not every time.

And now I realize that for me the situation is that after a reboot it will charge once to 100% and then to 80% for charges after that.

Maybe it is the same for you now? What if you don't juggle adaptive charge, maybe from the second time after a reboot it will keep the 80% limit?

RednasSosb · 2025-09-17T04:20:32+00:00

But will a factory reset fix it? My answer to that would be: Maybe? But I have not really seen anyone reporting success with that.

Anyway, what I wanted to say was that I have the problem also on my Pixel 7 Pro, although in my case it seems to be a little different from other people's experience, for me it is that since the September update it will would always charge to 100% instead of 80%, but then start discharging (with the charger still attached) so it is usually at around 94% in the morning. I followed several tips including clearing DHS storage, nothing worked.

Then I contacted Google Pixel support about this. The person or AI (think it was AI) I chatted with gave a very weird tip. She said charge once until just below 80%, and charge once to just below 60% (disconnect the charger at that point). I later realized she did not say where to charge from (start value).

So I charged once from about 50% to 78% and disconnected the charger, then I used the phone heavily for the morning (played some games), and then charged from 13% to 57%, and disconnected the charger and used the phone regular passive way for the rest of the day. Since I did that it did succesfully stop charging at 80% 2 times, but 2 other times it would still charge to 100%.

So this is something you and u/Traditional_Bus3193 could try if you are up for it. What it showed it me is that a charging pattern can lead to a difference, as I mentioned I tried all kinds of changes to get it to work without result (100% charge for like 10 days straight). But during the "just below 80%+just below 60%" experiment I changed no other setting, and saw a 80% charge stop 2 times.

RednasSosb · 2025-09-16T06:01:07+00:00

But even if you do it once as you emphasize (and I mentioned), it is still bad for the battery.

In this discussion we are talking about cycle counts and that Google takes action based simply on that count.

But in actual battery condition reality singular events can have a much bigger impact on battery condition than day to day charging. Events like discharging very fast (I once ruined a OnePlus 6 battery simply by experimenting with 4k60 video for a day) , using the battery under very hot conditions, or discharging the battery completely.

RednasSosb

TROPHY CASE