Here i am placing the console details ,i need to change any emulator settings or need to add any statements in manifest file .help me ,thank you
[2013-03-28 11:08:29 - Lisnx] Android Launch!
[2013-03-28 11:08:29 - Lisnx] adb is running normally.
[2013-03-28 11:08:29 - Lisnx] Performing com.lisnx.activity.SplashActivity activity launch
[2013-03-28 11:08:34 - Lisnx] Launching a new emulator with Virtual Device 'AVD_4.0'
[2013-03-28 11:08:45 - Lisnx] New emulator found: emulator-5554
[2013-03-28 11:08:45 - Lisnx] Waiting for HOME ('android.process.acore') to be launched...
[2013-03-28 11:10:49 - Lisnx] HOME is up on device 'emulator-5554'
[2013-03-28 11:10:49 - Lisnx] Uploading Lisnx.apk onto device 'emulator-5554'
[2013-03-28 11:11:00 - Lisnx] Installing Lisnx.apk...
[2013-03-28 11:12:43 - Lisnx] Success!
[2013-03-28 11:12:43 - facebook_y] Could not find facebook_y.apk!
[2013-03-28 11:12:43 - Lisnx] Starting activity com.lisnx.activity.SplashActivity on device emulator-5554
Looks like you need to install the facebook sdk into the emulator before your app will run.
Try this:
adb install %HOMEPATH%\facebook-android-sdk-3.0.1\bin\FBAndroid-2.1.apk
Extracted from here section #2
Related
My emulator stopped working whilst making an app and kept saying it couldn't install the .apk in the console whilst running. When running the emulator in the manager it loads fine but obviously doesn't have an app to load.
When I try and run the app in the emulator it gives me the error and then loads up the phone without my app on it. This suggests its the apps fault in my mind, so i created a new project which i left untouched where it just said "hello world", even when trying to run this I get the same issue.
I've tried other peoples responses on here such as moving the apk file but that was to no avail, I've ended up redownloading and installing the sdk files but the same error persists. I'm new to this & appreciate any help.
My console after attempting to run app:
[2014-03-28 19:57:52 - LiverpoolPolls] ------------------------------
[2014-03-28 19:57:52 - LiverpoolPolls] Android Launch!
[2014-03-28 19:57:52 - LiverpoolPolls] adb is running normally.
[2014-03-28 19:57:52 - LiverpoolPolls] Performing com.example.liverpoolpolls.Loadhomemenu activity launch
[2014-03-28 19:57:52 - LiverpoolPolls] Automatic Target Mode: launching new emulator with compatible AVD 'emulator'
[2014-03-28 19:57:52 - LiverpoolPolls] Launching a new emulator with Virtual Device 'emulator'
[2014-03-28 19:57:54 - LiverpoolPolls] New emulator found: emulator-5554
[2014-03-28 19:57:54 - LiverpoolPolls] Waiting for HOME ('android.process.acore') to be launched...
[2014-03-28 20:02:12 - LiverpoolPolls] HOME is up on device 'emulator-5554'
[2014-03-28 20:02:12 - LiverpoolPolls] Uploading LiverpoolPolls.apk onto device 'emulator-5554'
[2014-03-28 20:02:18 - LiverpoolPolls] Installing LiverpoolPolls.apk...
[2014-03-28 20:04:34 - LiverpoolPolls] Failed to install LiverpoolPolls.apk on device 'emulator-5554!
[2014-03-28 20:04:34 - LiverpoolPolls] (null)
[2014-03-28 20:04:35 - LiverpoolPolls] Launch canceled!
I shall download that other emulator and see where that gets me.
I have checked my api level of the device and the program i'm creating. I have also restarted my eclipse and the problem still does not seem to resolve. is there any other solutions to this ?
[2014-02-15 19:31:39 - JudoApp] New emulator found: emulator-5554
[2014-02-15 19:31:39 - JudoApp] Waiting for HOME ('android.process.acore') to be launched...
[2014-02-15 19:42:15 - JudoApp] HOME is up on device 'emulator-5554'
[2014-02-15 19:42:15 - JudoApp] Uploading JudoApp.apk onto device 'emulator-5554'
[2014-02-15 19:42:16 - JudoApp] Installing JudoApp.apk...
[2014-02-15 19:44:37 - JudoApp] Failed to install JudoApp.apk on device 'emulator-5554!
[2014-02-15 19:44:37 - JudoApp] (null)
[2014-02-15 19:44:38 - JudoApp] Launch canceled!
change ADB connection timeout from ddms (default is 5.000,change it to 10.000)
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
After updating to ADT 12, at first it seemed ok, then I got some problems like these:
Emulator runs improperly and gives the problem I report below.
I tried to use the quick code from XML windows and it mingles the codeline. Has anyone encountered the same problems?
This is the error I got in the console after trying to run a project:
[2011-07-14 20:28:36 - cursoMC5leccion6] ------------------------------
[2011-07-14 20:28:36 - cursoMC5leccion6] Android Launch!
[2011-07-14 20:28:36 - cursoMC5leccion6] adb is running normally.
[2011-07-14 20:28:36 - cursoMC5leccion6] Performing com.wocmultimedia.cursoMC5leccion6.Main activity launch
[2011-07-14 20:28:36 - cursoMC5leccion6] Automatic Target Mode: launching new emulator with compatible AVD 'avdGooglemarket'
[2011-07-14 20:28:36 - cursoMC5leccion6] Launching a new emulator with Virtual Device 'avdGooglemarket'
[2011-07-14 20:28:42 - cursoMC5leccion6] New emulator found: emulator-5554
[2011-07-14 20:28:42 - cursoMC5leccion6] Waiting for HOME ('android.process.acore') to be launched...
[2011-07-14 20:29:57 - cursoMC5leccion6] emulator-5554 disconnected! Cancelling 'com.wocmultimedia.cursoMC5leccion6.Main activity launch'!
[2011-07-14 20:33:22 - cursoMC5leccion6] ------------------------------
[2011-07-14 20:33:22 - cursoMC5leccion6] Android Launch!
[2011-07-14 20:33:22 - cursoMC5leccion6] adb is running normally.
[2011-07-14 20:33:22 - cursoMC5leccion6] Performing com.wocmultimedia.cursoMC5leccion6.Main activity launch
[2011-07-14 20:33:22 - cursoMC5leccion6] Automatic Target Mode: launching new emulator with compatible AVD 'avdGooglemarket'
[2011-07-14 20:33:22 - cursoMC5leccion6] Launching a new emulator with Virtual Device 'avdGooglemarket'
[2011-07-14 20:33:24 - Emulator] WARNING: Data partition already in use. Changes will not persist!
[2011-07-14 20:33:24 - Emulator] WARNING: SD Card image already in use: C:\Documents and Settings\Angelo Giammarresi\.android\avd\avdGooglemarket.avd/sdcard.img
[2011-07-14 20:33:24 - Emulator] WARNING: Cache partition already in use. Changes will not persist!
[2011-07-14 20:33:24 - cursoMC5leccion6] New emulator found: emulator-5556
[2011-07-14 20:33:24 - cursoMC5leccion6] Waiting for HOME ('android.process.acore') to be launched...
Delete all the "*.lock" dirs in your AVD directory, i.e. [...]/.android/avd/[youravd].avd
You will sometimes also need to delete snapshots.img
Path to AVD folders on Windows 7 is:
C:\ Users \ (YourUsername) \ .android \ avd \ (YourAVDsName.avd) \
Delete userdata and sdcard image files from avd folder.That will fix this error for me
To clear the "already in use" problem without losing the state of your AVD, the specific files you need to delete are the "pid" files in the .lock directories under YourAVDName.avd. I did this while the AVD was not running, but I didn't test it without closing the AVD, so I don't know for certain if that is necessary (though it seems logical.)
clear your eclipse AVD (delete data with *.lock files)
The AVD locks some resources to be able to run. Clear your .lock directories, the AVD might have not closed properly which resulted into the resources being still locked, AVD unlocks the resources by simply deleting the .lock directories, you can do that manually by deleting the .lock directories.