I can't install an app made in eclipse - android

I have not managed to install or debug an app made by me.
1.- I was unable to compile my app so I updated all packages with all the versions on them. That worked.(My app does not have errors anymore.)
2.- I tried to debug it with some virtual devices I created (and deleted several times) and get the error in console(I tried all the answers given to this, like restarting and adding time to the timeout, and all the stuff posted on similar questions):
[2014-03-06 09:46:31 - MainActivity] Launching a new emulator with Virtual Device 'android_2.2'
[2014-03-06 09:46:35 - MainActivity] New emulator found: emulator-5554
[2014-03-06 09:46:35 - MainActivity] Waiting for HOME ('android.process.acore') to be launched...
[2014-03-06 09:46:54 - MainActivity] WARNING: Application does not specify an API level requirement!
[2014-03-06 09:46:54 - MainActivity] Device API version is 8 (Android 2.2)
[2014-03-06 09:46:54 - MainActivity] HOME is up on device 'emulator-5554'
[2014-03-06 09:46:54 - MainActivity] Uploading MainActivity.apk onto device 'emulator-5554'
[2014-03-06 09:46:54 - MainActivity] Installing MainActivity.apk...
[2014-03-06 09:49:02 - MainActivity] Failed to install MainActivity.apk on device 'emulator-5554!
[2014-03-06 09:49:02 - MainActivity] (null)
[2014-03-06 09:49:02 - MainActivity] Launch canceled!
3.- I tried to push the file to the virtual device, that did not worked.
4.- After that I opted for using a real device. Here is the error:
[2014-03-06 10:09:14 - MainActivity] Android Launch!
[2014-03-06 10:09:14 - MainActivity] adb is running normally.
[2014-03-06 10:09:14 - MainActivity] Performing *.MainActivity activity launch
[2014-03-06 10:09:23 - MainActivity] WARNING: Application does not specify an API level requirement!
[2014-03-06 10:09:23 - MainActivity] Device API version is 16 (Android 4.1.2)
[2014-03-06 10:09:23 - MainActivity] Uploading MainActivity.apk onto device '****************'
[2014-03-06 10:09:23 - MainActivity] Installing MainActivity.apk...
[2014-03-06 10:09:24 - MainActivity] Installation failed due to invalid APK file!
[2014-03-06 10:09:24 - MainActivity] Please check logcat output for more details.
[2014-03-06 10:09:24 - MainActivity] Launch canceled!
5.- My last resource push the .apk file to real device. The file was transferred ok, but when I try to install it, I get this:
PARSER ERROR
There was a problem parsing the package.
My questions are, What am i doing wrong? or Is there some kind of execution time error, i am not getting?

WARNING: Application does not specify an API level requirement!
In AdnroidManifest what sdk u use
<uses-sdk
android:minSdkVersion="14"
android:targetSdkVersion="19" />

Related

Installation error: Unknown failure

I have installed the ADT 23.04 plugin into my eclipse and Android SDK of the same version.
I am able to successfully start the AVD but when I try start the AVD a black black screen appears without and remains for many minutes without anything happening and then when I try to run the project on the AVD,I get the following error log:
[2014-12-15 23:05:53 - MyApp] ------------------------------
[2014-12-15 23:05:54 - MyApp] Android Launch!
[2014-12-15 23:05:54 - MyApp] adb is running normally.
[2014-12-15 23:05:54 - MyApp] Performing com.example.myapp.ExampleActivity activity launch
[2014-12-15 23:05:54 - MyApp] Automatic Target Mode: Preferred AVD 'Myavd2' is available on emulator 'emulator-5554'
[2014-12-15 23:05:54 - MyApp] Uploading MyApp.apk onto device 'emulator-5554'
[2014-12-15 23:05:56 - MyApp] Installing MyApp.apk...
[2014-12-15 23:06:05 - MyApp] Installation error: Unknown failure
[2014-12-15 23:06:05 - MyApp] Please check logcat output for more details.
[2014-12-15 23:06:06 - MyApp] Launch canceled!
Below is the screenshot of the AVD:
Below is the screenshot of the SDK manager:
Could someone guide me on this issue?
You have selected the Nexus-5 phone resolution for the emulator with Android-TV system-image.
So, you need to select the corresponding resolution for Android TV in Device.
Also, select the dynamic-hardware-control in Skin.

New android developer, need help getting emulator to run HelloWorld

