How to access Settings when Settings is already open

[Danny DeLoach]

I have created an action that calls up the Airplane Mode page in the Settings app.  If the Settings app is closed when the action runs, then it works properly.  However, if the Settings app is already open, then the action just displays the Settings app as the app last appeared (e.g. on the Display page or the Sound page) without moving to the Airplane Mode page.  How do I make the action call up the Settings app and move to the Airplane Mode page, regardless of what page the Settings app was previously on?

Thanks.

[Pent]

Maybe try a Go Home action first (with a small delay after).

I'll try see if I can reproduce this, and if so fix it.

Pent

[Danny DeLoach]

Thanks for the suggestion, Pent. The only 'Go Home' action I'm familiar with is the AutoInput Global Action 'Home'. I tried starting the task with that action (including a small delay), but I got the same results.

Another thing I've tried is preceeding the 'Settings | Airplane Mode Settings' action with the 'Settings | All Settings' action. The 'Settings | All Settings' action will call up the Settings app and cause it to display the All Settings page, regardless of what page the Settings app was previously on. However, the 'Settings | Airplane Mode' action still only open the Settings app to whatever page it was on last (in this case, the All Settings page).

[Jay M]

Maybe this is how your already doing it i cant see it mentioned but have you tried an intent? you should be able to open the aeroplane settings screen with a send intent action put this in the first field

android.settings.AIRPLANE_MODE_SETTINGS

and change the target to activity leave all the other fields as they are.

On Fri, 3 Mar 2017, 21:54 Danny DeLoach, <deloa...@gmail.com> wrote:

Thanks for the suggestion, Pent. The only 'Go Home' action I'm familiar with is the AutoInput Global Action 'Home'. I tried starting the task with that action (including a small delay), but I got the same results.

Another thing I've tried is preceeding the 'Settings | Airplane Mode Settings' action with the 'Settings | All Settings' action. The 'Settings | All Settings' action will call up the Settings app and cause it to display the All Settings page, regardless of what page the Settings app was previously on. However, the 'Settings | Airplane Mode' action still only open the Settings app to whatever page it was on last (in this case, the All Settings page).

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

--

Jay M ︻芫══一

[Danny DeLoach]

Thanks, Jay M. That solved the problem. For the sake of helping me better understand how Tasker works, can you explain why my original approach failed, while the 'send intent' approach worked? With Much Thanks, Danny.

[Jay M]

I dont know what your approach was the send Intent approach worked because thats what its for. I cant think how to word it but heres another one android.intent.action.DIAL this will open the dialer and if you put tel:4444 in the data field it will even open the dialer with the number already filled in why? because thats what its for. It works because if you were to view the code for this in a real Android app it would probably look similar to this.

Intent i = new Intent();
i.setAction(Intent.ACTION_DIAL);
i.setData(Uri.parse("tel:4444"));
startActivity(i);

As you can see how a dev would open the dialer is really no different to how we do it in Tasker. In Tasker theres an action field a data field an extra field basically everything we need to send an Intent. Only difference is Pents made it a lot easier for us to do what we need to do.

On Sun, 5 Mar 2017, 15:24 Danny DeLoach, <deloa...@gmail.com> wrote:

Thanks, Jay M. That solved the problem. For the sake of helping me better understand how Tasker works, can you explain why my original approach failed, while the 'send intent' approach worked? With Much Thanks, Danny.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[Danny DeLoach]

OK. Thanks. This helpful.

The way I had previously created the action was to tap the 'plus', then tap 'Settings', then tap 'Airplane Mode Settings'.

But now I see the power of the 'intent' method. So, I'll use that in the future. Thanks, again, for your help. I really appreciate it.

[Jay M]

No idea tbh :/

Theres a link to a load more intents and some info on how to use them in the thread titled send intent/activity so might be worth a look at that.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[Danny DeLoach]

Thanks!

[Pent]

I couldn't reproduce this problem, so I'm glad you've found a workable alternative.

Pent

[Pent]

I couldn't reproduce this problem, so I'm glad you've found a workable alternative.

Correction: I could reproduce this and have removed the offending flag, think it
was there to work around an Android bug in pre-history. At least, I hope that's
the only reason it was there :-)

Pent

[Danny DeLoach]

Thanks for checking into it.