I have installed several apps that need Accessibility set to On in order for them to keep working. 3 of those keep getting disabled by I guess the system and I have to go in and toggle that permission switch to Off and then back On again. It happens randomly, sometimes after a few days and sometimes after a few hours but when it happens it alway affects those 3 apps together.
The 3 apps are Super Status Bar, Power Shade Premium and Energy Ring. Others like Button Mapper or Nova (for doubletap to sleep) are unaffected.
Those apps are excluded from battery optimization, I'm not rooted (yet) and I don't have any "app killer" running. Googling was no help so I'm hoping someone here has an idea. I'm guessing A12 is doing something shady here, but how do I stop it from happening?
Nimueh said:
I have installed several apps that need Accessibility set to On in order for them to keep working. 3 of those keep getting disabled by I guess the system and I have to go in and toggle that permission switch to Off and then back On again. It happens randomly, sometimes after a few days and sometimes after a few hours but when it happens it alway affects those 3 apps together.
The 3 apps are Super Status Bar, Power Shade Premium and Energy Ring. Others like Button Mapper or Nova (for doubletap to sleep) are unaffected.
Those apps are excluded from battery optimization, I'm not rooted (yet) and I don't have any "app killer" running. Googling was no help so I'm hoping someone here has an idea. I'm guessing A12 is doing something shady here, but how do I stop it from happening?
Click to expand...
Click to collapse
I'm wondering if you've entered Power Saving Mode before this problem occurs? At least 2 of these apps will be killed when Power Saving Mode is entered and you have to restart your device to get it going again. Maybe it also kills the Accessibility service? Not really sure, just throwing it out there.
Lughnasadh said:
I'm wondering if you've entered Power Saving Mode before this problem occurs? At least 2 of these apps will be killed when Power Saving Mode is entered and you have to restart your device to get it going again. Maybe it also kills the Accessibility service? Not really sure, just throwing it out there.
Click to expand...
Click to collapse
No, Power Saving Mode is disabled and the battery wasn't low enough for it to even have kicked in. When it happened (twice!) yesterday the battery was 40-50% both times. Adaptive battery is disabled too so battery "shouldn't" be causing it in any way.
Thanks for replying though
Just a small update:
Oddly enough since I started this thread it hasn't happened again
I did sideload that mid-month update right around the same time of my post, maybe that fixed it ... no idea really, I'm just glad it's not happening any more
Related
Hey everyone,
After playing a bit with my Honor battery this week, I realized that my phone barely goes into deep sleep mode.
I have few Power consuming apps running in the background such as Facebook, Google App, Google Play Store, Textra, Gmail or Pebble.
Using tasker I periodically turn on and off the Auto Sync parameter (1 min of auto sync every 30 minutes) and I always shut down all the applications running in the background.
In my previous Nexus 5, I didn't had much of a problem with the CPU Deep sleep but now that I'm on EMUI without Root on I feel like I can barely control anything that's happening on my phone anymore, especially on the battery.
Overall the battery is still correct but I'm just wondering whether I'm the only one noticing this.
Thanks !
If battery life is normal then it doesn't matter. All cpu operate differently, maybe its just how kirin is. If apps are consuming power in background , emui will tell you.
Have you gone through the power saving and background apps managers of EMUI itself ? Maybe there is conflict of that with Tasker.
I just create battery discussion thread, I appreciate if you can post info here , Thanks
http://forum.xda-developers.com/honor-7/general/battery-life-discussion-t3196324
warea said:
Have you gone through the power saving and background apps managers of EMUI itself ? Maybe there is conflict of that with Tasker.
Click to expand...
Click to collapse
Yeah, I'm spending a lot of time checking out the power saving in the background and after a few day it seems that the phone kinda got used to it.
Facebook and G+ are still coming up first in term of power consumption (I actually wonder why every time I kill them, they just come back... even though they're both not synchronized anyway)
I've gotta admit that the on screen time is pretty amazing! The one thing that's kinda scaring me is the background power consumption but I'll try harder to get this right if anything can be done about these app running in the background. (I'll try rooting and grenifying it)
Other than that, yeah the phone last me a good day with a good amount of on screen time!
*edit: I apologize for the thread title, I didn't notice that I went beyond the character limit while typing.
I seem to have noticed that when using apps that download and sync things in the background (Spotify, Messenger, etc.) while Power Saver is enabled, they stop updating once the screen is turned off or when multitasking. I can tell they stop transferring data and performing tasks once I switch apps because they vanish from the notification shade.
I've never had any problems like this before on Lollipop even with the power saving mode active. I usually have my phone on Power Saver all the time, and it's frustrating me to an extent seeing as to how Marshmallow is forcing me to have it turned off just so I can use my apps properly. I've tried checking app optimization and the apps I mentioned have been turned off for optimization. All my applications are updated as well.
Is this a common issue? Any help with fixing this would be great.
I use Greenify for a long time with donation package, beta tester also.
At the moment I'm using it on a non-rooted Samsung Note 5
I add most of the programs be "greenified" except a few important for me.
The BIG PROBLEM is that in most of the times when there is an ACTIVE CALL, Greenify strart "working" and I can not do aniting. The phone is "black" and I can not even close/finish the call, just waiting Greenify to "hibernate" a.k.a. "force stop" all apps.
Sometime with 5 to 10 "power button" presses I'm able to interupt "hibernation" and to close my call.
Please, add an option to DISSABLE hiberation during a CALL!!!
Somebody else having this problem?
Best regards to all developers!
ChoSmile said:
I use Greenify for a long time with donation package, beta tester also.
At the moment I'm using it on a non-rooted Samsung Note 5
I add most of the programs be "greenified" except a few important for me.
The BIG PROBLEM is that in most of the times when there is an ACTIVE CALL, Greenify strart "working" and I can not do aniting. The phone is "black" and I can not even close/finish the call, just waiting Greenify to "hibernate" a.k.a. "force stop" all apps.
Sometime with 5 to 10 "power button" presses I'm able to interupt "hibernation" and to close my call.
Please, add an option to DISSABLE hiberation during a CALL!!!
Somebody else having this problem?
Best regards to all developers!
Click to expand...
Click to collapse
Have you greenified anything related to phone calls? Can you post a screenshot of what all you have greenified? Do you also use Amplify?
This is not the normal behaviour unless you greenified or limited something which you ought not have.
Nothing related to Call or Phone or other system realated apps are in Greenify list (178 apps).
Normal behaviour of Greenify is to start hibertatiing apps when screen goes off.
(In root or boost (xposed) mode this operation is very fast, it closes many apps at once.)
But in NON-root mode it use standart automated [Force close] dialog or every app, so it takes a second or two per app to close it.
When I make (or receive) a call, I put the phone near to my ear, the proximity sensor turns off the display.
After a while, Greenify starts hibernation process.
There is no problem with the CALL itself, it is not interrupted or disturbed and qualiry is excellent.
The problem is when I take off my phone from my head, proximity sensor "realesed" and display have to goes on (rise) again but this NOT happens.
At this moment Greenify closes apps one by one and screen is OFF.
Call conversation remains active and I can NOT hang up (close) my call.
No reaction if I press [Home] or [Power] buttons.
By pressing many times (5+) [Power] button I'm able to interupt the Greenify hibernation process, display goes on and I see the force close app's dialog.
Now I use drop down menu and press (red earphone icon) to hang up (close) my active call.
That's why I think that settings option in Greenify for "temporary disable of hibernation" during an active call will be very useful especialy for "non-root mode" users.
Do you think it is worth to add such option?
@ChoSmile
When you are on a call, it will hold a wakelock so that the screen going off doesn't affect it. The proximity sensor senses your face near it and switches off the screen. When the phone is held away from the face, the proximity sensor should sense it and switch on the screen. This is the normal behavior.
Greenify starting to hibernate the apps should not affect the proximity sensor sensing. Check the functioning of your proximity sensor because no one else seems to have reported this problem, as far as I know.
I don't think that Greenify hibernates apps during a call ie. while the screen is off during a call. Atleast for me, it doesn't.
ChoSmile said:
I use Greenify for a long time with donation package, beta tester also.
At the moment I'm using it on a non-rooted Samsung Note 5
I add most of the programs be "greenified" except a few important for me.
The BIG PROBLEM is that in most of the times when there is an ACTIVE CALL, Greenify strart "working" and I can not do aniting. The phone is "black" and I can not even close/finish the call, just waiting Greenify to "hibernate" a.k.a. "force stop" all apps.
Sometime with 5 to 10 "power button" presses I'm able to interupt "hibernation" and to close my call.
Please, add an option to DISSABLE hiberation during a CALL!!!
Somebody else having this problem?
Best regards to all developers!
Click to expand...
Click to collapse
By any chance do you have aggressive doze enabled in greenify? I started having about the same issue, i would receive a call and screen would never wake up. I had done a lot of tweaks and wasn't sure what exactly what was causing this. So I did a fresh install and started a little bit at a time doing my tweaks and never got to install greenify yet. So far, phone has been working properly. So maybe this had something to do with aggressive doze or the fact that I had two apps setting aggressive doze, greenify and force doze.
kenboyles72 said:
By any chance do you have aggressive doze enabled in greenify? I started having about the same issue, i would receive a call and screen would never wake up. I had done a lot of tweaks and wasn't sure what exactly what was causing this. So I did a fresh install and started a little bit at a time doing my tweaks and never got to install greenify yet. So far, phone has been working properly. So maybe this had something to do with aggressive doze or the fact that I had two apps setting aggressive doze, greenify and force doze.
Click to expand...
Click to collapse
I disable Aggressive Doze (experimental) but issue happens again, might be no so offen like before I disabled it.
@tnsmani
Do you use Greenify on NON rooted device?
Because on rooted devices, you probably use it "Root" or "Boost" working mode where hiberanating is "at once" for many apps.
ChoSmile said:
I disable Aggressive Doze (experimental) but issue happens again, might be no so offen like before I disabled it.
@tnsmani
Do you use Greenify on NON rooted device?
Because on rooted devices, you probably use it "Root" or "Boost" working mode where hiberanating is "at once" for many apps.
Click to expand...
Click to collapse
Normally I use Greenify in root/boost mode since my phone is rooted.
But to investigate your issue, I ran it in non-root mode (phone is still rooted). Still my screen behaves normally.
I have the same issues exactly non root greenify kicks in during calls and everything goes south. Any solution to disable greenify during calls
Sent from my ONE A2003 using Tapatalk
Guys. Anyine found a solution here? This is a real issue for me. I am using non root and everytime a call starts, screen goes dark, greenify starts and doesn't capture the right screens probably but rather initiates clicks on the task bar on the top. This way I see the WiFi starting or Hotspot being disabled or data being turned off.
All I need is for greenify to not work during calls!
Sent from my ONE A2003 using Tapatalk
ofird said:
Guys. Anyine found a solution here? This is a real issue for me. I am using non root and everytime a call starts, screen goes dark, greenify starts and doesn't capture the right screens probably but rather initiates clicks on the task bar on the top. This way I see the WiFi starting or Hotspot being disabled or data being turned off.
All I need is for greenify to not work during calls!
Click to expand...
Click to collapse
Seems to be a persistent, unresolved issue on some non-rooted devices with stock ROMs. You'll probably have to abandon Greenify.
My worst issues with battery drain is when the phone is on and not off. Maube screen brightness. I don't know but it drains like crazy
Sent from my ONE A2003 using Tapatalk
ofird said:
My worst issues with battery drain is when the phone is on and not off. Maube screen brightness. I don't know but it drains like crazy
Click to expand...
Click to collapse
Your ROMs built in battery stats may (likely will) provide clues to that type of drain. For a more comprehensive assessment try GSAM which is a available in the Play Store. BBS can also help but it's a little more difficult to interpret IMHO. Good luck.
I notice that the double click of the power button still opens the camera in nougat and now there doesn't seem to be a way to switch it off. I've accidentally triggered this twice, hit home to close camera, then pressed the power button to switch off. Soon after on both occasions the phone has partially rebooted in my pocket, sticking on the Wiley fox boot logo.
Anybody else confirm this behaviour? Not something you do everyday I guess......
Hi Ratbags, I tried it for you... I never noticed that tapping the power button twice starts the camera, but indeed it does; however my phone didn't reboot (so it also didn't get stuck).
Hallo ratbags, i can confirm this behaviour in my Swift 2 Plus with Nougat Android. Noticed that randoms reboots some while ago and with your hint about power double click i am able to reproduce it.
To switch it off
Go to parameters
Use the search option and search gestures
Click on Gestures and then you'll find the option you are looking for
naegi said:
To switch it off
Go to parameters
Use the search option and search gestures
Click on Gestures and then you'll find the option you are looking for
Click to expand...
Click to collapse
Thanks for that. I believe Wiley fox are bringing out an update to fix this issue. Strange you can only get to that setting by searching or is it hidden away somewhere deep in a settings submenu?
ratbags said:
Thanks for that. I believe Wiley fox are bringing out an update to fix this issue. Strange you can only get to that setting by searching or is it hidden away somewhere deep in a settings submenu?
Click to expand...
Click to collapse
I didn't find it anywhere else so I think it's hidden
There's others hidden menu (and some are not even working at all - like battery percentage). I think that it's the trace of some modifications of parameters that weren't done correctly, or those parameters were disabled because the option didn't work well.
With latest update Build no. TOS118C the Gestures are available in Options Menu. The "not quite random reboot" seems to befixed too. Tested it several times and got no reboot since 3 hours.
Was just scanning the forum for any reports of random reboots as I've also been having reboots and it hanging on the white WileyFox logo screen.
Have noticed it more since the more recent official updates and have even gone so far as a full factory reset, however, I've had the issue reoccur several times since then (reset done earlier in week) so will be interesting to see if disabling that camera gesture will help
Beyond that I'm thinking possibly a corrupt or "worn" SD Card as I have a MicroSD card, used to extend the internal storage, that I think I used for a year or so in my previously Swift so possibly suffering some mild wear....
With my Note 4, it would wake up from Android Doze, or simply not enter that state if there was movement of the phone. I felt stupid needing to pick up my phone every 10 min to give it a small shake, but at least it seemed to work. I keep my phone in my pocket when I'm working outside and that always kept the Note 4 from falling into Doze mode. Not so with the S9+. It drops into Doze even in my pocket. Anyway to stop that from happening? Like others here, I feel frustrated needing to activate my screen to find out if there are notifications.
Brokk said:
With my Note 4, it would wake up from Android Doze, or simply not enter that state if there was movement of the phone. I felt stupid needing to pick up my phone every 10 min to give it a small shake, but at least it seemed to work. I keep my phone in my pocket when I'm working outside and that always kept the Note 4 from falling into Doze mode. Not so with the S9+. It drops into Doze even in my pocket. Anyway to stop that from happening? Like others here, I feel frustrated needing to activate my screen to find out if there are notifications.
Click to expand...
Click to collapse
That's not Doze mode. Doze is when Android puts apps to sleep that are in memory not being used. This is done to save battery (and processing time?).
So what is happening here, if I understand, is that your phone display is going blank when you pull it from your pocket?
Scott said:
That's not Doze mode. Doze is when Android puts apps to sleep that are in memory not being used. This is done to save battery (and processing time?).
Click to expand...
Click to collapse
Doze was originally described as putting your phone into a power saving sleep mode after 20 min of "inactivity". The issue that caused me problems back then was not about the apps, but that notifications pushed to the device were queued up by the system until your phone "woke up", then the notifications would come rolling through. This happened at the system level regardless of app.
Perhaps in the latest version of Android they have changed the definition of Doze, but another poster was having a lot of issues with notifications (mostly email) and the culprit was deemed to be Doze.
Scott said:
So what is happening here, if I understand, is that your phone display is going blank when you pull it from your pocket?
Click to expand...
Click to collapse
No. My display is blank (as it should be) when I put it into my pocket, as well as when I pull it out. I always shut the screen off before putting my phone down, or in my pocket.
If I put my phone in my pocket, and 5-10 min later I get a notification, it comes through loud and clear and I pull my phone out and check it. If 20+ min has gone by without me having a reason to turn the screen on, then I stop getting notifications. When I pull it out to check the time or send a message, suddenly the notifications come rolling through.
Again, I was used to this if the Note 4 was put down, but this behavior is new to me if the phone is moving about.
Brokk said:
Doze was originally described as putting your phone into a power saving sleep mode after 20 min of "inactivity". The issue that caused me problems back then was not about the apps, but that notifications pushed to the device were queued up by the system until your phone "woke up", then the notifications would come rolling through. This happened at the system level regardless of app.
Perhaps in the latest version of Android they have changed the definition of Doze, but another poster was having a lot of issues with notifications (mostly email) and the culprit was deemed to be Doze.
No. My display is blank (as it should be) when I put it into my pocket, as well as when I pull it out. I always shut the screen off before putting my phone down, or in my pocket.
If I put my phone in my pocket, and 5-10 min later I get a notification, it comes through loud and clear and I pull my phone out and check it. If 20+ min has gone by without me having a reason to turn the screen on, then I stop getting notifications. When I pull it out to check the time or send a message, suddenly the notifications come rolling through.
Again, I was used to this if the Note 4 was put down, but this behavior is new to me if the phone is moving about.
Click to expand...
Click to collapse
I concur. Same happens to me.
I don't have this issue at all. I have my phone in my pocket most of the day and don't need to "wake" the phone up for notifications. I can leave my phone unattended for hour or 3 and it still receives the notifications without issues. I don't know if I have turned on a setting that mine works different, but I must say that my battery life isn't that great....as if the phone never sleeps/doze at all
termdj said:
I don't have this issue at all. I have my phone in my pocket most of the day and don't need to "wake" the phone up for notifications. I can leave my phone unattended for hour or 3 and it still receives the notifications without issues. I don't know if I have turned on a setting that mine works different, but I must say that my battery life isn't that great....as if the phone never sleeps/doze at all
Click to expand...
Click to collapse
I'm curious. Do you have any of the power saving modes turned on? Do you use "always on display"?
I never use the power save modes. Aod is on from 5 in the morning till 8 at night
termdj said:
I never use the power save modes. Aod is on from 5 in the morning till 8 at night
Click to expand...
Click to collapse
AoD could be keeping your phone awake, preventing Doze. The power saving features talks about putting apps to sleep, so unless you use them, that could also be disabling Doze. I could try changing the power saving settings, though it seems like a shame. I have zero interesting in AoD for multiple reasons, so it's not worth it for me to use that to solve my problems.
Thanks for the information!
Doze changed in Nougat, I believe, so that motion no longer prevented Doze from working. Since most men, at least, carry their phone in their pocket Doze hardly ever kicked in, greatly limiting its power saving capability.
You can exempt specific apps from Doze if you want to get notifications from them even when dozing.
Settings / Apps / 3 dot menu / special access / Optimize battery usage. Select All Apps from the drop down. Turn off the toggle for any apps you don't want to Doze.
Brokk said:
Doze was originally described as putting your phone into a power saving sleep mode after 20 min of "inactivity". The issue that caused me problems back then was not about the apps, but that notifications pushed to the device were queued up by the system until your phone "woke up", then the notifications would come rolling through. This happened at the system level regardless of app.
Perhaps in the latest version of Android they have changed the definition of Doze, but another poster was having a lot of issues with notifications (mostly email) and the culprit was deemed to be Doze.
No. My display is blank (as it should be) when I put it into my pocket, as well as when I pull it out. I always shut the screen off before putting my phone down, or in my pocket.
If I put my phone in my pocket, and 5-10 min later I get a notification, it comes through loud and clear and I pull my phone out and check it. If 20+ min has gone by without me having a reason to turn the screen on, then I stop getting notifications. When I pull it out to check the time or send a message, suddenly the notifications come rolling through.
Again, I was used to this if the Note 4 was put down, but this behavior is new to me if the phone is moving about.
Click to expand...
Click to collapse
Yes, I am confusing Doze with the Samsung power saving options. Blah!
I know the battery life will decrease with aod, but I have noticed that even without aod on my battery drop 2% per hour, so I leave it on...There are days that I can go 1 day and 8 hours before charging, but then my sot is only 2 hours....In general I'm happy with the battery life
meyerweb said:
You can exempt specific apps from Doze if you want to get notifications from them even when dozing.
Settings / Apps / 3 dot menu / special access / Optimize battery usage. Select All Apps from the drop down. Turn off the toggle for any apps you don't want to Doze.
Click to expand...
Click to collapse
Thanks!
It seems oddly redundant needing to do essentially the same thing in two places. One well advertised under the battery settings, and the other one hidden under settings/apps/special access.
Hopefully this will fix my problems. Glad to know there is a work around.
Brokk said:
Thanks!
It seems oddly redundant needing to do essentially the same thing in two places. One well advertised under the battery settings, and the other one hidden under settings/apps/special access.
Hopefully this will fix my problems. Glad to know there is a work around.
Click to expand...
Click to collapse
The two settings really are doing different things. Samsung's (in the battery settings), puts apps to sleep after 3 to 7 days (depending on your settings). The won't wake up again until you use them. Doze (the pretty much hidden option in Apps), lets the apps wake up on their own, when you start using the phone, even if you don't access those particular apps.
I'm not sure why the Doze setup is buried so deep in settings, though. I guess Google (or Samsung?) really doesn't want you interfering with it.
meyerweb said:
The two settings really are doing different things. Samsung's (in the battery settings), puts apps to sleep after 3 to 7 days (depending on your settings). The won't wake up again until you use them.
Click to expand...
Click to collapse
I made a mistake of putting an app to sleep that I use to keep my screen awake. It uses a widget to toggle it on/off, but will shut off along with the screen if you intentionally shut your screen off. After putting that app to sleep, the widget stopped working. I had to go find the actual app, start it, then quickly flip back to my home screen and click on the widget. I couldn't undo my "sleep" action on that app. I changed it to "unmonitored", so that the S9+ would never put it to sleep. I rebooted. I shut off the power saving options. Nothing worked. Everytime I would go to the widget (unless I just started the actual app), it wouldn't react to clicking on the widget.
I finally gave up and uninstalled the app from my phone. Rebooted. Reinstalled it and now it works fine. So I'm not sure I agree with "puts the app to sleep in 3 to 7 days". Maybe 3-7 minutes...
Well, 3 to 7 days is what Samsung says, and the optional range you can set in the app. Don't know what specifically happened with that widget, though.
meyerweb said:
Well, 3 to 7 days is what Samsung says, and the optional range you can set in the app. Don't know what specifically happened with that widget, though.
Click to expand...
Click to collapse
Where is the setting(s) for optimal range? I don't remember specifying that. I thought it was more of an on/off thing. White listed (unmonitored resource consumption) or black listed (never let it run in the background). Then apps in neither list it reports to you and you can force them to sleep or not.
Brokk said:
Where is the setting(s) for optimal range? I don't remember specifying that. I thought it was more of an on/off thing. White listed (unmonitored resource consumption) or black listed (never let it run in the background). Then apps in neither list it reports to you and you can force them to sleep or not.
Click to expand...
Click to collapse
Samsung does bury things....
Settings / Device maintenance, click Battery at the bottom.
Then click the 3 dot menu at the top, and Advanced Settings.
Tap App power monitor (the text, not the toggle).
Tap Put unused apps to sleep (again, the text).
You can set the slider anywhere between 3 days and 7.
I spent several days just wandering through every settings option I could find after I setup the phone. Discovered all kinds of hidden things. Sometimes I can even remember where I saw them.