A129 Pro firmware

I've been testing plate number reading with 4K, 2K 30fps and 1080p (30fps and 60fps) and all of them are poor especially the vehicles on the other lanes (those vehicles at your sides). They are blurry. Incoming cars are bad too. Overtaking motorcycles are mostly unreadable. Here in my country, most of the motorcycles always hit & run and they do not have valid insurance.

I noted the lower the resolution, the brighter the recording will be. 4k 30fps and 2k 60fps has the same brightness though since it has to capture the same amount of bytes. So lowering the EV may reduce the blur. Haven't tried that.

In still photography, you need to hold the shutter to let more light in to make the image brighter but any shakiness will cause the image to blur. I'm seeing similar thing here. No mater what resolutions or fps you use, the video captured are blurry if the other vehicles are not at the same speed as you. Can I say that the A129 Pro shutter speed is low?

Anyway since all of resolutions are almost equally blurry, the 4K captured the best image due to higher resolution.

Sent from my SM-N975F using Tapatalk
Were you judging by looking at moving video, or still frames?
 
Were you judging by looking at moving video, or still frames?
I'm using VLC Player with interactive zoom at 2x and pause it. I also tried slow motion to 0.3.

Sent from my SM-N975F using Tapatalk
 
Can the parking mode be made configurable? In my case 2K + FHD still cause it to shutdown on its own. Only FHD + FHD is able to stay on during the day.

Sent from my SM-N975F using Tapatalk
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.
 
I'm using VLC Player with interactive zoom at 2x and pause it. I also tried slow motion to 0.3.

Sent from my SM-N975F using Tapatalk
It probably won't help with the issue, but try hit "e" on your keyboard - you'll be able to move frame by frame. :)

Btw: One of the users who'll complain about lowering resolution in parking mode here :ROFLMAO: Even QHD isn't the best option for UHD resolution sensor... (if it's not cropped out of the FoV)
 
Last edited:
A quick fix for the previous version like resolution not saved and stamp issue. Also parking mode resolution changed to 2K + FHD to better handle overheating in parking recording.
https://drive.google.com/file/d/1Dls4SnaSlYqq6gpXPuCuXKJ3e8fFOiLh/view?usp=sharing

Link doesn't work.... Should updates be posted on VIOFO site???

I notice that parameters don't keep and changes. Having issue with Date, keeps changing by about 12 hours. Doesn't always happen. I don't use the VIOFO app, as it messes up settings. Occasionally I use it to download some video clips. I have to go through the settings to be sure it okay and fix some that change. After a day or so, suddenly live view is showing back camera and Front. I never use that, it always set for Front camera only. I have to go and change again. Not sure, about this, but it seems parking mode is no longer reliable as it was with v1.3. Still verifying if it an issue.
 
I notice that parameters don't keep and changes. Having issue with Date, keeps changing by about 12 hours. Doesn't always happen. I don't use the VIOFO app, as it messes up settings. Occasionally I use it to download some video clips. I have to go through the settings to be sure it okay and fix some that change. After a day or so, suddenly live view is showing back camera and Front. I never use that, it always set for Front camera only. I have to go and change again. Not sure, about this, but it seems parking mode is no longer reliable as it was with v1.3. Still verifying if it an issue.

I'm facing the same thing with V2.0. The settings keep resetting. For example the vehicle number goes blank, the GPS stamp changed back from speed+coordinate to speed only and etc. Maybe it happened when I removed the sdcard.

Note: link works.

Sent from my SM-N975F using Tapatalk
 
Link doesn't work.... Should updates be posted on VIOFO site???
Welcome to "beta" firmware distribution... ;) (... and the link works for me.)

Btw: What do you mean by "parking mode no longer reliable"? No offense here, I'm curious because i see/saw some random stuff as well so i was wondering what about others. I have to check my second unit with non-beta v2.0 then, i wasn't paying much attention since update and some initial testing, to be honest.
How exactly Date changes? Couldn't it be caused by exposing the dashcam to GPS which changes user's time preset?

Unfortunately most of those settings that you and @programatix mentioned i left at the default. :unsure:
 
Last edited:
@ Viofo
Can you restore audible warnings again on 2.0 please ?
Tks
 
Blank on my Browser, probably got feature block (I do for unknown site). It does show up on iPhone. It beta, so I wait until it release on VIOFO site. Still thinking of going back to 1.3. If park mode randomly stops working. Haven't established a pattern yet, seems to act randomly, even though I avoid using VIOFO app as much as possible.

The date seems to change by 12 hours, When it is 8:00, time is right on the display, later on, days, I notice for example 8:00 becomes 20:00. This is reflected not only on the display but on the recording. I have to go and change it. As if the parameters not stored and reverts to something else. Still working on it. I use the format: DD/MM/YY. Which is not the default. Will switch to default if it keep happening, to see if that the issue.

I need to know if there are recording failures. Alerts is a must, at least make it an option for those who need that certainty. Main reason, why I go back to 1.3 if not implemented.
 
Have you tried to power cycle the camera after the date issue occurred without changing anything? I'm wondering whether it changes the time in RTC as well or it's just a temporary software issue. I've just checked mine unit and it keeps the right time and date(default time format though).

But i have to admit, reset RTC in this dashcam is pretty easy (i don't mean by removing backup battery :ROFLMAO: ). When i was exploring available commands i accidentally wiped the time using just two words in terminal (if i remember correctly).
 
Last edited:
Have you tried to power cycle the camera after the date issue occurred without changing anything? I'm wondering whether it changes the time in RTC as well or it's just a temporary software issue. I've just checked mine unit and it keeps the right time and date(default time format though).

Yes, even did factory reset. Still troubleshooting.... I notice that if you change a parameter, it changes another. But doesn't show that change that I didn't change, until you exit out. If these thing keep happening, I may throw the towel and go back to 1.3. where I didn't have issues like others. It was reliable for me.
 
I had updated the A129 Pro Duo firmware to 2.0 -version- V2.0.20200710 - did reset the camera with the hard reset button. When using timelapse recording it stays on normal recording 2 min 4k clips no timelapse. tryed 3 sec and 5 sec timelapse settings bud all the same.
 
Have you formatted your cards to FAT32? (e.g. via dashcam itself) Windows won't give you this option for 64GB and larger.
 
Have you formatted your cards to FAT32? (e.g. via dashcam itself) Windows won't give you this option for 64GB and larger.
Ahhh so if I try a smaller SD card, this might help get the camera reading other cards again?
 
A quick fix for the previous version like resolution not saved and stamp issue. Also parking mode resolution changed to 2K + FHD to better handle overheating in parking recording.
https://drive.google.com/file/d/1Dls4SnaSlYqq6gpXPuCuXKJ3e8fFOiLh/view?usp=sharing

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.

Check this afternoon, notice time was okay, however got distracted as my live view changed from Front to Front & Rear. Also it switch from my selected resolution to 4k, which I haven't use yet. Changed back to my resolution and to Front live view. On exit, the hour time was off by 12 hours and the day was 30th, not 29.

That it..... firmware 2.0 is unreliable. Switch back to 1.3,
 
Last edited:
Back
Top