yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Kocane:
Anything new on this, mate? I see you limited Alarm Manager as well as ActivityManager. No consequences?
[Xposed Framework Modules] magnamentis:
really old post haha... yeah.. quite a few things

"M"

did not cause visible issues, but since it's a tasker wakelock and i'm managing my 1st-level device conditions with tasker i don't limit it anymore

"E"

did not cause visible issues, but since it's a tasker wakelock and i'm managing my 1st-level device conditions with tasker i don't limit it anymore

"Alarm Manager"

did not cause visible issues, but since it's managing key functions of the OS and others clearly outed this as unsafe i don't limit it

anymore. main criteria is that albeit the number of wakelocks is huge, there seems to be no significant battery drain by it and obviously we can assume

that core OS functionality is under control battery wise so far in kitkat. i mean less than 2mAh usage in idle mode is hardly possible

"ActivityManager-Launch"

did not cause visible issues, but since it's managing key functions of the OS and others clearly outed this as unsafe i don't limit it

anymore. main criteria is that albeit the number o wakelocks is huge, there seems to be no significant battery drain by it and obviously we can assume that core

OS functionality is under control battery wise so far in kitkat. i mean less than 2mAh usage in idle mode is hardly possible

"Location Manger"

no issues at all, raised to 1200" from 420" in the mean time

"NetworkStats"

no issues at all, raised to 780" from 180" in the mean time

"RILJ"

no issues at all, raised to 420" from 210" in the mean time

"SyncLoopWakelock"

no issues at all, raised to 240" from 180" in the mean time

"AudioMix"

no issues at all, but not limited anymore because it is either triggered by sounds with high priority (audio focus) or causes problems for apps

with out audio focus set to high priority, while battery drain through audio mix is low in idle and as expected while needed.

so the benefit is minor and the risk that something brakes with certain apps is not predictable.

"android.intent.action.TIME_TICK"

clearly brakes updating various clocks including statbar and lockscreen

"com.devexpoert.watheradfree.pfx.WAKEUP"

no issues at all, raised to 1800" from 420" in the mean time ( widget specific, some widgets don't update the clock properly when limited, this one works flawlessly )

"net.dinglisch.android.tasker.ANOFFCHECKORUM"

did not cause visible issues, but since it's a tasker alarm and i'm managing my first level device conditions with tasker i don't limit it anymore

"com.google.android.gmsnlp.ALARM_WAKEUP_ACTIVITY_DETECTION"

no issues at all, raised to 360" from 120" in the mean time

"com.google.android.gmsnlp.ALARM_WAKEUP_ACTIVITY_LOCATOR"

no issues at all, raised to 210" from 120" in the mean time

hope that helps ;)

EDIT: values are generally ok but may slightly defer from device to device and config to config, depending on usage, number of google accounts syncing locations etc. but i'm using the app on 6 devices and settings are very similar though. the above settings are from the OnePlus ONE
[Xposed Framework Modules] Thomas_BA:
Found a little translation bug in spanish.

Should be "Wakelooks bloqueados"
[Xposed Framework Modules] m1trand1r:
How about changing black text to normal white

...to make it readable for Black themed Tapa and black theme of xda page users...?

Then your post would help.

I changed color codes to white while quoting you....as nobody w/ black background is able to read most of your findings:)

No offense meant tho:)
[Xposed Framework Modules] magnamentis:
you have a point

you have a point i first chose all in color and then changed the black part back to black for titles to stick out better.

a) rarely someone has the exception in mind, sorry for not knowing that default black adapts while defined black does not :)

b) in the future i would let default black and only color the colored text, so each day to learn something.

that with the no offense was good to be added because the initial tone was a bit off indeed, i mean the message is readable on all original

thems and some could have a red or magenta theme and not be able to read read or magenta text ?

however all is well and i will be aware of this in the future, no doubt about that

and i will edit the post as to this new info, give me 5 minutes

DONE

BTW, if you could put that huge quote into a container, would be similarly good for those using tapatalk
[Xposed Framework Modules] m1trand1r:
Hey....don't worry ....there's no rush to fix your post as members can read it from my quote....and yeah....sometimes my statements do sound a bit off/harsh and i'm aware of that very well....hence "no offense" addon added at the end....coz I know we're different people with different understandings and ofcourse with different themes applied on our Android devices....oh..,magenta or red background would be awesomely wicked LOL:D
[Xposed Framework Modules] Kocane:
[MENTION=5372360]magnamentis[/MENTION]

Thanks for the reply.

Hm, well... One that troubles me is AudioMix.. I was so annoyed by the amount of wake time it took so I set it to 8000s. According to the app it avoided 17 mins of wakelock and I dont really notice as issues.

My music player uses another wakelock so that's that, however I think a consequence was shown with my 'timer' where I forexample set an alarm in 10 minutes. The alarm would sound but quickly silence itself until I turned the screen on which must be because of the audiomix wakelock not being allowed.

I've also had M and E limited ( I dont use Tasker THAT much ) but seeing as it seems like its just a huge amount of wakelocks but not really in a long duration, I guess it's dumb to potentially cripple tasker functionality

[MENTION=3763274]rkoby13[/MENTION]

What are you fellas on about :p? His post is perfectly readable... is it because I'm in my computer browser with the 2010 XDA theme enabled ^^?
[Xposed Framework Modules] cryptyk:
Nice. I've started putting in some code around version updates. It's crazy that you guys are deleting files, resetting stats, etc between version. I'm trying to make that all automatic.

Part of the stabilization stuff for these set of releases. Feels like it's getting closer.

Thanks,

Ryan
[Xposed Framework Modules] magnamentis:
ok more in detail then (smile)

audiomix is generally triggered each time the device produces a sound, there might be exceptions but this is generally how it is

so whenever you produce a sound and the app or OS which produces that sound has a high audio focus ( high priority ) it will play

that sound no matter what you've set in "Amplify" so it happens that player pro, radardroid and all other apps which i use and need sound,

have that audio focus and/or have a setting to toggle it. so i could set audiomix to 9000" and these sound would still play as expected.

BUT at the same tame the number of audiomix wakelocks would be very high as well, because the moment an app overrules the "amplify" settigs it will produce

that wakelock, but of course with apps using it, means phone not idle, means no additional battery drain. so if you listen to music you cannot

avoid high numbers in audiomix but the music playing the the same amount of juice. so this wakelock is not a usual wakelock, its' basically

indicating how much sound your device produced.

in short, it does not make sense to try to limit audiomix because if audio is aktive you cannot limit it or the sound will not work properly, the latter is a nogo and first means no benefit. on the other side is the risk, that if one or several of your apps do not have audio focus they will stop working properly the moment you switch of the display, worst case even with it on, but mostly when off.

i hope u get the point, we just have to live whith those number in the app, they are necessary for the device to produce sounds.
[Xposed Framework Modules] cryptyk:
This is interesting. Does it also happen in 2.0.4? If it happens in the latest version, it's really helpful to know that it affects every version except 1.3.2 and earlier. I can probably track it down with that info.

That said, please make sure it's an issue in 2.0.4 so I don't go chasing a ghost :)

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
I'm trying to not update the OP because I'd really, really like to fix the problem. Right now, people are uninstalling and reinstalling. Or they're deleting "the magic four files". Or they're restoring backups. Ya'll shouldn't have to do any of that. It should just work. I have some code in place that will help make version upgrades more solid. 2.0.4 should have helped a little, but it will continue to solidify. I'm not going to add any new features for a while, but instead focus on making it work for everyone, equally.
[Xposed Framework Modules] cryptyk:
Just want to say that posting the logcat REALLY helps. I've fixed this, and it will be in 2.0.5. Thanks!

Ryan
[Xposed Framework Modules] mustafa_1994emad:
Just wondering why you keep changing the name, otherwise no problem I faced till now
[Xposed Framework Modules] cryptyk:
Thank [MENTION=4354573]chhapil[/MENTION] for the package names. That's a pull request he submitted to the code base!

I'll look at the crash. Thanks for the logcat.
[Xposed Framework Modules] cryptyk:
Can you elaborate a bit?
[Xposed Framework Modules] cryptyk:
Done. Thank you for helping out!
[Xposed Framework Modules] cryptyk:
Sorry about the confusion. There were legal reasons for the name changes.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
Thanks. Looks like pedrazadixon already fixed it :)
[Xposed Framework Modules] m1trand1r:
Done:)
[Xposed Framework Modules] Rodin69:
Wakelock mdm_hsic_pm0

Hi!

