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

[rcg530]

I've experienced the "video protected" issue when returning from parking mode to normal recording mode with the A329S series for quite some time. The number of times it occurs now has been reduced, but it still happens. During a drive on Friday, it happened one time out of the four parking mode sessions from that driving route. I have firmware v2.0_260104 installed. The parking mode G-sensor setting is set to high and the driving mode g-sensor setting it set to low sensitivity.

The one time it occurred during Friday's driving route was after I had returned to my vehicle and loaded my groceries into the trunk of the vehicle. I closed the trunk which resulted in a parking mode impact event for the U3000 Pro dash camera, but not the A329S. I then returned the shopping cart and returned to my vehicle which is when I opened and closed the front driver side door which resulted in an impact event for the A329S. The currently recording low bitrate parking mode files along with the 1-minutes files from just before that time were placed in the DCIM\Movie\RO directory. Near the end of the low bitrate video file in the RO directory, I started the vehicle's engine. When the ACC power was restored after starting the engine [5-seconds after returning the ignition switch to the "RUN" position - see below], the A329S transitioned from low bitrate parking mode to normal recording mode. The A329S had just resumed recording low bitrate parking mode videos for a total of 2-seconds when it transitioned to normal recording mode.

The first normal mode recording file has a "video protected" announcement 6-seconds into the file. The A329S produced the double beep alerts to let you know parking mode files are present that need to be reviewed. This first 1-minute normal recording video file was also placed in the DCIM\Movie\RO directory.

The ACC power I use for dash camera use in this vehicle is passed through a digital relay with a timer. The logic in the digital relay is that the vehicle's ACC power must be present for at least 5-seconds, before the ACC power is passed along to the dash camera battery pack which passes it along to the HK4 hardwire kit that is powering the A329S. The reason for the digital relay is that my vehicle's available ACC power is on only when my vehicle's ignition switch is in the "ACC" and "RUN" positions. When the ignition switch is in the engine "START" position, the ACC power is turned off. The short time the ACC power was on while I was moving the ignition switch from OFF-through-ACC-through-RUN-to-START was causing some other unwanted behavior with some VIOFO dash cameras only half way exiting parking mode instead of fully transitioning to normal recording mode.

Video files: https://drive.google.com/drive/folders/1ubTpEMs91iDSgI7tYsmhLKWIIG3qT7VB?usp=sharing

 

[Chuck McCoy]

I think I managed to duplicate your low light flicker in LBR Parking Mode.
I could only get 3 “flickers” on film from 12:37:42AM to 12:37:45AM, (about 3 seconds of footage).
If my flickers are the same as your flickers does that mean your camera is not defective?

 

[SafeDriveSolutions]

@VIOFO-Support @viofo has been really silent for some reason. Not sure why?

 

[jsmith]

I think I managed to duplicate your low light flicker in LBR Parking Mode.
I could only get 3 “flickers” on film from 12:37:42AM to 12:37:45AM, (about 3 seconds of footage).
If my flickers are the same as your flickers does that mean your camera is not defective?

@Chuck McCoy Looks like same flicker issue, but I cannot 100% eliminate a shadow effect from flashlight. Presumably, this would mean if the flicker has been replicated then I've identified a firmware bug.

 

[jsmith]

I've experienced the "video protected" issue when returning from parking mode to normal recording mode with the A329S series for quite some time. The number of times it occurs now has been reduced, but it still happens. During a drive on Friday, it happened one time out of the four parking mode sessions from that driving route. I have firmware v2.0_260104 installed. The parking mode G-sensor setting is set to high and the driving mode g-sensor setting it set to low sensitivity.

The one time it occurred during Friday's driving route was after I had returned to my vehicle and loaded my groceries into the trunk of the vehicle. I closed the trunk which resulted in a parking mode impact event for the U3000 Pro dash camera, but not the A329S. I then returned the shopping cart and returned to my vehicle which is when I opened and closed the front driver side door which resulted in an impact event for the A329S. The currently recording low bitrate parking mode files along with the 1-minutes files from just before that time were placed in the DCIM\Movie\RO directory. Near the end of the low bitrate video file in the RO directory, I started the vehicle's engine. When the ACC power was restored after starting the engine [5-seconds after returning the ignition switch to the "RUN" position - see below], the A329S transitioned from low bitrate parking mode to normal recording mode. The A329S had just resumed recording low bitrate parking mode videos for a total of 2-seconds when it transitioned to normal recording mode.

The first normal mode recording file has a "video protected" announcement 6-seconds into the file. The A329S produced the double beep alerts to let you know parking mode files are present that need to be reviewed. This first 1-minute normal recording video file was also placed in the DCIM\Movie\RO directory.

