I followed this Google TV Emulation guide, which tells how to set up my emulator environment. Although when I launch the AVD created by AVD manager, the emulator starts but no logo appears and a black screen. One of my CPU cores is always 100 percent; KVM is enabed. The -verbose option log ends with the following lines:
emulator: control console listening on port 5554, ADB on port 5555
emulator: sent '0012host:emulator:5555' to ADB server
emulator: ping program: /media/Mywork/tools/sdk/android-sdk-linux/tools/ddms
emulator: ping command: /media/Mywork/tools/sdk/android-sdk-linux/tools/ddms
My host envrionment is: Intel i7, Ubuntu 10.04 64-bit.
Can you post the settings for your AVD?
Edit:
Also, have you tried pushing an app into the emulator?
Can you include the steps you used to launch the emulator?
Did you apt-get install kvm?
Related
I am trying to develop and application who connects to a serial port. For that, I am following this api:
https://code.google.com/archive/p/android-serialport-api/
https://github.com/cepr/android-serialport-api
When I run the application in a real device it works, but when run in the android emulator, no serial ports are shown in the setup activity.
I am doing the following steps to run the emulator:
C:\Users\myuser\AppData\Local\Android\sdk\tools\emulator.exe -avd Nexus_5_API_23 -qemu -serial COM1
C:\Users\myuser\AppData\Local\Android\sdk\platform-tools\adb.exe wait-for-device
C:\Users\myuser\AppData\Local\Android\sdk\platform-tools\adb.exe shell chmod 666 /dev/ttyS2
Similiar to this link:
https://github.com/cepr/android-serialport-api/blob/master/android-serialport-api/project/run_emulator.sh
I am using a Nexus 5 emulator, Should I choose another emulator?
What I am doing wrong? What I am missing?
While creating an emulator, encountered the following error
Reserved block group size: 7
Created filesystem with 11/4224 inodes and 1302/16896 blocks
Hax is enabled
Hax ram_size 0x40000000
HAX is working and emulator runs in fast virt mode.
adb_server_notify: Failed to establish connection to ADB server
console on port 5554, ADB on port 5555
emulator: ERROR: Could not initialize OpenglES emulation, use '-gpu off' to disable it.
Currently Android Studio IDE provides Virtualisation Technology for simulation for better and speedy performance.
For that purpose you have to install an patch of "HAXM". Virtualisation patch available at Android Download Manager.
after successful installation of that patch you have to enable the Virtualisation from system BIOS.
after that simulator will work surely with better and speedy performance.
if you are facing some issues with adb server then follows,
Go to the Android SDK platform-tools directory in Command Prompt.
type adb kill-server (Eclipse should be closed before issuing these commands)
then type adb start-server.
No error message is thrown while starting ADB server, then adb is started successfully.
Thats Done.
I m trying to get a memory dump from a Android system using the pmemsave command from qemu, but I have some problems with accessing the qemu monitor interface.
I start the emulator with the following command:
$./emulator -avd test -verbose -qemu -monitor telnet:127.0.0.1:1234,server,nowait
The emulator starts up just fine, but when I telnet to the port I am not greeted with a banner, and no input seems to have any effect. I have also tried to set -monitor to stdio without success.
Same here. I'm afraid QEMU Monitor is no longer available.
Create AVD, telnet to it, and type qemu monitor:
$ telnet 127.0.0.1 5554
<snip>
qemu monitor
KO: QEMU support no longer available
See also:
Tweet https://twitter.com/blundell_apps/status/536163955186860032
Git commit https://github.com/android/platform_external_qemu/commit/aa1180ca05774398245953deb306c0e25829afee
I am running my simplest Activity App in Emulator which I created in IntelliJ. I invoked Emulator from the IDEA IDE, it does show emulator in locked screen format. After unlocking I don't find icon of my application. Where am I doing wrong? or how can I run it manually on Emulator?
Emulator shows following message on Console:
Waiting for device.
/usr/local/Cellar/android-sdk/22.6/tools/emulator -avd myavd -netspeed full -netdelay none -wipe-data
emulator: ERROR: Could not load OpenGLES emulation library: dlopen(lib64OpenglRender.dylib, 1): image not found
emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.
HAX is working and emulator runs in fast virt mode
Device connected: emulator-5554
Emulator Snapshot attached. As you see. I don't find my app here
If you are using windows:
Go to cmd, cd into the folder containing the platform-tools.
Then -> adb install myapp.apk . This command installs the app.
If you are using GenyMotion emulator. Just grag and drop your apk into the emulator.
If the emulator is not in sync with the ADB,which is responsible for the connection. Just restart the ADB like:
adb kill-server
adb start-server
Running Eclipse Build id: 20110615-0604
Android SDK & AVD Manager (setup in eclipse)
Android X86 2.3-RC1.eeepc.iso
Oracle VM VirtualBox Version 4.1.2.r73507 (installed and running android)
In the VM using Alt F1 and the command netcfg produces:
Android root#eeepc:/ # netcfg
lo UP 127.0.0.1 255.0.0.0 0x00000049
The path for Android is set in eclipse to C:\android\android-sdk
In the tools directory I use the command 'adb kill-server'
I then use 'adb connect 127.0.0.1' which produces:
unable to connect to 127.0.0.1:5555
I have a virtual device setup already in Eclipse using the AVD manager and this works perfectly - though very slowly, hence the need to use X86.
When the working emulator is running the command 'adb devices' produces:
List of devices attached
emulator-5554 (the slow emulator)
When the slow emulator is running and I then use the command 'adk kill-server' and use the command 'adb connect 127.0.0.1' it produces:
C:\Android\android-sdk\platform-tools>adb connect 127.0.0.1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connected to 127.0.0.1:5555
So then I go back to:
C:\Android\android-sdk\platform-tools>adb kill-server
C:\Android\android-sdk\platform-tools>adb connect 127.0.0.1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connected to 127.0.0.1:5555
C:\Android\android-sdk\platform-tools>adb devices
List of devices attached
emulator-5554 device
127.0.0.1:5555 device
But the new X86 device, presumably at 127.0.0.1:5555 doesn't appear in the AVD manager. Should it? I'm stumped.
I've googled everywhere so any help would be greatly appreciated. Thanks.
Hello James,
I tried a similar set up and I got the same error as you. I eventually gave up using virtualbox. After struggling for two days I switched to using vmware and I had to use a different image.
I used the following image: http://android-x86.googlecode.com/files/android-x86-2.2-r2-eeepc.iso
and for the vmware set up I followed this tutorial: http://vmetc.com/2010/12/27/install-androidx86-in-a-vmware-workstation-vm/
Do not skip over the part that says to edit the virtual machines configuration file.
I hope this helps.
You might also want to consider using the android image provided by http://www.vmlite.com/ it worked right away for me and I connected using "adb connect 127.0.0.1"
I had the same problem of "unable to connect to 127.0.0.1:5555". I then found here:
http://www.android-x86.org/documents/debug-howto
...
2.using adb with a NAT'ed VM
•The steps above work nicely if you have a VM which is set up to use Bridged or Host-Only adapters
•However, if you have a NAT'ed VM you cannot connect to the VM IP from the host
•You will need to set up port forwarding for a host port to be forwarded to the VM port 5555 (which is adb)
VBoxManage modifyvm --natpf1 adb,tcp,,,,5555
Example from one machine:
VBoxManage modifyvm froyo --natpf1 adb,tcp,,5555,,5555
•Once this is done, you should see the local port (i.e. 5555 in this case) bound on the host via netstat -a
•You can now connect to the VM by adb localhost:5555
That solved the problem for me. Good luck!