We've been using 3.70 ever since it was released, on a 1100 km mc ride, and all three have worked flawlessly, with and without remotes.
Not one problem in that whole time.
And the batteries seem to last just as well as ever.
I've been running the Virbs pretty much whole days on each motorcycle ride since our season started back in April. For the two cameras my wife and I normally use while riding, we each have Garmin Montanas working as battery chargers. At lunch, the morning's camera battery gets switched from the camera to the gps/charger, so the dead battery charges up while we continue to use the cameras over the afternoon.
I've found the battery charges at almost exactly the rate it discharges in the camera, so by 4:30 I can switch again if needed. I am not recording continuously, but the camera is on continuously. That way I can record video when I want to, and take pictures both on their own and during video recording. It sure is nice not to have to carry a special battery charger.
My secondary Elite started having problems connecting to the Remote when I tried to use them together today. I had hoped to use the Remote but it kept being difficult to connect to, and disconnecting often so I turned off Remote in the camera a few times, and resynced the Remote to the camera but nothing had any effect.
So I turned off remote in the camera, and shut it down. When I restarted the camera, I turned Remote back on in the camera, and synced from the Remote by holding both red buttons in for 10 seconds, and it worked perfectly from then on.
Today I got a (second) brand new unit back from Garmin. I could not find my proper fast sdcard so I just inserted an old 2GB card and updated to firmware version 3.7. I am happy to report that the bug that locks the camera when taking more than one picture at a time is now fixed. This alone will make it usable to me and I hope the rest of the issues is fixed as well.
Guys I unfortunately did not get on well with the new firmware 3.70, how do I go back to the previous? in particular with respect to the previous year, when I turn on the camera before you start recording pass several seconds, whereas before it was much faster, can you tell me how to fix this problem?
Do a "Factory Reset". Power off, push and hold Down button, push Power and when asked, say yes to "Clear All Settings". No need to go back to a previous version. 3.70 is good.
Anyone else noticing that the gps is not working a lot of the time as evidenced in Virb Edit, where only some of the time I see speeds and tracks.
On a number of my videos there's no track information, speed data or temperature for ages, perhaps 10 or 15 minutes then all of a sudden it starts through no intervention on my part. It could be halfway through a ride video where there's no way I could have changed anything.
Check this video to see what's happening. No data is being recorded for the first 24 seconds in the video (I clipped about 12 minutes off before that where there was no data also)
This with VIRB Edit 2.5.x? Could it be an alignment problem between the video and the track? I did a time lapse today (1 per second), and when I got home and got the data off with VIRB Edit, it aligned horribly, about 1 hour off. That was the first time I had ever seen alignment problems with the track and video from the VIRB, although I also think it was the first time I've used time lapse in a while.
I haven't seen any GPS problems at all the few times I've used the VIRB with 3.7, but today both my ANT+ sensors (HR and speed/cadence) dropped. I wound up replacing the track with the one from my Edge 800. That also misaligned, so I had to manually align it, but that's happened often with previous versions of VIRB Edit. The Edge saw the sensors throughout the ride.
I didn't have these problems, but someone flying had, he solved it by attaching the FIT file to the clip. It was strange that the FIT was recorded but no GPX attached to the clip. I know a GPS needs some time to find satellites, but 12 min is a long time to find them. If you're sure it was better with older firmware you could try to re-install an older version.
