I've been playing around with Tasker trying to detect when Touchless Controls are summoned to disable Airplane mode(Secure Settings).
Does anyone have a profile for this because I was pretty close to getting it to work but I had a couple of issues. I was able to get it to perform the task when Touchless Controls were active. I would have it disable Airplane Mode, close Touchless Controls and launch Voice Controls but even using the Wait command I wasn't able to get it to launch Voice Controls once the internet connection was established.
I must have been setting the task wrong, I also noticed even though I used the If parameter for Airplane Mode Set, it would close the Touchless controls if Airplane Mode wasn't enabled.
ohmimpotence said:
I've been playing around with Tasker trying to detect when Touchless Controls are summoned to disable Airplane mode(Secure Settings).
Does anyone have a profile for this because I was pretty close to getting it to work but I had a couple of issues. I was able to get it to perform the task when Touchless Controls were active. I would have it disable Airplane Mode, close Touchless Controls and launch Voice Controls but even using the Wait command I wasn't able to get it to launch Voice Controls once the internet connection was established.
I must have been setting the task wrong, I also noticed even though I used the If parameter for Airplane Mode Set, it would close the Touchless controls if Airplane Mode wasn't enabled.
Click to expand...
Click to collapse
I'm still a tasker noob but I'm wondering, how is it knowing that touchless controls are active?
I would think the easiest way, and I'm throwing this out there , is to enable airplane mode when the screen is off and disable it when the screen is on. quick and simple.
ForSquirel said:
I'm still a tasker noob but I'm wondering, how is it knowing that touchless controls are active?
I would think the easiest way, and I'm throwing this out there , is to enable airplane mode when the screen is off and disable it when the screen is on. quick and simple.
Click to expand...
Click to collapse
UPDATE: Ok i figured out what was wrong. Instead of checking AIR is Set, I needed to specify *on* and *off* so
Currently the task is
1 If %AIR Is *on*
2 Secure Settings, Airplane Mode Disabled (There may be a 3 second delay here or on the next step)
3 Kill App Touchless Control
4 Wait X seconds (3-4 seconds seems to be optimal)
5 Load App Voice Search (Can set If %AIR Is *off* may help)
ohmimpotence said:
It was tricky finding it, using the Application Context even when I selected all I wasn't able to initially find Touchless Controls. I searched for it in ES File Explorer and made a copy of it to another folder and launched the properties and suddenly I was able to locate it in Tasker, not sure what actually made it show though.
Your suggestion sounds like a pretty considerable method, I'll give it a shot. I think the main issue is that I'm not able to get enough of a delay between turning Airplane mode off and launching Voice Search because the connection doesn't fully establish yet.
Currently the task is
1 If %AIR Is Set
2 Secure Settings, Airplane Mode Disabled
3 Kill App Touchless Control
4 Wait (tried variable times, it didn't seem to make a diff. I also tried Wait Until %Air ! Set)
5 Load App Voice Search (Tried If %Air ! Set, didn't seem to help)
Click to expand...
Click to collapse
oddly enough I don't even get the option to set airplane mode in secure settings but I see the dilemma you're running into .. in my 'scientific test' I would disable all radios minus the actual cellular. Then from there let the screen sleep. Speak a command and it would light up, kicking on the Bluetooth and Data radios in a instant, then jump straight to the google voice prompt long before wireless was connected, buuuuuut, I had bluetooth, and Mobile data load almost immediately upon the screen lighting up. Do you specifically need wifi or can you use mobile data until wifi is up?
ForSquirel said:
oddly enough I don't even get the option to set airplane mode in secure settings but I see the dilemma you're running into .. in my 'scientific test' I would disable all radios minus the actual cellular. Then from there let the screen sleep. Speak a command and it would light up, kicking on the Bluetooth and Data radios in a instant, then jump straight to the google voice prompt long before wireless was connected, buuuuuut, I had bluetooth, and Mobile data load almost immediately upon the screen lighting up. Do you specifically need wifi or can you use mobile data until wifi is up?
Click to expand...
Click to collapse
You'll need to load Secure Settings App and download Helper under one of the tabs on the top (There is a 4.1+ alternative)
Also to mess with Airplane on 4.2+ firmware you need an Xposed module, just search Airplane.. it says Jellybean but it works fine with KitKat.
I added another tidbit to the task so it will vibrate if I launch Touchless Controls with Airplane enabled, that way I realize not to speak until the second beep. Not sure why but it didn't function well when I added it to the same task so I created another Touchless App context profile and a task that just vibrates but it could just be me.
The only other issue is making sure Super SU settings remembers Secure Settings is permitted, that was an issue when it was slow to recognizing permissions.
I also created an App (using Tasker Factory) out of Airplane Mode enabled task so I can just say Ok Google Now, Launch Airplane (I also have a Screen Off app)
Everything is working good now
How did you end up getting Tasker to recognize whether or not Touchless Controls was active? I'm trying to get Tasker to turn on the wifi, (sometimes I turn it off, then use TC--but it doesn't have data, so it's useless), when TC is called.
natezire71 said:
How did you end up getting Tasker to recognize whether or not Touchless Controls was active? I'm trying to get Tasker to turn on the wifi, (sometimes I turn it off, then use TC--but it doesn't have data, so it's useless), when TC is called.
Click to expand...
Click to collapse
You should just be able to set the profile to run on the TC app (I forget all the specific names, but one of the profile trigger actions is 'apps')
piccit said:
You should just be able to set the profile to run on the TC app (I forget all the specific names, but one of the profile trigger actions is 'apps')
Click to expand...
Click to collapse
I don't have Touchless Controls as an app--just Touchless Controls Settings.
natezire71 said:
I don't have Touchless Controls as an app--just Touchless Controls Settings.
Click to expand...
Click to collapse
I believe that works
piccit said:
I believe that works
Click to expand...
Click to collapse
Not for me
any idea how to set up Tasker to turn on airplane mode at a specific time and turn it off at a specific time? The idea is to have airplane mode turned on at say 1am and turned off at 7am. Anyone?
Hi,
I'm looking for a way to unlock my screen to toggle VPN (Android default VPN since there doesn't seem any decent third-party app out there, which supports IPsec-VPNs) on while on specific wifi network. Everything is working fine except the screen unlock, since Autoinput doesn't work with screen off/locked.
I tried of course the Autoinput-Action "Screen unlock" but this doesn't seem to work on a rooted 7.1: Screen just gets turnd on, Notifications jumping a littl ebit up but then the srceen tunrs of again.
Also tried Secure Setting, but this app seems to be long dead...
Any ide, how to accomplish this? And no, Open-VPN is no option, since the target doesn't support it (it would make things so much easier of course since there is a real tasker integration available).
Thanks!
any idea how to get auto input working?
the unlock action can't be configured, so how should this ever work?
so if I understand correctly you want to turn on the screen and unlock it.
you have managed to turn it on, how about turning off screen lock, and then turn it on? then you should be being straight to home screen.
since you are already using Joao's apps, there is something about disabling lock screen in his Autosettings app I think.
alienyd said:
so if I understand correctly you want to turn on the screen and unlock it.
you have managed to turn it on, how about turning off screen lock, and then turn it on? then you should be being straight to home screen.
since you are already using Joao's apps, there is something about disabling lock screen in his Autosettings app I think.
Click to expand...
Click to collapse
thanks for your answer! you are right about what I'm trying to archiv and I guess the Unlock-Action from AutoInput does soemthing similar since it disables the lock screen completely and I have to set it active again after using this task. The disableing works, but the screen doesn't stay on long enough for AutoInput to perform the intended task – the unlock action doesn't have any configuration options, so basically I have to add something, which ensures the screen is on for a certain amount of time
Anyone know of a way (perhaps via Tasker) to prevent the phone's display from dimming after several seconds when connected to a vehicle's USB port? Thanks in advance!
second this.. i already detect that the phone is connected to the bluetooth in the car and used tasker to set the screen timeout to 30 minutes. but when AA finally starts, it overrides my tasker change and sets the timeout to 15 seconds. i tried using the "Docked" event detection to detect that the phone was placed in "docked car" state. but, the AA application needs to get this event to start, so tasker never gets it. i'm looking into having tasker be the default app that gets the docked car event and then have tasker launch AA... we'll see if that works.
but it would be great if someone else has already figured this out and can post...
schleprock
Hi guys,
I remember on my note 9 with good lock there was a way to enable AOD to turn itself on only when charging. I can't seem to find it now. Any ideas?
Thanks
You can now do this in Bixby Routines. Go to "my routines" then click the plus to create a new one. Set IF to "charging status: charging" and THEN to "Always on display: Show always".
You can also name the routine and select if you want a notification when its active.
Now when your device is charging the AOD will stay on, the setting will revert back to its original state when the routine stops (so when you stop charging).
You can automate a lot of nice things with Bixby routines, like having your phone unlocked when you're home (works a lot more reliably than Google smart lock). Or to enable Do Not Disturb when you're sleeping (auto detected)
nukeclears said:
You can now do this in Bixby Routines. Go to "my routines" then click the plus to create a new one. Set IF to "charging status: charging" and THEN to "Always on display: Show always".
You can also name the routine and select if you want a notification when its active.
Now when your device is charging the AOD will stay on, the setting will revert back to its original state when the routine stops (so when you stop charging).
You can automate a lot of nice things with Bixby routines, like having your phone unlocked when you're home (works a lot more reliably than Google smart lock). Or to enable Do Not Disturb when you're sleeping (auto detected)
Click to expand...
Click to collapse
Oh nice that is cool! Thank you for the tips!
Hey guys,
So I am using GoodLock Routines and I have this routine that sets AOD to 'always show' mode as long as I am charging my phone and I have it set to 'tap to show' while I am not charging the phone. This used to work perfectly before the OneUI 2.5 update. Now when I plug the phone to charge it and the screen is off and locked the AOD shows up for 1 second but then disappears. Can anyone else try this to confirm if it's an issue with the update or it's just me? I also tried to sideload Bixby Routines but it does exactly the same there as well.
If anyone knows a way to show my lockscreen for 1 second when I plug in my phone to charge that could also be a fix as the bug only happens when I plug my phone to charge with the screen off. If I plug it with the screen on and then lock it the AOD remains on as it should.
PS: I am not rooted and won't root so need a non-root method for the screen wake-up part. I tried Tasker with SecureSettings but it's a hit or miss, 1 time it works, then it doesn't.