yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] zyrgoth:
Hey.

all wakelocks that should be blocked by your module, and yes they are climbing according to WLD. with module working i get very few.. lets say 100 or sth like that, but after i've reset the counter I got nearly 1,5K of them over night.

btw. it is totally reproducable every time on my phone.

1. reboot.

2. check WLD , wakelocks happen according to settings in your module and they are very few

3. open your module, reset counter

4. check WLD, wakelocks every minute as without the module

5. open module, counters at zero

6. reboot,

7. check WLD, same as #2

tried it 5-6 times over couple of hours to be sure.
[Xposed Framework Modules] cryptyk:
Got it. Thanks for the detailed steps. I'll try to reproduce locally and get it fixed.

Thanks,

Ryan
[Xposed Framework Modules] rignfool:
Is your module installed to internal/phone.. And not external...

Xposed will not load modules from external SD... Because of when the OS loads the external... Its too late for xposed to 'activate' the module...

EDIT: FOR ALL USERS!
[Xposed Framework Modules] starcallr:
I'm having kind of a different problem here: if I use v1.1.4 on a 4.1.2 rom, my phone randomly just freezes/

not while using ne special app, just randomly/

I have to remove the battery to get back to normal/

if I use the version from post #75 (nplunbounce_JB4.1.2.apk), everything is fine/

I went back & forth like 6 times to make sure it is really the newer version of the app (because nobody ever mentioned nething like that)/

it might work for a few hours, but eventually it'll freeze/

so now I'm back again to the above mentioned version/

I really would like to run the new version with the counters, but the freezing thing gets annoying with time.....
[Xposed Framework Modules] MIKEMON:
must be on the phone and is fully functional.
[Xposed Framework Modules] zyrgoth:
yes i know that.

internal only
[Xposed Framework Modules] folusmile:
Great work

Pls does this great module has user interface? Like setting. Cos mine doesn't show up... Oh sorry I got it. Nice job gat to donate
[Xposed Framework Modules] Solace50:
would the setting of 0 be equivilant to wakelock terminator? or is that something different. is it because of nlpwakelockcollection being blocked by wakelock terminator that its eliminated the former ALARM's not to trigger anymore? im just curious/trying to figure out if this provides any befitit to my current setup in regards to GPS waking the phone.

com.google.android.gms (): Wakeups: 553 (13.9 / hr.)

Alarms: 87, Intent: {com.google.android.gms/com.google.android.gms.checkin.EventLogService$Receiver}

Alarms: 134, Intent: com.google.android.intent.action.MCS_HEARTBEAT

Alarms: 81, Intent: com.google.android.intent.action.SEND_IDLE

Alarms: 63, Intent: com.google.android.intent.action.GCM_RECONNECT

Alarms: 0, Intent: {com.google.android.gms/com.google.android.gms.playlog.uploader.UploaderAlarmReceiver}

Alarms: 0, Intent: {com.google.android.gms/com.google.android.gms.playlog.service.MonitorAlarmReceiver}

Alarms: 151, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVITY_DETECTION

Alarms: 12, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_BURST_COLLECTOR

Alarms: 0, Intent: {com.google.android.gms/com.google.android.gms.common.download.DownloadAlarmReceiver}

Alarms: 15, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_BURST_COLLECTION_TRIGGER

Alarms: 4, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_CACHE_UPDATER

Alarms: 2, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE cmp={com.google.android.gms/com.google.android.gms.icing.service.IndexWorkerService}

Alarms: 2, Intent: {com.google.android.gms/com.google.android.gms.security.snet.SnetService}

Alarms: 1, Intent: com.google.android.gms.recovery.WAKEUP

Alarms: 1, Intent: com.google.android.gms.auth.authzen.CHECK_REGISTRATION
[Xposed Framework Modules] TNSMANI:
A BBS dump file on idle would have served better. Charge your phone to 100%, leave WiFi on and let it sleep for about 6 hrs. On waking the phone, immediately go to BBS and save the text file and attach it here. That would give much more information than all the screenshots put together.

