yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] cryptyk:
I talked about this aa few pages ago:http://xdaforums.com/showpost.php?p=55802023&postcount=1730

In an upcoming version, I'm reducing the overhead of Unbounce so it can help get people to even lower drain percentages. They other thing to realize is that very few people have the excessive drain problem. Thousands and thousands of people use Unbounce and are gettigetting down to very low drain numbers. It's hard to develop modules for xposed because everyone has rooted devices, custom roms, custom kernels, and other xposed modules. If things aren't working properly and its working for most other people, the problem is likely some unique interaction on your device. It's really hard to track every one of those down.

but like i said, I'm trying and the next version should help.

Thanks,

Ryan
[Xposed Framework Modules] tboooe:
Just curious for everyone having more battery drain with this app what Android version are you running and how many wakelocks and alarms are you unbouncing?

For me, I have found that only a handlful of things drain my battery even if the wake time or alarms are high. So aside from the default unbounced items I so far have only added the following:

Icing (wakelock)

SyncLoopWakelock (wakelock)

SyncAlarm (alarm).

I get anywhere from 0.1-0.5% battery drain at idle with everything turned on (sync, wifi, gmail, etc).
[Xposed Framework Modules] yanleites:
Nexus 4, stock 4.4.4, unbounced everything "unbouncable".. It shows me alert 6 hrs, blocked 3hrs.

But without it battery is better...
[Xposed Framework Modules] tboooe:
What if you set Unbounce back to default settings? If I read your post correctly it seems you have a lot of things set to unbounce? Maybe thats the issue. Like I said, I dont think the point of this module is to unbounce everything but rather the handful that has real impact on your battery. I can see how unbouncing a lot of things can cause excessive battery drain.
[Xposed Framework Modules] yanleites:
Default settings blocks only 2 wakelocks, and only when GPS is on, I turn the GPS only when I need it, maybe once a week, so for blocking 2 wakelocks once a week I don't need this app.

Do you agree?
[Xposed Framework Modules] tboooe:
I disagree because like I said, only a few things really drains your battery. For me, its maybe 4-5 things. Unbouncing everything wont really help. Thats why you need to use BBS or GSAM or Wakelockdetector to see which things are really draining your battery.
[Xposed Framework Modules] Mistertac:
If that's how you use Location on your phone then no you don't have to worry about it, although this module helps greatly with Alarms and WakeLocks from various user apps like WhatsApp Facebook, Twitter and of course... Google Play Services.

I'd venture to say your phone has a couple of those running no?

- Tapatalked From The G3 -
[Xposed Framework Modules] yanleites:
Whatsapp, Skype, tango... But I use greenify. It works great.
[Xposed Framework Modules] mrQQ:
cryptyk, do you have any idea about these? i'd donate just for those.

Otherwise, I think my battery is worse with Unbounce than without it aswell, though I will keep an eye on it.
[Xposed Framework Modules] shinra00:
Hey so i have been following this thread since Ryan went away for holidays and the thread exploded!! Being away just for 2 days from this thread may lead to 10 unread pages :p but still i´ve read everything.

I have to be honest i´m not one expert user and i´m asking for some guidance. I do have the donation version running with only the default settings. I do have BBS and now i would like to understand how should i compare the stats from Unbounce app with the BBS to know which wakelocks and alarms i should unbounce in order to actually profit/save battery from the app

As i understood the best way is to charge the phone before going to bed, and reset the Unbounce count, since BBS already does this (unplugged feature)

Then i should compare the wakelock count from unbouce with the BBS "partial wakelocks" count? The thing is some high number counts from bbs, for example Icing have 4s (4s) count 322 0.1%. This means it had 322 hits that woke up the phone for 4s and spent 0.1% of the battery up to this point, am i right?

Should i only go for the BBS data or does the unbounce also provide important date? i ask this because unbounce does not have the amount of battery drained therefore a wakelock can have a really high amount of hits but still almost none drainage associated, please tell me if in thinking well.

and for last, should i be "worried" if a partial wakelock has a high number of hits? a high amount of time awake or just focus with the battery drainage?

