After the disaster of FW 4.3 and the numerous issues with FW 4.4 I thought it best to ask the DEVs because there's something puzzling me here and I'm not sure whether it's Garmin Connect Mobile or the Fenix3 Firmware acting weird.
With 4.4 installed via Garmin Express upon release, Garmin Connect Mobile still forced me 36 minutes on the phone waiting for the patch to be delivered via bluetooth to the Fenix3. As you can imagine, every 30" the phone was going idle, which forced the resync but luckily the procedure would resume otherwise it wouldn't have completed yet.
From 4.3 and onwards this is what happens on my end.
The Bluetooth connection reported active by F3 (connected) still shows "waiting for data" from Calendar, Weather and Notifications while the Music player works (as a further testimony that bluetooth is indeed up and running).
In order to REALLY have Garmin Connect Mobile connect to the Fenix3, the manual SYNC must be performed from the watch as the Bluetooth connection is apparently not enough.
When this is established, notifications and calendar start working but the weather doesn't. Yet the watch knows where I am because of my wireless internet connection (which is the same that takes place on the phone it's connected to).
So when I go outside and start the GPS, the weather starts working. It looks like F3 will grab the weather ONLY from its own GPS and not from the phone and BLT connection.
That goes without saying that should the BLT connection be severed, since GCM doesn't start the autosync (and apparently neither does the F3), every time someone wants to see the weather on his watch he must turn the GPS on.
Is this really working as intended? Why should I turn the GPS on if I am outside when I can just lift my head and look at the sky?! Did you make sure GCM is on par with the new FW? Isn't the BLT connection supposed to AUTOMATICALLY connect and sync F3 and phone when connection is re-established?
I started wondering if there's ME having problems and needing a F3 reformat or if it's GCM that has problems with FW 4.3 and 4.4. You, the DEVs are the only ones who can tell.