[android-developers] Logcat is broken every time phone is unplugged

2012-01-14 Thread Keith Wiley
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


Re: [android-developers] Logcat is broken every time phone is unplugged

2012-01-14 Thread Mark Murphy
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/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