This app was mentioned in 39 comments, with an average of 1.72 upvotes
Autoinput can simulate almost any inputs to other apps. Autovoice adds Google Assistant integration.
Intents are more technically capable than what Apple offers, and the stronger automation possible in Android wins by far.
I've got my phone turning off the sound during meetings automatically. Shortcuts isn't capable of that at all. Tasker can trigger tasks based on events in other apps (and it doesn't even need those apps to talk to it, it can monitor them via plugins if necessary).
Meanwhile everything in Shortcuts requires either a trigger by the app you're currently running, or manual activation, or at best an iBeacon can generate a prompt - but if still always require manual action to run.
Tasker is set and forget. It runs without interaction.
And you're forgetting that Tasker tasks also can be bundled and shared.
In fact they can be packaged as apps:
https://play.google.com/store/apps/details?id=net.dinglisch.android.appfactory
Also, the developers that has apps both on iOS and Android will quickly realize how much more powerful Intents are. Don't expect Android to lag behind on that point.
Oppure quelli che installano plugin di altre app che ovviamente non funzionano senza, e che lasciano 1 stella perché "nn funziona nn si puo nemmeno aprire, pessima!!", ad esempio app factory, plugin per Tasker.
Today I discovered a Tasker Add On called "Tasker App Factory" that let's you to quicly create an Android app based on Tasker Task. Then you can use Google Assistant to say "Start my app". It gives you a massive amount of flex ability. This video explains it. https://www.youtube.com/watch?time_continue=1&v=Z9LX5Xp7lSM Android app is here: https://play.google.com/store/apps/details?id=net.dinglisch.android.appfactory
Actually, OP can make it into an app really easily https://play.google.com/store/apps/details?id=net.dinglisch.android.appfactory&hl=en
I don't believe that's possible directly...
There is however an option to Exclude from recent apps when using the Launch App action.
A workaround could be to always launch the app through Tasker. You could set it as a shortcut and hide the original app if your launcher supports it. You could also export the app using <strong>Tasker App Factory</strong> to replace the original in the app drawer.
Have you tried exporting it with the Tasker App Factory? I haven't played with it but I believe you can export any task as an APK. Combined with AutoWear you might get something similar.
Sadly my 360 died a few months ago so I haven't been able to play with this stuff much but they might be worth a look.
In your OP you stated that you have Tasker 5.6. Was that incorrect?
Tasker 5.6 would need App factory 5.6, which can be found here.
IDE stands for Integrated Development Environment. In simple terms, its the software developers use to make softwares with ease. And yes <em>Tasker app factory</em> is on the play store. Its by the same developer who made tasker happen.
Edit : Added link
When you Export a Task, Profile or Project, you can export it as an APK to install on other devices. You just need AppFactory
https://play.google.com/store/apps/details?id=net.dinglisch.android.appfactory if you want to export APKs. Admittedly, it can be challenging to make standalone APKs, as you need.to take into account FireOS doesn't have all the features vanilla AOSP does.
For the Patreon, subscribe to João's Patreon channel. More here; https://tasker.joaoapps.com/patreon.html
Could you export the task using Tasker app factory?
>I'm not sure what's a kid app
For your use case, you can long click a Task and export it as an Application (an independent apk), after installing it, it will do the Task assigned to it when launched.
Needs Tasker App Factory provided by dev. Also info/guide.
This would be the basic content of the Task-
Task: Test mv
A1: Ask Permissions [ Required Permissions: android.permission.READ_EXTERNAL_STORAGE android.permission.WRITE_EXTERNAL_STORAGE ]
A2: Run Shell [ Command: mv command Timeout (Seconds): 0 Use Global Namespace: On ]
Set an icon for the Task, press export as App, give it a package name, check advanced configuration and then set Target Android Version
to 28. Now press Back Button and the export will start.
If your launcher supports it — though, I don't know any launcher ...
So you have to use Tasker App Factory to "export" your profile/task based, i.e. standalone, app.
It may not be possible to add to app drawer like you said. However, there maybe an alternative if you are willing to use Tasker. Basically you will need to create a task using Tasker and export it as an apk via Tasker App Factory. I have no experience with Tasker app factory but if you are feeling adventurous, here's the link: https://play.google.com/store/apps/details?id=net.dinglisch.android.appfactory
Click on the project tab > Export > As App
In order for the above to function you'll have to have the Tasker App Factory installed.
:D
>The only way this could possibly be cooler is if I didn't have to choose between which phone was client & server, and could send commands back and forth between both phones!
Go for the following path:
>- We can "compile" (with Tasker App Factory) a Child App that We can use as independent UDP server, that will send (via intent) received commands to the resident Tasker.
>Receive Intents From UDP - Server [Profile]
Profile: Intent Received - From UDP Sever Restore: no Event: Intent Received [ Action:tasker.ACTION_CMD Cat:None Cat:None Scheme:* Mime Type:* ] Enter: Intent Received - From UDP Sever Abort Existing Task A1: Flash [ Text:Received command: %cmd Long:On ]
Than install Your Server on both devices.
> I think it's paid but I'm not sure. I bought it years ago when NFC was neat. > > Pm me If you get it installed. I'll show you my simple setup.
It's not useful to me, as I leave GPS on all the time, but you could create an app to do that with Tasker App Factory so that /u/blueboy1980 doesn't need to buy it: https://play.google.com/store/apps/details?id=net.dinglisch.android.appfactory
As much as I love nostalgia, I think perhaps updating the screenshots from Tasker v1.1 in the App Factory Play Store listing may be a good idea :D
What's new
Compatibility with new Tasker Version
What's old
Tasker Screenshots in the Play Store from when dinosaurs still roamed the earth.
Tasker can build APKs from Projects etc. Use Appfactory.
This way, you can build a project to do all that you need, export it as an app and install it on the non GApps device.
You can export any Profile/Task/Scene to XML by long -clicking its name to highlight it, then choose 3-dot menu > Export > XML To Storage
and then choose where on your device you want to save the XML file.
If it's able to be exported as its own Application/APK there will also appear an option to Export "As App". You just need to have Tasker App Factory installed as well, in order to export something from Tasker to be its own application.
I'm trying to figure out if Tasker can do specifically what I want. I haven't bought it yet because I don't want to if it doesn't suit my needs. If I understand correctly you can create standalone apps from Tasker projects with the use of Tasker App Factory. Would you be so kind to compile your project and share the app to make sure it is what I'm looking for? I would be most thankful..
This bothered me as well. My solution was to create apps from the tasks using Tasker App Factory.
I couldn't use widgets, because I wanted to put them inside a folder on my home screen.
I think if you export the Profile as an actual app (via <strong>Tasker App Factory</strong>) it may detect the device boot quicker. You'll just have to try it out.
Another alternative is to just use an app like <strong>Startup Manager</strong> to handle the launching of your app.
The Tasker App Factory Plugin can be used to turn Tasker profiles, projects, and tasks into stand alone, self contained applications. The playstore link. ...Please Note: I am a Bot.. To report errors or request additions, message /u/letestaccount
Yeah. It's a relatively easy one for Tasker. EDIT: If you don't already have Tasker, there's a free trial on their website if you want to test it out first.
In Tasker, you would create a Task with the action "Mic Mute", and choose "Toggle". In order to make it easier to tell the status of your mic, create a second action "Notify". Under text you need to include the variable %MUTED. This is an Android variable that tells you whether the mic is muted or not. You can customize the other fields to your liking.
Then in bxActions, there's the option of choosing "Launch tasker task" under Apps.
You can also use Tasker to create an app from a task using Tasker App Factory. If you did that, you could launch it directly with Bixby Voice, and you won't need a 3rd party app.
Perhaps Tasker with the Tasker App Factory are enough for your needs?
This would be great. In the mean time, remember there's tasker app factory.
I mean when you export a Task or Project as an App using AppFactory
Tasker can, yes.
When you make an action, project or Profile, export as App. Will need https://play.google.com/store/apps/details?id=net.dinglisch.android.appfactory to complete.
Hi. Are you sure you correctly installed App Factory?
If so, try to uninstall and reinstall it.
Thank you! :) It's this app: https://play.google.com/store/apps/details?id=net.dinglisch.android.appfactory
If you're not using global variables with them then you could isolate them to a project and make a kid app via Tasker App Factory.
If you are using global variables with them then you could still isolate them as above, passing variables via intent extras or file writes/reads (or a few even less reliable methods). Or (also) you can maybe add those contexts (or testing methods) directly onto the profiles/tasks that use them.
Or, there's one other way to do it that I use for the states like you do. Here's an example.
Profile: "myPOWER=none"
State: Power [ Source Any Invert yes ]
State: Variable Value [ Conditions %myPOWER
neq none
]
Task: Variable Set [ Name %myPOWER
To none
] If [ %myPOWER
!~ none
]
Profile: "myPOWER=AC"
State: Power [ Source AC Invert no ]
State: Variable Value [ Conditions %myPOWER
neq ac
]
Task: Variable Set [ Name %myPOWER
To ac
] If [ %myPOWER
!~ ac
]
What happens is that, if the phone is on battery (%myPOWER=none) and I plug it in, the second profile activates (source AC, %myPOWER doesn't match ac), changes the variable, then deactivates (because the %myPOWER doesn't match ac is no longer true). The drawback is that you need one profile for each state, but the benefit is that it doesn't stay in your profiles list. (BTW, the condition for the task actions isn't really needed, but I think I had it there for some debugging, just didn't remove it.) Note also that I didn't name the tasks, and the profiles arguably don't need to be named either (I got them from an old project by /u/unklemike).
Installed App Factory?
https://play.google.com/store/apps/details?id=net.dinglisch.android.appfactory
Now you can export your tasks, profiles and projects as APKs.
And here I was going to be clever...
Yeah, you can see me struggling somewhere trying to consolidate all the above into a Tasker App Factory thingy.