[Android Auto] Profile rows should switch profile instead of opening an empty browse view #105

Open
opened 2026-09-28 06:46:04 +02:00 by alexander · 0 comments
Owner

Problem

Android Auto correctly shows the saved BookWave profiles under Profiles, but selecting a profile currently opens a new browse view that is empty.

That is not the intended interaction. A profile row is an action, not a browsable container.

This is a focused acceptance/regression bug against #65, which already defines Android Auto profile selection semantics.

Observed behavior

  1. Open BookWave in Android Auto.
  2. Open Profiles.
  3. Saved profiles are listed correctly.
  4. Select either the active or another profile.
  5. Android Auto navigates into a new child view.
  6. The child view is empty.

Expected behavior

Selecting a profile row should activate that profile directly.

For a different profile:

  • invoke the existing atomic profile-switch behavior defined by #65 / the normal BookWave profile-switch contract;
  • flush/preserve playback progress as required;
  • pause playback by default;
  • switch the active profile atomically;
  • invalidate/refresh the Android Auto browse tree;
  • return/show the refreshed Android Auto browse content for the newly active profile;
  • do not leave stale rows from the previous profile visible.

For the already-active profile:

  • do not open an empty child node;
  • either treat the selection as a no-op or refresh/return to the appropriate Android Auto browse level.

If a target profile is locked and cannot be unlocked safely through Android Auto, preserve the existing #65 lock policy and direct the user to unlock it on the phone rather than exposing its library.

Likely implementation concern

The profile entries appear to be exposed to Media3/Android Auto as browsable containers instead of actionable profile-selection items, or the click path is being interpreted as navigation to a child media ID rather than executing the profile switch.

Investigate the Android Auto browse item metadata/callback routing for profile rows and make the selection path execute the existing profile-switch command.

Do not introduce a second profile-switch implementation specifically for Android Auto.

Acceptance criteria

  • Profiles continues to list all saved profiles and clearly marks the active profile.
  • Selecting a different unlocked profile activates it directly.
  • Selecting a profile does not open an empty browse view.
  • Successful switching uses the existing atomic profile-switch behavior.
  • Android Auto browse content refreshes to the newly active profile.
  • No titles/artwork from the previous profile remain visible after the switch.
  • Selecting the already-active profile does not navigate to an empty child view.
  • Locked-profile behavior remains compliant with #65 and does not bypass phone-side unlock requirements.
  • Add focused regression coverage for the Media3 browse-item/click semantics where practical.
  • Verify physically on projected Android Auto.

Relationship

  • Parent/product contract: #65 — Redesign Android Auto browse home with artwork and profiles.
## Problem Android Auto correctly shows the saved BookWave profiles under **Profiles**, but selecting a profile currently opens a new browse view that is empty. That is not the intended interaction. A profile row is an **action**, not a browsable container. This is a focused acceptance/regression bug against #65, which already defines Android Auto profile selection semantics. ## Observed behavior 1. Open BookWave in Android Auto. 2. Open **Profiles**. 3. Saved profiles are listed correctly. 4. Select either the active or another profile. 5. Android Auto navigates into a new child view. 6. The child view is empty. ## Expected behavior Selecting a profile row should activate that profile directly. For a different profile: - invoke the existing atomic profile-switch behavior defined by #65 / the normal BookWave profile-switch contract; - flush/preserve playback progress as required; - pause playback by default; - switch the active profile atomically; - invalidate/refresh the Android Auto browse tree; - return/show the refreshed Android Auto browse content for the newly active profile; - do not leave stale rows from the previous profile visible. For the already-active profile: - do not open an empty child node; - either treat the selection as a no-op or refresh/return to the appropriate Android Auto browse level. If a target profile is locked and cannot be unlocked safely through Android Auto, preserve the existing #65 lock policy and direct the user to unlock it on the phone rather than exposing its library. ## Likely implementation concern The profile entries appear to be exposed to Media3/Android Auto as browsable containers instead of actionable profile-selection items, or the click path is being interpreted as navigation to a child media ID rather than executing the profile switch. Investigate the Android Auto browse item metadata/callback routing for profile rows and make the selection path execute the existing profile-switch command. Do not introduce a second profile-switch implementation specifically for Android Auto. ## Acceptance criteria - [ ] Profiles continues to list all saved profiles and clearly marks the active profile. - [ ] Selecting a different unlocked profile activates it directly. - [ ] Selecting a profile does **not** open an empty browse view. - [ ] Successful switching uses the existing atomic profile-switch behavior. - [ ] Android Auto browse content refreshes to the newly active profile. - [ ] No titles/artwork from the previous profile remain visible after the switch. - [ ] Selecting the already-active profile does not navigate to an empty child view. - [ ] Locked-profile behavior remains compliant with #65 and does not bypass phone-side unlock requirements. - [ ] Add focused regression coverage for the Media3 browse-item/click semantics where practical. - [ ] Verify physically on projected Android Auto. ## Relationship - Parent/product contract: #65 — Redesign Android Auto browse home with artwork and profiles.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
alexander/Audiobookshelf-Manager-Claude#105
No description provided.