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

[GPak]

Analyzing the parking Event video in the previous post (by monitoring the time in the lower right corner) - It takes approximately ±6 seconds to transit from parking to driving mode upon turning ignition On/starting engine.

 

[jsmith]

@rcg530
@TonyM
@jsmith

This is not a driving Event Lock issue, the Event Lock Triggers while the dash cam is still in LBR parking mode!
It’s a parking Event.

@jsmith, I do not do reviews, (English is not my native language, so it takes me longer to express my thoughts, type the text, check the spelling, and so on).

However, I have immense respect for the work of all the active members of this community who create product reviews, thereby helping manufacturers improve their products and helping users make informed purchasing decisions.
I try to contribute to this process as much as I can.
You asked for help and I wanted to get to the bottom of this issue.

I tested my camera again and this time I recorded video footage of the testing process.

-The first video is for parking G-sensor set to “Medium” – the Event Lock did not trigger.
-The second video is for parking G-sensor set to “High” – I was not gentle enough and Event Lock Triggered the moment I pressed the 3-line button.
-The third video is also for parking G-sensor set to “High” – But this time I was gentle enough so pressing 3-bar button did not trigger Event Lock, but starting the engine did trigger Event Lock (as expected).

I also have the actual video recordings from the dashcam itself - corresponding to this same test - which confirm that this was indeed an Event that occurred while still in parking mode; furthermore, I have screenshots of the contents of the "Move" and "Move-RO" folders, which I will post shortly.

EDIT: I noticed that in the second video, I made a slip of the tongue: I said "driving mode" instead of "parking," and "low sensitivity" instead of "high." Nevertheless, I hope you still grasped the main point.

@GPak

Why is your camera only showing one light at Parking Mode? Do you have all other lights disabled? How is your camera wired for parking mode? I don't see the HK6 notice.

Second Question: Can you do a Video where your camera is in parking mode.... Then you start the camera and let it naturally enter Normal Recording? I want to see if the car Triggers a Lock Event at Startup. Please do for Low, Medium, and High Sensitivity.

Thank you.

 

[jsmith]

Your case differs from the one described by @jsmith
Hope this is a rare exception, and that you will manage to get to the root of the problem and let us know the results.
--------
In the meantime - here are the promised dash cam footage and snapshots:
The first video is still in parking mode - Event saved in RO folder; The video cuts out the moment the dashcam switches to driving mode.
The second video is the first driving recording, saved in regular movie folder (continues from the parking Event recording).

@GPak

@rcg530 is accurate. Any Lock Event file Parking or Normal goes to the RO folder. So when the car starts (immediate in my case. 5 Seconds later in @rcg530 test), the Lock Event is Triggered. This file goes to the RO folder for this specific event. After the event is saved, the camera records normally to the Regular Folder.

I'm confused by your explanation?

 

[GPak]

Why is your camera only showing one light at Parking Mode? Do you have all other lights disabled? How is your camera wired for parking mode? I don't see the HK6 notice.

You can disable the LEDs in the settings to reduce power consumption while parked and make the device less conspicuous.
If I recall correctly, you can choose to leave only the power indicator enabled, or disable all lighting completely

Second Question: Can you do a Video where your camera is in parking mode.... Then you start the camera and let it naturally enter Normal Recording? I want to see if the car Triggers a Lock Event at Startup. Please do for Low, Medium, and High Sensitivity.

Thank you.

This is demonstrated in the videos I have posted (the first and the third videos).
When the parking sensitivity is set to "Medium," the vehicle does not trigger a lock event; at "High" sensitivity, it does.

 

[jsmith]

You can disable the LEDs in the settings to reduce power consumption while parked and make the device less conspicuous.
If I recall correctly, you can choose to leave only the power indicator enabled, or disable all lighting completely


This is demonstrated in the videos I have posted (the first and the third videos).
When the parking sensitivity is set to "Medium," the vehicle does not trigger a lock event; at "High" sensitivity, it does.

You press the 3 Line (Menu Button) to start Camera. What I mean is I didn't see where you had camera in parking mode then car started from Parking Mode to Normal WITHOUT touching Menu Button.

