This question already has answers here:
Not able to start Genymotion device
(25 answers)
Closed 7 years ago.
This question might seem a duplicate of this question but it's not because i've tried almost everything in this world to get a device run in genymotion.
Everytime i try to start a device i get the error:
after some minutes looking for the log file i could found it and the last line (where it get stuck) says this:
Mar 27 04:01:31 [Genymotion Player] [Error] Can't detect device IP address
The error is explanatory itself but i don't know how to make it detect the device ip address, things i've tried are:
Deleting all Host-only network in VirtualBox
Updating VirtualBox to last version.
Downgrading version.
Delete vm and recreate it.
Erase and download same device.
Fill manually network configuration (was a silly attempt but the error is driving me crazy)
By the way the Firewall isn't blocking the application because i checked myself.
I tried all the step from this answer and also none of them didn't work
I had a Linux distro called Elementary Luna and i installed genymotion and it worked perfectly on elementary luna but i had to came back to window due driver issue that doesn't let the distro boot up again. I can't use the emulator that came with the Android SDK because i have AMD processor and my CPU model isn't good, i don't even get 1 fps with the sdk emulator. But when i was using Genymotion back in linux i could run it at 20/30fps.
Forgot to say i'm on Window 8.1 Enterprise.
Do i have to fix and come back to linux again to test my android app?
unfortunately I could solve it downgrading to Window 7, i think the problem was with Window 8.1, now i'm using Windows 7 Ultimate and it's working perfectly.
Edit
I came back to Window 8.1 and everything is working perfectly, i still don't know what the problem was, but it's working now.
Related
TCP connections work fine as I am able to converse with someone over zoom and teamviewer. However, whenever I attempt to access another webpage, I get a network error. Google seems to work fine for some reason but any webpage I go to listed by Google fails to connect. The only way I can open up my http connections is by ending a task called "init" inside of task manager. This shuts down my vscode as well as my ubuntu terminals I have running. If someone knows the solution please do tell. It's really annoying having to close out my vscode and terminals as well as my local servers to look up information and debug.
I found a fix to this issue.
So I was running a Windows Subsystem for Linux and my Windows Build was outdated as well as WSL. When I updated Windows and upgraded to WSL2, my issue was resolved and I don't seem to get any more network errors.
I am running the “Arduino Example” model in the NetLogo Models library (it’s in the “IABM Textbook” > “Chapter 8” folder),
and I have encountered a problem with the arduino:open primitive.
The problem is that the Netlogo keeps crashing every time it reaches the point I use the open primitive.
I have followed the instructions given by this page: https://ccl.northwestern.edu/netlogo/docs/arduino.html#arduino:primitives .
I made sure that the port name is right and according to the device manger it works fine .
What could be causing this problem ? How can I solve it ?
I'll be happy for any suggestions.
The NetLogo 6.0.1 release announcement says:
The arduino extension doesn't work properly in Windows 10 under 64-bit NetLogo. It does work properly running under 32-bit NetLogo
(I would link to the announcement, but I don't see it on the netlogo-users group where I would normally expect to find it; I got it by email.)
I've followed the instructions at the link below to "Build and simulate a Cordova iOS app in the cloud". https://taco.visualstudio.com/en-us/docs/build_ios_cloud/
After completing the instructions I'm able to build and get the iOS simulator working, however, I'm unable to attach a debugger.
The message displayed in remotebuild is:
GET /cordova/build/5655/debug 500 10.865 ms - 28
In Visual Studio I see the following in the Debug window:
Starting launch process C:\Program Files (x86)\nodejs\node.exe "(redacted)\node_modules\vs-tac\emulator.js" --platform ios --action launch --path "(redacted)\buildInfo.json" --serverUrl https://(redacted):3000/cordova --certificateName (redacted) --language en-US --loglevel info --cliVersion 5.4.1 --npmInstallDir "(redacted)" --deployTarget "iPhone 5"
Timed out connecting debugger to remote Apache Cordova app. See Output window for JavaScript console output.
------ Cordova tools 5.4.1 already installed.
Requesting emulate on iOS Simulator for buildNumber 5655 on server https://(redacted):3000/cordova...
Emulated - Successfully sent to ios Simulator
------ Cordova tools 5.4.1 already installed.
Requesting debug on remote iOS device for buildNumber 5655 on server https://(redacted):3000/cordova...
Failed to Debug iOS remote for build (redacted)\buildInfo.json to https://(redacted):3000/cordova :
iPhone 5
My local development machine is using Visual Studio 2015 and Cordova 5.4.1. I have Node v0.12.2 installed locally and v0.12.9 installed on the MacInCloud. Following the instructions in the link above, I am NOT an admin on the Mac machine.
I've also already tried the instructions suggested in this SO answer: Visual Studio Debugger failing to connect to remote Apache Cordova app in iOS simulator
All the suggestions and the links provided by others were helpful but ultimately my assessment of the problem was not being admin/root on the Mac. The Visual Studio Cordova docs linked in my original question would suggest that you can do all that you need on a Mac without having admin/root access but in my experience that is just not the case.
To the credit of the MacInCloud group, they were very helpful in making changes that I requested to permissions and for reinstalling packages such as brew, ios-webkit-debug-proxy, remotebuild, etc... but after a while that back-and-forth kind of approach to fixing the issue proved painful. When I switched from a Managed MacInCloud server to a Dedicated one, everything worked almost immediately.
Looking back I think the initial execution of remotebuild, which executes brew -- without being admin on the box -- caused the whole process to go south. I was warned when I ran remotebuild for the first time that it would install some brew components that might need root access. That should have been a warning sign to me that not being admin on the box was going to be an issue...
Even though I was able to get a Dedicated MacInCloud server working, the lesson I learned about having control over the Mac prompted me to just buy a Mac Mini. That was a little more difficult to setup because I was now doing everything myself, but ultimately I think it will pay off in the end.
For anyone else struggling with similar issues here is a brain dump of some things I learned along the way:
You don't necessarily need to get Visual Studio talking to the Mac to debug Cordova applications. You can use Safari Web Inspector from the Mac. https://blog.nraboy.com/2015/10/debugging-your-apache-cordova-ios-app-with-safari/. Even though I finally got VS working, I actually prefer this because it is more like Chrome's debugger which I prefer to Visual Studio's.
The ios-webkit-debug-proxy NPM package mentioned in other comments and links is basically a proxy which Visual Studio uses to debug the simulator in exactly the same way Safari does as mentioned above. For this proxy to work you must also be allowed to connect to the Mac over ports 9221-9322. https://github.com/google/ios-webkit-debug-proxy. Prior to learning that I thought I only needed port 3000 open for the remotebuild proxy...
The package necessary for launching the iOS simulator from remotebuild is ios-sim and it will occasionally timeout when launching the simulator and cause the debugger not to attach. This is a known limitation. https://github.com/phonegap/ios-sim and https://blogs.msdn.microsoft.com/visualstudio/2014/11/13/tools-for-apache-cordova-update-ios-debugging-windows-8-1-support/ (see comments).
If you should feel the need to install/uninstall brew it is very easy to do. Just run the install script and if already installed it will give you instructions on how to uninstall. http://brew.sh/ and https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/Troubleshooting.md#troubleshooting. To uninstall or reinstall a NPM package is equally easy and Google is your friend.
Read and re-read both of these links for setting up a Mac: https://taco.visualstudio.com/en-us/docs/ios-guide/ and https://taco.visualstudio.com/en-us/docs/build_ios_cloud/. Getting the RemoteBuild.config right is crucial for getting secure connections to work -- especially if you want to access your Mac Mini at home from across the internet.
If you are remoting to a Mac I highly recommend iRAPP or some other VNC alternative. My experience has been that VNC is painfully slow and having a bad connection when you're troubleshooting issues just leads to more aggravation. http://www.coderebel.com/products/irapp/
As mentioned above, the MacInCloud guys were great when I asked for support, but if you do need root access for more than six months the cost of a Mac Mini is less than a Dedicated server plan.
Cheers
Since it is the call to /cordova/[...]/debug that is failing it looks like you might not have ios_webkit_debug_proxy installed. You could try making sure that homebrew is installed (from http://brew.sh) and running brew install ios-webkit-debug-proxy. Afterwards you should be able to run ios_webkit_debug_proxy without an error.
If that runs successfully then you should be able to quit out of ios_webkit_debug_proxy and debugging should work via remotebuild.
I've been trying to enable Bluetooth on an Acer Aspire V3 running Win 7 Pro 64 bit. I've uninstalled and reinstalled drivers several times and tried cleaning out the registry. No luck, doesn't seem to recognize the hardware.
According to Acer, the laptop comes equipped with "Acer Nplify 802.11a/g/n + BlueTooth 4.0", and another post I read said I had to update the "Quallcomm Atheros WiFi Driver Installation" program to enable Bluetooth. When I first attempted it asked me to locate folder containing layout.bin, then for folder containing 0x008xx. Found layout.bin in the driver folder, but not the second file.
Now, after cancelling out of that, I can't modify or uninstall the Atheros WiFi Driver Installation program, I get and error referencing: SetupNew/setup.cpp (135). I have a screencap if it helps, but I can't post it because I'm a newbie.
Can't find much on this error, it seems to be a service or program holding on to it, but I've deleted/stopped/uninstalled any related services, programs or drivers I could find and tried to delete. Again, no luck.
Sorry about the long post, but I've been trying for hours and can't find anything on point for this online. Anyone have any ideas?
I tried openstack on my laptop, my setup is like this
Host Machine: Windows 7
Virtualisation: VirtualBox
Ubuntu12 is running on this VirtualBox, On this Ubuntu12, I installed OpenStack Essex packages with qemu as hypervisor, and added few uec linux images on to glance, I was able to access linux images using ssh and vnc, it was great success.
Now, It has become very challenging to upload Windows image , it was really a night mare I tried all possible ways, searched in google found lot of solutions, but nothing worked, at last I converted WindowsXp.vdi file to WindowsXp.img using VBoxManage and added to glance, once I launch it I am getting blue screen error and windowsxp is horribly
restarting......................... So please help to resolve this issue
Your windows images (server or desktop) will BSOD without the correct drivers for the virtualization that you have chosen. Try installing the windows image with one of the drivers at http://www.claunia.com/qemu/drivers/index.html (QEMU drivers) and see how it goes.
Please note: Windows is notoriously difficult to run on any cloud not just OpenStack. In addition to the drivers, you will wrestle with image format (like you have) and initialization problems (otherwise all the images come up with that same GUIDs).