yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Osama Zabin:
Check this link, it explains the ActivityManager Wakelock.

Activity Manager

http://developer.android.com/reference/android/app/ActivityManager.html

Activity Manager is a system process and looks after processes including tasks you have recently started, running processes, or those that may be in an 'error' position.

If you were not to use your device for a while then this activity will be very low. If however you were to have opened lots of apps just before turning your screen off, then this activity will be active for a while before entering true deep sleep.

Activity Manager is normal. If you stop it your phone won't work. If you want to reduce it's 'footprint' however, make sure you exit apps you no longer need before turning the screen off. By this I mean pressing the back arrow to exit them rather than pressing the home button to return to the homescreen - and leaving them running in the background.

Just to re-iterate on hitting the back button to leave apps and why it helps reducing wakelocks. It is related to the lifecycle on activities (jargon for windows). You can see onPause is an important transition because it's the transition where the persistent state is to be saved (eg to a database). Pressing back on an activity calls onPause, meaning android can remove the app without the overhead of doing I/Os and the associated Garbage collection later as it does that straight away.
[Xposed Framework Modules] cryptyk:
NO! Please don't Unbounce that one.
[Xposed Framework Modules] cryptyk:
Honestly, it sounds like you might be trying too hard. You have a lot of different apps trying to manage your battery and they might be conflicting. I would pick one at a time and see which gives the best result. Most people here user Unbounce and Greenify together to good effect.
[Xposed Framework Modules] cryptyk:
Do you have location services turned on?
[Xposed Framework Modules] cryptyk:
Which message are you getting (exactly)?
[Xposed Framework Modules] tboooe:
I understand stopping logcat can be done on init.d or build.prop.

In build.prop add this line:

Logcat.live=disable

I look forward to hearing your results.

After two days I feel there is a definite improvement in battery at idle. I normally am at 0.2-0.3% drain per hour now I am at 0.1-0.2%. Not a big deal really but it's fun to see how efficient we can make our phones!
[Xposed Framework Modules] Nokiacrazi:
I'm at 1% per hour. Will try and get that down.
[Xposed Framework Modules] tboooe:
I have all sync on except for Gmail. I will activate and see what it does to my battery drain.
[Xposed Framework Modules] 1ceb0x:
I now use MyAndroidTools and it works perfectly. It does not consume that much as 3c toolbox and i am happy :).

BetterBatteryStats is free for xda users :). Search the threads using Better Battery Stats and you will find it.

Good luck!
[Xposed Framework Modules] wolfwork:
where is Korean translation?

I need new translation lang : korean

Cloud you add new lang(korean) on translation site?
[Xposed Framework Modules] lateral18:
Hi

The app is been working great ,

I have a question , the network location isn't showing , even when I've enabled the wakelocks for it , only shows when the GPS locks

Yes location is on settings
[Xposed Framework Modules] cryptyk:
Done!

Thanks for your help!
[Xposed Framework Modules] cryptyk:
Sorry - I don't quite understand. Where is network location not showing up?
[Xposed Framework Modules] lateral18:
In Google maps
[Xposed Framework Modules] cryptyk:
Oh. Make sure location is also turned on in Google Settings (in addition to your regular device settings). Also make sure Wifi is turned on.
[Xposed Framework Modules] lateral18:
It is turn on,

Now with the new version. Network locations isn't available to show on maps , ?? Only with Wi-Fi

Using tasker I have a profile enabled to enable the alarms and wakelocks when maps is open. But it doesn't seem to work

With WiFi I do get the point of the location though

I use maps a lot

