Its the visual studio android emulator as I 100% have to run hyper-v given my work environment. Hyper-v means genymotion and the google android emulators are not viable as they require VirtualBox and are incompatible with hyper-v, so there is absolutely no way I can use them / this VS emulator is my only option.
download virtual dj 9 for android apk
Download File
https://t.co/MI3EEW9v3N
The VS emulator didnt work at first, but adding the android studio adb version to path and a windows reg key to it seems to have worked, i.e. I can open a console and type adb devices and the virtual device is listed ok.
Expo seems to talk to the virtual device, if I open a 4.4 android and open on android device I get loads of error text in in the expo react native consol saying cant adb reverse which I later found out is supported in android 5.0.0 + devices.
Whats frustrating is I can see no log out put, no time out, or error saying cant deploy etc I have nowhere to start to try and make this work. From what I read, people have made this work with the VS android emulator so its possible.
So I made the switch to linux, after an inotify issue and adb path, it (seemingly) works fine Also, means there is no hyper-v requirement and I can just use virtual box / the standard android emulator which just works.
So here is the workaround I wanted to try: Virtual Android (Bluestack, Genymotion, ...) connected to tiktok and using the in-app streaming with no RTMP key. But feeding the virtual machine with my OBS Virtual Cam.
Problem, and I don't know why no virtual machine reconize the OBS virtual cam. Best I found was Genymotion that sees the cam as a source but can't display anything no matter what screen ration I feed it.
When I am running my android scripts on emulator(Pixel) in local device, it runs smoothly without any delay. But the same script if I try to run on my Virtual machine, the emulators are too slow. It hardly loads and runs the script. There is a huge difference in speed and performance.
Virtual machines often have limited resources compared to a physical machine, which can affect performance.
to improve the performance of emulators on your virtual machine
make sure your virtual machine is allocated enough resources such as CPU, RAM and disk space. Consider increasing allocated resources if possible.
Using Lightweight Emulators for example, you can try using the Android Emulator with x86 system images, which tend to perform better than ARM-based emulators.
You can do this, but I would not expect the emulator to perform well in such case, as nested emulation takes place there (emulator itself is also a virtual machine). Check -do-I-run-a-Android-emulator-on-a-virtual-machine for more details.
OK, I give up. With the new environment, how do I create a new virtual device? I cannot log into the original Samsung IDE website, which was always my go-to way to resolve driver issues or to create virtual devices. And there does not appear to be a user way to add one in the SmartThings Android app. I did find something about a Schema manager but that looks to be for developers, which I am not, just a user. So, how I do it now?
AVD is part of Android Studio and with this software you can virtualize Android devices. You can choose different phone models and decide which Android OS version you want to run. OS versions from 4.0 to 12.0 are available. The software is very suitable to test and validate different kinds of configurations. Some examples are: Application Deployment, Profile settings, Single Sign-On, Per-App-VPN configurations and even Device Compliance. This is great because you do not need all kinds of different physical devices!
As I mentioned earlier, the Virtual Device will boot straight into the OS and will not show the first-time setup wizard. In other words, if you want to test Company-Owned device enrollments, you will have to install a Virtual Device with Android 10 or lower. I found the blog from Roch Norwa very useful: -to-virtualize-android-devices-on-macos-and-windows-10/
An Online Android Emulator for PC replicates a browser or an Android App, on a defined operating system (like Windows, Mac). It attempts to create virtual hardware conditions of an Android device, which can be used for the purpose of testing and debugging.
35fe9a5643