LapMind Help
Troubleshooting
Check observable symptoms in a safe order, then verify recovery.
PlayStation & GT7
- PlayStation not foundThe saved target may be unavailable, the address may have changed, or the local network may block device traffic.
- The saved PlayStation IP is wrongA router or network change can give the console a different address.
- Console reachable, but waiting for GT7 telemetryConsole availability and receiver startup do not prove that valid fresh GT7 packets are arriving.
- Phone and console are on different networksDevices can both have internet access while being unable to reach each other locally.
- Guest Wi-Fi or client isolation blocks telemetryGuest/access-point isolation may prevent local devices from communicating even when internet works.
- Telemetry stops during a driveGT7 state, a network interruption, device background restrictions or ending the driving period can stop fresh data.
- Unexpected connection interruption or recoveryA service/network interruption can leave an incomplete Session without a trusted finish.
Voice & alerts
- No local voice outputLocal voice may be muted, TTS unavailable, output routed elsewhere, or no eligible event may have occurred.
- A checked callout is inactive or silentA saved checkbox can be structurally inactive under its current group/detail policy, or an event may not qualify.
- Voice volume is wrongLocal engineer gain, Android media volume and Discord member volume are separate controls.
- The preferred TTS voice is missingFemale/Male is a preference among the Android engine’s installed voices.
- Fuel laps remaining is unavailableThe estimator needs accepted lap consumption; refuelling or affected laps can delay a useful estimate.
- Lap Summary was not spokenSummary defaults OFF and has deliberate pit, fixed Final Lap entry and finish exclusions; ordinary events can also expire.
- Timed elapsed messages do not occurThe race may not be recognised as timed, the interval may be Off, or the elapsed fact may be unavailable/stale.
- Haptics are not feltThe master/child can be inactive, the device may not vibrate, or no supported Pit/Final event occurred.
Discord
- Bot token is rejectedThe token may be invalid, revoked, copied incorrectly, or validation may fail because Discord is unavailable.
- The private server is unavailableThe bot may not be installed in that server, or the wrong bot/token may be configured.
- The voice channel is unavailableThe selected server or channel permissions/type may be wrong.
- Bot permissions are incorrectServer roles and channel overrides can prevent visibility, joining or speech.
- The bot cannot joinConnection needs a valid token, accessible selected destination and usable internet/Discord service.
- Discord says Connected, but is silentBot connection alone does not mean your personal account is listening or that the audio route is audible.
- Bot and listener are in different channelsLapMind’s saved destination and your personal channel selection are independent.
- My personal Discord account has not joinedLapMind connects only its bot; it does not join your personal account on PlayStation or another device.
- PS5 Discord account is not linkedConsole voice chat needs Discord/PlayStation account linking outside LapMind.
- PS5 / PS5 Pro needs account relinkingAn older link can leave Discord voice unavailable; this is a conditional recovery, not a step every user must repeat.
- Bot is muted or chat balance hides itConsole/member mute, low volume or audio balance can hide a working voice stream.
- Automatic Discord connection does not occurAuto-connect requires a saved destination and fresh GT7 telemetry, not merely opening the app.
- Discord disconnected after FINISHThis is expected: FINISH ends telemetry and the bot connection for the driving period.
- A bot token may have been exposedA token is a credential and must be revoked at Discord if disclosure is possible.
Sessions & LAB
- A Session is missing from BrowseA tab/search filter, incomplete record, rejected disposition or lack of accepted Session data may explain absence.
- A Session is shown as InterruptedThe record did not receive a normal trusted completion and may be orphaned after interruption.
- Import is rejected or not appliedThe file may be incompatible, malformed, incomplete or fail current package validation.
- Session export is unavailable or file not foundSelection/live finalisation or the Android file/share destination may explain the unavailable action.
- A Session has no detailed lap dataThe drive may have been summary-only, details may have been evicted, or an older/imported package may not contain them.
- The track is identified incorrectlyAutomatic recognition can be uncertain; a stored label is not owner confirmation.
- A detailed map is missingThe selected layout may lack a detailed frozen Track Display even though a basic path/trace is usable.
- LAB shows only a basic outlineThis can be expected when detailed semantic map geometry is unavailable.
- Comparison or Reference is unavailableA best lap time may exist without a compatible detailed reference trace.
- LAB has gaps, unavailable time or an unexpected limitHistorical trace gaps and unsupported boundary/time evidence can limit review.
- Storage is full or the detail budget is reachedThe detail budget and phone free space are different constraints; active/protected records can exceed the budget.
- Recover a rejected SessionReject is reversible until permanent deletion; evicted detail is a separate issue.
Diagnostics & app
- Diagnostics recorder does not startRecorder state or insufficient free storage can prevent starting.
- Export capture is disabledRecording/stopping or absence of a usable local capture keeps export unavailable.
- An earlier diagnostic capture is unavailableThe local recorder is bounded and does not promise indefinite capture history.
- The Android device has insufficient free storageApp data, other files and protected traces can consume space beyond the selected detail budget.
- Did leaving the page stop LapMind?Back navigation, backgrounding, FINISH and Fully close LapMind have different ownership.
- Recovery after restart is unclearSaved preferences/destination are not proof of live services, and interrupted finalisation must not be counted as success.