yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] xsteven77x:
Whenever you first start up the app, it says some new default settings were applied. I can't Sseem to find a list or something that says what these initial default settings are? Am I missing it?
[Xposed Framework Modules] Eduardomb:
does limit gpslocationprovider mess with gps?
[Xposed Framework Modules] Eduardomb:
My greader stoped auto updating, does anyone knows what service/alarm can be preventing it from auto update?

EDIT: *net_scheduler*	was preveting the update from greader. Probably this wakelock is about some schedule update of internet info.

Now it's all fine.
[Xposed Framework Modules] mafsi:
I have limited com.google.android.intent.action.MCS_HEARTBEAT to 1200 sec and saw no side effects so far. ( JB 4.2.2 )
[Xposed Framework Modules] kip256:
When I go to bed my battery on my LG G3 typically depletes 12-15% by time I wake up. I just woke up and my phone only went down 7%. So far this module is working.
[Xposed Framework Modules] wilkster:
So far this module does exactly what it says it does with no side effects for me. LGG2 stock Kitkat.
[Xposed Framework Modules] Galactus:
You probably have an app or apps constantly sending packets of data. Use network log to find the offenders
[Xposed Framework Modules] 7786:
Any chance you can look into taking care of the audiomix wakelock? It's been doing me in for a while now, I attached a BBS dump.
[Xposed Framework Modules] :
Please upload it at Xposed repo.
[Xposed Framework Modules] hamsup1o:
I am definitely seeing an improvement in battery life since I installed this module last night. However I think it does affect sound profile management apps that uses location to trigger profiles (i.e. Profile Scheduler+). I noticed it lagged a bit in changing to my work profile this morning. It's definitely a sacrifice I'm willing to make though for improved battery life! Thanks for this!! :)
[Xposed Framework Modules] Mistertac:
You read the OP at all? Wants it tested more first.

- Tapatalked from the G3
[Xposed Framework Modules] lexluthor:
As far as possible negatives, does this mean if I'm running, say, Cerberus to track my phone, that if I try to locate my phone, instead of telling me where it was 60 seconds ago, it may tell me where my phone was 4 minutes ago or does Ceberus do an on demand lookup when location is requested?

There must be some negative to doing this, no?
[Xposed Framework Modules] Mistertac:
I have been running this module since early this morning and using location based apps and GPS and so far so good. Too soon to tell how Battery life will be impacted but I'll try and keep my eye on it.

- Tapatalked from the G3
[Xposed Framework Modules] nIGhT-SoN:
Seems to work fine here. Had no problems and I notice the wakelock is less frequent. I used to have 1min wakelock for every 1 hour. Now I get like 15min / 20h. I will keep testing.
[Xposed Framework Modules] Mistar Muffin:
Works as advertised for me. Now just get ALARM_WAKEUP_ACTIVITY_DETECTION to stop waking up my phone every 60 seconds and this will be the real winner.
[Xposed Framework Modules] marbulas:
Holy...
[Xposed Framework Modules] nummakayne:
Switched from Android L to CM11 again so I could try this. I would really, really like to leave Location Services on all the time on my Nexus 4 without having to micromanage it so thanks for the module. I hope it works out great.
[Xposed Framework Modules] metalboy94:
Results are in! Not as much time on battery as yesterday, but there's an obvious improvement.
[Xposed Framework Modules] nullx:
Just wanted to provide some feedback for you.

I'm running this on an VZW HTC ONE M7, using elitelunar kernel and stock debloated rom.

I flashed this yesterday, and tested it out while at work today because usually my battery dies around 8PM. (I'm in an area with poor cell receptioon so I think it's always looking for a better connection, switches between 3g/4g a lot).

Right now it's been on battery for 8 hours and is only down ~40% with moderate usage!

Usually at this time I'd be at around 35-40%,. Right now it's sitting comfortably at 60% which is pretty phenomonal in my opinion.

This is a huge improvement and I'm really grateful that you created this. I can definitely see these numbers improving as well with some further tweaks.

Anyways I just wanted to say thank you and keep up the great work!
[Xposed Framework Modules] cryptyk:
You guys are all awesome for taking a look for me.

I have some good news: I've found an even more elegant way to do this and I'm pushing an update soon. I'll put it here, as well as in the Xposed Repo.

Thanks!

Ryan
[Xposed Framework Modules] lexluthor:
Maybe in misunderstanding this, but this is only going to provide a modest boost in battery, nothing close to as dramatic as you are seeing.
[Xposed Framework Modules] cryptyk:
Ok. New version is posted. This is the v1 version found in the OP.

