yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] nvo2411:
On 2.03, working great, battery amplified truly
[Xposed Framework Modules] cryptyk:
Interesting. What Android version is your device?
[Xposed Framework Modules] cryptyk:
Sorry - I'm still working through the Play Store stuff with Google. It should work if you're non-US, but folks from America will need to wait still.

thanks,

Ryan
[Xposed Framework Modules] cryptyk:
It's very likely that the services are actually running like that. Amplify isn't making the numbers up :)
[Xposed Framework Modules] cryptyk:
I think I found the problem and fixed it. Thank you for the logs. Can you try this version and see if it works?
[Xposed Framework Modules] khairulez:
Aha..finally!

It works,all stats appear.great work [MENTION=526666]cryptyk[/MENTION].

Thank you so much.
[Xposed Framework Modules] wilkster:
you are probably better off freezing the apps vs disabling all of their services. Interested to know how they work like that.

Sent from my VS980 4G
[Xposed Framework Modules] CHEF-KOCH:
Most things are for ads, user tracking and analytics. Yes, it's a horrible app which ends up in battery drain and spying. Only one we can do is, restrict most things via xprivacy and give Bad reviews on the market so that they need to remove it asap.
[Xposed Framework Modules] HDFLucky:
Updated to v2.0.3 earlier over an hour ago, and the "Home" stats simply will not populate... even after pressing Reset and multiple reboots. Some (but not all) stats appear under Wakelocks and Alarms (no Services set). For example, NlpCollectorWakelock, which is usually my biggest culprit, is totally MIA. Also, the vertical scrollbar on the Wakelocks, Alarms, and Services page is offset to the left and obscuring the displayed info (it's okay on the Home and Settings screens though). Logcat attached - the 'thermal' alerts are from elementalX kernal, and due (I think) to having a conservative thermal foldback set while running the phone on charger.

(Nexus 5, stock 4.4.4 ROM, elementalX)
[Xposed Framework Modules] poodleDoo:
I also updated to 2.0.3 about 30 minutes ago, and it seems that in the update from Lion Tamer to Amplify, it lost the settings I have.

Actually it seems to be "discovering" the alarms and wakelocks, as time passes, more of them are starting to show on the respective screen...

I have the donation pkg if that makes any difference
[Xposed Framework Modules] MIKEMON:
Update to 2.0.3 seems to be fine

we'll see after some time of use
[Xposed Framework Modules] cryptyk:
It may not be showing up because it's blocked, and is therefor not being granted.
[Xposed Framework Modules] cryptyk:
That's normal. The upgrade reset your stats. Now they need some time to show back up.

Thanks,

Ryan
[Xposed Framework Modules] poodleDoo:
The problem is that I have to re-{unbounce, tame, limit} them because they're no longer limited. That is what I meant by lost settings.
[Xposed Framework Modules] marbulas:
[MENTION=526666]cryptyk[/MENTION]

I can't see the wakelock 'fingerprint_scanner_static' of Google+ on your app even if it occured more than 1hr...

Could you look up this?

I'm using 2.0.4 on android 4.4.2.
[Xposed Framework Modules] cryptyk:
Oh, I see.

Did you do an in-place upgrade? Can you take a look at the file in /data/data/com.ryansteckler.nlpunbounce/shared_preferences, and see if it has all of your settings?

It certainly shouldn't lose those during a standard upgrade.

Thanks,

Ryan
[Xposed Framework Modules] HDFLucky:
No. NlpCollectorWakelock is set to 300, and the phone had been running > an hour since booting.
[Xposed Framework Modules] cryptyk:
Can you set your logging to Verbose level, then do a look at the log? Is it being blocked or allowed? Is location services turned on? Do you see it occurring in other tools, like WLD?

Thanks,

Ryan
[Xposed Framework Modules] HDFLucky:
Ahh, this may be a clue to my problem. I did an in-place upgrade (repo to repo), and upon checking that file saw that my missing settings were in there but with a value of "true" instead of the numeric value. I don't know if that suggests anything to you, but I'm going to try a complete removal and then reinstall the latest version, manually set wakelock and alarm values, and see how things are after an hour or two.
[Xposed Framework Modules] xdakewie:
I am using a OnePlus One phone (running CyanogenMod 11s) and recently I noticed something strange: If the screen had just been switched off - either manually or the inactivity period has been reached - it would not turn back on immediately. There would be around a 5-10 second delay. If the screen was off for longer, say 20 seconds, then it would turn back on the instant the power switch was pressed.

I had tried fiddling with the system settings like gestures for turning the screen on/off, disabling the smart backlight, and even changing the screen timeout period. None worked. And I was not running any screen filter or smart screen on/off apps. Finally, I uninstalled Unbounce (formerly known as nlpunbounce & succeeded by LiOn Tamer then Amplify) and this problem was gone!! I then tried several versions (1.3.2. 1.4.1, 1.5.1, and 2.0.3) and I was able to come to the following conclusion:

Versions after 1.3.2 will lead to this "screen won't turn back on immediately straight after it has turned off" problem!!

I am not a developer so I couldn't tell what changes were made in jumping to v1.4.x that caused this, but it is indeed a strange one, and it might not happen on other phone models; so I am not submitting it as a bug, but instead share with those of you who might also be using a OnePlus One phone & experiencing this anomaly. For me, I just stick to v1.3.2. ;)
[Xposed Framework Modules] xdakewie:
From my previous post:
[Xposed Framework Modules] abhi08638:
Nope wake up is fine, what did you amplify?

sent from my amazingly awesome OnePlus One

don't forget to hit thanks!
[Xposed Framework Modules] Pkt_Lnt:
Your first choice is to stay with an old, outdated, buggy version?
[Xposed Framework Modules] magnamentis:
i call it a hick-up (smile)

i try to make the answer not too long, should you wanna exchange more info we can pm. this is intermittent and happens from day one on the ONE which in my case was back in July. it happened then and it happens now ( today once ) and then it doesn't happen for many days. my theory is simply that the ONE for what ever reason is overwhelmed for a split second which honestly is not specific to this device. i encounter things like that for the last 35 years on each computer or smartphone i was using just that it does not occur on the same kind of task with each of them and the ONE perhaps has it's weekest point in the wakeup process, perhaps connected to the way how screenwake is handled. I'm talking about dt2w and the hard- as well as software configuration needed for that. and indeed it happens on my nexus 5 as well, albeit less often, which i'm using with a custom kernel and dt2w. since it's a theory it could fill books and go back and forth. just want to say that if the device uses to screen to be woken up it could be that those low power units can get more easily reaching their limits. so if it happens every time, this would be different, if it happens intermittently, the above applies and would have nothing to do with this module. this is not meant to brake loose a discussion about dt2w or whatsoever, it's meant as a second opinion to what happens to you.
[Xposed Framework Modules] poodleDoo:
The file is there, but I guess it now has the settings for what I have been added the past few minutes.

I did upgrade via Xposed download from 1.5.1.

One weird thing I just noticed; Amplify is running 2.0.3 (I did reboot after upgrade); but in Xposed Download, I can install it again... See attached image
[Xposed Framework Modules] xdakewie:
Yes. That's why I wasn't calling it an outright bug (and not submitting it as one). It could be just an incompatibility with the OPO or even an

isolated case with my unit

.

I have tried turning off dt2w and/or tap statusbar to sleep but they didn't help. For me, and I have been tackling this problem on and off since v1.4.1 (I have been using nlpunbounce since v1.1.4 and donated on 15 Sep), the only solution is to downgrade to v1.3.2. That version has never posed any problem for me, and I don't need the new Service function anyway; so I am satisfied with this workaround.

As I have explained in my original post, I am sharing this information just in case anyone has the same problem and might like to try my solution. If only a few people are experiencing it, there is no point in flooding the developer with such a minor inconvenience; or else they could submit a bug report if they so wish. ;)
[Xposed Framework Modules] sanderg:
Nothing to do

