yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] gian90t:
I said that i don't think it's an hardware defect, with JB every things going well. From the instant the phone reboot to finish the KitKat update the problem starts.
[Xposed Framework Modules] TNSMANI:
Try to go back to JB and see whether it solves the problem. If it does, may be you can download Kitkat and flash it and see if that works alright.
[Xposed Framework Modules] schlager P.:
got a weird one: with audiomix limited I get a sweet 2% drain in flightmode but notification sounds stutter very much, so disabled limiting but got a 12% drain in flightmode(over 8hours), now the weird thing is: WLD doesn't even register audiomix.Is there a trick to limit audiomix without notifications stuttering and why doesn't WLD notice it?

Sent from the den of inequity
[Xposed Framework Modules] mafsi:
Audiomix is not good to be disabled as it breaks sounds as it shown in 1ceb0x file. Go to page 194 on this forum and try to disable some services. I have 0% lost in idle time with WiFi ON.
[Xposed Framework Modules] phantomblu:
I want to donate to get the pro version, but it keeps saying my device isn't supported. The app crashes when I click on the three developer links on the bottom of the homepage.
[Xposed Framework Modules] Cyclu:
Do you have XPrivacy if so allow your Google account for Amplify.
[Xposed Framework Modules] xn0live:
What I must do , if I have the app? any change settings for battery life?
[Xposed Framework Modules] phantomblu:
I've disabled xprivacy for amplify but still getting that message.
[Xposed Framework Modules] Dovidhalevi:
The continuing adventure:

I have found the best way, it seems, to throttle Play services is to have tasker/secure settings turn off location when phone not in use (screen off, no plug power). So now, Play services, even with its location and wakelock permissions active, is not sucking me dry. Now Maps becomes the culprit, before having sat quietly out of the way. I would not turn off its location permissions, of course. Tried turning off its wakelock permission and it seemed to make no difference. All of a sudden, this is eating 50%. Didn't do that last week (note: using a 6.* version that works on my older phone).

So I do not know if reactivating Amplify and sitting on Play and Maps wakelocks will help. Wanted to try to have tasker/secure setting turn off maps entirely when phone not in use but the app list never came up so was not able to try this.

Maybe more recent Maps works better with recent Play but crashes my phone. Funny, all this was just fine, with or without Amplify active, before I needed to replace my sdcard. Any ideas?
[Xposed Framework Modules] Takamoto:
Hi,what value must I set for keyguard and show keyguard? I'm on JB 4.1.1
[Xposed Framework Modules] Cyclu:
If you do not have disabled In App Billing for Play Store I don't know what is the issue have you killed Amplify after disabling it in XPrivacy

I don't have this problem when I allow my Google account or disable XPrivacy for Amplify.

Install My Android Tools https://play.google.com/store/apps/details?id=cn.wq.myandroidtools

And check if billing in Service (screenshot) and Broadcast Receiver for Play Store is not disabled.
[Xposed Framework Modules] tangcla:
I just wanted to share a quick story - I limited a few things but then got drastically reduced battery life. I wasn't sure which one it was, so I reset Amplify back to defaults and limited only the ones safe to limit (plus a few more, like the S Health one).

In short

1) Don't just limit everything, because some things can have a detrimental affect on battery life

2) Make sure your experimental limits can be easily identifiable, e.g. use a particular limit time like 59 seconds so you can determine which ones to unlimit.
[Xposed Framework Modules] Dovidhalevi:
So true. This can be a very problematic procedure. Needed

1. Previously proposed social aspect interface of some kind, accessed for each proposed limit item.

2. Some more realistic metrics. Time passed/time blocked or number passed/number blocked may or may not have any realistic meaning. Where do we get all those named wavelocks? Better-battery-stats and such do not show which ones or which ones did what.

3. The idea of a limited time-test is a good one if could be implemented. Effect on battery draw should be measurable over some minimum time to know if specific selections helped, hindered, no-real-change?
[Xposed Framework Modules] yunusemredar:
thanks :)
[Xposed Framework Modules] pantezuma:
Hi to all.

I´ve been playing around with the paid version of this app and have a few questions.

Does anybody successfully limited *net_scheduler* wakelock?

I thought I did it right by limiting it to every 300 seconds, but it seems that when I limit certain wakelocks "alarm manager" wakelock goes crazy and keeps the device awake... Is that possible?

My only success except from the ones that come pre cofigured with the app has been with GTALK_ASSYNC_CONN which keeps my phone awake at my work LAN.

