yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] adlx.xda:
Is this compatible with Greenify "Wake up Timer Coalescing" option? Any idea?
[Xposed Framework Modules] pham818:
Will the default settings this module came with be fine or should I have to set my own? And if I have to set my own, what should it be?
[Xposed Framework Modules] wilkster:
Just enable it in xposed, then reboot. All you need to do.

---------- Post added at 05:49 AM ---------- Previous post was at 05:49 AM ----------

Default should be fine.

---------- Post added at 06:04 AM ---------- Previous post was at 05:49 AM ----------

Good question. I think the KitKat alarm batching happens before nlpunbounce services the alarms so it should be compatible. Also i would hope google enabled the KitKat alarm timewindow for google play services already so time coalescing wouldn"t apply, but who knows. I just turned it on and will report back if I see a difference in behavior.
[Xposed Framework Modules] pugsang:
Same here.Only the initial release installs without errors. All other builds from OP or xordos give variousNoSuchMethodError as above post. Nevertheless I do not see it interacting and setting interval to 240 secs so I suppose it doesnt detecting NLP Reporting. Correct? Or is it something else?
[Xposed Framework Modules] trvbone:
I'm not sure what you mean here? You used greenify on the Google search and play services?

Sent from my USCC Note 3
[Xposed Framework Modules] knojap:
adb logcat -v time | grep "ALARM_WAKEUP_LOCATOR\|ALARM_WAKEUP_ACTIVITY_DETEC TION\|NlpWakeLock\|NlpCollectorWakeLock"

doesn't work in windows 7?

unknown "grep" blablabla

What do i have to do to get it work?

THX
[Xposed Framework Modules] wilkster:
If you want to see that it is working then look at your xposed installer logs.
[Xposed Framework Modules] knojap:
but I just want to see my default time before i install NLPbouncer
[Xposed Framework Modules] wilkster:
Ok, that info won't show up in the logs. Your best bet is to install Better Battery Saver. It will track your alarms and wakeups. Run it for a couple hours of normal use and then have it dump a text file of its results. There is an xda thread on how to use it and interpret the results.
[Xposed Framework Modules] xordos:
Have you tried the steps in post #288? Make sure you installed the build from post 74 properly.

Also, if you see post 264, the error is gone after he installed jb build.
[Xposed Framework Modules] knojap:
Got it.

I'm using Putty ADB!
[Xposed Framework Modules] xordos:
If you have adb working, just grep not found, then run following cmd

adb shell

logcat -v time | grep "ALARM_WAKEUP_LOCATOR\|ALARM_WAKEUP_ACTIVITY_D ETEC TION\|NlpWakeLock\|NlpCollectorWakeLock"

Then press ctrl-C to terminate the monitor.

adb shell will give you shell access to the phone, so be careful when you type-in (or paste) the 2nd command.
[Xposed Framework Modules] CheriePie:
I'm still catching up on the last several pages of this thread so I apologize if this has been covered; it didn't turn up in a search.

I recently used this mod to limit the alarm com.ticktick.task.action.DailyScheduleAction (for the todo app TickTick) which was showing an extraordinarily high amount of alarms on my tablet. I limited it to 120 seconds. I later had to reboot my tablet for something else, but now I'm not seeing com.ticktick.task.action.DailyScheduleAction listed on the Alarm tab at all anymore, not in the Limited section nor elsewhere. Shouldn't it still appear there even if it hasn't blocked anything? How can I modify this back to it's default if it's no longer showing up in Amplify?

One other oddity I noticed (and this I hadn't searched for but since I'm writing now I thought I'd add it), my Global Stats all show as 0 since I've been using Tasker to reset my Amplify stats on unplugged and reboot. And yes, I still have them set to participate (checked) in the settings.

Using latest version 2.0.4. Thanks for any insight. :)
[Xposed Framework Modules] Zordak7:
"controlling how often your device can wake up, and how long it can stay awake"

That's in the OP. 1) How does I control the time that an app can stay awake and doing its job?

2) And other question, when I unbounce (or limit or disable or tame) a service, is it totally blocked and won't do anything in the phone, like it never had been there?

And maybe some silly questions...

3) When BBS or Wakelock Detector show those wakelock times, do they include the time when the phone was awake and with the screen turned on? 3b) If they do that, can those apps make the diference between both kinds of wakelocks, those with screen on and off, of each wakelock?

