Develop Reference

Android-sdk emulator doesn't work

My platform: debian 8 (sid)
uname -a : Linux ... 3.2.0-4-686-pae #1 SMP Debian 3.2.78-1 i686 GNU/Linux
I downloaded android-sdk_r24.4.1-linux.tgz from https://developer.android.com/
but emulator(*) executables don't run because I get :
"bash: tools/emulator: cannot execute binary file: Exec format error. "
I guess this means these binaries can't run on my system. So does it mean , I can't run the emulator on my platform?
I didn't find source of emulator in tgz.
Or where can I find the source of emulator?
thanks

Hehe....
If I downloaded tgz file with wget (wget http://dl.google.com/android/android-sdk_r24.4.1-linux.tgz), binaries work!
I don't understand why.... ?.... :-|

Didn't work ! :(
This was very strange for me.
When I downloaded tgz and extracted, the binaries worked.
I run SDK manager and downloaded some packages for example : some System Images, Android 6.0 SDK platform, build tools, etc, and after this, binaries didn't work.
I figured it out, the case of problem was I updated current SDK tools. After update The binaries didn't work.

Exception in thread "png-cruncher_x" [duplicate]

I've installed Android Studio 1.2, and created a new project. When I attempt to build, it hangs. This is in the Gradle Console, along with about 20 other copies, with different numbers after png-cruncher_:
Exception in thread "png-cruncher_2" java.lang.RuntimeException: Timed out while waiting for slave aapt process, try setting environment variable SLAVE_AAPT_TIMEOUT to a value bigger than 5 seconds
at com.android.builder.png.AaptProcess.waitForReady(AaptProcess.java:104)
at com.android.builder.png.QueuedCruncher$1.creation(QueuedCruncher.java:107)
at com.android.builder.tasks.WorkQueue.run(WorkQueue.java:204)
at java.lang.Thread.run(Thread.java:745)

I had the same problem with Debian Jessie for AMD64. I did this, and it works:
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libncurses5:i386 libstdc++6:i386 zlib1g:i386

I had the same issue whilst running Android Studio 1.5.1 for Windows 8.1 (64 bit), and what I did to solve the problem was by adding the following two system environment variables:
SLAVE_AAPT_TIMEOUT = 30
JAVA_HOME = C:\Program Files\Java\jdk1.8.0_65
(Please note: The path for the JAVA_HOME system environment variable is dependant on where your JDK is located and that the version of your JDK may differ from the example above).

I had this problem on Windows 8.1 64 bits and what ended up solving everything was running gradle in the command line in debug mode, on the project folder:
gradlew -d assembleDebug
Running without the -d flag had the same problem.
After running the first time, everything was ok, I could even clean and rebuild my project.

I had this problem and what was missing were a library to be installed on the SDK.
Just installing the correct library immediately solved the problem.
In my case was the Android Support Library, as I was creating a navigation drawer.
The errors shown in the gradle console didn't give me a clue for the solution, and didn't helped me at all.
Click on SDK manager, and click on the tab SDK Tools, check "Android Support Library" and click apply.

This is a known bug reported here --> https://code.google.com/p/android/issues/detail?id=188627
The workaround on Mac is to reboot your computer.

If you are running on a Linux x64 machine you probably miss some required libraries. The offical sdk guide states:
Required libraries for 64-bit machines:
If you are running a 64-bit version of Ubuntu, you need to install some 32-bit libraries with the following command:
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386 lib32z1 lib32bz2-1.0
If you are running 64-bit Fedora, the command is:
sudo yum install zlib.i686 ncurses-libs.i686 bzip2-libs.i686
of course don't forget to
sudo apt-get update
first.

By pausing the antivirus I don't have anymore that problem, or better by making a rule at the antivirus in order to accept a given '.class' filename recognized as trojan, then banned at compile-time.

Check your firewall if it is coming in your way. Disabling my firewall works for me but i don't know if it's the right fix.

I had the same problem with CentOS 6.5. Before this error, I found the cause of the error, as follows.
AAPT err(Facade for 1129807373): xxx/aapt: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by xxx/lib64/libc++.so)
“libc.so.6: version `GLIBC_2.14' not found” . The highest version of CentOS 6.5 is 2.12, and we need to upgrade to 2.14.
Display the installed glibc version:
# rpm -qa | grep glibc
To download the corresponding RPM package. -> ftp.redsleeve.org/pub/steam/
Install the RPM package as follows:
# rpm -Uvh glibc-2.15-60.el6.x86_64.rpm glibc-common-2.15-60.el6.x86_64.rpm glibc-devel-2.15-60.el6.x86_64.rpm glibc-headers-2.15-60.el6.x86_64.rpm --nodeps --force

I uninstalled 1.2 and installed 1.1, but it did't work.
Because I used local SDK installed previously, I uninstalled and reinstalled 1.1 and installed SDK to new path.
After I used SDK in new path, I don't have those errors any more.
And I upgraded Android Studio to 1.2, and also I don't have errors.

Downgrading Build Tools rescued me.

Android Studio fails to build new project, timed out while wating for slave aapt process

I've installed Android Studio 1.2, and created a new project. When I attempt to build, it hangs. This is in the Gradle Console, along with about 20 other copies, with different numbers after png-cruncher_:
Exception in thread "png-cruncher_2" java.lang.RuntimeException: Timed out while waiting for slave aapt process, try setting environment variable SLAVE_AAPT_TIMEOUT to a value bigger than 5 seconds
at com.android.builder.png.AaptProcess.waitForReady(AaptProcess.java:104)
at com.android.builder.png.QueuedCruncher$1.creation(QueuedCruncher.java:107)
at com.android.builder.tasks.WorkQueue.run(WorkQueue.java:204)
at java.lang.Thread.run(Thread.java:745)

I had the same problem with Debian Jessie for AMD64. I did this, and it works:
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libncurses5:i386 libstdc++6:i386 zlib1g:i386

I had the same issue whilst running Android Studio 1.5.1 for Windows 8.1 (64 bit), and what I did to solve the problem was by adding the following two system environment variables:
SLAVE_AAPT_TIMEOUT = 30
JAVA_HOME = C:\Program Files\Java\jdk1.8.0_65
(Please note: The path for the JAVA_HOME system environment variable is dependant on where your JDK is located and that the version of your JDK may differ from the example above).

I had this problem on Windows 8.1 64 bits and what ended up solving everything was running gradle in the command line in debug mode, on the project folder:
gradlew -d assembleDebug
Running without the -d flag had the same problem.
After running the first time, everything was ok, I could even clean and rebuild my project.

I had this problem and what was missing were a library to be installed on the SDK.
Just installing the correct library immediately solved the problem.
In my case was the Android Support Library, as I was creating a navigation drawer.
The errors shown in the gradle console didn't give me a clue for the solution, and didn't helped me at all.
Click on SDK manager, and click on the tab SDK Tools, check "Android Support Library" and click apply.

This is a known bug reported here --> https://code.google.com/p/android/issues/detail?id=188627
The workaround on Mac is to reboot your computer.

If you are running on a Linux x64 machine you probably miss some required libraries. The offical sdk guide states:
Required libraries for 64-bit machines:
If you are running a 64-bit version of Ubuntu, you need to install some 32-bit libraries with the following command:
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386 lib32z1 lib32bz2-1.0
If you are running 64-bit Fedora, the command is:
sudo yum install zlib.i686 ncurses-libs.i686 bzip2-libs.i686
of course don't forget to
sudo apt-get update
first.

By pausing the antivirus I don't have anymore that problem, or better by making a rule at the antivirus in order to accept a given '.class' filename recognized as trojan, then banned at compile-time.

Check your firewall if it is coming in your way. Disabling my firewall works for me but i don't know if it's the right fix.

I had the same problem with CentOS 6.5. Before this error, I found the cause of the error, as follows.
AAPT err(Facade for 1129807373): xxx/aapt: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by xxx/lib64/libc++.so)
“libc.so.6: version `GLIBC_2.14' not found” . The highest version of CentOS 6.5 is 2.12, and we need to upgrade to 2.14.
Display the installed glibc version:
# rpm -qa | grep glibc
To download the corresponding RPM package. -> ftp.redsleeve.org/pub/steam/
Install the RPM package as follows:
# rpm -Uvh glibc-2.15-60.el6.x86_64.rpm glibc-common-2.15-60.el6.x86_64.rpm glibc-devel-2.15-60.el6.x86_64.rpm glibc-headers-2.15-60.el6.x86_64.rpm --nodeps --force

