yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Arjun42:
Xposed vs. Play Store

Great app! I just donated for the pro version and it's awesome!

Quick question: I downloaded Unbounce from Xposed, how will I retain the pro version if I flash/reset my phone? AFAIK, there is no logging-in capability (or persistence) in Xposed unlike the Play Store which uses our Google Account.

Thanks,

Arjun
[Xposed Framework Modules] lerx:
Hi guys should I unbounce RILJ wakelock? But I've search that unbloucing it makes battery life worse?
[Xposed Framework Modules] dungeonshard:
U need disable fast dormancy first. Then u see if high wakelock again. U can disable it. I disable with 600s. Smooth in my phone[emoji39]
[Xposed Framework Modules] lerx:
Even when my carrier supports fd? I've tried turning off before but I'm using 4g most of the time so...
[Xposed Framework Modules] schlager P.:
yes, that's all true but when I use it it drains 15% even in flight mode and the no. of wakelocks is ridiculous don't you think?

And I ticked "minimalize wakelocks" which clearly doesn't work, hence the attempt at unbouncing

Sent from the den of inequity
[Xposed Framework Modules] m0han:
use the same Google Account. read this and this.
[Xposed Framework Modules] vitoski:
Guys and gals do you know what causes: ANDROID.NET.CONNECTIVITYSERVICE.ACTION.PKT_CNT_SAMPLE_INTERVAL_ELAPSED alarm?

This is the highest number of alarms I get for Android.

I tried already to unbound it with 600sec but it was not blocked at all...

Searching on Google brings nothing but entries in BBS stats that people published on the Internet.

Thx.

Sent from my XT1052
[Xposed Framework Modules] Mistertac:
That's debatable really... I have mine set to this with no negative impact for me. I'd imagine set to high, you'd run into having to much over head like anything else you can limit.
[Xposed Framework Modules] tmushy:
Thank you for this! I believe it fixed my problem. I have a samsung s4 running hyperdrive.

Actually this also fixed another issue I had with bluetooth connectivity delays!

thanks given!
[Xposed Framework Modules] magnamentis:
let's see

ok, i see that you have a drain so let's see if we find the reason because:

a) i have lightflow on 7 devices for 2 years and my drain in idle is 2mAh or 0.15 - 0.2% per hour which makes 1-2% in 8-10 hours each night.

b) i have lightflow setup with 8 apps/tasks to cover at all times including some which are active in idle like mute = white, airplane = red etc.

c) the number of alarms is very high locically because it's non-stop checking in my case it's 2404 alarms during 19h still there is no drain due to those alarms

lightflow is by definition a user at all times but as mentioned above, if i can achive such good battery stats on many different devices for such a long time with daily