Lol
[Xposed Framework Modules] scy1192:
I'm having a problem with it not detecting root. I'm on an LG G3 vs985, rooted and using the SuperSU app. Root Checker says I'm rooted, and I've had no problems with root access in the past. It doesn't give me a pop-up to grant root, and SuperSU has no record of it ever requesting root.
[Xposed Framework Modules] cryptyk:
Sending you a PM to see if we can figure out why.
[Xposed Framework Modules] scy1192:
Not sure my PMs sent (guess it's just one of those days where technology turns against me), but I figured it out. I just updated busybox (1.20 -> 1.22) and it started working.
[Xposed Framework Modules] cryptyk:
Good to know. Thanks for looping back!
[Xposed Framework Modules] scy1192:
Yeah it looks like whatever I used to install busybox only put the busybox binaries in xbin instead of all the other binaries, so you would've needed to do 'busybox which su' instead of 'which su'
[Xposed Framework Modules] Skhulile:
Root Access? - Just Curious

Hello, first wanna say thanks for this amazing module:good: I see in the latest version you added some start-up checks for unbounce, xposed and root access. .. well I'm just curious that why does it also have to check for root? It has never asked me for root permission, it's not even listed in SuperSU, so I feel like maybe I'm missing something, it even told me that "something went wrong" on the startup root check, rebooted the device and it didn't show up the error again, so i'm just curious about why have it has never asked for root permissions?:)
[Xposed Framework Modules] cryptyk:
It checks for root so I can tell people who don't have root what the problem is :) You'd be surprised how many emails and one star reviews I've had because of people who install this on non-rooted devices.

Unbounce checks for root, but does so without requiring it. Once it's running correctly under Xposed, root access is assumed.

Thanks,

Ryan
[Xposed Framework Modules] picklu:
Amazon Coin for PRO features!

How can I purchase the pro features via donating amazon coins? If that feature is included then it will be very good for many of us! :)
[Xposed Framework Modules] Skhulile:
Oh I see, makes sense now:good: though surprisingly I'm rooted but it said "something went wrong"
[Xposed Framework Modules] cryptyk:
Which screen did you get after "something wrong"? Did it say you weren't rooted, or just that you needed to enable Unbounce and reboot?

Thanks,

Ryan
[Xposed Framework Modules] picklu:
216

any luck for Amazon coin to get PRO features! I really like your this module!
[Xposed Framework Modules] Skhulile:
I selected "Fix It" it took me to my Xposed modules tab, so since it was enabled already I disabled it and enable again then rebooted, it never said I'm not rooted. . But come to think of it it might have said that as after updating to 1.4 I didn't reboot the device, I just went straight on to open the app
[Xposed Framework Modules] cryptyk:
Cool. Sounds like it's working :)

Thanks!

Ryan
[Xposed Framework Modules] cryptyk:
Thanks for the idea. It's not super high on my list right now, but I'll keep it in mind. There just aren't that many people using the amazon store for root apps.

Thanks,

Ryan
[Xposed Framework Modules] asdfasdfvful:
You gave it root right? You could try moving it with titanium backup
[Xposed Framework Modules] engashelpdesk:
Thanks for this app.
[Xposed Framework Modules] rignfool:
TiBu moves it to /system/app/

The app need /system/priv-app/
[Xposed Framework Modules] 1ceb0x:
As much as i like seeing people helping others, please direct your problems in BBS thread. I am sure people there will help you and i am sure you are not the first one having this problem so a search first will do wonders :).
[Xposed Framework Modules] engashelpdesk:
First of all I want to thank you for this very helpful app. I successfully installed it to my lg g2 with out any problems.

By the way, when I installed it to my Lg L9 with JB, its says that my L9 is not rooted well infact that it is rooted because I successfully installed xposed framework, setcpu, and other apps that requires root access. Hope you can help me. Thanks in advance.
[Xposed Framework Modules] marbulas:
[MENTION=526666]cryptyk[/MENTION]

Unbounce says it doesn't activated on the list of xposed modules even if I did already. What'd I do?
[Xposed Framework Modules] jaibar:
Did you try a reboot?
[Xposed Framework Modules] marbulas:
YES. And I tried to reinstall xposed framework and this module but the problem stills.
[Xposed Framework Modules] xk0niR:
Maybe clear Cache and Data of Unbounce helps?
[Xposed Framework Modules] tylerdurden83:
I still have issues making sense of the unbounced stats.

In the homepage it says that the blocked wakelocks account for 19 minutes, in the wakelocks tabs they account for a lil less than 1 min and a half....

How can this be?

Thanks,

TD
[Xposed Framework Modules] dimm0k:
I believe the numbers you see in the tab refers to the amount of time it was allowed. if you go into that specific item, it'll tell you the time it was blocked.
[Xposed Framework Modules] furboom1240:
You're absolutely right

As usual, I lost battery life tremendously overnight on airplane mode. However, I have purchased a donation package in the past from Oasis Feng and boy, was it useful! As soon as I put my desired apps on Greenify, my phone finally quieted down. THANK YOU SO MUCH FOR YOUR SUGGESTION, [MENTION=526666]cryptyk[/MENTION]. I think my phone has finally found peace. I will report to this thread later if it tanks.
[Xposed Framework Modules] dimm0k:
FB, Messenger, chat apps

Just wondering what Unbounce numbers people here use for FB/Messenger and other chat apps without losing functionality. I've been using Greenify to tame FB/Messenger, but perhaps the previous beta of it was buggy so I wasn't getting notifications, so I removed them from Greenify and that's when wakeups/alarms for those two was off the charts according to BBS. Is the preferred method to just Greenify those two or Unbounce?
[Xposed Framework Modules] tylerdurden83:
If I go into the specific item, I'm even more puzzled by the stats...

