yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] DB126:
Setting Location to "Device Only"

Credit/props to magnamentis for calling out this solution. While you probably won't acheive <1% per hour drain with this fix only it does tame many of the wakelocks/behaviors that seem to whack battery life. I see a 50% savings while the phone is idle which is 80% of the time on many days. Quick and easy fix that can be applied to most/all devices - even without root. Thanks again for sharing.
[Xposed Framework Modules] shinra00:
Hi so i searched a bit online and the input I've got is that this wakelock is related to the fitness stuff from google.

I would really appreciate the input from the experts that exist in this thread. (the Google doc hasn't any input regarding this one)

wake:com.google.android.gms/.auth.be.proximity.authorization.userpresence.UserPresenceService

This is killing my battery so hard ?

One question related with wld. what's the difference between cpu wakelock and kernel wakelock? Should i mind the second or can i simply ignore it?

Thank you in advance
[Xposed Framework Modules] MBurns2:
yestaerday i had it, today no problems. Look at here http://xdaforums.com/galaxy-s3/help/wakelock-count-battery-drain-google-t2882894
[Xposed Framework Modules] shinra00:
thanks :)
[Xposed Framework Modules] magnamentis:
no

if aquired is 0 which is not perfect for other reasons the app did not work for nothing but a bit too much which is

certainly good for that specific wakelock but can cause other wakelocks to chime in with force.

however we were at another wakelock and the more you block the better as long as functionalitiy is not crippled and

as long as there are not other wakelocks taking it's place which happens with google play service quite often.

but with your assumtion, if i don't have total mental blockage, aquired 0 is closer to the goal of this app than blocked 0, frankly speaking ;)
[Xposed Framework Modules] 1ceb0x:
use the link from my sig...i posted a tutorial how to get rid of this :) quick and easy
[Xposed Framework Modules] Mistertac:
MyAndroidTools app and 1ceb0x's method kills that for you.

Just be careful in that app, if you disable the wrong things it can lead to other nasty Wakelocks popping up.
[Xposed Framework Modules] magnamentis:
there is a logic and makes totally sense, if you go a few pages back you'll see that i already then mentioned that there are other means to tackle this kind of interactive behaviour at its root (the cause) go back a few pages and do what is written and see whether it will reduce this problem to an acceptable level which as we hopefully agree is not ZERO.

make the device perform certain tasks with your usage in mind so that it does not come up with alarms and wakelocks around the clock, those which you really need perhaps a few minutes or hours per day. keywords are: profiles, tasker, settings, greenify. only with greenify alone you can avoid certain apps to do anything while the display is off which for most user is still tha vast majority of time etc. etc. go and have a lock, does not make much sense if i'd clog the thread with too many redundant contributions.

EDIT: thanks for naming other devices. to be clear each of us can always only speak for the devices we know ( own ) so if i say it happens only on my samsung devices this does not mean it cannot happen on devices i don't own or on roms i don't use. i just doupt that it's a simple rom issue because i use the same rom + 99% of the config on several devices and still on some the WL does and on others doesn't show. which can be a coincidence, albeit a persistent one, because look for this one each day on my 1+1 and then end up finding it on my note2 after trying to find it on the N5 and 1+1 without success. [ which might be success after all hehe.. ;) ;) ;) ;) ]
[Xposed Framework Modules] DB126:
Yes - and I responded to that post indicating that I experimented (using the tools you mentioned plus others) at some length and came to the conclusion that the ongoing effort to track the impact of every change exceeded the benefit in my situation and on my devices. However, for those interested in taking a less intense approach I would recommend staying away from Amplifying *net_scheduler* until other options have been explored/exhausted.

I also acknowledged your work setting location to "Device Only" which has yielded tangible benefits and can be easily implemented by virtually anyone without having to mess with rooting, Xposed, Amplify, etc. That combined with the non-root version of Greenify may be all that many individuals need to tame excessive battery consumption.