The ACC power I use for dash camera use in this vehicle is passed through a digital relay with a timer. The logic in the digital relay is that the vehicle's ACC power must be present for at least 5-seconds, before the ACC power is passed along to the dash camera battery pack which passes it along to the HK4 hardwire kit that is powering the A329S. The reason for the digital relay is that my vehicle's available ACC power is on only when my vehicle's ignition switch is in the "ACC" and "RUN" positions. When the ignition switch is in the engine "START" position, the ACC power is turned off. The short time the ACC power was on while I was moving the ignition switch from OFF-through-ACC-through-RUN-to-START was causing some other unwanted behavior with some VIOFO dash cameras only half way exiting parking mode instead of fully transitioning to normal recording mode.

Video files: https://drive.google.com/drive/folders/1ubTpEMs91iDSgI7tYsmhLKWIIG3qT7VB?usp=sharing

Thank you for chiming in.

My vehicle has a "Harder Start" which triggers the Dashcam Lock EVERY TIME I go from Parking ---> Normal Mode. My G-Sensor is set to Low Sensitivity for BOTH Parking Mode and Normal Mode. I did test "OFF" in Normal Mode without success to see if the Lock would not Trigger during the Parking --> Normal Transition Without Success (Lock Triggered). I am on the same firmware as you.

Note: If i sit in my vehicle, turn off the engine, let the camera enter parking mode, and then "Start" my car using the Ignition Button (without enabling engine) the, camera starts WITHOUT Locking the Video.

My only thought is either the Rougher Start of my Vehicle (2015 Volvo with 4 Cylinder Turbo) is causing the OVERLY SENSITIVE G-Sensor to trigger every time my car starts and exits the camera from parking mode. That or the G-Sensor in my Camera is Faulty.

What are your thoughts @rcg530 on my camera? Firmware Bug being too sensitive on my car for the G-Sensor or issue on Camera itself?

@EricSan also drives a Volvo and I am not sure where he's been on this forum. If he has his A329 hardwired, he'd be the perfect person to chime in, too.

 

[jsmith]

@VIOFO-Support @viofo has been really silent for some reason. Not sure why?

@SafeDriveSolutions

They asked if the rear camera has a flicker issue in other parking modes. I'll have to do my best to get that done ASAP as time permits. I was told they forwarded my concerns to their engineers regarding the rear flicker. Maybe they are trying to replicate the problems? I've not gotten any specific response beyond that from @VIOFO-Support @viofo

Far as the G-Sensor issue triggering Lock every time my vehicle starts, it doesn't happen when I transition the camera from Parking --> Normal using the Ignition (not starting engine). My vehicle has a rougher start by design and it triggers every time I start the engine from Parking --> Normal.

Not sure if my G-Sensor (set to low in Parking and Tried Low and OFF in Normal) is faulty or if Viofo set this to be WAY TOO SENSITIVE. My Vantrue Cameras nor the A139 Pro I own trigger when the car starts.

I'm at a loss on how to proceed on G-Sensor issue. It's hair trigger sensitive on my unit and not sure if that's Firmware or Hardware related. I emailed Viofo stating I am willing to do tests, but I need PROMISE that if unit is faulty, I am guaranteed a NEW replacement, not refurbished. My unit isn't a freebie, as I paid full price. Waiting to hear back.

 

[Chuck McCoy]

OK, I’m sure I duplicated the same flicker as you this time.
I used a different flashlight.
So, I don’t think your camera is defective.
It just needs better firmware tuning in LBR Parking Mode.
Would you agree?

As far as your G-Sensor issue, I think that’s the way it’s going to have to be.
If Viofo make any changes to sensitivity it’s going to negatively effect LPID, and that is their baby.

 

[jsmith]

OK, I’m sure I duplicated the same flicker as you this time.
I used a different flashlight.
So, I don’t think your camera is defective.
It just needs better firmware tuning in LBR Parking Mode.
Would you agree?

As far as your G-Sensor issue, I think that’s the way it’s going to have to be.
If Viofo make any changes to sensitivity it’s going to negatively effect LPID, and that is their baby.

Looks like a flicker issue to me. So this is a confirmed Firmware Bug. Viofo is wanting me to test in other parking modes to see if problem persists there, too. I'll do so ASAP if not tonight then I'll shoot for tomorrow.

Maybe Viofo can make an adjustment to the sensitivity in a custom firmware for me. Otherwise, if that's just how things are on the Lock / G-Sensor issue with my car (camera / G-sensor not being faulty), and Viofo won't make adjustments, guess I'll live with it and format the SD card more often.

I'll continue to test camera as I use it for more bugs, too. Viofo is getting freebie help from a paid customer 😉. Ideally, moving forward, Viofo will just include me in their future product testing to find bugs.

 

[Chuck McCoy]

