yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] brystel:
Hello,

Could someone tell me what is the event0 , event0-880 etc... ?

Since month ago battery drain issue happens to me. At night battery can drops more than 50%.

It is doesn't matter which soft I use (Stock CyanogenMod or unoffical CM - for now I have CM 12 (android 5.0.2), before I used CM11 (android 4.4)).

It seems that problem happens only when WIFI enabled.

I have checked many wakelock in Amplify but without success. Battery drain still happens.

Phone which I use is Oneplus One.

Thank you
[Xposed Framework Modules] esklarski:
This really sounds like the work of some app installed, not a wakelock problem. As far as I can guess this wakelock seems to be a generic OS wrapper for some other app to produce alarms (or something...), I've got lots of similar entries all numbered differently, none that amount to anything significatnt.

So having researched many wakelocks fruitlessly, I think you should take a close look at the apps installed on you phone.

Does this occur after a fresh OS install with no other apps installed?
[Xposed Framework Modules] brystel:
Yes, this occurs also in a fresh OS install...

Also with minimal gaps installed.
[Xposed Framework Modules] TheQuarterMile:
Want to get the donation version but I just wana confirm if the non donate version is working for me? In the stats it's showing the blocked wakelocks and alarms as 0 whereas the count is high. My se Linux is set to permissive. One Plus One on Euphoria ROM
[Xposed Framework Modules] ironictonic:
Hey guys,

I'm really interested in amplify since a lot of you are amazed by it's battery saving capabilities. But I just can't get it to work properly -.-

YES, I set SELinux to permersive,

YES, I got my Phone rooted and Xposed is running fine,

YES, I did uninstall and reinstall it and obviously rebooted the phone whenever necessary.

When i reinstalled it, it was checking root and was making sure everything is working correctly, it did. But all i see is the time counting up, everything else is still at 0 and the "Wacklocks", "Alarms" and "Services" tabs don't list any of those but only show the categories "Limited", Safe..." ...

Have tried to find a solution here and at reddit, couldn't find a thing.

best regards
[Xposed Framework Modules] Pkt_Lnt:
Start reading here.

http://xdaforums.com/showpost.php?p=59025734&postcount=4298

They are working on it and the next release should hopefully solve this.
[Xposed Framework Modules] zach_95:
I paid but had to do factory reset and I deleted the backup... If I download again would it restore?
[Xposed Framework Modules] cryptyk:
Yes, if you use the same google account.
[Xposed Framework Modules] aeoveu:
Alright, I'm throwing in the towel for location reporting. Apparently, my phone just seems to drain the battery regardless of what I throttle, so I'll just turn off location reporting and Google Now.

My findings do seem to be helpful (the entries refresh wake lock and traffic intent service) for throttling Now, but location reporting just seems to be a complete and utter b*tch.

BTW, quick question: Has anyone's phone entered a bootloop? Its happened a few times with me, and I've had to restore the system image a few times. Maybe its Xposed, or another mod, or something else... Not sure.
[Xposed Framework Modules] Takamoto:
Hi all..as I can reduce wakelock of SMSdispacher? Thanks.
[Xposed Framework Modules] AndroidBeginNinja:
Installed Amplify as system app

I just wanted to see what would happen. I have been doing it since feb 3
[Xposed Framework Modules] Jongla:
yes,i tried reboot,also reinstalled amplify but same thing happens..it finds and error,says to tick it and then reboot..

Sent from my C6603
[Xposed Framework Modules] cryptyk:
Go to Xposed installer, Framework. Soft reboot and see if that helps.

Thanks,

Ryan
[Xposed Framework Modules] AlexanderBig:
Not much context here, I'd just like to thank the dev for this amazing module, it really does a ton for your battery life unlike so many adware "battery savers".
[Xposed Framework Modules] trein91:
Feature request: long press entry to copy name of item and search it on google search.

Makes it so much easier to type in names of long entries.
[Xposed Framework Modules] Jongla:
worked after updating xposed framework.! ;)

Sent from my C6603
[Xposed Framework Modules] Dovidhalevi:
HW driver and ROM dependent. Big problem, worse than this, on my dinosaur. Use a battery saver to turn off WIFI when not using phone. Even though the initial blurb an Amplify said no longer necessary

This one is so far the only tweak that has helped. I am finally back to the battery life I had before recent Play Services "upgrades." Google's services are the culprits so finding stuff like this for Maps, Google+, Calendar, etc., would/should help.