So sorry for this huge thread but i would really like to understand how i can benefit from this module that almost everyone loves, and that i keep reading every thread even when most of the time i dont understand what i´m reading.

Thank you!
[Xposed Framework Modules] cryptyk:
Are those showing up in BBS and not showing up in Unbounce?
[Xposed Framework Modules] cryptyk:
I think we're all still trying to figure out the "best" way to approach this. My personal perspective at the moment is to look at BBS, and Unbounce to look for the alarms that fire most often. If those seem like things you should limit, I would start by limiting those. Basically, start with the alarms.

Then run for a day or two and check BBS, WLD, and Unbounce for wakelocks that are keeping the device awake for a long time. Duration is more important than count. If those are things you can unbounce, go for it.

Then, realize that once you're around 1-2% drain per hour, it's going to be really, really hard to get below that by unbouncing more items. There's just a point of diminishing returns.

Thanks,

Ryan
[Xposed Framework Modules] mrQQ:
Yes. But also Wakelock Detector shows many alarms coming from Exchange Services, and I can't find anything like that in Unbounce.
[Xposed Framework Modules] tboooe:
Yes for me as well. There are alarms from GoLauncherEx for example showing up in BBS but not in Unbounce.
[Xposed Framework Modules] Mistertac:
Well your logic is fairly good although to start what I would do is grab WakeLock Detector and use that.

For example my Screen shot here shows very minimal times for GPS but some do have a high count of WakeLocks. However the total time those WakeLocks actually woke the phone are only in Seconds.

The ConfigFetchService one was actually very high right after the recent GPS update, it was something like... 5-10 minutes during my daily use, so I then UnBounced it to something like 900 I believe and now it's back to being only Seconds.

WakeLock Detector is nice because you can see what is Waking your phone : Google Play Services, Android System, Facebook etc etc and then you can expand those to see the actual name of the WakeLock you'd be alerting using this UnBounce Module.

You can gain a lot of information from WLD and Better Battery Stats is obviously great to. I use that one for getting a big picture into what's going on in a very easy to understand way.

- Tapatalked From The G3 -
[Xposed Framework Modules] tboooe:
Personally, I use a combination of GSAM and BBS. I like GSAM because it quickly shows you the % of battery drain that each type of Wakelock does. I can drill down into each to see specifically what the wakelock is. I like BBS to figure out what alarms are waking up my device most. But keep in mind, just because the wakelock or alarm is high in number it doesnt mean its draining your battery alot.
[Xposed Framework Modules] shinra00:
Thank you very very much for the responses tboooe, Mistertac and cryptyk! Now i should be able to start digging my phone to find the what is keep it awake. Thank you :good:
[Xposed Framework Modules] Mistertac:
Just keep in mind to that you don't have to UnBounce everything that's in our Spread Sheet either, it's better to just UnBounce whatever is effecting your phone.

- Tapatalked From The G3 -
[Xposed Framework Modules] tboooe:
+1000!
[Xposed Framework Modules] RASTAVIPER:
Exactly same setup and device, in post 1717 I am mentioning my drainage during idle, although I don't know the reason for that.

How did you discover that Unbounce cause the drain ?
[Xposed Framework Modules] yanleites:
Used it for about a week, and saw that without it battery is better...
[Xposed Framework Modules] Mistertac:
Im not doubting you guys who say this module negatively effects your Battery, im just curious of some stats to compare using it and not using it and what are we talking here??? Like a couple % difference or just terrible terrible Battery life?

As said before, of course any app / module you run will require resources and Ryan already said he's looking into improving that aspect but I'm just wondering what kind of numbers we're talking here...

- Tapatalked From The G3 -
[Xposed Framework Modules] MIKEMON:
Well, that's about it

each has a different phone and other applications

therefore also differ from each other

use logcat
[Xposed Framework Modules] rignfool:
Stop unbouncing so much...

Think about this...

The wake lock runs... It holds your device for the prescribed time... Then its done...

You unbounce... The system tries and fails... So... Due to bad coding or some other unforseen issue it tries again...

Or... Instead of just the quick wake lock... It has to run unbounce as well...

Everything you do... Whether user interaction or not... Takes battery...

