Fixed
Status Update
Comments
vs...@google.com <vs...@google.com>
da...@google.com <da...@google.com> #2
Hey thanks for reporting! We're just starting to dig into this.
Can you run
$ adb version
and also
$ which adb
Can you run
$ adb version
and also
$ which adb
ro...@google.com <ro...@google.com> #3
$ adb version
Android Debug Bridge version 1.0.31
$ which adb
/usr/bin/adb
BTW - "adb kill-server" also does the job, so it's really the server restart, not "adb logcat" that kicks off logging in AS again.
Android Debug Bridge version 1.0.31
$ which adb
/usr/bin/adb
BTW - "adb kill-server" also does the job, so it's really the server restart, not "adb logcat" that kicks off logging in AS again.
da...@google.com <da...@google.com> #5
Hey Torsten, can you refresh my memory? You're using a Nexus 6 device, right?
ro...@google.com <ro...@google.com> #6
No, Nexus7 (2013), Android build MMB29K dev-keys.
da...@google.com <da...@google.com> #7
We got another report from an external dev posted in dup issue 36949180 :
confirming this bug
Nexus 4, Android 5.1.1, Android Studio on Windows 7
confirming this bug
Nexus 4, Android 5.1.1, Android Studio on Windows 7
da...@google.com <da...@google.com>
da...@google.com <da...@google.com> #8
+Tom as this may be an internal plugin issue. I've gotten two external reports that they're seeing this behavior as well, so they may add their idea.log files to this bug, which I can use to see if they have any non-standard plugins installed as well.
vs...@google.com <vs...@google.com> #9
BTW, there used to be a bug in the platform where clearing the log will cause it to stop producing logs anymore. IIRC, it was only present in 1 version of the platform, probably a couple of years ago.
I'd check if all these reports are from the same API level, and if so, also try this from the command line:
In one terminal:
$ adb logcat
From another terminal:
$ adb logcat -c
See if the first terminal continues showing logs after you do the clear from the 2nd one.
I'd check if all these reports are from the same API level, and if so, also try this from the command line:
In one terminal:
$ adb logcat
From another terminal:
$ adb logcat -c
See if the first terminal continues showing logs after you do the clear from the 2nd one.
ma...@google.com <ma...@google.com>
tn...@google.com <tn...@google.com> #10
Siva, this may be critical, WDYT?
st...@google.com <st...@google.com> #11
Already has fix, just need to merge.
ma...@google.com <ma...@google.com> #12
It's merged;
da...@google.com <da...@google.com> #13
We still need to merge into 2.2-release
da...@google.com <da...@google.com> #14
CL is up for review to be cherry picked into 2.2
st...@google.com <st...@google.com> #15
Triage: Madiyar has a CL for this, Esteban is reviewing.
st...@google.com <st...@google.com> #16
Triage: This is a regression in an important workflow but fix is not ready.
Still not blocking Beta3 for this. Esteban is working on fix, will have by RC1.
Still not blocking Beta3 for this. Esteban is working on fix, will have by RC1.
st...@google.com <st...@google.com> #17
Triage: Esteban: The fix should be landing today and we will test it today or Monday.
es...@google.com <es...@google.com>
st...@google.com <st...@google.com> #19
Triage: Fix checked in
Description
1.8.0_74-b02x64 Oracle Corporation, Linux(amd64) v3.13.0-88-generic unknown (2560x1600)
When I clear the logcat in the Android Monitor tab, logging stops and no more output appears in the monitor tab.
To restart, I have to run "adb logcat" from the command line.