About Android custom Launcher and androidlauncher
I haven't developed the Adroid project for a long time. I need to develop an APK temporarily.
The customer requested the APK to exist as the launcher, and it took some time to record it so as not to forget it.
Add
<Category android: name = "android. intent. category. DEFAULT"/>
<Category android: name = "android. intent. category. HOME"/>
Press "Home" at this time. The select launcher dialog box is displayed. However, if the default value is selected, the default value is the original launcher.
Stay up and search for a solution.
In this example, the SET_PREFERRED_APPLICATIONS permission is added,
However, you need to sign the authentication information on the terminal,
I only developed APK, a pure third party, and should not rely on the terminal. I decided to give up this solution.
I suddenly remembered that I had used a third-party desktop before. I had to get down to a Go desktop and it could really become the default launcher. It seems that others are okay.
What is the difference between my and Go? Decompiling the Go desktop is complicated and cannot be seen.
A flash of light, the selection box popped up when I started up has a Go desktop but no APK. Why.
View logs and search for "scan package". Well, find the original launcher and go, but there is no APK. Where is my APK,
Continue to view my APK on the SD card. I tried to move my APK to the internal storage and it was actually successful. I started my APK.
This is simple. Just add the default installation path option to the configuration file.
Android: installLocation = "internalOnly"
Finally, the success was over, and such a small thing had been around for a while. It seems that it has been useless for too long.
Supplement:
After Launcher, the main menu will disappear, which seems inappropriate. It is best to add an empty activity (receive Launcher filter) to jump to the previous activity.
The implementation will not be too long, just don't forget to add
Android: launchMode = "singleTask"