When tracking stops: phone, battery, permissions, signal and a car device
A clear guide to battery, permissions, signal, power cuts and offline states, plus the difference between an Oculamor tamper event and an enabled disconnect rule.
“The location has not moved.” That is a status to investigate, not a conclusion about the driver.
Tracking can pause for ordinary reasons: a phone battery can die, a permission can change, a vehicle can enter a poor-signal area, or a service can take time to reconnect. The right response depends on what is doing the reporting and what the product actually promises.
The interruption matrix
| Situation | Phone-based sharing | Oculamor car reporting | What you cannot infer |
|---|---|---|---|
| Phone battery is flat | No fresh app location from that phone; a last-known state may remain | The car device can continue independently if it has power and connectivity | That the driver caused the gap |
| Location permission is changed | App features can be limited; Apple says app access is controlled in Location Services | The car device does not depend on the driver’s phone permission | That the car stopped moving |
| App background or battery settings change | Drive detection may be affected; Life360 documents these conditions | Phone settings are not the reporting path | That a missing drive was deliberate |
| Mobile or GPS signal is poor | Updates and event quality may degrade | Device data or delivery can also be delayed | That a stale point proves tampering |
| Vehicle power is removed | A separate phone service may keep reporting the phone | A received power-cut/tamper event may be processed; coverage afterwards depends on power and signal | That every removal is instant or impossible to evade |
| Account sharing is paused | The provider may show a paused or unavailable state; stored reports can have separate rules | Account roles still govern access | That consent or all reporting has ended everywhere |
This is a troubleshooting guide, not a covert-monitoring guide. Do not use a gap as an excuse to accuse someone or to work around their safety and privacy controls.
Phone, battery and permissions
Life360’s Drive Detection guidance says it uses phone location and activity. It requires Drive Detection to be enabled, more than 10% battery, background operation, battery-saving settings disabled and a strong cellular signal. If a condition is not met, the service may label the event a Trip rather than a Drive. Its driving-events guidance also says Free members can see a weekly family summary, while Gold and Platinum members can see Individual Driver Reports.
Apple’s UK safety guidance describes Location Services as a permission that can be switched off globally or per app. When it is off, third-party apps cannot use Location Services in the foreground or background. That explains why a phone-based view may become less complete; it does not establish why a person changed a setting. Apple also has separate offline finding features for supported devices. Do not collapse every Apple feature into the behaviour of one location-sharing app.
The practical check is the timestamp, device battery, permission state, app status and network context. Ask the driver what happened. If you need a safety response, use a service that actually provides emergency support; a stale location is not an emergency dispatch mechanism.
Power cuts, tamper and ordinary disconnects are different
Oculamor can process a power-cut or tamper alarm when the device reports one. An ordinary loss of connection is different: a disconnect notification requires an enabled rule and has a ten-minute grace period. That rule is not part of the default setup, so check your settings and recipients.
Neither type of alert guarantees an immediate message whenever the device goes offline. Delivery still depends on the device, service and network. Agree together which notifications you want and who should receive them.
What a car device changes
Oculamor is installed in the vehicle, so its journey reporting does not depend on the driver carrying a charged phone with location permissions enabled. It can provide a car-linked journey record, recorded speed and available mapped speed-limit context for review. It still needs its own power and connectivity, and the person viewing the dashboard needs internet access.
That is useful if the phone is left at home or the family wants to discuss how the car travelled. It is not a person-identification system. A record follows the vehicle; it cannot prove who drove, who was a passenger or why an event occurred. Parked locations and destinations can remain visible, so explain the scope before fitting the device.
For a family agreement, write down the response: who checks, who is contacted, which gaps need a conversation and which simply wait for reconnection. That is more useful than turning every missing dot into a disciplinary event.
A calm review routine
When a record is missing, use this order:
- Read the last update time and current status.
- Check battery, permissions, background settings and signal for phone services.
- For Oculamor, check device power/connectivity and whether the intended alert rule is enabled.
- Ask the driver or account holder what changed.
- Treat a gap as uncertainty until other evidence explains it.
If your main need is phone location or an agreed arrival notification, a free sharing service may be enough. If your need is a vehicle journey record independent of the driver’s phone, see the Oculamor dashboard preview. Standard pricing is £7.99 per month per vehicle or £81.50 annually, plus a £30 device; create an account only after checking that this scope suits the family.
Check Oculamor's scope and alert limits
Oculamor removes the driver's phone from the reporting path, not the need for power and connectivity. Check its scope and alert limits before choosing it.
You might also like
More articlesDoes Life360 work when your teenager’s phone is off? Phone tracking vs a car tracker
Does Life360 work when a teenager's phone is off? Compare phone-based location sharing with a car tracker that records the vehicle's journey independently of the driver's phone.
AirTag or car tracker for a new driver? Start with what you want to know
Compare AirTag item finding with car journey reports. Understand phone independence, location updates, privacy and what a paid tracker adds for a new driver.
Who drove the family car? What a shared-car record can—and cannot—tell you
A car record follows the vehicle, not a verified human. Learn what Oculamor and phone-based apps can show, how to review a shared-car trip and where privacy limits remain.