Thanks in advance about any help regaring *net_scheduler* wakelock.

PS: Sorry for my English!
[Xposed Framework Modules] uhendran8:
I've been reading this thread and playing around with Amplify on my Nexus 5 (KK4.4.4). Anyway, I've been getting a persistent notification to upgrade to 5.0, which I blocked. Then I noticed both in BBS and Amplify a wakelock called SystemUpdateService, which was running at least 4-5 minutes during 6-7 hours idle time. Thinking it was better to cut the wakelock off at source, I disabled the associated service (com.google.android.gms/update.SystemUpdateService) and rebooted. Big mistake.

My phone didn't get any deep sleep at all during the 3 hours testing, basically since i rebooted (BBS screenshots included).

Wasn't sure who to get in touch with so decided to post here. Hope I helped, and hopefully someone else can test and confirm :fingers-crossed:
[Xposed Framework Modules] leijonasisu:
Is this app even being developed any more? I've never seen an update for it and I've donated and had it for months and months.

I'm really waiting for the developer to get started on the most important thing in the apö...

What all these bloody wakelocks and alarms do, and whether or not they're safe

to disable...
[Xposed Framework Modules] tylerdurden83:
Frankly there is little point spending much development time on an xposed module right now, imo at least.

Lollipop is advancing, all the new devices will have it preloaded, and xposed won't be a reality anytime soon.
[Xposed Framework Modules] Dovidhalevi:
Which wakelocks might interfere with calendar sync if limited? Alarms?
[Xposed Framework Modules] dimm0k:
I wish this wasn't true... Lollipop is a piece of sh...
[Xposed Framework Modules] m1trand1r:
But it is true.....Lp...is what you said....I agree...sadly...

Sent from my LG-G3/d-855/16Gb/Titanium Black
[Xposed Framework Modules] Black_Stark:
that means this thread is only open for discussion . no development ? :(
[Xposed Framework Modules] TNSMANI:
I have *net scheduler* limited to 240 and have no discernible issues.

Search for icebox's posts and you can find out which are the other wakelocks/alarms that can be limited. Beyond that you will have to experiment.

---------- Post added at 08:42 PM ---------- Previous post was at 08:35 PM ----------

System Update Service has been running all through. You do not seem to have completely blocked it. Did you limit/block its service in Amplify? It may not be sufficient.

Some wakelocks have services, receivers, activity etc. Unless you limit/disable all of them, it will have only a negative effect. Better use MyAndroidTools or some similar app for this.
[Xposed Framework Modules] txv0:
Does anyone know what QcConnectivtySerivce and WifiDelayIfNotUsed do? I looked around and cannot find any substantial info on them :eek:
[Xposed Framework Modules] xk0niR:
You need to block receiver and service (usw myandroidtools)
[Xposed Framework Modules] mafsi:
- QcConnectivityService => limit to 43200 sec

see here: http://xdaforums.com/showpost.php?p=57507862&postcount=2
[Xposed Framework Modules] Dovidhalevi:
Jury still out on how much battery I can really save with this. Seems trying to "amplify" Google's stuff is chasing one's tail, it is simply too interrelated.

I have, however, gotten some positive results with non-Google apps, such as Pushbullet, reducing its hit without reducing its function. K9 Mail might also get some reduction, not as much.

The question is ultimately how much, how much effort, diminishing returns.
[Xposed Framework Modules] 1ceb0x:
seems like Xposed for Lolli is on its way http://xdaforums.com/showthread.php?p=58751037

:D:D!!!!!
[Xposed Framework Modules] Ok_Kaleidoscope5109:
Several technical questions for you:

1) Does it matter what location accuracy you set? I imagine that because this is a network location request, both High Accuracy AND Battery Saver are affected.

2) Is this the baseline behavior of Google Play Services with no other 3rd party apps?

3) If you have 3rd party apps also wanting to use location services, could there potentially be additional requests in addition to the every 60 seconds? I thought the fused location provider was supposed to prevent this and to streamline requests.
[Xposed Framework Modules] Dovidhalevi:
I finally got battery-life nearly back to where it was before recent Play Services updates.

First method, before Amplify: No location and no wakelock permissions for Play Services. Use the App Op or Omnirom's app permissions settings.

Second method, with or without Amplify: Tasker/Secure settings turns off location when screen off (phone not in obvious use). Maps started to act up but problem not caused here--deleting its data fixed it. I gave the permissions back to Play Services though they really made no difference in phone's functionality.

