Last time I released a version, I changed only one line of code!

Dynamically change application icons

Product: Can we dynamically change the App Icon in the Launcher?

Development: No

Product: Can we dynamically change the App Icon in the Launcher?

Development: No

Product: Can we dynamically change the App Icon in the Launcher?

Development: No

Product: Can we dynamically change the App Icon in the Launcher?

Development: Let me think...

Principle 1 — activity-alias

In AndroidMainifest, there are two properties:

 //Determine the Activity that the application starts 
 
 android.intent.action.MAIN​ 
 
 // Determine whether the application is displayed in the program list 
 
 android.intent.category.LAUNCHER

In addition, there is an activity-alias attribute, which can be used to create multiple different entrances. I believe that developers who have developed system settings and launchers should have seen a lot of them in the system source code.

Principle 2——PM.setComponentEnabledSetting

PackageManager is a general class that can manage all system components. Of course, if you root your device, you can also manage all components of other apps. Some system optimization tools disable some background services in this way.

It is very easy to use:

 private void enableComponent(ComponentName componentName) { 
 
    mPm.setComponentEnabledSetting(componentName, 
 
            PackageManager.COMPONENT_ENABLED_STATE_ENABLED, 
 
            PackageManager.DONT_KILL_APP); 
 
 } 
 
  
 
 private void disableComponent(ComponentName componentName) { 
 
    mPm.setComponentEnabledSetting(componentName, 
 
            PackageManager.COMPONENT_ENABLED_STATE_DISABLED, 
 
            PackageManager.DONT_KILL_APP); 
 
 }

According to the two flags PackageManager.COMPONENT_ENABLED_STATE_ENABLED and PackageManager.COMPONENT_ENABLED_STATE_DISABLED and the corresponding ComponentName, you can control whether a component is enabled.

Dynamic Icon Change

With the above two principles, the only thing left to achieve dynamic icon replacement is the idea.

First, we create an Activity as the default entry with a default picture, then create an activity-alias for Double 11, pointing to the default Activity with a Double 11 picture, then create an activity-alias for Double 12, pointing to the default Activity with a Double 12 picture... and so on.

 <activity android: name = ".MainActivity" > 
 
 <intent-filter> 
 
        < action android: name = "android.intent.action.MAIN" /> 
 
  
 
        <category android: name = "android.intent.category.LAUNCHER" /> 
 
 </intent-filter> 
 
 </activity> 
 
  
 
 <activity-alias 
 
 android: name = ".Test11"   
 
 android:enabled= "false"   
 
    android:icon= "@drawable/s11"   
 
 android:label= "Double 11"   
 
    android:targetActivity= ".MainActivity" > 
 
 <intent-filter> 
 
        < action android: name = "android.intent.action.MAIN" /> 
 
  
 
        <category android: name = "android.intent.category.LAUNCHER" /> 
 
 </intent-filter> 
 
 </activity-alias> 
 
  
 
 <activity-alias 
 
 android: name = ".Test12"   
 
 android:enabled= "false"   
 
    android:icon= "@drawable/s12"   
 
 android:label= "Double 12"   
 
    android:targetActivity= ".MainActivity" > 
 
 <intent-filter> 
 
        < action android: name = "android.intent.action.MAIN" /> 
 
  
 
        <category android: name = "android.intent.category.LAUNCHER" /> 
 
 </intent-filter> 
 
 </activity-alias>

Wait, there is a problem with this, that is, this will display 3 entrances on the Launcher, so by default we will disable these activity-aliases first, and then enable them when they are needed. It takes a long time to train an army.

 public class MainActivity extends AppCompatActivity { 
 
  
 
    privateComponentName mDefault; 
 
    private ComponentName mDouble11; 
 
    private ComponentName mDouble12; 
 
    private PackageManager mPm; 
 
  
 
 @Override 
 
    protected void onCreate(Bundle savedInstanceState) { 
 
        super.onCreate(savedInstanceState); 
 
        setContentView(R.layout.activity_main); 
 
        mDefault = getComponentName(); 
 
        mDouble11 = new ComponentName( 
 
                getBaseContext(), 
 
 "com.xys.changeicon.Test11" ); 
 
        mDouble12 = new ComponentName( 
 
                getBaseContext(), 
 
 "com.xys.changeicon.Test12" ); 
 
        mPm = getApplicationContext().getPackageManager(); 
 
 } 
 
  
 
 public void changeIcon11( View   view ) { 
 
        disableComponent(mDefault); 
 
        disableComponent(mDouble12); 
 
        enableComponent(mDouble11); 
 
 } 
 
  
 
 public void changeIcon12( View   view ) { 
 
        disableComponent(mDefault); 
 
        disableComponent(mDouble11); 
 
        enableComponent(mDouble12); 
 
 } 
 
  
 
    private void enableComponent(ComponentName componentName) { 
 
        mPm.setComponentEnabledSetting(componentName, 
 
                PackageManager.COMPONENT_ENABLED_STATE_ENABLED, 
 
                PackageManager.DONT_KILL_APP); 
 
 } 
 
  
 
    private void disableComponent(ComponentName componentName) { 
 
        mPm.setComponentEnabledSetting(componentName, 
 
                PackageManager.COMPONENT_ENABLED_STATE_DISABLED, 
 
                PackageManager.DONT_KILL_APP); 
 
 } 
 
 }

OK, after disabling the default Activity, enable the Double 11 activity-alias, the result remains unchanged and still points to the default Activity, but the icon has changed.

Depending on the ROM, after disabling the component, you will wait for a while and the Launcher will automatically refresh the icon.

See the picture below for the effect.

[[180569]]

About the Columnist

eclipse_xu: Senior Android development engineer; author of "Android Heroes", "Android Heroes: Magic Weapons", Android lecturer at MOOC; CSDN blog expert