4) And some of those "times" can be overlapped? I mean, if a Wakelock "X" shows 20 seconds, and a wakelock "Y" shows 15 seconds, can it be that those 15 seconds took place within the other 20 seconds, so the real time in which the phone was awake was just 20 seconds?? 4b) [idem with the time showed by Amplify on the stats?? )

Thanks!
[Xposed Framework Modules] .sunny:
Unbounce -> Amplify

Hey, when I updated to Amplify, app doesnt show any wakelock or alarms. I have donated version. What do with it?
[Xposed Framework Modules] Taomyn:
Leave it for an hour and check again - for me I simply left things alone and then the list appeared. Perhaps there's a "feature" that nothing is displayed until there is data to be shown?
[Xposed Framework Modules] Hongrois123:
Hi,

I pulled a log part last night and today and thought you might want to look at them why system errors occur.

-sometimes I have force reboots (2 per day)

-google services sometimes FC (mostly at rebbots if module is on), no problem, just tired of clicking OK

Using tasker plugin, but random reboots were present earlier too.

ps: pls dont chg the name anymore :)))

http://xdaforums.com/showthread.php?t=2673839 - using this rom and PA gapps in Huawei Ascend P7

thanks very much in advance
[Xposed Framework Modules] kyrillos13:
Lux auto brightness still working fine after limiting the alarm !!
[Xposed Framework Modules] Mistertac:
I've since gotten rid of Lux myself because I think it was causing more over head blocking all those alarms... And my stock auto brightness has been very good
[Xposed Framework Modules] dcd17:
Works fine this morning, so letting it sit for a while must have done the trick!
[Xposed Framework Modules] rydako:
I'm having this problem now as well. Though, since I appreciate Cryptyk's work, I'll just make a small donation with my second account. Very weird issue though.
[Xposed Framework Modules] LiFeSII:
Same here.

Using a LGD855 Stock rooted. Have to go back to 1.5.1
[Xposed Framework Modules] rydako:
Just thought, Is there a way to view the default, untouched settings for each wakelock/alarm? It'd be extremely helpful to compare adjusted settings to original. I'd imagine this has been brought up before, but can't find anything.

I had the same issue when updating, I removed the xposed module and reinstalled from the playstore and it seems to be working fine now.
[Xposed Framework Modules] LiFeSII:
Try that Playstore version now

Edit: Thanks, playstore Version worked!
[Xposed Framework Modules] bland.life:
Happened to me too.

Solved it by clearing data from its App Info page.

Then open the app and let it reinitialize.
[Xposed Framework Modules] Smithfolk4:
No Wakelocks Detected after Update

I had the same issue. Used the restore to defaults setting in the Amplify settings and it is working again.
[Xposed Framework Modules] Hongrois123:
if refreshing didn't work there are files in the shared data folder you can safely delete as root- you can chk earlier this thread which. or complete remove and reinstall
[Xposed Framework Modules] ericsmart:
for 6 hours and 52mins, my batt drained 1.3% even with lux running. I haven't set limit on lux, but I used myandroid tool to turn lux compatibilitycheck off...and I also used icebox's spreadsheet to set limits mostly on wakelocks, and barely set limits on alarms and it benefits my batt. but lux compatibilitycheck are still increasing numbers so is autobrightservice. I'm going to turn off with myandroid tool and or set limit on lux autobright service but...c'mon I would not to try and against my own judgement when batt is so good to me...but somehow, one or more apps aren't accurate.

sorry my English sucks, wonder if you could add ASL(American sign language) lol it'll be lot of pictures of hands anyway Ryan, thank you and good work.
[Xposed Framework Modules] Upakul:
Can the developer of the app help me with the Lux issue?

What is this compatibility check thing?
[Xposed Framework Modules] ericsmart:
I think compatability check is timezone, I might be wrong...
[Xposed Framework Modules] 1ceb0x:
Disabling autobrightness service from Lux will obviously make the app to not adjust the light of your display to the ambient light. You don't want to do that.

And Compatibility Check has to do something with checking your sensors. Think about how this app works. In order to be able to set the correct brightness automatically, it needs access to read your sensors and/or camera. Every phone is different, most of them have the same path for the sensors but some of them are a bit modified.. Compatiblity check comes in handy here. Since you are not able to test this app on millions of setups/phones etc, you need some service that can automatically check and find the correct sensors path for your device. This can explain the large number of triggers.

I stopped using Lux and i used the AOSP autobrightness and i am more than happy, since my phone's battery consumption is very low (9% per one hour of use continously) - i don't need a better auto brightness alternative.
[Xposed Framework Modules] ericsmart:
right, as I were saying compatibility check might comes with time zone and your saying with sensor 'automatically brightness correct and it makes sense, but I brought lux app and I would like using lux than for nothing meaning I got to do manual, some thing I would sacrifice to get my hands dirty, 1.3% lost almost 7 hours not bad.
[Xposed Framework Modules] cryptyk:
Hi all,

Version 2.0.5 is in the OP, Play Store, and Xposed Repo.

One thing I want to call out specifically is the Package names in the Alarm, Service, and Wakelock descriptions. This is the work of [MENTION=4354573]chhapil[/MENTION] , and it looks awesome. Huge thanks to him for adding the feature.

More stability, and some bug fixes. I recommend you download it because some of the bug fixes reduce the overhead of Amplify and result in better battery life.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
You seem to have a lot going on in those logs. I would try a couple of things:

1) Try disabling all of your Xposed modules, then re-enabling them one-by-one to see which is causing problems. I have a guess that it's not Amplify.

2) Try resetting your stats manually in Amplify (using the blue reset button on the home screen)
[Xposed Framework Modules] pugsang:
Hello [MENTION=526666]cryptyk[/MENTION]

I am affraid that 2.0.5 update broke things again. I am attaching the error log to take a look. Thanks

https://docs.google.com/file/d/0Bxq...3BUdzAwb19WbmhGUlBVUzVN/edit?usp=docslist_api
[Xposed Framework Modules] cryptyk:
Fixed it. I'm pushing 2.0.6 to the store now. Thank you so much for the logs of your crashes. It helps me help everyone!

thanks,

Ryan
[Xposed Framework Modules] MIKEMON:
What is this wakelock

audio out_2

or even 2013?
[Xposed Framework Modules] cryptyk:
Phew. It feels like things are stabilizing after the last few weeks of craziness. Thank you all for sticking with me as I've been getting things settled. 2.0.5 and 2.0.6 should be pretty close to what I consider a solid platform for going forward.

Thanks,

Ryan
[Xposed Framework Modules] mauam:
Just want to congratulate you for the RC badge, is more than deserved. You're amazing:cool:
[Xposed Framework Modules] cryptyk:
Thanks for noticing ;)
[Xposed Framework Modules] Zordak7:
Sorry for the auto spam :mad:

But i'm really curious about those things :confused::confused:

Saludos!
[Xposed Framework Modules] cryptyk:
By controlling the alarms, services, and wakelocks.

Alarms wake up your device, wakelocks keep it awake, and services run constantly in the background.

No. That's what makes Amplify unique. The alarm or wakelock can still wake up the device and keep it awake. Just not as often. Instead of Facebook waking up to check for messages every 2 minutes, you can allow it to only wakeup every 20 minutes (for example). You get better battery life without compromising functionality.

If you're looking for something that completely hibernates an app, check out Greenify.

Not sure. BBS is open source, so you can go look.

BBS already tracks wakelocks that turn the screen on (full) and those that just wake the CPU (partial). I don't know if it tracks partial wakelocks when the screen is already on.

That's correct. This is how amplify works. If two wakelocks overlap, it attributes the overlapping time to both wakelocks. Otherwise, how would you say which one of them was keeping the phone awake? They're both responsible. This can result in weird numbers (like a tracking time of 1 minute, and a wakelock awake time of 2 minutes). Not sure how else to think about it, though.

Not sure what you mean.

Thanks,

Ryan
[Xposed Framework Modules] wbedard:
[Update: The problems I describe below were with versions up to 2.04. Further testing with 2.06 has everything seemingly working fine on several devices. On my Nexus 5, the initialization checks added recently actually found an issue and corrected it.

I also wanted to add the the "spit and polish" that is being put into the user interface (i.e. MatDesign, etc.) is truly "top shelf." You continue to set a very high bar for your fellow Android devs! ]

I am following this issue closely as I have experienced similar issues with 2.x of this module on my Nexus5 (earlier versions work fine, though). Are the newer versions of this module known to be (in)compatible with XPrivacy? I just ask because it's one of the larger XPosed modules and hooks into a lot of things.

I'll try and get you a boot-time logcat this week but I think it will look a lot this this other one with "a lot of things going on."

