Does anyone know if its bluetooth strength or brute physical distance that determines whether it locks/unlocks?
Im hoping someone can change a line in code within a plist to allow a greater range.
My bluetooth keyboard and track[ad have a bluetooth signal averaging -48 to -58 which I think is powerful enough but apparently its not enough to trigger the auto unlock.
Sometimes it works, sometimes it does not hence trying to work out is it signal or distance limit? Its completely random.
I have the BCM94360CD model. Im prepared to buy a new module if it'll certainly improve.
Thoughts?
No-one outside of Apple really knows what they're doing (at least, if they do, they aren't talking)
with this feature.
You could try pruning down the section within:
/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist
for your system (make sure you backup the file first)
You'll notice that some systems in there don't have thresholds. You could try removing them for your system (or tweaking the values) - see if it makes any difference.
If it does, please let everyone know on this thread, so they can replicate your results.
The BroadCom 4360 chipset supports both BLE as well as 802.11AC - chances are you'll be fine with that card (although, as the same chipset is utilized for both, there have been some suggestions that performance isn't as well as the airport cards that have separate chipsets for the two networking protocols).
[doublepost=1474207531][/doublepost]
Hey guys, I always get a message in the security prefs that communication between my Mac and AppleWatch failed.
I think I fulfill all the requirements:
– 2-factor-authentication
– MacBook Pro 15" late 2013
– Sierra GM (Build 16A323)
– latest WatchOS 3
– latest iOS 10.0.1
I even completely reset the Watch lately and the GM of Sierra is a clean install.
Of course all devices are logged into the same iCloud account.
I see the checkbox to allow AppleWatch unlocking my Mac for several betas now, but I always get this dialogue telling me communication between my Mac and Watch failed.
Since I reset the Watch yesterday to factory defaults, I guess there must be a bluetooth-, networking- or security-preference file in one of the library-folders that I could try to delete. Does anybody have an idea which ones might be relevant?
It can often be frustrating (and illogical) for what actually gets this feature working. I think Apple's over-complicated the feature (possibly in their efforts to ensure only the newest systems support it).
From your system side, you want to minimize the complexity of your installation until you get it working. (so, using the MacBook by itself - lid open, no external displays or peripherals (incl. keyboards or mice).
Also, if you have any other bluetooth devices connecting to your MacBook, I would unpair them until you get this working.
Copy/pasting advice I gave someone else on another thread:
Unfortunately, in order to get all of the bits to work can often require you to logout/login to Apple's cloud in multiple ways (iCloud, messenger, FaceTime - each has their own login). Toggling the handoff feature (System Preferences, General, Allow Handoff between this Mac and your iCloud devices) as well as on your devices (iPhone, both Utilities, Settings, General, Handoff as well as Messages, Text Message Forwarding) - and again, toggling your logins for iCloud, iMessage & FaceTime for all of your devices.
It REALLY shouldn't be this awful to get a feature like continuity to work, but Apple's made far too many hooks and checks into their cloud....and all of the ducks have to be in a row. (and our ability to see which duck isn't is almost non-existent).