It's the old juice defender argument... You save battery by... Wasting battery?

You'll notice the people that aren't complaining all have only a couple things unbounced... And those that are... Have everything unbounced... Coincidence?
[Xposed Framework Modules] Mistertac:
I've gotten nothing but Better Battery life from using this module.

I've UnBounced Location based WakeLocks and Alarms, Sync , and Google Play Services.

Perhaps too the people who are having worse Battery should lower the Time they have put into whatever they UnBounced and run it for a few days to see if that helps

- Tapatalked From The G3 -
[Xposed Framework Modules] yanleites:
So your great idea is not to unbounce ?

Just leave the 2 default wakelocks and thats it ?

---------- Post added at 10:21 PM ---------- Previous post was at 10:19 PM ----------

Can you please show screen shots of what you unbounced and times of it, it's interesting to try ....
[Xposed Framework Modules] rignfool:
I make no suggestion...

I say... You need to figure out what is best for your device based on your installed apps and usage...

For me... The 2 wakelocks and the 2 alarms is plenty... We are talking about a huge difference for me... From about 8% idle drain to 4% or less depending...

The big thing for me... Is I lose no features... And I'm letting android deal with itself... Just curbing googles data mining...
[Xposed Framework Modules] yanleites:
Which wakelocks and alarms you unbounced ?
[Xposed Framework Modules] yanleites:
Thanks, in will try...
[Xposed Framework Modules] Mistertac:
Here's what I've done FWIW

I've had many more for testing purposes but these ones are the ones that truly benefit me.

As for the times... Just start low at 240 and run it for a few days and see what happens. Obviously if you're seeing an Alarm or WakeLock that isn't actually being effected by UnBounce then slowly raise the time up.

I've also stated from scratch a few times and I've uninstalled UnBounce and wiped cache/Dalvic between Ryan's updates of this great app.

Not saying that's something you must do but I've found its helped me.

- Tapatalked From The G3 -
[Xposed Framework Modules] yanleites:
OK. Thanks.

I did the same as you, and had a drain...
[Xposed Framework Modules] Mistertac:
I get pretty much no drain. Over night idle my phone won't even lose barely 1% over the 8+ hours.

Not sure what else to tell ya

- Tapatalked From The G3 -
[Xposed Framework Modules] RASTAVIPER:
I uninstalled for tonight Unbounce to check if my Nexus 4 will have any difference in standby.

Then we will see if yanleites is confirmed.

Unleashed from Onda v957m
[Xposed Framework Modules] tboooe:
Damn thats good! I thought I was doing good with 0.1-0.4% drain per hour. I have to ask, does this include having 4G, wifi, Sync, etc all on?
[Xposed Framework Modules] betold:
Holy cow this is awesome!

Same daily usage on my Nexus 5 and I have about 15-20% more battery at the evening. Yesterday I had solid 4h screen on until the device dropped to 5%. I did not change a thing. 240 is just fine. Everything is working. Google now etc. I will try 300 sec just for fun.

I can't thank you enough, this is an excellent mod.
[Xposed Framework Modules] FredFS456:
Settings > Location > Google Location Reporting > Location Reporting > Off
[Xposed Framework Modules] Surfinette:
Hi,

This doesn't work for me....

I'm on Miui Rom which uses WsmTools (xposed for Miui). But I can't seem to be able to access NlpUnbounce settings through WsmTools...

[MENTION=526666]cryptyk[/MENTION] could you please please make the settings accessible from an icon like a normal apk ?

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Xposed Framework Modules] BTT8:
So with both location reporting off and history off, there I no need for this module.
[Xposed Framework Modules] wilkster:
Isn't this really a WsmTools issue?

Sent from my VS980 4G
[Xposed Framework Modules] briatide:
I have both disabled and was still getting nlp wakelocks, with this module I don't see them nearly as frequently. I assume it is because of my weather app.

It hasn't affected my llama rules; I don't use tasker but I assume it should be fine as well.
[Xposed Framework Modules] PiggyFlooper:
The device I'm using requires a secondary busybox app when used with newest XFramework, and this breaks a few other modules. I find it more convenient not only for me, but also for many ics users, to ask the developer to make it work with Frameworkv.2_4_1 to extend use-ability.

