MacID for OS X reconnection procedure

As MacID becomes more popular, more and more people in offices are using it.

This is awesome, but in an environment like this it really shows up an issue where MacID has to “ping” everything nearby to reconnect to your device.

I really wish I didn’t have to do this, but there are a couple of issues with Bluetooth on OS X that mean I have to.

  1. The APIs are meant to allow apps to search only for devices that have a specific service. Unfortunately this just doesn’t work, I’ve spoken to other devs and they’ve had the same issue.
  2. Apps are also meant to be able to save a device’s identifier to reconnect to it at a later date. This works, until iOS changes its identifier, which happens randomly. I suspect this is something to do with protecting users’ privacy, but it makes reconnecting difficult.

As you can imagine, both of these issues present a problem. The only solution to which is to scan for everything and then try and figure out which is the right device.

Every new version of OS X I check if this has been fixed so I can at least search for just devices that are advertising the right services but unfortunately that hasn’t happened yet.

Debugging Auto-lock

Auto-lock has always been a feature that works fantastically well for some people, and not so great for others. The main reason for this is signal quality, but it can easily seem like auto-lock doesn’t work.

I’d really recommend reading through Understanding MacID’s Proximity Features, if you haven’t already. That post goes into much more detail about how exactly Auto-lock and Proximity Wake work. Continue reading Debugging Auto-lock