Xamarin Android Player (Device Manager) does not show any device - android

I installed Xamarin Android Player a few days ago.
I installed Oracle VM VirtualBox, Xamarin for Visual Studio,...
I installed anything that Xamarin needs to work.
When I run Xamarin Android Player, I don't see any devices to download or update or install!
Here's a screenshot:
What should I do now?

I had the same situation.
In my case my system drive C:\ was lacking free space and when I cleaned it up a little bit to have at least 4GB free space, suddenly list was full of devices to download.
Yes, I know that this is a strange behavior...

Try it again with other client IP address. Maybe your IP is not available for download.

Related

How do I run Udemy app on any emulator?

I've tried on at least 8 different current android emulators to install and run the Udemy android app, but in all of them I get "This app is incompatible with your device," in PlayStore.
I have some courses in Udemy that I'd like to download with subtitles and currently the only way that I know of of doing that is by downloading them in android. I don't own a smartphone.
One thing I've found common in all the latest emulators is that they all emulate some sort of tablet and not a phone, as I can see in settings that all of them have "About Tablet" at the bottom.
I was hoping if someone could tell me of any emulator that's based on a phone (preferable a Samsung one) rather than a tablet. Or any other way I could change the emulator to show as a phone in PlayStore?
I know this was posted some time ago and I am not sure if you came right, but the only way I have managed to get it working is by installing Android in a VMWare Player virtual machine.
The steps I used are as follows:
1) Downloaded the Android ISO from http://www.android-x86.org/download (I downloaded the android-x86_64-7.1-rc2.iso)
2) Downloaded VMWare player from www.vmware.com
3) Followed instructions on here https://www.tactig.com/install-android-nougat-vmware/
It is possible to install on Virtual box from what I see, but I have never tried it. Instructions are here: https://www.avoiderrors.net/install-android-7-0-nougat-virtualbox/
From there I was able to install the latest version of Udemy, only message I got was that it was not optimized for the device.
Hope this helps.

Xamarin android emulator error: App not installed

I am trying to install app on a Nexus 4 virtual android 5.1 on Xamarin Virtual machine. If i want to install an app, I mostly get this error: App not installed (don't get this during some installations but 95% get this error).
I did ofcourse lots of research and testing.
Install Android studio their VM. Same error.
found some potential solution here
*Reboot the phone: In times like this, first thing to do is to reboot your device. Or just shut down, remove and reinsert your battery. Done and no luck
*Make sure to uninstall any apps you don’t use to free up space, also uninstall previous versions of the same app currently installed on your device.
I download them all for the first time via APKpure.com
*Double check the apk files you download and be sure they were completely copied or downloaded. App are released by companies their self and are fully downloaded
*Try resetting app permissions by going to Settings >Apps>All>Menu key >Reset application permissions or Reset app preferences. Done and no luck
*Change app installation location to Automatic or Let system decide. don't know how this is possible without a root
*Make sure your SD card is not mounted or connected to a PC or elsewhere. no Sd card
*For worst case scenarios, format your SD card – copy it’s contents somewhere else for backup and format. no Sd card
*The last solution would be to totally wipe your device. Either by doing a factory reset under Settings or by doing a full wipe in recovery mode. I even reinstalled Xamarin
Downloaded an android 4 version, no luck.
I found lots of post where they were talking about signing. I did not change the APK files and I never managed to install them before.
downloaded never Nexus device with A5.1 and still same error.
Help is much appriciated.
I've always had problems with Xamarin Android Emulator.
Please use the Android Emulator (AVD) instead which contains less bugs than the Xamarin one.
Click here for a guide on using the Android AVD.
And in the meanwhile, you can report the bug here to Xamarin with any relevant information such as logs and errors seen during app deployment.
The problem seemed to be an compatibility issue with lots of apps. I was able to retrieve the Logcat and after looking at the logcat, that was our only conclusion.

Why does Genymotion insist upon OpenGL support when Virtual Box doesn't, and how to work around?

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.

Android Emulator is Blank

I have a mid 2013 Macbook Air (so I should have the resources to make the emulator work) and I'm trying to get the Android Emulator working. It's been half an hour and the color pinwheel continues to spin. In the meantime I looked up and downloaded Andy and BlueStacks Android emulators but Andy was nothing more than a clock with no buttons and BlueStacks, while it had a number of options there was nothing that seemed evident that I could get 'Hello World' running from the basic tutorial.
http://developer.android.com/training/basics/firstapp/running-app.html
I want to progress but I'm stuck. Thanks.
I would look into Genymotion. They have a great android emulator that can spin up vms for different phones. Its free for personal use and easy to use. The VM image is download directly from their server so when it gets corrupted you can delete it and add it again.
It is also recognized by Eclipse and Android Studio.
There should be two downloads, one that includes Oracle VM and one that doesn't. I recommend the one that does so you do not need to install Oracle VM by its self.
If that doesn't work post a comment and ill see what I can do.
try restarting your computer..
When you start an emulator you should "Store a snapshot for faster performance" in the Android Virtual Device (AVD) configuration or the emulator won't start at all. After too much time troubleshooting, it was as simple as that.

Android SDK Emulator won't load

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.

Categories

Resources