Unable to connect ADB to Android Marshmallow (6.0.1) - android

I'm on a MacBook running macOS Sierra and I'm having trouble connecting Android Studio to the phone. The phone is a Samsung Galaxy A3 (2016) running the latest update - Android 6.0.1.
I've tried listing the devices using the command adb devices, but the list is empty.
When I connect the device I can hear a tone and the phone is charging. I do not get a notification when connecting the device, hence trying to tap on the notification and somehow forcing an MTP connection is impossible.
I've already activated the Developer Options and the USB configuration mode is set to MTP (Media Transfer Protocol). When trying to cycle through the available USB modes, if the phone is connected to the computer, it always reverts back to MTP automatically.
Trying to turn off and back on the USB debugging, or the Developer options didn't work. Also restarted both the phone and the computer but nothing changed.
Does anyone have a clue of what is going on?
From my research, the only thing that seems to have worked for other people is to tap the notification that is supposed to appear when I connect the phone to the computer.
Any help would be greatly appreciated. Thanks!

I presume that the cable is broken or just plainly wrong. Changing the cable should help.

Related

Android Studio - Device Offline

I am having a small issue with Android Studio. Whenever I put my phone into either of the front two USB ports, it shows my device as "Offline". If I use any of the back USB ports, it recognises the device perfectly fine.
I can charge and browse my phone fine from the front two USB ports. I have tried resetting ADB, and installing/updating Samsung USB drivers. I have tried enabling and disabling USB debugging - but no luck.
It really can't be an issue with the phone or with Android Studio, as in the back USB ports it works fine - surely it has to be an issue with the front USB port?
Anybody have any ideas on how I could solve this? (Other than just using the back ones!)
I have the same problem. I have 4 USB 3.0 ports on the computer and 2 USB 2.0 on the keyboard. Nexus 5 can be plugged and recognized on all of them while Samsung Galaxy S4 is not recognized on one of the keyboard ports and one of the PC ports. In my case it is the device I guess. You can try with another device to see.
You can try this:
Go to tools/enable adb integration and uncheck it.
now check it and run again. Next time, android studio will restart adb and it may find your device.

How to Connect Samsung Galaxy GT-N8000 with android studio

I have samsung galaxy note 10.1 and model GT-N8000, I want to connect it to android studio and want to run my own made app. But my android studio not showing anything and even pc do not detect it , not even popping up notification to show me that some thing is connected. I check this device to other computers but got same thing.
So what could be a problem. I have done resetting , but nothing is helpful, Updated driver, installed the google driver for usb, installed the universal driver. But nothing is really helping. So at least pc should detect it but its not.
Any solution. ? Please help
Make sure, that you chose Connect as Camera or PTP on your phone.
Go to developer settings and activate Adb-debugging or USB-debugging.
Also check, whether you have installed the correct drivers. Try to reinstall the correct drivers.
And make sure that neither your USB cable nor your USB-drive is faulty. If so try to use another cable and different usb-drive.
You could also try to connect your phone wirelessly to Android Studio
Couple of things you can try -
Go to settings, developer options and turn USB Debugging on. If it's off, Android Studio will not detect your phone.
If you PC is not detecting your device, either your USB cable is faulty or your USB drive. Only way to know is connect your phone to another USB-Drive or connect it using another cable.

Unreliable debugging with Android Studio and Samsung S5

I have problems with unreliable debugging with my S5 device on one USB port. I had no similar problem with my Nexus. I can work around the problem by switching USB port, but I really want to know what is going on. One day both USB ports starts to behave this way; and then I will have no clue if I don't fix it now.
Here is what I do to produce the problem.
I Connect phone to USB
This is what the ADB log says at that point
PropertyFetcher: AdbCommandRejectedException getting properties for
device c9c2d39f: device offline PropertyFetcher:
AdbCommandRejectedException getting properties for device c9c2d39f:
device unauthorized. Please check the confirmation dialog on your
device. DeviceMonitor: ExecutionException getting info for device
c9c2d39f
Please not that the phone actually connects -and that I can see the logcat etc on my device after I connect. I have tried to revoke debugging rights from the developer menu, and re-authorized the computer.
Start my app, that I want to debug
Press the "Attach debugger to process" icon (to the right of the regular "debug" icon)
At this point, the "Choose process" dialog appears with no running processes. The phone also disconnects the debugging session, and do not show up when running
Adb devices
At this point a restart of adb has no effect. The only way to get debugging back is to reconnect the phone to the USB port.
As I said, this only happens on one of my USB ports, it works on another. Does anyone have an Idea of what is going on here?
I had a similar issue on an older computer when the computer's motherboard was on its way out. Just as a precaution, you should back-up all of your work and try to determine if this is hardware or software related. From my experience, when USB ports start acting weird, it is usually hardware related.
When mine started to act up, it would connect and acknowledge a connected device, but the computer would throw all sorts of errors regarding reading the device files and even allowing the connection to remain. I tried re-installing software, resets, firmware re-installs, etc. I could not figure out what was going on, so I had my friend check it out (he has around 30+ years experience in computer engineering) and he determined it was my computer's motherboard that was on its way out. He said the only thing that would correct it was to replace the motherboard or get a new computer.
My S5 active showed 'offline' to ADB despite enabling/disabling debugging, updating the driver, and restarting the phone and computer. Finally - I move the USB plug from a HUB, and plugged it in directly from the phone to the PC - and it finally worked.
I had a similar issue too.
Try these steps:
Unplug the usb cable. Reboot your computer and samsung s5
In S5' Developer options, click "Revoke USB debugging authorizations" and press OK
In Android Studio, check "Tools | Android | Enable ADB intergration", if already checked, uncheck it, and then check it again.
Plug your samsung s5, and follow the dialogues instructions to allow this computer ...
Run your app
These steps should fix the problem.

Trouble connecting to LG phone with adb (Mac OS X 10.7.5)

When I run adb devices there are no devices showing as connected. My device is a LG Optimus Exceed 2 running 4.4.2
There are many of these posts around, so here's what I've done:
I'm using the cord that came with the phone. It charges and tries to sync photos, so it isn't an issue here. Switching usb ports and trying a powered usb hub doesn't affect it either.
I've added the vendor id (0x1004) to ~/.android/adb_usb.ini
Restarted and unplugged any combination of things you can think of
USB Debugging is on. And has been restarted. Same with Unknown sources.
I have never used EasyTether, nor is it installed anywhere on my computer.
Updated adb, updated my sdk.
Restarted adb server
Tried installing LG's drivers: http://www.lg.com/us/support-mobile/lg-VS450PP (They say they don't support Mac S/W upgrade, yet they have a package to install. No help there)
I have a Nexus S running 4.1 that works, and an old LG phone running Gingerbread that connect.
Any wizards out there who've already struggled with this who have advice?
I tried all of the connection types (charge, MTP, PTP) but perhaps not "Internet Connnection, modem"? You can change it by pulling down the system-wide drop down menu and touching "USB connection".
This is how I fixed it, but I thought I'd tried this already, so I can't guarantee it wasn't this in conjunction with one of the things done above.
PTP seemed to do the trick. Never had to do that on any other device...
I had the exact same problem. Selectin Internet Connection and then Ethernet as the USB connection type fixed it and everything is working as expected now.
I know this sounds like a stupid answer, but the same thing happened to me. It turns out the micro USB cord was just bad - which is weird, because it still charged the phone perfectly fine. After testing the bad cable unsuccessfully on a phone that had been recognized on my mac before, I switched to a different micro USB cable, and that made all the difference.
This is late in the game but I had an additional step to all the other suggestions. The phone was showing up in the System Profiler after I switched the usb mode to 'MTP' mode, but I didn't see any usb tethering options. After adding the phone's vendor ID to the usb ini file, enabling the developer and usb debugging, killing and restarting adb, I still didn't see my device in adb devices.
I finally had to download the Mac driver for the phone directly from LG.com. After installing and rebooting on the computer, the device showed up in adb devices.

Android Phone is not recognized on Ubuntu/Windows via USB

I am using Samsung Galaxy 3. I have turned on the debug option and have connected the phone via usb to ubuntu/windows but the phone is simply not recognized.
It was working perfectly fine i.e. recognized on ubuntu for me to work with Eclipse, until I decided to reboot the phone with usb still connected to the computer.
I have tried rebooting the phone multiple times and everytime, when I plug in the usb, it simply charges and no notification of usb connection ever shows up. What am I doing wrong here? Please help.
try using a different USB cable.
I had a similar issue where my phone had previously connected just fine, but months later it wasn't recognized...
turns out the cable I was using was a "charging only" cable and did not transmit data.

Categories

Resources