the updates block can't survive reboots [Android 16]

[martinotecco]

Even after updating the module to v4.2, which fixed the reset of the sources list after reboots, the module's core-feature, blocking the updates, can't survive reboots, at least on Android 16 (and on Samsung's OneUI 8).
Other than that, the module seems to work great, until you don't reboot the phone.

The issue is with Google Play Store, which, even with its auto-update feature turned off and per-app auto-updates turned off, it's trying - and partially succeeding - to update older apps installed on my phone.
I have the XDowngrader module installed - the one and only of it's kind that truly works - which allows any installed app to be downgraded; what I think such module does in order to work is removing the app version check during app installations. With the XDowngrader module installed, Google Play Store can partially succeed in updating all the apps it finds they need to be updated. "Partially succeeding" because after it updates them, then in the app info the version remains the same as before, but the "App downloaded from" section says it has been installed from Google Play Store: this partially succeeded update causes any app to break, it won't open at all and just crashes at startup. Due to this, I am then forced to manually go and install any of the apps I need to be in a specific version, by tapping on all the .apk files I had previously downloaded and allowing their update (technically downgrading them).

I don't know what really is the problem here, maybe the Google Play Store can update all those apps before it gets blocked by your Updates Manager Extended Xposed module?

---

some additional info:
  phone: Samsung Galaxy S24 Ultra (SM-S928B/DS) w/ OneUI 8
  Android version: Android 16
  Xposed/LSPosed framework: JingMatrix's Vector v2.0 (Xposed API v101)

[Senliast]

Okay let's make sure i got you right. You install the module, reboot, and then it works until you reboot again, is it correct? Do settings then gets deleted or what exactly happens? And another module "XDowngrader" does not work correctly as well, right?

[martinotecco]

You install the module, reboot, and then it works until you reboot again, is it correct?

Yes, that's exactly what is happening to me. After I enable the module and reboot to make it able to work properly, it works great, it seems to block the updates from the selected sources, Google Play Store is not updating those apps ...until I reboot my phone and then, after a minute or two have passed, I can see that Google Play Store has updated those apps I actually don't want it to update at all. However, after any reboot, the module says it's enabled and working, and it really is; in fact, if I then manually go and update (downgrade) those apps, Google Play Store won't update them anymore, and to me this is the sign the module is successfully doing its job.
Then if I reboot, the same problem occurs: Google Play Store updates those apps the very moment the phone turns back on. That's why I'm saying that maybe it could be a problem related to the fact that the module could not be loaded fast enough to prevent Google Play Store from updating those apps at startup.

Do settings then gets deleted or what exactly happens?

The module settings are still there after every reboot, they're not getting deleted.

And another module "XDowngrader" does not work correctly as well, right?

I don't know if XDowngrader isn't working correctly as well. Its source code is not publicly available, so I can't inspect it for further analysis. Its core-feature is to allow users to downgrade any installed app, and it does it job successfully.

[Senliast]

The module and it's settings are loaded and applied together with Android Framework which loads much earlier then Google Play. That's because Google Play is an app and needs Android Framework in order to run. And, Google Play can update apps only in AFU state (After First Unlock), because app data is encrypted with CE key (credentials encrypted, becomes available after you enter the PIN), but the module already runs in BFU state (before first unlock), because it and it's settings are encrypted with DE key (device encryption, available immediately after boot, befor you unlock for the first time, Xposed modules settings are not saved as regular app data). So, it cannot be the case, that the module is not fast enough.

I can see that Google Play Store has updated those apps

where do you check if the apps are updated? In the play Store update list? If so - do note, this list as well shows updates, which were done by you by installing an APK. So it not only shows updates, done by Play Store. You should compare version number, shown in the app settings.

[Senliast]

Does the issue still exists?

[martinotecco]

Yes, it's still there.

[Senliast]

Okay but i need a response to the question above. Are you sure the app got updated? Look in the system settings in the app info page.