I updated to 2.0.3, 2.0.4 but all settings windows (wakelocks, alarms, services) are empty except for the headers Limited/Safe to limit/Unknown/Not safe to limit. I cannot tick them. There are no wakelocks shown.

The module is still activated in Xposed.
[Xposed Framework Modules] MIKEMON:
Thx

here new czech

View attachment unbounce-android_Czech.rar
[Xposed Framework Modules] Malwin_:
Same story here :)

Edit: Clearing cache,app data for and phone reboot helped.
[Xposed Framework Modules] MIKEMON:
restart
[Xposed Framework Modules] magnamentis:
that's normal

the way you describe it it's normal and if you, as it was explained (felt) hundreds of times, were waiting long enough until the events are starting to populate the page, then you should provide more info.

so if you waited for about 5-10 minutes and still nothing happens, that as well was explained, first go and delete the 4 files in the app data directory and if that does not help, come back and say whatever you have tried before posting, so that your issue can be distinguished from simple ignorance.
[Xposed Framework Modules] Woody:
Ok, so this is what I did. I was running 2.0 and then 2.0.2 and while 2.0 was fine for me, the 202 version just wouldn't populate any stats for me and like the above, I couldn't get anything to show up for me to even tame (and deleted the 4 files in data/data/ryan). Reading the past few days worth of posts, I saw 1ceb0x's posts about a Titanium Backup for 1.5.1 where he installed 2.0.x and then restored the data from his 151 backup. This is the path that I took, sort of.