Default Amplify settings address the issue mentioned. Amplify has kept Pushbullet off the battery-drainer list without effecting its functionality and has marginally reduced K-9 mail.

Wonder what surprises the latest upgrade will give us?
[Xposed Framework Modules] siealex:
After one of the recent playservices update Amplify hangs my system completely after boot. WTF? Sometimes it freezes completely, sometimes it throws "application System is not responding". Also it blocks ADB access. WTF???
[Xposed Framework Modules] dimm0k:
interesting... are you using Pushbullet that often or something? Mine doesn't seem to cause any drain throughout the day.
[Xposed Framework Modules] Mistertac:
I'm pumped for this, maybe we could get back to it like old times lol

Sorry I've been on a Nexus 6 so I just wasn't able to contribute like I used to. This here is good news though!
[Xposed Framework Modules] abhi08638:
http://xdaforums.com/xposed/official-xposed-lollipop-t3030118
[Xposed Framework Modules] h4z3d:
And with that said, I wonder if it will need to be updated for L :eek:.
[Xposed Framework Modules] Smultie:
Amplify working for any of you on lollipop xposed?
[Xposed Framework Modules] h4z3d:
Testing in about 5 minutes.

EDIT: Doesn't detect any wakelocks, will need to be updated for L.
[Xposed Framework Modules] cryptyk:
Hi all,

It's been a long time since I've posted here! I've been working on a different app that I just launched that I hope will improve people's heath and fitness.

I wanted to let you all know that I'm excited to get Amplify working perfectly for Lollipop! I'm going to be out of town this weekend, but will be back Tuesday. As soon as I get back, I'm going to fire up the Amplify project and see what's working, and fix what's not. If, between now and Tuesday, you lovely guys and gals find problems, please post them in the issue tracker. That will make it was easier for me to get things fixed in a timely fashion.

Over the last few months, I've been asked hundreds(!) of times when Amplify will work on Lollipop. It finally looks like that day is here, and I couldn't be more excited! The beauty of material design combined with the battery life that we've come to expect from our devices!

Thanks!

Ryan
[Xposed Framework Modules] xxlakis:
I had to reinstall amplify and after that whenever i launch it,it get's stuck on the message "detecting xposed" and after some minutes it crashes.Yesyerday i updated also google services.Coujld it be that the reason?
[Xposed Framework Modules] NJGSII:
Seen the same on my M8 detects some alarms but not any wakelocks.
[Xposed Framework Modules] cryptyk:
This is embarrassing, but I don't have a Lollipop device. I *think* I may have fixed the wakelock issue, though. Can a few people with Lollipop give this test version a try?

Thanks,

Ryan
[Xposed Framework Modules] bgiesing:
With this version, it doesn't detect Xposed as installed.
[Xposed Framework Modules] cryptyk:
Weird. I didn't mess with that part of the code at all. When you try 2.0.7 on Lollipop it gets past that point?
[Xposed Framework Modules] bgiesing:
Yeah, I seemed to have fixed it by disabling, reboot, enabling, then reboot and open.
[Xposed Framework Modules] dsmitty166:
Seems to be detecting wakelock now.
[Xposed Framework Modules] cryptyk:
NICE!

After a few more folks here put it through the paces, I'll push it to the OP, Xposed Repo, and Play Store.

Thanks!

Ryan
[Xposed Framework Modules] bgiesing:
Forgot to mention that it works for me also.
[Xposed Framework Modules] marbulas:
list of wakelocks works fine on cm12. IDK it really works really [emoji14]

...well, no any critical logs didn't appear in xposed installer.
[Xposed Framework Modules] aeoveu:
Hey Ryan! I'm guess who's baaaack! ;)

I'm on stock Lollipop (5.0.1) and installed both xposed and Amplify. the logs show that Amplify is working as intended (allowing some location wakelocks, like it used to) but the alarms and services and wakelocks aren't populating (and hence, not letting me change their threshold figures).

