when looking into phonegap testing previously (I've looked into it and then got sidetracked for a year and now looking again) using my HTC Desire, I simply connected my device, clicked run as android in eclipse and then it would automatically run the app through my device.
But when trying on my new phone (SGS3),i get
[2012-11-27 07:48:18 - name] Android Launch!
[2012-11-27 07:48:18 - name] adb is running normally.
[2012-11-27 07:48:18 - name] Performing com.thing.name.name activity launch
[2012-11-27 07:48:18 - name] No active compatible AVD's or devices found. Relaunch this configuration after connecting a device or starting an AVD.
I have installed all drivers I can think of, even installed Kies and AllShare in case they came with any additional drivers but still the same thing.
Has anyone else come across this or know how to fix?
regards
Search for Developer Options and enable USB Debugging and also make sure Unknown Sources is activated unless you already did.
Android 4.2
To make the developer options appaear in Android 4.2 you have to go to menu "About Telephone" and hammer on the build number a couple of times, till a toast tells you you are developer now.
In addition to #dan's answer, you need to make sure the device is in USB MTP mode. (not Camera USB mode.)
Related
I created a game in unity that I want to download on my phone. I plug in my Samsung galaxy s7 edge and click on build and run.
It starts building as usual, but then the error shows:
I don't know why this is happening. I have enabled USB debugging on my phone and did all the requirements-(click build number seven times, enable USB debugging)
I also disabled and re-enabled the USB debugging but it didn't work. I even downloaded the SDK and JDK!
Few solutions to this problem.
Someone already mentioned try plug/unplug. Sometimes you have to change option from charging to transfer files or other.
Another solution that will probably work is killing adb server. Launch your OS console and type:
adb kill-server
then restart it by
adb start-server
This will force pc-phone communication to be restarted, and probably will solve your problem. Make sure the Android SDK path is correct in your Unity settings too.
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
I'm trying to do some app development for Android with Eclipse and my Nexus 5.
However, after the first time loading MyFirstApp from Eclipse, I can't seem to get the authorization right.
When I run adb devices from the command prompt, I end up getting
0350b965215d9854 unauthorized
or
0350b965215d9854 offline
and even after restarting everything, I only sporadically get the authorization popup on my phone. Even if I select 'always allow from this computer' checkbox (pic below), my computer remains unauthorized. I have never had it remember authorizing my computer as the checkbox would suggest.
A few times, after killing the server and restarting the server multiple times, adb will recognize the device, as after typing "adb devices", I get
0350b965215d9854 device
But if I try running the app in eclipse I'll get the following error message.
[2013-11-09 18:10:16 - MyFirstApp] Failed to install MyFirstApp.apk on device '0350b965215d9854': timeout
[2013-11-09 18:10:16 - MyFirstApp] Launch canceled!
I'm also unable to run shell or other commands from adb.
I've verified I'm using the latest usb drivers, android sdk, and eclipse release and have tried the following fixes:
On Nexus 5:
Booting in Safe mode
Toggling/untoggling USB Debugging
Revoking USB debugging authorization and reauthorizing
Restarting the phone
Allowing permissions on a one-time basis
On Windows 8:
Restarting the computer
Restarting Eclipse
Killing/starting adb from cmd
Killing adb from task manager
Reinstalling Eclipse
Reinstalling google's USB drivers
Installing the nexus 5 line in google's drivers as per this
question
Reinstalling the Android SDK
Changing USB Ports
I've seen very similar posts for the Nexus 4 and Nexus 7, but after trying everything contained in those solutions, I'm still not getting anywhere.
Here's my solution
1. I re-download the latest ADT bundle
2. uninstall the old driver in "My Computer" -> "Device Manager" (delete the old driver also)
3. Right click on "Nexus 5" and update the driver using the one under "[New ADT Path]/sdk/extra/google/usb_driver"
4. Turn on debug mode (click on KRT16M multi-times)
5. Deploy my first app . And a popup on device appears. Click "Yes" to accept the key.
Good luck!
Have you tried updating both the SDK and ADT ? Support for Kitkat is provided in the latests ADT
For me a tutorial provided by AndroidGeeks helped me fix the connection issues to my Windows (7) PC.
"Make sure to enable the USB Debugging for your Google Nexus 5 from the Developer Options first.
Open Settings, then About Phone.
Tap the Build Number seven times to unlock Developer Options.
Now you can continue to the tutorial.
How to install Google Nexus 5 USB / ADB / Fasboot / Bootloader drivers:
Download the Nexus 5 Drivers from here.
Extract the zip contents and place all files in a single folder on your desktop.
Connect your device to your computer.
Launch the Device Manager on your PC.
Now you should see the Nexus 5 listed in the hardware list.
Right-click the ‘Nexus 5′ line and then click on Update Driver Software.
Next, click the ‘browse my computer’ option.
In the new window click on ‘Browse…’ button.
Go to folder unzipped at step 2. Select the folder where you extract the USB Drivers. Click Next. - make sure to tick the subfolder box too.
Now, the Windows installer will search for Nexus 5 drivers, click Install when asked for permission.
Wait for the process to complete and then check the Device Manager list to confirm that the installation was successful.
Also, you should launch the device in Bootloader Mode to check and see if the device is connected by your computer. If not, then you should stay in Bootloader Mode menu and then repeat the entire tutorial listed above. Eventually, the Google Nexus 5 will be recognized by your PC."
Link: http://www.android.gs/download-and-install-google-nexus-5-usb-drivers-adb-fastboot/
After implementing Nevin Chen's steps above without success, I ended up upgrading my system to Windows 8.1 for unrelated reasons. Out of curiosity I tried usb debugging again, and it worked the first time without problems. It has continued to work since.
I can only suspect that the problem was a system setting that was installed with an incorrect driver that only a system restore or upgrade would end up rewriting. Trying to uninstall the drivers from the device manager seemed not to help the problem.
I would be curious to know if anybody else has solved this problem with a system restore or upgrade.
On Windows 7, I tried the instructions in the following link: https://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
I didn't get anywhere after several attempts with restarts of both the computer & device, and I tried multiple USB ports. I also switched from Nova Launcher to the stock launcher with no signs of improvement.
In the end, I changed usb cables and it worked!
The first cable was from a Samsung Galaxy S4 and had a noise reduction choke that was not present on the stock Nexus 5 usb cable.
I am using a brand new window 8 laptop:
Following steps works for me:
1. Download the latest ADT bundle
2.connect my nexus 5 to pc (it recognize the device after installing the default usb driver)
3 From Device Manager Right click on "Nexus 5" and update the driver using the one under "[New ADT Path]/sdk/extra/google/usb_driver"
4.Turn on debug mode (click on KRT16M multi-times)
works like a charm!
enter link description hereif you are using windows 7 and earlier, Adb installer works well. you just have to install the app and when u plug in your smartphone, it will recognize the build and get you what you need.
works well
I am successfully using Eclipse with emulators. Now I want to use my Defy for device debugging, since the emulator is a bit slow.
My Defy has Cyanogenmod 7. My app is for 2.1 Android, so it should work. I followed all description and have device debugging set in my app manifest as well as the device settings.
If I type "adb devices", it now shows up one device. First I had problems with the driver with Win7 64Bit. After manual installation of the driver it worked.
I am wondering how to select the real device in Eclipse. In debug, I have my emulators. The real device does not show up in the list of my emulators. It is not an emulator so it makes sense. But how can a Start debugging on it. Or shall I copy the apk on the device and somehow attach Eclipse to the running process for debugging?
Best Regards,
Patrick
I do not get my Defy debugging in Eclipse. Some days ago it had worked. I just restarted my laptop and found the below error. adb is installed under the requested path. If I type adb devices in cmd in that path I get a device: efefeSOME_NUMBERrggr offline, Do not know if the offine is a problem
I also tries the wifi adb apps. If i connect with this tools I also get a device 192.168...:5555 device. This looks good.
After trying again eclipse debug, it directly starts the debugger. I have switched on enable debug, my phone is rootet. Can anyone give me a hint, what I may also consider? It had worked one day and now it does not.
[2012-04-12 22:10:01 - MyApp] ------------------------------ [2012-04-12 22:10:01 - MyApp] Android Launch! [2012-04-12 22:10:01 - MyApp] The connection to adb is down, and a severe error has occured. [2012-04-12 22:10:01 - MyApp] You must restart adb and Eclipse. [2012-04-12 22:10:01 - MyApp] Please ensure that adb is correctly located at 'C:\Entwicklung\android-sdk\platform-tools\adb.exe' and can be executed.
I have been learning Android by developing under Windows 7, Eclipse and the emulator. I wanted to start using my old LG Adroid instead of the emulator, but a soon as I plugged it in and did all the stuff to get it working with ADB, Eclipse blew up with : Please ensure that adb is correctly located at 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe' and can be executed.
If I unplug the phone, Eclipse will start up the emulator and work just fine. I found that if I first do a "adb shell" and then exit the shell, Eclipse is happy and works.
I need to do this on every reboot of Windows.
You have to download the USB Driver from Motorola here USB DRIVER
then USB debugging like "Waqas" says and i also use Unknow Sources. I Develop with a Motorola Defy 2.1 and it works fine :-D
...sorry i read you question to fast. Maybe try this go in Eclipse to Run->Run Configurations and set the Target to Manual. Then you should be able to chouse your device
You need to enable USB Debugging mode in your device's setting to allow eclipse (ADT) to use it for development.
Settings -> Applications -> Development -> USB debugging (should be
enables)
I am developing an android app using Eclipse. All has been going well until I tried to deploy it to my device last night. When I clicked Run, I was presented with the following:
[2012-04-26 09:00:52 - Unicyclist] Android Launch!
[2012-04-26 09:00:52 - Unicyclist] adb is running normally.
[2012-04-26 09:00:52 - Unicyclist] Performing com.unicycle.UnicyclistActivity activity launch
[2012-04-26 09:00:52 - Unicyclist] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2012-04-26 09:01:05 - Unicyclist] Uploading Unicyclist.apk onto device 'SH0AZR805746'
[2012-04-26 09:01:05 - Unicyclist] Failed to install Unicyclist.apk on device 'SH0AZR805746': No such file or directory
[2012-04-26 09:01:05 - Unicyclist] com.android.ddmlib.SyncException: No such file or directory
[2012-04-26 09:01:05 - Unicyclist] Launch canceled!
It sounds like the directory it is attempting to install to on the phone is missing. Or perhaps it's a directory on my computer? I can't find anything on this by searching, and I'm not sure how to debug this.
This is a phone, not a virtual device.
The phone is running cyanogenmod, not stock.
A bunch of apps updated last night (related?) I re-imaged the phone from a backup, and the app deployed correctly. Then I updated the apps that had changed since last backup, and left it overnight. This morning, it won't deploy again (same problem)
The app launches fine on
another tablet, and fine in a virtual device
My dev environment is in a dropbox folder, if that makes any difference. I switch between developing on a windows and 2 linux computers.
Same problem occurs on both linux computers with this phone (haven't tried windows yet)
The problem is that Eclipse is not capable of finding your apk file. Just try build clean. Here is another similar question.