As you can see, I slightly bumped the 240 seconds to 300 seconds for this wakelock. It shows that it was blocked 230 times, and was let throught 18 times. That seems reasonable, but then I looked at the times, and it says: time allowed = 0 seconds, time blocked = 1 second.

Those don't really sound right to me.

In the op it says, in regard to this specific wakelock:

Therefore, for 18 allowed wakelocks, I expected a allowed time of at least 5*18 seconds, and for the 230 blocked ones, I expected a blocked wakelock time of at least 5*230... Instead of 90 seconds for allowed and 1150 seconds for blocked, I see 0 and 1 seconds respectively....
[Xposed Framework Modules] xk0niR:
I just use Messenger and unbounced every related Wakelock/Alarm except the mqtt push and it seems to be fine
[Xposed Framework Modules] Zordak7:
Hy again

Don't want to be annoying, just another detail about the problem.

In those apps, BBS and Wakelock Detector, the wakelocks have, in their description, the count number in zero (it says x0 in WD for example), don't know if that has anything to do with the issue that Unbounce can't detect "SMSDispatcher" wakelock, and another one which is also pretty bad and doesn't let the phone to go into deep sleep at all "copresGcore_EventLoop"

Thanks! and thanks again for the app, really helps with battery duration!
[Xposed Framework Modules] dimm0k:
Hrmm, I never really took a look at the math behind it, but after taking a look, it does look like the numbers are off for the time. There may be a better explanation as to why, which I'm also curious to hear now.
[Xposed Framework Modules] magnamentis:
learn

two posts, both with false expectations due to lack of knowledge.

a) stats show the allowed time so you can have any number of wakelocks blocked and the remaining allowed time will be the shorter

....so the stats seam to be totally correct, at least as far as to your concern. the absolute numbers nobody is able to and/or can verify.

b) why do you assume that a wakelocks has to be in seconds, just consider the possibility that 850 wackeloks of 1 millisecond are not even 1 second cummulated, hope this guides your thinking into the right and more fruitful direction

by the way, why should it matter, if the app blocks thousands of wakelocks and alarms for you that's what i is supposed to do thus "GOOD"

and if you see better battery life in "serious" comparison that's what this is all about, so we should not bother too much with superficial details IMO
[Xposed Framework Modules] cryptyk:
I've just fixed this, and will roll the new version in just a few minutes. Sorry for the inconvenience! With so many root methods, it's pretty hard to check reliably. I think we'll be good now, though.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
Hi,

Please standby for the 1.4.1 version which should help this.
[Xposed Framework Modules] cryptyk:
Couple of things:

First, every phone is different, and they're even different in varying environments. When I first set out to fix the Nlp problem, my S5 held NlpWakeLock and NlpCollectorWakelock for an average of 10 seconds every minute! That's where those numbers come from. My new HTC One M8 (stock) is much better, and only holds it for less than a second. Wifi, cell towers, signal, etc, all play into this.

So here's the math I use for a given wakelock:

# of times allowed: obvious

# of times blocked: obvious

Total duration allowed: The addition of all of the time between acquisition and release of the wakelock. This may underreport because of wakelock nesting, but it should give you a rough idea. WLD and GSAM are probably more accurate.

Total duration blocked: I can't know how much time is blocked, because I didn't let it happen :) Instead, I show:

(TotalDurationAllowed / NumTimesAllowed) * NumTimesBlocked

The stats could be better. I admit. I hope they're good enough to give people a sense for what's killing their battery. The guys that are chasing from 0.2% to 0.1% drain/hr are hardcore, and numbers get especially wonky at that level.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
I've fixed this in the upcoming version :)
[Xposed Framework Modules] cryptyk:
Well said. There are problems with the stats, but they should be directionally correct. Don't get hung up on them - just use them to get your battery life to where you want it.
[Xposed Framework Modules] cryptyk:
Hi everyone,

Version 1.4.1 is posted. A couple of changes:

- Fixed a lot of root checking issues. Sorry about that! It should be much better now.

- Fixed the missing wakelock and missing alarm bug. Exchange, FolderSync, GoLauncher, and some others will now be visible.

- Added a new teaser for some upcoming functionality. Can you find it?

Thanks,

Ryan
[Xposed Framework Modules] khairulez:
Yep..

Services Started

Services Blocked

Thanks for updated.
[Xposed Framework Modules] Mistertac:
Services?!

Very cool
[Xposed Framework Modules] MIKEMON:
thanks for the update and your explanation
[Xposed Framework Modules] tylerdurden83:
Thanks for the perfect explanation Ryan. Btw I updated the italian translations, let me know if there is any problem with them!
[Xposed Framework Modules] Osama Zabin:
Hi Ryan,

