You can:
1) Unzip the module
2) Open customize.sh
Add
/system_ext/ to the paths in the lines:
# Patch the XML and place the modified one to the original directory
ui_print "- Patching XML files"
gms=$(xml=$(find /system/ /product/ /vendor/ -iname "*.xml");for i in $xml; do if grep -q 'allow-in-power-save package="com.google.android.gms"' $ROOT$i 2>/dev/null; then echo "$i";fi; done)
ims=$(xml=$(find /system/ /product/ /vendor/ -iname "*.xml");for i in $xml; do if grep -q 'allow-in-power-save package="com.google.android.ims"' $ROOT$i 2>/dev/null; then echo "$i";fi; done)
pst=$(xml=$(find /system/ /product/ /vendor/ -iname "*.xml");for i in $xml; do if grep -q 'allow-in-power-save package="com.google.android.apps.safetyhub"' $ROOT$i 2>/dev/null; then echo "$i";fi; done)
trb=$(xml=$(find /system/ /product/ /vendor/ -iname "*.xml");for i in $xml; do if grep -q 'allow-in-power-save package="com.google.android.apps.turbo"' $ROOT$i 2>/dev/null; then echo "$i";fi; done)
aka
# Patch the XML and place the modified one to the original directory
ui_print "- Patching XML files"
gms=$(xml=$(find /system/
/system_ext/ /product/ /vendor/ -iname "*.xml");for i in $xml; do if grep -q 'allow-in-power-save package="com.google.android.gms"' $ROOT$i 2>/dev/null; then echo "$i";fi; done)
ims=$(xml=$(find /system/
/system_ext/ /product/ /vendor/ -iname "*.xml");for i in $xml; do if grep -q 'allow-in-power-save package="com.google.android.ims"' $ROOT$i 2>/dev/null; then echo "$i";fi; done)
pst=$(xml=$(find /system/
/system_ext/ /product/ /vendor/ -iname "*.xml");for i in $xml; do if grep -q 'allow-in-power-save package="com.google.android.apps.safetyhub"' $ROOT$i 2>/dev/null; then echo "$i";fi; done)
trb=$(xml=$(find /system/
/system_ext/ /product/ /vendor/ -iname "*.xml");for i in $xml; do if grep -q 'allow-in-power-save package="com.google.android.apps.turbo"' $ROOT$i 2>/dev/null; then echo "$i";fi; done)
3) zip the files in the root of the modules folder back up, and flash and test
OR
You can try my simpler GMS Doze module (added the /system_ext/ path just now)
It doesnt do as much as gloeyisk's, but it uses the "original" method as described
here (this is the OG of doze tweaks)
aka it merely comments out
<
allow-in-power-save package="com.google.android.gms" />
to
<!-- <allow-in-power-save package="com.google.android.gms" /> -->
my common/install.sh (i use MMT-Ex module format):
Bash:
gxml=$(find /system /system_ext /product /vendor -iname "google.xml" -print | head -n 1 | sed 's|/[^/]*$||')
ui_print "google.xml found at: $gxml"
root_folder=$(echo $gxml | cut -d "/" -f2)
if [ "$root_folder" == "system" ]; then
#remove the /system folder so we can use the same code beyond for all paths
finalgxmlpath=$(echo $gxml | cut -d "/" -f3,4)
else
#add /system folder prefix for product, system_ext and vendor paths
finalgxmlpath="system/$root_folder/etc/sysconfig"
fi
ui_print "creating directory: $MODPATH/$finalgxmlpath"
mkdir -p "$MODPATH/$finalgxmlpath"
ui_print "copying $gxml/google.xml to $MODPATH/$finalgxmlpath"
cp -af "$gxml/google.xml" "$MODPATH/$finalgxmlpath"
ui_print "modifying $MODPATH/$finalgxmlpath/google.xml"
# 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"
what it does (similar to above, though different): finds the first google.xml it can in the paths:
/system/
/system_ext/
/product/
/vendor/
copies the google.xml to the modules correct folder, either:
/system
/system/system_ext
/system/product
or
system/vendor
and then uses sed to add a <--- prefix and ---> suffix to the relevant line
thats all it does. for those who have issues with main GMS Doze module, you may like to try this simpler one. I made it (in 30 seconds) in response to a members question on here, and only up till now shared it with him privately. It resolved the issue was personally having, ymmv
attached....
never be afraid to open up a script and look for ways to customize it to your needs, its often easily to figure out how to add/change a path...its hard to hose your device with a magisk module, even if you bootloop it, its fixable....
play.google.com
forum.xda-developers.com
