V2.0 Firmware for Public Testing

@VIOFO-Support is there any chance of getting option to keep all parking recording on the SD Card even with SSD in use for normal recording?
A setting already exists for this: Video Settings > Parking Recording > Parking Files Storage
 
A setting already exists for this: Video Settings > Parking Recording > Parking Files Storage
Doesn't work (any more at least) when using hybrid mode parking, which is my point. In hybrid mode that setting is ignored; if you try to change it won't let you select the SSD however parking files that are not from low power impact detection end up on the SSD. And what I'm experiencing is what the blog post says is meant to happen. The setting might work for non-hybrid parking modes, have not tested that.
 
Doesn't work (any more at least) when using hybrid mode parking, which is my point. In hybrid mode that setting is ignored; if you try to change it won't let you select the SSD however parking files that are not from low power impact detection end up on the SSD. And what I'm experiencing is what the blog post says is meant to happen. The setting might work for non-hybrid parking modes, have not tested that.
Thanks for pointing that out. I reviewed the 2.0 beta blog post again and found the section that describes the new behavior when hybrid parking mode is used. I've been using low bitrate parking mode and with the parking mode file storage set to SSD. I haven't noticed a change using that configuration [low bitrate parking files always stored on the SSD]. Whenever LPID is used [directly or via hybrid parking mode], it must store the LPID parking files on the microSD card.
 
The version i am on is working fine.
The only anomaly i had was, after sitting in parking spot for a few minutes, the cam suddenly announced "Parking mode recording started" (something like that, for sure parking mode something), wich is odd, cause i do not use parking mode and is connected via usb adapter, so should not have any way to trigger parking recording.
Do you have an HK6 in the car?
 
@VIOFO-Support the Google Drive link for 2.0beta published in your blogpost is no longer available.
Where to look for the latest 2.0 beta firmware for the A329S?
Any news on when it would go public?
 
There is a download link in the first post of this thread
Cheers mate! Already downloaded and flashed.
Do they update this topic regularly with the new betas?
Any chance to get the changelog for between the specific versions?
 
There is a download link in the first post of this thread
AFAICS that's just for A329S

Is there a beta u/d applicable to the A329T?
 
@VIOFO-Support

As you may recall I was having significant issues with the prior firmware update of 12/5/25. However, soon thereafter, Viofo came out with the 12.30 update. As you may recall, I was about to downgrade to the original firmware because of the issues I was having with the 12/5/25 update.
Viofo, then updated their firmware to 12.30 and I reluctantly updated to that version about a week ago when they first came out with it. Since then I have not had the issues that I was encountering. No more blinking lights and slow card error messages. It appears that the updates are headed in the right direction at least in regards to the issues that I was having with the 329S. I have 3 of them installed and they were all having the same issue.

Thank you for the latest update.
 
An observation.

Viofo is listening and trying to introduce features other dash cams don't have in their entirety.
Being a beta tester is frustrating but can have its rewards.
Being frustrated about viofo trying to resolve request might mean it would be better for some not to participate in the testing.

Badgering the company may lead to them not listening or trying anymore.

