I am using fedora distro.
I went to create android emulator in android studio, but i got that /dev/kvm not found!
I tried to install kvm but still same.
Any one can help me ?
You need to enable KVM, from the BIOS by pressing F1 key before the system boot. Next, go to the Security tab and enable Intel Virtualization Technology and Intel VT-d Feature. Save the new settings by pressing F10. Finally, exit and restart your computer.
I am unable to install Android Emulator Hypervisor Driver for AMD Processor.
It is to be noted that virtualization is enabled.
Emulator Process for AVD was killed shown while running the code in Visual Studio while trying to install the Hypervisor Driver in Android Studio.
Error is also shown in Android Studio while installing the Hypervisor Driver:
What to do now? Thanks.
If you are using AVAST antivirus, It will not work .. So open Avast antivirus UI and go to Menu / Setting / troubleshooting and clear the tick on (( Enable hardware-assisted virtualization )) and restart. It will be installed.
First you should try to see if you have Hyper-V enabled. In most cases, the newer computers use it for hardware acceleration but it doesn't share with other virtualization apps, so to run this on an AMD or Intel VT-x first check if you have Hyper-V installed (go to your control panel, then in Programs and Features window, click “Turn Windows features on or off.” then look for Hyper-V and clear the checkbox then click OK.
If that doesn't work check your BIOS permissions, you can go to advanced CPU configuration or chipset and
find the "Intel Virtualization Technology", enable this option,
or
on AMD enable the SVM
then Save and Exit.
If you are using AVAST antivirus, It will not work .. So open Avast antivirus UI and go to Menu / Setting / troubleshooting and clear the tick on (( Enable hardware-assisted virtualization )) and restart. It will be installed.
This method by Tamer works for me but you have to restart your computer for it to be effective.
I had the same challenge when trying to add Bluestacks as an emulator in Android Studio and this was my solution.
Open PowerShell as Admin and do this command:
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V
A restart should follow and all should be fine.
I'm not sure why you tried installing an AMD Virtualization driver for your Intel-CPU. As other people already suggested, try to install the Intel-Driver instead.
The installation probably failed because the program detected your not using an amd-cpu, so there's no point in installing it.
I have a fresh install of 18.04 SERVER installed on an Advantech SBC. 16.04 Server was working find but on 18.04 Server when I do a:
sudo shutdown -r now
The system starts the shutdown but stops with the last status line:
[ OK ] Stopped LVM2 metadata daemon.
I've tried some different bios configurations with power management but I can't seem to get it to restart. Only option at that point is to physically kill power and power up.
Anyone seen this? Any ideas on what to try?
On my SBC setting the South Bridge USB Configuration for Windows 8.x compatibility resolved this issue. Seems that the V4.15 kernel interactions with hardware are different enough to have caused this problem.
I am trying to run an app from Android Studio on my Ubuntu laptop.
I have enabled USB debugging, but it is still not working.
When I press run in Android Studio, it does not detect my device (LG G3 Lollipop).
I could not find any help :(
First of all,
Open terminal and do following:
Do lsusb command to check your device is indeed connected.
Do adb devices to check if your device is connected then it is detected as in adb mode.
2.a. if the above command is not found, do sudo apt-get install android-tools-adb and then check if it is listed.
Secondly, post results of step 1 and 2 with your question to help us in finding a correct solution.
Troubleshooting:
Make sure adb mode in enabled.
Make sure you have opted for Allow option when prompted for in your device upon connecting to your ubuntu system.
This one is from some past LG users, Try connecting your device in PTP mode rather than MTP mode, it surprisingly works.
If it atill doesn't work, (most likely your case), try googling. I landed upon this page by pressing I'M FEELING LUCKY, you should try to feel lucky once in a while.
Source for step number 3 and 4
follow the steps as mentioned upon page:
Create a file: /etc/udev/rules.d/70-android.rules.
Write: SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666" to the file.
Assign proper permission via sudo chmod a+rx /etc/udev/rules.d/70-android.rules
Reboot the system and restart udev.
As a second step of troubleshooting (make sure you again repeated troubleshooting from step1 in case you failed at this step)
Again, the process:
Create a file: /etc/udev/rules.d/51-android.rules.
Write: SUBSYSTEM=="usb", ATTR{idProduct}=="1004", MODE="0666" to the file.
Assign proper permission via sudo chmod a+rx /etc/udev/rules.d/70-android.rules
Reboot the system and restart udev.
Make sure you have adb installed in your ubuntu system.
If not then type -
sudo apt-get install adb
Provide your system password and press 'Y' asked during installation process.
Then disconnect your device through USB and then reconnect it.
You will have to grant permission for debugging which prompts on your device just after reconnecting.
I faced the same issue but it was my mistake. I didn't turn on the " USB DEBUGGING MODE ".
Settings > Developer Option > Enable USB Debugging Mode.
Try to revoke USB debugging authorizations and then connect your device, it should show permission prompt for authorization.
go to
settings -> developer options -> revoke USB debugging authorizations.
I tried restarting adb using root priviledges and it worked for me. Use these commands in the terminal:
sudo adb kill-server
sudo adb start-server
Hope it works for you too...
For my situation with Ubuntu 16.04, with my device properly connected via USB, confirmed by lsusb
The solution is let the Studio aware of the Android/Sdk folder by defining
export ANDROID_HOME=<the Android/Sdk folder>
in ~/.bashrc
(I have installed the SDK at a custom location)
Then start a new shell, from there re-start the studio, then it works.
I solved with this: https://stackoverflow.com/a/37109216/5081063
If the problem is only on Android Studio and not in your OS you can solve with that.
So first check if adb recognize any devices with:
$ adb devices
If yes, open Android Studio and follow these steps:
Go to Run > Edit Configurations...
Under Deployment Target Options select Show Device Chooser Dialog from the drop-down-list
if you are doing it first time in Ubuntu Linux, then Use sudo apt-get install to install the adb package. This gives you a community-maintained default set of udev rules for all Android devices.
or, use
sudo adb kill-server
sudo adb start-server
and check using
sudo adb devices
you can also check uncheck the usb debugging option, in your developer option in the phone.
follow this link for more info.
Run apps on a hardware device
Enable USB Debugging from Settings->Developer Options
Enable Developer Mode by clicking on build number several times
My device appeared as unrecognized and when I ran adb devices fom android-tools directory it said: adb not a command. Strange. So what I did is installed adb tools additionally and then run adb devices:
sudo apt-get install android-tools-adb
89LY0810Y unauthorized
Then I saw the dialog on my device and selected: Always authorize.
Please make sure your device is in debug mode.
If you have tried many terminal commands to connect your physical device to android studio in ubuntu and you failed to connect try this :- Connect your device and change your USB preference(device notification) to PTP,android studio will detect your device.see this image
I had the same problem, as I had enabled the USB Debugger but it was my first try so I didn't know what to expect. If you answer "yes" to "use as storage device," you will set it to mtp, if you answer no, after that you will have the option to connect on debug mode and it will appear.
I was using a Samsung A31 and Debian
After trying a lot of different solutions, I notice that the problem was my cable, so I changed it and now it works.
Thanks to RazorHail Answer.
I have been trying maybe weeks now to figure out how to configure VirtualBox to have 1366x768 resolution on a linux guest, which is on a windows 8.1 host.
My configuration:
Windows 8.1 as host
Linuxmint 17.1 as guest (tried ubuntu and debian too but no luck)
Virtualbox 4.3.26 and its extension pack
Laptop is powerful with 16GB ram and 4GB Nvdia
My problem is that it doesn't matter what I used, nothing worked.
Please do not post the answers on most known websites, I tried them already.
Once your VM is started, you need to run the VBox Linux Guest Additions.
First try to run it from the VirtualBox window's menu:
Devices >> Insert guest Additions CD image...
and follow the instructions.
If that fails, open a terminal and go to the directory where you CD reader is mounted (/run/media/ on Fedora or /media/ on Ubuntu for example).
Then type command sudo ./VBoxLinuxAdditions.run
Complete instructions can be found on the VirtualBox user manual
Once Guest Additions are installed, reboot your virtual machine. You should be able to resize your screen to your heart's content.
I installed the new VirtualBox 5.0.0_BETA2 and it solved my all problems. Great product is getting ready! Cant wait the latest release. more than a PERFECT software. Now you can remove top bar and/or bottom bar easily. Show what you need.
If you are having problem like me with 1366x768 I recommend you to install latest versin of VB even if it is Beta!