R/

wbedard
[Xposed Framework Modules] Weetbix:
Amplify works perfectly fine with Xprivacy also installed (and enabled). I have both modules running on my Note 2, and I don't have any unexplained reboots/FCs/missing stats.
[Xposed Framework Modules] wbedard:
Thanks for relaying your experiences with XP and this module...much appreciated!

R/

wbedard
[Xposed Framework Modules] Black_Stark:
I have very simple question. Is this works on android 4.0.4 ICS version???
[Xposed Framework Modules] Smultie:
I have very simple answer; just try (or just read).
[Xposed Framework Modules] Black_Stark:
I asked coz playstore says 4.1 and above.

Could anyone tell me if it works on ICS 4.0.4 or not plsss ?? Just answer in yes or no .
[Xposed Framework Modules] Celestial Fury:
You know what would help? Being able to long press and COPY the services / alarms / wakelocks that we deny / limit so we can paste here to share what is safe or not.
[Xposed Framework Modules] Smultie:
Dude. It's a free app. How hard is it to just try??
[Xposed Framework Modules] m0han:
so, why ask if it works below 4.1? instead of (repeatedly) asking, try it out and post the result here, so others would (get a chance to) appreciate your chivalry.

edit: earlier versions worked on ics, i suppose. peruse the thread. also, you may take heart from this post by the dev.
[Xposed Framework Modules] Black_Stark:
I asked coz last time my friend installed on android 4.1.2 and he got reboots again n again. Also his google play stopped working. He only tested it on safe listed wakelocks n still got reboots.

I asked if any stability issues if i install it in 4.0.4 or any feedback dev got for ICS... Or if they currently working on it.

This is root app on based xposed.

I dont want to end up getting screwed in bootloops n end up in service centre. I m not wasting anybodys time by asking.

Thanks for giving me link. I appreciate.
[Xposed Framework Modules] SignetSphere:
Already searched the thread but didn't find any leads so figured I'd post this... but if it's been asked already please link me to the post and ignore my question.

[MENTION=526666]cryptyk[/MENTION]

Are you planning on adding a "search" function within the app? I bet it'll make things easier for all of us when we need to limit a certain wakelock if we can just search it cause when the app populates the list I find it hard to find some of the wakelocks that is safe to be limited.
[Xposed Framework Modules] 1ceb0x:
I want to be a smartass and say - if you don't know how to recover from a bootloop, i don't know what you are doing playing with root and xposed in the first place..........
[Xposed Framework Modules] wolfwork:
add my nick to translation credit

i upload korean translation string

but i am not placed in translator credit ?

plus : please insert new korean string it changed..
[Xposed Framework Modules] m0han:
read the thread well. lots of others got reboots as well. obviously, your friend's situation was different/unique in some way. did he tell you how his problem got resolved? ;)

if you want to get the dev's attention, tag him like this: [MENTION=526666]cryptyk[/MENTION] - or pm him. but, not with your question relating to ics; he's already answered that. it helps to be patient. :angel:

if you're rooted and have a custom recovery, what stops you from taking a nandroid backup and experimenting with this module? you can restore your phone back as before in a jiffy. :good:

you first have to decide whether you really need this module. from what i gather, if you don't have location services 'on' all the time, this module might not be of much help.

you can also find out if there's a 4.1.x os upgrade available for your device/rom. and, check your device forum to see if others have used this module. get their opinion.

lastly: if, like you said, you "dont want to end up getting screwed in bootloops", use your phone the way you got it when you bought it. :D
[Xposed Framework Modules] Jar3112:
+1
[Xposed Framework Modules] 1ceb0x:
False. This module is not about ONLY NLP anymore. You can amplify basically any wakelock now, of course, you need to donate first to do so.
[Xposed Framework Modules] Black_Stark:
Hahaha.... :D:D...thks for ur attention. U both r very cute.
[Xposed Framework Modules] kingvortex:
You probably won't even be able to install the newer versions that require Jellybean, as the minsdkversion is probably set to Jellybean and you will therefore receive a parsing error when installing. I can't be sure of this as I don't have an ICS device to test, but it's almost certainly the case.

As others have said, if you're determined to try, you should make a backup of your system and just try it. If it even installs, it may cause issues or just not work as the module will probably try to hook things that don't exist in ICS roms.

I would also advise you to read around your device specific forum to find out how to recover from problems/bootloops etc. It's essential knowledge if you're going to use experimental software on your device at all. ;)