Can you tell me where in video (timestamp) car is in parking mode then started to Normal (engine starts) without touching Menu button?

 

[GPak]

@GPak

@rcg530 is accurate. Any Lock Event file Parking or Normal goes to the RO folder. So when the car starts (immediate in my case. 5 Seconds later in @rcg530 test), the Lock Event is Triggered. This file goes to the RO folder for this specific event. After the event is saved, the camera records normally to the Regular Folder.

I'm confused by your explanation?

Yes, any Event (parking or driving) saved in the same RO folder.
But in your case and in my (high parking sensitivity setting) case the Event is triggered while dashcam is still in parking, i.e. "parking Event".
In @rcg530 case, the event triggers immediately after switching to drive mode—if I understood correctly, i.e. "driving Event"

Different sensitivity settings control parking and driving.

 

[jsmith]

Yes, any Event (parking or driving) saved in the same RO folder.
But in your case and in my (high parking sensitivity setting) case the Event is triggered while dashcam is still in parking, i.e. "parking Event".
In @rcg530 case, the event triggers immediately after switching to drive mode—if I understood correctly, i.e. "driving Event"

Different sensitivity settings control parking and driving.

There are three different problems here:

1. Quirk (Annoyance) waking camera up from Parking mode using 3 Button Menu Creates a Event Lock Trigger.

2. Problem (Firmware Bug) is camera is in parking mode, car starts from Parking Mode, G-Sensor Triggers, and Video Lock / Shutter Sound Triggers. Parking Mode file is moved to RO (Lock File Dir). Your RO (Lock Directory) is filling with unnecessary files when the car starts from Parking --> Normal Mode... This happens whether sensor is set to High, Medium, or Low in Parking Mode.

3. Problem (Firmware Bug) - Rear Camera flickers in Low Light / Dark.

 

[GPak]

You press the 3 Line (Menu Button) to start Camera. What I mean is I didn't see where you had camera in parking mode then car started from Parking Mode to Normal WITHOUT touching Menu Button.

Can you tell me where in video (timestamp) car is in parking mode then started to Normal (engine starts) without touching Menu button?

Okay, I understand what you're asking.

Honestly, I don't think the three-bar button makes a difference here: it doesn't start the dashcam (which is already ON and recording in LBR parking mode), but merely turns on the screen.
Nevertheless, I'll test it tomorrow and post; it's already too late and dark today—plus, my car is currently within a geofenced zone.

 

[GPak]

There are three different problems here:

1. Quirk (Annoyance) waking camera up from Parking mode using 3 Button Menu Creates a Event Lock Trigger.

For me, this only happens at "high" parking sensitivity. (which I consider normal)
Does it trigger for you at "medium" or "low" parking sensitivity?

As I mentioned earlier, pressing the three-bar button while parking serves no practical purpose.

2. Problem (Firmware Bug) is camera is in parking mode, car starts from Parking Mode, G-Sensor Triggers, and Video Lock / Shutter Sound Triggers. Parking Mode file is moved to RO (Lock File Dir). Your RO (Lock Directory) is filling with unnecessary files when the car starts from Parking --> Normal Mode... This happens whether sensor is set to High, Medium, or Low in Parking Mode.

For me, this only happens at "high" parking sensitivity. (which I consider normal)
The cause of triggering parking Event in the "medium" or "low" parking sensitivity may be a "rough engine start," as you described earlier, or the G-sensor in your camera may be defective.

3. Problem (Firmware Bug) - Rear Camera flickers in Low Light / Dark.

This is a real issue, as confirmed by @Chuck McCoy and others.

 

[jsmith]

Okay, I understand what you're asking.

Honestly, I don't think the three-bar button makes a difference here: it doesn't start the dashcam (which is already ON and recording in LBR parking mode), but merely turns on the screen.
Nevertheless, I'll test it tomorrow and post; it's already too late and dark today—plus, my car is currently within a geofenced zone.

3 Bar Lock is just Annoyance. I am pointing out "Bugs / Annoyances". Some more important than others of course.

Thanks.

 