Here is the log (granted, the phone has had an uptime of approx 10 min) and the screens I get in amplify. (Bad formatting alert, cause I'm using my phone to send this).

---

OK, in light of new information, here is an updated log http://pastebin.com/LhzjEYxF
[Xposed Framework Modules] marbulas:
OK I got errors now. Here's the pastebin about this.

https://pastebin.com/XpFw9XPY
[Xposed Framework Modules] cryptyk:
Thank you! This is super helpful. Logcats are perfect for things that aren't working.

For everyone: As I mentioned before, I'm going to be away until Tuesday. I might be able to do some quick fixes in my "free" time, but please don't expect things to work until next week.

Thanks!

Ryan
[Xposed Framework Modules] aeoveu:
Okay, turns out, it may not entirely be Amplify that's messing around (although the error logs do seem to indicate something) - a little bit of digging shows that on the Nexus devices (which have SELinux set to "enforcing") need to do this:

- download https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=en

- set mode to "permissive"

- go to xposed, and perform a SOFT REBOOT.

The issue is, when you perform a full reboot, Xposed doesn't run properly (and maybe that's why it's in alpha) and Amplify doesn't detect the wakelocks as well. This is because the selinux mode is not changed until after a few minutes the phone has rebooted (i.e. in normal cases, the phone first boots up, then changes to the permissive mode). Xposed runs during boot - but since the mode is changed AFTERWARDS, it doesn't initiate properly, and then starts to not work as intended.

With a soft reboot, after you've done changing the setting, you don't perform a full reboot, but only perform a software-level reboot, and THAT is when Xposed and Amplify work properly.

I tried to make it into an ELI5, and I think I've done a horrible job, but this should hopefully fix a few issues for those who can't seem to run mods properly. That said, the permissive mode is NOT required for all mods - since a few other mods were working fine without changing the setting, but if it doesn't work, then try giving this a shot.

Edit: got the above info from this thread: http://xdaforums.com/showpost.php?p=58836123&postcount=64

Also, in the link (linked to the specific post), they've made a workaround so that you can probably reboot normally a million times and not have to use the workaround - I'm trying it out in a bit.

Edit 2: I don't think the init.d file seems to work for me (or maybe I can't seem to get it working correctly). That said, probably the best way to ensure that any and all xposed modules work is by performing a soft reboot after whenever you happen to perform a full reboot.

Edit 3: Okay, I guess you need a combination of BOTH SELinux Changer AND the init script in order for you to restart as many times as you want (normally, cold restarts) *and* make Amplify function normally (without addiional steps). Guess this info should be put up somewhere.
[Xposed Framework Modules] NJGSII:
Installed this and the wakelocks are being detected now.
[Xposed Framework Modules] 1ceb0x:
nice global stats :D

It is good being back in the business!!!

Awesome quick fix cryptyk! Let the fun begin!
[Xposed Framework Modules] AvivEliyahu:
how to fix it on lolipop xposed ? tried installing version 3.0 and chang selinux to permissive but still it doesnt detect the wakelocks
[Xposed Framework Modules] dcclark:
Software reboot did the trick for me

sent from my Oneplus One
[Xposed Framework Modules] Skhulile:
Can't donate in new version

Hello, I've always been reluctant to donate and explore the full functionality of the app because of the fact that it was long since it had been updated, now that it got updated to 3.0 I can't donate, I get an error (see attached screenshot)

Thank you!

Edit*: Nevermind, i just installed the previous version again, donated and then installed the latest version
[Xposed Framework Modules] cryptyk:
That's just a weird Google Play Store thing. For a few hours after I update in the store, people get this error. It will take care of itself.

Thanks,

ryan
[Xposed Framework Modules] plantator:
Hey, for me at 5.0.2 amplify work only showing work time, no wakelocks or alarms, and when i erase IT from lastapp menu, it resets timer
[Xposed Framework Modules] DubleJayJ:
Think you could implement a $1 donate option? I got a $1.97 on my account and I'd love to help out

EDIT - For some reason it decided to crash when I hit the donate option
[Xposed Framework Modules] igloohed73:
For those looking for a little more insight to what's what with wakelocks on an individual app basis I found that GSam Battery Monitor really is a nice companion app to Amplify. Helps determine what wakelocks belong to what app a little faster & easier & maybe helps determine if it's safe to Amplify to a certain degree. Just thought I'd pass that along since it's helped me a bit. Came preinstalled on a ROM I flashed.
[Xposed Framework Modules] empire10:
amplify app shows empty list http://pastebin.com/pk9VwYz1
[Xposed Framework Modules] Dovidhalevi:
No, not really. However, it did show up on the battery list for a few %, just like k-9 mail. Noticed that its wakelocks were in large numbers so limited them. Lower or not on the battery list. Does not necessarily mean any real gain in battery life. Still have this question for the module itself.
[Xposed Framework Modules] 1ceb0x:
From where did you installed the app?
[Xposed Framework Modules] jawz101:
Anyone who is suggesting setting SELinux to permissive please don't. Lollipop is essentially a flashy gui, ART replacing Dalvik, and Security Enhanced Linux enforced. I don't like the idea of turning SELinux off for an app to work. That's taking away a great protection.
[Xposed Framework Modules] dsmitty166:
Then don't use it. For now. It's the only way xposed works. Take it or leave it
[Xposed Framework Modules] Wh1t3Rose:
Exactly and it's recommended by Rovo89 until he finds a workaround so we don't have to use Permissive.
[Xposed Framework Modules] 1ceb0x:
Do you make love with protection all your life?

ontopic: [MENTION=526666]cryptyk[/MENTION] - my list stopped to update itself..

http://pastebin.com/iBMd7Cum

L.E: apparently if you reboot normally, xposed won't work anymore. You need to perform a soft reboot from xposed. I think someone said this in this thread as well.

Now it seems to work OK.

LE - issue appeared again - libc will throw a fatal error and crash after a while saying that Amplify cannot find the path specified for com.android.server.AlarmManagerService.
[Xposed Framework Modules] empire10:
From here and it's nexus 7 2013 5.0.2
[Xposed Framework Modules] 1ceb0x:
Grab some logs and post them. Will be a lot easier for everyone to see what's going on.
[Xposed Framework Modules] empire10:
Oh yea I did,its on my first post
[Xposed Framework Modules] Sportfreunde:
ANyone know if this is safe to put a restriction on? It causes around 15 wakelocks/hour:

com.google.android.intent.action.mcs_heartbeat
[Xposed Framework Modules] 1ceb0x:
I think that's in the spreadsheet we made for this app.. Did you looked there? It is in my signature. Heartbeat is the 'pulse' used by GPS to check your ping, signal, etc to the servers. Basically a periodic check of your connection with Google servers. I suggest to leave it untouched.
[Xposed Framework Modules] jawz101:
Haha 1ceb0x is good at breaking the ice.[emoji112]
[Xposed Framework Modules] aeoveu:
Re. reboots: you can use the init.sh script method i linked to earlier - and that fixes things for normal reboots. You just have to leave your kernel in permissive mode (and then you can ignore that setting).

The fatal crash error - I've been getting those too.

---------- Post added at 07:41 AM ---------- Previous post was at 07:02 AM ----------

Okay, here is another log: http://pastebin.com/pYLn1ukE

Notice how it just skips on location reporting in between.

Shortcut: scroll to the bottom-most portion of the log, and then start scrolling up. Where it began to throw errors, I rmemeber using the phone (Twitter, but doing that'll make a difference). It fixes itself.

Location reporting stats on the web show misses in between as well. Sometimes its in sync with the xposed log, sometimes not - no rhyme nor reason. The app shows that it's throttling wakelocks though.
[Xposed Framework Modules] sumit yadav:
Only alarms working nothing else!!!
[Xposed Framework Modules] kenosis:
In order to install and use Amplify, what are other recommended apps to install?

Currently, i installed Amplify, Xposed, Wake Lock Detector and Better Battery Stats.
[Xposed Framework Modules] aeoveu:
http://xdaforums.com/showpost.php?p=58837492&postcount=4087

Quick question: since I'm coming back to this thread after ages (and wasn't following it properly), are the wakelocks throttled ONLY when the screen is off, or are they throttled regardless of the screen state? I ask because Location History tends to reflect minute-by-minute updates when I was using my phone, but almost every four minutes (as per the settings) when the screen is off. Just need a little clarification on this (because AFAIK, it should throttle ALL the time).
[Xposed Framework Modules] jekkel:
standalone?

Maybe a stupid question, but I was using this module back in the KK days last time.

Since then it seems that a lot of things changed.

Is it still requires to have Xposed installed, or is it a standalone app now and only needs root access?
[Xposed Framework Modules] eemgee:
Beta not working on stock moto g lollipop
[Xposed Framework Modules] Wh1t3Rose:
Post a log. Just saying it doesn't work will not help you or the developer.

---------- Post added at 06:09 AM ---------- Previous post was at 06:09 AM ----------

No Xposed is still required.
[Xposed Framework Modules] Cyclu:
Have you amplified some wakelocks for Play Service like you see in the quoted post certain PS wakelocks are under wrong package name justly Android System maybe it's related to your problem. Since this I can't even tried to amplify them thinking it will cause problems.

Hi [MENTION=526666]cryptyk[/MENTION] can you look to this issue please?
[Xposed Framework Modules] eemgee:
My moto g stock 5.0.2 exactly the same problem