yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Ryya:
For those having issues with version 9 of Google Play Services, I found that the restricting of 'icing' is whats causing the issues. Simply don't restrict this wakelock and everythings fine.

SM-N920C (Note 5) - Dr Ketan M rom - Audax M Kernel - TWRP Recovery
[Xposed Framework Modules] locolyric:
Never amplify icing since this happened.
[Xposed Framework Modules] paulpaul1308:
All Google things continually crashing since yesterday

Yesterday I started getting continual crashes in Google Play Services, Google Chrome, and the search app. Disabling Amplify has stopped this (and enabling it again started it again). Is there anything I can give you to help find the problem?

Edit it looks like it was the Icing issue.

I'm running xceed kernel, cloudyg2 3.3 on LG G2

---------- Post added at 11:50 AM ---------- Previous post was at 11:41 AM ----------

Try not limiting the Icing wakelock
[Xposed Framework Modules] TheXorg:
Feature "request": add a log of recently limited/disabled wakelocks, services, etc. so if something stops working properly you can undo the last changes. Would be a nice-to-have Feature :)
[Xposed Framework Modules] janobarakat:
Fix Gapps when you update Google play service to version 9.0.81

https://youtu.be/i0qoLS3xDeg

Thanks :)
[Xposed Framework Modules] 0850:
RegExp problems

Hello,

I cant get the RegEx function to work and need your help to understand the amplify implementation.

Im using Amplify 4.2 from Google PlayStore on CyanogenMod 12.1

Ive tried several times, read this and other xda posts about it and spent hours at google searching but cant find a clue.

Im familiar with using regex within programming but the regex within amplify seems to work completely different ?!

Within XDA ive found several times the regex ALARM_WAKEUP[0-9]{4,} but even this isnt working

1. Are RegEx limited Alarms shown as limited within the amplify-alarm list?

2. Are RegEx limited Alarms shown as limited within the details dialog?

3. How is the syntax of amplify's regex ?

Following a simple example of a regex witch should work within every system which supports regex (but isnt working within amplify)

.*ALARM_WAKEUP.*

[IMG="RegEx Test"]https://picload.org/image/rgorcrlc/amplify_regex.jpg[/IMG]

Pleasssssse Help :)
[Xposed Framework Modules] SIXAXIS_1:
Save changes

I'm a donator for the app and would be awesome if the app could have some save feature

like all the wakelocks/alarm were changed and saved to google cloud and then if happen a phone wipe

installing the app back and restoring de data would very nice

:o
[Xposed Framework Modules] Pkt_Lnt:
The only way you will possibly get this is to follow the method from post #1.

---------- Post added at 08:22 AM ---------- Previous post was at 08:16 AM ----------

Yes, posts just above yours, much simpler information.

http://xdaforums.com/showpost.php?p=66749750&postcount=6766

http://xdaforums.com/showpost.php?p=66751571&postcount=6767
[Xposed Framework Modules] kushtech:
In the meantime, you can use Titanium backup. I use it often when flashing new ROMs etc.

I just install it and restore the Amplify data and all settings and data are just like it was before.

Titanium Backup can also extract data from Nandroid backups and comes in quite handy at times.
[Xposed Framework Modules] Celestial Fury:
This works. There may be a simple reason why you think it's not working. Did you RESET statistics on the main page? Otherwise, it will keep on showing past alarms/wakelocks that were not limited before your REGEX.
[Xposed Framework Modules] 0850:
I reseted, restarted and checked with better battery stats after some hours. But didnt work.

Also within amplify, occurences are not shown as limited in the list nor within the details as limited

and blocked counter states 0
[Xposed Framework Modules] TNSMANI:
Attaching two screenshots. One showing how I have used the regex and the other showing the result after blocking. The result will not appear under "Limited". It will appear under "Unknown" but will show the count as "0" which means no alarm was allowed. On clicking the entry, in the next screen, you are shown the actual number of alarms blocked.
[Xposed Framework Modules] mrfrantastic:
Since I changed to cm13 "icing" is going through the roof (500/h). Any ideas how to stop this behaviour?
[Xposed Framework Modules] DB126:
Is it keeping your device awake? Or are you just counting wakelocks which are harmless by themselves.
[Xposed Framework Modules] jason504:
Just download this app and donated to. I have been looking for something to control my battery life. I am just going to play around with the wake locks and alarms and see what ones don't shake things up that much. Got to say love the layout and the info on each alarm and Wake lock.
[Xposed Framework Modules] aidy.lucas:
Here try this thread for amplify settings

