Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

No Call Notifications, Texts Working

Replies are disabled for this topic. Start a new one or visit our Help Center.

Upgraded my 2013 Moto X to Lollipop last week.  Call & text notifications were working great.  Decided to do a factory reset (recommended after a major upgrade), then I was able to get text notifications and music control working, but I still can't get call notifications working.

 

- using the latest FitBit Android App - v2.17.2

- All-Day Sync is off (tried on too), Always Connected is on, Encryption is on (tried off too), Notifications Widget is on

- tried uninstalling & reinstalling app

- unpaired bluetooth, paired again

- rebooted the phone and surge several times

- called tech support and was given the same list of troubleshooting steps from the website, case is being escalated

 

I don't suppose anybody has any other suggestions?  If call notifications are working for your Lollipop Android Device (a Moto X especially), can you tell me which options you have enabled & disabled (all-day sync, etc.)?

Best Answer
0 Votes
6 REPLIES 6

@PurpleSunday Thanks for stopping by! Make sure to follow each and every step on this troubleshooting article for call/text notifications. The "forget"  part on the Bluetooth is very important. Those are the troubleshooting steps I can find for you, if you already did them make sure to contact support to see how the escalation is going on.

 

Make sure you have followed every steps and let me know the outcome.

Santi | Community Moderator, Fitbit

Like my response? Vote for it! Also, accept as solution!

Best Answer

Thank you.  I followed every step including "forgetting" the device several times.  Support said they were escalating the claim yesterday.  I haven't heard anything yet.

Best Answer

@PurpleSunday Sorry that didn't worked. Give them one or two days, if  you don't get a response try to contact them back to see if they have any updates on your case!

 

Thanks for your patience! See you around. 

Santi | Community Moderator, Fitbit

Like my response? Vote for it! Also, accept as solution!

Best Answer
0 Votes

UPDATE:

 

Until yesterday my only tests of the call notifications was calling my cell number from my office phone and letting it ring until it went to voicemail... no alert.

 

I finally received my first "real" phone call yesterday evening.  (I basically use my phone for everything else, but talking.)  Right near the end of my 2 1/2 minute call, I finally got the alert on my Surge.

 

So alerts are working, they just take fooooooorever.  I've tried unpairing and paring again, rebooting, setting the app to "always connected", and more.  My phone is at most a few feet away from my Surge.  Alerts didn't take this long before my factory reset.  Any idea whey they're taking so long now?

Best Answer
0 Votes

Finally heard back from support.... "sorry to hear that your Surge is not receiving text notifications" and guiding me to follow the same troublehsooting steps that the person on the phone confirmed I had already done.  This is going even slower than the call notifications.

Best Answer
0 Votes

@PurpleSunday That is really strange. The good thing is that they are working. Have you tried a regular restart since you did the factory reset? Try that out and remember you can always try to forget the device on the Bluetooth as it may be a temporary issue. 

 

Regarding support, as your case was already escalated, I will recommend to give them a call and explain what happened.

 

Keep me posted! Smiley Very Happy

Santi | Community Moderator, Fitbit

Like my response? Vote for it! Also, accept as solution!

Best Answer