Purchased A329T - Firmware Bugs / Problems (Help) - Suggestions

@TonyM

Viofo sent me a replacement rear camera, and my preliminary test doesn't show a major flickering like before. I did notice in one lighting some slight metering taking place, but nothing I could categorize as what I experienced before. I need to run more testing before drawing a conclusive result here given I ran about 5 brief 2-3 minute parking mode tests.

Should the issue be resolved, my guess is Viofo had a bad batch of rear cameras given @rcg530 and others replicated issue. Anyway, I'll post back here with more extensive testing ASAP.
 
Last edited:
I wonder why the flicker was only evident in Low Bit Rate parking mode if it was the camera. I assume you are using the same Firmware revision with the new camera.
 
Hack_man said:
I wonder why the flicker was only evident in Low Bit Rate parking mode if it was the camera. I assume you are using the same Firmware revision with the new camera.
Click to expand...

I'm not really sure honestly. I didn't have a lot of time last night to run tests, but did return to the same spots I previously ran them. I cannot find any defined flicker in new camera video matching the old camera. The only changed variable right now is the new camera is mounted about 10CM (4 inches) over from the old camera, as I haven't yet removed the other camera. That placement shouldn't make a difference what so ever.

I'm going to repeat the test tonight more extensively and see what happens.

If there ends up being no flicker, I have zero explanation on why the old camera would only malfunction in low bitrate parking mode. Maybe the lens or internal circuits have an issue with low light focusing and there was a bad batch of cameras during production? Speculative right now, but my only guess.
 
@Chuck McCoy @rcg530 @GPak @TonyM @SafeDriveSolutions

I tested yesterday for about 20 minutes, and spent over 1 hour testing parking mode in various lighting conditions with and without HDR, and there's no flicker in the replacement camera. This leads me to believe that Viofo had a bad production batch of cameras. I absolutely CANNOT explain why the original camera ONLY has a problem in Low Light Conditions, regardless of parking mode selected.

I didn't test other parking modes (only low bitrate) given that all parking modes had flicker issue with previous rear camera. I can test auto event detection and 10 FPS, but I presume that if low bitrate is working, those are, too.

I intend to send the faulty rear camera back to Viofo and let them troubleshoot what might be wrong. Again, with other's replicating the issue, I'm guessing there was an issue with production.

Far as the Sensitive G-Sensor, that continues.....I'll await Viofo to release a firmware, and if that continues, request a replacement front camera, too. I'd rather eliminate the possibility of the camera having an issue, and be wrong, then stick with it and have a faulty unit.

So that's what I discovered. My Rear Camera is part of a faulty production.
 
jsmith said:
Tested a firmware sent to me by Viofo. Seems to solve overly sensitive Parking mode. Not seeing Lock Videos on start.
Click to expand...
Does it sense an impact if you tap the doors or window during parking mode?
 
jsmith said:
I have it set to low sensitivity on everything. I could set it to high and test tapping window??? Or do you want me to keep it at low?
Click to expand...
I was just checking that your A329T remains sensitive enough to detect parking mode impacts. I hope that fixing one issue has not created another.
 
For what it worth, here are my preferred settings:

- For normal driving, the G-sensor is disabled (OFF).
(Rationale: When using a 256 GB SD card, event files are not overwritten for several days; therefore, there is no need to save such files to the (RO) folder, running the risk of potential corruption).

- For everyday parking (LBR mode), the G-sensor is set to medium sensitivity.
(Rationale: This effectively prevents false triggers caused by opening/closing doors or starting the engine, while still ensuring (fingers crossed), that the dashcam will detect a moderate impact, save the recording to the RO folder, and provide a notification).

- For long-term parking, say at airports, hotels, etc., I will switch to (LPID mode), and I will switch the G-sensor to high sensitivity mode.
(Rationale: I want the longest parking recording possible and I want to capture absolutely every possible event—even if some of them turn out to be false triggers).
 
@TonyM @GPak

I tested today and they turned sensitivity WAY DOWN. Probably, too much. You have to set it at high for the camera to register tapping on windshield. Better than a ton of false positive lock videos, but I will let them know their firmware needs some adjustment.
 
@jsmith
Personally, I wouldn't accept custom firmware.
Your G-sensor is obviously out of spec - a defective component.
I would return the entire set and ask for a BRAND NEW replacement.
However, the choice is yours.
 
Last edited:
I have been following this thread and have found it amazing. With many guys chipping in it might have been more difficult. I would have sent it back a long time ago. I feel GPak has the right idea. You will never be able to up grade with normal upgrades. And also it will give this story a proper ending of is it the car or the dashcam. I feel the special update shows fault with dashcam. Anyway good luck.
 
GPak said:
@jsmith
Personally, I wouldn't accept custom firmware.
Your G-sensor is obviously out of spec - a defective component.
I would return the entire set and ask for a BRAND NEW replacement.
However, the choice is yours.
Click to expand...

I have requested they send me a new front camera like the rear camera mailed. If they do not, I will request full return. I think I am in agreement that my unit may be a problem given the rear camera was 100% faulty. Front could be issue, too.

We will see what they say.
 
You must log in or register to reply here.
Back
Top