http://xdaforums.com/showthread.php?t=2973588

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] mrfrantastic:
Not having much experience with MM I can't say for shure if the higher batteryloss is attributed to MM. But icing is also the highest ranked partial wakelock in BBS. So it may not be a real problem, but at least it's showing up way more than before (limiting causes FC on Gapps, as was already mentioned).
[Xposed Framework Modules] mathorv:
[MENTION=526666]cryptyk[/MENTION]

Would you consider adding:

1. profiles

2. exporting/importing rule sets

3. customizable run delay as a safety feature in case of botched configuration

4. comparing rule sets

5. merging rule sets

6. purging rule sets - from nonexistent wake/alarm/services and limited app usability in case of free version

Manual configuration is safe, allows to understand what we do better but it's really tedious and discouraging. Regardless of everything this tool is for power users but why they have pay long configuration time.

I would like to try one configs from one the following guides:

http://xdaforums.com/showpost.php?p=60429417&postcount=4

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

or any other you can recommend.

Time expense in case of this configs is a bit too high for me and most likely for may others.

Sharing profiles would make it more vigorous.

Also there an be experimental feature to download from the cloud profiles uploaded by other users or ones discussed and approved here before.
[Xposed Framework Modules] DB126:
Keep in mind WLs are a request with an associated max time parameter. It is up to Android and (indirectly) the app to decide whether the device is woken. When the action completes the device is eligible to return to a lower power state which is often sooner than the WL request. Once awake the device may busy itself with other unrelated tasks which are often mistakenly associated with the action/WL/app that woke the device.

If you suspect icing limit it for a day and stay off FB or whatever app(s) are FCi g. Obviously this is harder if Play Services/Framework is crapping out. General approach is to peel back the onion until your find the offending layer. Unlikely MM itself is the offender but make be a contributor depending on app cocktail.
[Xposed Framework Modules] Pkt_Lnt:
Ryan has a method for feature requests, follow the method from post #1.
[Xposed Framework Modules] jason504:
I have to say today was the first full day with Amplify and my battery % has increased about 30%. That's with just changing a couple of things. Great app worth the donation to keep this app going strong.
[Xposed Framework Modules] m0han:
i notice that v3.3.7 has been released May 7, 2016, although the op still says "3.3.6 is the latest version, available in the Google Play Store". how's v3.3.7 faring?
[Xposed Framework Modules] phanipk:
hi here is my 8hours idle dump stat. from 100% to 86% in 8 hours of idle.any help??
[Xposed Framework Modules] BatDroid:
no change on the app except updated license check system.

And ryan is busy.
[Xposed Framework Modules] TNSMANI:
Update BBS to 0B6.

Sync took 11+minutes.

The following were the wakelocks/alarms responsible for the battery loss:

com.google.android.gms (): Wakeups: 15 (1.8 / h)

Alarms: 12, Intent: ALARM_WAKEUP243913681

This can be limited by using the regex function of Amplify.

Lots of Flp expiration alarms related to GPS/location. Depending on your use, you can try to limit them.

com.android.server.action.NETWORK_STATS_POLL

Alarms: 6, Intent:

com.boxer.email (): Wakeups: 8 (0.9 / h)

Alarms: 5, Intent: com.google.android.googlequicksearchbox/com.google.android.apps.gsa.sidekick.main.TrafficIntentService

Alarms: 5, Intent: com.google.android.googlequicksearchbox/com.google.android.apps.gsa.sidekick.main.TrafficIntentService

Alarms: 6, Intent: com.google.android.apps.dashclock.action.PERIODIC_ALARM

All of the above can be limited by Amplify but you may lose some functionality. This is an excellent guide for Amplify: http://xdaforums.com/android/general/guide-0-0-hour-idle-battery-drain-stock-t2973588
[Xposed Framework Modules] Leoxur:
Bootloop on Note10.1 WiFi 2014 (stock lollipop) [emoji35][emoji20]
[Xposed Framework Modules] DanielF50:
"Icing" causing FC's with latest Play Services.

[MENTION=526666]cryptyk[/MENTION]

This may be specific to nexus devices (recreated on my N4, N5 & N6P) but I just updated to Google Play Services 9.0.83 and Chrome, GPS, WhatsApp etc are all FC'ing due to the "Icing", wakelock being blocked despite it being in the "safe to limit" list - can anyone else confirm?
[Xposed Framework Modules] Ryya:
You need to rollback your Google Play Services to version 8.x, 9.x is not safe for the limiting of 'icing'.

I have my icing set to 7200

