Not sure what I'm doing wrong here.
My basic goal is that I'd like to be able to take screenshots of my Android tablet via Android Studio which is running on my Windows laptop.
I gather I need Dalvik Debug Monitor Server (DDMS) to do this, however I'm struggling to find it within Android Studio.
All the guides I've read so far mention that you simply click on the DDMS menu button in the toolbar. This seems to appear like a green android robot.
Well, I have the android robot and so I click on that. The tooltip for the button says 'Android Device Monitor', nothing to do with DDMS.
And then normally says 'Android Monitor is already running' and does nothing. But all I have on my screen is Logcat and Monitors tab. I can't see the same stuff that I usually see on DDMS screenshots.
Occasionally it will throw an error which appears in the log files (but too big to post here)
How can I fix this?
Ok, officially dumb.
The DDMS was opening up in the background of another monitor.
Carry on...
Related
Android Studio upgraded to version 4.0.1, and now I get a "Unable to locate adb" message when trying to launch an Android emulator image from the AVD manager, in order to run/debug a Flutter app. I have tried all the obvious things, e.g. checked to see that there is an adb.exe image at .../AppDate/Local/Android/Sdk/platform-tools. I have even tried de-installing completely and did a clean install of everything from scratch. I have plenty of disk space, anti-virus has not quarantined it. Interesting, if I start a native Android app (e.g. "basic activity"), then the message goes away and the image starts OK
Android Studio - launch emulator AVD - "unable to locate adb"
Visit the above link to get solution in detailed way with pictures.
I had the same issue as you were facing, I have Researched the Whole Internet but found nothing useful. So, I somehow figured out the problem and fixed it, The problem is at
app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
Whenever we create a new project due to some reason the Module SDK is not set up automatically. Thus the ADB manager was throwing an error 'Unable to locate AVD', which is not that fatal as the error/warning is not stopping us from launching /starting the emulator, but it is so annoying to see that pop-up box. So here is my simple and quick fix.
Solution:
Click on the project folder, tap the dropdown icon just beside it.
Now Navigate to the path below.
android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
Now Click on the file GeneratedPluginRegistrant.java to open it.
Once it is open, At the Top you will notice a bar that says 'Module SDK is not defined',
Now right against it, you will also see a hyper-text named 'Setup SDK', Just Click on it.
That will open a Pop-up Box with the title 'Select project SDK'.
Now select the Android Platform API and then click OK. After that being done Restart your IDE.
Your Problem will be Solved. And you will also notice that Emulator Opens up way faster than before.
NOTE:
The Above Steps has to be performed with every new flutter project.
I have already answered to your question before to Read more and understand in detail with pictures just visit the link
Android Studio - launch emulator AVD - "unable to locate adb"
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.
Somehow I closed the logcat tab from the debug window and now I am unable to get it back.
In Run->Configuration->Logcat I have everything checked.
I do have the logcat tab in Android Monitor window, but not in Debug.
How can I get it back?
I created a bug on on their bug-tracker: https://youtrack.jetbrains.com/issue/IDEA-144525
I think with the release of Android Studio 1.4 the logcat tab has been removed from the Debug view. Now I believe the only place to access it is by opening the Android Monitor view by pressing Alt+6 on Windows or CMD+6 on Mac.
Release notes of Android Studio 1.4 Beta 3 allude to this:
Logcat view mostly rewritten to address a number of stability and usability bugs
In Android Monitor window, click the little tiny button on the top right corner.
No one has seemed to mention this, but make sure you are inside the "android" directory and not the root directory of your project (React Native). Logcat will not display otherwise.
Click on Android Monitor at the bottom of the screen.
and then you should see there are a tab call "Logcat" next to "Memory" tab.
In Android Studio 3.5.2, Logcat can be shown from View > Tool Windows > Logcat
For some reason in a specific project, it wasn't found using this way, but I could fix it as following:
File > Project Structure > Facets > Add > Android > my_module
While I would be a little late for the party, it has been a few years and new version of Studio.
Today when you encounter the bug, your logcat would not be shown, to resolve this you would need to follow these steps:
Menu -> Build -> Make Project
in your settings.gradle comment out everything and sync.
uncomment everything and sync again.
Menu -> Build -> Make Project
Once the project build is done.. your Studio would be ready.
I have encountered several different bugs related to this issue, this scenario covers most of these cases.
Given solutions not worked for me.
I found another solution
Click
View-> Tool Windows -> Logcat
Then the missing Logcat tab appears again.
Android Studio IDE version: (Android Studio Electric Eel | 2022.1.1 Canary 8)
It was working fine and it disappeared suddenly.
After nothing else worked, I ran adb devices to see if my device was correctly attached and TA DA.
adb server wasn't running and started automatically and Android Studio started to show Logcat as always.
➜ adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
0030713775 device
press alt 6.
If you still don't see it there should be a little icon in the top-right corner of the view, press that.
Top Menu:
View -> Tool Windows -> Logcat
Bottom bar:
View -> Appearance -> Tool Windows Bar
I'm having real trouble when I try to use the IOS emulator from the visual studio. So I created a hello world app in VS using xamarin (latest stable version), I set the project as main project, and When I refresh the connexion with the mac, I can't select the device that should be shown in the selectList. The message is "No device attached" :
And if I try to use xamarin studio on the host mac, all is okay, the sample app builds on the iphone emulator:
Thanks to help me !
I know this question has already been answered, but i found it when i had a problem, and it did not help... but i did find the solution:
Under the debugging menu in VS2012, click on Configuration Manager
make sure that iPhone Simulator (or iPad, if you want) is set...
Default seems to be looking for a physical device...
hope this helps.
Are you sure the device is connected to the Mac and not the Windows machine? Have you tried debugging from that same device from Xamarin Studio on the Mac?
Had the same problem. Issue was when i loaded my solution, visual studio 2012 decided to choose a library project as the 'Startup project'.
Rt Clicked the ios project, chose 'Set as StartUp Project' and the device list was populated.
P.S: Visual Studio you should be old enough to figure this out by now.
When I ran into this problem, I had another instance of visual studio running which was connected to the Mac.
Apparently you can only have on VS instance connected at a time.
Check your server log in Visual Studio output window for some more clues:
Closing the other instance of Visual Studio allowed me to connect in the instance I wanted to debug in
I discovered something missing. For me, in Visual Studio 2013, for some reason they have removed Solution Platforms from the toolbar. This makes it impossible to switch from iPhone to iPhoneSimulator without opening Configuration Manager. So, to fix this.
Click TOOLS/Customize then select the 'Commands' tab then select the 'Toolbar:' radio button and click the dropdown to the right of it and select 'Standard' as the toolbar you're working on.
Now, click 'Add Command' and select 'Build' from the catagories on the left and then scroll down commands until you find 'Solution Platforms'. Select that one and click OK. Then click the 'Close' button. You will now see an additional dropdown next to the Solution Configurations dropdown on your Standard Toolbar.
This will allow you to easily switch from iPhoneSimulator and iPhone. Use iPhone when you want to plug in an actual device, and use iPhoneSimulator when you want to pick a simulated device.
Hope this helps somebody out. I too have spent lots of time trying to figure this one out when I went from a device and was trying to use the simulator instead.
Restarting of Visual Studio 2010 worked for me.
Different things worked for me (Windows 8.1 & Visual Studio 2013):
Restart Visual Studio
Set 'iPhoneSimulator' as platform (only working one)
In Properties - iOS Application change 'Deployment Target' version to some lower number (6.0 worked for me).
As well as checking you have the right startup project selected as per #Chamkila's answer, check that you haven't accidentally broken your project's Info.plist file by attempting to open it through Visual Studio.