Fixed
Status Update
No update yet.
Comments
me...@thomaskeller.biz
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
ch...@google.com
$ 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.
vi...@google.com
Thanks for the feedback. We are sorry it took so long for us to get to this report. We would really appreciate it if you could confirm that this is still an issue for you and if so we will route it to the right team.
For information of what’s needed in the report please don’t forget to read this guide athttps://developer.android.com/studio/report-bugs
For information of what’s needed in the report please don’t forget to read this guide at
me...@thomaskeller.biz
Hey Torsten, can you refresh my memory? You're using a Nexus 6 device, right?
vi...@google.com
ko...@google.com
ko...@google.com
ko...@google.com
No, Nexus7 (2013), Android build MMB29K dev-keys.
ko...@google.com
We got another report from an external dev posted in dup
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
sp...@google.com
+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.
ko...@google.com
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.
sp...@google.com
Siva, this may be critical, WDYT?
sp...@google.com
Already has fix, just need to merge.
ko...@google.com
so...@google.com
It's merged;
Description
Version of Gradle Plugin: 2.0.0-beta6
Version of Gradle: 2.10
Version of Java: 1.8.0
OS: OS X 10.11
Steps to Reproduce:
- create a new build type configuration directory, like `releases/src/res/values`
- add a new file values.xml and add a tools-NS like this:
<?xml version="1.0" encoding="utf-8"?>
<resources xmlns:tools="
<string name="server_url">https://...</string>
</resources>
Expected:
Everything works
Actual:
Error "URI is not registered"