1. All these things are interrelated. Side-effects!

2. Time figures shown are not necessarily meaningful. Wavelocks time blocked does not mean battery life gained.

Too complicated, too many side-effects, as I said.

Location reporting is now controlled by Maps options in newest versions which will not run on my dinosaur. So Now request I enable it and I have no way of doing so. Guess what? Can live well enough without it.
[Xposed Framework Modules] armando_rod:
Nexus 5 5.0.1 enforcing mode kernel, Amplify (installed from Play Store) works because in the Xposed log shows when is allowing the default wakelocks BUT the list of wakelocks is empty on the app, I cant even see the default ones this is with more than a week of use.

This is because enforcing mode? or is a known issue? (I searched and only 3 post were shown with no answer).
[Xposed Framework Modules] voland66:
Yes, it is a known issue due to the enforcing mode and according to Ryan the fix is coming.

Here is a potential solution:

http://xdaforums.com/showpost.php?p=59025734&postcount=4298

and here are Ryan's comments:

http://xdaforums.com/showpost.php?p=59039363&postcount=4309
[Xposed Framework Modules] armando_rod:
Thanks! Btw I did it manually and now is working as intended :D
[Xposed Framework Modules] beeshyams:
please help fix a problem

Hi OP and other experienced folks

Am using the pro version of this for a few months but didn't aggressively use it as I was trying multiple ROMs. Now settled down on TW 4.4.2 " deep impact", a heavily debloated TW ROM. Device is note 2 N7100

Problem- went on a overdrive throttling wake locks with a vengeance and things are under control . after about 6 hour's of idle , percentage wise wake up time is same as screen awake time. However, I guess I over did and the clock on the cell takes a long time to refresh. If I manually set the time , it reflects correctly but after some time lags. Clock is from network and not GPS, which I hardly use

Can somebody help me by pointing out the culprit which needs to be re set to default? All system wake locks are back to default but not able to fix this.

a related Q, which I haven't searched on the forum and may be answered. Unable to search not having access to lap top. Sorry for this. How do I get to see the complete list of washrooms . I may have changed one and it doesn't show up is my guess

Thanks in advance
[Xposed Framework Modules] aeoveu:
Hey, thanks for your response. I suck at quoting, so I'll try to make it short and quick (I'm already failing....):

- I don't see how this is HW driver (since we all have the same drivers) or ROM dependent (from what I've read, it has NOTHING to do with the ROM). I'm on bone stock configuration btw - except rooted and have Xposed installed, but nothing hardware-related is different. That said, we all should have similar levels of performance.

- Re. your turning off wifi point: you can save a bit of juice (at the expense of slightly better location accuracy) by turning off wifi. What really drains the battery (as per the internet) is when your phone scans and alerts you that an open wifi is present... although I'm not too sure how. That said, for me, I've got wifi location scanning on, and it doesn't seem to impact the battery too much. What impacts is if and when the wifi ship is in use.

- Play Services is a b***h! I'm still tweaking with EntriesRefresh_wakelock, so would definitely love to hear what everyone else is experiencing. I think we need to fiddle with these settings combination.... but I feel it'll be a whack-a-mole because Google keeps doing something different each time, so we have to trap it down.

- Damn, I miss London lol. /nostalgia

- The graph comment I made was arbitrary - it's just a graph, one might say, and rightly so - but because you're usually in control of your phone, you can sometimes recognize when the battery drain is higher than usual. I meant it from a relative perspective.

- Location Reporting, in older phones, came with a different label, nor can I remember how exactly Maps controlled it - but you might be right (because Google Maps checks for the settings as well when opening it for the very first time).

My phone's on charging right now. And I managed to score a drain of 0.2% on wifi once again in ~4 hours or so (there was some screen time of 5 minutes approx.). This is how it deduced it as 0.2%:

- Initially set a reference point in BBS.

