- I was driving
- I was not driving
No, an active internet connection is NOT required for the app to record a trip.
However, your smartphone must have an internet connection (cellular or Wi-Fi) to upload newly captured trip data to the cloud. If your smartphone is not connected to the internet when new trip data is acquired, it will be uploaded when the internet connection is re-established.
No, the phone must be ON for the app to record trip data.
The phone’s battery level also determines whether the app can run. If the battery level is less than 20% and the phone is NOT connected to a charger, the app will not launch in the background to record data.
Once you download the Go PEMCO app, your phone will prompt you to grant various permissions.
Certain permissions must be “on,” “enabled” or set to “allow” for the app to operate properly:
Yes, the app uses the battery in the phone to operate.
A recent test of modern phones detected a ~5% battery drain per hour when recording a trip. This may vary based on phone model and age, as well as other common battery drain causes such as having multiple apps open or using GPS frequently. We actively review battery drain levels and take innovative approaches to reduce battery drain, such as limiting our reliance on GPS.
If your phone is not connected to a charger and its battery drops below 20% during a trip, the app stops recording the drive. If you connect your low-battery phone to a charger right away, trip recording resumes.
Safety first! Drivers should never attempt to connect the phone to a charging source while driving. Ask a passenger to do it or just wait for PEMCODOMETER to capture your next trip.
The app uploads approximately 500KB to 600KB of data per hour of driving.
If you drive one hour/day for a month, the app will use about 18MB of data. This is a small fraction of a typical U.S. mobile data plan.
- Number of miles driven
- Instances of phone distraction
- Instances of hard braking and hard acceleration
- Instances of hard cornering
Phone distraction is noted when:
- The screen is on
- The phone is moving around
- The car is moving
The app will flag a “hard braking” event when the phone registers about 1/3G when slowing down. If the pavement is slick from rain or ice, most tires can only handle about 1/2G without skidding. Staying well below that contributes to safe driving.
We understand not all hard braking is bad driving! Sometimes quick braking can save you from an accident if you’re cut off or a pedestrian unexpectedly steps into the street.
Frequent hard braking, however, is associated with things like tailgating and not paying attention. If the app notices you’re braking hard a lot, it notes it as a concern. PEMCODOMETER must detect all braking events to determine whether hard braking is common for you.
The app characterizes “hard acceleration” when it registers 1/3G or above when speeding up. It’s safer to accelerate more gradually. You’re less likely to skid if the road is wet or icy, and you reduce the risk you’ll be hit by someone running a red light.
Frequent hard acceleration is linked with aggressive driving, and aggressive drivers are more likely to get into crashes. The app lets you know if you’re accelerating quickly. If it notices hard acceleration often, it will affect your overall score more strongly.
The app will flag a “hard cornering” event when the phone registers about 1/3G sideways as you go around a corner.
If the pavement is slick from rain or ice, 1/2G is about the maximum that most tires can handle without slipping. It’s best to stay well below that.
Some intersections (and windy roads) can force you to corner hard to keep up with traffic. If you find that the app keeps flagging hard cornering at the same spot, consider choosing a safer route if one is available.
The app will flag speeding when you exceed the speed limit by more than an incidental amount.
We realize that sometimes the flow of traffic is faster than the legal speed limit. But as speed increases, fatal car crashes go up as well. The “safest” choice can be complicated, so we currently set the safe speed only slightly above the legal limit.
- Location and travel direction
- Accelerometer data
- Gyroscope data
- Magnetometer data
- Barometer data
- Phone state
- User Activity (Android) or Motion & Fitness (iOS)
The app begins tracking location information to determine if a trip is in progress when the smartphone’s operating system detects a change in the phone’s location. Once it confirms a trip has begun, it records the location for the duration of the drive.
- The phone is unable to identify GPS location.
- The accelerometer embedded in the phone is not working or is malfunctioning.
- The gyroscope embedded in the phone is not working or is malfunctioning.
- The phone is having memory issues.
- The phone is running multiple resource-intensive apps and is unable to provide the app with the required resources.
- Do not force quit the app unless necessary.
- To force quit an iOS app, open the apps switcher and swipe the app upwards off the screen.
- If you force quit the app during a trip, it stops the app from recording for a bit. However, the app will resume recording if it determines the trip is still in progress. The time during which the app was stopped will not have any recorded data available for processing.
- If you force quit the app when a trip is NOT in progress, there will be little impact. The app will be ready to begin recording again in a short while and will record as expected unless a new trip starts immediately following the forced quit.
Generally, it takes up to 10 minutes for tabulations to appear. There are many reasons why trips are not available to review instantaneously:
The app needs time to determine whether the drive is complete. When motion is no longer detected, it continues recording until it is certain the drive is over and you’re not simply sitting at a red light or stuck in traffic.
It takes time to perform all calculations and render the trip results. Depending on the length and quality of the drive, that could take up to 10 minutes.
If your phone loses its network connection, newly captured trip data cannot be uploaded to the cloud for processing. Likewise, your phone can’t receive tabulated trip information for display without a connection. If the phone’s network connection is down, trip data and tabulated trips awaiting transfer are transmitted when the connection is re-established.