I did not rest the ionic. While updating it did take longer than normal though - i remember it appeared to be done updating and i took it off the charger and the Fitbit icon reappeared. Should i reset now to see if that helps?
Best Answerfirst: i'd stop providing full name - workplace and phonenumber on public messaging boards.
second: no idea, i've got the .20 update, notifications didn't work. Then performed a reset, got the .15, still with dysfunctional notifications.
@MattFitbit: to the rescue! ![]()
Smartphone wise i haven't changed anything, between previous stable release and shortliving .20. Within the .20 i've tried to enable always connected and keep-alive widget - neither of them where needed with the previous release, and neither did make the notifications work again.
Same with the now pushed .15 version.
Best Answerok, i'd like to revert most i've said.
this morning i've got a call, which was displayed with name and accept/decline options on the ionic. -> i knew that the notification framework was working as expected on watch and phone.
then i've switched my sms app to androids default -> incoming messages are displayed with quick-replies.
Switched back to signal https://play.google.com/store/apps/details?id=org.thoughtcrime.securesms (of course, again as default application in andriod and in fitbit's settings as message app), and didn't get notified.
Signal supports Androids quick reply feature and should therefore work without further ado from fitbit, at least thats how it's described in some release notes - and like i've said before: the plain notification worked flawless in the previous firmware release.
@Libbee: can you check if incoming calls are pushed to the ionic?
Best Answer