Other companies are much slower at introducing improvements, partly, I suspect, due to internal processes. (Some don't really care once the product has been released. )

To be clear I am in no way affiliated with viofo. I don't have an A329S.

I just felt something was being overlooked with this open approach from Viofo.

I'll add imo. Lol
 
An observation.

Viofo is listening and trying to introduce features other dash cams don't have in their entirety.
Being a beta tester is frustrating but can have its rewards.
Being frustrated about viofo trying to resolve request might mean it would be better for some not to participate in the testing.

Badgering the company may lead to them not listening or trying anymore.

Other companies are much slower at introducing improvements, partly, I suspect, due to internal processes. (Some don't really care once the product has been released. )

To be clear I am in no way affiliated with viofo. I don't have an A329S.

I just felt something was being overlooked with this open approach from Viofo.

I'll add imo. Lol
100 percent agree.

I have seen some posters recently being overly aggressive with VIOFO support on the update issues and there really is no need for that. That is why I felt that I had to post about the newest update and to provide feedback to them. I did provide information regarding the 12.5 issues that I was having not to badger them but provide the feedback that they need in order to improve the firmware. It was almost within a few hours that they posted the new version which I am sure was in the works so I know they are listening and constantly attempting to improve.

They are excellent in listening to their customers and we certainly want to encourage that interaction. You are right on the money that being a beta tester is not for everyone.

In any case, I am glad you spoke up. I also find that their tech support outside of the forums are excellent as well.

Thank you for your input and your insight.
 
A report on the most recent firmware or camera in general, not sure.

A329S on the latest December 30 firmware.
Powered via a BP100 on the yesterday's firmware.

Today was a hot day. Left car baking in the sun. Camera went into the parking mode when I was leaving.
Came back two hours later to a camera with display either being off or displaying a triangle with an exclamation mark.
I (with big degree of certainty) assume that my camera overheated.
It was so hot to touch I couldn't hold on to it for more than 3-5 seconds.

The issue: when I started the car my camera stayed in either "OFF" or "parking mode".
When I started driving the camera never left the parking mode.
It kept cycling between the triangle with an exclamation mark, parking mode notifying me of the "impact" (I'm driving) and being all lights off.
It never went out of parking mode until I forcefully restarted it by holding the menu button long (OFF) and then short (ON).

I'm scratching my head now on how to protect the camera from heat while at the same time leave it seeing out of the vehicle.
If you know - share your tricks.

Didn't realise Aussie sun would make my camera go bonkers this quick.
 
Today was a hot day. Left car baking in the sun. Camera went into the parking mode when I was leaving.
Came back two hours later to a camera with display either being off or displaying a triangle with an exclamation mark.
What parking mode were you using?
 
A report on the most recent firmware or camera in general, not sure.

A329S on the latest December 30 firmware.
Powered via a BP100 on the yesterday's firmware.

Today was a hot day. Left car baking in the sun. Camera went into the parking mode when I was leaving.
Came back two hours later to a camera with display either being off or displaying a triangle with an exclamation mark.
I (with big degree of certainty) assume that my camera overheated.
It was so hot to touch I couldn't hold on to it for more than 3-5 seconds.

The issue: when I started the car my camera stayed in either "OFF" or "parking mode".
When I started driving the camera never left the parking mode.
It kept cycling between the triangle with an exclamation mark, parking mode notifying me of the "impact" (I'm driving) and being all lights off.
It never went out of parking mode until I forcefully restarted it by holding the menu button long (OFF) and then short (ON).

I'm scratching my head now on how to protect the camera from heat while at the same time leave it seeing out of the vehicle.
If you know - share your tricks.

Didn't realise Aussie sun would make my camera go bonkers this quick.
First, we suggest upgrading the firmware to the latest V2.0 20260104 version.

We are checking how to optimize the parking recording to avoid overheating and provide limited parking recording protection.
We can let the camera switch to impact-only recording while it overheats. When it starts up next time by impact, it can check the vehicle voltage or BP100 capacity.
If the chipset temperature is low and the voltage or battery pack capacity doesn't meet the specified value, the dashcam will continue recording.
 
What parking mode were you using?
My camera was in a Hybrid Parking Mode with time delay.
Low Bitrate -> 3 hours -> LPID (Low Power Impact Detection).

Firmware 12.30, end of December 2025: VIOFO_A329S_V2.0_251230

Front and Rear cameras connected (no internal).
GPS off, LEDs off.

Powered via BT100.

Ambient air temp at the time was around +40˚C.
Temp inside the car when I got back into it.... not sure. 50˚C+ easy, maybe higher.
Car was left baking in the direct sunlight, no shade, no clouds, no tinting allowed on the windshield, hot sunny summer Australian day.
Camera was too hot to touch for too long.
 
Last edited:
We can let the camera switch to impact-only recording while it overheats. When it starts up next time by impact, it can check the vehicle voltage or BP100 capacity.
If the chipset temperature is low and the voltage or battery pack capacity doesn't meet the specified value, the dashcam will continue recording.
Yeah. Good idea!
Go in LPID for thermal protection,
wake up and check power/voltages/remaining-battery-charge
try to get back into the appropriate parking mode or (if already driving) to a driving mode.

I believe I've seen similar algorithm advertised on Thinkware U3000Pro camera.
Here's the image I copied from Thinkware website:

1767920325082.webp
 
Back
Top