yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Celestial Fury:
Is it Whatsapp Plus? With the normal Whatsapp my messages come through just fine with default and many others amplified. Also #3680

It just means this alarm is activating after every 420 seconds (that you set) so Amplify doesn't catch it. Increase the time to a longer period.

That device has been awake for 16 hours. I don't think that's idle time. There are a lot of apps being used during screen on time and that's how it's supposed to be.
[Xposed Framework Modules] cAase:
It's Whatsapp, I'll try making it longer.
[Xposed Framework Modules] xator91:
So what i need to do?
[Xposed Framework Modules] Mistertac:
To tell if it's truly a problem, like a rogue app or two, or if the phone has just been in moderate to heavy use, we'd ideally like to see that info when your phone is idle.

For example, charge it up to 100% , then leave it unplugged over night, when you wake up the first thing you should do is either take those screen shots again or possibly use Better Battery Stats and get a dump file.

Now those two apps do have their own threads, but you are trying to use that info together with this module so I suppose it's still on topic.. So if you could do that it'd be much more helpful. Like the other guy said, your phone appears to have had some moderate to heavy use from looking at your screen shots.
[Xposed Framework Modules] Celestial Fury:
Charge it to full, then leave it idle overnight for at least 6 hours (while you sleep). Then post your stats.
[Xposed Framework Modules] Javi22:
To be honest, I'm confused... Because yesterday I got the issue again, with amplify disabled. But then the delay was not so huge, it was about 3min at most, and not all the time, only sometimes...

I am really desperate with this annoying thing, not sure if it's amplifys fault or what. Now I've installed amplify again, will need time to check what happens now

If you notice something or has some ideas about this, let me now please. Let's see if the issue comes again for you (I noticed it one or two days after disabling amplify)
[Xposed Framework Modules] topbasework:
It is normal..global show 0

Already reset 2 3 time
[Xposed Framework Modules] Mistertac:
In Settings you must have Global Stats turned off maybe?!
[Xposed Framework Modules] Tinchoska:
Guys, can I use this module with greenify at the same time?
[Xposed Framework Modules] Mistertac:
Sure can. Just don't Greenify Amplify and don't Amplify Greenify [emoji16]
[Xposed Framework Modules] Celestial Fury:
No need to Greenify Amplify because Amplify doesn't cause drain and you might stop it from working but I do Amplify Greenify because Greenify causes a slight drain.
[Xposed Framework Modules] Tinchoska:
The latest releases cause drain, 2.4 not... Do I need to know something about amplify? Or just leave it as it came by default and it'll be enough?
[Xposed Framework Modules] Celestial Fury:
Depends on how much of a drain you want to stop. I'm on Greenify 2.4.4 and if it's not amplified, I won't get < 0.1%/hour idle drain. Use BBS to see what's causing drain then amplify it. Check before and after the defaults as well as before and after installing Amplify and see if you're satisfied.
[Xposed Framework Modules] evo07:
Any chance to working with 4.1.2 on HTC One S c2?no wakelocks detected

Wysłane z mojego GT-S7710
[Xposed Framework Modules] mwrobe1:
Just wanted to share with the KB here. Had an issue with my SGH-I747 4.4.2 NJ1 getting a bad wakelock drain from ConfigFetchService...which, as I found out had to do with Google Fit/Wearables.

I will NEVER use this functionality.

Credit to the OP here: http://xdaforums.com/showpost.php?p=55640325&postcount=5

Service listed as: com.google.android.gmx.config.ConfigFetchService

I also denied any service with wearable in the name. I'll give this a couple days and try to measure impact.
[Xposed Framework Modules] cryptyk:
Please try pushing the RESET button on the home screen, then rebooting.

Thanks,

Ryan
[Xposed Framework Modules] evo07:
I'm trying

Wysłane z mojego HTC One S
[Xposed Framework Modules] Rodrigoleveck:
Doubt

Hi, i´m from Brazil, sorry for poor english, congratulations and thanks for the great app, but i have some questions about how to configure the seconds in the app.

Reading the description and FAQ I understand how it works for the alarm, it delay for the amout i stipulate.

However the wakelock has a diferente function, it holds the gadget awake for some time, my doubt is: am i changing the time for it to still awake? because if this is the point isn´t it better to unchange the time or enter a lower time rather than input a 240 seconds time?

