I am hitting web service and getting action to install and uninstall the application in background. Till now I am able to install and uninstall the application with user interaction.
I need that there should be no user interaction and the application should be installed / uninstalled as per the action in background without disturbing the user.
what you want to do is not possible
This kind of task can only be done by system apps, or apps with root access.
It is not possible via the public SDK for security reasons.
Related
is there any option in android studio to make an app so that user can not able to uninstall it for a particular period of time. For example if user granted permission of not uninstalling the app for one hour , so user can not uninstall this app for one hour
There is no way to do this, unless the app is enrolled in Android Enterprise (which is their program to allow businesses to control fleets of hardware. Using that you can install apps and prevent their uninstallation). Otherwise no, there's no way an app can prevent the user from uninstalling itself. That would basically make malware unremovable.
There is no way to prevent user to uninstall the app for particular period of time.
Thanks
I developped an android application which has to run on chromebooks.
I will be install it in mdm to avoid install it manually chromebook by chromebook.
This application wait alerts sent by a server. So, users has no action to do when the application starts. There is no screen. The authentification is done in background.
I want to start this application automatically after the installation without user action. But I don't know what I can do it.
Does somebody has an idea? I hope, I am clear
I'm developing an android app which will display list of all the installed app in mobile.
I'm already listed all the app which are installed in my phone, and trying to stop a app from list.
I want to stop a app from list by one click. Without Root
Thanks in advance.
You can only kill your own apps, for example, the apps which are running in the same process or with the same userID. You can not kill others, unless the device is rooted.
Look at this answer to know about killing background processes of app.
I'm building an app that needs to restrict which apps can be run along with it.
In example, when my app is running (foreground or background) I can allow user to run only GoogleMaps, and MusicPlayer.
I've read a bit about Device Policy Controller and creating profiles, and up to some point it seems to have the feature I need, but it is designed for enterprise deployment, and user needs to encrypt their phone beforehand. Is creating personalized profiles a way to go?
My other idea was to run a service that each few milliseconds check if there is any forbidden app running and finish it, but it seems to be not robust.
Is there any way of handling this problem programmatically?
I don't think that Device Policy Controller is a right thing for you.
And you can't just kill other apps without root.
So some kind of user-friendly way to achieve the goal is to check running apps list with ActivityManager.getRunningAppProcesses and to notify user that he has to finish particular apps to use your app.
What is the best way to let my users perform an application update?
Is there any way to force device reboot after the update? I'm asking this because my application registers some behavior on boot.
Please note, the application would not be published in the Market.
Update:
My app will be preinstalled on a set of ~100 handsets.
Should I periodically call a webservice that will inform the device about upgrade available, and then, redirect to an .apk file within a webkit view?
What is the best way to let my users
perform an application update?
Via the same way they got the app on their device in the first place, presumably. If they are getting the app via firmware, they get app updates via firmware updates. If they are downloading your app via your Web site, they get app updates via your Web site.
Is there any way to force device
reboot after the update?
No, thank goodness.
I'm asking this because my application
registers some behavior on boot.
There is some way you can be notified that your package was updated, though I do not have the technique handy right now. Just run your on-boot logic there for the first round, then subsequent reboots (if any) will be handled by the on-boot logic itself.