After choosing a default program for an action, every time an app gets updated that relates to that action, the OS unnecessarily asks which program to use. I can't be the only one to be aggravated by this defect.

It's especially irritating for apps that get updated frequently and serve multiple intents.

Here is the scenario:

  1. User installs app (for instance, a new web browser-Dolphin)
  2. User performs intent (for instance clicking a hyperlink from an email)
  3. Android OS asks user which app to use.
  4. User selects Dolphin browser, checks check box at the bottom of the popup window with the label "Use As Default" and selects new web browser app.
  5. Android Market installs new update for Dolphin.
  6. User performs same intent as #2 (clicking a hyperlink from an email)
  7. Android OS forgets "use as default" setting and Android OS asks user which app to use. [Steps 3-7 repeat ad infinitum]

The bug occurs at step 7.

I submitted a bug report for this issue. In the meantime, is there an app that works around it?

  • 3
    I've always found this behavior annoying, especially since I use GO Launcher which updates relatively often. I like my apps to get new features and bugfixes, but having to constantly reset it as the default app gets old.
    – Zeke
    Feb 27, 2012 at 17:01

1 Answer 1


No, you can't work around it unless you make changes to the android sources and compile a custom ROM. The Installer Service is a core part of the system and cannot be replaced or overridden like other apps can.

This is by design. It will only ask you again if one of the apps that was updated is one that has other apps that can perform the same task.

The same thing happens if you install a new application that can perform the task of another app. This is because updating an application is actually just like installing a "new" application. There is no difference in what happens when you install a new application on your device or if you update an existing application. So if there was a way to have it "always remember" this option, then when you installed a completely new application that you want to use, you would never get presented with the option to use it.

Lets use the launcher as an example. You use GO Launcher for a long time and you have it set as the default. Then you decide you want to use the new Foo Launcher, so you install it. Now when you go to the launcher you are asked what launcher you want to use. If you set it to "always remember", you would not be presented with the option and you (or maybe other users) would consider this a poor experience because now they have to figure out how to change the launcher to the one they just installed.

  • 5
    I get that this is by design--to me a poorly thought out design. I understand the very different use case you presented when a user installs a new application that can perform an intent that another app can already perform. In the case of a new app being installed that performs an intent, the default app should be requested again. Feb 27, 2012 at 16:11
  • It's especially annoying (and potentially dangerous) when, for instance, you're driving and use voice commands to call someone... only to have it sit there waiting for you to choose Skype or Phone as the default. :(
    – CodeRedick
    Sep 24, 2013 at 17:36

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .