Prevent uninstallation of application in Android

by denismo » Sun, 05 Oct 2008 20:32:12 GMT


Sponsored Links
 Hello,

I've got an unusual requirement - I need to PREVENT users from
uninstalling my application from their Android platform (not emulator
but the future devices). Is there an official way for doing this? An
unofficial?

If that's not possible exactly, perhaps it may be possible to:
- remove/hide the application from the installed applications list
- abort uninstallation by throwing an error from some standard class
- prevent uninstallation of only some types/configurations of
applications?
- automatically force reinstall of uninstalled application?
- invoke some class in the application before being uninstalled so
that it can send SMS/access a web site to notify someone about this?

Thanks.

Denis

--~--~---------~--~----~------------~-------~--~----~



Prevent uninstallation of application in Android

by David Farler » Sun, 05 Oct 2008 22:32:01 GMT


 Even if this were possible -- and I don't think it is -- can you give one
good reason why a user should let you do this?






--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Other Threads

1. Picking up a PhoneBook entry under Android 2.0 !!!

Happy Halloween All !

The party is over and Google suddenly released the much anticipated Android
2.0 SDK.

Much improvement for sure !

That said, the party is over and I came to have to deal with the following
Ghost;

I've released an app in the market (Ambu) - so far qualified under SDK 1.5
&1.6. Using the emulator for Android 2.0, things don't work anymore.

This is what I'd like to share;

- my app invokes an ACTION.PICK intent as way to extract phone contact from
the phone book and populate a database.

When compiling my app using the SDK version 1.6 and a target emulator
configured at 1.6 level, the following code WORKS:

        Intent pickcontact = new Intent(Intent.ACTION_PICK,
People.CONTENT_URI);
        startActivityForResult(pickcontact, CALL_CONTACTPICKED);

When running the same code (compiled with SDK 1.6) and a target emulator at
2.0 level, the above code never return the entries I have populated in my
the phone book. It's as if the phonebook was always empty.

A couple of additional observations;

- When running the emulator in 2.0 mode, the default local input type is
Japaneese. Any way to change this ?

- Under the 2.0 emulator, and setting a "clean" AVD image, if you launch the
dial button, press menu and select account, you'll probably immediatly get a
"android.process.acore" error ...

- In the most recent SDK document, I can read that "People.CONTENT_URI" was
deprecated after SDK 1.6. Therefore, I've changed the above code to:

        Intent pickcontact = new Intent(Intent.ACTION_PICK, AUTHORITY_URI);
StartActivityForResult(pickcontact, CALL_CONTACTPICKED);

Unfortunatly, with the above, I get a crash right away when invoking
ACTION_PICK.

Question to the Google Folks (dear dianne and others, please !);

How to we properly pick a phonebook contact under the 2.0 OS using 1.6 or
2.0 compiled apps ?

Thanks !!!!!!!

-- 

2. Since Android 2.0 the phone number in the emulator became null - how to set it?

It the earlier versions of Android SDK the emulator had the set phone
number. Visible in the phone settings and accessible to applications
through the TelephonyManager.getLine1Number method. In Android SDK 2.0
it is not set. How to set it?

-- 

3. app widget sizes for WVGA and FWVGA

4. what about the Android 3d module file type ".gles"

5. Could developers be liable for charges for using Google APIs?

6. IMPORTANT - display.getOrientation() does not work on all devices

7. Youtube