I actually installed the genymotion plugin in android studio and started the genymotion device manager.
Then it said the path isn't specified, so I specified the path to genymotion ( C:\Program Files\Genymobile\Genymotion ). After that the error happens again -
NullPointerException on opening genymotion. This image shows the error:
I think i found out the answer. My computer does not support VT-X. So obviously genymotion cant run. Also genymotion needs virtual box to run over.
Related
i just created a react native project on windows, using expo. After Creating the project i ran npm start and then expo start the next logical thing to do is to press the a button which will launch, the project on the android virtual device, but instead it gave me this error Couldn't start project on Android: Error running adb: Error running app. Error: Activity not started, unable to resolve Intent { act=android.intent.action.VIEW dat=exp://192.168.43.148:19000 flg=0x10000000 }
when i tried running it on my android phone with the expo android app it ran smoothly, i don't know what to do please help thanks
I had the same problem and I got it fixed as follows:
Go to SDK Manager in Android studio > SDK Tools and check whether there is any update for Android SDK Build-Tools. If there is any, please make sure you update it.
Close any Android virtual device currently running and then go to Android Studio Virtual Device Manager and wipe the data of your Android virtual device.
Make sure you have enough internal storage allocated for your Android virtual device to install apps.
Check whether Android Debug Bridge utility is installed in your device. If not please install it. To install in mac, I used the below command (Assuming that you have HomeBrew installed in your mac device):
brew install android-platform-tools
Start your Android virtual device ( This step should be done before running the expo development server)
In the Developer options menu of your Android virtual device, make sure USB debugging option is enabled.
Finally, try running the development server by expo start and press on the button to run on your Android emulator.
I have a Nativescript application that I'm developing using VS Code and have no issues when I try to run it using the Nativescript launch configurations from the Nativescript extension, when I'm using a real device connected with USB or when I use one of the android-sdk emulators.
Now I need to run Hyper-V on the machine too and those emulators cannot run when hypervisor is on. So I downloaded and installed Visual Studio Android Emulator which runs fine when I launch it manually.
Problem is that the nativescript project doesn't recognize this device either with tns device or adb devices commands and if I try to launch the application from VS Code it tries to launch one of the other emulators, which obviously fails due to the hypervisor/Intel Haax incompatibility.
Did any of you had this problem before and have any solutions you can share?
Thanks.
Microsoft MSDN say :
If the emulator is running, but it does not appear to be connected to ADB or it does not appear in Android tools that make use of ADB (for example, Android Studio or Eclipse), you may need to adjust where the emulator looks for ADB.
The emulator uses a registry key to identify the base location of your Android SDK, and looks for the \platform-tools\adb.exe file under that directory.
Here We Go!! Step By Step ;)
Copy Your ANDROID SDK PATH for me it look like this :
To modify the Android SDK path used by the emulator:
Open Registry Editor by selecting Run from the Start buttons context menu, typing regedit in the dialog box, and choosing OK.
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Android SDK Tools in the folder tree on the left.
Note : if Android SDK Tools folder doesn't exist, Create it under WOW6432Node, And open it, And Create a String Value name it Path:)
Modify the Path registry variable to match the path to your Android SDK.
Restart the emulator and you should now be able to see the emulator connected to ADB and associated Android tools.
Now! Open Your Terminal (CMD), and Run ADB command
adb devices -l
YES YES !! The Visual Studio Emulator is running, and connected to ADB!
HERE WE GOO !!
Now We Want To Create A Demo App (for example FIRSTZAKI) ZAKI is my nickname :p
On Terminal (CMD) :
tns create FIRSTZAKI
Choose Android Platform
cd FIRSTZAKI\
tns platform add android
Check if VS EMULATOR is ready!
tns devices
YES YES ^^
Finally Step (RUN/BUILD) :
tns run android
WOW ... Great :)
AND .. Good Luck ♥ — ZAKI
I have installed sdk with ide for webOS TV. I have installed emulator and run it before running webOS TV IDE. However doesn't matter how I try I can't connect to emulator devices. I have the following error:
First, you must run the .vbox file (LG_webOS_TV_Emulator) from Emulator installed directory folder.
If you are using windows OS for example, directory
C:webOS_TV_SDK\Emulator\v3.00\ (.vbox) file
then you can connect to emulator
I run into the same problem, cannot connect the emulator into the IDE. So I've tried to skip this step.
First I've exported my project into .ipk file and then using the "menu" button on the emulated remote control, installed it directly via "App Manager". App was working fine this way.
Funnily enough, after this "workaround" the connection error was somehow fixed within the IDE.
I wanted to test out the Visual Studio Emulator for Android, so I grabbed an example project (https://code.msdn.microsoft.com/hello-jni-Android-790ab73d#content). Unfortunately, I can only select 'No devices available' respectively 'Android Virtual Device Manager" under Target Device.
When I start the emulator from the menu (Extras - Visual Studio Emulator for Android), it works fine - Visual Studio just somehow can't see it.
I tried to restart VS while the Emulator was running, but that also didn't help.
adb devices -l correctly lists the running emulator, btw.
Does somebody have any idea what could be wrong?
I had the same type of issue on my environment. I checked registry key "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Android SDK Tools" location and "Android SDK Tools" Key didn't exist. I created the Key and add String Value called Path and I provided Android SDK Tools path. It solved my issue. It is worth to shot.
Turns out I didn't get the message that the emulator only supports the debugging of x86 images - I changed the target platform to x86 and now it is working.
(Btw, I very quickly got the answer from a friendly Microsoft Employee after I sent them an email - Worth mentioning, I'd reckon)
I've built my application as an x86 native app, and I've ran it on Genymotion. The problem occurs when I try to debug from Eclipse. In the console view, I get the age old:
gdbserver output:
run-as: exec failed for lib/gdbserver Error:No such file or directory
Verify if the application was built with NDK_DEBUG=1
It all works fine with ARM builds though. I checked that the x86 gdbserver is getting included in my .apk lib/x86/gdbserver. I've also read that the x86 versions of android include a gdbserver locally anyway, so not sure what the point of all that is.
I've been able to manually attach the included gdbserver using adb shell, and then get Eclipse to attach to it remotely using this is a starting point: How to get ndk-gdb working on Android?
It doesn't mention anything about x86 or Genymotion though. Unfortunately, it's tedious, and it's seemingly useless since it doesn't load any symbols (though that's probably because of my ignorance.)
Is there any guidance for making this setup, using Eclipse and Genymotion to debug native apps, work?
Sadly, this is due to a bug in Genymotion v2.2
It will be fixed on our next release (I work for Genymotion).
You are right, gdbserver is not deployed from the apk, and this is why it doesn't work.
You can find here a patch to apply that will fix this apk deployment bug for Genymotion KitKat devices created with Genymotion 2.2: native-debug-fix.kitkat.zip
Warning this patch is only for:
Kitkat (Android 4.4.2) devices
created with genymotion v2.2
Don't apply the patch on other devices, it will brake things.
to apply the patch, simply drag n'drop the zip file on genymotion.