Geek Answers Handbook

The application will not start on the device

I am an app developer for Java, Eclipse, and Android. I am going through an Android app , but it seems I cannot get the first lesson to run on my device. After fixing several problems that prevented the compilation of the project, I was able to run it on AVD. But no luck on the physical device. Below is information about my environment and what the console shows.

On the phone, I tried to find the installation in applications, downloads and on the desktop, but I do not see them.

Computer: Windows XP

Device: Samsung Galaxy Nexus works 4.1, core 3.036-04142-gfa7dc12-dirty

Dev Env: Eclipse Juno

Console:

[2012-07-10 13:35:11 - MyFirstProject] ------------------------------ [2012-07-10 13:35:11 - MyFirstProject] Android Launch! [2012-07-10 13:35:11 - MyFirstProject] adb is running normally. [2012-07-10 13:35:11 - MyFirstProject] Performing com.example.myfirstapp.MainActivity activity launch [2012-07-10 13:35:14 - MyFirstProject] Uploading MyFirstProject.apk onto device '014994321500300C' [2012-07-10 13:35:14 - MyFirstProject] Installing MyFirstProject.apk... [2012-07-10 13:35:14 - MyFirstProject] Success! [2012-07-10 13:35:14 - MyFirstProject] Starting activity com.example.myfirstapp.MainActivity on device 014994321500300C

Thanks for the quick answers.

My phone appears in Eclipse when debugging. I specifically did not install the Samsung driver on the machine on which I am doing this. Checking Device Manager I saw that the phone was not correctly recognized by Windows. Since then I installed the driver and now I can perform actions by phone at the command line (for example, rebooting adb).

After installing the driver, I rebooted my computer and phone. Unfortunately, the default intention is still not loading on the phone, as when using AVD. I would be happy with AVD, but on my computer it’s pretty slow and it’s just cooler to hold it in your hands (this is more real). :)

+4
source share
4 answers

For Google Nexus devices, you should download the Google USB driver from here: http://developer.android.com/sdk/win-usb.html After installing this (from the sdk android manager), just restart eclipse and it should recognize and install apk on your physical device.

+1
source

Check out the DDMS prospects for eclipse ADT if your device is listed or use the adb devices command to verify this from the console. From the logs it seems that the device is correctly installed, so most likely this is not a problem.

In the debugging perspective, go to the settings and select the break on exception option and run the application in debug mode. This link shows how to configure eclipse:

Break when an exception is thrown

Then you can check the error with which your application stops working. An alternative is to check logcat for errors.

0
source

I think your problem is with the configuration with the ADT plugins, and also you need to install the appropriate version of the SDK. Be specific to select the emulator version according to your application.

take the new version of eclipse and SDK from below link

http://developer.android.com/sdk/index.html

take Android 4.2 API

http://developer.android.com/about/versions/android-4.2.html

0
source

Other answers here are incorrect, and flat ones do not help. I was in this exact situation, and she was always called up because of a stupid mistake. Check your manifest! If your manifest is empty, or there is no application or launch activity, Android will not have any hints on how to start your activity and, therefore, the start icon will not be displayed!

Unfortunately, there is no stack trace, and your application will appear as installed in the application manager.

I ran into this problem when configuring gradle configurations. I accidentally did not load in my manifest, which I use to merge with an empty manifest.

0
source

More articles:


All Articles