Making custom firmware just for you ain’t sustainable.
Every time a new official firmware gets released on the public website, they’ll have to make another one just for you.
Viofo is working on 100’s of things more important than these two issues for future cameras to stay ahead of the market / competition.
I’ve been reporting some of the same issues for 6 years.
Not only are they still not fixed, but they somehow keep finding their way into the new models. lol
VIOFO IMPROVEMENT WISHLIST 2026

Because you are a paying customer I’m not saying your issues are not important, and they should not be fixed.
But in the grand scheme of things your issues are not important, and should not be fixed at this time.
If you reported these bugs when the camera was released May 19, 2025, (11 Months ago) that would be a different story.
Time has moved on, and you're late to the party.
And I hope Viofo starts sending you “freebies” for bug testing because then you will realize they ain’t FREE.
Your leisure time will replaced with actual WORK. lol

 

[jsmith]

Making custom firmware just for you ain’t sustainable.
Every time a new official firmware gets released on the public website, they’ll have to make another one just for you.
Viofo is working on 100’s of things more important than these two issues for future cameras to stay ahead of the market / competition.
I’ve been reporting some of the same issues for 6 years.
Not only are they still not fixed, but they somehow keep finding their way into the new models. lol
VIOFO IMPROVEMENT WISHLIST 2026

Because you are a paying customer I’m not saying your issues are not important, and they should not be fixed.
But in the grand scheme of things your issues are not important, and should not be fixed at this time.
If you reported these bugs when the camera was released May 19, 2025, (11 Months ago) that would be a different story.
Time has moved on, and you're late to the party.
And I hope Viofo starts sending you “freebies” for bug testing because then you will realize they ain’t FREE.
Your leisure time will replaced with actual WORK. lol

I already bug test for Vantrue and receive all of their products upon request. I've got no problems donating my time if there's an end benefit.

The Flicker issue affects everyone and it does appear Viofo is showing a genuine interest in resolving by requesting that I test various parking modes. I think this is a much bigger concern than the G-Sensor. Flicker affects the quality of recordings.

 

[rcg530]

What are your thoughts @rcg530 on my camera? Firmware Bug being too sensitive on my car for the G-Sensor or issue on Camera itself?

With this particular vehicle [Chevy Caprice], the digital relay with timer is delaying the ACC power restoration to the HK4 until 5-seconds after I return the ignition switch to the RUN position. The 6.0L engine in this vehicle is not perfectly smooth while idling, but it's not super rough.

The A329S in my Chevy HHR is a different story. I powered that A329S with a VIOFO OP100 OBD-II power adapter. I reviewed my stored video files from this vehicle and the A329S. I could not find any examples of the this behavior once I had "final" version of the OP100. The early OP100 test units did not work well with my vehicle for parking mode since they would restore ACC power to the dash camera when OP100 had detected an impact event had taken place. The OP100 should have kept the ACC power off to the dash camera until it detected the vehicle had been started. The final test unit/production OP100's firmware properly handles an impact event while parked and it leaves the ACC power off so the dash camera's parking mode can handle the impact event. The OP100 now waits for the vehicle voltage level to rise before it will restore the ACC power to the dash camera. It could be a timing thing [race condition], but the OP100 powering the A329S in my Chevy HHR doesn't seem to produce this behaivor [so far].

 

[Chuck McCoy]

A329S has been on the global market for 11 months.
You are the only person to report LBR flicker.
Saying it affects “everyone” is a stretch. lol

 

[jsmith]

A329S has been on the global market for 11 months.
You are the only person to report LBR flicker.
Saying it affects “everyone” is a stretch. lol

This is a dashcam enthusiast website. Most people that buy technology (or dashcams) use it at the most basic of levels. I doubt 95% of people who purchase a dashcam install it themselves or do anything beyond plugging it in and grabbing a video at random when needed (accident). The majority of time, the regular consumer plugs it in and has little understanding of the intricacies of day in and day out usage.

How many NON ENTHUSIASTS (regular consumer) have you encountered in life that can explain the various parking modes? Understand how to setup a dashcam, etc? Not many.

I would imagine the flicker affects all A329T/S series cameras. People don't check or run their product through the paces for bug testing. You'd be lucky if the consumer even has their camera configured properly.

 

[jsmith]

Auto Event Detection FLICKERS on rear camera: - If you cannot see it (at end) I'll post the longer clip.

Time Lapse Flickers at 10 FPS (Need to edit video will post later).

 

[VIOFO-Support]

Auto Event Detection FLICKERS on rear camera: - If you cannot see it (at end) I'll post the longer clip.

Time Lapse Flickers at 10 FPS (Need to edit video will post later).

Thanks for your testing, I will forward this to our engineering team.

 

[jsmith]

