A129 Pro firmware

Aly_Oops said:
Verified again. Set time correctly, display correct time in display and file recorded. The next day, after parking overnight, time was off by 12 hours. Off 12 hours in the display and file. Is this an issue that VIOFO is aware. I will test again, this time, set the time correctly and then power off the unit to see if it changes on boot up.

It seem like it doesn't recognize setting time in the morning. I tried in afternoon, using 16 hour for 4pm. Which I did, then it moved the date ahead, from 28th to 29. Went back in and changed the date back to correct date and time stayed the same. I see if it hold tomorrow.
Click to expand...
How are you setting the time - manually or with GPS? Have you checked that your GMT +/- setting is correct?
 
@viofo I've test v2.1 beta and here are what I found.
  1. The GPS information overlaid in the video files is now correct.
  2. When using Viofo app (android), viewing live feed from dashcam, only the latitude can be seen on the display.1596006479237.png
  3. On the first day I tested, somehow the dashcam was able to stay on the whole day (parking mode). It was a sunny day. After that, the dashcam as usual only able to stay on (parking mode) to around 11:00 am. So, the issue may not be due to temperature?
 
TonyM said:
How are you setting the time - manually or with GPS? Have you checked that your GMT +/- setting is correct?
Click to expand...
Oops, post this to the wrong person. Disregard.

Okay, I might have found a solution. First of all, in the beginning, when I installed v2.0, I used the iPhone App to set my settings, initially sync with my iPhone. However, notice lots of odds things happening. The VIOFO app messes up the settings badly. I stop using it. Did a reset and manually entered my preferred settings. Usually in the morning 8:00 AM, which is what I entered. My GMT is always 6+. However next day, it off by 12 hours.

As mention in previous post, I waited in afternoon, using the 24 hour format, set it to 16 hours, the minutes and seconds are okay. Verified the date was correct. Exit out, and notice the time was correct, but the date was off by 1 day. So, I went into the date setting and changed the date to the correct day.

Next morning, I check and my dates changes held. Seems to overcome the problem, as long as I don't set the time in the morning. Must be an error in the coding?
As long as it stays, all okay here.

Now the next thing, I need to verify is parking mode. I notice when I enter the park vehicle, I get my beeps (which is what I want, telling me it recording and active). However, it doesn't happen all the time (made changes in testing). Not sure yet, but if the set the park timer to OFF, no beeps ( I want recording with no delay, which I assume it meant), if I set it to 90 secs, I get my beeps, indicating it recording. Is this normal and intended? If so, that can throw people off with parking failure.
 
Last edited:
I have two 4K cams - and running one from V2.0 and the other on V2.1

