I am using Android Studio (v1.2.2). After I run a few times, I want to disconnect from the adb/logcat output without having to completely restart Android Studio. I need to be able to disconnect because multiple people are using these devices.
If I click on the 'X' (terminate program) in the Run menu, then it stops the program, but the logcat output keeps chugging away and the adb ports are held open by Studio. How can I close this connection?
I think the easiest way to use logcat and keep trace of what happend is to use command line. (I suppose adb is your path, if not add the platform-tools directory to your path).
In terminal adb logcat give you the logs as Android Studio. When you're done with your app and want the logs to stop interrupt the commnd by typing ctrl + C.
If you want to save the log to a file, use adb logcat > your_file.txt to redirect the output to a file.
Related
I am facing a problem, My android studio application. Loading Devices is disabling. I tried many ways to resolve that. but nothing didn't work.
-Create a New Project, Error didn't resolve.
-Restart the application even system also.
-Followed Previous posts :
Android Studio loading device button is disabled
Android studio virtual device not loading
Nothing Worked!!
Restart the PC and then don't open Android Studio directly , but run it as Administrator , this can be some permission issue , you can also try File->Invalidate Cache & Restart !
Try to kill adb with adb kill-server in the terminal tab inside Android Studio. It will be restarted automatically. If this does not help try adb devices in the terminal to see if the device is at least listed in the terminal. If you are under Linux you also need special permissions to access USB.
Also you have to enable on the phone USB debugging and confirm the access from the PC in case you have not yet done so.
The emulator in my android studio keeps showing "shutting down". I try closing it and run again, restarting my mac, but nothing worked, each time I run it, it shows "shutting down" again. even though I can see actions running below (very blur)
Click on Tools
Click on AVD Manager
Click on the dropdown arrow next to the AVD which is stuck
Click on cold boot now
This issue occurs when we forcibly exit an unresponsive/stuck AVD. AVD manager saves the state before it is forcibly exited and on the next start it continues from the unresponsive/stuck state. This is useful when we need the AVD to boot up quickly, however if you want to disable this feature entirely then follow the steps below:
In the AVD manager, click on the pencil icon
A new window will pop up. Click on show advanced settings
Scroll down to the emulated performance section
Next to boot option, select cold boot
open AVD Manager Dialog from top right corner
go to your emulator
click on the last icon on the right which is a drop down button
Click wipe data
Important Note: this will delete all data on that emulator and give it a fresh install again and might solve your problem
If that didn't work then check that you have enough rams to run both the emulator and the android studio.
I run my emulator with cold boot by command line
cd C:\Users\<your_user_name>\AppData\Local\Android\Sdk\emulator
emulator -list-avds
emulator -avd <your_adb_name> -no-snapshot-load
If the cold boot or wipe data does not work, you can try deleting the lock file. Then quit the emulator, and restart it.
In my case, AVD Manager prompted me to delete the following files, I did it, and the problem was solved.
If it shows "AVD *** is already running etc." then just connect any mobile device that after enabling debugging mode and run your app in a physical device instead of an emulator then
Click on Tools
Click on AVD Manager
Click on the dropdown arrow next to the AVD which is stuck
Click on cold boot now
First of all:
You have to close the window, or tab of your Virtual Appliance.
With this you get Android Studio to standby the Device and unlock the ADV (Android Virtual Device) files, so you can manipulate the virtualization.
Maybe you have to wait until Android Studio kill the process. If Android doesn't do this automatic, you will have to close Android Studio and delete C:\Users{YOUR_USER}.android\avd{YOUR_DEVICE_NAME}.avd and within this folder delete all files and folders with extension .lock to stay secure before start again Android Studio.
After that:
Just open the Device Manager, and click on the down arrow in the Actions section for your device, and select Cold Boot Now. This reload the Virtual Device without start or open any program.
Finally:
If Cold Boot Now worked fine, now you can run or debug your application to check that it functions perfectly. Without the device continuing with the problem that the system is still stuck/frozen.
And also you do not need to do a Wipe Data, so you do not delete the data of your application, since you can have any internal database in SQLite, which has the changes and advances that you have been implementing or creating during the development of your application for its operation.
I try to filter logs from adb to get the logs exactly like in Android studio. Tried to use adb logcat | findstr com.example.package but I can see anyway logs from the Android system.
If you want to filter all the logs coming from your app, my suggestion is to install pidcat and run it in the standard way such as:
pidcat your-package-name
This will allows you to filter out the app-related log entries in a nicely coloured way.
In the context of IONIC based application, I am developing a Native Cordova plugin for Android. I opened the Android prepared and run the application by Android Studio successfully. But I see that LogCat has gone away from everywhere: menu, actions ... But it is working for the bare project generated by Android Studio. And I reuse it. But it weird. I see that LogCat is not tangled to the project. It has to be available everywhere. I need it. I've attached my plugin and I do not see my notifications tagged. It is the issue of the next question ...
Regards.
I am not sure if I understand your question, but if you need LogCat, but your IDE cannot display it, you can always use a simple temrinal/command line for it:
adb logcat
this command will give you a tailed logcat in your terminal.
Just to make sure: The logcat is generated on the mobile device! Not on your computer! Android Studio is reading it from the device to show it.
If Android Studio is not showing it, you can either try to hide/show it using the Alt + 6 shortcut or you can try reconnecting your device by:
either just pulling the USB cable and reconnect it
or restart the adb server with the two commands adb kill-server and then adb start-server
or by clicking on the restart icon in the Logcat window of AndroidStudio (see image attached)
I must be missing something totally obvious, but I can't find a simple way to simply stop an app from running. I'm running it on my HTC One.
I first tried toggling the green run arrow. Didn't work.
I found a "Terminate Application" circle in the lower left of the window. That doesn't seem to do anything when you click it. It seems to be grayed out, non-functional. Screen shot here
http://www.screencast.com/t/VLTOzPQ7
So, I closed the entire project. That worked, but also the entire Android Studio closed instantly. Then reopening Android Studio failed (stack dump). Then reopening again worked, but it took 30 minutes to load my project.
To stop the next time, I turned my phone off, then closed the project. That seems to have worked better, since it took me to the Welcome to Android Studio screen and invited me to open or start a project.
Maybe there's an easier way to stop an app? I see the same question on this forum but no solutions.
The Android Studio controls you are trying to use only work if you are running your app in the emulator. There are a few ways to do this when you are using an actual device or VM (e.g., Genymotion):
Use the UI of the phone to Force Stop the application. This is done in the Settings->Apps menu.
Use Android Studio's terminal window or the host's shell and issue the command:
adb shell am force-stop <package-name>
Open Android Device Monitor (green "Droid" icon), select the process under the Devices tab and click the Stop Process button (stop sign icon). This is basically the GUI way of doing #2.
You need to select the process you want to terminate (ex. com.myname.myapp) then click terminate application.
Since the application is running on your phone, you need to end the application process on the phone. When you do that the application would be shown as terminated on Android Studio.