supervision of battery drain through each night under same conditions, cell-tower, wifi etc. it can simply not be that lightflow causes 15% drain ( you forgot to mention which timeframe

but i assume you're not talking of several days haha..... ) further the web would be full of such complaints if that would be the case. most problems with lightflow except during API

transition times were user errors and in your case i suspect that it's not even lightflow itself but another incompatibility.

now 15% is anyways far off so we (you) will have to look at something else then lightflow as such. to find out more you would have to let us know how you come to the conclusion

that lightflow is draining the battery and further you would have to define ( ridiculously high numbers, mention the numbers and timeframe ) probably the best will be to du this over email because this would clog this thread otherwise, we can still come back and post a reply with results. so if you're interested to fathom this out pm me and we go from there by exchanging email addresses to continue ( if you want of course ) much easier to attach files etc than using the pm-mask.

---------- Post added at 02:08 PM ---------- Previous post was at 02:05 PM ----------

does not matter at all, you will be able to update form both platforms and pro status will be kept automatically, no matter from where you download updates as long as the google account is the same
[Xposed Framework Modules] schlager P.:
I'll do that tomorrow when I got more time, found that lightflow is the culprit, 'cause installing "light manager""(almost identical though I didn't pay for that) fixes the drain (after uninstalling lightflow)
[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 the last week or so with no adverse effects. e-mails still arrive almost instantly. kept at 600 to keep it evenly divisible within an hour.

wakelocks

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

still testing

BbmPlatform - 240 -

still testing

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.
[Xposed Framework Modules] Pkt_Lnt:
Carrier IQ.
[Xposed Framework Modules] 1ceb0x:
Right... so if i do this:

I will have problems?

Hint: keep awake selected to OFF.
[Xposed Framework Modules] xk0niR:
I myself set it to OFF with no problems.

I only use push though.

Even disabled Location and still okay when trying getting GPS (I don´t use any location tracking).
[Xposed Framework Modules] 1ceb0x:
Yes, i know. i was just being sarcastic :D
[Xposed Framework Modules] DB126:
Humor appreciated :)

...but I'm curious if there is any benefit to disabling Location and Keep Awake in Play Services? Apparently I'm one of the few that find Amplify increases battery consumption even with default settings. My personal experience is squashing wakelocks is like squeezing a balloon. Suppress one and others shoot up. Sometimes I can contain the most common offenders but battery life still takes a hit - typically WiFi (which never seems to enter a low power state when Amplify is active) and the work Amplify itself has to do. I realize this is not common but I'm still left looking for a way to rein in Google Play Services without increasing battery utilization and/or impacting functionality.

Don't get me wrong - I think Amplify is a fantastic tool and have donated to Ryan as he has done some great work. Just not the solution for me.
[Xposed Framework Modules] magnamentis:
that's why

that's why it's important to fine tune the interplay between services, alarms and wakelocks with the help of:

AMPLIFY APP, TASKER APP, GREENIFY APP, WLD OR SIMILAR APP ETC.

most important is to get location services as a whole under control and as i posted earlier in this and other threads there is a solution for this albeit people tend to not pay attention to it because they did not try the combo and therefore don't know that the hint is more than just that. keypoint is to eliminate services which INSIST to perform, even though the were cut off very recently. in extremis that means that a service will try non-stop to perform it's task which can end up in an almost permanent awake state.

since it would be too much to repeat everything here ( you have to read as much as you can ) i will repeat the most important one for many which is location services: if you are not actively using location services but only in the background or if you want to avoid permanent attempts of the system to gather your location, you have set location settings to "DEVICE ONLY" but then again you have to make sure that if you want to get accurate location like upon navigating that the settings change to high accuracy. this kind of things can be achieved with the help of tasker. further it is recommended to use tasker as well to swich location settings to OFF while in airplane mode, otherwise you can end up with a bunch of attempts to gather your location to no avail since all readios are off.

the key point here is that only when location is set to device only, it is somehow guaranteed that the system will accept the fact that location gathering is not possible at the moment, while in every other mode it will retry shortly after failing to do so, somehow assuming that sooner or later there will be a cell tower or wifi network available. i don't know if that was meant to work like this but i made the experience on all my devices and with all roms under kitkat that this is how it works.
[Xposed Framework Modules] DB126:
Thanks. Actually, do use most of the above tools (plus others) to good effect and done a fair bit of reading/research/experimentation. Careful assuming others have not done due diligence just because a question gets posted. In this case I never considered tweaking permissions and wondered if others had experience with this approach. I suspect it won't help (much) as it would have been discussed at great length were it the magic bullet.

Yeah - I have disabled a few services, Greenified others and use WLD, GSAM and other tools to keep tabs on the most egregious abusers. In the end my phone and other android devices are productivity tools. It is easy to invest much time/effort into optimization out of need (extending battery life), desire (we all like to tinker!!), privacy, etc. Gotta find a balance. I'm glad others are willing to share their experiences to benefit others; I do the same when there are meaningful results.
[Xposed Framework Modules] Tinchoska:
guys, how can i make google play services stop drinking my battery juice....????

another one, using this module by defaukt, because i have no idea how to tune this up yet, will do anything? if yes, can someone explain what's it does?
[Xposed Framework Modules] 1ceb0x:
read the OP and the links in my signature.
[Xposed Framework Modules] HsHTCsen:
Hi, I've done a search and couldn't find anything definitive but I've been getting lock screen freezes since I limited the majority of the wakelocks and alarms listed in Safe To Limit with default settings. I've since deactivated Amplify in Xposed just to see if lock screen still freezes and it hasn't for 4days. Anyone pinpointed something around this? Cheers. HTC One m7 UL
[Xposed Framework Modules] 1ceb0x:
see if you amplified something called "keyguard". that's the lockscreen.
[Xposed Framework Modules] HsHTCsen:
I can see the keyguard but it's not limited. I'll unlimit anything to do with Android System and slowly make my way back
[Xposed Framework Modules] CHEF-KOCH:
Normally GP services can be untouched. The drain was already fixed with the .84 L build and for all in .88 most people I know complaining about these kind of problems because the services isn't visible via play store, so no update, thanks google! That means if you not use a gapps package, not fake the desensity/country or you not update your gapps you may run into this. Can only speak for ru and ger people which normally not see this via gp. But experts don't have any problems to deal with, thanks aptoide or other markets for the updates.

Keyguard also can be leaved untouched, because some apps that needs it (phone, dashclock may not recives update notf.) Better is to remove it if you not need or want e.g. dash clock or control / restrict it via xprivacy.

I'm not the Matrix Oracle. ?
[Xposed Framework Modules] body150165:
Until today, i worked with V1.5.1 and everything was fine. Since i updated to 2.0.3, the app doesn't not recognize neither wakelocks nor alarms or services anymore. Everything is empty. Restarted again with no success. Then i wanted to go back to 1.5.1, but install failed.

What can i do?
[Xposed Framework Modules] 1ceb0x:
uninstall

reboot

install the new version

activate and reboot

wait 10 minutes

profit
[Xposed Framework Modules] Solace50:
requesting an export/share system in the next update. would speed up the ability to diagnose/collaborate on whats safe or not + some predefined profiles can be created for new users instead of multiple help me posts collection in your thread.

as of now i have next to nothing waking my phone other then google services of which i will try to refine a bit without breaking avasts portal for anti theft. im sure the settings are not ideal for everyone as certain wakelocks/alarms serve purposes to others but it can be utilized as a baseline for others to tweak around.
[Xposed Framework Modules] body150165:
In this case, all my previous settings are gone, right?
[Xposed Framework Modules] 1ceb0x:
unfortunately, yes.
[Xposed Framework Modules] CHEF-KOCH:
I agree in that, but the problem seems that some apps often gets an update. I don't think that would help to 'improve' the product much and user should better ask himself why they need 100 background apps or why the app needs so much services/wakelocks. As said before, the Amazon app is one example how many tackers, services are possible to include (never saw an app without that much useless services). I still see this product here not for beginners, since it can (maybe) break some things in the wrong hands.
[Xposed Framework Modules] metalboy94:
Not sure if it's been posted before, can we get Amplifying for services by time intervals, like in wakelocks and alarms? I'm having major problems with FB Messenger battery usage and this is pretty much the only thing that can stop it.
[Xposed Framework Modules] Takamoto:
Does anyone know these alarms and tell me if it is possible to limit them? Tnx..
[Xposed Framework Modules] 1ceb0x:
amplifying the services is a one time process only - on/off. why you need timer?

Event log service and event log handoff ones are OK. Rest of them, no.
[Xposed Framework Modules] magnamentis:
perhaps i'm missing something here but to switch a service on every hour but have it off the rest of the time sounds not like such a bad idea to me, after all it might be easier let an entire service perform it's tasks 12 or 24 times a day than to fight singele alarms and wakelocks which in case of google services is sometimes even replaced by a, let's call it "backup alarm" or "backup wakelock"

so if you could desalbe location reporting as a service for 3600 seconds so that only once per hours the whole thing would only do all it's related activities once per hour sounds. independently of the feasability, a nice idea to me, well worth a discussion, specially about feasabilty, i somehow doubt it, but don't know thus would be very interested to hear more from more tech savvy people.
[Xposed Framework Modules] Takamoto:
[quote name="metalboy94" post=56657836]Not sure if it's been posted before, can we get Amplifying for services by time intervals, like in wakelocks and alarms? I'm having major problems with FB Messenger battery usage and this is pretty much the only thing that can stop it.[/QUOTE]<br />

amplifying the services is a one time process only - on/off. why you need timer?<br />

[quote name="Takamoto" post=56658786]Does anyone know these alarms and tell me if it is possible to limit them? Tnx..<br />

<br />

[/QUOTE]<br />

Event log service and event log handoff ones are OK. Rest of them, no.<br/>

Any solution please?
[Xposed Framework Modules] magnamentis:
first step to solution would be to start working on the matter with diligence and thoroughness. you don't even provide the time period for which your stats show, which has been mentioned over and over again that this is the only way to assess numbers and duration of wakelocks. considering the number of alarm manager wakelocks it could be quite a long period which would make most of those below being very ok numbers. but dunno due to lack of input.

further if you see that your post is a mess quote wise, perhaps you would consider to edit it and start putting huge images and texts into containers so that we don't have to extract the relevant info from a messy environment.

last but not least, don't seek for spoon fed solutions. there is no "one for all" solution. you have to first find your own solution for your confiuration. ways to do that have been posted at least dozens if not hundreds of times. limit events which you think are too high and watch the outcome and correct where necessary, sooooo.... easy. before you do that you should ideally set your self a max limit of number and duration of events for a given time frame.

i alone have posted this very thing about 10-15 times and others as often or even more often. so start working, take the finger out of you a... and don't wait for mama's full spoon like a ba..y
[Xposed Framework Modules] schlager P.:
I'm trying to figure something out here (massive wakelocks 20k+ by uninstalled lightmanager, it doesn't show up in WLD or titanium backup, which makes me wonder where/how "amplify" sees it)

Sent from the den of inequity
[Xposed Framework Modules] magnamentis:
so yesterday it was lightflow and now lightmanager ?

i just can say that i tried to explain that it's not lightflow, dunno about light manager since i don't se it. you have search in your config and rom-settings for incompatibilies. first thing which comes to my mind would be system > settings > "whatever led settings you have, if any ) next would be xposd modules with led management, not sure which all there are but i think that xblast and G'box do have those. there you have to make sure that all settings are either off or where not possible identically set and/or set to default (usually white)

these are only suggestions where to start searching, these things can take a while to find the culprits. just keep us posted with any success
[Xposed Framework Modules] metalboy94:
Because the services I need to amplify are those handling FB messages, so they'd have to start up every now and then to download new messages and notify me.
[Xposed Framework Modules] schlager P.:
yeah, that's what puzzles me. I installed light manager to see if that drains as well. It didn't , uninstalled it, reinstalled lightflow but light manager keeps those wakelocks anyway, while I can't find it anywhere

Sent from the den of inequity
[Xposed Framework Modules] Skhulile:
+1 if this is possible then I'm in support of it
[Xposed Framework Modules] 1ceb0x:
hmm... the push notifications is handled generally by the GCM or C2DM from Google play services... of course, the app itself plays the part that communicates with Google server.

