Join now - be part of our community!

Bluetooth Unlock Custom Range

CallMeBob
Visitor

Bluetooth Unlock Custom Range

Hi, I just tried to use my SWR30 to unlock my Z3 Compact and I would like to say it works... I really would like to. But I can't. Unlocking a phone 30 meters away is not really what I would call safe. Basically it means I can't leave my phone anywhere without it still finding me and unlocking, even on the other side of a building... Impressively dangerous.

My brother is using the SWR10 and on it he used the "set sensivity range" option you get on the phone security menu. And it works. His phone only unlocks when in his hands or really close. I was expecting the same from the more expensive model but when I try it, the phone writes back an error of the kind : "the device is not in range or does not support custom range.".

How come? Am I the only one? Is this a bug or a forgotten feature that will come with next update... (you know, the one supposed to bring voice control and sleep control) ?

3 REPLIES 3
kashy27
Visitor

Iv got the same problem with mine, hope this and all the other missing features get updated asap

Tags (1)
Rickard
Master

I'm sorry for the late reply.

You can use both SmartBand Talk (SWR30) and SmartBand (SWR10) to unlock your connected device using the Bluetooth unlock feature. However, the ability to determine the distance between the device and your SWR30 or SWR10 depends on the SmartBand's Bluetooth support.
When connecting SWR10 to a device, you can set a sensitivity range. This means that you can select to only unlock your device when holding it in your hands or when you are really close. The sensitivity range is only supported for BLE (Bluetooth Low Energy) which SWR10 uses. Since SWR30 supports voice control, Bluetooth Classic is used and therefore sensitivity range is not supported. To avoid unlocking the phone at a greater distance you can select to disable the Bluetooth unlock feature in your device.

CallMeBob
Visitor

I see, thank you for that very clear answer. Too bad it comes too late. I was hoping this was just an overlooked implementation that would eventually get fixed by a firmware update. But that now seems unlikely. It's quite sad, had I known I might have made a different choice. The only too things I was interested in were the notifications and the unlock (while in my hands). Alas, I absolutely don't care about voice control Slightly_smiling_Face

Anyhow, cheers Winking_Face