SM-N920C (Note 5) - Dr Ketan M rom - Audax M Kernel - TWRP Recovery
[Xposed Framework Modules] BatDroid:
update killed u, maybe :)
[Xposed Framework Modules] DanielF50:
Sorry, I didn't know this was common knowledge - my 6P decided not to update GPS since March so I had to manually update to 9.0.83. I'm going to turn off the "Icing" block for the moment and see how my battery life performs as apparently it helps with GPS wakelocks and battery usage :)
[Xposed Framework Modules] DB126:
You will likely find icing is not a BD. Yes, it generates tons of wakelocks but a request is not equivalent to wake time or power consumption.
[Xposed Framework Modules] DanielF50:
Awesome - I'll see how it goes for the next few days, so far so good :)
[Xposed Framework Modules] hanschke:
does I need it if I use greenify?
[Xposed Framework Modules] MihaiSG:
Of course, they work side by side to get you better battery life.
[Xposed Framework Modules] phantomblu:
This app keeps making my clock slow. It takes a few seconds whenever I turn it on for the time to update. What's causing this? I didn't turn on any alarms/wakelocks and the problem still happens.
[Xposed Framework Modules] jason504:
Have you tried uninstalling the app to see if it still does it?
[Xposed Framework Modules] hanschke:
[MENTION=6439022]MihaiSG[/MENTION]

you use both at the same time? if so I will give a try if it help.
[Xposed Framework Modules] munraf:
Does anyone else ever have an issue where Amplify will stop blocking all wakelocks and alarms? Xposed log files just state something about "resetting stat files on version upgrade." I cannot seem to find a reason for it, but a restart usually resolves the issue.
[Xposed Framework Modules] phantomblu:
You mean reinstalling it? Yea, it didn't fix the problem.
[Xposed Framework Modules] ayamgoreng:
which one is considered as "Icing" block ?

thank you
[Xposed Framework Modules] marbertshere:
Icing is the name of a wakelock created by Google's location services, I believe.
[Xposed Framework Modules] mineIsAlreadyTaken:
no, 0 = default Google timings. To block as many as possible use a high value - 3600 = 1 wakelock per hour allowed, 7200 = 1 per 2 hours, etc.
[Xposed Framework Modules] jb901:
My Phone freezes when i use v1.1.4 on JB 4.1.2. Other Versions are okay, only the v1.1.4 is buggy for me. Please fix it in the next Version,...
[Xposed Framework Modules] otonieru:
Upgraded to 1.1.4 , and set it to 300,

So far so good, my battery rate from BBS is around 5-7% per hour now,

I combine this with greenify and auto run manager to kill the checkin and event log services

My android batt never been this great. Love it
[Xposed Framework Modules] pugsang:
Hello Ryan,

After 8 hours of yout 1.1.4 version on 4.2.2 it stll shows 0 blocked alarms. Only NlpWackelock has blocked count
[Xposed Framework Modules] KRiZ-R:
Wow, it is working great here on my HTC m8, thank you!
[Xposed Framework Modules] starcallr:
well, I'm back to this version from post #75 (nplunbounce_JB4.1.2.apk) & everthing works perfect/
[Xposed Framework Modules] rignfool:
Request:

Please remove the 'this is working' text from the xposed log...
[Xposed Framework Modules] tangcla:
Is there any consequence of restricting ALARM_LOCATOR and ALARM_ACTIVITY_DETECTION to a higher threshold? I know that NlpWakeLock and NlpCollectorWakeLock can be restricted higher with no ill consequences.
[Xposed Framework Modules] khairulez:
Weird..v1.1.4 on 4.2.2 after more 11 hours.

Tap via Tapatalk
[Xposed Framework Modules] swedkg:
Working great on my Moto G, a big "Thank you" to the developer!! A beer is on your way!!

In a next version, if you have the time, could we have a 'reset' button for those counters, and/or better organise what they actually represent (since NlpUnbounce was installed, since phone boot, when screen was off blocks, etc). I believe it could help us better understand what is really happening under the hood.
[Xposed Framework Modules] markrs:
Hey Ryan, thanks for the great work, have sent you a small donation as a thank you.

Mark
[Xposed Framework Modules] RASTAVIPER:
At my stock 4.4.4 , Android System at battery stats recently got around 30%.

Could Nip affect it?

Also all block times are at 0. Stock Nip settings. No wakelocks in BBS though.

Unleashed by my Nexus 4
[Xposed Framework Modules] pugsang:
[MENTION=526666]cryptyk[/MENTION]

