Develop Reference

Android Studio - Logcat not working for emulator but OK for phone

I'm very new to Android Studio. I have been using it on Windows but the machine was too old to run any of the emulators so I installed it (via Ubuntu Software store) on a laptop running Unbuntu 18.04.
It all seems to work OK except the Logcat does not show anything. Sometimes, after cold starting the emulator, I get some output to the Logcat but then it just halts and nothing I do (see below) causes it to output anything else.
I cannot get ANY output when running an app.
I have searched extensively here and via Google and tried the following:
restarted the Studio
restarted logcat
killed and restarted adb
invalidate caches and restart AS
deleting and recreating AVDs
use logcat via AS built in terminal and external shell :
./adb -s emulator-5554 logcat
and get:
Unable to open log device '/dev/log/main': No such file or directory
NB: When using an attached phone e.g. Moto G. the logcat works fine. I get all the system output and the app output works as expected.
Thanks in advance
2019-12-14 UPDATE: when the emulator is running it shows the active processes (see screenshot) in the drop down, including my app but NO entries. Not sure if this gives anyone a clue? It is clearly communicating with the emulator in some way.
2019-12-16 UPDATE: Started in from scratch. Installed MX Linux 19 and fresh Studio install. Created new AVD. EXACTLY THE SAME!!! This is so ridiculous. Anyone, please?

sometimes you might be trying to use a gun to kill a fly. For a try, ensure that the emulator you have run is actually selected in logcat like in this screen shot
.

OSX: Android studio emulator not showing up in adb devices or Logcat window

