Jake Wharton recently published his ProcessPhoenix library, which does this in a reliable way. You basically only have to call:. The library will automatically finish the calling activity, kill the application process and restart the default application activity afterwards.
It only lets the app "restart" the home activity and dismiss all other activities. It looks like a restart to users, but the process is the same.
I think in some cases people want to achieve this effect, so I just leave it here FYI. There is a really nice trick. At some point, it stopped functioning. The user tried to exit the app and launch it again -- with no result, because finishing an activity is not the same as finishing or killing the process. By the way, the user could go to the list of the running applications and stop it from there -- this would work, but the users just do not know how to terminate applications.
If you want to observe the effect of this feature, add a static variable to your activity and increment it each, say, button press. If you exit the application activity and then invoke the application again, this static variable will keep its value.
If the application really was exited, the variable would be assigned the initial value. And I have to comment on why I did not want to fix the bug instead. The library was written decades ago and leaked resources ever since.
The management believes it always worked. The cost of providing a fix instead of a workaround I think, you get the idea. Now, how could I reset a jni shared a. I chose to restart application as a new process. The trick is that System. The calling activity just executes the code MagicAppRestart. And do not forget to mention this activity in AndroidManifest. I've found that this works on API 29 and later - for the purpose of killing and restarting the app as if the user had launched it when it wasn't running.
I have confirmed that the Application object in my app is re-created, so I believe that the process really has been killed and restarted. The only purpose for which I use this is to restart the app after the user has enabled or disabled crash reporting for Firebase Crashlytics.
According to their docs, the app has to be restarted process killed and re-created for that change to take effect. The only code that did not trigger "Your app has closed unexpectedly" is as follows. It's also non-deprecated code that doesn't require an external library. It also doesn't require a timer. Ok, I refactored my app and I will not finish A automatically. I let this run always and finish it through the onActivityResult event. So my solution is to do it from your app or even from another app, the only condition is to know the app package name example: ' com.
Note : I know this answer is a bit out of topic, but it can be really helpful for somebody. You can use startInstrumentation method of Activity. You need implement empty Instrumentation and pointed in manifest. After that you can call this method for restart your app. Like this:. Call startInstrumentation make reload of your app. Read description of this method. But it can be not safe if acting like kill app. The application I'm working on has to give the user the possibility to choose which fragments to display fragments are dynamically changed at run-time.
The best solution for me was to restart completely the application. With the Process Phoenix library. The Activity you want to relaunch is named "A". Mikepenz's Alternative Answer needed some changes in my case. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. How do I programmatically "restart" an Android app? Ask Question.
Asked 10 years, 4 months ago. Active 13 days ago. Viewed k times. That was the use-case. Is this really what you want? Taha Gorme 1 1 silver badge 12 12 bronze badges.
Stuck Stuck 9, 11 11 gold badges 45 45 silver badges 68 68 bronze badges. Add a comment. Active Oldest Votes. RTC, System. Tim Kist 1, 1 1 gold badge 14 14 silver badges 38 38 bronze badges. Oleg Koshkin Oleg Koshkin 3, 2 2 gold badges 14 14 silver badges 6 6 bronze badges. This worked perfectly for me! I just used android. Pressing back takes me to the old app, one screen back. The restart app requires root permissions and hence it is not for all users.
There are many options of the rebooting system of Android which this app accesses. The app has been highly rated just because of the fact that it works and ensures that the state of the art results are provided to the ones that have installed it. It might not work on some phones as the users might install it on un-rooted phones.
Note: Restart or reboot your Android device may lead to data loss without any warning sign. For that reason, you'd better backup your data in advence to totally keep it safe. It can be done with dr. Step 1. Download the program from the Free Download Button. Step 2. Connect your Android to the computer using a USB wire.
A pop-up may come into sight saying you to allow USB Debugging. If that happens, click OK. Step 3. Preview and select backup files. The app has all the options which are required to root the application. The best part is that the user needs no root access to get it working. It works on all devices and hence no software alteration is required. The core processes are the ones which are targeted by this application and hence it fosters the process of reboot.
This Android reboot app is highly recommended and reliable. This is the PRO version of quick reboot but it is free of charge. The reboot management has never been as easy as it is with this app. The apps are excluded from the reboot and it makes sure that the phone restarts with ease and in a very fast manner. Quick reboot PRO also requires root access so once again this Android restart app is not for every user or phone.
There are numerous reboot options to choose from when it comes to this app. It is highly rated just because of the fact that it allows the users to get the phone restarted as fast as they could imagine. Because the server manages connections to devices and handles commands from multiple adb clients, you can control any device from any client or from a script. On Android 4. Return to the previous screen to find Developer options at the bottom. You can now connect your device with USB.
If connected, you'll see the device name listed as a "device. Note: When you connect a device running Android 4. This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog.
Android 11 and higher support deploying and debugging your app wirelessly from your workstation using Android Debug Bridge adb. For example, you can deploy your debuggable app to multiple remote devices without physically connecting your device via USB.
This eliminates the need to deal with common USB connection issues, such as driver installation. To use wireless debugging, you need to pair your device to your workstation using a pairing code. Your workstation and device must be connected to the same wireless network. To connect to your device, follow these steps:.
Before issuing adb commands, it is helpful to know what device instances are connected to the adb server. You can generate a list of attached devices using the devices command. The following example shows the devices command and its output. There are three devices running. The first two lines in the list are emulators, and the third line is a hardware device that is attached to the computer.
The adb devices command has a corner-case command sequence that causes running emulator s to not show up in the adb devices output even though the emulator s are visible on your desktop. This happens when all of the following conditions are true:. One way to avoid this situation is to let the emulator choose its own ports, and don't run more than 16 emulators at once. Another way is to always start the adb server before you use the emulator command, as explained in the following examples.
Example 1: In the following command sequence, the adb devices command starts the adb server, but the list of devices does not appear. Stop the adb server and enter the following commands in the order shown.
For the avd name, provide a valid avd name from your system. To get a list of avd names, type emulator -list-avds. Example 2: In the following command sequence, adb devices displays the list of devices because the adb server was started first. To see the emulator in the adb devices output, stop the adb server, and then start it again after using the emulator command and before using the adb devices command, as follows:. For more information about emulator command-line options, see Using Command Line Parameters.
If multiple devices are running, you must specify the target device when you issue the adb command. To specify the target, use the devices command to get the serial number of the target. Once you have the serial number, use the -s option with the adb commands to specify the serial number. In the following example, the list of attached devices is obtained, and then the serial number of one of the devices is used to install the helloWorld.
Note: If you issue a command without specifying a target device when multiple devices are available, adb generates an error. If you have multiple devices available, but only one is an emulator, use the -e option to send commands to the emulator.
Likewise, if there are multiple devices but only one hardware device attached, use the -d option to send commands to the hardware device. You can use adb to install an APK on an emulator or connected device with the install command:. You must use the -t option with the install command when you install a test APK.
For more information, see -t. Instead, Android Studio handles the packaging and installation of the app for you. You can use the forward command to set up arbitrary port forwarding, which forwards requests on a specific host port to a different port on a device.
The following example sets up forwarding of host port to device port Use the pull and push commands to copy files to and from an device. Unlike the install command, which only copies an APK file to a specific location, the pull and push commands let you copy arbitrary directories and files to any location in a device. In some cases, you might need to terminate the adb server process and then restart it to resolve the problem e.
To stop the adb server, use the adb kill-server command. You can then restart the server by issuing any other adb command.
You can issue adb commands from a command line on your development machine or from a script. The usage is:. If there's only one emulator running or only one device connected, the adb command is sent to that device by default. You can use the shell command to issue device commands through adb, or to start an interactive shell.
To issue a single command use the shell command like this:. To start an interactive shell on a device use the shell command like this:. Note: With Android Platform-Tools 23 and higher, adb handles arguments the same way that the ssh 1 command does. But, this change means that the interpretation of any command that contains shell metacharacters has also changed.
For example, the adb shell setprop foo 'a b' command is now an error because the single quotes ' are swallowed by the local shell, and the device sees adb shell setprop foo a b. To make the command work, quote twice, once for the local shell and once for the remote shell, the same as you do with ssh 1.
For example, adb shell setprop foo "'a b'". Android provides most of the usual Unix command-line tools. For a list of available tools, use the following command:. Help is available for most of the commands via the --help argument. Many of the shell commands are provided by toybox. General help applicable to all toybox commands is available via toybox --help.
See also Logcat Command-Line Tool which is useful for monitoring the system log. Within an adb shell, you can issue commands with the activity manager am tool to perform various system actions, such as start an activity, force-stop a process, broadcast an intent, modify the device screen properties, and more. While in a shell, the syntax is:. You can also issue an activity manager command directly from adb without entering a remote shell.
See the Specification for intent arguments. Options are: -D : Enable debugging. Prior to each repeat, the top activity will be finished. This command kills only processes that are safe to kill and that will not impact the user experience. Use with [-e perf true] to generate raw output for performance measurements.
0コメント