When I try to connect my plantronics wireless headset via Bluetooth to my windows 8.1, I find that the device is not visible to pair.
Hence I am not able to connect to it.
I have made the settings to enable my laptop detect the bluetooth devices. Still its not able to search.
Try to install [Broadcom Bluetooth 4.0 Driver for Windows 8.1 ] LINK=>> 1 !
At least works fine on my HP-EliteBook-8570p with stereo "BlueDio 99B" headset. After switching the headset ON the Windows connect the device automatically, and switch Audio-Stream into new-attached device. Optimal!
PS - Unfortunately it is still the Problem with Windows 8.1 + Skype( MIC-Problem) :( Windows 8 is the first OS, than not support Skype at all! ;)
Related
Bluetooth device not working on my windows 10,Toshiba laptop.I have tried updating but still can't get it.
Hi all Windows CE developer,
is there an option that a Windows CE device (HP iPAQ) acts as a "normal" USB-drive if it will connected to PC. In this case I have an linux (embedded) device and I have to copy some files from iPAQ every few seconds.
I can not change or recompile any CE Firmware from this devices. The best would be a program to get the USB-drive possibility.
I tryed an CE-ftp server but it did not work because of the "RNDIS" stuff - TCP/IP is missing.
The ActiveSync did not work with linux. I only could get an usb-ethernet connection with RNDIS but without the communication library it makes no sense. "Synce" did not work as well some derivates.
thanks
regards
ferdl
I have a Raspberry Pi3 running Windows IoT version 10.0.14931.1000. The Raspberry Pi 3 onboard bluetooth adapter is supposed to be supported in this version of Windows IoT.
When I use the web portal to search for Bluetooth devices nothing is found, and my Raspberry Pi does not appear to be discoverable. When use Windows IoT Remote Client to connect to the Raspberry Pi and look at the Bluetooth settings it says: "No usable Bluetooth adapter can be found on this computer: The device is not ready for use. (Excep_FromHResult 0x800710DF)".
Is there something else I need to do to enable Bluetooth on the device?
I could try reinstalling Windows, but before I do that I wanted to know if I'm missing something obvious.
I reinstalled Windows (10.0.14393.0) on the Raspberry Pi 3 and Bluetooth is now working. I can only assume that because I started with an insider build that did not support Bluetooth it has got itself into an unexpected state.
If it was full blown Windows I suspect deleting the device and reinstalling it would have done the trick, but that's not an option on IoT.
In Samsung Galaxy S6 Edge with Android 6.0, when the device is rebooted, phone complains that the connected computer doesn't recognize the phone and the device is not any more reachable over ADB from the connected Linux PC. The phone in fact instructs user to install proper drivers for Windows or Mac OS, but as the phone is connected to Linux host, there is no help here.
This means, that in order to continue debugging over ADB, one must manually toggle the USB mode from phone from MTP to PTP, after which phone is connected through ADB again. This makes test automation impossible, as the test scheduler needs to reboot the target device between test rounds.
With previous Android versions, rebooting the device remotely and getting ADB connection back was possible, but with Android 6.0, this became a problem. This particular device had earlier Android 5.1 and there were no problems with remote reboots.
As manually toggling of USB mode solves the problem, it might help, if this mode could be automatically toggled after reboot. So far, only solutions I have seen require device rooting and that is out of question.
Does someone have any idea, how Android 6.0 device could be automatically recognized by ADB after reboot?
The solution was after all simple: the Linux user, who starts up the adb server, needed to be added to the "plugdev" group. This group was defined in file /etc/udev/rules.d/51-android.rules with line:
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
With previous Android versions, this didn't seem to be important as we didn't have any users in that group and everything worked fine.
I have an Asus USB-BT400 Bluetooth Dongle, it works with BLE devices. I also have an TI Sensortag, i installed the drivers and software and I can connect my PC to the sensortag (using windows 7 or windows 8.1 in VM, both works).
Windows doesn't find drivers for the sensors (I think 8 in total) so I would like to know how I can communicate to them. I already exposed a COM port for the bluetooth device (that's possible via Bluetooth settings). I tried the BLE device monitor, where the COM port shows up, but it gives an error (no response from BLE host at port COM3). I also tried the windows Desktop app (win8), which doesn't work either.
I would be glad for any solutions, resources and hints which do not require me to buy the Dongle from TI website for ~50$.
Thank you!
I don't believe it works under anything less than Win 8.1 as the OS must have the BLE Profile drivers.
Running VM is not going to help, as you need those drivers at the base OS level.