I restored a 151, rebooted and charged up (I was already at 10% anyways). Let it charge and used my phone normally. Then I updated through the Xposed repo to 203, as I've read up to that point that it was working fine. Rebooted and lo and behold all the things that I had unbounced were there after I restored the 151 data. Decided to add in a 1 Alarm and 1 Wakelock (still checking out the services part for now) and I am now sitting at 81%, 3h45 off charge and 1h4m of screen time with a rather intense Hangout session with the Admins of the site, some G+ and some texts/calls with the Mrs.
[Xposed Framework Modules] sanderg:
Oh, it was simple ignorance. I applied the Xposed patch for that and now it's fixed.
[Xposed Framework Modules] pugsang:
2.0.4 works perfectly on my 4.2.2 and even on my androidx86 4.4 device. Services show up and no errors at the xposed log. Great work once again [MENTION=526666]cryptyk[/MENTION]. Thank you so much
[Xposed Framework Modules] magnamentis:
nobody stated otherwise

ok not to add to the heat which is for no good reason i try to explain better:

nobody says the problem does not exist, it's just that it's normal that it takes a while until the pages start to populate, so if someone says:

Quote: "i just updated and nothing is there" End Quote, i said that, without further info about how long after the update that was, is normal behaviour and only combined with a longer time span would be considered an issue and that info was missing. nothing to do with underlings, more with infer... comp....x.

further i asked, considering the possibility that what you wrote might be the case, to provide more info, but with more info i meant info upon which others can help, not info which makes false assumptions about the intention of the author.

so for me it's settled, the problems have been around quite frequently and the solutions were posted at least AS frequently. without further input (on topic of course) nobody can help without guessing.

in such cases i usually say, make a format all and clean install, and if someone is sorry for his few bucks. nothing more to say about that.
[Xposed Framework Modules] Josvaz:
Clear data and working again ^^
[Xposed Framework Modules] sanderg:
Thanks for the clarification/heads up.

As you say, some solutions have been posted multiple times. So how about updating the first page of this thread with those solutions so people don't have to go through 300+ pages of discussion? That might take less time than discuss things over and over again.

I appreciate your activity in the forum, you're much more active than I have been in the past 5 years :) and I agree that I could have given every step I tried including switching from Playstore to separate version, clearing app data through Manage Applications, reboot, wait 30 minutes, observe the same, update to 2.0.4, reboot, wait 30 minutes, observe the same, check this thread to no avail, until it appears that clearing appdata does not seem to remove /data/data/com.ryansteckler.nlpunbounce/files/* even though it does re-run the wizard and say all is fine. Which it isn't.

Well, maybe a future version might include this check so it can fix what's broken itself, without unaware users having to go into the mentioned location themselves :)

Still a lot of opportunities here.
[Xposed Framework Modules] magnamentis:
i'm with you but please consider one thing ?

i understand your point very well. albeit with this app i don't have issues, it happens with other software from time to time that things get wonky :)

but please consider that this app had very few issues ( for me none ) until google kicked him out of the playstore.

since there are so many dependencies based on the name, a semicolon, a space or whatever it might be, changing the name of an app almost never goes without this kind of glitches. theoretically it could, but i've seen no one doing it within such short time and without a large team crosschecking code. in this case we are talking about 2 such name changes withing a few days.

so for those of us who are using this app for longer ( nlpunbounce it was once ) we know how it was and will be and the fact that the dev implemented services as a feature the day the google mishap happened was probably adding to it, so new-features-bugs mixed with name-change-bugs and the stress to deal with mr and mrs big ( copyright, google, etc.)is certainly not making it easier.

so in short, let's be fair and have some more patience and i'm still not sure why this works 99.9% for some while others seem to have a lot of trouble. might be device and config specific and thus difficult to help out while coming from another end.

