Android Remote Voice fails before thread/realtime/start after working August 23
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Samsung Galaxy S25 Ultra SM-S938U, Android 16, ChatGPT Android 1.2026.230. Windows 11 host running ChatGPT/Codex 26.825.5331.0.
Full Android Remote Voice worked for 56 minutes on August 23. Remote text still works. Force-stopping ChatGPT and relaunching restored the green Remote Voice coordinator button, but two empty Voice attempts returned "Voice connection failed. Try again." No thread/realtime/start request reached the Windows host.
A controlled host realtime probe reached OpenAI but returned HTTP 400: "AVAS requires OpenAI-Alpha: quicksilver=v2," code invalid_quicksilver_alpha_header.
Please verify the Android Remote Voice rollout assignment and client-owned realtime call protocol. The Android client appears unable to establish the required quicksilver v2 call before handing it to the Windows host.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Android Remote Voice failure with the listed Android and Windows versions, then trace whether a thread/realtime/start request is emitted. Compare the client-owned realtime call with the controlled probe, including the required quicksilver v2 header; done means the Android client establishes the call and reaches the Windows host.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100