I have Android X-86 installed on Virtual Box as Virtual machine on my Windows 7. I am using Bluetooth dongle to access the Bluetooth on my VM. But I cannot turn on Bluetooth from menu. When I start Bluetooth app, it just says
Turning on Bluetooth...
and does nothing.It was working fine till the last time I used it but it stopped working suddenly.I have created VM using the following steps:
Set the type of guest OS as Linux instead of Other.
After creating the virtual machine, set the network adapter to 'Bridged'.
Start the VM and select 'Live CD VESA' at boot.
Now you find out the ip of this VM. Go to terminal in VM (use Alt+F1 & Alt+F7 to toggle) and use the netcfg command to find this.
Now open a command prompt and go to your android install folder (on host). This is usually C:\Program Files\Android\android-sdk\platform-tools>.
Type adb connect IP_ADDRESS
Plug in USB Bluetooth dongle.
In VirtualBox screen, go to Devices>USB devices. Select dongle.
Moreover I have found similar questions however nothing has helped yet
Bluetooth does not work in Android x86 on VirtualBox
USB bluetooth in Ubuntu 12.04 on Virtual Box
Any ideas how can I use blue tooth dongle on Vm would be really appreciated
Successfully verified on:
Ubuntu: 16.04
Virtualbox: 5.0.24
Android x86: 4.4-r5, 5.1-rc1, 6.0-rc1*
Bluetooth USB Dongle Tested:
PASSES: Cambridge Silicon Radio CSR8510 A10 [8891]
FAILS: Broadcom BCM20702A0 [0112]
To be able to do the following:
Android -> Settings -> Bluetooth -> On
You need to physically attach the Bluetooth USB dongle to the Host and virtually attach it to the VirtualMachine before starting it up the VirtualMachine.
*NOTE: For Android 6.0-rc1, you can virtually attach the bluetooth USB dongle (and do a Android settings bluetooth enable) after boot up.
Virtualbox -> AndroidVitrualMachine -> Settings -> USB -> USB+ (Button icon with the balloon help that says - Add new filter with all fields set to the values of the selected USB device attached to the Host PC.)
I have verified this which included running the nRF Master Control Panel Android app and scanning for Bluetooth LE devices on the AndroidVirtualMachine.
When you start up the VM, under Devices in the VirtualBox window that opens, ensure that under USB Devices there is a checkmark next to your bluetooth dongle device.
If it is not checked, and warns you that the device is in use already when you try to check it, unplug the dongle and plug it back in while the VM is still on the initial blue boot-up screen. This must be done before the Android has booted up, or it will not work.
Related
I am working on developing an app for Android that requires a bluetooth connection. I currently have the most recent version of android x86 installed using virtualbox on my linux mint 18.3 OS. Everything is working fine except one thing, bluetooth.
When I go to turn the bluetooth on, it says it is on temporarily, but then shuts off when I go back to the bluetooth settings.
Image of bluetooth settings turned on
Bluetooth settings after returning to general settings
As you can see, the bluetooth doesn't actually turn on. I have ported my laptop's integrated bluetooth to virtualbox, and my output from hciconfig -a is as shown below:
I really would like bluetooth to work so I can properly test the app, any help is appreciated!
I have the same problem with VirtualBox and androidx86 under windows 10 with a USB stick Cambridge Silicon Radio and
found this page
http://andex.exton.net/?p=726
which states
Bluetooth doesn’t work. (You can enable Bluetooth and see units though).
I would try with a hd install without Virtual Box.
bye
I am trying to run and debug android project using hardware device. I have Huawei P8 Lite and whenever i enable developer mode and usb debugging from my phone, it shows the message that usb device not recognized. It happens just when i enable usb mood on developer options, otherwise its working fine if i want to transfer files between computer and phone.
I followed all these articles
http://developer.android.com/tools/device.html
http://developer.android.com/tools/extras/oem-usb.html
and also tried to update the driver software but computer shows that driver is updated.
IN device manager, under options universal serial bus controller, the usb port have yellow notification mark on it with the label that unknown device.
Please help. Emulator is killing me. Its very slow even after installing HAXM.
Hi those instructions are for the google usb driver. To install the huawei adb driver and lte software, on your device (settings):
Enable Developer Mode.
Enable USB Debugging.
Connect your device via a usb cable.
You have to go to Computer -> double click on HiSuite
Accept terms and click install. This should take about 30 seconds, after which you click start.
Automatically, all drivers are installed as below.
The instructions are available on http://consumer.huawei.com/en/support/faqs/detail/index.htm?id=6630
My breakdown according to my device (and country) and the link above are slightly different but the logic is the same. All the best!
I have a very specific problem. I am trying to create an Android app for educational purposes, together with a friend of mine. The problem is, my processor does not support VT-x, which is essential for using an AVD, and my Android phone is considerably old so it can't really take much.
Therefore, the one solution I have in mind is using VirtualBox to create a 32-bit Android Virtual Machine and test my app there.
The problem is that, unlike an actual Android device and an AVD, a VirtualBox Android VM does not have, for what my knowledge is, an obvious way of being connected with Android Studio for testing each new app build.
So, what I am asking for is exactly that: a way to immediately test the app I have written in Android Studio in my Android Virtual Machine I have created on VirtualBox, including any workarounds that effectively allow me to immediately test the app on the VM, other than finding a way to make adb work with it.
I see I'm a bit late on this one but I figured it out. I am using Windows 8, running Android x86 (4.4 r1) on VirtualBox.
1. Set up a Host-Only adapter so that the VM has access to your network; You can set this up only when the Android image is off. Basically just go into your settings, click on Network, and select Host-Only Adapter in the drop-down labeled Attached to. For Adapter Type select PCnet-FAST III. Check the box next to Cable Connected if it isn't already.
2. Set up an NAT Adapter by selecting a different Adapter tab and for Attached to select NAT. For Adapter Type select PCnet-FAST III again. Check the box next to Cable Connected if it isn't already.
3. Enable Developer Mode by starting up the Android image, then going to Settings > About phone/tablet > Build Number. Click on Build Number 7 times. You should see a pop up that tells you how many more times you need to click to get into Developer mode. Credit to RMP PianoTuning's answer below
4. Get the virtual Android's IP address by going into Settings > About phone/tablet > Status > and then scrolling down until you find your local IP Address. Remember this number, you'll need it for the next step.
5. Start up Android Studio and go into the console; it should be one of the options in the bottom-left corner. Type in adb connect (IP address from step 4). Take a deep breath and hit enter. If it says
connected to (IP address)
you are ready to rock! When you run the app within Android Studio, your virtual Android should appear as Innotek GmbH VirtualBox, or something like the same. Select that puppy and enjoy your new, easy-to-test-on emulator. Its even Bluetooth Compatible! (but thats a whole 'nother story... google it)
Now a virtualbox isn't an answer to your need.
here are some alternatives,
Genymotion http://www.genymotion.com/ which is an easy to use android emulator , i suggest you look into it. based on virtualbox , can be integrated into android studio with ease . needs an AMD-V proc if not a VT-x . If the processor does not support these, the emulator still works, but your emulated device will only be able to use one CPU.
The other option is adb over wifi, which will let you use your phone without doing the dropbox step http://forum.xda-developers.com/showthread.php?t=1685736. For this to work you will need root though.
I was able to follow OMiKeY steps and get my app to run in VirtualBox,
the part he leaves out:
In your Android simulated device, you have to enable Developer mode.
Goto 'Settings' -> About Phone/Tablet->Build Number.
click on Build Number 7 times.
For me I got pop up that told me how many more times I needed to click to get into Developer mode.
After that i re ran the adb connect XXX.XXX.XXX.XXX command
Here's how it works for me.
I just connect my android phone with USB to my host (Windows 10).
Then make sure the USB phone is found from within the guest OS (ubuntu desktop 18.04 in VirtualBox 6.0). (VirtualbBox app: Devices > USB > check the USB corresponding to my phone). Once it's recognized by ubuntu, there will be a phone icon showing up on the desktop screen.
Next, I start android studio (v3.3.2); once that is complete, from the Terminal window (Android studio: View > Tool Windows > Terminal), I type in: adb devices, which would list the devices attached and my phone is on the list.
Now I run the app for a test (monitor my phone and confirm if there's prompt)...and the app shows up on my phone. Hope this may of help for others.
If you are running Windows, open the specific port in Firewall. In VirtualBox in your Android instalation Settings->Network Adapter 2 Tab - Port Fowarding and create a rule with Protocol (TCP) - Host IP (Your IP) - Host Port (in my case 5555) - Guest IP (Same Step 4 - Check your IP ) - Guest Port (I put the 5555 too). Ok! Now I can run my Apps in VM.
AppData\Local\Android\Sdk\platform-tools>adb connect 192.168.0.101
connected to 192.168.0.101:5555
Running devices:
innotek GmbH VirtualBox
:-)
I've tried everything, when I run 'adb devices' on my new HP Envy Windows 8 laptop I get a blank 'list of devices attached'. I've reinstalled the USB driver for the phone (Samsung Galaxy s3), I've set it to developer settings. The only clue as to what is wrong is when I performed troubleshooting on the hardware and devices control panel it said I have USB 3.0 ports and a USB 2.0 device. Though I read that the ports would be backwards compatible. Any ideas?
2014-April: I agree this is an issue with Windows 8 / 8.1 and this approach was only successful by happenstance.
On my Win8.1 system, even with Samsung's official driver installed (see link below), my SGH-I727 Galaxy SII Skyrocket would not connect over USB - neither with MTP nor PTP enabled on the device under Settings > Storage > [press menu] > USB Computer Connection.
I ended up doing the following, while the phone was untethered, and after installing the Samsung driver:
Open an elevated CMD prompt, if logged in as a non-admin
Type: set devmgr_show_nonpresent_devices=yes [press enter]
Launch DEVMGMT.MSC
Clicked VIEW > enabled SHOW HIDDEN DEVICES
Expand Universal Serial Bus controllers
Right-click uninstall all entities that appeared in gray [gray = not present]
Expand System Devices and repeat removal of non-present devices.
[NO REBOOT WAS REQUIRED at this point]
Plugged the phone into a standard USB port - still unresolved
Plugged the phone into a USB 3.0 port - device was recognized and installed itself
There is now an entry under Universal Serial Bus controllers named "SAMSUNG Mobile USB Composite Device". The driver tab for that entity is dated 02-Jan-2014 with version 2.11.7.0 from "SAMSUNG Electronics Co., Ltd." Note this version is different than the one downloaded directly from Samsung (see link below) which is 1.5.14.0.
There are now also two new entries under Portable Devices: "MTP USB Device" which is presently gray despite the device being currently connected, and "SAMSUNG-SGH-I727".
Windows Explorer now shows a device named "SAMSUNG-SGH-I727" and, when opened, shows both "Internal Storage" as well as "SD Card" directories.
ALSO NOTE that the phone has to REMAIN UNLOCKED, in order for Windows Explorer to provide access to the aforementioned directories. Most smartphones will block access to these directories, when the phone's interface is locked due to your security preferences. In other words, ensure you swipe or enter your passcode and remain seeing your phone's main screen, while trying to view its directories via tether.
Samsung Driver [version 1.5.14.0]:
www.samsung.com/us/support/owners/product/SGH-I727MSAATT
Are you mounting the device as a camera?
In other words, head over to Settings > Storage > "Usb computer connection" (via the ActionBar) > Camera (PTP).
Make sure the Samsung drivers are installed. Power off your phone. Power on the phone in Download mode. (Volume Down + Home + Power) Press Volume Up to continue. Once it's in Download mode, plug it into your computer. Windows should now discover it and load the driver. Once this is complete, unplug the phone from the computer, and pull the battery out of the phone to get out of Download mode. Replace the battery, and power on the phone like normal. It should connect to the computer properly.
this from this thread
http://forums.androidcentral.com/verizon-galaxy-s-iii/286104-s3-wont-connect-via-usb-my-computer.html
the problems will be related to the driver i face problems like this with my android device connecting to my pc
I had a similar problem (samsung note 3, hp win 8.1). When plugged in, the phone would constantly connect and disconnect. I tried 3 things - delete the whole driver from device manager (did nothing), swap from USB 2.0 port to usb 3.0 port (may have been part of getting it working) and changing one drive settings.
One drive has a setting to sync data across all devices. It appears that windows trying to grab sensitive data from the phone was causing it to reset the connection. When I turned that off I got a stable basic connection.
I may be the only one, but I am creeped out that MS takes every opportunity to behave as spyware.
Good luck, I hope that helps
How can I run Bluetooth Based application on Android emulator on my laptop. When I run the Bluetooth application, it's said, Bluetooth Device not connected. I was googled and I found a way for using Oracle VM VirtualBox. and I followed this steps too,
Download Androidx86 from http://www.android-x86.org/. This is an .iso file, so you'd need something like VMWare or VirtualBox to run it. Me, I use VirtualBox.
When creating the virtual machine, you need to set the type of guest OS as Linux instead of Other.
After creating the virtual machine, set the network adapter to 'Bridged'.
Start the VM and select 'Live CD VESA' at boot.
Now you need to find out the ip of this VM. Go to terminal in VM (use Alt+F1 & Alt+F7 to toggle) and use the netcfg command to find this.
Now you need open a command prompt and go to your android install folder (on host). This is usually C:\Program Files\Android\android-sdk\platform-tools>.
Type adb connect IP_ADDRESS
There done! Now you need to add Bluetooth. Plug in your USB Bluetooth dongle.
In VirtualBox screen, go to Devices>USB devices. Select your dongle.
Done! now your Android VM has Bluetooth. Try powering on Bluetooth and discovering/paring with other devices.
Now all that remains is to go to Eclipse, and run your program. The Android AVD manager should show the VM as a device on the list.
I did this and it's working fine. but the problem is, if I use Bluetooth Dongle it's working good, but I can't use my Laptop's inbuilt Bluetooth device with VM Machine. How can I connect my inbuilt Bluetooth device with VM Machine and how can I use it for Test Bluetooth Based Application.? Kindly suggest some ideas. thanks in Advance..
In the Virtual Box :
right click and go to settings
select Serial Ports and Enable it
click Ok.
Now click Start
Select Devices from Top Menu
Select USB Devices
Select your Bluetooth Adapter
that's all. now You can use your Laptop Bluetooth for VM.
In addition to the steps in RamRaj's answer, the VM's Bluetooth adapter requires an exclusive connection. No other devices may be paired on the laptop—otherwise the connection attempt will hang.
If the connection is successful, you won't be able to manage Bluetooth within the laptop (host) OS for the duration of the connection.