Can't see my device of chrome://inspect/#devices - android

I've followed the instructions at google: https://developer.chrome.com/devtools/docs/remote-debugging. I've also went over the troubleshooting section - but nothing seems to work.
I have samsung galaxy 3 (android 4.1.2, chrome 42.0.2311.111). USB debugging enabled. I've tried restarting the device after ticking the USB debugging a few times.
On windows 8 I run chrome (44.0.2388.0 canary). I've installed Samsung USB Driver, and my computer can see my device.
I do not get any notification when plugging the device nor when opening canary with the inspect page.
Did I miss anything?

Try these steps:
Download and install Android SDK
Open SDK Manager.exe
Select Android SDK Platform-tools and press Install packages...
Open a command prompt and execute these commands:
cd C:\Program Files(x86)\Android\android-sdk\platform-tools (or C:\Users\User\AppData\Local\Android\Sdk\platform-tools)
adb.exe devices
You should receive a response like this:
List of devices attached
ABCDEFG123 device
If your device is listed check if Chrome detect the device, otherwise try to execute this command:
adb.exe kill-server
adb.exe start-server
adb.exe devices
Check again if Chrome detect the device.
If your device is not listed at all after executing adb devices command there is something wrong in your configuration (e.g. incorrect or missing drivers?)

Hope this helps somebody else...
This happened to me because I was trying to Chrome inspect a release build (Ionic; i.e. ionic build android --release). If I build a debug app (ionic build android), I am able to see the app from the chrome inspection tool without any issues.
Google play does not like debugable apps https://developer.android.com/studio/publish/index.html
which is needed for the inspection - see this SO link: debugging an ionic app for android platform hence proper releases won't appear in the Chrome inspection.

In my case the problem was solved changing the usb connection mode in the settings of the Android device to "Camera (PTP)" . For some reason the usb debbuging did not work when connection mode was set to MTP.

This looks like a bug in Chrome or in Android. This helped me: on your android device select USB connection settings (popup which is open on cable connect). It has MTP/PTP/charge modes. Switch between MTP/PTP and back.

Download and install Android SDK
Open SDK Manager.exe
Select Android SDK Platform-tools and press Install packages...
MTP -> PTP

Related

ADB and Xcode not detect connected devices, after update to Catalina mac os

I have updated my mac mini os to Catalina. After that Android Studio and Xcode not detect connected devices. "adb devices" command not showing any devices.
But, in Android Studio, it detects my device (on troubleshoot mode). But, it was saying, not recognized as Android device. Usb debugging is already enabled. Need help on this Catalina issue.
So far I tried:
Xcode command line tools installed.
Xcode updated.
Android Studio updated.
Android SDK updated.
Tried connecting with different cables.
I think the problem is from the OS, when I see the console log. I see an error
adb#(null): AppleUSBHostUserClient::start: missing entitlement com.apple.appledfr.client
waiting for a patch from apple
For adb it started working again, after i tried to set up the sdk path again ,
export ANDROID_HOME=~/Library/Android/sdk
I did the "Revoke USB debugging authorizations" from the Developer options on the phone and run Xcode so it would install some updates.
Once I did that, it offered up the usual "did you want to allow debugging on this device" option, and everything was back to normal.
After Mac OSX is upgraded, then open Xcode to install the components. Then connect your android phone through USB rather than double type-c. After that, do the "Revoke USB debugging authorizations" from the Developer options on the phone. Then adb devices list will show the connected phone.
Using zsh, I added
ANDROID_HOME=~/Library/Android/sdk
to my .zprofile file (if you don't have one, just create it with touch .zprofile in your home directory) and rebooted.
1) go to and install www.android.com/filetransfer
2) then revoke the USB debugging authorizations on android device
3) make sure you are running the old bash (in Catalina), to do this: chsh -s /bin/bash
4) unplug Android device from USB cable
5) restart Mac Catalina
6) plug back in Android device
7) run terminal (bash)
8) adb devices
it should show up, note: I had tried to run the Android File Transfer app after installing it, but it never would run. With that said, it seems to try and run something when it detects the cable being plugged in. Disclaimer: I don't know if this will work for you, but these are the steps I ran through to get it to work for me

WARNING : No target specified, deploying to emulator

