Reviewing and Testing the new Vantrue N4S Dashcam

Yep, there are a variety of potential mechanisms. I'm more interested in the outcome than the specific process that reaches that outcome. My protocol was really just a thought exercise: "What's a simple way to achieve XYZ result?"
 
I don't think my Viofo cameras need settings to be reconfigured after a firmware update. I know they still recommend a reset after the update but the settings are not automatically reset.
 
I don't think my Viofo cameras need settings to be reconfigured after a firmware update. I know they still recommend a reset after the update but the settings are not automatically reset.

Trust me, you want to reset everything back to factory defaults... It holds true for a computer's bios settings after firmware updates, too. Clears out any potential conflicts. I've had dashcams act erratically after update until i cleared settings.
 
Hack_man said:
I don't think my Viofo cameras need settings to be reconfigured after a firmware update. I know they still recommend a reset after the update but the settings are not automatically reset.
Trust me, you want to reset everything back to factory defaults... It holds true for a computer's bios settings after firmware updates, too. Clears out any potential conflicts. I've had dashcams act erratically after update until i cleared settings.
I worded it very poorly. I agree it makes sense to reset menu settings back to factory after a F/W upgrade to prevent conflicts, although I have not reset and experienced no adverse effects.
The Viofo camera does not automatically reset its user menu settings when its firmware is updated (unlike Vantrue). Viofo maintains the pre-F/W upgrade user menu configuration and depends on the user to reset them (as recommended by Viofo).
Vantrue cameras reset menu settings after a F/W upgrade to a factory default state which prompted @EricSan to recommend Vantrue consider an automatic process to reload them back to the original user preference.
At least that's how I see it working.
 
Last edited:
I worded it very poorly. I agree it makes sense to reset menu settings back to factory after a F/W upgrade to prevent conflicts, although I have not reset and experienced no adverse effects.
The Viofo camera does not automatically reset its user menu settings when its firmware is updated (unlike Vantrue). Viofo maintains the pre-F/W upgrade user menu configuration and depends on the user to reset them (as recommended by Viofo).
Vantrue cameras reset menu settings after a F/W upgrade to a factory default state which prompted @EricSan to recommend Vantrue consider an automatic process to reload them back to the original user preference.
At least that's how I see it working.

Correct. Viofo doesn't reset and Vantrue automatically resets. Vatrue takes a proactive approach (although creating a file with settings saved would be idea). Viofo assumes the user will know to reset after firmware update.
 
@Jeff_Vantrue I have another "wish list" item: Is it possible to preserve the menu settings during a firmware update?

I'm thinking something like this:
1) before starting the firmware update, write all current menu settings to the SD card as a text file
2) perform the firmware update
3) after the firmware update is complete, but before the "format SD card" action happens, open the text file containing the menu settings and read back in and restore the menu settings that are still appropraite to the new firmware. I'm assuming that not all settings will remain consistent between firmware versions, so just scan the text file for those menu settings that are still relevant/present and restore them. It won't be 100%, but will save a bunch of fiddling that is associated with each firmware update.
4) then format the SD card (or not...)
Thanks for your suggestion! We also agree that having to reconfigure settings after every update can be quite tedious. However, our current approach is intended to clear out any potential conflicts that might arise from previous firmware versions.
Technically, your idea is feasible and we’ll evaluate it carefully and consider implementing it in future updates. Thanks again for sharing your thoughts!
 
our current approach is intended to clear out any potential conflicts that might arise from previous firmware versions.
I understand this perspective, especially in light of the recent timer changes to the PlatePix feature. A quick "range check" of parameters can address this while settings are being read back in.
 
I have posted a number of comparisons between the N4S (3-ch) and N5S (4-ch) cameras. It looks like the front camera from each of these dashcams are highly similar. There are some differences (which vary by lighting conditions), which seem to indicate that a different algorithm is at play with each camera. Overall, resolving power of the forward facing cameras as evident in the resulting video files is highly similar (to be expected given that each uses the same lens and sensor).

 
Last edited:
Back
Top