yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] dwang:
yes you make perfect sense.

I think a lot of people obsess over wake locks but in the grand scheme of things, they don't really consume as much battery life as people think.
[Xposed Framework Modules] 1ceb0x:
it is advisable to use better battery stats to get a better picture of what wakelocks/alarms is killing your battery then decide to unbounce or not. what we mostly do here is trial and error to see what we gain, what we lose. unbouncing is similar to what they say about greenify... you greenify half of your system and then you expect enormous battery life.
[Xposed Framework Modules] tboooe:
AudioMix???

This as well as PowerManagerService.Display keeps my device awake 15-20% of the time.

Anyone know what Audiomix and PowerManagerService.Display is and if its safe to unbounce? I get lots of wakelocks even when my device is off and idle.
[Xposed Framework Modules] Pkt_Lnt:
It is Google Cloud Messaging. You are messing with core functionality there.

https://developer.android.com/google/gcm/index.html

Too much "if a little is good a lot must be better" attitude in here with no research and thought as to what and why to unbounce a service.

Google Search a wakelock and read carefully could keep you from making serious mistakes that stop basic functions of a android smartphone.
[Xposed Framework Modules] 1ceb0x:
No attitude here brother. i am not unbouncing because i want to squeeze any tiny little bit of my battery... i do it mainly for testing purposes so i can build up the spreadsheet with what it is safe and what is not so that in the future we will avoid posts like these from new users. But thank you for the link.
[Xposed Framework Modules] Pkt_Lnt:
No attitude at all. Sorry. I wanted to warn you to be careful and research before trial and error. This was intended more to those who say "can I unbounce XXXXXXXXXXX safely, relying on someone else's opinion.

Again sorry to come off as giving you trouble, My sincerest apologies, just be careful.
[Xposed Framework Modules] naughty6t9:
That's how we will learn bro. What to block and what not to. We will have to play with devices until v built the database,

Good thing is that v can always disable xposed on boot and revert the changes if v r stuck with boot loop.

Thanx for concern :)
[Xposed Framework Modules] magnamentis:
yes, what you say is exactly the point here

good point indeed, medium level problems like clock not "clocking" haha... can easily be learned and reverted and should there be a bootloop

you mentioned the solution.

by the way when i had the app first i unbounced around 30 wakelocks and 20 alarms, many of them not recommended as i known now after a bit of reading and friendly hints like the one from [MENTION=4403217]Pkt_Lnt[/MENTION] but i also have to mention, so to not shying of others to try things out, that i never had a random reboot, bootloop, phone not working anything like that or even worse, so obviously these things are quite forgiving. so i'd say shoot ahead and report your findings.
[Xposed Framework Modules] Pkt_Lnt:
A little advance research goes a looooong way in my 45 years of doing science. Just sayin'. :cyclops:
[Xposed Framework Modules] tboooe:
Audiomix...improvement

Its only been about 1 hour but I think I may have done something to lessen the wakelocks caused by Audiomix. After doing some research it was suggested to turn off screen touch and lock screen sounds. I guess this is a real bad problem on Nexus 4 devices. So far I have only turned off the screen touch sounds (I like the screen lock sound!). Before making this change, my Note 3 would be held awake for about 20% of the time. After this change, Audiomix wakelock has gone way down. My device is awake about 10% of the time now. Of course I need to keep monitoring this over a longer period of time but so far results are encouraging.
[Xposed Framework Modules] Finnegans:
This module pretty much singlehandedly saved my battery life. Couldn't be happier. Hope the developer enjoys the coffee on me!
[Xposed Framework Modules] pabloyan:
decided to set all the defaults (ie wakelock/alarms that the app has info on) from the app default 240 to 600

should be no issues, right?
[Xposed Framework Modules] 1ceb0x:
I knew this since a long period of time mate. While it is not really a fix, it is a workaround but do note that Audiomix kicks in every time a sound is played. Unbouncing it does not work, the only way to make it smaller is to do what you did. I don't think that this is a wakelock because it will only fire when the UI sounds are played so being afraid that it will eat your battery while screen is off is not actually 'true'.

You should be fine, yes.
[Xposed Framework Modules] rignfool:
All the powermanagerservice wakelocks are at the kernel level...

They are not in userspace...

Audiomix is 'noises' your phone makes EG: rings... Notifications... And screen off music...

To quote the BBS guys...

Power your phone off... Then on... Then plug and unplug the charger... Take a 4 hour idle reading... Look at the 'out-of-control' wakelocks... IN USERSPACE...

Then try unbouncing a wakelock that you know what it does... Use Google...
[Xposed Framework Modules] Thomas_BA:
Try it and you will see if everything is working as expected. All those unbounces you do are wakelocks from applications that drain your battery or wake your phone up for a long time??

Again do not unbounce wakellocks which do not drain your battery or wake your phone during sleep for a LONG time. You do no good with this and this in not the purpose of this module.
[Xposed Framework Modules] RoxAbout:
Gleaned Stuff

Lots to read, But I love the app.

From my observations of the various posts:

1] The module DOES NOT stop any process/wakelock it just delays it by X seconds default = 240 = 4 minutes then it allows it to run.

2] Therefore [ at least on my NX5 ] If #1 is correct I set quite a few of them to 43200 = 12 hours surely they do not need to run every 4 mins!

My battery life is much better and the drain is much less by using this app.

Other:

In my humble opinion I found that greenify causes more trouble than its worth [yes I bought it] But its uninstalled. Wake lock detector is so so It was of no help really to me to figure out what ones to "unbounce". I will have to reinstall Better battery stats and see what that does for me.

I like the idea of the spread sheet but it prolly would be of more help if the items data was inside the unbounce app, which I'm sure the dev will fill in the blanks as time goes by.

However I also agree that the various settings + apps + combos + devices = way too much for a spread sheet to cover.

Your milleage will vary!

Request:

When your going thru the list and you pick one to look at....and your done looking and hit the back button...it drops you nicely where you were at on the list.

However if you make a change on that item it drops you at the top of the list! and you have to scroll back down to where you were...please fix this, there are way too many items on the list to have to start over every time you make a change.

Thanks again for the awesome app.

:good:
[Xposed Framework Modules] marbertshere:
Just so I understand correctly, you are devising a database of known wakelocks and whether or not they can be safely unbounced? Are you the only one working on this?
[Xposed Framework Modules] 1ceb0x:
Yes. And no. I have two other users from this thread that will help me out to fill it and most probably i will add a few more depending on the number of wake locks/alarms that we find during the process. Right now not that many to report but i bet the spreadsheet will go bigger.
[Xposed Framework Modules] Surfinette:
[MENTION=2688060]1ceb0x[/MENTION] I've looked into your spreadsheet. Great idea.

I've noticed that you have put a red flag (not safe to unbounce) to:

android.appwidget.action.APPWIDGET_UPDATE

But actually I did unbounce this one with a value of 3600 and I don't experience any issue with my widgets (tested for the last 3 days). So it may depend on the widgets we are using, but for instance I use the BZ weather widget and it is always updated correctly (including the clock within the widget, always on time)

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Xposed Framework Modules] 1ceb0x:
Clock within the widget i believe it is updated by the android.intent.action.TIME_TICK	. Did you noticed anything else on other widgets, like for example weather, battery level, etc? Because i tested it and for me it seemed it stops a few widgets from update.

I am curious as of why yours worked correctly.

And thank you!
[Xposed Framework Modules] Surfinette:
I know this will sound very strange, but just for the stake of the experiment I've pushed the value to 99999, and even now I don't seem to have an issue with my widgets. I know it doesn't even make sense to me...

Ok, I don't use a lot of widgets, but still, the BZ weather widget updates fine (including date, time, weather, and battery level).

I also have a music widget that will update the album cover when I move to the next song using the widget buttons.

I have a question which is probably very stupid/noobish.

Will unbouncing an alarm have a delay only while screen off, or both when screen on and off? Because, if it's only when screen off, then who cares if a widget doesn't update when screen off? ;)

But I guess it wouldn't make sense that unbouncing is only effective when screen off...

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Xposed Framework Modules] naughty6t9:
It's not about one not getting random reboot or having issue by unbouncing, where as I feel even a single person falls in boot loop means by some or other means it's not safe to unbounce it so v should avoid it.

I had random reboot when I unbounced Audio Mix. I know it has to do with sound. I was just giving it a try what happens if v try to reduce.. so had to disable xpose

