I always get a Error message when launching "Android device Monitor".
There is no error when launching Android Studio, it's running without problems. The error is just thrown when launching Device Monitor.
I reinstalled JRE 64 bit (I tryed version 1.7 and 1.8) but the error is still there.
I use Windows 7 64 bit and Android Studio 1.1.0
My User Variable JAVA_HOME is H:#Install\Java\jdk1.7.0_75
What can I do? Thanks in advance!
Possible fix would be to increase the XX:MaxPermSize
http://www.javavids.com/video/how-to-increase-java-memory-fix.html
Also, seems to be similar to the following posts:
-XX:MaxPermSize with or without -XX:PermSize
to increase MaxPermSize memory in Java by command line
I know quite some time has passed since this question was posted. Just replying for helping other people. It's not JRE that you have to re-install. But JDK. In fact the Android Device Monitor is not part of the JRE.
I had same issue and fixed by installing the appropriate JDK for my system (x64).
Related
I have just migrate to Mint from windows. I installed android studio v4. As I want to start the emulator, I got into error.
I'll be thank of who can give me a hand.
Add 32-bit support:
https://blog.linuxmint.com/?p=2211
Make sure you install all the dependencies needed by Android Studio:
https://developer.android.com/studio/install
And libvrt for emulation:
https://ubuntu.com/server/docs/virtualization-libvirt
After that, it should work properly. These instructions are valid for Ubuntu, but I think you can find similar packages for Linux Mint. Make sure you install the 32-bit packages (a_package:i386) when the links above require it. If it still doesn't work, try running Android Studio and the emulator from the command line (to see what goes wrong) and send a bug report to the Android Studio team.
My friends help me. He sayed it was due to GPU. He changed the Graphic card.
Not be able to launch emulator in Android Studio.
I have updated my SDK some days ago.
Here is my current SDK details.
My current system is Ubuntu 12.04 LTS with 32 Bit.
I am having Android Studio v1.3.2.
My problem is when I try to launch any AVD from Android Studio I get following error.
I am not able to find out what is the problem ! For your reference I can able to run the Application on real device.
The problem is only related to emulator.
Any help will be appreciated.
Please help me if anyone knows about this i am still facing same problem. Not be able to solve it anyhow.I have tried some of the solutions of SO but it didn't solved for me.
It's because of Linux 32 bit os. I solved this issue replacing old platform tool instead of updated.
following steps you need to perform:
1) download and take old platform tool
2) remove existing platform tool.
3) add old platform tool
4) restart android studio.
now it work fine and you can open emulator without error.
Also if you replace os to 64bit then good for future updates.
Its is because the android emulator doesn't like linux 32 bits. try to create a new Os 64bits.
I’m using MacBookPro OSX YOSEMITE 10.10.3
Till yesterday I was a happy Android Studio user with no complaints. But,
since yesterday Android Studio is making unintelligible trouble.
1. It’s not possible to start SDK Manager.
Every time I try to start it from Tools > Android > SDK Manager this happens:
2. The next issue comes with Gradle.
Every time I run my app this pops up:
My JAVA_HOME is:
$JAVA_HOME
-bash: /Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home:
I’ve reinstalled the Android Studio and JRE, Java SDK and Android SDK several times. Nothing changed. Getting same alerts as you see on the pictures.
I’ve also tried this solution with no success.
Do you have any Idea how to fix this problem!?
You can try to install 'Java SE Development Kit 8' to fix this problem. I think it will become normal after that
The reason was, that (my) OSX Yosemite doesn't work with Java 8 für Mac OS X from java.com. I've installed the JRE8 many times, but it was still not working. Here is how to solve that problem:
Like Tram Nguyen said, Open Terminal and type
java -version
if there is no responde like
java version "1.8.0_45"
get Java for OS X 2014-001 from >> Apple !
The Apple version will work on Yosemite.
Try again
java -version
If there is a responde, well done!
Thanks to Tram Nguyen for helping out.
I have read many of the posts for logcat not displaying in Eclipse and so far nothing has solved my problem. I have two installs. Logcat in Eclipse installed on my windows laptop works, but on my Linux Mint laptop those same programs will not display in logcat and not just with my log command in the program, but nothing shows - not even a trace.
The command line options of using adb logcat shows the logs just fine. It just won't show in the logcat window in Eclipse.
I have made sure the emulator is selected on the device tab, I have reset adb, I have restarted eclipse,Under I made sure "Monitor logcat for messages from applications in workspace" was checked and selected "VERBOSE".
I don't have any filters set.
Any ideas on what to try next?
I have had other problems with this linux installation that I had to fix. For instance, the default Google Eclipse/Plugin Bundle had some bugs. Some of which were solved with a new version of Eclipse and some were solved with a new version of ADT.The version of ADT also had a bug that would not let you upgrade it through Eclipse. So, I removed that bundle install and re-installed everything manually:Eclipse 4.4, then installed the 4.4 plugin and the various build tools and API levels and extras I needed. That solved some of those bugs.
That left the logcat issue and one major bug. Eclipse would freeze-up when the android auto-complete pop-up would display. On a hunch, I decided to run Android-Studio to see if it had any freeze-ups. When I started Studio, it warned me that I was using OpenJDK and it has known GUI performance problems and hangs. It gave a message that it recommended that I install the offical Oracle JDK, which I then did. That solved freeze-ups and hangs on Eclipse with the Android auto complete popups.
Now just this one problem left to solve - on my Linux environment, making logcat within Eclipse wok. Any suggestions are appreciated.
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.