V2.0 Firmware for Public Testing

I will say every other feature on this camera seems to work perfect. And I like it very much. Just must be something I am doing wrong on the setup. Is it safe to load the first update it had as new and then try again? Or can one of my settings be wrong.? IT ACTS PERFECT EXCEPT FOR THE NOTIFICATION.
Could there have been a problem with upgrade V2.0 - 102825 The unit said it updated successfully ??
 
Last edited:
mentadent said:
If it was perfect, they wouldn't be testing though.
Click to expand...


Understood and I agree, my point is if they're testing it should be Beta, not public.
But I'm old, and old school. Using the public as beta-testers has been a thing for
quite a few years, and in many industries.

They got my money, and I have their product and I'm happy with it. You early-adopters,
you tip-of-the-spear guys, have at it. I'm enjoying following the progress. When the
water is right I'll jump in. 😉
 
Forester25 maybe they will read it and developer will add it to bug list.
 
I will be keeping mine also. As good as this unit is I still feel I must have something wrong.
As far as the upgrade it is better now with more features. Just one glitch.
 
It'll be some strange bug like some bit or byte or variable got wiped when some setting they were testing did this or that, they'll figure it out with enough reports.
 
I am hoping soon Viofo will have another update that can be tried. The V2.0 102825 update really helped with GeoFencing. Or can give a idea to try. I think the notification of a impact would be handy and I am sure that is why it was included.
Hard to imagine I want to see something but then never want to see it again.
 
It's a shame that support for new features are essentially dropped for the previous flagship when VIOFO releases a new dashcam.
 
van1337 said:
It's a shame that support for new features are essentially dropped for the previous flagship when VIOFO releases a new dashcam.
Click to expand...
What new features are you expecting? Some features may just require firmware updates. Others might be hardware-dependent.
 
van1337 said:
It's a shame that support for new features are essentially dropped for the previous flagship when VIOFO releases a new dashcam.
Click to expand...

As I use my original A329 as my back camera, it would be nice to see some of the new functions that aren't related to hardware differences added to that as well (like the geofencing, which I assume should be compatible since the GPS modules are identical between A329 & A329S).
 
It seems I am having a little communication problem describing the problem with this camera. Have tested so many times and tried to explain it gets frustrating.

Viofo,

Will try once again. Even though the config file shows I have impact notice setting ON .

For the most part the camera works fine. Camera has been tested so many times that I connect a battery minder to the car battery to make sure the voltage is up all the time when testing. HK-6 is set to 12 volt. Low Impact Mode is selected in settings. Notification is turned ON. When I make a impact nothing happens that I can tell, the camera does not turn on lights. The camera does NOT notify of impact turning on a least 5 min latter it only does a regular start up, no notification of a impact is disclosed. Latter when checking the micro sd card a Read Only file was created. And shows proper time of impact. I hope this explains correctly as I am getting tired of explaining.
 
Last edited:
@Forester25 I adjusted my PM settings to match yours and tested--I also encounter the lack of visual or voice notification of impact when the cam comes out of PM into regular recording, but like you the locked video file is there as expected.

I even tried adjusting the Voice Notification setting from On to Only Critical Alerts with no change to this specific behavior (well, lack of expected behavior to be accurate).

I recognize this is a beta firmware, so hopefully Viofo is working on a solution for this.
 
Thank you very much for your test and report. So maybe the problem is just with their up date. Thanks so much for responding. I am 81 now and I'm trying to get this corrected for my wife. Without a notice of impact you loose the awareness at the time of the event possibly. Trying only the critical alerts was also my next move, but not needed now. Again thank you for letting me know. Please let me know if you are able to solve the issue. And I the same.
Added: Well actually I don't need to test any more, just wait for @viofo to fix.
 
Last edited:
Ok, somewhat related to new software releases in general, and simultaneously somewhat off topic. I used to be a software engineer, so this is especially entertaining to me:

 
Well I feel a lot better now. It is only going to be a temporary problem now. And I do not need to bang my head against the wall. With the V.2 update the camera is better than when it was bought and I can look forward to the fix. I am learning from the experience. So I am good.
 
Haha the QA getting kicked in the nuts.

@Forester25 your reports are also helping make the product better for everyone!
 
speedingcheetah said:
This is rather useless a setting if implemented this way.
It is not what i had asked for.

The cams are still cropping to 21:9, image is still being lost. Stretching the cropped image is just removing the letterboxing and distorts the image.
The point to having 16:9 on Tele and Rear is to capture the full frame with no cut off. The tele cam most importantly needs full frame field of view.
Having the front wide angle cam cropped to 21:9 is beneficial to remove static dash and excessive sky.

I had asked, a few times i believe, if there is a technological reason as to why each cam can not have its own set ratio setting.
I gather, since each cam does not have its own cpu/encoder etc, the main front cam has a single cpu encoder, and can only encode at one master setting for its inputs.
Encoding each channel with independent settings, might require multiple encoders, or multi threaded processing.
However, VIOFO was able to modify the video metadata to set the other cams ratio to 16:9, but it still is applying the 21:9 crop...so something is messed up with that.

I can tell with my rear cam, it is being cropped in 21:9, as it cuts off my rear wiper, same as when i set it in all cams to 21:9. In the all cams to 16:9, it shows.
Click to expand...
Have you tried the latest 1027 version?
 
VIOFO-Support said:
Have you tried the latest 1027 version?
Click to expand...
There was nothing in the change log to indicate any change in this issue. I do not recall changing the setting back to that resolution after the cam reset after upgrading to see if anything changed with that issue.

Will check next time have a drive unless someone else here confirms any change with it in the meantime.
 
jsmith said:
because
Click to expand...
jsmith said:
I believe QA is kicking the Developer in the nuts? Makes more sense because Quality Assurance nitpicks everything that's wrong with the Developer's work!
Click to expand...
Haha you're right. Hope they pass the kicking on to the rest of the team.
 
VIOFO-Support said:
Have you tried the latest 1027 version?
Click to expand...
I can confirm the issue of the stretched video ratio (the rear and tele cam being 21:9 and stretched to 16:9) appears to be resolved in the newest beta firmware 1027.
Thank You!
 
You must log in or register to reply here.
Back
Top