yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Pkt_Lnt:
Has Google Play Service updated as noted in so many posts above that state it makes many changes? It used to be that "icing" was safe to limit, now myself and others get FC. Those who say it does not probably have not gotten the update yet. Check you version against the posts above.
[Xposed Framework Modules] Dovidhalevi:
9.0.* Play Service is a catastrophe, and I am NOT bouncing Icing. I have tried removing any and all bounces touching gms, but to no avail. I have restored the 8.* version, used my phone until it force-upgrades to 9.0.* and all over again!

1. I can try without amplify (temporarily). OK, it is just battery life. Maybe I will unbounce anything and everything Google, leave some limits on some other resource hawgs.

2. Is there any way to pin the play services version, to stop it from upgrading? Even with all auto-upgrades off, it still forced that on me.

UPDATE:

1. Tried bouncing nothing touching Google, Android. No change.

2. Tried with Amplify inactive. No change.
[Xposed Framework Modules] JCCCC:
Can't update to 3.3.7 via Xposed, keeps saying "App not installed"

Moreover, Amplify stop blocking wakelock, literally 0 wakelock was blocked.

Anyone know what might cuz the problem??:crying:

Thanks
[Xposed Framework Modules] BatDroid:
in 3.3.7 updated nothing.

Some users had issues with pro version and dev fixed it.

I tried updating through play store,app installed too.

But crashed right after open.So,I'm still with 336.

And about wakelock i need 2 answer...

1)Free or pro?

2)R u using any other app that pushed Amplify on its blacklist?
[Xposed Framework Modules] JCCCC:
It's pro version.

I do have greenify but Amplify is excluded in the list...

It started acting like this since last night, I wonder if it is caused by the apps updated in google play. You know...messing up your phone is the main feature in every google play update..lol
[Xposed Framework Modules] Dovidhalevi:
Because of all this business with unwanted Play Services upgrades, I have had to freeze out the Play store. Unfortunately, Amplify cannot check that I have bought the full version. All bounces that I had as of the freeze seem still active but I cannot activate or re-activate those that I had canceled.

Alternative?

If I restore a data backup, would that simply put everything back?

EDIT: That did work. Titanium if your friend.

Of course, there are other such apps that check Play for premium features rather than rely on downloadable keys. So the freeze is a very temporary (hopefully) work-around. This Play Services thing is one gigantic pain in the ...
[Xposed Framework Modules] leAndroid91:
I'm facing the same issue.

Google App and Play Services are crashing constantly since the last update.

BUT: deactivating amplify and reboot(!) helped to prevent above mentioned from crashing.

That's of course just a temp solution.

Does anyone have a source to get the last Google Play crap which is working with XPosed and amplify?

Thanks!
[Xposed Framework Modules] Portgas D. Ace:
apkmirror.com
[Xposed Framework Modules] phanipk:
can i limit this alarm

android.intent.action.TIME_TICK
[Xposed Framework Modules] urgali:
You can but your clock won't update
[Xposed Framework Modules] bm_s:
Please help me set up the program properly.

The file BetterBatteryStats-2016-05-20_064515412.txt is located at https: // yadi.sk/i/vx3zMyGwrrpox
[Xposed Framework Modules] TNSMANI:
Even this is a temporary solution. It will auto update again and repeat the earlier behavior.

If you have 'icing' amplified, unlimiting it solves the issue.
[Xposed Framework Modules] JCCCC:
Try release the icing wakelock. In some cases, blocking this will lead to the mentioned problem.
[Xposed Framework Modules] proag:
Is it safe to limit RILJ wakelock? I'm not sure if it drains my battery but it shows up a lot.
[Xposed Framework Modules] NoyNoying:
Hi,

Amplify didn't ask for root. How can I resolve this issue? Please help me. Thank you! ?

Phone History:

