I see the description of "Disable" and "Force Stop" operations on Android devices for apps as:
Force stop will temporarily stop the app from running in the background. The app will start running again as soon as you open it next time whereas Disable will close the application from the phone and you will not be able to use the application again unless you enable it again from settings
But why do disabled apps have an option "Force Stop"? They should not be running as per above definition and there should be nothing to stop.
That behaviour is even observed after a phone restart.
Moreover, "Force Stop" is not available for all disabled apps.
In Android, I developed service and install apk on device.
I need disable or hide 'uninstall' button in Application Manager Setting, also 'Force Stop' button.
In Application Manager Setting, there are some services and apps exist like above.
I also have seen Device administration api on here.
I'd appreciate it if someone would teach me.
Answer, lock your settings. You can't "force stop" apps with settings locked.
For this question, how to disable google asking regularly checking app, there are answers like "uncheck the option Settings > Security > Verify apps". However, on Lollipop I am using, there is no such an option, instead there is an option "Unknown sources".
I unchecked this "Unknown sources", and I could have my app installed. I was asked if "google can regularly check installed apps for potentially harmful behavior". I clicked allow (by mistake). Then I can not start my application. Every time I click my app to start it, it is going to run, but immediately, it is stopped by google.
Do you know where can I configure the android to allow my app to run?
Thanks a lot in advance!
Best Wishes,
York
Don't use settings.
On your device, open the Google Settings app(not android settings app);
Touch Security.
Move the switch next to "Improve harmful app detection" on or off.
Is it possible for an Android device administrator app to disable uninstallation of itself?
The default behavior is that the app's uninstall button is grayed out, unless the user unchecks it from the list of device administrators. However, I've seen MDM apps that goes the extra step to disallow users from unchecking the app from the list of device administrators (e.g. Citrix XenMobile). How is this possible?
Thanks.
Okay, I'm pretty sure that this is not possible but a client had asked me to do so in one of our Android application we developed for her.
What she had wanted is that if our application is running, and user navigate to:
Settings > Manage Application > [Our Application]
, the button for "Force Stop" is disabled.
Is this possible? If it is possible, could someone point me out which way I should walk, or if it is not possible, how, using a valid argument based on facts, should I break the news to her.
Update:
She just sent me a screenshot that, in her opinion, validates her request that there's an Android application that disables "Force Stop" button. How am I supposed to explain this to her?
How to disable the "Force Stop" button
Short answer: Use the Device Administration API.
How to explain this to my client?
Show this to your client. It is a nice slideshow providing an easy-to-understand overview of the Device Administration API and its uses.
How do I demonstrate that it works?
Yes, back to your job. Use the API link provided above and the Api Demos included in Google's sample
collection to figure out how to integrate this into your app.
Build the demo and run it on your device.
Choose API Demos->App->Device Admin->General->Enable admin.
Choose Activate once the Device Administration API prompts you with its enabling screen.
Exit the app and attempt to manage the app via your device's settings menu (specifics for this step varies by device).
When viewing the Api Demo's "app info" screen, you should see both Force Stop and Uninstall are disabled.
How do I do this in my own app?
Review DeviceAdminSample.java in the Api Demos app for inspiration. You will need the following:
The following code is what brings up the activation screen:
// Launch the activity to have the user enable our admin.
Intent intent = new Intent(DevicePolicyManager.ACTION_ADD_DEVICE_ADMIN);
intent.putExtra(DevicePolicyManager.EXTRA_DEVICE_ADMIN, mDeviceAdminSample);
intent.putExtra(DevicePolicyManager.EXTRA_ADD_EXPLANATION,
mActivity.getString(R.string.add_admin_extra_app_text));
startActivityForResult(intent, REQUEST_CODE_ENABLE_ADMIN);
However, there are a few other pieces you will need to get this to work:
A broadcast receiver that derives from DeviceAdminReceiver.
Entries in your manifest file that refer to the above broadcast receiver.
Permissions in your manifest for using the Device Administrator API.
An xml file stating what policies your app can access.
All of this can be found in the above links. Good luck with your client!
This is not remotely possible, for great reason.
You should tell her that making this possible would be a huge security disaster. Imagine what would happen if you could create apps which just ate at your processor time by holding a wake lock, and you couldn't kill them. This would be horrible.
In general, if you're wondering if you can modify the "extra-app" behavior of the device, the answer is usually *no*. You should take the viewpoint that nothing on the device is yours to control besides your app and (to a limited extent) the resources to which you're granted access.
No other app has this kind of control, so it's not reasonable to expect that your client's would either. However, the fact that she's asking for this control usually implies something else: that they are worried the user will stop the app and then something bad will happen (the locations will stop being synced, data will stop being sent out to the net, etc...). This would imply that you should look into improving the resilience of the app to different situations. Remember, your app can even be killed off at any time by Android (for example, in the case of low memory).
I think the device screen shot has confused us. Even I can show my application that is installed on the device and the "Force Stop" button is disabled. Where as I have not done any thing specific to that.
The reason of the "Force Stop" button being disabled is, that particular application is NOT running currently. Hence there is not meaning in having the button enabled.
#Rhama you can ask your client to start the application once, press the home button of the device, and goto the settings and see. Surely the "Force Stop" button will be enabled this time.
Regards,
Rajan
From ICS, disabling Force stop is possible. If your app has an active device admin then the framework will not allow user to kill the process
Hey I think it is quite possible to disable the "Force Stop" button...check Kaspersky
Parental Control from the market it is doing the same.
Its service is running in the background then also the force stop button is disabled.
The application service is running in background
you can disable the forcestop when the app has admin rights. but soon as those admin rights are revoked then it is back to normal. however in android 4, an application called applock (domobile) was able to prevent that by asking a password when you tried to change admin rights. It could only be done by installing an extra program that applock asked you to. And I guess this might even be seen as a security flaw, infact it no longer works in Android 5.