Reading and making sense of all these screenshots require a lot of patience which many may not have. A single BBS idle dump would have made the job easier. Then if any further info was needed, only that screenshot could have been uploaded.
[Xposed Framework Modules] arubamon:
Thank you for your reply. I wasn't aware that a BBS dump file would provide all the info needed, since I figured y'all would need to see what I have limited in Amplify. Also, as I stated, I'm not sure if I have things limited that I shouldn't, and wanted to show exactly what I'm limiting, to see if there's anything I need to go ahead and reallow. I will provide a dump file as soon as I let my device sleep overnight. Thank you again.
[Xposed Framework Modules] arubamon:
Thank you in advance for taking a look at my dump file.
[Xposed Framework Modules] Portgas D. Ace:
According to your log, you have lots of known battery draining alarms and wakelocks. Head over to this great thread for troubleshooting and follow the guide.
[Xposed Framework Modules] arubamon:
Thanks for your reply. I've followed several guides, but not that one, yet. Looking at everything I do have limited, can you tell me why I still get Gmail notifications on my device immediately upon receiving an e-mail? Also, have I limited anything that I shouldn't have? I use YouMail for my voicemails, and I've noticed that as soon as I get a voicemail, when I open YouMail, I have a new voicemail, however, I'm not getting a notification in the status bar and my notification sound isn't working either. Wondering if it's something I've limited that I shouldn't have. Thanks again for your help.
[Xposed Framework Modules] Portgas D. Ace:
Do you have Titanium Backup installed? If yes, use it to backup Amplify's data (in case you want to return to your original Amplify set up) and go to Settings->Apps->Amplify and delete its data afterwards. Then follow the guide to limit everything according to the guide with Amplify. Have a closer look at those alarms/wakelocks with the red cloud symbol, as they affect push notifications. Limit everything without the cloud symbol and post another idle dump file in the linked thread.

Setting up your device with Amplify takes some time, my advice for the best individual user specific setup is to limit one element and reboot. Check afterwards if it will cause any issue (delayed notifications for example). If not, go ahead and limit the next element and repeat the steps (reboot and check for issues). If you encounter any issue, there are two possibilities: either decrease the time limit (maybe reduce it to 50% of the original one and check again for issues) or undo the latest change you have made and continue with the next element. As said before, it takes some time, but you can set up everything according to your needs. After finding the best setup, you can use Titanium Backup to backup your ideal preferences.
[Xposed Framework Modules] arubamon:
Thanks again for your reply. Right before you posted this, I backed up Amplify w/ Titanium Backup, cleared its data, and tried leaving myself a voicemail. Still no notifications. So, not sure what's going on there; it used to work. I'll have to try it on another device to see if it's me or the app. I'll go through the guide tomorrow and probably post another log the following day.

I notice it says its not recommended to limit AudioMix, but my AudioMix wakelock seems really high, and I don't appear to be experiencing any delay in getting notification sounds w/ it limited; as I said, I'm still getting Gmail notifications for some reason, even with SyncLoopWakeLock set to 1800 seconds. Also, I have touch sounds and lock screen sound disabled.

Thanks again for your help. :)
[Xposed Framework Modules] trancinguy:
I had no problems limiting Audiomix, but I don't use my phone as a music player and youtube videos were OK.
[Xposed Framework Modules] Portgas D. Ace:
A high number in Amplify does not mean that this alarm is a battery drainer. Use BetterBatteryStats to identify the major drainers.
[Xposed Framework Modules] arubamon:
Looking at my BBS log file, I see:

Since 9 h 40 m 41 s

Level lost [%]: Bat.: -31%(52% to 21%) [3.2%/h]

Deep Sleep (): 6 h 35 m 49 s 68.2%

Awake (Screen Off) (): 3 h 4 m 46 s 31.8%

wlan_rx_wake (): 1 h 33 m 47 s Cnt:(c/wc/ec)10475/1633/10474 16.2%

qpnp_fg_memaccess (): 28 m 37 s Cnt:(c/wc/ec)1313/421/0 4.9%

qpnp_fg_update_temp (): 21 m 30 s Cnt:(c/wc/ec)978/309/0 3.7%

qpnp_fg_update_sram (): 8 m 9 s Cnt:(c/wc/ec)352/105/0 1.4%

alarm (): 6 m 17 s Cnt:(c/wc/ec)1747/269/0 1.1%

PowerManagerService.WakeLocks (): 5 m 50 s Cnt:(c/wc/ec)2781/306/0 1.0%

alarmtimer (): 5 m 15 s Cnt:(c/wc/ec)158/158/158 0.9%

wlan_oob_irq_wake (): 2 m 37 s Cnt:(c/wc/ec)9548/459/17 0.5%

wlan_ctrl_wake (): 1 m 40 s Cnt:(c/wc/ec)102/195/102 0.3%

suspend_backoff (): 1 m 9 s Cnt:(c/wc/ec)9/0/9 0.2%

android (): Wakeups: 74 (7.7 / h)

Alarms: 0, Intent: android.intent.action.TIME_TICK

Alarms: 0, Intent: android.content.jobscheduler.JOB_DELAY_EXPIRED

Alarms: 48, Intent: android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED

com.google.android.gms (): Wakeups: 72 (7.4 / h)

Alarms: 5, Intent: ALARM_WAKEUP_SENSOR_UPLOADER

Where do I find what was actually causing my device to trigger wlan_rx_wake for ~1.5 / 9.5 hours, which, to me, appears to be the reason my device kept waking up? Thanks again
[Xposed Framework Modules] Pkt_Lnt:
Quick Google Search shows that it is DHCP requests from a router using dynamic IP. Static IP solves it for many. There are many posts about this on XDA and other sites.
[Xposed Framework Modules] arubamon:
I have my device set to a static IP.
[Xposed Framework Modules] shueking:
I have posted the screenshot for the catlog, its been about 3 weeks and i am still not able to block any alarms or wakelocks.

Your help would be greatly appreciated.

Thanks
[Xposed Framework Modules] bbgun7:
Any updates on this? I'm getting this alarm like crazy, trying to figure out how to fix it

---------- Post added at 03:10 AM ---------- Previous post was at 03:02 AM ----------

Can you expand on lockbox? I'm getting slammed by that alarm
[Xposed Framework Modules] arubamon:
Limited everything from http://xdaforums.com/android/general/guide-0-0-hour-idle-battery-drain-stock-t2973588?nocache=1 and my device is staying awake slightly more than it was before. Log attached. What exactly should I be looking at in the log? Thanks again
[Xposed Framework Modules] Portgas D. Ace:
If you have limited everything according to the linked thread, you can ask for help there.

I am currently on my mobile device, I will check your log when I have access to my PC.

You can check your log by yourself, look for the highest times of wakelocks, they are listed on top of the wakelock list. Same goes for alarms. A high number of individual alarms should be looked at. Those are the important things to look for. If you have identified them, search for them on XDA or Google to see what they are for and if they can be limited safely.
[Xposed Framework Modules] Adywizard:
Lockbox isn't a battery hog even though amplify's showing huge amount of alarms.
[Xposed Framework Modules] Al Gore:
Does anyone have any experience with these alarms?

lockboxAlarmReceiver (14800 times welp)

android.deskclock.ON_QUARTER_HOUR (5300)

greenify CleanerService (4500)