I really did´t get it, because you explain how wakelock works, but in the app configuration it shows "allow every ______ seconds" it realy make sense for allarm, but isn´t the wakelock wake by an allarm? So how this "allow every ______ seconds" works for the delay on wakelock?
[Xposed Framework Modules] SignetSphere:
The reason it's configured to be "allow every _____ seconds" is because the overall android system still "needs" those wakelocks to trigger. What this app does is it limits the amount of time that specific wakelock wakes the device so that the device will save battery. However there are cases after a lengthy study by the contributors (like 1cebox for e.g) some wakelocks can be disabled entirely if you set it to "0" on the allowed time (refer to the spreadsheet posted on the first page for more info).
[Xposed Framework Modules] TNSMANI:
I note that the device was on battery for 16+ hours with a SOT of 3.5+ hours. You have 36% battery left. I don't think that you have a huge drain problem notwithstanding the big numbers in Amplify.

So before jumping into Amplify to limit the wakelocks and alarms, please evaluate your device's drain and only when it is bad, you should need Amplify.

Contrary to what is stated here about the battery drain due to Amplify, I get 2% to 3% drain due to Amplify consistently. Greenify doesn't even figure in the battery drain list.

Having said that, I am still using Amplify because I get 0.3 to 0.4% drain while idle, only when I use Amplify and Greenify.

So thanks again to the Dev.
[Xposed Framework Modules] Tinchoska:
Can you tell me anything about those wearable things?
[Xposed Framework Modules] Pkt_Lnt:
Do you have access to Google Search or YouTube? Search "android wearable". Millions of hits.
[Xposed Framework Modules] DiscoTuna:
New maps made some default wakelocks and alarms disappear

Anyone else seeing this? One of the alarms and one of the wakelocks is gone.
[Xposed Framework Modules] Mystique:
What is more of a concern?

The numbers on the left or the right?

The 4750 or the nine minutes?

Thank you in advance.
[Xposed Framework Modules] Smultie:
The nine minutes!
[Xposed Framework Modules] kagwind:
The same thing happening to me, busy busy busy :P

Good to hear that you are still continuing this project.

Too bad I've switched to Lollipop and can't use Amplify (for now). :(

I updated the translation a little bit on poediter (the only thing I can do), you might want to pull that in your next release.

Have a good life, Ryan!

PS: Forgot to mention that after updating to Lollipop, some Google wakelocks stop plaguing, such as the ConfigFetching one and the Proximity one. Hope Google will not create more problems.
[Xposed Framework Modules] Celestial Fury:
Whichever wakelock that shows up higher in BBS is more of a concern. That said, duration of wakelock usually causes more drain than quantity of wakelocks.

Stop amplifying according to Amplify and start amplifying according to actual battery drain.
[Xposed Framework Modules] Lucas Eugene:
And this is why I'm going back to kitkat
[Xposed Framework Modules] magnamentis:
worthless

without providing the runtime, matter of factly both, the questions as well as the answer are worthless.

why ? because if the values are let's say for a month of runtime they are good for a day they are horrible, while 9 minutes for almost 5000 wakelocks is not that bad, it means just a fraction of a second ( 0.1xxx ) per wakelock which is not the problem. so far i disagree with the answer and the number itself is the problem here, provided the uptime is shorter than let's say 3-4 weeks which i assume is the case. further i don't really understand the question, no matter which is worse or more important, if you amplify the wakelock down to reasonable numbers the time problem will be gone, so first limit the event and only post if you don't succeed or run into functional problems due to limiting it. everything else is clogging the thread IMO
[Xposed Framework Modules] cAase:
Does anyone have an idea which ones of these could cause this issue? In 30 percent or times I don't receive any updates until I enter Whatsapp or waking the phone from deep sleep.
[Xposed Framework Modules] LiL_Assassin:
Hey guys, and developer for this app. It's. Amazing, and I donated to you right away :) I may donate again if I can get this problem sorted. Does BBS still display the weird readings? Because I put RILJ under 0 seconds and a few other services/wake locks under 0 seconds. And they still persist. And the reason why I am concerned is because when my phone is in deep sleep it takes a little bit to come on. When RILJ is currently affecting it will not go into sleep. Even with amplify
[Xposed Framework Modules] shuklendu:
How allow every ... Seconds affect battery?

If I set 600 seconds instead of default 240 for 2 alarms and 2 wakelocks in basic free version then will it save more battery ?
[Xposed Framework Modules] 1ceb0x:
None. You greenify Whatsapp?

You need to put a value, not 0 (i.e 240, 420)

In theory yes.
[Xposed Framework Modules] magnamentis:
first i just wanted to write one word: "kindergarten" because most learn to read after that in school.

but then it came to my mind that the typical age of spoon-feeding is around the age of 1 and that's way pre-kindergarten

so to me it looks that things are clear to those who are able to read and are willing to follow advice and work a bit for themselves and what remains is poorly educated kids.

i usually try to restrain myself because it usually does not pay of to write things like that but from time to time i take the liberty and give a ......
[Xposed Framework Modules] LiL_Assassin:
Yep, i thought i read somewhere if you put it to zero, it would get rid of it completely, but i understand now thankyou :), could anyone recommend me some services to stop? that would be safe to do so. or other options
[Xposed Framework Modules] MIKEMON:
Each is different

