ADB does not show Pixel XL on Macbook Pro (2016) [37127698]

Fixed

Bug

[AOSP] Version-Studio-2.2

adexe s nau

Status Update

No update yet.

Description

fr...@gmail.com

created issue #1

Nov 23, 2016 07:47PM

My Pixel XL does not appear in the list of available devices when running "adb devices" or in the devices list in Android Studio. I have managed to get it running 2x out of hundreds of attempts but there is no specific logic to the success events.

I have tried running "adb kill-server", restarting the phone + mac and resetting USB Authorizations in the developer options.

When I plug in the device I see the developer notification and "USB debugging connected", but I cannot use the device as a target.

The mac console is reporting:

kernel AMFI: allowing exception handler for 'studio' (64152) because SIP is disabled.

As well as:

icdd #ICDebug - 511:{ICDDMessageCenter.m} (Pixel XL is unavailable)
icdd #ICDebug - 51:{ICWiredBrowser.m} (USB terminate)
icdd #ICDebug - 344:{ICWiredBrowser.m} (--> USB Terminate)
icdd #ICDebug - 363:{ICWiredBrowser.m} (Reclaiming Resource: Pixel XL)
icdd #ICDebug - 371:{ICWiredBrowser.m} (1 USB Descriptions Managed)
icdd #ICDebug - 373:{ICWiredBrowser.m} (<-- USB Terminate)
icdd #ICDebug - 471:{ICDescriptionBrowser.m} (--remDescription: [ USB ] : Pixel XL)

I am guessing this has to do with some 2016 macs shipping with System Integrity Protection disabled, but I am logging the bug just in case it is something deeper.

Comments

lz...@zitseng.com <lz...@zitseng.com> #2Nov 24, 2016 02:41PM

We use build flavours heavily with a lot of common code. The refactoring support in AS is really good but it continually catches us out when it doesn't work across all flavours in a project. It's a big gap for serious product development.

lz...@zitseng.com <lz...@zitseng.com> #3Nov 24, 2016 02:42PM

