yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] _mysiak_:
Installed the latest version and it's constantly rebooting (every 15-30 minutes) even if phone isn't used at all (just a standby). Also almost all wakelocks disappeared from the list and nothing is "unbounced". Previous version works without these issues.

Xperia SP, stock 4.1.2
[Xposed Framework Modules] cuttingeugen:
I've got the exact same Problem!
[Xposed Framework Modules] DSC05:
Yep, me too.
[Xposed Framework Modules] xdakewie:
thankfully i am not experiencing the reboot problem, but the stats aren't being refreshed like they did with the previous versions, and i am striped of my donator status despite updating through the Play Store & having waited for 24 hours!
[Xposed Framework Modules] Dan Steely:
My stats aren't refreshed automatically either.

Verstuurd vanaf mijn GT-I9300 met Tapatalk
[Xposed Framework Modules] cbomb101:
Hey my phones been rebooting alot to. I thought it was the kernal. Maybe its my app i double checked settings on kernal it all fine.
[Xposed Framework Modules] Pkt_Lnt:
Logs? Xposed log? Lion debug log? Logcat? Come on guys, nothing can be solved or fixed without logs. Thanks
[Xposed Framework Modules] tesslerc:
Just wanted to hop in and give a personal thank you.

This app is amazing, thank you for your amazing work :)
[Xposed Framework Modules] RobLudo:
Sorry, I missed this thread for a while, why did the name changed? This has broken all tasker rules :(
[Xposed Framework Modules] Bleedos:
Here is cryptyk's post about it:

http://xdaforums.com/showthread.php?p=56215165

There's a lot going on right now. I'm sure that Tasker's issue will be resolved when the name change thing will be over.
[Xposed Framework Modules] trancinguy:
I have been experiencing random reboots. There is a small bug where when pressing the stats refresh, it goes back to zero and then press it again it shows current allowed and blocked.

Lion Tame at default because my system N5444 elementalx freezes the UI when I I set it at 420 or tame some other thing.
[Xposed Framework Modules] 1ceb0x:
I used lux for many months and i know about that alarm triggering a lot of time.. Solution? Disable the compatibility check service from lux and everything will be back to normal (either through this module or any other app that can disable services) - i always do that and i had no problems.

As for why this alarm is picked out of a sudden - it is not a bug. [MENTION=526666]cryptyk[/MENTION] reworked the way how unbounce was picking up alarms and wakelocks so that the app will show everything (remember there were some alarms/wakelocks not showing in the app?).
[Xposed Framework Modules] tboooe:
Thank you. How did you disable the service?
[Xposed Framework Modules] 1ceb0x:
you can do so with the latest version of lion tamer 1.5.1. personally i moved from 3c tool box to MyAndroidTools to take care of my services/providers/receivers :).
[Xposed Framework Modules] tboooe:
Maybe I missed it but I don't see that service listed in Lion Tamer. I only see the alarm.
[Xposed Framework Modules] 1ceb0x:
Install MyAndroidTools and disable that service from Lux ;) or any other app that can do that.
[Xposed Framework Modules] tboooe:
Thank you. I know I can that but I'm wondering why the service is not listed in Lion Tamer?
[Xposed Framework Modules] Mistertac:
Jeeeez!! Thank you I've completely forgot Lux had that option lol
[Xposed Framework Modules] tboooe:
Did you find that Lux service in Lion Tamer? I could only find it in Alarms.
[Xposed Framework Modules] 1ceb0x:
Services part of this module is still wip for now, mate!
[Xposed Framework Modules] Mistertac:
I used MyAndroidTools as well. Found it no problem.
[Xposed Framework Modules] tboooe:
Did you use the free or Premium version? Whats the difference? I couldnt tell by reading the descriptions on Play Store.
[Xposed Framework Modules] mikkelrev69:
Just want to report that latest 1.5.1 is ****ed up. Behaves more or less like early alpha. Doesn't show any services. Sometimes doesn't unbounce locks. Totally unstable. Don't have logs. Had to roll back to 1.4.1.

Note 3, 4.4.2 XXUGNG1

Sent fra min SM-N9005 via Tapatalk
[Xposed Framework Modules] HDFLucky:
Too early to tell if it's providing any benefit, but I used the new Services feature to disable this. Since I do not (and likely will not) have any wearable devices, it's an obvious candidate.