Would you please check the attached log? the new version 1.4.1 keeps crashing after successfully passing root/xposed check.

Thank you in advance.
[Xposed Framework Modules] cryptyk:
Can you try deleting the four files in your /data/data/com.ryansteckler.nlpunbounce/files directory?
[Xposed Framework Modules] kingbeta:
Updated to 1.4 and I'm getting FCs again. This happened on all of the last 3/4 updates. Last time I ended up clearing app data and starting again. Anything else I can do? Uninstall doesn't change it.
[Xposed Framework Modules] Osama Zabin:
Many thanks for your super fast response. It's not crashing anymore.

:thumbup::thumbup::thumbup:
[Xposed Framework Modules] cryptyk:
I'm not quite sure why the crashes on updates happen, but you can delete the 4 files in /data/data/com.ryansteckler.nlpunbounce/files to fix it. I'll try to figure it out, because it sounds like a few people have the problem.

[EDIT] If you haven't already fixed this yourself, can you wait a second? I have a test build I can send you that should hopefully fix the problem. PM me and let me know! [/EDIT]

Thanks,

Ryan
[Xposed Framework Modules] kingbeta:
I deleted the files and rebooted, problem solved thanks. Sorry didn't see your message in time to try the test build.
[Xposed Framework Modules] marbulas:
1.4.1 still has a problem. Unbounce says it is not an activated module even if I already.

And much worse thing is previous builds are not working properly also. What happened on 1.4?

So I rolled back the version to 1.1.4. Now seems fine.
[Xposed Framework Modules] Weetbix:
1.4.1 correctly appears for me as an activated module. Installed via the playstore...
[Xposed Framework Modules] engashelpdesk:
Thank you very much sir. I really appreciate it....
[Xposed Framework Modules] xnap30:
Sort by time still not working properly for me.
[Xposed Framework Modules] cbomb101:
Alarm and activity manager have high wakelocks for me. Already unbounced them.
[Xposed Framework Modules] 1ceb0x:
Good luck with that...both of them are unsafe to unbounce. you unbounce alarm manager you render Unbounce Alarm page useless.
[Xposed Framework Modules] shinra00:
Thank you Xordos
[Xposed Framework Modules] wilkster:
No, only when you update the app.

Sent from my VS980 4G
[Xposed Framework Modules] nIGhT-SoN:
Thanks for the fast reply.
[Xposed Framework Modules] CheesyNutz:
this module has helped my battery life for sure can't wait for the dev to put this on the repo for easy updates !
[Xposed Framework Modules] tylerdurden83:
So all the ppl that reported benefits suffered from placebo?
[Xposed Framework Modules] dimm0k:
I have location reporting turned on, as well as location history, but I don't see this mod working at all... I'm on 4.4.2 for the Samsung Galaxy S4 from Sprint. using the two logcat commands in a terminal from the OP's instructions I see nothing from logcat. Am I missing something?
[Xposed Framework Modules] wilkster:
Only very slightly. This was only one of four alarms/wakelocks.

Sent from my VS980 4G
[Xposed Framework Modules] Poine001:
Nice mod.
[Xposed Framework Modules] mwrobe1:
Thanks for this...I am running 4.4.2 and can confirm this fix, log snippet below.

Aug 27, 2014 8:52:55 AM NlpUnbounce: Allowing ALARM_WAKEUP_LOCATOR.240000

Aug 27, 2014 8:52:55 AM NlpUnbounce: Allowing NlpWakeLock.240000

Aug 27, 2014 8:52:55 AM NlpUnbounce: Allowing NlpCollectorWakeLock.240000

Aug 27, 2014 8:56:21 AM NlpUnbounce: Allowing ALARM_WAKEUP_ACTIVITY_DETECTION.240000

Aug 27, 2014 8:57:29 AM NlpUnbounce: Allowing ALARM_WAKEUP_LOCATOR.240000

Aug 27, 2014 8:57:29 AM NlpUnbounce: Allowing NlpWakeLock.240000

Aug 27, 2014 8:57:29 AM NlpUnbounce: Allowing NlpCollectorWakeLock.240000

Aug 27, 2014 9:04:47 AM NlpUnbounce: Allowing NlpWakeLock.240000

Aug 27, 2014 9:04:47 AM NlpUnbounce: Allowing NlpCollectorWakeLock.240000

Aug 27, 2014 9:05:58 AM NlpUnbounce: Allowing ALARM_WAKEUP_LOCATOR.240000