Research has started there is no way to turn around now.. [emoji12]
[Xposed Framework Modules] cryptyk:
It affects both, but only makes a battery difference when the screen is off. Apps will grab a wakelock even when the screen is on to make sure that if the screen goes off, they still have the cpu awake so they can continue doing what they're doing. If the screen stays on for the duration of the wakelock, you didn't really save battery by blocking it because your device was awake anyway. The current stats in unbounce don't take this into effect yet, but it's likely a small margin of error for most people.

The reason you want to let your widgets update while the screen is off is so they are updated the moment the screen comes on. You don't want to sit and wait for 30 seconds while all of your widgets update when you turn your phone on. That said, your weather widget has no business updating every 60 seconds. if your weather reading is 20 minutes out of date, you're probably ok ?

Sorry for the lack of posts, and short posts. I've no access to a computer until Saturday, the 27th. I have been reading the thread daily, though. Thanks to those that are helping! I love the spreadsheet and will roll it in to unbounce later.

Thanks,

Ryan
[Xposed Framework Modules] 1ceb0x:
2 new wakelocks added to the spreadsheet

[B]GCM_CONN: [/B]Keeping app content fresh is important to retaining users. And it’s easy with the popular Google Cloud Messaging for Android, by sending lightweight messages to your apps installed on Android devices anywhere in the world. Responsible for sending push notifications to your phone, for every app.

[B]GOOGLE_C2DM:[/B] Android Cloud to Device Messaging (C2DM) is a service that helps developers send data from servers to their applications on Android devices. The service provides a simple, lightweight mechanism that servers can use to tell mobile applications to contact the server directly, to fetch updated application or user data. The C2DM service handles all aspects of queueing of messages and delivery to the target application running on the target device. This service was deprecated since 2012 but there are still apps that are using this service instead of the newly and improved GCM.

Safe to unbounce: [B][COLOR="Red"][B]NO[/B][/COLOR][/B]

Thank you [MENTION=4403217]Pkt_Lnt[/MENTION] for the link for GCM_CONN.
[Xposed Framework Modules] cAase:
Does anybody knw what MCS_hearbeat does? Seems to give alot of wakelocks.
[Xposed Framework Modules] Mistertac:
Another one safe to UnBounce is the "SyncLoopWakeLock" - WakeLock

Info on this one can be found here

https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/SyncLoopWakeLock

It's not a huge offender on my phone, but research shows that it has been for others so I figured why not look into it and post it.

Like someone else already stated... Our phones do need WakeLocks and Alarms to function correctly. This UnBounce utility that we now have is very powerful and I don't think people should just start UnBouncing things without using Better Battery Stats and/or WakeLock Detector + using Google to search beforehand.

Just be careful and UnBounce things one at a time and see what results you get, or you could run into problems.

- Tapatalked from the G3 -
[Xposed Framework Modules] rignfool:
MCS_heartbeat is the 'keep my connection to Google alive' wakelock...

Keeps GCM working...

It sends data to Google and will keep you connected to hangouts
[Xposed Framework Modules] 1ceb0x:
Connected to Google servers in general, not only for Hangouts.

---------- Post added at 12:46 PM ---------- Previous post was at 12:45 PM ----------

Feel free to add it to the spreadsheet, mate! Nice find.
[Xposed Framework Modules] Pkt_Lnt:
Others gave the simple answer, here is more info to decide.

https://code.google.com/p/ics-openvpn/issues/detail?id=246
[Xposed Framework Modules] Smultie:
Thanks, this sheet is however so locked down that I can't link to it in my own Google Drive.

Also, really looking forward to some info on unbouncing the CastSocketMultiplexer wakelock. It's somehow linked with Google Chromast/Screencast and can sometimes really keep my Nexus 5 awake.
[Xposed Framework Modules] yurividal:
Can you make this public-editable? Right now it is read-only for me...
[Xposed Framework Modules] Mistertac:
There's a few of us actively working on the list, I think [MENTION=2688060]1ceb0x[/MENTION] just wants to be careful adding things without people doing as much research as possible beforehand.... So that's why its not public.

Course that's entirely up to him I'm just throwing that out there.

I think if a few of us actively work on the list it could be finished up rather quickly.

Finding the right reference material so that it's understood for the masses seems to be one of hardest things... For me at least. Just have to spend some time on good Ol Google.

