I am have issues using the remote debugging feature of the Chrome Developers tools with my Android device (LG Nitro running Android version 4.0.4). It was working perfectly several days ago but now my device never appears on the about:inspect page.
I have followed and carefully considered these instructions including the troubleshooting tips. I have also searched for the answer to my problem but have not been able to find anything that works.
I am using Chrome version 35.0.1916.141 on my Android device and version 35.0.1916.114 on my PC (Windows 7). Neither says any updates are available.
Please note:
I have enabled debugging on my Android device and the small bug icon appears in the menu bar at the top of the screen when the USB cable is connected.
I have installed the necessary drivers for my phone on my PC.
Chrome is open on both devices
"Discover USB devices" is checked
I have tried restarting both the computer and my phone several times
The only thing I have changed on my computer since the last time it was working was to download 64-bit Java. Could this have any effect? If anyone has any input or ideas, it would be much appreciated!
Sounds like you may have gotten lucky. Next time this happens, try this:
1) Unplug your device.
2) Revoke USB debugging in the Developer Tools.
3) In the command line:
adb kill-server
adb start-server
Plug in device and accept fingerprint.
Voila, it appears in Chrome again. I went through a lot of pain with random problems with my Galaxy S5 not showing up, I was pulling my hair out for hours trying to figure it out.
Update: After launching my Android application from Eclipse on my device, it suddenly showed up on the about:inspect page. I am not sure why it was not recognizing my phone before but it seems to be working now.
Related
I am working at an android studio project and I always work with my own physical device SAMSUNG S7. It always worked (for a few weeks now) but today suddenly from one moment to the other my device cant be recognized by android studio anymore. I didnt change any settings! I just changed a line in the code (like a hundred times before) and after it my device is not shown in the list of devices. There is only the virtual device which is useless for me because it never displays the app correctly. Just my physical device shows the app correctly so now I need help. Otherwise I cannot continue programming.
I tried to reopen android studio and restart my phone but it didnt help.
Changing the cable plug mode (credits to Hack06)
Just swipe down the OS status bar, and tap on the device, then choose another connection mode.
Installing Samsung's development drivers
When this doesn't work, try installing the drivers provided by Samsung to improve developments. These can be found here.
USB Debugging
USB debugging may have failed. Or all of the developer settings have been reset. Try that
Reboot your phone into ODIN mode
Caution:
ODIN mode is in charge for flashing your Android phone, and if you’re not careful, you can cause permanent damage to your phone.
This solution applies only to Samsung’s devices, since they are the only devices with access to ODIN mode.
A guide how to access ODIN mode for your phone can be found here.
Install KIES software
If nothing worked till here you might want to download KIES software.
KIES software only works for Samsung’s devices.
Samsung KIES is part of Samsung Smart Switch.
Download here.
Google - Android USB Driver
My last suggestion would be to install Google's Android USB drivers. An official guide can be found here.
This may sound obvious..
but sometimes it could be a cable issue
even if it's charging it could not transfer data
try a new cable
I am trying to create a React-Native app and I need to connect my device to troubleshoot some issues that only occur on the physical device and not the simulator. For some reason I have never been able to connect my Pixel 2 XL to my PC. I am running Windows 10 and I have tried all of the following.
Enabling developer mode and USB Debugging on my device.
Uplugging and replugging my device 20+ times in a row.
Changing the USB port I am using.
Changing the USB connectivity settings in Developer Options > Default USB Configuration. (Options are: File Transfer, USB tethering, MIDI, PTP, No data transfer) I've tried them all.
Restarting my device while it's plugged in
Downloading the Google USB Driver (in Android Studio).
Restarting my PC when the device is plugged in.
Updating my PC, and updating my device.
Checking Device Manager and trying to update the driver. (So the device used to show up with the yellow warning triangle next to it and trying to update the driver never worked. But now, the device doesn't even show up in Device Manager anymore)
Factory Reset my phone.
Downloaded Media Feature Pack for N and KN versions of Windows 10 (Suggested by the google tech support)(I called them)
I feel like I've tried everything previously addressed in every Stack Overflow question on this issue.
Finally solved the issue. The data cable was the problem. If you have tried all the steps above, and nothing is working, buy a new cable. This one works great and seems very durable for my Pixel 2 X: https://www.amazon.com/gp/product/B01N4OKUB8/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
I had this issue too - my Google Pixel 2 XL is about 9 months old. Was developing an app, so using USB debugging to debug the app as I built it. One day it mysteriously stopped working, though no issues with charging. I tried everything, including using all the different USB ports on my laptop, with no luck.
I eventually gave up and started using the emulator on Android Studio, and since I didn't need data transfer for anything else, I didn't send my phone for repair or anything.
A few weeks later it just started working again, all by itself...
I don't think I did anything to fix it - the moral of the story is, if you don't need it urgently, there's a chance it might just decide to work again!
I know this question has been asked numerous times, but none of the threads have had an answer to solve my problem. It seems no matter what i try Eclipse just wont detect my phone, I have set it to debug mode in the settings, i've installed "Kies 3" on my laptop and it says i have the latest drivers already installed on my phone when i try to update it.
I've installed the google USB driver package from the sdk manager and have downloaded and installed the samsung driver from the samsung website. Windows recognizes the device and in the device manager under android phone it appears as "SAMSUNG android ADB Inerface".
Im running windows 7 and have even tried deleting all the mounted dive drivers from regedit as i seen suggested in another thread but still no joy! Really starting to get frustrated with this at this stage i've been trying for two days now to figure this out!
This is such a pain! I need to be able to debug on my phone too as i'm using features that the emulator can't handle (i.e. audio recording). I'm all out of ideas here so any help would really be appreciated!
Thanks
The method I followed to install my GT-I9300 drivers was this:
Download samsung drivers from this link:
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Then just connect your phone and make sure you have a stable Internet connection: It will download required drivers automatically.
Also, make sure you have enabled Android developer options in your phone settings. Enable USB debugging in developer options.
I usually get it to work, when I switch the USB mode in my smartphone (e.g. MTP to PTP). This way, windows starts downloading more drivers.
1) Try disconnecting device from PC, revoke USB Debug authorization from settings menu, and then re-authorize the computer you are working on once you connect it again.
2) Check to see if you see the phone in DDMS perspective (left hand side) - if so, try clicking on it and it should work.
3) try removing all drivers (Google, Samsung etc.) + scan "leftover" registery entries using a reg cleaning program. Then install ONLY Kies Light version and try again.
4) It once worked for me - try changing the USB cable (preferably, to an original one)
Let us know if something worked!
1) enable USB debugging in your phone's settings.
2) ensure that you have the proper drivers installed.
3) open adb in command prompt and run "adb connect"
I have a problem debugging apps on my Samsung Galaxy S3, (GTI9300, I believe this is also known as the international version) from Eclipse.
The thing is, debugging actually worked for a time and then it just stopped working. I've tried quite a few things to make it work again. I'll describe my whole experience briefly, to keep you from suggesting things I've already tried, and save us all some time.
When I first got my phone, debugging didn't work. When I plugged in my phone, the system detected it, and I could use it almost like a storage drive (using Media Transfer Protocol or some such thing) But when I started Eclipse and tried to debug, the debugger didn't see the phone.
I googled some, learned that I had to install some specific driver. I honestly don't remember which driver it was, but I believe it was an official one (from Samsung's website). Once I installed this driver, Windows would no longer detect my phone as a storage device. But the debugger did see it, and I was able to debug a few simple apps that I'd made. I could easily live with this tradeoff.
Then I got busy with other stuff and set Android development aside. I came back to it this weekend - after 2 or 3 months - only to find that it no longer works. No matter what I do, the debugger does not detect my phone (Windows still won't detect it either).
I tried all the first aid solutions like restarting Eclipse, rebooting my computer and rebooting the phone. Just for the sake of completeness, I do have usb debugging enabled on my phone.
The only major change of the whole setup that I can think of is that my phone's OS has recently updated. I don't know the exact version it was before, right now it's Android version 4.1.2 (Kernel version 3.0.31-1160235, if this is useful to anyone). I tried plugging the phone into other computers, it gets recognized as a media/storage phone. I can't install the Android development tools and try debugging on any of these computers - I'm stuck with the one I've got.
I've tried reinstalling the usb drivers for my phone. It didn't help. In desperation (and against my better judgement) I tried installing Samsung's software, first AllShare Control, and eventually Kies. None of it helped. When I run Kies, it gives me the option of connecting through USB or via WiFi. However it won't detect my phone when I plug it in. When I click "Troubleshoot connection" (or some such thing, unfortunately Kies decided to use my native language instead of English) it starts reinstalling the USB driver. This process takes quite a while, and fixes nothing.
I'm basically out of ideas, I don't know what to try next. Any help would be appreciated.
I just upgraded my phone to 4.2.2, but now i cannot use it in eclipse anymore.
I tried rebooting the device, reset my debug-settings but I cannot get it to work anymore.
I saw it is already a registered issue. There are some new security enhancements, so there should be a dialog (see here at bottom) but this dialog doesn't appear. I don't have several accounts on the phone, which is pointed out in the issue..
Anyone any suggestions?
EDIT: Look at accepted answer below, this should cover all cases. In my case, there were some packages missing, which weren't shown in the Android SDK Manager. I just found the Packages -> Reload in the Android SDK Manager... And I thought this happens automatically
You need three things in order to make sure this update goes smoothly:
Make sure your device is actually running 4.2.2 and the problem is not something else
Your SDK is updated to the latest tools. The adb binary in all but the latest version does not support the 4.2.2 security enhancements.
You are on the main account of your device in case of multiple user accounts.
Connect your Device to your computer and execute adb devices (make sure USB debugging is enabled). You should see something like this:
3tiu52839ry082j3 offline
Right about now, there should be a dialog on your device that looks something like:
Check the Always allow from this computer box if you want and click OK.
That's about it.
Some other things to check:
Make sure your USB cable isn't broken. Sometimes, the smaller cables break inside the main one, and your device may charge but have no data connection. Try with a different cable, or try accessing files on the device over USB (this will go fine if your cable is fine)
Make sure you're using the newest version of adb. Even after I updated my SDK tools, I couldn't get my device authorized when using adb. I eventually figured out that the Nvidia install of the NDK and SDK tools had updated my PATH variable to use the adb from that install, which wasn't the latest update. By using the adb in my newly updated install, I was able to get it all working.
For me it was solved by changing Nexus 7 tablet to "Camera(PTP)" mode.
Check out this blog post on how to do it.
After USB connection of Nexus 7 and confirming digest on Nexus 7, also connecting through TCP/IP with ADB worked.
Wierdly, unchecking and rechecking the "Allow USB Debugging" option popped me the window and selecting "ok" solved my problem.
If none of the solutions worked for you then Reset ADB.
Go to Devices ---Click the right most down arrow----Select Reset ADB from the list.
I had tried everything suggested here and suggested in every log/blog that I could find in google, but still no go. The USB cable is known to be good. ADB is version 1.0.31 (as shown with , USB Debugging is enabled in the Nexus 7 tablet, the SDK was updated to the very latest tools as available on 1-mar-2013 for 4.2.2/API 17. I had tried both Media and Camera modes for USB, rebooted windows, rebooted device over and over again, re-installed latest google USB driver, etc. etc. but ADB Devices still showed nothing.
I hard reset the Nexus 7 tablet thinking that maybe the screen to allow usb debugging had appeared but got hit with cancel. But that didn't work either.
What finally worked was:
going into windows control panel | Device Manager,
selecting NEXUS under Portable devices,
then in the Driver tab clicking on update and manually selecting the Google USB driver (the check feature said it was up to date). Previously, the date shown was in 2006, afterwards a date in 2012 (but more on this in a moment).
That didn't fix anything though.
So then I switched USB from MEDIA device to Camera device - THEN it wanted to install driver software, so I let it do that. Afterwards, I noticed that the driver for the Nexus was back with the 2006 version, BUT then ADB DEVICES FINALLY SHOWED OFFLINE!!!! HALLELUJAH AND the Nexus was displaying the Dialog to allow USB debugging, and it now all works.
What I am not sure of is what step actually solved the problem. I don't think it was necessary to hard reset the Tablet, but the fiddling with the device driver wasn't a very convincing solution either - I don't think the driver was corrupt - but maybe it had to be changed to get the right driver associated with the tablet when connected as a Camera Device. In any event, it is necessary to connect the tablet as a Camera device for ADB to work...
Restarting device or enabling USB debugging did not solve my problem.
However I changed USB PC Connection to "Camera(PTP)" mode and adb devices showed the device id of the phone.
After reading a lot post talking about this particular problem, I actually solved it by resetting user permissions on files (that were owned by root): ${HOME}/.android/adbkey and ${HOME}/.android/adbkey.pub
Go to Device Manager and uninstall your device and remove from USB
HAve you CMD opend and make sure you are at least in ADB Help.
Connect device to USB and continue with steps provided by Raghav Sood - few answers ahead of me.
Worked for me just fine
I tried with this custom build and it works for me. Now I can see my logcat in Eclipse again.
https://github.com/khaledev/ADT/releases
Download the zip file then in Eclipse menu Help > Install New Software... > Add > Archive... Just pick the downloaded zip and do the rest of the install process.