Hopefully this makes sense, its a lot, so stick with it
Okay, im going to refer first to the original (traditional) method first discussed years ago, and which my simplified module does
Back in the dawn of time, to doze gms
the line in google.xml
<allow-in-power-save package="com.google.android.gms" />
was manually commented out to become:
<!-- <allow-in-power-save package="com.google.android.gms" /> -->
this left the line in place and able to be reversed
this is essentially what my module does, but automatically, (and adjusted for a range of paths since the original path):
Code:
# add <!=== prefix and --> suffix around relevant line in google.xml
sed -i 's/<allow-in-power-save package=\"com.google.android.gms\" \/>/<!-- & -->/' "$MODPATH/$finalgxmlpath/google.xml"
other modules may just delete the line - theres comments about this in the thread - me i like to (try and) make fully reversible modules
Okay, from the files attached
system_google.xml:
theres NO <allow-in-power-save package="com.google.android.gms" />
i assume it either never existed (perhaps because of the presence of the my_bigball version - only a stock clean install would tell for sure) , or was removed by another module
my_bigball_google.xml:
theres 3 lines...
the "standard" <allow-in-power-save package="com.google.android.gms" />
and 3 more :
<allow-in-data-usage-save package="com.google.android.gms" />
<allow-unthrottled-location package="com.google.android.gms" />
<allow-ignore-location-settings package="com.google.android.gms" attributionTag="com.google.android.gms.thunderbird" />
the other 3 include where its toggling on with data...so that mystery is partially solved
the (modded) gloeyisk GMS Doze 1.8.6 i attached was modded to check for /my_bigball but it only looked for the lines
allow-unthrottled-location package
allow-ignore-location-settings
the one it didnt look for out of the 3 you have was:
allow-in-data-usage-save
so i assume therefore thats the one triggering when data is on....mystery solved?
gloesky's module latest 1.8.7 (github) module searches for and attempts to patch these other lines
allow-unthrottled-location package
allow-ignore-location-settings package
allow-in-power-save package
allow-in-data-usage-save package
Both gloeyisks module and now CrazyBytes (modded) version on the Alt-Magisk-Repo (and github here:
GMS Doze. Contribute to Magisk-Modules-Alt-Repo/GMSDoze development by creating an account on GitHub.
github.com
Also both patch lines not related to gms, and for other packages like ims etc
Neither though look for the my_bigball path....
Mine, as mentioned, has never looked for the additional lines, or modified for other packages, and it wouldnt be true to the original method, or "simplified" if i started adding all the "features" that gloeyisk and now CrazyBytes version added. My version was merely made for me, and it serves me well, i merely uploaded it for anyone wanting the "original method" that broke less stuff, and i have added new paths where ive come across them.
So im not going to alter my module for these new lines (or other packages)
But what i will do is make a request for the gloeyisk and CrazyBytes to add the my_bigballs path to their modules, if your test (see below) pans out. Going on recent history CrazyBytes will likely make this change first
In the meantime, ill attach modded versions of CrazyBytes (which will hopefully work), as this seems like it will be the most updated going forward. Can you then test and give me feedback if it works (or not) as its all still theory until backed by evidence
CrazyBytes has 2 versions (both have been modded with the path)
GMS.Doze.V1.3A.zip = Find My Phone NOT blocked for extra battery saving
GMS.Doze.V1.3B.zip = Find My Phone IS blocked for extra battery saving
His warning (somewhat redundant i feel): These should only be flashed after Google account has been added...
If testing okay and i submit a request for path addition, when/if he adds the changes, i will update you and you can update via the Repo of via his github going forwards