thanks however for bringing this back on topic and thus fruitful exchange.
[Xposed Framework Modules] b.watson:
Don't unbounce (I'm still hooked on the old name) any wakelocks or alarms that are related to widgets that update their clocks.. When analyzing these, they may seem numerous, but they don't actually keep your device awake. If you do limit their alarms/wakelocks the widget will not update the time and/or weather and the widget will keep trying to update but can't and may either cause instabilities and reboots or adverse battery use.
[Xposed Framework Modules] magnamentis:
well observed

but it depends on the widget/app

these are exactly the things which have to be observed and decided upon by each user himself depending results with his specific configuration:

for many limiting audiomix causes issues, while with player pro or any other sound i never had any if audio focus ( audio priority of an app ) can be / hast to be set to very high.

same applies for weather, clock etc widgets, while some don't update or as you say, even worse, don't give up trying, other behave perfectly well. so weather and clock widget behaves well and updates as expected but not more often than allowed in amplify, while some google services will try to acquire (location for example) until they get their way. ( can be avoided by setting location to device only while not navigating etc., best done with tasker )

so to avoid to make this too long, you're right, it can happen as you say but does not have to, so general statements can keep others to try and succeed. further if i encounter an app whith the behaviour you describe (insisten) i would try to replace it if the design is not unique and extraordinary haha... or, of course, like google servcie which many of them one does not want to miss.
[Xposed Framework Modules] HDFLucky:
Quoting myself, but given the traffic volume in this thread, it's probably the easiest way to jog [MENTION=526666]cryptyk[/MENTION] 's memory of what I'm referring to.

[IMG="Good news everyone!"]https://theloungeisback.files.wordpress.com/2013/07/professor-farnsworth.jpg[/IMG]

I don't know whether it is due to the total removal and fresh install or v2.0.4 that was released today, but everything is working perfectly now. And I think it's new as of this version that individual wakelock stats now also report time allowed/blocked AWA the raw number of wakelocks? At least I don't remember seeing it before. It's possible that my memory might be faulty though, as I reported earlier that 2.0.3 had a misplaced scrollbar on the Wakeups, Alarms, and Services page. Well it does, but apparently the issue has existed for a while, as during my troubleshooting today I reverted to a fresh install of 1.4.1, and the issue existed there as well. It's totally harmless, but just sayin…
[Xposed Framework Modules] m1trand1r:
[MENTION=526666]cryptyk[/MENTION] I don't see global status in Amplify 2.0.4.....freshly installed ...

is it just me?
[Xposed Framework Modules] m0han:
go to settings and check "participate in global stats" or something similar.
[Xposed Framework Modules] CatsAreGods:
Just another thank you for this great program. I was losing 2% power per hour overnight with stock kernel, cut that down by half with Hell's Doctor, but this obliterated all of that:

So I started out losing 15% a night, but now it's down to 1 or 2%!
[Xposed Framework Modules] Cyclu:
[MENTION=526666]cryptyk[/MENTION] Updated from 1.5.1 to 2.0.4 I have found these errors in Xposed log:

java.lang.NullPointerException

at com.ryansteckler.nlpunbounce.models.UnbounceStatsCollection.resetLocalStats(UnbounceStatsCollection.java:595)

at com.ryansteckler.nlpunbounce.hooks.Wakelocks.resetFilesIfNeeded(Wakelocks.java:96)

at com.ryansteckler.nlpunbounce.hooks.Wakelocks.handleLoadPackage(Wakelocks.java:77)

at de.robv.android.xposed.IXposedHookLoadPackage$Wrapper.handleLoadPackage(IXposedHookLoadPackage.java:20)

at de.robv.android.xposed.callbacks.XC_LoadPackage.call(XC_LoadPackage.java:34)

at de.robv.android.xposed.callbacks.XCallback.callAll(XCallback.java:70)

at de.robv.android.xposed.XposedBridge$2.beforeHookedMethod(XposedBridge.java:228)

at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:611)

at com.android.server.ServerThread.initAndLoop(Native Method)

at com.android.server.SystemServer.main(SystemServer.java)

at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)

at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)

at com.android.server.SystemServer.main(Native Method)

at java.lang.reflect.Method.invokeNative(Native Method)

at java.lang.reflect.Method.invoke(Method.java)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)

at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)

at dalvik.system.NativeStart.main(Native Method)
[Xposed Framework Modules] kurtextrem:
Same here. Deleting the 4 files from /data/data/com.(i forgot the name)/files fixes it :)
[Xposed Framework Modules] Cyclu:
Thanks bro problem fixed. Still the issue with automatic stats refresh I have to do manually.
[Xposed Framework Modules] Black_Stark:
Is this app compatible with ICS 4.0.4 version.??

