We are developing a hardware device that implements BTLE profiles and already works fine with iOS.
Now, we are implementing HID over Gatt profile so that it can communicate with OS X. The final purpose is changing PowerPoint slides and that such of things.
My iMAC does not detect the device using Bluetooth assistant, but I can connect to it with LightBlue app, although I get no keyboard effect. That makes me think I would need drivers/code, even develop an app.
I would appreciate any point to start with.
I answer myself in case it could be useful for anybody. I've updated my iMAC to Mavericks 10.9.4 and the first quick test has worked properly. I previously had Mountain Lion and it did not work as I posted before.
#Paulw11, thanks for the link. I watched the video and if I'm not wrong, there is a statement that HID over Gatt profile (HOGP) is available from iOS7 and OSX Mavericks.
Related
I am trying to locate documentation on USB driver development for macOS 10.12
Everything I can find online seems to be dated 2013 / OS-X 10.9 or earlier
(e.g. https://developer.apple.com/hardwaredrivers/)
Is this because the USB drivers in OS-X haven't significantly changed since 10.9?
The documentation I can find is pointing me at USB Prober and IOUSBFamily both of which don't appear to be supported in 10.12.
Am I missing something?
Thanks
Apple's USB stack was at one time Open Source, but it was closed when they re-architected it.
The API is now dramatically different but IMHO it's better than the old API.
I found your question while searching for USB Prober myself. It's still available at https://developer.apple.com/downloads but it's packaged inside a collection of tools whose name I just now do not recall.
I'll edit this post once I locate it.
I'm trying to use Kinect2 for a project. But it has a problem that the device is recognised on Hi-Speed Bus not on the SuperSpeed Bus. I suspect that due to this problem, the kinect programm is not able to be opened. The laptop is a Early 2015 Macbook Pro, OS X: Yosemite.
Has anyone come across similar issue?
The libfreenect2 FAQ says if that happens, you should:
try unplugging the Kinect from power source with the USB cable connected, and plug the power again, then verify.
It seems like a combination of Macbook Pro and Yosemite.
The problem was fixed simply by upgrading to El Capitan. The same issue happened on 2 different Macbook pro with Yosemite.
But it worked perfectly on a IMac with Yosemite.
right now i am running the OS X Yosemite beta 10.10, after upgrading my OS X i lost my camera, i tried everything in the forums, but nothing helped.
i can't FaceTime, or Skype or anything. normally i would take it in to an apple store, but the closest apple store to me is about 200 miles away.
since i am beta testing OS X Yosemite, i knew i was going to have some problems, but i need this to work
also; i also installed the update 2 days ago as it was recommended in the app store.
(not a hardware problem, was working perfectly before the upgrade and it is not found in the "system info> USB"); also not user specific.
Open your terminal and type this command:
$ sudo Killall VDCAssistant
Now, go to your Skype->Preferences->Audio/Video and you can see the webcam working.
Have a good one!
Apparently, this problem persists even in the recent versions of OS X Yosemite. I also had this problem. So, the answer to solve it is basically resetting the SMC, which Apple provides instructions in https://support.apple.com/en-us/HT201295
Now, I was not able to sort it even by resetting the SMC in a Macbook Pro 15 mid 2012. At least, not immediately. As I keep a few things connected in the USB ports, I believe it might have been the reason, so I closed all my applications (just in case), turned off the computer, unplugged all the USB and thunderbolt connectors (yes, including the LAN adaptor), as well as the earphone connector to speakers. THEN, reset the SMC (for non-removable battery computers, by pressing and releasing control-shift-alt-power [left shift] simultaneously while connected to power). For me, it worked.
It might be useful to remember that the SMC is the System Management Controller, that takes care of the hardware in a low-level, including i/o, keyboard backlight, speakers, camera... so, if you are going to reset it, it might make sense to release all the possible burden it might feel.
Resetting SMC is the only thing that solved the problem on my MBP Mid-2012.
The issue came about around the time I upgraded to High Sierra.
This issue is solved with the newest update of OSX Yosemite. Just update through the Appstore app and everything will be normal.
does anyone notice any issues when using your mac (running OS X 10.10 yosemite DP 6) as an iBeacon? I tried several tools and I also developed it myself (using the CBPeripheralManager startAdvertising) but without any luck.
When running those apps (+ the the code I developed myself) on a mac running OS X 10.9 Mavericks, it works like a charm.
Is there anything specific required for OS X 10.10 yosemite or is this a bug?
Any help is appreciated!
EDIT: Radius Networks has confirmed this issue has shown up on subsequent pre-releases of Yosemite. This OS veesion blocks sending an iBeacon transmission with the internal interface, but allows it with external interfaces. So you can add an external Bluetooth dongle like the GBU521 and transmission works again.
It's gotta be a bug in the code or something specific to your machine. We have tested our MacBeacon OSX app on Yosemite and have not noticed any problems.
In fact you can indeed advertise your Mac running Yosemite as an iBeacon with an external compatible Bluetooth 4.0 (USB).
I wrote a simple iBeacon transmitter for Yosemite written in Swift, look here https://updatemycode.com/2014/11/29/yosemite-as-an-ibeacon-swift/.
This does seem to be a problem with Yosemite 10.10. This is acknowledged now on the radius network website: http://www.radiusnetworks.com/ibeacon/macbeacon/
I'm having to buy usb beacons that I can easily power on and off for testing because of this issue.
I didn't test this with 10.10, but I'm able to use 10.11.3 to advertise as a beacon (at least with the project from #mgigirey). Perhaps Apple opened this again?
I just recently started working with Qt 4.7.4 64-bit in order to make some cross-platform multi-touch applications. However, I can’t get Qt's touch events working in Mac OS X.
When I build and run my own application or any of the Qt touch demos, including fingerpaint and knobs, it doesn’t work. No touches I perform on the trackpad, be it a single or multiple touches, does anything in the application; no QTouchEvents are received. I’ve tried on both a Mac Pro with a magic trackpad and a Macbook Air with its build-in multi-touch trackpad, and in both Snow Leopard and Lion.
Qt's documentation doesn't make any mention of these demos, or QTouchEvents in general, not working in OS X, and implies that they do. And in my searches for a solution, I have seen videos of Qt's multi-touch working on Mac OS X, and found other people talking about using it, so there must be some way to get this to work.
Does anyone have any idea what’s going wrong? Thanks in advance!
Try link Cocoa framework to your application, it can fix some strange behaviour with events on MacOS X.
For posterity, I solved this by updating to Qt 4.8.0. After doing so multi-touch just started working.