Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I frequently switch between using my Galaxy Buds with my phone and computer. I've found the most trouble-free way to do this is to turn off bluetooth on one device and switch. What I would like to do it simply create a Windows 10 batch script that turns on bluetooth (if currently off), and connect to my buds. Is there any easy solution? It would save me like 4 clicks but I think I would appreciate the convenience.
You can use pnputil to disable or enable your Bluetooth driver using the pnputil driver servicing tool. As for specifically connecting to a bluetooth device through CMD, as far as I know, I don't believe that it is possible but I believe that you can in powershell.
(Looking at the Blutooth diagnostic files under C:\Windows\diagnostics\system\Bluetooth, they are all powershell and running it, may reset the driver, so it should be possible to use part of that code.)
# scan bluetooth devices
pnputil.exe /enum-devices /class bluetooth
# ... a long list of Bluetooth related items.
# Look for something like:
Instance ID: USB\VID_0CF3&PID_E500\5&2a9042b0&0&4
Device Description: Qualcomm Atheros QCA9377 Bluetooth
Class Name: Bluetooth
Class GUID: {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}
Manufacturer Name: Qualcomm Atheros Communications
Status: Started
Driver Name: oem41.inf
# Disable this device:
$ pnputil.exe /disable-device "USB\VID_0CF3&PID_E500\5&2a9042b0&0&4"
Microsoft PnP Utility
Disabling device: USB\VID_0CF3&PID_E500\5&2a9042b0&0&4
System reboot is needed to complete configuration operations!
Take note of Device ID!
To re-enable:
$ pnputil.exe /enable-device "BTH\MS_BTHBRB\6&6d7d961&0&1"
Microsoft PnP Utility
Failed to enable device: BTH\MS_BTHBRB\6&6d7d961&0&1
Device is pending system reboot to complete a previous operation.
Don't listen, instead go into settings and toggle the Bluetooth flip a few times.
UPDATE: 2022-11-29
Strangely enough after having rebooted once, and now running the same pnutils commands in admin shell, I no longer get asked to reboot.
For completeness:
When Bluetooth USB device is disabled.
When Bluetooth USB device is enabled, but BT switched OFF.
When Bluetooth USB device is enabled, but BT switched ON.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed last year.
Improve this question
I have bought today a NodeMCU v2 (I think).
I connected my NodeMCU to my laptop with a microUSB to USB cable, the same one that I use to transfer photos from my phone to my laptop. The laptop simply does not show me the NodeMCU while connected (I am running Windows 8 for reference). It makes the little sound when I plug it in (also a small blue light flashes once) or out and the Wi-Fi AI-THINKER_2CD750 appears in the Wi-Fi tab.
It doesn't try to install the drivers or anything, nothing happens. I tried to install the drivers myself from the github page, that did not work either, it says that they are preinstalled.
It happened to me too. For me The board was bad. After replacing with new one it was working with same drivers
I had to install the driver for the NodeMCU manually: https://github.com/nodemcu/nodemcu-devkit/tree/master/Drivers. Afterwards, it worked.
I had the same problem on a Mac (Big Sur) and Windows 10. Tried everything. Saw this about the USB ports, still no love. Then I swapped out the cable for giggles and it worked. So much time wasted. I used the cable in the past and it worked, also it powered on the device so I was lured into a false sense of security. Anyway, swapping out the cable did the trick. Test a second cable even if you think you are sure the cable is not the problem!
Okay, I faced a similar error where my NodeMCU was being detected as a faulty CP2101 device.
I tried to install the NodeMCU drivers but it didn't work.
Then I landed up using this link: https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers to install the CP210x Universal Windows Driver.
This was installed correctly and I was able to use the NodeMCU again.
I would also recommend taking a look at your board. Not all the ESP8266 development boards use the same peripherals. So you'll have to find a driver accordingly.
For future people with this issue try using a USB 2.0 port. I had mine plugged into a 3.0 and it wouldn't detect.
My troubleshooting (with NodeMCU 12-E, V3):
I tried plugging it after removing the driver from the Device Manager in Windows 10, reinstalling the (CH341SER) driver and 3 cable swaps. In the end my laziness foced me to use my 2.0 front panel. The 3.0 everywhere else wouldn't work.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
Here's the problem - I need my Bluetooth Low Energy-Only device to be able to connect to Windows 7 computers. Preferably using a regular CSR dongle, if possible. Is there any way or workaround?
I spent the two last days googling stuff to make my designer mouse working on my Lenovo T450 under Windows 7.
The solution I found may not apply to everyone: your computer must have a Bluetooth 4.0 capability (which as I understand allows Bluetooth Low Energy (aka BLE or Bluetooth Smart) to work.
The BLE drivers are not native to Windows 7 so you need to install them: go to your manufacturer's website and download the latest Intel Bluetooth drivers. Depending on the make, they might have various combinations of drivers (sometimes with overall wireless drivers, sometimes Bluetooth separately,.. I had to try about 3 - 4 different without really knowing what they meant). Once those drivers installed, you should be able to see your mouse/keyboard and pair to them.
I had to reboot my laptop multiple times and had to download a lot of different drivers from various sources but the one thing that worked was googling: Intel Bluetooth driver "your laptop make and model" and downloading the drivers.
Ps. I have also downloaded the "Microsoft Mouse and Keyboard Center" application and although opening it and trying to use it did not help at all, it might have help setting something in the background that made the drivers get installed smoothly (not an IT person, I have no idea).
I hope it helps!
Good luck
You need Bluetooth hardware that supports Bluetooth 4.0 or higher. Then just install the driver for Windows 7. Don't use Windows' internal update service (its lying and will tell you that your driver is up to date). I used this:
https://downloadcenter.intel.com/download/28510/Intel-Wireless-Bluetooth-for-Windows-7-
Well, Logitech Mx Anywhere 2 surprisingly started working with Windows 7 (Dell 380 Module on E6430 laptop) with IVT Bluesoleil Stack (unfortunately not freeware). Context menu of its icon in tray has "Bluetooth 4.0 functions", that allow adding BLE/Smart devices.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I am having trouble getting my Windows 7 x64 computer to recognize my Tango device. I have Android Studio installed with USB Drivers installed, and manually loaded Google USB Driver.
The device loads as "USB Controllers - Unknown Device" with errors. When I try to update drivers and pick a driver from file, pointing to the Google USB Driver I get an error message: "...doesn't contain a compatible driver for your device. ...make sure it is designed to work with Windows x64..."
I was able to get my Nexus 7 tablet to connect with this driver.
I have tried with USB debugging on and off, and I have tried changing the USB connection to MTP and PTP back and forth with the same result.
When I turn off USB debugging the device sometimes loads as "Android ADB device" with errors. When I try to update the drivers I get the same error message as above.
First thing you need to check is whether Google USB Driver is up to dated?
Go to http://developer.android.com/sdk/win-usb.html
Download the new driver. Tango Device's driver are included in the Google usb driver.
Unzip the new driver to your folder.
As the problem you mention, you may need to manual install the driver.
Manual Install the Google Usb driver step:
1.Goto Device Manager by Control Panel->System->Device Manager
Find the "Unknow Device" or "ADB Interface" in "Usb Controller" or "Other devices"
2. double Click the Device, it brought you to the Properties windows
Click "Update Driver"
3. Click "Browse my computer for driver software"
click "Let me pick from a list of device driver on my computer"
Select Have Disk"
Select "Android Phone"
Select "Have Disk"
Find the Unzip folder/usb_driver/android_winusb.inf
Click Ok.
Back to hardware list
Select "Android Composite ADB Interface"
Click "Next", installing the driver and ignore the warning message.
you are all good.
If it is not working, try removing "Unkown devices" and do again
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Locked. This question and its answers are locked because the question is off-topic but has historical significance. It is not currently accepting new answers or interactions.
I am running Windows 7 inside Mac OS X with VirtualBox,
I used a BLE inside W7 without any problem. Then I used the BLE USB in the Mac, and when I try to use it again in the W& I got this message:
Failed to attach the USB device SEGGER J-Link [0100] to the virtual machine WINDOWS 7.
USB Device 'SEGGER J-Link’ with UUID {} is in use by someone else
I unplugged the USB, restart the Mac, start W7, but I can't attach it again to the W7
I figured it out. You are supposed to:
Shutdown the guest
Plug in the device, let the host grab it
In the host, go to virtual box, and edit the configuration for the guest. In the "Ports" tab, go to USB and add a filter to include the plugged in device
Unplug the device
Start the guest OS
When the guest os is running, plug in the device.
Virtual box will grab the usb device and make it available for the guest. The guest will then go on and try to identify and configure the device.
Done.
The solution for me was to install the Oracle VM VirtualBox Extension Pack. I had to update virtual box to the latest version then download the latest version of the extension pack.
Then, on the USB tab of the virtual machine settings, I set 'Enable USB Controller' and 'USB 2.0 (EHCI) Controller'. Before it was set to USB 1.1 (OHCI) Controller which did not work. Then just add a USB filter for the composite device and when I started up the machine again everything worked.
I am using an nRF51-DK Embedded Development Kit from Nordic Semiconductor which has a Segger JLink embedded on the board. I was having problems getting it to detect on the Mac OS X, Running VirtualBox/Windows 7.
I tried adding a filter under Ports->USB in the Device Image Settings. The device was coming up as a composite device under USB Devices in Windows 7 Device Manager.
Then I removed the filter, installed the Segger/JLink Driver for Mac, ensured that Mac is picking up the device by running the JLinkExe Utility. I then proceeded to add a filter in the Ports->USB under the device image and voila! - Windows 7 Picked up Segger/JLink over VirtualBox.
As a side note, I had also installed the Oracle VM Extension Pack for my VirtualBox version from www.virtualbox.org
J-Link debug probe of version 9.3 works perfectly with the VirtualBox(VB) with USB1.1 (without an extension pack). Once I started using the newer J-Link debug probe of version 10.1, the jlink device was not recognized in the VB because the jlink device driver failed to install. This problem was solved with the extension pack for virtualbox. But the extension pack needs a license for long term use so be aware.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I need two systems running, with a mic on system A going to speakers on system B, and vice versa, in realtime.
I currently have three systems set up:
Fedora
Jack works fine
Ubuntu
Jack has problems recognizing microphones
Windows
Jack works fine
I can connect Jack between the two linux systems fine, but since the ubuntu system is having jack problems regarding microphones, I'm trying to get Windows to communicate with either of them, to no avail so far. I've tried googling around but people seem to either say "It works!" or "It has problems!" without giving details.
Is there a canonical method for using netjack W<->L?
Would really appreciate any help I can get on this.
you could try jacktrip, that has an experimental windows client.
people also reported that soundjack.eu is supposed to work great, but i have never tested it (and couldn't find a linux client on their website)
I was able to get audio playback working from Windows to Linux with netjack2.
I did a small write-up of it here: https://gist.github.com/kotarou3/3813bbf7833a0e4618f7fbe8a377872d
Partially quoting here for posterity:
Stream audio from Windows to Linux
Tested on Ubuntu 16.04 and Windows 10 Redstone 1
Both boxes need to be on the same network (such that multicast packets
can be passed between them)
Installing
Linux
Setup JACK (easy to do with Cadence)
Windows
Install JACK and ASIO Bridge on the Windows
box
Run regsvr32 32bits\JackRouter.dll and regsvr32 64bits\JackRouter.dll from JACK installation directory
Modify 32bits\JackRouter.ini and 64bits\JackRouter.ini to match your channel and sample config
(Optional) Set the ASIO Bridge (Hi-Fi Audio) input as the default playback device
Running
Start the netjack2 server on Linux with jack_load netmanager (probably also possible to add to .jackdrc for it to autoload)
Run JACK NetDriver on Windows (it's in the Start menu), or jackd -R -d net
A new device named the hostname of the Windows box should have appeared on the Linux JACK patch panel
(Catia if you're
using Cadence). Connect it as you see fit (Note: Channels might not
match up as expected if you have more than 2).
Run ASIO Bridge (also in the Start menu), turn ASIO on, and set the ASIO device to JackRouter
The ASIO Bridge should have automatically set up routes to the system device in the Windows JACK patch panel. You can double check
with qjackctl (Jack Control in the Start menu) → Connections
and connect them if not
I imagine this can be further adapted to get microphone input from Windows as well by using Windows' microphone to speaker loopback feature (it's in the microphone config for Windows 10), albeit at the cost of more latency.
Basically get Windows to send the microphone to the ASIO Bridge input.