I am using the OS as Windows 7. In which I want to run my Android app through the Eclipse.
so I connect my android device to my laptop through USB connector. In my device shown as " USB connected ", but when I click the run configuration to select the device, the device id never shown/displayed. and I was tried in the CMD prompt mode, by Killing and start ADB server, but it never worked. Could you anyone provide the solution.
First make sure that USB debugging is enabled. To do that go to your phone and find "Developer Options", for me it is Settings->System->Developer Options. If the device doesn't show up in Eclipse after that, make sure the ADB is running, and that it can recognize your device.
If a device doesn't appear in the list when you use a command like "adb list", probably there is some issue with device drivers.
But if you think device drivers are installed .. just try restarting the device..
Enable USB debugging in your phone settings: Apps -> Development -> USB Debugging.
Related
I have a basic Hello World Cordova application working on an Android emulator (Nexus 4) on my Mac. I wanted to try deploying to a Samsung Galaxy S3 that I have (model SCH-R530M) but when I try running adb devices and empty list is returned.
I have already tried unplugging the device, killing adb using adb kill-server, running adb using adb start-server, and then plugging the device back in and it is still not being recognized.
The only other problem I can find is that my USB cable might be a "charge only" cable, but I don't know how I would go about determining if it is.
Does anyone have a potential fix for this issue?
Is it in developer mode?
Does it allow USB debugging?
https://developer.android.com/tools/device.html
These are the instructions for your device:
https://muffinresearch.co.uk/samsung-galaxy-s3-where-are-the-developer-options/
Go to Settings → More → About Device
Scroll down to Build Number
Tap it repeatedly (It'll show a message telling you how many more times you need to tap it to enable developer mode).
See the Developer options menu under Settings → More
Then make sure 'usb debugging' is selected in the developer options.
I would try a different USB cables too. I had to try a couple before it would register the device.
Kies can also sometimes kickstart it.
http://www.samsung.com/uk/support/usefulsoftware/KIES/
How to run a program on your phone sony zr ،Personal computer with the Eclipse runtime , but knows it 's shown as offline while the phone is placed in debug mode
This is maybe because you did not verified your PC on your phone.
First, unplug you device, open Developer Options, make sure "Android debugging" is turned on. Then select "Revoke USB debugging authorizations" and confirm.
Now plug your device in again, make sure its display is turned on. Now you should get a message that you must authorize your PC to get access on your phone.
That should work now.
You can also enable Wireless Android Debugging. Then you open a terminal/command line in your "sdk/platform-tools" and type "adb connect YOUR_IP" (or ./adb connect YOUR_IP under linux). Replace YOUR_IP with your phones IP which you can find on your phone settings under "About Phone" -> "Status".
In addition to that all: Why do you still work with eclipse? Switch to android studio, that's the new standard!
Good luck and happy coding!
So I started getting errors in my ADB logs which, I think, are causing my device to now display any logcat output for my app. I am getting all the logcat output except the one from the app itself.
PropertyFetcher: AdbCommandRejectedException getting properties for device 04799057970ed1fc: device offline
PropertyFetcher: AdbCommandRejectedException getting properties for device 03799467970ed5fg: device unauthorized. Please check the confirmation dialog on your device.
you have missed the Fingerprint Certificate Authorization dialog in your phone when you connected it, try to change the USB mode to Media, or another different than the one you have in and then reconnect your device, or go to Developer Options -> Revoke USB Debugging and reconnect, watch for the dialog and click on accept, that should solve your problems.
If that doesn't work, set your ANDROID_SDK_HOME again, and then:
Unplug device
Run:
adb kill-server
adb start-server
Plug in device
I experienced the same issue.
To ensure that your Android Device is expecting the correct fingerprint from the system (e.g. after switching Android SDK installations -> different adb server running!), do the following (actually, this did the magic for me):
unplug your Android Device
revoke USB debugging authorizations in Android Developer Options
plug your Device. You can accept the fingerprint once more.
1) Go to Phone Setting > Developer options > Revoke USB debugging.
2) Turn off USB debugging and Restart Again.
It will work definitely, in my case it worked.
Please check this.
https://code.google.com/p/android/issues/detail?id=82850
I faced the same issue. Could notice that the "adb integration" was disabled. Please enable it at your IDE (Tools | Android)
This happened to me because I enabled usb debug previously on another pc. So to mke it work on a second pc I had to disable usb debugging and re-enable it while connected to the second pc and it worked.
The solution to this was just to change the USB cable, having enabled
ADB Integration via
Tools >
Android >
Enable ADB Integration.
Below are the commands for Ubuntu user to authorise devices once developer option is ON.
sudo ~/Android/Sdk/platform-tools/adb kill-server
sudo ~/Android/Sdk/platform-tools/adb start-server
On Device:
Developer option activated
USB debugging checked
Connect your device now and you must only accept request, on your phone.
In my case, it was literally a bad USB cable. Apparently it was right on the edge - adb logcat would work, but about half the time I would get this error when trying to push an app to the device.
Changed to a different cable, and everything was fine. The old cable was also very slow at charging, so I should have suspected it sooner...
Remove the Debug permissions on the Device, with the cell phone connected, then put them back, and ask if you want to allow the PC to have debug, accept and ready permissions: D
I had the same problem when debugging over wlan. I could launch the application from Android Studio but couldn't get any messages in logcat.
I fixed it by connecting the device to my pc via USB cable, launched the application once and everything was working. Then I disconnected the USB cable and tried debugging again via wlan and everything was working again.
I've got the same message too.
In my case, I have changed my dev environment to another notebook pc and my device is samsung galaxy note 2014 edition.
My OS is windows 7
My galaxy note condition listed as following
developer option activated
USB debugging checked
The error message was "device unauthorized. Please check the..."
In general, the location of the default android setting was C:/Users/Your_login_name/.android then I copied and pasted all files in the '.android' folder to my new pc's setting folder.
After that the problem was gone.
I think the problem was adbkey file mismatched.
Also, I didn't have any menu name such as revoke adb authorization.
Seems strange the intricate cable&restart solution steps ... The first time I've plugged the Android device to my Ubuntu (15.10) I've got Connect as: multimedia or camera options and in my Android Studio the device status was unauthorized. It wasn't until I choose between one of the options that I got in the Android device the PC authorization option. When you give the proper permissions in Android then the device status changed to online in Android Studio. Cheers
This might help -
Just Download and install the Android SDK version(same as your mobile's android version), then run.
In my case the problem was about permissions. I use Ubuntu 19.04
When running Android Studio in root user it would prompt my phone about permission requirements. But with normal user it won't do this.
So the problem was about adb not having enough permission.
I made my user owner of Android folder on home directory.
sudo chown -R orkhan ~/Android
Download platform-tools-latest-linux.zip.
Run:
unzip platfo*.zip
cd plat*
./adb devices / ./adb usb / etc
I get this error very often for some reason when doing "ionic cordova run android" and running on an emulator. What works for me is to end the "adb.exe" process and re-run. Sometimes that also doesn't work and what I do is exit the emulator and in android studio do a "Cold Boot" on the emulator.
in Linux i had to delete the content of .android folder which holds the adbkey and ofcourse enable USB Debugging.
I had the same issue despite:
developer options enabled
USB debugging enabled
Solved by simply unplugging and then replugging the USB.
Eclipse is not able to detect my android device even though it is connected to my computer. I had it working on my computer earlier, but my hard drive crashed so I had to reinstall/setup eclipse, and now it doesn't work. I have enabled USB debugging. I updated my USB drivers/ android devices. I tried connecting my android phone first, and then tried my tablet, but there was no change. I tried restarting the ADB server. The android project runs on the emulator, but the emulator takes so long to load and is laggy. I did a lot of research on how to fix this, but nothing is working. In my eclipse console it says, "Failed to find an AVD compatible with target 'Android 4.4W'."
if you have root, you can try to use Wireless adb via wi-fi. for this you must install from GooglePlay app like "wireless adb" run it and connect from cmd like this:
"e:\androidSDK\sdk\platform-tools\adb.exe connect 192.168.0.68:5555"
Also i recommend you to install free third-party android emulator BlueStacks, it work very fast! faster then real device connected by usb
For virtual device try Genymotion
For hardware
-first check if your device is connected - adb devices //some serial number should list. If empty, you need to install proper drivers manually.
also check in windows Device manager
Try to disable USB debugging then enabled USB debugging.
Relay! Yeah it's work.
I want to run my Android project on a device.
My device is not detected in Eclipse when I connect it with a USB cable.
I restarted Eclipse and I have checked that USB debugging is on, on the device.
Can anybody tell me what the problem is and how to resolve it?
Before starting, Make sure that USB DEBUGGING IS ENABLED in your phone settings !!!
1) BASIC STEP - Plug in device via USB, then go to device page in Android developers blog. There you can find necessary information regarding adding USB vendor ids. Add your device specific ids, and restart eclipse if needed.
2)If you were able to see the device connected(using command: 'adb devices'
) earlier, but not anymore, then just try restarting ADB. (you can use the commands: 'adb kill-server' followed by 'adb start-server'. adb commands need to be executed from platform tools folder in the Android SDK, if you havent exported it).
3)If neither of them works out and you are on windows machine,
then check the installed usb drivers are correct. If not install proper drivers
Please find more information on how to install/update drivers in http://developer.android.com/tools/extras/oem-usb.html
If this also is not working, try installing Universal ADB windows driver https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
4)You may also try increasing the timeout time
Go to preferences-> android->DDMS in eclipse, then try increasing 'ADB connection timeout(ms)' value
Update based on newer answers:
5)Run > Run Configurations > Target. Please make sure, the option "Always prompt to pick device" is enabled.
Special case: Windows 8 and Nexus 10 (from this question: ADB No Devices Found)
Windows 8 wouldn't recognize my Nexus 10 device. Fixed by Setting the
transfer mode to Camera (PTP) through the settings dialogue on the
device.
Settings > Storage > Menu > USB Computer connection to "Camera (PTP)"
I solve this problem by updating PC portable device drivers:
Go to : Settings -> Applications -> Development to enable USB debugging
Plug in device USB
Desktop "My Computer" right click -> "Manager"
Choose "Device Manager"
Portable Device
right click on your device -> "Update Driver software" -> Search automatically (wait about 3-5min, )
Done
Restarting the adb server, Eclipse, and device did the trick for me.
C:\Android\android-sdk\platform-tools>adb kill-server
C:\Android\android-sdk\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
I had the same problem as mentioned on this question.
I had similar problem, drivers was okey, but Eclipse did show me the device in Run > Run Configurations > Target tab. But I checked the option "Always prompt to pick device". And then running the application from Eclipse the prompt window finally showed my device.
After a long and frustrating search, finally I made my Micromax Funbook p362 to connect with eclipse and made it to suit for development.
*Installed Moborobo (All in one Android smart phone management tool).
*Perform stop -server / start -server using ADB.
*Reboot the device.
*Restart the eclipse.
*Device got detected.(Eclipse - list of adb devices)
In addition to the steps provided by #asfsafgsf (above), make sure to re-enable your phone's developer modes/functions. For my Motorola Atrix:
settings>applications>Unknown Sources: allow 3rd party apps
settings>applications>Development: to enable USB debugging, mock locations, and disable phone sleep
A note on developer modes
USB Debugging is the main mode you will need for running apps through eclipse when your phone is connected via usb (obviously). Disable phone sleep is also handy for self-explanatory reasons.
Allowing 3rd party app sources allows you to beta test your app on a larger-scale. With this, you can host your own apk and instruct your beta-testers to download it (prior to releasing it to the Google Play storefront). More specifically, 3rd party support allows the installation of android package files that don't contain a google approved signature (required for play store hosting). With 3rd party apps enabled, a handset will be able to run packages regardless of their source. You should also be able to receive an APK via bluetooth and install it in this mode.
You can also list all currently connected devices by running the following command:
adb devices
Go to http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver and follow the steps on the android website but on browsing for the USB folder don't use the directory specified -> ((sdk)\extras\google\usb_driver). (sdk) just means your sdk location.
Your phone should have the correct driver and it can be accessed when you plug it in and go to the CD Driver in My Computer, in my case it's G:\drivers\adb_driver. Use this directory instead and it should work. (It may be differ with devices).
One possible reason is to check Android SDK Manager and install Google USB Driver in Extras folder if you have not installed it.
Following the steps here: http://developer.android.com/sdk/oem-usb.html#InstallingDriver allowed Eclipse to display the device.
Do following steps to detect your device in eclipse : -
On Mobile Side:- For Connect USB sync, your Android device needs to have USB Debugging enabled.
To enable Android USB Debugging Mode do following steps :-
Android 2.x - 3.x devices:
Go to Settings > Application > Development > USB Debugging.
Android 4.x devices:
Go to Settings > Developer Options > USB Debugging.
For devices running Android 4.2.2 or later, you may need to unlock Developer Options before it is available within the Menu:
Go to Android home screen.
Pull down the notification bar.
Tap "Settings"
Tap "About Device"
Tap on the "Build Number" button about 7 times.
Developer Mode should now be unlocked and available in Settings >
More > Developer Options or in Settings > Developer Options
On PC side
Connect your device to the PC with USB cable.
Download Google USB Driver
Extract/Unzip “latest_usb_driver_windows.zip” file on your computer
(using 7-zip free software, preferably)
Open device manager on your PC
Windows 7 & 8 users → search for
Device Manager from Start (or Start screen) and click to open.
Windows XP users → Google it
You will see list of all devices attached to your computer in the
device manager. Just find your device (it’ll most probably
be in the Other devices list with a yellow exclamation mark by the
name of ADB devices), then Right-click on it and select Update
Driver Software.
Select “Browse my computer for driver software” in the next window
Now click the “Browse…” button and select the “usb_driver” folder
that we extracted in Step 3 from “latest_usb_driver_windows.zip”
file.
Do NOT select the zip file, select the folder where the
contents of the zip file are extracted. And keep the Include
subfolders box checked
During the installation (as a security check) Windows may ask your
permission to install the drivers, click “Install”
Once the installation is complete you’ll see a refreshed list of
devices on the Device manager screen showing your phone’s driver
installed successfully.
Now in eclipse do following steps to install your app in your device:-
Go to Run > Run Configurations > Target tab.
Check option "Always prompt to pick device". And then running the
application from Eclipse,the prompt window finally showed
your device.
Please check whether your device is shown in the Eclipse device tab in Window > Open Perspective. If its not shown there then you need to install drivers for the the device. Once the device is visible in the Devices tab then change the launch settings for manual target. Once you launch your app then it will allow you to choose from the real device or the virtual devices
If you have the following problem
Then you can so following to fix it
Note : You should enable USB debugging on your android device(It will be in developer option in System settings)
I had this problem. With my galaxy S2. So came here for advice, but couldn't find anything specific. Then I found this 'Kies' software on the Samsung site, under the section for my exact model of phone, under downloads, after clicking software.
It installed the right USB drivers as part of the process of installing Kies and so my phone instantly then became visible on eclipse.
The Kies version for Galaxy S2 (GT I1900) = http://www.samsung.com/uk/support/model/GT-I9100LKAXEU-downloads#
There are other versions of Kies for other android models of course.
(new) device not showing, Check List:
Developer Option ON
USB debugging ON
Try changing to USB Storage/MTP/PTP
if it installs Window driver and fails, there's your problem (verify in Windows Device Manager) fix it.
ok this is an old thread -
but I spent nearly two days and did not get anywhere
Here is what solved my problem
I had USB debugging enabled ( finding developer options itself was a pain - I think the 7 times tap from google is childish and just plain stupid - rant over )
However HTC syn manager , eclipse ADT and windows computer management were all unable to identify my device
My problem was my phone was set to ONLY USB Charge - this was the problem
In 'USB Computer connection' >> Choose the option USB Storage
Once you do this - PC will install drivers and your device will get detected by Eclipse as well as in 'Computer Management' under ''Android USB devices '
Now I still dont know a way to access ''USB Computer connection' but at that time I did get the option to change and t worked
For those ( like me earlier ) who dont know how to identify if 'Computer Management' shows their device look for 'Android USB devices '
If its present - then your device is being detected by your PC
Hope this helps some others
shankar
On a kitkat Google Nexus 7, I tired everything here, and did not succeed. The device did previously connect properly to this computer.
Then I hit settings - developer-options - Revoke USB debugging authorisations
and confirmed that I really did want to revoke them.
I unplugged and plugged the USB. The tablet beeped and asked if wanted to authorise the computer for debugging. I said "Yes" and everything worked again.
For me the problem is with Defective USB Cable. I have tried those above all answers. Nothing gives me any fix. But finally i came to know the problem is because of my usb cable while changing the usb cable. While connecting through the usb cable the phone is charging but the drivers are not installed. Some usb cable don't have the option for that. So while buying check it and buy.
Best approach is install PDA net(software) on both system as well as in android device. This software automatically installs global driver for all phones, provides easy connectivity to android device.
Follow these links to download
For system
http://pdanet.co/
For android device
https://play.google.com/store/apps/details?id=com.pdanet&hl=en
Here is my checklist in windows (not the device itself) when my device is not shown:
Make sure "USB debugging is turned in setting>Developer options.
Check status bar on your device. It tells you if your phone is connected as Media Device (MTP) or Send images (PTP). My device is only listed when PTP is selected.
Turn of windows firewall.
Turn of any proxy programs ran on whole windows ports.
And finally stop adb.exe from windows task manager and wait some seconds to restart automatically.