
BlackVue DR970X-2CH Settings Guide
Our starting choices for recording, parking and connections
Before changing settings
We would set up the original DR970X-2CH around two priorities: keep the driving footage you need and make parking recording suit the way the car is powered. Start with continuous driving recording, then choose parking behaviour and alerts. Adjust one thing at a time so you can see what changed.
Check the camera label and installed firmware first. This guide covers the original DR970X-2CH. The DR970X Plus, Plus II, built-in LTE and Box models have their own instructions. A similar app screen does not make their settings interchangeable.
Back up important clips before saving time or image-quality changes. BlackVue’s original-model instructions warn that these changes can format the card, including locked events. Copy both views of an incident and confirm the copies play before proceeding.
The app’s layout can change. Use the DR970X settings instructions alongside the camera’s own menu, and ask us if an option does not match.
Recording quality and the footage you keep
The named DR970X specification lists 4K UHD at 30 FPS in front and 1080P FHD at 30 FPS behind. The original smartphone settings page contains a conflicting 1080P FHD/60 FPS front description. We would not use that sentence to select a 60 FPS mode or apply a different model’s instructions. Check the actual saved files and exact firmware if the displayed values differ.
For image quality, Highest is a sensible starting point when that option appears on your camera. Highest (Extreme) increases the front bitrate further and uses more storage. High and Normal can retain more history at lower bitrates. Compare saved day and night clips before making that trade; more data is not a guarantee of readable plates in every scene.
The original manual lists one-minute segments. These are file divisions, not an instruction to stop continuous recording every minute. Keep Normal recording enabled when you want the journey recorded between triggers; disabling it leaves event-only recording during normal mode.
On smaller screens, swipe the table sideways to read every column.
| Setting | Starting choice | What to check |
|---|---|---|
| Normal recording | On for continuous driving footage | A saved section between event triggers |
| Image quality | Highest, if offered | Detail, playback and the history your card retains |
| Audio recording | Your privacy preference | The microphone state in a saved clip |
| Date and time | Display on | Correct time zone and daylight-saving setting |
Check audio deliberately rather than leaving it on unnoticed. If you do not want conversations recorded, disable audio and verify a clip. The microphone choice is separate from voice announcements coming from the camera’s speaker.
GPS, orientation and video overlays
We recommend keeping the date and time visible and checking them against an actual recording. Select the right time zone and daylight-saving choice; if setting time manually, follow the model’s instructions for the time the camera will next be used. GPS reception alone does not make every time-zone choice correct.
GPS location recording and the speed overlay are separate controls. Turning location recording off does not necessarily turn off GPS time correction or speed-related functions. Choose location sharing for your privacy needs, then review the saved overlay and any Cloud location features separately.
Choose km/h, MPH or no displayed speed. If you add identifying text, keep it short and avoid personal details you would not want shared with a clip. The documented text field allows up to 20 supported characters. The master Video overlay switch can remove the date, speed and text overlays together.
Use front rotation if an upside-down installation requires a 180° correction. The rear orientation control can rotate or mirror its view. Play back both cameras afterward, including a scene with recognisable left and right sides, so a mirror setting does not go unnoticed.
Parking recording and battery protection
Enable parking recording if you have a suitable power installation and want footage while the car is off. Hardwiring can use the ACC signal for the transition; other supported arrangements use the camera’s stationary detection. Confirm the actual transition in your own installation rather than assuming an always-powered socket behaves like an ACC connection.
We would start with Motion & Impact detection in a quieter parking location. It saves activity detected in view and separate impact events. For a busy street, time lapse can be easier to review as an overview; the documented mode records fewer frames and keeps separate ordinary-speed impact events. Neither mode guarantees that every incident will be detected.
Keep rear-camera parking recording enabled when you want both views. The original instructions say that disabling this option stops the rear camera five minutes after parking mode begins; it resumes in normal mode. Check a saved parking clip from each camera before relying on rear coverage.
Leave battery protection enabled for an appropriate hardwired parking setup. Review both the timer and voltage cutoff for the vehicle, battery condition and driving pattern. They limit how long the camera draws power; they do not guarantee a vehicle will start. We would not lower a cutoff just to chase more recording hours without checking the battery and installation first.
If a parking session ends sooner than expected, check the power source, cutoff settings and saved footage before changing recording sensitivity. Motion activity affects the files you save, but turning detections down is not a substitute for a suitable parking-power supply.
Event triggers: useful alerts without unnecessary noise
We would keep driving-impact detection enabled, then review actual unwanted events before reducing sensitivity. Start with whether they happened on rough roads, when a door closed, or while loading the vehicle. Driving and parking impact settings serve different situations; changing one does not settle the other.
For motion detection while parked, review sensitivity and any detection regions offered by the matching firmware. Branches, passing traffic and rain can create activity in view. Reduce an unwanted region or adjust a setting gradually, then check what is saved. There is no universal sensitivity number that guarantees both zero false triggers and detection of every damaging impact.
On smaller screens, swipe the table sideways to read every column.
| Event | Our advice |
|---|---|
| Manual recording | Enable the control if you want to mark a clip deliberately; verify it while parked. |
| Driving impact | Check unwanted road-bump events before reducing sensitivity. |
| Parking impact | Review the event time and surroundings before changing detection. |
| Speed alert | Use only if you want an event at your selected threshold; check its km/h or MPH unit. |
| Hard acceleration and braking | Enable if these driving-behaviour records are useful to you, then assess the thresholds from real trips. |
| Hard cornering | Review the documented vehicle-motion threshold; it is not collision detection. |
Beep alerts and Live Event Upload are separate choices for supported event types. A local beep can help you notice a trigger; a Cloud upload requires a working Cloud connection. The driving-behaviour unit is also separate from whether speed is printed on the video.
Enable Protect event files if you want to retain marked incidents against ordinary loop replacement, and review the locked-file capacity and overwrite policy. Protection has limits. Back up important manual, driving-impact and parking-impact clips instead of leaving your only copy on the camera’s card.
The parking-impact history announcement is a return-to-car notice, not proof that a remote message arrived. The original instructions exclude impacts in the three minutes immediately before exiting parking mode from that history alert. Check the actual event list when something matters.
Touch control, indicators and system preferences
The original DR970X overview says that pressing the touch sensor starts a manual recording when that control is enabled in firmware settings. Keep it enabled if you want that function and check a saved manual clip while parked. Touch-assisted pairing is a separate setup task; do not assume a touch has marked a recording without checking the camera’s response.
We would leave the recording-status light visible during setup so it is easier to check the camera. Front security lights have separate normal and parking choices, and rear security is a separate setting. Their visibility is a preference; turning off a light does not by itself turn off recording.
The overview describes orange for normal recording, red for event or manual recording, and green for motion activity in parking mode. GPS has a blue indicator. Its connection indicator uses white for Wi-Fi, yellow for LTE and a yellow blink for Bluetooth. The settings page swaps the Wi-Fi and LTE explanatory labels, so use the overview and the actual connection state rather than following those swapped lines.
Choose voice guidance, volume and firmware language so you can understand important announcements. Set event beeps separately. If you keep Scheduled reboot enabled, review its time: the original instructions describe a daily restart in parking mode that is skipped when recording is active. A scheduled restart does not replace checking recordings or maintaining the card.
Before formatting, copy anything you need. The documented physical sequence uses two five-second holds of the format button, with a beep and release between them. Do not use formatting as a casual test while incident footage is still on the card.
Local Wi-Fi, pairing and optional Cloud access
For local access, use the camera’s Wi-Fi name and password and change credentials deliberately. Try 5GHz when the phone supports it and the nearby connection works reliably; use 2.4GHz if that works better with your phone or surroundings. Keep Seamless pairing enabled if you want the assisted setup, and follow the app’s matching instructions.
Pairing your phone and connecting the camera to the Cloud are separate steps. Hotspot settings tell the camera which internet-connected Wi-Fi network to use. The original non-LTE DR970X-2CH needs an appropriate internet route, such as a hotspot or supported external connectivity module; a built-in LTE variant is a different camera.
Before enabling Live Event Upload, confirm that the camera is online and that the account supports the feature. Choose which event types and front or rear sources you want uploaded. The current Cloud documentation says retention depends on the plan and expired videos are deleted, so keep a separate copy of important files.
We would not buy a modem or SIM from the camera-family name alone. Confirm the exact module, region, service and current account requirements first. An old app illustration or a successful local Wi-Fi connection does not establish remote-access service.
Check the result and get help with your setup
After saving, confirm that recording resumes and play files from both cameras. Check orientation, audio, date and time, plus a short parking session. That is the useful final check: seeing the menu change is not the same as seeing the footage you intended to keep.
For help, send us the full camera model, firmware version, vehicle details, power connection and a screenshot of the setting you want to change. Tell us what happened and which clips you have checked. Ask our team about your settings
The original range included one-channel, two-channel and built-in LTE versions. Check the exact model’s instructions and accessories when comparing them. Their settings are not interchangeable.
Questions about your DR970X settings
Why am I getting many impact events during ordinary driving?
Review a saved example and its time before changing anything. Driving-impact sensitivity is separate from parking-impact and motion detection. Adjust gradually and check another trip; no sensitivity value guarantees that every significant impact will be detected.
Why does motion-detection parking seem to record constantly?
Activity in view can produce frequent files. Check the selected mode, detection regions and sensitivity in the matching firmware. Time lapse serves a different purpose, and neither mode creates unlimited parking power.
Does touching the sensor start a manual recording?
The original DR970X overview documents that function when the touch sensor is enabled in firmware settings. Verify the response and a saved manual clip while parked. Use the exact camera’s instructions rather than another generation’s control behaviour.
Will locked clips or Cloud uploads keep an incident indefinitely?
No. Card protection has a capacity and overwrite policy, formatting can erase locked clips, and Cloud retention depends on the plan. Copy important front and rear files somewhere else and confirm they play.