[jsmith]

For me, this only happens at "high" parking sensitivity. (which I consider normal)
Does it trigger for you at "medium" or "low" parking sensitivity?

As I mentioned earlier, pressing the three-bar button while parking serves no practical purpose.

Yes. Happens in Medium and Low for G-Lock Trigger with 3 Button Menu Press.... Just Annoyance. I am pointing out Bugs / Annoyance.

For me, this only happens at "high" parking sensitivity. (which I consider normal)
The cause of triggering parking Event in the "medium" or "low" parking sensitivity may be a "rough engine start," as you described earlier, or the G-sensor in your camera may be defective.

@rcg530 is reporting G-Sensor Trigger Lock 5 Seconds after his car starts. Mine happens immediately. This seems to be even setting to Low G-Sensor Setting is simply too sensitive. Viofo is telling me a firmware will be out to adjust sensitivity. I will see what happens from there and if my G-Sensor still triggers.

This is a real issue, as confirmed by @Chuck McCoy and others.

Viofo is sending me second rear camera to test again. But yes, I 100% believe this is a real issue and confirmed firmware bug.

Note:

All this free testing 😉 Viofo is getting from a Paid Customer. @Chuck McCoy this is Viofo's flagship camera that's been out 11 months. It's important to fix these bugs unless some new model is coming out that isn't made public. An aside note, Lots of testers, reviews, and freebie A329s handed out.... and I'm the one pointing out these bugs. Goes to show that Reviewing (comparison videos) and Bug Testing aren't one in the same.

 

[GPak]

I forgot to answer your question:

I don't use the HK6 cable -firstly, because I use a DIY battery pack with LTO cells, which has its own app, that provides all the information I need; and secondly, the HK6 cable has a significantly larger diameter compared to the HK4, which is the one I use.

Besides, if memory serves me right, the HK6 consumes slightly more power.

 

[jsmith]

I forgot to answer your question:

I don't use the HK6 cable -firstly, because I use a DIY battery pack with LTO cells, which has its own app, that provides all the information I need; and secondly, the HK6 cable has a significantly larger diameter compared to the HK4, which is the one I use.

Besides, if memory serves me right, the HK6 consumes slightly more power.

Not sure power consumption on the HK6. Out of the scope of my testing / troubleshooting for the moment. By the way, what language do you speak? I couldn't place your accent. Turkish?

 

[GPak]

Yes. Happens in Medium and Low for G-Lock Trigger with 3 Button Menu Press.... Just Annoyance. I am pointing out Bugs / Annoyance.

Definitely your G-sensor is too sensitive, this is not normal.

 

[jsmith]

Definitely your G-sensor is too sensitive, this is not normal.

The 3 Button to wake up camera triggers no matter what. It's an Annoyance.

The G-Sensor Triggering at Startup is happening to @rcg530 even on low sensitivity I believe. Mine happens immediately. His happens after 5 seconds. So waiting for feedback on firmware. If firmware doesn't fix, I will ask for replacement unit.

 

[GPak]

Not sure power consumption on the HK6. Out of the scope of my testing / troubleshooting for the moment. By the way, what language do you speak? I couldn't place your accent. Turkish?

I am Armenian; I am originally from the Republic of Georgia—was part of the former USSR, and now an Independent State.
My native language is Russian (from school, university, and work); I also speak Georgian and Armenian.

 

[GPak]

The 3 Button to wake up camera triggers no matter what. It's an Annoyance.

Agree

The G-Sensor Triggering at Startup is happening to @rcg530 even on low sensitivity I believe. Mine happens immediately. His happens after 5 seconds. So waiting for feedback on firmware. If firmware doesn't fix, I will ask for replacement unit.

I think that in your case, this can be logically explained by an abnormally high sensitivity.
In case of @rcg530 , it would be interesting to know the reason for such behavior; I hope he manages to figure it out.

 

[rcg530]

In case of @rcg530 , it would be interesting to know the reason for such behavior; I hope he manages to figure it out.