I just got the bignerdranch android book, and already, I cant get my emulator to work. This is not exclusive to Big Nerd Ranch, since even the default hellworld wont run... I get the following in my console box.
[2013-12-18 13:17:40 - HelloWorld] ------------------------------
[2013-12-18 13:17:40 - HelloWorld] Android Launch!
[2013-12-18 13:17:40 - HelloWorld] adb is running normally.
[2013-12-18 13:17:40 - HelloWorld] Performing com.example.helloworld.HelloActivity activity launch
[2013-12-18 13:17:40 - HelloWorld] Automatic Target Mode: launching new emulator with compatible AVD
'Nexus_API_17'
[2013-12-18 13:17:40 - HelloWorld] Launching a new emulator with Virtual Device 'Nexus_API_17'
[2013-12-18 13:17:56 - Emulator] creating window 0 0 577 1025
[2013-12-18 13:17:56 - Emulator] eglMakeCurrent failed
[2013-12-18 13:18:23 - Emulator] eglMakeCurrent failed
[2013-12-18 13:18:23 - Emulator] FrameBuffer::post eglMakeCurrent failed
[2013-12-18 13:18:24 - Emulator] eglMakeCurrent failed
[2013-12-18 13:18:24 - Emulator] FrameBuffer::post eglMakeCurrent failed
I have tried redownloading eclipse, I have tried both 32 and 64 bit versions. I have tried making the emulator different rams, different phones, different sdk versions. I have tried running as admin as well. I am out of ideas on what I can do.
PS: I have also scoured the web looking for solutions, and did just try the end ADB task, then relaunch eclipse and try again.. no success
Please checkout how much ram size you define for emulator; it should be greater than or equal to 256MiB. You can also verify this in the logcat files.
FIXED IT! So the way I got it to work for me, and this is simply so that other people can read this in the future if they have the same issue, is:
1) I had to switch to 32bit instead of 64.
2) I had to run the emulator (which still throws errors), and wait for it to load fully.
3) After it loaded fully, I then run the emulator a second time while the first is still opened.
4) I get the following errors:
[2013-12-19 15:20:35 - Emulator] WARNING: Data partition already in use. Changes will
not persist!
[2012-09-02 15:20:35 - Emulator] WARNING: Cache partition already in use. Changes will
not persist!
followed by:
[2013-12-19 15:21:46 - HelloWorld] New emulator found: emulator-5554
[2013-12-19 15:21:46 - HelloWorld] Waiting for HOME ('android.process.acore') to be
launched...
5) Then you close the first emulator and the new one opens and runs the app...

Emulator doesn't show itself

I was using android API 10 2.3.3 for making my application before. It was working fine. Then i converted my code to API 7 2.2.1. Now whenever i try to run the code, the virtual emulator doesn't show itself. Any ideas why this is happening?
[2012-02-29 08:57:38 - MyApp] ------------------------------
[2012-02-29 08:57:38 - MyApp] Android Launch!
[2012-02-29 08:57:38 - MyApp] adb is running normally.
[2012-02-29 08:57:38 - MyApp] Performing com.kahaf.MyApp.MyAppActivity activity launch
[2012-02-29 08:57:38 - MyApp] Automatic Target Mode: using device 'TA18801WF4'
[2012-02-29 08:57:38 - MyApp] Uploading MyApp.apk onto device 'TA18801WF4'
[2012-02-29 08:57:39 - MyApp] Installing MyApp.apk...
[2012-02-29 08:58:25 - MyApp] Success!
[2012-02-29 08:58:26 - MyApp] Starting activity com.kahaf.MyApp.MyAppActivity on device TA18801WF4
[2012-02-29 08:58:30 - MyApp] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.kahaf.MyApp/.MyAppActivity }
[2012-02-29 08:58:31 - MyApp] Attempting to connect debugger to 'com.kahaf.MyApp' on port 8622
i have tried connecting my droid too but it won't show anything either.
As per the Console info you have posted.. Looks like the app is being installed on the device rather than emulator..
As a suggestion, Go to Run Configuration and set the target as manual and then try selecting the emulator from the list.
Remove your device and run again. if that is not working try restarting eclipse.

Cant get helloWorld Loaded on AVD