@VIOFO-Support - Light Metering Problem issue on other Parking Modes. I think testing these two proves issue not just low Bitrate.

Sensitivity of G-Sensor for starting my car and G-Sensor Triggers Lock. G-Sensor Lock does not trigger if starting car with 12V Ignition without turning on Engine. Thus, issue is G-Sensor is very Sensitive to shaking of my car when engine start. G-Sensor too sensitive in Low Sensitivity Parking Mode or Maybe Faulty if Trigger too easily in parking.

Please Advise:

Time Lapse 10 FPS Flicker Video: (Sorry for Delay): 57 Seconds for instance....

 

[jsmith]

General FYI: This is how my cameras are mounted. A139 Pro on the Right. Vantrue N5S Center. A329T on Left. Smaller Cameras are the Interior A139 Pro Left and Telescopic A329T on Right.

The A329T is at the very top near headliner due to the Wiper Clearance and also to remove from out of my view. I'm not sure if this is affecting the G-Sensor at all due to location. Either way this is my setup.

 

[GPak]

Sequence: Car shuts off --> A329T enters parking mode --> Car Starts - A329T Locks Video every time Car Starts and Exits Parking Mode --> Returns to Normal Recording: See Videos:

@jsmith
In post #24, I mentioned excessive camera vibration, sufficient to trigger the G-sensor even at low sensitivity, when the engine is started.

But then I was misled by the information that the G-sensor activates even when the ignition is turning ON, without the engine starting, which led me to assume your G-sensor was faulty.
We now know that this is not the case.

So, I return to my original thought about the problem with your G-sensor.
Again, after reviewing the original videos provided, I believe the "issue" with the G-sensor is related to significant camera vibration.
This significant vibration could be due to combination of your specific car-rough staring engine and perhaps poor camera installation on windshield.
(Other cameras installed in your car are not a good reference in this case in my opinion)

Look at the bottom edge of the camera when the engine is started.
None of my cameras vibrate even close to this when I start the engine; in fact, there is no visible vibration at all.

 

[Chuck McCoy]

@GPak said:
Look at the bottom edge of the camera when the engine is started.
None of my cameras vibrate even close to this when I start the engine; in fact, there is no visible vibration at all.
@Chuck McCoy
Yes. Yes. Yes.
This is why I'm always saying; "remove camera from car, and bench test in house" when people report curtain malfunctions. lol
We need to isolate the camera to check for proper operation BEFORE installing in car.
But, AIN'T NOBODY GOT TIME FOR THAT

 

[jsmith]

@jsmith
In post #24, I mentioned excessive camera vibration, sufficient to trigger the G-sensor even at low sensitivity, when the engine is started.

But then I was misled by the information that the G-sensor activates even when the ignition is turning ON, without the engine starting, which led me to assume your G-sensor was faulty.
We now know that this is not the case.

So, I return to my original thought about the problem with your G-sensor.
Again, after reviewing the original videos provided, I believe the "issue" with the G-sensor is related to significant camera vibration.
This significant vibration could be due to combination of your specific car-rough staring engine and perhaps poor camera installation on windshield.
(Other cameras installed in your car are not a good reference in this case in my opinion)

Look at the bottom edge of the camera when the engine is started.
None of my cameras vibrate even close to this when I start the engine; in fact, there is no visible vibration at all.

@GPak

The misinformation on the Start via 12V was a bit of a misunderstanding on my part. Sorry. I didn't test the 12V ignition (without engine starting) both ways.

A. I first tested hitting the Menu Button (3 lines) to wake camera up from Parking Mode (low bitrate) with 12V enabled (no engine started), and that caused a "Lock File" Event.
B. The second test eliminated the Menu Button in waking up camera from parking mode using 12V Ignition ONLY, and that DID NOT trigger a Lock File.

@Chuck McCoy
Yes. Yes. Yes.
This is why I'm always saying; "remove camera from car, and bench test in house" when people report curtain malfunctions. lol
We need to isolate the camera to check for proper operation BEFORE installing in car.
But, AIN'T NOBODY GOT TIME FOR THAT

@Chuck McCoy

I'm not certain bench testing would have yielded different results. Remember, pressing the 3 Line Button (Menu) to wake camera from Parking Mode TRIGGERS A LOCK VIDEO EVENT.

@GPak

I agree and think the rougher start is triggering the camera's VERY VERY sensitive G-Sensor. The Adhesion itself is fine. Trust me, when I prep the window, you're never getting my cameras off! I use alcohol to clean windshield and then firmly press for about 1 minute. Placement is due to windshield wipers' ability to clear windshield. Dashcam lens need to be below that "residual" line for clearest picture.

Here are 3 videos (1 No Trigger Lock and 2 Trigger Lock) of my vehicle starting with a much clearer video.