Lifehackster, a YouTube camera technology reviewer, has just posted actual footage of an auto accident involving his wife at an intersection in the States. Although the interior camera captured the entire event, the front camera shows only the before and after footage is recorded on the memory card. Although some audio is recorded, the video of the entire collision event itself is completely missing, and thus useless as evidence for establishing blame. It has therefore completely failed at carrying out its primary purpose. Fortunately on this occasion the accident circumstances themselves were sufficient to establish who was the guilty party, but not all accidents are as clear cut as this, of course. According to the reviewer, VIOFO has been informed of the incident and are investigating, but other owners of this (and possibly other models too) are advised to try and check the impact functionality of their cameras, just in case you ever need to rely on it.
A229 Pro glitch failed to record full accident impact footage
- Thread starter RafflesNH
- Start date
lufa6977
Active Member
I hope he sent that camera back to VIOFO for replacement. I have experienced where there have been no recording during driving. Every time the camera would notify recording on vehicle start, but later during driving I would get the voice notification that two channel recording started. When checking the files, there would be a big gap between recording. Firmware related as far as I am concerned. Problem ended on one of the FW updates.
Vortex Radar
Well-Known Member
- Joined
- Mar 26, 2014
- Messages
- 888
- Reaction score
- 1,444
- Location
- Seattle, Washington
- Country
- United States
Yikes! Definitely not good. I'm so glad his wife is okay.
Regarding the dashcam, this is definitely unfortunate, especially since the primary reason we run these is to help is in case of crashes just like this. Fortunately the interior camera still worked, but it's strange that the front cam cut out with properly capturing and saving the clip with the impact. Not sure why that happened, but I'm glad he's reported it to Viofo and hopefully they can identify and fix the issue in a future firmware update.
On a different note, I wonder if the issue was related to the G-sensor trying to save that file to a separate location. Personally I generally disable the G-sensor while driving because it can wind up "protecting" clips when I hit a speed bump or pothole. In case of a crash like this, I'm definitely pulling the video footage soon and not worried about the file eventually getting overwritten, you know? While most people use the G-sensor feature, it's on by default, and obviously it shouldn't create any issues of its own, I'm curious if the dashcam would have recorded properly if he had disabled the G-sensor feature while driving.
Regarding the dashcam, this is definitely unfortunate, especially since the primary reason we run these is to help is in case of crashes just like this. Fortunately the interior camera still worked, but it's strange that the front cam cut out with properly capturing and saving the clip with the impact. Not sure why that happened, but I'm glad he's reported it to Viofo and hopefully they can identify and fix the issue in a future firmware update.
On a different note, I wonder if the issue was related to the G-sensor trying to save that file to a separate location. Personally I generally disable the G-sensor while driving because it can wind up "protecting" clips when I hit a speed bump or pothole. In case of a crash like this, I'm definitely pulling the video footage soon and not worried about the file eventually getting overwritten, you know? While most people use the G-sensor feature, it's on by default, and obviously it shouldn't create any issues of its own, I'm curious if the dashcam would have recorded properly if he had disabled the G-sensor feature while driving.