- Tapatalked from the G3 -
[Xposed Framework Modules] cAase:
com.android.internal.telephony.data-stall - 2400 s

Is that a typo where it's supposed to say 240 or is it really 2400?
[Xposed Framework Modules] Mistertac:
I updated the spread sheet WakeLock section with :

SyncLoopWakeLock

WindowManager

ICING

Still looking for better details on a couple of them since I pieced together multiple sources in regards to what they are really doing... Hopefully more to come soon

- Tapatalked from the G3 -
[Xposed Framework Modules] 1ceb0x:
Let me know how i can give you access to add it to your Drive and i will do it. I am not that experienced in Google drive, sorry :).

This. Thank you [MENTION=5500746]Mistertac[/MENTION]! I didn't want to make it public because i am a catious type of guy and very careful with what i deliver. Having the spreadsheet public will give me extra work by testing each wakelock that appears new in the sheets. Having only a carefully selected users that i know they will do their research - let's just say i can sleep well at night :). Mistertac is one of the users that have access to the spreadsheet. He demonstrated that he does his homeworks.

My post is not a direct hit to the other users, it is just my precaution. I will see if we need more guys and select a few from the thread. For now we are OK only 3 because as i said before, we don't have that many wakelocks/alarms to consider.

To make it even better, you guys can give hints or other wakelocks/alarms that are not in the spreadsheet and we will add them.

That is my personal settings. I suggest go lower - 600. If the wakelock still bothers you, go higher. For me at 2400 is OK and no side effects.

Thank you mate! Appreciate your help!
[Xposed Framework Modules] nobnut:
Edit the value to your chosen one and then press the enter key on your keyboard. if you just enter it and back out, it isn't saved.

Once you've changed it and press enter [return key], then you can go back in and verify it has stuck.
[Xposed Framework Modules] yurividal:
OK. So, you can add com.whatsapp.messaging.MessageService.LOGOUT_ACTION alarm as SAFE... It was my top alarm. I changed it to 1800
[Xposed Framework Modules] 1ceb0x:
Sure. Any side effects? I don't have it so i can't test it myself. Thank you.
[Xposed Framework Modules] yurividal:
Sure. I have it like that for 3 days already. No problems AT ALL... WhatsApp is still 100% functional, and notifications are immediate too.
[Xposed Framework Modules] Mistertac:
I have 2 Alarms I've changed and I'm still monitoring.

Androin.Content.SyncManager.SYNC_Alarm

And

Android. App. Backup. Intent. RUN

I've had them both set to 600 and I believe they could go higher. I have seen no negative effects.

Both those Alarms are fairly high on my BBS list and UnBouncing them has reduced that.

Does anyone in here have a decent explanation of what they are actually doing aside from gathering they are tied into backing up Apps/Data and Sync?

Edit::

I've added them to the Spread Sheet with more info TBA.

It's definitely a WIP so at least they've been tested for now..

- Tapatalked from the G3 -
[Xposed Framework Modules] JerryGNYC:
FWIW, if your weather widget also has a clock, for example - Beautiful Widgets, you will want it to update every 60 seconds.

However, I do keep the weather refresh rate set to 30 minutes...
[Xposed Framework Modules] Brutal_Master:
Has anyone else noticed that this module uses quite a bit of CPU? BetterBatteryStats said it used almost as much CPU as gmail to run all day. This seemed a bit high to me.. Kitkat4.4.3
[Xposed Framework Modules] tboooe:
RILJ unbounce...interesting results

