Phone: PLK_L01
Build: PLK-L01C432B121
The EMUI seems to be very quick to kill apps running in background which is mostly a great thing (too many apps are running background service for nothing).
Unfortunately, some times, it's useful.
I'm using Tasker but it's regularly killed by system (sometimes it last 2 days before being killed and some times only few hours)
Normally, the problem can be avoid in parameters with "protected apps" which normally allow you to select some apps that can not be killed. I've added Tasker to it but it still being killed...
I've also tried to put Tasker as a system app, not working too.
Tasker is also configured as "running in foreground" to avoid being killed, it's also not working.
Did some of you have the same problem with Tasker or another app htat need to run constantly in background ?
I've been using tasker for the last couple of weeks since I got my phone with no problems.
It's on the protected list with only one other app.
Sent from my PLK-L01 using XDA Free mobile app
I have been having issues on Tasker although are slightly different to the OPs. I also have Tasker set as protected and running in the foreground and I can see that it is running in the Taskbar. However, I have found that the tasks aren't being triggered at the times when they are supposed too. It seems that they will only trigger if I disable and then reenable Tasker each time.
The tasks that I have setup were imported from my old Nexus 5 where they were working fine, they are also the same tasks that I was using on a Moto G. Therefore I'm sure that the issue is with the phone and not Tasker itself.
Does anyone have any idea what could be causing this issue?
---------- Post added at 02:57 PM ---------- Previous post was at 02:43 PM ----------
dws199xda said:
I have been having issues on Tasker although are slightly different to the OPs. I also have Tasker set as protected and running in the foreground and I can see that it is running in the Taskbar. However, I have found that the tasks aren't being triggered at the times when they are supposed too. It seems that they will only trigger if I disable and then reenable Tasker each time.
The tasks that I have setup were imported from my old Nexus 5 where they were working fine, they are also the same tasks that I was using on a Moto G. Therefore I'm sure that the issue is with the phone and not Tasker itself.
Does anyone have any idea what could be causing this issue?
Click to expand...
Click to collapse
I've just noticed in the Tasker log that the TaskService keeps getting stopped, I presume that this causing the scheduled tasks not to trigger. But I don't know what could be causing the service to stop, I'm not running any app killers and just the stock power manager
I had a problem with protected apps being killed with all versions of the firmware until I installed b170, which solved it.
Try installing b170 and see if it solves your problem too.
Snackiz said:
I had a problem with protected apps being killed with all versions of the firmware until I installed b170, which solved it.
Try installing b170 and see if it solves your problem too.
Click to expand...
Click to collapse
Thanks for your suggestion however I think I now know that the issue is being caused by the Power Saving mode being set to "Smart", I have switched it back to "Performance" and I can now see that the tasks are being triggered as expected. So I guess that there is an issue with the "Smart" setting where it is still killing Protected apps. BTW I'm running B121
dws199xda said:
Thanks for your suggestion however I think I now know that the issue is being caused by the Power Saving mode being set to "Smart", I have switched it back to "Performance" and I can now see that the tasks are being triggered as expected. So I guess that there is an issue with the "Smart" setting where it is still killing Protected apps. BTW I'm running B121
Click to expand...
Click to collapse
That's great
My problem persisted even after I set the power saving mode to performance.
I used tasker with honor 6, nexus 4 and now honor 7. the only mobile that doesn't work is honor 7, even with last version . Last week finally I uninstalled tasker with 4 months triying to work. the substitute is automateit and automate
Still in b140 and the problem seems to have been solved b itself...
Thank you all for your answers
Having the exact problem with my Huawei phone.
Model: SCL-L21
EMUI: SCL-L21C432B130
edit: I was wrong fortunately. It was not about Tasker and/or EMUI. I was using the "Last Cell" location Profile in Tasker and it didn't work properly so I thought it means Tasker is getting killed by EMUI battery manager (it's really aggressive). Fact is, Huawei is just good at switching cell towers rapidly, choosing between 3G, 2G or 4G while accepting a call or in other circumstances. This was the problem, Tasker is still protected from EMUI battery manager (2 days +).
Just add Tasker to the list of protected apps (PhoneManager - Settings - Protected Apps)
Related
So, my emails arrive late, the stock messaging app doesn't show new texts unless you scroll down when you open it (!!!), replacement sms apps have been wonky as well,... In general things just aren't updating correctly. I've made sure to go through the power management menus to allow apps to do what they need to but no go.
Anyone else had this problem? The battery life, size, and tethering capabilities are nice, but I just put my sim back in the Note 2 as those problems are making using this too unreliable.
Same problem here
I also have this problem, and I believe several people mentioned this in different places, so following is what I have done so far, not sure if this help your case, I am still monitor my phone since I just change my settings a few days back.
Standard steps includes:
("the app" below mean the application you have problem receive notification)
1. Set the app as protected in the Battery Saving settings.
2. Allow the app run in background.
3. In Wifi advanced settings, set to "always" during sleep.
4. Set power saving mode from "Smart" to "normal" .
I still have problem after all above steps, so I have make following attempt:
1) Disabled/Freeze "Phone Manager" system app.
2) Another app is "Power Genie", this app still run even I freeze it. So I have to use Root Explorer to rename them
under /system/app, rename HwPowerGenieEngine3.apk to HwPowerGenieEngine3.apkk, and rename HwPowerGenieEngine3.odex to HwPowerGenieEngine3.odexx
then reboot to recovery, clear cache, and dalvik cache, then reboot.
Again I am still testing this... HTH.
Just want to write a update, I think this resolved app got killed issue in my phone.
I think I found what was messing with my texts. I had mysms installed to backup and send texts to my N7. There's no way to select the stock app as the default messaging app. I ended up deleting mysms and only downloading it when I switch the sim into my Note 2.
The bigger problem is with Spotify. Even with it saved as a protected app it turns off about two minutes after the screen turns off, rendering the app almost useless. Wtf??
Mine works idk. it has to be a setting. hmm. you sure you have wifi on when screen is off. it is it's own setting on this phone
My notifications seem to quit working at times and I notice when using root explorer that my ext SD isn't showing
I wonder why my phone is working with notification (I even have ac display working to turn the screen on for 10 seconds when receiving a text message or email from work) I also use Spotify every day since I'm a premium member. No issues at all. I'm even able to change the volume and skip track and play and pause from my LG Tones
---------- Post added at 09:14 AM ---------- Previous post was at 09:13 AM ----------
make sure Spotify is set to run in background not just a protected app otherwise when you shut your phone off it will end the app. that might be your problem.
xordos said:
I also have this problem, and I believe several people mentioned this in different places, so following is what I have done so far, not sure if this help your case, I am still monitor my phone since I just change my settings a few days back.
Standard steps includes:
("the app" below mean the application you have problem receive notification)
1. Set the app as protected in the Battery Saving settings.
2. Allow the app run in background.
3. In Wifi advanced settings, set to "always" during sleep.
4. Set power saving mode from "Smart" to "normal" .
I still have problem after all above steps, so I have make following attempt:
1) Disabled/Freeze "Phone Manager" system app.
2) Another app is "Power Genie", this app still run even I freeze it. So I have to use Root Explorer to rename them
under /system/app, rename HwPowerGenieEngine3.apk to HwPowerGenieEngine3.apkk, and rename HwPowerGenieEngine3.odex to HwPowerGenieEngine3.odexx
then reboot to recovery, clear cache, and dalvik cache, then reboot.
Again I am still testing this... HTH.
Click to expand...
Click to collapse
I can't modify or remane the two files
caymal said:
I can't modify or remane the two files
Click to expand...
Click to collapse
Yeah root is required to rename system apps.
xordos said:
Yeah root is required to rename system apps.
Click to expand...
Click to collapse
yeah, there's not root for the moment for my model (mt2l05 4.4.2 EMUI 3)
but, did it work ?
it works in my phone. But you know, some mate2 owners don't have this issue at all.
May be an issue with APN settings. What I had when I first got the phone and what my settings are now seem much better especially when breaking up data and MMS into two different it independent panes. Once set to fast.t-Mobile.com and APN type default,supl,hipri the second selectable APN labeled for MMS as APN type and everything else identical and all hand offs via WiFi or mobile data are seamless. I was having various network issues prior to changes made to build.prop and default APN and once phone went to sleep it would not get alerts or transition to active/awake very well.
bob60626 said:
So, my emails arrive late, the stock messaging app doesn't show new texts unless you scroll down when you open it (!!!), replacement sms apps have been wonky as well,... In general things just aren't updating correctly. I've made sure to go through the power management menus to allow apps to do what they need to but no go.
Anyone else had this problem? The battery life, size, and tethering capabilities are nice, but I just put my sim back in the Note 2 as those problems are making using this too unreliable.
Click to expand...
Click to collapse
Yup yup, same here. I'm using Nova Launcher + TeslaUnread Plugin. Also stopped using my previous favorite 3rd party SMS replacement, Chomp, and now I'm back on stock SMS. The plugin seems very stable to me, I get a little number bubble on my SMS app on the homescreen, even if the notification doesn't come through on the status bar. Not exactly a fix, but it's been a decent workaround for me.
Huawei Ascend Mate2 problem solved
xordos said:
it works in my phone. But you know, some mate2 owners don't have this issue at all.
Click to expand...
Click to collapse
I was able to get my phone to connect with my surge hr Fitbit. Just wasn't reading directions correctly. The Surge hr is a nice product, now if I could only squeak out more time between charges. Roughly 3 days is the most I get between charges. I turn off the notifications when not needed.
I haven't posted in a while, but I've run into a problem.
I recently got the Aplus GV18 smartwatch. The watch requires an app called BTNotification to be on my phone; the app pushes notifications from my phone to the watch. However, if I leave the phone for any length of time then the app turns off and I don't get notifications.
I downloaded the app on another phone of mine and it stayed connected overnight. So it isn't the watch. I've tried just about everything I've found. I have:
-Changed the battery mode to "Normal"
-Disabled "Phone Manager" and the "Power genie" thing
-Fiddled with the # of background processes in the Dev options
-Changed the WIFI to stay on even with the screen off
-Other things in various threads
Any ideas??
Gir357 said:
I haven't posted in a while, but I've run into a problem.
I recently got the Aplus GV18 smartwatch. The watch requires an app called BTNotification to be on my phone; the app pushes notifications from my phone to the watch. However, if I leave the phone for any length of time then the app turns off and I don't get notifications.
I downloaded the app on another phone of mine and it stayed connected overnight. So it isn't the watch. I've tried just about everything I've found. I have:
-Changed the battery mode to "Normal"
-Disabled "Phone Manager" and the "Power genie" thing
-Fiddled with the # of background processes in the Dev options
-Changed the WIFI to stay on even with the screen off
-Other things in various threads
Any ideas??
Click to expand...
Click to collapse
Did you make it a Protected App?
I did, it didn't work.
I ended up disabling the entire "Phone Manager" app.
Sent from my MT2L03 using XDA Free mobile app
Huawei rooting
xordos said:
Yeah root is required to rename system apps.
Click to expand...
Click to collapse
Yes - notification problems actually cost me a job.... I received a phone message notification nearly 2 days after it was left on my phone.
I'm going back to the forum to to follow unlock instructions after getting the unlock code just today. I want to root the phone.
I am having problems with disappearing navigation keys. Once I go
to an app, I cannot get out of it. I have to constantly restart my phone. Do you have a solution?
@oasisfeng Disclaimer: Apologies in advance -- this is a long one!
I've been experiencing an odd issue, as of late, running the 2.6.1 stable on my Nexus 5 (LP 5.1 / LMY47I, Cataclysm ROM). I'm using Root Mode (donation version), without Xposed.
This issue is slightly difficult to explain. By observing my SuperSU logs, I've noticed that a seemingly random and previously Greenified app will be continually hibernated every 30 minutes or so, each time my device goes idle for a prolonged period (such as while I'm working, or asleep). Curiously, the apps in question will change during each idle period, largely excluding the possibility that this is simply the case of a rogue app. The various apps are usually quite innocuous, and never known to (randomly) wake while my device is in use -- last night's was MX Player, for instance.
(Edit: Upon further observation, it seems that the random app in question is often among the last to have been manually woken/used before entering the next deep sleep period, in case it helps.)
Unfortunately, I've yet to successfully return to my device in time to catch any possible wake-up paths. I do question, however, if the apps are actually being woken in the first place (as opposed to Greenify simply "re-hibernating" apps that are already sleeping), as the issue will seemingly disappear entirely when auto-hibernation is disabled -- according to my SU logs, at least.
The only potential user-side cause that I can think of is that I had previously cut-off the Google Play Services wake-up path for Maps (neither G.P.S. nor any important system apps were ever actually hibernated). I've since re-attached the wake-up path, and de-Greenified Maps. Although that's probably unrelated, it's pretty much the "riskiest" thing I've done with Greenify on this device. I normally just keep a number of seldomly used user apps hibernated, and don't have any known offenders (like Facebook) on my device.
I've since removed and re-added each of my hibernated apps, as well as reinstalled Greenify (and its donation package) several times. I should note, as well, that I have not experienced any noticeable battery drains. Unfortunately, I'm unable to confirm whether or not this occurred before updating to Greenify 2.6.1 stable -- I've simply only observed this behavior since the Play Store rollout.
I've attached an example screenshot of my SuperSU log (taken after a 7 hour idle period), just so you can better visualize the pattern (the actual content of each log is simply the usual force stop message). Apologies for not providing anything more helpful at this time; please let me know if there's anything you'd like to see.
Thank you, for both your time and continued support for this wonderful app.
I am experiencing the same issue as above
"(Edit: Upon further observation, it seems that the random app in question is often among the last to have been manually woken/used before entering the next deep sleep period, in case it helps.)"
this is definitely the case with me. I am quite certain the apps are not actually being woken up every 30 minute period. It feels like greenify is running the command needlessly.
I am in the beta channel and using root mode
@oasisfeng I also experiencing this issue. On BetterBatteryStats, I have partial wakelocks every 30 minutes and it seemed greenify is causing this.
I'm on XtreStoLite 2.1 - LP TouchWiz based ROM running Greenify 2.6.1 on Root mode with Donation Package
It's not an issue, but a protective design, to ensure the apps occasionally woken during the idle period being put back to hibernation again.
First of all, this is not a wake-up periodic timer, that means if your device fell in sleep for more than half a hour, it will never wake up the CPU until other apps wake it. So, it consumes little battery juice, which you could hardly perceive.
I'm planning to add latest wake-up information for all apps including the hibernated ones.
Hi, guys, do you use Tasker for periodic hibernation/wakeup task with Greenify?
I dont. I have tasker installed, but havent set it up to do anything yet. Cheers
oasisfeng said:
Hi, guys, do you use Tasker for periodic hibernation/wakeup task with Greenify?
Click to expand...
Click to collapse
Thanks for your replies! In my case, I haven't been using any hibernation/wake-up tasks (although Tasker is installed).
Regarding your first response, I'm not entirely sure what you mean about the protective design. Apologies if there's any confusion, but if you're suggesting that Greenify simply ensures that woken apps remain hibernated, the puzzling thing is that these particular apps will not wake at all when auto-hibernation is disabled.
Auto hibernation/Manual hibernation
@oasisfeng
I have the same issue as the others above but noted your explanation for the same. I am running stock Lollipop 5.1 in my rooted Nexus 4 with Greenify 2.6.2 beta 3 running in Root mode with donation features.
One more issue which is more serious (in my opinion), is auto hibernation and manual hibernation. Some system apps like Google Services Framework and Google Play Services do not get autohibernated occasionally. Likewise even if the manual shortcut Hibernate+lockscreen is used, these remain running sometimes, even after half an hour of sleep. However, there is no noticeable impact on battery. (I have brought the battery loss down to 0.3 to 0.7% per hour while sleeping, from 6 to 7% without Greenify. Thanks for that) As the others reported, SU logs indicate that every half hour Greenify hibernated these apps though they are present as running continuously when Greenify is opened. My suspicion is that though they are actually hibernated, Greenify does not correctly reflect the status.
This is more of a report than a complaint to keep you and others informed.
tnsmani said:
@oasisfeng
I have the same issue as the others above but noted your explanation for the same. I am running stock Lollipop 5.1 in my rooted Nexus 4 with Greenify 2.6.2 beta 3 running in Root mode with donation features.
One more issue which is more serious (in my opinion), is auto hibernation and manual hibernation. Some system apps like Google Services Framework and Google Play Services do not get autohibernated occasionally. Likewise even if the manual shortcut Hibernate+lockscreen is used, these remain running sometimes, even after half an hour of sleep. However, there is no noticeable impact on battery. (I have brought the battery loss down to 0.3 to 0.7% per hour while sleeping, from 6 to 7% without Greenify. Thanks for that) As the others reported, SU logs indicate that every half hour Greenify hibernated these apps though they are present as running continuously when Greenify is opened. My suspicion is that though they are actually hibernated, Greenify does not correctly reflect the status.
This is more of a report than a complaint to keep you and others informed.
Click to expand...
Click to collapse
jacknicholson said:
Thanks for your replies! In my case, I haven't been using any hibernation/wake-up tasks (although Tasker is installed).
Regarding your first response, I'm not entirely sure what you mean about the protective design. Apologies if there's any confusion, but if you're suggesting that Greenify simply ensures that woken apps remain hibernated, the puzzling thing is that these particular apps will not wake at all when auto-hibernation is disabled.
Click to expand...
Click to collapse
jacknicholson said:
@oasisfeng Disclaimer: Apologies in advance -- this is a long one!
I've been experiencing an odd issue, as of late, running the 2.6.1 stable on my Nexus 5 (LP 5.1 / LMY47I, Cataclysm ROM). I'm using Root Mode (donation version), without Xposed.
This issue is slightly difficult to explain. By observing my SuperSU logs, I've noticed that a seemingly random and previously Greenified app will be continually hibernated every 30 minutes or so, each time my device goes idle for a prolonged period (such as while I'm working, or asleep). Curiously, the apps in question will change during each idle period, largely excluding the possibility that this is simply the case of a rogue app. The various apps are usually quite innocuous, and never known to (randomly) wake while my device is in use -- last night's was MX Player, for instance.
(Edit: Upon further observation, it seems that the random app in question is often among the last to have been manually woken/used before entering the next deep sleep period, in case it helps.)
Unfortunately, I've yet to successfully return to my device in time to catch any possible wake-up paths. I do question, however, if the apps are actually being woken in the first place (as opposed to Greenify simply "re-hibernating" apps that are already sleeping), as the issue will seemingly disappear entirely when auto-hibernation is disabled -- according to my SU logs, at least.
The only potential user-side cause that I can think of is that I had previously cut-off the Google Play Services wake-up path for Maps (neither G.P.S. nor any important system apps were ever actually hibernated). I've since re-attached the wake-up path, and de-Greenified Maps. Although that's probably unrelated, it's pretty much the "riskiest" thing I've done with Greenify on this device. I normally just keep a number of seldomly used user apps hibernated, and don't have any known offenders (like Facebook) on my device.
I've since removed and re-added each of my hibernated apps, as well as reinstalled Greenify (and its donation package) several times. I should note, as well, that I have not experienced any noticeable battery drains. Unfortunately, I'm unable to confirm whether or not this occurred before updating to Greenify 2.6.1 stable -- I've simply only observed this behavior since the Play Store rollout.
I've attached an example screenshot of my SuperSU log (taken after a 7 hour idle period), just so you can better visualize the pattern (the actual content of each log is simply the usual force stop message). Apologies for not providing anything more helpful at this time; please let me know if there's anything you'd like to see.
Thank you, for both your time and continued support for this wonderful app.
Click to expand...
Click to collapse
I have a similar problem
yesterday I was using Wakelock Detector and I found out this:
Today I flashed a new Rom and all I did was configuration stuff and install some basic apps such as facebook, twitter etc. and greenify (not xposed module) greenifying NOT system apps
After 3h it caused screen wakelock during 7 minutes
BTW I amb on stock lollipop 30b
Is greenify incompatible? is supersu broken?
Boopie11 said:
I have a similar problem
yesterday I was using Wakelock Detector and I found out this:
Click to expand...
Click to collapse
First, learn some etiquette. Quote only what is relevant or simply say that you have the same issue as others. Don't go about quoting multiple full posts.
Second, you have opened a separate thread for the same issue. So what is the point of posting the same here?
Third, though your attachments are not visible, your description gives the impression that your issue has no relevance to the posts you have quoted.
The issue appears to have been resolved with version 2.6.2. As always, my thanks go to @oasisfeng -- although if I may ask, did you manage to find the source of the issue, or is this a coincidence?
jacknicholson said:
The issue appears to have been resolved with version 2.6.2. As always, my thanks go to @oasisfeng -- although if I may ask, did you manage to find the source of the issue, or is this a coincidence?
Click to expand...
Click to collapse
Yes, your report is very precious for me to analyze this issue. It was fixed in an earlier beta version before the final release of version 2.6.2. Thanks very much!
oasisfeng said:
Yes, your report is very precious for me to analyze this issue. It was fixed in an earlier beta version before the final release of version 2.6.2. Thanks very much!
Click to expand...
Click to collapse
I was wondering whether Greenify had stopped working, after installing 2.6.2.
Now I know the reason. So this is why I don't see those repeat hibernations.
Thank you, @oasisfeng!
Hi, Greenify keeps losing access to the accessibility service for some reason. It happens after a few minutes of using the phone, not even a reboot is required to get it unticked again. Then when I try to hibernate+lock screen again, it says that it requires the service for automation to work.
Phone: Huawei Mate 7
System: KitKat 4.4.4
Greenify: latest version
Root? No (Greenify set on non-root mode)
Accessibility activated for Greenify? Yes but keeps getting unticked all the time and asks me to enable automation again and again!
Greenify device administrator? Yes
Donation package? Yes.
Anyone?
Have you noticed any clue on when and what caused the stop of accessibility service?
If you device memory is running low, it may be killed by Android system for more memory for foreground app, especially when playing large game.
oasisfeng said:
Have you noticed any clue on when and what caused the stop of accessibility service?
If you device memory is running low, it may be killed by Android system for more memory for foreground app, especially when playing large game.
Click to expand...
Click to collapse
No it does it all the time, after a few minutes usually. If I lock the screen within a minute or two, it works fine, it later than that, the hibernation service is normally turned off already.
Other Info
Any other updates on this issue? I was running Greenify on my Galaxy S5 with no issues. I just changed over to an S6 Edge and now I'm getting the same problem with Greenify losing its Accessibility permissions. No rhyme or reason for when it happens. I'm not running any big applications or games. I have a few other apps that need Accessibility authorization and those never seem to lose their access like Greenify does.
Same Problem on my new Galaxy S6 edge. Any help to solve the problem would be greatly appreciated.
This can solved by removing Greenify from Protected Apps or in the case of non Huawei phones by disabling battery optimisation for greenify or the app in question.
On my phone gets it often after I kill the any application with /long press/back button. Rooted, CM13
this happen as well with OOS 3.2.1 on OnePlus 3
if you decide to clear recents and the memory as well, it will straight away losing the accesibility access..
Is there an established reason for this?! Reinstalling and add power-saving exception doesn't seem to being helpful.
Issue started after update to android 8. On previous versions never had a tiny problem.
Sent from taptalk
The (my) m10 pro has extreme memory management and several of my apps that need to stay in mem, running in the background are kicked out by either oreo or emui all the time.
This makes this phone much less fun to use than my mate 9 where all these apps just ran fine.
The following apps are stopped all the time:
Garmin Connect (communicates with my Fenix f5)
Cambridge connect that connects to my (music) amplifier
Adguard (adblocker)
The problem is that with the garmin and cambridge apps the Bluetooth and wifi connects are also gone and thus communication stops.
My colleague has the very same problem so there must be more people out there with this isse.
Anybody else have this problem cause I think Huawei has a serious issue here.
I have the same issues. Apps that I want to keep running are stopped regardless the different settings to keep them running.
What I do see is that only the Sonos app stays in the background. That app gets reported as still being active and stopping it requires a force stop action. So maybe Garmin Connect should investigate the Sonos solution.
Yes, saw the same. Antivirus apps also play nice and keep running. Nevertheless I think Huawei should be the one playing nice and stop the app killing madness to save 2 minutes battery life...
The Mate 9 had similar issues when it first launched but it was fixed quick. Any idea how to bring this message to their attention?
I'm gonna try it through HiCare anyway.
did you try to add it to "ignore batteryopti..." just do a search in settings
Hi, tried it and it seems to be better now. Lets see what happens over time. Thanks!
It's kinda solved now but after about 12 hours all the background apps I mentioned were killed somehow. So it improved but it's not yet perfect...
Greetings,
I have an Infinix Note 3 Pro updated to Nougat and rooted. I'm not new to rooting and you can consider me a power user. I have many rules programmed via tasker and various tools that must be active at all times like everywhere launcher. As you know, Android as of Marshmallow introduced Doze, which is the most frustrating system I've ever come across. It's intended purpose mercilessly kills any background running task once the phone is idle. Yes there are supposed to be settings that can exempt certain apps, but it does not work. Additionally , the accessibility option also keeps going off for selected apps like tasker and everywhere launcher. IN fact all accessibility settings revert back to the off state after some time.You set it now, in a little while it's back to off. In short, apps like tasker, and sidebar launchers continue to disappear when Doze kicks end.
I've search the net for over a year and have tried every method I've found to solve this but the problems are persistent.
Can anyone please tell me how to solve this problem which has made my phone frustrate me for so long. I find it hard to believe that Android designed Doze to work the way it has worked against me.
Thanks for reading this long rant
iomari