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

[jsmith]

I can check my A329T for this issue when I return home from Germany

@TonyM Thank you. My goal is to bug check and make sure what I purchased is working properly. So it's helpful if others can look at items I find to verify. I did this with Vantrue's cameras (those were promotional and given at no charge). This time, I purchased the A329T since I wanted one. My goal here is to assist Viofo to make sure things are stable, given I spent a decent amount of money.

 

[Chuck McCoy]

My goal here is to assist Viofo to make sure things are stable, given I spent a decent amount of money.

Did you ever SUBMIT A TICKET for this?
Since you spent cash money, you might get better results having direct communication with VIOFO.

 

[SafeDriveSolutions]

Unless something has changed, the RO folder will also loop, making room for new files. I don't recall the allocated size, but I think it's around 20% of the card.

We have tested this with viofo cards it does not delete. Even though viofo says their sd cards will. It does not

 

[GPak]

@jsmith
I risk to sound persistent, but could you just turn off the G-sensor in parking mode - and maybe even in driving mode - simply to rule it out completely?
If this solves your problem, then either the G-sensor is faulty, or the vibration when starting the engine is too strong and sufficient to trigger the G-sensor even at low sensitivity.

(The video recordings you provided show excessive camera vibration during engine startup)

 

[jsmith]

Did you ever SUBMIT A TICKET for this?
Since you spent cash money, you might get better results having direct communication with VIOFO.

Wanted to have others verify to make sure before I did any kind of ticket. Viofo is pretty responsive here, too. Will open a ticket.

@jsmith
I risk to sound persistent, but could you just turn off the G-sensor in parking mode - and maybe even in driving mode - simply to rule it out completely?
If this solves your problem, then either the G-sensor is faulty, or the vibration when starting the engine is too strong and sufficient to trigger the G-sensor even at low sensitivity.

(The video recordings you provided show excessive camera vibration during engine startup)

Unrelated to G-Sensor. I hadn't tried off, but did just now. Made no difference. Same issue persists. Appears to be a firmware problem per @SafeDriveSolutions

 

[TonyM]

Unrelated to G-Sensor. I hadn't tried off, but did just now. Made no difference. Same issue persists. Appears to be a firmware problem

Does it also happen if you turn on the ignition (but not the engine), just to send 12V on the ACC line?

 

[jsmith]

Does it also happen if you turn on the ignition (but not the engine), just to send 12V on the ACC line?

Was away Easter Weekend. Yes, happens with ignition.

@Chuck McCoy I submitted a ticket. I also used your linked video from Viofo to show the problem exists even in their own video: @VIOFO-Support @viofo Please watch video from Viofo Promotional. Lock Video Problem in Link when Camera wakes from Parking. I have a TON of unnecessary parking Mode Files on my SD Card Now.

 

[Chuck McCoy]

@jsmith A329S was released May 19, 2025, (11 months ago).
So far you are the only person reporting this malfunction.
I think we are close to getting a solution.
-Chuck

 

[jsmith]

@jsmith A329S was released May 19, 2025, (11 months ago).
So far you are the only person reporting this malfunction.
I think we are close to getting a solution.
-Chuck

@Chuck McCoy

I have the A329T, but assume the A329 series (Video is A329S) all use the same platform except for the interchangeable Telescopic Camera. On low bitrate, an audio prompt appears when car starts that says event has been detected. In the video, the person waves and Auto Event Detection Parking Mode Icon Appears.

The Yellow Triangle Lock only happens in video when Use simulates waking up camera with the 3 lined button. Similar to what happens when the Camera awakes from Parking Mode.

I would like to get to the bottom of issue, even if I am the only one reporting. I found many issues on Vantrue Cameras that I reported, were replicated, and corrected, too. I am very thorough when I test products. I just hate making reviews.

@Chuck McCoy do you have 5 minutes to do a test if you've got parking mode enabled. Can you turn on your car, let it enter parking mode, wait about 2-3 minutes, and hit the 3 line button to simulate waking up the camera. Do you get the "Yellow Triangle".

What about when you start the car from parking mode? Do you get a shutter sound and lock?

I appreciate your help if you're willing to test.

 

[Chuck McCoy]

@jsmith
1.) VIOFO A329 2CH (2024)
2.) VIOFO A329S 3CH (2025)
These are two completely different cameras.

A329S is the same “main unit” for;
A329TC
A329WW
A329T
This is the most confusing naming convention they’ve ever done. lol
I wish they would have called it something like;
A329S 3CH Master (rear, interior, waterproof, telephoto available).
But I guess that’s too long.

I’ve got my (2) A329S 3CH units installed with a dash cam battery pack in an “uncoventional” way.
I’m willing to help, but I’m waiting to hear from Viofo Support .

 

[jsmith]

@jsmith
1.) VIOFO A329 2CH (2024)
2.) VIOFO A329S 3CH (2025)
These are two completely different cameras.

A329S is the same “main unit” for;
A329TC
A329WW
A329T
This is the most confusing naming convention they’ve ever done. lol
I wish they would have called it something like;
A329S 3CH Master (rear, interior, waterproof, telephoto available).
But I guess that’s too long.

I’ve got my (2) A329S 3CH units installed with a dash cam battery pack in an “uncoventional” way.
I’m willing to help, but I’m waiting to hear from Viofo Support .

@Chuck McCoy

Thanks. Very confusing.

May I ask what your "unconventional configuration" may be? If using a dashcam battery park , shouldn't it act the same way if using the HK6? or are you not using the HK6?

