Well, perhaps that sounds somewhat drastic
But sometimes, seemingly at random, Automagic (mostly together with the Telegram app somehow) just starts draining the battery like there is no tomorrow.
The only thing i know is that i have a disabled flow that has a trigger "Notification on Statusbar Displayed" of which the "package Name" field is: org.telegram.messenger.
But again, that flow is disabled for over months now,since i need to expand it some time.
Here is how much:
And here is how long that took:
Green = Voltage
Blue = CPU
Red = Temperature
White = Battery
Battery Slayer
Moderator: Martin
- digitalstone
- Posts: 342
- Joined: 21 Oct 2017 12:36
- Location: The Netherlands
Battery Slayer
Phone: LG Nexus 5X (rooted vanilla Android 7.1.2)
Re: Battery Slayer
It is possible you have run-away flow. Try to check each group and see if there is any flow shows in red. The culprit will be the red one there. Or you can peek at the automagic statistic and see which flow is running all the time or triggered the most. It is not necessary to be related to telegram, it can be just side effect.
Index of Automagic useful thread List of my other useful posts (and others')
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
- digitalstone
- Posts: 342
- Joined: 21 Oct 2017 12:36
- Location: The Netherlands
Re: Battery Slayer
The only flow that is constantly active is "Profile Switcher" (which should actually should be called "Profile Manager").Desmanto wrote:It is possible you have run-away flow. Try to check each group and see if there is any flow shows in red. The culprit will be the red one there. Or you can peek at the automagic statistic and see which flow is running all the time or triggered the most. It is not necessary to be related to telegram, it can be just side effect.
Automagic statistics are reading like they should. No conspicuous readings anywhere.
The only apps that opted out of Battery Optimization are: "Automagic" & "Timely".
Timely is just a 3th-party time app, which includes an alarm clock, timer etc. I've been using it since 2013.
Don't know what else to cover here.
Telegram indeed isn't necessarily bonded to this phenomenon, but until now i've seen it almost every time i can remember.
Phone: LG Nexus 5X (rooted vanilla Android 7.1.2)
Re: Battery Slayer
Hi. Maybe you could try and use gsam battery monitor, although it hasn't been updated in a while and I don't trust it as much as I used to. Also, I don't know if the free version actually allows seeing each app in particular. Anyways, as you can see from the report below it shows which flows are running and for how long. Maybe it's more helpful then AM statistics.
If not I think you should clear cache and app data after backing up flows and widgets and restoring them afterwards.
Personally I think I ran AM on maybe 10 different devices and I haven't seen this behavior.
Good luck
GSam Labs - Battery Monitor - Export Data
Automagic Premium
3 Oct 2018 21:47:21
Usage Details
CPU Usage:26s
CPU Usage (Background Only):0s
Keep Awake:29s
Number of Wake Locks:9
Number of times waking device:12
Bytes Sent:1.55 KB
Bytes Received:10.79 KB
App UID:10273
Wakelock Detail
29.9s(3)[ login_internat]
0.1s(4)*alarm*
0.0s(2)AMS onStartCommand
Included Packages
Automagic Premium
Included Processes
ch.gridvision.ppam.androidautomagic:Forum
*wakelock*
ch.gridvision.ppam.androidautomagic
com.google.android.webview:sandboxed_process0
If not I think you should clear cache and app data after backing up flows and widgets and restoring them afterwards.
Personally I think I ran AM on maybe 10 different devices and I haven't seen this behavior.
Good luck
GSam Labs - Battery Monitor - Export Data
Automagic Premium
3 Oct 2018 21:47:21
Usage Details
CPU Usage:26s
CPU Usage (Background Only):0s
Keep Awake:29s
Number of Wake Locks:9
Number of times waking device:12
Bytes Sent:1.55 KB
Bytes Received:10.79 KB
App UID:10273
Wakelock Detail
29.9s(3)[ login_internat]
0.1s(4)*alarm*
0.0s(2)AMS onStartCommand
Included Packages
Automagic Premium
Included Processes
ch.gridvision.ppam.androidautomagic:Forum
*wakelock*
ch.gridvision.ppam.androidautomagic
com.google.android.webview:sandboxed_process0
- digitalstone
- Posts: 342
- Joined: 21 Oct 2017 12:36
- Location: The Netherlands
Re: Battery Slayer
Thank you for that. I shall take a look at it.
Phone: LG Nexus 5X (rooted vanilla Android 7.1.2)
Re: Battery Slayer
One of the way you can try is to turn off automagic services for several hours and see if it drains. Then try to start automagic and disable potential flow that might cause problem.
It seems my Automagic statistic flow can be very useful in this case, as it can save all flow state and restore it later. But I still left the last looping state before I can share it. (which probably take another week to finish it).
It seems my Automagic statistic flow can be very useful in this case, as it can save all flow state and restore it later. But I still left the last looping state before I can share it. (which probably take another week to finish it).
Index of Automagic useful thread List of my other useful posts (and others')
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
- digitalstone
- Posts: 342
- Joined: 21 Oct 2017 12:36
- Location: The Netherlands
Re: Battery Slayer
I think i forgot to mention one important thing.
It only happens sometimes. like, once every couple of weeks.
That is the main reason i find this odd behavior. There is nothing that i do different than any other time.
So it seems very random because:
-It happens every 2-3 weeks
-And i/the phone/both do nothing different.
This makes it very hard to test.
It only happens sometimes. like, once every couple of weeks.
That is the main reason i find this odd behavior. There is nothing that i do different than any other time.
So it seems very random because:
-It happens every 2-3 weeks
-And i/the phone/both do nothing different.
This makes it very hard to test.
Phone: LG Nexus 5X (rooted vanilla Android 7.1.2)
Re: Battery Slayer
Yeah, intermittent problem always the most difficult to test. That's why we need something that can monitor silently such as the GSAM or BBS as pointed out by bogdyro. If there is runaway flow, it will appear immediately as the main battery drainer. Other than that is to check the statistic and last executed flow.
Index of Automagic useful thread List of my other useful posts (and others')
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
Xiaomi Redmi Note 5 (whyred), AOSP Extended v6.7 build 20200310 Official, Android Pie 9.0, Rooted.
- digitalstone
- Posts: 342
- Joined: 21 Oct 2017 12:36
- Location: The Netherlands
Re: Battery Slayer
Yes sorry, i forgot.
I installed GSam Battery Monitor and generated a log file to see where that leads to.
The log looks impressive.
Now we'll see what fish we can catch here..
I installed GSam Battery Monitor and generated a log file to see where that leads to.
The log looks impressive.
Now we'll see what fish we can catch here..
Phone: LG Nexus 5X (rooted vanilla Android 7.1.2)