OK, how about this for a feature request
@viofo? this one might be a stretch though.
What if instead of simply stopping recording, motion detect would switch between full speed and low-fps recording? then you would just rename "motion detect" to "parking mode".
when the camera sees motion, it would record at whatever the user set in the menu - 2k30, 1080p60, 720p30, whatever... but when it does NOT detect motion and after the timeout, it would stay at the same resolution and drop to 2-3fps. Then to let the user know the camera is switching modes, it can show a message on screen and/or beep to tell which mode is active. maybe the red REC led could start flashing slowly to indicate parking mode. It should continue recording audio (if the user has the mic turned on) to maybe hear details like another car bumping/scraping yours, or people talking - things like "oh crap, let's get out of here before he comes back!"
even if it wasn't just for parking mode, this would be better insurance so that there's SOME recording going on for rare cases like i described (boring straight highway where nothing much is really changing in the scene), instead of no recording at all.
it would also be useful if those low-FPS recordings could be stored in a separate folder on the SD card (ie: PARK, stored at the same level as the RO folder), or maybe if they had PARK added to the beginning of the filenames so they will sort easier. this might complicate loop recording though. one solution could be to only use 10% of the total SD card space for PARK files before it starts looping the PARK files (since low FPS = small files). For example, if you have a 32gb card, then it will keep 3.2gb of PARK files, and a 64gb card would keep 6.4gb of PARK files.
During parking mode, only the PARK files would be looped/overwritten, and during normal driving, the regular videos would be looped/overwritten. RO/lock files should still work the same way whether you're in parking mode or normal mode.
I guess the only hiccup is, any time it sees motion, it will go to normal recording mode at full FPS. As long as there isn't a long delay when switching between low-fps and full speed (30/60fps), this could work out great. of course in a busy parking lot where the camera sees a lot of motion, it may never go into parking mode at all. UNLESS...
I have a Blacksys CF-100 which has parking mode, but it does not have separate BATT and ACC wires - just one power and one ground - so it has no way to know if the ignition is turned on. it uses a combination of g-sensor and motion detection to switch between parking and normal mode. if it doesn't "feel" any movement AND doesn't see any motion for 5 minutes, it switches to parking mode and starts recording/looping in the PARK folder instead of the NORMAL folder. as soon as it feels motion or sees enough motion (ie: camera-car slowly moving in traffic or a drive-thru), it switches back to normal recording mode. it doesn't seem to be more sensitive to g-sensor during parking mode - it won't lock any files. when i get back in the car after the camera has gone to parking mode, i usually hear it say "Parking mode is ending" right as i get into the seat, meaning that it's switching to normal driving mode because it "felt" something w/ the g-sensor. it never locks the file due to me just opening or closing the door. and in fact i've never seen an EVENT (same as RO) file that came from parking mode. so if someone does hit my car while it's parked, i'll have to sit there and go through all the videos in the PARK folder till i find what i'm looking for. So hopefully i would have some idea of the time/date that it happened, so i'm not looking through tons of really boring footage. but i'll take that over having NO idea who hit my car! if there's a chance i can get proof and then make them pay for my damages, it will be worth it.
anyway... i don't know if the a119 has a good enough g-sensor to do that, but this might be worth looking into, for a complete and true parking mode solution.