you need to test what is good for you
[Xposed Framework Modules] daltonhrrll:
Normally after 6 hours my device is almost dead but after playing with amplify for a little bit I've gotten pretty good results.
[Xposed Framework Modules] metuskale:
Missing it on Andoid L :( :( :( :(
[Xposed Framework Modules] 777.300:
Ryan, thanks for this great app. Have been using it successfully on my Nexus 4 and 7. Just switched to Android 5.0 and I hope to see your app working on lollipop in the future. Good luck and thanks for all your effort and time you have put in to this app.
[Xposed Framework Modules] schlager P.:
strange, been silent for a while 'cause reinstalling rom stopped the flight mode drain, but now it's back (14% in 8 hours of flight mode) without doing anything(installing apps or something). I don't notice any new wakelocks/alarms in bbs.

Sent from the den of inequity
[Xposed Framework Modules] LiL_Assassin:
Try a different kernel maybe? I am using dorimanx unnoffical 005
[Xposed Framework Modules] Köhvwezd:
Another one here missing Unbounce (old habits die hard, can't change the name in muh mind) on 5.0 :(

Edit: So I took to myself to finish up the finnish translation, done with that now, might fine tune it later
[Xposed Framework Modules] tcchuin:
I've donated 1 dollar before and I can't seem to be able to use the custom setting now. what can I do?
[Xposed Framework Modules] mafsi:
I put some k9 wakelocks under 300 limit. No efect so far. Turning on the syncronization k9 reacts instantly with no delay. See the screenshot wakelocks started with Core..

If any of You can share best practices for k9-mail & facebook messenger it will be great.
[Xposed Framework Modules] marbertshere:
Hi, I'm noticing that I'm receiving very delayed push notifications from some Google apps (Gmail and G+, specifically). I've only amplified location wakelocks in addition to GCoreflp, URL dispatching service, and a backup.intent.run alarm. The spreadsheet didn't mention push notifications when it comes to these. Anybody have any ideas, please?
[Xposed Framework Modules] dimm0k:
don't think it's anything to do with Amplify... I've been noticing delays in GMail too, not incoming e-mails... but if I read a message on the device it's never marked as read on the web... is that happening to you too?
[Xposed Framework Modules] cryptyk:
Hi all,

I just posted 2.0.7. It includes:

- Sorting by package name (Thanks to [MENTION=4354573]chhapil[/MENTION] !)

- Updated translations

- Bug fixes

Thanks!

Ryan
[Xposed Framework Modules] marbertshere:
No, I'm just not getting notifications until many hours later. I could go into gmail and manually refresh it, and I would probably have new mail right now.

Your issue sounds more like a delay in syncing your gmail. Check out your sync settings and make sure you haven't amplified anything like that.
[Xposed Framework Modules] grisu59964:
I tried version 2.0.7, but it refuses to work. Always tells me that it is not activated. :(

Reverted to 2.0.6.

Thanks for your work anyway :)
[Xposed Framework Modules] trancinguy:
N5444

Hi, I think after the update Audioin has switched places with Audiomix. In the safe and not safe.
[Xposed Framework Modules] Celestial Fury:
Not willing to find out why then? Are you on Lolipop? Is the module checked in Xposed? Have you rebooted?

My Audioin is still in the Not Safe place.
[Xposed Framework Modules] grisu59964:
Of course I rebooted, but the check fails. Is it working on your device? Have you loaded the update from the Xposed repo or from the Play Store?

As long as Xposed does not work with Lollipop, I'll stay on Kitkat.
[Xposed Framework Modules] TNSMANI:
+1! I also will wait for Xposed compatibility with Lollipop.

Installed Lollipop in my Nexus 7 and immediately missed Gravity Box:(. Sometime later, missed Greenify and a day later missed Amplify:(. In addition to that, the device became laggy. I think that the 1 GB RAM is not sufficient for Lollipop.:crying:

So removed Lollipop and reinstalled KitKat and everything is back to normal.:D
[Xposed Framework Modules] Celestial Fury:
I updated from Play Store and rebooted once. You haven't mentioned if the updated module was checked in Xposed. It's a little thing but we have to go through the process of elimination. Did you also check Xposed log for errors relating to Amplify? I'm just saying you gave up too fast.
[Xposed Framework Modules] grisu59964:
Thanks for trying to solve my issue :) I checked my device for the typical errors before I posted my issue, thats why I dod not write about an unchecked module (which was not part of the problem).

So I downloaded version 2.0.7 once again. This time from the Xposed repo. Now it looks like everything went fine - no error message when I open Amplify. So it's hard to reproduce what the problem was and it was the first time that reapplying the update solved the problem. Maybe it solves the issue for someone else, too. Thanks anyway :)
[Xposed Framework Modules] Cyclu:
Hi Ryan! Updated from version 2.0.6 to 2.0.7 rebooted twice (sometime it helps to fix certain issues with Xposed modules)

1) We don't have anymore service stats of course with "Service Blocking" enabled in settings.

2)it lacks the scroll bar in alarms category.

I know it has been discussed before can you please give us the possibility to exit the application from home screen (like for others app's) I prefer for now: go to category then return to home each time to not spend all used category to go back to home. With both method that's a lot of clicks and It's really annoying.

Thanks in advance and sorry for my translator English.
[Xposed Framework Modules] FrozenLord:
Could you please implement a search view?

This view could search for the entered letters/words in alarms, services and wakelocks and display them separately, e.g. by separating the results with a dash.

I am having a hard time when trying to block a single service because of those ridiculously long names.

Feel free to pm me if you'd like to read my specific ideas about implementing this feature :)
[Xposed Framework Modules] Javi22:
Totally agree :)
[Xposed Framework Modules] dimm0k:
just curious how Amplify stores its data. are new alarms and wakelocks automatically stored with the default of 240 even if they aren't limited at all or do they get stored the first time you turn on limiting?
[Xposed Framework Modules] Celestial Fury:
Turning the phone landscape triples the amount viewable. Haven't had a problem with this method so far.
[Xposed Framework Modules] dimm0k:
just a note, mainly to myself, and I suppose for those maintaining the spreadsheet and request for any information available on what I have listed...

alarms

com.devexpert.weather.pfx.WAKEUP - 600 (first reported by magnamentis) - confirmed working great

kept mine at 600 to keep it evenly divisible within an hour.

com.syntomo.email/com.syntomo.exchange.EmailSyncAlarmReceiver - 600 - confirmed working great

used by MailWise for Exchange accounts. tested this one for more than a few weeks with no adverse effects. e-mails still arrive almost instantly. kept at 600 to keep it evenly divisible within an hour.

com.sec.ims.android (com.samsung.rcs.framework.alarms.action.registerrefresh) - 480 -

still testing

anyone have any idea what this is for or what's using it? searches have not turned up much information other than it being a bit troublesome. not too bad on my device, but...

wakelocks

!32@/B4Tb64 ... / QSxQT ... [wechat] - 240 - still testing

BbmPlatform - 600 - confirmed working great

used by BlackBerry's BBM chat client. tested this one for more than a few weeks with no adverse effects. messages still arrive almost instantly. kept at 600 to keep it evenly divisible within an hour.

com.carrieriq.tmobile.Wakelock - 240 - still testing

anyone have any idea what this is for or what's using it?

Thanks to [MENTION=4403217]Pkt_Lnt[/MENTION] on the post below I've frozen the related files dealing with CarrierIQ to disable (hopefully) CarrierIQ and this particular wakelock.

MAIL_SERVICE - 600 - confirmed working great

used by MailWise for ??. tested this one for the last couple of days or so with no adverse effects. e-mails still arrive within my specified sync time of 10 minutes. kept at 600 to keep it evenly divisible within an hour.

NOTES:

looks like setting a default of 240 for the wechat wakelock helps noticeably! chats are still coming through and wakelock has dropped dramatically.

the following alarms com.syntomo.email.intent.action.MAIL_SERVICE_WAKEUP and com.rim.bbm.ACTION_PLATFORM_WAKEUP_ALARM look like they break MailWise and BBM respectively. using the default of 240, no new mail arrives and no BBM messages come through.
[Xposed Framework Modules] Celestial Fury:
You actually typed out the names? Looks like the names still can't be copied to the clipboard. I was rather looking forward to it.
[Xposed Framework Modules] dimm0k:
lol, unfortunately I did type them out... figured I might as well since it was a short list and it'd be good in case I lose the settings on my device so that I could look this up and restore in the future...
[Xposed Framework Modules] cryptyk:
Thanks for the feedback.

1) I took those out because they were confusing people. Blocked service counts don't really mean much anyway. You can still find them in the individual services.

2) Weird. Are you sure you have enough alarms to fill up the page? And it doesn't scroll?

3) The back button behavior is actually consistent with Google's UI design principles. If you look at Play Store or Google Music, it acts the exact same way. I don't really like it either, but want to follow the guidelines.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
I have search on the list . 2.0.7 was just a small bugfix release. I'm SO busy at my day job right now and haven't had time to do a lot with Amplify.

Thanks,

ryan
[Xposed Framework Modules] cryptyk:
Wakelocks, Alarms, and Services are all collected by default, but not limited at all.

You need to limit them to have any effect.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
I know it's painful. I'll try to find time this week to make another small release with this.

Thanks,

ryan
[Xposed Framework Modules] dimm0k:
[MENTION=526666]cryptyk[/MENTION] oh, that I know. I was just wondering if the default time of 240 is saved along with the collection even though it's off or are the times saved only after it's been limited at least once?
[Xposed Framework Modules] blumenkasten:
Sometimes you have disable modules in Xpose and reenable after updates. This is a bug in Xpose.
[Xposed Framework Modules] cryptyk:
Oh, I see. It's only stored once you limit the alarm once.
[Xposed Framework Modules] shinra00:
hi there i was playing with my wi-fi configs and noticed that there is a Wi-fi optimization.

I usually get whatsapp messages pretty delayed or even when i turn the screen on. I unchecked this option and for one day i haven't noticed any delays.

I browsed a bit on the web and found that disabling it helped someone else receiving the notifications on time:

http://www.pocketables.com/2013/10/...ing-trouble-using-certain-apps-over-wifi.html

and got someone to get less wakelocks and better battery in idle - like amplify :D

http://www.reddit.com/r/Android/comments/2dzwjb/tip_disabling_wifi_optimization_may_give_you_a/

hope this helps

ps. sorry for posting external links but both of them explain much better than i did

ps2. can any pro comment on the better battery effect please?
[Xposed Framework Modules] marbertshere:
Thanks, I'll give it a try.
[Xposed Framework Modules] Cyclu:
Ok just wondering why they are not there.

2) No I misspoke I can scroll but this blue scroll bar (see the screenshot) turns sometime to gray.