- First two hours: drain was 0% (that's what the battery stats showed - and we know that they round off the figures).

- Second pair of hours: 1-2% (GSam said so) (I measured the drain from the moment the screen went off). When I went back to BBS, since the custom reference point was being used (I hope I'm making sense) and the drain was 0.2%.

Google really has made us go apes**t crazy. I'm glad we don't NEED Location Reporting to be enabled. Sure, Now sometimes nags us, but it works PERFECTLY FINE without it - all you have to do is refresh Now at whatever location you are, and it updates accordingly. I just wished that we could use Location Reporting without draining the battery significantly. I s'pose we can't.
[Xposed Framework Modules] Dovidhalevi:
We do not all have the same drivers. They are written by the OEMs, chipset designers, et al., for their hardware. A WIFI wakelock drainage problem is known for my device. Nothing to do with any other device, however, but other phones could have similar problems. Such a wakelock goes under Amplify's radar, outside of the "framework."

Other points: Battery drain graphs, while percentages are shown, are not really linear. This is in the chemistry and the chips in the battery. Milliamp monitoring is not supported by all devices and kernels--this might provide some better test data for those of us who can do it.

Anyway, when my sdcard died and I had a phone with no apps, no Google, nada, battery life was like that of a dumb-phone (which is what I had at that point).
[Xposed Framework Modules] Duck86:
Hi all!

I'm having some issues with Amplify, mainly that it is not working AT ALL for me. I'm using a Moto G 2014 running Titan Prime ROM and I have Xposed for lollipop installed. I have activated the module and rebooted. When I open the app the device stats almost always say 0 for everything. When I go into any of the other screens (Wakelock, Alarms etc), there is nothing listed and no options to do anything. Am I doing something wrong, or am I missing something here?

*I donated in the hope that I would unlock extra features and that this would solve my problem, but no avail, so now I have donated for software that doesnt even work for me :(
[Xposed Framework Modules] Redsandro:
Is this app permanently active, or only active while on battery?

I would like to put a lock on com.android.server.sip.SipWakeupTimer while on battery, but have it wake as often as it wants when charging. I cannot find information or settings about this behavior.

This so my VoIP line works while at the office, but not while on the road.
[Xposed Framework Modules] cryptyk:
[MENTION=5338090]Duck86[/MENTION]

http://xdaforums.com/showpost.php?p=59025734&postcount=4298
[Xposed Framework Modules] cryptyk:
Hi all,

I have a new version (attached) that should fix the SELinux problems. I needs some help testing. Can I ask for three people to test this version:

1) Someone with Lollipop + SELinux Enforcing

2) Someone with Lollipop + SELinux Permissive

3) Someone with an earlier version like KitKat

I want to make sure it works, and doesn't break old phones before I push it to release.

Thank you all so much!

Ryan
[Xposed Framework Modules] str8str:
Do you have Wi-Fi advanced keep Wi-Fi on during sleep? I always select never.
[Xposed Framework Modules] malteasers:
Forgive me if this has been asked before, but safe to limit *alarm* wakelock?
[Xposed Framework Modules] cmstlist:
I can test it on my Nexus 5. I assume that if I have rooted the stock 5.0.2 and installed Xposed, it should be in category 1) Enforcing?

I updated the APK and did a reboot. Amplify is definitely still enabled in Xposed. I will check in a few hours but here is an observation matching what I saw last night on the Play Store version:

- I open Amplify and press the reload button and I see "Stats collected for" ticking upwards

- I press Back to exit Amplify, then launch it again and it's still ticking upwards.

- I go to the task switcher and swipe it away. I launch Amplify again and it's reset to 00:00.

I see this is consistent with the other problems upthread but I assumed this version for Lollipop was supposed to eliminate that problem. Is there something special I need to do to allow Amplify to collect stats even after it's been killed? Cause it will get killed in the background at some point, guaranteed.
[Xposed Framework Modules] AA1973:
I can't see a difference, maybe I am doing something wrong. SlimLP in SELinux Enforcing Mode. Nexus 5.

As soon as I switch in Permissive Mode, everything is fine.

Enforcing Mode

Permissive Mode
[Xposed Framework Modules] cryptyk:
Got it. Sounds like the fix isn't working. I'll get a Lollipop test device tomorrow and debug it. Thanks for testing it out.
[Xposed Framework Modules] AA1973:
No worries. Happy to test it ?? keep up the good work. Just an idea. "Other battery stats apps" (BBS, GSAM) do install a second apk in system/priv-app in order to function properly. Would it help in your case too?

https://github.com/GSamLabs/GSamBatteryMonitor-RootCompanion

Ignore it if I am completely off-track. (Which is likely to happen) ?
[Xposed Framework Modules] voland66:
[MENTION=526666]cryptyk[/MENTION]

Ryan,