I'm honestly just trying to figure out what's going on as to resolve concern, especially if a firmware bug that may have been overlooked by others. Clearly, my vested interest is getting my newly installed and purchased unit functioning 100%. These things happen, so not upset. Vantrue had bugs that affected operation, too. I realize that tech needs tweaking.

In the off chance (don't think it is) that this is hardware related, I'd also like to know, too.

It's the whole reason I posted here first to get feedback. There are people on this forum with far more experience and long term use of the A329S/T/TC, etc series to assist with troubleshooting.

 

[Chuck McCoy]

@jsmith
My unconventional configuration is explained here in post #147: HERE
Yes, I'm using (2) HK6's, but not in the conventional manner.
I'm also not charging the battery pack with the vehicle's charging system / ignition power.

Where did you buy your A329T from?
I'm asking because you may end up returning it as defective.
Most retailers have a 30-day return policy.
Have you not heard from Viofo Support after submitting a ticket?

 

[jsmith]

@jsmith
My unconventional configuration is explained here in post #147: HERE
Yes, I'm using (2) HK6's, but not in the conventional manner.
I'm also not charging the battery pack with the vehicle's charging system / ignition power.

Where did you buy your A329T from?
I'm asking because you may end up returning it as defective.
Most retailers have a 30-day return policy.
Have you not heard from Viofo Support after submitting a ticket?

@Chuck McCoy

Direct from Viofo.com so I hope they will honor a return if item is defective. Amazon doesn't sell the A329T. I've was away for Easter Weekend. Submitted ticket Monday.

 

[Chuck McCoy]

If I’m reading this correctly Viofo’s refund policy is 3-Days, and buyer pays return shipping.

VIOFO Warranty Policy — Coverage, Terms & Claim Process

Latest Update on January 1, 2025 From the date of purchase on, all cameras are covered by 18 months warranty, all accessories are covered by 12 months warranty. You could contact the store where place your order firstly, if they cannot help you out, then please contact us for further support...

www.viofo.com

 

[jsmith]

If I’m reading this correctly Viofo’s refund policy is 3-Days, and buyer pays return shipping.

VIOFO Warranty Policy — Coverage, Terms & Claim Process

Latest Update on January 1, 2025 From the date of purchase on, all cameras are covered by 18 months warranty, all accessories are covered by 12 months warranty. You could contact the store where place your order firstly, if they cannot help you out, then please contact us for further support...

www.viofo.com

I meant exchange versus return for refund. Hoping issue is Firmware. So 90 days, per your screeshot,and Viofo pays shipping, IF DEFECTIVE. Waiting to hear back from Viofo for guidance.

FYI: Read your thread on your Viofo A329S configuration. I'm a bit confused on your logic for forcing camera to run in normal mode and eliminate parking mode. People don't generally shut off, start car, shut off, and start car in rapid succession to cause a dashcam to "Hang" on purpose. Most people shut off car, give camera enough time to enter parking mode, and return X amount of time later after completing their errands. Causing a software lockup in this way isn't fault of manufacturer, but of user not giving camera time to properly transition from one mode to the next.

 

[Chuck McCoy]

It’s all explained right here.
This type of configuration is only for gathering test footage for image quality comparison, not bug testing.
It’s like you read a different post. lol

 

[jsmith]

It’s all explained right here.
This type of configuration is only for gathering test footage for image quality comparison, not bug testing.
It’s like you read a different post. lol

See Below. This was from post #147 that you directed me to read (also screenshot above). I don't see logic here, but testing methods are a personal preference. I've only seen such a failure of parking mode if people don't permit the camera enough time to enter parking mode and exit parking mode. Repeated stops and later starts shouldn't cause software crashes.

The reason I go to these great lengths is because I want to pre-emptively “eliminate” as many possible points of failure that would cause a recording malfunction when I go on a drive cycle to gather test footage.

I’ve always done this since 2019.
And I keep doing it because of the countless malfunctions Robert has reported when gathering test footage on his drive cycles.
When he goes on his weekly shopping trip he usually goes to Costco / Sam’s Club, Post Office, Carl’s Jr. etc.
This involves 4, or 5 ignition cycles where the cameras he’s testing switch from Driving Mode to Parking Mode, and back.
Sometimes by the second, or third ignition cycle a recording malfunction occurs, or a firmware setting gets inadvertently changed that exposes a firmware bug.

 

[jsmith]

@EricSan @Hack_man

Anyone here have the A329S/T hardwired with HK6? And willing to test?

@Chuck McCoy Viofo responded by saying my concern was forwarded to their tech team. So we will wait and see what happens.

 

[Hack_man]

@EricSan @Hack_man

Anyone here have the A329S/T hardwired with HK6? And willing to test?

@Chuck McCoy Viofo responded by saying my concern was forwarded to their tech team. So we will wait and see what happens.

I've been following this thread with interest but Unfortunately I don't have an A329. @EricSan does and is usually up for a challenge.
I found a slightly similar problem on a Reddit thread, but the photo was triggered when Entering parking mode, not upon Exiting parking mode like you are experiencing.

https://www.reddit.com/r/VIOFO/comments/1p2rbx0/viofo_a329s_firmware_20_parking_mode_issue_first

 

[jsmith]

I've been following this thread with interest but Unfortunately I don't have an A329. @EricSan does and is usually up for a challenge.
I found a slightly similar problem on a Reddit thread, but the photo was triggered when Entering parking mode, not upon Exiting parking mode like you are experiencing.

https://www.reddit.com/r/VIOFO/comments/1p2rbx0/viofo_a329s_firmware_20_parking_mode_issue_first

Appears @Augustus and @EricSan are the two who reviewed this in the forum. Hopefully either can chime in.