This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Vivosmart - new troubles after 2.7.2 Connect Mobile update

Former Member
Former Member
I had been having the widespread problem with failure of my vivosmart to sync previously, so was quite excited when the new 2.7.2 CM App update came through yesterday.

Anyway - once the update was done (and noting that it said you'll need the 2.90 firmware, which at that stage, wasn't out) I didn't try to do anything more than wait. I did notice, however, that once the update was done, the Bluetooth connection dropped within a few minutes of pairing, and if I go into the Bluetooth settings on the phone, the vivosmart doesn't show up as a paired device, but shows in the garmin app as 'disconnected'.

I figured I'd let this lie till the 2.90 FW update came through, which I installed this morning, but the problem remains.

In short:
1. I can pair the device through the Garmin app IF I first delete all the associated files from the phone and restart the app, ##EDIT##or remove the device in the app
2. The vivosmart stays connected for only a couple of minutes then a 'Garmin Device Disconnected' notification appears on the phone.
3. The vivosmart doesn't appear as a paired device in the phone settings, even immediately after the pairing is completed in the garmin app
4. The vivosmart does not seem to register that it has been paired, as I don't get the 'forget on paired device' screen (on the vivosmart) when I try to re-pair it.

I am thoroughly confused and more than a little disappointed at the apparently highly unstable, buggy nature of this device and the associated software. It has potential, but the main reason I bought it was for the direct syncing to the net via my phone. The failure of that key feature to work properly is really starting to make me question why I own it at all!
  • Former Member
    0 Former Member over 10 years ago
    Its not just vivosmart. I've all kinds of problems syncing my forerunner 920XT since then too.
  • Former Member
    0 Former Member over 10 years ago
    I figured I'd let this lie till the 2.90 FW update came through, which I installed this morning, but the problem remains.

    Glad you have the 2.90 firmware. That's the first step. Now, go into "bluetooth settings" and manually unpair any vivosmarts. If after doing so, a dialog pops up to "repair"... press cancel. Yes, "cancel". Starting with firmware 2.90, the vivosmart does NOT need to be paired (as far as Android is concerned) :)

    1. I can pair the device through the Garmin app IF I first delete all the associated files from the phone and restart the app, ##EDIT##or remove the device in the app
    I like to start from scratch too. Long press the device card and choose "remove device". Now, turn off bluetooth, wait until it is completely turned off, then turn back on.

    The vivosmart doesn't appear as a paired device in the phone settings, even immediately after the pairing is completed in the garmin app.

    This is to be excpected! Starting with vivosmart 2.90 and Garmin Connect Mobile 2.7.2, you will NOT see this listed as "paired" in Android's bluetooth settings. If you do, start back at the top of this reply.

    Put the vivosmart into pairing mode and start the setup wizard in the app. Please note that there is currently a server issue preventing many devices from syncing... thus, the device cannot be "setup" completely. In fact, it may never even show up in the "devices dashboard" of the app, if sync fails.

    I believe there are some forthcoming videos to demonstrate what I've outlined above.
  • I've done all those steps twice. Still no notifications, no syncing. Post all the videos you want, apparently they are not going to help me with my Galaxy S4.
  • Former Member
    0 Former Member over 10 years ago
    I've done all those steps twice. Still no notifications, no syncing. Post all the videos you want, apparently they are not going to help me with my Galaxy S4.
    If the vivosmart is staying connected to your S4 while in range, and reconnecting when going out of range, and back into range, then you're 90% there. Due to server issues, yes, sync is failing often, but when those issues are resolved (not an app component at all, as the app just calls the server for the data), the "total" experience should be much, much better.

    Disclaimer: I am a Garmin employee. Opinions expressed are solely my own and do not express the views or opinions of my employer.
  • If the vivosmart is staying connected to your S4 while in range, and reconnecting when going out of range, and back into range, then you're 90% there. Due to server issues, yes, sync is failing often, but when those issues are resolved (not an app component at all, as the app just calls the server for the data), the "total" experience should be much, much better.

    Disclaimer: I am a Garmin employee. Opinions expressed are solely my own and do not express the views or opinions of my employer.


    Hi Doug, thanks for taking time to reassure. Is the notifications issue due to the server issue? Good luck and thanks
  • Former Member
    0 Former Member over 10 years ago
    Thank You!

    Glad you have the 2.90 firmware. That's the first step. Now, go into "bluetooth settings" and manually unpair any vivosmarts. If after doing so, a dialog pops up to "repair"... press cancel. Yes, "cancel". Starting with firmware 2.90, the vivosmart does NOT need to be paired (as far as Android is concerned) :)

    I like to start from scratch too. Long press the device card and choose "remove device". Now, turn off bluetooth, wait until it is completely turned off, then turn back on.


    This is to be excpected! Starting with vivosmart 2.90 and Garmin Connect Mobile 2.7.2, you will NOT see this listed as "paired" in Android's bluetooth settings. If you do, start back at the top of this reply.

    Put the vivosmart into pairing mode and start the setup wizard in the app. Please note that there is currently a server issue preventing many devices from syncing... thus, the device cannot be "setup" completely. In fact, it may never even show up in the "devices dashboard" of the app, if sync fails.

    I believe there are some forthcoming videos to demonstrate what I've outlined above.



    Thank you for the tips. I did everything you posted above and my vivosmart syncs fine.
  • Former Member
    0 Former Member over 10 years ago
    Is the notifications issue due to the server issue?

    They are unrelated. Starting with vivosmart version 2.90, the first device setup sync must be successful, in order for the smart notifications to work.

    Flow
    1. App sends the vivosmart "sync successful".
    2. Vivosmart sends app "ready for smart notifications, if the user wants them".
    3. App displays an Android notification in order for user to grant access to app.

    It was changed for various reasons. One of them being, we didn't want to clog the bluetooth pipe with smart notifications bytes, while sync was occuring. It's better the pipe be dedicated to sync completing. The less time the app needs to send data over HTTP to Connect, the better. Think battery... :)

    Disclaimer: I am a Garmin employee. Opinions expressed are solely my own and do not express the views or opinions of my employer.
  • Former Member
    0 Former Member over 10 years ago
    Thanks for all the responses. I can get the connection working ok now, but I have a new problem...

    If I exit the connect mobile app and restart it, the vivosmart does not get the BT connection back, and I have to remove and re-pair it to get connected again.

    Any ideas how to fix???
  • Thanks for all the responses. I can get the connection working ok now, but I have a new problem...

    If I exit the connect mobile app and restart it, the vivosmart does not get the BT connection back, and I have to remove and re-pair it to get connected again.

    Any ideas how to fix???


    Why do you feel you need to close the app?
    I never do.
    I do go into airplane mode and it always reconnects.
  • Former Member
    0 Former Member over 10 years ago
    Phil,

    I agree that there isn't often a specific reason to close the app, but if the phone runs out of batteries, or I inadvertently push the back button one too many times, I don't really want to have to go through the pairing process again.

    And my Edge 510 reconnects without problem...

    Cheers