GCM_Reconnect (3600 but in BBS it's the most active alarm every day)
[Xposed Framework Modules] Portgas D. Ace:
android.deskclock.ON_QUARTER_HOUR -> see here, I wouldn't limit this one, otherwise you may encounter clock-related issues (for example alarms not working correctly)

greenify CleanerService -> related to Greenify's hibernation service (Greenify might stop hibernating apps at all if limited)

GCM_Reconnect -> required for proper push notifications (push notifications will be delayed if you limit this one)

lockboxAlarmReceiver -> no idea yet
[Xposed Framework Modules] TNSMANI:
See post #4000 in this thread for some info on lockbox. I think it is related to Android Device Manager used for locating a lost phone. Someone can deactivate it in Device>Settings>Security and see whether the alarms go away.
[Xposed Framework Modules] kosmasgr:
Hello guys.

This modules isn't compatible with cm 13 right ?
[Xposed Framework Modules] Portgas D. Ace:
It is compatible with CM13.
[Xposed Framework Modules] rapiollymega:
Hello,

I've been having a lot of "wakelocks" from *Alarm* and *Net Scheduler* in Amplify. Some days I won't have them at all and other days they show up with absurd amounts of wake time (more than the stats collected time). When they are awake it also causes NLP wakelocks and GCM wakelocks to skyrocket as well. I'm not sure if its an actual battery drain becuase I don't see it show up in any other app or just an Amplify bug. Just wondering if someone else here had experience with it.

On moto x 2013 5.1 stock.
[Xposed Framework Modules] biogon:
I am on an institutional WiFi network and could not switch to a static IP.

The only way I suppressed those was switching to ElementalX kernel, which has an option to suppress wlan_rx_wake. Battery life appreciably increased.
[Xposed Framework Modules] arubamon:
Thank you, although it doesn't appear this kernel is compatible w/ my Xperia Z5 Premium (E6853). :(
[Xposed Framework Modules] biogon:
Oooh. That sucks! I don't know if there are any kernels for the Z5 that would help. :(

From the little reading I've done, it looks like it's something that has to be blocked in the kernel. I don't know why Google won't (or can't) address this themselves.
[Xposed Framework Modules] xn0live:
i do not get more notication from email(app:outlook) why?
[Xposed Framework Modules] Portgas D. Ace:
Maybe because you have limited something that should not been limited. Upload a screenshot of limited alarms and wakelocks, please.
[Xposed Framework Modules] xn0live:
Hi,

what u exactly mean? Go to menu wakelock and make a screenshot?
[Xposed Framework Modules] Portgas D. Ace:
Yeah, make a screenshot that shows all wakelocks and alarms that you have limited. How else should we be able to say what you have limited with Amplify and thus causing your issue? ;)
[Xposed Framework Modules] gpz1100:
Amplify is a very powerful tool. But like all tools, care must be exercised in its use. It's very easy to break something by limiting a particular wakelock, alarm or service. Sometimes, the entry limited may not even be directly related to what's broken.

I suggest using a systematic approach and limiting only a few things at a time, then test over a day or two. If everything is working correctly, then limit some more. Keep good notes of what you're changing.

Posting a screen shot may or not help in this situation.
[Xposed Framework Modules] xn0live:
i have nothing amplifiyed

i just install it give the hakc by xposed do a restart, finished
[Xposed Framework Modules] Portgas D. Ace:
Basic version of Amplify does not limit anything related to Outlook. In this case a log file might be helpful.
[Xposed Framework Modules] joeyflippinbats:
Flashed CM13 snapshot for Oneplus One yesterday night and everything is working fine except I cannot see a list of wakelocks, alarms or services to choose to limit in amplify. Xposed logs show that it is working for the basic NipWakeLocks, but obviously I'd like to limit a ton more than just the core few. It was working earlier in the day when I was on the nightlies, and poking around these forums I found a couple of things about SElinux being enforced causing this problem and found a few posts explaining the vanishing lists in the past, but no real solution aside from a couple that uninstalled/reinstalled (which I tried several times) or that the problem vanished on its own.

All other Xposed modules working perfectly.

I guess I'm curious to know if I should wait for an update to the amplify app that will fix this issue for me or if I should just wipe and flash the nightlies back onto my phone?
[Xposed Framework Modules] xn0live:
i can make a logfile from the app bbs is that helpful?
[Xposed Framework Modules] kuba929:
I think I can't set up correctly amplify on LG G4, can someone send me a flashable zip with amplify settings (drawn by Titanium buckup maybe? is there any option to do it?) to improve battery stats? With my settings in amplify apps I have 4,5 h sot on wifi/3g and 50 % automatic brightness. I would like to have closer 6 h. And another question - I will be able to flash this settings via flash fire?
[Xposed Framework Modules] joeyflippinbats:
I figured it out! I was ignoring SuperSU binaries needing to be updated, so amplify couldn't access the system files because I never granted it super user permissions. Flashed an older version of SuperSU and everything is working perfectly, all lists are back!
[Xposed Framework Modules] JohnHorus:
Community Spreadsheet

Deleted... Mods should consider reading closely
[Xposed Framework Modules] zyguo:
feature requests

Custom default screen(section) after app loaded
[Xposed Framework Modules] EuEra:
This was working great but now its not blocking anything anymore?
[Xposed Framework Modules] OnceHeaven:
It happened to me when i wipe cache and dalvik. You could try to disable on xposed, reboot, re-enable on xposed, reboot. It should work again.
[Xposed Framework Modules] Jojo5678:
Does anyone know what could be limotong my gmail.

When screen is off, gmail will not sync and push notifications, until I turn on the screen.

Thanks :)
[Xposed Framework Modules] PePeMoke:
Working less efficient than on cm12.1.....and proximity sensor

I am using a S4 I9505 and I am on cm13 optimized by JDC team.

Noticed that the wakelocks blocked are way less than when I on cm12.1 optimized and I am still using celestial fury's guide. Will amplify be updated anytime?

Second thing is that I've got a wakelock that I cannot explain.

I don't use any gestures to wake up the device so why so many wakelocks from the proximity sensor?

Screenshots attached.
[Xposed Framework Modules] TNSMANI:
There are only three wakelocks for proximity sensor but their time are high. Were you speaking on the phone during that period?

Try restarting your phone.
[Xposed Framework Modules] nola mike:
Got the "in-app billing" error. Have had the donate version for a couple of years, multiple roms/phones without a problem.

I've never installed Lucky Patcher. Tried all the suggestions on page one, and am still getting the error. Also tried deleting app data/cache, no joy. What am I supposed to do now?
[Xposed Framework Modules] 2phazt:
For me it helped to start the playstore - some playservice had stopped.
[Xposed Framework Modules] TNSMANI:
Did you install it from Xposed repo or from backup? If you do either, sometimes the app misbehaves.

