Enable Doze For Gms Magisk Module

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

[MAGISK 16][Bombardment Saver][6.0+] ENABLE DOZE on Google Play Services

• Thread starter otonieru
• Start date May 18, 2017

• #1

Hi guys,

I really fabricated this module for my personal ain use, merely who knows, someone here might discover it useful also.

PIE & Magisk v19 Uniform Update
https://drive.google.com/file/d/ane-Nw6xHIhOPz06j4FqD-geAnMCz2NzPKX/view?usp=drivesdk

UPDATE NOTES :
OOS Nougat & Oreo User might non be able to find organisation app on Bombardment Optimisation list, you can work around this by using third party app like Greenify or Naptime to open Doze Whitelist, you lot will see Google Play Services already listed every bit "Optimised App". Or go to App Info from setting, choose "Bombardment" and ringlet down to "Battery Optimisation" - if the module work, information technology should written "Optimising Bombardment Use"

OREO User, Delight Utilize OREO version. v6 Update is already in the Magisk Repo.

BACKGROUND :
I always detect that Google Play Services is manner too aggresive in doing its activities in the groundwork. And its no underground that this main services from google is oftenly one of the master culprit for the sub par bombardment operation on most stock or even custom ROM beyond devices.

THE IDEA & THE Bulwark :
Starting in Android 6.0, Google has introduced one of my favorite features in battery saving : DOZE (quick read most this Here), information technology help u.s.a. to make apps go into a "shallow" hibernation state. Where it apply less energy but retain it's functionality.

Matter is, this feature is NOT applicable for Google Play Services. Thus, information technology cant help yous to save the battery from being eaten by Google Play Services. And this is not for no reason of course (read SIDE EFFECT/Note section bellow for further explanation)

THE SOLUTION :
Quick study (if you lot are interested, 1 of the word can be found Here) reveal that Google put elementary configuration is /system/etc/sysconfig/google.xml that WHITELISTING Google Play Services from the DOZE Machinery.

So to brand DOZE able to piece of work on it, we

merely need to remove the whitelisting.

This is WHAT THIS MODULE Practise - SYSTEMLESSLY (evidently)

By installing this module, you can move Google Play Services from the "App Not Optimised" listing to "App Optimised" which mean

DOZE mechanism will work its magic on Google Play Services, thus should saving you lot more juices/batt throughout the mean solar day.

THE SIDE EFFECT/Notation :
Saving free energy never come without side upshot. Same goes with this method.

By enabling Doze on Google Play Services, it will theoritically filibuster/break some it's services. Almost noticeable might be the GCM (cloud messaging) services.

App that use this services might experience delay in notification when Doze already kicking in.

Although, in my experience (i use this modernistic on all of my 3 devices) my notif for LINE, WhatsApp and Telegram (my primary comm app) is never been delayed. ( I put all these apps in my whitelist btw)

The ane i noticed had slight filibuster is GMail. Only i check my post regularly throughout the twenty-four hours, so i need no real time notif for that.

Every bit for all other main services like Accounts, Warning, Location and elses, i never have whatsoever outcome with them when i got this module active. GPS work fine, Warning ringing, Account Syncing normally.

HOW TO INSTALL :
And so if afterward reading all the PROs and the probable CONs to a higher place , you nevertheless interested in trying this modern,

But dowmload it from the zipper, and install it through your MAGISK Manager. And reboot.

After reboot, get to "Setting" - "Battery" - tap the tri-dot menu on the top right and choose "Battery Optimisation"

Choose "All Apps" and switch ON the toggle for Google Play Services (in most ROM, it will be automatically switched to ON once this mod is installed)

Relish THEN ! :highfive:

Addendum :

WHAT IS THE Departure between (+) and standard module ?
• Plus (+) version modified by @VR25 has an extra feature, which removing Google Play Services from Background Data Access Whitelisting. Thus enabling data saver or restricting background data will impact Google Play Services likewise. This might save yous extra juice, simply BEWARE for interrupted groundwork data activities.

Choose the one suit y'all nearly.

COMPATIBILITY :
This Mod should compatible with any Marshmallow and Nougat ROM (Official & Custom) that has Google Play Services Installed on information technology,

Tested on :
OOS, LOS, CM13, MIUI, EMUI, and TouchWiz

If yous found that this module causing issue for your fix, simply uninstall it from magisk managing director, or utilise the TWRP Uninstaller.

Screenshot of expected level of Google Play Services Battery Usage :

Attachments

• EnableDozeGMS-TWRP-past-otonieru.zip
• EnableDozeGMS-TWRP-Uninstaller.zip
• EnableDozeforGMS-Rev5-by_otonieru.aught
• EnableDozeforGMS-Magisk13xONLY-by_otonieru.zip
• EnableDozeGMS+Magisk-by-VR25-Rev5.nothing
• OREO_EnableDozeGMS+_TWRP_by_otonieru.cipher

• #two

Uncomplicated and piece of work fine with RR rom, Cheers :highfive:

Sent from my Nexus 6 using XDA Labs

• #3

Htc 10 on viper rom. This breaks fingerprint sensor/home push for me

• #four

Htc 10 on viper rom. This breaks fingerprint sensor/home push for me

Thats weird,

My S8, OP3 and P9 all has fingerprint scanner, and work normal.

Can you try,

Before placing finger on the scanner, turn on your screen first by pressing lock button,

