[android-developers] Re: Logcat is broken every time phone is unplugged
Although I dont' remember encountering exaclty the same problem, the unreliability of logcat display from inside Eclipse is the reason I long ago got into the habit of runnig logcat in a Terminal window (I run Eclipse under Linux, not Windows) instead. But even then, when I disconnect the USB cable for the phone, I find that often I have to restart adb. But this is a lot less drastic than restarting Eclipse. So that is what I suggest you try: stop and restart the server using the adb command from a terminal window (or a command shell) when you see that problem. It is a lot faster than restarting Eclipse. On Jan 14, 12:24 pm, Keith Wiley kbwi...@gmail.com wrote: Every time the phone is unplugged from USB, the logcat is permanently corrupted in that the when the phone is reconnected, logcat does not reestablish. Restarting an app, either in debug or run mode produces zero logcat output after that point. Closing the logcat window view and reopening it has no effect. The only solution is to quit and restart Eclipse. Therefore, I must quit and restart Eclipse every time I take my phone with me and then later return. I've been having this problem since day one with Android development, three years ago. In that time I have installed new versions of Eclipse and numerous updates to the Android SDK and Eclipse plugin. Nothing has ever improved the situation w.r.t. this bug. Anyone know anything about this? Thanks. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Logcat is broken every time phone is unplugged
The following appears in the Console window when I plug the usb cable into the phone. Any ideas? [2012-01-24 18:27:21 - Unexpected error while launching logcat. Try reselecting the device.] device not found com.android.ddmlib.AdbCommandRejectedException: device not found at com.android.ddmlib.AdbHelper.setDevice(AdbHelper.java:736) at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java: 373) at com.android.ddmlib.Device.executeShellCommand(Device.java:372) at com.android.ddmuilib.logcat.LogCatReceiver $1.run(LogCatReceiver.java:100) at java.lang.Thread.run(Thread.java:680) -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Logcat is broken every time phone is unplugged
Eclipse Indigo SR1, Windows 7 Home Premium 64bit. When I reconnect, I always have to reclick on the device in the Devices view (of the DDMS perspective). However, in the latest version of ADT, I have a similar problem, where clearing the log output results in subsequent log messages not appearing at all. I need to click around a bit (on other filters) to get it to kick back in again. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Logcat is broken every time phone is unplugged
same here On 15 Jan., 11:50, Mark Carter mjc1...@googlemail.com wrote: Eclipse Indigo SR1, Windows 7 Home Premium 64bit. When I reconnect, I always have to reclick on the device in the Devices view (of the DDMS perspective). However, in the latest version of ADT, I have a similar problem, where clearing the log output results in subsequent log messages not appearing at all. I need to click around a bit (on other filters) to get it to kick back in again. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Logcat is broken every time phone is unplugged
G1, OS 1.6 Eclipse Helious I'm part way through installing Android SDK rev 16, but like I said, this has been persistent across a variety of versions of all the associated pieces. I don't understand why I haven't seen more reports of this. Thanks for any help. On Jan 14, 12:27 pm, Mark Murphy mmur...@commonsware.com wrote: I haven't seen that on any of my devices. What's the phone? On Sat, Jan 14, 2012 at 3:24 PM, Keith Wiley kbwi...@gmail.com wrote: Every time the phone is unplugged from USB, the logcat is permanently corrupted in that the when the phone is reconnected, logcat does not reestablish. Restarting an app, either in debug or run mode produces zero logcat output after that point. Closing the logcat window view and reopening it has no effect. The only solution is to quit and restart Eclipse. Therefore, I must quit and restart Eclipse every time I take my phone with me and then later return. I've been having this problem since day one with Android development, three years ago. In that time I have installed new versions of Eclipse and numerous updates to the Android SDK and Eclipse plugin. Nothing has ever improved the situation w.r.t. this bug. Anyone know anything about this? Thanks. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Mark Murphy (a Commons Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy Android Training in NYC:http://marakana.com/training/android/ -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Logcat is broken every time phone is unplugged
On Sat, Jan 14, 2012 at 3:35 PM, Keith Wiley kbwi...@gmail.com wrote: G1, OS 1.6 Eclipse Helious I'm part way through installing Android SDK rev 16, but like I said, this has been persistent across a variety of versions of all the associated pieces. I don't understand why I haven't seen more reports of this. I just dusted off my G1 and I cannot reproduce your problem. When I unplug and re-plug in the G1, LogCat shows all the old entries, plus any new ones from whatever app I run. Perhaps try a different micro USB cable. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in NYC: http://marakana.com/training/android/ -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Logcat is broken every time phone is unplugged
Hmmm, okay. I don't have one that fits the G1's connecter, but I'll consider the suggestion. Sigh. On Jan 14, 12:47 pm, Mark Murphy mmur...@commonsware.com wrote: Perhaps try a different micro USB cable. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en