Shell warning

[Peter Pliquet]

I´m running into an issue which not always comes up, but often.

See the pop up which comes up in case I see the issue.

After clicking OK Tasker works as expected.... but only starts working after I pushe the button.

[João Dias]

That can happen if you run a shell command and it stops running unexpectedly or doesn't stop running when it should. Nothing to worry about other than maybe a command not running as expected.

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[Peter Pliquet]

Well, thanks for answering! Appreciate that.

I use one task on startup to check if an app is running or not. May be I need to rethink this task, because it seems that the unit is blocked until this message get closed.

By the way... Do we have a possibility to press the marked button anyhow automatically by another app which is now used to activate Tasker after deep sleep.

The issue that Tasker is not active after booting is still present.

[Peter Pliquet]

Sorry, wrong screenshot...

[João Dias]

Hi there.
To make sure Tasker and the AutoApps run in the foreground please check here: https://tasker.joaoapps.com/userguide/en/faqs/faq-problem.html#00

Pay special attention to the location part. If Tasker doesn't have permission to get location in the background it might not work correctly, so disable and re-enable the location permission and make sure that you allow Tasker to always access it.

Make sure to check here too: https://dontkillmyapp.com/?app=Tasker

Hope this helps!

[Peter Pliquet]

Hmmm... this is nothing I have to look for. Foreground, location and battery is not what this issues.

I may explain a bit more:

This is an Adnroid car unit based on an RK3399 (PX6).

The issue nearly all owner of these units have is, that Tasker get´s killed when going into deep sleep.

Problem is here, that even the Accessibility settings are changed to denied on wake up.

I already built an app which activates the accessibility settings on reboot, but it is still an issue that Tasker is not "ativated", will say: there are no active profiles, independent what I choose as a trigger.

To "repair" that, I have to open Tasker and press the check mark button to get profiles working.

Sometimes it works with another app created with Tasker to start Tasker, give it  some seconds, check the return button twice and go home.

Then I can see that tasks are activated and stuff in the background is working... mostly at least, not always.

[Peter Pliquet]

Sorry @ joaomgc,

but the standard answers with foreground, location and battery,  and Dontkillmyapp are not always that what it needs.

The android car radio community needs really a solution here. It´s not only me using Tasker for special things which are working really great as soon as Tasker is somehow activated, but that does not happen automatically.

Please don´t get me wrong... I really love Tasker, just this single issue is really annoying.

BR

Peter

[João Dias]

Hi! Sorry for the late reply!

Unfortunately I don't have a way to make Tasker startup if the device itself doesn't start it up as usual :( It's out of my control. Does that device have a way to send an intent at startup? I've heard of other car related devices that had that option and that did allow you to send an intent to start Tasker up. 

Hope I can help!