Hello Developers,
I spent my continuous effort to solve Genymotion errors i was getting on my window vista based system.I followed all the available questions and there solutions but nothing works in my favor.Here i am adding the error details which i am getting-
Very First i was getting the No ip address found for device .i updated my genymotion and virtual machine so that is solved.
Now i am getting error unable to start virtual device.Failed to create frame buffer.Make sure that your video card support open gl 2.0,update driver.
Tried -
Updated driver from intel site ,no effect after that too.
Updated genymotion latest i am using,Jdk everything,Virtual machine
Sorry Due to new bees here i am not able to upload images .I will update once i get atleast 10 reputation thats minimum requirement.
Please guys provide my solution.Almost two full day i am continuously trying please guys provide me solutions.
this same thing happened to me. I found this link which explains that starting an Open GL 2.0 software application (Genymotion emulator) over Microsoft RDP will cause the software to run on the client machine, not the host. I requested my boss to login to the physical machine, launch the emulator, and then log out so I can RDP back in, sure enough my emulator was running and accessible. I have found also that using TeamViewer will not give this error, so perhaps if no one is able to access your physical computer, you can start the emulator through TeamViewer and revert back to RDP as needed. Best of luck with this, it was very frustrating to me as well!
Related
I am aware of Genymotion openGL error stack overflow question.
I am attempting to run Genymotion on a Windows 10 system, but the graphics adapter is Intel G45/G43 Express Chipset WDDM1.1 and the driver supplied does not support OpenGL and Intel appear to have no interest in delivering a driver that does for Windows 10. I understand that officially this combination is not supported.
But here's the thing: I can start a Genymotion VM fine from Virtual Box, and it appears to work (almost) perfectly, as far as I can tell.
Certainly I don't see any problem with the graphics.
This must be using some (probably Virtual Box provided) software implementation of OpenGL.
However, when I try to start the same phone VM from the Genymotion console, or from the Genymotion button inside Android Studio, I get the error dialog-box in the linked question above.
My question is: Why is Genymotion insisting that there is OpenGL support from the real physical display driver? And of course, if its for a quality reason only (ie: sub-optimal user experience otherwise) is there any way to disable this check?
The reason this matters is that Android Studio does not list the Virtual Box started phone VM as somewhere an application can be run upon. I suspect that when Genymotion runs a phone VM, they set up something that the Android Studio integration needs, that simply running from Virtual Box doesn't provide.
In addition, I can't circumvent the Android Studio integration by deploying to a phone VM using the gmtool device install file.apk command bundled with Genymotion because this is a paid license feature. As you can imagine I am somewhat reluctant to purchase such a license when I know I am running in an unsupported configuration.
Purchasing new hardware also isn't an option for me in the short term.
EDIT: The justification for this question has since evaporated. Although I can't deploy using Android Studio or gmtool.exe, I have managed to deploy by using the phone web browser to fetch the .apk file. The gotcha here is that the web server must supply a Content-Length header or the download will fail. So I now have a workable solution.
{{{ Andy
I'm part of the Genymotion team. That's an interesting question. The answer is: yes, we ask for OpenGL drivers for performance reasons. Without this, the whole Android rendering would be handle by the CPU (as soft rendering) which is not fast enough to allow a real usage of the devices, with a seamless user experience, particularly since 4.3. If you run a 4.2.2 image from VirtualBox, you'll see the UI inside the window but the rendering will be very laggy.
As you maybe already noticed, running the Genymotion devices from VirtualBox works only for images up to 4.2.2 (released 3 years ago). The other image will show only a console window. And to be honest, you should more consider it as a side effect than a real feature. This behaviour could disappear on a future release for any reason. And there is no way to disable this check.
As you mentioned, this configuration is really weird and exceptional. As far as I know, we don't plan to support these kind of configuration and I don't see any real viable solution to make it work properly.
Also, to explain the problem you encountered with Android Studio. When a Genymotion device start, it gets a local IP. This IP can be used to connect it to adb. Then it is possible to interact with the device like with any other Android device. This is the tools used by your IDE (and (m)any other tools communicating with Android devices.
Usually, the Genymotion app does this for you, by connecting the newly started device to adb. But you can do it yourself by running adb connect <DEVICE_IP>:5555. Just be careful because this connection could not be permanent and you should have to run this command regularly in some situations.
I hope this answer will help.
Cheers.
I'm currently trying to do this tutorial
http://developer.android.com/training/basics/firstapp/running-app.html
but I'm having trouble getting the simple "Hello World" app to run. Here's what I'm facing.
1) The AVD I'm using has been displaying the shiny "android" loading image you would associate with a boot-up for ages and I cannot get it to progress beyond that despite leaving it to run for an hour.
2) Trying to search for a device also yields nothing. I've connected my 1 year old Sony Xperia SP, entered USB debugging mode and have made sure the device can be seen on my device manager. Yet, the device does not appear on the device selection menu.
Is there something I'm doing wrong? It's really frustrating to get stuck at the first hurdle in my Android Developer journey, so would really appreciate any help I can get.
EDIT: Managed to fix #1 with a Genymotion simulator. The problem with the Xperia is still there though, even though I got it running with the Sony PC Companion... Anyone got any tips?
EDIT #2: Finally figured found out from a friend I needed to change the USB Connection mode to "Mass Storage". Wow such a simple change that is barely documented anywhere really cheeses off beginners -_-
Oh well, onward!
1) See this
2) If you follow android's instructions clearly, using your phone as a developers tool should work. You might need to install some drivers and you should be able to get it going through ADB.
I'm trying to get my phone to connect with Eclipse so I can run android apps without using an emulator. I've already gotten this to work and made an app, but I got a new hard drive since then. Every time I try to reinstall it on the new hard drive, it says that it doesn't install properly. I've tried using 2 different usb cords, rebooting every time I try it and installing/uninstalling the USB driver from the Motorola website to no avail, and I can't remember exactly how I did it before.
Can anyone help?
Make sure your usb debugging turned on and use this free software to install the driver :
http://adbdriver.com/
Android's development page doesn't explain this one in full detail. I had problems with it myself. Although my situation wasn't exactly like yours, installing the usb driver from the SDK made it work.
Follow this guide!
So i'm having awful trouble trying to get the Emulators in the Android SDK to start up. I can create the AVDs just fine, and then when hitting the 'start' button from the SDK Manager, bring up the small loading console window, indicating that the emulator is launching. However, after that, nothing happens!!
I have read many threads and posts with people having the same problem, maybe to do with the settings requiring too much memory, with some people waiting 30 minutes for the emulator to load!!
When trying to run the AVD emulator through terminal, I simply get a 'Bus Error' with no further indication of what could be going wrong...could it be a memory issue?
What I did to get where I am now:
Download the Android SDK package for Mac. I'm extracting the sdk only, not eclipse. I'm on Mac 10.6.8.
Install the SDK, and download the latest version of Android in the SDK Manager, along with default tools.
create a AVD and hit start.
window pops up to boot the emulator, that process is complete and window closes.
Nothing happens.
My knowledge of the sdk tools are very limited, all I want is to be able to do some testing...
Any help greatly appreciated!
Thanks
Actually, the simplest way to get emulators running right now is probably GenyMotion. They provide an interface, and pre-configured emulator images to make it pretty simple to get running.
This is not an endorsement (I use the standard ADT myself) but a lot of people find their tools useful.
Here is my suggestion: instead of using AVD, start using espresso and virtual remote android hardware emulator from Google servers - also known as android-test-kit. You will have the possibility to run and test you App on several different devices, without the need to spend money on actually all different devices for developing and testing purposes before releasing your Apps. You find further details here:
android-test-kit
Why Espresso
The 2 videos are somewhat long, but worth watching.
Taking this approach will solve your problem, save you money, and improve your productivity.
I run into the same issue on my mac 10.6 and it only works if i do
emulator64-x86 -avd my_android
Besides, my virtual device has to configured using x86 but not ARM
maybe this link can help you.
I've installed genymotion about 2 days ago and I've been facing the same problem every time I tried to start a device.
After I downloaded a device in genymotion (Nexus S - 4.2.2 - API 17 - 480*800) I launched it.
Then after a box poped up telling me I have to wait, I got this error:
The virtual terminal genymotion didn't get an ip address. For an
unknown reason the virtualbox's dhcp servor didn't assign an ip adress
to the virtual terminal. Please launch virtualbox to find a solution
to this problem
I can't figure out how to solve this problem.
I looked up on many websites but it seems as if I'm the only one to get this error.
I'm on Windows XP-SP3.
My graphic card is a radeon HD 3600 driver up to date.
Does anyone have any idea?
Thank you.
Try downgrading to Virtual Box 4.2.18, if you are using 4.3.X.
I had a similar situation to yours.
I was using Genymotion 1.3.0 on Win7, with latest Virtual Box 4.3.2. Genymotion broke down after a computer shutdown, and never worked again.
I kinda stumbled onto this solution. After downgrading, Genymotion survived one shutdown now.
All Android VMs used to work for me under Genymotion 2.0.0. with default RAM and CPU settings and VirtualBox 4.3.2 (on ubuntu 13.10). Upgrading to 2.0.1 made them stop working and give the error you mentioned.
I tried various fixes as I described here: https://stackoverflow.com/a/20018833/2527118, but in summary what fixed my problem was to delete VM and recreate it (same source and settings) in GenyMotion. You might want to try the other fixes (less destructive) before doing that.
Andrei
I try to solve this for 6 days and in the end, I realized I needed to uninstall then re install virtual box so I can get their default settings then change my network settings as explained better in this link. It explains in depth how the ip address works with the virtual machine, and how the chances of it trying to use a static ip address are very likely.
https://askubuntu.com/questions/232876/how-to-let-a-virtualbox-guest-running-windows-access-the-internet
let your network settings be handled by themselves if you've tried everything, maybe this will allow your VM to use its own IP address and stop trying to use your Physical devices IP address.
Hope this helps.
I had the problem with the IP error, too. As I have a real Samsung Galaxy S2, I downloaded the vitual version 2.3.7 Api 10 in Genimotion. All IP settings were correct, the sequence of starting the programms didn`t matter. The IP error reoccured :( .
Finaly, I tried to use another virtual device: Custom Tablet 5.1.0 API 22. It loaded and worked, but very slow. WhatsApp got stuck on the installation process :( . As this article on Heisse.de recomended to use the Nexus S 4.1.1 for WhatsApp, I tried this third vitual device and everything worked fine :) !
http://www.heise.de/download/special-whatsapp-auf-pc-mac-und-linux-nutzen-152241.html?hg=1&hgi=3&hgf=false
I know this post is old. But my answer is just for someone who google this issue and hopefully it may help them since I also stuck on it for a long time and fix it fortunately.
This is my way to fix the problem:
First of all, I had configured all the settings what the people said on the internet like the following link: Not able to start Genymotion device
I found that it's still failed to run the VM on GenyMotion.
So I tried to remove all the existing Host-only Network like vboxnet0 or vboxnet1(According to the official website of GenyMotion, it said that it will regenerate a new one when there is no any vboxnet)
Finally, I tried to restart the VM on　GenyMotion, suddenly I run it successfully without any errors message
Notes: I disabled the adaptor 2, 3 and 4 before I was gonna tried the above actions.
As other have said, you have to install Virtual Box. In my case (using Ubuntu 16.04), I had to enable the 'virtualization' in Bios. Once that was setup, I was able to set the 'OS' to use 'Ubuntu 64bit' in 'settings/general' tab.
Other possible solutions include, configuring Virtual Box further, including reducing the RAM usage (in settings), in 'Network' tab in settings, under 'advanced' options, disabling the 'cable connected' option & setting 'Promiscuous mode' to 'allow all'.
IN case a Genymotion device cannot obtain an IP address any more, you might want to check the configuration in the VM-Ware settings: I got this fixed by removing the "promiscous mode" from the network adapter 1 settings - see screenshot.
The promiscous setting may lead to difficulties in obtaining an IP address in the genymotion simulator