VIOFO A139 Pro - Firmware

Have you tried to forget the wifi in your home and then connect to the camera wifi? If you have remembered the home wifi, it will interfere with the connection between the camera and your phone. Actually, 5GHz is less likely to experience interference from other devices than 2.4GHz due to the smaller using range.
Tried that, even turned off my router to make sure but it makes no difference. It struggles hard to connect in this area and even when it manages to connect, I can hardly do anything due to long loading and timeouts.
I'm able to connect without problems and everything works great once I leave this area, so something is clearly interfering.
 
Hello`

I just updated my A139 Pro to V1.1 0629 from the Viofo Support Website and it looks like something went wrong. The Dashcam is not recording anymore. It says "recording two channel started" but is continuously bipping ....
I already tried to format the SD-Card and reset all the settings of the dashcam but it didn't helped.

Does anyone have a clue on what I can do???
 
Hello`

I just updated my A139 Pro to V1.1 0629 from the Viofo Support Website and it looks like something went wrong. The Dashcam is not recording anymore. It says "recording two channel started" but is continuously bipping ....
I already tried to format the SD-Card and reset all the settings of the dashcam but it didn't helped.

Does anyone have a clue on what I can do???

Per https://viofo.com/content/75-A139-Pro-Support/#FAQs first check your SD card and as a test try the original charger cable. If you have another SD card try that one and see if it still beeps continuously. Also test without the back camera connected.

Why is my camera beeping constantly?
Constant beeping indicates that the camera is not in the recording, most of such issues are related to the microSD card and connection.
Please use the original car charger cable and format the card to FAT32.
If the issue persists, please unplug the back cameras and try one card we recommend.
 
The firmware is not very new and has been in use for some time ... you need to look for the problem in yourself and possibly do a factory reset.

What is the exact type of your SD card ?
 
Thanks for the comments and sorry for the late response. I used a 256gb card for the update and it seems that the Dashcam didn't liked it. Reformating the card on my computer worked and the dashcam is now recording again.
 
Hello.
Got a VIOFO A139 PRO 2CH directly from China 20230802( or for Americans 08/02/23:)) and it also has firmware: VIOFO A139P_V1.1_0629.
So there doesn't seem to be any newer than the firmware discussed in the thread.
Sincerely
Ordered A139 Pro 1CH (Replacing A139 non-pro, and keeping existing rear camera) from Viofo's website on 2023-03-03.

Received camera with Firmware VIOFO_A139P_V1.1_1108. Doesn't appear to be on the website. Not sure what may have changed.
 
Thanks for the comments and sorry for the late response. I used a 256gb card for the update and it seems that the Dashcam didn't liked it. Reformating the card on my computer worked and the dashcam is now recording again.
Yes, specifically for firmware updates you have to use a small SD card ... about 32 Gb. Unfortunately, this is not mentioned in the manual ... Viofo mentioned it as a recommendation on the website
 
Yes, specifically for firmware updates you have to use a small SD card ... about 32 Gb. Unfortunately, this is not mentioned in the manual ... Viofo mentioned it as a recommendation on the website
you can do it with bigger sd cards just need to format for fat 32. On a Mac computer no issue on bigger sd cards. From my understand there is a challenge on PC
 
I see a new A139 Pro Firmware posted today, 7/11/24, V1.2_240710. I've been having some boot up start failing to recording issues, hardwired, so I just flashed this, reset all the settings, and going to see what happens.
 
I see a new A139 Pro Firmware posted today, 7/11/24, V1.2_240710. I've been having some boot up start failing to recording issues, hardwired, so I just flashed this, reset all the settings, and going to see what happens.

Nice, looks like they've also added BTR200 support for both the A139Pro and A139 (y)
 
Viofo!!
Why did you leave a pause in the work of the HDR??
They wrote to you that the dex_ fixed the firmware and there is no more pause, they even offered you this firmware!!
 
One thing I noticed about this new 1.2_240710 firmware is now my camera is lock protecting videos while driving as I hit bumps, dips, holes, etc. The detection is set to Medium, like it was on the earlier firmware. Guess I have to set it to Low sensitivity now.
 
You can turn this off in the menu!!
Right. IIRC my G-sensor was set to Medium before, now I'll try Low. I'm not sure if turning it completely off is a good thing or not.
 
Well, here’s a comparison, the new 139PRO firmware is good!!

A139 Pro does look a bit sharper than the 229. Plates are a little more legible during movement and at distance. I've never played with those EV settings. Assuming they should be the same for every camera and mine would be best to set to -1 as well?
 
Everything is in your hands, select the exposure individually, depending on the glass (tinting or heating...), and use the bluetooth remote control and you will see everything!!
 
Firmware FWA139P_ V1.2_240710 upgraded by master Dex_
Bow and Respect to him for his work!!
The HDR function is now controlled via a new (the old model also works) Bluetooth BTR200 remote control from VIOFO

 

Attachments

  • zxc.jpg
    zxc.jpg
    34.2 KB · Views: 6
I noticed now with the V1.2_240710 firmware, powering off the dashcam manually with the power button is a lot more easier with an audible confirmation beep. Prior to the new build, I would have to hold the power button for an arbitrary amount of time and then release. With the new firmware, if I hold the power button, after a few seconds an audible confirmation beep will emit and then turn off.
 
One thing I noticed about this new 1.2_240710 firmware is now my camera is lock protecting videos while driving as I hit bumps, dips, holes, etc. The detection is set to Medium, like it was on the earlier firmware. Guess I have to set it to Low sensitivity now.
Greater sensitivity is not a disadvantage, it is essential to lock even minor collisions. It's better than not locking an event. The fact that there will also be "false indications" in locked records is not a glitch that bothers you. You format the card regularly anyway.
 
Back
Top