I have rechecked for the moment it still blue.

3) What amazing choice by Google:eek: but anyway I use every day Play Store and I'm sure I can exit from home page or maybe you can add "exit" to lateral menu under settings.
[Xposed Framework Modules] naughty6t9:
I had purchased the app earlier and I am on latest play store. Y m I facing this error
[Xposed Framework Modules] VoLTaqe:
If you cut google play store service with greenify turn back to stock setting (inapppuchase)
[Xposed Framework Modules] naughty6t9:
i degreenified the play store how do i turn back stock settings in app purchasse, i just cleared data/ cache of both the applications, still facing same issue, if i click to purchase app again, it says unfortunately amplify stopped working..
[Xposed Framework Modules] cryptyk:
I would try to uninstall and reinstall Amplify from the Play Store.

Thanks,

Ryan
[Xposed Framework Modules] jonatutu:
I am not using nfc and i have set the timer to 1day. I read in the thread that setting timer too high might not be good as it will call on the app and keep retrying thus resulting a higher battery usage instead. I have attached a screenshot can someone helo to check is it ok?
[Xposed Framework Modules] naughty6t9:
Still same error while opening.. If I click to buy app again it closes saying unfortunately stopped. .

I just reflashed the same ROM again after a month, as phone went for repair it updated from unbounce to Amplify. And this error started .

I had a premium app earlier. Is there any workaround now