when i tried to debug my android application with eclipse, the emulator started and shows this message: "Application openconnection is waiting for the debugger to attach",and i got this messages in my console:
[2012-04-26 12:12:24 - openconection] ------------------------------
[2012-04-26 12:12:24 - openconection] Android Launch!
[2012-04-26 12:12:24 - openconection] adb is running normally.
[2012-04-26 12:12:24 - openconection] Performing org.anddev.android.getdatafromtheweb.GetDataFromTheWeb activity launch
[2012-04-26 12:12:24 - openconection] Automatic Target Mode: Preferred AVD 'emul' is not available. Launching new emulator.
[2012-04-26 12:12:24 - openconection] Launching a new emulator with Virtual Device 'emul'
[2012-04-26 12:12:33 - Emulator] emulator: WARNING: Unable to create sensors port: Unknown error
[2012-04-26 12:12:33 - openconection] New emulator found: emulator-5554
[2012-04-26 12:12:33 - openconection] Waiting for HOME ('android.process.acore') to be launched...
[2012-04-26 12:13:08 - openconection] HOME is up on device 'emulator-5554'
[2012-04-26 12:13:08 - openconection] Uploading openconection.apk onto device 'emulator-5554'
[2012-04-26 12:13:09 - openconection] Installing openconection.apk...
[2012-04-26 12:13:29 - openconection] Success!
[2012-04-26 12:13:29 - openconection] Starting activity org.anddev.android.getdatafromtheweb.GetDataFromTheWeb on device emulator-5554
[2012-04-26 12:13:30 - openconection] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=org.anddev.android.getdatafromtheweb/.GetDataFromTheWeb }
[2012-04-26 12:13:31 - openconection] Attempting to connect debugger to 'org.anddev.android.getdatafromtheweb' on port 8656
[2012-04-26 12:13:51 - openconection] Launch error: Failed to connect to remote VM. Connection timed out.
Is it a problem with port ?
I added this code to my manifest file
<uses-permission android:name="android.permission.SET_DEBUG_APP"></uses-permission>
Edit: i have a default emulator called 'emul' i didn't know why it can be started (by the log )
Automatic Target Mode: Preferred AVD 'emul' is not available. Launching new emulator.
Close your other applications those maybe use your debug port.
If you use eclipse and other SDK, you maybe need to close others.
Good Luck.
Related
This may not be a programming question. But any help will be appreciated.
When I launch my android application in emulator, I used to get some kind of log message on console. Like below:
[2014-09-01 18:56:44 - POSStore] ------------------------------
[2014-09-01 18:56:44 - POSStore] Android Launch!
[2014-09-01 18:56:44 - POSStore] adb is running normally.
[2014-09-01 18:56:44 - POSStore] Performing com.POS.Store.LoginActivity activity launch
[2014-09-01 18:56:45 - POSStore] Automatic Target Mode: Preferred AVD 'SamsungGalaxyS' is not available. Launching new emulator.
[2014-09-01 18:56:45 - POSStore] Launching a new emulator with Virtual Device 'SamsungGalaxyS'
[2014-09-01 18:56:54 - POSStore] New emulator found: emulator-5554
[2014-09-01 18:56:54 - POSStore] Waiting for HOME ('android.process.acore') to be launched...
[2014-09-01 18:57:28 - POSStore] HOME is up on device 'emulator-5554'
[2014-09-01 18:57:28 - POSStore] Uploading POSStore.apk onto device 'emulator-5554'
[2014-09-01 18:57:28 - POSStore] Installing POSStore.apk...
[2014-09-01 18:57:43 - POSStore] Success!
[2014-09-01 18:57:43 - POSStore] Starting activity com.POS.Store.LoginActivity on device emulator-5554
[2014-09-01 18:57:44 - POSStore] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.POS.Store/.LoginActivity }
[2014-09-01 18:57:45 - POSStore] Attempting to connect debugger to 'com.POS.Store' on port 8626
But suddenly console stopped showing logs. But application is launched successfully and running.
Why does console stopped showing application logs? I've updated my android version. Does this afects?
Go to Display Selected Console drop down on top right side of your console window. And select Android.
I'm unable to start my AVD. I've uninstalled and installed it 2nd time. Still the same. I have kept the AVD for approx half an hour, Still no luck.
Below is the Console log i get when try to run the Application in AVD.
[2014-02-12 20:43:02 - HelloAndroid] ------------------------------
[2014-02-12 20:43:02 - HelloAndroid] Android Launch!
[2014-02-12 20:43:02 - HelloAndroid] adb is running normally.
[2014-02-12 20:43:02 - HelloAndroid] Performing com.example.helloandroid.MainActivity activity launch
[2014-02-12 20:43:02 - HelloAndroid] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2014-02-12 20:43:05 - HelloAndroid] Launch canceled!
[2014-02-12 20:44:38 - HelloAndroid] ------------------------------
[2014-02-12 20:44:38 - HelloAndroid] Android Launch!
[2014-02-12 20:44:38 - HelloAndroid] adb is running normally.
[2014-02-12 20:44:38 - HelloAndroid] Performing com.example.helloandroid.MainActivity activity launch
[2014-02-12 20:44:38 - HelloAndroid] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2014-02-12 20:44:49 - HelloAndroid] Launching a new emulator with Virtual Device 'AVD_for_Nexus_4_by_Google'
[2014-02-12 20:45:23 - Emulator] bind: Permission denied
[2014-02-12 20:45:23 - HelloAndroid] New emulator found: emulator-5558
[2014-02-12 20:45:23 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
And attached is the logcat when starting the AVD from AVD Manager.
http://sdrv.ms/1bWRKru
I think there is a problem in mounting the data partition or its not available.
In a real device, if you have not flashed the data partition properly, with fastboot, the same issue will occur.
I have an emulator open, but when I launch my application it starts a 2nd emulator rather than running on the one that is already open.
Console Output:
[2013-02-24 14:30:40 - AdatBpro] Android Launch!
[2013-02-24 14:30:40 - AdatBpro] adb is running normally.
[2013-02-24 14:30:40 - AdatBpro] Performing hu.AB.example.adatbpro.MainActivity activity launch
[2013-02-24 14:30:40 - AdatBpro] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2013-02-24 14:30:47 - AdatBpro] Launch canceled!
[2013-02-24 14:31:04 - AdatBpro] emulator-5554 disconnected! Cancelling 'hu.AB.example.adatbpro.MainActivity activity launch'!
[2013-02-24 14:42:15 - AdatBpro] ------------------------------
[2013-02-24 14:42:15 - AdatBpro] Android Launch!
[2013-02-24 14:42:15 - AdatBpro] adb is running normally.
[2013-02-24 14:42:15 - AdatBpro] Performing hu.AB.example.adatbpro.MainActivity activity launch
[2013-02-24 14:42:16 - AdatBpro] Automatic Target Mode: launching new emulator with compatible AVD 'AVD412'
[2013-02-24 14:42:16 - AdatBpro] Launching a new emulator with Virtual Device 'AVD412'
[2013-02-24 14:42:16 - Emulator] WARNING: Data partition already in use. Changes will not persist!
[2013-02-24 14:42:16 - Emulator] WARNING: SD Card image already in use: C:\Users\Edit\.android\avd\AVD412.avd/sdcard.img
[2013-02-24 14:42:16 - Emulator] WARNING: Cache partition already in use. Changes will not persist!
[2013-02-24 14:42:16 - AdatBpro] New emulator found: emulator-5556
[2013-02-24 14:42:16 - AdatBpro] Waiting for HOME ('android.process.acore') to be launched...
[2013-02-24 14:43:32 - AdatBpro] HOME is up on device 'emulator-5556'
[2013-02-24 14:43:32 - AdatBpro] Uploading AdatBpro.apk onto device 'emulator-5556'
[2013-02-24 14:43:33 - AdatBpro] Installing AdatBpro.apk...
[2013-02-24 14:44:30 - AdatBpro] Success!
The program is runing and database open but when the first emulator wrote nothing. I try again run. The first emulator is there open and open the second emulator and wrote everything on the second emulator.
Its only made on emulator.
it does not run on a telephone.
Tested the kill-server and start-servert.
Did not solve the problem.
I run anything this happens
Why make this? What I made wrong?
I can not find the solution.
Open a console window (terminal window, command prompt, etc) and run:
adb kill-server
adb start-server
That will fix your dueling emulator problem. It happens to a lot of us ;) Note: adb can be found in the platform-tools folder under your SDKs folder.
I am attempting to launch my application but this is what I get. I am using Eclipse with ADD.I am trying to run this project but it seems it cant get uploaded on the virtual device
any suggestions on how I could resolve this ?
[2012-10-05 04:44:10 - Android_Test] ------------------------------
[2012-10-05 04:44:10 - Android_Test] Android Launch!
[2012-10-05 04:44:10 - Android_Test] adb is running normally.
[2012-10-05 04:44:10 - Android_Test] Performing com.example.android_test.MainActivity activity launch
[2012-10-05 04:44:10 - Android_Test] Automatic Target Mode: launching new emulator with compatible AVD 'TestDevice'
[2012-10-05 04:44:10 - Android_Test] Launching a new emulator with Virtual Device 'TestDevice'
[2012-10-05 04:44:12 - Android_Test] New emulator found: emulator-5554
[2012-10-05 04:44:12 - Android_Test] Waiting for HOME ('android.process.acore') to be launched...
[2012-10-05 04:45:04 - Android_Test] HOME is up on device 'emulator-5554'
[2012-10-05 04:45:04 - Android_Test] Uploading Android_Test.apk onto device 'emulator-5554'
[2012-10-05 04:45:09 - Android_Test] Failed to install Android_Test.apk on device 'emulator-5554': timeout
[2012-10-05 04:45:09 - Android_Test] Launch canceled!
Go to > Window menu >Preferences > Android > DDMS > increase value of ADB connection Time out
if this not works then try..
Reset ADB from DDMS > Devices > Reset ADB (down arrow from right corner)
if this fails then you have to restart your AVD
whenever I run an android application there comes the emulator but it does not show the output.
At runtime this warning is showed.
[2012-02-18 10:31:15 - Emulator] Warning: No DNS servers found
the console part shows the following messages
2012-02-18 11:26:52 - LunchList ------------------------------
2012-02-18 11:26:52 - LunchList Android Launch!
2012-02-18 11:26:52 - LunchList adb is running normally.
2012-02-18 11:26:53 - LunchList Performing apt.tutorial.LunchList activity launch
2012-02-18 11:26:53 - LunchList Automatic Target Mode: launching new emulator with compatible AVD 'secondAVD'
2012-02-18 11:26:53 - LunchList Launching a new emulator with Virtual Device 'secondAVD'
2012-02-18 11:27:15 - Emulator emulator: WARNING: Unable to create sensors port: Unknown error
2012-02-18 11:27:16 - LunchList New emulator found: emulator-5554
2012-02-18 11:27:16 - LunchList Waiting for HOME ('android.process.acore') to be launched...
2012-02-18 11:29:15 - LunchList emulator-5554 disconnected! Cancelling 'apt.tutorial.LunchList activity launch'!
Close your eclipse and AVD both and start again everything will be fine.
try to run in your command prompt:
adb kill-server
adb start-server
this is to restart the Android Debug Bridge.
If you have any problem running the command above, try to check if adb in in your path environment variable.
Try to remove BackCamera and Snapshot from Emulator, it worked for me.