There are different versions of Google Play services, and one of them (not the one I have installed in my Nexus 5) has a fitness interface that can be toggled on/off. It may be possible to accomplish the same thing there. You can check for this feature in the Google Settings app (gray gear icon). I had actually received an auto-update to that version, which caused the new Hangouts to always popup an "Unknown Google Play services" error. A day or two later, I received another auto-update that fixed it.

http://androidcommunity.com/google-...-preview-play-store-redesign-leaked-20140917/
[Xposed Framework Modules] Mistertac:
I got the premium one myself, not sure if it's needed for that or not.

Soon enough this will me integrated into this module here which will be cool <---- trying to stay on topic lol
[Xposed Framework Modules] Adywizard:
Hi guys. This is the list of the Google services that you can safely disable.

AdRequestBrokerService

AnalyticsIntentService

AnalyticsService

FusedLocationService

FusedProviderService

GeocoreService

GeofendeProviderService

GoogleLocationManagerService

NlpLocationReceiverService

SystemUpdateService

WatchdogService

WearableControlService

WearableService

I found this list in another thread.

Sent from my personal space station with the power of the minde!
[Xposed Framework Modules] 1ceb0x:
sorry, don't want to spoil your party, this is already covered by my post that is in my signature. you also need to disable its receivers and providers to disable it completely. everything is in my post :). cheers!
[Xposed Framework Modules] xordos:
Definitely, each major android release may change these methods that this module trys to hook, so it throw methodnotfound error.

Have you tried my build for 4.1.2? Or maybe you can see if you can upgrade to 4.4.
[Xposed Framework Modules] deejayburnout:
Been using this for a few days now and it's simply awesome. Kept it at the default setting and my battery life had got a lot better.

So simple to use. Very happy with it.

Thanks
[Xposed Framework Modules] Shisma:
After 2 hours I have 340 NlpCollectorWakelock and 96 NlpWakeLock (900 seconds).
[Xposed Framework Modules] harpreet.s:
Thanks, your 4.1.2 build worked. Now I can see the actual difference made by this module. All other builds are not working on 4.3 so we can assume the original module actually works only for kitkat.
[Xposed Framework Modules] Jayy_Suave:
You changed your settings to 900?
[Xposed Framework Modules] Shisma:
Yes, don't need how much time to go home or work [emoji16]
[Xposed Framework Modules] Jayy_Suave:
Cool. I changed all options to 900.
[Xposed Framework Modules] dimm0k:
How did you get BBS to display the alarms per hour? Nevermind, figured it out... change the display to Alarms instead of Partial Wakelocks...
[Xposed Framework Modules] mwrobe1:
I should have looked at my BBS alarm stats before posting my last reply. It appears...if I am understanding the functionality of this module...my previous post may be in error. It seems that I should have read and comprehended the OP before stating that I thought there were still issues.

From the OP:

1) If Google Location Services are turned on, it sets an alarm to wakeup every 60 seconds, check the network location, and broadcast ALARM_WAKEUP_LOCATOR.

2) Everytime ALARM_WAKEUP_LOCATOR fires, Google Search receives the broadcast and grabs an NlpWakeLock and NlpCollectorWakeLock.

3) Those wakelocks hold the keep the device on for 5-15 seconds. This means that the device is actually awake for about 15 seconds per minute, or 25% of the time!

The above points do not state that it will limit the COUNT of occurrences of NlpWakeLock and NlpCollectorWakeLock to 1 per 240 seconds...only that the alarm that TRIGGERS those processes will fire off every 240 seconds. Depending on the device and apps installed...the actual wakelock count is probably going to be variable....not a constant 1 to 240 sec ratio...so looking at the partial wakelock stats in BBS is close to meaningless vs. the alarm count.
[Xposed Framework Modules] pugsang:
[MENTION=3266877]xordos[/MENTION]

