I have a Pixel 2 that is unlocked and has USB debugging enabled. Yet if I plug it into my computer, it only ever shows charging. The USB cord works to connect other devices for data transfer no problem though, so it's not the cord. I have no trouble connecting any other devices to any of my ports, even the original Pixel. I am running Windows 10 pro. The Pixel 2 connects fine to an older computer running Windows 10 pro. I have Android Studio 3 and the usb driver from Google tools. If I go into device manager and click on the Pixel 2, it says I have the most updated driver if I try to update. I have tried disabling and reenabling USB debugging, revoking permissions, etc. Nothing causes it to do anything other than charge. There is no pull-down menu either to select different options.
How can I get my Pixel 2 to be seen by my computer?
I had the same issue connecting my S7 Edge to my MacBook Pro running Android Studio. Make sure that you have the "USB Configuration" setting in the Developer Options to be set to "MTP" ("PTP" on newer phones).
One last ditch effort, a lot of the times when my phone would not show up, switching USB ports on my computer would work most the time. I am very unsure as to why it would, but it would. I thought this was just my situation, but it's worth a try on your end.
Plug cable into device by interchanging upside down. This is hilarious but it worked for me.
I had the same issue connecting my Google Pixel 2 to my Android Studio and this works for me:
Settings -> Connected devices -> USB -> Transfer files (otherwise it's only charging your phone by default)
Settings -> System -> Developer options -> USB debugging (turn this on)
A question prompts up and you need to allow your computer to see your device
lo and behold, my Android Studio can see my Google pixel 2.
My problem ended up being that my Pixel 2 wouldn't connect to my MacBook Pro when using a USB 3.0 cable. It would charge fine, but the mac wouldn't detect it (in any USB Configuration) and the trust device dialog or USB debugging notification never appeared on the device.
Using a chain of cables/adapters that included a USB 2.0 component fixed the problem, e.g. Pixel 2 -> USB-C to USB 2.0 cable -> USB to USB-C cable -> MacBook.
It doesn't appear this problem (and solution is limited to just me
I tried all of the above, several times over the last few months and the only way I am able to get it to work (temporarily) is to reboot my MacBook Pro. It will work for the rest of the day, until I sleep the MBP again.
After my Pixel 2 updated to Android 9, I had to clear the cache of the Media Storage app for my phone to be recognized by my computer / have my phone recognize it was connected to a computer.
My phone has to be plugged in at Windows 10 startup time for this to work.
I connected my phone with USB-C and restarted Windows 10.
In Android,
Search Settings for Media Storage
App info -> Storage -> Clear Cache
Phone prompts me (immediately in my case) with 2 notifications, 1 notification that USB Debugging is enabled (follow steps from this answer), and 1 notification that it is charging.
Tap the charging notification for more options. What I see by default worked for me. I see "USB controlled by: This device" and "Use USB for: No data transfer" (Selecting "File transfer" also works for me)
In Windows 10's Devices -> Bluetooth & other devices -> Other devices, I now see Pixel 2 (Or "MTP" if I had selected "Use USB for: File transfer" in step 4.
The first time you do this, Windows should have sent a notification that the device is being set up (I assume it installs the drivers).
I can now see my Pixel 2 as a connected device in ADB.
Solution based on this thread:
https://productforums.google.com/d/msg/phone-by-google/JlooQqANO2A/d_n-MGIHAgAJ
For debian/ubuntu only
If you try to use the adb in {your sdk location}/platform-tools/, you will see the message
no permissions (user XXX is not in the plugdev group); see [http://developer.android.com/tools/device.html]
Turns out, you should be using another package with some custom rules of some sort (I have no idea what plugdev group means), and basically you just have to
apt-get install android-tools-adb
and use that adb instead.
Related
I need to know how to make Windows 7 forget it ever connected to my LG G Stylo phone. I have three devices that I use in Android Studio development. For some reason, this one is no longer being detected by the ADB. Something has happened to make it no longer show up, because it did a couple of weeks ago.
AS's ADB will detect my other two devices, and this device shows up in the in the ADB on another computer. I have tediously gone through the registry and removed everything referencing the Stylo, but it still will not show up in AS's ADB.
Thanks for the help!
John
To start, I have just purchased the LG Stylo 3 plus and ran right into this situation. TO repeat the basics you need
With Android Studio shut down...
Turn on Developer options (tap 7 times on build number in settings
(Settings>System>About Phone>Build Number
Turn on USB Debugging in Developer Options
(optionally) check on the type of USB connection, MTP or PTP should
work
(Optionally) Because I did it, also do a revoke USB tap.
Here was the key for me. I needed to install the LG USB Windows Drivers for my Windows 7 (I'll try 10 tonight and update). Go to this page
LG Drivers and firmware
and either type in model number or browse to find device. LG has a nice interface to install the Windows Drivers. I recommend the Support tool to verify the device as the up to date drivers as well. Start Android Studio and to test I just started the app in debug mode and went through the process of setting up ADB for using the new;y connected device.
Developer options" has to be ON in order to make AS see the device
If even though device manager you can't saw the device, Windows couldn't find drivers.Maybe the drivers are hidden on the device otherwise download it and install it.
If that doesn't work:
Shut down
Hit F8 (or whatever gets to startup options screen on your computer)
Disable Driver Signature Enforcement.
Run driver
Having trouble with Android Studio connecting to my Pixel phone. I'm sort of out of ideas and am looking for suggestions. I feel like I'm missing an obvious step.
Things I've done:
Made sure developer options is on with USB debugging on.
Have tried switching from MTP to PTP.
My computer recognizes the Pixel just fine under windows 8.
Made sure android studio is up to date including "Google USB Driver" installed under SDK tools.
My previous phone (Droid mini) connects just fine.
Tried different USB ports for the cable to my phone.
Encountered this problem today as I tested on other people's phones. I found 4 possibilities why a device may not be recognized:
Case #1: The USB cable supports charging but not data transfer.
Case #2: Developer options haven't been enabled on target phone (see: https://www.verizonwireless.com/support/knowledge-base-215055/)
Case#3: Developer options enabled, but USB debugging hasn't been enabled. Go to Settings > System > Developer Options > USB Debugging
Case #4: Some (but not all) phones require MTP transfer mode to be enabled. It can be enabled by sliding a finger from the top of the screen and tapping "Android system - USB charging this device" > Tap for more options > Transfer files.
Hope this helps someone ^_^
EDIT:
It's come to my attention that there's another possibility. I don't know what causes this, but if you get really stuck, sometimes you need to go into Settings > Developer Options > Debugging > Revoke USB debugging authorisations. This will reset your device USB pairing fingerprint which will often bring the phone back as a device target in Android Studio.
In Pixel devices USB debugging is enable when:
Step 1. Enable Developer Options to double tap on Build Number, you can get it by search with build in setting.
Step 2. Enable USB debugging Option, to enable this just to search usb debugging in settings.
Step 3. Pixel devices require USB tethering mode to be enabled, It can be enabled by sliding a finger from the top of the screen and tapping "Android system - USB use for " > Tap on USB tethering.
After completion of all these steps you will be able to use you pixel device as enabled for debugging in SDK.
Android Studio / SDK Manager will provide the driver but Windows might not automatically install it for your device. Try checking the device manager, unplugging and reconnecting the device or let the device manager search for new hardware.
The driver (when installed via SDK Manager) will be found by windows when provided with the SDK root directory, usually AppData/Local/Android/sdk
I have had the same trouble with my Google Pixel 2 (Android 9); I couldn't connect it to ADB in Android Studio 3.3. In my special case, AS runs on Kubuntu 18.04 in a VMware Workstation on a Windows host.
I have to do following steps every time I want to connect the phone (the phone is already in developer mode):
Plug phone via USB into the computer (and connect it to the VMware guest, if you use it)
Phone: Swipe down the notification bar, there should be a message 'Charging the device via UDB'
Tab on it and change the 'Use USB for' from 'No data transfer' to 'File trasfer'
You can activate 'USB debugging' on your phone's developer screen before or after this procedure, both works for me.
That happened to me with a generic Type C to USB Cable (White Cable in the Picture Attached). Then I bought another Cable (The Black one in the Picture Attached) and it worked perfectly. It was the Cable. Make sure to have one that says "Data & Power".
Hope it helps!
The solution to device not found when running adb devices from windows 7 standard terminal for my Pixel 4a 5g was to simply update my google USB drivers. https://developer.android.com/studio/run/win-usb
If dev options aren't available, double click the build number until a notification appears stating dev options have been enabled.
When I connect samsung tab s2 to pc windows 7, initially windows does not recognize usb device, or MTU driver failed install, many error.
I uninstall all other usb driver, still has problem.
samsung android usb driver, unknow device, usb device disconnect constantly
MTU usb driver, not installed properly.
not sure what is the cause.
=============================================
Updated:
The problem solved by Buy a non-samsung, non-OEM cable.
This this so bad, that samsung OEM cable is the reason of all trouble.
I end up spend $10 buy any brand(except Samsung) cable on amazon.
samsung android usb driver, unknow device, usb device disconnect constantly
MTU usb driver, not installed properly.
Samsung OEM micro usb cable is the ultimate cause, when you move or touch the cable around, it get disconnected, device manger constantly refreshing, constantly scan for hardware change.
Replace Samsung OEM micro usb cable with any other brand will fix all problem.
==========================================================
For my HP Desktop.
1) repeat press F10 when power on, get into BIOS configure.
2) on top menu - advanced - device option - USB 3.0 support (enable it), default is disabled.
3) sometime device manager refresh scan for hardware change, then unknow device,
this is because windows install driver from windows update, should disable it, should let windows install driver from samsung driver folder only,
Disable Searching Windows Update for Device Drivers
Click Start, right-click Computer, and then click Properties.
In the Tasks list, click Advanced System Settings.
On the System Properties dialog box, click the Hardware tab, and then click Windows Update Driver Settings.
Select Never check for drivers when I connect a device.
Click OK twice, and then close the System dialog box.
I believe this is the real cause for all trouble, such as MTU usb driver not installed properly, samsung android device not recognized by PC, android usb device constantly disconnect and reconnect and failed to recognized. etc.....
if you use android simulator, must enable bios vt-x visualation technology from bios
bios - security - system security - visualation technology - enable.
Leeds VT enable.jpg
below are try may not be the cause.
=====================================================
try:
1) remove previously installed blue tooth usb device. (or SD card), they may be the problem.
2) remove google androic studio ( maybe problem )
3) unplug internet. ( I see samsung continuing removed add, remove add, not sure if computer keep removing hardware)
=========================
windows, device manager, 'scan for hardware change' constantly , android device disconnect constantly,
Scroll to the right and type 'Power Options' in the search field and click on it.
Click 'Change plan setting' on your chosen plan.
Click 'Change advanced power setting' on your chosen plan.
Find 'USB settings' and open.
Find 'USB selective suspend setting' and change it to disabled.
This fixed ALL my USB 3.0 issues. Not mentioned anywhere else!
Its a BIOS ISSUE. Hopefully your computer has this option.
Go into your BIOS and TURN OFF "Legacy USB Support".
If you want even more speed, (there is a catch), Switch from "quick remove" to Buffering. BUT YOU HAVE TO DISCONNECT THE DRIVE WITH THE REMOVE USB DEVICE OR POWER DOWN THE COMPUTER FIRST.
hey guys here is the fix if you are having trouble with your Windows 8.1 all USB devices keep disconnect / reconnect with power saving off ... this took me two days to try to figure out what the heck was going on so i luckily found the fix hope this saves you alot of time an you dont have to downgrade to windows 7 if you love windows 8.1 good because its not what virgin of windows you have it dosnt matter what OS your on its clearly your BIOS so i suppose many people having this problem has an ASUS motherboard so heres the fix
restart your computer an go into your BIOS Press F2 repeatedly or THE DEL Key for those who dont know how to go to BIOS
2.Go into Advanced mode in your BIOS by clicking F7 on keyboard
3.Go to Advanced Tab Scroll down to USB Configuration Scroll down to XHCI Mode yours Will probably be on Smart Auto or Auto so Disable it Completely an Save changes F10 an click yes an exit it will auto restart your computer an BOOM You have Fixed the Problem by simply reading this post Hope this helps guys
my samsung tab s2 and tab pro 8 can't connect to pc windows 7. device manager showing unknow device, device manger constantly refreshing. I try million way, find out Samsung OEM micro usb cable is the problem, I replace it with other brand from best buy, all problem fixed.
I had exactly the same issue, and I think it is related to actual motherboard driver (Windows 8, 10). I have several android devices and all of them are connecting/disconnecting every 1-2 sec.
Things I did:
My BIOS doesn't have any configuration to switch USB 3.0 support
From Power Options USB selective suspend setting set to disabled (didn't fix the issue for me)
In Android dev options change USB configuration to MTP (also didn't fix the issue, as it was automatically switching back to Charging after ~10 attempts to connect)
Fix:
Disconnect all USB devices. (very important as disable operation might not be available)
Open System Properties -> Device Manager
Disable USB Root Hub (USB 3.0)
Disable Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
Connect your usb devices including android
Enable Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
Enable USB Root Hub (USB 3.0)
Btw it works fine on windows 7 before it makes updates to motherboard drivers, usually after first updates you can see that usb 3.0 driver support is enabled, and same issue appears.
Hope that will help someone.
Discovered a random weird solution that worked for me (Windows 8.1, Samsung Galaxy A20, Dell Lattitude laptop). The A20 uses a USB-C connector which, supposedly, is non-polarized unlike earlier versions of USB. I flipped the cable over in the phone and the problem went away. Go figure... It probably is a mix of MB hardware, drivers, and who knows what else. Users are on their own as standards evolve.
I recently bought LG G3 and I have enabled debugging mode but Eclipse is still not recognizing it, back when I used the Galaxy S3 for development I had to install Samsung Kies. The G3 drivers are installed and I can see it in My Computer, do I need something like the Kies but for the LG? If so can someone please post a link for that?
See update below
I found the answer that worked for me.
When you plug in the phone, bring down the status shade, pick the USB item ("USB connected") then, from there, pick "Internet connection" -- I chose Ethernet, but I'm not sure the choice matters on the dialog that pops up..
This enables USB debugging to become active; leaving it on Charging, MTP, or PTP does not work.
Once you do this, you can follow #Siddharth's steps to setting the ADB drivers, if needed. (You may need to use the actual LG drivers and not the Google drivers, but once I got this far, it was just like any other phone.)
Caveat
For me, even after going through this once, I still get the "installer" first and then have got go in and choose the "Internet connection" again. But, at least it works.
Update 10 Dec 2014
A recent firmware update has, indeed, removed the "Internet connection" as an option. Instead, PTP now works. I still get the "Connected as an installer" notification every time I plug in the phone and have to click on the notification then click on "Camera (PTP)" -- or wait about a minute. It's slightly better than what It was.
Also note: When this change occurred I had to install the drivers again for the phone, since it comes up as a different type of device when "Camera (PTP)" is chosen than when I used the "Internet connection" option.
For me, this has solved the problem: simply go to LG's website, http://www.lg.com/us/support/software-manuals, select the model (I have selected 'D850') and go to Software Updates tab where you can download the driver. I have installed it and then Eclipse recognized my device. I'm working on Windows 8.1, by the way.
yakobom
After a lot of searching and trying all solutions still I couldn't connect my LG G3 to eclipse on mac. Finally I find this solution, it works for me hope for you works too:
Install LG USB driver for mac
Go and enable developer mode in your G3 (Setting->About phone (in General Tab)--> Software information --> Tap 8 times on Build Number) then you will see the message which says the Developer option is enabled
In this step you expect that after connecting your mobile via USB cable, the Eclipse detect it
But for me it didn't happen
in this step you need to go (Setting--> Developer Options--> and turn off this option from above green (on/off) switch then again switch on this option from same place (If you don't do this step the "USB Debugging" mode will stay fray and you can not enable it)
In Developer Options menu scroll down until find the "USB Debugging" then tic it and enable it.
almost finished , you should back and configure running mode for your application and see the G3 in your connected usb devices
Try this solution :
Right click on My Computer --> Properties --> Device Manager
Right Click on your device --> Update driver software
Click on "Browse my computer for driver software"
Give path of your android sdk like "D:\Android_Sdk\sdk\extras\google\usb_driver" and tick "Include subfolders"
Click
Now repeat the steps till "Browse my computer for driver software".
Then click on "Let me pick form list of device drivers on my computer". Click on the first option and click next and then click yes. Drivers will be installed for your device.
Hope this helps.
Change the USB mode to PTP and you will get the RSA prompt.
Within the prompt, select allow it > ok and you are done.
This worked for me when I had the same problem on a Mac computer.
To contribute to possible solutions for this fix: I am using an LG G3 on a Mac.
In my case, ADB saw it as a device when I checked, and the Mac showed the device information in the System Information window, yet Eclipse did not see it. I also did not get the RSA confirmation pop-up when I connected the device through USB.
To fix, with my G3 connected, I selected the USB PC Connection (either from the navigation bar or through the settings) and changed it to be Send Images (PTP). Once this was on, I was given the RSA pop up and Eclipse recognized the phone in the Run Configurations window.
If you have this problem on Ubuntu; here is what I did to get it working:
Switch to PTP from MTP on the phone (this assumes you're connected via USB)
Disconnect the USB cable
Go to settings -> developer options and select revoke usb authorizations then ok
Make sure USB Debugging is checked
Reconnect the USB cable and your phone will say its connected as an installer; wait a minute or three and debugging mode should appear on the status bar (on the phone)
Open Eclipse and go to DDMS
Select "reset adb" in the dropdown if your phone isn't appearing yet
Working on Windows 7. All of the solutions from other sites didn't help (i.e. restarting adb and switching between MTP, PTP, Charing). In the end, I found this article (http://www.technobuzz.net/install-lg-g3-lg-drivers-windows-mac-usb-adb/), which contains links for the necessary drivers for the lg g3 (and some others I think). This did the trick and made the RSA key fingerprint dialog appear finally. After confirming, adb and eclipse recognize my device perfectly!
I had this buggy error with my LG Optimus L3 phone connecting to Win7/8 machines!
Cause: Device Driver was missing as it seemed at the end when I fixed it!
How to Fix:
Search through web (using Google) "LG < Your_Phone_Model Number > Drivers Download".(Ex.:- Go to About phone in your settings list > Model Number, for me it's LG-E400f)
Mostly the first few links are related to the required Device Driver download page.(Ex.:- for me I got the following link and for each device driver LG or most of the other vendors/manufactures have that kind of a Manuals and Drivers Page) Visit that page mentiioning about software update and drivers downloads.
Scroll down to the section of "Manuals and Software Update" and doing just the Step 1 was enough for me, which is "Install the USB DRIVERS "
Download it(for Mac or Windows) > Install It > Check Your Eclipse ADT > and it should be visible under Devices tab by now
Cheers!!!
Hope this helps to someone else to clearly get to the solution!
it seems that Eclipse shows the offline mode for lg G3 and some newer devices
and there is no way no use these devices for ADB debugging
there is a way
I am using windows 10
1- download this 11 MB file < http://dl2.uncox.com/android/upload/platform-tools-v22.zip>
2- then go to the directory that you installed the SDK
3- extract the zip file in to the platform-tools folder , override all files(click yes to all) be sure that Eclipse doesn't running
4- open Eclipse and select your android device that stands in devices tab at the right-top corner of your screen and then you can see the arrow near the screen- capture icon and you will find the reset-ADB. click on it ,after that your phone will ask you to allow android debugging for your device click on it
5- congratulations .now you can see that your device shown online
i hope this will help .sorry for my english
I also had a great deal of trouble when attempting to debug android applications on my shiny new LG G3. What ended up working for me was first installing the default google drivers onto the G3 and then following the process detailed by #lilbyrdie.
The process of installing the google usb drivers is very nicely gone through here.
However, with the most recently pushed android update to the G3 there are no longer the options for internet connection or charge only; but they seem to have fixed this defect forcing you to make this odd choice to enable debugging. The only options remaining are MTP and PTP, but if you pull down the notification drawer, choose the 'USB connected' notification (assuming the device is connected to your computer via USB of course) and from there click on 'Media sync (MTP)' even if it is already selected then debugging should be enabled.
Android can't update on the fly the developer mode. So, after turning on developer mode (and given you have the latest driver) switch the green button(under settings->general->developer options) to off and then back on. Then turn debug mode on (after that windows recognizes a new device) and you should be good to go.
In my solution for Windows 7 was helpful to update Android SDK Tools to latest version.
ADB Single/Composite values for LG G3 phones -
I found it was necessary to update (~userName/.android/)adb_usb.ini file with the line 0x1004:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2207
0x1004
In addition, I needed to add the following entry in (.../sdk/extras/google/usb_driver/)android_winusb.inf:
;
; Android WinUsb driver installation.
;
...
[Google.NTx86]
...
;LGE Android Phone
%SingleAdbInterface% = USB_Install, USB\VID_1004&PID_633E
%CompositeAdbInterface% = USB_Install, USB\VID_1004&PID_631D&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_1004&PID_631D&MI_01
[Google.NTamd64]
...
Oh, and set USB to PTP as well as turn-on USB debugging.
When you're all done with the file modifications and several passes at installing the drivers (ref. earlier posts), you can verify your phone is ready via the Device Manager. It will list your phone as "Android Device"->"Android Composite ADB Interface". I believe an earlier post explains setting up the drivers
Im setting eclipse on MacOS 10.8 for android development. My Nexus 7 does not show up in the Android device chooser list. I have an HTC One S and that works fine.
Here are the things i have tried.
enabled developer mode on the nexus
installed all Android SDK extras
tried switching between both MTP and PTP modes on nexus
Installed Android File transfer App on Mac.
There are several versions of this question on SO, most of the answers pertain to windows machines. Note i'm interested in a MacOS solution
I had the same problem & came across this post. For me ono's comment worked. I needed to use a usb data cable - not a usb charge only cable.
See http://answers.yahoo.com/question/index?qid=20130418072711AA6kqOP
For me that happened to be a usb I used to transfer books to my Kindle.
Once I connected the correct usb on the upper left corner the Nexus 7 printed
Connecting as a Camera
USB Debugging Connected
I already had USB debugging enabled and in an attempt to fix this problem I had selected Camera (PTP) instead of Media device (MTP) under the Android Settings - Storage - : (Eclipse) - USB computer connection
Reset ADB by going to the DDMS perspective, look at the devices View and you will see a drop down arrow with one of the options being to "Reset ADB". I'm using the same setup and I have to do this from time to time.
Also, adb seems to be more stable when neither MTP or PTP modes are checked.
Try plugging your Nexus into a USB hub attached to your Mac.
After tearing my hair out for a day, trying every single cable and set of troubleshooting steps I could find online, I found out that if I plug my Nexus 7 into a crappy little USB hub I have kicking around it works PERFECTLY. If I plug it directly into my Mac I get nothing. (Running MacOS Sierra 10.12.5 on a late 2013 Macbook Pro Retina BTW.)
I do not know if this can help you but I see my Nexus 7 tablet in Google Chrome Canary on Mac Os 10.9.1 after doing that:
Installing Chrome Canary on the Mac
- On the nexus 7 : in the settings, click 7 times on the "version" to allow developer mode (not a joke)
In the general settings of your device, the "developer options" items shows up, click on it and in the submenu allow USB debugging
Plug in the USB cable between the device and the mac
- On your device in Chrome Canary: go to "webbdevelopper tools" and allow USB debugging
On the mac, in canary your devices will appear at this adress :
chrome://inspect/#devices
You can inspect the devices with the usual debugging tools (You can open URLs and inspect them) through Chrome Canary.
If I am not clear, the whole procedure is demoed in a video in the course "Web mobile development" at Udacity.
Good luck!
I was struggling with this too. It appears that Nexus 7 devices have an issue with their data pins inside the micro USB slot getting worn out.
My resolution was to
1) blow into the port and try to clean out any dust.
2) i used a small paper clip to pry the data pins up slightly (the inside pins, the 2 outer pins are for power).
This worked for me, as now the data pins in the slot are making contact with the cable pins. Be careful though!