The RedTiger mobile app uses the camera as its own WiFi access point. That's a simple design with a predictable set of failure points. The camera broadcasts a network, your phone joins it, and the app opens a socket to the camera at a fixed local address. Nothing goes over the internet. So when the app says "device not found," the problem is nearly always one of three things: your phone stayed on its normal mobile network, the phone's "smart network switch" quietly kicked you off the camera's WiFi because it had no internet, or the camera's WiFi module is asleep.
\nThe fix for the second one trips up almost everyone. Android and iOS both prefer networks with internet access. A camera WiFi network has none, so the phone will silently reassociate to your home WiFi or 5G within a minute. Turn on airplane mode, then manually re-enable WiFi only \u2014 that stops the phone from hunting for a better connection. On Android, also open the camera network's advanced settings and set it as "unmetered" and disable auto-switch. On iPhone, tap the info button next to the camera's SSID and turn off "Private Wi-Fi Address," which some phones apply in a way that breaks the app's handshake.
\n\nOne quirk worth knowing: some phones only connect to 2.4GHz networks reliably when the camera's AP is 2.4GHz-only, and many Android phones default to preferring 5GHz. If the SSID doesn't appear at all, check that your WiFi settings aren't filtering out 2.4GHz-only networks.
\n\nOnce connected, you'll land on a live preview. Two settings matter more than the rest and both live in the app's camera settings menu. First, set the resolution to the highest the camera supports for the front channel \u2014 many units ship on 1080p to keep file sizes small, and you're leaving detail on the table. Second, turn on the timestamp and your plate/ID watermark if the app offers it; a timestamp you can prove is set to local time is worth far more in a claim than a beautiful 4K clip with the wrong clock. The app syncs camera time from your phone, so make sure the phone's time zone is right before you connect.
\nAlso check loop recording duration and G-sensor sensitivity while you're in there. Medium sensitivity and 3-minute segments are the settings that keep a 128GB card healthy through a full month of driving.
\n\n| Method | Speed (1-min clip) | Best For |
|---|---|---|
| App WiFi download | 20\u201360 seconds | Grabbing one clip at the roadside |
| Card in a laptop reader | Under 5 seconds | Reviewing a whole trip, archiving |
| App cloud/phone backup | Minutes, data-dependent | Small clips you want off the card fast |
WiFi transfer is convenient and slow. A 1-minute 4K clip is roughly 200\u2013350MB, and the camera's WiFi throughput is typically in the 2\u20136 MB/s range, so expect somewhere between 30 seconds and two minutes per clip. If you're standing at the scene of a collision, don't fight the app \u2014 pull the card and use a reader or your phone with an OTG adapter. That's faster, and it avoids the risk of the app truncating a file mid-download, which produces a corrupt clip that won't play at all.
\nIf you need to hand footage to a police officer or the other driver, the app's "download and play" path produces a phone-local copy you can share immediately. Do that before you leave the scene, because the camera will loop over the original within a day or two depending on card size and driving hours.
\n\nUpdates usually arrive as a WiFi-pushed notification when the app is connected. Take them. Firmware fixes on dash cams tend to address exactly the things that annoy people: random reboots in heat, better night exposure, and parking mode trigger reliability. Before updating, format the card \u2014 updates write to the card and a fragmented card can abort the process halfway. Keep the phone within arm's reach and don't let the screen lock; a dropped WiFi link during a firmware write can leave the camera needing a manual recovery file.
\n\nExport clips out of the app to your camera roll as soon as you can. Apps that keep footage in their own library lose it when you uninstall or clear storage, and more than one insurance dispute has died because the clip lived only inside a phone app that got wiped. Put the important ones in a cloud folder with the date in the filename. If you're assembling an incident report, grab the front and rear clips plus one clip from 60 seconds before the event \u2014 the lead-up is what establishes who did what first.
\n\nWork through this in order and you'll solve it about 95% of the time: reboot the camera by unplugging it for 30 seconds; forget the camera's network on your phone and rejoin; force-close the app; then try a second phone. If a second phone connects and yours doesn't, the camera is fine and your phone's WiFi settings are the issue \u2014 usually private MAC randomization or an auto-switch setting. If neither phone sees the SSID, the camera's WiFi module needs a power cycle at the fuse box level or the card needs formatting, since a card the camera can't mount sometimes prevents the AP from starting at all.
\nFor reference, the RedTiger units that support app control and 2-channel recording are listed on the current RedTiger lineup page.
\n ← Back to Blog