Beh penso che cmq sia legato al firmware... fino a ieri sera mai avuto questo problema... è iniziato subito dopo l'aggiornamento....dutchman ha scritto:Le attivita' fantasma sono un problema legato a garmin connect e non al fenix3!
che ci sia installato un firmware o un'altro il risultato non cambia, a quanto pare il problema e' legato a come GC riconosce il vostro fenix3 infatti per alcuni utenti non ci sono attivita' fantasma. Se si vuole la certezza di non avere attivita' fantasma, dopo aver verificato che anche con l'ultima versione di connectmobile installata sul vostro smartphonepersiste il problema, l'unico modo e' disattivare l'activity tracking (di fatto viene creata una attivita' fantasma ogni volta che il F3 scarica i dati dei passi su connectmobile).
qui sotto una risposta relativa al problema scritta dal beta team del F3.
"I think it's obvious the fix from the GC side that was intended to resolve the phantom activities issue did not completely squash the problem as we had hoped. The GC Team continues to seek solutions. It appears there are multiple side cases that have yet to obviously show themselves, even though we have examples (even internally) to work with. If your account shows as an unknown or as a Quatix 3 device, you're probably going to start seeing phantom activities.
Just a little background, we have devices on the fitness tracking side that require nothing from the user to generate an activity file. There is logic that monitors their step data and then turns it into an activity. Because the Fenix 3 has specific 'activity creation' options, there is no need for this logic on our side. The problem is that GC sees the Fenix 3 step data and is applying the logic used to identify activities in our fitness tracking products. The reason for this confusion is complicated.
I spoke with the GC Team yesterday and they were working hard to try and clean up phantom activities in accounts and resolve these edge cases. I know some of you have upgraded to the latest beta and only then have seen phantom activities at that time. I can promise you that we've looked at the beta's over and over again and even reproduced this issue in 6.50. This issue still has no appearance to be on the device side. Furthermore, if I knew it was a device beta issue, there would be no reason for me not to tell you. I'm being as transparent as possible so that you have a clear picture as to how to prevent it in your case, and so that you know that we are working towards a solution as fast as we are able.
I'd like to ask for these threads not be filled with reports of phantom activities. We are well aware. If we need more on this issue from the community, I will most certainly ask. More than likely we will ask from users who've reported this issue in the beta email box.
Thanks again for your diligence!"
Ma qualcuno sa come fare il downgrade all'ultimma beta? Io ho ancora i file di installazione che ho usato basta che rifac io la procedura?
Se facendo il downgrade il problema sparisce allora è sicuramente un problema di firmware e non di GC...