Clear data and cache of Amplify and uninstall it. Reboot and install it from Play Store, enable in Xposed, reboot and see whether the issue is resolved.
[Xposed Framework Modules] Dr Grato:
i installed and trying to apply some of the setting. sometimes, it force close. i already sent bug report (i hope it send it to u not google or CM). anyhow, i will try again later.
[Xposed Framework Modules] celikbasm:
[MENTION=526666]cryptyk[/MENTION], Regex not working, i'm on 3.3.6. i asked that before but not answered. Could you advise please. Thanks.
[Xposed Framework Modules] nola mike:
Yeah, I already did all that. Installed from play store, disabled all xposed modules, disabled powernap, nothing relevant greenified. Still getting the error.
[Xposed Framework Modules] Brutal_Master:
Can someone please help me, I've noticed SEVERAL times now that after uninstalls apps I see their services STILL listed under the "Services" tab of Amplify....I don't' actually believe these are real so how do I get amplify to remove them?
[Xposed Framework Modules] DB126:
Reset stats (upper right corner) from home page. Anything that comes back is real. Give it a few hours to fully repopulate.
[Xposed Framework Modules] lakyberry:
I don't see any nlp wakelocks in wakelock menu. Am I missing something?
[Xposed Framework Modules] Logan:
Um guys in last facebook update it looks like the wakelocks and services chabged or renamed anybody can take a look?
[Xposed Framework Modules] TNSMANI:
Do you use location? If location is off, they wont appear.
[Xposed Framework Modules] luke1513:
Hello. I disabled the wakelocks, alarms and processes listed with amplify. When i activated it in xposed and rebooted the phone wouldn't recognise the SIM card, so i coulnd't call or use the mobile network at all. I disabled amplify from xposed and sim card was sucsessfully recognised. Do you know what causes this problem? Because if i keep amplify disabled every wakelock and alarm will be back to normal.
[Xposed Framework Modules] urgali:
Hey everyone!

First of all i want to thank you for this awesome app and all the juice it helps to save.

I'm here for the first time to ask a few things: i found 2 really high wakelocks in list that are put under "unknown", the *alarm* and the "launch* one.

I see from bbs that a lot of apps use them, even when device is deep sleeping.

I just wanted to know if anyone actually knows what are those wakelocks for and if it is safe to limit them; i'm trying with 800 limit and i've got no issues atm, but as i said, i'd like to know what i am limiting.

Thanks in advantage, i even tried to look for an answer on google, xda, this thread but nuthin' :)
[Xposed Framework Modules] Kocane:
Is it just me or does Amplify cause frequent play store services force close? Messes with push notifications.
[Xposed Framework Modules] mondohow:
That's just you. Or more specifically your setup.
[Xposed Framework Modules] Kocane:
Hm, okay. I'll try sticking to default setup
[Xposed Framework Modules] BartLuke94:
Some time ago I tried to limit the *alarm* wakelock, and I had a reboot every 2 minutes. I had to remove that limit.

Inviato dal mio Nexus 6P utilizzando Tapatalk
[Xposed Framework Modules] urgali:
Got no such issue; i'm actually running Oneplus two with Rremix and custom kernel and i've limited *launch* and *alarm* to 1600 seconds; i still don't know if it will bring more or less battery drain, but for now there is no strange behaviours in daily usage
[Xposed Framework Modules] BartLuke94:
Oh nice. Let me know if you see some battery improvement :)

Inviato dal mio Nexus 6P utilizzando Tapatalk
[Xposed Framework Modules] v7:
*launch* and *alarm* doesn't cause any drain.They appear on all LP&MM ROMs.

___

v7

XDA Assist
[Xposed Framework Modules] urgali:
Thanks for the info! So should I leave them free even if very high?
[Xposed Framework Modules] luptatorul:
Hello everybody! I would like to thank the developer first of all for creating this awesome app! I have read about it and I saw that it does wonders, hehe. I would love to buy the pro version of this, unfortunately I can't pay for it at the moment. Is there any similar application I could use that does the same job until I can buy this one? Thanks in advance!!
[Xposed Framework Modules] DB126:
Fools errand to limit these. A high number of wakelocks does not automatically equate to increase wake time. Look at the other stats and argument with a tool like Wakelock Detector to see what is really keeping your device up at night.

---------- Post added at 02:47 PM ---------- Previous post was at 02:45 PM ----------

Free version handles the lions share of wakelocks that make a meaningful difference. No reasinable alternatives that I'm aware of.
[Xposed Framework Modules] RASTAVIPER:
So, wake time is more important then number of wakelocks, right?
[Xposed Framework Modules] DB126:
Only as reported by Wakelock Detector or similar app/tool. The times reported in Amplify represent wake time requested which is typically far greater than actually realized. There are complex rules on how Android deals with wakelocks; most do not actually 'wake' a sleeping device. When activity subsides the device can return to a low power state even if the wakelock duration has not expired.