Amplify has helped me with quite a few wakelocks, and now it seems that only one persists. According to Wakelock Detector it is mdm_hsic_pm0, which isn't mentioned once in this thread, but searching the web it seems a lot of people are having problem with it. I haven't found anyone solving it, but it seems to be present on different roms, both stock and custom.

I asked Ryan about it, but he suggested me to ask about it here, which I now do. :)

Is anyone here having problems with this wakelock, or does anyone have a clue what to block/restrain in Amplify to cool it down?

Usually when I suspect this wakelock to keep my phone from sleeping I can restart it, and most of the times the battery drain will be a lot less after rebooting.

Regards,

Michael
[Xposed Framework Modules] Kocane:
Without being certain, I assume it's a kernel wakelock? Amplify cant really do anything about those afaik. It's probably the 3g modem. I had something similar with my xperia Z called msm_hsic_host and on my z2 its named something else but basically it's just the 3g/data modem. Using wifi can tame it and perhaps less data activity but I dont know.
[Xposed Framework Modules] Rodin69:
Yes, you're right, it is a kernel wakelock. And your assumption about the modem seems reasonable. That is what some other people are suggesting as well, without being completely certain.

If that can't be tamed it's a pity.

I have a Samsung Galaxy Note II LTE, and it's about time to upgrade anyway. So hopefully this is fixed in the radio/modem firmware for newer Samsung devices. The next device will probably be a Samsung Galaxy Note 4. Future will tell. :)

Thanks for the reply!

Regards,

Michael
[Xposed Framework Modules] cryptyk:
Is this consistent? A particular service, or all of them?
[Xposed Framework Modules] Kocane:
It's a bummer. My old Xperia Neo didnt have these kind of kernel wakelocks when using data. But my newer phones have had weird wakelocks for both data and wifi, sometimes bugging out so it would never sleep, etc.
[Xposed Framework Modules] HsHTCsen:
Having trouble keeping up with what's safe and what's not safe to Limit from all the trial and error mentions in here. Any suggestions please?
[Xposed Framework Modules] iRushaad:
I cant buy the pro version :(
[Xposed Framework Modules] Red_Vex:
Cant see service Anymore. Nexus 5

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Xposed Framework Modules] CHEF-KOCH:
Go into app details and clear app data and cache.
[Xposed Framework Modules] Red_Vex:
Already done. Doesnt work

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Xposed Framework Modules] picklu:
search options for wakelock and alarm

Sometimes it's really hard to find exact wakelock or alarms. It will be nice if there will be any filter options which will help us to find the desired thing.
[Xposed Framework Modules] CHEF-KOCH:
Works fine, try to reboot, normal not needed but may some time helps.
[Xposed Framework Modules] rignfool:
The only suggestion would be to see about a custom kernel...

Sometimes... Those wakelock can be tamed that way... It would depend
[Xposed Framework Modules] Celestial Fury:
Has no one noticed this? Is it 28 minutes allowed or 28 seconds? Shouldn't there be a colon in front of 28? Like this :28? There are many other examples.
[Xposed Framework Modules] cryptyk:
That's usually because you're in a country that Google doesn't allow IAP for.

Or, you've greenified or blocked the IAP part of Google Play Services.
[Xposed Framework Modules] Marcovanbasten:
Hi,

I made a donation.

How can I find google playstore and google search wakelocks ?

Thanks !
[Xposed Framework Modules] aeoveu:
Damn... I'm using Lollipop, and knowing that it may never get Xposed, I feel sad. I'm glad that I had donated my only dollar to you (I mean - look where you've come), but this time, I honestly thought that if you're able to figure out a way to throttle or intercept the wakelocks independent of Xposed, then I'd love to donate again.

But earlier, somebody said that your mod requires Xposed (I didn't study programming) cause of the hooks and everything required - but if you could achieve this one day.

One day...

Right now, I'm torn between Kitkat + Xposed + your mod, and Lollipop... it's torn me apart!
[Xposed Framework Modules] Cyclu:
Apparently the problem with automatic device stats refresh is gone with version 2.0.4 before I had to press the button refresh to have updated stats.

Sorry for my English I use a translator.

---------- Post added at 10:10 AM ---------- Previous post was at 09:56 AM ----------

No it's random it happened twice with two service elixir widget and an other unfortunately for the second I don't know the name. I will watch it make you sign If this is repeated.

---------- Post added at 10:32 AM ---------- Previous post was at 10:10 AM ----------

Use you XPrivacy? I had this dialog even if my country authorizes In-app Billing and a force close when I pressed an donation item after authorized my Google account in XPrivacy the both problems are gone.

Thanks [MENTION=4354573]chhapil[/MENTION] for adding the package name in description really good idea!:good:
[Xposed Framework Modules] tylerdurden83:
[MENTION=526666]cryptyk[/MENTION] Are you already working on a non.exposed version? All other additions are great, but that is imo the most urgent one, with lollipop being only a matter of days away...
[Xposed Framework Modules] rydako:
Lol went into xposed and there was another name change, was pretty confused until I read the description and realized what this was. Think you've settled on the name now? Haha

Ah okay, understandable. Hopefully no one gets grumpy about the new name.
[Xposed Framework Modules] Taomyn:
Still not working for me and I've also uninstalled and reinstalled it.
[Xposed Framework Modules] cryptyk:
Can you get a logcat of your bootup?
[Xposed Framework Modules] Citizen88gr:
Thanks for the module m8. I never thought the common battery saving apps are helpful because the don't focus on those alarms/wareclocks, plus they consume batter to "save" batter. That's not really smart. I recently heard about this module so I finally found a way to root my phone and get the module. I tested it for half a day and I saw some difference, so I got 2 Pro's, for me and my girl. I'll tell my friends about i. Keep up the good work man. I think this is the most useful app ever ;)
[Xposed Framework Modules] HsHTCsen:
Man. That's some comprehensive sh#t! Thanks. I'll see how I go. Can I also just add to this for anyone else reading, when charging the battery, even tho the % indicator on the device may say 100% when it's "full", it's a good idea to find an app, or in my case I have a little widget on the home screen, that measures your battery mA and to charge the device until that measure 0mA. It can take an extra 15-30min but only then is the battery truly 100%. That is what I understand to be true.
[Xposed Framework Modules] Taomyn:
Strange, went to check it again and found it had populated the list now, so all seems normal again.

Never had an update do that before, it normally picks up from the version before.
[Xposed Framework Modules] Marcovanbasten:
Could please someone help me ?
[Xposed Framework Modules] magnamentis:
they'll find you LOL

they appear only when they occur so you have to wait some time and should they occur you will find them in the wackelock and/or alarm lists in the app. however i don't think that wakelocks with that exact NAME exist. there certainly exist wakelocks related to the verious google services but the naming is not always that intuitive, for example GCM.... would mean GoogleCloudServices but then the shortcuts after that still don't tell which one in clear text but you have to lock it up which sometimes can be quite difficult.

on the other hand, wakelocks which really count are on top of the lists be it in number of wackelocks or in time. so whatever does not produce high numbers and/or long times you can just forget about them, they are there, have a purpose but don't have a large impact on your battery life.

these is general info, from time to time there are exceptions which are a bit out of the pattern like audiomix but you can use the info as a guideline
[Xposed Framework Modules] CHEF-KOCH:
An build for paid users without ad libs would be nice. ?
[Xposed Framework Modules] wbedard:
Ditto with my Nexus 5.
[Xposed Framework Modules] tj_cute:
hello. I just donated when this app is still nlpbounce. when I update, a message told me that pro features not available. please help...
[Xposed Framework Modules] magnamentis:
it's has happened

it was a known issue that pro status got broken between updates. you can do the following:

a) faster propably ;) search this very thread for what the dev wrote about it and how to solve it. it's mentioned and explaind in this thread.

b) slower perhaps ;) wait until the dev will answer here and repeat what he already said before as to how to proceed.

i think it's clear that a) would not only be faster but also the proper way, just MHO

good luck and main thing is, you will get your pro status back without any doubt, so no worries here :)
[Xposed Framework Modules] eraycetin:
GREAT APP !

If you like a can help you translate the app to Turkish.