Can a newer version of the module handle that GTALK_ASYNC_CONN Wakelock? I see huge wakelock numbers in both BBS and WLD despite the fact that Google Talk is uninstalled
[Xposed Framework Modules] Mistertac:
Little Off Topic for this thread but just to answer your question you could get something like Auto Run Manager or use ROM Toolbox Auto Start Manager and disable GTalk receivers and that should get rid of that for you.

- Tapatalked from the G3
[Xposed Framework Modules] nIGhT-SoN:
I had a strange thing happening. Few days ago I was looking at battery stats (default from Samsung) and Android OS was using a lot of CPU, it showed CPU usage for more than 5h almost 6h in 1 day and 10h of running and didn't showed any data sent or received, while Screen was on for 1h and 50min. I thought there were apps that was doing this and tried removing some, but still no change in cpu usage by minute. Then I tried deactivating NlpUnbounce v1.4 see if there is a difference. As soon as I rebooted my phone Android OS showed 3h and 20min of CPU usage and also some data sent and received.

I must say I tried a lot of reboots before deactivating this module thinking there might be a glitch or something. I'm gonna test without this module if I get that much CPU usage. Usually I didn't had that much CPU usage on Android OS. It used to be on 3-4th place in the list, after Screen.
[Xposed Framework Modules] pugsang:
Agree. I could also do the same thing with Receiver Stop xposed module by defim. But the OP said that this app could become a one stop for battery drainers and since it is a part of GSF I thought to make a suggestion. It doesn't need to have 2 or 3 apps to do the job that could possibly be done with one app
[Xposed Framework Modules] Kocane:
Not really when the OP mentions that he is willing to look at any other battery killers :)

Gtalk doesnt even exist anymore, does it? Hangouts might still be called gtalk in code.. but afaik that "gtalk" service is what takes care of push notifications. I might be wrong.
[Xposed Framework Modules] Mistertac:
Well make no mistake I wasn't scolding the other guy for mentioning that.... I was just referring to getting into another app like Auto Run Manager.

I'm the king of being Off Topic lol so I was basically just trying to respect the OP here.... As far as GTalk goes I have no idea. I just know that it was still doing something behind the scenes..

- Tapatalked from the G3
[Xposed Framework Modules] pugsang:
WLD and BBS both are reporting GTALK_ASYNC_CONN. I do not have Hangouts installed.
[Xposed Framework Modules] Mistertac:
I also don't use Hangouts... I remove it

- Tapatalked from the G3
[Xposed Framework Modules] MihaiSG:
[MENTION=453210]hanschke[/MENTION]

Yes and I also use PowerNap.

Here is a guide for them:

http://xdaforums.com/android/general/guide-extreme-battery-life-t3095884
[Xposed Framework Modules] marbertshere:
Hi, so the ICING wakelock is draining my battery. Obviously I can't amplify it. It's that's anything else I can do? I've heard that it's related to Google Messenger but that isn't confirmed. Anyone have any extra input? Thanks!
[Xposed Framework Modules] DB126:
Why do you believe icing is the source of battery drain? Understand it generates tons of wakelock *requests* (and associated max time period) but that does not necessarily equate to wake time. Wakelocks are hugely misunderstood. They're not bad.
[Xposed Framework Modules] tangcla:
Got a new wakelock from Google Play Services since the venue 9.0.83 update BeaconBle_WakeLock. Does anyone have knowledge on this wakelock?
[Xposed Framework Modules] hanschke:
@ MihaiSG

I look for the guide and have to read much stuff.
[Xposed Framework Modules] marbertshere:
Well I look at my idle dump from BBS and it's telling me that my phone is around 10% awake when my screen is off. The only partial wakelock that continuously appears at the top of that list is icing. It might read as icing holding 10 minutes of wakelocks while the next highest wakelock is about a minute in total length. So I assumed that's what is keeping my phone awake for the most part. Am I wrong?
[Xposed Framework Modules] hanschke:
A community sharing prefs will be nice for the pro version to safe work ;)
[Xposed Framework Modules] Pkt_Lnt:
Post #1 has a link for feature requests.
[Xposed Framework Modules] proag:
Hello, could you please tell me which location wakelocks/services/alarms are responsible only for location stuff? I don't use location services at all so I'd like to disable/limit them all. Thanks!
[Xposed Framework Modules] Ryya:
I found that as I now had to enable ICING on the latest version of play services. I disabled the Service ....pendingintentcallback service from Google, the drain appears to have ceased.

SM-N920C (Note 5) - Dr Ketan M rom - Googymax Kernel - TWRP Recovery
[Xposed Framework Modules] jten9:
Edit- Oops sorry all, accidental post, please ignore/delete!

