5Cowbells
Well-Known Member
- Joined
- Oct 9, 2016
- Messages
- 431
- Reaction score
- 369
- Location
- California
- Country
- United States
- Dash Cam
- FW A119 V4.01, FW A119S_180919_V4.0
I once stated or implied that the A119S Parking ModeTHREAD was immature, but what I meant was that the Parking Mode was better documented in the A119 Parking Mode threadsince the Parking Mode Beta testing was done on the A119. As far as I have observed, the Parking Mode works the same way on the current firmware of both the A119 (Version 3.3) and A119S (Version 2.1) and has not changed from the A119 V3.1B Beta version. Several tweaks have been suggested but none implemented to my knowledge.I've been reading around the web that the parking mode function on the VIFIO (A119 and A119S) was coming out recently and then still "immature" and improving.
{Edited: In Parking Mode, once the A119 goes to Standby (not recording) after a quite period (no motion or no G-sensor triggers sensed for 1.5 minutes), the camera waits for motion sensed in the FOV to enter Time-lapse recording.} A G-sensor trigger is needed to resume normal recording from Standby or Time-lapse recording, but the G-sensor sensitivity is very high at this point. The G-sensor trigger described above does not trigger an Event (emergency) recording which "locks" the file. I found previously that Event (emergency) recording will still happen and file(s) will be "locked" while Time-lapse or normal recording if a "hard bump" or crash occurs, but that such did not happen while in Standby Mode (not recording) for an instantaneous event. From Standby mode, the aftermath from an instantaneous "hard bump" would be recorded normally because the "hard bump" "wakes up" the camera, but the file may not be "locked".
It should be noted that at times in the Parking Mode, the A119 automatically switches the G-sensor Menu setting to "High Sensitivity", mostly during and a while after a Standby/Time-lapse/Normal recording cycle, so that Event recordings activate much easier during these periods. {Edit: The A119 will eventually switch the G-sensor setting back to the user's setting (I don't know what makes this happen) so that the G-sensor operates normally while driving.} If you notice frequent G-sensor activated Event (emergency) recordings while driving, check the G-sensor menu setting and reset if necessary.
The A119/A119S do not do pre-buffered video recording so that instantaneous triggering events (sensed motion or G-sensor activity) that have no aftermath will be missed if they occur when the camera is in Standby mode (not recording). In addition, recording gaps of 2-3 seconds occur when the camera is switching from Time-lapse to normal recording after a G-sensor trigger.
In Parking Mode, once screensaver kicks in, the screen stays off unless you press a button or an Event (emergency) recording is activated by a "hard bump" G-Sensor trigger. The button lights can be turned off using the "LED" menu setting. This would give complete stealth as long as no buttons are pressed and no Event (emergency) recording is activated. With LED menu setting OFF, you must activate the LCD screen with a short press of the power button to check the recording status, which is not convenient while driving. Even with LED OFF, the A119 still sounds the repeating double beep warning if not recording. The Parking Mode can be used continuously while driving or parked as long as it is powered. It's possible that the A119 may slip into the Standby and Time-lapse recording while driving if stopped with little motion about for a 1.5 minute or greater period, but it's a rare occurrence in my experience.
G-sensor and button press activated Event (emergency) recordings are "locked" by being saved to a separate "RO" file folder. In the latest firmware, the file being recorded at the time of the event (current file) is "locked". If the event happens within the first 15 seconds of a file, the previous file is also "locked". The duration of each locked file is, at maximum, the Loop Recording time. Any subsequent files you want locked, you will have to do that manually by button press. {Edit: The behavior above is described for an event happening while recording normally (not sure about Time-lapse - checking).} Older RO files can be overwritten by new RO files when the card is full, so it is advisable to save your RO files to another device occasionally if you want to ensure they survive.
Last edited: