Hi All,
I just recently rooted my Note5 with ForeverLoco's ROM using ODIN and with Anter47's Kernel. I noticed that after a while, the accessibility services (Settings > Accessibility > Services) which control Tasker and Greenify (among others) all turn themselves off after I manually turn them all back on. I have Clean Master as well as Greenify that kills/hibernates apps but none of the apps in the accessibility page are included on either list. What am i doing wrong?
Thanks in advance!
Viridian
[Can't upload screenshot because I am a noob with less than 10 posts]
Anyone? :/
Viridian95 said:
Hi All,
I just recently rooted my Note5 with ForeverLoco's ROM using ODIN and with Anter47's Kernel. I noticed that after a while, the accessibility services (Settings > Accessibility > Services) which control Tasker and Greenify (among others) all turn themselves off after I manually turn them all back on. I have Clean Master as well as Greenify that kills/hibernates apps but none of the apps in the accessibility page are included on either list. What am i doing wrong?
Thanks in advance!
Viridian
[Can't upload screenshot because I am a noob with less than 10 posts]
Click to expand...
Click to collapse
On the S6 edge, I have a similar problem: the settings remain, but they simply stop working after some time. I have to either restart the phone, or switch them off and back on to get them working again.
Viridian95 said:
Hi All,
I just recently rooted my Note5 with ForeverLoco's ROM using ODIN and with Anter47's Kernel. I noticed that after a while, the accessibility services (Settings > Accessibility > Services) which control Tasker and Greenify (among others) all turn themselves off after I manually turn them all back on. I have Clean Master as well as Greenify that kills/hibernates apps but none of the apps in the accessibility page are included on either list. What am i doing wrong?
Thanks in advance!
Viridian
[Can't upload screenshot because I am a noob with less than 10 posts]
Click to expand...
Click to collapse
hi
I also had similar problem when i had my Note4.I was also rooted etc etc .My workaround was to... ..when i flashed my new updated stock Rom i would quickly enable it ,but as you stated it would/might turn off later , I flashed numerous Lollipop Roms and it was present in all except my last Note 4 Rom.. ...COH4. i found issue to be fixed in this Rom.
The problem ( i supect ) , is that most users don't use this service a lot ,so it goes mostly unnoticed .Very fustrating "bug"
So far i have no issues with my Note5 .
Could be that root interferes with setting or just a Samsung "bug " ????
good luck
willcor said:
hi
(...)
Could be that root interferes with setting or just a Samsung "bug " ????
good luck
Click to expand...
Click to collapse
My S6 edge is not rooted, so it might be a bug on some Samsung roms
I am having the same issue on my find 7. It is very frustrating as I just set up a lot of automation tasks that rely in autovoice being accessibility enabled. Grrr
So from another post around here I found the solution for me and it's very (stupid) easy..
Under settings -> program management, I had to lock certain apps.
I had almost flashed another rom.
Same problem here with Tasker, Nova Launcher and True Phone accessibility services turning off. My phone has Lollipop and is rooted.
Which apps ?
https://lastpass.com/support.php?cmd=showfaq&id=9272
Viridian95 said:
Hi All,
I just recently rooted my Note5 with ForeverLoco's ROM using ODIN and with Anter47's Kernel. I noticed that after a while, the accessibility services (Settings > Accessibility > Services) which control Tasker and Greenify (among others) all turn themselves off after I manually turn them all back on. I have Clean Master as well as Greenify that kills/hibernates apps but none of the apps in the accessibility page are included on either list. What am i doing wrong?
Thanks in advance!
Viridian
[Can't upload screenshot because I am a noob with less than 10 posts]
Click to expand...
Click to collapse
Download Servicely from GP and keep everything turned on!
Im on Phronesis v6.5 rom 5.1 1 on my note 3.
I got the same issue, after reboot all my accessability permissions for my apps are turned off. Apps that need the accessability are Twilight, switch swiftly and a bunch of others including greenify.
Has anybody found a solution to this issue?
PS somehow Nova Launcher seems to keep its accessability ON through reboots!
Samsung and Huawei
Saw the subject is saying [ROOTED] but posting anyway even if this also applies also to non-rooted devices running the stock versions of Android:
On Samsung Galaxy devices (SG 5 and later), check to see if you have App Battery Optimizer in Samsung Smart Manager app enabled. Please disable this as it is known to disable app Accessibility Services: go to Android Settings > General > Battery > look under App Optimization and select Details. Then find the apps in question and turn them off.
For Huawei phones, go to Settings > Apps > Advanced Options > Ignore Optimations and toggle "allow" for your apps that needs to be allowed accessibility permissions.
It happens to me as well. When I use titanium backup to clear apps cache it will shut off all accessibility apps and you will have to turn them back on. I noticed it happens when I use cool master as well.
Hi, it happens to me with Greenify on a Xiaomi redmi note 3 (marshmallow), the only thing that worked for me was: Settings>apps setting>permissions> autostart, and allowing Greenify. It works, even when i went back to optimization feature and leave Greenify to be optimized as it was.
Hi, I am also nor rooted but thought I would chime in as I am also experiencing this annoying issue with my Huawei Mediapad X2 running EMUI 4.0 Marshmallow Stock. Unfortunately, setting Greenify to ignore battery optimizations does not help. Once apps are killed, their Accessibility setting is turned off automatically - very frustrating. Anyone have any other solutions?
The solution given by elpipo22 works for me in a rather different environment, a xiaomi MI 4 with miui. The autostart option here was in Security app -> permissions -> autostart -> choose the apps which should retain accessibility settings.
Hii,
In my case, oppo f1s, i found out one solution
First of all your device should be rooted, the best
way to do that is through resetting firmware to factory or updating to newer oppo system image, then installing custom recovery BIOS or whatever it's name is,
then rooting under Recovery mode using Magisc...
All this is described in some xda-developers forum topic.
But that is not our issue for now,
To prevent accessibility permission to be revoked
from our service or app, we have to go developper,
by browsing SETTINGS >> DEVICE INFO , then clicking about 8 times or more on BUIL NUMBER... now that we
have become DEVELOPPER for good, we go back and then
we navigate towards SETTINGS >> ADVANCED SETTINGS >> DEVELOPPER SETTINGS... then enable DEVELOPPER OPTIONS, open section RUNNING SERVICES, browse for application named SECURITY CENTER, inside whitch we can see 4 running services, then STOP service named
CONTROL_VERIFY_SERVICE (of course on your own risk)
, that is it, now just go to SETTINGS >> ADVACED SETTINGS >> ACCESSIBILITY and enable accessibility for your application and enjoy it.....
I'm trying to get tasker to switch an app on and off depending on if I am home. I can get the app to launched but not to kill it. Have added an exit task but it doesn't seem to work. Tried to get it to make a notification when I get home and leave using the same setup and that works any ideas how to get around this.
Very new to the app so bear with me.
Killing apps is iffy at best. I believe since lollipop, it has to do with SELinux. Google play pulled Taskkill from the play store a long time ago. It's still available though. See this Reddit post.
ktmom said:
Killing apps is iffy at best. I believe since lollipop, it has to do with SELinux. Google play pulled Taskkill from the play store a long time ago. It's still available though. See this Reddit post.
Click to expand...
Click to collapse
That's bit of a bummer. Killing apps at various locations was my main reason for buying the app.
+ Profile -> State -> Phone -> Cell near (at home) SCAN
... + task -> app -> launch app => exit task -> app -> kill app
Similar to this I mananged to enable/ disable (cgi, http get) my ip camera at home.
perhaps it helps.
br
Ulrich
That's what I did on my oneplus 3t but the Three in Touch refuses to switch close down.
Eggstones said:
That's what I did on my oneplus 3t but the Three in Touch refuses to switch close down.
Click to expand...
Click to collapse
Mmmh, I checked with three apps on my device, they also refuses to close.
Go to settings -> about phone and look for SELinux status. I'm sure it says enforcing.
Can't find SElinux in that menu.
You must be stock, so it's enforcing.
I am
I've the same problem, but i've magisk and SElinux permissive. Can not kill an app anymore with Tasker on Nougat (tried with root option checked and unchecked). Tasker is enabled in Magisk superuser.
AutoInput back out of the currently running app.
I ended up with an autoshorcut to a kill task in automate. Works perfectly. It's a shame that this function is not working in Tasker but in others like automate or macrodroid.
Hi,
how do I prevent the Huawei software to stop playing the music once it turns off the screen? I have tried to give the google music app all sorts of permission that explicitly state that it would keep on running in the background.
The only way is to turn off standby mode off?
Settings -> Battery -> App launch -> Disable "Manage automatically" for your music app.
Settings -> Search for "Battery" -> Battery optimization -> Change to "Don't allow" for your music app.
Did that already, it seems there are some other dependencies with the Google Music app, which also need the same settings.
In the end I used another app, and set the right permissions, now my mother has stopped complaining.
I have noticed this same problem. I use my P20 pro as my music phone, and the Play Music app is always getting killed. I'll probably have to just switch to another app or use a different phone.
I have problem with Android Auto on Anroid 10. It looks like AA is preinstalled because in the Settings>Apps & Notifications I can deactivate the application or uninstall updates. However, I don't see the icon in the installed applications. I found that solution should be to turn on Autolaunch option in Additional Settings in the App, but I don't have that option there. Is it possible that this is due to the fact that AA is not officially supported in the Czech Republic? Any idea how to solve it?
https://support.google.com/androidauto/answer/9468382
Here is your answer... I wanted to install the app "android auto for phone screens" like suggested in the support article but got the message" not available in your country"
Funny thing is that on my pixel 3a android 10, its working just fine here in Greece, i just have the system language set to english so that the assistant works....
Edit: here is the apk Android auto for phone screens
Android auto for phone screens solved it! Thanks
I updated my Samsung S21 Ultra (G998B) to Android 12 a couple of days ago. After that the default navigation app is set to Google Maps. I tried to figure out how to reset that to Waze but it can not be changed.
Before Android 12 is was just a matter of setting all apps to "not default" and a pop up appeared to ask you what you wanted to use.
But now it seems that you have to fnd the app in Apps and select the option "set as default". You can also choose the links that have to open the app. But when I want to set my default navigation app to Waze things go wrong. For some reason the links do not stay selected and are deselected as soon as I close the window. So there is no way to set the app as default. I already removed Maps but that doesnt help.
I already contacted Waze Support but the only replies I get from them is a simple answer on how to set default apps in Android 11. It seems they do not read questions.
Does anyone know how to resolve this issue?
I'm using this
Thanks for the reply. Nice app!
But it doesn't work when you want something through a browser. At that point is still goes back to Google Maps, either the app itself or Maps on the internet.