Develop Reference

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.
...

android app won't install

I recently bought a couple of books on android programming and have been having a terrible time getting anything to work. I finally got one of the books sample code to show up. I noticed that when it worked that in the eclipse console it showed installation logging. In everything else I've tried it never gets to that point. All I ever get is what is shown below. Does anyone know why it doesn't continue to the installation point?
I also noticed that in the code that does work, there's a folder structure in the bin directory that matches the src directory.
src>com.deitel.doodlz
bin>com>deitel>doodlz - contains all the class files
In my project, there is no folder structure like this in my bin directory. Is there something else I need to do besides just hitting the run button? Do I have to do some type of build first? Thanks.
[2012-03-12 21:21:52 - Now2] ------------------------------
[2012-03-12 21:21:52 - Now2] Android Launch!
[2012-03-12 21:21:52 - Now2] adb is running normally.
[2012-03-12 21:21:52 - Now2] Performing my.android.stuff.Now2Activity activity launch
[2012-03-12 21:21:52 - Now2] Automatic Target Mode: Preferred AVD 'android_2_3_3' is not available. Launching new emulator.
[2012-03-12 21:21:52 - Now2] Launching a new emulator with Virtual Device 'android_2_3_3'
[2012-03-12 21:21:57 - Emulator] emulator: WARNING: Unable to create sensors port: Unknown error
[2012-03-12 21:21:57 - Emulator] emulator: emulator window was out of view and was recentered
[2012-03-12 21:21:57 - Emulator]

failed to link /system/bin/sh CANNOT LINK EXECUTABLE

I've been using the Android development tools in Eclipse to make a proof-of-concept app for my employer, to show them what our company can do with apps. I've got a long history of programming with and without IDEs; I've written several internal Java tools using Eclipse. However, I've never messed around under the hood of Eclipse or the ADT.
I was hammering away at the project this morning, and I changed one simple string in res/values/strings.xml. I didn't even change the length of the string, just changed two characters from "35" to "50". When I hit Run to see the changes, I got this cryptic message in the console output:
[2012-02-21 13:56:58 - CableCalc2] ------------------------------
[2012-02-21 13:56:58 - CableCalc2] Android Launch!
[2012-02-21 13:56:58 - CableCalc2] adb is running normally.
[2012-02-21 13:56:58 - CableCalc2] Performing com.rletech.cablecalc2.CableCalc2 activity launch
[2012-02-21 13:56:58 - CableCalc2] Automatic Target Mode: Preferred AVD 'first_avd' is available on emulator 'emulator-5554'
[2012-02-21 13:56:58 - CableCalc2] WARNING: Unknown device API version!
[2012-02-21 13:56:58 - CableCalc2] Uploading CableCalc2.apk onto device 'emulator-5554'
[2012-02-21 13:57:01 - CableCalc2] Installing CableCalc2.apk...
[2012-02-21 13:57:01 - CableCalc2] Success!
[2012-02-21 13:57:01 - CableCalc2] Starting activity com.rletech.cablecalc2.CableCalc2 on device emulator-5554
[2012-02-21 13:57:01 - CableCalc2] ActivityManager: link_image[1995]: failed to link /system/bin/sh
[2012-02-21 13:57:01 - CableCalc2] ActivityManager: CANNOT LINK EXECUTABLE
[2012-02-21 13:57:01 - CableCalc2] ActivityManager:
... and I'm stuck there. I tried some other projects that I know should work, because they've worked before, including the classic HelloAndroid project. All projects give me this same failure.
I didn't change anything in the code. It's like the ADT or Eclipse changed something for me and forgot to tell me about it. Any clue on how I can fix it?
System details:
Eclipse Indigo SR1 build ID 20110916-0149. Downloaded some time ago.
Android Development Toolkit version 16.0.1.v201112150204-238534. Downloaded on 6-Feb-2012.
ADB version is 1.0.29
Emulator platform 2.2 (API level 8)
Update before posting: I also have a platform for 4.0.3 (API level 15), and everything still works when I change the Run Configuration to 4.0.3. That's fine, but our customers don't run out and buy new Androids every month, so we need to run it and test it on API level 8. And like I said, it stopped working on API level 8, rather abruptly and not for a predictable reason.
As a proof of concept, this isn't looking terribly good. So once again, how do I fix it?
--
Regards
Ray

WAY late to the party here, but I've found that you can get this error when /system/bin/linker is deleted from your Android device. (In my case, I was trying to update linker at runtime). A missing linker seems to throw this error on every executable, not just sh. In my case, I was able to restore /system/bin/linker with adb push, but the device still continued to have problems, and ultimately, completely re-flashing the OS was the only solution I found that worked.

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