“does it let you know if you have a call coming in and if so how far away can the phone be from the fitbit”
Answer This Question
1-10 of 10 Answers
Yes it does notify if you have a call, I usually have my phone in my purse. It used to be that sometimes if I had my phone in my purse I would miss calls or texts but now the Blaze lets me know.
Sorry, there was a problem. Please try again later.This product will keep you updated on calls as well as other events. The phone can be 10 meters away from the Fitbit.
Sorry, there was a problem. Please try again later.Yes, but not sure how far you can be from phone. I have been in another room before and it worked that far.
Sorry, there was a problem. Please try again later.Depending on the model of your phone, yes, it will vibrate when a call comes in. The Fitbit Blaze connects to your phone only by "Bluetooth" so you have to be within the range of Bluetooth for this feature to work and that varies (10-15 feet).
Sorry, there was a problem. Please try again later.You get an incoming call alert if you're connected to your phone via bluetooth and within range (usually about 200 ft).
Sorry, there was a problem. Please try again later.Limited to the Bluetooth range, usually upto 30 or so feet.
Sorry, there was a problem. Please try again later.Yes, the Blaze will vibrate and show you the phone number of the caller. Distance will vary depending on interference of what is between your phone and the Fitbit. It uses Bluetooth so expect roughly the same distance as any other Bluetooth product.
Sorry, there was a problem. Please try again later.I was at the gym about 30 feet away from the treadmill and I got a notice about a call. Hope that helps.
Sorry, there was a problem. Please try again later.It does let you know if you are paired via bluetooth. As you are using bluetooth, you get the usual limitation of 30 feet or so from your phone.
Sorry, there was a problem. Please try again later.yes, it let's you know about incoming calls. don't know how close phone needs to be
Sorry, there was a problem. Please try again later.