Quick answer — what usually goes wrong

You come back to your parked car, find a dent, and pull the SD card expecting to see what happened. Instead, there is nothing—or only a clip that starts after the hit. That is frustrating, but it usually isn’t a sign that the camera is broken. More often, it’s a wiring or parking-mode limitation that means the camera never got the chance to save the moment. If you don’t fix that, the next bump or hit-and-run may go unrecorded too, and you’ll be left with no evidence again.

If your camera didn’t capture an incident, it is likely due to one of these specific technical gaps:

  • Wiring faults: The camera might still think the car is running. This happens if your ACC wire (the wire that tells the camera the ignition is on) is connected to a constant power source instead of a switched one.
  • Detection settings: Most cameras require an object to stay in view for a certain amount of time before they start recording. If someone bumps your car and drives off quickly, the “dwell-time” threshold might not be met.
  • Lack of buffering: If your camera doesn’t have “buffered recording,” it only starts writing to the SD card after it feels a hit. This means you lose the seconds of video leading up to the actual impact.

How parking mode actually works (and why that matters)

Understanding how your camera “thinks” can help you prevent future misses. There are two main ways cameras handle parking: buffered and non-buffered.

Buffered parking mode is the gold standard. The camera continuously records a short loop of video in its memory, always overwriting the old seconds with new ones. When a trigger happens—like a bump or movement—it saves that existing loop before it gets overwritten, and writes it to the SD card. On supported Viofo models, this can preserve about 15 seconds before the trigger and 30 seconds after, giving a 45-second total clip of the incident.

Non-buffered mode is different. The camera only starts writing to the SD card the moment the G-sensor (the sensor that detects physical impact) or a motion trigger fires. Because it wasn’t saving a “pre-buffer” in its memory, you miss the crucial moments of the person approaching your car or the seconds just before the collision.

Some cameras also use “deep-sleep” parking mode. To save your car’s battery, the camera turns off its main processor and sensor entirely. Only the tiny accelerometer stays awake. While this is great for your car’s battery, it creates a “wake-up latency.” The camera has to “wake up” and initialize the SD card, which can take a few seconds.

Why the camera didn’t “see” the event

Even if your camera is powered on, it might simply ignore the event. This is usually a settings issue rather than a broken camera.

Motion detection is not perfect. Some users find that they can walk past their camera without triggering it, even on high sensitivity, yet touching the camera itself triggers a recording. This happens because of “dwell-time.” For example, 70mai cameras have specific thresholds: High sensitivity might require someone to stay in view for 8 seconds, while Low sensitivity might require 17 seconds. Some default settings even require more than 20 seconds of continuous presence before the camera decides it is worth recording.

Other factors include:

  • Sensitivity levels: Thinkware recommends using Low sensitivity to avoid the camera constantly recording “fake” motion like falling leaves or raindrops. However, lowering the sensitivity also makes it harder for the camera to trigger on actual movement.
  • Detection regions: You can often tell a camera to ignore specific areas, like a swaying tree in the background. If you set these regions too strictly, you might accidentally tell the camera to ignore the very spot where a person is walking.
  • Sensor limitations: Some users have reported that the G-sensor fails to trigger even when the car is physically shaken, meaning impact-based protection isn’t always a guarantee.

Why the camera wasn’t in parking mode at all

If you check your footage and find nothing at all, the camera might never have entered parking mode.

A dash cam needs to know when you have turned off the engine. It does this through the ACC (accessory) wire. This wire must be connected to a fuse that loses power when the ignition is off. If you accidentally connect the ACC wire to a constant power source, the camera will think the car is always running and stay in “driving mode.”

Many people try to use their cigarette-lighter socket for power. This is a common mistake because many cars cut power to those sockets the moment the engine stops. If your camera is plugged into a socket that turns off with the ignition, your camera dies the moment you park, leaving it with no power to monitor your vehicle.

Why the clip starts after the hit

Have you ever found a clip that starts only after the impact has already happened? This is the “hit-and-run trap.”

This happens because of wake-up latency. In deep-sleep modes, the camera is essentially “napping.” When a collision occurs, the accelerometer feels the shock and tries to wake the camera up. This process—powering the image sensor and getting the SD card ready to write—can take between 3 and 5 seconds. If a vehicle backs into you and speeds away immediately, that 5-second delay means the camera was still “waking up” while the culprit was driving off.

Even in modes that aren’t in deep sleep, a lack of buffering causes this. Without a pre-trigger cache, the recording begins at the exact moment of the trigger, leaving you with no footage of the moments leading up to the hit.

Common mistakes that look like camera faults

Before you assume your camera is broken, check if you have fallen into one of these common traps:

  • Misunderstanding sensitivity: Thinkware notes that its dash cams are very sensitive and will capture small movements like leaves blowing or raindrops, which is why the manufacturer recommends using LOW sensitivity for motion detection. Lower sensitivity means fewer false alarms, but it can also require a person to stay in motion longer before a trigger—70mai’s settings documentation, for example, cites about 8 seconds of continuous presence at High, about 17 seconds at Low, and more than 20 seconds at the default. So a quick bump-and-run can easily stay below the threshold and produce no clip.

Next-step checks (5-minute diagnostic)

If you want to make sure your camera is actually protecting you, run through this quick checklist:

  1. Check the wiring first if parking mode never starts. If the hardwire kit’s ACC wire is connected to a constant-power fuse instead of a switched one, the camera will keep thinking the ignition is on. Viofo’s guidance is direct: the ACC cable must be connected to a switched power source that cuts power when the ignition is off. Also, don’t expect parking mode to work from a cigarette-lighter socket—many cars cut power there when the engine is off, which is why hardwiring is required.
  2. Run a realistic motion test. Walk into the camera’s view and stay at least as long as your sensitivity setting requires—70mai documents about 8 seconds at High sensitivity, around 17 seconds at Low, and more than 20 seconds for the default. The “auto-event detection” mode can be temperamental: one user reported that walking past the rear window recorded nothing even at High sensitivity, while touching the camera did trips.
  3. Look for “buffered” in the settings. If your camera doesn’t have buffered parking mode, it only starts recording after the G-sensor or motion trigger fires, so the clip begins after the events starts. In deep-sleep parking mode, the camera’s sensor and processor are powered down and only the accelerometer stays awake, so there is no pre-buffer at all—and wake-up latency exists long enough to delay the start of the clip.
  4. Adjust detection regions if your camera supports them. Some models, such as the BlackVue DR770X series, let you tune motion sensitivity and choose detection regions to reduce unwanted triggers from trees or far-away moving objects. Set them carefully so they don’t miss the area you are trying to protect.

FAQ

Why is there no clip at all after a parking-lot dent? The camera most likely never entered parking mode. That happens when the hardwire kit’s ACC wire sits on a constant-power fuse instead of a switched one, so the camera still thinks the ignition is on.

Can you run parking mode from the cigarette-lighter socket? No. Many cars cut power to that socket the moment the engine stops, so the camera loses power exactly when you park. Hardwiring is required.

Why does the clip start after the impact? In deep-sleep parking mode only the accelerometer stays awake, so the camera has to power the image sensor and ready the SD card first. That wake-up can take three to five seconds, which is long enough for a hit-and-run driver to leave.

Why did someone walk past the car without triggering a recording? Motion detection uses a dwell time, meaning a person must stay in view for a set number of seconds. On 70mai cameras that is about 8 seconds at High sensitivity, about 17 seconds at Low, and more than 20 seconds on the default, so a quick bump-and-run stays under the threshold.