Need help recording a ride, importing a vehicle setup, joining a group or making a replay? Email support@neuralisai.com.
PEV Ride Computer is currently in testing for Android. Coming to Google Play. A public store download is not available from this page yet.
The instructions below cover the Android build. An iOS version is planned after the Android commercial launch, with platform-specific help to follow.
Help us understand the problem
Include your phone model, Android version, app version, what you tried and the message you saw. For group problems, say whether you were hosting or joining and whether personal recording continued. A cropped screenshot can help.
Keep exact routes, home locations, contact numbers, private invitations, account credentials and full backups out of your first message. We can start with a description. Never send a password or a Tailscale sign-in link to support.
Recording stops or the route has gaps
Check that location is enabled, precise location is allowed and the app reports an active recording. Review recording-readiness messages, notification settings, available storage and your phone's battery restrictions. Poor satellite reception, phone shutdowns and interrupted operation can leave gaps.
If the app offers to recover an interrupted recording, review that option before starting another ride. Avoid uninstalling or clearing storage while investigating: those actions remove local records. Save a backup first when the app allows it.
Read Your first ride for the basic recording flow.
The map stopped following me
Panning or focusing on a rally lets you inspect the map without new positions pulling it away. Choose Resume follow to follow again. Follow retains your zoom and bearing and recenters as your position approaches the usable map edge. Choose Full map for more viewing space and quick Ride, Group and Rally panels; Exit returns to the compact view. Make adjustments while stopped.
Finishing a ride needs attention
The finish sheet offers saving your personal recording and leaving the group as separate choices that you can confirm together. Hosts must explicitly choose End group for everyone. An unchecked activity continues. Review the ride name before saving and wait for the completion message.
One action can succeed while the other needs attention. Read the reported result and check Ride and Map before retrying. A saved recording does not need to be saved again merely because group departure failed. If the recorder is still finishing or group sharing is still stopping, let that operation finish and follow the message shown before starting an export.
Group positions look old or a connection fails
Check the group's connection status and the age of the displayed positions. A rider's last position is not proof they are still there. Internet loss can interrupt group updates while your personal recording continues.
Open Map → Group ride to review the connection and membership. Group rides use your optional Tailscale account; follow any account or invitation steps shown by Tailscale. The app does not need this account for solo recording.
Leave group stops your local sharing even if the app cannot confirm departure with the host. Other members may still see your last known state or an unresolved SOS. Contact them another way if they need to know you have left. Leaving is not an all-clear.
Removing a friend from the app is different from revoking Tailscale access. Manage account or network access in Tailscale when that is your intention.
Rally attendance looks wrong
Automatic arrival needs fresh, sufficiently accurate shared positions that remain slow and near the rally for 30 seconds. Passing through, uncertain GPS or repeated old fixes may not establish arrival. Check the rider's connection and position age. Missing updates are not treated as proof of departure.
Use I'm here to confirm your arrival or Undo my arrival to correct it. Undo prevents immediate automatic re-arrival until you leave and return, or confirm again. A manually confirmed arrival can remain current while your connection is fresh. A new or moved rally resets attendance. Older hosts may not show these controls. Attendance is an estimate for coordination, not proof of exact location or safety.
If a host removes you, the app explains the current session's rejoin restriction. Your personal recording and saved friend permissions remain independent. Contact the host another way if you need to discuss access.
Group SOS or alert sounds need attention
To send a manual Group SOS, complete three distinct taps on SOS · 3 taps within four seconds, then choose Send SOS in the confirmation. Holding the button does not complete the sequence. A timeout, cancellation, navigation or leaving the app resets incomplete progress. You can send without a message or add up to 160 characters; Edit SOS message updates the active incident without creating another incident or sending emergency-contact SMS. Older hosts may support SOS without message editing.
Incoming SOS and rally alerts repeat different sound and vibration patterns. Silence and swiping away a notification acknowledge it only on this phone. I'm coming or On my way also attempts a shared response; review pending or failed status. Silencing does not send an all-clear or tell anyone you are coming. A changed SOS message can notify you again unless you are already responding.
Open Group alert sounds, review readiness and use Test SOS sound or Test rally sound. Tests are local, last three seconds and pause during an active alert or crash countdown. Check Android notification permission, the relevant notification channel, volume, vibration, Do Not Disturb and any Bluetooth audio connection. Calls and audio interruptions can prevent sound; your own crash countdown takes priority. A readiness message or sound test does not establish that a later alert will be delivered or heard.
Leaving the group stops its repeating alerts locally. If an alert needs attention, communicate directly with the group when possible; do not treat silence or an old marker as proof that someone is safe.
A setup file will not import
Use a PEV vehicle configuration file, normally ending in .pev-vehicle.json
. In Garage → Import vehicle from JSON, choose the file and read the preview before adding it. A full app backup, GPX route or ordinary spreadsheet is not a vehicle setup file.
If an import is rejected, keep the original file and include the error text in your support request. Do not edit units or numbers at random to make the file pass. Imported specifications still need to match your exact vehicle and configuration.
Map downloads or replay exports fail
Map downloads need an internet connection and enough free space. Download a supported region before you need it offline. Coverage depends on the regions available in the app; a route-only replay is useful when street-map coverage is missing.
Replay videos are rendered on your phone. Long or detailed exports can take time and need free storage. Finish recording and leave any live group before starting a video export; the finish sheet lets you select both. Wait for both operations to complete and follow any remaining blocker shown by the app. Select local music you have permission to use. Spotify Jam links are separate and do not supply audio for replay videos.
Replay photos, stops or edits do not look right
Open Replay → Your ride story to review the video title, stops and photos. Supported stationary stays of five minutes or more and qualifying recording pauses are candidates for review. Missing GPS stays a gap. Add a stop manually if needed, and check any suggested place name against what actually happened; names come from installed offline maps and may be missing or outdated.
You can attach up to 12 photos per ride. Reliable capture times may suggest a place on the route. Photos with missing or ambiguous time information need manual placement; move them along the route or choose a stop. The app accepts supported photos up to 40 MB and 150 megapixels, then keeps smaller private copies. If an image cannot be read, choose a supported copy and keep the original safe.
Save your title or placement edits, then create a new video. Previously exported videos do not update. Exclude leaves a photo attached for later editing; Remove photo deletes the app's private copy, without deleting the original from your photo library. Check captions and locations before sharing.
A trimmed replay is missing a moment
Open Replay range → Adjust to check the selected start and finish against the route preview. Times refer to the original ride; Apply range uses that section in the preview and next export. The displayed video statistics describe the section. Photos and approved events outside it remain saved but do not appear in that section. To bring them back, expand the range or choose Reset to full ride, then choose Apply range.
Smooth Stops shortens intervals the app recognizes as sustained waiting, while preserving included stops and photos in the selected section. It does not erase the original ride or fill missing GPS. Turn it off if you prefer the previous pacing. It starts on when you first set up a replay; an existing replay keeps its saved setting. Apply changes and render a new video—old exports remain unchanged.
Elevation or a hill highlight looks wrong
Reopen the saved ride so the app uses its current analysis. It compares available GPS and pressure elevation and rejects some inconsistent changes, but a smooth sensor error can still resemble a real hill when there is no reliable independent measurement. Phone sensors and GPS quality affect the result; elevation and ascent/descent totals are estimates.
If the result still looks wrong, note the app version, phone model and approximate point in the ride where it occurs. Start with a description or a cropped image that hides private locations; do not send a full route unless it is needed. Regenerate replay videos to include revised analysis. Previously exported videos and files cannot update themselves.
Spotify Jam is out of step or will not open
The host starts a Jam in Spotify, chooses Invite → Share link → PEV Ride Computer, then confirms the invitation in PEV. Riders use Join / reopen Jam; the host can use Open Jam in Spotify. Invitation shared reports the invitation, not verified membership or playback.
Open Music out of step? for the in-app steps. In Spotify, check that you joined the host's Jam and selected Listen remotely for your own phone. Playing the same playlist separately does not join the Jam. If necessary, leave and rejoin in Spotify or ask the host for a fresh invitation. Spotify's account and eligibility requirements apply. PEV cannot confirm playback, measure drift or synchronize phones, so these steps do not guarantee matching audio timing.
Backups and a new phone
Use Settings → Backup & restore → Full app data. Save the backup privately and copy it to the new device. Restoring replaces the current personal app library after you review and confirm it; the app keeps a recovery copy from before the last restore.
Full backups include saved replay titles, stop edits, attached photo copies, event choices, replay ranges and Smooth Stops settings. Excluded photos and photos outside a trimmed range remain in the backup until removed from the ride. Keep original photos separately: the app's copies are optimized for replay. Older app versions may ignore newer replay settings or reject newer backups, so keep a backup from before changing test builds. Do not uninstall or clear storage to resolve an update or restore problem before preserving the data you need.
Downloaded maps, exported videos, imported music, Android permissions, texting-SIM selection and group account/friend setup are not transferred. Review Ride safety afterward: restoring does not send texts, and automatic alerts are turned off. Read Data and deletion before removing the old installation.
Ride safety and alerts
Ride safety is optional and experimental. It can miss an incident or raise a false alarm. Phone operation, placement, permissions, internet or carrier service and recipient availability all affect what happens.
Review the selected phone placement and readiness before riding. In Ride safety → Alert history → Detection checks, recent entries can explain why a possible incident was considered or dismissed, with limited readings such as impact strength and duration. These are diagnostic clues, not proof of a crash or recovery. Walking, handling the phone or losing GPS after a possible incident does not by itself establish safe riding recovery. If you are okay, use the app's cancellation or all-clear controls deliberately.
The recipients depend on the action:
- Manual Group SOS goes to the active admitted group. It does not text your emergency contacts.
- Manual emergency-contact alert uses SMS to the selected contacts. It does not become a group alert.
- An enabled automatic possible-incident alert can request SMS and send to an eligible active group when its countdown reaches the send decision. Each channel has its own result.
Read the confirmation and recipient list before sending an all-clear. Dismissing an alert or leaving a group does not send one. A queued, sent or device-received status does not prove a person has read the message or that help is coming.
The app is not a monitored emergency service and does not arrange rescue. Support email is not an emergency channel. Contact local emergency services directly when possible.
Purchases and privacy
When the app is released, Google Play will show the price, availability and purchase terms for your region. For a store purchase issue, send only the order information needed to identify it; never send payment-card details. Google Play's rules and applicable consumer rights govern refunds.
Read the FAQ, Privacy Policy, Terms of Use and Data and deletion guide.