yashsingh1/xdaforums huggingface dataset:
[Android General] DB126:
Enable watchdog service in BBS which will expand the scope options to include screen off/screen on.

Root cause of the eMMC failures has not been determined (or at least revealed by Samsung). More likely due to lower quality lots (cost savings choice), poor voltage control or localized heating. I personally doubt throttling the CPU will prolong eMMC life if visits to the upper ranges are infrequent. However, completing tasks quickly/efficiently often yields better battery endurance vs puttering along at lower speeds (Google 'race-to-idle'). Not sure if that applies to the 910F chipset.

Your device is experiencing a connectivity issue which appears to be WiFi related. There is an inordinate number of wakelocks and scanning activity that suggests difficulty attaining/maintaining a stable connection. A less than ideal mobile signal is a minor contributor given the magnitude of the issue.

There are few 'new' batteries for a 2014 vintage design. While the pack may have been a recent purchase the date of manufacture for the internal cells is likely back aways. External date codes often reflect assembly or are simply fabricated. Still, if authentic it should perform better than the original which likely had many full charge/discharge cycles.

While RR is a well regarded ROM customization for your device and kernel are what matter. In my neck of the woods, Andersen and Pella are highly regarded windows. However, if the rough opening, installation and weather sealing are not optimized they will not perform to specifications. There are similar analogies for automobiles where clever individuals have 'hacked' or swapped the ECU then complain about poor mileage. Third party ECUs and the components it controls may be individually optimized but they don't always play well together.

Check your device forums. Are others running the same RR 8.1 build without excessive drain? Are they using the stock kernel or one packaged by the maintainer? Focus on radio integration as that seems to be the core of your issue. Have you made other modifications to kernel parameters that have inadvertently deoptimized integration with the underlying hardware?

NB: Just noticed were are in the "Extreme Battery Life" thread. No doubt some cowboy will jump in with a 'solution' that is alarm/wakelock management based, ie: symptom squashing. Don't drink the lemonade. Better to practice something more benign like dipping your head into a pot of boiling oil :)

Moving on; hopefully provide enough material for you to run with. Good luck tracking down the source of your issue.
[Android General] xt7xda:
I had faced the same issue using powernap, i removed powernap.
[Android General] tullian:
[MENTION=5488402]Davey126[/MENTION]

Thanks a lot for taking the time and sharing your knowledge! Much appreciated!
[Android General] speedy56:
Anyone knows how to get rid of this "job.delay"?

It's crazy...1.5 alarm/min
[Android General] strongst:
Check out this discussion about the same topic https://xdaforums.com/showthread.php?t=1179809&p=77200193 maybe you can provide a similar dump file to get a better overall view of your device and its behavior?
[Android General] speedy56:
I've done an idle test now, my phone lost about 0.4%/h during the night, it's not that bad.

Based on the linked topic, I guess that that "job.delay" alarm doesn't cause much drain, if any.

Will try to forget about it and uninstall bbs [emoji23]
[Android General] strongst:
Exactly :cool:
[Android General] DB126:
0.4%/hr idle falloff is excellent. BBS exposes many items that do not need to be 'managed'. Attempting to screw with Android internals generally yields no benefits and can bring a boatload of side effects.
[Android General] creeve4:
Deleted
[Android General] Mietjelan:
I left my phone overnight and noticed that it doesn't enter deep sleep, can anyone help?
[Android General] Oswald Boelcke:
An average drainage of 0.7%/h for a device that never goes to sleep over nine hours doesn't seem to be bad. I don't want to be sarcastic but I don't recognise anything dramatic (yet). As I see you're on Oreo but also on a pretty mature version of BBS. Currently, I simply don't trust the record.

Consider to probably migrate to BBS v2.3-148 from here and to take another idle dump.

Personal remark: Amplify hasn't received any updates for quite a while, and I don't know how it caters with Nougat or any other later Android version. Since I moved from MM to Nougat, I refrained from using Amplify any longer.
[Android General] Mietjelan:
Thanks, i removed amplify this morning already as I thought that might have been a problem, I also joined the beta program for BBS so i have the newest version (2.4-262). I will try again overnight.

Verstuurd vanaf mijn Moto G6 Plus met Tapatalk
[Android General] Mietjelan:
New one from overnight, still no deep sleep
[Android General] DB126:
Idle falloff averaged 0.6%/hr which is par for stock device/rom combo. Modern HW and ROMs not need to enter 'deep sleep' while in a low power state. Enjoy your G6 as designed; no need to 'fix' what ain't broke.
[Android General] Mietjelan:
Okay, thanks!
[Android General] Reda.da:
Hi thanks for the tutorial i have followed it step by step but my battery still drain so fast, xda w'ont let me poste link in here !!how i can send you the dumpfile !?
[Android General] strongst:
When you modify the link by implementing spaces within the link for example ;)
[Android General] Reda.da:
I get a message that i need to comment like 10 times in here to get that feature
[Android General] Reda.da:
My battery drain fast.Here is my dumpfile

https://drive.google.com/file/d/15R9q2pQsGC6_vJ1nQthLYXeisR4DpCvu/view?usp=drivesdk
[Android General] strongst:
You have more than one hour screen on time. It should only be some seconds. Please provide a new idle dump.
[Android General] Reda.da:
Thanks for this tutorial. I followed it but i couldn't find most of alarms and services Please someone looks at my dump files. I have a terrible battery life
[Android General] strongst:
All dumps are useless cause the battery voltage does not drop significant. Therefore you did something wrong.

Have you charged your device while taking the dump? Please charge your device to 100 % start better battery stats, unplug the device and immediately turn off the screen and let it settle for 6+ hours.

That's no drain at all:

Level lost [%]: Bat.: 0%(100% to 100%) [0.0%/h]

Voltage lost [mV]: (4137-4089) [11.1%/h]

Level lost [%]: Bat.: 0%(100% to 100%) [---%/h]

Voltage lost [mV]: (4137-4151) [---%/h]
[Android General] Reda.da:
Ok i Will try one more time and sorry for bothering you for the second time :angel:
[Android General] strongst:
No problem, we're always trying to help you even when you think there's no help anymore ;)
[Android General] Reda.da:
Help :/
[Android General] strongst:
Please provide a full dump file from better battery stats, screenshots without enough background information about your device are useless and are irritating you especially.

For explaining detail behavior there's more to provide from your side, also for help.
[Android General] Reda.da:
I tried today but an a**hole called me the morning and the phone was in sleep for like 5 hrs.i will try again tonight.
[Android General] strongst:
Take your time:good: We need quality, not quantity and have patience ;)
[Android General] Reda.da:
Morning, that's my best man,please take a look.
[Android General] strongst:
Ok, what we have here:

1. 4 year old device with Android 6.0.1 and maybe 4 year old battery

2. xposed running power nap which isn't good while investigating battery issues, so please remove it

3. ads running in background: com.ushareit.ads.promotion.PromotionLoadService:launch ???

Correct me if something is wrong.

I would recommend to remove power nap and tell us what other mods or battery tools you're running before providing a new dump file.

Otherwise, the 2nd dump file is perfectly recorded :good:
[Android General] Oswald Boelcke:
Wow... Does SHAREit really gets all these permissions granted that are indicated on this AppBrain site?

Maybe one of the reasons why the Indian government ordered their troops to delete the app as spyware according to Wikipedia.

@Reda.da: Already many months ago, I stopped using others things (incl. Amplify and PowerNap) than Greenify and AppOpsXposed. And I can just recommend to read this very true and wise statement by @Davey126.
[Android General] Reda.da:
You"re 100% correct im currently using greenify+implify+powernap (will be removed)+appOpsxposed+herb optimiser for google play service fix only +force doze + lspeed and yesterday i downloaded mobile radio active fix xposed module.

I'm just looking for a 4 to 5 hs battery life, i got this before two weeks or so before i screw everything up and do a fresh flash.(existenZ rom 5.6.5)

And im still having google services drain up to 31% !!
[Android General] strongst:
Lol, that's a lot :eek: really, I also recommend to uninstall everything mentioned above and make a new dump do identify battery drainers instead of using unnecessary tools when you don't know the reason for sure :o
[Android General] Reda.da:
I just followed the tutorial man lol, i will uninstall everything and make another dumpfile tonight :good:
[Android General] strongst:
The tutorial is good(but now we're 2 years older) , but if you don't know what you do or what the real problem is, it's useless install tools that can have side effects ;)

It's like pumping water out of a sinking boat with tools and don't spent time so search the hole where the water drains in :laugh:
[Android General] Reda.da:
Good morning, here's the dumpfile without those tools. So please take another look (my battery is max 6 month old and it lost from 3100 m to ~ 2700 mah)
[Android General] strongst:
0.9%/h isn't bad for Android 6 devices! And as you can see, you gained 0.3%/h :svetius::svetius: by getting rid of all those tools :cool:

Something to take care of it:

com.lenovo.anyshare.download.cache.CacheService:launch (com.lenovo.anyshare.gps.SHAREit): 2 m 26 s Count:16 0.6%

com.ushareit.ads.promotion.PromotionLoadService:launch (com.lenovo.anyshare.gps.SHAREit): 2 m 26 s Count:32 0.6%

You should identify what apps/services can cause those wakelocks and eliminate them, then you can make a new dump with same parameters to compare if you gained again some %;)
[Android General] Reda.da:
I just removed that app (shareit) i will make a new dump file tonight.
[Android General] Oswald Boelcke:
I personally believe this was a really wise decision. Please refer to here.
[Android General] Reda.da:
Morning :) , here's another dumpfile (sorry, almost 6 hr.. i realy left it more....!) Please take a look.
[Android General] Reda.da:
Here's the dumpfile
[Android General] strongst:
Thanks, seems to be some cellphone wakeups but I don't know if you're at the same place or your provider changed something.

Nevertheless, seems 0.9%/h or 1%/h is your lowest idle drain you can achieve with your device and stock rom/kernel. You can check the device forum what other members can achieve with same setup.
[Android General] Reda.da:
No my provider doesn't change, so you don't suggest to use those tools anywa, cuz I'm sure there are some things i don't need in this device like location sevices and stuff. Plus my Google services drain so much battery
[Android General] strongst:
The stock roms contain bloatware, that's true. If you don't need them, just deactivate them. There's are also running services in background which are possible can be debloated. You need to refer to your device forum.

Don't trust the screenshot you provided, play services are needed for nearly every app to communicate with your google accounts and other things. Better battery stats give more detailed information.
[Android General] Reda.da:
Thanks for your time man ! I appreciate that;)
[Android General] Jomr:
Thanks for the guide
[Android General] theflyingsquirrel:
messenger setting

I am a newbie to this app and am trying to get it to limit the battery drain from messenger such as whatsapp, fb messenger.

And I found many wakelock from those apps.

Which one should I change and to what number?

Would 900 000 works?
[Android General] peterlee928:
so just fyi, you are of course more than welcome to do this. but it is generally recommended to NOT block anything related to messenger/text apps. reason is that it will impact how your phone gets notified from messages. if you do not care to receive messages as they arrive, then disregard everything i have said :)
[Android General] vvaklnprm:
Phone 100% awake when screen is off (even with greenify + naptime)

Hi all, came across this thread after a lot of investigation into why my phone is 100% awake when screen is off (as confirmed through using BBS). Fortunately for me, I see there's a few good souls in here willing to help out hapless newbs to the concept of wakelocks and doze.

I am attaching the BBS screenshots that I took in the morning leaving the phone untouched for 9 hours overnight. Please let me know if you find the culprit.
[Android General] githyanki:
Please post an idle dump as outlined in the first post. Screenshots are not suitable for analysing.
[Android General] ngshixuan:
My phone power off sometimes when I turn off my screen after using power nap, take note that I have already whitelist android system. But still the shutdown problem persist. Any other critical apps have I missed? BTW I using a oneplus 5.
[Android General] Ferbee:
I noticed the same thing, and just decided to not use powernap everything else works fine
[Android General] Oswald Boelcke:
My personal opinion and experience with PowerNap: Here.

Also the development seems to have halted quite a while ago i.e. I've serious doubts that it positively affects modern ROM but might even have negative ones. Additionally, over a long time my experience has raised that tools like PowerNap or Amplify probably fight effects but not the reasons of excessive battery drainage, and my personal intention is to go for the roots.
[Android General] DB126:
Search the thread; common issue (among many others). Like my physician father use to say after I smashed my finger with a hammer: "That hurt? Don't do it any more". Wonderful guidance as most pain is self inflicted.
[Android General] Wenro:
Hey :)

I managed to block out a lot and have way better batterylife now. However, I got a few questions..

My Wakelock time allowed should be low, right? It shows really high compared to the time blocked.

[IMG="https://i.postimg.cc/br4TkN8v/Screenshot-20181013-143420.png"]https://i.postimg.cc/br4TkN8v/Screenshot-20181013-143420.png[/IMG]

*alarm*

DeviceMonitorService

are far ahead with the number of wakelocks. Can these be fixed?

[IMG="https://i.postimg.cc/s2K4KJyq/Screenshot-20181013-143521.png"]https://i.postimg.cc/s2K4KJyq/Screenshot-20181013-143521.png[/IMG]
[Android General] DB126:
Over time you will come to realize the reported metrics associated with wake lock limiting/blocking can not be rationalized using any form of reasonable analysis. It will slowly drive you insane but you'll keep coming back for more. Like the Mirror of Erised one can not resist the pull of false hope.

Alternatively, you can stop the foolish journey of alarm/wakelock tinkering, identify the root causes of poor battery endurance (hint: it's probably in your apps) and let Android deal with managing your phone. Head over to the BBS forum, submit an idle study and allow one of talented members show the way to better battery life without all the black magic. Just say'in ...
[Android General] Wenro:
Calm down with the dictionary stuff. I have only limited a few items and I see no excessive battery drain from none of my apps, I have a little more than 2 days batterylife, which is fine already.

I simply asked about the wakelock and the wakelock time allowed. Not that I "have 5 minutes of batterylife and REALLY NEED TO FIX IT!!!!"
[Android General] DB126:
As noted the reported stats rarely align with reality.

There is nothing to "fix" because nothing is broke. Akin to a laymen looking at a hospital monitor and asking if the pulse can be suppressed.

I am sure someone has an 'answer'; i'll step aside and enjoy the entertainment.
[Android General] Oswald Boelcke:
YOU asked here (and by the way cluttered lots of screen with your screenshots), and only because you received a very valid reply that obviously doesn't suit you well you raised your voice? YOU should calm YOUR voice down towards the guys who are always here to support. If you don't like this, the I suggest to flip the pages in your encyclopedia to find your answers.
[Android General] Wenro:
I didn't raise my voice....? I used quotation marks to kinda simulate how some people write. As an example. Please, read it again.

I'm eternally grateful for any support I get.

EDIT: And no, it wasn't a valid reply. I asked a valid question however, since Amplify and the wakelocks are one of the focus points of this topic. To tell someone they shouldn't tinker with something is not a valid reply. Because "tinkering" is exactly what OP and the rest of the people in this thread are doing to manage batterylife.
[Android General] Oswald Boelcke:
I apologise to all that I continue off-topic. Not being a native English tongue, I might really have misjudged your speech, in which case I apologise. However, as I'm a bit more than slightly familiar with the English (not necessarily the American) language, I doubt that. And I assume in English it's the same as in my mother tongue that a phrase nested within quotation marks shows a statement of a different "speaker" or "source". The one and only quotation by you, I did recognise in this post and please allow me to quote you:

Sorry, but I can't find the source of your quotation; I doubt that we at XDA intend to uphold the policy of senior leaders of some countries.

Anyhow back to Amplify; here's my opinion: Amplify itself is also on halt for a year. Maybe Amplify was "qualified" to run on Android 6.1 and below, but for newer Android versions I've my doubts that the changes that came with these versions were/are really implemented in Amplify. I terminated utilisation of Amplify long time ago, and I don't miss the capabilities Amplify promised 12 months ago at all.

I personally go with @Davey126's recommendations and suggestions. But we're all our own commanders (my wife is the commander-in-chief), and the final decision rests with us. I wish you to receive a reply in this thread that suits you.
[Android General] Wenro:
Hey

The whole thing was an attempt of sarcasm that went wrong. What I meant with the entire thing is kinda hard to explain, english nor american are my native languages.

Let me try.. I asked about the wakelocks, and also stating that I already have pretty decent batterytime, and it's not like (here is where the quotationmarks came in) "I'm in desperate need for help since my phone has 5 minutes of batterytime and it really needs to be fixed".

The part where you thought I "raised my voice" was just me trying to be sarcastic and I might have used quotationmarks wrongly, even though I always do like that when I attempt sarcasm.

I also don't wish to have a bad reputation here and that people see me as some spoiled brat. I do have manners and I'm always really glad to recieve answers to my questions. It was a little bit of a feeling being jumped, since I didn't understand what I did wrong and I was sure I was staying relevant to the topic. I love this forum and the people taking their time to help others, and I've received plenty of help here!

On topic: If it's on halt and not super relevant to my version being 7.1.1, I will not dig into it further.

Thank you for the elaborated post, I really appreciate it! :good:
[Android General] Oswald Boelcke:
@Ampull: I appreciate and thank you for the explanation. This clarified really ALL to me. Since I've lived for a year in California in 1982, I've learnt my lesson not to try to be sarcastic unless I use my mother tongue. Everything else - at least in my case - always went tits-up. I hope we continue to find useful times together in this thread, and that we're able to help and support each other.
[Android General] DB126:
Stock AOSP 7.1.1 does a fine job managing background activity. Unfortunately, some custom ROMs are not optimized for the target device/kernel which sometimes leads to extraneous wakelock activity.

Limiting/blocking system level wakelocks, especially those associated with Play Services, often generates additional wakelocks with receptive receivers. The 'system' recognizes missed events and becomes more aggressive. Simply allowing Android to get what it wants when it wants it is often the most efficient approach. Time is better spent observing app behavior and addressing 'offenders' as identified. Good luck with whatever approach you choose.
[Android General] Wenro:
Great to know, I'm sure you have provided this info earlier and I should've read, but the topic is huge.. :)

I'm on stock ROM with GreenKernel, so I think that it's better letting the phone do its thing, then. ?

Thank you!
[Android General] dilidani:
Hello guys, could you please help me?

I have a nasty standby drain, like 12-15% in a night. Here is my dump (6+ hrs)

Best,

Dani
[Android General] strongst:
Hello, the dump looks OK, but you have a custom kernel and rom(Pixel rom pie I guess), correct me if I'm wrong. So did you tried a rom suited for your device like oxygenOS stock rom? I guess it will perform better.

Otherwise it can also be an old battery or your wifi connection.
[Android General] dilidani:
It's an AOSP Extended Oreo rom, guessed it will be more stable haha :D

But custom kernel indeed. Maybe I should try another build of the kernel, stock kernel, or something like that.. :)
[Android General] strongst:
Yeah, you also can break it down and change the kernel at first, then rom, wifi connection test...

Several things to try out ;)
[Android General] k54k54k54:
after months of tests and readings and reading and reading etc etc etc ... I have not yet understood if amplify is useful or not to improve battery life daily

thanks

by k54 from italy
[Android General] strongst:
Have you made your personal comparison with and without amplify? You need to do it.

In general if you don't know the root cause of your personal battery drain its not recommended to use tools that can lead to unwanted side effects.

Better to identify the battery drainers and engage them individually(amplify can help too, but not without knowledge).
[Android General] k54k54k54:
but it is so different the use in a day that it is difficult to estimate an improvement and a worsening. obviously it was an hour more than screen on time then I'll understand immediately

ok !

thanks

by k54

from italy
[Android General] Kopni:
How to stop 'Smartmanager framework thread' in Samsung n9005 with Android 5.0

Hello!

I have 'Package disabler pro' in Samsung n9005 with Android 5.0. 'Smartmanager framework thread' wakes CPU hundreds times more often than any other 'Android system' component. Disabling 'Smart manager provider' in 'Package disabler pro' does not stop 'Smartmanager framework thread'. What other should I disable in 'Package disabler pro' to stop 'Smartmanager framework thread'?

Kind regards
[Android General] DertYazu:
Battery Life

Hello guys this is my recent dumpfile can anyone tell me what to do if there more to customize to have less battery loss during idle? :fingers-crossed:
[Android General] strongst:
For this device with lollipop version its a good drain 0.8%/h. Maybe you can try without Facebook messenger, but as I said: a good idle drain :svetius:
[Android General] Estebanium:
Hi guys,

I use BetterBatteryStats to track my phone. I also installed Amplify to control some of the Wakelocks and Alarms, only a few. I noticed that there is one alarm that has a very high counter and even Google gave me no result:

Wificondscannerimpl Background Scan Period

Does someone know what it is? I have no clue and even in Amplify I am not able to track it down.

I attached a dump and a screenshot, maybe you have an idea, or you can give me some more tips to my setup.

I have a Samsung S7 Edge with LineageOS 15.1 installed. Ignore the HTC thing, this is related to my Gear S3, otherwise Samsungs App would not run.