The vehicle I have/had the A329S 3CH installed into is my Chevy Caprice. I believe I explained earlier in this thread that this vehicle has a digital relay with a 5-second delay timer in the ACC power circuit that feeds power to the hardwire kits in this vehicle. The only available ACC power in this vehicle that's not involved with a critical module [without going through the firewall and to the front of the engine bay fuse box], is an ACC circuit that is only has power in "ACC" and "RUN" positions of the ignition switch. When I move the ignition switch to the "START" position, the ACC power turns off.

That On/Off toggling of ACC power during a start of the engine was determined to be one of the root triggering causes for some of the older VIOFO firmware versions to only halfway exit parking mode [low bitrate files with normal mode filename suffixes and parking mode sensitivity still in place stored in the "Parking" directory]. The more recent firmware versions [A329S and A229 series] should have a logic patch to help mitigate this behavior for this type of ACC power behavior.

In an effort to stabilize my dash camera installations in this car, I added the digital relay in the ACC power circuit which can be configured with a delay timer to govern when the "LOAD" side of the relay receives power. I programed the digital relay timer so it must see constant power [ACC power in this case] on the supply side of the relay for 5-seconds before the "LOAD" side of the relay is provided power. The ignition switch is not placed or left in the "ACC" or "RUN" position for 5-seconds before I start my vehicle. This results in the HK4 hardwire kit only getting ACC power after the ignition switch has been returned to the "RUN" position after the engine has been started.

In my case, the engine has been running for at least 5-seconds before the ACC power is restored to the HK4. That's when the A329S begins its transition from low bitrate parking mode to normal recording mode. The normal mode MP4 files have the announcement stating "Recording, 3-channels started". At the 5-second mark, this is when the A329S announces "video protected".

In my recent example, there are a few things going on:

• 10:33:08 - LBR files recording
  • 10:33:32 - Trunk closure initiates an impact event "Photo Sound"
  • 10:33:39 - You can hear the "beep" sound of the BlackVue Elite 9 powering up to handle the impact event as well
  • 10:34:08 - This LBR video file set finishes and is placed in the "RO" directory
• 10:34:08 - LBR files recording
  • 10:34:13 - The Elite 9 announces that it connected to the BlackVue Cloud service - "Cloud Connected"
  • 10:34:35 - I open the driver side front door
  • 10:34:44 - I sit down in the front seat and about 1 second later the A329S "Photo Sound" is heard
  • 10:34:46 - Front door is closed - impact beep sound from Elite 9/10 cameras
  • 10:34:52 - BlackVue cloud push notification alert tone from my phone
  • 10:34:56 - Key inserted into ignition switch
  • 10:34:57 - Ignition switch moved to RUN position - windshield wipers make one pass on the windshield
  • 10:34:59 - Ignition switched moved to the START position
  • 10:35:03 - Engine starts - Ignition switch returns to RUN position
  • 10:35:08 - This LBR video file set finishes and is placed in the "RO" directory
• 10:35:14 - Normal Mode Recording Starts
  • 10:35:14 - Announcement from another dash camera is heard
  • 10:35:16 - A329S announces "Recording, 3-channels started"
  • 10:35:17 - Vueroid S1-4K announces "GPS is connected"
  • 10:35:18 - A329S announces "Video Protected"
  • 10:35:21 - Double beeps from A329S are heard
  • 10:35:22 - Thinkware U3000 Pro parking mode results announcement starts
  • 10:35:24 - A329S "Photo Sound"
  • 10:35:32 - I placed the transmission into "Drive"
  • 10:35:35 - Emergency brake disengaged
  • 10:35:37 - Vehicle begins moving
  • 10:35:39 - Thinkware U3000 Pro announcement finishes
  • 10:36:14 - This LBR video file set finishes and is placed in the "RO" directory

 

[jsmith]

The vehicle I have/had the A329S 3CH installed into is my Chevy Caprice. I believe I explained earlier in this thread that this vehicle has a digital relay with a 5-second delay timer in the ACC power circuit that feeds power to the hardwire kits in this vehicle. The only available ACC power in this vehicle that's not involved with a critical module [without going through the firewall and to the front of the engine bay fuse box], is an ACC circuit that is only has power in "ACC" and "RUN" positions of the ignition switch. When I move the ignition switch to the "START" position, the ACC power turns off.

