Status Update
Comments
bo...@google.com <bo...@google.com> #2
you explicitly mention "brew", which is nothing to do with us, but imply that when you downloaded "platform tools" (presumably from developer.google.com), that worked. so i think you need to talk to the (home?)brew folks...
hs...@google.com <hs...@google.com> #3
[Deleted User] <[Deleted User]> #4
hs...@google.com <hs...@google.com> #5
did you adb kill-server
to ensure you're actually running the new one?
[Deleted User] <[Deleted User]> #6
hs...@google.com <hs...@google.com> #7
yo...@intel.com <yo...@intel.com> #8
hs...@google.com <hs...@google.com> #9
Are you not gonna fix it even though it was working in the 33.0.3 release?
at the moment, this is at best on the "maybe there's the a problem?" pile. if macOS was as broken as you suggest, we'd probably have heard more than one complaint by now. so in the meantime, there are lots of other more bugs to look at, that we're already convinced are real.
you can make this bug more convincing by trying to work out what the actual variable is --- is it some specific model of mac? is it only some specific macOS versions? android versions? is there anything interesting in logcat?
pj...@google.com <pj...@google.com> #10
sa...@google.com <sa...@google.com> #11
pj...@google.com <pj...@google.com>
sa...@gmail.com <sa...@gmail.com> #12
Also the fact that it was working in the previous platform tools release, and then you assuming that I would make a bug up just because is pretty far out there.
not make it up, just be confused/mistaken. you'd be surprised how many of our bug reports are "user error" or "bad cable". is anyone else on your team having similar troubles? have you tried --no-streaming
to confirm it's specifically the streaming?
yo...@intel.com <yo...@intel.com> #13
su...@gmail.com <su...@gmail.com> #14
does export ADB_OSX_USB_CLEAR_ENDPOINTS=1
(
pe...@gmail.com <pe...@gmail.com> #15
This particular change was in response to a possible edge-case, which you might have been encountering.
And, as enh@ mentioned we have many cases of confusion (often from the part of the end-users). Thanks for your patience while we work through this!
Description
The CL causing the problem is the same one as Roman(rkir@) found in
I am going to revert the CL for the moment so that it won't impact emulator experience. However, I hope Intel can take a look as such "vcpu shutdown request" could be a potential bug.