Finally, I want to thank (again) the developers of Xposed, Amplify, Greenify, GSam, etc along with the many contributers to this forum for their hard work and dedication. Only through such sharing is progress achieved. Don't forget to buy the various devs a cup of coffee through a donation or upgrading to Pro versions - they truly deserve it!
[Xposed Framework Modules] MBurns2:
thanks mate, you re so kind.

Now i have: acquired 198 blocked 2000.

In wakelock detector and bbs i have no wakelock even in 3g, my phone seems perfect. If amplify was working too much, i will certainly see it on bbs process right ? if i go to bbs process amplify is very low..

Today i see a bit more battery drain on screen on, maybe because i flashed xposed ? yesterday my battery was better (yesterday i didn't amplified rilj).

Thanks a lot guys
[Xposed Framework Modules] Majesty00:
Hello,

I've been using this app for a while now and I went from 18h of battery to more than 48h. Great app!

Now, I was wondering what was the future of Amplify with Android 5.0? The author of XPosed said it's possible the app won't be updated to work with Lollipop (or it could take months...).

Could Amplify be released as a standalone app?

Thanks!
[Xposed Framework Modules] cryptyk:
Amplify requires Xposed right now. Any challenges Xposed has with Lollipop will be the same challenges Amplify has.

I'm guessing the fate of the two will be tied together, but could be wrong. We'll see in the future.

Thanks,

Ryan
[Xposed Framework Modules] Weetbix:
Long overdue thanks :good:

Has anybody been able to do this with the free version of 3c? I've just installed it to have a go, and it is all good until I get to the services tab. Once I get there I can see the services listed, but I can't do anything with them. It looks like a static list that nothing can be tapped on.
[Xposed Framework Modules] DB126:
Try Disable Service app. Worked for me (obviously need root).

https://play.google.com/store/apps/details?id=cn.wq.disableservice

I disabled the following two services (as recommended by others):

- ConfigFetchService (com.google.android.gms.config.ConfigFetchService)

- UserPresenceService (com.google.android.gms.auth.be.proximity.authorization.userpresence.UserPresenceService)

Don't forget to send author a donation if it does the job :)
[Xposed Framework Modules] Solace50:
also SYNC_ALARM is related to procing account based syncs, regardless of those apps intervals they will not sync automatically ex. EMAILS (not gmail) will fail to sync while this is locked. if you have a static value between this and all your apps i would see no negative effect, but i believe this is redundant at best given not all apps sync at the same time. this may also just affect EMAILS and nothing else, i have disabled every other google related sync so maybe someone else can test.

if you look under accounts and select EMAIL it will show the last sync time, in my test it had 5 minute intervals and was out of date by an hour. after enabling SYNC_ALARM under alarms the functionality restored. if gmail syncs work regardless then thats great along with other 3rd party apps, if not then someone should go test to ensure others are not affected.
[Xposed Framework Modules] cryptyk:
Is there a reason you guys don't use Amplify to block the services? It's not that I'm jealous or anything. Everyone should be using the best tool for the job. I'm just wondering if I missed the mark on service blocking in Amplify and that's causing you to need a separate app for that.

I'd like to make Amplify better so you don't need a bunch of different modules!

Thanks,

Ryan
[Xposed Framework Modules] Solace50:
works fine, the only thing 3c cant do is disable its own services as i tried that lol. no need for it to be doing anything in the background as once recievers are disabled they stay disabled.

just make sure you click right on the little box its kind of finicky. disable services is a much simpler UI and does the same job and works fine as well.

---------- Post added 14th November 2014 at 12:01 AM ---------- Previous post was 13th November 2014 at 11:56 PM ----------

how does amplify block the service is what people should question. also the UI layout is not exactly ideal currently and i would honestly just choose something like disable services for that. as for how its blocked, if im not wrong disable services/3c straight disable the service at the root not creating any future overhead where as amplify would block it on requests correct? i mean if its the same method i as the other tools then its just more or less a UI thing and they list all available services for each APP rather then whats previously been called. if amplify just mimicks disable services/3c for recievers/services/other then i see no reason to have multiple apps doing the same job.

tl:dr UI needs to be more intuitive with listings/names/apps
[Xposed Framework Modules] DB126:
At present I have Amplify disabled as I wasn't getting a significant benefit from disabling wakelocks/alarms. Also, with Lollipop on the horizon I am trying to ween myself off Xposed modules until the devs indicate support will be continued and/or just remain on Dalvik. Easier said than done as there are a handful of Xposed apps I view to be essential with no viable alternatives.

In reference to previous post Disable Services does not require Xposed.
[Xposed Framework Modules] Weetbix:
I'm comfortable with the knowledge that I do have a benefit with Amplify installed ... and now I've reached that comfort level I am slowly starting to go through some of the things that have been referenced multiple times in this thread as being useful - to see if I can improve things even more.

I tend to dislike having multiple apps/modules installed that overlap in their functionality. Since Amplify works for me I'm all for stuff to be improved ... with "improved" being defined by those more knowledgable than myself :)
[Xposed Framework Modules] Solace50:
basically incorporate everything 3c tool box has under permissions and you have one universal app for making your phone your *****. all the other tweaking swag seems like overkill but i guess you could do it in the long run if you wish. other then whats said earlier the only other thing i found useful and intresting under 3c toolbox was the ability to run the trim task which made me wonder if i could configure it to run with tasker and block the wakelock. this way i could have it run while on the charger rather then off the charger as i read it is a resourceful task and will only run when idle + 20% battery.
[Xposed Framework Modules] 1ceb0x:
The main reason i don't use the service part in Amplify is because, in my tests, a service disabled will provoke other wakelocks/alarms.

In order to be clear of that, i have to disable the receivers and providers as well.

For example, if i only disable the Config Fetch Service (without the receivers and providers), GPS will wakelock my device like crazy. In order to stop it from doing that i also have to disable receivers and providers... As we don't have those in Amplify, i use a dedicated app that can disable everything.

If you can implement those as well, then, we are golden.

PS - i myself use MyAndroidTools (made by the guy who coded Disable Services app) because of its small memory foot print compared with 3C.
[Xposed Framework Modules] Weetbix:
Not bad. The thread is less than 3 months old - and already it's on page 356 with 3552 posts before this one.

Congrats Ryan :good: :) :good:
[Xposed Framework Modules] Solace50:
im going to have to request you do something else for the UI displaying names, having to wait for the names to scroll around and not being manually able to view the (entire) name is honestly a gigantic waste of time especially when trying to type out one of the names. that or a copy service/name function would be nice. i litteraly have to wait 5 seconds to view the other half of the service name because even clicking on it doesnt have a full display name if its too long for the UI.
[Xposed Framework Modules] 1ceb0x:
That's a good idea... like a dialog box where it can display the full name and a copy button so that we can be able to copy it without writing it down manually.

