Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
Where: Grok Bot Android app (phone). Desktop/laptop Grok Bot is fine.
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/voiceSpeedvs a hard-coded local default on cold start.
Thanks.
Does this stop you from using Cursor
No - Cursor works, but with this issue