yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] drup88:
Thanks for your reply mate. However my issue is that i cannot find it in Amplify. Infact alot of things i cannot find in Amplify. But well take this one as an example.

If i go into amplify>Alarms/Services/Wakelocks i cannot find anything related to "smsr.com.cw.UpdateService" or smsr.com.cw.Countdown Widget.

I can clearly see what the problem is. What i want to do is stop it/limit it. I understand that a coundown would need to check every hour but for my situation im happy for it to check just once a day.

[MENTION=526666]cryptyk[/MENTION] - Is there ever a situation where Amplify would not list a wakelock/alarm/service that Battery stats/Wakelock detector would show?
[Xposed Framework Modules] MBurns2:
Guys today I had rilj wakelock, in the past days i didn't change my configuration but today this one was crazy, why?

thanks to this awesome app i solved my problem.. big donation for an awesome dev
[Xposed Framework Modules] khairulez:
Some information about RILJ
[Xposed Framework Modules] magnamentis:
yes and

right answer !

to the person with the problem (thus not correcting khairulez) this workaround is only solving the symptom and not the cause, nothing wrong with that but i posted and endless number of times already that people with location service related battery hogs should learn how to set location settings to "device only" when not needed and only switch to high accuracy when needed. ( battery saving and off will not do the job properly ) this is counter-intuitive but i watch this behaviour for almost a year on 7 devices and it's consistent.

this can be achieve with tasker and the appropriate plugin.

be aware that setting location settings to off might be another possibility, but frankly speaking, it's an overshoot because not necessary to solve the problem and further some apps for some reason respect the inability to acquirer location while on device only but still think they have to come back and try over and over again while location settings are set to off. i cannot explain that, i think it's something some devs simply overlooked or eventually the device only setting is more enforced than off or eventually off looks similar than no signal and therefore can be interpreted as just no signal and thus worth a retry. no clue really i'm just brainstorming possibilities as to why this can be and if somebody know better and can explain this behaviour i'll appreciate it.
[Xposed Framework Modules] MBurns2:
you re the man. i had location to off, i turned it on then i put only gps then off again. now no rilj even without amplify. Thanks bro i hope to really have solved my issue
[Xposed Framework Modules] teemo:
Cool.

Now, if you turn on location again. Then enable high accuracy. And finally turn off location.

What will then happen? Back to high drain or does it stay low?

Like magnamentis suggest, it would be good to get some facts and brainstorm what is going on.
[Xposed Framework Modules] magnamentis:
glad to hear

good to hear :)

unfortunately you are one of only few people who really took the advice seriously. 99% simply don't try it out. however there is more to it than that. it took me many months to develop and verify a set of means which solves this kind of battery drain reliably on all my devices. the goal was to use a set of configs which, when setup accordingly, would make each device i setup consume not more than 2-6 mAh in idle mode which sums up somewhere between 1-2% in 8-11 hours idle. the ingredients to achieve that goal reliably are: tasker, tasker plugins, greenify ( moderately used for about 6 or 7 apps ) profiles ( system > settings > profiles in cm for example ) WLD-App or similar as well as "Amplify" of course, while i have to admit that when amplify was still nlpunbounce it did 90% of the job because most real repeating battery hogs have been network location related.

any other attempt to measure battery life has proven to be much prone to changing conditions. during daytime there are more or less calls, more or less SOT, other cell towers, more or less participants in the network etc. etc. and each day provides different results why i'm using night times with consistent patterns to test each night. by the way if we start our day with 98% battery instead of 93 or even less, the difference of 5-10% means at least half an hour more SOT and up to 20 hours of increased standby which after all makes the difference whether we can make it 1 or 2 days on one charge with modereat use. of course not applicable to those who are off charger for most of the day and use a device more than 3-4 hours on battery. however i think most people have an office or a charger at home and in vehicles so that the off charger time for many users is not that long. on an average day i'm basically never more than 3-5 hours of charger during daytime and therefore can use my devcies at full power when actively used.
[Xposed Framework Modules] vitoski:
Would you mind sharing your settings to get 1-2% batter drain during 8 hours? Was it something special apart from setting up location as you advised?