Sent from my C6603
[Xposed Framework Modules] Taomyn:
I'd like to make a comment regarding the interface of the app, the behaviour of the back button. Is there really a need to remember every change of area visited in the app? If you go Wakelocks, Services, Wakelocks, Alarms, Wakelocks, Alarms, then hit "back", you'll go through all 6 screens and the home one before the application closes. Overkill or as intended?
[Xposed Framework Modules] Ikkuh84:
+1. I use the back button for quiting an app, but with this one I have to press 4 times back because all the screens. Or maybe an exit button?

Verstuurd van mijn GT-I8190
[Xposed Framework Modules] m0han:
which ics users are gonna 'donate first' and see if it works on their rigs at all?!

and, which users who "don't know how to recover from a bootloop" are gonna amplify basically any wakelock?!
[Xposed Framework Modules] vsa:
heading for german language to big

Hello,

one (design) bug: due to the big font you use for headings, the text is too long for german (language) words and the automatic wordwrap looks awful since the last 4 versions....

Please reduce the font size in headings...

thanks vsa
[Xposed Framework Modules] Gizmundo:
Application its self eating the battery, is it only me who notice that? It figures on the first ranks in BBS in services also eating data even when global stats are off. I've managed to drop the battery consumption to 0,2 overnight and I thought I drop it more with this very good looking app but I don't know now.. I didn't set up anything just started measuring the stats..
[Xposed Framework Modules] netweaver2009:
How did you manage that? That's v v low. You must be sacrificing something to go that low. Care to share your magic?
[Xposed Framework Modules] Gizmundo:
0.2/hour..2% in 9 hours.. sorry for confuse you. The point is that I did it without amplify. Now I wanted to do more improvements with unbouncing the wakelocks but it seems that the consumption is higher with amplify. I hope I'm wrong I keep testing.
[Xposed Framework Modules] Nokiacrazi:
I think the question was how are you running your device to get 0.2% / hour drain (presumably idle).

ROM? FW? Mods? Greenify? Low brightness, power saver, auto sync off etc?

You know just your setup and usage habits kinda thing..
[Xposed Framework Modules] tboooe:
I also get around 0.2-0.3% battery drain per hour at idle with all Google sync services on. I have a Note 3 running a custom rom but since it is from ATT I cant load a custom kernel so no fancy power saving CPU changes. I also use Greenify, Lux auto brightness. Lately my biggest battery drain aside from Android System and Kernel is Inbox. It seems to use way more battery then Gmail.
[Xposed Framework Modules] Gizmundo:
Note3 stock, stock kernel, mods no, greenify yes, sync yes, wifi yes, Bluetooth NO, location NO, get rid of few bloatware, turn off few services via disable service, same services restricted with receivers + more unneeded staff in autostarts. I do not see reason to buying a powerful phone and then cutting off the performance. I do not need Location,Bluetooth to be on all the time just when I need it like navigation, that does a lot. Thats it

I will test it without any modification via amplify, just let it run this night to see if there is a reason to keep it
[Xposed Framework Modules] cryptyk:
In theory, yes. But right now I have the app set to only install on API level 16 devices (Jelly Bean). I plan to open it to ICS in the future, but want to test it personally first to work out the kinks. Unfortunately I don't have an ICS device. If you'd like to beta test an ICS build, shoot me a PM.
[Xposed Framework Modules] cryptyk:
Already on the list :)

I also plan on saving your profile in the cloud so it remains between rom flashes, etc. Then you could also use someone else's profile.
[Xposed Framework Modules] cryptyk:
It's on the list, here: https://github.com/rsteckler/unbounce-android/issues/73

Also, all lists now support sorting by name. That should help a little, at least.
[MENTION=4354573]chhapil[/MENTION] is also working on sort by package name.
[Xposed Framework Modules] cryptyk:
Sorry about that! The next version I push will have the updated translations and credits. Thank you for your contribution to the project!

Ryan
[Xposed Framework Modules] cryptyk:
Thanks. I know the German translation could use some love. I'll try to reduce font sizes for you guys.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
It's actually intentional, per the Google design guidelines. The same thing happens in other modern Google apps. Try the Play Store for example. Go to My Apps, then Apps, then Books, then People, then start pressing the back button. It navigates through them all backwards before exiting.

I agree it's weird, but so far I've decided to stay with the experts on this one.