Can tasker app factory apps run shell commands at boot?

[Kent Christopher]

I created a Tasker profile which would run a single shell command at startup to configure a network setting (something which can't be done through init.d or other boot scripts on the stock ROM of this device). It works fine when being run directly from Tasker. 

I decided to experiment with the App Factory and make it as an app. I uninstalled Tasker, installed the app and launched it once, but noticed that after reboot, the app didn't appear to be doing it's job (running the command at boot). 

Is this a built-in limitation of App Factory apps to prevent malware creation? 

[Pent]

I created a Tasker profile which would run a single shell command at startup to configure a network setting

How exactly ? Please export the profile description (not XML) via long-click, export, and post it here.

>Is this a built-in limitation of App Factory apps to prevent malware creation?

Not intentionally :-)

Pent

[Pent]

Presume you're using Tasker 4.3u4 BTW ?

Pent

[Kent Christopher]

Version 4.3u4, yes. Here's the profile description:

Profile: Boot (3)
Event: Device Boot
Enter: Wi-Fi Name (2)
A1: Run Shell [ Command:setprop net.hostname OptimusF3 Timeout (Seconds):0 Use Root:On Store Output In: Store Errors In: Store Result In: ] 

[Scott Miller]

Check your superuser app. SuperSU, for example, blocks root requests during boot by default.

Scott

--
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 http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[Pent]

Check your superuser app. SuperSU, for example, blocks root requests during boot by default.

 Also that you've granted root permission to the new app.

Pent

[Kent Christopher]

The problem was my own newb-ness: I exported the task as an app, rather than a project containing both the profile (Device Boot) and task. 

Having corrected that, it does work now, and no need to change the default superuser settings to allow su permission at boot. 

However, I notice that the app stays resident in memory, which is really unnecessary given it only needs to do this one simple task at boot. I tried adding a Stop action at the end of the task list. I've been searching without success... is there a proper way to exit a task/profile so that the resulting Tasker App will unload from memory?

[Brandon Horwath]

is there a proper way to exit a task/profile so that the resulting Tasker App will unload from memory?

According to:
http://tasker.dinglisch.net/userguide/en/appcreation.html

Most child apps include a service which constantly monitors for events. If you know that you don't need to monitor events anymore (in-between app launches) you can use the Disable action in the Tasker category to stop it.

It will be automatically started again next time the app is launched.

Hope this helps.

[Kent Christopher]

Thanks for that. With some tweaking using Wait actions, that did the trick.