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'm still unclear as to what symptoms other than some beeping, that you are seeing which lead you to believe that the G-sensor "High Sensitivity" menu that reset during a parking period did not reset back to the original user setting after Normal recording resumed.
But anyhow, ran several tests with WDR ON and OFF, rebooting between tests to determine if WDR affects Parking Mode.
- First confirmed the user original G-sensor setting set to LOW.
- Then switched WDR to either On or OFF and rebooted the camera by pulling power several seconds then reconnecting.
- Then induced a simulated parking period where both the Standby and Time-lapse sub-modes engaged twice during each test.
- Then picked up the camera to initiate a G-sensor restart of Normal recording.
- Then at 65 seconds on the camera elapsed time counter, stopped recording by pressing the REC button and pressed the Menu button to enter the menu.
- Proceeded to the G-sensor menu setting and checked the setting and noted the result.
- Reset the G-sensor menu setting to "Low Sensitivity" if needed in preparation for the next test.
- Switched the WDR setting.
- Rebooted the camera by pulling power several seconds, then re-connecting.
- Repeated steps 3 through 9 for the opposite WDR setting until finished testing.
In all cases, Parking Mode engaged Standby/Time-lapse sub-modes properly and a check of the G-sensor menu setting 65 seconds after the resumption of Normal recording indicated that the G-sensor setting had switched back from "High Sensitivity" to the my original setting. IMO, switching WDR on and off alone does not cause any Parking Mode problems.
This doesn't say that problems experienced in the previous 2 days by me at times being unable to force Parking Mode into the Standby/Time-lapse sub-modes or the problems @TCK81 is seeing should be dismissed, but its difficult for Viofo to fix a problem that you can not reliably reproduce.
{Edit: Post test FINDING: The cover-the-lens technique does not work for my A119S. Covering the lens or pointing the camera at a bland featureless object that fills the FOV will perpetuate Normal recording indefinitely. Place the still A119S where it views a static scene, even very dimly lit, that has some features and contrast, and it will consistently slip into the Standby mode right on time, in about 90 seconds. Further testing indicates the G-sensor resets to the User's original setting 60 seconds after the resumption of Normal recording.}
I had changed some of my settings so I will list all here, Red indicates values not default:
Resolution: 1920x1080P 60fps
Loop Recording: 2 Minutes
Video Format: TS
Exposure: +0.0
WDR: ON or OFF - subject of the test. Normally ON.
Sharpness: Normal
Parking Mode: 5fps
Time-Lapse Recording: OFF
Motion Detection: OFF
GPS ON: ON but no mount attached this test, used one some yesterday.
Speed Unit: MPH
G-sensor: "Low Sensitivity" for this test only. Normally default "Middle Sensitivity".
LDWS: OFF
FCWS: OFF
Date Stamp: ON
GPS Info Stamp: All Info
Camera Model Stamp: ON
Record Audio: ON
Screensaver: OFF for test. 15 seconds normally.
Boot Delay: 5 Seconds
LED: ON
Date/Time: Set by GPS, maintained by RTC.
Time Zone: GMT-7 (PDT)
Language: English
Beep Sound: All ON
Frequency: 60 Hz
Image Rotation: OFF
Format: (a command)
Format Warning: 30 Days
Default Setting: (a command)
Car Number: 1080P60 D1 (resolution and lens pointing elevation angle in clicks)
Custom Text Stamp: NCPL B4.02 (no cpl and firmware version)
Firmware Version: A119S_180903_B4.02
I pretty much agree with the detection levels you have in place now. But it seems possible, and seems like you already do it, to detect multiple levels of G-sensor activity by having the code go check the G-sensor level(s) for each particular comparison need. Seems that this can be and is done for different purposes now such as normal G-sensor event recordings level, a parked car detection level, and a parked car bumped event recording detection level). Seems like this could be done without changing the User's G-sensor menu setting whose primary purpose is for crash detection event recordings while driving. Perhaps not easy to implement and even then you may still get problem reports for users not happy with the various individual detection levels, but then they can't blame it on the G-sensor menu setting being changed by the firmware.
Excellent idea if changing menu setting method is maintained. I already use the Car Number and Customized text stamp to tell myself settings and other info in use during the recording.
Last edited:
… the cover-the-lens technique does not work for my A119S as it did for the A119, probably because of the different sensor. At least for my A119S, covering the lens or pointing the camera at a bland featureless object that fills the FOV will perpetuate Normal recording indefinitely. Place the still A119S where it views a static scene, even very dimly lit, that has some features and contrast, and it will consistently slip into the Standby mode right on time, in about 90 seconds.
