Related
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
Hi!
Ok, I'm attaching 2 screenshots where the hibernated list shows an excessively big amount of wakeup time. If I understand correctly, the apps in this list are apps that are to be hibernatized later on since they were awaken by a service or another app, and the timers correspond to the total amount of time that said apps have been awaken in the background. Am I wrong? If so, please let me know.
atomomega said:
Hi!
Ok, I'm attaching 2 screenshots where the hibernated list shows an excessively big amount of wakeup time. If I understand correctly, the apps in this list are apps that are to be hibernatized later on since they were awaken by a service or another app, and the timers correspond to the total amount of time that said apps have been awaken in the background. Am I wrong? If so, please let me know.
Click to expand...
Click to collapse
If I understand correctly, you have chosen these apps for hibernation but they are not being hibernated.
Which version of Greenify are you running and in which mode? Do you have the donation pack and Xposed? Have you enabled Greenify in Device Administrator?
IIRC, you don't need to enable Greenify in Device Administrator. Isn't that to just allow hibernating from a shortcut on the screen?
No. It is for immediate screen off after auto hibernation, as per the description. But I have noticed that not enabling it sometimes interferes with hibernation itself.
Thank you @tnsmani and sorry for the delay in my reply. I'm using latest stable 2.8 I think? In Boost Mode, with Xposed enabled and donation package. I wasn't aware of the Device Adminitrator component, but I just enabled it. Will see how it goes.
And disable 'shallow hibernation' in Greenify if you have such an option in your version.
Yes, I do. I had disbaled that one or two days after it was first introduced. For some reason I felt Shallow Hibernation is less effective, at least my battery didn't seem to last the same vs normal hibernation.
Hi,
when using aggressive doze on a rooted Nexus 4 with Android 6.0.1 in my GPS tracking app (I tried several), even though whitelisted, the tracking stops after a few minutes.
The apps still show as tracking thus I suspect the GPS itself gets killed and provides no signal/values anymore.
Is it a bug or a feature?
Thanks for the great work
DarsVaeda said:
Hi,
when using aggressive doze on a rooted Nexus 4 with Android 6.0.1 in my GPS tracking app (I tried several), even though whitelisted, the tracking stops after a few minutes.
The apps still show as tracking thus I suspect the GPS itself gets killed and provides no signal/values anymore.
Is it a bug or a feature?
Thanks for the great work
Click to expand...
Click to collapse
Uninstall Greenify and check.
If I disable aggressive doze it works.
If I uninstall the app too of course.
This is a limitation of the doze mode itself enforced by Android. I'm afraid there's no way to workaround that.
A new Tasker plug-in is added in 2.9.5 beta 1 to toggle Aggressive Doze. Hope this could do some help here.
Ah no problem, I thought it might be something like this. I'll just disable aggressive doze while using the app.
The tasker plugin would do this automatically for me, did I get this right?
oasisfeng said:
This is a limitation of the doze mode itself enforced by Android. I'm afraid there's no way to workaround that.
A new Tasker plug-in is added in 2.9.5 beta 1 to toggle Aggressive Doze. Hope this could do some help here.
Click to expand...
Click to collapse
Shouldn't it be enough to disable "Doze on the go" to maintain the gps sensor on?
I have this same problem, and the only way to allow a foreground sports tracking app to access the gps data is to disable both "Agressive doze" and "Doze on the go"...
daniel.mota said:
Shouldn't it be enough to disable "Doze on the go" to maintain the gps sensor on?
I have this same problem, and the only way to allow a foreground sports tracking app to access the gps data is to disable both "Agressive doze" and "Doze on the go"...
Click to expand...
Click to collapse
No. As someone tested before, the stock Doze also disables GPS.
Hello,
I had the same behaviour. I tested something this morning : added to whitelist my navigation app + LocationServices + FusedLocation.
And while I was on the road, the gps worked till I arrived. In the agressive doze log I see that the device did'nt went in Doze during that time.
Don't know if this is directly related, I'll give it another try tonight.
Didn't work tonight, lost gps signal. Something else prevented doze this morning.
Will give a try to the beta and the toggle.
Any news on the subject? I get GPS signal lost while using maps...
RFrancis said:
Any news on the subject? I get GPS signal lost while using maps...
Click to expand...
Click to collapse
I'm now using the beta + Tasker to prevent doze when my navigation apps are on. Works great.
madxxcow said:
I'm now using the beta + Tasker to prevent doze when my navigation apps are on. Works great.
Click to expand...
Click to collapse
Could you export the profile
Here is an example for Google Maps.
madxxcow said:
Here is an example for Google Maps.
Click to expand...
Click to collapse
You should probably re-enable aggressive doze with an exit task. This does not seem to be one of those system settings that will auto restore when the task terminates. Also note that this profile will not trigger if Maps or your GPS app is in the background. I am debating whether aggressive doze is worth the hassle.
I've been having the same issue for a while. I use Locus Maps to record tracks on airplanes (so it may run for 12hrs) and it turns off GPS. Sometimes its hard to tell if its lost because of Doze or I simply lost the signal.
Also, it is plugged into a power source (charging) so I believe Doze should be disabled while charging.
I see above mention of "Tasker". What is this?
eng3 said:
I've been having the same issue for a while. I use Locus Maps to record tracks on airplanes (so it may run for 12hrs) and it turns off GPS. Sometimes its hard to tell if its lost because of Doze or I simply lost the signal.
Also, it is plugged into a power source (charging) so I believe Doze should be disabled while charging.
I see above mention of "Tasker". What is this?
Click to expand...
Click to collapse
The simple solution is to avoid aggressive doze which is tagged 'experimental' and is known to cause some odd device/radio/app behaviors.
Davey126 said:
The simple solution is to avoid aggressive doze which is tagged 'experimental' and is known to cause some odd device/radio/app behaviors.
Click to expand...
Click to collapse
I'm sorry, I should have clarified. I was broadening to Doze itself as I thought I read that it will also disable GPS (but not as fast or "aggressively").
My behavior has been a little different. I notice that if I run maps navigation at the same time as recording my track, there is no issue. but if I just record my track, then it not be able to prevent GPS from stopping.
Perhaps this should go in another forum, I'm just not sure which
eng3 said:
I'm sorry, I should have clarified. I was broadening to Doze itself as I thought I read that it will also disable GPS (but not as fast or "aggressively").
My behavior has been a little different. I notice that if I run maps navigation at the same time as recording my track, there is no issue. but if I just record my track, then it not be able to prevent GPS from stopping.
Perhaps this should go in another forum, I'm just not sure which
Click to expand...
Click to collapse
Try running a GPS Status app (example) concurrent with your tracking app. Aside from helping to keep the GPS 'awake' most have a variety of useful features and functionality.
I have tried that but it does not seem to work. I'll have to check the GPS status options to see if there's something for keeping it awake.
I have noticed that if I run Navigation (not just Maps) in parallel, then the GPS will stay awake.
eng3 said:
I have tried that but it does not seem to work. I'll have to check the GPS status options to see if there's something for keeping it awake.
I have noticed that if I run Navigation (not just Maps) in parallel, then the GPS will stay awake.
Click to expand...
Click to collapse
- as previously noted make sure Aggressive Doze is disabled as it can break cross-app/component communications
- also add you tracker app to 'white list' of you haven't done so already
- good chance Google Maps (any navigation app) is using wakelocks to keep GPS active
- assume all is well when you disable Greenify
- if true you many need to step away from Greenify or consider another app with similar functionality like Force Doze
I use Greenify with shallow hibernation.
I noticed that various apps like Facebook, Messenger, Whatsapp and Tapatalk sometimes are offline when I try to use (to refresh a page, to check a status or a message, etc.). After minutes and casually they return online. I'm sure that it is not a connection problem, and if I substitute shallow hibernation with normal hibernation this problem does not exists. So I think that it is a shallow hibernation bug. This happens with all the last versions of Greenify, beta and stable.
Do you have any feedback?
My system is a rooted Samsung Galaxy S5 stock 6.0.1.
rogxd said:
I use Greenify with shallow hibernation.
I noticed that various apps like Facebook, Messenger, Whatsapp and Tapatalk sometimes are offline when I try to use (to refresh a page, to check a status or a message, etc.). After minutes and casually they return online. I'm sure that it is not a connection problem, and if I substitute shallow hibernation with normal hibernation this problem does not exists. So I think that it is a shallow hibernation bug. This happens with all the last versions of Greenify, beta and stable.
Do you have any feedback?
My system is a rooted Samsung Galaxy S5 stock 6.0.1.
Click to expand...
Click to collapse
I experience something similar with Youtube, Maps and Firefox which i greenified: sometimes, when i resume them from hibernation, they can't go online. The connection is ok and other apps can connect but not those ones. Try to hibernate them again manually with the greenify button, then reopen them and see if they can connect.
Did you also disable any broadcast receiver for the problematic apps?
Are you still experiencing this problem after one year?
i'm on a sony stock 6.0.1 rom
Real question why use shallow hibernation? What problem/behavior are you attempting to address? Although native to Android 6+ it seems this mode is automatically utilized by normal/regular/standard doze as needed. I don't see a benefit to using it globally but obviously individual situations vary.
Additional background: https://greenify.uservoice.com/knowledgebase/articles/828357
Davey126 said:
Real question why use shallow hibernation? What problem/behavior are you attempting to address? Although native to Android 6+ it seems this mode is automatically utilized by normal/regular/standard doze as needed. I don't see a benefit to using it globally but obviously individual situations vary.
Additional background: https://greenify.uservoice.com/knowledgebase/articles/828357
Click to expand...
Click to collapse
I'm answering this a month later but would like to point out that for me Shallow Hibernation is amazing.
I have a device with plenty of memory for my usage, so I don't need the app to be wiped out of memory every time, just to be set as inactive.
For example, I found that Spotify is a great candidate for Shallow Hibernation.
Whenever I'm listening music on my computer, my phone has a tendency to stay awake because of Spotify Connect.
However if I shallow hibernate it, it won't keep the phone awake but still be kept in memory for me to use whenever I want. The same things goes for Maps, Youtube, and some games.
I’ve put an “Hibernate and Sleep” shortcut at homescreen and works really great.
Hi,
I recently installed Greenify on my Pocophone F1 /MIUI 10.3 on which I have already Tasker.
For Tasker, I have removed all battery restrictions so it is never optimized and it is fine. If I stop it manually, then for I don't know which reason accessibility and notification services get disabled so I have to enable them again.
The problem since I installed Greenify is that although Tasker is not part of the apps to hibernate, after some time when the screen is off, the same services get disabled on Tasker, exactly as if Tasker was forced to stop. So I am wondering why Greenify acts like this and how to prevent it? Isn't there any kind of whitelist?
I have not changed any default setting in Greenify.
Any idea what is happenning?
Thx.