I'm in the process of trying to make a release build of my first android app to send to a few testers. However, I ran into a problem with it. When you exit the app and then re-enter it by launching it via its icon, it restarts the whole app instead of returning to it's previous location. This occurs even if you re-enter right after exiting. However, it does not happen if I hold the Home button and launch it through the recent apps list.
I've searched online for others having this problem and there are a few, but no one has ever had a solid answer as to why it's happening to them. It's been suggested in old questions to set the launchmode to singletask or singleinstance in the manifest file, but that hasn't helped me, and besides - from what I understand, the default behavior for android is to return to the previous state of the task in this situation, so I don't know why I would need special manifest options to make it do that.
The most bizarre thing about this problem is that if I use eclipse and the debugger to put the app on my phone, this problem does not occur. I don't even need to be connected to the debugger, it seems like as long as I have a debug version of the app, the problem doesn't occur. But if I use a release version (I create it using the Android Tools - Export Signed Application Package menu option in Eclipse), the problem happens.If anyone has any insight as to what is causing this, I'd love to hear your thoughts.
I had the same problem with an application and I resolved this behavior adding flag "android:launchMode="singleTop"" instead of "android:launchMode="singleTask"" in the declaration of your AndroidManifest.xml file. Hope this will help somebody.
I would be pleased to know if there's any possible way to distribute correct APKs for beta testing. I already tried exporting a signed APK because when you copy and paste an APK and install it manually it shows the rogue behavior.
It is the default behavior in Android. For the debug builds it works differently for some reason. It can be solved by adding android:launchMode="singleInstance" to the activity, you want to restart after you launch from the icon.
The best way I know of doing this is, open Android Studio then under Tools click on "Create Desktop Entry". This will list android studio in all programs list, from there you can add the application to quick launch.
I deleted my only launcher and now I cannot open settings to set to debug mode in order to use ADB or similar to install a new launcher. I can't open the Play store, can't open anything except those that use voice commands: e-mail, text, phone, maps, navigation, and note to self.
Download the Launcher .apk file (just Google your "demand launcher name" and plus "apk"), save it to your friend's phone, and send it to your phone via Bluetooth. After you recieve the .apk file just click whatever option that directs you to INSTALL the file. If Bluetooth is off, ask your friend to call your phone; when the dialer window pops up you can see a "make another call" button. Click it and you will see the shortcut bar for Bluetooth appear.
if your android has search button then you are lucky first hard reset your android(learn how to hard reset your mobile) after the mobile started running hit search button and search the app 'settings' then turn bluetooth on and select discoverable or visible then share any launcher (like smart launcher) from other android to your mobile then install it and enjoy
Go into Recovery Mode (try turning off the phone and do not turn it on but press and hold the home button the volume up button and then hold the power button along with it). You need to do a Factory Reset from there and then reboot the phone.
Hello from France, first, excuse me for my poor English writing... I installed mobile security and i encountered difficulties to activate the antiphishing... I could not activate accessibility for the different browsers because they did not appear in the list in which there was only Eset and Microsoft launcher (which is the launcher I use on my smartphone).. . I did some tests and found that by enabling accessibility for eset and microsoft launcher, the antiphishing protection for browsers worked. Is this normal? and isn't it a security risk to have to activate the accessibility mode for the launcher? Thank you.
It is important that ESET Mobile Security has accessibility services enabled. As for the MS Launcher, it's unrelated and it's fully at your discretion if you want to continue using it and grant permissions that it needs.
unfortunately, there is a link between the two because if I don't give accessibility rights to microsoft launcher, eset mobile security's antiphishing stops working... MS launcher don't need accessibility rights to work... I haven't found any way to protect the browsers without giving accessibility rights to Microsoft launcher... I'm not sure it makes sense, from a security point of view, to give such a right to the launcher to activate antiphishing protection...
I don't understand why it works this way for me... As my phone is a poco (xiaomi), I disabled the mi battery saver for mobile security but it doesn't change anything... it's as if the launcher prevented mobile security from directly accessing the applications to be protected... it's weird...
I followed the advice of the web page (autostart activated and battery saver on no restrictions) and everything seems to work well, without needing to give special rights to the launcher... Thank you very much for your help Marcos ?
On Android Enterprise fully managed devices, Launcher allows enterprise IT admins to customize managed device home screens by selecting the wallpaper, apps, and icon positions. This standardizes the look and feel of all managed Android devices across different OEM devices and system versions.
Once the Microsoft Launcher application has been added to Intune, navigate to the Microsoft Intune admin center and select Apps > App configuration policies. Add a configuration policy for Managed devices running Android and choose Microsoft Launcher as the associated app. Click on Configuration settings to configure the different available Microsoft Launcher settings.
Configuration designer allows you to configure settings with an easy-to-use UI that lets you toggle features on or off and set values. In this method, there are a few disabled configuration keys with value type BundleArray. These configuration keys can only be configured by entering JSON data.
If you add properties with Configuration Designer, you can automatically convert these properties to JSON by selecting Enter JSON data from the Configuration settings format dropdown list as shown below.
Once properties are configured via the Configuration Designer, the JSON data will also be updated to only reflect these properties. To add additional configuration keys into the JSON Data, use the JSON script example to copy the necessary lines for each configuration key.
When editing previously created app configuration policies, if complex properties have been configured, the edit process will display the JSON Data editor. All previously configured settings will be preserved and you can switch to use the configuration designer to modify supported settings.
The following table lists the Microsoft Launcher available configuration keys, value types, default values, and descriptions. The description provides the expected device behavior based on the selected values. Configuration keys that are disabled in Configuration Designer aren't listed in the table.
NOTE: For Microsoft Launcher v 6.2 and later, this setting will no longer be enforced. Therefore, setting this value to True will have no effect. Your end users won't be able to customize the location of the search bar placement on their device.Dock ModeStringShowAllows you to enable the dock on the device when the user swipes up from the bottom on the home screen.
Properties: