Develop Reference

Pixel 1 no longer detected by Android Studio 2.3.3 after Oreo Update

Android Studio 2.3.3 does not detect my Pixel 1 device when attempting to generate a build
It did detect it on Noughat, but not now that I updated to Oreo
I made sure to update Android Studio and all the SDK stuff
This seems like an issue other developers might be having
What are the steps to troubleshoot or make it work?
Thnx

Try to switch your phone in Transfer files mode. It helps me.

I had the same issue.
The solution to the problem was restart the adb service with rights of sudo.
sudo adb kill-server
sudo adb start-server
Аfter that the connection was established.

Not sure if this'll help, but it's worth a shot.
1) You might have adb off. Go to Settings, Developer Options, ADB. Make sure that it's on. You also have to make the device trust your development computer.
2)There's also a new version of Android Studio, 3.0. Try updating and see if that works.
3) It might be your driver. Make sure you have Google USB Driver or any other drivers applicable for adb
P.S. Make sure your cable isn't broken.

Ecilpse won't recognize my device after upgrading to Kitkat (4.4.2)

I just upgraded my Android device to 4.4.2 and now Eclipse will not be able to choose a running Android device when I want to run my project. The Android Device Chooser shows my device up with a serial number as "????????????" and Target as "unknown" and State as "??". Additionally, I have enabled Developer Options with USB Debugging.

what os are you using. i see that on my linux box with some devices. i normally kill adb and restart it as root and the devices shows up and works correctly. found that solution years ago on stack overflow or something like that. not sure if the same thing is needed with windows/osx. on linux, assuming adb is in your path:
$ killall adb
$ sudo adb devices
otherwise os you're trying to connect it to and the specific device information would probably be helpful in tracking it down.

I have a few suggestions. Try them in this order until it works.
Reboot the phone.
Try turning off and then back on "USB Debugging" on your phone (in Developer Options probably).
open cmd > go to the your Android SDK directory > type cd platform-tools > type ./adb kill-server > then finally type ./adb start-server
References:
Eclipse - Target "unknown" in Android device chooser
Android device chooser - My device seems offline

The solution for my device after updating was to completely uninstall the device driver from device manager and reinstalling it. I am using windows and my mobile was shown as Android Phone and not as Nexus 7. Home it helps someone.

Trying to debug apps from eclipse on android

I am developing apps for android and I bought an bq Maxwell 2 Lite, and I wanted to test them in the device, but i can't seem to do it... can somebody help me with that?
The android version on the device is 4.1.1 and I have enabled debugging throw USB.
Thank you all for your time and thanks for all the help
Carlos Morgado

So to test with any device you need
Install the driver for the device on your OS.
Enable USB debugging on your device.
Plug-in the device through an USB.
Run the app through the IDE and select the configured device to run the application
This should help you get started.

For using USB debugging in eclipse, make sure that you have all the drivers installed. Open sdk manager, under extras you can see Google USB drivers, make sure that this is downloaded.
If after this also it didn't work, go to device management if you are using windows and find your device. Right click on your device and update device drivers, update from my computer and give this folder sdk folder\sdk\extras\google\usb_driver. Set platform-tools folder in your path variables and run these commands:
adb kill-server
adb start-server
You can see list of attached devices using this command:
adb devices

Android 4.2.2 Device Offline

I've read several users having similar problems, but none of the solutions I've found have solved my issue.
I have several Nexus devices running Android 4.2.2 and they all show up as offline and none of them show a prompt when I plug them in.
I already tried:
unplugging/plugging them in
switching off/on usb debugging
restarting computer, nexus devices and the adb server
reinstalling drivers and even switching drivers to Samsung ADB drivers
Confirmed I'm running adb 1.0.31
Made sure my path points to adb.exe
Deleted any old adb.exe files on my entire computer

if you have properly installed adb and you tried all of the remedies mentioned at above the listen to my remedy:
The reason to appearing "device offline" in android 4.2.2 is that android has a security feature in 4.2.2 that create a whitelist of usb ports that can be used as debugging port.
After plugging deivce in usb and entering the command "adb devices" a popup window will be raised in your device and ask you to accept the connection:
After accepting RSA fingerprint of you usb you can now issue the "adb devices" again and see the device is no longer offline,
If you dont see the popup window, the reason is your adb version is old, your adb version must ne at least 1.0.31 (you can see the version using the command "adb version"). if version is older than 1.0.31 then update your platform-tools package using latest updates from google. You can find the latest version in sdk-repository. find platform-tools*.zip associated with your OS and download from https://dl-ssl.google.com/android/repository/platform-tools*.zip .
for example version 19.0.1 of platform-tools can be downloaded using these links:
For linux: https://dl-ssl.google.com/android/repository/platform-tools_r19.0.1-linux.zip
For windows: https://dl-ssl.google.com/android/repository/platform-tools_r19.0.1-windows.zip
For MacOSx: https://dl-ssl.google.com/android/repository/platform-tools_r19.0.1-macosx.zip
that's it

Finally found the answer. I had installed "SnapPea", which apparently ships its own ADB.exe. It was somehow getting in the way. Uninstalling this poorly written software and rebooting fixed the issue.
As an Android developer, this type of thing is scary. Was it sending everything I did to a home server somewhere? Why should any software install ADB on a customer's computer?
This is probably the reason Google had to add this security measure in the first place...

I got the same problem and it was just my ADT Eclipse plugin wich was out of date.
I install all the updates and everything went ok.
I don't know if its the same for you, sometimes we just forgot to put the updates...

For me it was working, but a minute later (upon reconnecting the usb cable) the device was 'offline'. I got it 'online' again by disabling and then re-enabling the USB Debugging option in the developer settings of the device.

Adb can't find my device

I was developing an android application from Eclipse, connecting my Acer ICONIATAB A 500, with Android 3.0.1. And I did not have any problem.
Now I'm trying to developing the same application on Acer ICONIATAB A 501, with Android 3.2
and my ADB can't find the new device, while Windows can find it! I set in my tablet Debug USB option active, and I installed the appropriate driver on Windows.
I installed even the last Google USB driver (Rev. 7)
I tried to list the device find form adb with command
adb devices
from command line, but List of devices attached is empty.
What can i do?

execute these line
adb kill-server
adb start-server
if it is mobile device check that in settings, developers options , debugging mode is checked or not

You need to install LGUnitedMobileDriver package from the LG website, even though Windows 7 automatically installed USB drivers for the phone.

Try to update your Android-SDK on your computer (in Eclipse or whatever IDE you are using), this helped me solve a similar Problem.