Bluetooth tire monitoring for travel trailers
Know every tire.
Every mile.
Spartan RV TPMS gives you a clear view of tire pressure, temperature, leak, battery, and missing-sensor conditions on Android and iOS. Keep essential tire status close at hand on your phone and compatible vehicle display.


Built for the road ahead
Important tire information,
without the clutter.
See each paired sensor in its tire position, so the tire that needs attention is easy to identify.
Live pressure and temperature
View readings in PSI or kPa and Fahrenheit or Celsius.
Clear safety alerts
Recognize fast leaks, pressure warnings, high temperature, low batteries and missing sensors.
Your trailer layout
Choose a single-, dual-, or triple-axle layout and include an optional spare.
Background monitoring
Continue receiving compatible sensors with the screen off, subject to phone permissions and power settings.
Trips History
Review saved readings and offline charts on Android, and export a trip as CSV.
QR scanning & sharing
On Android, share or scan a setup QR, then review sensor assignments before applying it.
More from your TPMS app
Review the trip.
Share the setup. Stay informed.
Trips History
On Android, review saved trips and offline pressure and temperature charts. Export a trip as CSV when you want to keep or share its records.
Settings → Trips History

QR scanning & sharing
On Android, share your trailer setup as a QR image, or use Scan asset QR with your camera. Review the layout, baselines and sensor assignments before applying a scanned setup.
Settings → QR Asset Sharing

Android Auto & Apple CarPlay
Use Android Auto with the Android version or Apple CarPlay with the Apple version to view tire status on a compatible vehicle display. Complete setup on your phone while parked.
Compatible phone & vehicle display

Guided setup
Ready in four clear steps.
Configure your trailer while safely parked.
Choose your trailer
Select the axle layout and optional spare.
Pair each sensor
Start a fresh scan for one tire position and follow the compatible sensor's learn procedure.
Set baseline & units
Use your vehicle's placard pressure and choose your display units.
Finish and monitor
Confirm the setup and check fresh readings from every paired tire.
During Android setup, readings continue while audible alerts remain quiet. A one-minute quiet period follows Finish Setup.
Help inside the app
Guidance is a tap away.
Tap the question-mark button on the monitoring screen to open Help & Support.
- App Behavior
- Understand tire colors, alerts, mute and background monitoring.
- Support & Help
- Find pairing guidance and direct support contact details.
- About
- Check the app name, publisher and installed version.

Compatibility
Use the phone and display
that suit your RV.
Core monitoring communicates directly with compatible Bluetooth Low Energy tire sensors. No account or cloud connection is required for tire monitoring.
- Mobile devices
- Android 9 or newer phones and tablets, plus compatible Apple devices.
- RV profiles
- Single-, dual-, or triple-axle trailers, with an optional spare.
- Vehicle display
- Android Auto is supported by the Android version, and Apple CarPlay is supported by the Apple version. Availability depends on the phone and compatible vehicle display.
- Connection
- Compatible powered TPMS sensors via Bluetooth Low Energy.
Spartan RV TPMS Privacy Policy
This policy explains how Spartan RV TPMS, published by SpartanLync Technologies, accesses, uses, stores and shares information. It covers the Android app and information you choose to send to its support contact.
At a glance: RV settings, paired sensor assignments and Trips History are stored on your phone. No app account or cloud trip-history service is required. The app does not obtain GPS coordinates or record travel routes. QR scanning uses Google ML Kit, which processes camera images on the device and separately sends technical diagnostics and usage metrics to Google as described below.
1. Information the app accesses and why
| Information | Purpose and handling |
|---|---|
| RV configuration and preferences | Vehicle model, axle and spare layout, an asset or monitor name you enter, cold-pressure baselines, units, paired sensor identifiers, setup progress, consent choices and alert preferences are saved locally to configure monitoring and restore your setup. |
| Bluetooth sensor data | Nearby sensor identifiers, received pressure and temperature, battery or voltage information, alert and availability states, reception times and signal strength when available are used to discover and pair compatible sensors, display tire status and generate alerts. |
| Trips History | Monitor names, trip/session start and end times, tire positions, sensor identifiers, received readings, battery information, alerts and signal information are recorded locally for history, offline charts and optional CSV export. Trip times describe monitoring sessions; they are not GPS routes. Illustrative sample records use separate storage from real monitoring history. |
| Camera images and scanned QR content | When you choose Scan asset QR and grant camera permission, camera frames are processed on the device to read a setup code. The scanning flow does not save photographs or record video. A decoded setup is shown for review before you confirm replacement of your configuration. |
| Technical SDK information | Google ML Kit processes technical device, app, identifier, usage and performance information for diagnostics and operation of its scanning technology. These SDK communications are separate from locally stored tire records; see section 3. |
| Information you send to support | If you email us, we receive your email address, any name in your message, its contents and attachments, and information you choose to provide such as app version, phone model, sensor identifiers, screenshots, logs or exported records. This is used to answer your request, investigate the issue you report and maintain necessary support records. You do not need to send unrelated personal information. |
The app does not require a personal profile, login, payment information, contacts, SMS messages or a GPS travel history. We do not sell app user data or use tire history for advertising. The app does not contain an advertising network or use an advertising identifier for personalized advertising.
2. Permissions and background operation
The app presents its data notice before requesting the permissions needed for live monitoring. Android also lets you control permissions in system settings.
- Bluetooth / Nearby Devices: on Android 12 and newer, discovery and connection permissions allow the app to find compatible tire sensors and receive their broadcasts.
- Location on older Android versions: Android 9–11 associate Bluetooth discovery with Location permission and the system Location setting. Android 10–11 may also require Background Location permission for continued discovery when the app is not in use. Spartan RV TPMS uses these permissions for Bluetooth tire-sensor reception, including background monitoring, rather than obtaining coordinates or building a location or route history.
- Camera: optional, requested for QR scanning. Denying camera access prevents camera scanning but does not prevent normal tire monitoring or creating a sharing QR. Closing scanning or moving the app to the background releases the camera preview. Microphone permission is not requested.
- Notifications, sound and vibration: used for monitoring status and tire alerts, subject to your choices and Android settings. Notification permission is optional on Android versions that request it.
- Foreground service and battery operation: a foreground service, ongoing notification and wake lock support sensor monitoring with the screen off or the app in the background. The app offers a battery-settings choice because Android battery restrictions can interrupt reception. These functions do not give the app access to GPS routes.
- Network access: supports SDK communications and user-selected support or website links. There is no app-operated server to which tire history is automatically uploaded.
Revoking permissions, stopping the app or restricting background activity can interrupt live readings and alerts. Camera permission controls camera access; it is not a separate opt-out from Google ML Kit's technical diagnostic processing.
3. Google ML Kit and technical diagnostics
QR camera scanning uses Google ML Kit barcode scanning. According to Google, camera images and the decoded input/output are processed on the device and are not sent to Google's servers by ML Kit. This is distinct from SDK technical information.
Google's ML Kit disclosure describes collection of device manufacturer/model, operating-system version/build and supported processing hardware; app package and version; per-installation identifiers and, for Google Play services-backed features, diagnostic device identifiers; feature/version/configuration information, input/output size, initialization and other usage events, errors and performance measurements such as processing latency. The library can initialize independently of a successful scan. SDKs may contact Google to obtain models, fixes or compatibility information. These communications also involve the connection information needed to contact Google's servers.
Google uses the metrics to operate, diagnose, protect, maintain and improve ML Kit. Google states that the documented diagnostic data is encrypted in transit using HTTPS and is not transferred by ML Kit to third parties. Google's processing and retention are described in its Privacy Policy and data-retention information. See also ML Kit privacy information and ML Kit's Android data disclosure. The app does not use these metrics to build an advertising profile.
4. When information leaves your phone
- CSV export: records are shared only when you choose an export and a destination through Android. A CSV can contain monitor names, trip times, sensor identifiers, tire positions, readings, battery information, alerts and reception details. The selected app, service and recipients handle the copies they receive.
- QR setup sharing: a setup code contains the asset name you enter, vehicle model/layout, cold-pressure baselines, units and sensor identifiers. It excludes Trips History, live readings, consent and permission choices. Anyone who receives or photographs the code can read that setup. A CRC-32 checksum checks for corruption; it does not encrypt the content or authenticate the sender. Share codes only with intended recipients.
- Android Auto: tire status, configured tire positions, units, readings and alerts are passed to a connected Android Auto host through Android's automotive interfaces so they can be displayed. The connected host and Google platform services operate under their own privacy practices, including Google's Privacy Policy.
- Google SDK diagnostics: ML Kit's technical information is sent to Google as described in section 3, separately from user-initiated file sharing.
- Email and external links: your chosen email provider and our email-delivery/storage providers process messages you send to support. A browser and the website's hosting/network providers receive normal connection information when you open a website. External services have their own privacy practices. Information you provide to support may also be disclosed where necessary to comply with a lawful obligation.
Permission to access Bluetooth or the camera is not permission to upload your tire records. Normal monitoring, saved history and charts work locally without an app account or a cloud-history subscription.
5. Storage and security
Settings, assignments and history are kept in the app's private Android storage, protected by Android's application sandbox and your device's security controls. Android cloud backup and device-transfer backup for app data are disabled in this build. Use a device screen lock and keep Android and the app updated. The app does not provide an additional password-protected or separately encrypted history vault.
Google's documented SDK diagnostic transmissions use HTTPS. The security of an exported CSV, shared QR image, email or recipient's copy depends on the destination and service you choose. Avoid sharing personal names or sensitive records with unintended recipients. No storage or transmission method can guarantee absolute security.
6. Retention
- Settings and assignments remain until you change or reset them, clear the app's storage or uninstall it.
- Trips History normally retains up to 100 trips per monitor, removing older eligible trips when the limit is exceeded. Trips with unresolved critical events are protected from automatic pruning, so records can exceed that limit and remain until you delete them. History is not automatically removed after a fixed number of days.
- Temporary sharing files: CSV export and QR-image caches older than 24 hours are pruned when the next corresponding export/share operation runs. This is not a guaranteed deletion exactly 24 hours after creation. Android can also remove cache files. Copies saved or sent outside the app remain under their recipients' control.
- Support messages and attachments are kept while needed to handle the request and maintain necessary support or legal records. You may request deletion using the privacy contact below; any information that must be retained for an unresolved request or legal obligation is limited to that purpose.
- Google's SDK records are subject to Google's retention practices. Clearing this app does not erase diagnostic data already received by Google; consult Google's linked privacy information for its handling and available request options.
7. Your choices, access and deletion
No app account exists to close. You can inspect and change locally saved RV settings, view Trips History and export records yourself. Because we do not hold a cloud copy of your tire history, an email request cannot remotely retrieve or erase records held only on your phone.
- Delete one trip: open Settings → Trips History, open the trip, choose Delete and complete the confirmation swipe.
- Delete history: open Trips History, choose Clear History and complete its confirmation swipe.
- Reset configuration and history: use Factory Reset and complete the confirmation swipe. This clears the app's pairing, settings and history and its cached QR sharing images.
- Remove all app-local storage and caches: use Android Settings → Apps → Spartan RV TPMS → Storage → Clear storage/Clear data, or uninstall the app.
- Control permissions: use Android's app-permission settings to change camera, Bluetooth/Nearby Devices, Location or notification access. You can stop background monitoring using Android's app controls, with the reception and alert limitations described above.
- Remove external copies: separately delete exported files and email attachments from their destinations, or ask the recipient/provider to delete them. Resetting this app cannot remove those copies.
For access, correction or deletion of information sent to support, email support@spartanlync.com with the subject “Spartan RV TPMS privacy request”. Identify the correspondence concerned and the request you want handled. We may ask for information reasonably needed to verify the request. Do not send passwords or unrelated identity documents. Applicable legal retention obligations may limit deletion of particular support records.
8. Intended users
The app is intended for adult RV owners and operators, not for children. We do not ask children to create profiles or submit personal information. If you believe a child has sent personal information to support, contact us so that it can be reviewed and deleted where appropriate.
9. This website and other services
This policy describes the app and its support correspondence. Website hosting, content-delivery, email and other external services can process connection information such as IP addresses, browser details, request times and requested pages to deliver and protect their services. Website-level cookies, analytics and forms are separate from the app's local tire monitoring and depend on the published site's configuration and notices. Contact the website operator at the privacy address below for questions about those services. Opening this policy does not grant the app new phone permissions.
10. Contact and policy updates
SpartanLync Technologies
Privacy and support: support@spartanlync.com
Please identify Spartan RV TPMS in your message.
We will update this policy when the app's data handling changes and show the updated effective date here. This policy and the app's Google Play Data safety disclosures should describe the same current practices. Where a change requires a new in-app disclosure or consent, that must be provided before the changed access or processing takes place.
Help & support
We're here when you need us.
Include your phone model, operating-system version, app version and a short description of the issue.
Contact support
Questions about Spartan RV TPMS, setup or pairing?
Email support@spartanlync.comBefore driving
Reinflate tires to the manufacturer's recommended cold pressure and confirm that every expected sensor is reporting.
Open the user manual →To remove local app records, use Trips History, Factory Reset or the phone's app-storage controls. The privacy policy explains deletion and external copies.
Terms of use
Spartan RV TPMS Terms of Use
Purpose and compatible hardware
Spartan RV TPMS displays information received from compatible, paired TPMS sensors and provides the enabled monitoring, alert, history and export features. A compatible Android phone, permissions and supported sensor hardware are required for live monitoring. Reception and alert delivery can be affected by range, interference, sensor batteries, phone settings and the operating system.
Safe use
Check tire pressure against your vehicle placard before travel. When an alert occurs, stop where safe and inspect the tire. Enter the vehicle placard pressure rather than treating an example value or screenshot as a recommendation. Inspect tires independently. Perform setup, pairing and settings changes while safely parked. Do not use the phone while driving; the Android Auto display is for viewing monitoring information.
Examples, exports and third-party services
Illustrative sample values must not be used to assess actual tire condition. CSV files describe locally available app records and are not certified calibration or maintenance reports. QR setup imports require independent placard and sensor verification: a valid checksum detects corruption but does not establish the sender or safety of a baseline. Sharing destinations, Android Auto, the operating system and the hosting website are separate services with their own terms.
Availability and updates
Features depend on the enabled app profile, hardware and platform support. App and host compatibility can change. Keep appropriate backups of exports you wish to retain and check release information before an update. These terms do not remove rights that cannot be excluded under applicable consumer law.
Contact
Questions about use or support: support@spartanlync.com.
User manual
Spartan RV TPMS · Android 0.1.9
User manual
Set up while parked. Check your tires before travel.
Use this guide alongside your sensor manufacturer's instructions and the vehicle placard. Contact support when the observed behavior differs.
1. Before you start
- Park safely. Inspect tires and use a suitable gauge to check cold pressure against the vehicle placard. Example readings and screenshots are not inflation recommendations.
- Use a compatible Android phone and compatible powered TPMS sensors. Turn Bluetooth on.
- Read and accept the app's data disclosure. Grant the Bluetooth / nearby-device permissions requested by your Android version. Older Android versions also require Location for Bluetooth discovery, and background access where requested. The app does not record a GPS route.
- Allow notifications where requested. Review the separate battery-optimization prompt: select Open Battery Settings and choose Unrestricted / Don't optimize where available, then return; or choose Not Now. Pairing waits for that choice.
2. Choose your layout, baseline and units
- Choose the Spartan RV Travel Trailer model and the correct axle count: single, dual and triple axles. Enable the spare only if you intend to monitor it.
- Locate the certification label or data plate on your RV. Use Settings to manage your sensor assignments and pressure baseline. Enter a valid cold axle pressure and, when enabled, the spare pressure from the vehicle placard / approved tire guidance. Confirm the placard statement before saving.
- Select PSI or kPa for pressure and Fahrenheit or Celsius for temperature. Unit choice changes display values; it does not change the physical tire pressure. The high-temperature set point is fixed at 85°C / 185°F.
- Complete sensor setup and tap Finish Setup to save baseline and units and start normal monitoring.
First setup and setup after Factory Reset suppress alert outputs. Finish Setup starts a further one-minute quiet period: BLE reception and live updates continue, while sounds, vibration and alert notifications/popups are suppressed. Old suppressed alerts are not replayed; new frames follow normal rules after that minute. Reopening the app or editing settings does not restart this timer.
3. Pair or unpair a sensor
- Open Settings > Manage Sensors. Normal tire monitoring pauses while Manage Sensors is open; perform this work while parked.
- Choose the tire position and start its fresh 60-second pairing scan before triggering the sensor's approved learn procedure. Only that active selected-tire scan uses high-performance BLE scanning.
- Activate one intended sensor at a time using the manufacturer's procedure. Nearby eligible learn broadcasts can be selected first. For a procedure requiring air release, release air only after the scan has started, and reinflate to the approved placard pressure afterward.
- Check the assigned sensor ID and first received reading against the intended tire. Repeat for each tire and the optional spare. If the scan expires, start another fresh scan and retry the learn procedure.
- Use the selected position's unpair action to remove an incorrect or replaced assignment. An unpaired position is gray and is not monitored. Pair the replacement and verify the assignment again.
- Leave Manage Sensors and finish the required setup / save flow. Confirm live reception for each intended tire before travel.
The pairing frame supplies initial pressure, temperature and battery information. New advertisements replace those readings. A last received value does not prove that the tire is currently healthy.
4. Read the monitoring screen
The vehicle drawing maps road and curb positions and the optional spare to their assigned sensors. Read the pressure, temperature, battery, status and timestamp / reception information available for each tire.
| State | Meaning and action |
|---|---|
| Normal | Received values are within configured limits. Continue independent tire inspection. |
| Warning / critical | Read the alert text, stop safely as appropriate and inspect the tire. See the alert table below. |
| Searching | A paired sensor has not sent its first frame. The app waits silently for up to 15 minutes after monitoring setup. |
| Missing | No frame has arrived for 15 minutes. A yellow caution and unavailable “--” value replace a current measurement. |
| Unpaired | No sensor is assigned. The gray position is not monitored. |
| Invalid / unavailable | No trustworthy current measurement or signal information is available. It is not a zero pressure or a healthy reading. |
Signal/RSSI, when available, describes received radio information. Unknown signal stays unavailable. Check fresh readings for actual tire checks.
5. Understand alerts and the sound control
Pressure limits are relative to your saved cold baseline. They are auto-applied safety limits, not alternative inflation targets.
| Condition | Threshold / indication | Sound schedule while active |
|---|---|---|
| Pressure warning | 12.5% below or 25% above baseline; yellow warning. | Immediately, then every 30 minutes. |
| Critical pressure | 20% below or 30% above baseline; red critical alarm. | Immediately, then every 3 minutes. |
| Rapid leak | Sensor reports a fast-leak condition; critical alert. | Immediately, then every 1 minute. |
| High temperature | 85°C / 185°F or higher. Fixed set point. | Immediately, then every 30 minutes. |
| Low sensor battery | 50% or below (2.6V in the app's 3.0V-to-2.2V estimate). | Once per monitoring session. |
| Missing sensor | No frame for 15 minutes; yellow caution and “--”. | Once per monitoring session. |
Timing is independent per tire and is subject to initial setup quiet periods, mute and phone/platform settings. Reported sensor faults or invalid readings should be investigated rather than interpreted as healthy.
Tap the speaker control to mute or unmute sound only. Tire colors, in-app warnings, phone notifications, background reception and Android Auto status remain active. Mute does not fix an unsafe condition. A first healthy frame clears the active fault and cancels future repeats; a chime already started may finish once, and a silent Resolved notification remains until dismissed.
Battery percentage is an estimate of the sensor's usable voltage range, not a phone-battery gauge or a remaining-life guarantee. Sound and vibration require a capable device and suitable Android settings; verify them safely before relying on them.
6. Monitor in the background
After setup, the foreground monitoring service supports reception while the app is in the background or the phone screen is off. Keep Bluetooth, required permissions and the ongoing monitoring notification enabled. Review manufacturer battery restrictions if reception stops.
Return to the app and check each tire's latest status after a phone restart, force stop, permission change or long interruption. Android and device power policies can interrupt background execution. Opening Manage Sensors pauses normal monitoring. Choosing Quit stops monitoring and completes the current trip; reopen and verify monitoring before the next journey.
7. Use Android Auto
- Complete real setup on the phone while parked and verify sensor reception.
- Connect the phone to a compatible Android Auto host using the host's supported connection method. Follow Android Auto's own setup and permission prompts.
- Open Spartan RV TPMS from the host's available app list. Check that the configured tires, units, values and status match the phone.
- Use the head unit as a view-only display. Change layout, pair sensors, edit settings, export or delete on the phone while parked.
If the app is absent from the launcher, check phone/host compatibility and whether the installed app is authorized for Android Auto. A local QA build may need developer testing access; a public store release is a separate step. The PC Desktop Head Unit was used for bench verification. Android Auto host support can change, especially on older phones.
Unknown / missing measurements are not presented as healthy live readings. Apple CarPlay is supported by the Apple version.
8. Review Trips History
- Open Settings > Trips History. Recording starts automatically when a paired sensor sends a reading during monitoring.
- Select a trip to inspect its times, duration, monitor, status and stored measurements. An active trip is still recording; quitting monitoring completes it.
- An unexpected stop leaves an interrupted trip with its saved readings. Nothing is recorded while monitoring is stopped.
History is stored locally on this phone and works offline. Samples are recorded at the core's five-second history cadence when available; this does not make the sensor transmit every five seconds. Times use the phone's time zone. Each trip keeps the references saved at its start.
The automatic limit is 100 trips per monitor. When that limit is exceeded, the oldest trip without an unresolved critical alarm is removed. Trips ending with an unresolved critical alarm remain protected from automatic pruning and may take the count above 100. They can still be deleted manually. Export records you want to retain.
9. Explore offline charts
- Open a trip to see pressure and temperature timelines. Select all tires or the tire you want to inspect.
- Choose a time window or pinch to zoom. Drag left or right to move through the trip; choose Full trip to restore the whole interval.
- Tap a reading for its time and value. Tap a legend entry to bring an overlapping line forward. Review the displayed minimum, maximum and saved trip pressure references.
Gaps and invalid / unavailable periods stay disconnected. A smooth displayed line does not create additional recorded samples. Empty charts mean no usable readings in that selection; switch tires or restore Full trip before concluding data was lost.
What the trip graph looks like
This actual app capture illustrates pressure and temperature timelines with synthetic sample records. Your graph uses the tire positions, readings and references saved with your trip. Single, dual and triple axle setups are supported.

Read the chart
- Tires to display: inspect all saved tires or select a position.
- Time window: choose an interval; Full trip restores the complete recording.
- Zoom and pan: use + / − or pinch, then drag to inspect another part of the trip.
- Pressure: compare received readings with the saved trip reference.
- Temperature: read its timeline separately from pressure.
- Legend and readings: tap a legend entry to bring a line forward; tap a reading for its time and value.
Missing or invalid periods remain gaps. A line is drawn only from available stored samples.
Share the trip as CSV10. Export CSV records
- In Trips History choose Export all trips · CSV, or open a trip and choose Export trip · CSV.
- Select a destination in the Android share sheet. Check the destination and recipient before sharing sensor IDs, times and measurements.
- Open the resulting CSV in your chosen spreadsheet or file app. Export includes stored samples, both pressure/temperature unit systems and relevant alert / availability records. It does not fill reception gaps.
Exported copies belong to the destination you choose. Deleting app history cannot remove them.
11. Share or scan a trailer asset QR
Use QR Asset Sharing in Settings or the initial layout screen. This transfers the current trailer setup to another phone using the same branded app, without a cloud account.
Create and share
- Finish and save the trailer setup first.
- Enter an asset name and choose Create sharing QR. The code contains the vehicle model, axle layout, optional spare, cold-pressure baselines, units and assigned sensor IDs.
- Show the code to the recipient, or choose Share QR image and select an Android sharing destination. The PNG contains the same checked setup data. Sharing does not need camera permission.
Scan, review and apply
- Open QR Asset Sharing and choose Scan asset QR. Choose Allow camera when ready and grant Android camera permission. You can go back or close without granting it. If access is blocked, use Open app permissions. The torch control can help in low light.
- Aim the rear camera at a QR created by the matching branded app. CRC-32 is required and checked before preview. Missing or mismatched checksums, unrelated links, invalid fields, duplicate sensor IDs, unsupported layouts and the other brand's codes are rejected. Use Scan again after an error.
- Read the preview and independently verify the cold pressures against the vehicle placard and each sensor assignment. The checksum detects changed data; it does not prove who created the code.
- Check I verified the vehicle placard and sensor assignments, then choose Replace setup with this asset. Cancel import or Close leaves your setup unchanged.
- Import replaces layout, baseline, units and assignments. Existing Trips History remains on the phone. Imported sensors have no transferred live readings; verify fresh real reception before travel. A one-minute setup quiet period follows import while reception continues.
No photos, video or microphone recordings are taken. Camera preview stops when scanning closes or the app leaves the foreground. History, live measurements, alert overrides, consent and permission decisions are never transferred. Anyone with a QR copy can read its setup and sensor IDs; share it only with the intended recipient. Factory Reset removes app-cached QR images; copies already shared remain with their recipients.
QR code example and app screenshot
The exported PNG and phone screenshot below show how Spartan RV TPMS presents a sharing code.

5AB04713. Open it at full size to inspect the code.
On the receiving phone, use QR Asset Sharing > Scan asset QR in the matching branded app. A valid checksum opens the review step. Scanning alone does not apply a setup: check the placard and sensor assignments before confirming replacement.
12. Delete history or reset the app
- One trip: open the trip, choose Delete trip, read the warning and swipe all the way right to confirm.
- Current history scope: choose Clear history and complete the confirmation swipe. Live monitoring continues and new readings can start a new trip.
- Factory Reset: open Settings > Factory Reset, read the scope and complete the confirmation swipe to clear local pairing, settings and history and return to first setup.
- Cancel / partial swipe: does not confirm deletion or reset. Confirmed deletion cannot be undone.
Android Settings > Apps > Spartan RV TPMS > Storage > Clear data, or uninstalling, also removes app-local storage. CSV files already shared and support email copies remain outside these controls. There is no app account to delete. Support and data-deletion details.
13. Help and troubleshooting
Use the monitoring screen's help control to open Help & Support. App Behavior explains the alert rules; Support & Help opens email and website actions; About shows the app logo and installed version.
A sensor will not pair
Check the powered sensor and supported protocol, permissions and Bluetooth. Start a fresh scan before the approved learn action, keep only the intended sensor in learn mode, and retry within 60 seconds. Confirm its ID afterward. Restore any pressure released during learning.
A reading is searching, missing or stale
Check sensor power, distance, interference, permissions and the timestamp. Leave Manage Sensors to resume normal monitoring. Do not treat an old or unavailable value as a current tire measurement; inspect the tire safely.
Alerts are silent
Check the speaker mute state, initial setup quiet period, notification permission, Android volume / sound restrictions and device settings. Low battery and missing-sensor sounds occur once per monitoring session. Resolve the actual tire condition even if there is no sound.
Monitoring stops with the screen off
Recheck background permissions, Bluetooth and the manufacturer's battery settings. Confirm the monitoring service notification and return to the app to inspect fresh reception. Force stopping the app prevents monitoring until it is opened again.
History is empty or a chart has gaps
A paired sensor must send a reading during monitoring to start history. Check the selected trip, tire and time window. No-data periods are intentionally left as gaps; deleted or automatically pruned records cannot be restored by the app.
Android Auto is missing or differs from the phone
Check the compatible host, phone requirements and authorized app access. Complete phone setup first, then reconnect while parked. See the Android Auto section and report the app version, phone and host model if the mismatch remains.
Email support@spartanlync.com with Spartan RV TPMS, app version, phone / Android version, sensor model and a short reproduction. Include screenshots or CSV only when relevant. Do not send unrelated sensitive data.
14. Platform limits
This manual covers the delivered Android profile. The Apple version for iOS includes Apple CarPlay support. This manual describes the Android version; follow the Apple version for platform-specific setup. QR asset sharing and camera scanning are included in this Android update; bar pressure units are not included. The full monitoring UI is English.
