Has anyone that's upgraded to 5.0 noticed issues with profiles running when the phone is locked? I have a profile that runs when I connect to WiFi that only works when I unlock my phone. Also I have an exit task that will only run when I unlock my phone.
Have you made sure tasker is not battery optimized? Settings > battery > 3-dot menu > battery optimization.
ktmom said:
Have you made sure tasker is not battery optimized? Settings > battery > 3-dot menu > battery optimization.
Click to expand...
Click to collapse
Yes. I've also tried Run in Background and setting Reliable Alarms to Always.
willclein said:
Yes. I've also tried Run in Background and setting Reliable Alarms to Always.
Click to expand...
Click to collapse
Maybe keep Wi-Fi on during sleep? Settings > wifi > gear icon.
ktmom said:
Maybe keep Wi-Fi on during sleep? Settings > wifi > gear icon.
Click to expand...
Click to collapse
It's set to Always
willclein said:
It's set to Always
Click to expand...
Click to collapse
Try this and see if it helps.
Tasker > preferences > monitor > net/cell wake screen
What device and OS version?
ktmom said:
Try this and see if it helps.
Tasker > preferences > monitor > net/cell wake screen
What device and OS version?
Click to expand...
Click to collapse
I'll see if that works when I get back in my car. I've also turned on the Run Log in hopes that it may help to shed some light on the issue.
I'm running LineageOS 14.1 on a Moto G5 Plus
Cell/Net Wake didn't do anything
willclein said:
Cell/Net Wake didn't do anything
Click to expand...
Click to collapse
I'm running low on ideas. There is a thing that Pent, tasker's creater flagged and that's the google app can cause interference in getting tasker plugin broadcasts to run in a timely fashion. The bug report. If this is the problem, it should show up in a logcat as a significant wait to execute a broadcast.
I don't know if this is applicable to your task. If it's possible to remove any updates to your google app, maybe that will improve things.
ktmom said:
I'm running low on ideas. There is a thing that Pent, tasker's creater flagged and that's the google app can cause interference in getting tasker plugin broadcasts to run in a timely fashion. The bug report. If this is the problem, it should show up in a logcat as a significant wait to execute a broadcast.
I don't know if this is applicable to your task. If it's possible to remove any updates to your google app, maybe that will improve things.
Click to expand...
Click to collapse
I think the issue is related. I installed a version earlier than he references, and it seems to be working fine now. Not sure what Google changed that is causing the issue. Thanks for pointing me in the right direction!
willclein said:
I think the issue is related. I installed a version earlier than he references, and it seems to be working fine now. Not sure what Google changed that is causing the issue. Thanks for pointing me in the right direction!
Click to expand...
Click to collapse
Glad that helped. If you haven't already, could you go back to the link and star the bug report. The more people doing that, the higher probability Google will take action.
ktmom said:
Glad that helped. If you haven't already, could you go back to the link and star the bug report. The more people doing that, the higher probability Google will take action.
Click to expand...
Click to collapse
Sure thing!
Edit: The u2 update corrected the issue I had seen with Tasker 5
I have the same problem even before Tasker 5. The only way I could get my profiles to run whiles locked. is to add another task, which is run shell > input keyevent 26 > use root yes
Turns out rolling back the Google App did not fix the issue. I was finally able to get it working by running the following from Terminal emulator:
Code:
su
dumpsys deviceidle whitelist +net.dinglisch.android.taskerm
Apparently turning off battery optimization doesn't stop Doze from affecting Tasker. This line will prevent Doze from messing with Tasker.
I have the same problem with tasker and a Galaxy S8! It's driving me mad. I got this problem when I bought the phone, and magically it disapeared... now it returned.
Doze got the process whitelisted and also battery optimization is off , tasker is configured to use reliable alarms, nothing new installed and sistem is not updated (using a custom rom).
When the device is on the table for a period, tasker stop working until I turn on the screen
Is there another solution? the doze is too extreme.
There is a list of things to check on the Tasker usage problems page.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
They marked this bug as "Won't Fix (Obsolete)", but I'm still facing this issue today. I have a profile that enables Bluetooth when I exit my home's Cell Near towers. However, even though the profile is updated the Bluetooth won't turn on until I unlock my phone, which makes the profile useless because I keep my phone in my pocket when I drive off.
Related
Hi all
I am owning the device almost a month, as i am x mate 7 user the only thing Iam missing is the battery life, the rest are ok.
Also i have some bugs i wanted to report may huawei listen!
BUGS :
1. Losing the contacts names in whatsapp some time.
2. Connectivity or paring with bluetooth devices such as head set,car audio and android watch sometime disconnected without notice!
3. Accessibility access services turned off for the application need that access such as Notify, sound profile and Pushbullet.
Please shear your experience also if you have above bugs to confirm or you have any solution.
Thanks
Only get notifications when phone comes out of sleep mode. and sometimes it works fine....
ChristoBotha said:
Only get notifications when phone comes out of sleep mode. and sometimes it works fine....
Click to expand...
Click to collapse
How does one fix this issue?
lucian96 said:
How does one fix this issue?
Click to expand...
Click to collapse
For me a workaround was to make sure the app I want notifications from is running, then press the recents button and find the app on the list, then swipe the app down, it will only move a little way then spring back and also obtains a small padlock icon.
You will probably also need to go to the settings menu and find either protected apps or app settings (depends if you are using the Lollipop version or the Marshmallow beta) and enable the setting for the app which makes it stay awake when the phone sleeps.
Thanks so so much. I try this out
You have tomark the app to run in background...
this is no bug it is an energy saving feature.
the device has a stock white list of apps allowed to run in background.
but normally you re asked if an app should be able to run in background or not.
any app that is not allowed to will be closed immediately in standby
lucian96 said:
How does one fix this issue?
Click to expand...
Click to collapse
I've tried all of the above and still was missing viber notifications. Then I disabled Phone Manager and this sorted out the problem completely.
crubbish said:
I've tried all of the above and still was missing viber notifications. Then I disabled Phone Manager and this sorted out the problem completely.
Click to expand...
Click to collapse
I tried to disable phone manager, but the disable button is not highlighted. What to do?
lucian96 said:
I tried to disable phone manager, but the disable button is not highlighted. What to do?
Click to expand...
Click to collapse
Wouldn't you need to root the phone and then use an app like TitaniamBackup to disable it?
brumgav said:
Wouldn't you need to root the phone and then use an app like TitaniamBackup to disable it?
Click to expand...
Click to collapse
That's the way.
Hey all,
there is probably nothing new for you that the long-running application consuming some bigger amount of power are killed after some time on Huawei P10 (and on other Huawei/Honor phones using EMUI). I use Runkeeper for example and it's always killed after some time (1-3 hours). I tried those:
Settings > Battery > "gear icon" > "Close excessively power-intensive apps" > Off
Settings > Battery > Lock screen cleanup > "Don't close Runkeeper app"
Apps > Settings > Special access > Ignore battery optimization > "Allow Runkeeper app"
I tried to kill "Power Genius" system app. I tried to kill "imonitor" system app but it's started again in a while
I tried to open the recent applications and lock the application by a padlock.
There is nothing more I could try. Still the same issue. So my question is if there is some workaround for that even when I would have to root my phone.
Thanks!!
Try to Open the recent application and click the lock icon to keep the application from being killed.
gm007 said:
Try to Open the recent application and click the lock icon to keep the application from being killed.
Click to expand...
Click to collapse
Thanks for reply. I tried that but it also didn't help :-/. I updated the list of attempts in my first post.
I installed the new update B133 and it's seems to be fine so far. I biked with Runkeeper 4h30m yesterday.
update: nope, it didn't help
gm007 said:
Try to Open the recent application and click the lock icon to keep the application from being killed.
Click to expand...
Click to collapse
Same probleam with me cant fix
It seems that the only workaround for that is to buy a big powerbank and keep a phone charging all the time you are running a power-instensive app. Then the app is not killed.
I hate Huawei. They do not reply to my mails and a support does not work. This bug should be fixed for a phone like P10.
I had a similar problem with Strava. After an hour or so it was killed. Hopefully the issue gets solved in the B164 version.
M1chiel said:
I had a similar problem with Strava. After an hour or so it was killed. Hopefully the issue gets solved in the B164 version.
Click to expand...
Click to collapse
I hope that also. The option to turn off this aggressive behavior is in the settings but it obviously doesn't work. I'm pretty sad that I didn't find any way how to report this bug to Huawei. I just got an anwser from Czech 1st level support that I can complain about it to a seller. I hope that they know about this bug and they are going to fix it. It's already 3rd update and this bug is still there.
Did it get fixed?
I’m currently looking into buying a new phone, and I came across the P10 and fairly quickly this issue caught my attention - I’m not going to buy a phone that automatically kills the programs I want to have running, so does anyone know if this got fixed?
Oreo update
Mavser said:
I’m currently looking into buying a new phone, and I came across the P10 and fairly quickly this issue caught my attention - I’m not going to buy a phone that automatically kills the programs I want to have running, so does anyone know if this got fixed?
Click to expand...
Click to collapse
I don't own P10 anymore but maybe Oreo will fix it https://www.xda-developers.com/huawei-p10-p10-plus-android-oreo-emui-8-0/
If you're like me you're bummed that we have no root and are missing the abilities of root. Namely having the ability to use Xposed to turn off the annoying high volume warning. The following information aims to restore that functionality without root but requires some work but when you're done it's "set it and forget it.". You will never have to do it again. (Unless you wipe your phone)
I have this running on my phone and it works perfectly. I've attached a screenshot showing that the high volume warning is disabled on my phone. Note there is no popup on my volume slider when it's at max, so it's working. This mod uses Tasker and AutoTools. If you're not familiar with them it's OK, the article I'm linking has a step by step process for creating events and tasks.
Once again this isn't my work. I'm just bringing the information to the masses.
All set? Click here to go to the article. Enjoy!
P.S. You will need to open AutoTools and activate the 30 day trial if you don't have the full version. Then grant it permission, If not this won't work. To get the full version just open AutoTools and clock "Get full version".
***********UPDATE 09/15***********
I have confirmed that you will have to manually "test" this procedure first before it survives a reboot.
To do this:
Open tasker.
Click on the Monitor Start event.
Click on the 30 second task.
Click the "play" button in the lower left corner.
The task will begin manually.
If all is well both of the actions will turn green.
If anything turns red something isn't configured correctly.
***********UPDATE 09/17***********
For those that either don't want to or are having difficulty setting up the profiles I have attached them to this post in XML form, Then all you have to do is give the apps permission in ADB as stated in the article and import the profiles.
To import them into Tasker:
Download the file called "Tasker Profiles.zip" from the link below.
Unzip it and save it anywhere on your internal storage. Open up Tasker and disable Beginner Mode in Preferences.
Then, go back to the main screen and long-press on the “Profile” tab up top. You should see a pop-up with one of the options being “Import.”
Tap on that and browse to where you saved the .prf.xml files and select that file to import.
Repeat for the second profile.
Screenshots for this are attached to this OP.
I have also attached a quick demo video to show that this process works perfectly. No popup.
Credit:
Mishaal Rahman
reboot and see if it still works.
I already tried this and after reboot it still prompts the first time.
I've rebooted several times. It works for me. There is a 30 second delay before the task is executed. That is by design.
Compusmurf said:
reboot and see if it still works.
I already tried this and after reboot it still prompts the first time.
Click to expand...
Click to collapse
Try this to see if everything is set up correctly:
Open tasker.
Click on the Monitor Start event.
Click on the 30 second task.
Click the "play" button in the lower left corner.
The task will begin manually.
If all is well both of the actions will turn green.
If anything turns red something isn't configured correctly.
I've attached screenshots of this procedure.
Also something to consider is that if you have any task killers installed or anything that kills tasks on startup you should add tasker to the ignore list of that app.
Hope this helps.
It's configured correctly. Here is the thing. If you pull the value before without using, then pull the value after clicking ok manually, it is NOT 2, it's 0. This was discussed on the s7 and s8 forums. Odd that yours works and dozens of other folks doesn't.
Sent from my SM-N950U using Tapatalk
I dont know what to tell you. It does work for me just fine as my screen shots show. Sorry it's not working for you.
Can you screenshot your configuration screen? Is the value your sending "int" for integer? It shouldn't matter but what Carrier are you using? I'm Sprint.
One other thing to check is under app permissions ensure that AutoTool has the ability to change system settings. Just running the adb shell pm command isn't enough.
Compusmurf said:
It's configured correctly. Here is the thing. If you pull the value before without using, then pull the value after clicking ok manually, it is NOT 2, it's 0. This was discussed on the s7 and s8 forums. Odd that yours works and dozens of other folks doesn't.
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
According to the article 0 is 'not configured' 1 is 'disabled' which is what the value would be when you click ok. 2 is 'inactive'.(How this differs from 'not configured' or 'disabled' I do not know). and 3 is 'enabled'. All depending on your mobile country code. Perhaps changing it to 1 will work for you?
Specifically, we will be modifying the System.Global property audio_safe_volume_state both on boot and periodically so Android will always think you have consented to bypass the warning. This property is defined in AOSP, which we’re reproducing below. There are several states this property can take, ranging from 0-3. 30 seconds after boot or after every 20 hours of continuous music playback, the state is set to ‘0’ or ‘not configured.’ It is then set to ‘1’ for ‘disabled’ or ‘3’ for ‘enabled’ depending on your Mobile Country Code. If you live in the E.U., this property is set to ‘3’ by default but is changed to ‘2’ for ‘inactive’ whenever the user manually bypasses the volume warning. We will be changing the value of this property to the ‘inactive’ state (changing it to ‘disabled’ never worked for me, in case you’re wondering).
Click to expand...
Click to collapse
Hope this helps.
This is already built in...Vibration>Volume>3 dots menu in upper right hand corner> Media Volume Limiter> Turn it off.
Namuh said:
This is already built in...Vibration>Volume>3 dots menu in upper right hand corner> Media Volume Limiter> Turn it off.
Click to expand...
Click to collapse
Confirmed.
Going to Settings -> Sound and Vibration -> Volume -> hit the 3 dot menu -> Media Volume Limiter -> Off works.
I came from a Note 4 with Android 5.1.1 that didn't have this feature. I had no idea Samsung finally caved and added it.
Thank you.
Or not. I rebooted again and it does NOT work anymore. I'm really not trusting Samsung with this. The tasker method works every time. Every reboot. See attached screenshots showing it's turned on (and set to max) and still showing this message. I rebooted several times just in case I had a weird reboot. I'm still getting the popup even with it turned on and the max adjusted to the maximum or even with it turned off completely.
I only wish I was wrong. Thanks for the try though.
Yeah will reset after a boot
https://forum.xda-developers.com/showpost.php?p=73802232&postcount=4
marctronixx said:
https://forum.xda-developers.com/showpost.php?p=73802232&postcount=4
Click to expand...
Click to collapse
Yup...so with tasker I don't have to do any of that. I never have to touch it again. It never comes back.
Thanks again though.
I did learn something from this process. When I re-enabled the tasker even it didn't work when I rebooted. So I hit the "play" button that I mentioned earlier to retest the task and once everything turned green I rebooted and it now works again...after every reboot. So I'll add this to the OP that the task must be "tested" after it's set up in order to get it to work.
Even more interesting is who posted it. Compusmurf was the guy who stated in this thread that this did not work for him. Interesting.
I did get it to work finally. I had another tasker/app that was stepping on it.
Compusmurf said:
I did get it to work finally. I had another tasker/app that was stepping on it.
Click to expand...
Click to collapse
Well I also confirmed that when I disabled it and allowed the popup to come back by rebooting simply re-enabling the tasker even then rebooting did not make it work again. I had to "test" it with the play button to get it to work again. So I'm updating the OP to reflect this.
rawintellect said:
Yup...so with tasker I don't have to do any of that. I never have to touch it again. It never comes back.
Thanks again though.
Click to expand...
Click to collapse
Yeah my point of my post was to show the reason why the built in way doesn't work long term. The tasker way is preferred for those who find the nanny thing an annoyance. :good:
System ui tuněr app should be able to do it
Techvir said:
System ui tuněr app should be able to do it
Click to expand...
Click to collapse
I looked at every single screenshot of System UI Tuner in the play store. I saw no option to disable the high volume warning. Only an option to remove the volume icon which isn't the same thing.
Can you show me a screenshot of it working?
I know this process I linked is a long one and I would really love to be shown a better way but until I am this works for non rooted devices every time.
With the announcement of the new gestures feature for the Pixel 4 I thought: "I should try something similar with Tasker".
Here it is!
It's obviously less precise because you don't have all the extra sensors needed for accurate gestures, but on the other hand it's infinitely more customizable!
Depending on what situation you're in, you'll be able to do lots of different things!
Included are:
Music control gestures
Whatsapp gesture
These are just 2 examples. You can expand on these and do whatever you want with them!
Import the project here!
Enjoy!
Great job Joao!!!
If I can, I would like to share mine too from time ago. Hope this helps yours
https://www.youtube.com/watch?v=_Pfuk7jy4J8
https://drive.google.com/file/d/10pu5BlcN59xFcvZ9P1pav9YGchhaIDiz/view
I'm assuming one would need root for this, yes?
stanleyopar2000 said:
I'm assuming one would need root for this, yes?
Click to expand...
Click to collapse
No root needed at all!
joaomgcd said:
No root needed at all!
Click to expand...
Click to collapse
So I gave it a whirl and i'm not sure if i'm a tasker noob but I could not seem to get it working and the setup was a little too complicated for me : /
It was saying no profiles currently running even though I switched the toggles
stanleyopar2000 said:
So I gave it a whirl and i'm not sure if i'm a tasker noob but I could not seem to get it working and the setup was a little too complicated for me : /
It was saying no profiles currently running even though I switched the toggles
Click to expand...
Click to collapse
I have imported the profiles and can not get it to work neither. Galaxy S10.
stanleyopar2000 said:
So I gave it a whirl and i'm not sure if i'm a tasker noob but I could not seem to get it working and the setup was a little too complicated for me : /
It was saying no profiles currently running even though I switched the toggles
Click to expand...
Click to collapse
mirrik said:
I have imported the profiles and can not get it to work neither. Galaxy S10.
Click to expand...
Click to collapse
What did you try it with? The music one or the Whatsapp one?
joaomgcd said:
What did you try it with? The music one or the Whatsapp one?
Click to expand...
Click to collapse
Not working with both of them. Tried with google play, spotify and whatsup. After import It asked to install AutoInput and AutoNotification which I did and purchased. I allowed all the permissions but maybe some are missing...
mirrik said:
Not working with both of them. Tried with google play, spotify and whatsup. After import It asked to install AutoInput and AutoNotification which I did and purchased. I allowed all the permissions but maybe some are missing...
Click to expand...
Click to collapse
Thanks. Can you verify that you have Tasker 5.8.2?
Also, did you give AutoNotification access to your notifications? Go to Tasker > Menu > More > Android Settings > Notification Access > Check if AutoNotification is enabled.
joaomgcd said:
Thanks. Can you verify that you have Tasker 5.8.2?
Also, did you give AutoNotification access to your notifications? Go to Tasker > Menu > More > Android Settings > Notification Access > Check if AutoNotification is enabled.
Click to expand...
Click to collapse
Yes, version 5.8.2 installed. AutoNotification has an access. All is set as you indicate. Maybe there is an issue with my proximity sensor. I test it by dialing *#77692# and by default it was off. I turned it on and It worked perfectly. On second attempt to dial It was off again. Maybe It is activated on samsung S10 only at performing specific action as making phone call?
I also checked with Sensoroid - Senso info app what sensor are there at my S10. It lists about 52 sensors found including TMD4910 Proximity sensor, Proximity pocket and Palm Proximity Sensor.
mirrik said:
Yes, version 5.8.2 installed. AutoNotification has an access. All is set as you indicate. Maybe there is an issue with my proximity sensor. I test it by dialing *#77692# and by default it was off. I turned it on and It worked perfectly. On second attempt to dial It was off again. Maybe It is activated on samsung S10 only at performing specific action as making phone call?
I also checked with Sensoroid - Senso info app what sensor are there at my S10. It lists about 52 sensors found including TMD4910 Proximity sensor, Proximity pocket and Palm Proximity Sensor.
Click to expand...
Click to collapse
Ah yes, that is possibly the issue! I've had reports from other people that the S10's sensor is not working as it should and only turns on during calls... Unfortunately I can't help with that one Check here for example.
I would love to hear some other ideas that people on this thread used when activating this. I'm not a WhatsApp user, so I'm only basing my experiences through GPM. Any additional apps where this could be advantageous?
Mate 20 lite not working i wasted 3 euros
---------- Post added at 10:13 PM ---------- Previous post was at 10:11 PM ----------
And yes latest version and autonotification enabled
Works for me. Thanks!
Is it posible to control Google Assistant with gestures? Just asking.
correcting my comment, it works perfectly now
great job
I'm new to tasker, and wanted to know if you can trigger the camera to take a photo with this air gesture?
I imported the file from the OP to my OnePlus 6T. This is the only thing I have setup in Tasker, and for the life of me I can not get it to function. An I missing something
phillymade said:
I imported the file from the OP to my OnePlus 6T. This is the only thing I have setup in Tasker, and for the life of me I can not get it to function. An I missing something
Click to expand...
Click to collapse
Start with making sure the proximity sensor is working. A poster above with a Samsung had a problem like that. If you need an app to test it, try Sensors Toolbox
Then look at the tasker log and see if there is any messages there that will help.
Are you trying the WhatsApp or music controls?
ktmom said:
Start with making sure the proximity sensor is working. A poster above with a Samsung had a problem like that. If you need an app to test it, try Sensors Toolbox
Then look at the tasker log and see if there is any messages there that will help.
Are you trying the WhatsApp or music controls?
Click to expand...
Click to collapse
Music.
I'll try your suggestion
I really want to control the camera with this, but I do not think it's possible.
Sensor is working see photo
Sent from my ONEPLUS A6013 using Tapatalk
View attachment 4859291
phillymade said:
Music.
I'll try your suggestion
I really want to control the camera with this, but I do not think it's possible.
Sensor is working see photo
Sent from my ONEPLUS A6013 using Tapatalk
View attachment 4859291
Click to expand...
Click to collapse
I actually installed this to see what was up. On the music version, the profile "Proximity With Music" has three contexts. The AutoNotification context is set to trigger the profile only on notifications from specific apps. You need to check and make sure your app is enabled there. Also, if you don't have AutoNotification installed, it won't work.
As far as taking a photo, that definitely can be done. Here is a Air Camera project. It builds on Joao's project and requires AutoInput to be installed.
It's possible that it won't work out of the "box" due to two things.
1) The "Camera" profile gets triggered based on the Google Camera app opening. This would need to be updated to whichever camera app is used.
2) In the "Handle Camera Gesture" profile entry task, the AutoInput action is expecting the Google Camera app. If that doesn't exist, that action can be updated to operate the shutter button in whatever camera app is installed.
NOTE: In the "Handle Camera Gesture" profile entry task, there is a paused action, "Take Photo". That is actually the Tasker action that will take a photo regardless whether the camera is open or not. It's a bit silly in this application but could be used instead of the AutoInput action.
Is it possible to use tasker to switch on lastpass accessibility toggle? My OnePlus 3t (not rooted, OOS 9.0.4) deactivates it almost on a daily basis. I have switched off battery optimisation for lastpass but the phone turns the toggle off.
Use auto input
Ta. I'll check that out
Hi there. Maybe you can try using the "Custom Setting" action for that. Try using the Magnifying glass in the action with the option to automatically find the setting and see if Tasker can find it. Hope this helps!
joaomgcd said:
Hi there. Maybe you can try using the "Custom Setting" action for that. Try using the Magnifying glass in the action with the option to automatically find the setting and see if Tasker can find it. Hope this helps!
Click to expand...
Click to collapse
I found that by googling but I can't figure out how to make it toggle the switch. The tasker forum talks about reading the accessibility setting but gives no more details than 'brilliant that works'
Eggstones said:
I found that by googling but I can't figure out how to make it toggle the switch. The tasker forum talks about reading the accessibility setting but gives no more details than 'brilliant that works'
Click to expand...
Click to collapse
The easy way is to use the Secure Settings action in AutoTools. That has a direct option for accessibility services. I plan on adding that option to Tasker directly at a later date.
With the Custom Setting action what you should do is read the value, remove or add the needed service from the list, the write the setting.
Ta I'll test that
joaomgcd said:
The easy way is to use the Secure Settings action in AutoTools. That has a direct option for accessibility services. I plan on adding that option to Tasker directly at a later date.
With the Custom Setting action what you should do is read the value, remove or add the needed service from the list, the write the setting.
Click to expand...
Click to collapse
I must be missing something here. Autoapps seems to only control a subscription service. Can't see anything called secure settings when I download it.
Eggstones said:
I must be missing something here. Autoapps seems to only control a subscription service. Can't see anything called secure settings when I download it.
Click to expand...
Click to collapse
I mentioned AutoTools, not AutoApps
joaomgcd said:
I mentioned AutoTools, not AutoApps
Click to expand...
Click to collapse
Mea culpa mea maxima culpa.
I'll try again.
I seem to have manage to get the change state to react to it switching state but need to do some adb to see if it works.
Deleted
joaomgcd said:
The easy way is to use the Secure Settings action in AutoTools. That has a direct option for accessibility services. I plan on adding that option to Tasker directly at a later date.
With the Custom Setting action what you should do is read the value, remove or add the needed service from the list, the write the setting.
Click to expand...
Click to collapse
I can now get the profile to switch on but I cannot figure out how to get the secure setting to change the toggle.
Both profile and task shows up as green but nothing seems to happen.
Eggstones said:
Mea culpa mea maxima culpa.
I'll try again.
I seem to have manage to get the change state to react to it switching state but need to do some adb to see if it works.
Click to expand...
Click to collapse
No problem at all Let me know how it goes!
joaomgcd said:
No problem at all Let me know how it goes!
Click to expand...
Click to collapse
Not well at all. The profile activates but nothing is actually changed.
Eggstones said:
Mea culpa mea maxima culpa.
I'll try again.
I seem to have manage to get the change state to react to it switching state but need to do some adb to see if it works.
Click to expand...
Click to collapse
Eggstones said:
Not well at all. The profile activates but nothing is actually changed.
Click to expand...
Click to collapse
Does it work if you run the task manually?
joaomgcd said:
Does it work if you run the task manually?
Click to expand...
Click to collapse
No. If I click on the task I don't get an error or the green dot. Instead I get a grey play arrow Infront of the task.
In the profile window both the profile and task shows up as green.
Eggstones said:
No. If I click on the task I don't get an error or the green dot. Instead I get a grey play arrow Infront of the task.
In the profile window both the profile and task shows up as green.
Click to expand...
Click to collapse
That means that Tasker doesn't seem to be able to communicate with AutoTools. Do other AutoTools actions work?
To make sure Tasker and the AutoApps run in the foreground please check here: https://tasker.joaoapps.com/userguide/en/faqs/faq-problem.html#00
joaomgcd said:
That means that Tasker doesn't seem to be able to communicate with AutoTools. Do other AutoTools actions work?
To make sure Tasker and the AutoApps run in the foreground please check here: https://tasker.joaoapps.com/userguide/en/faqs/faq-problem.html#00
Click to expand...
Click to collapse
Sorry to be a pain but I cannot find the run in foreground setting on my OnePlus 3t.
Eggstones said:
Sorry to be a pain but I cannot find the run in foreground setting on my OnePlus 3t.
Click to expand...
Click to collapse
Did you check here?
joaomgcd said:
Did you check here?
Click to expand...
Click to collapse
Yep. All those seeking are correctly set. It's the tasker foreground setting I cannot find. Tried googling it but the links I found doesn't match what I see in tasker.