I decided to try and create an Android app using Xamarin in Visual Studio 2015. However, when I click on Debug, the emulator opens and there is only a black screen. No Android logo or anything.
I already scavenged Stack Exchange among other sites for solutions, such as checking or unchecking Use Host GPU. But nothing seems to work.
Here is a screenshot of the configuration
What could be the problem?
Thanks
Have you consider trying Samsung Test Lab? every time i run an emulator it's a pain, and it's super slow, the best way i found that works for me was Samsung Lab you can test your app on a real device i think this is the best way to test apps
you can connect the device via adb using adb connect localhost:port or adb connect 127.0.0.1:port
Related
this the screenshot of my Android Studio, I'm trying to learn flutter but I'm having issues while setting my physical device to it, android studio says loading device for hours and nothing happens, and even I'm failing to initialize ABD
As you can see on the top side of your screenshot, the android studio doesn't recognize your physical android device. Make sure that your phone is connected properly and USB debugging is turned on. also you can install ADB directly if it was not included in the Android SDK.
I have written a simple login page using xamarin forms. When I try to deploy it on emulator, the emulator opens but my app is not visible.
1) Does it take time for the app to be deployed? Or would it appear on start up?
2) Should warnings be considered? I have no errors though.
Most Android emulated devices are slow. I have found that some of them simply won't render an app. This is not an indication that the physical device, which you are trying to emulate, won't work however. Try testing what works in an emulator and then creating a copy of what works in the device manager. Then make slight changes that are closer to the target device in the copy. Deploy every time to ensure that it is working. This process takes patience. If you are fortunate enough to have the physical device, debug through the USB connection.
I've been working with React Native for about the last week on my mac. After the initial setup which was a pretty huge pain in the ass I've had no issues building my app. Of course, today all builds decide to fail and I get the following message
I run adb devices and it looks like my device has disappeared?
Debugging, etc is enabled in my settings and I've setup the android environment obviously because I've been developing like this for about the last week.
I vaguely remember using the linux setup to get it working initially
https://facebook.github.io/react-native/releases/0.21/docs/getting-started-on-linux.html
But now my device isn't even showing up when I run lsusb
I've also tried different USB cables and different ports but still doesn't show up.
Any thoughts what this could be? Thanks
I am trying to learn android on a dell device having 4gb ram and intel pentium chipset. I am trying to run hello world app on a emulator but it actually take much time(more than 5 minutes) to start the process and at the end give error message "Error while waiting for device: Timed out after 300seconds waiting for emulator to come online". As far as testing on device is considered i find it fast and easy.
So my question is that possible to always test an app on real device and skipping the testing on an emulator.
Also suggest me some tips to make my android studio run faster.
.
Its always better to test on a real device. Its very fast especially when debugging. If your emulator is taking long to load imagine a situation where you are trying to debug and want to check the app's behaviour after each change in code. Just install the usb drivers and sdk tool that your device's api version is running on
Sure it is!
First of all, enable the developer mode in your device (if it's not enabled already). Info for doing this here.
Then just plug your device via USB and it will appear when you run your project in Android Studio.
NOTE: The first time you attempt to run the project, your phone will ask for permissions, make sure you allow it!
It will be good if we are testing the application in real device rather than emulator if you have the device. But we can't buy different density, different dimension, different android version devices for testing so for that purpose we need to use emulator.
To improve the speed of android emulator install HAXM in your system, it will speed up the emulators.
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.