Sent using Tapatalk
[Xposed Framework Modules] DB126:
A wakelock is simply a request to defer 'sleep' if work needs to be done. The associated time represents a max window; if the task completes sooner the device is free to migrate to a different power state if conditions permit. If no work is needed the device will generally remain it the same power state it was in prior to the wakelock firing. Note: once the device is woken other background tasks are free to execute pending tasks even if they have no associated wake lock. The resources consumed by those tasks are often mistakenly associated with system wakelocks.

Is icing the culprit? Don't know but likely not. Better to go after the underlying service, receiver or alarm.
[Xposed Framework Modules] Dovidhalevi:
Play services gets worse and worse and also less and less stable with every upgrade! How might I defeat its upgrades, stick with a reasonable version?

Worth checking out!!

The last upgrade is keeping my phone awake even though I have that permission turned off!! for play services. Seems to work and now well eat the battery without permission.

I have had icing on and off. Never a big hit in any event but staying away because of Play Services instability.

I think this clarification of wakelocks is very valuable. The numbers shown in our statistics are for all intents and purposes meaningless. And the absence of chosen and unchosen alternatives with 0 statistics is not the best idea either. Still tied to trial and error and errors can be not-so-lovely.

I have not upgraded the module because I have no use for regular expression alarms and the process of upgrading is kind of scary. The module needs a better, more normal, upgrade path, and simply needs more useful instrumentation! (Hint: instrumentation is a battery hawg, unless done like in Tasker: settable intervals. Defaults to 10 minutes with screen off.)
[Xposed Framework Modules] Crayvolt:
why 3.3.7 crush without google apps services ?

because for billing ?

when i remove gapps in lolopop it doesnt work but if gapps exist then amp 3.3.7 works without complain. huhu:) please help

I realy realy like it make my battery last for 4 to 6 days

Please Ignore if it is just a nuisance.but ilike if someone help me to use amp without gapps

sent from ancient s3 mini.
[Xposed Framework Modules] phoberus:
A backup and restore function would be great in pro version. So I could import all settings when I clean flashed a rom :)
[Xposed Framework Modules] Pkt_Lnt:
Look in post #1 for the link to GitHub and feature requests. This is in there already. It has been requested many times and you can upvote it. You can also restore with TiBu which has been answered many times in response to the many requests for this feature. Use the GitHub link, as this message will be lost soon, just like the dozens of requests already made that you did not see. ;)

---------- Post added at 07:41 AM ---------- Previous post was at 07:39 AM ----------

Keep in mind that when you look at each wakelock in the list, at the bottom you see the number of wakelocks allowed and blocked,

but also the amount of time allowed and blocked

. This is very valuable for evaluating each one.
[Xposed Framework Modules] TNSMANI:
I believe it is related to BlueTooth.
[Xposed Framework Modules] DB126:
Also wakelock time allowed does not necessarily (usually does not) equate to actual 'wake time' as the targeted task generally completes in a fraction of the (max) time requested by the corresponding wakelock.
[Xposed Framework Modules] TNSMANI:
It is here:

http://xdaforums.com/android/general/guide-0-0-hour-idle-battery-drain-stock-t2973588
[Xposed Framework Modules] Bobthahog:
For some reason amplify is not working with the new Google play services update. 9. 0.83. It makes Google Play services stop and then it makes chrome shop and then Gmail stops. It happened on my Note 5 and S6 after they both received the new Google Play services update. As soon as I made amplify inactive n Xposed everything worked fine again. So I don't know what the issue is with the new update but it does not work so hopefully he will push out an update to make it compatible with the new Google play services.
[Xposed Framework Modules] Pkt_Lnt:
Post above about this point to icing.
[Xposed Framework Modules] kurtextrem:
Same here. But they don't crash always. So it must be a wakelock / alarm we both have amplified.
[Xposed Framework Modules] azsl1326:
What would cause me to get a wakelock from clock? I have never used the alarm clock functionality.
[Xposed Framework Modules] aidy.lucas:
You can limit it no problem, till you try and use anything Google related(chrome,Google app,Gmail, ect) on your device then it just has a fit. The icing wakelock is the only one I've un-amplified and so far so good no Google play services has stopped ect.

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] Pkt_Lnt:
What do you see in the very top right of your screen shot? ;)

It checks to see if alarms are set, even if you don't have one set. If it did not, a set alarm would not sound.
[Xposed Framework Modules] azsl1326:
I have had the phone for six months. This is the first time that I have seen this wakelock.