Nokia 909>Nokia 5110>Nokia 3310>Nokia 3530>Nokia 5100>Nokia N-Gage>Sony Ericsson W810i>Nokia 5230>LG Optimus One>LG Optimus Black>Samsung Galaxy S3 GT-I9300
[Xposed Framework Modules] MihaiSG:
From your screenshot I can see that Amplify is working.

Check Xposed logs to see if Amplify is working because as far as I know it doesn't show a popup for Root Access.
[Xposed Framework Modules] NoyNoying:
Hi,

I can see this in xposed log. Is it working perfectly? I'm sorry, because I'm new in amplify... Please bare with me... ?
[Xposed Framework Modules] BatDroid:
sure..

just put it on 800-1000s

---------- Post added at 02:51 AM ---------- Previous post was at 02:49 AM ----------
[Xposed Framework Modules] tazzysingh1731:
I'm getting ril_fd kernel wakelock and no deep sleep . Anyone know to how to fix this or disable this

Thanks
[Xposed Framework Modules] TNSMANI:
For kernel wakelocks, only a ROM/kernel change will help.
[Xposed Framework Modules] BatDroid:
check my signature, sir.

I hope u will find things about this WL there. :)
[Xposed Framework Modules] NoyNoying:
Please help me guys....

6 hours 5% lost in battery. How can I improve this? Please help me guys in how to improve battery....

:crying::crying::confused:
[Xposed Framework Modules] BatDroid:
try powernap,greenify and amplify combined.
[Xposed Framework Modules] NoyNoying:
Yep I already installed the 3 applications. What can I edit more in Amplify?

Sent from my GT-I9300 while drinking ?
[Xposed Framework Modules] cbomb101:
Hey guys im getting crashes from the app just from browsing the tabs and pressing on the apps and services and then going back into its menu.

Im using a galaxy s5 marsh mellow
[Xposed Framework Modules] cbomb101:
Um ether 3.3.6c or 3.3.7 not sure. I cleard data on the app and reset it and am blocking less stuff. Ill see if that fixes it.
[Xposed Framework Modules] DB126:
Try search - wonderful tool.
[Xposed Framework Modules] crackers8199:
just updated to the may Android build on my Nexus 6, and it doesn't look like amplify is blocking anything. either that or it's not correctly updating the counters...I don't see anything in the logs except for a few allowed messages. where should I start troubleshooting?

---------- Post added at 05:34 PM ---------- Previous post was at 05:18 PM ----------

