Aftrbrnr
New Member
As Nextbase support pointed out, probably the most useful thing you can do is use the myNextbase Connect App to download the clip you want to your phone via the camera's wifi function, which you should probably do as soon as possible after the incident. After tinkering around with my 522GW, I noticed another thing you could do is through the playback function, you can manually "protect" clips of your choice, even the standard 1 to 3 minute clips the camera produces. I see this as the same as other cams that save the whole clip through a button press or g-sensor, though no where as convenient especially since you have to stop recording to get to the playback function.
That being said, I do find it odd to remove the ability to save entire clips with a button press for the second gen models given this is a very common, if not almost universal feature on most dash cams. I think I speak for some users on here, but I can't see how difficult it would be to re-implement the feature given its commonality on these devices along with how this was possible on Nextbase's first-gen cameras. As Paul said, it is a possibility Nextbase won't ever do this, but for me, it seems like it would be a relatively simple change to the firmware rather than something complex such as re-engineering the camera's hardware.
One thing I do wonder is what happened with the G-sensor in dundeelad's incident, which no one has pointed out so far. I found even setting the sensitivity on low I still get too many automatically protected clips being produced from bumps in the road. The t-bone impact IMO should have produced enough force to create a protected clip at that moment without them having to voluntarily push the protect button. I could see the possibility they turned off the g-sensor function, but could it have also failed?
That being said, I do find it odd to remove the ability to save entire clips with a button press for the second gen models given this is a very common, if not almost universal feature on most dash cams. I think I speak for some users on here, but I can't see how difficult it would be to re-implement the feature given its commonality on these devices along with how this was possible on Nextbase's first-gen cameras. As Paul said, it is a possibility Nextbase won't ever do this, but for me, it seems like it would be a relatively simple change to the firmware rather than something complex such as re-engineering the camera's hardware.
One thing I do wonder is what happened with the G-sensor in dundeelad's incident, which no one has pointed out so far. I found even setting the sensitivity on low I still get too many automatically protected clips being produced from bumps in the road. The t-bone impact IMO should have produced enough force to create a protected clip at that moment without them having to voluntarily push the protect button. I could see the possibility they turned off the g-sensor function, but could it have also failed?