I'm trying to run an ionic app on my mobile phone (Android 4.4.2).
USB-Debugging is activated.
When i run the command "ionic emulate android" everything works fine and the app is opend in the emulator.
But when I run the commad "ionic run android" I get following warning:
WARNING : No target specified, deploying to emulator
and the app is started on the virtual device...
Shouldn't the app run on my mobile phone? What am I doing wrong?
How can I specify the target?
P.S.: When I copy the .apk file to the phone I can run the app.
I had another developer tool opened (Chrome Inspect) and it "ate" the connection. In my case, just closing the Chrome Inspect panel and running ionic run android worked.
I solved the problem.
Here is what I did:
I typed into the command line: adb devices (located in the "platform-tools" folder in the Android SDK) which returned me an empty list.
So I installed my phone's drivers, which I downloaded from the vendors homepage.
Now the list contains my device and the app is started on my mobile phone.
I had a different problem, with a very simple solution.
When plugging in your Android device for the first time, it'll ask you to trust the computer's certificate. That popup screen disappeared on me, as I was just getting a call.
Simply unplugging/replugging your phone and accepting your computer's certificate should do the trick!
Once you've enabled your device for debugging, make sure to turn on usb tethering on the device;
Settings > Tethering & Networks > USB tethering
This fixed the problem for me.
In my case I had Android 5.1.1, and below are the steps I took:
Please check that your PC recognizes your phone (you can access the files like in a USB flash drive). If not please install the drivers from google here.
Please check that the USB debugging options is checked on your phone, then:
1- Go to Setting -> General -> '{} Developer options'
2- Look for the 'USB debugging' option
3- If the 'USB debugging' option is disabled then turn off 'Developer options' and turn it back on. Now you should be able to check the 'USB debugging' option.
None of these worked for me on android 6.0 on a mac.
I found this article: http://trendblog.net/android-file-transfer-not-working/
quoting from it:
Enable Developer Mode by going to Settings > About Phone (at the very bottom usually) > press on Build Number repeatedly until the pop-up appears
Go to Settings > Developer Options
Enable USB debugging
I'm on a Mac.
What worked for me was to heed the warning on the device that said no program on the Mac was available that could connect to the device, such as Android File Transfer.
I installed that. Unplugged and replugged the USB cable. And voila.
I had two problems (Ubuntu OS):
I had a connection open with chrome//inspect - close that (simply close the tab)
I missed the dialog that appears when you connect your device through USB cable. You must trust the computer.
Now run the command cordova run android and look at your device there another dialog will be appeared click ok, now you are done! In the terminal you will see LAUNCH SUCCESS. By the way I removed the old app from my device too.
No target specified and no devices found, deploying to emulator
When this message appears, you have to click START, and activate your emulator before.
If your app is already installed in your device and your device debuging is already enabled.
Then uninstall the previous app and install the fresh apk
sudo ionic cordova run android
Once you are remove the USB plugin from the computer means it will not work. Already open the Chrome inspect in your PC means close that tab and run.
In my case, just closing the Chrome Inspect panel and running ionic cordova run android worked.
Thats all. Enjoy your coding
I got the solution by removing the Android emulator and re-create the emulator from AVD Manager of Android Studio.

Chrome remote debug Samsung Galaxy s4