addendum (since tapatalk won't let me edit and keeps crashing when I try)...

rebooting seems to have fixed the issue. not sure what was going on there, but let me know what I can do to try to figure out what was going on in case there's a bug that needs fixing...
[Xposed Framework Modules] Cpt.mactavish:
i'm kindda noob.....

do i need to configure(i hate configuring) anything or select apps/bla bla like greenify????

or just install->open->close/...??there says they've a default settings for me.....but,i see only one wakelock is in limited list....then howit is gonna save juice??i'm on free version.....can't it be made automatic(or it's already automatic??like-just install and fire it up and the app will do everything by it's own..no configuring or anything????))
[Xposed Framework Modules] Portgas D. Ace:
Did you even read the OP? Amplify limits the most annoying wakelocks for you (they are location-related wakelocks). Those are the only wakelocks that are limited in the free version. If you decide to buy the pro version, you can manually limit additional wakelocks/alarms and also block services.
[Xposed Framework Modules] Cpt.mactavish:
yep,I've read....but....I didn't understand very much.....

I don't want to do manually.... does pro version do better/more than free( of course automatically :D,don't like to do manually :'( ) ??
[Xposed Framework Modules] Portgas D. Ace:
Well, without your own contribution, there is no proper battery saving. Limiting most of the wakelocks/alarms will result in some drawbacks like delayed push notifications for example. Therefore a default template would not make much sense as everyone uses his/her device in a different way. Therefore it is up to you to decide whether to limit something or not and if yes, to which amount.

And yes, the pro version is definitively worth the money.
[Xposed Framework Modules] aidy.lucas:
For those suffering with CONTEXT_MANAGER_ALARM_WAKEUP_XXXXXXX alarms since the last few Google play services updates. I've got the regex finally blocking the alarms instead of _

ALARM_WAKEUP[0-9] it now needs to be _

CONTEXT_MANAGER_ALARM_WAKEUP_[0-9]

You only need to change the first part

Image of the alarms being blocked below

D2303 5.1 deodexed z2 port+z5+X apps+themes, be,xr,sv,ad,XZRt2urecovery,xposed,z5 cam2.0,xLOUD,S-Force,viperaudio+more
[Xposed Framework Modules] ianmacd:
Until you understand what wakelocks and alarms are, and the potential consequences of inexpertly interfering with them, do not play with a tool like Amplify; not even to the minor extent of installing it and allowing its minimal default configuration to work automatically; and certainly do not entertain the idea of making manual changes.

Wakelock and alarm modification is a low-level operation that, by its very nature, requires that the user spend a significant amount of time reading, experimenting, observing results and fine-tuning. If you're not prepared to do that, leave Amplify well alone. Otherwise, you may find that you quickly get your device into a state that will require even more of you to fix.
[Xposed Framework Modules] Cpt.mactavish:
how much default template can save.....
[Xposed Framework Modules] TNSMANI:
This is becoming ridiculous. I am amazed at the patience of you people.
[Xposed Framework Modules] dimm0k:
what do you mean, you people?
[Xposed Framework Modules] Dovidhalevi:
So, still no progress on getting the Play Store to stop auto-upgrading to a catastrophic version of Play Services (GMS). So have to keep it frozen which means difficult upgrades and no use of paid features on many apps.

Is there a service dedicated to these auto-upgrades (not under auto-upgrade options for most all other apps) that I can simply block using Amplify?
[Xposed Framework Modules] PirateNL:
Had the same problem. Disabling the "nlpwakelock" and "icing" wakelocks fixed it for me
[Xposed Framework Modules] Bobthahog:
I only had to not limit the icing wakelock and it fixed it for me. Would be nice when we are able to limit it again.
[Xposed Framework Modules] crackers8199:
with the latest version of play services (since we can't amplify the icing wakelock), am i safe to deny all icing services? this seems to be working so far and better on my battery than without limiting them, but i'm not sure what functionality exactly i'm giving up by amplifying all of these...

LightweightIndexService

IndexWorkerService

icing.proxy.UpdateIcingCorporaService

SmsMonitorIntentService

AppsMonitorIntentService

search.core.icingsync.UpdateIcingCorporaService

IcingGcmTaskService

PeriodicRebuildIndexService
[Xposed Framework Modules] Docek70:
Can you pass us exact instruction containing interval (9999999)?

Just like this:

Code:

ALARM_WAKEUP[0-9]+

Set the interval to 9999999 seconds.
[Xposed Framework Modules] Dovidhalevi:
Possible victory over the Place Services catastrophe?

Play has a ...SelfUpgrade... service. I denied it using Amplify, rebooted. This did not do the trick :(

I installed a Disable Service utility (root, obviously, required). I did it there. It paused and apparently also brought down three services in Play Services as well.

So far, so good. Hopefully, I can use my phone normally again.
[Xposed Framework Modules] Portgas D. Ace:
CONTEXT_MANAGER_ALARM_WAKEUP_[0-9]+

Set the interval to 9999999 seconds.
[Xposed Framework Modules] aidy.lucas:
What was not to understand, you only need to change the first part rest stays the same or I would of put the complete regex change from-

ALARM_WAKEUP change to-

CONTEXT_MANAGER_ALARM_WAKEUP_

D2303 5.1 deodexed z2 port+z5+X apps+themes, be,xr,sv,ad,XZRt2urecovery,xposed,z5 cam2.0,xLOUD,S-Force,viperaudio+more
[Xposed Framework Modules] DB126:
Why? Icing is not a significant contributor to battery drain. Wakelock frequency and associated duration are not directly correlated to SO wake time. It's only a request. But people will blindly keep limiting wakelocks due to the high counts then complain when their device misbehaves. Oi.
[Xposed Framework Modules] Docek70:
What was not to understand?

I'm sorry, but I'm not an expert, and not all was clear for me.

I know that even the smallest mark may affect the proper operation.

The first part was of course understandable.

The difference is here:

_xxxxx_[0-9] or rather _xxxx [0-9]+

Difference is the line before the parenthesis and plus behind him.

Now I know that the plus is necessary but what about the line after "wakeup" word it hve to be or not? ALARM_WAKEUP[0-9]+
[Xposed Framework Modules] klaidliadon:
The plus is needed, means that the digit can be repeat 1+ times
[Xposed Framework Modules] cbomb101:
When i click on settings in amplify it force closes.
[Xposed Framework Modules] xda26:


---------- Post added at 06:22 AM ---------- Previous post was at 06:13 AM ----------

content://com.google.android.apps.docs.storage.legacy/enc%3DGuWQxr1AO2dLCNZLiK6yW9Fhs2M0wQT-_Efv1CnOhG4EskXW%0A
[Xposed Framework Modules] Dovidhalevi:
yes, indeed.

This is why the statistics presented are of only limit value, can even be counterproductive. Need better instrumentation to safely and effectively touch this stuff (noting that without the most careful implementation, this can be itself a battery hawg).
[Xposed Framework Modules] sensei_sai:
Hi all!

delete
[Xposed Framework Modules] kosmasgr:
Hello Im running rremix 6.0.1 cm13.

Anyone knows what is *launch* wakelock ? Huge wakelock
[Xposed Framework Modules] DB126:
- if surrounded by asterisks you probably don't want to mess with it

- Huge? By what measure, count and duration? If so a poor indicator of actual behavior and impact on battery life.
[Xposed Framework Modules] kosmasgr:
Thanks. Stats for 6 minutes
[Xposed Framework Modules] DB126:
Total misunderstanding of metrics. Go back and read prior posts. A wakelock is merely a request with associated max time duration which may or may not be acted upon. A wakelock that appears once a day can have a far greater impact on actual wake time than one that fires hundreds off times per hour. The latter may (and often does) have zero influence on sleep time.
[Xposed Framework Modules] ianmacd:
It doesn't help that Amplify sorts by wakelock count by default; and even when sorting by time, still colour-codes wakelocks by count, not by time. The app itself is rather misleading in this regard.
[Xposed Framework Modules] grimloktt:
Recently, gmail and Google Play started force closing. I figured out with I disabled amplify the crashes stopped. Does anyone know what setting I need to change in amplify to stop the crashes? Thnx!
[Xposed Framework Modules] aidy.lucas:
If using the latest Google play services, you need to unlimit anything with the word icing in it even if it says safe to limit this you would already know if you'd looked back through the thread a page or two as it's already been covered.

D2303 5.1 deodexed z2 port+z5+X apps+themes, be,xr,sv,ad,XZRt2urecovery,xposed,z5 cam2.0,xLOUD,S-Force,viperaudio+more
[Xposed Framework Modules] DB126:
Yep - in hind sight the red/yellow colour coding probably generates unwarranted concern.

BTW - I hold no absolutely disregard for the dev as it is hard to get a handle on wakelock behavior (direct and indirect) given the general lack of supporting docs from Google and the varying implications by device and app suite. Amplify is simply trying to provide information for the user to interpret and act upon. Dev has provided a unique tool that provides viability to something Google would rather keep under wraps. Two thumbs up for that! :good::good:
[Xposed Framework Modules] arunkafley:
Thanks for the helps with the CONTEXT_MANAGER_ALARM_WAKEUP_[0-9] alarm regex.

Can you please provide me with a regex for limiting android.net.netmon.lingerExpired_xxx_xxxxxxxxx. I got the regex when both are positive but I dont know how to configure when the second numerical part is negative e.g android.net.netmon.lingerExpired_112_-2112734287
[Xposed Framework Modules] aidy.lucas:
Not something I've seen in amplify on my device. I figured the last change in regex out totally by chance to be honest, but have you tried just adding the -minus on the end of the original regex if that's the only difference in the actual alarm/regex.

D2303 5.1 deodexed z2 port+z5+X apps+themes, be,xr,sv,ad,XZRt2urecovery,xposed,z5 cam2.0,xLOUD,S-Force,viperaudio+more
[Xposed Framework Modules] jawz101:
This app has lost its purpose lately. The only hardcoded recommendations "safe to limit" are things that now aren't really safe to limit. More descriptions of wakelocks and alarms should be added in the app as well as maintenance of the "safe to limit" items. It'd be nice if those could be maintained by the community on a github page and refreshed on command within the app. Otherwise, this app requires too much legwork or following a long thread to keep informed of new discoveries in what is and isn't safe.

Please don't take my criticism the wrong way. I could see this app evolve one more time to have a contribution feature or be able to make heuristic, hands-off decisions on how to do what it does.

I get the suspicion taking the recommended steps to limit location things may be messing with my running app lately. Consequently, it's kinda feeling but worth the maintenance. If I truly need to control a wakelock there's probably a checkbox in the questionable app to uncheck. I turn off location history, Bluetooth when not needed, Android Beam and NFC, anything relating to letting Wi-Fi wake up to improve location, permissions to let Google scan for usage, etc. All of the random things like that.
[Xposed Framework Modules] Portgas D. Ace:
There is a community-maintained sheet available in the OP. You can check it and see its recommendations.
[Xposed Framework Modules] krolla03:
I cant find this community maintained sheet you speak of
[Xposed Framework Modules] Portgas D. Ace:
Read the OP again, especially the part called "Additional details" and look for "What are the consequences of reducing alarm and wakelock frequency?".
[Xposed Framework Modules] krolla03:
Haha wow i must of passed it 5 times. Thanks.
[Xposed Framework Modules] TNSMANI:
You can also read these two guides. Just don't limit "icing" though it is recommended. The list is yet to be updated.

http://xdaforums.com/android/general/guide-0-0-hour-idle-battery-drain-stock-t2973588

http://xdaforums.com/android/general/guide-extreme-battery-life-t3095884
[Xposed Framework Modules] m44x:
Facebook Messenger tuning

Hello everyone.

Does anyone can help me to tune Facebook Messenger from waking up my phone so often? What alarms and wakelocks should i limit to get push update period = 1 hour?

Thanks in advance for your replies.
[Xposed Framework Modules] ianmacd:
Search for facebook in the alarm and wakelock screens, and limit everything you see. You may need to tweak things a little to get exactly what you want, but there's no risk posed by experimentation in this case.
[Xposed Framework Modules] BatDroid:
There's package name for every alarm and wl's.

Just limit facebook push/gcm push or something like that.
[Xposed Framework Modules] aidy.lucas:
3600=1hr, 86400=24hrs hope this helps. Setting up amplify is a time consuming thing every user has different usage and different apps installed best way is to start with just user installed apps, social media apps and do not limit anything with "icing" in the title or you'll have problems even if it says it's safe to install Google play services has changed/been updated many times since this and the other battery life threads on here were started.
[Xposed Framework Modules] m44x:
del
[Xposed Framework Modules] kushtech:
Context_manager_alarm_wakeup_xxxxxxx

Just wondering if there is a custom regex entry I can use to block the random CONTEXT_MANAGER_ALARM_WAKEUP_XXXXXXX alarms that randomly pop up since updating to stock Marshmallow.

Every time I limit one of those alarms, eventually a new one with a new number at the end is triggered.

I tried creating a custom regex similar to ALARM_WAKEUP[0-9] but they still get triggered.

I've blocked the contextmanager.service in the services section of Amplify but they still show up in the alarms section.

Any help would be appreciated, its not a critical issue, I just want to know if there is a way to block these alarms.
[Xposed Framework Modules] Pkt_Lnt:
Yes, this post.

http://xdaforums.com/showpost.php?p=66986424&postcount=6867
[Xposed Framework Modules] kushtech:
I feel pretty dumb. I searched for context_manager in the thread search and there were no results.

Thank you very much!!
[Xposed Framework Modules] Pkt_Lnt:
Odd, that is how I found it, but I remembered searching and reading it before because of this issue.
[Xposed Framework Modules] kushtech:
Yes very odd, just tried searching context_manager again and no results.

The following errors occurred with your search: Sorry - no matches. Please try some different terms.

Must be my browser or something.
[Xposed Framework Modules] lepa71:
Is there a way to control Google play services? I have an 9.0.82 version on my VZW S3 running TW 4.3 rooted rom and I have big battery drain for couple weeks now.

I bought pro version long time ago, but never really use it.

Thanks
[Xposed Framework Modules] DB126:
Unlikely icing is the real source but limiting it on GPS 8.xx may prevent the true culprit from running. If you can identify root cause you have a better chance if reining it in. Reverting to GPS 8.x (daily) is a temporary measure at best and not something most people have to do to enjoy reasonable battery life.
[Xposed Framework Modules] methoddon1:
been using Amplify for a long time... devices change, set up stays the same... if you want real Doze, go with Amplify, Greenify, PowerNap. thanx to all devs... battery drain in idle 0.25% per hour still with notifications, sync, data etc.

p. s. wakelocks/alarms drop from 23ph to 7-9ph.

Sent from Galaxy Beast Edge+ (aka Sensei) Powered by Audax Plus M v5 Rom
[Xposed Framework Modules] ianmacd:
What does PowerNap add to Marshmallow, that you don't already get from Doze and Amplify?

I asked the same question a week ago in the PowerNap thread, but no-one seemed able to answer the question. I got the impression that PowerNap becomes redundant after Lollipop.
[Xposed Framework Modules] Bob823:
Correct me if I'm wrong but doze only works while the motion sensors are not triggered, while Powernap will 'force dozing' even when the phone is moved.

Heads up - this is something I read on the topic myself, I can not verify this, just forwarding hearsay. :P
[Xposed Framework Modules] ianmacd:
Greenify has this, too. It's part of the feature called Agressive Doze.
[Xposed Framework Modules] methoddon1:
you got the answer below your post... doze sucks! my brother is a Nexus boy and he gets 14h with 4.5 SOT with so called "doze", (Nexus 6P). these 3 modules work instantaneously on screen off, unlike doze that needs for the device to be flat on the table for 30 minutes to kick in.

doze feature and it's effect is a Myth.

19h Stanby with 7h SOT on Galaxy Edge+ with Amplify, Greenify, PowerNap. that's what I call "Doze".

Sent from Galaxy Beast Edge+ (aka Sensei) Powered by Audax Plus M v5 Rom

---------- Post added at 01:23 AM ---------- Previous post was at 01:12 AM ----------

so why aren't you using it to full extent?! the reason I bought Pro version too. BBS will tell you which wakelocks/alarms you have in details if you tap on stats and you can find them by putting the exact name in Amplify. just start with 240 limitations and see what that will give you. in time, observing, you'll get to a point of satisfaction, with low wakelocks/alarms/drain and all you have to do is make backup of the module/data with Titanium Backup so you can use it on other roms, devices. basically you can call it a one time thing (trying, observing, limiting).

p. s. I'll try dropping a screenshot of wakelocks/alarms below.

Sent from Galaxy Beast Edge+ (aka Sensei) Powered by Audax Plus M v5 Rom