Reputation: 309
Constant issue with being able to connect an Android device via USB to Android Studio running on a Mac.
Tried numerous things like:
trying adb kill-server
and then adb devices
, which usually resulted in:
List of devices attached
daemon not running. starting it now on port 5037
adb E 655 23135 usb_osx.cpp:327] Could not open interface: e00002c5
adb E 655 23135 usb_osx.cpp:289] Could not find device interface
daemon started successfully
But not actually finding the connected device.
Upvotes: 8
Views: 36405
Reputation: 683
Not sure if this will help everyone but figured I would share my "odd" solution.
So I literally just switched over the connection of my cable from the right side of the Mac over to the left hand side and then it worked! Android Studio recognized my device.
Details of my situation:
The regular USB with the adapter was plugged into my laptop on left hand side, top port (if it makes any difference here). The USB C part of my cable was plugged into my device.
Hopefully this helps out people!
Upvotes: 0
Reputation: 7772
My limited mobile developer-experience is on xcode so attaching an android-phone to android studio was not straigtforward. Found this thread where I tried the suggestions to no avail. Then a new search-result pointed to Android's getting started guide, macos in my case. From the guide.
On your Android device, tap Settings > About phone.
Tap Build number seven times.
Return to Settings and then tap System > Developer options.
If you don't see Developer options, tap Advanced options
Tap Developer options and then tap the USB debugging toggle to turn it on.
Upvotes: 0
Reputation: 824
I just wanted to write it down in case someone else comes across this issue.
It took me more than a couple of days to solve this while I was banging my head trying to understand what seems to be the problem.
Note: For me it was a cable issue.
I have Nexus6P with 2 original cables:
The problem was I was trying to hook the cable 1 directly from the Nexus to the Mac Pro (which didn't work since I think the Mac has a thunderbolt protocol on the Type-C inputs)
Then I tried a Type-C to regular USB cable with an adapter from to make it Type-C to Type-C (bear in mind this wasn't the original cable I got with my phone)
Only when I used the original short cable (cable 2) with an adapter it worked.
Although the non-original cable I used was a high-end cable - it still didn't work
Hope it helps other people who struggle with this
Upvotes: 13
Reputation: 309
There are some great responses that worked for others, like this one or this one which seemed to work for others.
In my case, the issue was Tizen Studio (I was working on a watch app for Samsung Gear). Through this poster's research, found that the adb error could not open interface: e00002c5
implies that the usb device is already in use by some other driver.
So it seems Tizen Studio takes up the usb driver resource even though it is not using it. Quitting the application will automatically allow adb devices
to list your device and run the project on it.
Hope this helps other lost souls.
Upvotes: 1