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?
Related
I have been trying to get the HelloIOIO example running for ages now. It really looks good now. All dependencies are met. All the Libraries built succesfully. (All this thanks to this awesome page: https://github.com/ytai/ioio/wiki/Eclipse-Troubleshooting)
But when I want to start the app on my phone I get this:
[2014-02-03 19:34:33 - HelloIOIO] Android Launch!
[2014-02-03 19:34:33 - HelloIOIO] adb is running normally.
[2014-02-03 19:34:33 - HelloIOIO] Performing ioio.examples.hello.MainActivity activity launch
[2014-02-03 19:34:33 - HelloIOIO] Uploading HelloIOIO.apk onto device '172.16.10.103:5555' [2014-02-03 19:34:34 - HelloIOIO] Installing HelloIOIO.apk...
[2014-02-03 19:34:45 - HelloIOIO] Success!
[2014-02-03 19:34:46 - IOIOLibAndroid] Could not find IOIOLibAndroid.apk!
[2014-02-03 19:34:46 - HelloIOIO] Starting activity ioio.examples.hello.MainActivity on device 172.16.10.103:5555
[2014-02-03 19:34:47 - HelloIOIO] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=ioio.examples.hello/.MainActivity }
The funny thing is though that in the actual IOIOLibAndroid-Project is a ioiolibandroid.jar-File (As I said - it is compiling perfectly)
Please help me :)
I found some help here:
groups.google.com/forum/#!topic/ioio-users/WmWrdpyjc8U
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 }
I installed the Android Development Tool and created my first app but when I run the app, the emulator doesnt launch.The console reads:
[2013-06-18 14:36:57 - MyFirstApp] Android Launch!
[2013-06-18 14:36:57 - MyFirstApp] adb is running normally.
[2013-06-18 14:36:57 - MyFirstApp] Performing com.example.myfirstapp.MainActivity activity launch
[2013-06-18 14:37:19 - MyFirstApp] Launching a new emulator with Virtual Device 'AVD'
Unfortunately, it never launches. The following is what I have tried to do to solve the problem:
I created AVD both by graphical user interface and command line but it didnt run.
I tried to open task manager and stop the adb.exe process then run it again but no.
I tried to kill the adb server and restart it by command line but again no, didnt run.
I finally tried to launch the emulator on command line and this is what it says (directly translated): "a problem interrupted the program, trouble-free operation. Windows will close the program and notify you if a solution to the problem is available."
Please help.
After a long struggle, I decided to install a new Operating System. The emulator can now launch.
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.
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