[Android Remote] No Remote nav entry on home screen; Remote-home back arrow does nothing
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What issue are you seeing?
Summary
Remote works immediately after pairing and is fully functional, but on Android the system Back action behaves like an app-exit and the app does not restore the Remote surface after returning. Additionally, the in-app top-left back arrow on the Remote “home” screen is nonfunctional.
Actual Result (3-button navigation)
- After closing the app or pressing Android system Back (triangle) and then re-opening or restoring, ChatGPT returns to the normal ChatGPT home UI.
- There is no Remote nav entry anywhere (not in sidebar, not in Chat/Work switcher, etc.).
- Only re-pairing restores Remote, and only temporarily until the Remote screen is closed/minimized again.
- The top-left in-app back arrow on the Remote home screen shows no reaction when tapped.
Additional Observations
- If instead of system Back you leave Remote via Home (circle) or Overview (square), you can switch apps and return and the Remote screen stays active/working.
- With gesture navigation, a back-swipe also minimizes the app, but upon restore the app shows “Pairing…” and then returns to a working Remote screen (different from 3-button Back).
- The top-left in-app back arrow does work inside a Remote chat (it returns from the chat to the Remote main screen). It’s specifically nonfunctional on the Remote main/home screen.
- Clearing cache/storage and reinstalling the Android app did not change behavior.
- No Android Developer Options enabled.
What steps can reproduce the bug?
Preconditions
- Desktop host shows Remote enabled (“Allow other devices to connect” enabled); both iPad and Pixel appear connected/allowed on host.
- Android device is logged in and remains logged in (regular ChatGPT chats persist across restarts; not a sign-out issue).
- Pairing completes successfully and Remote becomes accessible immediately.
Repro Steps (3-button navigation)
- Open ChatGPT on Android.
- Pair to the Windows host (Remote becomes available and works).
- While on the main Remote screen (shows desktop connection + recent remote chats), press Android system Back (triangle).
- App minimizes.
- Restore the app from recents.
What is the expected behavior?
App returns to the Remote screen, or at minimum Remote remains accessible in the app UI (Remote nav entry still visible) and/or the in-app back arrow provides a way to exit Remote without breaking access.
Additional information
Environment
- Device: Pixel 8
- Android: 17 (Build CP3A.260905.009)
- Navigation: 3-button nav (triangle/circle/square); also tested gesture nav
- ChatGPT Android app: 1.2026.237
- Host: Windows
- ChatGPT desktop app (host): 26.831.20005
- Control case: same host + same account works correctly from iPad
Possibly related, but not duplicates
- #42063 — Android Remote direct-entry routing/state issue; Remote sidebar entry remains present in that report.
- #22800 — Android Remote state/list restoration issue after app restart; Remote surface itself remains accessible.
- #24454 — stale Android Remote state/session listing despite working host and iOS.
This report differs because Android system Back specifically causes the app to leave Remote and subsequently removes the Remote entry point from the app UI entirely.
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 flow on a Pixel 8 with Android 17 and 3-button navigation, then compare it with Home, Overview, and gesture navigation. The fix is complete when returning after system Back preserves a Remote entry or restores the Remote screen, and the top-left arrow on the Remote home screen provides a working exit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100