I'm trying to create a virtual device in AVD, however the graphics setting is grayed out. I've been able to successfully install HAXM and have also disabled windows Hyper-V. But the option is still grayed out.
I had the same issue and the answers here didn't work. Try this:
vim ~/.android/avd/Pixel_3a_API_28.avd/config.ini
Search for hw.gpu.mode = software change it to: hw.gpu.mode = host
Now it shows correctly in AVD manager as:
You have other options too: https://developer.android.com/studio/run/emulator-acceleration?authuser=1
I don't know exactly why but sometimes images with the Google Play Store don't allow you to configure graphics. Try with another image.
Another option is to edit the emulator ini file directly - under ~/.android/avd-emulator-name/config.ini
U will see the options:
hw.gpu.enabled=yes
hw.gpu.mode=software (or hardware)
Change as needed
Related
I can not find any solution for this error when starting virtual device.
There are some similar topics here, I know, but it seems that none of them solves my issue.
I tried:
uninstall/install Android SDK Platform Tools in SDK Manager
add Platform Tools path to system PATH variable (windows)
set ANDROID_ADB_SERVER_PORT
download Platform Tools from https://developer.android.com/studio/releases/platform-tools and install it
For me extending my path helped.
%ANDROID_SDK%\emulator
%ANDROID_SDK%\platform-tools
%ANDROID_SDK%\tools
%ANDROID_SDK%\tools\bin
See https://stackoverflow.com/a/54030970/16364154
I just did this today
1>First of all disable fast restart from here
2>Then enable VT-x from here
3>Third go to your antivirus. If AVG, open the menu options and click quarantine.Else see where to find quaratine chestbox for your antivirus And then there should be something whose file name will be adb.exe. Yes, even if it it shows in the platform tools, there will be a file with file location Idead or something like that and restore it
4>Then go to your android studio and go to file in the top left corner. Click invalidate/caches and then Invalidate and Restart. Then try.
5> Also go to the sdk manager and update everything that isn't updated.
6>Should work\
If this does not work, just comment it and I will find a new way
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 have been trying for days to get a simple app any app made in livecode to display either on my tablet, smartphone or emulator. It just doesn't work. Here is what I have done:
I have installed my sdk and pointed livecode to it in preferences.
Picked 2.3 as my version
Check my google usb drivers and they are up to date.
I followed live code's step by step and no success. I am thinking that since I am running windows 7 not a Mac, maybe this cant be done. It seems all the developers run Mac's?
I even tried to make a .apk, It made the file but " There was a problem parsing the package" once I got it on my Galaxy tab. I made sure that I checked the box to allow programs to run on my tablet. So I am still stuck.
To see if the SDK is working correctly you could try to use the Android SDK emulator first.
Open the Android SDK Manager and select the menu Tools->Manage AVDs.
There you can create a virtual Android device and run it.
If the virtual device is running you can see the virtual device under "Development->Test Target in Livecode. Select it and either select "Test" under "Development" or press the "Test" button. Does this work?
That error message means that the operating system on your device is preventing the app from being installed. The most likely reason for this is that you haven't changed the "Allow installation of apps from Unknown Sources" setting on your Galaxy Tab. There are other reasons and solutions for this error message - to see them visit Panagiotis's excellent blog post on the LiveCode website, your error message is in the fifth example
https://livecode.com/how-to-deploy-apps-to-android-devices/
I'm new to Android programming. I was installing the Android studio and it got stuck at one point during installation showing the following message.
So, don't to how to proceed, I searched about it, but couldn't get explanation about this specific condition.
Can someone explain what to do next?
Screenshot:
Note: I'm using Windows 7, Installed JDK 7 before installing Android studio.
Update: I tried to click upon "Setup Proxy" and then just clicked ok without doing anything and it worked, don't know how, but it did.
Try that if any one face the same.
Add the following code to C:\Program Files\Android\Android Studio\bin\idea.properties
disable.android.first.run=true
Just open the file and press Ctrl+F and type run then you will find this run=false, change it to true.
1) click on set up proxy.
2) Select option Auto Detect proxy.
3) Click continue, it will work!!
All the best
I clicked Cancel at this screen and process of setup continued. I saw it on Linux after copying android studio folder from one PC to another. By the way, I started studio not connected to Internet cause I try to be able to work offline.
I just hit this same problem - I was on a VPN.
I tried setting a proxy with 'auto detect proxy settings' but it did not help.
Then I tried disconnecting from the VPN with no proxy set - this resolved the problem for me.
good luck.
You can set the right proxy to solve this problem.
Set proxy ->
Manule...
Https and port
Sometimes,if you use Shadowsocks on your macOS, maybe you will have the same problem.You can turn Shadowsocks off to deal with this problem.
I finally solved the problem by following the Steps:
Add the following code to "C:\Program Files\Android\Android Studio\bin\idea.properties"
Open idea.properties with notepad
Then, enter the code below anywhere on a new line in the file (see attached image)
Code :
disable.android.first.run=true
Save the file
Run the application
Clear your DNS if there is any dns server settings like google, comodo,
symantec etc.
Check your firewall settings if you are using tinywall, zonealarm etc.
If your computer and network connection doesn't have any dns settings and firewall; then check your internet connection maybe there is an update process to slowing down your internet speed. So if there is a process stop or wait for it. And try again. Good luck...
Yet another reason why this can happen is when your time and date settings are not synchronized correctly. I installed android studio inside a virtual machine linux guest that didn't properly synchronize the time with the windows host and as a consequence the above message occured even though my internet connection was working fine.
I would like to know if there is a tool simillar to mymobiler for Wince 5.0 which I can use to control the device from my desktop.
I use mymobiler (v1.25) but I believe it controls only devices running on WM5 and above.
Any help would be highly apprecited as the screen of my device has stopped working.
I use MyMobiler myself when I am coding for WinCE5.0 (not very often but I do know that it works.)
In your extracted MyMobiler zip file is three versions of remote.exe.
remote.exe
remote.exe.50
remote.exe.40
The only one I have gotten to work on wince5 is remote.exe.40
Just rename the existing remote.exe file (remote.exe.wm) [you may have to click tools, folder options, and uncheck hide extensions for known file types]
Next rename remote.exe.40 to remote.exe.
After that you are good to go. Copy remote.exe to the device through activesync (xp) or WMDC (>XP) and launch it on the device. It was a bit funny connecting for me the first time - I click connect on pc, then had to click the tray icon on the device, and click connect.
Good Luck!
Link to Video Showing it Running 1
This does work, the auto-install doesn't seem to work but if you copy the remote.exe over as mentioned (any location will do), then start remote.exe, click on the MYMobiler icon in the tray and select Connect, it will attach to your PC like the WinMobile version does.
Also, check the ini files in the MyMobiler directory. There's some details on the features/options.
I can confirm that Dave and Mike's solutions work on Windows CE 7 as well.
I was getting an error with the AYGSHELL.dll library when starting My Mobile after the gun was connected.
Run Mymobiler.exe before you connect the scanner to the PC and then connect to the PC using the tray icon from the gun. No error.