V2.6 firmware issues

[Augustus]

Anyone actively using the Stop and Go feature in the latest firmware? I find it doesn't trigger reliably, and always triggers when I put the car into reverse for some reason.

The Fatigue Detection I don't use because it's easy inbuilt into my Kia Forte

 

[N.T.]

It’s just a gimmick feature. Of course it can’t tell if your car is reversing.

 

[HypnoToad]

I've got them both turned off on mine. Really I don't see the need for this feature, but I'm glad there are still updates being released for this camera.

 

[Robertm]

My stop and go works reliably, but you need to be stopped behind someone for several seconds. It seems to need to see a very steady picture which then has movement to activate. Sometimes if I pull up behind another vehicle and it pulls away in 3 or 4 seconds it doesn't activate, but always does after 10 or 15 seconds. Mine activates when I backup in my driveway too if I wait too long. I guess it thinks the shed is moving away. It's gimmicky, and 90% of the time not needed, but it has reminded me when I was looking out the side window that the car in front had left. My old Papago camera had a stop sign feature and would beep when it saw one. I liked that feature, but sometimes it would beep if the car in front had rally large tail lights.

 

[Augustus]

My stop and go works reliably, but you need to be stopped behind someone for several seconds. It seems to need to see a very steady picture which then has movement to activate. Sometimes if I pull up behind another vehicle and it pulls away in 3 or 4 seconds it doesn't activate, but always does after 10 or 15 seconds. Mine activates when I backup in my driveway too if I wait too long. I guess it thinks the shed is moving away. It's gimmicky, and 90% of the time not needed, but it has reminded me when I was looking out the side window that the car in front had left. My old Papago camera had a stop sign feature and would beep when it saw one. I liked that feature, but sometimes it would beep if the car in front had rally large tail lights.

You probably have the best explanation of the behaviour I was experiencing, guess it can be useful in some capacity but since it's sight-based not the best compared to something like ultrasonic sensors/dedicated cameras in new cars. I've kept mine off since.

 

[Kremmen]

These extra features and associated complication is where Nextbase went wrong.

Just stick to a basic dashcam.

Turns on with ignition, records continuously until ignition turned off, job done.

 

[Augustus]

Can't believe I missed this, but there was a firmware update for the A119 V3 a few months ago. The first in two years actually, that added Privacy Mode and some bug fixes.

Good to see a dashcam getting firmware updates five years later! It means that @viofo is on the ball, always.

Although my V3 is not in active use, I have fond memories as it was highly reliable and dependable in the Australian heat, and had stellar quality video footage. Kudos to @VIOFO-Support

 

[Augustus]

You definitely missed it. This firmware was mentioned here as soon as it appeared on the official site:

H

Post in thread 'VIOFO А119V3 FIRMWARE'

Dec 8, 2024

Can anyone comment on the recently updated and current "official" firmware:
V2.6_20241031 with Release Date: October 31, 2024?
especially as it relates to other 2.6 versions and/or version 1.03?

I have been using version V2.6_20220808 for the last 2 years, but just recently needed to make out a motorcycle's license plate, but it wasn't clear enough, so I was thinking of trying 1.03. But then I saw this much newer release of 2.6.

Thanks!

• Howie_S

• 

Yeah I know, you've missed a few yourself with Vantrue too 😉

 

[Augustus]

I haven't missed anything anywhere.
I only follow what interests me. 😉

Sure thing matey 😉

 

[Augustus]

As for Vantrue...
I already have a fresh firmware for E360 in my collection: E360_VT-EEA213.
So I haven't missed anything.

As do I for 70mai camera coming out this week. What's your point old man?

 

[Kremmen]

Head over the parapet - "still using 1.03 with sharp freezeframe" - ducks down again

 

[ogzogz]

a119 v3 software version V2.6_20241031
@viofo @VIOFO-Support

error!
When 60 fps resolution is selected, timed hdr is not activated.
When the resolution is set to 30 fps, hdr is activated if it is within the set time frame.

What should happen is, when the 60 fps resolution enters the hdr time frame, it should be reduced to 30 fps and hdr should be active. When it goes out of the time frame, it should record again with 60 fps hdr off.

 

[VIOFO-Support]

a119 v3 software version V2.6_20241031
@viofo @VIOFO-Support

error!
When 60 fps resolution is selected, timed hdr is not activated.
When the resolution is set to 30 fps, hdr is activated if it is within the set time frame.

What should happen is, when the 60 fps resolution enters the hdr time frame, it should be reduced to 30 fps and hdr should be active. When it goes out of the time frame, it should record again with 60 fps hdr off.

You can update this firmware to test (V2.6_20241225) : https://we.tl/t-nsKWJu7dxU

 

[ogzogz]

a119 v3 software version V2.6_20241031
@viofo @VIOFO-Support

error!
When 60 fps resolution is selected, timed hdr is not activated.
When the resolution is set to 30 fps, hdr is activated if it is within the set time frame.

What should happen is, when the 60 fps resolution enters the hdr time frame, it should be reduced to 30 fps and hdr should be active. When it goes out of the time frame, it should record again with 60 fps hdr off.

You can update this firmware to test (V2.6_20241225) : https://we.tl/t-nsKWJu7dxU

hi,
I tested the new version. the problem of not being able to activate auto hdr while 60fps is fixed, which i added above

You can update the version in the official update.