How to kill an application with an unrooted phone ?

D

Dimlos

Well-known member
To use ADB Shell [Tasker Plugin], you must first connect to your PC and enter the adb command adb tcpip 5555.
This command is valid until the device is rebooted.

Storing outputs and errors in variables makes it easier to identify the cause.
 
C

Cili

New member
Hi everybody,

I just registered, because I have a similar question / idea:
There's an app with wich I earn money by playing games named Mistplay.
It's always running in the background and uses a lot of battery. So when I'm not playing, I want to stop Mistplay.
Right now I'm doing it by swiping the notification bar thingy (Sorry, I'm German and don't know the english terms of everything), then tap settings -> Apps -> App-Management -> type "Mistplay" and tap it, then click the button "force stop" and confirm.

So this seems to be the only way to stop Mistplay. Would it be possible to let Macrodroid do this by telling it every single step?

This way it would also be possible for Christoph to end his CamSam.
 
C

Christoph

Member
Dimlos said:
To use ADB Shell [Tasker Plugin], you must first connect to your PC and enter the adb command adb tcpip 5555.
This command is valid until the device is rebooted.
Click to expand...
I have done this and now it works perfectly 😊 thanks.

Dimlos said:
Storing outputs and errors in variables makes it easier to identify the cause.
Click to expand...
Good tip, I have stored the output StackTrace and Terminal, how can I know if the command was successful ? (the output of both seems to be the same when it succeeds and when it fails).

@Cili : use ADB Shell as it was recommended in this thread. It is more elegant and I can confirm it works.
 
C

Cili

New member
Dimlos said:
To use ADB Shell [Tasker Plugin], you must first connect to your PC and enter the adb command adb tcpip 5555.
This command is valid until the device is rebooted.
Click to expand...
I installed the Tasker Plugin and in it I tried to type this command or any other and always get this error message attached. Even when I enabled USB-Debugging and connected to a computer. Do I have to do anything ON the computer or phone settings?
 

Attachments

  • Screenshot_2023-03-28-16-43-26-18_c500bd22b8b6ce50d92894d3df6c85b3.jpg
    Screenshot_2023-03-28-16-43-26-18_c500bd22b8b6ce50d92894d3df6c85b3.jpg
    335.9 KB · Views: 5
D

Dimlos

Well-known member
You need to send adb tcpip 5555 with the PC ready to send ADB commands.
Do you know of an ADB hack for MacroDroid? It sends the command the same way.
 
C

Christoph

Member
You need to download ADB tool on your PC, then plug your smartphone to the pc via usb and then connect to it via ADB tool.
Then you just type the command provided by Dimlos and ADB Shell will then work
 
D

Dimlos

Well-known member
There is a way to do this using only a smartphone with wireless debugging without a PC, but it is hard to explain to someone who is not familiar with this method, so I will skip it.
 
C

Cili

New member
Now I got it! Didn't understand that this needs an extra tool on the computer. This way it works now *yay*

BUT: As Dimlos said it only works until phone is rebooted... I switch it off every night. So this is actually no real method for me :-(
Any other ideas for my case?
 
D

Dimlos

Well-known member
There is also a way to automate the sending of commands by automatically turning on wireless debugging when rebooting, but this is difficult to explain to someone unfamiliar with the system, so I will skip it.
If you must, the information in this thread may be helpful.

Wifi ADB debug mode lost on restart?

I remember a while ago on my old phone (non-rooted), that I was able to use "adb tcpip 5555" and MacroDroid would continue working using ADB debug mode, even when the phone was restarted. On my new phone, it seems that I lose ADB debug mode after a restart, which is annoying. Is there a way...
www.macrodroidforum.com www.macrodroidforum.com
 
D

Dimlos

Well-known member
Probably the easiest way to kill an app in non-root.
I haven't looked into it much because I don't think it is necessary to kill the app in normal use.
UI Interraction would work after a reboot, but it only works when the screen is on.
 
C

Cili

New member
Dimlos said:
Probably the easiest way to kill an app in non-root.
I haven't looked into it much because I don't think it is necessary to kill the app in normal use.
UI Interraction would work after a reboot, but it only works when the screen is on.
Click to expand...
As I intentionally want to end Mistplay after I'm done playing, the screen would be on anyway. So if you got an easier way instead of using wireless debugging, please explain that to me.
 
D

Dimlos

Well-known member
It's your device, so use whatever apps you like.
If it doesn't work, you'll have to do it one UI Interraction at a time.
 
C

Cili

New member
Dimlos said:
There is also a way to automate the sending of commands by automatically turning on wireless debugging when rebooting, but this is difficult to explain to someone unfamiliar with the system, so I will skip it.
If you must, the information in this thread may be helpful.

Wifi ADB debug mode lost on restart?

I remember a while ago on my old phone (non-rooted), that I was able to use "adb tcpip 5555" and MacroDroid would continue working using ADB debug mode, even when the phone was restarted. On my new phone, it seems that I lose ADB debug mode after a restart, which is annoying. Is there a way...
www.macrodroidforum.com www.macrodroidforum.com
Click to expand...
Oh my! I read that and don't think I can reproduce that.
Maybe the step-by-step-UI interaction-method will be enough.

But thanks for the link anyway!
 
You must log in or register to reply here.
Top