# Beating a dead horse (smart watches) **URL:** \ **Category:** C/GM\ **Created:** [February 1, 2019, 5:23pm UTC](https://forum.fudiabetes.org/t/beating-a-dead-horse-smart-watches/6382 "2019-02-01T17:23:43Z")\ **Posts on this page:** 1\ **Showing post:** 12
**Author:** ![Michel](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fudiabetes.org/michel/32/387_2.png) [@Michel](https://forum.fudiabetes.org/u/Michel)\ **Post date:** [February 1, 2019, 7:19pm UTC](https://forum.fudiabetes.org/t/beating-a-dead-horse-smart-watches/6382/12 "2019-02-01T19:19:03Z")
> [@Irish](#): > > Is it possible that updating my watch and/or phone would do this at some point? Unfortunately that is quite possible ☹ Here is a recent example of a bad update to an app that killed Bluetooth connectivity to a meter: > [@Accu-Chek Mobile wireless adapter](https://forum.fudiabetes.org/t/accu-chek-mobile-wireless-adapter/6344): > > Hi all, I got one of those new Accu-Chek Mobile wireless adaptors the other day, and it all worked fine for about 48 hours, and now just won’t connect to my phone at all. Nor will it pick it up when trying to search for it in Bluetooth or mySugr (it comes with a free premium mySugr membership so transfer the data over). I’ve called the helpline, but they can’t offer any help beyond the steps below which I have already tried multiple times. Can anyone suggest anything else to get this working … --- _[View the full topic](https://forum.fudiabetes.org/t/beating-a-dead-horse-smart-watches/6382)._