In playstore it shows 4.1 and above.
[Xposed Framework Modules] Cyclu:
[MENTION=526666]cryptyk[/MENTION] Force close when I have tapped an entry in Services I :

11-01 11:36:13.749 W/dalvikvm(30052): threadid=1: thread exiting with uncaught exception (group=0x416846f8)

11-01 11:36:13.759 E/ActivityManager(1291): App crashed! Process: com.ryansteckler.nlpunbounce

11-01 11:36:13.759 E/AndroidRuntime(30052): FATAL EXCEPTION: main

11-01 11:36:13.759 E/AndroidRuntime(30052): Process: com.ryansteckler.nlpunbounce, PID: 30052

11-01 11:36:13.759 E/AndroidRuntime(30052): java.lang.NullPointerException

11-01 11:36:13.759 E/AndroidRuntime(30052): at com.ryansteckler.nlpunbounce.ServicesFragment.switchToDetail(ServicesFragment.java:189)

11-01 11:36:13.759 E/AndroidRuntime(30052): at com.ryansteckler.nlpunbounce.ServicesFragment.onListItemClick(ServicesFragment.java:135)

11-01 11:36:13.759 E/AndroidRuntime(30052): at android.app.ListFragment$2.onItemClick(ListFragment.java)

11-01 11:36:13.759 E/AndroidRuntime(30052): at android.widget.AdapterView.performItemClick(AdapterView.java)

11-01 11:36:13.759 E/AndroidRuntime(30052): at android.widget.AbsListView.performItemClick(AbsListView.java)

11-01 11:36:13.759 E/AndroidRuntime(30052): at android.widget.ListView.performItemClick(ListView.java)

11-01 11:36:13.759 E/AndroidRuntime(30052): at android.widget.AbsListView$PerformClick.run(AbsListView.java)

11-01 11:36:13.759 E/AndroidRuntime(30052): at android.widget.AbsListView$3.run(AbsListView.java)

11-01 11:36:13.759 E/AndroidRuntime(30052): at android.os.Handler.handleCallback(Handler.java)

11-01 11:36:13.759 E/AndroidRuntime(30052): at android.os.Handler.dispatchMessage(Handler.java)

11-01 11:36:13.759 E/AndroidRuntime(30052): at android.os.Looper.loop(Looper.java)

11-01 11:36:13.759 E/AndroidRuntime(30052): at android.app.ActivityThread.main(ActivityThread.java)

11-01 11:36:13.759 E/AndroidRuntime(30052): at java.lang.reflect.Method.invokeNative(Native Method)

11-01 11:36:13.759 E/AndroidRuntime(30052): at java.lang.reflect.Method.invoke(Method.java)

11-01 11:36:13.759 E/AndroidRuntime(30052): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)

11-01 11:36:13.759 E/AndroidRuntime(30052): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)

11-01 11:36:13.759 E/AndroidRuntime(30052): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)

11-01 11:36:13.759 E/AndroidRuntime(30052): at dalvik.system.NativeStart.main(Native Method)

11-01 11:36:13.759 W/ActivityManager(1291): Force finishing activity com.ryansteckler.nlpunbounce/.Settings-Alias

Thanks Ryan for adding the package name in description for Alarms and Services.
[Xposed Framework Modules] SignetSphere:
Well then the playstore already answered you ICS is 4.0.4 so it's not compatible.
[Xposed Framework Modules] ztoldy:
Hi,

I would like to make a hungarian translation. Please add hungarian language to the projekt. Thank you!
[Xposed Framework Modules] codeknight11:
For the time being don't limit anything for which the app says ''We don't have information about this event''.

I have limited very few events in each category. Over time as this app evolves and by collecting feedback from users, the developer can then confidently tell us what we should limit and what we shouldn't.
[Xposed Framework Modules] m1trand1r:
This is what i've limited/blocked:

That being said and posted ...I haven't encountered any issues or apps closing or anything simmilar on my side....note that i'm running Android 4.4.4 from sig as written :)

And yes....some of blocked/unbounced wakelocks/alarms and services don't have description ....but on the other hand....if one does block/unbounce wakelocks w/o description it may help to future development of this awesome app.... but i'd prefer to fetch logs after certain issue arisen...just like in your case.....that could help to resolve what to block and what not.....

My 0.02€ :)