Develop Reference

Android Studio Cannot launch AVD in emulator. /opt/sdk/tools/emulator: Syntax error: word unexpected (expecting ")")

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.

OS X Yosemite - Android Stuio wont start SDK Manager and can't execute gradle

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.

Problems starting "Android device Monitor"

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).

Gradle gets stuck at either 'build' or 'assembleDebug' when using the 64bit or 32bit version of Android Studio

The issue I've had over the past few months is that Android Studio would often get stuck on Gradle: build, as seen here. Android Studio itself would stay responsive but the build simply wouldn't progress. It also never generates any kind of error, so I can't really post any useful information. Once in a blue moon it might suddenly work, but nothing reliable.
Recently I found a post here on Stack Overflow where someone's Android Studio would get stuck on Gradle: build when he tried to create a new project, and he noticed that this issue didn't exist in the 32-bit version of Android. So I thought, why not try that. Turns out that building isn't an issue anymore, but assembleDebug is, when trying to build the application. As can be seen here.
Of course all these commands work flawlessly when run using command prompt and gradlew.
What I've tried so far:
Reinstalling Android Studio (including the removal of .AndroidStudioProject)
Upgrading Android Studio to the latest version
Removing any build files from projects
Creating completely new projects in Android Studio
Switching from 64-bit to 32-bit Android Studio
I'm running the latest version of Android Studio, using version 19.1.0 of the build tools, gradle v0.11+ and am on Windows 8.1.
Is there anything else I can try? This is starting to become seriously annoying. The last possible solution I can come up with is just doing a complete format and a fresh Windows installation.

I was experiencing the same problem, and the solution was very unexpected in my case: AVAST antivirus was somehow interfering with the Gradle:build process.
Deactivating this antivirus solved the problem!

Because there is no answer to this problem I will share, what I have done, to solve this issue. From what I have seen, the problem is that there is a dependancy(or many) from a maven repo that can not be loaded. So you have to take all dependacy one by one and check if exist on the maven repo.
For example I was having a dependancy for "org.jraf:android-switch-backport:1.3.1" from "http://JRAF.org/static/maven/2" that at that time could not be opened.
My build.gradle looked like this:
repositories {
mavenCentral()
maven {
url "http://JRAF.org/static/maven/2"
}
}
compile "org.jraf:android-switch-backport:1.3.1

For me, this problem occurred when I was USB tethering using an Android device. The first build took anywhere from 5-10 minutes, and every subsequent build took about 3-7 seconds. I found that by disabling USB tethering, the first build completed quickly (and so would all subsequent builds). After the first build completed, I could reenable USB tethering.

If you have a fresh Ubuntu 14.04 with Android Studio 1.5, you may be missing a library. Try this:
sudo apt-get install lib32z1
Another stack overflow answer

It happens 1 in 2 times for me. The hack that works for me is File->Exit and confirm exiting. Then a message shows up telling me that Gradle is running and then all of a sudden the screen to choose the device shows up. I Click NO and all goes well again.
Anyway, still a bummer, but I have not found an answer yet.

My problem was that the Android Sdk executables were missing the executable bit. You can check some of your binaries like /Sdk/build-tools//aapt to see if they have permission to execute. If not you can solve it by running this on the Sdk folder
chmod -R +x ./

If you are behind a proxy on ubunthu you might need to set your gradle system wide proxy:
sudo nano ~/.gradle/gradle.properties
And enter the following entries:
systemProp.http.proxyHost=<Your Host>
systemProp.http.proxyPort=<Your Host Port>

Exporting APK from eclipse (ADT) silently crashes

Every time I try to export an APK from Eclipse (tried Juno and Indigo) on Mac, eclipse crashes after a few seconds
This used to work fine on my current setup.
Running the app straight (debug mode) on my phone works fine.
The error from the console is:
Invalid memory access of location 0x10073f113 rip=0x101f656f7
Bus error: 10
I'm using Mac OS X 10.7.4 on a ~2010 MacBook Pro, with the following java:
java version "1.6.0_33"
Java(TM) SE Runtime Environment (build 1.6.0_33-b03-424-11M3720)
Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03-424, mixed mode)
I'm using ADT 20.
I've tried reinstalling Eclipse and the Android SDK, and re-downloading ADT.
The Eclipse error view doesn't show anything
Any ideas of different methods I can try, or other ways to investigate what's going wrong?
Cheers
Update: For anyone coming along post-2014, you should be using Android Studio, which doesn't have this problem.

Disable Project/Build Automatically when you are exporting
I think is a problem of Eclipse unable to detect the Android command is still working or something similar.
Of course there is ever the option of APK generation using Ant outside Eclipse you can generate an Ant build.xml from your Eclipse project more info in official Android docs

Disable Project->Build Automatically. I've noted that this works for me.

Disable project/build Automatically before export the apk.

This seem to be problem with your JVM. Can you update your java and check again. Also check this link

project/ clean worked for me. I think it could be related to the building of the project, as other users have posted.

The problem has gone until I have update ADT and Eclipse. I don't know which one solve the issue.
Now it's working smoothly for severeal signed export, with:
ADT Version: 22.2.1.v201309180102-833290
Eclipse Juno Service Release 2 Build id: 20130225-0426
Gentoo Linux running Java 1.7.0_45-b18.
UPDATE: Few exports after, I still get crashes from time to time, but no very frequently.

may be you should try to add execute authority . you can try something like this
first close auto-build
cd /home/your name/android-dev/sdk/tools/
sudo chmod +x zipalign
done and good luck to you

I used the disable Build Automatically for months now, until I realized that AWS plugins were slowing down the entire launch process. I uninstalled all AWS plugins from Help->InstallationDetails and everything now works perfectly as before. I do not need to disable Build Automatically any more.