Develop Reference

Seeing my android application on emulator all the time

My Android application has successfully installed , but I am not sure if it ran or not.
It may have run for a short time or not at all.
How do I fix the emulator so that I can watch my application all the time?
[2014-01-30 12:11:22 - AndApp] Installing AndApp.apk...
[2014-01-30 12:13:12 - AndApp] Success!
[2014-01-30 12:13:13 - AndApp] Starting activity
com.example.AndApp.MainActivity on device emulator-5554
[2014-01-30 12:13:17 - AndApp] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.example.AndApp/.MainActivity }

Build android error activity manager

Please help me, i try build android with eclipse on device phone warning error
[2013-11-10 19:04:28 - SynergyAutoparts] Android Launch!
[2013-11-10 19:04:28 - SynergyAutoparts] adb is running normally.
[2013-11-10 19:04:28 - SynergyAutoparts] Performing com.gatot.synergyautoparts.MainActivity activity launch
[2013-11-10 19:04:31 - SynergyAutoparts] Application already deployed. No need to reinstall.
[2013-11-10 19:04:31 - SynergyAutoparts] Starting activity com.gatot.synergyautoparts.MainActivity on device SANUGYPY5KBWOYLNVB6
[2013-11-10 19:04:32 - SynergyAutoparts] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.gatot.synergyautoparts/.MainActivity }
[2013-11-10 19:04:32 - SynergyAutoparts] ActivityManager: Warning: Activity not started, its current task has been brought to the front
thk

Just kill currently working process on your AVD and try to this again. AVD relaunch can help as well.

Trouble running app from Eclipse after ICS update

Ever since my phone got updated to ICS about a month ago (HTC Design on Sprint) whenever I try to run my app from eclipse about 80% of the time it fails. No error, just doesn't run. I get this in the console:
[2012-09-21 17:29:59 - GetAClue] ------------------------------
[2012-09-21 17:29:59 - GetAClue] Android Launch!
[2012-09-21 17:29:59 - GetAClue] adb is running normally.
[2012-09-21 17:29:59 - GetAClue] Performing com.badbob.app.getaclue.MainActivity activity launch
[2012-09-21 17:30:01 - GetAClue] Uploading GetAClue.apk onto device 'HT1CHMB00902'
[2012-09-21 17:30:01 - GetAClue] Installing GetAClue.apk...
[2012-09-21 17:30:15 - GetAClue] Success!
[2012-09-21 17:30:15 - GetAClue] Starting activity com.badbob.app.getaclue.MainActivity on device HT1CHMB00902
But it stops there and doesn't give me one of these like it should:
[2012-09-21 17:26:28 - GetAClue] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.badbob.app.getaclue/.MainActivity }
If I keep trying eventually it will run. I also notice that when it fails the processor on my phone is thrashed for a good minute or two. Can't tell what process is thrashing it though.
I have 2 older Droid X's that I don't have this problem with. I also have two dev computers and it happens on both of them with the HTC so it seems to be something up with my phone, or ICS.
Anyone else experiencing this?

After change some code, should i restart the Android Emulator?

I have opened the Android Emulator for my first set of code change. Then later i change some of my code. Should i want to close the emulator and relaunch (re-run) the code to reflect my new changes? or else simply pressing run key in eclipse will reflect the changes?
Please clarify.
PS : Till now, i wont close and relaunch the emulator for every code change. But today i faced the error in console like "Application already running, uninstall the application and try". That's why i have doubt on this.

You do not need to relaunch the emulator, pressing the Run button in Eclipse will work.
When you receive a message similar to this one:
Re-installation failed due to different application signatures.
You must perform a full uninstall of the application. WARNING: ...This will remove the application data!
Please execute 'adb uninstall com.antew.code' in a shell.
Open a command prompt and use:
adb uninstall <package name>
e.g.
adb uninstall com.antew.code
Then relaunch the application from Eclipse to install it again. The adb exe is in the /platform-tools/ folder of the SDK.

no need to close the emulator at all .............
the message is due to as some time application is in front (running) emulator denys to re-run . For this just simply close the app by back button and run from eclipse

There is no need to restart the emulator for a code change -- simply "Run"ning it from Eclipse does the trick. I think the reason you're getting that error is that you're trying to run it with no code changes.

Don't restart your emulator for every changes made. Just deploy your application on the emulator.
If you won't face the Application already running, uninstall the application and trybe sure that your application is not started in the emulator.
If it is,just switch to another ativity and then try deploy your application.

There is no need to restart the emulator!!!
You simply need to run youe application again from eclipse(Ctrl + F11). If you have done any changes in code(and saved them all) then on running the application you will get output something like below
[2013-06-19 13:19:12 - MyFirstApp] ------------------------------
[2013-06-19 13:19:12 - MyFirstApp] Android Launch!
[2013-06-19 13:19:12 - MyFirstApp] adb is running normally.
[2013-06-19 13:19:12 - MyFirstApp] Performing com.example.myfirstapp.MainActivity activity launch
[2013-06-19 13:19:12 - MyFirstApp] Automatic Target Mode: using existing emulator 'emulator-5554' running compatible AVD 'Micromax_A_68'
[2013-06-19 13:19:12 - MyFirstApp] Uploading MyFirstApp.apk onto device 'emulator-5554'
[2013-06-19 13:19:14 - MyFirstApp] Installing MyFirstApp.apk...
[2013-06-19 13:19:26 - MyFirstApp] Success!
[2013-06-19 13:19:26 - MyFirstApp] Starting activity com.example.myfirstapp.MainActivity on device emulator-5554
[2013-06-19 13:19:28 - MyFirstApp] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.example.myfirstapp/.MainActivity
Above logs are specific to my app but you get the point... If you have no changes saved then you will get some additional output lines as follows
...
[2013-06-19 13:22:10 - MyFirstApp] Application already deployed. No need to reinstall.
...

No variables shown in eclipse debugging

I saw many similar questions, but the solution was not found, so i'm asking:
When i'm debuging the my android app NONE of the variables are shown in the "Variables" window. The console shows me that the debuger is not fully loaded.
[2012-02-21 22:23:29 - Watcher] Android Launch!
[2012-02-21 22:23:29 - Watcher] adb is running normally.
[2012-02-21 22:23:29 - Watcher] Performing com.workspace.watcher.WatcherActivity activity launch
[2012-02-21 22:23:29 - Watcher] Automatic Target Mode: using device 'F4559C737D65'
[2012-02-21 22:23:32 - Watcher] Application already deployed. No need to reinstall.
[2012-02-21 22:23:32 - Watcher] Starting activity com.workspace.watcher.WatcherActivity on device F4559C737D65
[2012-02-21 22:23:33 - Watcher] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.workspace.watcher/.WatcherActivity }
[2012-02-21 22:23:34 - Watcher] Attempting to connect debugger to 'com.workspace.watcher' on port 8601
What is the problem? How can i fix it?

After talking with Chorche in chat we determined that the problem was he did not set any breakpoints and as such there were no available variables to read.
This seems to be a pretty good explanation / tutorial on debugging using eclipse: http://www.vogella.de/articles/EclipseDebugging/article.html