V2.0 Firmware for Public Testing

I did not have this issue before updating to V2.1, so for me the problem is the firmware, not the dashcam.

I have now changed back to FW V2.0_251027 and the only parking files in my RO folder are triggered when opening and closing the door/tailgate, which is perfect for me.
I coudnt find FW v2.0_251027

i managed to do FWA329S_V2.0_251230.zip

I hope this the one that is not buggy with the parking mode.

Can i assume with this firmware that the battery pack will not connect to the dashcam anymore thus only letting my phone be connected to it?

@viofo
@VIOFO-Support

Can you confirm this is the case?
 
My engineer is comming on Monday to install.
I wish i never updated to ver 2.1. I got happy because i wanted the battery percentage cut off but had no idea that renders the phone not able to connect at the same time.
I think the one i already had was good but i cant remember the number it came with when i purchased it.
 

260104 2.0 firmware Download 입니다.
 

260104 2.0 firmware Download 입니다.
The user needs firmware: FW v2.0_251027
 
The user needs firmware: FW v2.0_251027


이것이 원하는버젼인지 확인해보세요.
 
So the one I did is the wrong one?
I just want the one that's the most stable that doesn't have these weird glitches
 
So the one I did is the wrong one?
I just want the one that's the most stable that doesn't have these weird glitches

저는 2.1로 업데이트하고 번호판을 잘 못읽는거같아서 2.0으로 바꾸려고합니다.
 
With the 2.0 version, the camera does not support Cut-off BP100 Capacity feature, the battery will not be connected to the camera automatically.
 
With the 2.0 version, the camera does not support Cut-off BP100 Capacity feature, the battery will not be connected to the camera automatically.
Yes that's what I want right now.
Until the feature gets fixed where the battery and phone can both connect to the battery pack at the same time, I'll just stick to this.
Thanks
 
Can someone confirm with version 2.1 is the an option for Geofencing certain locations where it's low power impact detection only as opposite low bit rate parking recording?
 
What does this mean?

7. Add the 'Low Power Impact Recording' sub-option under Geofence settings.

Geofencing was already available
 
Can someone confirm with version 2.1 is the an option for Geofencing certain locations where it's low power impact detection only as opposite low bit rate parking recording?
What does this mean?

7. Add the 'Low Power Impact Recording' sub-option under Geofence settings.

Geofencing was already available
In FW version 2.0 the dashcam shuts down when the car is parked in a location covered by an active geofencing zone.

In FW version 2.1 you have an additional option of low power impact detection, which means you can have the dashcam shut down as before, or it can enter LPID when the car is parked in an active geofence zone. This setting applies to all 3 geofence locations - it cannot be toggled on/off independently for each location.
 
In FW version 2.0 the dashcam shuts down when the car is parked in a location covered by an active geofencing zone.

In FW version 2.1 you have an additional option of low power impact detection, which means you can have the dashcam shut down as before, or it can enter LPID when the car is parked in an active geofence zone. This setting applies to all 3 geofence locations - it cannot be toggled on/off independently for each location.
That's an amazing feature. I actually asked for that and they did it so quickly.

So let me get this straight.
You have regular Geofencing where the car won't go into parking mode at all


In the new version you can set low power impact detection in a location where it would have gone normal bit rate recording but because you chose Geofencing LPID it will just sit in this mode when you're at that location right?

Is this how I interpreted it correct?

I really want to update for these features but the Bluetooth battery issues is holding me back.
Also the instability in parking mode everyone is complaining about.
 
So let me get this straight.
You have regular Geofencing where the car won't go into parking mode at all


In the new version you can set low power impact detection in a location where it would have gone normal bit rate recording but because you chose Geofencing LPID it will just sit in this mode when you're at that location right?

Is this how I interpreted it correct?
There are two modes of operation in V2.0 that determine what happens when you switch off the ignition (ACC = OFF)
- Geofencing OFF > Dashcam enters the user's selected parking mode (low bitrate, hybrid, motion detection etc.)
- Geofencing ON > Dashcam shuts down

There are three modes of operation in V2.1 that determine what happens when you switch off the ignition (ACC = OFF)
- Geofencing OFF > Dashcam enters the user's selected parking mode (low bitrate, hybrid, motion detection etc.)
- Geofencing ON, LPID OFF > Dashcam shuts down
- Geofencing ON, LPID ON > Dashcam enters low power impact detection parking mode
 
There are two modes of operation in V2.0 that determine what happens when you switch off the ignition (ACC = OFF)
- Geofencing OFF > Dashcam enters the user's selected parking mode (low bitrate, hybrid, motion detection etc.)
- Geofencing ON > Dashcam shuts down

There are three modes of operation in V2.1 that determine what happens when you switch off the ignition (ACC = OFF)
- Geofencing OFF > Dashcam enters the user's selected parking mode (low bitrate, hybrid, motion detection etc.)
- Geofencing ON, LPID OFF > Dashcam shuts down
- Geofencing ON, LPID ON > Dashcam enters low power impact detection parking mode
Yh so I think that's what I said.
That's an amazing feature. When you only want low power impact detection in certain semi secure places then this is perfect.

But do you get three choices for full off no protection ahd three choices where it can use lower power?
 
But do you get three choices for full off no protection ahd three choices where it can use lower power?
No. There is a single option for OFF or LPID. It applies to all 3 locations.
 
Back
Top