hi i am a new app developer, when i was trying to run my app the following occured...
[2011-02-24 09:33:35 - FirstImage] Android Launch!
[2011-02-24 09:33:35 - FirstImage] The connection to adb is down, and a severe error has occured.
[2011-02-24 09:33:35 - FirstImage] You must restart adb and Eclipse.
[2011-02-24 09:33:35 - FirstImage] Please ensure that adb is correctly located at 'C:\android-sdk-windows\tools\adb.exe' and can be executed.
The adb is located in "C:\android-sdk-windows\tools\"
i tried "adb start-server" in run command but no use, is there any way to solve the issue.
Try killing the Android Debug Bridge (adb) by just running the command adb kill-server and then adb start-server on your command prompt.
Also ensure that if you have updated your SDK then path of adb may be android-sdk-windows\platform-tools in your new sdk. So just try copying that file in the android-sdk-windows\tools directory.
Related
I'm trying to install an apk file in the Linux terminal on my Chromebook, so I followed instructions from this website. So I installed the ADB and ran adb connect 100.115.92.2:5555, and after that I tried installing my apk by running adb install opinionrewards.apk but it returned this error:
error: more than one device/emulator
adb: error: failed to get feature set: more than one device/emulator
- waiting for device -
error: more than one device/emulator
Can someone please explain why this error occurred and how to fix it?
Okay, all I had to do was adb kill-server and then start it again, and just install it again.
Use this command:
adb -s emulator-5554 install filename.apk
I am using Android Studio 2.2.3. Everything is up to date.
Running "adb shell" on Terminal in Android Studio generates the following:
adb server is out of date. killing...
* daemon started successfully *
error: device not found
To reconnect the device, I have to run "adb kill-server" first.
This makes running shell commands impossible.
Could anyone offer a tip on how to fix this?
From Android Studio Terminal run
$ $ANDROID_HOME/platform-tools/adb shell
this ensures you will be using the same adb.
When I want to run an android project in Eclipse, it cannot choose a running AVD as below picture.Anyone knows what's wrong with it.Thanks a lot
[
This happens when adb starts before the emulator. so write in the command prompt
adb kill-server
adb start-server
and Then
adb device
or simply restart eclipse
I just changed my PC, and now I have a problem with Android Studio, every time i try to run or compile an app it install it correctly, but then it cannot start the main activity of the app, if you need it this is the full Android studio output:
Waiting for device.
Target device: samsung-gt_i9000-3733E37B1ACB00EC
Uploading file
local path: C:\Users\Federico\swagmasta\TurnarioConapo1.0\app\build\outputs\apk\app-debug.apk
remote path: /data/local/tmp/feddycapdev.conapo.turnario
Installing feddycapdev.conapo.turnario
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/feddycapdev.conapo.turnario"
pkg: /data/local/tmp/feddycapdev.conapo.turnario
Launching application: feddycapdev.conapo.turnario/feddycapdev.conapo.turnario.MainActivity.
DEVICE SHELL COMMAND: am start -D -n "feddycapdev.conapo.turnario/feddycapdev.conapo.turnario.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Error: Adb refused a command
I tried to manually run am start -D -n "feddycapdev.conapo.turnario/feddycapdev.conapo.turnario.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER from the adb shell, and it work correctly, some ideas on how could i fix it?
UPDATE : I tried running as admin, rebooting PC, reconnecting cable, killing all the adb.exe processes, killing the adb server and restarting it, noone of this worked.
Maybe it's a problem of driver? I'm using a Samsung Galaxy S for debugging, at the beginning the PC didn't recognized it, so I installed samsung USB driver, so maybe that's the real problem, but if i can install app to my device via adb the driver should be working right?
Please kill and start adb server from console or terminal using following commands:
adb kill-server
adb start-server
If it does not help try to restart your computer.
If you are getting
adb command not found
error then you have to go in platform-tools directory in Android SDK.
hope it helps!
It could be blocked by some other instance of adb.
Look into your task manager if you are not running another instance of adb.
I am getting this exception when i trying to run my application
[2013-09-10 12:09:21 - EffectiveNavigation] The connection to adb is down, and a severe error has occured.
[2013-09-10 12:09:21 - EffectiveNavigation] You must restart adb and Eclipse.
[2013-09-10 12:09:21 - EffectiveNavigation] Please ensure that adb is correctly located at 'E:\Configured-Eclipse\adt-bundle-windows-x86-20130522\sdk\platform-tools\adb.exe' and can be executed.
When i tried to reset adb from eclipse it is showing this error
[2013-09-10 12:18:20 - adb] Attempting to restart adb, but version check failed!
I have tried this also from the command prompt.
1.adb kill-server //kill all active server
2.adb start-server //start adb server
Restarted the eclipse also but still the same error .Help me to resolve the issue.
Finally this was the issue
turned off COMODO Defense+ module and all worked....
If you install some application manage your phone, kill the application.
First of all, make sure you can run adb.exe itself without any errors. run it in "Administrator Mode" in cmd.exe and also, "adb.exe devices" should output list of connected and recognized USB devices.
Check update for eclipse adt first.
============== For most adb-down situations this may work. ========
Exit eclipse and kill the process adb.exe from Task Manager.
run adb kill-server and adb start-server. then retry.
If an error occurred when 'adb start-server'
Use netstat -abn to finger out if there is a process which is listening on port 5037 (default adb port), and kill it. Then run 'adb start-server' or just 'adb devices'