Changes:

- Better method for intercepting the alarms.

- Added settings activity so you can specify the frequency you want the alarms to happen.

- Added ALARM_WAKEUP_ACTIVITY_DETECTION for those people for whom it was causing a problem

- Added the ability to directly temper the NlpWakeLock and NlpCollectorWakeLock. I recommend setting these to 0 (to disable them) unless the alarm tempering doesn't work well for you.

- Added this to the Xposed Module Depo.

More to come, but I'm catching a plane!

Be back in a week.

(HEY, ROVO! You rock. Seriously, awesome work.)
[Xposed Framework Modules] NJGSII:
I was the guy on reddit who brought up the ALARM_WAKEUP_ACTIVITY_DETECTION to you. Trying it out now. Thanks
[Xposed Framework Modules] vsa:
Sounds great! :good:

But I have a question: I have eleminated from GooglePlay Services NLPCollectorWakeUp, NlpWakeLock and UlrDispatchingService with "Wakelock Terminator (Play Store)" which can terminate Partial Wakelocks within many Apps.

My GoogleNow still works fine and I don't see any Waklocks of the terminated Services mentioned above in WLD anymore.

What is the difference to your XPosed Module? :confused:

Vsa
[Xposed Framework Modules] irish-sid:
Installed. Looking forward to the improvement!
[Xposed Framework Modules] chw9999:
ICS 4.0.3 and 4.0.4 no issues with installation and log
[Xposed Framework Modules] xordos:
Thanks, confirmed, there is no exception anymore for 4.1.2 device. And two wakelock logging is showup, also the alarm not supported yet as expected.

Thanks for all this fixes during the long weekend, especially after a trip. I am in no rush, just want to say thank you for this amazing idea to fix bugs for google. :)
[Xposed Framework Modules] geenyous:
I second xordos comments!

Now, you asked for other drainers, with me it's Checkin Service, eating away most battery with relatively long wakelocks. Can you handle this one similar?
[Xposed Framework Modules] aeoveu:
Alright - I think I'm having a slight comprehension lapse. If I understood correctly, you said that setting the

Seconds between NlpWakeLocks and

Seconds between NlpCollectorWakeLocks

both to zero, should be sufficient for everybody. But your default settings (well - my phone apparently) shows that both of those entries, in addition to the other two entries, are affixed to 240.

So - is 240 all over the recommended setting, or should the aforementioned two entries be set to 0 for a better battery life?

Also, I'm embarassed to ask this after 39 pages have gone, but what exactly is the difference between the settings? I'm sorry, but apparently, it seems I've gotten a MAJOR memory lapse lol. A quick ELI5 woud help and shut my mouth as well (and hopefully the others too).

I'm going to start navigating backwards again, but it would be great if someone can provide an ELI5 too.

TIA
[Xposed Framework Modules] Pkt_Lnt:
[MENTION=526666]cryptyk[/MENTION] changed from 240,240,0,0 to 240,240,240,240 between 1.0 and 1.1 and carried it to 1.1.1 as well. This helped me (from the OP):

I experimented with settings as high as 900,900,300,300 and saw no significant improvement (or downside), so I am back to 240,240,240,240 the current defaults.
[Xposed Framework Modules] :
This module messes with push notifications: WhatsApp only shows new messages when I actually open the app. After turning this module off, the app pushes notifications again.
[Xposed Framework Modules] aeoveu:
Thanks for clarifying.

Now - if someone could try and ELI5 the actual mechanism (the four options) so that I could actually know what's going on properly. So far, I understand the importance of the alarms - but not sure what the other two do.

I think it's my yearly hayfever kicking in :/

---------- Post added at 05:43 PM ---------- Previous post was at 05:38 PM ----------

Also, a quick edit for everyone - the OP may want to include this piece of info in their OP for everyone: Google Play Services' drain on wifi is significantly lower than it is on cellular data. One theory could be the pedometer (or other) sensors hooked into Google Play (don't take my word for it - I could be talking bollocks, but sensor time is apparently significant for Google Play Services), and the other theory could be that with a wifi access point, it's not searching for a new wifi AP repeatedly.

