Picture this: you're a new driver, you've got Marmalade insurance because you wanted rates that actually fit your situation, and you install the telematics thing because discounts sound good. Then the app says "no journeys recorded" or you can't log into the Direct Line app and your insurance score sits at zero. Frustrating, right? Let's sit down with a strong coffee and sort it out step by step.
Master Marmalade Telematics: What You'll Fix in One Afternoon
By the end of this guide you'll be able to:
- Get DrivePlus or a telematics app to reliably detect journeys again. Fix Direct Line or insurer app login problems that block access to scores and discounts. Adjust phone and app settings so trips record in the background without you babysitting the app. Apply advanced tweaks that increase recording reliability and protect your privacy. Know exactly what to tell support when escalation is needed, and how to avoid common mistakes.
Before You Start: What You'll Need in Your Pocket and Garage
Gather these items before you begin troubleshooting. Think of this as putting your toolkit on the table.
- Your smartphone with the telematics app installed (DrivePlus or insurer app). The account login details (email and password). If you use single-sign-on, have that account accessible. Access to the car - the phone will need to detect movement and connect to car systems if a plug-in dongle is used. USB cable or charger to keep the phone powered during a test drive. Patience and a notebook or screenshot tool to capture error messages for support.
Optional but useful:
- A second phone to test whether the issue is the device or the account. An OBD-II dongle if your policy uses a plug-in device - check that it’s properly seated and showing any LEDs the manual mentions.
Your Marmalade Telematics Repair Roadmap: 7 Steps to Fix DrivePlus and App Issues
Follow these steps in order. Think of this as a map for getting journeys to show up. Take the shortest path first.
Step 1 - Confirm account health
Log in to the insurer's website from a desktop or laptop. If you can't log in there, the problem is account-related not the phone. Use "forgot password" to reset, check spam for verification links, and confirm the email address matches the one you used on the app.
Step 2 - Update everything
Open the App Store or Google Play and update the telematics app. Update your phone's OS if it's pending. Apps and OS versions that don't match the expected versions often break background location permission or authentication tokens.
Step 3 - Phone-level settings that break recording
On Android: set location to "High accuracy", allow background location access, exempt the app from battery optimizations (Settings - Battery - Battery optimization - exclude the app), and enable autostart if your manufacturer hides background apps (Xiaomi, Huawei, Oppo tend to kill apps aggressively).
On iPhone: set Location to "Always", enable Background App Refresh, switch off Low Power Mode during testing, and ensure Motion & Fitness is allowed. Make sure the Date & Time is set to automatic - skewed clocks break tokens.
Step 4 - Clear app state
Force quit the app. On Android, go to App Info and clear cache (not always necessary to clear data unless you want to log in again). On iPhone, delete and reinstall the app. Re-login and watch for any permission prompts - grant them.
Step 5 - Test with a short drive
Create a controlled test: park, make sure phone GPS is working, start the car and drive somewhere five minutes away. Keep the phone in a stable mount or cup holder. Check the app immediately after switching off. If journeys appear, you fixed it.
Step 6 - Inspect physical telematics devices
If your policy uses a plug-in dongle (OBD-II), ensure it’s fully inserted, clean, and not obscured by steering locks or security collars. Some dongles need ignition on for initial pairing. Check any status LEDs and consult the dongle manual for blink codes.
Step 7 - Gather evidence and escalate
If steps 1-6 fail, collect screenshots of permission settings, the app's error messages, timestamps of test drives, and photos of the dongle and its placement. Send these to insurer support and ask for a remote session or higher-level technical review.
A Quick Win: Get a Journey Recorded in Under 10 Minutes
Do this now while you still have attention. It solves most "no journeys" problems immediately.
Avoid These 7 Mistakes That Stop DrivePlus from Recording
These are the things people do that sound plausible but silently prevent recording.
- Leaving battery saver on. The phone's OS punts background GPS to save power and the app will be starved of updates. Ignoring multiple phones. If you have a second device, make sure it isn't the one paired for trips or sending conflicting data. Using a cheap phone mount that blocks GPS signal. Metal enclosures and full-size phone cases can degrade reception. Assuming a dongle always stays plugged in. A partially seated OBD-II plug won't pair consistently. Granting "approximate" location only (iOS) - telematics need precise location. Not updating the app - older versions may use deprecated background APIs. Relying on the app to "magically" fix itself overnight. Sometimes you need to actively clear and reauthorize permissions.
Pro-level Fixes: Optimize Your Telematics Score and App Reliability
Ready for the stuff most people skip? These tweaks reduce false negatives and boost your chances of getting a fair score.
Lock the app into memory
On many Android skins you can lock an app so the OS doesn't kill it. Open the recent apps screen and tap the lock icon or app pin option. This keeps the telematics app running in the background.
Use a dedicated phone for telematics
Crazy-sounding but effective: a cheap runner phone with GPS and a stable battery can be dedicated to telematics. No games, no social apps that wake the phone and no power-hungry services fighting for GPS time.
Force GPS to high accuracy programmatically
Some advanced users install a GPS status app to confirm satellite lock and force high accuracy. This helps when hilltop parking or urban canyons confuse the logger.
Manage Bluetooth and car systems
If your phone pairs to the car for calls, some telematics systems use the Bluetooth connection as a trigger. Ensure Bluetooth pairs reliably and isn't locked by car settings that prioritize a different phone.
Firmware and dongle health
Ask insurer support whether your dongle has firmware updates. Older firmware sometimes drops connections with modern phones. If you suspect hardware failure, request a replacement.
Protect privacy without breaking recording
Turn off unnecessary permissions not needed for telematics (like camera). For many insurers, the minimal required set is precise location, motion data, and background refresh. Audit what the app actually asks for in permissions and keep only those.
When Telematics Apps Fail: Fixing Common Journey, Login, and Sync Errors
Here are targeted fixes for the exact problems you mentioned: DrivePlus not recording and Direct Line app login failures.
DrivePlus or journey not recording - targeted fixes
- Check the in-app status: some apps have a "connected device" or "status" page where they show last sync time. If it's hours old, the app isn't sending data. Look for a "start trip" toggle - some systems expect you to start the trip manually if automatic detection fails. If using a plug-in device, try unplugging and replugging it while the ignition is off, then start the car and wait 60 seconds. Ensure your phone's motion sensors are working. Some phones let you calibrate the accelerometer in diagnostic menus.
Direct Line app login problems - targeted fixes
- If you see "invalid credentials" but the same info works on the website, clear the app cache or reinstall. Corrupt cached tokens are common. Two-factor SMS codes not arriving? Check blocked senders and that your carrier isn't filtering the SMS. Try a different phone number if possible. Login stuck on a loading spinner - check that device time is set to automatic. Security tokens rely on clock sync. Password resets directing to an old email - make sure the insurer has your current contact on file. Ask support to manually verify your identity and update the email.
Contrarian Viewpoints: When Telematics Is Doing You a Favor by Being Strict
Most guides treat telematics as a purely benevolent tool. Here's a different angle: sometimes unreliable logging or an app that aggressively kills background tasks protects you from constant surveillance. If you're worried about privacy, that "journeys not recorded" message might be the lesser evil.
Also, the industry trend of rewarding only "perfect" sensor data what does a black box track creates perverse incentives. A driving score that plummets because your phone is denied background access isn't a measure of driving ability - it's an artifact of ecosystem complexity. Pushing insurers to accept broader evidence - like in-car dashcam logs or OBD trips - is a valid approach rather than just tweaking your phone.
When to Complain and How to Escalate Effectively
If you've done everything above and the readings still make no sense, escalate, but do it like a professional.
- Prepare a timeline: dates, times, screenshots of failed journeys, phone model, OS version, app version, and whether a dongle was used. Send a single, clear email to support with the evidence attached. Ask for a specific outcome - replace dongle, escalate to technical team, manual credit for test drives. If the first-level agent can't help, ask for a written escalation reference number and the expected response time. Keep records - you'll need them for complaints or ombudsman claims.
Final Checklist: Do This Before You Call Support
Reboot the phone and car electronics. Ensure app and OS are updated and permissions are granted (location always, background refresh, motion access). Run a short 5-10 minute test drive and note the exact start/stop times and route. Take screenshots of the app's dashboard, permission screens, and any error messages. Check whether journeys appear on the insurer's web portal - sometimes the mobile app lags behind the server view.All that remains is to accept that telematics will occasionally produce false negatives. Most problems are solvable with a methodical approach: check accounts, fix permissions, test, and provide evidence to support. If you're buying Marmalade or another insurer for a young driver, insist on clear setup instructions and an easy way to test the device so you don't find out about missed trips at renewal time.
Now go fix that app. If you want, tell me the phone model, OS version, and the exact app error, and I’ll give a tailored checklist you can hand to support.