My Helloworld tutorial sample builds and runs just fine, except it doesn't show the text (i.e. loads apps). The only thing I see is that Emulator (Target 2.2 API level 8) comes up with just the "Android" in it. and then the emulator shows up a locked up screen in a while. Here is output from the console
[2010-09-20 10:36:55 - HelloAndroid] Android Launch!
[2010-09-20 10:36:55 - HelloAndroid] adb is running normally.
[2010-09-20 10:36:55 - HelloAndroid] Performing com.example.HelloAndroid.HelloAndroid activity launch
[2010-09-20 10:36:55 - HelloAndroid] Automatic Target Mode: Preferred AVD 'my_avd' is not available. Launching new emulator.
[2010-09-20 10:37:56 - HelloAndroid] WARNING: Application does not specify an API level requirement!
[2010-09-20 10:37:56 - HelloAndroid] Device API version is 8 (Android 2.2)
[2010-09-20 10:37:56 - HelloAndroid] HOME is up on device 'emulator-5554'
[2010-09-20 10:38:23 - HelloAndroid] Uploading HelloAndroid.apk onto device 'emulator-5554'
[2010-09-20 10:38:27 - HelloAndroid] Installing HelloAndroid.apk...
After I exit the emulator, I get the following errors.
[2010-09-20 09:02:24 - DeviceMonitor]Sending jdwp tracking request failed!
[2010-09-20 09:38:46 - ddms]null
java.lang.NullPointerException
at com.android.ddmlib.JdwpPacket.writeAndConsume(Jdwp Packet.java:213)
at com.android.ddmlib.Client.sendAndConsume(Client.ja va:573)
at com.android.ddmlib.HandleHello.sendHELO(HandleHell o.java:142)
at com.android.ddmlib.HandleHello.sendHelloCommands(H andleHello.java:65)
at com.android.ddmlib.Client.getJdwpPacket(Client.jav a:670)
at com.android.ddmlib.MonitorThread.processClientActi vity(MonitorThread.java:317)
at com.android.ddmlib.MonitorThread.run(MonitorThread .java:263)
[2010-09-20 09:38:47 - ddms]null
java.lang.NullPointerException
at com.android.ddmlib.JdwpPacket.writeAndConsume(Jdwp Packet.java:213)
at com.android.ddmlib.Client.sendAndConsume(Client.ja va:573)
at com.android.ddmlib.HandleHello.sendHELO(HandleHell o.java:142)
at com.android.ddmlib.HandleHello.sendHelloCommands(H andleHello.java:65)
at com.android.ddmlib.Client.getJdwpPacket(Client.jav a:670)
at com.android.ddmlib.MonitorThread.processClientActi vity(MonitorThread.java:317)
at com.android.ddmlib.MonitorThread.run(MonitorThread .java:263)
[2010-09-20 09:50:11 - DeviceMonitor]Sending jdwp tracking request failed!
[2010-09-20 09:59:29 - DeviceMonitor]Sending jdwp tracking request failed!
[2010-09-20 09:59:31 - Logcat]device not found
com.android.ddmlib.AdbCommandRejectedException: device not found
at com.android.ddmlib.AdbHelper.setDevice(AdbHelper.j ava:736)
at com.android.ddmlib.AdbHelper.executeRemoteCommand( AdbHelper.java:373)
at com.android.ddmlib.Device.executeShellCommand(Devi ce.java:285)
at com.android.ddmuilib.logcat.LogPanel$3.run(LogPane l.java:516)
[2010-09-20 10:40:46 - DeviceMonitor]Sending jdwp tracking request failed!
Also, is there a way to capture the TEXT from CMD window that runs while the Emulator is coming up?
Simply press on the Menu button in the emulator.
Here is what your console has to say,by any means your eclipse is unable to add the minimum sdkversion to your manifest
WARNING: Application does not specify an API level requirement!
just add the following code to your manifest file and check whether it works or not,also close any open xml file prior to running your application
<uses-sdk android:minSdkVersion="8" />
give it a try and say what happens

Can't deploy Android/Google Maps app from eclipse

I'm an android newbie having a lot of troubles with the android emulator. I have inconsistent luck in starting up the emulator, and no luck if I start it from within eclipse instead of from the commandline (it waits forever and never boots -- not even after 24 hours).
However, since I figured out how to get it to (sometimes!) start from the command line, I have a workaround to that particular problem. But I have no workaround for my latest problem. When I try to run it:
[2010-08-09 22:08:12 - MyApp] ------------------------------
[2010-08-09 22:08:12 - MyApp] Android Launch!
[2010-08-09 22:08:12 - MyApp] adb is running normally.
[2010-08-09 22:08:12 - MyApp] Performing com.android.MyApp.MyApp activity launch
[2010-08-09 22:08:12 - MyApp] Automatic Target Mode: using existing emulator 'emulator-5554' running compatible AVD 'TestDroid'
[2010-08-09 22:08:12 - MyApp] WARNING: Application does not specify an API level requirement!
[2010-08-09 22:08:12 - MyApp] Device API version is 8 (Android 2.2)
[2010-08-09 22:08:14 - MyApp] Uploading MyApp.apk onto device 'emulator-5554'
[2010-08-09 22:08:14 - MyApp] Installing MyApp.apk...
[2010-08-09 22:08:15 - MyApp] Success!
[2010-08-09 22:08:15 - MyApp] Starting activity com.android.MyApp.MyApp on device
But nothing starts on my android instance. MyApp doesn't even show up on the app list.
I assume I'm doing something wrong?
Try looking at the adb logcat output, it might show some errors. Also, does your app specify a launcher Activity?
I think I may have fixed this by (possibly) resolving my emulator startup bug.

Categories

Resources