So I unbounced RILJ and my battery consumption at idle doubled from about 0.5% per hour to 1% per hour. The worse offender was the phone radio according to GSAM which accounted for over 30% of the battery drain. Usually this amount is 10-14%. I have since reverted RILJ back to default and my battery drain at idle is settling back to my normal range. Not sure how RILJ can have this effect.
[Xposed Framework Modules] aeoveu:
Well - I just checked it, and unbounce uses way more CPU than Gmail (over a period of 13 hours, Gmail only used 6 seconds whilst Unbounce used around 3 minutes-something.

Not sure if that has an impact as such, because IMO, what really drains the battery is network communication (and wakelocks).
[Xposed Framework Modules] tboooe:
I have found the opposite to be true. In the past 3 hours Gmail has used about 3min of CPU tiime while Unbounce has used 24 seconds. This is according to GSAM. BBS shows roughly the same. I also have not unbounced any other wakelocks or alarms aside from what came with the module. Maybe this has something to do with it?
[Xposed Framework Modules] yurividal:
Maybe BBS sees it as using CPU every time one wakelock that is blocked tries to run and is blocked...
[Xposed Framework Modules] Brutal_Master:
hmm Thanks for the info guys, i think at this point we need some feedback from Cryptyk on this CPU issue. [MENTION=965229]yurividal[/MENTION]: You're theory is a very interesting one; hoping cryptyk can verify/deny it.
[Xposed Framework Modules] Henri Blanche:
Greetings All!

A trivial observation and a question.

First, the program still calls itself NlpUnbounce in the menu. It's Unbounce everywhere else. Might want to fix that to be consistent.

Second, it seems to be working and I've made a Karma contribution. Nonetheless, I don't see where I can tinker with the settings. What am I missing? Program certainly doesn't behave the same way as it does in the video.

Cheers, Henri
[Xposed Framework Modules] magnamentis:
does it really make sense ?

to compare apples with pears ?

a) if somone has 8 gmails account it will use more resources than someone else with just one

b) if somone unbounces 30 apps with a high wakelock/alarm frequency it will use more resources than somone else unbouncing only 10 apps.

c) every process, even energy production is not 100% efficient, so to save 0.5% battery per hour in idle we definitely have to invest something

.....other wise we would perhaps saving 0.6% per hour, so in this example we would pay 0.1% to save 0.5 net. so we cannot disconnect the

.....investment form the purpose and the return on investment. this kind of separation does not make sense but makes a false impression on

.....newcomers who just read and don't have much experience, so indirectly we deprieve them of the opportunity to safe battery.

i tried to stay as short as possible and hope the meaning is clear. don't drive at full speed over the highway and complain about fuel consumption :) ;) ;)
[Xposed Framework Modules] marbertshere:
[ deleted ]
[Xposed Framework Modules] tboooe:
GSAM

I thinks its really ironic that the app I use to track battery usage (GSAM) is my 3rd highest battery hog behind Kernel and Android System! LOL!

Luckily its not usually the case but for whatever reason the past 4 hours GSAM has been acting up.
[Xposed Framework Modules] cryptyk:
Press the menu at the top left, then wakelocks. Select an item to modify its settings.
[Xposed Framework Modules] Henri Blanche:
Ah, thanks. That definitely looks like the screen prints.
[Xposed Framework Modules] esimon311:
Question why are all my wake locks and alarms saying. Sorry we have no information on this Wakelock at this time? Am I missing something?

_________________

IT'S OVER 9000!!
[Xposed Framework Modules] tboooe:
This is a work in progress. People on this thread are trying out unbouncing various wakelocks and alarms to see what is safe. There is a great document started by 1ceb0x that has good info on what people on this thread have been able to unbounce with little or no impact on the performance of their device.
[Xposed Framework Modules] dimm0k:
I have an app called Transit that comes with a widget that I do not use at all that I have reason to believe is causing the TRANSIT_WIDGET_UPDATE alarm. My alarms list has that as the highest and if I tell Android to stop this app or if I uninstall it, this alarm goes away or stops its increments. If I start the app again, it doesn't go off right away... I believe once I start moving around from one destination to another does it pick up. I barely ever use this application, but it's useful from time to time so I'm wondering if I should Unbounce the alarms... both in GSAM or BBS I do not see this alarm at all... but in Unbounce it's listed as the highest alarm and keeps increasing. any suggestions?
[Xposed Framework Modules] magnamentis:
something general

perhaps you remember that we were talking about device specific differences:

so albeit it was clear that it will happen sooner or later a just came across a very significant difference.

i'm currently testing with 3 devices, setting them up identically to see the difference in result and behavior: N7100, Nexus 5, OnePlus One

as it happened and even though all settings re identical ( unbounce and otherwise ) my note 2 has started to permanently loose cell signal

after a few hours, while the other two devices continued to work properly.

to verify i deactivated the module and cell signal was stable again. now i will have to find the culprit but be aware that most probably not all modems

will accept specific settings in the same way. obviously my exynos equiped note 2 was not able to handle the same settings like the qualcomm equiped devices, so stay alert as to device specific differences