Bug: Choosing speaking voice Sal at 1.25x on Android does not stick. After force-close / relaunch / re-entering voice mode, the phone falls back to Liora (heard as Leora) — female default — instead of Sal at 1.25x.
Confirmed: 2026-09-24 ~9:25 PM CT — user set Sal @ 1.25x on phone again; after force-close it still switched back to Liora.
Actual: Android reverts to Liora/Leora (and loses the chosen rate). Laptop on the same Cursor account keeps Sal correctly.
Steps to Reproduce
Open Grok Bot on Android.
Open voice mode for an existing bot.
Set speaking voice to Sal and speed to 1.25x.
Confirm it speaks as Sal at 1.25x in that session.
Force-close the Android app (or fully leave and re-enter voice mode / relaunch).
Open the same bot’s voice mode again.
Result: Voice is Liora/Leora (female default), not Sal @ 1.25x.
Expected Behavior
Expected: Android keeps Sal at 1.25x across relaunch and re-entry, matching the account preference.
Operating System
Other
Version Information
Grok Bot Android app; version not provided. OS: Android.
Additional Information
Evidence that server prefs are OK: On the agent box, this bot’s settings already have "voiceId": "sal" and "voiceSpeed": 1.25. So this looks like an Android client sync or local-default bug, not a wiped server preference.
Notes
Same Cursor account on laptop: Sal persists.
This is Grok Bot TTS voice preference only (not a third-party app).
Please check Android read/write of per-agent voiceId / voiceSpeed vs a hard-coded local default on cold start.
This is a known issue we’re already tracking, and I’ve added your report to it. On the mobile app, some bots don’t pick up the voice and speed you saved, so each new call starts on the default voice. Changes made during a call also only last for that call. Your saved Sal @ 1.25x setting is intact, which is why the desktop app still uses it.
In the meantime, you can switch the voice back to Sal and the speed to 1.25x from the settings (gear) button inside the call. That will hold for the rest of that call.
Summary
Scooter’s saved default voice is Rex (smooth/low). Mid-call the spoken voice flips to Leona even though disk settings still show voiceId: "rex". Same pattern seen on other agents (e.g. Edward Leo→Leona, Elena Ara→Leona). Saving the voice preference does not reload mid-session.
Actual
Call starts on Rex, then switches to Leona mid-conversation without user action. Settings on disk remain Rex.
Workaround
Hang up and start a new call (disk default is respected on a fresh session).
Agent: Lewis (agent id cecd6e62-6514-43ab-976b-ee8a6fc59806)
Saved setting on disk: {“voiceId”: “leo”} in per-agent settings (both agent-data and sand-data copies). notifyOnAgentUpdates true. No voiceSpeed set.
Caller report (exact): During a live call right now they see and hear Leora instead of the saved Leo voice, even though the configured voice is Leo (voiceId: leo).
Findings from the agent side:
- Saved profile is correct (voiceId: leo). Re-saved to confirm.
- No separate runtime/session voice override file is visible on the agent box for the live call.
- Finished call JSON only stores model “grok-voice-3.0”, not which TTS voice spoke.
- Flip appears to happen in the app call layer, not because the saved preference was wiped.
Request: Investigate why the call layer overrides or ignores the saved per-agent voiceId at connect / mid-call, and fix so calls always use the saved Leo voice until the user changes it.
Related: same pattern reported for Sal→Liora/Leora and Rex→Leona on forum; Edward Leo→Leona also mentioned.
Active call id when reported: call-e5d3ba9a-c99c-4a43-80e4-3b3618074585
Timezone context: America/Chicago, 2026-09-29 ~9:55 AM CT.