We at my company need this same feature. We have a lot of white labels and need refactor the same class across flavours. :(

me...@drewzh.com <me...@drewzh.com> #4Nov 24, 2016 08:33PM

I need this feature too...

ka...@gmail.com <ka...@gmail.com> #5Nov 27, 2016 06:09PM

+1, I need this very badly

fr...@gmail.com <fr...@gmail.com> #6Nov 29, 2016 05:00PM

+1 My company also need this feature.

lz...@zitseng.com <lz...@zitseng.com> #7Nov 29, 2016 09:02PM

Can we atleast know the status of the issue please? Will it be fixed or is it in low priority. It's been 4 years.

lz...@zitseng.com <lz...@zitseng.com> #8Nov 29, 2016 09:03PM

We are currently investigating possibly solutions.

ka...@gmail.com <ka...@gmail.com> #9Nov 29, 2016 10:29PM

+1 This will exclude a lot of unnecessary work. In my work I have 25 flavours. :(

je...@gmail.com <je...@gmail.com> #10Dec 11, 2016 07:34PM

+1 .. we need it as well...

[Deleted User] <[Deleted User]> #11Jan 10, 2017 03:10AM

Any update on this?

gu...@gmail.com <gu...@gmail.com> #12Jan 16, 2017 08:34PM

We also need this feature...please...

jb...@gmail.com <jb...@gmail.com> #13Jan 24, 2017 10:01PM

I would like to vote for this feature as well.

yi...@google.com <yi...@google.com> #14Jan 30, 2017 11:45PM

lz...@zitseng.com <lz...@zitseng.com> #15Jan 31, 2017 01:13AM

Build flavor source code is useless until this is fixed.

lz...@zitseng.com <lz...@zitseng.com> #16Jan 31, 2017 01:14AM

yi...@google.com <yi...@google.com> #17Feb 1, 2017 03:57PM

ka...@gmail.com <ka...@gmail.com> #18Feb 1, 2017 05:17PM

+1 "Build flavor source code is useless until this is fixed." - agree

ka...@gmail.com <ka...@gmail.com> #19Feb 1, 2017 05:18PM

dr...@gmail.com <dr...@gmail.com> #20Feb 25, 2017 08:58PM

My team are heavy users of Android Flavours and the IDE remaining semantically aware of all flavours besides the currently 'focused' one, for refactoring and searching purposes, would be a major productivity boost.
Indeed, the current state almost feels like flavours are only partially supported in the IDE.

ph...@bayfmail.com <ph...@bayfmail.com> #21Mar 5, 2017 04:35PM

Have the same problem, USB C to USB C often doesn't work at all and requires a reboot, after that it's temperamental and often requires switching ports. All but the standard charging mode cause the ADB connection to drop.

It's marginally better with USB A to USB C via a converter, ADB is a bit more stable but still can't use thins like file transfer.

ec...@gmail.com <ec...@gmail.com> #22Mar 17, 2017 12:03AM

Google / Apple get this fixed

du...@gmail.com <du...@gmail.com> #23Mar 18, 2017 03:19AM

I just tried to use USB-C cable that comes with MacBookPro charger (Apple one) and it worked. Will see how it goes, but works fine last couple of hours.
USB-C cable that came with my Pixel phone didn't work.

ec...@gmail.com <ec...@gmail.com> #24Mar 22, 2017 05:15PM

Interesting update Dudka.pa. It should definitely work though with the USB C to C cable that comes with the pixel. I've also tried a high quality Anker USB 3.1 cable from amazon between my pixel and 2016 Macbook USB-C port. I'm guessing its a mac/OSX side issue thats not detecting it correctly but not sure.

ea...@google.com <ea...@google.com> Mar 22, 2017 08:57PM

Assigned to en...@google.com.

en...@google.com <en...@google.com> Mar 22, 2017 09:39PM

Reassigned to jm...@google.com.

nd...@gmail.com <nd...@gmail.com> #26Apr 3, 2017 06:52AM

Has anybody found a solution to this problem? I am using an older Mac. I can see the files on the Pixel using Android File Transfer, but I cannot connect with the adb tools in the console; even after updating.

rs...@gmail.com <rs...@gmail.com> #27Apr 8, 2017 04:26PM

Connecting my Google Pixel phone to a 2016 15" MacBook Pro using the type c to type c cable provided with my Google Pixel phone, System Information does not show the presence of any USB devices. However, attaching a USB Type C connected thumb drive results in both the thumb drive and the Pixel Phone being recognized in System Information. With the thumb drive attached, Android File Transfer functions with the Pixel Phone. Weird....

fr...@google.com <fr...@google.com> #28Apr 14, 2017 09:19PM

Contents scrubbed on user request by admin.

Message last modified on Apr 14, 2017 09:19PM

bf...@gmail.com <bf...@gmail.com> #29May 11, 2017 09:41PM

Is there any work being done on this issue? Is there any hope for this to be fixed? It's been a VERY long time with no fixes so far, for something so fundamental as this that should never have made it into production in the first place...

Thanks

bo...@gmail.com <bo...@gmail.com> #30May 27, 2017 06:58PM

I see this as well, a straight usb-c cable doesn't work, I have to adapted from c-a and then a-c for the pixel or nexus 5x to be recognized by adb or even to transfer photos. Please get this fixed!

en...@google.com <en...@google.com> May 27, 2017 07:52PM

Reassigned to ba...@google.com.

gu...@gmail.com <gu...@gmail.com> #31Jun 1, 2017 01:05PM

This actually seems to be fixed in Android O Beta 1
The device is now detected 95% of the time it is connected (the other 5% the macbook kernel panics)

to...@gmail.com <to...@gmail.com> #32Jun 13, 2017 03:31PM

> (the other 5% the macbook kernel panics)

gg apple

ec...@gmail.com <ec...@gmail.com> #33Jun 13, 2017 08:53PM

Agree, can someone from google step in and acknowledge this, give a status etc?
It's been broken for months.

[Deleted User] <[Deleted User]> #34Jul 25, 2017 04:22PM

I am also experiencing the issue. I seem to be able to reboot my mac, and revoke usb authorizations to get it to work until I unplug the USB cable again..

ba...@google.com <ba...@google.com> #35Aug 25, 2017 06:21PM

The type-c stack was revamped and bunch of fixes were made in Oreo.
Please attach Bugreports. Happy to triage and see if that was an issue fixed in O.

bo...@gmail.com <bo...@gmail.com> #36Aug 26, 2017 01:51AM

Nexus 5X on beta-program Oreo does indeed work for me now on a straight usb-c cable to new mac pro 15".

ma...@gmail.com <ma...@gmail.com> #37Aug 26, 2017 02:24AM

Pixel XL on Oreo final works fine on a MBPr 13" no touchbar 2016.

ba...@google.com <ba...@google.com> Mar 6, 2018 02:02AM

Marked as fixed.