[Magisk] scootley:
Hi,

I have a Pixel 5 (Android 11 stock, but rooted) with Magisk (canary) version 6d88d8ad (21201). I also have the Developer setting for "Automatic system updates" turned off.

It seems to me like the phone is not able to detect (and thus never notifies about) any available OTA, such as the Dec 2020 "201205" OTA, since it has been out for a long time now. Note: I am not talking about installing OTA updates. Just checking for them and getting notifications of them being available.

Is this a known issue? If so, is it documented in an easy-to-find official up-to-date place, such as:

1) Within the Magisk manager app

2) On the Magisk github readme, github site, or github issues list (edit: in an OPEN issue, not a closed one)

3) In the official locked release thread

Hard-to-find or unofficial or outdated places where this would be documented would include:

1) Some XDA forum post somewhere (like this one. hypocrisy noted ;)

2) A tweet by topjohnwu

Is it related to MagiskHide or hiding Magisk Manager? I didn't enable those until just now. Is there a specific package/app that can be toggled in the MagiskHide list to allow OTA update checks/notifications to work?

EDIT: Possible theories discussed below and elsewhere include:

1) Having your bootloader unlocked (independent of Magisk) prevents OTA updates from being made available to you [which to me is absolutely in conflict with my personal experience in the past]

2) Having Magisk installed prevents OTA updates from being made available to you [consistent with my experience]

3) Even after uninstalling Magisk, OTA updates are not made available to you for either some time or forever due to a theory that Google knows you had Magisk and penalizes you (either on purpose or perhaps as a protection from update failures including some time buffer for extra safety) [consistent with my experience]

4) If you ever manually check for updates while Magisk is installed, it prevents them from being made available to you then and subsequently (for how long I dunno). But for a Pixel device I find this to be nonsensical, since even with "Automatic system updates" turned off, a Pixel device will still check for updates (daily?) and notify about them. It just won't install them and prompt for reboot. With this setting on (the default), it will actually install them and prompt for reboot.

5) "if you even have magisk zip on your sd card, the update will detect and prevent OTA check/notification. This stays set until the next month's update"

6) "took a logcat while checking for updates and saw the update program errored complaining about a corrupt partition"

7) The carrier has actually delayed the update, and as usual very rarely is this information proactively posted in an official public place by the carrier even if the update is over a month delayed. See here for fun details on how carriers can delay updates that are created by, led by, and distributed by Google.

8) If you somehow have a current update from one carrier installed but your SIM card is for another carrier, this can prevent updates.

9) If you don't have the latest "Google Play system update" (Under Settings->Security), which is perhaps indicated by the icon next to it being red, that may stop OTA updates from coming. But this presents another issue if the "Google Play system update" can't be updated either. This type of update is also known as "Project Mainline".

10) Devices that say their "Play Protect Certification" is uncertified (Play Store Settings) may not receive OTA updates. In fact Google has a help page on this that actually says "Devices that aren't Play Protect certified may not get Android system updates or app updates"

11) Google has delayed or staggered the rollout of the update more than usual, but in my case this delay was longer than 1 month and I would imagine that this would be covered by the media if the delay took that long on Pixel devices, since it actually went past the release date of the next month's update.

Thanks