I am trying to create a android application in eclipse .When i am running the application it is showing
[2013-06-26 11:14:41 - FirstApp] Android Launch!
[2013-06-26 11:14:41 - FirstApp] adb is running normally.
[2013-06-26 11:14:41 - FirstApp] Performing com.example.firstapp.MainActivity activity launch
[2013-06-26 11:14:41 - FirstApp] Automatic Target Mode: launching new emulator with compatible AVD 'Test'
[2013-06-26 11:14:41 - FirstApp] Launching a new emulator with Virtual Device 'Test'
[2013-06-26 11:14:50 - FirstApp] New emulator found: emulator-5554
[2013-06-26 11:14:50 - FirstApp] Waiting for HOME ('android.process.acore') to be launched...
[2013-06-26 11:16:24 - FirstApp] HOME is up on device 'emulator-5554'
[2013-06-26 11:16:24 - FirstApp] Uploading FirstApp.apk onto device 'emulator-5554'
[2013-06-26 11:16:25 - FirstApp] Installing FirstApp.apk...
[2013-06-26 11:18:30 - FirstApp] Failed to install FirstApp.apk on device 'emulator-5554!
[2013-06-26 11:18:30 - FirstApp] (null)
[2013-06-26 11:18:30 - FirstApp] Launch canceled!
I also faced the same issue once and one of the following should work for you:-
Restart the virtual device with the option Wipe User Data checked and then run the app. That works for me,
Simply restart the device and check,
Restart the device after changing the VM heap size.
If restarting the device doesn't work, try increasing the upload timeout to something really huge like 20000 ms. It's at Window → Preferences → Android → DDMS → "ADB connection time out (ms)".
Please post your AndroidManifest.xml code as well. I think u didn't placed the below code for Activity to be launched.
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
If any logcat errors/warnings present, please post them as well. So, that we can help much better.
Try and format the log output so that its better readable. However, most likely you have something wrong in your Manifest. Check adb logcat (or the Logcat Tab in the DDMS perspective) while the app is installed. You should see some info there on what exactly android does not like with your application.
Related
I am new to developing Android applications. My first application takes too much time to load, and fails at the end.
I'm using a Windows 8 laptop with 4GB of RAM and an Intel processor. I'm writing all of this because I saw an answer regarding Windows.
[2014-03-08 07:26:52 - Mytest] Android Launch! [2014-03-08 07:26:52 -
Mytest] adb is running normally.
[2014-03-08 07:26:52 - Mytest] Performing
com.example.mytest.MainActivity activity launch
[2014-03-08 07:26:53 - Mytest] Automatic Target Mode: launching new
emulator with compatible AVD 'nnt'
[2014-03-08 07:26:53 - Mytest] Launching a new emulator with Virtual
Device 'nnt'
[2014-03-08 07:27:15 - Mytest] New emulator found: emulator-5554
[2014-03-08 07:27:15 - Mytest] Waiting for HOME
('android.process.acore') to be launched
[2014-03-08 07:39:36 - Mytest] HOME is up on device 'emulator-5554'
[2014-03-08 07:39:36 - Mytest] Uploading Mytest.apk onto device
'emulator-5554'
[2014-03-08 07:39:36 - Mytest] Installing Mytest.apk...
[2014-03-08 07:41:51 - Mytest] Failed to install Mytest.apk on device
'emulator-5554!
[2014-03-08 07:41:51 - Mytest] (null) [2014-03-08 07:41:51 - Mytest]
Launch canceled!
Please let me know.
I have had this problem before. I have tried following steps.
Plug-in your charger, if it's not connected.
Start emulator from AVD - manager, this works for most of the time.
Try Genymotion emulator, it is free for personal use and it works smooth. You also can use Eclipse plug-in.
Get it here: Genymotion
If you having troubles with installation, here is User Guide.
I am using it and I am very happy.
I am following http://developer.android.com/training/basics/firstapp/running-app.html
and trying to run my first android app on the emulator on my PC.
The emulator is running (started from eclipse)
I managed to lauch myFirst App via eclipse as described, although in this tutorial it should be added you have to wait minutes before the emulator is up and running.
Now my problem is that when I modify myFirstApp, and wnat to test it, that eclipse keeps starting a new emulator:
[2012-10-15 19:32:44 - MyFirstApp] ------------------------------
[2012-10-15 19:32:44 - MyFirstApp] Android Launch!
[2012-10-15 19:32:44 - MyFirstApp] adb is running normally.
[2012-10-15 19:32:45 - MyFirstApp] Performing com.example.myfirstapp.MainActivity activity launch
[2012-10-15 19:32:45 - MyFirstApp] Automatic Target Mode: Preferred AVD 'Hobbit' is not available. Launching new emulator.
[2012-10-15 19:32:45 - MyFirstApp] Launching a new emulator with Virtual Device 'Hobbit'
This is extremely annoying, because of the performance penalty to launch a complete emulator.
But what is even more frustrating that I get back the very first version of MyFirstApp in this new emulator.
When I restart myself the emulator from scratch I see this in the console:
[2012-10-15 19:55:42 - MyFirstApp] New emulator found: emulator-5554
[2012-10-15 19:55:42 - MyFirstApp] Waiting for HOME ('android.process.acore') to be launched...
[2012-10-15 19:56:57 - MyFirstApp] emulator-5554 disconnected! Cancelling 'com.example.myfirstapp.MainActivity activity launch!'
Why? The emulator is still running at this point. This cannot be the normal way of working. Can anybody help me out?
Go to Run -> Run Configuration in eclipse. Select your application and update the target tab at right side to "Always prompt to pick device"
If the emulator is running and doesnt show in Devices then try to reset adb.
In eclipse: Device tab-> Dropbown - > reset abd
I have been working on fixing this for two days to no eval. Any Help would be much appreciated.
I have the following installed:
Eclipse
android-sdk-macosx
Android SDK Tools
Android 2.2 API 8
Android 2.3.3 API 10
I have a phonegap Project setup. Click "Run" -> "Run as" -> "Android Application"
In the console tap I see this:
[2011-12-14 10:47:38 - Foanar] ------------------------------
[2011-12-14 10:47:38 - Foanar] Android Launch!
[2011-12-14 10:47:38 - Foanar] adb is running normally.
[2011-12-14 10:47:38 - Foanar] Performing com.phonegap.foanar.App activity launch
[2011-12-14 10:47:38 - Foanar] Automatic Target Mode: launching new emulator with compatible
AVD '3DEVO'
[2011-12-14 10:47:38 - Foanar] Launching a new emulator with Virtual Device '3DEVO'
[2011-12-14 10:47:40 - Emulator] 2011-12-14 10:47:40.256 emulator-arm[3278:80b] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.
[2011-12-14 10:47:40 - Emulator] emulator: WARNING: Unable to create sensors port: Connection refused
[2011-12-14 10:47:40 - Foanar] New emulator found: emulator-5554
[2011-12-14 10:47:40 - Foanar] Waiting for HOME ('android.process.acore') to be launched...
[2011-12-14 10:48:04 - Foanar] HOME is up on device 'emulator-5554'
[2011-12-14 10:48:04 - Foanar] Uploading Foanar.apk onto device 'emulator-5554'
[2011-12-14 10:48:05 - Foanar] Installing Foanar.apk...
The AVD "3DEVO" Launches but never installs the Foanar.apk. I never get any errors in LogCat or Console. Eclipse seems to hang here and go no further. I suspect it maybe has something to do with this line:
[2011-12-14 10:47:40 - Emulator] emulator: WARNING: Unable to create sensors port: Connection refused
I have been able to install the app via terminal using:
adb install /CapitalOnline/android/Foanar/bin/Foanar.apk
I would like to get Eclipse back up and working as terminal is ok but Eclipse is more convenient for testing builds directly from Eclipse. I used to be able to run this all the time. The only change to my machine outside of Eclipse that may or may not have anything to do with this... I installed AppMobi XDK and AppMobiPhoneGap XDK though my Chrome browser which creates its own dev environment in my user directory. Is it possible that in some way ports are crossing and refusing connections?
Thanks to anyone willing to help figure this out!
Once I came across this problem too. I don't remember exactly what I did to resolve it. I have had 2 emulator-related problems in that period and I found solutions for both of them, but now I can't remember which solution was for which problem :) So I'll suggest both methods.
Try cleaning the user data on your emulator. To do so, open your avd location (for me it was "C:\Users\UserName.android\avd") find your emulator (I guess it's 3DEVO.avd) and delete the files called "userdata.img" and "userdata-qemu.img".
While your program is running and stuck, open your Task Manager, go to processes and kill adb. Go back to Eclipse and run again. If there's an error about adb not launched, quit Eclipse and launch again.
Hope this will help.
killing adb from activity monitor fixed this for me.
if you have the device view open (windows > show views > other... > android > devices), you can choose downward arrow > reset adb
Since last week when I run a project it starts the emulator but sooner I got this message and I have to close and restart again otherwise it refuse to install the apk. Does someone know some reasons and what I have to do beside destroy and rebuild the Avd cause it doesn't make any change. Thank you. Here's the console lines
[2011-07-30 19:39:24 - NewStavanger] ------------------------------
[2011-07-30 19:39:24 - NewStavanger] Android Launch!
[2011-07-30 19:39:24 - NewStavanger] adb is running normally.
[2011-07-30 19:39:24 - NewStavanger] Performing com.wocmultimedia.NewStavanger.Main activity launch
[2011-07-30 19:39:24 - NewStavanger] Automatic Target Mode: launching new emulator with compatible AVD 'avdGooglemarket'
[2011-07-30 19:39:24 - NewStavanger] Launching a new emulator with Virtual Device 'avdGooglemarket'
[2011-07-30 19:39:31 - NewStavanger] New emulator found: emulator-5554
[2011-07-30 19:39:31 - NewStavanger] Waiting for HOME ('android.process.acore') to be launched...
[2011-07-30 19:40:46 - NewStavanger] emulator-5554 disconnected! Cancelling 'com.wocmultimedia.NewStavanger.Main activity launch'!
A lot of times wiping the user data off the emulator will fix those types of problems, I've had emulators get pretty buggy sometimes, especially if you constantly open and reclose them. Reinstalling the emulator would likely fix the issue. If its setup is fairly simple, that should only take a few minutes.
Try this site:
http://phonedevelopment.blogspot.com/2010/09/android-emulator-5554-disconnected.html
Running Eclipse 3.5.2 (Classic) in OS X 10.6.7 with the ADT plugin. I have the SDK installed and have run the SDK and AVD Manager to install all available platforms and tools. I have an AVD setup with Android 2.2 as the target API, and have configured the example 'Hello, Android' app for Android 2.1 Update 1, so compatibility should not be an issue. When I Run the application, it starts up the emulator, but gives me an error before the android startup animation appears. Here is the output in the Console window of Eclipse:
[2011-04-10 06:45:40 - HelloAndroid] ------------------------------
[2011-04-10 06:45:40 - HelloAndroid] Android Launch!
[2011-04-10 06:45:40 - HelloAndroid] adb is running normally.
[2011-04-10 06:45:40 - HelloAndroid] Performing com.twopoint7.testing.HelloAndroid activity launch
[2011-04-10 06:45:40 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'testDroid'
[2011-04-10 06:45:40 - HelloAndroid] Launching a new emulator with Virtual Device 'testDroid'
[2011-04-10 06:46:04 - Emulator] 2011-04-10 06:46:04.613 emulator[997:903] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.
[2011-04-10 06:46:04 - HelloAndroid] New emulator found: emulator-5554
[2011-04-10 06:46:04 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
[2011-04-10 06:47:22 - HelloAndroid] emulator-5554 disconnected! Cancelling 'com.twopoint7.testing.HelloAndroid activity launch'!
Any advice on what might be going wrong would be greatly appreciated. I've found lots of posts (here and on other forums) that seem to indicate the NSQuickDrawView vs. Quartz warning seems to be a problem across the board but doesn't have a solution yet. I'm more concerned with the "emulator-5554 disconnected..." bit and the fact that I can't seem to run any apps in the emulator. Any other info I can provide which would be helpful? Any insight?
Thanks in advance for your time!
I guess you need to reset your adb after launch the emulator. In eclipse, go to window -> show view -> other -> device(under android folder).
In the device view, find and reset adb. Then run your apps.