Aug 27, 2014 9:07:47 AM NlpUnbounce: Allowing ALARM_WAKEUP_ACTIVITY_DETECTION.240000

Aug 27, 2014 9:11:21 AM NlpUnbounce: Allowing NlpWakeLock.240000
[Xposed Framework Modules] dimm0k:
Thanks for posting this... I retraced the conversation and realized I missed the post for this as I'm using 4.4.2 and it looked as if I had no wakelocks!
[Xposed Framework Modules] Shisma:
Finally a solution for this wakelocks!!! I have only a question, I've setted all the tabs with 900 seconds, but in partial wakelocks have high counts of NlpWakelock:

It's normal?

Galaxy S4 with 4.4.2.

Inviato dal mio GT-I9505
[Xposed Framework Modules] xordos:
No, that's not normal, you have 66 wakelock in 1 hour.

Please check your XPOSED framework log, also make sure you rebooted your phone.
[Xposed Framework Modules] Shisma:
I've downloaded your apk, disabled and uninstall old apk, reboot, install new apk, activate it and reboot, set all the tabs to 900 and reboot again.

Edit:

Have 350 NlpCollectorWakelock.
[Xposed Framework Modules] mgbotoe:
Hey guys is there a value to disable completly? What's us every one set up? I put in 600 seconds for all 4 values. Advice ease!
[Xposed Framework Modules] Pkt_Lnt:
Use 86400 :D
[Xposed Framework Modules] xordos:
Thanks for the log, the log looks normal, it only allow the wake lock every 15m as expected. So I have no idea if you do see 350 wake locks, sorry.
[Xposed Framework Modules] Shisma:
Thanks to you for your hard work, reboot my phone and start a new monitoring(1 hour), no NlpCollectorWakelock but 38 NlpWakeLock. Alarms seems to be ok.
[Xposed Framework Modules] abbz123:
Damn bam dmux wakelock sucks =(
[Xposed Framework Modules] mwrobe1:
Yeah...+1 with there still being an issue.

Rebooted and it appears that the log reporting issue is fixed, but NlpCollectorWakeLock appears to be unaffected/acting pre-module...got a 86 count for 13mins of up time since boot. NlpWakeLock is behaving as expected (2 count). Note I'm running with the default 240 setting.
[Xposed Framework Modules] cbomb101:
What! I didnt know that! Thank u for letting me know. I dont think it said anything in description. ill disable them 2 from being blocked. The app force closes alot to when clicking on wakelocks. How do i send u a log.
[Xposed Framework Modules] desertmod1:
I'm the one with the android 4.2.1 that the alarms didn't show anything and now with the latest update I can see them.
[Xposed Framework Modules] kingbeta:
There are lots of alarms and wakelocks your phone needs to run properly. They don't necessarily keep it awake when sleeping. For real stats on wakelocks while screen is off, look at better battery stats specifying the range between screen off and screen on (use watchdog), or reset your Unbounce stats before a long screen off.
[Xposed Framework Modules] DB126:
Unfortunately, after a more extended test I found average consumption with Unbounce enabled was greater than without. Same problem as before: WiFi activity would spike for no apparent reason keeping phone awake for extended periods. This typically happened right after completing a charge cycle; later in the day the phone would usually (albeit not always) sleep peacefully. I experimented with a few different 'safe' alarms and wakelocks but it didn't seem to make a consistent difference. While the lowest drains with Unbounce active where impressive my average daily consumption (20% active use; 80% idle) typically didn't improve.

Keep in mind my handset (XT1030) was well behaved prior to installing Unbounce with commendably low idle drain rates. The many positive reviews in this forum and elsewhere demonstrate the value of Unbounce. That said, if you have already 'optimized' your device for power savings Unbounce may not get you much further. You'll also want to test over an extended period as initial results looked good for me on two occations but then deteriorated over time.
[Xposed Framework Modules] magnamentis:
perhaps it is about time to remind some that wakelock occur while in idle mode of course, but as well while the device (apps) are in use. so if yo want to optimize your battery stats you have to test in idle mode because while sceen is on wakelocks might count for your stats but have little to no impact on battery life.

same with rading stats. if yo play music you will see tons of mediamix wakelocks which you can then discard. or if you navigate you will see tons of range of location based wakelocks in stats to discard as far optimization is concerned. so if you are interested in least intrusive optimizations you have to reset stats to 0 and use stats from idle periods only to judge.

little preliminary question to [MENTION=968402]cryptik[/MENTION]: since the future of xposed in its current form ( compatible with almost all roms and devices) is in jeopardy or at least questionable, did you consider to make it a common root app eventually?

Sent from my A0001