I'm following the book "Professional Android 2 Application Development" by Reto Meier. I created the "HelloWorld" project. I use Eclipse as an IDE. If I run the application then the simulator starts but my application cannot run. he following information is displayed in the console:
[2011-07-03 16:03:28 - Hello_world] ------------------------------
[2011-07-03 16:03:28 - Hello_world] Android Launch!
[2011-07-03 16:03:28 - Hello_world] adb is running normally.
[2011-07-03 16:03:28 - Hello_world] Performing com.paad.HelloWorld.Hello_worldActivity activity launch
[2011-07-03 16:03:28 - Hello_world] Automatic Target Mode: Preferred AVD 'device2_1' is not available. Launching new emulator.
[2011-07-03 16:03:28 - Hello_world] Launching a new emulator with Virtual Device 'device2_1'
[2011-07-03 16:03:56 - Hello_world] New emulator found: emulator-5554
[2011-07-03 16:03:56 - Hello_world] Waiting for HOME ('android.process.acore') to be launched...
[2011-07-03 16:05:12 - Hello_world] emulator-5554 disconnected! Cancelling 'com.paad.HelloWorld.Hello_worldActivity activity launch'!
I cannot understand why my application is not able to run.
Did you wait until the emulator finished starting?
The log you posted may indicate that you closed the emulator before it started up.
The start takes a while, depending on the device configuration you have chosen (up to 5 minutes for me, if I try to launch a tablet emulator).
While starting, it goes to a small text saying "android" to an android text-logo and after that its usually up
And did you unlock them emulator? The emulator behaves like a real phone,
there is the usual key-lock in place. You have to release that first,
depending on the android version your are using you either have to drag a handle sideways
or press the menu key (e.g. in Android 1.6). If the phone is locked, you cant launch your app. There should be some info text on the screen telling you what to do.
After you got that, try to run your app again. It should start.
Please note that you can leave the emulator open once you started it.
If you run your application, the newest version will always be uploaded into the
emulator and executed. No need to restart the emulator all the time (which takes ages).
Android has some very good official documentation and tutorials. I suggest you try starting with the "official" Hello World example. I started there with my first Android app, and it worked as advertised for me.
You could post your code so we can see possible problems.
You can also look at warnings and errors with LogCat (Window > Open Perspective > Other... > DDMS or something). Then use Log.d or Log.e in your code so you can trace how far it gets before messing up.
Related
I'm trying to run one of the Android sample apps in Eclipse. I've been through all the possible errors, and now I was finally able to run without any of them. But still, nothing works, and the emulator just has the "android" sign shining on it.
The log I have is:
[2011-12-26 21:18:50 - AccelerometerPlayActivity] ------------------------------
[2011-12-26 21:18:50 - AccelerometerPlayActivity] Android Launch!
[2011-12-26 21:18:50 - AccelerometerPlayActivity] adb is running normally.
[2011-12-26 21:18:50 - AccelerometerPlayActivity] Performing com.example.android.accelerometerplay.AccelerometerPlayActivity activity launch
[2011-12-26 21:19:26 - AccelerometerPlayActivity] Uploading AccelerometerPlayActivity.apk onto device 'emulator-5554'
[2011-12-26 21:19:26 - AccelerometerPlayActivity] Installing AccelerometerPlayActivity.apk...
[2011-12-26 21:19:28 - AccelerometerPlayActivity] Success!
[2011-12-26 21:19:28 - AccelerometerPlayActivity] Starting activity com.example.android.accelerometerplay.AccelerometerPlayActivity on device emulator-5554
I already changed the configuration of the AVD, created a new one, etc. Nothing seems of any help
Does anyone have any idea?
Thanks
I would try to 'downgrade' the emulator.
I'm assuming you aren't programming for the newest android 4.0+ or something like that,
(Samsung galexy s is 2.0 or 2.2, I think).
When I had that problem it helped me alot.
try it :)
I had similar problem a long time ago. Make sure that path to your android sdk (or adb) doesn't contain any national symbols (cyrillic in my case) except English.
If you using Windows, also check your profile name.
Wait a little more.... in some computers, the emulator wait up to 10 minutes to run first time. Its a lot of time, but, next compile time, don´t close it, just clear proyect, build all and run, and it will work.
If I run my application when there is allready an emulator running, the applications isn't run on the existing AVD, but a new one is started.
[2011-12-22 18:03:15 - Report_v6_2] ------------------------------
[2011-12-22 18:03:15 - Report_v6_2] Android Launch!
[2011-12-22 18:03:15 - Report_v6_2] adb is running normally.
[2011-12-22 18:03:15 - Report_v6_2] Performing mast.avalons.ReportActivity activity launch
[2011-12-22 18:03:15 - Report_v6_2] Automatic Target Mode: Preferred AVD 'Acer' is not available. Launching new emulator.
[2011-12-22 18:03:15 - Report_v6_2] Launching a new emulator with Virtual Device 'Acer'
[2011-12-22 18:03:28 - Report_v6_2] New emulator found: emulator-5554
[2011-12-22 18:03:28 - Report_v6_2] Waiting for HOME ('android.process.acore') to be launched ...
[2011-12-22 18:04:46 - Report_v6_2] emulator-5554 disconnected! Cancelling 'mast.avalons.ReportActivity activity launch'!
[2011-12-22 18:20:16 - Report_v6_2] ------------------------------
[2011-12-22 18:20:16 - Report_v6_2] Android Launch!
[2011-12-22 18:20:16 - Report_v6_2] adb is running normally.
I use Windows 7, Eclipse Indigo, last versions adt, adb,sdk
Q: Has this ever worked on your Windows 7 PC?
Suggestion:
http://androidforums.com/application-development/5398-android-help-emulator-5554-disconnected.html
solution : before message like "emulator-5554 disconnected!
Cancelling " go to Eclipse IDE-->window--> Show Views --> device-->
view menu --> reset adb
This is caused when your project properties are not setup to run manually and for whatever reason (SDK or Target version) the emulator opens in a new instance.
To Solve:
Right Click your Project --> Run As --> Run Configurations
Then, make sure the Project in question is the one selected on the left and the Name is on the top.
You will then see 'Target' at the top:
Choosing Manual should allow you to choose the running emulator. If not, make sure your project SDK is set with an SDK version you have installed or a range that is compliant:
<uses-sdk android:minSdkVersion="3" />
<uses-sdk android:targetSdkVersion="14" />
Hope that helps!
Try this! Possibly this could answer your query. https://stackoverflow.com/a/2049798/1051682
Also, if you can give it a try using Android x86, may resolve your issues.
Hmm...Looking at the first problem statement where "trying to open new app (in same emulator) when one is already running in emulator..." above mentioned link seemed to be relative thinking it could be similar issue. And if that problem exist, trying Android x86 comes next. Anyways. "Run as" pops up "Android Device Chooser" wherein you can select the already running emulator/device. I am unable to paste image, being new, but hope this helps. Thanks!
I got stuck at the first hurdle - The Hello World app. I kept seeing an emulator-5554 appear which my debugger was connecting to; after a bit of digging in the package names of the emulator from within DDMS, I noticed 'bluestacks'. I had Bluestacks emulator installed. On Mac i went to Library>Bluestacks Player and uninstalled - solved the problem.
I created a Hello-Android Application and made all the required configurations as told in the developer.android.com site. When i ran the application the emulator was not launched.
In the console the following message was displayed.
"[2011-07-08 10:44:04 - HelloAndroid] Android Launch!
[2011-07-08 10:44:04 - HelloAndroid] adb is running normally.
[2011-07-08 10:44:04 - HelloAndroid] Performing com.HelloAndroid.HelloAndroidActivity activity launch
[2011-07-08 10:44:04 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'AVD'
[2011-07-08 10:44:04 - HelloAndroid] Launching a new emulator with Virtual Device 'AVD'".
Then a pop up message came which showed the following.
"An Unhandled win32 exception occured in emulator-arm.exe[3656].
Just-In_time debugging this exception failed with the following error:
No installed debugger has Just-In-Time debugging Enabled.
In Visual Studio,Just-In_time debugging can be enabled from
Tools/Options/Debugging/Just-In_time.
Check the documentation index for 'Just-in-time debugging, errors'
for more information."
Please help me out so that I can launch the emulator.
Start the Android SDK Manager
In the SDK Manager, go to the "Virtual devices" page and click "New" to create a new device.
Make sure you create a "Target" API that is within the range of the API's that your app supports.
Once the Android Virtual Device (AVD) is created click "Start" to start it.
Wait until the AVD is fully started, then goto Eclipse
In Eclipse create a "Run configuration" for your app (if you do not have it already). In the run configuration
make sure you select the device you've just created.
Run your "run configuration".
Here are few instrucitons before running the Android applicaiton.
Make sure when you are launching the emulator for the first time for running this specific app you have not checked following check boxes.
. Launching from snapshots
because first time you don't have any snapshot existed before as you are running this application for the first time.
2 Make sure that you have selected small resolution emulator because larger resolutions does not perform good.
Hello stackOverflow readers,
I am hoping that this is a simple setup issue, but here it goes:
Eclipse 3.6.0
AVD 2.2 and 1.5 (created both and tried with both)
XP Pro 2002 SP3
I followed the tutorial at site http://developer.android.com/resources/tutorials/hello-world.html but my custom TextView control never rendered.
I set a few breakpoints in the public class HelloAndroid extends Activity method and these breakpoints are never tripped. It is as if my android.process.acore is never run, based on the console output.
I am tempted to remove all and reinstall the packages, but I thought I would ask the web for a little guidance first.
This is the output in the console window:
[2010-08-24 12:05:08 - HelloAndroid2] Android Launch!
[2010-08-24 12:05:08 - HelloAndroid2] adb is running normally.
[2010-08-24 12:05:08 - HelloAndroid2] Performing com.example.helloandroid2.HelloAndroid activity launch
[2010-08-24 12:05:08 - HelloAndroid2] Automatic Target Mode: launching new emulator with compatible AVD 'My_avd_2_point_2'
[2010-08-24 12:05:08 - HelloAndroid2] Launching a new emulator with Virtual Device 'My_avd_2_point_2'
[2010-08-24 12:05:11 - HelloAndroid2] New emulator found: emulator-5554
[2010-08-24 12:05:11 - HelloAndroid2] Waiting for HOME ('android.process.acore') to be launched...
< I then kill the Android simulator here >
[2010-08-24 12:05:34 - HelloAndroid2] emulator-5554 disconnected! Cancelling 'com.example.helloandroid2.HelloAndroid activity launch'!
Thanks in advance for helping me understand this issue.
What is displayed in the emulator screen ? Do you get to the "unlock" screen ?
It seems you don't wait enough for the emulator to launch.
I have the same issue but waiting and using the on/off button does not work. (I have the unlock screen up.)
Oddly, a different tutorial appears to work (Simple Flashlight).
Never mind - newbie issue I guess.
I got it to work by using (the Menu button, followed by) the Launcher icon, followed by choosing my app.
I am brand new to Eclipse and Android, but somewhat familiar with Java. That having been said, I tried to follow the 'Hello Android' tutorial from the developer site using the latest Eclipse (Galieo) and the 2.1 Android SDK, I am on a Macintosh running Snow Leopard (OS X 10.6). I have a default virtual device (though my target is actually for phones like my own HTC Incredible which has the snapdragon processor and of course all the latest accoutrement in smart phones).
Everything seemed to go okay until I went to RUN>RUN and then selected 'Android Application'. My computer spins its wheels for a while and then I see two errors. I have pasted the output from Eclipse below:
[2010-05-04 01:53:46 - HelloAndroid] ------------------------------
[2010-05-04 01:53:46 - HelloAndroid] Android Launch!
[2010-05-04 01:53:46 - HelloAndroid] adb is running normally.
[2010-05-04 01:53:46 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2010-05-04 01:53:46 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'myAVD'
[2010-05-04 01:53:46 - HelloAndroid] Launching a new emulator with Virtual Device 'myAVD'
[2010-05-04 01:53:58 - HelloAndroid] New emulator found: emulator-5554
[2010-05-04 01:53:58 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
[2010-05-04 01:53:59 - Emulator] 2010-05-04 01:53:59.501 emulator[10398: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.
[2010-05-04 01:54:23 - HelloAndroid] emulator-5554 disconnected! Cancelling 'com.example.helloandroid.HelloAndroid activity launch'!
I never do see the text in the emulator and the emulator crashes with a message about it quitting unexpectedly.
The crash report states:
Process: emulator [10472]
Path: /Applications/android-sdk-mac_86/tools/emulator
Identifier: emulator
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: eclipse [10468]
Date/Time: 2010-05-04 02:25:41.153 -0500
OS Version: Mac OS X 10.6.3 (10D573)
Report Version: 6
Interval Since Last Report: 2558914 sec
Crashes Since Last Report: 4
Per-App Crashes Since Last Report: 2
Anonymous UUID: C5F178C1-5290-4CA9-AD6E-E9C4F5582754
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000001fd2f000
Crashed Thread: 3
NOTE: Running the emulator from the command line with:
iainnitro-Mac:tools iainnitro$ ./emulator -avd myAVD
2010-05-04 02:49:23.011 emulator[10556: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.
Segmentation fault
iainnitro-Mac:tools iainnitro$
yields a segmentation fault(as noted above from the terminal output). So the emulator is dying on its own before anything can be shown.
I have tried restarting the ADB processes.
The actual code is line by line from the tutorial and I have never been able to get to the XML part yet.
I am not sure what is wrong with my environment setup or if it is just an incompatibility with Snow Leopard? I would REALLY appreciate any help in resolving this as I am very interested in developing on this platform.
Thank-you,
Mike N Lawrence, Kansas
No direct experience, but this seems to be a recurrent issue:
This thread suggests:
You haven't let the emulator boot all the way up. Start it then wait until you see a desktop, just like on a real phone.
This one mentions (I suspect point 1. is not a concern for you):
Get more RAM. I was running on 256 MB (which I believe is below minimum requirements), just upgraded today to 1024 MB (long time coming), application now starts fine. Although I still do see some error messages in the emulator, they don't seem to actually do anything.
Install from command line. This is a bit laborius, but you can launch an emulator from the command line (assuming <android sdk path>\tools is added to your PATH variable) just type emulator, then browse to the location of your_app_here.apk, and execute
adb install your_app_here.apk
If you launch the emulator from Eclipse, execute adb kill-service and then adb start-service first (or kill-server / start-server. not sure the exact commands). Then your app will be installed on the emulator.
Also (a bit old but might still be relevant)
Maybe the emulator is running so slow, and the adb server, or another component like "DDMS" is a little "desperate" because seems it's waiting to the emulator to iniatialize the some HOME aplication.
But the emulator is running slow, the console in Eclipse send a message: emulator-5554
disconnected! Cancelling 'com.android.hello.HelloAndroid' launch!; and the emulator continues running normally and boot it's system, but don't run application that I build.
So for that problem I run program, and when the emulator is opened, I go back to eclipse in DDMS Perspective and in the Device tab y press a button "restart adb server" before the console shows me the message of "emulator-5554 disconnected!".
I do it several times until the emulator finally boot the OS.
After booted the OS on the emulator, eclipse don't send that disconnect error, and "sends" the app that I've built, also the console shows messages about this.
Then finally appears on the mobile "Hello, Android".
There has been a discussion on this with two proposed solutions
http://code.google.com/p/android/issues/detail?id=724
Comment 17 by zachrcrowe, Jan 06, 2010
FYI - I had to change a line in the Hello Android example to read
this.setContentView(tv); in order for it to work. As mentioned above, the deprecation
warning shouldn't affect the functionality of the emulator.
Comment 18 by mfrony, Jan 14, 2010
I had the same problem when I ran the Hello Android example. The way I solved it and
could run my first Android code was by changing the Project Build Target from 1.1 to 1.5.
This seems to be a timing issue. For some reason Eclipse attempts to load the application on to the emulator before it is "ready". I'm not sure why this occurs but I did find a work around: just start the emulator from the command line before you run the application.
Start clean by closing Eclipse (maybe the OP didn't exit Eclipse before he tried to run via the command line?)
Start the emulator via Terminal by navigating to the android-sdk-mac_86/tools directory and typing:
./emulator -avd my_avd
Open Eclipse and attempt to run the tutorial again using the same steps as before
A dialog box should open asking whether you would like to start a new AVD or use the one that is already running--choose to use the one that is already running.
what i did was to move the circle that appears when the AVD launches to the unlock position, and there it was 'Hello, Android'!
I had this same problem when I tried to run the emulator using a 4.0 AVD. It used to crash at the bootup screen and show 'Segmentation fault' in the console. I was able to fix it by increasing the SD card size of the AVD to 1GB from 32MB.
For whatever reason, I stopped getting the segmentation fault when I added:
this.setContentView(tv);
the 'this' seemingly solved the issue. The seg fault happens if you try to run the emulator without any .apk file I assume. (I was getting that from the command line as well). I hope the tutorial will be updated.
See Related post
Another related post
This worked on Linux for me:
Run Emulator (Wait for the home screen of the Emulator to load)
Click Window > Open Perspective > DDMS
In Devices Panel, click on drop down menu > Reset adb
Run project