app can't install after update eclipse? - java

I've build android application using eclipse, everything work well when i change my code and run on emulator before i update my eclipse,after my eclipse update, i change my code, my app didn't install new code but still running previous code and show log like this.
[2013-11-25 10:27:07 - ChatKrawala] Application already deployed. No need to reinstall.
[2013-11-25 10:27:07 - ChatKrawala] Starting activity com.ltvie.chatkrawala.ChatkraActivity on device S5830ae0c94c8
[2013-11-25 10:27:07 - ChatKrawala] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.ltvie.chatkrawala/.ChatkraActivity }
why my eclipse cant install new app when i change my code after i update my eclipse and ADT?

Related

Instant run does not work

I'm getting this issue in android studio 2.3 when I click on run:
03/09 19:02:36: Launching app
$ adb shell am startservice
com.a890m.s/com.android.tools.fd.runtime.InstantRunService
Error while executing: am startservice com.a890m.s/com.android.tools.fd.runtime.InstantRunService
Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.a890m.s/com.android.tools.fd.runtime.InstantRunService }
Error: Not found; no service started.
This issue is only in Android Studio 2.3 which is still open in google issue Tracker
You can resolve it (for time being not a permeant solution because Instant run is needed) by disabling instant run in your android studio.
goto-> Android Studio -> Preferences -> Build, Execution, Deployment -> Instant Run
I get this error before and the solution that works for me is to Try unplug and plug the cable again and see if it works
This is happening for some specific devices because some manufacturers have customized their devices and added some sort of "auto-start" blocker. For affected Asus devices, for example, you can fix this issue by enabling Auto-start for your app with Asus's Auto-start Manager. See this page for details: https://www.asus.com/support/faq/1013752
But different manufacturer seems to do this differently. For example, for LeEco devices, you can allow "auto-launch" under settings. See this issue (https://github.com/openstf/stf/issues/407#issuecomment-247852532) for info on how to enable auto-launch for your app.
You can Google how to turn off such autostart/autolaunch feature for your specific device to get Instant Run to work. You can also just use the emulator.
Hope that helps.

How do I debug my Android app on Samsung

I am trying to debug my first app. I have a Samsung Galaxy S3 with Android Jelly Bean (I'm a Windows user) and I have installed the latest version of Kies and have installed all required drivers for my device.
Following the steps to debug in the Android Getting Started tutorial, I have not been able to successfully debug my app on my phone or in an emulator.
Actually I don't really care fo the emulator at this point since this app is just a hello world app. I need to see it on my device but I can't and I don't know what I'm doing wrong, if anythin.
When I hit the debug button in Android Studio, and select my Device as the device to debug on from the popup dialog, Android Studio then displays the following error:
Installing myapplication
DEVICE SHELL COMMAND: pm install -r
"/data/local/tmp/myapplication"
pkg: /data/local/tmp/myapplication
Failure [INSTALL_FAILED_INVALID_APK]
I have searched this error but all the solutionts I have seen are telling me to do things I've already done!
How can I debug an app on Samsung GS3 using Android Studio?
Whats your package name ?
You must have one "." at least

What does this error mean when building and Android project?

I am developing an Android application in Eclipse but it shows the following in my console when I clean, build and debug it:
[2013-06-05 09:05:37 - TSRAndroidSystem] ------------------------------
[2013-06-05 09:05:37 - TSRAndroidSystem] Android Launch!
[2013-06-05 09:05:37 - TSRAndroidSystem] adb is running normally.
[2013-06-05 09:05:37 - TSRAndroidSystem] Performing com.lk.lankabell.android.activity.LoginPage activity launch
[2013-06-05 09:05:37 - TSRAndroidSystem] Automatic Target Mode: launching new emulator with compatible AVD 'test'
[2013-06-05 09:05:37 - TSRAndroidSystem] Launching a new emulator with Virtual Device 'test'
[2013-06-05 09:05:49 - Emulator] Failed to create Context 0x3005
[2013-06-05 09:05:49 - Emulator] emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.
[2013-06-05 09:05:51 - TSRAndroidSystem] New emulator found: emulator-5554
[2013-06-05 09:05:51 - TSRAndroidSystem] Waiting for HOME ('android.process.acore') to be launched...
[2013-06-05 09:06:42 - TSRAndroidSystem] HOME is up on device 'emulator-5554'
[2013-06-05 09:06:42 - TSRAndroidSystem] Uploading TSRAndroidSystem.apk onto device 'emulator-5554'
[2013-06-05 09:06:44 - TSRAndroidSystem] Installing TSRAndroidSystem.apk...
[2013-06-05 09:07:13 - TSRAndroidSystem] Re-installation failed due to different application signatures.
[2013-06-05 09:07:13 - TSRAndroidSystem] You must perform a full uninstall of the application. WARNING: This will remove the application data!
[2013-06-05 09:07:13 - TSRAndroidSystem] Please execute 'adb uninstall com.lk.lankabell.android.activity' in a shell.
[2013-06-05 09:07:13 - TSRAndroidSystem] Launch canceled!
My emulator is running though.
Is it an error, a warning or is it saying that I have to unlock my android emulator screen?
Actually this Scenario was oocured for me many times when i use phone for testing my application
This is because you had installed TSRAndroidSystem alredy in your phone .Te error occur because the app that installed in your phone uses differnt debug keystore that present in your system .
But in your case it happened in emulator . It's really wiered to me .
Did you directly insatlled the TSRAndroidSystem.apk developed in another system in your emulator ??
Any way i thing by un-installing the alredy installed app from your Emulator . Then run your project so that the app will be signed with debug keystore of your system hope this will sove your issue
This normally happens when you develop on multiple computers.
When you install an application from Eclipse it uses your debug keystore to sign the application. Different computers have different debug keystores (they are just generated automatically), so you have to fully remove the app from your device before installing it again.
Not sure why this would happen on the emulator, but just fully remove the app from the emulator and it should work.
It means you need to uninstall the app from the device that you had previously installed the last time you launched it.
That error usually occurs when you have another application with the same package name installed on the device. In your case com.lk.lankabell.android.
It can also happen when you develop on multiple computers which means different debug keys in which case the application with the same package is the one you try to install. But since you are using an emulator this cannot be the case.
In either case: go to Settings > Apps on your emulator or phone and uninstall the app with that particular package name and try again. And always make sure to choose unique package names to prevent this from happening.

Error:emulator-5554 disconnected: [duplicate]

This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
Why do I get a emulator-5554 disconnected message
i run mine application in eclipse and the following results found in console
[2011-09-27 12:47:58 - AndroidBlackjack] Android Launch!
[2011-09-27 12:47:58 - AndroidBlackjack] adb is running normally.
[2011-09-27 12:47:58 - AndroidBlackjack] Performing com.android.blackjack.Setup activity launch
[2011-09-27 12:47:58 - AndroidBlackjack] Automatic Target Mode: Preferred AVD 'yahoo' is not available. Launching new emulator.
[2011-09-27 12:47:58 - AndroidBlackjack] Launching a new emulator with Virtual Device 'yahoo'
[2011-09-27 12:49:52 - AndroidBlackjack] New emulator found: emulator-5554
[2011-09-27 12:49:52 - AndroidBlackjack] Waiting for HOME ('android.process.acore') to be launched...
[2011-09-27 12:51:12 - AndroidBlackjack] emulator-5554 disconnected! Cancelling 'com.android.blackjack.Setup activity launch'!
please help me
i do not understand this.
Solution (Eclipse IDE)
Select & Right Click on Android Project
Run Configurations
Go to tab Target
Enable option Wipe User Data on Emulator launch parameters
Run Application
If you are using other IDE, you can restart your emulator using -wipe-data flag to delete all the temporary files that the emulator created in previous runs.
the cancellation occurs because of three reasons:
i had not clean the project
emulator => project => clean
i had written the .main in small letters in manifest.xml by mistake
i had not removed windows firewall settings of window
The problem as I discovered lays in the fact the the project has no appropriate Virtual Device defined for it in the AVD manager.
So the recommended steps in eclipse are:
Go to "Project"-> Properties-> Android.
On the right pane see what line is checked in the Project build target.
Remember the target platform number that appears in the selected line.
Go to "Windows"-> AVD Manager.
Check the list of existing Android Virtual Devices for a device that matches the Platform and API level that you have set for your project (see step #2 above).
If there is no line that includes an AVD for your platform (as I suspect), add it using the "New" button.
A "Create New Android Virtual Device" window will be opened. set a new device name. in the "Target" selection box choose the right platform for your project.
Enjoy your emulator once again!

runtime error in android devices

I have created an app and it runs successfully in the emulator. When I was trying to run it in any of my devices it shows the following error:
[2011-02-12 09:57:06 - FirstImage] Android Launch!
[2011-02-12 09:57:06 - FirstImage] adb is running normally.
[2011-02-12 09:57:06 - FirstImage] Performing com.gis.image.FirstImage activity launch
[2011-02-12 09:57:23 - FirstImage] Uploading FirstImage.apk onto device 'HT96WKF01291'
[2011-02-12 09:57:32 - FirstImage] Installing FirstImage.apk...
[2011-02-12 09:57:52 - FirstImage] Re-installation failed due to different application signatures.
[2011-02-12 09:57:52 - FirstImage] You must perform a full uninstall of the application. WARNING: This will remove the application data!
[2011-02-12 09:57:52 - FirstImage] Please execute 'adb uninstall com.gis.image' in a shell.
[2011-02-12 09:57:52 - FirstImage] Launch canceled!
What is the issue and how can I overcome it?
You have installed this .apk before, and it was compiled using a different signature (see here for details). To fix this you need to remove the previous installation (you have to do that only when the signature has changed - not normally).
On the device itself, go Menu->Settings->Manage Applications. Select the application which you want to Uninistall, and click on the ‘Uninstall’ button. Now try your install.
When you install the application directly from eclipse it is signed by a different certificate than the one you use when you create the application for market.
What is most likely happening is that you have the app installed with a different signature than the one you are trying to install now.
Some times this happens, when you keep on installing the app through your code then it sometimes gives such kind of error..To over come this Just Open a terminal And paste this
adb uninstall com.gis.image
This is according to your Above error log...
You Just need to Uninstall your app from the Device.. Just like it :)
Hope this Helps....

Categories

Resources