Android Road Recorder: Use Tasker for Automated Dashcam
Transforming Your Android Device into a Car Video Recorder
Do you wish to maximize the functionality of your Android smartphone or tablet? Perhaps you'd like to utilize it as a convenient video recording solution for your journeys by car.
HTG details a method for achieving this using readily available, standard components.
Simple Setup with Common Components
This process allows you to repurpose an existing Android device, eliminating the need for dedicated and potentially costly dashcam hardware.
The setup is designed to be straightforward, requiring only items that are easily obtainable.
Image Attribution
Image credit goes to Ernest, dinglisch, rubberbigpepper, Svet Ivantchev, and Aviad (also known as Hotfortech).
Their work is acknowledged for the visual representation accompanying this information.
The Rationale Behind Trip Recording
Frequently, I am questioned about the purpose of documenting my journeys. The perceived interest in such recordings, and the subsequent handling of the collected data, are common inquiries.
Initially, this practice stemmed from a well-known local anecdote in Israel. It involved a driver who received a citation for failing to halt at a stop sign, despite having done so correctly…
However, the primary benefit of this system lies in its ability to capture in-car audio. Consequently, all conversations occurring within the vehicle are preserved, creating a lasting record of valuable family experiences.
Setting aside these considerations, there remains the potential to document unexpected events, such as:
The embedded Flash content is unavailable, as Flash technology is no longer compatible with current web browsers.
Alternatively, one might encounter situations similar to this example (sourced from 9gag):
Regarding the management of this data, I retain it for personal reasons. I prioritize the accumulation of memories and am prepared to allocate the necessary resources for their preservation, a decision reflecting individual preferences (a more detailed discussion will follow in a subsequent article).
Utilizing a Smartphone Versus a Dedicated Device: A Consideration
While we at HTG acknowledge the advantages of specialized equipment, many tech enthusiasts prefer a converged device. The inconvenience of managing multiple devices and the need for constant manual synchronization of data can be significant drawbacks. Fortunately, smartphones offer numerous applications designed to streamline these processes and eliminate the need for manual intervention.
However, prolonged and intensive use of a smartphone’s capabilities – such as recording 1080p video, utilizing GPS, and maintaining Bluetooth connectivity with the screen active – can present certain challenges.
- Battery Life – Unless your device, similar to the S4, supports charging while performing these functions, you might experience a net loss of battery power during extended trips, even when connected to a power source. My personal experience, starting with the S2, indicates that a robust power adapter capable of delivering the device’s maximum charging current (around 1000mAh) can prevent this issue. I’ve even successfully used a first-generation Galaxy Tab with a 4100mAh battery for 40 minutes daily without external power, retaining sufficient charge for the remainder of the day.
- Heat Generation – Pushing your device to its operational limits may exceed the manufacturer’s intended usage parameters. Given the typical dashboard mounting location, exposing the device to direct sunlight can exacerbate this. This could potentially result in A) an uncomfortably warm device upon arrival and B) a possible reduction in the device’s overall lifespan. While the standard two-year warranty offered with Galaxy devices may cover such issues, this remains a personal assessment.
- Performance Impact – The continuous background workload may lead to noticeable slowdowns when attempting to use other applications concurrently, such as a navigation app like Waze. Furthermore, devices with limited processing power and RAM may trigger the Android system to automatically close applications to free up memory. For devices with lower specifications, these limitations could be prohibitive. Nevertheless, my experience with the S2 has shown that the performance decrease is often acceptable.
Ultimately, the decision involves a series of trade-offs. The suitability of using a smartphone in this capacity is a matter of individual preference and depends on your specific needs and priorities.
Essential Components for Transforming Your Android Device into a Road Recorder
To repurpose your Android device as a dashcam, only a few readily available items are required.
A Video Recording Application
Numerous video recording programs exist, but after extensive evaluation dating back to my early Android explorations, I continue to recommend VideoReg as the superior option.
While it's a paid application, its capabilities, in my opinion, surpass those of any free alternative. Beyond standard features like full HD video recording, proximity sensor-triggered image capture, adjustable temporary data allocation, and GPS data overlay, this app uniquely records GPS information as a standard subtitle file. This allows playback with any subtitle-compatible application. Furthermore, it can display the recorded video directly on your screen, eliminating the need to open the app to monitor the recording. Importantly, VideoReg supports Tasker triggers for actions like starting or stopping recording, making it ideally suited for automated operation.
I’ve also been informed that the application’s developer is currently working on enabling support for the Samsung Galaxy S4’s dual-camera functionality, allowing simultaneous audio and video capture. Support the continued development of this valuable tool by acquiring VideoReg from Google Play.
An Automation Program
The goal is to eliminate the need for manual intervention when entering your vehicle. We aim to automate the process, so that simply mounting your device initiates recording. Tasker will be utilized for this automation, though any comparable automation application can be employed.
Tasker can be directly downloaded from the developer’s website.
A USB Power Adapter for Your Vehicle
Even if your car features a USB port integrated into its sound system, it’s generally not advisable to rely on it for power delivery. These systems often lack the capacity to provide the necessary amperage. Some systems deliver as little as 200mAh. Considering the power demands of modern devices like the Galaxy S4 (2000mAh) or even older models like the S2 (800mAh), this is insufficient.
Numerous adapter options are available (the image below is merely an example). A model offering “2.1A + 1A” (2100mAh + 1000mAh) output is preferable. We strongly recommend selecting an adapter with at least a one-year warranty, as a faulty adapter could potentially damage your device.
A Bluetooth-Enabled Car System (Optional)
This guide will demonstrate utilizing a Bluetooth connection as a state indicator for Tasker, for two primary reasons:
- Firstly, a Bluetooth connection allows for hands-free phone calls and audio playback from your device through your car’s sound system, aligning with the concept of a converged device.
- Secondly, compatibility issues can arise between Android devices and car stereos with USB connectivity. Phones may not always register as standard “mass storage devices,” preventing audio system functionality.
If your car lacks a Bluetooth-compatible stereo system and you’re unwilling to invest in an upgrade, consider a Bluetooth-to-FM transmitter. This device connects to your phone via Bluetooth and broadcasts the audio signal to your car stereo as a standard radio frequency. I have personally used the JABRA CRUISER, and while I eventually upgraded to a dedicated car stereo after two years, it performed adequately.
A Car Mount
While a vast selection of car mounts is available, consider these points:
- Avoid mounts designed exclusively for your specific device. These are often incompatible with cases or skins and become obsolete with device upgrades.
- Invest in a quality mount. While inexpensive options are tempting, they often prove unreliable and require frequent replacement. Prioritize a mount with at least a one-year warranty.
A Camera Lens (Optional)
This may be unnecessary for most users, but for those interested, camera phone lenses can expand the field of view. A wider angle is beneficial for capturing more of the road, potentially crucial for recording events outside the central view. A set of these lenses can be found for around $5.50 on eBay.
I personally utilize a 180-degree lens for road recording, while preferring a 160-degree lens for general photography:
Tasker Profiles and Tasks for Road Recording
To enable this functionality, utilizing Tasker is essential. You can either import a pre-configured simple project or advanced project, or alternatively, construct everything manually following the instructions provided below.
The simple project incorporates all the profiles and tasks detailed herein. The advanced version expands upon this with A) a profile that maximizes the "Media" and "BT" volumes; B) a delay implemented after a phone call concludes before video recording resumes; C) the capability to create a toggle widget; and D) a disconnection between the BT toggler and the VideoReg profile, allowing for a dedicated "car mode" profile, potentially enabling BT connectivity alongside other "car mode" functions unrelated to VideoReg.
Creating Profiles Manually
The necessary steps involve creating a profile to initiate and halt recording when in car mode, and another profile to manage the BT device activation, unless the device is consistently left running.
The V4C Profile Configuration
To begin, we will guide you through the process of adding the "BT state" trigger to the profile; further triggers can be added independently.
First, add a "State" trigger.
Next, select the "Net" category.
Then, select the "Bluetooth Connected" subcategory.
When prompted for the BT connection name, ensure Bluetooth is enabled on your device and click the search icon. Subsequently, choose the appropriate BT connection name corresponding to your car's system.
For enhanced specificity, you can also select the MAC address of the device. This prevents accidental triggering by other BT devices sharing the same name.
The completed configuration should resemble the following:
We have renamed the profile to "v4c" (VideoReg For Car) for brevity in the status bar. A battery level check has also been added, ensuring the profile only activates with at least 6% battery remaining, preventing potential device shutdown due to power consumption.
Furthermore, the profile is optionally configured to disable during active phone calls. This is due to potential instability and disruption to both call participants when the camera restarts during a call.
When prompted to create or select an entering task, create a new task and choose the "Misc" category.
Select the "Send Intent" action.
In the "Action" field, enter "rubberbigpepper.VideoReg.StartRecord" (without quotation marks).
Then, create an "Exit" task that performs a similar function, utilizing "rubberbigpepper.VideoReg.StopRecord" in the "Action" field.
The BT Trigger Profile (Optional)
This profile may be unnecessary if you consistently leave your BT enabled. However, for those who disable BT, here's how to create a toggler that:
- Activates the BT device when the Android system is connected to a power source.
- Allows 15 seconds for the pairing process to complete.
- Maintains BT activation if pairing is successful, otherwise disables it.
Add a "State" trigger.
Select the "Power" category.
Select the "Power" option.
Select the "Any" type.
The "Save on 3" Profile (Optional)
This profile addresses the limitation in VideoReg of assigning only one action to the proximity sensor. If you desire both photo and video capture, this profile provides a solution.
VideoReg is configured to capture a photo upon proximity sensor activation, while Tasker initiates a "save video" action if the proximity trigger remains active for 3 seconds.
To create this profile, add a state and select the "Sensor" category.
Select the "Proximity Sensor".
Leave the settings unchanged and proceed to create the "Task".
The "Task" should begin with a 3-second "wait" followed by sending an "intent" of "rubberbigpepper.VideoReg.RescueVideo".
Then, scroll to the end of the "Intent" action and add an "IF" condition, ensuring the action is only triggered if the "Save at 3" profile remains active.
The final configuration should appear as follows:
With these configurations complete, you should be able to connect your device to the car's power source, initiate BT pairing, and begin road recording once paired.
The HTG simple profile and HTG advanced profile are available for your convenience should you prefer to import them.
It’s a rare person, someone who’s mistaken for what he truly is…