Stopping running applications without root.

[MacroDroidDev]

The whole point of MacroDroid supporting Tasker plugins is to offer a wide range of functionality beyond what I can feasibly implement/support myself. Of course it's preferable if everything is within the app and I wish that was possible, but even the mighty Tasker lacks a lot of functionality offered by these plugins (hence why they exist). I think in this if suitable plugins exist then I cannot really prioritize this above many other things I need to do.

 

[Mr.Lon]

Guys guys... It's important to mention and it was already mentioned in this thread, that there's an app called SecureTask that offer exactly this and it can be controlled by MacroDroid. I think SecureTask plugin is good temporary solution for these kind of features.

All the real Secure Task features only with device owner perms


But hey!....is it really that simple Mr.MacroDroidDev?

CCSWE App Manager (Device Owner) - CCSWE

CCSWE App Manager is the ultimate package disabler and bloatware killer for Android devices! Samsung, root, and non-root variants available.

ccswe.com

....then...hey...c'mon .... give it a try and make us happy....and I promise...no!.....I swear!...not to ask for additional support in this case

 

[jmh2002]

After years of frustration with these various types of issues it's part of the reason why I'm so pleased to be back on a phone that is both Rooted as well as running LineageOS (17.1, so basically Android 10, with the update to 11 waiting if I want it). This plus MacroDroid and I can already do way more than I personally need.

Life's too short to constantly be trying to find work arounds to stuff that should just be possible in the first place.

 

[Mr.Lon]

This is awesomely true my friend but if you want to do various banking things an opened Bootloader and a rootet Handset kills your nerves....har

Anyway you would get the most functionality out of the MacroDroid box with device owner permisson and your device unrootet.

 

[jmh2002]

Yes sure, it's a trade off. So far with banking apps Magisk has either been sufficient as a work around, or I just log in via the banks mobile web page instead. For me that's a smaller inconvenience compared to all of the other restrictions and nonsense on devices these days. But I understand that it might not work for everyone and in all situations.

 

[Koer]

De vuelta al punto principal de este hilo. ¿Podría alguien enumerar una selección de aplicaciones que pueden matar aplicaciones en un dispositivo no rooteado y echaré un vistazo exactamente a lo que están haciendo? Ciertamente me gustaría agregar la capacidad de eliminar aplicaciones en dispositivos no rooteados, ya que esto será popular, estoy seguro.

Tenga la seguridad de que lo es, muchos de nosotros podríamos usarlo maravillosamente.

 

[GuadaMIjia]

I'm not entirely sure what the problem might be, but it could be related to the QR code itself. Have you tried scanning the QR code with a different scanner or device to see if the issue persists?

 

[Endercraft]

I'm not entirely sure what the problem might be, but it could be related to the QR code itself. Have you tried scanning the QR code with a different scanner or device to see if the issue persists?

Also, if you're interested in exploring other options for scanning QR codes, you might want to check out smartengines.com. They offer a great range of services for automatic document scanning and OCR that might be helpful in your situation.

What does this have to do with this thread..?

 

[Carl Zyex]

Just discovered this thread. Interesting discussion about 'force stop' and 'freeze' apps from MD (even though it's not the same).

Anyway, another, better option is to freeze an app with the 'disable package' ADB command.
In my case, I use Shizoku for sending the ADB commands and Hail for managing the packages. They run pretty well.

All in all, I'm honest enough to say I really don't see any positive change in battery level!

 

[Endercraft]

All in all, I'm honest enough to say I really don't see any positive change in battery level!

Simply, because these 'app killer & booster' apps are useless. They are just repeating a basic Android process of killing certain apps.
If the app is not doing anything in background it won't use that much battery. So you won't notice.

 

[MacroDroidDev]

@Endercraft is spot on, all these apps are really just frauds and play on old ideas about how memory management works in operating systems like Windows etc. where you really do have many apps fully open at the same time. They only are perceived to work due to the placebo effect and hence why Google is cracking down.

Now if they could just do the same with "Virus Killer" apps, most of which are an absolute joke.

 

[Raman]

This is a non root method: http://www.macrodroid.com/macrostore?id=5521

Reference to your app for force close app.
i want to exclude some apps from being "force closed".
i see that there is a variable named UserExclusion wherein user can mention the apps to exclude from the macro. However, instead of typing the individual package names, can there be an option to tick mark the apps to exclude. how to do this?

I'm new to the macrodroid and therefore don't know much about this. Your guidance is appreciated and requested.

 

[hsurB]

Reference to your app for force close app.
i want to exclude some apps from being "force closed".
i see that there is a variable named UserExclusion wherein user can mention the apps to exclude from the macro. However, instead of typing the individual package names, can there be an option to tick mark the apps to exclude. how to do this?

I'm new to the macrodroid and therefore don't know much about this. Your guidance is appreciated and requested.

I believe You can open window with creating new macro, choose app closed/opened trigger and go to list with your apps. Each app there has the name of package below its name, so just write it down and use in the variable

 

[Raman]

Instead of writing down so many apps packages. A list of all apps with an option to tick mark the ones to be selected will be easy.

 

[Jacob L]

I don't think it's possible at the moment

 

[hsurB]

Unless you would create a macro for each app and tried text manipulation to edit the variable inside this macro. Then enabling/disabling macro could work as add app to the list of excluded or delete it from there. I don't know if its considered as a solution and I couldn't do it probably myself

 

[Raman]

i'm using the macro. I've entered packages of the app those are to be excluded. However, when the apps are "forced stopped", the screen remain on the settings page of the last app. macro does not go back to the home screen.
What an i doing wrong?.

 

[Jacob L]

i'm using the macro. I've entered packages of the app those are to be excluded. However, when the apps are "forced stopped", the screen remain on the settings page of the last app. macro does not go back to the home screen.
What an i doing wrong?.

At the very end, it should be taking you home. If you mean that pressing the back button when the app details page is open, it is because it layers up. There's little that can be done about this.

 

[Raman]

There is a local variable named Apps. What app should be listed under this?

There is a local variable named system defaults. What should be listed under this?

 

[Jacob L]

Apps is all installed apps and system defaults is the input keyboard. The keyboard is excluded from force stop by default