Android Studio not executes the IDE, it only shows the splash screen, after few seconds, it dissapears.
I tried the following solutions:
I uninstalled the program and installed again
I restarted my PC after installation
I added "JAVA_HOME" and "JDK_HOME" as environment variables
I checked if "studio.exe" process is executing, if IDE is executing in background.
I executed Android Studio as "Administrator"
I disabled Antivirus temporarily
I deleted ".android", ".AndroidStudio", ".gradle", ... folders
These solutions not worked.
Which is the problem with execution?
If you have done this:
do you have installed the JAVA SDK donwload the latest release from here!
be sure to have configured the JAVA_HOME and JDK_HOME in your environmet variables.
then check the .log file generated by Android Studio to get more information about your issue:
C:\Users[MyUser].AndroidStudio1.2\system\log\idea.log
I recently experienced this issue as well.
It was related to me having dual monitors and oddly the secondary screen was not able to load android studio.
In my setup the issue resolved itself once the secondary screen was made the primary screen ( I have an ATI graphic card 8300) with Android Studio 2.3 and Canary build 3.x
This is typicaly a low memory problem. I currently have the same and I was able to make few correlations. If you start your task manager, you will notice that "Disk" goes to ceiling when starting Android Studio. Actually, you will surely notice that it goes more often to 100% that you'd expect and Android Studio is just the perfect vector to observe this, since it consumes a lot of resources.
The annoying part of the answer is that this "Disk 100%" bug on windows 8.1 is really widespread and solutions doesn't seem that straightforward. For the record, if I find my cause (or if I'm all wrong in my hypothesis), I'll keep you posted.
Regards
Related
I just downloaded Android Studio and the simulator for some reason is zoomed in very far or has enormous text. I've tried everything on the right-hand bar to handle this and there are no menu bar options. How can I resolve this?
I was experiencing the same exact problem at first. After I had opened my project in Android Studio, the IDE installed a bunch of other libraries and tools; in turn priming the environment. To note, this was all after a fresh install of Android Studio. After the supplemental install, I then started the emulator from the AVD Manager from within the IDE. Afterwards, whenever I ran the emulator again I had experienced zero issues like this. I understand some of this sounds anecdotal but it seems that the Android Studio IDE helped sort this out for me at least.
I would also like to note that, if you experienced any warnings or errors when executing the simulator, it may also be an issue originating from the emulator's environment itself. Possibly tweaking some of the settings on the emulator could also help (i.e., memory/storage capacity).
I accidentally ran my Android Studio project on an emulator (for a different device) instead of my real device (forgotten I unplugged it), and the whole computer froze/ran out of memory. No big deal I thought, I turned off my computer and started it again.
However, now when I start Android Studio, I run into problems. It first says indexing for a very long time (like 10 minutes+), then it goes to Building symbols also for 10 minutes+, until it warns me about low memory and eventually runs out of memory.
The out-of-memory error window gave me the opportunity to increase the memory limit and I tried increase the memory field to 2000 (from 1200 something), and that is where I am now, still building symbols 20 minutes later.
Edit: Now it ran out of memory again.
Note that before, when I start Android Studio, everything was set up
within minutes
What should I do? Do I have to reinstall Android Studio? Should I change these memory settings to something else, or clean up Android Studio settings somehow?
What finally worked for me was downloading version 3.2 of Android Studio (if I download via Ubuntu Software it is version 3.3), installing to a different directory and reinstalling the sdk to a different directory. Not sure what part of that was the solution, but anyway, if anyway has the same problem they can try this.
Try going to File then Invalidate Caches / Restart
Try going to C:\users\.android\avd and remove all folders. If the issue is related to your emulators, deleting all folders might help.
Background
I'm trying to use Android Studio 3.3 Canary 8 (the latest Preview release). I'm running Ubuntu 18.04 LTS 64-bit, and if it's relevant, my desktop environment is KDE Plasma and my window manager is KWin.
Issue
It was working completely fine until a couple of days ago, when I began experiencing an unusual display bug which rendered the editor completely unusable for me.
Here are a couple of screenshots of what Studio looks like right now. The first one is the Tip of the Day window that pops up at startup, and the second one is the actual editor itself.
From what I can tell, it seems that all UI elements have been stretched vertically, or something along those lines.
Troubleshooting
I tried Googling around for my issue, but I'm not entirely sure what to even Google in the first place. I tried some variations of "Android Studio display bug" or "Android Studio UI vertically stretched", things along those lines, but most search results apply to Android applications and not the editor itself.
I suspect that there's an issue with Android Studio's DPI detection, but I have no way of fixing any issues there given the fact that I can't see any text anywhere.
Attempted Fixes
I tried redownloading Android Studio from their website and running that fresh install. No dice.
I tried completely removing any Android Studio configuration or cache folders and reinstalling. Nope.
I tried using the release candidate instead of the Canary build. That didn't work so I tried using the stable release (3.1.4), which didn't work either.
I tried rebooting my computer too, but the issue persists.
I can't think of anything on my computer that might have changed between the last time Android Studio worked fine and now. I do remember installing some system updates, but I'm not sure which ones specifically (if there's a way to find out what updates were installed for a given run of sudo apt upgrade, I can include that information in this post).
Bottom Line
I'm really at a loss, and this is a really frustrating issue. Any help would be greatly appreciated, and if this is the wrong place to ask I apologize. If there's any more information you might need to troubleshoot this, please let me know and I'll update this question.
The second I open up layout.xml file from a simple skeleton app in Eclipse example plugin, the cpu usage locks up to 25% IE. 1 full core. and it's been on like this for the last 30minutes I wanted to let him run a longer time because I thought it is working something in the background but it just keeps doing that.
I've tested this on 2computers so far and the setup is
install Android SDK,
install Eclipse IDE for Java Developers,
install ADT plugin: http://dl-ssl.google.com/android/eclipse/
open new project, select a skeleton project for Android 2.3.3
and just open the layout skeleton activity and perhaps change to android 2.3.3 in the upper right corner and maybe setup to theme.black.noTitleBar.Fullscreen.
And now your processor should be hitting 100% ( on one core ) and should be locked like that from now on.
Is there any solution to this issue, because at home I only have 1 core and I can not work on anything.
Does any one have any clue as to why this is happening ?
http://my.jetscreenshot.com/demo/20110517-gbr8-201kb
I'm seeing the same issue so I filed a bug report at http://code.google.com/p/android/issues/detail?id=18865.
The Android team have now released a fix and it works for me. You have to upgrade to the latest revision of each SDK module that you downloaded through the android tool. The latest version of the ADT also has a number of fixed for long-standing issues.
I can't answer "Why" this happens. But I can say what fixes it.
I encountered this on Ubuntu 12.04 64 bit. I had 100% cpu and eclipse hang when I switched to debug view - Eclipse was unusable and had to kill it. I found the below bug report
https://code.google.com/p/android/issues/detail?id=34641
Following the comments there, I tried
cd /usr/lib/x86_64-linux-gnu/gtk-2.0/modules
mv libgail.so libgail.so.moved
Eclipse did not hang (no 100% cpu) when I switched to debug view.
Start Eclipse with -Dcom.sun.management.jmxremote (put it into eclipse.ini or start eclipse.exe with this option).
When Eclipse runs, start jconsole and look at the thread dump to see which thread hogs the CPU. It's the one which isn't WAITING. File a bug report.
I had the same problem and it was resolved just by moving my workspace to C:/workspace instead of Win 7 Libraries.
The following situation will surely be familiar to any Android developer using Eclipse and ADT.
I'm tired of this endless cycle of switching Build Automatically on and off, running Clean, building and running. I'm constantly doing all of these operations when I'm fine tuning UI (i.e., editing XML files and needing to see the results live), and any time I save, an Eclipse window telling me I have these pending operations shows up. When that happens, I turn off Build Automatically. I do my alterations and then run. Sometimes Eclipse decides the changes in the XML file weren't enough, and it won't reinstall the app in the emulator or device, so I force a build and install.
All of this is just wasted time. I've already done an AppleScript to build & run my app into all the emulators and devices I have connected at once, described in this SO question, but my workflow could be much improved if I found a way to save and build silently and fast.
Does anyone have any tips or alternatives?
IntelliJIdea Community Edition now supports Android
Have you tried the bundle for Textmate? It's pretty cool. It's basic but its got all the features you need. Building, Deployment and integration with AVD and Logcat.
I use this for all my Android Dev now as I found Eclipse painfully slow.