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)
Related
I'm having a devil of a time using the Android Emulator on my new M1 Mac. My Android project compiles fine, and I can run it on a hardware device. But I'm not able to run it on the Emulator.
I followed instructions carefully, and set up an arm64-based emulator running API 31. When I press the "Run" button in Android Studio, the emulator opens and boots normally. However, Android Studio is never able to launch my app on it. I see a message "Waiting for all target devices to come online", and that's it.
I have of course tried restarting the emulator, restarting Android Studio, rebooting my computer, and wiping the data from the emulator. I have also made sure that Developer mode is enabled in the emulated Android environment and "USB Debugging" is turned on.
Another suggestion I saw was to un-check "Enable ADB Integration" in Android Studio. This option doesn't exist in my copy of Android Studio, although I did some further research and found that it is now called "Use libusb backend" instead. It is unchecked by default. I tried checking it anyway, and that didn't help.
I'm at a loss as to what to do next. I really need to be able to test my app in the emulator as my inventory of physical devices is fairly limited.
Thanks,
Frank
Download Android Studio Preview, create emulator (API 30 or S), now you can use emulator on both preview or stable Android Studio.
I want to start coding with flutter, so i decided to download android studio.I created an avd called "Pixel 2 API 28" with android pie. When i want to select the pixel 2 as the avd device, the programme tells me that theres no avd, but on the right i can see the avd i created. When i put my cursor on it, it says "not applicable for the main.dart configuration". i have HAXM installed and Hyper-V is disabled, but i also tried it with both being active. I used the default code, which appears when you launch android studio.
Please help!!!
Edit:
I somehow managed to select it now, but i get this error: Running multiple emulators with the same AVD is an experimental feature. Please use -read-only flag to enable this feature.
Try starting the emulator from avd and then check if the device is showing up there if not try running
flutter devices
If the device shows there you can try running
flutter run -d <your-device-name>
You can also check whether the android sdk is configured with flutter try running
flutter config --android-sdk /path/andriod/sdk
hope it helps
Close Android Studio and Run again as Administrator
This is Only the solution i got after working hard for 3 days.
I am trying to build an android app using bluestacks (my phone died)
Android studio can see the emulator in the devices list but when i try to run my app, android studio throws this error:
Installation did not succeed.
The application could not be installed.
Installation failed due to: 'closed'
Retry
I have tried launching both android studio and bluestacks as administrator.
I have also tried opening the standalone device monitor in the SDK tools folder
This throws another error :
could not open Selected VM debug port(8700)
The error log of the monitor contains lots of errors of missing directories.
error log: https://pastebin.com/mmA83ch7
thanks
Go to Settings -> Preferences and Enable Android Debug Bridge, Enable android input debugging
So someone on the bluestacks team decided that putting an adb toggle in "Preferences" and not in "advanced" was a good idea,
also literally not on any other single post has anyone said to make sure adb was toggled on.
the seting is in Setings -> Preferences, at the bottom
Open BlueStacks Go to Settings -> Advanced and Enable Android Debug Bridge, Enable android input debugging
Restart Bluestack and then Android Studio, this will make the connection.
happy debugging :)
I created a new dummy Kotlin project in Android Studio. I'm not developing an app, I just need it as a toolset to test apps on emulators and devices. For some reason Logcat window is not available in View > Tool Windows.
I have a device connected. Shell command adb logcat works fine from Studio's terminal.
I looked in preferences, tried updating platform tools, didn't help.
What am I doing wrong?
I am using Android Studio 1.3 with DDMS on Linux 64-bit. For some reason, when I try to debug with DDMS by selecting my app in the process list and clicking the "bug" in the tool menu, it shows debugging as disabled (grayed out). However, if I close DDMS and just use Android Studio for debugging, then everything works fine. Note that I've installed the debug version of my app so I should be able to connect to it.
Is there a way to use DDMS and be able to debug my app at the same time? I've tried attaching with Android Studio and loading up DDMS but it seems I can only have one ADB session at a time. Therefore, I must close DDMs before I can debug my app.