Maybe post what services you mean and then we can discuss further..
[Xposed Framework Modules] metalboy94:
Facebook have mostly stopped using GCM for notifications, they use MQTT which drains battery horribly. Here are the services I'm talking about.
[Xposed Framework Modules] 1ceb0x:
they still use GCM... otherwise it won't compile to Google's guidelines. The ones from your screenshots are receivers (app side). i have heard people greenifying the app itself and use the option in Greenify (donate) to keep the GCM running:

So your best case (to not break the app completely) is to use this option until other method is available.
[Xposed Framework Modules] metalboy94:
I did use that option, until I got my Galaxy Gear - SWAppLink crashes if it is enabled. I did reach out to the developer, but I figured I could try in here as well.
[Xposed Framework Modules] abhi08638:
Did you reboot

sent from my amazingly awesome OnePlus One

don't forget to hit thanks!
[Xposed Framework Modules] vitoski:
Hi all.

Wanted to share my recent finding. I shared it on BBS thread and thought some of you may find it useful here as well.

I was getting 1 minute 'ConnectivityService' wakelock every time I turned off WIFI. Finally I was able to pinpoint under which circumstances it appears.

When the 'Mobile Data' is switched off (i.e. by toggle in notification area) and you switch off Wifi this wakelock appears. It looks like it is searching for alternative source of network connectivity for a minute.

If you turn on mobile data and then switch off Wifi it will not appear or will be there but for a very short time.
[Xposed Framework Modules] schlager P.:
multiple times yes

Sent from the den of inequity
[Xposed Framework Modules] dimm0k:
NOTES:

looks like setting a default of 240 for the wechat wakelock helps noticeably! chats are still coming through and wakelock has dropped dramatically. pretty much the same thing for BbmPlatform, however it looks like the wakelock can be limited some more so I've bumped that to 480 from the default of 240. adding the following wakelock:

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

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...

also, 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] cryptyk:
You can often fix this by just pushing the RESET button on the home screen.
[Xposed Framework Modules] cryptyk:
I think service intervals would be hard for some people to understand because of the way they work. Because of that, I opted to just have on/off.

The challenge is that many services run at boot and stay running the entire time. Having an "interval" for them would require two things:

1) It requires a second setting for the service: How long should I let this thing run. That means that after the service runs for a certain amount of time, I have to stop it. I'm guessing that can cause problems in services that expect they're running 100% of the time in the background. It could be in the middle of network comm, writing a file, etc. when I kill it.

2) It requires me to start the service based on some interval. It won't start itself because it only starts at boot. That means I have to know for each service when and how to start it, which I don't love.

Other services start themselves occasionally to do some work. Those are started by alarms, though, so you can stop them from occurring by finding the related alarm (I think). I don't think services can't wake up the device. Only alarms do that.

Hope that helps.

Ryan
[Xposed Framework Modules] metalboy94:
Personally I have been reducing the alarms more and more with no actual difference in battery drain. It's funny, but the FB/messenger services are the ones keeping the phone awake, more specifically the radio part - if I turn on an ordinary iptables-based firewall on Messenger I get virtually no drain at all.

But thanks for your input, it makes a lot of sense. And thanks for developing Amplify :)
[Xposed Framework Modules] ztoldy:
I finished the hungarian translation if possible please, add it to the app.
[Xposed Framework Modules] Osama Zabin:
Global stats is showing 0 services, is it a bug? I already reset the stats several times yesterday.
[Xposed Framework Modules] cryptyk:
Just not done yet :)
[Xposed Framework Modules] drup88:
Can someone assist with trying to find this? Is it considered a wakelock, alarm or service? I've tried looking in all three but can't find it.
[Xposed Framework Modules] Mistertac:
That has to do with your countdown app/widget.

So if you want that thing counting down correctly, I'd imagine you'd need it running. You could look for it in Amplify and try anyways, can't hurt.