When Android voice preference does not persist in Grok Bot

On the Android app, some Bots start each new voice call on the default speaking voice and speed even after you saved a different choice. Staff (Colin, Sep 25, 2026) on the forum report call this a known issue already under tracking. The account preference itself stays intact, which is why the desktop app on the same Cursor account still uses the voice and rate you saved.

A common pattern is choosing Sal at 1.25x on the phone, hearing it correctly for that call, then force-closing or leaving voice mode and finding the next call back on Liora (heard as Leora) at the default rate. Laptop sessions keep Sal. That split is the bug: mobile sometimes fails to pick up the saved voiceId and voiceSpeed when a new call opens.

What holds today

There is no permanent Android Settings path that forces the phone to honor the saved voice on every cold start yet. Do not chase a hidden preference toggle that product has not documented. Treat each new mobile call as starting on the default until the client fix ships, and use the in-call control below so the rest of that call matches what you want.

Desktop continues to read the saved preference. If you need the chosen voice without re-selecting it every time, run the call from the desktop app while the mobile bug is open.

Switch voice and speed inside the call

1. Open the Bot on Android and start a voice call the same way you usually do.
2. Tap the settings (gear) control inside the call, not only the account or Bot settings outside the call.
3. Set the speaking voice (for example Sal) and the speed (for example 1.25x).
4. Confirm the Bot is speaking with that voice and rate for the remainder of the call.
5. Expect the next new call to open on the default again until you repeat the in-call gear change.

Changes made during a call last for that call only. Leaving voice mode, relaunching the app, or force-closing and returning starts another call on the default for affected Bots.

Confirm the saved preference is still there

If desktop on the same account still speaks with Sal at 1.25x (or whatever you saved), the server-side preference was not wiped. The Android client simply did not apply it when the new call started. Re-saving the preference on desktop is optional and does not replace the in-call gear step on phone.

For how to start a voice call in the first place, see Start a voice chat with Grok Bot. Watch the forum thread for staff updates when a lasting mobile fix lands.

Pitfalls

• Looking for a permanent Android Settings fix that product has not shipped — staff’s current path is the in-call gear for the rest of that call.
• Changing voice only outside the call and expecting the next cold start to keep it — on affected Bots each new call starts on the default.
• Assuming the account preference was deleted because the phone reverted — desktop on the same account still using the saved voice means the preference is intact.
• Confusing this with a missing voice icon or spoken-result lag when the app is backgrounded — those are separate mobile voice issues with different staff guidance.