[BUG]: This module doesn't work: "Google Photos Features & Unlimited backup" v2 by Kingsman44

[KrakenByteKraken]

Version

v1.0.0-rc.5

Reproducible since version

I only try this version.

System Information

LineageOS 15, POCO F1 (beryllium): lineage-22.2-20260317-nightly-beryllium-signed.

Root Implementation Information

Lygisk

Modules

Submodule "Google Photos Features & Unlimited backup" v2 from Kingsman44 Pixelify.

Description

The submodule "Google Photos Features & Unlimited backup" v2 from Kingsman44 Pixelify is enabled but really it doesn't work.

Steps to reproduce

1. I found that the affected module works fine with Dr-TSNG ZygiskNext but not with ReZygisk wich is my preferred Zygisk flavor.

Confirmations

• I am currently using the latest CI version of ReZygisk while reporting this Issue
• My environment meets the minimum requirements.
• I have ASSURED that no other Issue has been made about the same topic.
• I have acquired the MDA redacted log, utilizing the debug version of ReZygisk, and after creating this Issue, I will send it to performancorg@gmail.com or one of the project maintainers, with the GitHub Issue link included in the e-mail and the log attached.
• I have written, in all the fields above, using English, and I will be able to provide more information in English if required by the maintainers.

Code of Conduct

• I agree to follow this project's Code of Conduct

[ThePedroo]

Like in the example given, the Modules part are all modules you have installed, not just the impacted one. Who did you send the logs to, too?

[KrakenByteKraken]

I only installed this only module because it was possible to install only a submodule (now the link from the GitHub page seems doesn't work). I didn't send logs to anybody because there isn't a failure or a crash, simply the submodule doesn't have any effect, it doesn't work as it supposed to do because the Photos app doesn't have unlimited backup. But if you use ZygiskNext instead ReZygisk, then it works flawless.

[ThePedroo]

The logs are critical, they're obligatory for a reason -- even if no crashes happen, ReZygisk might or not be impacted by errors and silently ignore it.. Especially when using such a -- let's put it lightly -- unexpected root implementation.

[KrakenByteKraken]

All right then! It has sense. In fact, the submodule has a collateral effect: it impacts over the Google Fit app enabling it to measure heart and breathing rate and this "extra" part works like a charm with ReZygisk. So, how can I extract these logs and where I must report them? I never did it before, I'm only a typical user, but I'll try it.

[KrakenByteKraken]

Oh, I forgot to say that the old vanilla Zygisk included in Magisk, of course, works also flawless with that submodule.

[ThePedroo]

All right then! It has sense. In fact, the submodule has a collateral effect: it impacts over the Google Fit app enabling it to measure heart and breathing rate and this "extra" part works like a charm with ReZygisk. So, how can I extract these logs and where I must report them? I never did it before, I'm only a typical user, but I'll try it.

In your own Issue it guides on how to collect them, last part

[KrakenByteKraken]

Oh, sorry!!! I must remember to read all, at least, all that I sign!!!
Now I'm following the instructions: Installing the debug version of ReZygisk and Debug Assistant, collecting logs (located in /data/local/tmp/) and sending them to the said e-mail. Thank you in advance!

[ThePedroo]

Hey, could you try the build I sent #301?

[ThePedroo]

03-20 17:23:41.988  7704  7704 I Pixelify: inject android.os.Build for com.google.android.apps.photos with 
03-20 17:23:41.988  7704  7704 I Pixelify: PRODUCT:marlin 
03-20 17:23:41.988  7704  7704 I Pixelify: MODEL:Pixel XL 
03-20 17:23:41.988  7704  7704 I Pixelify: FINGERPRINT:google/marlin/marlin:10/QP1A.191005.007.A3/5972272:user/release-keys

The Zygisk module is doing its thing, so it should be all fine. In fact, I missed that in the first log. To double check, can you send me the Pixelify zip?

[ThePedroo]

You can send those non-sensitive things here, by the way, but thanks! Also, I see it mounts things, but in your logs, Google Photos in DenyList:

02-11 08:44:26.619   944   949 I Magisk  : denylist add: [com.google.android.apps.photos/com.google.android.apps.photos]
....
03-20 17:23:41.954  7704  7704 D zygisk-core64: set mount namespace to [/proc/1065/fd/12] fd=[76]: clean
03-20 17:23:41.954  7704  7704 D zygisk-core64: Registering module with API version 4
03-20 17:23:41.954  7704  7704 D zygisk-core64: Registering module with API version 2

Could you try to remove it from DenyList, reboot (just to be REALLY sure), and try again?

[ThePedroo]

I will get our internal testers to repro such. Thanks for the information.

[KrakenByteKraken]

COMMUNICATIONS SUMMARY FROM E-MAILS (ONLY FOR DOCUMENTATION PURPOSES)

---

Hi, I tried. #301
Unfortunately, it didn't work. I send you another new log.
Thanks, anyway.
DebugAssistant-Redacted.log

---

Here you are. Have a nice checking!!!
Google-Photos-Features-Unlimited-backup.zip

---

More logs, these are with Photos removed from DenyList. It continues failing.
DebugAssistant-Redacted.log
DebugAssistant-Boot3.log

---