Tasker doesn't detect root on my device?

[Charles Mann]

Recently picked up a Moto G5 Plus and rooted it with Magisk 16.0. It's running the stock Motorola Android 7.0 US ROM.

Installed Tasker 5.1m and then tried to setup some "kill-app" tasks with root-access.

But for some reason, Tasker isn't requesting root accessing and not killing the app when these tasks are run.

Other apps like CatLog and AdAway have requested (and was granted) root access in Magisk Manager.

Is there a way to force Tasker to request root access when killing apps?

Thanks!

[Duck Redbeard]

Try setting the default response to root request to allow?

[João Dias]

This is on my bug-todo-list, thanks!

On Tue, Apr 10, 2018 at 1:33 AM, Duck Redbeard <duckre...@gmail.com> wrote:

Try setting the default response to root request to allow?

--
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+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[Charles Mann]

Hi.

Do you mean enable the "Use Root" option? That is enabled on all of my "Kill App" tasks but I never get the root prompt from Magisk.

It's like Tasker doesn't realize that the device has been rooted.

Is there a test or action that I can use to force Tasker to ask for root access?

Thanks!

P.S. The same scripts appear to work fine on my Nexus 6P (and Tasker requests root) but that was rooted with SuperSU so I was thinking perhaps Tasker doesn't like Magisk on the Moto G5 Plus?

[João Dias]

What I meant is, I'm going to fix Tasker root recognition so it works with Magisk :)

--

[Kenny]

Think this page can help you:

https://groups.google.com/forum/#!topic/tasker/nzyqfAqQe48

I manually added this #modversion line at the top of build.prop file, and it immediately prompted SuperSu to grant Tasker root access.

Give it a shot.

--
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.

[João Dias]

Root is now fixed on the latest beta :)

On Wed, Apr 11, 2018 at 1:40 PM, Kenny <kwashin...@gmail.com> wrote:

Think this page can help you:

https://groups.google.com/forum/#!topic/tasker/nzyqfAqQe48

I manually added this #modversion line at the top of build.prop file, and it immediately prompted SuperSu to grant Tasker root access.

Give it a shot.

On 4/9/2018 6:13 PM, Charles Mann wrote:

Recently picked up a Moto G5 Plus and rooted it with Magisk 16.0. It's running the stock Motorola Android 7.0 US ROM.

Installed Tasker 5.1m and then tried to setup some "kill-app" tasks with root-access.

But for some reason, Tasker isn't requesting root accessing and not killing the app when these tasks are run.

Other apps like CatLog and AdAway have requested (and was granted) root access in Magisk Manager.

Is there a way to force Tasker to request root access when killing apps?

Thanks!

--
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+unsubscribe@googlegroups.com.

Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.

[André Jeromin]

Not for me.. Root detection doesn't worked on my Huawei Mate 10 pro Magisk root v16

[joaomgcd]

Did you enable Superuser in Magisk? It's working for everyone else...

[André Jeromin]

Yes I did. For me the beta 5.1.5b worked I think

joaomgcd <joao...@gmail.com> schrieb am Do., 12. Apr. 2018, 17:56:

Did you enable Superuser in Magisk? It's working for everyone else...

--

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.

[João Dias]

If you go into Magisk  -> Superuser does Tasker appear there and is enabled?

On Thu, Apr 12, 2018 at 6:08 PM, André Jeromin <a.jer...@gmail.com> wrote:

Yes I did. For me the beta 5.1.5b worked I think

joaomgcd <joao...@gmail.com> schrieb am Do., 12. Apr. 2018, 17:56:

Did you enable Superuser in Magisk? It's working for everyone else...

--
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+unsubscribe@googlegroups.com.

Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

--

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+unsubscribe@googlegroups.com.

[André Jeromin]

João Dias <joao...@gmail.com> schrieb am Fr., 13. Apr. 2018, 16:59:

If you go into Magisk  -> Superuser does Tasker appear there and is enabled?

On Thu, Apr 12, 2018 at 6:08 PM, André Jeromin <a.jer...@gmail.com> wrote:

Yes I did. For me the beta 5.1.5b worked I think

joaomgcd <joao...@gmail.com> schrieb am Do., 12. Apr. 2018, 17:56:

Did you enable Superuser in Magisk? It's working for everyone else...

--
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.

--
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.

--
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.

[Charles Mann]

Awesome. The beta works!

