A139 Pro FIRMWARE

I’m finding the firmware versions a bit confusing.

Is the firmware version based on date released?

Is v1.0_0206 newer than v1.0_1217 ?
The VIOFO firmware versions do include a month/day value. Some include a year/month/day value. In the past, I've provided feeback to VIOFO that only having the month/day in the firmware version will lead to confusion. In theory, they could update the v1.x each year to account for different calendar years as well.

For the A139 Pro, the first few pre-release firmware versions were v1.0_0928, v1.0_1012, v1.0_1014, etc. The v1.0_0206 firmware version is a 2023 firmware release because the A139 Pro did not exist in February 2022. Again, confusing .... :unsure:
 
Many thanks @rcg530.
That makes good sense, easy to understand once one has a grasp of the format.

I made my first hardwired journey with two cams today. I’ll post my initial feedback in the other thread.
 
V1.1_0321 is now available on the Viofo website (https://viofo.com/content/75-A139-Pro-Support/#Firmware). It looks like they took @rcg530 feedback and made it V1.1 for the new calendar year instead of V1.0.

Change Log:

1. Refine video effect in 2K 60fps resolution.

2. Add Czech, Slovak, and Thai voice notification

3. Add LED options.

4. Fix the record issue after rebooting when AUTO HDR is enabled.

5. Restrict changing resolution in parking mode.

6. Add stamps in AV out mode and parking mode.
 
Hello DoubleDawg.

5. Restrict changing resolution in parking mode.

So it doesn´t switch gears into second-hand 2K 1440P 30fps low bitrate but keeps on recording in glorious 4K 2160P 30fps max. bitrate?
 
Hello DoubleDawg.



So it doesn´t switch gears into second-hand 2K 1440P 30fps low bitrate but keeps on recording in glorious 4K 2160P 30fps max. bitrate?
Not sure what it means, as there wasn't a way to change the resolution in parking mode on the user end that I know of. I also wonder what "Add LED options" are.
 
Hello DoubleDawg.

DoubleDawg: [...] there wasn't a way to change the resolution in parking mode on the user end that I know of.

I scratched my head about that too. Maybe now there is. But: my cams work 110% like they want to run for some critical space-mission. And i don´twant to be the guinea pig rendering them to two potatoes because of being dazzled by new firmware-porn ... Oo

DoubleDawg: [...] I also wonder what "Add LED options" are.

Someone somewhere asked about something like `Isn´t there a way to shut down the (annoying?) LEDs? And someone else answered `Put a strip of electric-tape on them` ... :)

Maybe Mr. and Mrs. Viofo read about that and thought `No ugly tape on our Porsche´ and now there´s a blackout-option ...
 
Hello DoubleDawg.



I scratched my head about that too. Maybe now there is. But: my cams work 110% like they want to run for some critical space-mission. And i don´twant to be the guinea pig rendering them to two potatoes because of being dazzled by new firmware-porn ... Oo



Someone somewhere asked about something like `Isn´t there a way to shut down the (annoying?) LEDs? And someone else answered `Put a strip of electric-tape on them` ... :)

Maybe Mr. and Mrs. Viofo read about that and thought `No ugly tape on our Porsche´ and now there´s a blackout-option ...
Just switched the firmware and checked the app settings (along with redoing all my settings as they went back to default). I didn't see anything new and special in the settings to indicate what the restrict changing resolution in parking mode was about. The added LED options are "All on", "Rec only", and "All off"; there is also the ability to set these options separately for driving and parking mode.
 
Hello DoubleDawg.

DoubleDawg: I didn't see anything new and special in the settings to indicate what the restrict changing resolution in parking mode was about.

Maybe then it´s a `silent`/transparent-feature, means: The resolution (and very much many intensively hopefully > the bitrate) you´re recording in non-parking mode is kept in parking mode. The secret will only be revealed by actual recording and forensic aftermath. Thank you for your report!
 
Just switched the firmware and checked the app settings (along with redoing all my settings as they went back to default). I didn't see anything new and special in the settings to indicate what the restrict changing resolution in parking mode was about. The added LED options are "All on", "Rec only", and "All off"; there is also the ability to set these options separately for driving and parking mode.
Are you using an Android phone? I just updated, but don't see any LED options on the iPhone app.

One option I'm hoping to see in the future is to only disable the startup tone & leave everything else on, including the voice prompts.
The startup tone is shrill & unpleasant, like nails on a chalkboard to my ears. I think the startup tone really detracts from the perceived quality of the unit, as it makes it sound like a cheap Chinese toy (like the Ring Doorbell chime)
 
Are you using an Android phone? I just updated, but don't see any LED options on the iPhone app.

One option I'm hoping to see in the future is to only disable the startup tone & leave everything else on, including the voice prompts.
The startup tone is shrill & unpleasant, like nails on a chalkboard to my ears. I think the startup tone really detracts from the perceived quality of the unit, as it makes it sound like a cheap Chinese toy (like the Ring Doorbell chime)
Android. There might be an update for the app as well.

Unless it's different for the iPhone app as well, there is a Notification Sounds setting that has "All off", "Button beeps only", "Startup sound only", and "All on". The button beeps only may accomplish what you're looking for (unless there are other notification sounds outside of the startup sound that aren't considered button beeps, requiring "all on" in order to receive those). For voice notifications, there is a separate toggle slider for those.
 
Android. There might be an update for the app as well.

Unless it's different for the iPhone app as well, there is a Notification Sounds setting that has "All off", "Button beeps only", "Startup sound only", and "All on". The button beeps only may accomplish what you're looking for (unless there are other notification sounds outside of the startup sound that aren't considered button beeps, requiring "all on" in order to receive those). For voice notifications, there is a separate toggle slider for those.
No app update for iOS from what I can see. Guess I'll have to wait a bit; no big deal, I don't mind all of the LEDs being on.

I saw the separate voice toggle, but it doesn't appear to work properly with the notifications set to "Button Beeps Only". If the Voice toggle is supposed to do what you say, that'd be PERFECT!
Setting notifications to "Button Beeps Only", even w/ Voice toggled on, it does just that, only beeps with buttons: No voice, no 'not recording" beeping, no protected video sound, no startup / shutdown chime, no audible indications except for when I toggle something on/off with the buttons. The weird one is pressing the protect video button doesn't audibly alert, as that's a button; it just flashes all of the LEDs when pressed.
 
Last edited:
Today, one of the updates I downloaded on my Android 10 device from the Google Play store was the VIOFO app v3.2.10. When I connected to either of my A139 Pro 3-CH dash cameras with firmware v1.0_0206 (test firmware), the VIOFO app did not display the new LED related settings. After updating the A139 Pro dash cameras to firmware v1.1_0321, it does show the new LED settings. I was able to set the parking mode LED setting to only display the REC LED. When I tested it, it worked correctly.

1679640188402.png 1679640205589.png 1679640222522.png 1679640242314.png
 
Was hoping VIOFO would better balance the bitrates in 2 & 3CH mode in this Firmware release. Main camera bitrate is far too low and the rear & internal bitrate could be dropped to 11mbps from 15mbps.
 
I’ve got an iPhone, ended up loading Viofo’s app on my cheap android tablet to change parking mode LED’s to only REC LED.

Wonder if this reduces current consumption in any tangible / meaningful way. Indicator LEDs are typically designed to draw 5mA - 15mA continuous; pulse width modulation (which is nearly guaranteed on the A139) reduces average current down from these fixed maximum values set by hardware design.

Edit: Did the math, the power reduction would be mostly negligible. Around 100mW reduction at best with all LEDs set to off.

Edit#2: Apple App Store just released the update for iOS devices. Version 3.4. Verified it has the LED settings
 
Last edited:
Compared to what?
The limit is 60mbps shared across all cameras, just the front camera @ 8MP then thats great.

If you have a 3 channel system then the 2MP rear and internal cameras run at 15mbps but the front 8MP camera only gets 30mbps. That would make sense for a 2K front camera but a 4K camera at 4X the pixel count as the rear and side it should really a lot more then it currently does - it's unbalanced.

I'd like to see the Front camera in 1600p @30fps get 38mpbs, the rear and internal get 11mbps (1080p dashcams are typically this so should be fine for the rear and internal which are less important then the front).
 
@rcg530

Robert - which (stable) firmware do you use now on the A139 Pro please?

Paul.
 
@rcg530

Robert - which (stable) firmware do you use now on the A139 Pro please?

Paul.
I've installed v1.1_0321 in both A139 Pro dash cameras, but I don't have either unit in a vehicle to test on a daily basis.
 
Back
Top