01-31-2020
09:31
- last edited on
02-10-2020
16:33
by
JuanFitbit
01-31-2020
09:31
- last edited on
02-10-2020
16:33
by
JuanFitbit
Hey Everybody - I know this is a sore subject, however there was an update on my watch this morning and I gained the ability to receive notifications of my text messages (my calls had been coming thru the whole time). Try the update!
Also, I thought I was reading that you should have your preview on via your phone, that apparently is false! You should turn off the preview on your phone and then it comes thru as a notification on your watch.
So my problem is....When I hit the "OPEN MSG" on my watch - it does nothing. I dont get a blank screen, I dont see the text or anything...it just flashes and then says all caught up-nothing here. Does anyone know how to remedy that??
Thanks
Moderator edit: format
02-10-2020 16:32
02-10-2020 16:32
Hi @fromSCtoTX2019 , a warm welcome to the Community! I apologize for the delayed response.
There seems to be a misunderstanding. The Versa lite will show you a preview of the messages with a limited amount of characters.
When you press "Open MSG" , the original message will open in your phone, not your watch. As the messages are saved on your phone and not the watch.
Please let me know if you have further questions
JuanFitbit | Community Moderator, Fitbit. Hat dir mein Beitrag geholfen dann markier ihn als Lösung und gib mir Kudos !! Habt ihr Tipps um fitter zu werden? Lifestyle Discussion forum.
11-27-2020 16:57 - edited 11-27-2020 17:16
11-27-2020 16:57 - edited 11-27-2020 17:16
Prior to the update I was able to open the text on my Versa Lite and send a quick reply.
Online Fitbit says that you can do quick replies... so why would it only open on my phone and no longer all on my Fitbit? The Fitbit app literally has a quick reply option setting for text messages!
I keep seeing responses like above... "it opens your phone app". Tried that... and it doesn't. I got a text, selected open message on my Versa, but it did NOTHING on my Samsung. HOW USELESS!!
When is this getting fixed or returned to its original state?