Thanks a bunch for the quick fix.

On Thursday, April 12, 2018 at 7:45:57 AM UTC-7, joaomgcd wrote:

Root is now fixed on the latest beta :)

On Wed, Apr 11, 2018 at 1:40 PM, Kenny <kwashin...@gmail.com> wrote:

Think this page can help you:

https://groups.google.com/forum/#!topic/tasker/nzyqfAqQe48

I manually added this #modversion line at the top of build.prop file, and it immediately prompted SuperSu to grant Tasker root access.

Give it a shot.

On 4/9/2018 6:13 PM, Charles Mann wrote:

Recently picked up a Moto G5 Plus and rooted it with Magisk 16.0. It's running the stock Motorola Android 7.0 US ROM.

Installed Tasker 5.1m and then tried to setup some "kill-app" tasks with root-access.

But for some reason, Tasker isn't requesting root accessing and not killing the app when these tasks are run.

Other apps like CatLog and AdAway have requested (and was granted) root access in Magisk Manager.

Is there a way to force Tasker to request root access when killing apps?

Thanks!

--
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.

--
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.

[Charles Mann]

Whoops. Spoke too soon.

Root detection is working but when I run the action, the app that I'm trying to kill isn't terminating.

In the Kill App action, when I enable "Use Root", Tasker does a root check and I get a root toast from Magisk.

But when I run the Action, I don't get the root toast that I expected to see and the app isn't killed.

Are there any debugging steps that I can take?

Thanks!

[João Dias]

Do other root actions work correctly for you? Airplane mode for example?

To unsubscribe from this group and stop receiving emails from it, send an email to tasker+unsubscribe@googlegroups.com.

[Charles Mann]

Interestingly the Airplane mode toggle works. I see the Magisk toast and Airplane mode is toggled when I trigger the action.

But I don't see the Magisk toast when I try to trigger the Kill App action.

Very odd.

[João Dias]

Interesting. Does running a shell command (like settings list global for example) with root work for you? Do you get the result in a variable?

To unsubscribe from this group and stop receiving emails from it, send an email to tasker+unsubscribe@googlegroups.com.

[Charles Mann]

Hi.

Yes, I was able to run a "settings list global" shell command and store the output in a user variable. I got the root toast when running the shell command as well.

Would output from logcat help track down this issue?

[João Dias]

Can you please try again with the latest beta? :) 5.1.7b

Thanks!

To unsubscribe from this group and stop receiving emails from it, send an email to tasker+unsubscribe@googlegroups.com.

[Charles Mann]

Hi. Just tried the latest beta and I'm now seeing the root toast when I trigger the Kill App action.

But oddly the app that I'm trying to kill isn't killed?

[João Dias]

Do other root actions work correctly for you?

To unsubscribe from this group and stop receiving emails from it, send an email to tasker+unsubscribe@googlegroups.com.

[Charles Mann]

Hello,

Sorry for the delay!

I updated to 5.1.8b but the Kill App action still isn't working.

I can use Airplane Mode toggle though.

What other root action should I test?

Thanks.

[Christophe]

Hi,
Some app are hard to kill using the default way.
Have you give a try to run a shell command like "am force-stop com.tomtom.gplay.navapp", I'm using it without any issue to close TomTom app, just replace package name.
Christophe

[João Dias]

Does that shell command work for you consistently? :) Maybe I should make it work that way in Tasker itself.

--
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+unsubscribe@googlegroups.com.

[Christophe]

Hi Joao,

Yes it does !

I'm using it for several month now without any issues

Christophe

Le mercredi 2 mai 2018 14:21:55 UTC+2, joaomgcd a écrit :

Does that shell command work for you consistently? :) Maybe I should make it work that way in Tasker itself.

On Wed, May 2, 2018 at 1:12 PM, Christophe <cge.a...@gmail.com> wrote:

Hi,
Some app are hard to kill using the default way.
Have you give a try to run a shell command like "am force-stop com.tomtom.gplay.navapp", I'm using it without any issue to close TomTom app, just replace package name.
Christophe

--
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.

[João Dias]

Ok, changed it for the next release :) Thanks!

To unsubscribe from this group and stop receiving emails from it, send an email to tasker+unsubscribe@googlegroups.com.

[Charles Mann]

Another late update. :)

Thanks for the change in the default way that Tasker kills apps.

It's now working much better.

Thanks!

[João Dias]

Great!