I uninstalled 1.2 and installed 1.1, but it did't work.
Because I used local SDK installed previously, I uninstalled and reinstalled 1.1 and installed SDK to new path.
After I used SDK in new path, I don't have those errors any more.
And I upgraded Android Studio to 1.2, and also I don't have errors.

Downgrading Build Tools rescued me.

Android Emulator not coming up on Ubuntu

I have Ubuntu 12.04 and the java 1.7.
The problem is that the emulator won't start whatever I try. I have also tried changing the java to Open Jdk 6 but that doesn't help either.

Renaming tools/lib/libOpenglRender.so to tools/lib/libOpenglRender.so.xxx has fixed the problem.

If you are running a 64-bit distribution on your development machine, you need to install the ia32-libs package using apt-get::
Download the package
apt-get install ia32-libs
http://developer.android.com/sdk/installing/index.html. Check the the link under TroubleShooting linux

Android SDK Issues Ubuntu 10.04lts

I have looked through the other questions on here, and on other forums. The answers didn't help my issue. I originally started out with 11.10 but thought there could be a bug or something that was stopping it from working. I have had the SDK and ADT working with Eclipse on both 10.04 and 11.10 so I really am at a loss as to what is going wrong.
The error I get is as follows:
Cannot complete the install because one or more required items could not be found.
Software being installed: Android Traceview 16.0.1.v201112150204-238534 (com.android.ide.eclipse.traceview.feature.group 16.0.1.v201112150204-238534)
Missing requirement: Android Traceview 16.0.1.v201112150204-238534 (com.android.ide.eclipse.traceview.feature.group 16.0.1.v201112150204-238534) requires 'org.eclipse.ui 3.6.2' but it could not be found
When I ran the SDK install a second time (after uninstalling it) I noticed the following error:
Stopping ADB server failed (code -1).
Unable to run 'adb': Cannot run program "/home/ben/android-sdk-linux/platform-tools/adb": java.io.IOException: error=2, No such file or directory.
Starting ADB server failed (code -1).
I didn't see it there the first time and I don't know what it means or how to fix it!
Any help would be greatly appreciated, the other 'answer' I found was from the same person who asked the question, that reinstalling everything corrected the problem, I have not been so fortunate so I thought I would re-raise the query. Thank you in advance. I am using Indigo as the version, I saw elsewhere that Helios was the lowest that could use the SDK.
Gone back to 11.10 but the issue remains the same, the laptop is a Samsung R580 64bit.
Preparing to install archives
Downloading Android SDK Platform-tools, revision 10
Installing Android SDK Platform-tools, revision 10
Stopping ADB server failed (code -1).
Still appears when installing the SDK Tools using the following command from terminal:
android-sdk-linux/tools/android

You're problem is entirely different than the one posted by robertly, although I'm sure you've found it using google.
You're running 64bit ubuntu and forgot to run the following command.
apt-get install ia32-libs
The phones aren't 64bit, so there is no 64bit version of adb. You need the ia32-libs.
After this is done, open eclipse and go to
Windows -> Android SDK Manager
then, uninstall all the tools(under tools sub folder) and reinstall them.
You should no longer get the adb error.
Source:
http://developer.android.com/sdk/installing.html#troubleshooting
Solution #2 - I had to do this because sudo apt-get remove eclipse didn't remove it completely and it still cause errors. Doing all of this, combined with the step above solved my problem the other night.
Delete eclipse, android folders
sudo apt-get remove eclipse
sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
sudo apt-get update
sudo apt-get install sun-java6-jre sun-java6-plugin
sudo update-alternatives --config java
Reinstall eclipse 3.7.1, android-sdk-linux folder
Proceed with normal installation.

Head on over here, it looks to be the same problem, but with a different package.
Eclipse Indigo - Cannot install Android ADT Plugin
This is assuming you haven't seen that yet. If you are still having problems, I can look into it further for you.