Turk people will love this program.
[Xposed Framework Modules] Limbani:
I seem to have a feeling that something I have limited is affecting my pushbullet.. Is anyone else having problems e.g. re. Quick reply pushbullet, and universal copy and paste
[Xposed Framework Modules] Skhulile:
Well it's easy to find out whether it's something you have limited or not, just disable the module, restart your device and then observe whether you still have errors, if yes then it's not something you have limited, if not then you'll have to keep on testing one by one, which can be tedious, alternatively if it's probably a service or alarm that you have limited just open every entry in the limited section and check the package name and see whether it's related to the app or feature you currently facing problems with, and just disable those, reboot the device and observe:)
[Xposed Framework Modules] Takamoto:
Hi all,witch of this do I limit?
[Xposed Framework Modules] vitoski:
Look in the OP for link to spread sheet with listed alarms and wakelock safe to be unbounced. The list provides good explanation of an impact on phone functionality along with some guidance.

Sent from my XT1052
[Xposed Framework Modules] magnamentis:
incomplete info

depends on for how much time these stats stand. 100 wakelocks in a week are great in an hour horrible.

just assumed that these stats stand for about a day, there is none i would limit because the only ones with outstanding numbrers is not safe to limit

or are supposed to be there for a purpose. i mean keeping screen on wakelock sound intentional to me, but again not sufficient input

but as i said, this is an assumption based on almost nothing so get uses to provide the necessary information to get a valuable reply
[Xposed Framework Modules] cryptyk:
Sorry about that. As mentioned, there was a bug no early donations. If you send me your google order number to gotcode+amplify@gmail.com, I'll refund you.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
Thanks! I just added Turkish to the translation site: https://poeditor.com/join/project?hash=cba2f814b8847c56fda6850f288f2f7d

On a side note, I just visited Istanbul. What an awesome city. Great people, great food, great shopping, great parks, and amazing historic sites.

Thanks,

Ryan
[Xposed Framework Modules] hosgor45:
Wow just today I was looking at your app and saw there was no Turkish and I was going to contact you to offer you the Turkish translation but I guess no need for it now ;)

Istanbul is a great city to visit. I live in Istanbul and there is so much to explore :)
[Xposed Framework Modules] cryptyk:
Nice. I stayed in the old city with the rest of the tourists :)

If you'd like to help with the Turkish translation, please do! It's currently at 0% complete!

https://poeditor.com/join/project?hash=cba2f814b8847c56fda6850f288f2f7d

Thanks,

Ryan
[Xposed Framework Modules] brolic925t:
Anyone use this on the com.google.android.GMs/.icing service? Any downsides to this? Please answer and thanks for the help!
[Xposed Framework Modules] Osama Zabin:
I've already disabled ICING related services/receivers with no side effects.

Try to tame it and see yourself.

you can check [MENTION=2688060]1ceb0x[/MENTION] signature for more details
[Xposed Framework Modules] dcd17:
New version won't load wakelocks and alarms

I saw someone else mention it, but didn't see any resolution. Since it updated to the newest version (Amplify) it will no longer load any options beyond the attached screen rendering it basically useless. I've cleared cache and re-installed to no avail. Does anyone know of a fix for this?
[Xposed Framework Modules] cryptyk:
Can you post a logcat of your bootup?
[Xposed Framework Modules] wilkster:
I am having good success with 420 seconds for LOCATOR/DETECTION and 240 seconds for NlpWakeLocks and NlpCollectorWakeLock. I have been trying it with location history/reporting enabled (previously this was a battery killer for me).
[Xposed Framework Modules] dimm0k:
[MENTION=4195288]wilkster[/MENTION] why the difference between the two groups?
[Xposed Framework Modules] wilkster:
I was going off the assumption (perhaps incorrectly) that the wakelocks may be acquired by google services for reasons other than the two alarms firing. Therefore I was allowing the wakelocks more often than the alarms. Probably doesn't make a big difference.
[Xposed Framework Modules] geenyous:
I am on HTC Stock Sense 6.0 4.4.2 ROM and according to the Xposed Logs the module seems to be working, except for the known NullPointer Exception. I also see a lot less Nlp wakelocks now. I have nothing under running or cached apps, however.

Btw, now I get most Kernel Wakelocks from "PowerManagerService.WakeLocks" and most alarms from "com.google.android.gms" and most partial wakelocks from "Checkin Service" (after the apps I use, like Spotify, WeChat and Email sync).
[Xposed Framework Modules] Ev0d3vil:
Does this stop Android Services from eating more battery usage than the screen?
[Xposed Framework Modules] 1ceb0x:
No. It dwells with Google play services calls.
[Xposed Framework Modules] Misoginul:
Silly question from my part but ... how do I use it?

I've installed the apk but I don't know what should I do further.