• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Tasker Project works great, App Factory app does not work, HELP PLS

F

famgadget

Newbie
I have built a Tasker project, the goal is to monitor a specific app in the foreground. When it is closed I create a Scene that gives the user time options before the app is re-launched. There are about 6 profiles, 8 tasks, one scene and 4 variables. All parts reside in a Project.

As mentioned it works great in Tasker, but I would like to create the app. In using the APP Factory, the app does not work. The Profiles do not appear to activate, even if I add Profile Status = on in the task that the App Factory requires to build the App.

In testing this further I created a simple Project folder with; Profile (if camera app is started run Task (Task Sets Camera Profile Status to on then Displays Scene) (Scene shows button to close Scene). Created App, when icon is pressed the task runs. When camera is started, nothing. Not rooted. Please, what am I missing?

Is this beyond the scope of App Factory? Is there something I am missing. Any ideas would be great.
 
Last edited:
Welcome to android Forums.

I have found the approach to Tasker is to start out small and slowly expand.

Can you create a small section of the Project (one Profile and associated Task(s)) that works in Tasker and fails when made into an app? If you then post it here perhaps we can help determine the problem/solution.

... Thom
 
Thom said:
Welcome to android Forums.

I have found the approach to Tasker is to start out small and slowly expand.

Can you create a small section of the Project (one Profile and associated Task(s)) that works in Tasker and fails when made into an app? If you then post it here perhaps we can help determine the problem/solution.

... Thom
Click to expand...

Thanks for the reply.. I am new to Tasker. I am attaching the app, is that what you wanted? It has one profile, one task and one scene, and was created from a Project. It is suppose to open a Scene when the Camera is started.
 

Attachments

It will tell you what permission is requiring the authorization. It is highly lily this is the answer to your question.

Here is an example of a Profile that must be enabled. It is done with an export of the Profile description.

Profile: tlaProx
State: Proximity Sensor
State: Not Call [ Type:Any Number:* ]
Enter: tlaProxEnter
A1: System Lock

Also ... when you are creating the app you need to have the profiles in the intial state they will be in when the app is loaded. This is almost always On.

... Thom
 
Thom said:
It will tell you what permission is requiring the authorization. It is highly lily this is the answer to your question.

Here is an example of a Profile that must be enabled. It is done with an export of the Profile description.

Profile: tlaProx
State: Proximity Sensor
State: Not Call [ Type:Any Number:* ]
Enter: tlaProxEnter
A1: System Lock

Also ... when you are creating the app you need to have the profiles in the intial state they will be in when the app is loaded. This is almost always On.

... Thom
Click to expand...

OK, so I have installed Tasker on a new Lenovo tablet (same model as the others) to test my methods. I created a Project, one Profile (When Camera starts, run Task) the task only runs a scene that pops up a button to close the scene ( the text on this scene button is different than the other). I ran the Profile description and it is attached. I created the app, still doesn't appear to monitor the profile.

Another interesting data point. I had the previous App installed on this tablet, it did not work but was still there. After I installed Tasker and created this new project I tested the project, obviously Tasker is enabled. When I open the Camera app, it triggers both the current Project and the test app from before. Both scenes appear. So the app runs If Tasker is enabled. But it was my understanding that an app did not require Tasker being installed on the target device.

Any other thought?
 

Attachments

  • Screenshot_2017-01-23-13-49-33[1].png
    Screenshot_2017-01-23-13-49-33[1].png
    196.2 KB · Views: 471
Does it run successfully on the old machine under Tasker?
Was the Profile On when you created the App and then turned Off when done?

On the new machine ...
Tasker is not needed.
With the app installed is it listed for Device Administrator and if so did you enable it?
Did you reboot after enabling it?

I admit to being confused as to what you are trying to do. For simplicityyou could try a test that does not use a scene.

... Thom
 
Last edited:
I have duplicated the original problem. I do not have a solution yet. Here is my simple Profile ...

Profile: Sample
Application: Camera
Enter: SampleEnter
A1: Flash [ Text:Sample Enter Long:Off ]
Exit: SampleExit
A1: Flash [ Text:Sample Exit Long:Off ]

... Thom
 
Solution Found

When you create the profile with the Application context make sure the App button at the bottom of the screen is selected.

When you build the app in App Factory a dialog appears.
In Min Android Version set it to at least 16.
Build the app and install it.
In System Settings/Accessibility go to your listed app and set it On.

The profiles in the app that monitor Applications will now work.

... Thom
 
Thom, Thank you so much for your attention and time. You are awesome!!!
I was able to get the test Project working.
Now I am off to try the full Project.
Thanks Again...
 
You must log in or register to reply here.
Back
Top Bottom