Android Studio on my OS X Yosemite very often stops displaying log messages written by my app under development.
If I go to the ADB logs tab I see a plenty of different error messages:
1) Broken pipe:
ddmlib: Broken pipe
java.io.IOException: Broken pipe
2) null
ddms: null
java.lang.NullPointerException
at com.android.ddmlib.Client.read(Client.java:731)
at com.android.ddmlib.MonitorThread.processClientActivity(MonitorThread.java:311)
at com.android.ddmlib.MonitorThread.run(MonitorThread.java:263)
3) Closed connections
DeviceMonitor: Adb rejected connection to client '5022': closed
4) Unauthorized device
PropertyFetcher: AdbCommandRejectedException getting properties for device HT4C9JT00135: device unauthorized. Please check the confirmation dialog on your device.
5) EOF
DeviceMonitor: Adb connection Error:EOF
It would be funny if this wasn't the development environment for Android.
I was able to solve only error number 4 (I had to forget associated devices and authorize again).
I tried combos of answers found here on SO (for example adb kill/start-server), enabling the ADB integration (which was disabled), ....
Besides planning a trip to Lourdes, what else can I check to see why Android Studio refuses to log my messages? It used to work till some days ago: problems started after the upgrade to 1.1.
Update
I uninstalled and reinstalled Android Studio.
The first time I ran my app adb worked fine: I could see the log messages. From the second run, adb started refusing connections again (problem 3).
Is there anyone who was able to solve this incredible mess?
2nd Update
When there are no log messages, if I unplug and plug again the USB cable, the messages magically appears.
Related
can someone got problem like me the logcat show error com.android.studio E/AndroidLogcatService: com.android.ddmlib.ShellCommandUnresponsiveException
restart android studio
invalidate cache still not working
use emulator or use real device with usb or wifi still same
update adb not fixed it
my adb already new on version
i dont know how to fix it now
adb logcat working on cmd
but i need adb logcat on android because cant instal apk directly from android studio show message waiting device to online
I'm starting the android tutorial at udacity. This course consist on creating a weather app sunshine. At the end of lesson 1 when I try to run my app, android studio marked it as DEAD.
I tried all the steps in a similar problem however the problem remain the same. Here is the adb logs:
DeviceMonitor: adb restarted
PropertyFetcher: ShellCommandUnresponsiveException getting properties for device emulator-5554: null
DeviceMonitor: ExecutionException getting info for device emulator-5554
DeviceMonitor: Adb rejected connection to client '14794': closed
Remove your device (Samsung GT-I9060I) from USB.
Close Android Studio.
Open Task Manager and kill all processes named adb.exe.
Open Android Studio and wait until Gradle build is finished.
Connect your device as emulator again.
Run your app.
Btw, I also faced this issue a month ago, and those steps help me.
I actually rebuild my application and it works. I have no explanation . I guess it has something with Android studio.
The ADB still works unstable, and never mind which IDE are used Eclipse or new Android Studio.
The workaround for this is to restart adb.
Type in console:
adb kill-server
adb start-server
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
Usually, this is enough condition to solve the issue for some time.
I recently switched to connecting to the phone via WiFi. I am able to compile and upload programs through Eclipse. However, I do not receive any logcat ouput. The phone is also shown in the DDMS view and when my program is started it also displays the name and pid. Is it possible to get the logcat trace via wireless or do I have to switch back to using a USB connection?
UPDATE:
Maybe I did not make it clear enough in my initial post. There is no problem with the connection itself. I can dump the logcat by using a terminal with 'adb logcat -d'. What I want is to see the live logcat in Eclipse's logcat viewer. Not sure if it is of any importance, but I am using Eclipse 3.8 in Debian Jessie.
(1) connect phone with usb, then type in command line:
adb tcpip 5555
you can disconnect your phone from usb now
(if the reason for using wifi is that usb does not work on your machine, just do the above on another computer
(2) find out the IP address of your mobile device (somewhere under settings .... phone status)
(3) in command line type:
adb connect [IP of your mobile]
NOTE: all devices need to be connected to same wifi; avoid using public wifis
In your eclipse,
just go to: windows->preferences->Android->logcat and follow the following setup:
1. double-click action: "go to problem (error line)
2. switch to: java
3. both checkboxes are checked
if setup is fine, clean the project and restart eclipse
Restart Your ADB Server
1) open cmd
2) change directory to platform-tools
3)type adb kill-server
4)then adb start-server
I am not sure what exactly happened, but it is working now. I did not do anything that I had not tried earlier. It just started working after several attempts. Might be a faulty Eclipse installation, it did crash earlier today.
This question already has answers here:
Error "The connection to adb is down, and a severe error has occurred."
(39 answers)
Closed 7 years ago.
The connection to adb is down, and a severe error has occurred.
You must restart adb and Eclipse.
Please ensure that adb is correctly located at '/home/ASDK/platform-tools/adb' and can be executed
WHAT SHOULD I DO?
this question was raised by me and here I am explaining my experience.
Actually this question was raised when one of my friend was trying to setup android on his laptop but his micromax mobile could not be detected for debugging. he is just a teen eager. I suggested above answer and some other solutions to him one of which is installing mobomarket mobile synchronization software (used for micromax mobiles- a company whose adb driver can not be installed automatically).
He install that s/w but facing this error every now and then. one thing he observed that this s/w installed req adb driver for micromax mobile. but port no 8700 on which adb process used to run was occupied by this new s/w.
so he made very good assumption that if he uninstalled the s/w driver will not be uninstalled. and trick works. good thing is that he completed his whole android app without facing this error.
hope this trick will help you all.
I'm trying to work through their notepad tutorial and it describes how the Eclipse project should automagically build and re-generate the auto-generated code when a file is saved. That wasn't happening, and looking at their debugging, they suggest the "reset adb" link in the DDMS perspective in the Devices panel. When I try to do that, I get the following output which I assume is bad:
[2010-01-03 23:09:51 - DeviceMonitor]Adb connection Error:EOF
[2010-01-03 23:09:51 - DeviceMonitor]Connection attempts: 1
a quick Google didn't reveal anything particular useful. What are the next debugging steps and/or what might be the issue?
UPDATE: So this actually isn't a problem like I thought it was, but I'd still be curious what this message means if anyone knows.
DDMS uses a long-lived connection to the adb server running locally to get info about connected devices/emulators etc. The error message you posted generally just means that the connection to adb has been lost.
Because you ran the reset command, you essentially just killed and restarted an adb process, so Eclipse showed that harmless warning for a moment.
You can see this yourself by killing the adb process manually. Eclipse will show Connection attempts: n for about 10 attempts before giving up.