Currently I use Tasker to switch off location when screen goes off and set it to 'Battery Saving' when it comes on. But I am happy to test 'Device only' with high accuracy in case of navigation.

Thx.

Sent from my XT1052
[Xposed Framework Modules] cryptyk:
There was a bug in early version that caused some wakelocks to be hidden. It shouldn't be a problem anymore.

I'll install the countdown app and see if I can reproduce.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
I installed the countdown widget, and the wakelock appears for me. Check the attached screenshot.

Thanks,

Ryan
[Xposed Framework Modules] Amr Nasser:
Important

I Don't Really Know How To Use It !

I Hope There Is Tutorial Or Something !

How To Turn Off Wakelock ?!
[Xposed Framework Modules] MIKEMON:
for a start the default application settings

Read the first page and a table that helps ..
[Xposed Framework Modules] MBurns2:
guys maybe i find the source of my problem related to rilj.

I had 4g as preferred line, the problem is that i haven't any 4g plan. So the phone was trying to take 4g line without any success and this was causing me the wakelock.

I didn't notice this at my home because in my city we haven't any 4g cells, i notice it only today because i was in a city with 4g cells.

Is it possible ? thanks to all
[Xposed Framework Modules] 97_3:
So anyone know anything about this com.android.deskclock.on_quarter_hour?
[Xposed Framework Modules] vitoski:
I have the same but could not find what causes this wakelock. Trying to limit this with Amplify (600sec) gave me nothing... like no single wakelock was blocked.

EDIT:

I have 111 from today's morning when I unplugged the device from charger.
[Xposed Framework Modules] 97_3:
Can't attach an image right now, but I got +3k alarms fired off.
[Xposed Framework Modules] cornelito:
Would you mind to create tutorial on how to save the battery on SGN4 eg. list of the app you are Greenifying, what Tasker Plugins are you using, share your Tasker profiles / projects, your full Amplify setup etc?

Can you please remind me how to set Location to "Device Only" ?

Thx
[Xposed Framework Modules] Mistertac:
I have this Alarm as well on Liquid Smooth. Mine is no where near what you're having however.

What device and ROM are you running?
[Xposed Framework Modules] 97_3:
HTC One X, Slimkat 7.6. Haven't rebooted for a week, might be something fishy with those stats.

Sent from my One X
[Xposed Framework Modules] magnamentis:
read below, just in your case i have no SGS4 but a N7100 so you will always play with settings to adapt to your device and the rom in use has a certain impact as to what degree my settings will be applicalbe, while, of course, again others are valid cross-devices and cross-roms.

i will have to think about how to do it when i have time, reason is, the more i think about it the bigger that becomes :) it's quite a lot of things. since it's become a routine for me i only got aware of this when i started a reply and did not come to an end :) however right now i'm considering a bunch of linked screenshots but not sure if that will do without a lot of explanations. so gimme time, will not forget it ( calendar entry made)
[Xposed Framework Modules] DennyD123:
Hey guys,

after I updated Amplify from 1.5.2 to 2.0.6 it doesn't show anyone Wakeclock or anything else.

I reinstalled Amplify, make a reboot and reactived it in Xposed but nothing works.

Anyone knows the problem? Thanks :)
[Xposed Framework Modules] cryptyk:
Please try pressing the RESET button on the home screen.
[Xposed Framework Modules] DennyD123:
Thank you i have reset my settings in the settings^^
[Xposed Framework Modules] cryptyk:
Make sure you do the reset on the main screen. That's the one that will fix it. Reset in settings might help, but it's really the stats that need to be reset.
[Xposed Framework Modules] tangcla:
Does anyone know about TimaService or ProximitySensor - whether that's safe?
[Xposed Framework Modules] magnamentis:
ok here we go :)

[MENTION=1606575]vitoski[/MENTION] _ [MENTION=5004275]cornelito[/MENTION] and to who ever it may concern:

i decided to go with the 34 screen shots linked below, because many of the settings are slightly different from device to device, from config to config, so the only thing which makes

sense to provide is: what, how and with which tools to tweak to get there. this seems to be the most efficient way to provide max info at a minimum post length.

If you combine the info in the following link with the hints available in the screenshots you will be able to set things up accordingly:

Link 1: http://xdaforums.com/showpost.php?p=56434550&postcount=3158 ( how to narrow down amplify settings, each device and rom and kernel combo asks for different time limits) ( this you have to read with patience because albeit it's easy, it reads a bit overwhelming, but i thought it makes more bullet proof to repeat each step than just hinting, the small amount of follow-up questions hint to that being the right choice :)

Link 2: https://docs.google.com/spreadsheets...gid=2072742181 ( wellknown spreadsheet from the opp to avoid unnecessary trouble, you'll see i limited much less than possible

Link 3: https://www.dropbox.com/sh/w8swdc373sakl1s/AAC7TAjOSK5PQaLuY4idIiKFa?dl=0 ( dropbox folder with subfolders named by topic so to better understand the content )

the images are named as well where necessary, the 3 WLD images below are from 3 different divices with different battery capacities. so 3% on a nexus 5 2300mAh is not worse than 2% on a N7100 3100 mAh etc. the images should be some kind of a teaser so to keep your interest high haha......

only stat missing is the stat from battery monitor widget which shows very nicely the %h and the mA usage each morning, just that i never made a screenshot so i don't have it yet. however i made s screenshot from current screen to illustrate which app and how it looks.
[Xposed Framework Modules] 1ceb0x:
unlikely... sadly you didn't find any gold mine. the RILJ wakelock is triggered everytime you use cellular data. it does not matter whether it is 3g or 4g, or what settings you have with what you get on your phone. I doubt that if you had 4g setup but you only got 3g, that that's the problem. the phone only took what he knows he is accepted to by your carrier - 3g.

i have this wakelock everytime and it is bigger when you use cellular data and sometimes smaller when you use wifi.

no fix has been found until now and trust me i have researched a lot. the only way to deal with this for now is to use amplify.
[Xposed Framework Modules] amnher:
Is there a battery drain wakelock? I am already using amplify
[Xposed Framework Modules] 1ceb0x:
yes there is.. it is the first one on your list.

wake:com.google.android.gms - please click on it and give us the full name.. I bet it is either Config Fetch service or the User Presence wakelock.
[Xposed Framework Modules] amnher:
wake:com.google.android.gms/.auth.be.proximity.authorization.userpresence.UserPresenceService

So what to do??
[Xposed Framework Modules] 1ceb0x:
2 things you can do:

Amplify it (the process will still run once in a while, depending on your timer)

Use my tutorial from my signature to disable a few services/providers/receivers from Google Play Service and your problem will be gone completely.

Your choice!
[Xposed Framework Modules] amnher:
I'll try thanks because this drain is unbearable. I am not even using Location services but this google services kills my battery
[Xposed Framework Modules] dimm0k:
if you don't mind, could you please leave the pics up on your dropbox? otherwise I'll have to grab them so I can build some Tasker tasks from what you have... pretty nifty I must say!
[Xposed Framework Modules] eazzy28:
What services can I amplify? Well that won't lead to trouble. I only have one amplified. Help would be appreciated
[Xposed Framework Modules] MBurns2:
thanks mate.. in the past I had this wakelock a lot, thanks to amplify this is the first time that I really solved my problem.

one question : when i allow a wakelock every xxx sec, can i decide for how much time he can stay activated? (i allow rilj every 600 sec)

This app is the only one really able to block the hardest wakelocks.

Thanks dev
[Xposed Framework Modules] teemo:
It's the Clock.

/**

* Intent to be used for checking if a world clock's date has changed. Must be every fifteen

* minutes because not all time zones are hour-locked.

**/

public static final String ACTION_ON_QUARTER_HOUR = "com.android.deskclock.ON_QUARTER_HOUR";
[Xposed Framework Modules] tj_cute:
hello there. it's now okay. I just clear the cache using recovery and it works.

oh by the way, I don't need a refund. it pays enough for your effort. keep it up! :good:
[Xposed Framework Modules] Solace50:
i would assume turning off sync to network would solve this, i did see this one pop up randomly the odd time but no more.

currently im down to only two AndroidOS alarms procing aside googles wakes and @ .2% an hour over 4 hours off a fresh charge. though i dont consider it to be 100% accurate as the battery readings could be off. this is with locations disabled and using tasker to enable when needed.

the last two androidos alarms are twilight update service and idle maintence service of which i believe the first one is related to automated brightness adjustments based off time of day in regards to the CABL service, probably can be restricted if autobrightness is not utilized.

as for the other i have read its related to fstrim for the sd cards, of which i would not fiddle with as i recall trim is related to longevity of sd cards and fixes the degradation of performance over time. according to documentation this does not run unless the phone has 20%+ battery and has been fully idle for 1+ hours anyways. this is probably resource intensive but rarely runs, i am curious though as if you can manage your own schedule for this specific wake as its a maintence service for ssds as windows has its defragger/task manager.

as for google wakelocks those are all 100% disabled including the "unsafe ones" as i use alternatives that allow better control over the device and alternate chat software, alarms though are left untouched due to avast depends on google play services and its finicky as to what does what in regards to google play services. only so much i can figure out by myself, regardless the phones state is ideal for the time being and can be left alone until furthur research is done on googles alarms. 90% of my software does not have any intruvise alarms or wakelocks and the few that have them are already restricted to a near infinite value without issue.

if possible, requesting access to the gdocs xml file to append information along with additional notes to existing entries that are important.
[Xposed Framework Modules] 1ceb0x:
Solace PM me with your gmail account and i will add you to the spreadsheet.
[Xposed Framework Modules] shinra00:
[MENTION=5372360]magnamentis[/MENTION] thank you for the tutorial
[Xposed Framework Modules] Mistertac:
The more people we can have helping on this the better right my friend?

I'm limited to just my device and my apps, which I don't run too many and I don't run widgets either.

Next week I'll be getting a Nevus 6 hopefully but I've already thrown Amplify on my girlfriends One Max so I should be able to get some more info off that one to add.
[Xposed Framework Modules] 1ceb0x:
For sure, mate. The only reason that the spreadsheet was 'closed' is because we needed people with ability, patience and time to experience, search. Solace seems he's one that knows what he is doing and he requested access so... i am waiting for his PM :).
[Xposed Framework Modules] Mistertac:
[MENTION=5372360]magnamentis[/MENTION]

Have you found any more info on the NetScheduler Wakelock?

Since I've been on Liquid Smooth ( AOSP ) I've had this pop up like crazy, where as I didn't have it on stock LG G3 ROM .

I've limited it to 600 and no ill effects but doesn't seem to be much info on this one.... There's obviously a few on the Sheet we've have hard times finding more info on other than... Seems safe! Lol
[Xposed Framework Modules] MBurns2:
i set rilj to 600, no battery drain or heating up.
[Xposed Framework Modules] vitoski:
Have you encountered any drawbacks after that? Like higher battery usage with screen on?

Sent from my XT1052
[Xposed Framework Modules] xk0niR:
I myself limted it to 345600 which is 3 days.

No problem, not any side effect

But is it good to unbounce something this high? I heard high unbouncing can cause battery drain?

Can someone explain why it should cause high drain?
[Xposed Framework Modules] Celestial Fury:
It's worth repeating that unless these wakelocks and alarms appear in BBS and actually cause battery drain, it's pointless limiting them and just degrades your phone's capability.

High numbers ? in Amplify don't matter if they are not high on BBS. By limiting only the ones that cause battery drain, Amplify has brought my battery drain to 0.09% per hour or less. In fact BBS shows it as 0.0% drain, tested several times. Do note that the battery tends to hold its charge better (and longer) when full.

I'm practically done with experimenting and limiting with Amplify. Just waiting to post what I've limited when the new version lets us copy paste them. ?
[Xposed Framework Modules] Mistertac:
Well long story short if something is Amplified too high and it is a necessary Wakelock or Alarm, in theory your phone could continue to call on that Wakelock/Alarm in order for the phone or app to function correctly... Resulting in even higher Alarms and Wakelocks.

If it is set low enough to where the Wakelock/Alarm can still function and complete it's task, in theory that's better than just cutting it off completely.

[MENTION=2688060]1ceb0x[/MENTION] and [MENTION=5372360]magnamentis[/MENTION] typically explain this better than me but hopefully you follow...

---------- Post added at 05:45 AM ---------- Previous post was at 05:42 AM ----------

Well said man.

Myself, I use BBS for my Alarms and Wakelock Detector for Wakelocks and that's been treating me well.

I look forward to seeing your list!
[Xposed Framework Modules] MBurns2:
no problems.. i will keep u informed
[Xposed Framework Modules] 1ceb0x:
Like a rule of thumb... unless you know exactly what it does, it should be better to just run small numbers and compare the number of wakelocks vs the time it keeps your device awake.
[Xposed Framework Modules] magnamentis:
a few thougts though

no explicit explanation found as well but to narrow things further down (perhaps) this is what i found out:

- i have amplify in use on currently 6 devices 5 of them identically setup with cm11+xposed same launcher, same apps etc.

- this wakelock appears only on on Samsung devices, which i think is a coicidence, while on 1+1 and nexus 5 the wakelock does not show at all

- only major difference between those devices, besides chipset etc of course, is the kernel. while i'm using default cm11 kernels on samsung devices due lack of custom kernels which meat my standards, i have custom kernels in use on the devices which don't have this wakelock.

- one of the things which come to my mind is that with custom kernels i set the wifi supplicant scan interval 75 seconds while the cm11 default is set to 15" as i can see in build.prop on the devices with original kernel.

so my idea ( more it is not at the moment ) is that this could be related.

I will check this out by setting the 15" in builld.prop on my samsung galaxy N7100 manually to 75" at this very moment and then will check tomorrow if anything has changed as far as the *net_scheduler* alarm is concerned. if you could to the same we can cross check and if we get the same ( hopefully positive ) result can considered this as solved ( answered )

so tomorrow, same place same time hahaha.... just kidding

EDIT: forgott to mention: mine is limited at 900" without visible negative impact, but i must mention that this device is not as frequently in use anymore since it's main purpose was taken from the OnePlus ONE. navigation, bluetooth gps, bluetooth music over headset, emails, content browsing and doc handling
[Xposed Framework Modules] 1ceb0x:
You might want to see this:

LG G2 running Liquid smooth, custom kernel, wifi supplicant of 200s
[Xposed Framework Modules] iamolu:
[MENTION=526666]cryptyk[/MENTION] I believe the random reboot issue was rom related. I went back to stock rom and have no issue with amplify
[Xposed Framework Modules] magnamentis:
tomorrow same time same place haha...

thanks for the input

that would speak against my theory then, however i'll check the difference anyways and post it, further i'd day that sooner or later we gonna find out :) capitulation is not a valid option, cheers :)

interestingly i have this only on samsung devices all on same rom, so it cannot simply be a rom issue, otherwise i would see it on the n5 and 1+1 as well.
[Xposed Framework Modules] MBurns2:
is this ok? or is it blocking too much?
[Xposed Framework Modules] magnamentis:
runtime is missing

nobody knows without you let us know your runtime and even then, what does not spoil your experience, (criple functions) is ok

if this is for approximately 24h i would ( personal choice ) let it go up to between 75 and 95, if its for 8h i would be fine with it and

if running time was smaller than that i would probably raise it in increments of 30" as long a no negative side effects are showing

further if unsure, go and check the battery usage (not time and numbers but mAh )
[Xposed Framework Modules] MBurns2:
i amplify rilj two hours ago..
[Xposed Framework Modules] magnamentis:
then raise it, mine is at 900" but you have to adapt to your needs. you can reduce this by setting location settings to device only and

by other means which you find a few pages back in on of my more detailed posts. if you try to reduce wakelocks on the source side

you have to respect the interaction of settings with each other, one alone will not do a perfect job. so if you set location to device only

you have to use tools to activate high accuracy when you need it automatically otherwise this would become heavy work and remember
[Xposed Framework Modules] DB126:
*net_scheduler* wakelock

This wakelock is also appears regularly on my Droid Mini running 4.4.2. Increases dramatically when I over Amplify nlpxxx wakelocks (>900 sec). If I squash *net_scheduler* then WiFi drain and/or total wake time begin to creep up. Ultimately opted to leave this one alone. As with any tweak YMMV.
[Xposed Framework Modules] MBurns2:
is my goal to reduce the difference between wakelock acquired and wakelock blocked?

For example: rilj wakelock acquired 0 wakelock blocked 240, for me it is not good because amplify is working for nothing.

Right? ty