Also, it will be awesome if the UI will go back to how the timer was displayed, right now, frankly, i don't understand the overview:

some wakelocks are having timer like "xx" some timers are normal "xx:yy"..
[Xposed Framework Modules] cryptyk:
All good feedback. Thank you!

The timers are DD:HH:MM:SS, but only display the amounts needed.

For example, 07 is 7 seconds. 40:05 is 40 minutes, 5 seconds.

I got ya though. The old timers were more helpful, the names aren't "fit" well, and the copy paste would be awesome.
[Xposed Framework Modules] Solace50:
are unbounced wake/alarms/services saved into an xml file or something somewhere where i can go either modify the values/obtain names/delete entries.
[Xposed Framework Modules] vaibhav011286:
unbounce GCM_LIB to 240

can I unbounce GCM_LIB to 240??

Will it make any problems in my sync or other apps??
[Xposed Framework Modules] shinra00:
Regarding the use of MyAndroidTools or 3c instead of Amplify to block the services wel.. even though i read every single post made here, and i've been following the thread every day, i don't truly understand very well what is happening when i unbouce something.

I 'm still struggling with the analysis of WLD + BBS + Amplify. So much that at current moment i have only the default values of Amplify and a terrible battery consumption at idle (5%/hour). Even after the many many posts of [MENTION=2688060]1ceb0x[/MENTION], [MENTION=5500746]Mistertac[/MENTION], [MENTION=391802]solace[/MENTION] and [MENTION=5372360]magnamentis[/MENTION] explaining time after time the "how to" and what is the meaning of every wakelock and alarm, you guys deserve a truly "Thank You!" because i feel that more than 80% of the followers of the thread depend on your comments, analysis and experiments in order to achieve results with the app.

So back to the why not using the Amplify to block the services.. well because [MENTION=2688060]1ceb0x[/MENTION] hasn't said so :silly:
[Xposed Framework Modules] 1ceb0x:
GCM aka Google cloud messaging is the link between you and your apps notifications.

Amplifying its library might make your push notifications to not be received anymore.

And i don't think it has a big impact on your phone either (i rarely see it wakelocking myself). In case you don't provide how many times it wake up your phone in how many hours/days of use, we can only provide you our thoughts about it.

My thought: don't. unless you want to experiment with it (clearly you don't since you asked about it here).
[Xposed Framework Modules] MBurns2:
is there a way for see if amplify is draining my battery?

i would see it on bbs process if he is working too much (maybe because I unbounced too much things)? ty
[Xposed Framework Modules] magnamentis:
my thoughts on this

just want to throw in another thought on the above topic:

while limiting alarms and wakelocks can under circumstances reduce the functionality of certain apps and services, these 2 things can hardly really mess up the device, so they are relatively safe means to optimize battery life and no danger to those who like to to click around a bit or for the many for who trial and error is a common way to tackle tasks :)

in my opinion this does not apply to an app like "3C" or "My Android Tools" albeit if there is a reset all button, i would consider carefully about which kind of user is expected to use an app. a user who downloads "My Android Tools" is far from being an average user. they are in the hundreds more than in the thousands, while this app "Amplify" is probably used by thousands of users and the repeatingly same questions showing in this tread imply that it's not certain that the benefit for a few will pay off ( not money ) for the hassle and the trouble which would IMO be imminent, last but not least for the dev if one cares, and we all know that our dev cares a lot :).

i hope i was able to explain well. the well intent purpose of this post is basically do keep something great simple and easy and perfect for user level while certain features, no matter how good they might be, multiply the amount of trouble while giving a small benifit to few which can be satisfied easily by other means. so i'm just thinking ahead, usually unheard, so no offense taken if others don't share the thought, but from experience i can say. you'll see haha....
[Xposed Framework Modules] Mistertac:
There's no doubt using apps like MyAndroidTools is risky if you are not 110% sure about what you're doing.

In my opinion, who ever decides to use that app along with this module should most certainly make a Nandroid backup first. If you do not have a custom recovery and cannot do that, be extra careful. You can totally screw up Play Services, and in turn bork quite a few things.

I've only gotten comfortable using these tools myself through much trial and error and many restores lol so just keep that in mind.

Well said [MENTION=5372360]magnamentis[/MENTION]
[Xposed Framework Modules] vitoski:
Would you mind please share the screenshots again? I did not download them on time and now cannot get back to them and I am playing around with Location (device only). For some reason it eats more battery (by Google play services) than when I was on location off profile with Tasker.

What I would like to look at again were your tasker and amplify screens.

Thanks!

Sent from my XT1052
[Xposed Framework Modules] kmarc33:
Just a thought: perhaps it's because what I'm used to but I like how BBS does it, long press on something and a pop up box shows up with the full name (wrapped around if needed) and all of the info on the thing. A regular tap could bring you in to something to update/change/read about it but having something scrolling because it's a ba-jillion characters long is sometimes difficult, popping it up with the current stats and status (Amplified or not, seconds set) would be nice (IMO).
[Xposed Framework Modules] dynospectrum:
Unbouncing Lux will render Lux' compatibility checker null. The compatability checker is what allows Lux to go to sleep in the apps you've selected or to do so. Don't unbounce it if you want it working properly ;]

"Android APK installer is one of such apps which fails to work properly if there's a screen filter active on your phone."
[Xposed Framework Modules] magnamentis:
link reinstated

the link has as well be re-instaded in the old post as well as been made available below:

https://www.dropbox.com/sh/w8swdc373sakl1s/AAC7TAjOSK5PQaLuY4idIiKFa?dl=0

may i ask you out of curiosity why you don't just download the whole set and keep it though available for as long as you need it. just wondering as nothing came up to my mind as to what could be a reason for this ?
[Xposed Framework Modules] teemo:
The key to understanding and to get good performance, is: Patience!

Patience and small steps. Reading all the posts here, you will find that the "knowing" people here use these skills.

Change one parameter - watch what happens. Change next parameter - watch what happens.

Its like one big organic ecosystem. Everythin depend on something else. Remove one thing and three things will break.... and you won't know why unless you take the time required to test.

Most of us want results fast, me included. It just don't happen. Best place to start the adventure, is a clean install of the stuff you need. Make sure everything is working well. Then read the many messages here, test a few things from the spreadsheed and notice what is working. Fortunately, I don't need the trick to put location to "Device" before I disable Location. Once I disable Location, my wakelocks go away. For some reason it doesn't work that simple for many users. So, notice what your device is doing.

I believe the easy solution is already in OP: Disable location and you are good. Want the last 0.2%, then get ready for some hard work :)
[Xposed Framework Modules] vitoski:
I quickly looked yesterday in the morning at your screenshots while going to work. Later I was too busy and did not have a time to download it[emoji3]

Thx for sharing again.

Sent from my XT1052
[Xposed Framework Modules] DB126:
Simple solution

Sooooo true! Having a way to quickly/efficiently toggle location settings has been the best solution for me. QuickSetting tiles in GravityBox provide that capability (what I use) but there are many simpler location toggles/shortcuts/widgets available in the marketplace. Amplify in conjunction with other tools mentioned these forums offer the opportunity for further refinement if you prefer (or need) to keep location enabled 7x24. But it takes time and careful analysis of each change to achieve the desired result.
[Xposed Framework Modules] vitoski:
Guys and gals this alarm from Google Play Services ( com.google.android.intent.GCM_RECONNECT) appears when you turn off and then on 'mobile data' either through Android settings or toggle from notification area.

I have Google sync disabled completely so have no clue if sync has any impact on this alarm.

So if you do not want to see it at all don't disable mobile data.

Sent from my XT1052
[Xposed Framework Modules] magnamentis:
wisely said more than fully agree to the first 90% of your post, but not really to the last sentence. this is not a solution, it's a workaround only for those who don't need and want location on at all times like myself. but tha later is personal preference though, for each user his indivudual setup :) so far it's a good hint for those who don't need/want location services at all times

but really i must say that if i wanna know where my wife is i need her to have location history on hahaha... just kidding

enjoy further

---------- Post added at 05:43 PM ---------- Previous post was at 05:36 PM ----------

mobile data disables automatically if you come into range of a wifi network you're subscribed to. so as certainly as we could switch of wifi to avoid that, the battery drain through the use of mobile data is by very far higher than that of the wakelock we're facing here. so i think there is little we can do here.

we have to keep in mind that all these alarms and wakelocks usually have a very good purpose and the word wakelock and the word alarm should not become some kind of "red fabric" like for the "torros" in andalucia. btw this wakelock is far below the number and time i would consider it worth to limit or even investigate further. this might be different for others of course, i only speak for my 7 devices and their specific config.
[Xposed Framework Modules] vitoski:
Yes I am not saying it's good or bad but just wanted to let you know under which circumstances it appears.

I have Tasker profile that turns off my mobile data when screen goes off and on when it lights up. This profile was to limit data exchange by apps while phone sleeps.

So to say it is not bad but for sure if you use similar profiles you will see those alarms in BBS.

Sent from my XT1052
[Xposed Framework Modules] Osama Zabin:
Anyone know what's ShoeboxComputing wakelock? It wast keeping my phone awake for nearly 20 minutes in 20 hours, amplified without any problem (600 sec)

Any input about this wakelock is appreciated.

HTC one M7

ARHD 82.0 (4.4.3)

EX 18.0 kernel