I am trying to use my mac (MacBook Pro (Retina, 15-inch, Mid 2014) to connect to a device for an application I am trying to write however when setting up my CBCentralManager I am always returned with The platform doesn't support Bluetooth Low Energy. If i check my system information under bluetooth it clearly says that My computer does support Bluetooth low energy by this statement (Bluetooth Low Energy Supported: Yes).
What am I missing here is this me messing something up or is this something seriously wrong with my computer?
Also what can I do to bypass this annoying only Low Energy Devices and just start scanning for peripherals, seems kinda silly that it wont let me set a property to skip Low Energy.
Thanks for your time.
Sometimes the Bluetooth hardware can get messed up. Try a reboot and if that doesn't work a PRAM reset.
Related
while developing for the new Microsoft Surface Dial I noticed the device going to sleep after a few minutes and taking about 1-2 seconds to wake up again after an interaction with the device. This is insufficient for my specific use case, where the application has to give immediate feedback.
I've tried turning off the energy settings for the bluetooth device in the device manager, but the problem persists. Is there a way to turn this off, either in code or in some other way?
Unfortunately there is no way to solve the issue without a Microsoft firmware update.
The unit use a Nordic Semiconductor nRF52832 Bluetooth Low Energy SoC, is possible change that on the chip, but with a firmware update. Really sorry but is the only way.
I'm currently working on 2 applications (one on iOS and the other on Mac) that are communicating using Bluetooth Low Energy (Bluetooth 4.0).
I develop these applications using CoreBluetooth on iOS 8 and OS X Yosemite.
I'm facing the following issue :
On my Mac, if the Wifi is turned OFF or if it is connected to a 5 Ghz wifi network, I have a stable Bluetooth connection between the iPhone and the Mac. No problem.
If my Mac is connected to a 2.4 Ghz Wifi network and if I have at least one Bluetooth device connected like a keyboard, trackpad, mouse... (using Classic Bluetooth), I have a stable Bluetooth connection between the iPhone and the Mac. No problem.
If my Mac is connected to a 2.4 Ghz Wifi network, the Bluetooth connection becomes unstable : the connection is stopped almost every 10 seconds and in Xcode I get an error message telling that the connection had an unexpected timeout.
I spent days on the Internet to try to figure out what I can do.
The best answer I found was this answer : CoreBluetooth and Wifi interference
But it means that I have to tell to my app's users to run this script and reboot their computer which is not for me a viable solution for production.
I also heard something about dealing with classical bluetooth peripherals (maybe to simulate one) or Wifi interfaces, but I found no solutions involving these kinds of manipulations.
Does anyone have an idea about something that I can do ? A workaround about the OSX Bluetooth management, the Wifi interfaces ?
I really need help about this issue.
Thank you very much in advance for your help.
I have a Metrologic MS1690 Barcode scanner that I'm trying to use with Windows 8.1, I get a Unrecognized Device: Device descriptor request failed error in devices and printers. The scanner gets no power from the computer when it is plugged in because of this. It usually shows up as a usb keyboard in windows 8 and 7, but with 8.1 it does not and I can't find an answer anywhere. Please help! Or even if someone could tell me how to get a generic usb keyboard driver for this thing that may help as well. Thanks.
The scanner gets no power from the computer when it is plugged in
Bit of a guess, but there was a change in Win8.1 that can affect HID devices like this. Such devices are now suspended when no application or service is accessing it. This can cause the device to misbehave if it depends on receiving timely power to operate correctly.
The workaround is to disable Enhanced Power Management for the device. The instructions are pretty elaborately spelled-out in this blog post. At break-neck speed: use Regedit.exe, locate the device in the HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Enum\ USB key and set the EnhancedPowerManagementEnabled value to 0.
The "solution" for me has been to add a PCI-E USB card, and use that for the scanner. I went with this one from Rosewill because it uses an NEC chipset which I have heard good things about.
After installing the provided drivers for the PCI-E card, the scanner seems to enumerate consistently (I have only been able to test it for a couple days so far).
According to the person I bought my scanner from, it's an issue with the USB chipset on the motherboard. Some are compatible and some aren't. If I had to do it over again, I would go with an RS232 cable and a power adapter instead of USB. I haven't tested that setup, but if your app needs serial data like mine does, it should be more reliable given that it's not dependent on the vagaries of integrated USB chipsets.
I am experiencing lot of troubles detecting BLE devices with a CSR8510 chipset. I don't have much knowledge in bluetooth hardware/stack and osx systems. I made a lot of research to solve my problem but I can't find any information specifically related to my issue.
Here is all the informations about my setup :
The dongle is plugged in a Macbook Pro late 2011 (mavericks). I made all the necessary to make the dongle work :
HCI bootmode
com.apple.bluetooth.plist deletion and reboot
I used Bluetooth Explorer to change the Host Controller (default internal chipset -> CSR8510)
Now the dongle is fully recognized by the system, I can use my Magic Mouse (all functionalities work), but I am not able to detect my BLE chest belt (Runalizer blue).
When I launch a scan with the Device>Low Energy Devices panel in Bluetooth Explorer or the demo app indicated by the belt manufacturer I don't find anything.
Demo app : https://developer.apple.com/library/mac/samplecode/HeartRateMonitor/Introduction/Intro.html
To be fully exhaustive my Xperia SP works perfectly with the belt.
I tried to dig into kernel extensions and I've found in System/Library/IOBluetoothFamily.kext/PlugIns two interesting kext :
CSRBluetoothHostControllerUSBTransport.kextCSRHIDTransitionDriver
I do not know if it is relevant or if it could help me but since they start by "CSR" I thaught that it may be related.
I hope someone can help me. It is bothering me so much because I am not able to do the job I was willing to do (gather data from the belt and statistical processing).
Thanks for your attention.
In Windows XP SP3 is there a registry key or some setting, maybe even at the device level in the registry, that an EHCI USB 2.0 High Speed hub can be enumerated as a UHCI or OHCI full speed device at the host level?
I am seeing an issue where a USB 1.1 full speed device is deadlocked due to infinitely NAKd split transactions with the transaction translator buffer on a high speed hub. This only happens under certain circumstances the full speed device is connected behind a 2.0 high speed hub only in XP SP3. I have opened an issue with Microsoft and they have confirmed this is a known issue and there is no Hotfix for the issue (nor will one be developed). It has been corrected in Vista+.
If the device is connected directly to the host controller, or has a full speed hub upstream of the high speed hub the problem goes away (because there are no split transactions). So, if there is a way to force the high speed hub to enumerate as a full speed device then it may help us out.
Furthermore, the hardware design is set in stone. Systems have been developed and there is no way to insert a full speed hub chip anywhere in the design, or hook up the devices directly to the root hub. And finally, it is not an option to upgrade the OS on the systems.
After some work and research with help of Microsoft the current conclusion is that there is not a way to do this.
The workaround that we will be using is to perform a PnP reset on the bus to stop the infinite NAKs, then reopen the port to begin communication again. This is not very clean, but it will solve the problem.