On Windows 7 64-bit, running Eclipse 3.6 64-bit, JDK (jdk1.6.0_23) 64-bit and Android 2.3 (bitness?), running a program via Eclipse's Run|Run (Ctrl+F11) invokes the android emulator, but won't install .apk on the emulator (and certainly won't run it).
(update, answering #Computerish's question) All I am getting at Eclipse's Console is:
[2010-12-16 10:23:33 - HelloAndroid] ------------------------------
[2010-12-16 10:23:33 - HelloAndroid] Android Launch!
[2010-12-16 10:23:33 - HelloAndroid] adb is running normally.
[2010-12-16 10:23:33 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2010-12-16 10:23:33 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'AVD23'
[2010-12-16 10:23:33 - HelloAndroid] Launching a new emulator with Virtual Device 'AVD23'
This problem doesn't happen on Windows XP, running Eclipse 3.5.2 and Android 2.2 (all 32-bit).
I tried the solution suggested by the accepted answer in this thread but it didn't help. Task manager shows adb's Image Name as 'adb.exe *32'. Perhaps there is a mismatch between the bitness of Eclipse+JDK (64-bit) and the Android emulator/SDK?
Is Android development using 64-bit JDK not possible (yet)?
OK, here is the final answer (as of today): Android development, using 64-bit JDK only, is not possible (yet).
If you install the 64-bit Eclipse and install only the 32-bit JDK, Eclipse will refuse to start.
So, if you decided to install the 64-bit Eclipse, you need to install both the 64-bit JDK and the 32-bit JDK.
Thereafter, even the infamous installer_r08-windows.exe will run (and even invoke "SDK Manager.exe" automatically for you).
But 64-bit Eclipse still won't install .apk on Android emulator.
Conclusion: Google is absolutely correct in stating that Android is not supported (yet) under 64-bit Windows. The fact that some geniuses manages to do some magic to make their environment work is beyond me.
I suppose that 32-bit ADB waits for 32-bit JDK. Just install 32-bit JDK - and everything should work after that. i'm running Android SDK on 64 bit machine with both installed JDK's 32 and 64 bits - and everything is OK
I know this might be late, but I found a fix for it.
I'm running:
-64-bit Windows 7
-64-bit Java 1.7 SDK
-64-bit Eclipse for Java Developers + ADT Plugin
-64-bit Android SDK
So what I do is save my java source files, and run the application through Eclipse. I close the emulator after it fully loads to the home screen. Next, I go to my command prompt in Win7 and type emulator -verbose -avd youravdname. After you press enter, Eclipse will decide to upload and install the .apk file onto the emulator. Now you can see your new activities!
It's very cumbersome, and I wonder why this even works. I seriously spent hours wondering if I even installed everything correctly.
I had the same problem as the original poster and I'm also using Android SDK 2.3, Eclipse Helios, JDK 1.6.0_23 64-bit on Windows 7 Professional 64-bit.
However, once I've killed the adb.exe *32 process and then restarted eclipse and then tried running HelloAndroid app again, the emulator started successfully, the app *.apk was loaded and ran perfectly.
I didn't do anything else and I haven't installed JDK 32-bit on my machine.
Related
Hopefully someone can help me with the following problem:
I installed Android Studio (Artic Fox, 2020.3.1. patch 3) on an fairly old MBP (mid 2012, i7, 16G, NVIDIA GeForce GT 650M 1024 MB, Intel HD Graphics 4000 1536 MB, High Sierra 10.13.6)
When i want to run my first app i get this message:
Error while waiting for device: The emulator process for AVD Pixel_XL_API_30 has terminated.
I searched on Stackoverflow for solutions and i found the following:
Error while waiting for device: The emulator process for AVD Pixel_3a_API_30 has terminated
Emulator always crashes with error "Error While waiting for device: The emulator process for AVD has terminated"
But both solutions did't work for me.
Can someone point me to the right direction.
Thank you.
To summarize from Arthur Wilton's medium post:
Recent versions of the Android emulator won't run on macOS before 10.15 Catalina. The AVD Manager alert might read, "The emulator process for AVD Pixel_2_API_29 was killed."
Arthur encountered this problem with emulator version 30.5.3.0.
As of this writing, the current release is 31.1.4.0.
Launching the emulator from Android Studio doesn't reveal error info but in this case it's because the new emulator requires the IOUSBHost library that Apple introduced in macOS 10.15.
You can get error messages and other information from the Android emulator from the command line:
emulator -version
emulator -list-avds
emulator -avd Pixel_2_API_29 # try to run the named AVD
(The emulator is typically installed in ~/Library/Android/sdk/tools/emulator on macOS. It might not be on your shell path.)
An obvious solution is to upgrade to macOS 10.15 Catalina or later. If you can't do that (staying on Mojave in order to run 32-bit apps?), Arthur's workaround is to download Android Emulator 3.4.5 from https://dl.google.com/android/repository/emulator-darwin_x64-7140946.zip, install it by unzipping it into ~/Library/Android/sdk/emulator, then editing the <revision> info in package.xml to trick Android Studio into thinking you have the latest emulator installed. Otherwise it'll try to upgrade it.
I am running android studio 2.3.3 on ubuntu Gnome 17.04 when running the android app on the emulator it gives timeout error after "waiting for target device to come online", Actually the emulator doesn't start even when trying to start it alone from the AVD manager. I tried all the solutions in the following links but still not working.
Waiting for Target Device to Come Online
Android Studio Waiting for Target Device to Come Online Linux Mint 18
Android Studio Waiting for Target Device to Come Online Linux Mint 18
Note: The app is working on a physical device
Here are some screenshots from android studio:
Try creating a new AVD with different API and also use the recommended ones for better support for API's .
Hope this helps
The emulator now starts and the problem was solved by locating lib64 folder since i am running ubuntu 64 bit. In my case, its located under ~/Android/Sdk/emulator/lib64. Then run the following commands in terminal :
// Double Check to see if these are available
$ sudo apt-get install lib64stdc++6:i386
$ sudo apt-get install mesa-utils
// Navigate to the ~/Android/Sdk/emulator/lib64 folder
$ mv libstdc++/ libstdc++.bak
$ ln -s /usr/lib64/libstdc++.so.6 libstdc++
Source: How can I get more information about "Waiting for target device to come online" in Android Studio?
Using android studio on W10 had the same problem with the emulator tried all of the answers on StackOverflow: none worked for me until was playing with settings on Emulator, problem was because of OpenGL
Fix: the "More" button on emulator ----> Setting ----> Advanced
1- OpenGL ES Renderer: scroll to select Desktop Native OpenGL.
2- OpenGL ES API Level: scroll to select Compatibility OpenGL.
I did setup eclipse with ADT and the Android SDK 2.3.3 however it seems that trying to run ./adb connect <ip_of_vm> does not do anything as the execution hangs and nothing happens. I was able to install the SDK with the ia32-libs and eclipse works like a charm... however this is the last step preventing me from attaching my VM to eclipse/adb.
Can anyone explain me how to troubleshoot?
This is my development framework:
Ubuntu 10.04 x86_64
Java 1.6.0_26-b03 (64 bit)
Eclipse IDE for Java Developers: 1.2.2.20100216-1730 (64 bit)
Android Development Tools: 15.0.1.v201111031820-219398
Android Debug Bridge version: 1.0.29
I do not remember having done anything related to ia32
Do you have 64 bit versions of Java and Eclipse?
I would suggest to uninstall the SDK and install it again without using the ia32-libs
Yes,adb tool is not available with android x86 so you can not use adb commands here some commands are modified also see what all you can use press Alt + F1 then go at /system/bin/ then make use of ls
I've been making some apps for android for quite a while but I've only been using windows 7. Due to some reasons sometimes I'm forced to program in linux so I followed the guide to configure the SDK and eclipse (http://developer.android.com/guide/developing/device.html).
After that I ran "adb devices" and got this:
List of devices attached
???????????? device
As you can see the name is unknown but this also happens in windows so I didn't fret too much over it.
Then I launched eclipse and made a very simple project to test the deployment but here two things happened:
1st- It doesn't detect the android SDK version. (http://img515.imageshack.us/img515/5611/escolha.jpg)
2nd- when I try to deploy I get the following output:
[2010-10-09 23:06:45 - testeAndroid] Android Launch!
[2010-10-09 23:06:45 - testeAndroid] adb is running normally.
[2010-10-09 23:06:45 - testeAndroid] Performing com.examples.teste.teste activity launch
[2010-10-09 23:06:45 - testeAndroid] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2010-10-09 23:09:50 - testeAndroid] WARNING: Unknown device API version!
[2010-10-09 23:09:50 - testeAndroid] Uploading testeAndroid.apk onto device '????????????'
[2010-10-09 23:09:50 - testeAndroid] Failed to upload testeAndroid.apk on device '????????????'
[2010-10-09 23:09:50 - testeAndroid] com.android.ddmlib.AdbCommandRejectedException: device not found
[2010-10-09 23:09:50 - testeAndroid] Launch canceled!
I'm using:
eclipse 3.5.2
adt 0.9.9
android SDK tools r7
android phone: vodafone 845 = Huawei U8120 - android 2.1-update1
Any idea for what is happening?
thanks in advance ;)
The Huawei U8120 (Vodafone 845) phone is one of those USB devices that present themselves as USB storage devices to the host operating system to serve up files for Windows driver installation. To switch them into the USB slave from Linux mode you need to use usb_modeswitch. You can download the latest usb_modeswitch package from the homepage, it includes support for your device. Or just use this call on the command line:
$ sudo usb_modeswitch -v 0x12d1 -p 0x1031 -s 20 -M "55534243123456780600000080000601000000000000000000000000000000"
However to use it with the Android tools you need to solve another problem, because the Huawei U8120 (Vodafone 845) provides no serial number. There might be other workarounds, but the one that made it work for me is a patch for the "adb" utility that can cope with devices that have no serial number.
$ ./tools/adb devices
List of devices attached
noserial-/dev/bus/usb/001/036 device
The patch is here: https://review.source.android.com/#change,13552 and here you can find an "adb" binary if you trust that source :) www.mediafire.com/?oizmyyw0wwz
see also http://code.google.com/p/android/issues/detail?id=4365
You have to update your udev rules according to the manual on http://developer.android.com/guide/developing/device.html - then it will work.
I have also android plataform and just a couple of days, an upgrade seemed to solve the problem. You have to make sudo usb_modeswitch -v 0x12d1 -p 0x1031 -s 20 -M "55534243123456780600000080000601000000000000000000000000000000" and the standard adb, as well the ADT plugin worked in ubuntu 10.04.
My adb version is 1.0.26 and the ADT plugin 10.0.0.v201102162101-104271, since the ADB upgrades forced me to update Eclipse plugin.
I am a beginner android developer and I had followed the instructions in the Quick Start and SDK Setup. After following all the steps I attempted to run the Hello World sample application and when I run the project, I get the standard "emulator.exe has encountered a problem and needs to close." box. I tried running the avd that I created in the AVD manager with the same results. I also tried running the AVD from the command line, using "emulator.exe #my_avd". I've tried 2.1 and 2.2 platforms. I using Eclipse 3.5 SR2 with the android plug-in. I am running Windows XP SP3, 512MB RAM, Intel Core 2 Quad on a virtual machine using VM-Ware. My machine running the virtual machine has the 3GB max ram for a 32-bit machine.
Thanks in Advance,
Mark
In response to comments:
Android console says:
[2010-07-29 10:39:20 - HelloAndroid] ------------------------------
[2010-07-29 10:39:20 - HelloAndroid] Android Launch!
[2010-07-29 10:39:20 - HelloAndroid] adb is running normally.
[2010-07-29 10:39:20 - HelloAndroid] Performing odog.andriod.example.helloandroid.HelloAndriod activity launch
[2010-07-29 10:39:20 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'my_avd'
[2010-07-29 10:39:20 - HelloAndroid] Launching a new emulator with Virtual Device 'my_avd'
DDMS console says nothing.
I have not tried to run the emulator on the physical machine. I'm trying to keep the Android development machine "clean". My physical machine has Visual Studio 2010, 2008, 6, Windows Platform SDKs, DirectX SDKs of various versions as well as various versions of Eclipse for micro-controller and BlackBerry programming. Little mucky .... needs to be formatted.
It seems deleting and reinstalling all the packages in the Android SDK and AVD Manager worked. Thanks for interest.