I bought a new Alcatel Onetouch 918n phone for app testing. I can't however get it to be recognized in eclipse to test.
After some painful steps, I now see "Alcatel Android ADB interface" in Device manager. But I just can't seem to make this phone visible to Eclipse/ddms/adb.
Since i somehow (I Think after installing Alcatel Android mgr on PC) got the OEM Usb driver installed, I think I don't need the google usb driver, correct?
And Yes usb debugging on phone is on.
Please help?
Take a look at http://blog.fh-kaernten.at/wehr/?p=1182, where the author describes his problem with his device being in Device Manager but not showing up in ADB. Also look at Adb Devices can't find my phone. Some other things to try:
See what you get when you run ADB outside of Eclipse ("adb devices" from a command line). Sometimes Eclipse is finicky, so it may be better to troubleshoot this outside of it. Sometimes it's necessary to quit and restart Eclipse when it's not seeing your device, or unplug and re-plug your device.
When you make any changes, use "adb kill-server" and "adb start-server" to stop and restart the adb server, before again trying to see your device.
If possible, try a different device and see if it shows up in adb (though you'll probably have to install a driver for it first). That may tell you whether the problem is with your Alcatel phone or the software on your computer (missing SDK component, wrong USB driver, etc.)
Related
Hello stackoverflow mighty community,
Please help !
I have a Datalogic DL-AXIST (http://www.datalogic.com/eng/products/automatic-data-capture/mobile-computers/dl-axist-pd-702.html) which is an android device but i guess the company fiddled a bit with its core. Also I have a windows 7 toshiba pc.
Anyway my concern is that it is not showing on the adb devices chooser.
Here is what i've tried so far:
I'm using Eclipse IDE, my SDK is up to date and i can test my application on all the other devices i tried so far.
The datalogic device has Android 4.1.1, driver is correctly installed on my pc i'm sure, enabled developer options.
I tried connecting it as MTP and PTP but will not work, there is also a CD-ROM installer connection which i tried as well, followed through the installation on my pc but still does not work.
It gets even stranger, when i used the third pc connection type and installed the device with its own adb on pc, i even copied those adb files in that folder and pasted them my eclipse's own adb. This worked ! my device was recognized but it changed for a reason i do not know.
I tried uninstalling the device driver and re-installing it from windows device manager, tried rebooting device and restarting eclipse and pc.
I really need some help because making this device work will greatly benefit my work.
Thanks !
This is genuine issue which may come frequently,but the soln is simple you may try these steps:
step 1;
try swictching developer options on and off
if the above dont works then go to device manager in your pc check portables devices select device and update driver software-->browse my comp-->let me pick list of device drivers-->select android as in option or MTP
if your device dont show in portable devices just update the device which comes in portable devices list trust me it works all time
try to do this once
1. Check if authorized:
\platform-tools>adb devices List of devices attached 4df798d76f98cf6d unauthorized
2. Revoke USB Debugging on phone
If the device is shown as unauthorized, go to the developer options on the phone and click "Revoke USB debugging authorization" (tested with JellyBean & Samsung GalaxyIII).
Restart ADB Server:
Then restarted adb server
adb kill-server adb start-server
4. Reconnect the device
The device will ask if you are agree to connect the computer id. You need to confirm it.
Now Check the device
It is now authorized!
adb devices \platform-tools>adb devices List of devices attached 4df798d76f98cf6d device
I can't seem to make eclipse recognize my Xperia E1 as an ADB device.
The problem is that in the devices list of eclipse it is detected but it says 427ac413 as serial number and the target is unknown. USB Debugging mode is on, I have tried both MSC and MTP modes, I rebooted the device, the ADB Driver is installed from PC Companion (although it says Sony so0107 and not so0101 as I have seen on some other forums). I'm thinking it could either be a driver problem, maybe the wrong one is installed, because the first time I installed it the adb driver said it was from Samsung, and I had to uninstall it and reinstall it.
Any suggestions on how to make it work?
Here are some steps that may work.
Turn off the USB Debugging mode
Connect your phone with both MSC and MTP modes (check that it is accessible in each mode, this means that at least these 2 drivers are fine)
Disconnect phone
Make sure ADT USB Drivers are up to date.
Check that adb is running, better by task manager (If you try at the same time eclipse and cmd adb they mess themselves, red errors about adb start appearing in eclipse console at this case.)
Turn on the USB Debugging mode on the phone, connect it in MSC.
Connect the phone, it should ask for USB debugging access.
In case everything fails.
Try another USB
Try another USB cable, some idiot phones work better by the "authentic" cable Sony with Sony, Samsung with Samsung etc.
Restart phone
Restart computer
On / Off USB Debugging mode with either the phone connected or not.
Try manually driver installation by pointing the folder of PC Companion or ADB drivers
Restart eclipse
If still resists, lets make sure that android connects:
(Close eclipse) Open cmd run adb command
Connect phone on debug mode adb devices check that is online. If yes, its a matter of chance that eclipse recognize it. If no, you may have issues either with adb or with drivers (?).
In case you have issues with adb. Some Companies install an adb in the Phone Suites in order to update phones or access phone data. This adb sets itself in installation at the PATH and starts instead of the Android ADB which is for development. In this case you can run in cmd adb kill-server navigate to android adb location and adb.exe start-server.
In case of the drivers search the net for Xperia E1 android debug drivers and start testing if anything works.
It seems that this issue can be fixed by manually updating the ADB driver through Windows Device Manager. There is a support thread on the Sony Experia Forum that discusses, and provides detailed steps for a solution, this issue:
http://talk.sonymobile.com/t5/Xperia-E-E-dual/ADB-driver-XPERIA-E/td-p/290337
I have solved my problem by following these steps.
The problem was that the SDK_HOME folder wasn't set properly and the PC wasn't authorised. So i disabled developer tools and enabled them again, revoked USB Debugging authorisations and then plugged it back in. The dialog appeared on my phone and then it all worked.
First, you may used the wrong driver, try to get it from here, here, or here.
Then, force the windows to reinstall the driver again:
Choose the device from [device manager].
update driver ----> browse my computer for driver software ----> let me pick from a list... ----> Have Disk.
Browse and choose the proper driver, the press OK.
Last, restart your adb:
from cmd go to /platform-tools directory then write adb kill-server then adb start-server.
I've been developing an Android app using Eclipse and the Android plug-in for Eclipse and all these days, I would just plug in my phone into the computer and hit Run and would see my app run on my Samsung Galaxy Phone. But now it shows me a window like the following and am unable to choose my phone as the device because under the "State" column it says "Offline" even when the phone is plugged into my computer. I can't even use the emulator because its painfully slow on my computer.
Refer this link
Android device chooser - My device seems offline
Restart adb by issuing 'adb kill-server' followed by 'adb
start-server' at a cmd prompt
Disable and re-enable USB debugging on the phone
Rebooting the phone if it still doesn't work.
Sometimes Android devices appear "offline" (according to adb devices). I've generally had success fixing this by rebooting the device, though it won't hurt to also adb kill-server followed by adb start-server.
I've seen this happen with multiple unrelated devices, infrequently, and seemingly randomly (that is, seemingly unrelated to anything I had been doing).
Reformatting the phone solved this problem for me. I don't know if that solved the problem but once I reformatted the phone, I was able to run the app on the phone.
I have tried downloading the Samsung specific drivers. It installs the modem, not sure if the adb bridge got installed. I don't see it in the device manager. I have installed kies 2.0, I have tried connecting USB via MASS storage, via Kies, and under no circumstances so far will ADB detect the device when running adb devices command. I got lots of suggestions to use Kies, I tried this. Don't see any real relationship between Kies and ADB which is a debug bridge. I simply have no clue what ADB is doing when I type adb devices. How does it look for devices, where does it check, where can i register my device with ADB?
Apparently sometimes you need to uninstall and reinstall the driver multiple times before it works (http://androidforums.com/captivate-all-things-root/136373-adb-shell-error-device-not-found.html). Also, make sure that USB debugging is turned in your application settings.
make sure you are using the correct drivers (32 bit or 64 bit). when you connect your phone in debug mode check device manager. I would bet you have an error in there. Try and delete the error and rescan for changes.
I am running Android SDK 2.2 and am trying to get the adb to connect to the Google Nexus One phone. Its a new phone, shipped straight from Google - haven't installed any apps on it yet.
(I have Windows XP)
Here is what I have done so far:
Followed the instructions on setting up the device for development as given on the Android Developer's site:
http://developer.android.com/guide/developing/device.html
added android:debuggable="true" to my application manifest
USB debuggable is checked on the phone
downloaded the Device Drivers For Windows Revision 3 (this supports Nexus One phones)
Went through the Hardware Installation wizard to install the device - the device shows up as "Android Composite ADB Interface".
When I run adb devices on the shell, the device appears for a moment, then disappears.
On the Eclipse console, I get the following message:
[2010-11-13 11:54:42 - DeviceMonitor]Failed to start monitoring
I have rebooted the pc several times, uninstalled and reinstalled the drivers several times, but I get the same error each time. As I was researching this problem, someone had recommended rebooting the phone. I am a bit confused by that - is that a soft or hard reboot? Do I just power the phone off/on and is there something more complex involved? Do I have to hard reboot it to reset to factory version - even though its brand new?
Has anyone run into a similar problem? Any help on this would be great.
I can't test my application on the device if the adb cannot view the device. Thanks so much in advance.
I had this same problem. To get it working, do the following:
Close Eclipse
Open Task Manager and kill the adb.exe program.
Re-open Eclipse (Eclipse will automatically restart the adb.exe service)
Run adb devices from a command prompt and you should see something like the following:
C:\> adb devices
List of devices attached
0123456789ABCDEF device
Of course, I'm assuming you have your phone plugged into your computer.
It sounds like something is killing the service as soon as it starts. Try disabling any anti-virus and running adb devices again. You can also check your system logs for errors - run compmgmt.msc and check the Event Viewer's logs.
When I run adb devices on the shell, the device appears for a moment, then disappears
Do you mean Windows' command shell cmd.exe? The output of 'adb devices' doesn't update itself, it should just print out what's currently connected then terminate.
Nothing here worked for me. And you know what? I plugged it to my USB 3.0 port.
Just plug it to regular USB 2.0 and it'll work.
Hi you jst need upgrade your usb driver, follow this ref link, after upgrading you need to uncheck USB debugging, disconnect cable from device and then check USB debugging and connect cable to device again. this'll solve your problem..
link text
I had this same problem. Do the following:
Plug your phone into your computer and:
Run the command prompt.
Go to the tools location of the android sdk.
run 'adb kill-server'
then run 'adb start-server'.
Turn off COMODO Firewall and Defense+ module
I got my Nexus One on Windows 7 64 bit going by following these instructions:
http://developer.android.com/sdk/win-usb.html
Note that the directory has changed to /extras/google/usb_driver.
You know that you need to do this if you go to control panel->devices and printers and show properties on the device, and there's no driver shown.
Open the task manager by Ctrl+Shift+Esc
In the Processes select adb.exe and Click the End process Button.
Now close the eclipse and restart it again.
This worked for me. Hope this would work for you as well.