Kill App when screen is turned off, start it when screen is turned on?

Welcome to Android Forums.

The following Tasker profiles and tasks do it. The Beeps are so you know it's executing ...

Code (Text):

1. Profile: Off
2. Event: Display Off
3. Enter: Anon
4. A1: Beep [ Frequency:8000 Duration:1000 Amplitude:50 Stream:3 ]
5. A2: Kill App [ App:Poweramp Use Root:Off ]
6.  
7. Profile: On
8. Event: Display On
9. Enter: Anon
10. A1: Beep [ Frequency:8000 Duration:1000 Amplitude:50 Stream:3 ]
11. A2: Launch App [ App:Poweramp Data: Exclude From Recent Apps:Off Always Start New Copy:Off ]

... Thom

 

Have a look at AutomateIt at the play $tore.

Much simpler than ta$ker...

 

if the coding of Tasker is a problem, look at MacroDroid.
it is a Plug 'n Play type macro program.

* MacroDroid - Device Automation - Android Apps on Google Play

I use it to do what you want.

 

The Tasker solution I showed does not require root. I am on an un-root-ed Droid Turbo 2.

... Thom

... Thom

 

Just like Tasker, MacroDroid does not need Root to turn an app on/off.
It is just your personal choice of whether you want an app that will do the job within 30 seconds of you installing it, or get Tasker and take a while figuring out how to program it.

either works. and the way they handle the process is the same.

I use the Power Charging signal to turn OFF all System Sounds period for as long as the charger is connected. My wife literally screams at me if she hears anything from my phone at all. So, the Charge Full sound just drives her up the wall.

MacroDroid senses "charging" and the phone goes deaf....
Taken off charge, it immediately comes back to life.

for you, the "Action" to be taken is to "Enable/Start an app".
that is just one macro.

Then you create a 2nd macro and the Trigger is "Charger off",
"Action" is close app.

 

I'm not following what you are doing with Tasker.

In Tasker there are two profiles and each has a single entry task.
You need to have both profiles on.
You need to exit Tasker and do a Save First if you made any changes.
Then tap the power button to turn the screen off. You will hear the beep.
Tap the power button again and hear the beep and the app will be displayed.

This is killing and starting one app and in this example it is Poweramp.

This processing will continue until the profiles are turned off (and you do an Exit Save First).

... Thom

 

Don't know how you tried to set up the macros in MacroDroid, but it does indeed shut down apps when I lock the screen.

and it does indeed shut OFF all of the System sounds when the Charger is working, whether it be a wireless charge, or a usb plug in charger.

go into Developer Options and check to see if you have something set that should not be.

 

There are multiple paths here on the table. This is not a trivial activity. It takes some involvement. The Tasker path is being partially addressed by the OP.

Choose which path you want to follow and tell us.

The Tasker button you referred to is to execute a Task and not a Profile. In this one there are two Profiles that are triggering two Tasks. Both Prodiles must be On.

If I had to guess I would guess that my sample app of Poweramp is not installed on your device and that is the reason it is not working. Chose an app that is installed on your device.

... Thom

 

Choose an app to launch and kill that exists on your device.
Go to System Settings/Security/Device Administrators. Tasker must be enabled.
Go to System Settings/Sound & Notification/Notification Access. Tasker must be enabled.
Hitting the button on the Task should perform the launch or kill.

... Thom

 

Did you reboot your device after setting Tasker as an Administrator?

Did you launch an app using that task and can then not kill that app?

What app are you launching and killing?

... Thom

 

I am on an un-root-ed Droid Turbo 2 running 5.1.1. Launch and Kill work witout a problem.

From what I've read elsewhere the Kill was a problem with earlier versions and the solution was to ...

Root
Use the Secure Settings Tasker plugin​

From what you are experiencing it is clear that the correction was not (yet) retrofitted to support earlier versions of the system.

To do it with Tasker on your device will need root and a plugin.

... Thom