Perhaps the best way to tame the wake locks but have location reporting enabled is to disable wifi always on for scanning (that options in your Wifi menu). But note that it'll lead to a less accurate reading.
[Xposed Framework Modules] spupuz:
Why not updated the xposed repo too?

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Xposed Framework Modules] Pkt_Lnt:
He states above that there are still problems to solve before full release.
[Xposed Framework Modules] cryptyk:
Added 1.1.2 to the OP. This fixes the wakelock hook exception for 4.2 and 4.3. Thanks to xordos (again :)) for pointing out the signature difference between API level 17 and 18. I think it's pretty stable now, so if I can get someone to verify that the wakelock hook works on either 4.2 or 4.3, I'll push to the repo.

Thanks, everyone, for testing this on different device versions. I'm coding a bit in the blind by only having a 4.4 device. That, combined with kids running around the house while I code has caused a couple of things to slip through :)

I also added a debug logging setting. If you have any unexpected issues, please set debug logging on so you can attach a full log to the issue.

I also implemented best practices on git branching strategy in case anyone else wants to directly contribute pull requests.

Thanks!

Ryan
[Xposed Framework Modules] cryptyk:
Yea - My vision is to put you in control of the alarms and wakelocks on your device. I'm not sure what this will look like in the future, but I would love to get to a point where the module collects the alarms and wakelocks for each app and lets you temper them as desired in a more generic way.

We'll get there, but need to get this first implementation stable first. Once we have a solid base for the hooks and error handling, it will be a good time to make the entire module more generic.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
My Whatsapp still pushes notifications. I know everyone assumes that the problem isn't in *their* code, but I don't think this messes with WhatsApp directly. There may be some interaction between different things on your device causing the problem.

Can you do an uninstall of whatever NlpUnbounce version you have, reboot, install 1.1.2, reboot, then see if Whatsapp push works?

Thanks,

Ryan
[Xposed Framework Modules] faboz84:
+1 Whatsapp Push Issue with v1.0

as reported by another user i had Whatsapp Push Issues

with official v1.0 module randomly i didn't received messages until i opened the Whatsapp App

setting for the module were 420 - 420 - 420 - 420

Now i'm with the official module v1.1.1 since 12h and i didn't had any issue till now...i'll report back here

[MENTION=526666]cryptyk[/MENTION] and [MENTION=3266877]xordos[/MENTION] have you seen my previous post #375 with errors in the log? is it ok or not?

http://xdaforums.com/showpost.php?p=55174398&postcount=375

thx again dudes
[Xposed Framework Modules] cryptyk:
1.1.2 should fix that for you :)
[Xposed Framework Modules] cryptyk:
1.1.2 should work for your device, and will be pushed to the repo soon.
[Xposed Framework Modules] mistermojorizin:
I have 4.2.2 and the modified module from post 325 works perfectly but none from the first post work. That includes up to 1.1.1
[Xposed Framework Modules] cryptyk:
1.1.2 should fix Android 4.2.2.
[Xposed Framework Modules] cryptyk:
Pushed 1.1.2 to the repo.
[Xposed Framework Modules] touch of jobo:
Version 1.1.2 from OP on Android 4.2.2

No exceptions, no more 'Unsupported Android version trying to hook WakeLocks'.

All 4 different entries appear in the log when they get Allowed.

It does.
[Xposed Framework Modules] TNSMANI:
That is supposed to be a crucial wakelock which is not to be meddled with. How long since you Amplified it? Any discrepancy in your clock or phone signal?

Run it for 24 hrs atleast and report whether it is ok. I am having huge wakelocks of heartbeat.
[Xposed Framework Modules] mafsi:
It is 11:27 here in my country and i unbounced this alarm at 19:30 yesterday and i dont have any discrepancy
[Xposed Framework Modules] TNSMANI:
Ok, thank you for the info. I will amplify it now and report back after 24 hrs

EDIT: Sorry, my bad. I was thinking about timetick which has 8520 alarms in 17 days and wrongly mentioned it as heartbeat. Heartbeat is only 56 alarms in 17 days. So I am not going to touch it.
[Xposed Framework Modules] dajmanjt:
I went ahead and limited lockbox and no issues so far. Here is the info I've found on it so far.

Lockbox

Lockbox is another mystery feature, but there are enough clues to indicate that it's likely some kind of anti-theft component. After digging into the code, I found that Lockbox accessed both Location Services and "Telephony" (the actual telephone part of your smartphone). Additionally, there is a service and receiver responsible for watching account changes, for whatever purpose that would serve. Unfortunately, there's just not very much to look at here, but this could grow into something more tangible in the near future.

<service android:name="com.google.android.gms.lockbox.LockboxService" android:exported="false" android:process="com.google.process.gapps" />

<service android:name="com.google.android.gms.lockbox.service.LockboxBrokerService" android:exported="true" android:process="com.google.process.gapps">