Why am I receveing message app not installed with 4.1.2 build on 4.2.2?
[Xposed Framework Modules] xordos:
I have seen a few reported that they have more wakelocks than expected, and this also happened in my phone. (but since I am on 4.1.2 build which is not equivalent as OP 4.4 build, so I won't say too much about it).

But I do have a guess/theory, there maybe some other path/way to trigger this wakelock? This module currently is hooked on class "com.android.server.power.PowerManagerService" method "acquireWakeLockInternal" only. So, if other app/services is trigger this wakelock, then they won't be captured.

Sorry, really don't know too much about android, this is probably completed wrong. Just my 2cents.
[Xposed Framework Modules] wilkster:
I think what you really want to look at is the total time the wakelocks are held. That is what really impacts the battery life.

Sent from my VS980 4G
[Xposed Framework Modules] dimm0k:
[MENTION=4195288]wilkster[/MENTION] how do you determine how long wakelocks are held? BBS is telling me NlpCollectorWakeLock for Google Play services is

32s (32 s) Count: 611 0.5% under Partial Wakelocks and
Wakeups: 179 (1.8/min) for com.google.android.gms under Alarms.

I have NlpUnbounce set to 240 for all 4 options, rebooted and that's what's showing. Am I dead in the water??
[Xposed Framework Modules] wilkster:
The alarm count seems high but the total wakelock time doesn't seem that bad. Post all of your partial wakeup data (or at least the top 5-6) along with the details of the gms alarms. May be easier to decode. Also, does you xposed log look ok? Are you getting the NLPUnbounce messages with no errors?
[Xposed Framework Modules] xordos:
Hi, can you give more info, like in which screen it show that, and you can attach the screen shot, or if this from log, then can you attach the log
[Xposed Framework Modules] khairulez:
[MENTION=3266877]xordos[/MENTION]

Thanks for 4.1.2 build.Works fine on my 4.2.2.

Tap via Tapatalk
[Xposed Framework Modules] dimm0k:
[MENTION=4195288]wilkster[/MENTION] hope an hour each is enough to gauge what might be the issue here... first two pics are with this module disabled for about an hour. the remaining three pics are after a reboot with the module enabled with the defaults of 240 for all four options. the last image shows my Xposed log.
[Xposed Framework Modules] dimm0k:
[MENTION=526666]cryptyk[/MENTION] [MENTION=3266877]xordos[/MENTION] a slight bug with this module is that when opening up the settings it shows the current value for LOCATOR and DETECTION, but not for the other two - NlpWakeLocks and NlpCollectorWakeLocks. If you actually change the latter two settings, it then does show their current values. However after a reboot, they no longer show again.
[Xposed Framework Modules] b.watson:
Thank you xordos for your 4.1.2 build. I can confirm that this works perfectly on 4.2.2. Great work. And thank you cryptyk, this has made a huge difference to my battery life, without losing any functionality.

Link to the Jellybean build
[Xposed Framework Modules] wilkster:
Even though the total number of alarms when up on the NLPUnbounce case, the total wakelock time went down. So it shows it should be working. Note however, you should probably use the version from post 237 from Xordos since it does fix a minor bug with one of the alarms and improves the logging to xposed. To get a better idea I would run the updated version from post 237 (after a reboot) using the default settings. Run it for longer than an hour however, such that you can get a feel from your experience with your phone if it is working. You can also export the BBS data to a text file (using the share icon at the top) to get a very detailed look at wakelock and alarms on your phone after you have run it for while. Having this BBS detailed data for both cases could help you in determining why the alarms are higher for the enabled case.
[Xposed Framework Modules] tboooe:
I just checked by gray gear and didnt see a setting for Fitness. Also I checked Services in Lion Tamer and could find a few entries at the bottom related to wearable:

com.google.android.gms/.wearable.service.WearableControlService

com.google.android.gms/.wearable.service.WearableService
[Xposed Framework Modules] jarno_jarno:
Using this great tool with much benefits a couple of weeks now! New name is also interesting, maybe even better. Due to this my battery is only dropping 0.5% per hour now [HTC One M7 - MaximusHD 44 rom - Kangeroo kernel). Wifi is mostly 85% of this percentage when idling :angel:

Anyway, I read disturbing posts [rebooting/crashes] here about the new version with support for services. Should such versions not be labeled 'beta' or even 'experimental' in the Xposed repository for some time? Maybe something to think about for upcoming versions?

Have to say, much respect for cryptyk's going around with people and support :good:
[Xposed Framework Modules] root/dev/null:
Thanks for the tip about MyAndroidTools!I've been using 3C Toolbox but the fonts in MyAndroidTools are much easier to read.
[Xposed Framework Modules] MIKEMON:
yep, but something is wrong?

After rebooting again waiting for the lock and nothing

try to delete the application data and start again
[Xposed Framework Modules] jcvr:
X2
[Xposed Framework Modules] cryptyk:
The new version should have been marked experimental. I had a lot of stuff in there that wasn't quite finished, like service blocking, and some bug fixes around the way stats are reported from the Xposed process over to the Activity process.

When the name change thing came up, I needed to get the name change out to every distribution point (including the name of this thread, Play Store, Xposed Repo, as quickly as possible so we can move forward.

That resulted in a bunch of things that weren't quite ready getting pushed out in a hurry. Any delay in getting the latest version out to people was going to be even more painful than the current thrash. I know people are having problems. I know service blocking doesn't work well. I know there is some unstable code. I know the name isn't awesome. I had to make a call quickly, and think the best thing to do is destabalize the app for a few days, get things worked out with the pleasant folks over at Unbounce.com, then pick up the pieces and move forward.

We'll get there soon. Everything will become stable again. Services will be an awesome new feature. The real new name will be better. It just takes time. Believe me, I feel the pain as much as you :)

Here's my best guess at a timeline:

1) Unbounce.com has already contacted Google to let them know the app no longer infringes on their trademark. They've been very quick to respond, and very fair.

2) I'm waiting on Google to re-list the app in the USA. This will probably happen Tuesday or Wednesday, but I'm not 100% sure.