That On/Off toggling of ACC power during a start of the engine was determined to be one of the root triggering causes for some of the older VIOFO firmware versions to only halfway exit parking mode [low bitrate files with normal mode filename suffixes and parking mode sensitivity still in place stored in the "Parking" directory]. The more recent firmware versions [A329S and A229 series] should have a logic patch to help mitigate this behavior for this type of ACC power behavior.

In an effort to stabilize my dash camera installations in this car, I added the digital relay in the ACC power circuit which can be configured with a delay timer to govern when the "LOAD" side of the relay receives power. I programed the digital relay timer so it must see constant power [ACC power in this case] on the supply side of the relay for 5-seconds before the "LOAD" side of the relay is provided power. The ignition switch is not placed or left in the "ACC" or "RUN" position for 5-seconds before I start my vehicle. This results in the HK4 hardwire kit only getting ACC power after the ignition switch has been returned to the "RUN" position after the engine has been started.

In my case, the engine has been running for at least 5-seconds before the ACC power is restored to the HK4. That's when the A329S begins its transition from low bitrate parking mode to normal recording mode. The normal mode MP4 files have the announcement stating "Recording, 3-channels started". At the 5-second mark, this is when the A329S announces "video protected".

In my recent example, there are a few things going on:

• 10:33:08 - LBR files recording
  • 10:33:32 - Trunk closure initiates an impact event "Photo Sound"
  • 10:33:39 - You can hear the "beep" sound of the BlackVue Elite 9 powering up to handle the impact event as well
  • 10:34:08 - This LBR video file set finishes and is placed in the "RO" directory
• 10:34:08 - LBR files recording
  • 10:34:13 - The Elite 9 announces that it connected to the BlackVue Cloud service - "Cloud Connected"
  • 10:34:35 - I open the driver side front door
  • 10:34:44 - I sit down in the front seat and about 1 second later the A329S "Photo Sound" is heard
  • 10:34:46 - Front door is closed - impact beep sound from Elite 9/10 cameras
  • 10:34:52 - BlackVue cloud push notification alert tone from my phone
  • 10:34:56 - Key inserted into ignition switch
  • 10:34:57 - Ignition switch moved to RUN position - windshield wipers make one pass on the windshield
  • 10:34:59 - Ignition switched moved to the START position
  • 10:35:03 - Engine starts - Ignition switch returns to RUN position
  • 10:35:08 - This LBR video file set finishes and is placed in the "RO" directory
• 10:35:14 - Normal Mode Recording Starts
  • 10:35:14 - Announcement from another dash camera is heard
  • 10:35:16 - A329S announces "Recording, 3-channels started"
  • 10:35:17 - Vueroid S1-4K announces "GPS is connected"
  • 10:35:18 - A329S announces "Video Protected"
  • 10:35:21 - Double beeps from A329S are heard
  • 10:35:22 - Thinkware U3000 Pro parking mode results announcement starts
  • 10:35:24 - A329S "Photo Sound"
  • 10:35:32 - I placed the transmission into "Drive"
  • 10:35:35 - Emergency brake disengaged
  • 10:35:37 - Vehicle begins moving
  • 10:35:39 - Thinkware U3000 Pro announcement finishes
  • 10:36:14 - This LBR video file set finishes and is placed in the "RO" directory

So at least you and I have confirmed sensitivity issue with the A329S/T series transitioning from Parking ---> Normal and creating a Event Trigger Lock (RO File).

Flicker Appears Confirmed, too. I'm getting Second Rear Camera from Viofo just to "Eliminate" any chances of some faulty production units.

@rcg530 Appreciate your help and everyone elses' who have assisted with verifying my findings.

 

[TonyM]

@jsmith I have not had time to check the rear camera at night, but I did find an old test video showing flicker / exposure hunting on the front camera. Over the years I've seen a few dashcams and action cameras hunt around to find the right exposure at night. I don't think this is a fault, it's just something that can happen in very low light.