<intent-filter>

<action android:name="com.google.android.gms.lockbox.service.START" />

<category android:name="android.intent.category.DEFAULT" />

</intent-filter>

</service>

<service android:name="com.google.android.gms.lockbox.LockboxAccountsChangedService" android:exported="false" android:process="com.google.process.gapps" />

<receiver android:name="com.google.android.gms.lockbox.LockboxAlarmReceiver" android:exported="false" android:process="com.google.process.gapps" />

<receiver android:name="com.google.android.gms.lockbox.LockboxAccountsChangedReceiver" android:process="com.google.process.gapps">

<intent-filter>

<action android:name="android.accounts.LOGIN_ACCOUNTS_CHANGED" />

</intent-filter>

</receiver>
[Xposed Framework Modules] shinra00:
So i have one question for the gurus of this module.

Have any of you started using Android L? I´ve read some posts now saying that the devices batteries are incredible with android 5.0 when compared with android 4.4. I asked the opinion of the gurus because there are few people here that actually managed to achieve the 0.2 0.3% battery drain while the phone is idle.

So what i want to ask is, which one is better? Android 5.0 vs Android 4.4 + xposed + amplify
[Xposed Framework Modules] magnamentis:
not much has changed really, the LP threads are still full of posts with complaints about wakelocks and alarms like were KK threads. as long as people don't manage their configuration properly this will never change. i usually link them to this thread where they can learn almost everything about what wakelocks and alarms really are, not a synonym for battery drain for example.

under LP you can achieve many goals of this app with tasker and considering the some rogue never ending troublemaking apps should just not be used and the NLP stuff is the by far greatest cause for rally draining wakelocks and alarms there is not so much work to do. all the necessary info can be found in this thread and instead of just easily limit the wakelocks they can be tamed with tasker scripts.
[Xposed Framework Modules] hienvahieu:
i have problem with google push communication when i use amplify

how can i fix this problem

thank you :D
[Xposed Framework Modules] Weetbix:
People aren't mind readers. You'll have better luck if you actually say what the problem it is that you're having, and what you have tamed using Amplify :D
[Xposed Framework Modules] Smultie:
Could you link me one of those scripts?
[Xposed Framework Modules] magnamentis:
i'm not aware that there are any such script readily and publicly available, sorry, i make each of them myself and they are very individually tuned to rom and apps and ui etc. so not much help i can give you here. furhter i'm currently still on cm11 as my daily driver and on bliss and cataclysm to get a feel for and keep up with LP developement. this kind of work ( scripting ) i only do for my daily drivers when i'm sure that i will stick to rom, kernel and general user space configuration. so for LP roms i don't even have it myself yet. currently for the 1-2 hours per day running LP i'm not interested in battery life but ui appearance bugs, xposed replacement mods etc.
[Xposed Framework Modules] wahuka:
Hi friends.

I need help with this Whatsapp Alarm.

It would be sure limit any?

Thanks
[Xposed Framework Modules] krohme:
Folks can locationmanagerservice be amplified?
[Xposed Framework Modules] TNSMANI:
Yes, if you don't use location.
[Xposed Framework Modules] Eduardomb:
Does limit gpslocationprovider and locationmanagerservice mess with gps? Anyone tried?
[Xposed Framework Modules] TNSMANI:
What do you mean by "mess"? If you amplify location services, they will not work properly unless manually called for. Some services which depend on location also will not work.
[Xposed Framework Modules] Eduardomb:
If, for example, I have running some run app ( runkeeper) and the screen is off and the app tries to get into gps, will it work ? Or will I get some wrong gps data?
[Xposed Framework Modules] magnamentis:
this is not a spoon feeding thread for babies, if you had just tried yourself you would already know and were able to share your newly acquired knowledge instead of asking multiple times around the point, albeit:

a) the answer has generally and in detail been given in this thread multiple times in length and in detail

b) the answer is in the app itself whether it's safe, unknown or unsafe. unknown means, you have to find out yourself and eventually share your findings, the other two should be clear

the underlaying pattern is that you already know the answer but don't want to accept it and are looking for a way out for a wakelock which does not matter at all. basically if you use this app out of the box ( default settings ) you're 99% there, the rest is very individual and often managing a wakelock can cost more juice than it safes. but this has all been written here by myself and other dedicated fellows who spent a lot of time to give for example you the necessary knowhow to go from there. so do your homeework, search, read, test and then