3) I'm working on a new build with the new name, and some fixes for the stabilization problems. Any logs of crashes, reboots, etc are *very, very, very* helpful. My devices aren't rebooting. I know these are real problems, and I'll get them fixed.

4) As soon as the app is re-listed in the USA, I'll push the newly named, stable version to all distribution points. There will probably be a period where I need to take care of some housekeeping things, like changing screenshots in the Play store across 16 languages, responding to negative reviews in the Play store because of the trash, and helping people over email who aren't on this forum and don't know why all this is happening.

I know that feels like a long time, but I honestly only have maybe an hour every day to work on this stuff. It just takes time :)

Thanks,

Ryan
[Xposed Framework Modules] HDFLucky:
Didn't realize I was having a party, but it's a moot point, because I've had to roll back to v1.4.1. 1.5.1 was causing spontaneous reboots and inability to wake phone up. Among other problems, I would see no stats when first opening the module, but after selecting one of the other screens and then going back to Home, the stats would be populated. If I went direct from Wakelocks, Alarms, or Services to one of the other choices, I'd get two 'sort' icons in the upper right (neither of which did anything). If I went 'Home' in between selections, the screen presentation and data seemed normal.

Sorry [MENTION=526666]cryptyk[/MENTION] that I can't be more helpful, but there is nothing noteworthy in the logs and I can't take a chance of these issues rendering my phone unusable (no removable battery).

(Nexus 5, 4.4.4, elementalX kernel)
[Xposed Framework Modules] 1ceb0x:
Uhmmm did you quoted the wrong person or it was intended for me?
[Xposed Framework Modules] MIKEMON:
I'm sorry ...

Czech language updated

everything is fine with me
[Xposed Framework Modules] cryptyk:
For those on 1.5.1 and who don't see any wakelocks, alarms, or services listed, please try deleting the 4 files in:

/data/data/com.ryansteckler.nlpunbounce/files

That should solve most problems until I can get the new version published.

Thanks

Ryan
[Xposed Framework Modules] root/dev/null:
That solved it for me.Thank You
[Xposed Framework Modules] MIKEMON:
delete the entire component? or only selected files?

I have a cache, files, lib, shared_prefs ??

thanks
[Xposed Framework Modules] root/dev/null:
1329

Just the 4 files in the files folder.
[Xposed Framework Modules] jackulus:
I have impression that you limit the Lux functionality having this service disabled. I make my first steps with this (lux) application but it seems to me, that when you stop the compatibility check service you can't effectively use the auto "after wake up" mode. Brightness doesn't change automatically when I turn on the screen in quite different light conditions. Doesn't matter when you don't use it.
[Xposed Framework Modules] MIKEMON:
I've got multiple folders?

that exactly?

thanks
[Xposed Framework Modules] cryptyk:
You only have four files in the /data/data/com.ryansteckler.nlpunbounce/files directory. Delete all 4.
[Xposed Framework Modules] root/dev/null:
/data/data/com.ryansteckler.nlpunbounce/files/gaClientid,nlpunbounce.global.stats,nlpunbounce.push.stats,nlpbounce.stats

At least those are the 4 I have.
[Xposed Framework Modules] MIKEMON:
Thanks, now everything is loading ...

Perfect
[Xposed Framework Modules] Gizmundo:
Hi.. I purchased the donation version and roll back to earlier version because the new one keep restarting. Now I've lost pro version. Please help because I can't wait to test it.thanx
[Xposed Framework Modules] touch of jobo:
bug

Found a minor cosmetic GUI bug:

Page title is incorrect after coming back from Settings.

When you choose Home, Wakelocks, Alarms or Services from the menu, you go to that page and the title says which page you're on.

When you

go to Settings and then back

, you're back on the page you came from, but

now the title says 'Lion Tamer' instead

.

(Expected behavior is that the page title would be the same it was before going to settings.)

If you then go to another page and back, the page title is correct again. Going back further, page titles are also correct.

Xposed 2.5.1; Lion Tamer 1.5.1 from repo, Pro options enabled.

-Jobo
[Xposed Framework Modules] camry89:
Awesome post, noticed one problem with my S4 (M919 & GPE) though, when disabling the following services:

checkin.CheckinService

checkin.EventLogService

update.SystemUpdateService

there's an infinite wakelock that prevents deep sleep altogether, bbs shows those 3 locks, as soon as I enabled them the locks are gone.

Also, was unable to uncheck most of the services under "Receivers", 3c toolbox gives error and automatically reenables.

Used unbounce for the Event Log Service and set that ***** to 9999, same for Checkin Service, Event Log Handoff, and SystemUpdateService..... F*ck you google
[Xposed Framework Modules] Wi1son:
Yea, same issue here with 3c. I switched to System Tuner (the blue one) and it works every time.

SCH-I545 on HyperDrive 19
[Xposed Framework Modules] sino8r:
Same thing here... Phone has frozen a zillion times and/or won't wake. I'll roll back until new version comes. Thanks so much for confirming it was this app and not another. Was beginning to think it was the Greenify beta. Love this app! Has worked well before always so no biggie... Love the new name as well!
[Xposed Framework Modules] root/dev/null:
System Tuner is also made by 3C,it's just 1 module from the Toolbox.
[Xposed Framework Modules] 1ceb0x:
I should edit my post then. i never had problems with 3c tool box but almost everyone here said they had. i then moved to MyAndroidTools app (from the developer of Disable services app) due to its slim memory foot print and everything is great. Regarding your massive wakelock, it was caused due to the fact that 3c was unable do disable the receivers and/or the providers thus you had the wakelocks.

As a rule, once you disable these, you don't need to unbounce them anymore since they

will never appear.
[Xposed Framework Modules] grisu59964:
I'm happy to see that I'm not the only person with reboots.

The German translation is already updated to the new name and wording, so I'm looking forward for the next update :victory:
[Xposed Framework Modules] cbomb101:
I froze mine yesterday. Everything seems good for now.

---------- Post added at 01:03 PM ---------- Previous post was at 01:00 PM ----------

3c (cedric) is ment to be fixing the event, receivers, boot complete issues with next update. Hopefully it is fixed.
[Xposed Framework Modules] euqiddis:
Would be a good idea to have functionality of backup/restore of all the wakelocks/alarms/services.

Great app btw!
[Xposed Framework Modules] ivan_iraci:
Same here. My phone reboots every 15 minutes or so, with 1.5.1.

With 1.4.1 all was working wonderfully.
[Xposed Framework Modules] 1ceb0x:
logcat or it didn't happen... i have no problems with 1.5.1
[Xposed Framework Modules] ivan_iraci:
I really don't have the time to mess with my phone.

For me it's ok to stay with 1.4.1, as long as it works well.

Thanks anyway.
[Xposed Framework Modules] kingbeta:
I managed to fix my donation issues. Using titanium backup, I detached unbounce 1.5.1 from market, then forced re-attach. The donation showed up immediately. Note I had updated in the play store, not via xposed.
[Xposed Framework Modules] blumenkasten:
Same here
[Xposed Framework Modules] VanillaDeath:
Unfortunately with the newest version (1.5.1), the app always shows 0 for all stats and soft reboots my phone a few minutes after I open it up.
[Xposed Framework Modules] cryptyk:
Can you try resetting your stats?
[Xposed Framework Modules] gd6noob:
Is this similar to App Ops? I can turn off "Keep Awake" in App Ops, is this the same as the wakelocks??

Sorry for the noob questions...