In the video, you can see the footage from both with V2.0 which is positioned in the centre of the car and the top of the clip, and V2.1 is on the lower part of the clip located left of the rear view mirror (and the video quality is affected from the windscreen a bit - always has been for clarity from it's placement compared to the one bang in the middle of the windscreen).

The images show grabs from both - but I don't use HDR or WDR, or parking mode or motion detection. I get no bleeps, and no errors from either firmware version - and the cams run purely when I am driving.

So for me at the moment, still no issues. The text on both cams is correct as well - nothing overlapping.

2.0
v2right_1-XL.png

v2right_2-XL.png


2.1
v2.1left1-XL.png

v2.1left2-XL.png


Video is at 4K (make sure you check your settings for viewing)

 
Last edited:
viofo said:
Yes, I have read your comments before, we plan to use FHD + FHD before, but worried many users may complain about the resolution.
Maybe it is better to add parking recording resolution option, offer 2K + FHD, and FHD + FHD for choices.
Click to expand...


Okay, I might have found a solution. First of all, in the beginning, when I installed v2.0, I used the iPhone App to set my settings, initially sync with my iPhone. However, notice lots of odds things happening. The VIOFO app messes up the settings badly. I stop using it. Did a reset and manually entered my preferred settings. Usually in the morning 8:00 AM, which is what I entered. My GMT is always 6+. However next day, it off by 12 hours.

As mention in previous post, I waited in afternoon, using the 24 hour format, set it to 16 hours, the minutes and seconds are okay. Verified the date was correct. Exit out, and notice the time was correct, but the date was off by 1 day. So, I went into the date setting and changed the date to the correct day.

Next morning, I check and my dates changes held. Seems to overcome the problem, as long as I don't set the time in the morning. Must be an error in the coding?
As long as it stays, all okay here.

Now the next thing, I need to verify is parking mode. I notice when I enter the park vehicle, I get my beeps (which is what I want, telling me it recording and active). However, it doesn't happen all the time (made changes in testing). Not sure yet, but if the set the park timer to OFF, no beeps ( I want recording with no delay, which I assume it meant), if I set it to 90 secs, I get my beeps, indicating it recording. Is this normal and intended? If so, that can throw people off with parking failure.
 
Paul Iddon said:
.............
Click to expand...
Could be just by lens focus but the top one looks sharper but produces more smearing to licence plates in edges of the image. Which one is which? I thought v2.1 shouldn't change IQ in normal mode.
 
2.1 is the lower one. The left side of the windscreen has always had this effect.
 
@Aly_Oops Please note that if you enable GPS, the unit will always update the clock from the GPS data. Thus you only need to set the correct time zone.

Sent from my SM-N975F using Tapatalk
 
programatix said:
@Aly_Oops Please note that if you enable GPS, the unit will always update the clock from the GPS data. Thus you only need to set the correct time zone.

Sent from my SM-N975F using Tapatalk
Click to expand...
Yup, that what I did. Still not right
 
TonyM said:
My understanding is that the time zone in Alberta is UTC-6. If you are setting your A129 to +6, that would explain the 12 hour difference.
Click to expand...
Yes, i meant -6.... typo
Too many other issue also show up. So went back to 1.3, my time and date was correct without having to make corrections. Long as this work 1.3 reliable, I stay, only move up if a feature is needed, which I don't see at all in 2.0.
 
Last edited:
Paul Iddon said:
I have two 4K cams - and running one from V2.0 and the other on V2.1

In the video, you can see the footage from both with V2.0 which is positioned in the centre of the car and the top of the clip, and V2.1 is on the lower part of the clip located left of the rear view mirror (and the video quality is affected from the windscreen a bit - always has been for clarity from it's placement compared to the one bang in the middle of the windscreen).

The images show grabs from both - but I don't use HDR or WDR, or parking mode or motion detection. I get no bleeps, and no errors from either firmware version - and the cams run purely when I am driving.

So for me at the moment, still no issues. The text on both cams is correct as well - nothing overlapping.

2.0
v2right_1-XL.png

v2right_2-XL.png


2.1
v2.1left1-XL.png

v2.1left2-XL.png


Video is at 4K (make sure you check your settings for viewing)

Click to expand...


I will say running in town and city 95% will not trigger a video drop and causing any beep (viofo removed the video drop beep starting from v1.7T firmware). Try driving through in a sunny day inside the country side road that full with tree if you could like as shown in my previous demo, the complex trees branch and bushes give heavy calculation and easy to trigger the video drop issue.
 
remati said:
So the A129 Pro Duo is my first dashcam and I got it hardwired installed this past weekend. After a few drives I am glad to report there are no issues! My question is in the new beta firmware does Viofo let us change the recording format in parking mode? From what I have been reading in these forums is that 4k + 1080p recording seems to overheat in parking mode in the summer sun but a few people are saying 1080p + 1080p seems to be ok.
Click to expand...

viofo said:
Yes, I have read your comments before, we plan to use FHD + FHD before, but worried many users may complain about the resolution.
Maybe it is better to add parking recording resolution option, offer 2K + FHD, and FHD + FHD for choices.
Click to expand...

I am glad that we will be able to switch resolutions for parking mode for more testing. After these past few months of using the A129 Pro Duo the only issue I have is parking recording being stopped too early because of overheating. I was even debating opening up the unit and adding a better heatsink to the chip. FHD + FHD recording will probably work but the only issue I could possible see now are people not being able to read license plates of cars that hit them in this mode (maybe). I'm looking forward to testing more choices for parking mode in the next firmware revision!
 
V1.3 is working like before. No issues so far.

The only bug was the G force sensitivity, when unit get very warm, at low sensitivity it will think an accident happen when I hit a mild bump, but okay when unit is just warm. So for now, I leave it as it, on long trips I may shut it off if it proves to be annoying. I don't think it can be fixed with software updates without compromising the feature. May require hardware changes. Not sure, only VIOFO would know if they are willing to be candid and tell us the result of their investigation.

On V1.3 parking mode worked perfectly and 24 hours or more. Again, this requires your battery to be 100 Battery Health and 100 percent voltage charged. Those two things are not the same. One area that could cause an issue, if you are not aware, if you enable motion sensor, it auto shut off parking mode.

I found V2.0 was too irritating to use. Parameters would change by itself. For example, I was using 1440 Resolution for days and the next morning it switch to 4K on it own, changing other parameters, such as live viewing. It was set to Front Camera view, but when it changed resolution to 4K, it automatically set live view to front and rear camera view.

Another issue, if correct, if they disable the beep when their are write failures or frame lost, then that not kosher, if they were local business, they would be open to all sorts of liabilities. I need reliability.

If you want to play with it, go ahead, but keep a copy of 1.3 on your computer. VIOFO sites have removed it, some other countries site may still have it available.

For me, V2.0 is not fit to be GM, contains too many weird issues. VIOFO has to also update the iPhone app as it not compatible with 2.0, parameters don't match at all. I had to stop using it, as it did weird changes to the camera parameters.

However, it is not an issue with current version of iPhone app with v1.3.
 
V2.1 has been out for a week now, heard it fixed those weird issues, which me myself have yet to experience, will update it and try it out tomorrow.
 
xiongguoy said:
V2.1 has been out for a week now, heard it fixed those weird issues, which me myself have yet to experience, will update it and try it out tomorrow.
Click to expand...

Do we know where this version is hosted, is it another beta? Looking in the official firmware page now and I cannot see it listed.
 
JohnnyFiama said:
Ah, thanks!!

I believe this version still reports itself as v2.0 (albeit a different build date), and if so that is the version my camera already sports.
Click to expand...
It should show as 2.1. I remember that is what shown from the Android app. Also, when it goes to parking mode, it will show 1440p+FHD.

Sent from my SM-N975F using Tapatalk
 
You must log in or register to reply here.
Back
Top