come back and share if you find something new, which in relation to Google Play Services i doubt.
[Xposed Framework Modules] Sportfreunde:
Anyone know what Checkin Services is it's one of my most frequent wakelocks and I can't figure out where it's from. Almost everything google related has been greenified on the phone.
[Xposed Framework Modules] LiL_Assassin:
When you stop something, it checks it.
[Xposed Framework Modules] Dovidhalevi:
As has been repeated here, wakelock does not imply batter-hawg! I have been playing with this quite a bit, have not really gained anything (I have Play services--worst offender--kept off locations and keep-awake from Omni app permissions and this did make a large difference).

Besides a social exchange where someone with a "eureka!" can share the great news, we sort of need a "better-battery-statistics" style rundown within the module's UI. Even that may not be conclusive.
[Xposed Framework Modules] cAase:
Does anyone know if there's any way to disable the Facebook messenger "analytics service". I disabled it completely and yet it pops up a lot of times.
[Xposed Framework Modules] mafsi:
This is what i limited
[Xposed Framework Modules] JerryGNYC:
Yes, Google can also be YOUR friend! :p

http://androidsecuritytest.com/feat...orts-and-agents/upload-agents/google-checkin/
[Xposed Framework Modules] dionysos77:
Hi everyone

I've been using donated amplify for about one or two months.

It was all OK, upto last week, last week I flashed lean kernel then come back to AEL 7.12.

But I saw that amplify is not blocking anything.

Here is some screen shots, can you please help me to find out what is the problem?

Wine&Fun talks via N9005
[Xposed Framework Modules] xn0live:
HI

how is that app wprk?

only install it and make a hack on xposed =finished?
[Xposed Framework Modules] Dovidhalevi:
After an sdcard catastrophe and having to use the phone without all the apps, just as a ... telephone (heaven forfend!), and getting 40+ hours battery life ....

The way to save battery is to throttle everything Google when phone is idle, screen off, not plugged in. Might allow for periodic sync but otherwise, nada.
[Xposed Framework Modules] gian90t:
Please Help me - RILJ Wakelock

I have a RILJ wakelock problem.

Using WiFi my smartphone IS PERFECT.

In 2G-3G it become really HOT (45-50°) and drain battery in a few moments... i talking about 15%-20% per hour

Using Amplify i see that the problem could be the RILJ wakelock, blocking it (with an update every 250 seconds) the drain stops, but i can't receive incoming call or sms.

Do you have a solution??

ps: i tried a lot of different modem and rom, when i bought my s4 mini it was perfect, after kitkat update the drama starts
[Xposed Framework Modules] Pkt_Lnt:
Sounds like a defective phone.
[Xposed Framework Modules] gian90t:
Yeah, i know, but i used it for 10 months without problems, that start in the same time of kitkat update from 4.2.2

This app is the first that show me a possible problem, and i am really interest to a solution
[Xposed Framework Modules] LiL_Assassin:
As bad as it sounds try a custom rom.
[Xposed Framework Modules] Pkt_Lnt:
As someone who spent 16 years as a phone tech, I have never seen software solve a hardware defect.
[Xposed Framework Modules] LiL_Assassin:
Well, welcome to the world of Android.
[Xposed Framework Modules] Pkt_Lnt:
Where were you six years ago to welcome me? The cellular radio has gone bad, this fine piece of software is not going to fix it.
[Xposed Framework Modules] Sportfreunde:
Can't find any info from Android Security on these wakelocks:

NetworkStats

GCoreFlp

RILJ

Wakeful State:Machine: Geofencerstatemachine
[Xposed Framework Modules] tangcla:
[MENTION=526666]cryptyk[/MENTION] can I suggest an enhancement in a future version - similar to the global stats, maybe we could vote up or down whether limiting a particular alarm/wakelock/service a) causes problems, or b) beneficial for battery life?

---------- Post added at 05:01 PM ---------- Previous post was at 04:56 PM ----------

Also... any Samsung owners using S Health notice a massive alarm in recent times, I think since a version upgrade?

com.sec.android.app.shealth.walkingmate.service.START_ALARM
[Xposed Framework Modules] Pkt_Lnt:
Yes you can and he requests you place them here, per post #1.
[Xposed Framework Modules] xsteven77x:
That's a great idea actually!
[Xposed Framework Modules] Dovidhalevi:
+1

Previously suggested a "social" interface for this module!
[Xposed Framework Modules] LiL_Assassin:
i get excessive RILJ wakelock, i use amplify, my phone goes into deepsleep and i still get phonecalls and sms, so i dont know what you are going on about :P