I tried to use the remote debugging tool of Google Chrome for my Samsung Galaxy S4 (https://developers.google.com/chrome-developer-tools/docs/remote-debugging?hl=nl). But my Chrome does not found my device after i used about:inspect. The list stays empty.
I already install the newest driver on my computer and both devices running Chrome version 32. On my phone the USB debugging checkbox is checked.
Does someone know what i can do to view my phone trough Chrome debugging?
Do you have ADT (Android Development Toolkit) installed? If so, you may have to restart the ADB server. Follow these steps: (from this answer).
Open a command prompt (Win+R, "cmd.exe", Enter)
Go to the platform-tools directory of your locally installed ADT. In my case:
cd /d D:\apps\adt-bundle-windows-x86_64-20131030\sdk\platform-tools
Restart the ADT server by running the following commands:
adb.exe kill-server
adb.exe start-server
Now observe that your tablet will ask for remote debugging permission (by checking a fingerprint) upon connection.
The device should now be found if you open chrome://inspect.
workaround if you don't have ADT (Android Development Toolkit) installed:
Managed to detect android based Samsung Galaxy phone after downloading andorid SDK platform-tools.zip and running the following command: "adb devices".
It started some deamon, found attached device, and I was also able to see it in chrome canary inspect tab.
previously I also installed "Universal ADB driver" but not sure if this was required
I stumbled over this exact problem. The solution above work's like a charm for me.
But I'm lazy as hell, so I created a .bat file:
#ECHO OFF
cmd.exe /K "cd C:\Users\YOUR_USERNAME\AppData\Local\Android\sdk\platform-tools && C: & adb.exe kill-server & adb.exe start-server"
The directory depends on your installation of your ADT.
Save as killstart_adb.bat and run this.
Works for me.

Eclipse won't recognize my device

I searched trough many questions and couldn't find an answer that fix my problem.
I'm new on creating Android projects and I'm still getting familiarized with the eclipse platform.
To the point, when I run my project I get this error
No compatible targets were found. Do you wish to add new Android Virtual Device?
I changed the AndroidManifest.xml from targetSdkVersion="18" to "15" (Which is my device level, Android version 4.0.4, correct me if I'm wrong)
Then I clicked on Run Configuration and switched from "Launch on all compatible devices/AVD's" to "Always prompt to pick device", and still couldn't get the project to work.
When I reverted the Run Configuration I get this output everytime I try to run the project
[2013-12-15 21:27:28 - MyFirstApp] No active compatible AVD's or devices found. Relaunch this configuration after connecting a device or starting an AVD.
What's the meaning of both messages? How can I make it work?
Some details:
Android Version: 4.0.4
OS: Windows XP
Samsung Galaxy S DUOS
Please follow the steps
Step 1
Check if the device driver is installed successfully. If not, download the drivers and plug the device again.
Try this link to download the driver software - http://samsung-kies.en.softonic.com/
Step 2
Click Start-> Run-> CMD. (Go to command prompt)
Navigate to the android SDK platform tools path.
Type adb devices
Now you should get the device listed and a tag "device" next to the device ID
Step 3
If you get "no devices found", type adb kill-server
Type adb start-server
Now type adb devices.
Now you are good to start testing your applications on device.
You have to have Samsung Kies installed on your computer so you can have drivers for your device, also, from eclipse:
window -> show view -> devices
if you don't see your device here, this means either your ADB is not running, or your device is not recognized by your computer
also verify you have debug mode enabled in your device
Do you have the usb debug driver for you device installed? This is the driver that allows your device to "comunicate"with eclipse in order to debug

How to connect the device to Eclipse?

I am not able to resolve this simple issue.
I am trying to connect my device to Eclipse via USB cable.
On my PC, I have installed Eclipse and the Android SDK and running the program on the emulator is working fine.
I have downloaded and installed Samsung Kies on my PC. It shows my device if connected via USB to the PC.
But I dont know how to connect the device with the emulator.
Connect means, I want to run the Eclipse code on my device instead of emulator. I am using Samsung Galaxy Ace GT-S5830i. Please help me out to resolve this issue.
Comment is lack of formatting so i add an answer.
Check if your computer had your phone driver. I assume that your use Windows. Open Device Manager
At a command prompt, in the Start Search box, or in the Run box, type the following command: mmc devmgmt.msc
. Other ways : check link
If you find your phone name or ADB Interface so you got driver. Try to restart DDMS or restart your Eclipse.
If you don't find your device or see something Other device with yellow question mark so try to install driver by browsing on your phone to Settings - Developer Options - Enable developer option - Enable USB debugging - Plug your phone to computer. Windows will ask you to install driver.
3, Update Google USB driver in Android SDK Manager (in Eclipse) or search Samsung Galaxy Ace GT-S5830i driver
4.Some weird case i got on some device.
Nexus S: disable Developer option. Restart phone. Enable again. Windows ask to install driver or you will see it in Eclipse.
HTC phone or Samsung : change Connectivity Option on phone to Charge only (Swipe status bar. Check notifications displayed). Some phone set it to some kind of Sync data so Windows can not recognize device.
I think your emulator is in Automatic. You can change that to Manual.
Try this,
Step 1
Go to Run Configuration
You can see three Columns Android,Target and Common.
Step2
Select the Target
Step 3
Choose Always prompt to pick device.Click Ok
Step 4
Now run your project you should see the emulator and your device. Select your device and click ok.
Hope it helps.
Source.
Troubleshooting
This all sounds very straightforward, but there are countless quirks and hard-to-diagnose problems that can make connecting a device much more difficult than it sounds. In this section, we'll run through a checklist of things to try when your device isn't registering.
Check that USB Debugging is enabled. This setting can inadvertently (and perhaps even automatically) change when you plug/unplug your device from your machine, or when you reboot your phone.
Check your device while it's connected to your machine. Is it asking you to choose between different modes? Some phones have a 'charge only' mode that can prevent Eclipse from recognizing the device.
Choose a connection type
Make sure you don't have an Android Virtual Device running in the background.
Could there be a problem with the USB cable? If you have a spare cable to hand, plug it in to rule out a fault with the cable itself.
Double-check you're running the correct driver. Even if you are, some devices have all the required software pre-installed (for example, HTC Sync) and downloading drivers from another location can muddy the waters. If this might be the case with your device, try uninstalling the driver from your machine and reinstalling the software from your device's memory.
Does the driver require supporting software? Samsung Kies on Windows requires .Net Framework 3.5 SP1 or above, for example. This is usually installed along with the driver, but there's no guarantee.
Running the Android Debug Monitor tool (monitor.bat) has been known to kickstart Eclipse into recognizing a new device. Connect your device, locate monitor.bat (android-sdks/tools/monitor.bat) and double-click to open. This will open the Android Debug Monitor, a stand-alone debugging tool that lists connected devices.
Android Debug Monitor
A running adb.exe process can interfere with the connection. Close Eclipse, and open the Task Manager by pressing CTRL, Shift and Esc. Find the adb.exe process and kill it. Launch Eclipse and try again.
Check that your 'Project Build Target' is compatible with the Android version on your device. You can check what version of Android your device is running by opening 'Settings' and selecting 'About Phone,' followed by the 'Software information' option if available. If you need a reminder of your project's build target, ensure the project is selected in Eclipse's 'Package Explorer,' open the 'Project' menu and select 'Properties.' If the 'Android' tab isn't selected by default, open it and the Build Target will be displayed.
Have you enabled USB debugging in your device?? You can find it in your device
Settings -> Developer Options -> USB Debugging.
The android app you have created will be a .apk file, generated by eclipse, during a successful Run. Find the .apk file from the eclipse project explorer or by tracing your workspace. Copy the .apk file to your memory card (via USB or a card reader) and install it.
You should also enable the "Unknown Sources" option under "Security" of your Android device.
If you have required options enabled on your phone (USB Debugging and Unknown Sources) you can try do this. On your computer open command console. Using cd navigate to your android sdk installation folder. Go to platform-tools. You should have there adb file. Run this
./adb kill-server
and then
./adb start-server
Then check plugged devices
./adb devices
First, you are not connecting device with emulator. What you want is eclipse to identify your device and use it for development.
Everything about using devices for android development is given in official documentation.
You have to put the phone in 'debug' mode - I don't have the instructions handy (but you can search here or on the android site for the info you need).
Also check for THIS.
Try right clicking the project -->Run As --> Run Configurations then select target and choose always prompt
On your device turn on debug mode
Now try running project
I am assuming you don't mean connecting the device with the emulator but connecting the device to your computer so you can debug it and run applications directly from Eclipse to the device. In which case KIES by Samsung will not help you at all. What you need is the Android USB Drivers provided in the Extras tab in SDK. Sometimes the installation will bug up because you didn't run SDK manager as an administrator so make sure you do that. When all of this is done make sure your device is unconnected to your computer and then reconnect it after the drivers are installed. You should be prompted with a new device installation wizard which you must accept. Additionally, you should have debugging enabled on your device, and as an extra step you can setup launching as a manual configuration but it is not needed.
To enable device debugging
Settings -> Developer Options -> USB Debugging.
For more information visit here
BTW : If the Google USB Drivers don't work you might need to install the specific Samsung drivers which are located here
Goto -> Setting -> Application -> Development -> USB Debugging
Enable it and try.
I know this is a little old, but I was having the same issue. I tried all the options of setting usb debugging (off), disconnecting, restarting phone, usb debugging (on), connecting the phone and it just wouldn't connect.
I ended up installing the latest version of Kies on my machine and added the Unified option at the end of the installer and I then the phone would connect. (Not sure i needed the unified option) but it worked for me.
I tried all the above but it didn't helped me. I did couple of things additionally
Since my mobile device is Android, I unchecked Unified option from Kies installer. This is the crucial thing that helped me solve my problem
I restarted my mobile phone.

Categories

Resources