I am currently on Android Studio 3.0.1 and OSX 10.13.1
This is a screenshot of the problem
I have tried all the following things:
killing and starting adb server (adb kill-server and adb start-server)
Enable and Disable adb integration with android studio
Added android-sdk/platform-tools and /tools paths to ~/.bash_profile
I have created multiple emulators - wiped their data, etc
Have unistalled/installed android sdk platform tools multiple times; even done the same with HAXM installer
restart android studio and my system
The interesting thing is that I can see the devices
when I connect to deviceConnect (https://mobilelabsinc.com/resources/videos/deviceconnect-demo)
This software was closed while I was trying out with the emulator, I have checked in activity monitor too to make sure.
I still cannot see my emulator in either "adb devices" or logcat window.
Side Note: I see here: ~/.android/avd/: the emulators that I have created, I feel somehow this needs to be linked to the android avd? I have spent wayyy too much time on this!!
Any help would be highly appreciated!

This is caused by the deviceConnect/deviceBridge tool from mobilelabsinc that you are using. You only have one option: uninstall the deviceConnect/deviceBridge tool.
Just moving the deviceConnect/deviceBridge tool to the trash will not work. You will need to use a tool like AppCleaner(https://freemacsoft.net/appcleaner/) to remove it. Once you have removed the tool, it should solve your problem (Might need a reboot!).

android emulator on eclipse won't open

I've gotten it to work before but now the android emulator on eclipse refuses to open. No new window, nothing. Most of the time the console says nothing when I tell it to launch, other times it says "The connection to adb is down, and a severe error has occured." but if I try again after waiting a bit it goes away then it says Launching.... and does nothing.
I try to delete the avds and it says they are currently running in emulators and cannot be deleted even though there are no windows open. I tried re-installing the (1.6) SDK and that didn't work.
Oh and I'm using Ubuntu
Edit The console is finally working, after complaining about adb, I ran it again and I got
"Launching a new emulator with Virtual Device "XXX" and then nothing
then I tried to launch a different project with the same emulator and got:
Automatic Target Mode: Preferred AVD "XXX" is not available. Launching new emulator.
Launching a new emulator with Virtual Device "XXX"

Run adb kill-server and then sudo adb start-server and then adb devices and see if you see the emulator. Sometimes the emulator is running but it hides somewhere. Also trying running the app in debug mode. Also the emulator can be just damn slow sometimes. adb is a command located in the sdk tools directory I think. Add it to your path and it will save you a lot of time. You can also do install and uninstall of your apps using command. Then tell us what you see.

I did have the same issue and I solved it by running the emulator from the command line. Go to the tools folder in the SDK package and start the emulator from there, use the name of the emulator you setup in Eclipse (in Virtual Device Manager):
./emulator -avd [the name]
The GUI should either come up (the GUI comes up fairly quick but will "idle" quite a bit) or you'll probably get an error on the command line. For me it was a missing library, namely libGL.so. Install a lib with apt-get containing libGL and retry.
sudo apt-get install libgl1-mesa-dev:i386
./emulator -avd [the name]
I did some googling and I'm not the only one, and of course those libs are missing in a 64 bit environment. Here's another one with the same problem.
Hope it helps!

Eclipse Failed to start Android app in Emulator

I get the following output on Eclipse Console (Started with UAC on Win 7):
(Nothing on LogCAT)
[2011-07-01 18:13:42 - Test_Android_2_2] ------------------------------
[2011-07-01 18:13:42 - Test_Android_2_2] Android Launch!
[2011-07-01 18:13:42 - Test_Android_2_2] adb is running normally.
[2011-07-01 18:13:42 - Test_Android_2_2] Performing nx.Android.Test_Android_2_2Activity activity launch
[2011-07-01 18:13:44 - Test_Android_2_2] Launching a new emulator with Virtual Device 'Test_AVD'
But still there is no trace of my application on the emulator. It just shows the regular menu items & API Demos & other stuff.
Am I missing something?
P.S.
-adb kill-server & adb start-server did not help.
-Launching SDK, adb & Emulator before Eclipse does not help. While launching the app Eclipse doesn't see the any Currently Running Emulators so I'm forced to start a new one.
Thanks,
Nisheeth Barthwal

Strange as it may be. I went to LogCat console and noticed it had nothing. While people all over the net said to look for LogCat log.
That led me to thinking that maybe Eclipse wasn't able to talk to the adb.
Oddly enough my already running emulators wouldn't show up while Run/Debug-ing a new Project/Activity.
A somewhat of a adhoc approach, here's how I fixed it.
I opened the Devices View, which shows up the currently running emulators, mine wasn't there.
So I clicked on the little down-arrow & clicked on "Restart ADB" (or something like that). And presto! as the adb rebooted the Devices View listed my emulator (along with other stuff I didn't quite understand). Viewing the LogCat console showed the entire trace. And I could launch my app into the currently running emulator.
I had tried to restart adb numerous times through the console but it didn't made a difference. From Eclipse, it however did.
P.S. ADB still pesters by not listing the emulator & the same approach fixes it everytime. (Restart via Devices View)

it sounds like you haven't yet added the program.
Right click on your android project
select run as
select android application.

Android adb.exe crashes - Only when called from Eclipse (win7 32)

ADB when run stand-alone works fine. I can connect to my device (HTC Desire) and perform .apk installs etc, so I know the USB drivers are working correctly. A common reason for this question, I know, but that can be ruled out.
Occasionally I can connect to the phone, very occasionally. 99% of the time I just get the standard windows popup "adb.exe has stopped working".
I've updated Eclipse to the latest version.
I'm sure the USB drivers are working correctly
I can connect via adb in command line mode with no issues.
I've searched for a solution until google begged me to stop :)
Seems like a DDMS Eclipse issue.
Any ideas ?
Actually, just before I sent this I had a brainwave.
Without Eclipse running I ran adb.exe from command line and performed an install -r of my .apk package.
All worked fine.
I then started Eclipse - the connection to my phone worked fine...
Nope, Eclipse now failing again. BUT with eclipse trying to connect (and failing) I can simultaneously run adb from command line and install the package. It's got to be Eclipse

If you have an alternate "launcher" or "home-screen" installed, that might be forcing the connection to close. If you have one installed, either force stop it or uninstall it.

I've found that some apps running in your phone can cause ADB to crash for some reason. Try to close unnessecary apps running on your phone when developing in eclipse

In my case, I had an instance of adb.exe from another package (Android-Sync) running. Processes with this file name are common in packages that sync devices. You can find more information about programs that use an adb.exe process here: What is adb.exe ? adb.exe info
To determine if you have an adb.exe process already running, look in your Task Manager on the Processes tab to find the running adb.exe. You can right-click and select Properties from the menu to find out the full path of the adb.exe.
To solve the problem and allow Eclipse access to the correct adb.exe, I shut down Eclipse and the emulator. Then I went into the Task Manager and shut down the running adb.exe. There may be more than one. Then I restarted Eclipse and the emulator. Fortunately, when I started my Android Virtual Device, that program was smart enough to start up the correct adb.exe.

In my case was kinda problem with USB driver. Just plug your phone always to the same USB port.