As you already know a clean install of 3.0.2 does not solve the problem. An update of a manually fixed installation might have worked (I am not sure anymore that I checked carefully). A restore from a titanium backup of a manually fixed installation also leads to a problem.

In more detail, I see that after the installation of 3.0.2 selinux context of the files in question is still

u:object_r:app_data_file:s0

instead of the context we want. I do not have sufficient knowledge of selinux at this point, but it is possible that system sets default app contexts after the installation, overwriting everything you specified in the apk. Maybe someone with knowledge of selinux can tell us what can be done in this case (if my guess is correct anyway). Alternatively, one could reset contexts during the first run (if that is not what you are trying to do in the first place).

On a slightly related note: reinstalling amplify gave me an opportunity to check which files need their selinux context changed. It seems to me now that it is enough to only change context of nlp* files in "files" folder, while the app's main folder and the "files" folder can have default contexts. I.e. only one command may be necessary:

chcon u:object_r:system_data_file:s0 /data/data/com.ryansteckler.nlpunbounce/files/nlp*
[Xposed Framework Modules] yanleites:
Can I please get help make the app working on lollipop?

Thanks!
[Xposed Framework Modules] Pkt_Lnt:
No one has it working on lollipop yet, give the dev some time to figure it out.
[Xposed Framework Modules] str8str:
Am I understanding that this is intact not working with the new xposed? That's a shame
[Xposed Framework Modules] dimm0k:
if you don't know how to read... there's little help we can do...
[Xposed Framework Modules] Pkt_Lnt:
http://xdaforums.com/showpost.php?p=59159874&postcount=4387
[Xposed Framework Modules] yanleites:
Or you can just be a normal user and explain it to me...
[Xposed Framework Modules] Pkt_Lnt:
This is not a simple app and you have to read and test and understand. We aren't big on holdy hands gloves and googy spoon feeding here.

It has been explained over and over, if I type it again, why would you read it when you will not read what was typed already? :(
[Xposed Framework Modules] jjl468:
Does anybody have any information on HostWithRpcCallback? The package name is Android Wear so I'm assuming it's related to syncing and maintaining connection with my Moto 360 but I only got it a few weeks ago and HostWithRpcCallback is already the highest wakelock that Amplify has a record of. Just wanted to know if anybody else sees this and if they have had any success amplifying it before I try it out myself.
[Xposed Framework Modules] PiggyFlooper:
Thank you for replying, it's been hard to get support on this thread- ask a question and 20 more are made so quickly. I may seem ungrateful, I'm very dissatisfied with your decision because back-support is definitely extending functionality of your module. I wish I was smart enough to do it myself, I don't understand git, pulls, hooks- it's blableeyaketysmackety to me. For I am a lowly user. This is my formal challenge to you to increase your dev skills. I hope you don't take this as an insult. I'm using persistence to try n get what I want- and portraying it as being a big help for many people:)

I don't think it's uncommon for one to ask for help when it's needed- http://xdaforums.com/showthread.php?t=2852950

Please overlook my attempt to be a jerk and reconsider backsupport, you, or anyone [MENTION=4775688]GermainZ[/MENTION]

Sent from above using Xparent Tapatalk Blue
[Xposed Framework Modules] shawn0223:
Thanks for the response man, unfortunately I'm at work so I can't use adb at the moment. Any other way to pull that info without a computer? Lol. I attached a screenshot of bbs since it was the one showing the counts. Hopefully I'm looking at the wrong thing and it's actually working. Would be a blonde moment for myself but at least we'd know lol.

edit: xda app is being gay. ill upload in a sec lol

got it i think

see how the google services shows 646 and the google serach shows 105
[Xposed Framework Modules] faboz84:
nothing wrong

i just don't know how to read the logging :D

thaks again!
[Xposed Framework Modules] cryptyk:
It's all good man. Just to explain: It's not a challenge to do it; I've been a professional software engineer for 19 years, and work on a product that millions of people use. It's just a question of what I'm going to spend my very limited amount of time on. I have a full-time job, two kids, and a really full life. If I have 20 minutes to work on NlpUnbounce, I need to decide whether I add a new feature that 95% of people are hungry for, or whether I backport so that 0.5% of people still on old Xposed versions can use it. Like everything, it's just a question of priorities.