This question is for [MENTION=526666]cryptyk[/MENTION]

Sent from above using Xparent Tapatalk Blue
[Xposed Framework Modules] wilkster:
As long as you have location services enabled (i.e. GPS or WiFi/Cell) there are apps that will request location data. When they do, the wakelocks will appear. Weather apps, some social networking, Google Play Services, Google Search all use it.... Google location reporting and History also use the same location data but upload it to Google for later use.When History and/or reporting is enabled the frequency of use of the location services increases (substantially on some phones). That is why many folks will disable reporting/history. Both to save battery and for privacy. The easiest way to completely disable location services is to turn them off in settings, typically under Settings->Location or Settings->GPS. Hope this helps answer your question.
[Xposed Framework Modules] BlastTyrantKM:
It's staggering the number of people who don't read the OP before they install this. Then they open the module, have absolutely no clue what the settings mean how what to do with them. And they STILL don't think, "Hey, maybe I should read the OP." Instead, they all post the same dumb questions.

Contrary to the popular phrase, there ARE stupid questions. Those are the questions that are answered in the directions you chose to ignore.
[Xposed Framework Modules] HDFLucky:
Excellent point! Most have been operating under the mindset that with Google location services disabled, location related wakelocks are non-existent. You have just reminded me that other apps can use these services (and thus cause the wakelocks). I also have a weather widget running, but have only installed this module within the last hour, so it's too soon to judge the benefit.
[Xposed Framework Modules] Surfinette:
Possibly, but it's also quite unusual to install an apk that doesn't create an app that can be launch straight from the desktop... I'm using many xposed modules... This is the first one I encounter that I can't be launch from the desktop ! That is why I was kindly asking the OP to mod his app so it can work with Miui...

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Xposed Framework Modules] spupuz:
I have read the op but I can't understand which are best parameter to set a timer

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Xposed Framework Modules] Bec de Xorbin:
There are no "best" parameters. Default is 60 seconds, so wakelock will appear every 60 seconds. Increase the timer and there'll be less wakelocks -> better battery life.
[Xposed Framework Modules] tylerdurden83:
I understand the timer meanings and their relation to polls more apart - less accurate pinpoint geolocation - more battery life, but what I couldnt get from the op or the rest of the thread is, does this only affect background location requests, or foreground ones too?

One example, say that I put the delay to 240 seconds, 4 minutes. A wakelock triggers, and it gets my current location. 3 minutes pass, 1 more min before the next request, when I open the camera app and take a picture. Is the picture taken with my current position, or the position last received, 3 minutes ago?
[Xposed Framework Modules] tonyp:
There seems to be quite a lot of misunderstandings in this thread, I'll try to clear up some of the issues.

The seconds you can change in the module don't directly modify the timer. They just set a minimum barrier after which the wakelock is allowed to happen again. So changing it below 60 won't increase the battery drain, it won't have any effect at all.

Setting it to 300 means the first requested wakelock is allowed to happen after the minimum of 300 seconds. So it's possible that it gets invoked after e.g. 350 seconds.

Next big misinformation in the thread: changing the value to 0 won't disable the wakelock completely, it will disable the timer so it stops messing with the default behaviour and thus the service will work like default.

No, obviously not. When locations are completely disabled they won't request any wakelocks.

When you're referring to the locations reporting and location history setting, then it might save some battery, as other apps can access location services as well.

This is another point many people are having trouble to understand.

We're just talking about the wakelocks here. A wakelock will keep the device awake when it's display is off and thus tries to stay in deep sleep mode.

With an alarm requesting a wakelock the developer requests the device to interrupt it's deep sleep to execute a task (like getting a location fix)

This module won't affect anything once the display is turned on.

