OK so I am trying out Genymotion for testing my app, so that I can reproduce the errors that my users are telling me they experience with my app, which leads me to fixing the issues. I guess that is the main reason for using Genymotion.
Real life example:
A guy says: "I'm using a Moto X (2013) on Android 5.1.1 and I can't do X with your app.
Me: Looks at Genymotions list of virtual devices and can't find neither the brand of phone nor the android system. I can only find android 5.1.0.
Does this mean that I Genymotion just doesn't have what I need, or is it because one of the other options are just as good? I really don't know. What am I missing?
Any help would be appreciated.
Brian
An emulator, be it the default android emulator or Genymotion or any other emulator will not be able to replicate a real physical device to the complete extent.
The devices available on Genymotion are just templates to recreate the device with values such as RAM, Screen size etc. You could try creating a custom device by using the values for Moto X.
One possible idea would be to get the stacktrace from your friend and see what's going on. The best way to do that would be to integrate crash reporting system like Crashyltics. You will automatically get crash reports in your fabric dashboard.
I have installed the latest Version of Android Studio. Now I like to set up an Emulator. I had used the SDK Manager to load the Intel Atom Image, and set up an AVD.
I think I have done this like in all other Examples but if I start the Emulator, all what I can se is an empty home screen without any other icons or setting. I thought the emulator would be like an real device, or quite close to it.
Maybe I think wrong?
But I had seen videos where the emulator is like an real phone.
What can i do to get my emulator to an pretty phone? :)
Thanks all.
Check if in your emulator parameters the "hardware buttons" are checked. However, sometimes android studio emulators are giving some errors. You can try download Genymotion emulators for android, if you don't lack ram it will work out pretty well for you.
I'm a newbie for Android development. I want to run a Hello World on the emulator in Eclipse as my starting point, but the magic words never show up. I just follow the tutorial, Launch the Android Virtual Device Manager, Create a New AVD and Click Run.
But Everything is fine if it runs on a real device. Is there any special setting on Mac?
Please help.
You have to wait a long time util it appears. I'd advise you to use USB debugging and a real device. It works much faster than the emulator. In addition you can use the app with the normal gestures and all the sensors like camera etc.. But as I said: it's much faster than the AVD.
Check Console tab in Eclipse for information about APK upload and installation progress.
Is there any special setting on Mac?
No there is not. Settings are pretty much the same on all platforms.
I have written some codelines with libgdx in eclipse and want to run them on my android device.(It's a tablet)
But i cant find out how to do this.
I even cant run it on the android emulator provided by the android sdk. I get an error that the app stopped unexpectedly.
The app is working fine with the desktop launcher...
I hope someone can explain me how to get it working on the emulator or on my android device.
I saw somewhere that simply connecting my device via usb should be enough that eclipse is able to create an temporary app on the device, but this also didnt work.
Regards
1st of all, download SamsungKies[latest], to get and install proper USB Drivers. Its important that it should be the latest, cuz there was a bug in the previous versions.
Now that you have the drivers, simply connect your device to your machine IN USB DEBUGGING MODE.
Go to your main activity, and run.
If it launches in an emulator, close the emulator, and again in main activity, select run configurations -> Android Applications -> target -> always prompt to pick device.
Run again, and it should install and run in your phone/tablet.
NOTE:The activity closes in emulator because, by default, the emulator doesn't support OpenGLES emulation, its too heavy for your CPU.
i know its kinda late, but i hope it helps others:)
I have a celeron processor :/ and android emulator on eclipse uses 100% of cpu and hangs everything unless I kill it . I was just trying a hello android program from a book and don`t know much about android or even eclipse .I have the android-eclipseplugin installled .
Can someone help me with is ?thanks!
As others have said, the solution is disabling sound. Unfortunately, in recent Android Studio releases (I'm using 1.4) the option to disable sound has been removed from the GUI. To disable sound you can do it either by launching the emulator from the command line with the -noaudio flag, or by editing the AVD's config file and setting the following parameters:
hw.audioInput=no
hw.audioOutput=no
On Linux, I found that file at ~/.android/avd/myAVD.avd/config.ini
I've had the exact same problem and found a solution that works for me.
In the config of the AVD I've set an extra flag "Audio playback support" to "no".
I've also made sure the AVD has 1GB of RAM.
This worked for me.
For me, it was unchecking the Multi-Core CPU check box
Niels' answer worked well for me https://stackoverflow.com/a/7706018
in that the emulator stopped using 100% CPU (dropped down to 10-15%)
Furthermore it had another useful "side effect". I noticed that playing video in Totem or music in RhythmBox would block while the emulator was running. VLC would play video but refuse to play the accompanying soundtrack for the video.
As soon as the emulator was killed, music would start playing.
Niels' answer to set "Audio playback support" to "no" prevents this issue.
I am running Ubuntu 11.04 and Android emulator version 13.0 (build_id OPENMASTER-172639).
I had same issue on my macOS High Sierra and for me helps to create new AVD device and choose CPU/ABI = x86_64, not x86 in Android version dialog. Hope that helps.
The Android emulator is emulating an ARM CPU without hardware acceleration which can be pretty slow even on a core2duo for example.
You can try to reduce the screen resolution of the virtual device which should result in a small performance increase.
The emulator is notoriously slow to start; it can take 15 minutes or longer on an underpowered machine. You can speed start-up a bit by passing the -no-boot-anim to the emulator start-up command. Other emulator options are described here. Also, some AVDs start faster than others. Try creating an AVD with the lowest level SDK that is useful for you.
Once the emulator has started, you don't need to shut it down. When an app exits (or crashes, or whatever), you can just run it again.
One alternative that worths mentioning is Genymotion. It's an android emulator based on VirtualBox, with pre-created images. It supports some features the stock Android emulator isn't very good at, like Wifi 3G, Bluetooth, GPS (with a fancy Google Maps integration, so you don't have to find coordinates manually), multiple screens, etc.
It worth giving it a try at http://www.genymotion.com/
I had this issue running the emulator on Ubuntu 14.04. Disabling the audio does bring down the CPU usage, but in case you need audio to work, it can be fixed by adding a symlink:
sudo ln -s /usr/lib/x86_64-linux-gnu/libpulse.so.0 /usr/lib/x86_64-linux-gnu/libpulse.so
The reason for this is that the emulator tries to use pulseaudio as the backend, but will be unable to link to libpulse.so, which does not exist on Ubuntu (unless you installed the libpulse-dev package). Then it will fall back to ALSA, which constantly calls poll, causing 100% CPU usage.
A fix for the emulator is coming, but for now, adding the symlink solves the issue.
I strongly recommend not to use android emulator. Use VirtualBox + android x86 OS (you can download it here ), and you will get real perfomance increase.
Unfortunately, as far as i remember, it is not from google and it supports only Android 2.2. I really do not understand, why google is not going to make simulator as fast as iPhone simulator , or to make official x86 release for debugging. I do not need emulating ARM processor instructions and I think 99% developers do no need it too.