If it managed to scan, and so information technology means it doesn't really break FP, it just the phone go to deeper slumber (since GMS is now hibernated as well) and reject to wake up merely by placing finger.

But if it atill decline to scan even with screen on. Ship me a logcat

• #5

Thats weird,

My S8, OP3 and P9 all has fingerprint scanner, and work normal.

Can you try,

Earlier placing finger on the scanner, turn on your screen first by pressing lock button,

If it managed to scan, then it means it doesn't actually pause FP, it just the phone go to deeper sleep (since GMS is now hibernated every bit well) and pass up to wake upwardly merely by placing finger.

But if it atill refuse to scan even with screen on. Send me a logcat

I don't have any FPs fix but waking screen and using it equally a habitation button does not work and I become no vibration either fifty-fifty though it's set to 90 in exkm
edit give me a few minutes to reinstall and I'll get a logcat for you

• #6

Works bang-up on my nexus 6p, cheers!

Sent from my Nexus 6P using Tapatalk

• #7

and then later on flashing this time I lost root and no cell serviceafter reboot. Looked at your module.prop and from my understanding with v12 modules are supposed to employ versioncode 3 not 1. So I changed it iii and zipped it back upward. Booted into twrp used magiskmount to delete this module and flashed the one with 3 as versioncode and after booting up I have root and cell service and my habitation button is working like it should.

• #8

so subsequently flashing this time I lost root and no prison cell serviceafter reboot. Looked at your module.prop and from my understanding with v12 modules are supposed to use versioncode three non 1. Then I inverse it iii and zipped it back up. Booted into twrp used magiskmount to delete this module and flashed the one with 3 equally versioncode and after booting up I have root and cell service and my home push button is working like it should.

Crap, and so that's where the issue belong,

although am using v1 myself on v12 Magisk, since information technology'southward supposed to have backward compatibility. And then far there'southward no issue.

I think ROM combination might have something to practice also,

but every bit for now i'll update the installer zip.

Thx for the debug!

• #ix

Crap, and then that's where the issue belong,

although am using v1 myself on v12 Magisk, since information technology's supposed to accept backward compatibility. And so far there's no effect.

I recall ROM combination might have something to do as well,

simply as for now i'll update the installer zip.

Thx for the debug!

No problem! Happy to help. If you lot need a tester for anything merely allow me know

Jul 1, 2013

ii,543

1,053

Lyon

• #x

Works successfull, thanks for works :good:

• #11

Hi. I tried installing it. Installation worked and module appeared in the list, but on reboot information technology disappear. I'm on Galaxy Annotation 3 with custom kernel and custom magisk. I've asked if it could be that magisk'south problem, but maybe could be this module mistake?
My rom is Unofficial LineageOS 7.ane.2.

P.S. I also tried flashing it with TWRP without success. I'll endeavor this module in my tablet to check too (Lineage 7.1.2 too).

Inviato dal mio SM-P605 utilizzando Tapatalk

Last edited: May 19, 2017

• #12

Howdy. I tried installing it. Installation worked and module appeared in the list, but on reboot it disappear. I'thousand on Galaxy Notation 3 with custom kernel and custom magisk. I've asked if information technology could be that magisk's trouble, only maybe could be this module fault?

Inviato dal mio SM-P605 utilizzando Tapatalk

Well, all i tin say is that i only test it on official Magisk

But, try utilise the new module fastened, and whether it solve your issue

• #13

Well, all i can say is that i only exam it on official Magisk

Merely, try utilise the new module attached, and whether information technology solve your effect

Only for data, with modified magisk didn't work, but information technology works in both devices with official magisk 12.

And now let'south exam its impact on battery life![emoji1]

Inviato dal mio SM-N9005 utilizzando Tapatalk

• #14

Thanks a lot bro .. Working fine . Improved my battery life a lot :fingers-crossed:

• #16

Works like a charm.
BTW, there is besides Download Managing director which cannot exist optimized. Tin can you add it to your module?

• #17

Works similar a amuse.
BTW, there is too Download Director which cannot exist optimized. Can yous add it to your module?

You do realize if you're downloading a big file and download manager is optomize your download will stop soon after you lot turn off the screen when doze starts. Download manager doesn't produce whatsoever wakelocks or alarms.

• #18

You do realize if you're downloading a large file and download director is optomize your download will stop soon after y'all turn off the screen when doze starts. Download manager doesn't produce any wakelocks or alarms.

Subconscious downloads such as play shop or play services are besides downloaded with this app.

• #19

Hidden downloads such equally play shop or play services are as well downloaded with this app.

What is your point?

---------- Post added at 04:21 PM ---------- Previous post was at 04:17 PM ----------

Hidden downloads such equally play store or play services are besides downloaded with this app.

Download managing director is independent from those services. If everything is optomize, nothing should exist invoking download director in the first place during doze. Thus download manager shouldn't be bothered with the bombardment optomize choice.

• #20

What is your point?

---------- Postal service added at 04:21 PM ---------- Previous post was at 04:17 PM ----------

Download manager is independent from those services. If everything is optomize, nix should exist invoking download managing director in the beginning place during doze. Thus download manager shouldn't be bothered with the battery optomize option.

This is true @Shished

I even put ADM to whitelist. I dont want any of my downloads interrupted when the screen is off or when am sleeping

Thus, it shouldnt be bothered.

Similar threads

Source: https://forum.xda-developers.com/t/magisk-16-battery-saver-6-0-enable-doze-on-google-play-services.3608783/

Share this post