I am working with Eclipse and running my apps on my phone(Motorola DROID2 GLOBAL, Android 2.2). Once I install a new project the previous one will disappear. Any ideas? Is this Eclipse problem or the phone?
Is a normal behavior of the Android development enviroment, it remove the application that you're debugging to upload the new one (new version).
It is like when you update an application with the Market, the old one will dissapear.
The problem was related to the operating system. Once I got upgrade pushed on my phone I stopped having this issue. Now it's all works just fine and can see all my apps available.
Related
i'm trying to install my app debug from my android studio. it's work well yesterday, but today when i try to install it again, the application cant be installed on my device and showing error like below on my android studio.
Installation did not succeed.
The application could not be installed: SHELL_UNRESPONSIVE
The device timed out while trying to install the application.
Retry
what should i do? i tried install on other device, and it worked fine. My device is Redmi 4X and other device is Samsung J3
Faced the same issue, not sure of the reason but in Android studio, Click on the File -> Invalidate Caches/ Restart and then it starts to work.
I got same issue with my device. i restart my device and its work properly.
The problem is because you don't have the proper SDK for the Android version. I'm telling you because a month has passed for me too. The solution is to download the appropriate pack in the SDK Manager.
If you have doubts how to enter:
Close the project.
In the welcome panel click on settings, then choose the SDK Manager option.
Click show package details and select the version for Android and choose all packages.
Finally you click ok XD
Try this method if it works perfect greetings
If other answers didn't help and previously application was installing correctly on your device, try to check your AndroidManifest file. Check that nothing forbids to install your app because of os version conflict or manifest merging errors or other reasons.
I came across this problem recently, through process of elimination I determined the cause was related to dependencies in the build.gradle(your app name).
I suggest working backwards and comment out everything that was added since the last known working build/install.
In my case I have a legacy app developed back in 2016 being rewritten, dependencies for signalR have changed quite a bit since then, the original libs where causing the install to fail while everything else seemed excellent, not even a single build error was occurring. Commenting out the libs and references got the application to a runnable state.
In my case, I deleted the emulator and recreated it. It solved the issue.
Before this, I had already tried following which did not work for me:
From menu: File->Invalidate cache/restart.
Deleting .cxx, .idea, .gradle, build folders and rebuilding.
Cold boot device emulator
Posting this in case someone is trapped in my kind of situation.
After updating my Android Studio to version 2.2.1 I can't get my app to display anything except black on the screen of my phone. Before updating it used to work. The app uses OpenGL ES 2.0. It works on an emulator but not on the real device. The app is running, it plays sounds as I touch on the screen, it's just not displaying anything. My phone is Huawei Honor 7.
I've tried everything I can think of such as restarting the phone, deleting the app from the phone, cleaning the project multiple times, manually deleting all the build directories and .iml files, disabling the instant run, building with different gradle versions, testing previous revisions of the app, switching between debug and release builds etc.
What could be causing this?
I still don't know what caused this, but what I did to get it working was that I deleted my previous project from Android Studio and made a completely new project with all the new project files stuff that Android Studio created for me, including CMake stuff that didn't exist before, and then copied all the relevant content to it from the previous project. Took one whole day but now at least it works. A lesson learned: Don't update your Android Studio if you're not prepared to spend some time fixing issues. I wish the Android Studio guys had hard of a concept called backwards compatibility...
I had my project running. And testing it on mobile device by clicking on the run button. But suddenly it has stopped working. Whenever i click on run button (run configuration is selected) it opens the dialog to choose the device but afterwards it does nothing.
Please help me with this problem. Since it has wasted my whole time.
I had the same issue. Studio project was working fine. After updateding the gradle plugin, it started showing the same issue.
Updating the Android studio to latest version only solved the problem. Looks like compatibility issue
#ShoaibAnwar Firstly Android Studio 2.0 has a security risk. http://www.androidcentral.com/google-advises-developers-upgrade-android-studio-211-over-security-concerns
You should upgrade to the latest dev release (2.1.1) in the dev channel or if you are not in a hurry, the latest stable 1.5.2. in the stable channel. (Perhaps in the future, 1.5.2 will be available in the dev channel) The run button in 2.0 won't work, instant run will not always deploy changes.
Secondly I would not mix TV and mobile modules. It is advised to separate android TV and wear modules from mobile and tablet modules. Just create 2 separate apks.
Any way to make common APK for API-15+ on mobile and API-21+ on TV?
http://tools.android.com/download/studio/builds/1-5-2/
I am using Android Studio-1.0.1 with Genymotion virtual device emulator for app development.Of late,studio has started behaving erratically.
Whenever I make some changes in the layout or the java class files and deploy the application,it does not reflect the changes that I made.
I already tried to:
1.make/clean/build app
2.Uninstalled the app several times from the emulato
3.cleared genymotion cache,invalidated studio cache,and even deleted the build folder of my app to remove old builds,
but it still does not help.
Is there anything else that I can do to solve this problem,and what is its possible cause in the first place?
I created four or five little test Android apps in Dreamweaver CS6 using PhoneGap Build. Each time, the current app would run in the emulator. Now, instead of running the project in the current site, the emulator64-arm keeps running a previous project when I click the PhoneGap Build icon on the Android emulator home screen. I have tried deleting all my projects from build.phonegap.com, and deleting all but the most recent project from the local drive. Even so, the emulator runs the old project -- which as far as I know, doesn't even exist anymore, either locally or on build.phonegap.com! Do I need to delete the project from the emulator? If so, how would I do that? Any help will be greatly appreciated, cause I'm stumped!
Mac OS X 10.6.8
Mystery solved. The first few times I installed apps on the emulator, I clicked the PhoneGap Build icon to run them. But later appps installed under different names -- I guess based on info I entered into the config.xml file.
Still would be nice to know how to delete those apps from the emulator. But at least the really mysterious part is explained -- why it ran a different app from the one I just built. I was just clicking on the wrong icon.