It's too early to tell at this point, but the 10.8.1 update seems to have
helped quite a bit. I'm not longer needing to play USB Port roulette in
order to get the device to pick up. At least for now.
--
You received this message because you are subscribed to the Google
Groups "Android Develop
So, I'm also using a Thunderbolt Display. I plugged into the USB on the
display and that worked. So it looks like it has something to do with the
usb ports on the computer itself. I think they are USB 3.0 so maybe that's
the difference.
On Monday, August 27, 2012 12:36:01 PM UTC-4, Ian wrote:
>
Any update Dave?
I just got a new Macbook Pro with Mountain Lion and am having trouble
getting my phone to detect ADB as well. About Phone > Status shows Charing
(USB) but no indicator comes up on my phone for debugging and I'm not
getting any device in adb devices either. I'm also unable to mo
Macbook Pro, and it definitely does. Symptoms are the same regardless of
device.
On Friday, August 10, 2012 4:02:33 PM UTC-6, bob wrote:
>
> I have the Galaxy Tab 10.1, and it doesn't give me any trouble. Are you
> sure it gives you trouble?
>
> Also, are you on Macbook Air or Pro? I'm on Pro
I have the Galaxy Tab 10.1, and it doesn't give me any trouble. Are you
sure it gives you trouble?
Also, are you on Macbook Air or Pro? I'm on Pro.
On Thursday, August 9, 2012 9:32:47 PM UTC-5, Dave Smith wrote:
>
> Galaxy Tab 10.1, Nexus 7, Droid 2, Droid Intercept; I'm fairly confident
>
Galaxy Tab 10.1, Nexus 7, Droid 2, Droid Intercept; I'm fairly confident it's
not device/manufacturer specific. Wondering if there's a USB cache I can
clear...
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send
What other devices do you use besides Galaxy Nexus, Nexus S, and HTC EVO 4G?
I don't have any of those.
I use mostly a Galaxy Tab and haven't seen any adb issues with Mtn Lion.
On Thursday, August 9, 2012 11:36:03 AM UTC-5, Dave Smith wrote:
>
> This definitely does help, but only for 1-2 times
This definitely does help, but only for 1-2 times; then I have to move the
port again. This is definitely faster than rebooting the devices, though,
so this will be my new go-to workaround.
It just feels like there's a bug somewhere in how it picks up connected
devices, or how it reads the enu
Try using a different usb port. Fixed it for me. I'm using the new MacBook
Pro.
On Wednesday, August 8, 2012 9:28:16 AM UTC-7, Dave Smith wrote:
>
> I noticed that, as soon as I upgraded to Mac OS Mountain Lion (10.8) I
> have been unable to reliably get any of my devices to connect with ADB
>
I upgraded, and I have not seen that.
On Wednesday, August 8, 2012 11:28:16 AM UTC-5, Dave Smith wrote:
>
> I noticed that, as soon as I upgraded to Mac OS Mountain Lion (10.8) I
> have been unable to reliably get any of my devices to connect with ADB
> (Galaxy Nexus, Nexus S, HTC EVO 4G, jus
As an addition to this, I have noticed that I can almost always get the
devices to detect if I power them down and then back up while still
connected to USB. The problem arises trying to get ADB to pick them up if
they are connected while alive.
--
You received this message because you are su
11 matches
Mail list logo