That's also exactly why I opened sourced it. If someone else is passionate about backporting it, they can! I'm now just one of millions of developers that can work on the project. That means you don't have to convince me to make the change. You just have to convince someone :)

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
Got it. Strange - I'll take a look. Can you confirm your settings are 240,240,240,240?

Thanks,

Ryan
[Xposed Framework Modules] pugsang:
Yes the last line actually

NlpUnbounce: Alarm prevention is not yet supported on Android versions less than 4.2.2
[Xposed Framework Modules] shawn0223:
yessir, all are set to 240 and the debug log is unchecked. i uninstalled the initial release from my phone, installed the latest release, activated it in xpose and rebooted. didnt mess with any options. I'll pull a log via adb when i get home and post it up for you unless you know of a way for me to pull that info without a computer.
[Xposed Framework Modules] cryptyk:
Oh. That's expected for the moment. There's a limitation in the 4.2.1 (and earlier) API that prevents me from stopping the alarms. You still benefit from stopping the wakelocks, though. I have a plan to fix this, so you'll see it in a future release.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
Cool. An ADB logcat will be the best way to help.

Thanks!

Ryan
[Xposed Framework Modules] pugsang:
OK Thanks for replying.
[Xposed Framework Modules] shawn0223:
no problem man. I'll try to get you one when i get home tonight.
[Xposed Framework Modules] osvii:
Do i need this module?

Do i need this module?
[Xposed Framework Modules] cryptyk:
Yes, based on your second screenshot.
[Xposed Framework Modules] osvii:
but what do those numbers mean?
[Xposed Framework Modules] natezire71:
I still get the logs loaded with NPE errors.

Pastebin, NPE from Xposed Log

I'm on v4.4.2, on a MotoX.
[Xposed Framework Modules] cryptyk:
Can you verify that you're on v1.1.2? The easiest way to check is to make sure you have a "Debug Log" setting in the NlpUnbounce module settings.

Thanks,

Ryan
[Xposed Framework Modules] natezire71:
EDIT: I rebooted again and the logs are fine. Disregard.
[Xposed Framework Modules] cryptyk:
K. I can't tell from the exception where it's crashing. Can you do me a favor? Turn on Debug Logging in the settings and grab a logcat from boot? Something like:

adb logcat -v time | grep "NlpUnbounce\|Xposed"

You can either PM it to me, or add an issue on the BitBucket site, and attach the logfile there.

Thanks,

Ryan
[Xposed Framework Modules] natezire71:
I rebooted and the logs are fine. Disregard me. Sorry for wasting any time of yours!
[Xposed Framework Modules] rsngfrce:
Would there be any reason my msm_hsic_host kernel wakelocks would go way up after installing this (on standard settings)? They have, but I don't know if it was caused by this or something else. Of course, I could obviously disable it and find out for myself, but I just thought I would ask... :rolleyes:
[Xposed Framework Modules] s2d4:
It does work.

The link you are talking about is with regards to getting it to work in enforce.
[Xposed Framework Modules] Pkt_Lnt:
I'll take the dev's word on that.

http://xdaforums.com/showpost.php?p=59159874&postcount=4387
[Xposed Framework Modules] s2d4:
Did you actually read what you are linking?
[Xposed Framework Modules] Pkt_Lnt:
Yes, yes I did. They are having issues with the system app communication with the ui to show stats correctly and that is not solved yet. That is why cryptyk needs a lollipop device to trouble shoot. :p.
[Xposed Framework Modules] s2d4:
Ummmmm, yes in enforce mode. It works in permissive.

Read what he is actually quoting, which is one post above the devs post.
[Xposed Framework Modules] Pkt_Lnt:
I have read every single post in this thread from the beginning. It is not 100% working yet for everyone. More people have issues than have success.
[Xposed Framework Modules] s2d4:
Maybe comprehension is the issue here.

It was explained entirely in the post you claim to state it does not work on lollipop, hint: SElinux

My Nexus 6, apparently not running lollipop.
[Xposed Framework Modules] aeoveu:
Okay, I think I know what could be the culprit: its probably not Location Reporting, but instead, it appears to be the ICC Cricket World Cup scores lol.

Google Now seems to update the scores every so often - with no fixed frequency as such. Even though I've turned off location reporting and throttled the other wake locks above, it still drains the battery, since it seems to update Google Now fairly regularly, and its the only new thing I can see right now.

I honest don't know what's going on. I'm going to try and disable the sports scores, and pray for the best. This is the only logic I can think up of right now.