Every app requesting a location update will immediately get served (if there's no fix yet a location search will get invoked).

This is hard to say. The moment you start the camera app with location enabled it will request a location update, the question is if it gets a fix before you're taking the picture.

Enviado desde mi Nexus 5 mediante Tapatalk
[Xposed Framework Modules] Citadel69:
Would someone help me with where to set my settings for this app. All the default settings are at 240. Thanks in advance for any help
[Xposed Framework Modules] starcallr:
240 is ok for you/
[Xposed Framework Modules] 1ceb0x:
The amount of BS information in this thread is staggering. I can't believe some of you...

In order to truly understand how this works let's all do this thing (i did, maybe it will work for you too):

- uninstall the module

- run your phone for 1 day and check your wakelocks with BBS

- you will notice the wakelocks from this module to be very high (sometimes reaching 3k per day)

- install the module and run it WITH ITS PREDEFINED VALUES (240 s).

- run your phone for 1 day and check your wakelocks with BBS

- you will notice that the wakelocks from this module will be very low now.

PS: the GOOGLE VALUES (AKA before installing this module) is 60s.

PS2: the MODULE VALUES (aka after installing this module) is 240s.

FAQ:

1. Will this **** my apps that require location?

R: NO

2. Will this work if i don't use Google Location Reporting?

R: YES

3. Why?

R: Because even if you have the location reporting OFF, your phone will still trigger those alarms and wakelocks from various sources (Weather apps, Zooper widget, Uccw widget, anything that uses Location).

4. Will this improve my battery life?

R: Depends on your usage and setup

5. Will this stop the wakelock completely if i put 0 as a timer?

R: NO. 0 will mean that these wakelocks can trigger themselves at any given moment --> worst battery life ever.

6. Can i tweak the values?

R: Of course you can. You can raise the values in order for the wakelocks to trigger later --> better battery life but be aware of the apps that use location - they might get data slower than usual.

7. How can i stop these wakelocks completely?

R: Search on Google (ironically) or go extreme bollocks and remove Google Play services from your phone.

There. Any questions?
[Xposed Framework Modules] NJGSII:
This module is really is something. Got alarms from play services down to only 30 something an hour with Google now and everything location wise on. I have both settings at 420 vs 240

Majority of the alarms from that are from activity detection, but there is no effect on battery from that.
[Xposed Framework Modules] rignfool:
It would be nice to see something like this post maybe as #2... Or an FAQ
[Xposed Framework Modules] Mistertac:
The G3 gets ridiculous standby time and that's with Data WiFi and Sync. Course when I fire up the Screen on this thing the Battery starts dropping!

I can leave it overnight at 100% and usually in the morning it's at 99% give or take. It's pretty amazing my S4 couldn't do that.

- Tapatalked From The G3 -
[Xposed Framework Modules] tboooe:
My bro has a G3. He loves it too. If it only had a pen....
[Xposed Framework Modules] rignfool:
The top one in your first pic can be killed by disabling the built in backup feature in settings...

If you're going to unbounce it... Might as well disable the backup feature...

It only runs when there is new info to backup...

So by unbouncing it... You're making it have to run again... Thereby using more battery... Instead of just letting it run once and be done...

FWIW I think that only runs when your phone is plugged in and charging

And the data-stall wakelock has to do with switching from edge to 3g to LTE...

If you unbounce that... You'll wind up with times without service when your phone could switch bands and find service...

! FINALLY what I was talking about where unbouncing causes more drain than it helps!
[Xposed Framework Modules] tboooe:
Yup...this is what I've been saying. Only a handful of things are worth unbouncing. Everything else, even if it has a high number of alarms of wakelock time does not necessarily mean it drains the battery. I personally only unbounce 3 things more than default.
[Xposed Framework Modules] Mistertac:
Well I've left some in there from testing and adding to the Spread Sheet so... But I can tell you im not seeing a negative impact so.. My service is fine too BTW and I drive for a living all around different service areas.

Also I get what you're saying about killing services and just plain disabling things but that's not the point of this module.

The point is to have things operating normally, but less frequently. And that's what I've done here with my phone, everything is working just fine, but with less times being woken up.

- Tapatalked From The G3 -
[Xposed Framework Modules] rignfool:
Not to beat a dead horse... But if the backup ran... It would only wake lock when there is new info... And you would use less battery... Unless your ROM is borked and it tries to backup regardless of new information...