I have created emulator in android studio and create little application in it. When i run it gives me an error[See image 1]. When i googled, it told me that your system does not support virtualization. But my system suport it. [See image 2].
Now my question is that when my system support virtualization then why i cannot run my app in emulator. Also please help on this following error too.
1-Intel HAXM is required to run this AVD.
2-Your CPU does not support NX.
Please anyone help to resolve this issues, thanks in advance
(Source of answer here)
First off, download Coreinfo, extract the zip in your Downloads folder, then run CMD (Not as admin), and type in:
cd Downloads
cd Coreinfo
coreinfo
Then, you should get a list of text. Scroll up/down until you find NX. If there's - next to NX, then it isn't enabled or it isn't supported. If there's * and you still get the error, then you're doing something else wrong.
Then, check if NX and VT-x are enabled in BIOS:
If not, enable it. If you don't see an option, then your CPU doesn't support NX.
After you enable it, do the first step again. You should now see *, which means NX is enabled:
Related
I was trying to install SDK and Emulator without the Andriod studio on Ubuntu 20.04.
But got stuck at this error.
E0520 11:06:29.866803544 5261 socket_utils_common_posix.cc:201] check for SO_REUSEPORT: {"created":"#1589952989.866791260","description":"SO_REUSEPORT unavailable on compiling system","file":"/mnt/tmpfs/src/android/emu-master-dev/external/grpc/src/core/lib/iomgr/socket_utils_common_posix.cc","file_line":169}
checkValid: hw configs not eq
I got the solution from this article:
So in order to fix this, I just disabled the Camera by switching the option from Emulated to None and that was all.
Don't ask why this works, but it seemed to solve it for me.
Install Android SDK Platform tools. if already exist uninstall and install Android SDK Platform tool in ubuntu 20.04
Seems a GPU issue, try :
sudo ubuntu-drivers autoinstall
Or (or both) change graphic emulated performance to software if your emulated device allow it.
Had same issue with linux mint android studio ..
Hope it will help.
Though not directly affected by the error you described, when stuck at this point (namely, when supposed to be connecting back to the ADB server, but can't), this can be a result of a corrupted quick-boot snapshot.
What worked for me is to hard-delete the existing quick-boot snapshot, and have the emulator regenerate it on the next run.
To delete the snapshots:
rm -fr ~/.android/avd/<AVD name>/snapshots/default_boot
To regenerate the next snapshot, rerun the emulator as you normally would, then kill it after if full loads. But first, make sure that it is configured for saving a quick-boot snapshot on exit:
Edit quickbootChoice.ini, for example:
vi ~/.android/avd/<AVD name>/quickbootChoice.ini
The only line there should be:
saveOnExit = true
If you wish to see whether any of this is likely to help you before making any changes, run the emulator with the -no-snapshot argument applied, beforehand. For example:
$ANDROID_SDK_ROOT/emulator/emulator -no-snapshot #Pixel_API_29 &
(Or find a way to do this through Android Studio)
A note regarding other answers here that advised configuring the camera differently (which seems unrelated): It is very likely that changing the camera setting, for the Emulator, is considered a configuration change - which ends up in forcing a cold-boot (i.e. skipping usage of the quick-boot snapshot), which can explain why it works (but with no voodoo involved).
Everything used to work fine, but I haven't been using Virtual Box for several weeks. Now all of the sudden, I get the following exception when trying to start my Windows 10(32-Bit) VM. Note - Things were working fine several weeks ago. As far as I can tell, I haven't changed anything on my system that would cause this. The exception details are as follow:
VirtualBox - Error In supR3HardenedWinReSpawn (rc=-5640)
Please try reinstalling VirtualBox. where supR3HardenedWinReSpawn
what: 1 VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification
Failure: The process has more than one thread
I have been researching this for some time, to avail. Any help would be greatly appreciated.
There is a workaround:
Open VMbox manager
Run your VM with option "Detachable start"
Wait a while and then use "Show" to show the screen
Detachable start option
Show the screen
My setup:
Oracle VM Box 6.0 running on Win10,
VM is Ubuntu 18.04
If you are using vagrant to boot up your Virtual machine, then in most cases the error is due to improper shutdown of the VM. A fix that worked for me is to execute vagrant halt or similar commands multiple times until you have a clean boot.
In case anyone is in the same predicament, I will share what finally fixed my issue. I found a post during my hours and hours of searching that said you have to enable virtualization in BIOS settings. I checked my machine and virtualization was enabled, so I went on searching. At a loss for what to try next, I finally tried turning virtualization off, just to see. No change, but when I went to turn it back on, just as a flook I turned Turbo off, and what do you know - All of the suddent I can start my VM. So the solution, in case it saves someone time:
Uninstall Virtual Box (Latest Version)
Reboot your machine and enter BIOS
Make sure anything with the term 'Virtualization' is turned on
Make sure anything with the term 'Turbo' is turned off
Reboot your machine
Install Virtual Box
Hopefully this saves some poor soul what I had to go through to get this thing working.
METHOD A
If you are using WindHawk, exit it and re-try.
Method B
download previous version from https://www.virtualbox.org/wiki/Download_Old_Builds
install & extensions
Try to re-run your guest OS.
Try to do these steps:
1. Uninstall the VirtualBox program.
2. In your C:\users\\ might have two folders called ".VirtualBox" and "VirtualBox VMs": Delete them
3. Restart your PC
4. Install VirtualBox again
5. Add again your VM
6. It must working fine!
These steps worked for me!
Workaround 1:
Just increase the RAM size from virtual box settings
Right Click on OS image .
Settings->System->MotherBoard
Increase the base memory
Workaround 2:
Change the Paravirtualization Interface from default to none
Right Click on OS image .
Settings->System->Acceleration
Change acceleration from default to none.
The above one's was basically a workaround , which can work in some but not in all.
The best thing would be to reinstall virtual box with latest version which virtual box has tried to rectify the bug and use the same vdi files which was made by Virtual Box .
One of the most common causes that will cause this type of behaviour is a missing driver (VBoxDrv.inf). It’s possible that due to some permission issues, the installation of this crucial driver doesn’t complete during the initial installation. In this case, you can fix the problem by installing the VBoxDrv.inf manually.
1.Fix the directory problem Press Windows key + R to open up a Run dialog box. Inside the text box, type ‘regedit’ and press Enter to open up Registry Editor. When you’re prompted by the User Account Control (UAC), click Yes to grant admin access.
Once you’re inside the Registry Editor, use the left-hand section to navigate to the
following location: HKEY_LOCAL_MACHINE\system\currentcontrolset\services\vboxdrv
After you arrive at the correct location, move over to the right-hand section and
double-click on ImagePath the path associated should be \C:\Program
Files\Oracle\VirtualBox\drivers\vboxdrv\VBoxDrv.sys
if not replace with the above path and click ok.
Install the VBoxDRV.inf OPen location C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv right-click on VBoxDrv.inf and choose Install from the context menu.
Then in cmd run command "sc start vboxdrv"
Restart system. This should work.
I am trying to debug some OpenGL code, so I wanted to make use of the GPU debugger from Android Studio. For this I need to get a GPU trace, according to the steps detailed at https://developer.android.com/studio/debug/am-gpu-debugger-trace.html. But, after the dialog for trace name, Android Studio shows directly the message: Failed to attach to process.
Android Studio has version 2.3, and was recently updated.
On the device (Samsung S3) I see the alert: !Waiting for debugger.. process zzz is waiting for debugger to attach.
I tried to enable all GPU related options from developer options in device settings, also to disable all, with the same result. Is this feature working? My setup is not very uncommon.
I reached to a point where I get the message: The GPU debugger does not currently support tracing on this device. So the answer would be that it does not work on S3. I'll leave the question here, maybe it will save someone a few hours of investigation.
When trying to enable Run/Debug Configurations>Profiling>Capture GPU Commands, I was required to install "GPU Tools". Then, after accepting to install, it complained that they were already installed in the folder, and I should remove them prior to new installation. So I moved them away. Then it would give the error from the question.
After some attempts, I decided to put the contents of the folder back, deselect/select again Capture GPU. It said once again that I needed to install GPU tools, but this time I did nothing. The checkbox got checked anyway, and when trying to start the trace, went on to do some stuff without complaining about the attaching to the process. Finally it did not work anyway, but at least I know the reason.
I installed El Capitan and have run into issues with loading audio units for Native Instruments. The workaround is to go into system recovery and type csrutil disable, which enable you to load an old version of the aulvaltool. I am booting off an external firewire drive, and everytime i boot into system recovery and try to use the command, it replies "command not found". I tried specifying the volume/csr/bin to no avail. Any ideas?
I am not a programmer- I just back everything up, and if I crash the drive, I just reinstall and start over..
Any help would be appreciated. Also if anyone has downloaded the new 10.11.1 beta, curious if it fixes this problem.
Thanks.
Follow these step by step instructions:
reboot
as you hear the Apple Chime press COMMAND+R
you will be in the Recovery mode
from the upper MENU select Terminal
you're booting from your internal drive recovery mode, so:
A) el capitan is on your internal drive
• type /usr/bin/csrutil disable
B) el capitan is on your external drive
• type /Volumes/TYPE_THE_EXTERNAL_DRIVE_NAME/usr/bin/csrutil disable
And you're done. Then you probably know how to proceed from the NI forum.
I have a Kernel mode filter driver project. Host: Win8 Pro x64 running VS2012, Target:Win8 Pro x64 VM on the same machine. I was able to provision the VM through VS 2012 over the network. I deployed the package project. When I try to deploy and Install the package from VS, I am not able to succeed. So I manually installed the driver and the driver works fine. After installing the driver manually, I attach to the kernel of the VM and click on Break all. I find the Kd console in the immediate window of VS '12. I type the command "bu !DriverEntry" and then I type the "g" command. I see the message Debuggee is running. When I place break points on my code and press any key in the VM, I don't see the break points getting hit in my code. Need help!!
Use Fltmc command to load and attach your filter to a specific drive
You can put breakpoints directly in VS without the need to type in the console, if your filter is getting loaded after you type fltmc load "filter name" VS should stop at the driver entry function breakpoint, you may also need to attach it.
Dont forget to check if your debugger is working by when you click break all target machine should freeze.
I wasn't able to debug through VS. I went for a work around and this time I used a Win7 VM. Made use of the KdPrint() method and used the DebugView tool to see the messages. This is a lengthy process but atleast I'm able to debug my driver. Hope this helps someone else too