yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Mistertac:
Ahh OK sorry I'm on Tapatalk and don't get to see the title..

That one I couldn't find much on either other than its a GPS Wakelock. Not very helpful i know lol

Have to keep digging around and see what I can find.
[Xposed Framework Modules] tboooe:
I assume you still dont see any issues with unbouncing it for 240 secs?
[Xposed Framework Modules] Mistertac:
No issues here at all no!

Is that one holding your phone awake for a long time or are you just experimenting?
[Xposed Framework Modules] tboooe:
I just noticed it last night. It accounted for over 50% of the wake time of my phone at idle. Ok I will try your 240 sec unbounce and see what happens.
[Xposed Framework Modules] Osama Zabin:
I have nlp wakelocks (13m during 16 hr) even though the location is turned off, is it normal? It's not happening every charge, but can see it randomly with previous and new GPS version 6.1.74

I haven't activated Unbounce mod yet; still checking battery performance with different scenarios.
[Xposed Framework Modules] cryptyk:
Do you have global stats turned off in the settings? I think the problem stems from there. The logs unfortunately don't help because they crash in the system code. It will be fixed, but it's not straightforward. I know that can be frustrating, but stick with me as I find a way to get it working for you.

Thanks,

Ryan
[Xposed Framework Modules] the7thson:
Yes, global stats are off. PS - I've been encountering this issue since before global stats were even introduced in the app. That said, I've kept them off for the most part.

Thanks for your quick reply, I'll wait patiently as you work through the issue. Let me know if there is anything I can do to help test, I'd love to be able to use Unbounce :)

Thanks!

EDIT: I'm seeing some references to XPrivacy with Unbounce, but I have Unbounce 100% unrestricted in XPrivacy. Could this be causing the issue?
[Xposed Framework Modules] Zordak7:
SMSDispatcher has the same problem, it's not detected by Unbounce, so can't be unbounced, and is a partial kernel, and it's under the "Phone"app or service or whatever that is. The wakelock is really agressive, and doesn't let my phone go into deep sleep at all.

How can I make the app recognize this evil wakelock?
[Xposed Framework Modules] cryptyk:
Make sure Unbounce I'd checked in the xposed modules and reboot.
[Xposed Framework Modules] 1ceb0x:
I have it ocasionally. I unbounced it only once and i haven't noticed something major but then again, it was only once. It has something to do with cellular data.

---------- Post added at 04:30 AM ---------- Previous post was at 04:28 AM ----------

You need to disable services, receivers and providers for these to go away.check out my post from my signature.You can do it with any app you want, no need to use the one from my post, as long as you know where to find them and to disable them.
[Xposed Framework Modules] cbomb101:
My battery lifes better with this. Usually have 5 hour mark. Looks like 6 hour + is gonna happen. Over night android tuner said 0.14 % per hour loss which is good. Lost like 1% over night.
[Xposed Framework Modules] shinra00:
those are so great stats!!!! i'm still on the 1.1%/h. congrats
[Xposed Framework Modules] LiFeSII:
Hi Guys,

Sry noob question:

I bounced the RILJ to 240 - so i dont miss phone calls ?

Thanks
[Xposed Framework Modules] kingbeta:
Audiomix is still marked as safe to unbounce in the app, but unsafe on the spreadsheet. Which is correct?
[Xposed Framework Modules] shinra00:
The information that you have on the app was removed from the spreadsheet. They are not linked (maybe a possibility Ryan?), and therefore the spreadsheet is always more accurate than the app.

Ryan made the app and all the programming while others like icebox (i appologize to the others that i cannot remember by heart their nicknames) are finding and exploring all the possibilities of this tool (unbounce app)
[Xposed Framework Modules] Mistertac:
I've changed it in the Spread Sheet to UnSafe and that's the most current status. I'm not sure how Ryan pulls the info from there or how often.

You should be OK to have that one at 240, just test it out over time and see how your phone behaves.
[Xposed Framework Modules] xk0niR:
For myself unbouncing RILJ did cause more drain than battery saving.

The problem (for me) was it did cause more wakelocks actually which get blocked by unbounce. Blocking wakelocks does also require battery.

Just see if its fine for you
[Xposed Framework Modules] furboom1240:
Hello there

Hi there, Ryan. I had an issue just last night in which despite Unbounce fully enabled and working, my phone crapped out 25% of its battery life in just 5h11m in airplane mode (from a full charge!). I had your recommended wakelocks in place and yes, Android OS is 55% of that value.

If you can assist me later today in regards to this, I would certainly appreciate it! I go to College, so I won't be able to immediately reply.

thank you for all you do! This module is a step in the right direction!
[Xposed Framework Modules] Mistertac:
Yup.... This is definitely the case with a lot of these, results may vary [emoji106]
[Xposed Framework Modules] LiFeSII:
Thank you,

I think im good going - losed 5% from 6:20am to 3.30pm - so i think its working great :fingers-crossed:
[Xposed Framework Modules] tboooe:
+1...the best I get according to GSAM and BBS 0.2-0.3% per hour at idle overnight with 97% deep sleep. I am still tweaking though, hoping to get to 0.1%!!!!

---------- Post added at 06:55 AM ---------- Previous post was at 06:40 AM ----------

Install an app like GSAM or BBS to determine exactly what it is thats causing the drain. From my experience it will be only a handful of things causing the majority of it. Also, dont go crazy unbouncing everything. Even though something may have a high number of alarms of wakelocks it does not mean its draining the battery a lot. GSAM will show you how much battery is drained.

Good luck.
[Xposed Framework Modules] 1ceb0x:
Reaching 0.1% is almost impossible unless you have a kernel option to stop log spamming overnight while screen is off - that improves the battery life greatly as well. i am afraid you won't be able to reach 0.1% even if you unbounce everything and greenify everything :).
[Xposed Framework Modules] tboooe:
One can dream though....:D
[Xposed Framework Modules] Chahk:
Just wanted to thank the dev for this invaluable module. Got the donation version, and finished up the Russian translations.
[Xposed Framework Modules] HDFLucky:
Like this?

#!/system/bin/sh

rm /dev/log/main
[Xposed Framework Modules] magnamentis:
go for it :)

this is what i get for months already so what is definitely real:

- Nexus 5 every night for 8 months 0.1 - 0.15% per hour

- N7100 almost every night for 8 months 0.15 - 0.3% per hour with exceptions, perhaps 2 or 3 per month, 0.5 - 0.6% per hour reason unknown but got better with the use of ubounce. was mostly nlpwakelocks and the likes.

- OnePlus One 0.12 - 0.2% per hour for the last 2 months and i'm sure i'll get it to nexus 5 level after another month or two.

so as you can see it's worth to try if you like to play and optimize things but of course it does not really matter whether you start your day with 99% or with 98% showing :)

good luck and enjoy
[Xposed Framework Modules] dimm0k:
might be a little off topic, but what devices do you guys have? I have the Samsung Galaxy S4 and if I go off the charge anywhere in the 90s, it seems like battery life goes down quickly until I get into the 70s where it seems to be longer there to go down... kind of screws up my numbers I think so I never see that low.
[Xposed Framework Modules] tboooe:
Pls excuse my ignorance [MENTION=5216891]HDFLucky[/MENTION]...how do I implement this and is there any downside? Are these commands I can execute in terminal emulator?
[Xposed Framework Modules] xk0niR:
Exactly the same for me.

I got a S4 too

The 90s go down so quick, but then it goes slower and slower
[Xposed Framework Modules] HDFLucky:
The code shown is an init.d script. You would simply create/append it using a *nix editor (NOT Windows Notepad!), and then reboot. This will kill all logging, so that's the only downside I think.

I suppose it could also be done from a terminal emulator window, though you'd probably have to add a new line with "su" before the rm (remove) command.
[Xposed Framework Modules] tboooe:
Thank you...I wonder if doing this actually saves battery. I will give it try.

BTW I believe I can also disable logcat in the build.prop file too.
[Xposed Framework Modules] shinra00:
Superuser app has an option to disable the permission of other apps to make logs. Do you think disabling it will save any battery ?
[Xposed Framework Modules] tboooe:
Good question..only one way to find out! I do wonder what is more efficient...disabling logcat via init.d, build.prop, or superuser? Maybe I will try all three!
[Xposed Framework Modules] MIKEMON:
I have forbidden / Logcat / v SU and super

Otherwise, this application works

https://play.google.com/store/apps/details?id=ma.wanam.stoplog&hl=cs
[Xposed Framework Modules] HDFLucky:
I guess that depends on whether the overhead of doing so creates less drain than just letting the logs run.

I'm unsure what you mean by "each term." If you choose to do it in init.d, it would be exactly as I showed it in the earlier post - just 3 lines.

See if this helps: http://elinux.org/Android_Logging_System

Certainly all Xposed module logging would be disabled. It might make an interesting experiment to try, but I don't think that would be good on a permanent basis.
[Xposed Framework Modules] HDFLucky:
Ordinarily I would say that it should have no impact on the module performance, However, in the case of Unbounce, a large part of its functionality depends on capturing data and then acting upon it.

This might more properly be a question for [MENTION=526666]cryptyk[/MENTION], the OP, since I don't know where the wakelock stats are stored.
[Xposed Framework Modules] MIKEMON:
yep, but disable logging

would not affect the Unbounce you have selected

For me everything is fine and functional
[Xposed Framework Modules] cryptyk:
Unbounce shouldn't be affected by disabling logs.
[Xposed Framework Modules] tboooe:
So you have disabled logcat? Did you notice any improvement to battery?

Did you disable through init.d or build.prop?

OK I just disabled logcat via build.prop adding the following line:

logcat.live=disable

I will monitor my battery drain and report back. I am already very low at 0.2-0.3% drain per hour at night during idle so I am not sure how much better I can get.
[Xposed Framework Modules] VoLTaqe:
What is your settings ? Do u use airplane mode overnight ?
[Xposed Framework Modules] tboooe:
No, that is with all Google sync, 4g, etc on. Overnight I usually get 97% deep sleep time.

Along with Unbounce and Greenify I removed a lot of useless Samsung apps with Titanium Backup. I dont have any apps auto updating or syncing though except for weather which I have every 4 hours.

As for Unbounce I only found a few that were troublesome for me aside from the two NLP ones that are unbounced as default.

Ulrdispatchingservice

Configfetchservice
[Xposed Framework Modules] furboom1240:
I installed Wakelock Detector and found the app responsible. Hold your breath...it was...Facebook Messenger. I should've guessed that. I restrict most permissions via app ops yet I fail to deny its keep awake and wakeup policy.

I will see how it goes overnight and get back to you.

Thank you for your help, [MENTION=4290049]tboooe[/MENTION] !
[Xposed Framework Modules] Mistertac:
I've recently been having a hard time disabling some of the GPS Services/Receivers that our friend [MENTION=2688060]1ceb0x[/MENTION] has referenced in his signature, I was getting endless EventLogHandOff Wakelocks along with CheckIn as well... I was using 3c and that just wouldn't allow me to make certain changes, it would say " failed "

OK so I try ROM ToolBox's Auto Start Manager and although it would show that I disabled them, the Wakelocks would continue.

So I went and re-downloaded Auto Run Manager and that finally did the trick, no more random Wakelocks popping up as a side effect from disabling things.

I know myself and couple others in here have spoken about 3c not being able to disable things before so I just wanted to mention to try out Auto Run Manager.... Worked like a charm for me.
[Xposed Framework Modules] tboooe:
Is there any additional overhead using apps like 3c, Auto Run Manager, or ROM Toolbox? Or are these apps only used once to make changes then they can be shut down?
[Xposed Framework Modules] Mistertac:
No there isn't any additional over head from those apps... 3c can do quite a bit so the only other over head you'd get with that one is if you're scheduling tasks to be performed at Boot such as optimizing database, apps, and ZipAligning.

But even then it's very minimal.
[Xposed Framework Modules] MIKEMON:
I have disabled logcat using Stop logcat from Wanam

I am using init.d script

no batteries do not expect big savings
[Xposed Framework Modules] furboom1240:
It is a bit better

Good morning! (in GMT -4:00)

But this time Google Search was the culprit. I am utilizing app ops in combination with Unbounce to improve my battery. I restricted the the living daylights outta com.facebook.orca (Facebook Messenger) and that seems to be at the bottom of the list. No FCs either, which is good, because I did that to Android System and my phone randomly restarted.

Take heed-do not touch android system permissions via app ops! It is much safer through Unbounce. You could crash your phone. I am lucky.\

i went from 100% to 84% in 5 hours. better than yesterday, but could be much better. I guess I'll keep experimenting with WLD and App Ops until I find the perfect balance. Then I will report it here.

Have a great day, everyone!
[Xposed Framework Modules] DirkStorck:
Hi. I have noticed that resetting the states seems not to be working 100%.

If I reset the states and check back later the total state shows a value that can't be.

Thank you ?
[Xposed Framework Modules] tboooe:
Just an update after I disabled logcat through build.prop file. In 9 hours I lost 1% battery at idle. I normal lose 2-3% battery in 9-10 hours so there was a definite improvement. Not sure if this is related to disabling logcat or some coincidence so I will have to monitor over the next few days. Here are some details:

Total time: 9 hours

Drain: 1% (77>>76%)

Held awake: 25 mins

Deep sleep: 95%

% Battery consumed by apps: 64.2%

% Battery consumed by phone radio: 32.9%

Held Awake detail:

Kernel: 15 min

Android system: 5 min

Google services: 5 min

Whats bothering me though are these two items in Kernel:

Bam-dmux: 9 min

Powermanagerservice.Display: 5 min

My display was only on for 1 min during the 9 hour test so I dont understand why Powermanagerservice.Display is holding it awake for so long.

Bam_dmux...I know this has something to do with mobile data so I need to find the app that is causing this. Strange because the only app that I allow to automatically update is my weather app every 4 hours and I dont see it in my list of things causing battery drain or wakelocks.
[Xposed Framework Modules] MIKEMON:
yep,PowerManagerService is basically a catch-all for partial wakelocks (wakelocks requested by non system apps). To see which apps are actually requesting the wakelocks, go to the Partial Wakelocks screen.

---------- Post added at 06:47 PM ---------- Previous post was at 06:41 PM ----------

Google Voice is an example uses the incoming and outgoing calls
[Xposed Framework Modules] tboooe:
Thank you. I understand what Powermanagerservice is but I was referring to Powermanagerservice.DISPLAY in particular. I checked the Screen Wakelocks in WLD and I only have 3 items listed under totaling 40 seconds. Gotta look more into this.
[Xposed Framework Modules] MIKEMON:
Well, they are at each other
[Xposed Framework Modules] Zordak7:
How can I get to android.internal.telephony? Which app should I block to avoid wakelocks activated by that?
[Xposed Framework Modules] cryptyk:
Hi everyone,

I'll be releasing version 1.4 a little later today. The big change is that when Unbounce starts up, it will detect and fix the following:

- Unbounce isn't running. It pops up the modules list and asks the user to check Unbounce and reboot.

- Xposed isn't running. It pops up the Framework box and asks the user to push Install/Update.

- Xposed isn't installed at all. It downloads Xposed and launches the APK Installer.

- The device isn't rooted. I don't try to root the device :) I just point the user to Xda-Developers.

Most of you won't notice the changes because most of you already have your device setup properly. These things were confusing lots of other people, though, and I was fielding dozens of emails a day to tell people that Xposed is required, to check the module, to reboot, etc.

Another big thing is Alarm support for Android 4.1.2. Xda-Developers member [MENTION=4354573]chhapil[/MENTION] added 4.1.2 support, so please thank him if you're one of the many people who will benefit from that!

I also moved the project from BitBucket to GitHub. I'll be moving the issues over later, but if you'd like to report something, fork the code, get the latest, etc, please check the Github site.

I also improved the translation workflow, and fixed a bunch of bugs.

I'll probably do a 1.4.1 release tomorrow as people find the inevitable bugs.

!One request! If you're one of the folks who has been helping with translations, there are some new string in the welcome section. I'll probably do the build around 21:30 GMT. If you can stop by and do the new translations by then, they'll make the build. Otherwise, I'll do another build tomorrow sometime that will pick up the new translations. If you're not already someone who is helping with translations, please consider it. It's really easy, you can translate one word, or an entire language, and you'll be helping out all those people in the world who don't speak English. Thanks!

Ryan
[Xposed Framework Modules] cryptyk:
Since many of you will never see the FIXIT feature of Unbounce, you can see what it looks like here:

:)

[YOUTUBE]vgcOnGvGMw0[/YOUTUBE]
[Xposed Framework Modules] MIKEMON:
Completed to a friend

Thanks for the update

---------- Post added at 10:01 PM ---------- Previous post was at 09:57 PM ----------

everything works according to my expectations

just please add my translation

Completed a moment ago
[Xposed Framework Modules] cryptyk:
Done! Thanks for the fast translation! You're the fastest :)
[Xposed Framework Modules] Zordak7:
Hy

OP, do you know why SMSDispatcher, aPhone Partial Wakelock is not detected by Unbounce, so can't be unbounced, ???

It's under "Phone" in BBS (that's the only thing it says, "Phone"). The wakelock is really agressive, and doesn't let my phone go into deep sleep at all.

How can I make this great app to recognize this evil wakelock?
[Xposed Framework Modules] cryptyk:
It's already on the issues list to investigate., and it's already high priority.

My guess is that it's because Unbounce collects its stats from apps that use the "normal" method of acquiring wakelocks, and some kernel apps like the phone go around that.

BBS, on the other hand, depends on the Android system to collect stats, which works slightly differently.

Thanks,

Ryan
[Xposed Framework Modules] Zordak7:
Thanks a lot for the answer.

In case this helps for something, in Wakelock Detector (if that app collects stats differently that BBS, I don't know that :p), the wakelock is also detected, also under "Phone", along with RILJ, GsmConnection, AlarmManager, CallerInfoCche, PhoneApp, etc, and its count is very low, usually it's x2, x1, and even, sometimes x0, unlike RILJ which is always in several hundreds, or some thousands.

Thanks
[Xposed Framework Modules] cryptyk:
-removed-
[Xposed Framework Modules] J_awn:
I've been using Unbounce for a few weeks now, switching from ROM to ROM trying to find the best combination for functionality as well as sustainability in terms of battery. On the DH GPE ROM, I'm getting a little over 1.5x the usage per charge than on CM, both running Unbounce. Definitely worth a latte when I get my Pay sorted out.
[Xposed Framework Modules] cryptyk:
That's awesome. Sounds like it's working well for you. Thanks for stopping by and saying so. Sometimes it seems like most people that post have problems with the app. Good to hear it's actually working for someone now and again, too!

Thanks!

Ryan
[Xposed Framework Modules] HDFLucky:
[MENTION=526666]cryptyk[/MENTION]: Nice job with the update and video demo. If people don't "get it" after that, they never will. :p
[Xposed Framework Modules] tapa_t:
Thank you, devs for the latest update to fix alarm on 4.1.2 roms. I did not expect that to happen so soon.

I am still bit confused, though. In the "ALARM" tab, I don't see anything listed under "Unbounced". All alarms are under either "Safe to unbounce", "Unknown", or "Unsafe to unbounce", which require the pro version to unbounce.

So, ALARM_WAKEUP_LOCATOR and ALARM_WAKE_ACTIVITY_DETECTION still can't be controled in the free version? Although, I didn't find these two anywhere among the not-unbounced alarms either.
[Xposed Framework Modules] Ankit Tulsian:
I unbounced rilj and I don't see any negative result on my battery nor on my network connectivity. I will report once I am done with full cycle.
[Xposed Framework Modules] Matze060906:
Hello guys,

I'm running this module since a few weeks and it works great. Now I have a question: Is it save to unbounce this wakelock? It drains my battery very much.

Sorry, if this is a stupid question and if this question was answered in the past. I'm new to this thread and it have so much sites to read. Btw: Sorry if my english isn't so good as yours...
[Xposed Framework Modules] marbulas:
I already enabled Unbounce but Unbounce says I didn't. What'd I do?
[Xposed Framework Modules] eongab:
did you reboot your device?
[Xposed Framework Modules] marbulas:
Of cource :P

And I found Unbounce doesn't request su permission itself.

I'm using SuperSU 2.14 on Android 4.4.2.
[Xposed Framework Modules] cornelito:
Kernel Wakelocks

Hi.

Can someone please help me figure out why am i getting such a huge battery drain over night with Airplane Mode on ?

Majority of wakelocks is down to Kernel Wakelocks - please see attached Log Dump from BBS.

Thanks in advance !
[Xposed Framework Modules] wilkster:
Do you have any weather or battery monitor widgets running? You can try removing those. Also, in the future include process stats in the BBS dump file (enable it in settings).
[Xposed Framework Modules] furboom1240:
Checking in

I let my phone go to sleep at 11 PM (courtesy of Timed Toggles-Auto Airplane) and my phone was at 72%. I wake up at 6:10 AM the next morning and my phone had dropped to 31%.

I had Unbounce installed and claimed it was working.

I put Unbounce in Go Power Master's safe list and ES Task Manager's ignore list.

My location services are running at full blast and won't stop unless I want to cause my phone to randomly reboot (I mentioned this earlier about AppOps).

Unbounce has free rein, but I have yet to see the benefits I saw in Jelly Bean 4.3, as they're very much gone.

No matter what I do, I kill battery hogs and more come to take their place. Except those that do are critical system apps.

What to do, what to do?